ahhhh... I found the driver in /lib/modules/2.4.18-k7/kernel/drivers/net/ ----- Original Message ----- From: "Neal Pollock" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; "Shyamal Prasad" <[EMAIL PROTECTED]> Sent: Friday, September 27, 2002 10:19 PM Subject: Re: eth0 problem after kernal package upgrade
> Thanks Shayamal. I have the following lines from 'dmesg' on 2.2.20 kernel: > > "eth0: Macronix 98715 PMAC rev 37 at 0xd400, 00:80:C6:EA:C0:69, IRQ 4 > eth0: EEPROM default media type 10baseT. > via-rhine.c:v1.08b-LK1.0.1 12/14/2000" > > How can I discern the name of the driver module for 2.4.18 from this? > > Neal. > ----- Original Message ----- > From: "Shyamal Prasad" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, September 27, 2002 9:22 AM > Subject: Re: eth0 problem after kernal package upgrade > > > > "Neal" == Neal Pollock <[EMAIL PROTECTED]> writes: > > > > Neal> Thanks for the repsonse, here's my details: > > Neal> http://members.rogers.com/npollock1/sysinfo.txt > > > > Neal, > > > > I think the only thing you missed there is the kind of NIC you > > have. If you don't know this look in the output of 'lspci' for a > > hint. For example, on my machine I see this line in the lspci output: > > > > "00:12.0 Ethernet controller: VIA Technologies, Inc. Ethernet > > Controller (rev 70)" > > > > which gives me a good clue that this is supported by the via-rhine > > driver. If you can't guess what the driver is, try booting into your > > 2.2.x kernel and look in the output of dmesg for a line starting with > > "eth0'. In my case I might have seen something like this: > > > > "eth0: VIA VT6102 Rhine-II at 0xe400, 00:50:2c:03:26:a8, IRQ 11." > > > > which really does not offer a clue as to the driver name, but who > > knows, you might get luckier. If you don't have a PCI NIC this won't > > work (and it's been far too long since I messed with ISA cards to > > remember how to help you!). > > > > Now do the following as root: > > > > modprobe via-rhine #use the appropriate NIC driver module name > > ifconfig eth0 #to see if it works now > > ifdown eth0 #might fail, no worries > > ifup eth0 > > > > If you have /etc/network/interfaces set up correctly from earlier this > > should fix your problem. Then add a line to /etc/modules containing > > the name of your driver so the next time you boot things are okay. > > > > Cheers! > > Shyamal > > > > > > -- > > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > > > > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
