e100 misbehaviour
Alexander Apprich
a.apprich at science-computing.de
Tue Mar 1 14:49:11 UTC 2005
Remco Poelstra wrote:
> Alexander Apprich wrote:
>
>> pls, post your comlete /etc/modprobe.conf. Could you also try
>
>
> alias eth0 e1000
> alias snd-card-0 snd-intel8x0
> options snd-card-0 index=0
> install snd-intel8x0 /sbin/modprobe --ignore-install snd-intel8x0 &&
> /usr/sbin/alsactl restore >/dev/null 2>&1 || :
> remove snd-intel8x0 { /usr/sbin/alsactl store >/dev/null 2>&1 || : ; };
> /sbin/modprobe -r --ignore-remove snd-intel8x0
> alias usb-controller uhci-hcd
>
looks good.
>>
>> find /etc/ -type f | grep -i eepro100
>> find /boot/ -type f | grep -i eepro100
>
>
>
> Both give no results. Neither with e100 as argument to grep.
> I did see that in /etc/sysconfig/hwconf there is a section:
>
> class: NETWORK
> bus: PCI
> detached: 0
> device: eth0
> driver: e100
> desc: "Intel Corp. 82801BA/BAM/CA/CAM Ethernet Controller"
> network.hwaddr: 00:00:39:2A:06:3B
> vendorId: 8086
> deviceId: 2449
> subVendorId: 8086
> subDeviceId: 3013
> pciType: 1
> pcidom: 0
> pcibus: 2
> pcidev: 8
> pcifn: 0
hwconf comes from kudzu. Try changing the driver: e100 to driver: e1000
or driver = unknown. To me it seems that the module gets loaded before
/etc/modprobe.conf is reached at boot time. Did you try configuring the
NIC using kudzu or something else e.g. system-config-network*?
>
> Remco Poelstra
>
Alex
More information about the fedora-list
mailing list