Hide Forgot
Description of problem: Hi, used F15Alpha LiveOS. With this card as primary adapter http://www.smolts.org/reports/view_device/NV44A%20%5BGeForce%206200%5D the Live OS will not boot. The default boot becomes textmode without any intentional action on my part, and then it gets hung up after dracut appears in the messages. The card works fine, even providing dual monitors, in Fedora13. If this card is set on secondary, it does not become activated, only the single output AGP card activates the monitors.
... activates its (1) monitor.
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. Please add drm.debug=0x04 to the kernel command line, restart computer, and attach * your X server config file (/etc/X11/xorg.conf, if available), * X server log file (/var/log/Xorg.*.log) * output of the dmesg command, and * system log (/var/log/messages) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Matej, when I boot with drm.debug=0x04, and even with '3 drm.debug=0x04' (also removing 'rhgb quiet') ... the behavior is as reported in the original description: textmode boot appears on both monitors and messages scroll by including a section that mentions drm and nouveau and concludes with 4 lines [ 1.885004] [<ffffffff8106ebd1>] kthread+0x84/0x8c [ 1.885004] [<ffffffff8100a9e4>] kernel_thread_helper+0x4/0x10 [ 1.885004] [<ffffffff8106eb4d>] ? kthread+0x84/0x8c [ 1.885004] [<ffffffff8100a9e0>] ? kernel_thread_helper+0x4/0x10 [ 1.885004] Coode: 00 10 00 76 ........... [ 1.885004] RIP [ 1.885004] RSP [ 1.885004] CR2 [ 1.885004] --[end trace f8fe9f9a1d13919c]--- and then goes into USB probing, recognizing the flash USB drive, keyboard, mouse, and a second USB drive. There is a pause and then 6 lines starting [ 30.7...] dracut: udevadm settle - timeout of 30 seconds reached, the event queue contains: [ 30.7...] /sys/devices=/pci000:00/0000:00:01.0/0000:01:00.0 (716) [ 30.7...] /sys/devices=/pci000:00/0000:00:01.0/0000:01:00.0/drm/controlD65 (822) [ 30.7...] /sys/devices=/pci000:00/0000:00:01.0/0000:01:00.0/drm/card1 (823) [ 30.7...] dracut: starting plymouth daemon And then 10 minutes pass: [ 601.....] [drm] nouveau 0000:00:0d.0: Setting dpms mode 1 on tmds encoder (output 1) [ 601.....] [drm] nouveau 0000:00:0d.0: nv_crtc_dpms:165 - settindhg dpms mode 3 on CRTC 0 [ 601.....] [drm] nouveau 0000:00:0d.0: Setting dpms mode 1 on vga encoder (output 2) [ 601.....] [drm] nouveau 0000:00:0d.0: nv_crtc_dpms:165 - settindhg dpms mode 3 on CRTC 0 [ 601.....] [drm ] nouveau 0000:00:0d.0: [ ] [drm:drm_crtc_helper-set-config] and then there is another pause for 10 minutes, and this section continues.
That is to say, the file is processed all over again, repeating the two types of stanzas. So I can't provide the files you are asking for. Do you recommend another ?
I mean that since the boot process seems to get stuck, All I can do is request.
Created attachment 486370 [details] Xorg.0.log from the working boot (video adapter priority swapped in BIOS the working version Matej Cepl : if you can suggest another way to boot with the newer videocard as the primary adapter, that would be great, beacause right now I can't get it to boot far enough to get a log file without rebooting. I will attach the files you requested but tehy are from booting up with the older AGP card as primary. Please note that the smolt record is at http://www.smolts.org/client/show/pub_7b966414-694a-4bd1-852f-89ac9ee07505 And I have tried both nvidia and ATI videocards in this system. All cards work well with Fedora13 and previous. No cards work completely with Fedora15, except this single-headed AGP card. ==== I am using F15alpha liveCD for the following: * /etc/X11/xorg.conf does NOT exist. * X server log file (/var/log/Xorg.*.log) * output of the dmesg command, andb * system log (/var/log/messages)
Created attachment 486371 [details] dmesg output dmesg , but from the working boot (AGP as primary, PCI as secondary.
Created attachment 486405 [details] /var/log/messages when successfully booted on AGP 1-output card /var/log/messages when successfully booted F15Alpha-Live on AGP 1-output card Will see if there's some way to retrieve such files from an unsuccessful boot.
(1) Note on HARDWARE ! this system has similar problems in booting F15alpha when ATI cards are installed. (One card dualhead works in F13; Will not boot in F15.) See Bug 679674 for the details. (Q1) Would an unsuccessful USB boot update on the USB the requested files * X server log file (/var/log/Xorg.*.log) * output of the dmesg command, and * system log (/var/log/messages) (Q2) Is there any way to extract them from the overlay file? (Q3) Otherwise I guess I'll have to install into a new drive to get the information you requested?
Thanks a lot.
(In reply to comment #10) > Thanks a lot. Do let me know if I can provide more information that would help solve the problem. I built this computer myself to be quiet and would like to keep it going with Fedora. It seems that there are others having problems upgrading "mature" computers past Fedora 13, so perhaps my reports will help track down the common causes.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping