Description of problem: Video output with ATI Radeon X800GTO is unusable (both text and graphics Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. urpmi kernel-desktop-3.14.32-1.mga4-1-1.mga4 2. reboot 3. no more video output --> can neither enter a shell nor a graphic session but I can log in the machine with ssh with no problem. I've tried with kernel-desktop-3.14.32-1.mga4-1-1.mga4 and kernel-desktop-3.14.18-3.mga4 with the same result. No problem with kernel-desktop-3.12.25-3.mga4-1-1.mga4 and previous releases. Hardware : Mainboard : ASUS M2VTVM-VM890 CPU : AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ Memory : GSkill DDR2 1Gb X2 (tested error free with memtest) lshw|grep Radeon gives : produit: R480 [Radeon X800 GTO] produit: R480 [Radeon X800 GTO] (Secondary) from /etc/X11/xorg.conf : Section "Device" Identifier "device1" VendorName "Advanced Micro Devices, Inc. [AMD/ATI]" BoardName "ATI Radeon HD 4870 and earlier" Driver "ati" Option "DPMS" EndSection No error in /var/log/Xorg.0.log Reproducible: Steps to Reproduce:
CC: (none) => tmb
Can you try 3.14.39 from core updates testing. If that does not help... Can you attach the following *.txt: as root do: lspcidrake -v >lspcidake.txt dmesg >dmesg.txt journalctl -b >journalctl.txt you may need to compress the journalctl.txt in order to attatch it to this report
Created attachment 6357 [details] dmesg from 3.12.25 (video OK)
Created attachment 6358 [details] dmesg from 3.14.39 (video KO)
Created attachment 6359 [details] journalctl -b from 3.12.25 (video OK)
Created attachment 6360 [details] journalctl -b from 3.14.39 (video KO)
Created attachment 6361 [details] lspcidrake from 3.12.25 (Video OK)
Created attachment 6362 [details] lspcidrake from 3.14.39 (Video KO)
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: NEW => RESOLVEDResolution: (none) => OLD