So from the strace, it looks like it's failing while trying to load
vgahw. Maybe it'd be worth adding `Disable "vgahw"` in the Modules
section?
Of course, I wonder why it is trying to load vgahw - shouldn't it be
attempting to load -amd? According to the strace, prior to the vgahw
stuff, it does find the chipset as GeodeLX:
write(0, "(II) AmdProbe: Probing for suppo"..., 46) = 46
write(0, "(II) AmdProbe: Before MatchPciIn"..., 41) = 41
write(0, "(--) Chipset GeodeLX found\n", 27) = 27
...
write(0, "(II) AmdProbe: MatchPCI (1)!\n", 29) = 29
write(0, "(II) AmdProbe: CPUDetected 32!\n", 31) = 31
write(0, "(II) resource ranges after xf86C"..., 59) = 59
write(0, "\t[0] -1\t0\t0x00100000 - 0x0ffffff"..., 45) = 45
...
write(0, "(II) AMD(0): AmdProbe: result (1"..., 35) = 35
write(0, "(II) resource ranges after probi"..., 36) = 36
Then there's a bunch of hex stuff I don't grok, and it ends up deciding
to use vga:
write(0, "(II) Setting vga for screen 0.\n", 31) = 31
lseek(6, 4, SEEK_SET) = 4
write(6, "\7\0 \2", 4) = 4
write(0, "(II) Loading sub module \"vgahw\"\n", 32) = 32
write(0, "(II) LoadModule: \"vgahw\"", 24) = 24
Looks like it also attempted to load fbdevhw:
open("/usr/lib/xorg/modules/linux/",
O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 7
...
stat64("libfbdevhw.so", 0xbfc1c24c) = -1 ENOENT (No such file or directory)
Any of this mean anything to you guys?
--
amd driver fails to autoconfigure
https://bugs.launchpad.net/bugs/140051
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
