Intel GMA 500 problems on Eee

[Kam Leo]

On Tue, Oct 27, 2009 at 4:48 PM, Colin Brace <cb at lim.nl> wrote:
>
> Hi all,
>
> I have installed F11 on an Asus Eee PC 1101HA which has the GMA 500 chipset.
> After running yum for updates, I now have two kernels installed:
>
> kernel-2.6.29.4-167.fc11.i586
> kernel-2.6.30.9-90.fc11.i586
>
> For the GMA 500, I installed the following:
>
> Oct 28 00:28:57 Installed: psb-firmware-0.30-4.fc11.noarch
> Oct 28 00:28:58 Installed: xpsb-glx-0.18-5.fc11.i686
> Oct 28 00:28:58 Installed: libdrm-poulsbo-2.3.0-10.fc11.i586
> Oct 28 00:29:46 Installed: rhpxl-1.12-2.fc11.i586
> Oct 28 00:29:48 Installed: system-config-display-1.1.3-2.fc11.noarch
> Oct 28 00:29:48 Installed: livna-config-display-0.0.23-1.fc11.noarch
> Oct 28 00:29:48 Installed: kmod-psb-4.41.1-10.fc11.2.i586
> Oct 28 00:29:51 Installed:
> kmod-psb-2.6.30.9-90.fc11.i586-4.41.1-10.fc11.2.i586
> Oct 28 00:29:58 Installed: xorg-x11-drv-psb-0.31.0-15.fc11.i586
>
> If I boot the original kernel, X boots OK, only the startup complains about
> not finding "psb.ko". Ok, that makes sense; I only have the 2.6.30 version
> installed. But if I boot the latest kernel, the boot process hangs at some
> point after "Starting UDEV..." (no error message is displayed).
>
> There are a few lines in the system log but they don't tell me much:
>
> Oct 28 01:13:05 pollux kernel: psb 0000:00:02.0: PCI INT A -> GSI 22 (level,
> low) -> IRQ 22
> Oct 28 01:13:05 pollux kernel: [drm] psb - 5.0.1.0046
> Oct 28 01:13:05 pollux kernel: [drm:psb_do_init] *ERROR* Debug is 0x00000000
> Oct 28 01:13:05 pollux kernel: psb 0000:00:02.0: firmware: requesting
> msvdx_fw.bin
> Oct 28 01:13:05 pollux kernel: fbcon: psbfb (fb0) is primary device
> Oct 28 01:13:05 pollux kernel: [drm] fb0: psbfb frame buffer device
> Oct 28 01:13:05 pollux kernel: [drm] Initialized psb 4.41.1 20090416 on
> minor 0
>
> Can anyone give me some pointers on how to determine what is going wrong
> here? The Xorg log isn't much help. Also, is there a way of forcing the boot
> process to stick with text-only? Booting at run level 3 doesn't seem to do
> the trick.

If you are complaining about the graphical boot screen just edit
/boot/grub/menu.lst and delete "rhgb" from the kernel stanza.

> Thanks.
>
> -----
>  Colin Brace
>  Amsterdam