Description of problem: X-Server crashed, console crashed Version-Release number of selected component (if applicable): 12.5 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 354989 [details] kernel crashdump
Created attachment 354990 [details] X-Server log
Created attachment 354991 [details] anaconda log
It seems like a problem with the nouveau driver for NVidia cards. Can you tell us what graphic card do you have? You can also try to force the installer to use vesa driver using the argument xdriver=vesa on the kernel command line during boot.
in german: 1. Geforce 8400 (G98) 2. mit dem vesa-Treiber habe ich auch schon probiert = automatischer neustart, kein Speicher-Abbild, keine Meldungen.
Please use english language, because most of developers are not german speaking. It didn't work, I understood that much, but the reasons...
Stefan, sprechen Sie bitte Englisch. Ich bin die einzige die Deutsch sprechen kann, aber verstehe ich "Speicher-Abbild" nicht... Martin, I *think* he's saying he tried with the vesa driver and an automatic restart, and got no image and no error message.
Andy, "Speicher-Abbild" is a crashdump ( comment #1 ). Yes, I was probing it in vesa-mode. -> x-server started, then a black screen and a beep, then hanged the PC up.
Got it. I've been having the same problem (or one that is very similar) with vesa for a while. Will poke ajax about it..
If you complete a text install and then try to launch X, does it still crash? If so, can you attach the log file from that crash?
Created attachment 355316 [details] /var/log/message I can't attach the log, because the console is frozen. (No keys, no log). Switching between the console is o.k. I have a log from after upgrade.
Created attachment 355317 [details] /var/log/Xorg.log
Created attachment 355374 [details] lspci dump
Created attachment 355375 [details] /tmp/X.log It's new log with 28.07.2009 boot.iso.
same? https://bugzilla.redhat.com/show_bug.cgi?id=514063 https://bugzilla.redhat.com/show_bug.cgi?id=513433
Created attachment 355407 [details] snowy screen It's definitly not. It's like this attachment.
How're the latest versions of everything from rawhide?
I've installed new kernel (2_6_31-0_125_rc5_git2_fc12), the snowy screen is gone, but kernel is very unstable.
can you try with latest kernel? 125 was known to be buggy. Later kernels can be found in Koji. try with the latest nouveau and kernel you can find in Koji. thanks! -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
(In reply to comment #19) > can you try with latest kernel? 125 was known to be buggy. Later kernels can be > found in Koji. try with the latest nouveau and kernel you can find in Koji. > thanks! > > -- > Fedora Bugzappers volunteer triage team > https://fedoraproject.org/wiki/BugZappers Adam, you are to late! I've updated the kernel yesterday and the nouveau last week. I can't test more because I've found another bug (#518220).
OK, I see... -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Is this OK now?
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.]
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
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. [Note please, that this is machine generated comment for large amount of bugs; due to some technical issues, it is possible we've missed some of the responses -- it is happens, please, just a make a comment about that; that we will see. Thank you]
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as INSUFFICIENT_DATA. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers