LinuxMCE Forums

General => Installation issues => Topic started by: Gryvel on March 25, 2008, 07:36:28 AM

Title: Unable to pxeboot - Kernel panic - not syncing: Fatal exception in interrupt
Post by: Gryvel on March 25, 2008, 07:36:28 AM
Hi!

Trying to pxeboot a Abit NF-M2 nView http://www.phoronix.com/scan.php?page=article&item=625&num=4 but with no luck. I get the error message Kernel panic - not syncing: Fatal exception in interrupt. What can I do to troubleshoot this?

Using LMCE 7.10 beta 4

/Gryvel
Title: Re: Unable to pxeboot - Kernel panic - not syncing: Fatal exception in interrupt
Post by: totallymaxed on March 25, 2008, 08:36:37 AM
Quote from: Gryvel on March 25, 2008, 07:36:28 AM
Hi!

Trying to pxeboot a Abit NF-M2 nView http://www.phoronix.com/scan.php?page=article&item=625&num=4 but with no luck. I get the error message Kernel panic - not syncing: Fatal exception in interrupt. What can I do to troubleshoot this?

Using LMCE 7.10 beta 4

/Gryvel

Hmmm... this might be the solution http://wiki.linuxmce.org/index.php/Unrecognized_NIC#Modify_modules_on_core (http://wiki.linuxmce.org/index.php/Unrecognized_NIC#Modify_modules_on_core)

But we really need more info about what printed to the screen... the complete text of the error would be useful.

Andrew
Title: Re: Unable to pxeboot - Kernel panic - not syncing: Fatal exception in interrupt
Post by: Gryvel on March 25, 2008, 08:37:20 PM
Just now I can't replicate the error message because the core won't start... See my other post http://forum.linuxmce.org/index.php?topic=4761.0

Please advice on how to reset/repair the core

Gryvel

Title: Re: Unable to pxeboot - Kernel panic - not syncing: Fatal exception in interrupt
Post by: totallymaxed on March 27, 2008, 01:04:26 PM
Quote from: Gryvel on March 25, 2008, 08:37:20 PM
Just now I can't replicate the error message because the core won't start... See my other post http://forum.linuxmce.org/index.php?topic=4761.0

Please advice on how to reset/repair the core

Gryvel



Orbiter #20 is the Core/Hybrids Orbiter... Hmmm... you could try doing a regen all & a reload from Web Admin -> Wizards -> Devices -> Orbiters

Andrew
Title: Re: Unable to pxeboot - Kernel panic - not syncing: Fatal exception in interrupt
Post by: OuZo on March 28, 2008, 10:46:02 AM
i also get an error when trying to network boot by laptop.
i get a kernel panic, then message tells me to try boot with noacpi or  apci=off
how or where do i do pass that to a network image?
thanks
Title: Re: Unable to pxeboot - Kernel panic - not syncing: Fatal exception in interrupt
Post by: totallymaxed on March 29, 2008, 08:14:37 AM
Quote from: OuZo on March 28, 2008, 10:46:02 AM
i also get an error when trying to network boot by laptop.
i get a kernel panic, then message tells me to try boot with noacpi or  apci=off
how or where do i do pass that to a network image?
thanks

You should be able to turn of acpi in your Bios setup

Andrew
Title: Re: Unable to pxeboot - Kernel panic - not syncing: Fatal exception in interrupt
Post by: Zaerc on March 29, 2008, 12:33:31 PM
You can add extra kernel parameters for the diskless MDs in /tftpboot/pxelinux.cfg/<01-MAC-ADDR-OF-MD>, just add them to the "APPEND" line.
Title: Re: Unable to pxeboot - Kernel panic - not syncing: Fatal exception in interrupt
Post by: OuZo on March 30, 2008, 12:07:31 PM
Zaerc, i had similar issues trying to network book a HP DV9607US laptop....

so i went to /tftpboot/pxelinux.cfg/ & changed default like so

$ diff default.ORIGINAL default
5,6c5
< APPEND root=/dev/nfs acpi=off vga=normal initrd=default/initrd ramdisk_size=10240 rw ip=all apicpmtimer
<
---
> APPEND root=/dev/nfs vga=normal initrd=default/initrd ramdisk_size=10240 rw ip=all apicpmtimer


so basically just removed acpi=off, since there are no BIOS options relating to acpi & i have the latest bios as far as i know

now, i get as far as... "we announce our self to the CORE"
its says loading diskless.sh
then it says rebooting... & reboots...
i tried a few times to boot the image but it always does these exact same things...


:/usr/pluto/diskless/74$ sudo du -hs .
2.5G    .


this leads me to believe that the CORE has finished creating the image.
htop shows nothing much happening on the core...