Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am going to apologize in advance for a long first posting, but hope it will save time in the long run.
I'm another one of those newbies that can't get their eth0 up.
The basic gripe is, this hardware configuration will work (sans sound card, that is) in RedHat 7.1 install from .iso cd's.
When I did a fresh install from .iso cd's to RedHat 7.2, networking
does not come up.
I do another install of 7.1 - networking works again.
I enable RedHat's auto updater thingie from RedHat Network and
it fixes me up with a later kernel - and bingo - no networking again.
I've read the scoop Donald Becker, who is the principle developer/maintainer of the "tulip" driver for these DECchip ethernet cards. He maintains that someone it the Mandrake camp broke the driver and (I don't know the connection) that somehow has affected RedHat's latest offerings also.
His explanation of how to fix it was too daunting for me, as it involved getting another compiler (kgcc) to recompile the kernel, making sure I had the right kernel headers and some other stuff that I am too unsure of myself to attempt. I've seen too many posts here and elsewhere on the net to know that the tulip driver (at least as it comes from RedHat in version 7.x and maybe
Mandrake) is screwed up. The details of how and why it's screwed up, I may have gotten wrong - after all I'm just a newbie!
Below I've included information of my present install of 7.1 that got updated from RedHats up2date thing and is now in a broken state as far as networking is concerned. Hopefully this will provide those with the know-how to decide what is really broke.
Hardware configuration:
AMD Athlon 1.2 Ghz on a Abit KT7A motherboard
Ethernet card (NIC) is an SMC 8432BT EtherPower PCI Ethernet Adapter. (uses DEC 21041 chip)
Sound Card is an Ensoniq ES1370. (Which by the way does not work under RH 7.1, but does in RH 7.2!)
Video Card is nVidia GE Force II MX w/32mb AGP
Plug & Play is turned off in my BIOS.
Output from /var/messages:
...
...
Mar 2 17:08:47 localhost network: Setting network parameters: succeeded
...
Mar 2 17:08:48 localhost network: Bringing up interface lo: succeeded
...
Mar 2 17:08:48 localhost ifup: Determining IP information for eth0...
...
Mar 2 17:08:48 localhost pumpd[406]: starting at (uptime 0 days, 0:00:40) Sat Mar 2 17:08:48 2002
...
Mar 2 17:09:48 localhost ifup: Operation failed.
...
Mar 2 17:10:48 localhost dhcpcd[434]: timed out waiting for a valid DHCP server response
...
Mar 2 17:10:48 localhost ifup: failed.
...
Mar 2 17:10:48 localhost network: Bringing up interface eth0: failed
...
Mar 2 17:11:03 localhost kernel: ip_conntrack (2047 buckets, 16376 max)
Mar 2 17:11:03 localhost kernel: Linux Tulip driver version 0.9.15-pre6 (July 2, 2001)
Mar 2 17:11:03 localhost kernel: PCI: Found IRQ 11 for device 00:0f.0
Mar 2 17:11:03 localhost kernel: tulip0: 21041 Media table, default media 0001 (10base2).
Mar 2 17:11:03 localhost kernel: tulip0: 21041 media #0, 10baseT.
Mar 2 17:11:03 localhost kernel: tulip0: 21041 media #4, 10baseT-FDX.
Mar 2 17:11:03 localhost kernel: tulip0: 21041 media #1, 10base2.
Mar 2 17:11:03 localhost kernel: eth0: Digital DC21041 Tulip rev 17 at 0xd08a1000, 21041 mode, 00:00:C0:41:F7:E4, IRQ 11.
# cat /proc/version
Linux version 2.4.9-31 (bhcompile@daffy.perf.redhat.com) (gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-98)) #1 Tue Feb 26 07:11:02 EST 2002
# cat /proc/iomem
00000000-0009fbff : System RAM
0009fc00-0009ffff : reserved
000a0000-000bffff : Video RAM area
000c0000-000c7fff : Video ROM
000f0000-000fffff : System ROM
00100000-0ffeffff : System RAM
00100000-002af6d9 : Kernel code
002af6da-002c648b : Kernel data
0fff0000-0fff2fff : ACPI Non-volatile Storage
0fff3000-0fffffff : ACPI Tables
d0000000-d7ffffff : PCI Bus #01
d0000000-d7ffffff : nVidia Corporation NV11
d8000000-dbffffff : VIA Technologies, Inc. VT8363/8365 [KT133/KM133]
dc000000-ddffffff : PCI Bus #01
dc000000-dcffffff : nVidia Corporation NV11
df000000-df00007f : Digital Equipment Corporation DECchip 21041 [Tulip Pass 3]
df000000-df00007f : tulip
ffff0000-ffffffff : reserved
# cat /proc/ioports
0000-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0070-007f : rtc
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : ide1
01f0-01f7 : ide0
02f8-02ff : serial(auto)
0376-0376 : ide1
03c0-03df : vga+
03f6-03f6 : ide0
03f8-03ff : serial(auto)
0cf8-0cff : PCI conf1
5000-500f : VIA Technologies, Inc. VT82C686 [Apollo Super ACPI]
6000-607f : VIA Technologies, Inc. VT82C686 [Apollo Super ACPI]
d000-d00f : VIA Technologies, Inc. Bus Master IDE
d000-d007 : ide0
d008-d00f : ide1
d400-d41f : VIA Technologies, Inc. UHCI USB
d400-d41f : usb-uhci
d800-d81f : VIA Technologies, Inc. UHCI USB (#2)
d800-d81f : usb-uhci
dc00-dc3f : Ensoniq ES1370 [AudioPCI]
dc00-dc3f : es1370
e000-e07f : Digital Equipment Corporation DECchip 21041 [Tulip Pass 3]
e000-e07f : tulip
# lspci
00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 03)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP]
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40)
00:07.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06)
00:07.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16)
00:07.3 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16)
00:07.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40)
00:09.0 Multimedia audio controller: Ensoniq ES1370 [AudioPCI]
00:0f.0 Ethernet controller: Digital Equipment Corporation DECchip 21041 [Tulip Pass 3] (rev 11)
01:00.0 VGA compatible controller: nVidia Corporation NV11 (rev a1)
# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:246 errors:0 dropped:0 overruns:0 frame:0
TX packets:246 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:00:C0:41:F7:E4
BROADCAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:18 dropped:0 overruns:0 carrier:27
collisions:0 txqueuelen:100
Interrupt:11 Base address:0x1000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:246 errors:0 dropped:0 overruns:0 frame:0
TX packets:246 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
# insmod tulip
Using /lib/modules/2.4.9-31/kernel/drivers/net/tulip/tulip.o
insmod: a module named tulip already exists
Well, I don't have an answer, but I do have the exact same problem. 7.1 and mandrake 8.1 both found my nic and the tulip driver worked fine, but rh7.2 doesnt initialize the eth0. I've been looking for help on this one as well, and the TLUG gave me this advice:
> Try using '/usr/sbin/netconfig'. Its simpler and meant for getting your
> network up quickly.
>
> Before that, your problem seems to be with the kernel not recognizing
> your network card. The file /etc/modules.conf should have an entry like
> 'alias eth0 eepro100', based on your NIC (Intel Ethernet Pro 100 in this
> case).
>
> After adding that, run '/sbin/depmod -a' and then 'modprobe eepro100'
> (replacing eepro100 with the module for your card). Then use netconfig
> to setup networking.
I haven't been able to get it to work yet... if anyone has any luck, please tell us how you did it so we can ride that penguin bus to glory.
Yes, I am set up to acquire an IP address via dhcp - by design.
I have a D-LINK DI-701 Residential Gateway that acts as a
DHCP server. It also behaves as a NAT firewall. I am connected
to the internet via this Gateway to a Cable Modem. But I should
get an IP from the D-LINK in the range of 192.168.0.1 through
192.168.0.254. Which all works under RH 7.1 and also Windows.
So, you see, setting a static IP is not an option in my configuration.
What I need is the answer to why RH 7.2 behaves differently
from RH 7.1. I'm not looking for a work-around. I want to find
a true fix for RH 7.2. I have read that 7.2 has a broken tulip
driver. So I'm wondering if someone out there has fixed the
driver and compiled it into a working kernal which equals or is
later than the one that ships with RH 7.2
If you observe the printout I listed above of /proc/ioports,
you'll see that the card was recognized and it lists the
io range as follows:
e000-e07f : Digital Equipment Corporation DECchip 21041 [Tulip Pass 3]
e000-e07f : tulip
Adding the line as suggested in modules.conf would be
redundant, would it not? I.E. since the system has already
identified that range and shows it assigned to the ethernet
card with the appropriate tulip driver??
Well, I tried the suggestion of adding "option io=0xe000" and
I now get a different failure - insmod error.
That fix was from the 7.2 guide book and I am actually running
7.1 that has been "up2date"d at the moment. It causes the
exact same symptom as a 7.2 complete install, as far as
networking with this NIC is concerned. Referring to the 7.1
guide book and looking at the relevant entry in the appendix,
the suggestion to add "option io=0xe000" does not exist - it's
blank.
Still wanting somebody to tell me what's broke and how to get
a real fix.
Well troups, I finally conquored the problem.
I re-installed RedHat 7.2 and edited /etc/modules.conf
to change the line from:
alias eth0 tulip
to
alias eth0 tulip_old
Rebooted and networking is now operating.
It sure would have been great if somebody in RedHat had documented the
fact that some DecChips need an "old" driver and that it could be had
just by changing /etc/modules.
Great news! I just stumbled on this site because I installed RH7.2 a month or so ago and didn't get any network connection. Like you, previous versions of Red Hat worked fine and -- in fact -- automatically. I know nothing about networkind and did not need to.
My previous connection was through cable modem, hooked to a Digital DC21041 NIC and it worked in OS/2, Win95, ME, 2kPro and various versions of Red Hat. But not in 7.2. Last night I switched to ADSL from the local telco, again just plugging the ADSL 'modem' into the same Digital DC21041 NIC. Still no go with RH7.2 but still flawless and magic operation with Win2k and OS/2.
I've seen all kinds of weird things with my setup. Output of ifconfig showed that my NIC was recognized and initialized but DHCP was not getting found.
Based on your report, I'm going to give a shot at reinstalling and trying the trick you mentioned. You're right, it's damn ridiculous how such important "trivial" things get ignored by some people/companies.
I tried the tulip_old setting and it worked. For the record, my setup is OLD hardware, two ethernet cards, one an SMC EtherPower PCI SMC 8432BT and the other a 3COM EtherLink XL PCI 3C90x on a new RedHat 9 install.
When both cards were in the system, nothing worked, with only the 3COM it worked.
The originally installed setting (by RedHat install) was:
alias eth0 3c59x
alias eth1 tulip
I changed it per above and the following setting in /etc/modules.conf works:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.