Description of problem: When I boot the KDE live cd (Fedora 9) then the screen turns reddish then white when rhgb loads or when loading X if I load w/o that parameter. After this happened, I decided to try to use the vesa driver (xdriver=vesa) and that doesn't work. It would load up to KDE but my screen would be blank the whole time. I could tell it loaded up into KDE because I could hear audio. I tried added Option ForcePanel to xorg.conf when I was using openchrome but to no avail, all that did for me was turn red to purple then to white. Note that this laptop works fine with Fedora 8 with openchrome with the Option "ForcePanel" added. This is a regression. Feel free to move severity to medium but obviously this is high and a show stopper for me :(. Version-Release number of selected component (if applicable): Default version in Fedora 9 How reproducible: Always Steps to Reproduce: 1. Load CD wait for rhgb to load 2. 3. Actual results: Screen turns reddish/brown then to white Expected results: To see rhgb. Additional info:
Created attachment 306432 [details] xorg.conf (disregard .new)
Created attachment 306433 [details] xorg log
Can you please add to the Device section of your xorg conf : Option "ActiveDevice" "LCD" Option "ForcePanel" and send the corresponding xorg log ?
Created attachment 306591 [details] new xorg log
X still doesn't start with those options. It goes blank. However, when I kill X it says X: symbol lookup error: /usr/lib/xorg/modules/drivers/openchrome_drv.so: undefined symbol: xf86strstr. Not sure if that's useful or not.
The undefined symbol is indeed a bug. I got a fix for it, but the fedora build system is currently under maintenance...
I am attaching a more recent xorg log. This is with your unofficial rpm that I obtained on irc. Also if I let X go out to the end I can hear the KDE log in music and it ends up with the screen being 1/2 black and the other 1/2 consisting of multicolored vertical lines.
Created attachment 306689 [details] Latest xorg log
xorg-x11-drv-openchrome-0.2.902-5.fc9 might work better for you. Available from Koji before it hits updates-testing. http://koji.fedoraproject.org/koji/taskinfo?taskID=629814
Well it works better for sure. The first time I tried the driver it loaded X (i.e. the screen came up with the options mentioned above) however it ultimately froze before fully loading KDE and per usually I was unable to recover my X log. The next time I tried it I had a scrambled X. So it looks like it's getting closer.
can you please try adding Option "NoAccel" ?
or better, first try Option "AccelMethod" "EXA" and if it still doesn't work, try Option "NoAccel".
Unfortunately that still didn't work. I am attaching a screen shot of what it looks like with the parameters added that you've mentioned.
Created attachment 306860 [details] screenshot of X
Could you please post the xorg log from xorg-x11-drv-openchrome-0.2.902-5.fc9 with Option "NoAccel" ?
Unfortunately I can't. It freezes my computer and I'm not able to ssh into it to recover it.
Any more ideas? I am now running Rawhide in hopes it will fix my problem. Seems the -7 openchrome driver gives a backtrace.
Chris, there's a new version in rawhide, xorg-x11-drv-openchrome-0.2.902-8.fc10. Does it work ?
Reporter, could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
I saw a white X a few days ago. It turned out to be the user account was set to use compiz, but I logged in from a machine using qemu-kvm with cirrus emulated hardware. The display was entirely white but I could tell that clicking things was working. Manually removing the compiz option so it runs metacity instead fixed the problem. Not sure if this is the same issue, but I thought I would mention this.
I'm downloading the latest alpha version of f10 to test this and I'll report on it when it finishes. Also it's very difficult for me to track rawhide on this laptop when the last time I used it I had no X so I can only really test this at milestone releases like alpha, beta, etc.
This is bug can be closed. The openchrome driver on Fedora 10 alpha 1 is working.
(In reply to comment #22) > This is bug can be closed. The openchrome driver on Fedora 10 alpha 1 is > working. Thx for testing, Chris. Could you please attach the xorg log and xorg conf ? I'll then close the bug.
No log, too bad, but the bug is fixed, so let's close it. Thanks and regards, Xavier
Sorry. My laptop is currently broken and was just sent in to HP for repair. I'll report on this when I get it back.