Bug 557447
|
Description
colin
2010-01-21 14:29:48 UTC
I forgot to mention that I did root# yum update kernel\* libdrm mesa\* plymouth\* xorg\* --enablerepo=updates-testing Before I tried the koji builds, but it was no better. kernel boot without nomodeset still fries monitor
using:
kernel-PAE-2.6.32.6-36.fc12.i686.rpm
Dual monitor still not vailable using :
libdrm i686 2.4.17-1.fc12
mesa-dri-drivers-7.7-3.fc12.i686
mesa-libGL-7.7-3.fc12.i686
mesa-libGLU-7.7-3.fc12.i686
glx-utils-7.7-3.fc12.i686
plymouth i686 0.8.0-0.2009.29.09.19.1.fc12
plymouth-gdm-hooks i686 0.8.0-0.2009.29.09.19.1.fc12
plymouth-libs i686 0.8.0-0.2009.29.09.19.1.fc12
plymouth-plugin-label i686 0.8.0-0.2009.29.09.19.1.fc12
plymouth-plugin-two-step
i686 0.8.0-0.2009.29.09.19.1.fc12
plymouth-scripts i686 0.8.0-0.2009.29.09.19.1.fc12
plymouth-system-theme i686 0.8.0-0.2009.29.09.19.1.fc12
plymouth-theme-charge i686 0.8.0-0.2009.29.09.19.1.fc12
plymouth-utils i686 0.8.0-0.2009.29.09.19.1.fc12
I am now seeing very similar to this after upgrade to Linux kernel version 2.6.32.9-67.fc12.i686. This is on a Dell Inspiron 6400 laptop with a Dell E228WFP LCD monitor attached (to analogue VGA port). This occurs at boot time with Plymouth and continues when GDM login panel is displayed and after Gnome starts up. The built in LDC panel appears to have no issues. Can you retry with F13 Alpha LiveCD? Created attachment 402802 [details]
Xorg.log from F13-Alpha-i686-Live-KDE.iso textual boot
As requested I have tried F13-Alpha-i686-Live-KDE.iso
[BTW: whose idea was it to make it impossible to boot from a Gnome Live _CD_ ? Idiotic.]
I get the boot menu but boot hangs immediately with blue screen on both monitors.
When I edit the kernel options to remove rhgb and quiet:
Can see the text mode boot console, which does switch successfully to higher resolution Frame Buffer text mode.
Boot progresses past udev and through services startup.
Fedora splash screen background appears mirrored on both monitors with moveable mouse pointer.
No progress from there.
No logon screen.
Am able to <ctrl><alt> f2-f12 to console.
Can <alt> f1 back to fedora splash screen.
dmesg and Xorg.log retrieved via ssh and attached here.
dmesg is filled with repetition of this error.
[drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !
[drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(3).
Created attachment 402812 [details]
dmesg from F13-Alpha-i686-Live-KDE.iso textual boot
Thank you for reporting back. Created attachment 405845 [details]
/var/log/messages from RC-5 F13-Beta-i686-Live-KDE.iso textual boot
I have tested with F13 RC5
As before machine hangs at boot.
As before I have to edit boot parameters to do a text boot and initialisation of drm radeon fails.
N.B To retreive log files by scp you first have to
<ctrl><alt> f2
/etc/rc.d/init.d/iptables stop
passwd --stdin root
service sshd start
Created attachment 405846 [details]
F13 RC5 Xorg.0.log
from RC5
F13-Alpha-i686-Live-KDE.iso textual boot
/var/log/Xorg.0.log
Created attachment 405871 [details]
F13 RC5 Xorg.0.log
I could not see any way to edit the attributes of the file that I uploaded
(from application/octet-stream to text/plain)
so I have uploaded it again.
F13 RC5 Xorg.0.log
from RC5
F13-Alpha-i686-Live-KDE.iso textual boot
/var/log/Xorg.0.log
Can you please test if kernel : http://koji.fedoraproject.org/koji/taskinfo?taskID=2110907 Helps with your issue. (In reply to comment #11) > Can you please test if kernel : > http://koji.fedoraproject.org/koji/taskinfo?taskID=2110907 > > Helps with your issue. Certainly. I will be happy to help in any way that I can. This latest test was the result of booting from the RC5 live KDE CD. How do you propose that I test this kernel? The machine currently has fully updated F12 on it and and I am understandably not keen to repeat the folly that was the 'upgrade' from F11 to F12 which left me with a machine that was unuseable for an extended period - and destroyed a monitor in the process. You can try force installing the kernel on f12 it should work. Created attachment 406247 [details]
Kernel panic on boot of kernel-PAE-2.6.33.2-41.fc13.i686
Kernel starts boot from grub menu but panics when
cannot find root device ( which is a normal IDE disk with LVM )
Sorry for the poor quality of this image, but it was the best that I could manage with my cameraphone. :-(
Here is what I did.
[root@A1200 koji]# rpm -iv kernel-PAE-2.6.33.2-41.fc13.i686.rpm
error: Failed dependencies:
grubby >= 7.0.10-1 is needed by kernel-PAE-2.6.33.2-41.fc13.i686
[root@A1200 koji]# rpm -iv kernel-PAE-2.6.33.2-41.fc13.i686.rpm grubby-7.0.13-1.fc13.i686.rpm
Preparing packages for installation...
package kernel-PAE-2.6.33.2-41.fc13.i686 is already installed
file /sbin/grubby from install of grubby-7.0.13-1.fc13.i686 conflicts with file from package grubby-7.0.9-1.fc12.i686
file /sbin/installkernel from install of grubby-7.0.13-1.fc13.i686 conflicts with file from package grubby-7.0.9-1.fc12.i686
file /sbin/new-kernel-pkg from install of grubby-7.0.13-1.fc13.i686 conflicts with file from package grubby-7.0.9-1.fc12.i686
[root@A1200 koji]# rpm -iv --force kernel-PAE-2.6.33.2-41.fc13.i686.rpm
error: Failed dependencies:
grubby >= 7.0.10-1 is needed by kernel-PAE-2.6.33.2-41.fc13.i686
rpm -iv --nodeps kernel-PAE-2.6.33.2-41.fc13.i686.rpm
here is relevant excert from grub.conf [these cut'n pasted from a remote terminal so dont line wrap properly]
title Fedora (2.6.33.2-41.fc13.i686.PAE)
root (hd0,2)
kernel /vmlinuz-2.6.33.2-41.fc13.i686.PAE ro root=/dev/mapper/vg_a1200-lv_root SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYT
title Fedora (2.6.32.11-99.fc12.i686)
root (hd0,2)
kernel /vmlinuz-2.6.32.11-99.fc12.i686 ro root=/dev/mapper/vg_a1200-lv_root SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABL
initrd /initramfs-2.6.32.11-99.fc12.i686.img
title Fedora (2.6.32.11-99.fc12.i686.PAE)
root (hd0,2)
kernel /vmlinuz-2.6.32.11-99.fc12.i686.PAE ro root=/dev/mapper/vg_a1200-lv_root SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEY
initrd /initramfs-2.6.32.11-99.fc12.i686.PAE.img
Created attachment 406593 [details] /var/log/messages from kernel-2.6.33.2-41.fc13.i686 Unfortunately Fedora13 Beta released today has old kernel 2.6.33.1-24 That seemed no better then F13 RC5 Fortunately I have downloaded livecd-i386-nouveau-200502020230.iso as part of the Radeon test day today. and that uses kernel-2.6.33.2-41.fc13.i686 Results are similar to those seen in Comment 5 When I edit the kernel options to remove rhgb and quiet: Can see the text mode boot console, which does switch successfully to higher resolution Frame Buffer text mode. Boot progresses past udev and through services startup. when I type startx from init 3 As before dmesg is filled with repetition of this error. [drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB ! [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(3). /var/log/messages and Xorg.log retrieved via ssh and attached here. Created attachment 406597 [details] /var/log/Xorg.0.log from Comment 15 This accompanies comment 15 startx showed a slightly garbled background graphic with a moveable mouse pointer that displayed no proper graphic -just a large randomly coloured square sprite. attached Xorg.log shows that VGA-0 and DVI-0 with both monitors seem to be detected ok. I updated related components first so for the sake of completeness I will paste the details here. Updating: desktop-effects i686 0.8.6-1.fc13 updates-testing 82 k gnome-applets i686 1:2.30.0-1.fc13 fedora 5.4 M gnome-icon-theme-extras noarch 2.30.0-1.fc13 fedora 360 k gnome-panel i686 2.30.0-1.fc13 fedora 1.9 M gnome-panel-libs i686 2.30.0-1.fc13 fedora 61 k gnome-python2-extras i686 2.25.3-17.fc13 fedora 49 k gnome-python2-gtkhtml2 i686 2.25.3-17.fc13 fedora 21 k gnome-python2-libegg i686 2.25.3-17.fc13 fedora 53 k gnome-terminal i686 2.30.0-1.fc13 fedora 1.3 M gnome-themes noarch 2.30.0-3.fc13 fedora 2.5 M gnome-vfs2 i686 2.24.3-1.fc13 fedora 794 k Updating: libX11 i686 1.3.1-3.fc13 updates-testing 585 k libX11-common noarch 1.3.1-3.fc13 updates-testing 188 k libX11-devel i686 1.3.1-3.fc13 updates-testing 1.0 M util-linux-ng i686 2.17.2-3.fc13 updates-testing 1.5 M Updating for dependencies: libblkid i686 2.17.2-3.fc13 updates-testing 109 k libuuid i686 2.17.2-3.fc13 updates-testing 61 k Success at Last! With use of the latest live build gfx_test_week_20100414_i686.iso which has the 2.6.33.2-46.fc13.i686 kernel and the use of the radeon.modeset=0 parameter I have finally been able to startx. It is still necessary to do a textual boot to init 3 first as graphical boot stops making progress after the progress bars finish and the blank screens display a moveable cursor arrow - although the two screens are now, for the first time, not mirrored but 'side by side' :-) Unfortunately from this state I cannot <ctrl><alt>f2 and it is not possible to SSH either so I am not able to provide any log files. I continue to see this on F12 with kernel-2.6.32.11-99.fc12.i686 on my Dell Inspiron 6400 laptop. [This has ATI Radeon Mobility X1400, which I neglected to mention earlier] Created attachment 407340 [details]
Xorg.0.log after upgrade to 2.6.32.11-99.fc12.i686
This is my Xorg log when connecting the second monitor after boot up with X & gnome running and enabling the second monitor using the gnome display preferences applet.
Now that F13-RC has been released I have tested the Live CD image. There have clearly been massive improvements over previous releases. dmesg shows that setup of DRM and radeon looks ok with all connectors recognised. I still have to boot textual to init 3 as before X is still not functional and Dual Head is still broken. I have captured some log files using ssh: I did 'lspci -vvnn > lspci.out' 'Xorg -configure' to generate xorg.conf.new and This generated Xorg.0.log.setup 'xrandr -display :0.0 --verbose > xrandr--verbose.out' looks fine. I did <alt> f2 to get me back to a shell and init 3 to stop X At the keyboard I typed 'X -config /root/xorg.conf.new' This generated the Xorg.0.log.setup I see that the configuration file generated recognises only one monitor. Created attachment 412533 [details]
boot log for F13-RC Live
/var/log/messages from init 3 boot of F13-RC Live
Created attachment 412534 [details]
'lspci -vvnn > lspci.out'
Created attachment 412535 [details]
auto generated xorg.conf
This is the config file generated by
'Xorg -configure'
Created attachment 412536 [details]
This is the xorg.log generated by 'Xorg -configure'
This is the xorg.log generated by 'Xorg -configure'
Created attachment 412537 [details]
This is the xorg.log generated by 'X -config /root/xorg.conf.new'
This is the xorg.log generated by
'X -config /root/xorg.conf.new'
Created attachment 412538 [details]
'xrandr -display :0.0 --verbose > xrandr--verbose.out'
I have upgraded to FEDORA 13 and no longer have this problem. This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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 Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |