- DoneEdit /etc/conf.d/net as I suggested
- modprobe e1000 does not work but modprobe e100 does workthen do the modprobe
Code: Select all
ifconfigCode: Select all
modprobe e100Thanks again
Luke
- DoneEdit /etc/conf.d/net as I suggested
- modprobe e1000 does not work but modprobe e100 does workthen do the modprobe
Code: Select all
ifconfigCode: Select all
modprobe e100
I don't know why the appropriate module is not being loaded at boot. I've done several Gentoo installs over the last couple of years or so and I've never had this happen. However, except for the first time I've always compiled my own kernel, and chosen to have the ethernet driver compiled into the kernel rather than as a loadable module which rather guarantees it's going to be in memory. I guess this problem is something to do with the genkernel and the million and a half loadable modules it has to deal with. As I said earlier, the same has happened to my new install with a via ethernet chipset, and I had to modprobe the (via_rhine) driver in. I haven't rebooted yet, but I wouldn't be surprised if the driver doesn't load.shawl01 wrote:what do I need to do to make it stick after reboot?

happens to me too. The e1000 module is the driver for Intel Gigabit ethernet (e100 is for Intel pro100) but I don't have a sniff or whiff of Intel about this particular machine - AMD processor, VIA chipset motherboard and Nvidia graphics card. Ho hum.shawl01 wrote:incidentally it was loading the e1000 module and still is I can't find any file that calls it - strange
Code: Select all
PORTAGE_ELOG_CLASSES="info warn error log"
PORTAGE_ELOG_SYSTEM="save"