Bug 520030
Summary: | KMS:RV515M:X1400 backligth seems off (display goes blank on X startup with F12 Alpa) | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Amit Shah <amit.shah> | ||||||
Component: | xorg-x11-drv-ati | Assignee: | X/OpenGL Maintenance List <xgl-maint> | ||||||
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | low | ||||||||
Version: | rawhide | CC: | adam, amit.shah, awilliam, jglisse, jmoskovc, jnovy, mcepl, mcepl, rhe, xgl-maint | ||||||
Target Milestone: | --- | Keywords: | Reopened | ||||||
Target Release: | --- | ||||||||
Hardware: | All | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2009-11-13 10:47:35 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Amit Shah
2009-08-28 05:30:16 UTC
Can you try with radeon.modeset=0 instead of nomodeset=1 Created attachment 359024 [details]
/var/log/messages
radeon.modeset=0 works; gets me the startup bar and also X.
But it also shows
Unknown boot option `radeon.modeset=0': ignoring
Attaching /var/log/messages and Xorg.0.log
Created attachment 359025 [details]
Xorg.0.log
*** Bug 522034 has been marked as a duplicate of this bug. *** *** Bug 522050 has been marked as a duplicate of this bug. *** Tests from the F12 Radeon Test Day https://fedoraproject.org/wiki/Test_Day:2009-09-09_Radeon show that the LiveCD prepared for the test day too has this issue. can you re-try with a recent nightly image? http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ there've been quite a few changes since the report was filed. thanks! -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers I tried with the beta image and the machine reboots in a short while after booting begins. Before that, the plymouth screen appears and instantly goes off, leaving an fb display with a blinking cursor. Have there been changes since the beta-rc2 compose? since beta? yes, quite a lot. can't say if any of them would fix this but they can't hurt. please grab a nightly... -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Yay, with the 3 Nov nightly plymouth bootup + gnome desktop works fine! Can the others who had the same problem report success/failure as well? Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages (at least F12Beta, but even better if the very latest versions). Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you. If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you. [This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.] Amit, no-one else posted in this bug that they are seeing the same problem, so if it works for you now we can close it. Thanks for testing! -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers I just ran into this bug yesterday when testing RC4 on my laptop. I ended up with vesa driver, as radeon is not working for me either :( the pc is: Lenovo t60 with ati mobility X1400 I took a closer look to this and it seems that the problem is with the backlight, because I can see the grey gdm login screen. I tested it couple times and the problem is only with laptops LCD, if I connect an external monitor then it works fine (but only the external lcd). And when I put the laptop in the docking station, the backlight turns on. Jirka The docking station doesn't matter, it is the plugging/unplugging the power cord what turns on the backlight. Jirka Happens to me as well. Please everyone affected attach full dmesg and give the GPU you are using. Also gives output of : rpm -q kernel xorg-x11-drv-ati xorg-x11-server-Xorg Thanks It seems I blame a wrong component here, I'm using radeonhd bacause xorg-x11-drv-ati was unstable and it kills my X - e.g. running chromium-browser kills X server every time. I have these packages installed: kernel-2.6.31.5-127.fc12.x86_64 xorg-x11-drv-ati-6.13.0-0.10.20091006git457646d73.fc12.x86_64 xorg-x11-server-Xorg-1.7.1-7.fc12.x86_64 Jiri do you still get X endup being kill with this package when using xorg-x11-drv-ati with kernel modesetting activated (note that with radeonhd you can't have KMS enabled iirc) I don't use KMS with neither of the drivers (do you think enabling KMS would fix the stability problem??). And yes, my X dies everytime I try to open newegg.com in firefox (I have flash installed) and the other 100% reliable reproducer is: 1. open thunderbird 2. right click on some folder->properities->Check this folder for new messsages 3. and X dies ... Jirka Jiri i am closing this bug as the original reported don't have the issue anymore. Please test with KMS and if you have X crashing with KMS enabled please open a bug report for it. Otherwise we already have several bug against UMS (no kms) for firefox crashing the X server : https://bugzilla.redhat.com/show_bug.cgi?id=528390 https://bugzilla.redhat.com/show_bug.cgi?id=536832 https://bugzilla.redhat.com/show_bug.cgi?id=534142 https://bugzilla.redhat.com/show_bug.cgi?id=533105 Which are likely all duplicate and you more than likely experiencing the same issue. Note also that we don't work actively on fixing UMS bugs are we do care a lot more about KMS. Out of curiosity why don't you use KMS ? |