Hi Steve, Thanks for the reply .. I gave "modprobe eepro100" a shot and it looks like everything in the dmesg output regarding the eepro100 is successful - however, a different driver is being used than the "Intel" driver from my default SuSE 9.0 installation. When I did an "ifconfig eth0 up" and "ifconfig" though, I see a 32 character hardware address with lots of 0's. This is the same way the nic would come up before I did "modprobe eepro100" and was/is my clue that the nic is not working properly. The hardware address should be 16 characters I think, or at least it is when the nic works on my default SuSE 9.0.
From the Gateway 200 ARC specifications, this is my nic chipset:
IntelR ICH3-M integrated LAN Controller and i82562ET Platform LAN Connect (PLC) device Not sure if that is eepro100 compatible or not .. Anyone else have one of these chipsets? -----Original Message----- From: steve-ss [mailto:mail@steve-ss.com] Sent: Wednesday, April 21, 2004 9:01 AM To: SuSE Help mail list Subject: Re: [SLE] Mantel 2.6 upgrade and dead notebook nic .. On Wednesday 21 April 2004 14:56, Gerhard den Hollander wrote:
* dreadnought
(Tue, Apr 20, 2004 at 07:40:17PM -0700) I don't know much about kernels. Why does upgrading my kernel to Mantel's 2.6 series break the nic support? Any ideas on how to get it back?
Not to be rude, but if you don;t know much about kernels, you should steer clear of the mantel kernels, and esp. on notebooks simply stick to the stock SuSE kernel (2.4.21 I think was shipped with 9.0) .
Yes, 2.6 breaks the nic support but you can get it back easily by typing: modprobe nic-diver-name eg my nic driver is: eepro100 so I type: modprobe eepro100 I made it permanent on boot by adding the line: alias eth0 eepro100 to the file /etc/modprobe.conf HTH Steve. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com