eepro100 driver in LiveCD 1.4_rc1
"Tom Caudron" <[email protected]> Fri, 1 Nov 2002 12:03:09 -0500
| Newsgroups | gmane.linux.gentoo.newbies |
|---|---|
| Message-ID | <[email protected]> |
I've installed Gentoo 1.2 on an older system and decided it is the way to go for my main box. Before starting the install, I went to Redhat's hardware browser and wrote down all the hardware and driver info, so as to make sure I got it right. Upon beginning the install I had some problems, however. The CD booted fine and I ran pci-setup. It detected everything fine. When I did a "modprobe eepro100", however, it couldn't find the driver. A quick look confirmed it. I did see eepro, but not eepro100. I tried the same with eepro and insmod failed. Still, I wasn't sure if that a normal message or not (against my better judgement I was optimistic). I went to the next step and ran "net-setup eth0", which also failed (telling me dhcpcd was already running, I think?). I had a look at the interface with "ifconfig eth0" and it said that it was both UP and RUNNING, with what looked like a valid IP, so I again foolishly plodded forward. I went forward. Partitioned everything, chroot'd the system and got as far as the first "emerge sync", which then failed to connect. I tried other stuff like "ping microsoft.com" to which it failed to resolve the name, let alone attempt a ping. Definately no network connection. I went on the Gentoo forums and found that other's had this problem (missing eepro100 driver in 1.4_rc1) but the answers weren't so helpful. They were conflicting and not clear, mostly. I looked in bugzilla and found one problem with eepro100 that seemed to be related to a usb conflict (not that same as my problem, I think), so I'm here hoping someone on here can help. :-) When I got the sync error, I ran "dmesg" and found that early on, it mentions an eepro100 driver (eepro100.c not eepro100.o) but I guess it doesn't load that driver, because later on it tries loading the eepro driver and spits this back out: eepro_init_module: Probe is very dangerous in ISA boards! eepro_init_module: Please add "autodetect=1" to force probe In the output of dmesg, that message gets repeated a few times, then it goes on to other stuff, then it comes back and repeats that message one last time. Are there plans to include the eepro100 driver in future iterations of the 1.4 CD? Can anyone offer me some advice about getting it running? Thanks in advance for any help. :-) -Tom Caudron