[K12OSN] Etherboot, kernel panic, 8139
ericbrow at gmail.com
Thu Jul 27 12:24:43 UTC 2006
In my lab this last year, I started getting those same errors on
random machines. Usually, a reboot or two would get things going
again. Sometimes it would only be one client on the network, other
times it would be a bunch of them.
I would replace a network cable, swap out a thin client, but I'd still
get these errors in a random client.
My k12 lab is closed off from the rest of the network behind my
server. Someone had ran a patch cable from the switch to the rest of
the network, so my network which was supposed to be closed no longer
was. I think that my clients were expirencing an IP conflict between
my server's internal nic and the district's router.
If you're sure this isn't your problem, you could try using a boot floppy.
On 7/27/06, Edward Holcroft <edward at netday.org.za> wrote:
> Hi list
> On k12 v5rc2 I get the following message when using Etherboot cards
> (Realtek 8139D chipset):
> RAMDISK: Couldn't find a valid RAM disk image starting at 0
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
> block (1.0)
> If I plug in a PXE card on the same client, it works fine. It happens
> with an upgrade from 4.4.1 of k12 as well as with a clean install.
> Works perfectly on k12 4.4.1.
> Is there perhaps an option-129 that may help? I've already tried
> 8139cp that Jim suggested on the ltsp list. No go.
> K12OSN mailing list
> K12OSN at redhat.com
> For more info see <http://www.k12os.org>
More information about the K12OSN