eth0 problem
Greetings all, since I need to install the wireless device driver for the Debian system, so I compiled and installed the 2.6.13.2 version kernel, but the eth0 (wired-ethernet card) now cannot be found using the newer kernel. Some kinda :eth0: no such device is displayed on the screen during booting procedure. I guess that's because I incautiously removed the necessary ethernet card driver when I was doing the make menuconfig part. How can I re-install those drivers for the eth0? (I am not sure which one is the precise driver, but I'm sure it is contained in the kernel source). Thx a lot! Regards, Deephay Z -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: eth0 problem
sorry for this dupicate post, I just thought the post through the usenet is not going to sucess.. On Tue, 20 Sep 2005 00:38:51 +0800 Deephay Z [EMAIL PROTECTED] wrote: Greetings all, since I need to install the wireless device driver for the Debian system, so I compiled and installed the 2.6.13.2 version kernel, but the eth0 (wired-ethernet card) now cannot be found using the newer kernel. Some kinda :eth0: no such device is displayed on the screen during booting procedure. I guess that's because I incautiously removed the necessary ethernet card driver when I was doing the make menuconfig part. How can I re-install those drivers for the eth0? (I am not sure which one is the precise driver, but I'm sure it is contained in the kernel source). Thx a lot! Regards, Deephay Z -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] Regards, Deephay Z -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: eth0 problem
Deephay Z wrote: Greetings all, since I need to install the wireless device driver for the Debian system, so I compiled and installed the 2.6.13.2 version kernel, but the eth0 (wired-ethernet card) now cannot be found using the newer kernel. Some kinda :eth0: no such device is displayed on the screen during booting procedure. I guess that's because I incautiously removed the necessary ethernet card driver when I was doing the make menuconfig part. How can I re-install those drivers for the eth0? (I am not sure which one is the precise driver, but I'm sure it is contained in the kernel source). Thx a lot! Regards, Deephay Z To identify the NIC device, try lspci (if it's a PCI device) or else grep for eth0 in your boot message logs. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Strange eth0 problem. Help!!!!
Okay I only used the exclamation marks to get your attention. My problem is that I had to change my IP address from dhcp to static to setup my dlink broadband router then I changed eth0 back to dhcp. Now upon rebooting my laptop if I don't have my cable plugged in it takes along time for it to get past the configuring network option. Then the Configuring Network Option tries to ping 192.168.0.1 and has to timeout before the machine comes on up. Where would the 192.168.0.1 be coming from??? My /etc/network/interfaces looks like this for eth0 auto eth0 iface eth0 inet dhcp Thanks __ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Strange eth0 problem. Help!!!!
On Sun, 13 Jul 2003 14:03:16 -0700 (PDT) Bruce Banner [EMAIL PROTECTED] wrote: Okay I only used the exclamation marks to get your attention. My problem is that I had to change my IP address from dhcp to static to setup my dlink broadband router then I changed eth0 back to dhcp. Now upon rebooting my laptop if I don't have my cable plugged in it takes along time for it to get past the configuring network option. Then the Configuring Network Option tries to ping 192.168.0.1 and has to timeout before the machine comes on up. Where would the 192.168.0.1 be coming from??? My /etc/network/interfaces looks like this for eth0 auto eth0 iface eth0 inet dhcp You can't very well get an IP address via DHCP if you're not plugged in. 192.168.0.1 is probably the address of the DHCP server (your broadband router). If you don't want to wait for dhcp to time out you can press ctrlc when you see the Configuring Network message on the console. Since I'm usually plugged in, that's what I do when I'm not. Kevin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Strange eth0 problem. Help!!!! Solved
I fingered it out. In /var/lib/dhcp/dhcp.leases the dlink put in a very long lease(about 3 months) I deleted the entry now my machine knows nothing about 192.168.0.1. Kevin if you don't want to wait you can shorten the amount of time it looks for a dhcp server in /etc/dhclient.conf timeout I set mine to 5 secs and never have aproblem getting dhcp info in that time frame. unless you are using pump. Thanks --- Kevin McKinley [EMAIL PROTECTED] wrote: On Sun, 13 Jul 2003 14:03:16 -0700 (PDT) Bruce Banner [EMAIL PROTECTED] wrote: Okay I only used the exclamation marks to get your attention. My problem is that I had to change my IP address from dhcp to static to setup my dlink broadband router then I changed eth0 back to dhcp. Now upon rebooting my laptop if I don't have my cable plugged in it takes along time for it to get past the configuring network option. Then the Configuring Network Option tries to ping 192.168.0.1 and has to timeout before the machine comes on up. Where would the 192.168.0.1 be coming from??? My /etc/network/interfaces looks like this for eth0 auto eth0 iface eth0 inet dhcp You can't very well get an IP address via DHCP if you're not plugged in. 192.168.0.1 is probably the address of the DHCP server (your broadband router). If you don't want to wait for dhcp to time out you can press ctrlc when you see the Configuring Network message on the console. Since I'm usually plugged in, that's what I do when I'm not. Kevin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] __ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com -- 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
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]
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
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]
eth0 problem after installing netscape
I just did a dist-upgrade and installed netscape 4.76. Now it seems my eth0 connection (cable modem) won't stay active. I am unable to connect to anything and then when I switch to init 1 and back [ctrl-d] then I have a connection that works. Has anyone else had this problem? I'm wondering if it's something from the upgrade or a net work problem. It seems to work for a short time, then dies. this time the connection died in about 4 minutes. here's the result [EMAIL PROTECTED]:~$ ping www.lvcm.com ping: unknown host www.lvcm.com Any easy way to fix this? thanks -- For de little stealin 'dey gets you in jail soon or late. For de big stealin 'dey makes you Emperor and puts you in de Hall o' Fame when you croaks. Eugene O'Neill, 'The Emperor Jones' 1921
Re: eth0 problem after installing netscape
Well, I'm realizing what has happened here. I installed potato on my wife's machine and in the libranet cd it asked for network connection data. I entered my IP address (static IP), dns name servers, gateway, domain, etc.. then when I configured the kernel, I configured it using dhcp. Now, I find that as long as the wife's machine is in windows, everything works fine (because it's using the dhcp connection) but in linux both machines are screwy. I tried using linuxconf (included with the distro) to edit my network configuration, but it doesn't seem to write to the proper file, in short doesn't work. Could someone please tell me how and which file to edit, so I can get her machine using dhcp in linux. Hopefully, this will solve my problem. thanks in advance Dale Morris [EMAIL PROTECTED] wrote: I just did a dist-upgrade and installed netscape 4.76. Now it seems my eth0 connection (cable modem) won't stay active. I am unable to connect to anything and then when I switch to init 1 and back [ctrl-d] then I have a connection that works. Has anyone else had this problem? I'm wondering if it's something from the upgrade or a net work problem. It seems to work for a short time, then dies. this time the connection died in about 4 minutes. here's the result [EMAIL PROTECTED]:~$ ping www.lvcm.com ping: unknown host www.lvcm.com Any easy way to fix this? thanks -- For de little stealin 'dey gets you in jail soon or late. For de big stealin 'dey makes you Emperor and puts you in de Hall o' Fame when you croaks. Eugene O'Neill, 'The Emperor Jones' 1921 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- For de little stealin 'dey gets you in jail soon or late. For de big stealin 'dey makes you Emperor and puts you in de Hall o' Fame when you croaks. Eugene O'Neill, 'The Emperor Jones' 1921
Re: eth0 problem
The card is a Netgear with a Tulip Digital 21040 chip which is what we have in the Redhat and SuSe servers and they do not behave this way. Do they all have the same kernel (read: driver) version ? Maybe Suse/RH use a newer driver ? Because I can remember tulip drivers having problems with this now and then.
Re: eth0 problem
On Sat, Nov 25, 2000 at 01:58:12PM +1100, Daniel Knights wrote: Do the servers all have the same type of network-cards? I have a 3Com 3c900 Combo and it seems this card doesn't react anymore after some time. An ifdown+ifup brings it back again. Phil Hi Phil The card is a Netgear with a Tulip Digital 21040 chip which is what we have in the Redhat and SuSe servers and they do not behave this way. Like Leen already wrote: I assume you have different tulip-versions then. I once had an Asix-card (worked with old_tulip) and it was not reachable unless this card initiated a connection (like ping). Donald Becker wrote me that a newer driver will fix this problem but it never did. Phil
eth0 problem
Hi, I have added 3 Debian boxes to my network and they all seem OK, till I noticed that when changing some of the cat5 cables around, that the 3 debian boxes eth0 does not start passing data again when cat 5 is replaced, the cables were only removed for a minute or less.I did not notice straight off as when I replace the cable all looks fine as the hub lights up, but a few minutes later bigbrother is telling me that all three debian boxes are down. I did an ifconfig eth0 up and still no good, but an ifcongif down and then up brings them back online again. There were no errors recorded in log files. This only happens to the debian boxes as the redhat and the SuSe linux servers are not bothered by having the network cables missing for a minute or two. Any advice on what might be causing this would be appreciated. Thanks Daniel
Re: eth0 problem
On Sat, Nov 25, 2000 at 02:20:59AM +1100, Daniel Knights wrote: I have added 3 Debian boxes to my network and they all seem OK, till I noticed that when changing some of the cat5 cables around, that the 3 debian boxes eth0 does not start passing data again when cat 5 is replaced, the cables were only removed for a minute or less.I did not notice straight off as when I replace the cable all looks fine as the hub lights up, but a few minutes later bigbrother is telling me that all three debian boxes are down. I did an ifconfig eth0 up and still no good, but an ifcongif down and then up brings them back online again. There were no errors recorded in log files. This only happens to the debian boxes as the redhat and the SuSe linux servers are not bothered by having the network cables missing for a minute or two. Any advice on what might be causing this would be appreciated. Do the servers all have the same type of network-cards? I have a 3Com 3c900 Combo and it seems this card doesn't react anymore after some time. An ifdown+ifup brings it back again. Phil
Re: eth0 problem
Do the servers all have the same type of network-cards? I have a 3Com 3c900 Combo and it seems this card doesn't react anymore after some time. An ifdown+ifup brings it back again. Phil Hi Phil The card is a Netgear with a Tulip Digital 21040 chip which is what we have in the Redhat and SuSe servers and they do not behave this way. cheers Garry Regards, Daniel ___ Daniel Knights Highway Internet Services ABN: 14 088 130 269 Part of the LiSP Group http://www.lisp.com.au Servicing the Dubbo, Mudgee, Coonabarabran, Gilgandra, Warren, Wellington and surrounding areas. Enquiries 02 6372 3645 129 Market St, Mudgee 2850
Re: 2.2.x kernel and PCI eth0 problem - the answer
Thanks Jor-el, I upgraded dhcpcd and netbase and it works like a charm. The fact that 2.2 kernels require an upgrade is documented in the release notes section on www.debian.org. (Yes I am embarrassed - I should have caught that myself) Thanks also to Paul Wade, who also dropped me a helpful note, with other diagnostic techniques. Namaste Rupert B. At 08:02 AM 03/08/99 -0500, Jor-el wrote: -BEGIN PGP SIGNED MESSAGE- Rupert, I assume that you are running Slink. Have to installed the upgrade versions of the packages that are required for your to be running the 2.2.x kernels? I belive the net-tools package is one of the packages that need to be ugraded, so I am not at all surprised to hear that networking is failing for you. There is a URL available somewhere on the Debian website which tells you about the packages that need to be upgraded. Unfortunately, I do not have a URL handy - so you'll have to search. Regards, Jor-el Everywhere I go I'm asked if I think the university stifles writers. My opinion is that they don't stifle enough of them. There's many a bestseller that could have been prevented by a good teacher. -- Flannery O'Connor On Mon, 2 Aug 1999, Rupert Brooks wrote: Hi, I have configed and compiled both the 2.2.10 and 2.2.5 kernels, and my ne2000 clone PCI ethernet card does not work with either. With my 2.0.34 kernel, the card worked fine. The module ne2k-pci loaded without a hitch and dhcpcd configured the ip information flawlessly. ( I use an ADSL connection which requires DHCP to be used to set up the IP address.) I have tried both kernels with NE2000 support compiled in. In this case, the card appears to be recognized on startup, but DHCPCD does not create new files when it runs. DHCPCD does not report any errors either. ifconfig without arguments shows the loopback device. Ifconfig listing all devices lists the eth0 device and it looks ok, but none of the IP information is configured. Note that I have also used dhcpcd eth0 to try and force dhcp to use the ethernet card. If I configure the kernel to use loadable module support for the ethernet card, then the module ne2k-pci won't load. When using insmod to try to load it, it will complain aboutn several symbols not being resolved. From their names they look like the ethernet card hooks in the kernel. After that lengthy description - I have a couple questions Does anyone out there have a ne2000 PCI ethernet card working under a 2.2.x kernel? If so, did you have to do anything wierd to get it to work? I am not sure what is not working, because there have been so few error messages. Can anyone recommend some diagnostic tests? TIA Rupert Brooks -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -BEGIN PGP SIGNATURE- Version: 2.6.3a Charset: noconv iQCVAwUBN6boavrE9j2ZpWNBAQHr7wQAhRVXTfZcyb+oRJegJ/K7BOOT+mS06H8+ Ptmz35+BkgSJddrYScmO/8bxzZHNoinhVDd2KwPfYEnJQFvIf2thP40rqXj4wJA8 w5/AIQJvDaOtxg98g09qquHRH57rbBcyVE0bJCLC+l9qJiYzPjSxmD3RHvOKtZlL P7WQVXUVi0M= =WzBR -END PGP SIGNATURE-
2.2.x kernel and PCI eth0 problem
Hi, I have configed and compiled both the 2.2.10 and 2.2.5 kernels, and my ne2000 clone PCI ethernet card does not work with either. With my 2.0.34 kernel, the card worked fine. The module ne2k-pci loaded without a hitch and dhcpcd configured the ip information flawlessly. ( I use an ADSL connection which requires DHCP to be used to set up the IP address.) I have tried both kernels with NE2000 support compiled in. In this case, the card appears to be recognized on startup, but DHCPCD does not create new files when it runs. DHCPCD does not report any errors either. ifconfig without arguments shows the loopback device. Ifconfig listing all devices lists the eth0 device and it looks ok, but none of the IP information is configured. Note that I have also used dhcpcd eth0 to try and force dhcp to use the ethernet card. If I configure the kernel to use loadable module support for the ethernet card, then the module ne2k-pci won't load. When using insmod to try to load it, it will complain aboutn several symbols not being resolved. From their names they look like the ethernet card hooks in the kernel. After that lengthy description - I have a couple questions Does anyone out there have a ne2000 PCI ethernet card working under a 2.2.x kernel? If so, did you have to do anything wierd to get it to work? I am not sure what is not working, because there have been so few error messages. Can anyone recommend some diagnostic tests? TIA Rupert Brooks
Re: 2.2.x kernel and PCI eth0 problem
On Mon, Aug 02, 1999 at 09:25:14PM -0400, Rupert Brooks wrote: Hi, I have configed and compiled both the 2.2.10 and 2.2.5 kernels, and my ne2000 clone PCI ethernet card does not work with either. With my 2.0.34 kernel, the card worked fine. The module ne2k-pci loaded without a hitch and dhcpcd configured the ip information flawlessly. ( I use an ADSL connection which requires DHCP to be used to set up the IP address.) I have a cable modem over here and also use DHCPCD to get my IP address, etc from the provider. The old dhcpcd was doing Bad Things (TM) in regards to the new kernel networking code (i.e. setting the IP address to 0.0.0.0 IIRC). A newer dhcpcd-sv package is part of potato and it has worked fine for me. If you don't run potato, you can fairly easily grab the source and recompile it against glibc 2.0. -- Stephen Pitts [EMAIL PROTECTED] webmaster - http://www.mschess.org
Re: 2.2.x kernel and PCI eth0 problem
-BEGIN PGP SIGNED MESSAGE- Rupert, I assume that you are running Slink. Have to installed the upgrade versions of the packages that are required for your to be running the 2.2.x kernels? I belive the net-tools package is one of the packages that need to be ugraded, so I am not at all surprised to hear that networking is failing for you. There is a URL available somewhere on the Debian website which tells you about the packages that need to be upgraded. Unfortunately, I do not have a URL handy - so you'll have to search. Regards, Jor-el Everywhere I go I'm asked if I think the university stifles writers. My opinion is that they don't stifle enough of them. There's many a bestseller that could have been prevented by a good teacher. -- Flannery O'Connor On Mon, 2 Aug 1999, Rupert Brooks wrote: Hi, I have configed and compiled both the 2.2.10 and 2.2.5 kernels, and my ne2000 clone PCI ethernet card does not work with either. With my 2.0.34 kernel, the card worked fine. The module ne2k-pci loaded without a hitch and dhcpcd configured the ip information flawlessly. ( I use an ADSL connection which requires DHCP to be used to set up the IP address.) I have tried both kernels with NE2000 support compiled in. In this case, the card appears to be recognized on startup, but DHCPCD does not create new files when it runs. DHCPCD does not report any errors either. ifconfig without arguments shows the loopback device. Ifconfig listing all devices lists the eth0 device and it looks ok, but none of the IP information is configured. Note that I have also used dhcpcd eth0 to try and force dhcp to use the ethernet card. If I configure the kernel to use loadable module support for the ethernet card, then the module ne2k-pci won't load. When using insmod to try to load it, it will complain aboutn several symbols not being resolved. From their names they look like the ethernet card hooks in the kernel. After that lengthy description - I have a couple questions Does anyone out there have a ne2000 PCI ethernet card working under a 2.2.x kernel? If so, did you have to do anything wierd to get it to work? I am not sure what is not working, because there have been so few error messages. Can anyone recommend some diagnostic tests? TIA Rupert Brooks -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -BEGIN PGP SIGNATURE- Version: 2.6.3a Charset: noconv iQCVAwUBN6boavrE9j2ZpWNBAQHr7wQAhRVXTfZcyb+oRJegJ/K7BOOT+mS06H8+ Ptmz35+BkgSJddrYScmO/8bxzZHNoinhVDd2KwPfYEnJQFvIf2thP40rqXj4wJA8 w5/AIQJvDaOtxg98g09qquHRH57rbBcyVE0bJCLC+l9qJiYzPjSxmD3RHvOKtZlL P7WQVXUVi0M= =WzBR -END PGP SIGNATURE-
Re: 2.2.x kernel and PCI eth0 problem
I am using such a system. I compiled the kernel with module autoloading, but I also have /etc/modules like this #auto ne2k-pci It works fine. My network card is automatically detected and configured. Maybe you have to specify some parameters in /etc/modutils/aiases and then recreate /etc/conf.modules To recreate it you have to use update-modules. See man page for it. --JS On Tue, 3 Aug 1999, Jonas Steverud wrote: Rupert Brooks [EMAIL PROTECTED] writes: [...] Does anyone out there have a ne2000 PCI ethernet card working under a 2.2.x kernel? Just a quick check: Do you load the 8390-module (8390.o)? (As a module or compiled into the kernel.) -- ( Jonas Steverud @ www.dtek.chalmers.se/~d4jonas/ !Wei Wu Wei) ( U2MoL, Roleplaying, LaTeX, Emacs/Gnus, SCWM, etc. ! To Do Without Do ) -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
