Description of problem:
Version-Release number of selected component (if applicable):
F11 preview (live cd)
Steps to Reproduce:
1. boot from the live cd into a white Macbook (Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller)
hangs in the gdm login screen (just before completing painting the user list)
shows the "autologin" user and allow the user to log in
everything works fine if booting with the "nomodeset" grub option
as a side note, the lower white bar of plymouth shows some unexpected artifacts
a clean installation from DVD (F11 preview) shows the same behaviour (during installation too).
You _always_ have to boot with the nomodeset option
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, if available) 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.
And of course you can edit /boot/grub/menu.lst and add that nomodeset keyword to the kernel line there to make it premanent.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
I have a similar problem and created a bug #495149 Perhaps you can find information you need here.
I need those information from the original reporter to know what we are talking about.
Created attachment 345250 [details]
Hello!I'm the original poster. I've just attached my Xorg.0.log. On that machine I don't have an xorg.conf.
With the latest update gdm doesn't even come out, and all I get after the boot now is a blank black screen with a corrupted mouse pointer (that work).
Although i can access the machine via ssh, i'm not able to switch to a working console via alt+Fn
thanks in advance!
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:
I see this on F11 on a Mac Mini after booting nomodeset.
[root@localhost ~]# lspci -nn | grep Graphics
00:02.0 VGA compatible controller : Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03)
Boot completes, Plymouth transitions to GDM and then GDM "hangs" before showing the user list. Mouse cursor is responsive but otherwise display is frozen.
More detail including logs to follow.
This is resolved for me with kernel 184.108.40.206-32 from F11 updates-testing. On a
Mac Mini with this chipset booting in legacy BIOS mode, I am now able to boot
with KMS, X starts in default UXA, GDM starts and automatically logs in as expected.
[root@localhost xsessions]# lspci -nn | grep Graphics
00:02.0 VGA compatible controller : Intel Corporation Mobile 945GM/GMS,
943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03)
[root@localhost xsessions]# rpm -q kernel xorg-x11-drv-intel
(In reply to comment #9)
> This is resolved for me with kernel 220.127.116.11-32 from F11 updates-testing. On a
> Mac Mini with this chipset booting in legacy BIOS mode, I am now able to boot
> with KMS, X starts in default UXA, GDM starts and automatically logs in as
That kernel resolved the bug for me too (Macbook "white") as they seems to have the same graphic chipset (same lspci output)
If that kernel resolved the bug for you (origina poster), can this bugzilla be closed?
(In reply to comment #11)
> If that kernel resolved the bug for you (origina poster), can this bugzilla be
since Paul's solution (comment #9) worked perfectly for me, I consider this bug be closed.
However, don't know if it is reasonable to close it before the working kernel hit fedora-updates.
But that's just a doubt that I have: you surely knows what do to :)
kernel-18.104.22.168-43.fc11 has been submitted as an update for Fedora 11.
kernel-22.214.171.124-43.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.
Kernel package which resolved this has been pushed to F11 stable updates. Can someone close this bug?