Red Hat Bugzilla – Bug 436708
graphics garbage and system lockup with intel 945GM (MacBook)
Last modified: 2008-11-02 19:48:57 EST
Description of problem: After upgrading to rawhide the intel 945GM graphics card in my macbook 13 will garble the screen and lock the system when logging into GNOME. Could be related to a misbehaving applet as X is fine up to a certain point, and works perfectly all the way through RHGB How reproducible: Always Steps to Reproduce: 1. Start computer 2. Log into GDM 3. Wait for crash to occur Actual results: Screen is garbled, cursor no longer moves, caps lock button fails to light up, so the system has panicked in some way Expected results: GNOME session to finish starting. Additional info: I have a bunch of things in my session startup including seahorse, and possibly others, this could be due to nm-applet as that is the last thing to be displayed every time it happens. Could be related to automount as a bunch of errors are thrown out to /var/log/messages just prior to the crash.
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 attach your X server config file (/etc/X11/xorg.conf) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. Could you please also try to run without any /etc/X11/xorg.conf whatsoever and let X11 autodetect your display and video card? Attach to this bug /var/log/Xorg.0.log from this attempt as well, please. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
I've just been toying with this, and started bits of gnome piece by piece. Its most certainly network manager applet starting up that causes it to crash. This is a macbook 13 with an atheros wifi card. I suppose its possible something is wrong with the ath5k driver which appears to be present on rawhide
P.S. can we change the component to network manager I don't think this is related to X anymore, sorry for the misfiling this is probably some kind of network manager panic.
Karl; can you get the output of lspci, and are you using the ath5k driver or madwifi?
Sorry for the delay, I'm using the ath5k driver its not functional though :/ can't seem to scan for networks :( lspci relevant line; 02:00.0 Ethernet controller: Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter (rev 01) Also this bug is no longer exhibited, in that it doesn't crash my system...
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
does this still happen? If so, what kernel version are you running?
Nope, no longer an issue, close it :)