When booting LiveCD 1.4_rc4 on an IBM ThinkPad R30, PIII/1G, ALi15x3-based, hwsetup crashes producing the following output: Autoconfiguring devices... <funny rotating prompt> Oops: 0000 CPU: 0 EIP: 0010:[<c01720d9>] Tainted: GF EFLAGS: 00010a87 eax: c7126000 ebx: c5718230 ecx: c71261b0 edx: c889e2e4 esi: 00000000 edi: c63c0dc0 ebp: c63c0dc0 esp: c5ed7f34 ds: 0018 es: 0018 ss: 0018 Process hwsetup (pid: 3983, stackpage=c5ed7000) Stack: c5718230 c712fba0 c0172a6a c5718230 c03331a0 c712fba0 c63c0dc0 ffffffe9 c77b6410 c0132818 c63c0dc0 c712fba0 00000800 c7152000 bffffe14 bffffd18 c013274e c7715ba0 c77b6410 00000800 c7715ba0 c77b6410 c7152000 00000003 Call Trace: [<c0172a6a>] [<c0132818>] [<c013274e>] [<c0132a91>] [<c0108a07>] Code: 8b 42 14 39 de 74 0b 50 e8 16 57 fa ff 85 c0 5a 75 04 31 c0 /sbin/runscript.sh: line 660: 3983 Segmentation fault hwsetup -p >/dev/null dmesg logs some additional info just before this event: Unable to handle kernel paging request at virtual address c889e2f8 printing eip: c01720d9 *pde = 072a3067 *pte = 00000000 When boot process is completed, the funny rotating prompt caused by '-p' option of hwsetup is still alive slowly advancing console cursor to the right. Killing hwsetup process, recovers normal cursor. Dafo Reproducible: Always Steps to Reproduce: 1. 2. 3.
ill look into this, up until now, weve been lucky to boot this laptop.
I have the same problem with my IBM ThinkPad iSeries 1200 (Model 1161-257). Even if killing the procesms, generated by the command "hwsetup -p", stops the annoying spinner, the real problem comes latter when executing "grub" command in the final steps of x86 Installation Guide. The same error hangs the probing for drivers of grub and just don't let the installation finish. After searching the Gentoo Foruns, I just discovered this thread (http://forums.gentoo.org/viewtopic.php?t=52800&highlight=hwsetup) that didn't help as much, since I can't disable or enable my nonexistent floppy disk deriver, with the "very simple" BIOS provided by IBM for this ThinkPad model.
does 1.4 release still have this problem?