Bug 502521

Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

When the anaconda crashes, please, switch to the console (Ctrl+Alt+F2) and copy /tmp/X* and /var/log/anaconda.xlog to some other place -- USB stick, some other computer via network, some on the Internet, and please attach it to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below.

I am not sure whether you were actually able to make X work for you; if yes, then the log files I am after are /var/log/Xorg.0.log and /var/log/dmesg. Please attach these instead.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

I have managed to run installation by using vesa driver, then installed nvidia proprietary drivers from rpmfusion and they work fine.

Created attachment 345455 [details]
X.log from installation process

Created attachment 345456 [details]
anaconda.log

also, when I switched into text mode, text is damaged but still readable.

I know the binary driver's working well for you, but I'd still like to resolve this.  Are you able to switch back to the nouveau driver, and attach the output of the "dmesg" command from after starting X with nouveau?

Also, if possible, are you able to grab a screenshot of the display?  With a camera would be fine, but an actual screenshot can be useful too.  Since you can't see the screen, booting to runlevel 3 (append "3" to the kernel commandline), logging in as root and running:

export DISPLAY=:0.0
startx -- -ac :0 & (sleep 10 && import -window root screenshot.png && killall X)

should get you a screenshot.

Thanks!
Ben.

This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

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.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

(In reply to comment #6)
> I know the binary driver's working well for you, but I'd still like to resolve
> this.  Are you able to switch back to the nouveau driver, and attach the output
> of the "dmesg" command from after starting X with nouveau?
> 
> Also, if possible, are you able to grab a screenshot of the display?  With a
> camera would be fine, but an actual screenshot can be useful too.  Since you
> can't see the screen, booting to runlevel 3 (append "3" to the kernel
> commandline), logging in as root and running:
> 
> export DISPLAY=:0.0
> startx -- -ac :0 & (sleep 10 && import -window root screenshot.png && killall
> X)

sorry for late response, I am attaching requested data.

when nouveau starts, at first screen is dark then its getting slightly green, then getting brighter, brighter till it becomes yellow.

see picture taken from camera.

Created attachment 354787 [details]
screenshot grabbed from the nouveau

Created attachment 354788 [details]
photo of what I see when nouveau is used

Created attachment 354790 [details]
dmesg.txt output after running nouveau

Just tested Fedora 12 Alfa... bug still exists :(
now pressing Alt+Ctrl+F1 / F2 doesn't switch me into text mode, so I am unable to save any log files.

does 'nouveau.modeset=0' as a kernel parameter change anything?

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

(In reply to comment #14)
> does 'nouveau.modeset=0' as a kernel parameter change anything?

"nouveau.modeset=0" uknown option: ignoring

(In reply to comment #15)
> (In reply to comment #14)
> > does 'nouveau.modeset=0' as a kernel parameter change anything?
> 
> "nouveau.modeset=0" uknown option: ignoring  

should be *unknow option

then blank screen, ctrl+alt+f1/f2 doesn't work

that message is normal, it doesn't mean the option didn't work. but obviously it doesn't help :/

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

(In reply to comment #17)
> that message is normal, it doesn't mean the option didn't work. but obviously
> it doesn't help :/

I've tried it again without option, same effect as before - blurry, damaged greenish screen - with option just blank.

how can I start livecd in safe graphics mode ie. vesa or how can I force nv to be used rather than nouveau?

Did you see *any* boot messages with nouveau.modeset=0?  Nouveau won't touch the hardware at all until X starts with that option, so if you get a blank screen before then you have something else wrong..

(In reply to comment #19)
> Did you see *any* boot messages with nouveau.modeset=0?  Nouveau won't touch
> the hardware at all until X starts with that option, so if you get a blank
> screen before then you have something else wrong..  

Not at home, so can't check it now, but before I got the blank screen fedora was loading showing a progress bar at the bottom of the screen - then in the moment when the X should start I got a blank screen and Live CD stopped spinning.

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.]

(In reply to comment #21)
> 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.

I don't want to upgrade Fedora 11 to Fedora 12 Beta to see whether this changese will work or not, but I am just running Fedora 12 Beta Live CD and it is working flawlessly - graphics on nvidia chip has been initialised correctly.

I assume full installation will work without any problems too as before I could not run Live CD as well as installation.

you got that message because the bug is filed against 'rawhide'. if it was filed before f11 came out and still exists in f11, we should change it to be against 11. I think we changed it to rawhide back when you were testing F12 Alpha. do you want to close this as it's working in 12, or re-set it to f11?

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

(In reply to comment #23)
> you got that message because the bug is filed against 'rawhide'. if it was
> filed before f11 came out and still exists in f11, we should change it to be
> against 11. I think we changed it to rawhide back when you were testing F12
> Alpha. do you want to close this as it's working in 12, or re-set it to f11?

I am going to install Fedora 12 when it comes out, so I am happy to close this as FIXED in CURRENTRELEASE, not sure whether the issue has been resolved in Fedora 11, but if you want I can test it for you.

eh, let's just close it.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

This issue still occurs with Fedora 12.  I first encountered the issue when I switched to Fedora 11 (via USB Persistent boot)...the prior Fedora 10 (or was it 9) worked fine.

I decided to give it another go since Fedora 12 has been released.
Same issue as described above.  The screenshot of the graphics issue already provided is all I see after boot.

Can you file a new bug report please.  These issues tend to be hardware specific, and this particular one is fixed.

OK..I'll open a new bug case and reference this one.
FYI: My laptop model and graphics card are the same as the original poster.

Dell Latitude D620
Intel Core 2 Duo T5600
1 GB RAM
NVIDIA Quadro NVS 110M