Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Distribution: Win98+WinLinux+Red Hat 7.1 on one system Win98+Peanut 8.4 on the other.
Posts: 27
Rep:
...eth0 [Failed]
I'm trying to get my Linux box connected to my cable connection. Could somebody please go to http://www.linux.com/learn/newsitem....id=1&aid=12537 and help me figure out why it doesn't work for me. When I boot up I get 'Bringing up interface eth0...' for a really long time. Then of course it fails. I have Red Hat 7.1 and Cox @Home. I know I don't have a hardware problem because when I boot Windows everything works fine.
Make sure the correct kernel module for your ethernet card is loading at boot and that it loads before attempting to contact a DHCP server. To check what modules are loaded do "lsmod" in a console as root. To load a module do "modprobe <module name>".
The link you provided assumes that your network card is already configured - it only addresses how to get a functional network card working with the cable modem and DHCP. I would recommend looking at the Ethernet HOWTO, as well as any documentation you have on your network card. Since you're using RH 7.1, you should be able to use LinuxConf to setup the card (command 'linuxconf' at the prompt). If the module required to run card is not listed on the LinuxConf list, you'll be in for some extra work, but in most cases it should be pretty easy. If you continue to have problems, post back on this thead and include the make and model of your network card.
Distribution: Win98+WinLinux+Red Hat 7.1 on one system Win98+Peanut 8.4 on the other.
Posts: 27
Original Poster
Rep:
I use a D-Link DFE-550TX, which (I hope) uses the Sundance module. The 'lsmod' command shows that Sundance is loaded. If I run 'ifup eth0' it does the same thing that it does during bootup (but I don't know if that's the exact command it runs during bootup). This should mean that it can't contact the DHCP server even after the module loads.
Looks like the sundance module is the right one (http://www.dlink.com.au/tech/drivers...ux_drivers.txt) for the DFE-550Tx (but the DFE-550Fx uses a different one). As it turns out, I ran into a lot of the same touble installing a DFE-530Tx under RH 7.0, so I'll tell you what I did to make it work:
*In the Networking | Client Tasks | Basic Host Infomation | Adaptor 1 section of LinuxConf, I selected the module name that D-Link listed for the DFE-530Tx (via-rhine).
*I compiled the module object that came on the driver disk (there was a directory called 'linux' on it that contained the linux driver). This created a file called rtl8139.o. I put this file in the /root directory (for lack of any other good place to put it that I knew of at the time).
*I edited the file /etc/rc.d/init.d/network. A little ways down, there was a line that read:
case "$1"
start)
This is the beginning of the part that starts up the network interface. At the beginning of this section (on the line directly after the the lines listed above) I put in the command
insmod /root/rtl8139.o
This is almost certainly not the most effifient way to handle this (installing the module on the system), but it does have the virtue of working.
Anyway, with this stuff done, it works like a champ. I hope this helps!
Also, if you haven't bumped into it yet, D-Link's support page for the DFE-550Tx (http://support.dlink.com/products/vi...ctid=DFE-550TX) has a link to download linux drivers for the card.
Do a "lspci" and see what sort of chip is on the card. Linux drivers go by the chip used for the card not the company that made it. My ethernet card was made by Acer but uses a realtek chip (8139) so the module for it is 8139too (rtl8139.o is the old module).
To answer your question on weather or not to use the Sundance that came with the driver download, I would say yes. In my case, (with the DFE-530Tx) the rtl8139.o that came with my RH distribution did not work with the card, but the one that I compiled from the driver disk (also rtl8139.o) did work.
Distribution: Win98+WinLinux+Red Hat 7.1 on one system Win98+Peanut 8.4 on the other.
Posts: 27
Original Poster
Rep:
Here's what I get when I cat /proc/pci:
Ethernet controller: PCI device 1186:1002 (D-Link System Inc) (rev 18).
IRQ 5.
Master Capable. Latency=64. Min Gnt=10.Max Lat=10.
I/O at 0xd800 [0xd87f].
Non-prefetchable 32 bit memory at 0xe9000000 [0xe90001ff].
Bus 0, device 10, function 0:
Distribution: Win98+WinLinux+Red Hat 7.1 on one system Win98+Peanut 8.4 on the other.
Posts: 27
Original Poster
Rep:
Thanks Aussie, I'll try the driver as soon as I get time. I'm having a hard time finding time for this stuff because my dad is trying to finish writing a book in two weeks. The other driver that I got from http://www.dlink.com.au/tech/drivers...ux_drivers.txt had a really lousy readme. The readme said there was a makefile and there wasn't. The one you sent had the makefile.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.