Comment 10 for bug 291294

Revision history for this message
Tore Anderson (toreanderson) wrote :

I think the Sempron is a 64-bit capable processor, so it makes sense that a amd64-* module is loaded even though you're using a 32-bit operating system. Anyway:

(EE) open /dev/fb0: No such file or directory

is telling, for some reason /dev/fb0 didn't show up when you loaded the sisfb kernel module. Either your particular chipset isn't supported by the sisfb driver and you're out of luck, or something else is amiss...

When I load the sisfb driver, I see the following appear in the dmesg output:

sisfb: Video ROM found
sisfb: Video RAM at 0xd0000000, mapped to 0xded00000, size 32768k
sisfb: MMIO at 0xdeee0000, mapped to 0xdec80000, size 128k
sisfb: Memory heap starting at 32160K, size 32K
sisfb: Detected SiS302LV video bridge
sisfb: Detected 1280x800 flat panel
sisfb: Detected LCD PDC1 0x00 (for LCD=CRT1)
sisfb: Default mode is 1280x800x8 (60Hz)
sisfb: Initial vbflags 0x8000012
Console: switching to colour frame buffer device 160x50
sisfb: 2D acceleration is enabled, y-panning enabled (auto-max)
fb0: SiS 760 frame buffer device version 1.8.9
sisfb: Copyright (C) 2001-2005 Thomas Winischhofer

This looks normal - as you can see it detects the LCD's native resolution of 1280x800, and it's assigned the name "fb0", and afterwards /dev/fb0 shows up as a character device with major number 29, minor number 0. Presumably udev is responsible for that. The text-only console has also changed resolution, so the text is smaller and crisper. You should look into why /dev/fb0 doesn't appear, if it is because of a failure in sisfb (should be apparant in dmesg if so), or if it is because udev doesn't correctly create /dev/fb0. If it's the first case you might be able to try a few module options (see "modinfo -p sisfb" for a list of available ones) and hopefully make it work, if it's the last case you can possibly work around it by doing "mknod /dev/fb0 c 29 0", perhaps also making sure the "video" group can write to the created device node.

You should probably also make sure that you're running the latest available kernel (2.6.27-7-generic here).

Good luck!

Tore