Hello everybody,
I'm new with Pluto, and read many of it on your site, and I'm very enthousiastic about the futures! I'm living in The Netherlands, and starting now to build a Core on a testmachine, a HP DC7600 with 1Gb ram and 250Gb HD (SATA).
The problem: The installation from CD1 ends good, but after the first reboot I got a message:
CPU: 0
EIP: 0060:[<c0111c16>] Not tainted VLI
EFLAGS: 00010246 (2.6.16.20-pluto-1-686 #1)
EIP is at setup_local_APIC+0x26/0x180
eax: 00000000 ebx: 00050014 acs: 00000000 edx: ffffffff
esi: 00000014 edi: c18e1fd0 ebp: 00000000 esp: c18e1f90
ds: 007b es: 007b ss: 0068
Process swapper (pid: 1, threadinfo=c18e0000 task=c18dba90)
Stack: <0>c0360bb9 c18e1fa8 c011768d c0100290 00000000 c0361389 00000000 c013b85b
00000008 00000000 00000000 00000000 00000000 0000000 00000000 00000000
00000000 c01002b8 0000007b 0000007b ffffffff 00000001 c01013b5 00000000
Call Trace:
[<c0360bb9>] verify_local_APIC+0x69/0x120
[<c011768d>] wake_up_process+0x1d/0x30
[<c0100290>] init+0x0/0x170
[<c0361389>] APIC_init_uniprocessor+0xb9/0x130
[<c013b88b>] cpu_callback+0x8b/0x90
[<c01002b8>] init+0x28/0x170
[<c01013b6>] kernel_thread_helper+0x5/0x10
Code: c3 8d 74 26 00 56 53 83 ec 0c 8b 1d 30 d0 ff ff a1 20 d0 ff ff 0f b6 f3 c? e8 18 83 e0 0f 0f a3 05 20 61 38 c0 19 c0 85 c0 75 02 <0f> 0b b8 ff ff ff ff a? e0 d0 ff ff a1 d0 d0 ff ff 25 ff ff ff
<0>Kernel Panic - not syncing: Attempted to kill init!
The ? above in the two hex-numbers are not readable for me on the screen.
And with this error everything stops. The following I've tried:
- to boot with the following command: linux noapic nolaic
--> This doesn't work, he says: " linux is not a package" or something
- to boot with the following command: linux26 noapic nolapic
--> This works; the boot continues, but again the same error after rebooting!
- Changed parameters in the BIOS from the HP PC
--> same error!
- Verify the CD-Rom (by the expert-installationmenu)
--> same error!
- Changed the bootlines, and added 'noapic' and 'nolapic' in the bootlines
--> same error
- Used another PC (same brand, same type)
--> same error
The PC's are brand new, and I tested Windows Vista (RC1) on them: no problem at all!
Can anyone help me with this strange problem?
Thank you in advance!
Theo Derks,
The Netherlands.
