Ok, so I tracked down some differences from the dmesg logs between the two kernel versions and it seems apparent that a different framebuffer device driver is used in the live CD kernel. I attach the intalled kernel (2.6.15-23) log for reference against the already attached log from the live CD kernel (2.6.15-26) The interesting lines are:
< [ 0.000000] Linux version 2.6.15-23-powerpc ([EMAIL PROTECTED]) (gcc version 4.0.3 (Ubuntu 4.0.3-1ubuntu5)) #1 Tue May 23 13:46:54 UTC 2006 > [ 0.000000] Linux version 2.6.15-26-powerpc ([EMAIL PROTECTED]) (gcc > version 4.0.3 (Ubuntu 4.0.3-1ubuntu5)) #1 Thu Aug 3 02:53:39 UTC 2006 and < [ 32.329540] aty128fb: Invalid ROM signature 8181 should be 0xaa55 < [ 32.329568] aty128fb: BIOS not located, guessing timings. < [ 32.329592] aty128fb: Rage128 RL AGP [chip rev 0x2] 8M 64-bit SDR SGRAM (2:1) < [ 32.364369] Console: switching to colour frame buffer device 128x48 < [ 32.364402] fb0: ATY Rage128 frame buffer device on Rage128 RL AGP > [ 65.884727] Using unsupported 1024x768 ATY,Rage128k at 94000000, depth=8, > pitch=1024 > [ 65.919532] Console: switching to colour frame buffer device 128x48 > [ 65.919556] fb0: Open Firmware frame buffer device on /[EMAIL > PROTECTED]/ATY,[EMAIL PROTECTED] The live CD kernel uses some other device driver that isn't working with the UseFBDev option "true" as it seems. ** Attachment added: "dmsg log from kernel 2.6.15-23" http://librarian.launchpad.net/4845578/dmesg-2.6.23-ppc.txt -- [R128] Dapper ppc install cd SIGSEGV initializing X on iMac https://launchpad.net/bugs/63072 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
