insmod (path is null)

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

 



I'm moving one step at time to my fully automatic install.

I added the 8139too.o module from the 2.4.7-10BOOT kernel.  I then
edited module-info.  I did not add anything to pcitable. I looked but
did not see anything that looked similar for say a 3c5x9 ethernet card. 

I then created a bootable cdrom using this new image.  It boots,
/sbin/loader gets run, and then I get a screen asking for me to chose a
ethernet interface, I can see the text I added, I select that and then
get "Failed to insert 8139too module."   If I switch to virtual console
3 I see "going to insmod 8139too.o (path is null)"

I double checked the ISO image to be sure that the 8139too.o file is
actually in modules.cgz and it is.

Two questions 

Any idea how to fix the path is null problem? 

If the above is solved will I still be prompted to select my NIC?  My
goal is to have a NO KEYBOARD required install. While selecting a NIC is
trival it does require human intervention and I'm trying very hard to
avoid that.  :)  Once the above is solved, if I'm still prompted to
select a NIC is there anyway to get around that?

btw - Linux on the desktop ROCKS!!  :)


Thanks,
Chad









[Index of Archives]     [Red Hat General]     [CentOS Users]     [Fedora Users]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux