Bug 468294
Summary: | F10 Blackscreen with cursor then whitescreen after kernel update | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Gerald Cox <gbcox> |
Component: | kernel | Assignee: | Dave Airlie <airlied> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | rawhide | CC: | gerwinkrist, jlayton, kernel-maint, phiporiphic, quintela, zaitcev |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-10-29 01:59:34 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
Gerald Cox
2008-10-23 22:21:56 UTC
Created attachment 321353 [details]
results of dmesg of system, before X started
Created attachment 321354 [details]
Xorg.0.log when whitescreen occurs
Created attachment 321355 [details]
Xorg.0.log when blackscreen occurs
*** Bug 468334 has been marked as a duplicate of this bug. *** This looks the same as 468369. Applied: kernel-2.6.27.3-44.fc10.x86_64 Problem still exists. Attaching new dmesg and Xorg.0.log. Also, found that what is occurring without "nomodeset" parameter is: 1. Black screen with cursor blinking in upper left hand corner of screen 2. Then white screen with some "sparkles" appears 3. Then hang 4. Pressing power button without holding it down signals normal system shutdown Workaround is kernel 2.6.27.3-30.rc1.fc10.x86_64 Created attachment 321508 [details]
dmesg with kernel 2.6.27.3-44
Created attachment 321509 [details]
Xorg.0.log with kernel 2.6.27.3-44
Created attachment 321510 [details] xorg.conf being used due to bug 467983 For clarity purposes, problem also occurs when "nomodeset" is specified. *** Bug 468369 has been marked as a duplicate of this bug. *** Same problem here, seems only to happen with ATI gpu's. I have some other symptons actually: normal: - if plymouth is loaded (no bar comes up), my monitor starts blinking and nothing happens with nomodeset: - I see the plymouth bar running till end .... nothing happens Really nasty, anyone knows where to find "old" working kernels, forced to use a fc9 kernel now ... I'm having similar problems... You can get older kernels from koji: http://koji.fedoraproject.org/koji/packageinfo?packageID=8 *** Bug 468505 has been marked as a duplicate of this bug. *** My symptoms are similar. When X starts, I get a "garbage pattern" with horizontal lines on the screen (maybe the result of uninit'ed video RAM?). If I boot with nomodeset, I also get a black screen when X starts. My video chip is: 01:05.0 VGA compatible controller: ATI Technologies Inc Radeon XPRESS 200M 5955 (PCIE) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device 30ae Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 66 (2000ns min), Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 17 Region 0: Memory at c8000000 (32-bit, prefetchable) [size=128M] Region 1: I/O ports at 9000 [size=256] Region 2: Memory at c0100000 (32-bit, non-prefetchable) [size=64K] [virtual] Expansion ROM at c0120000 [disabled] [size=128K] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Kernel modules: radeonfb, radeon Let me know if you need other info. While I haven't tried it, the machine seems to be responsive when it's in this state. It's just the display that's problematic. I can probably set it up so that I can ssh into the laptop when it's in this state and collect other info if it'll be helpful. Applied: kernel-2.6.27.4-47.rc3.fc10.x86_64 Problem still exists. No change. Workaround continues to be: kernel-2.6.27.3-30.rc1.fc10.x86_64 Applied: kernel-2.6.27.4-51.fc10.x86_64 Problem still exists. No change. Workaround continues to be: kernel-2.6.27.3-30.rc1.fc10.x86_64 Applied: kernel-2.6.27.4-58.fc10.x86_64 Problem resolved. Closing. Nice razzle/dazzle startup eye-candy btw... ;-) |