eth0 deactivates overnight...
Hello. After an upgrade to woody my eth0 deactivates when my machine is left on overnight. As eth0 is dhcp-driven, I suppose this is something about dhcp. But I can't spare enough time to look for the solution myself right now, I hope someone solved this problem before and can help me. Symptoma: * after I leave my computer on overnight, network is unreachable * ifconfig shows everything is right (at first glance, at least) * '/etc/init.d/networking restart' helps * os was upgraded recently from potato to woody Thanks for any hints. Adam ~~ Adam Galant o Programmer, network administrator O Telestar Electronics Ltd. /|\/` \ |_ phone: (+48) (022) 332 32 85 ' | |. |. ~~ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ETH0 not recognized
I'm coming up with Ethernet0 not being recognized. Now, back when we were in Potato, I would have looked to make sure that my modules were all set up correctly. But now in Woody, everything is automatic -- so what do I need to do to get it working? When I ifconfig, I get my loopback listed, but no eth0. Funny thing is, I can switch back to my pre-rebuild kernel, and it's recognized again. So where's the error? What do I need to do to get this set up? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Kernel upgrade, eth0 gone.
O Them Who Know, I upgraded the kernel from the Woody 2.4.18-bf2.4 that I installed with to a 2.4.19, by installing the kernel-image. All went well, initrd and all. But this morning, after booting my new kernel, eth0 is not up! That's where the LAN is, I dial out with PPP. These seem totally unconnected to me, and I'm puzzled. Whatever could have changed with the network? -- Juha Siltala -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: eth0 deactivates overnight...
On Tue, 2002-09-03 at 05:52, Adam Galant wrote: > Hello. > > After an upgrade to woody my eth0 deactivates when my machine is left on > overnight. As eth0 is dhcp-driven, I suppose this is something about > dhcp. But I can't spare enough time to look for the solution myself right > now, I hope someone solved this problem before and can help me. > > Symptoma: > * after I leave my computer on overnight, network is unreachable > * ifconfig shows everything is right (at first glance, at least) > * '/etc/init.d/networking restart' helps > * os was upgraded recently from potato to woody > > Thanks for any hints. > > Adam > > ~~ > Adam Galant > o > Programmer, network administrator O > Telestar Electronics Ltd. /|\/` >\ |_ > phone: (+48) (022) 332 32 85 ' | |. > |. > > ~~ > > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > Not certain, but *overnight* to me leads to thoughts of a daily cron job resetting eth0. I presume that your daily cron jobs start at about 6:25 am (a Debian default, iirc) - anything in your logs around then referring to it? A possibility is that something is supposed to do a quick recycle - say, obtain a new dhcp lease, and is failing at that time (such as requesting just at the time that the network's dhcp server is for some reason unavailable - maybe recycling, or its ethernet card is recycled.) -- Mark L. Kahnt, FLMI/M, ALHC, HIA, AIAA, ACS, MHP ML Kahnt New Markets Consulting Tel: (613) 531-8684 / (613) 539-0935 Email: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: eth0 deactivates overnight...
> > After an upgrade to woody my eth0 deactivates when my machine is left on > > overnight. As eth0 is dhcp-driven, I suppose this is something about > > dhcp. But I can't spare enough time to look for the solution myself right > > now, I hope someone solved this problem before and can help me. At what time does it deactivate. If you don't know, run the following in a console for the night: while ping -nc1 66.218.71.198; do sleep 10; done && date and look at that console again in the morning. Also, what's deactivation? What does `ifconfig eth0` say? Is the interface still UP and does not have an IP assigned, or any other combination of the two? what does this output: `pidof dhclient` in the morning? finally, can you confirm that your DHCP server remains operable throughout the night? -- martin; (greetings from the heart of the sun.) \ echo mailto: !#^."<*>"|tr "<*> mailto:"; net@madduck "i'm always frank and earnest with women. uh, in new york i'm frank, and in chicago i'm ernest." -- the long kiss goodnight msg00733/pgp0.pgp Description: PGP signature
[SOLVED] eth0 deactivates overnight...
Summary of the problem: * woody recently upgraded from potato * DHCP driven eth0 * when the computer was left running overnigth, in the morning pinging any host showed 'unknown host', pinging IP resulted in 'no route to host' * eth0 was up, and had correct IP address * routing table was empty (which I discovered after submitting the post) * /etc/init.d/networking restart brought the network back * the problem hasn't occured before upgrade from potato * DHCP server has been running for months without problems Solution (partial): Installed dhcp-client in place of pump (potato ran on dhcp-client, which was quietly changed to pump during upgrade process). The problem was probably pump config (or a bug). Most probably default lease time in pump (why no renewal?). Hard to tell now since I removed pump with config files. Thanks for all hints! Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ETH0 not recognized
> When I ifconfig, I get my loopback listed, but no eth0. > > Funny thing is, I can switch back to my pre-rebuild kernel, > and it's recognized again. > > So where's the error? What do I need to do to get this set up? > What does /etc/network/interfaces look like? Mike - This mail sent through IMP: http://horde.org/imp/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ETH0 not recognized
Sounds like your kernel isn't loading the module for your nic or something. I'm not a kernel expert so I can't help much. Perhaps run modconf to select the module for your nic. You may want to upgrade to a 2.4.x kernel too. Cheers, Mike Quoting "DSC@Siltec" <[EMAIL PROTECTED]>: > Mike Egglestone wrote: > > > > > When I ifconfig, I get my loopback listed, but no eth0. > > > > > > Funny thing is, I can switch back to my pre-rebuild kernel, > > > and it's recognized again. > > > > > > So where's the error? What do I need to do to get this set up? > > > > > What does /etc/network/interfaces look like? > > auto lo > iface lo inet loopback > # > # explanatory text is here > Auto eth0 > iface eth0 inet static > address 192.168.13.1 > netmask 255.255.255.0 > network 192.168.13.0 > broadcast 192.168.13.255 > gateway 192.168.13.254 > > > -This file is the same no matter which kernel I boot > up with. > > > One other thing that might help, is that during bootup, I noticed > ne2k-pci being loaded for the kernel that works. For the kernel > that doesn't work, I noticed only PCI devices being recognized at > certain locations -- but no ne2k-pci being loaded. > > Once I've booted, I can run "insmod -p ne2k-pci" on the one that works, > and I get back "module not found". But if I run "insmod -p ne", then > I get back that the module is installed. So I think that what starts > out > as ne2k-pci registers under ne (when it works). > > Under the broken kernel, I get back the following error: > > #insmod -p ne > /lib/modules/2.2.20/net/ne.o: unresolved symbol ei_open > /lib/modules/2.2.20/net/ne.o: unresolved symbol ethdev_init > /lib/modules/2.2.20/net/ne.o: unresolved symbol ei_interrupt > /lib/modules/2.2.20/net/ne.o: unresolved symbol NS8390_init > /lib/modules/2.2.20/net/ne.o: unresolved symbol ei_close > /lib/modules/2.2.20/net/ne.o: > Hint: You are trying to load a module without a GPL compatible license > and it has unresolved symbols. Contact the module supplier for > assistance, only they can help you. > > > > > > > > Mike > > > > - > > This mail sent through IMP: http://horde.org/imp/ > > > > -- > > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > - This mail sent through IMP: http://horde.org/imp/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel upgrade, eth0 gone.
Oh well, thinking about kernels and network devices I was enlightened and realized there are such things as modules :) All is well, sorry to waste your time and bandwith. -- Juha Siltala -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian eth0 full duplex
On Thu, 2002-10-17 at 23:01, Raghavendra Bhat wrote: > Joe T. posts: > > >> How do I find and/or set my eth0 interface to 100 Mb/s full duplex? > > I use this command to set the speed of my eepro card to 10 MBps full > duplex. `mii-tool --force=10baseT-FD --log eth0', maybe you need to > substitute 100baseT-FD in lieu of 10baseT-FD. You should start this > command via the run-level init scripts, preferably a level of 25 in > the rcS.d symlink dir. > I have fillowing in the /etc/modutils/3c59x file: post-install 3c59x /sbin/mii-tool --force=100baseTx-FD I bet something similar would work for eepros. Just watchi it if you have more then one ethernet card that need to difference modes. Sven -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian eth0 full duplex
On Fri, Oct 18, 2002 at 11:38:49AM +1000, Rob Weir wrote: > On Thu, Oct 17, 2002 at 01:08:01PM -0500, Joe Thykattil wrote: > > How do I find and/or set my eth0 interface to 100 Mb/s full duplex? > > Have a look at the output of dmesg, that should tell you. There is a discrepancy between dmesg and mii-tool: >From dmesg: eth0: Setting 100mbps full-duplex based on auto-negotiated partner ability 45e1. mii-tool: zsh % sudo mii-tool eth0: 10 Mbit, half duplex, no link ??? Johann -- Johann Spies Telefoon: 021-808 4036 Informasietegnologie, Universiteit van Stellenbosch "Delight thyself also in the LORD; and he shall give thee the desires of thine heart." Psalms 37:4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian eth0 full duplex
On Fri, Oct 18, 2002 at 10:04:00AM +0200, Johann Spies wrote: | On Fri, Oct 18, 2002 at 11:38:49AM +1000, Rob Weir wrote: | > On Thu, Oct 17, 2002 at 01:08:01PM -0500, Joe Thykattil wrote: | > > How do I find and/or set my eth0 interface to 100 Mb/s full duplex? | > | > Have a look at the output of dmesg, that should tell you. | | There is a discrepancy between dmesg and mii-tool: | | >From dmesg: | | eth0: Setting 100mbps full-duplex based on auto-negotiated partner | ability 45e1. | | mii-tool: | | zsh % sudo mii-tool | eth0: 10 Mbit, half duplex, no link | | | ??? | | Johann | | | -- | Johann Spies Telefoon: 021-808 4036 | Informasietegnologie, Universiteit van Stellenbosch | | "Delight thyself also in the LORD; and he shall give | thee the desires of thine heart." Psalms 37:4 | hi, i have the same exact output. dmesg says 100 mb while mii-tool says 10 mb. is it possible mii-tool only works with specific cards, or is a "network tool" rather than a "card tool"? i have two d-link nic's using the rtl8139too driver. according to the other pc, running some other os (for the kids :-(), it is also running at 100 - which it should - but doesn't tell my the duplex. my eth1 is connected to another d-link via a cross-over cable. i thought using a cross-over cable limited you to half-duplex? interesting. take care, jason -- -- | http://jharv.com | http://counter.li.org/| | 2.4.16-k6 | Debian GNU/Linux 3.1 Sarge| | [EMAIL PROTECTED] | registered linux user #202942 | -- msg07863/pgp0.pgp Description: PGP signature
Re: Debian eth0 full duplex
On Fri, Oct 18, 2002 at 11:40:35AM -0400, Jason M. Harvey wrote: > my eth1 is connected to another d-link via a cross-over cable. i thought > using a cross-over cable limited you to half-duplex? > interesting. This computer (with an 8139 ethernet card) is connected to my firewall (with an eepro100) using crossover, and both dmesg and mii-tool say I've got a full duplex connection. -rob msg08015/pgp0.pgp Description: PGP signature
eth0 problem after kernal package upgrade
i recently upgraded my kernel from 2.2.20 to 2.4.18 using a kernel image via dselect. Unfortunately when I boot the new kernel i cannot establish an internet connection. Am I correct in assuming that i need to to check: a) eth0 is properly configured b) dhcpclient obtained an IP inorder to troubleshoot this problem. i thought the new kernel would run all my old services and leave my system configuration untouched. what's happening? neal. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: eth0 problem after kernal package upgrade
Neal Pollock wrote: > i recently upgraded my kernel from 2.2.20 to 2.4.18 using a kernel image via > dselect. Unfortunately when I boot the new kernel i cannot establish an > internet connection. Am I correct in assuming that i need to to check: > > a) eth0 is properly configured > b) dhcpclient obtained an IP > > inorder to troubleshoot this problem. i thought the new kernel would run > all my old services and leave my system configuration untouched. what's > happening? > > neal. > > Neal, I have had this same problem. The cause is that some of the 2.2.XX series kernels have various NIC driver code built-into the kernel code and the NIC is thus detected automatically. The 2.4.XX kernels are designed to be modular and few have this code compiled into the kernel. Another complication is that at least one of the NIC driver modules has changed its name from the 2.2.XX series to the 2.4.XX series. This is the code for any RealTek 8139 chipset. Even if you were using the "rtl8139.o" module in 2.2.20, it doesn't exist in 2.4.18! The relevant new module is the 8139too.o module. Since you didn't say which NIC you have, it is hard to specifically diagnose your problem, but I would recommend you use modconf to insert the proper driver module for your NIC. This course of action would cover both situations described above. Alternatively, if you know the correct module for your NIC in the 2.4.18 kernel, then you can just add it to the /etc/modules file. Cheers, -Don Spoon- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: eth0 problem after kernal package upgrade
Neal Pollock said: > i recently upgraded my kernel from 2.2.20 to 2.4.18 using a kernel image > via dselect. Unfortunately when I boot the new kernel i cannot establish > an internet connection. Am I correct in assuming that i need to to > check: > > a) eth0 is properly configured > b) dhcpclient obtained an IP > > inorder to troubleshoot this problem. i thought the new kernel would run > all my old services and leave my system configuration untouched. what's > happening? do you have an eth0 interface? maybe the new kernel doesn't have a working driver for your NIC(unlikely but it is possible). what kind of NIC? 2.2.x to 2.4.x is a MASSIVE upgrade so it's not unusual to have such a problem IMO. so questions: what NIC chipset what driver are you using whats the output of 'lsmod' whats the output of 'ifconfig -a' whats the output of 'route -n' whats the output of 'dmesg' preferrably if you can post this on a website and post a link to the site rather then email everything that would be best, save some people some bandwidth. nate -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: eth0 problem after kernal package upgrade
"Neal" == Neal Pollock <[EMAIL PROTECTED]> writes: Neal> i recently upgraded my kernel from 2.2.20 to 2.4.18 using a Neal> kernel image via dselect. Unfortunately when I boot the new Neal> kernel i cannot establish an internet connection. Am I Neal> correct in assuming that i need to to check: I'm almost certain this is because your network driver is built as a module in 2.4.18. Most drivers are modules in 2.4.18 and it works very nicely once you get used to it. Add it to /etc/modules for the next time you boot. Just 'modprobe ' for now and use ifup/ifdown to see if comes back up. If this makes no sense to you feel free to ask for details. Good luck. Cheers! Shyamal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: eth0 problem after kernal package upgrade
Thanks for the repsonse, here's my details: http://members.rogers.com/npollock1/sysinfo.txt Neal. - Original Message - From: "nate" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, September 26, 2002 2:46 PM Subject: Re: eth0 problem after kernal package upgrade > Neal Pollock said: > > i recently upgraded my kernel from 2.2.20 to 2.4.18 using a kernel image > > via dselect. Unfortunately when I boot the new kernel i cannot establish > > an internet connection. Am I correct in assuming that i need to to > > check: > > > > a) eth0 is properly configured > > b) dhcpclient obtained an IP > > > > inorder to troubleshoot this problem. i thought the new kernel would run > > all my old services and leave my system configuration untouched. what's > > happening? > > do you have an eth0 interface? maybe the new kernel doesn't have a working > driver for your NIC(unlikely but it is possible). what kind of NIC? > > 2.2.x to 2.4.x is a MASSIVE upgrade so it's not unusual to have such a > problem IMO. > > so questions: > > what NIC chipset > what driver are you using > whats the output of 'lsmod' > whats the output of 'ifconfig -a' > whats the output of 'route -n' > whats the output of 'dmesg' > > preferrably if you can post this on a website and post a link to > the site rather then email everything that would be best, save some > people some bandwidth. > > nate > > > > > -- > 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]
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]
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]
1Re: eth0 problem after kernal package upgrade
a... 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]
Re: eth0 problem after kernal package upgrade
"Neal" == Neal Pollock <[EMAIL PROTECTED]> writes: Neal> Thanks Shayamal. I have the following lines from 'dmesg' on Neal> 2.2.20 kernel: Neal> "eth0: Macronix 98715 PMAC rev 37 at 0xd400,00:80:C6:EA:C0:69, IRQ 4 Neal> eth0: EEPROM default media type 10baseT. Neal> via-rhine.c:v1.08b-LK1.0.1 12/14/2000" Neal> How can I discern the name of the driver module for 2.4.18 Neal> from this? Never seen that one before I'd guess, first, that it is the via-rhine driver since the driver printed a line. Try 'modprobe via-rhine' with your 2.4.x kernel running and see if 'ifconfig -a' lists eth0 as being available. However a quick search of Google seems to indicate to me that that the Macroniz 98715 is (was?) supported by the tulip driver. So give 'modprobe tulip' a shot too. In fact I looked in my kernel source and the Macronix 98715 does seem to be supported by the tulip driver. Give it a shot. Hopefully this will bring a response from some one more knowledgeable than me. Good luck! Shyamal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 1Re: eth0 problem after kernal package upgrade
"Neal" == Neal Pollock <[EMAIL PROTECTED]> writes:
Neal> a... I found the driver in
Neal> /lib/modules/2.4.18-k7/kernel/drivers/net/
>> "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?
Which one? Like I said in my earlier post a few minutes ago, I'm
leaning towards the tulip driver. I believe the via-rhine driver is
just printing an empty line (it used to be a very verbose driver a
while back), and the "eth0" line is actually coming from the "real"
driver (which I'm *guessing* is tulip).
If you do get it work, please let us know! Improve the collective
knowledge base and all that.;-)
Cheers!
Shyamal
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 1Re: eth0 problem after kernal package upgrade
tulip worked beautifully. I apoligize for not mentioning the driver in my previous post. Shyamal you can read my mind ;) - Original Message - From: "Shyamal Prasad" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: "Neal Pollock" <[EMAIL PROTECTED]> Sent: Friday, September 27, 2002 11:20 PM Subject: Re: 1Re: eth0 problem after kernal package upgrade > "Neal" == Neal Pollock <[EMAIL PROTECTED]> writes: > > Neal> a... I found the driver in > Neal> /lib/modules/2.4.18-k7/kernel/drivers/net/ > > >> "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? > > Which one? Like I said in my earlier post a few minutes ago, I'm > leaning towards the tulip driver. I believe the via-rhine driver is > just printing an empty line (it used to be a very verbose driver a > while back), and the "eth0" line is actually coming from the "real" > driver (which I'm *guessing* is tulip). > > If you do get it work, please let us know! Improve the collective > knowledge base and all that.;-) > > Cheers! > Shyamal > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
