Re: 8139too.o: init module: No such device

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I have had numerous issues with the 8139too and Linux machines.  I know
others have them working just fine, but then are a constant headache for me.
So I switched to INTEL or 3COM nic cards and don't have any issues there.

  Tom
----- Original Message ----- 
From: "regis" <crescen7@xxxxxxxxxx>
To: <redhat-list@xxxxxxxxxx>
Sent: Saturday, October 04, 2003 12:06 PM
Subject: Re: 8139too.o: init module: No such device


> Thanks for the response Raymond,
>
> I considered that, but the network card works fine when I boot the machine
to
> Windows.
>
> That leads me to another thought.  The last time in Windows I did an
> "upgrade" of the
> Yahoo Messenger.  Is it possible that the "upgrade" hosed the network card
so
> that it
> causes the error I'm getting?
>
> Any thoughts appreciated.
>
> Regis
>
>
> Raymond Fung wrote:
>
> > Regis,
> >
> > Looks like your network card was dead. Try swapping in a spare and you
> > can tell.
> >
> > Regards,
> > Raymond Fung.
> >
> > On Sat, 2003-10-04 at 04:32, regis wrote:
> > > I've had a working desktop installation of Redhat 7.1 for about 2
> > > years.  No big problems.  Yesterday it failed to boot giving the
> > > following message:
> > >
> > > /lib/8139too.o: init_module: No such device
> > > Hint: insomd errors can be caused by incorrect module parameters,
> > > including
> > > invalid IO or IRQ parameters
> > > Error: /bin/insmod exited abnormally
> > > Mounting /proc filesystem
> > > Creating root device
> > > mount error 19 mounting ext2
> > > pivotroot: pivot_root(/sysroot, /sysroot/initrd) failed:2
> > > Freeing unused kernel memory: 252k freed
> > > Kernel panic: No init found.  Try passing init= option to kernel
> > >
> > > I can boot to "linux rescue" using the CD.  I can mount the root
> > > filesystem.  I've checked to make sure  I have an initrd sub-directory
> > > with correct permissions.  I've run fsck and the filesystem is fine.
> > > So I'm guessing it's a problem somewhere in the 8139too module.  I
tried
> > > to install it manually using insmod, but it failed.  I tried
recompiling
> > > the module from the source, but I'm not to well versed in compiling
from
> > > source,  so after not finding anything more specific in the archives
or
> > > google, I thought I'd try the list.
> > >
> > > Any ideas on how to trace down this problem?
> > >
> > > thanks,
> > >
> > > regis
> > --
> > Raymond Fung <raymondf@xxxxxxxxxxxxxx>
> >
> > --
> > redhat-list mailing list
> > unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
> > https://www.redhat.com/mailman/listinfo/redhat-list
>
>
> -- 
> redhat-list mailing list
> unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/redhat-list
>


-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

[Index of Archives]     [CentOS]     [Kernel Development]     [PAM]     [Fedora Users]     [Red Hat Development]     [Big List of Linux Books]     [Linux Admin]     [Gimp]     [Asterisk PBX]     [Yosemite News]     [Red Hat Crash Utility]


  Powered by Linux