Messages

16

Users / Re: MD PXE Boot, used to work, now fails

« on: February 25, 2010, 06:47:51 pm »

No, I cannot PXE boot any computers off of the core.  Something must have gotten screwed up possibly when I updated sqlCVS or maybe during an apt-get update.  Either way I am going to wait until another beta or RC comes out (I understand it may be months) and format and re-install.

17

Users / Re: MD PXE Boot, used to work, now fails

« on: February 23, 2010, 06:55:31 pm »

Yeah it was exactly the same error.  There is a 60 second timeout before the kernel panic.  I didn't wait the 60 seconds before I started my last post.  I am with wierdbeard65, I do not think it was the hardware, as I tried a whole different computer, with different memory.  The only software change I would have done is to update sqlcvs.  Once I get all my DVD ISOs backed up onto another computer, I will probably format/re-install unless anyone has any other ideas.

18

Users / Re: MD PXE Boot, used to work, now fails

« on: February 23, 2010, 02:06:06 am »

I took purps' advice and tried PXE booting a whole different computer.  It did still use the e100 module however.  Similar results.
IP-Config: eth0 hardware address 00:09:6b:38:c4:5c mtu 1500 DHCP RARP
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex

That is right before where it would stop before and say
/init: .: line 1: can't open /temp/net-eth0.conf
kernel panic - syncing: attempted to kill init!

Any other ideas?

I suppose I could try to PXE boot a laptop or something that uses a different module...?

19

Users / MD PXE Boot, used to work, now fails

« on: February 22, 2010, 09:34:11 pm »

Getting message:
/init: .: line 1: can't open /temp/net-eth0.conf
kernel panic - syncing: attempted to kill init!
When booting Media Director

After searching the forums, I followed the directions on the wiki for adding module that are at http://wiki.linuxmce.org/index.php/Unrecognized_NIC#Modify_modules_on_core

No change.  By the way my ethernet device uses module e100.

I have also tried removing the device from the media directors page in web admin, and re-running the diskless build scripts.  I have also re-booted the core several times.

Everything was working fine before, and then I had to turn off the media director to move the power cord and after I booted it back up I got these errors.