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'm having trouble with my D-Link DFE-530TX+ NIC under Fedora Core 3. It seems like the card was recognized during the install phase, but I can't get an IP address for it at boot up using DHCP. I try to manually activate the the card, but it fails everytime. It looks like the correct driver (8139too) is instaled and is being used by the system. The device comes up using ifconfig, it just doesn't have an IP address. Could this be caused by using the wrong driver?
Has anyone had any (good) luck or experience with this card?
Distribution: Slackware, Windows, FreeBSD, OpenBSD, Mac OS X
Posts: 5,296
Rep:
Hi tjf1, welcome to lq. Could you post the output from lspci -v please. That should give us the chipset so we may determine what module you'll need. You could also post the output from lsmod as well.
good luck.
Distribution: Slackware, Windows, FreeBSD, OpenBSD, Mac OS X
Posts: 5,296
Rep:
I'll be glad to try and help, but, I'll need you to post the information that I ask for. It is not to dispute that you do or do not have the proper driver loaded. Some modules need other modules loaded to work properly. My request is so that I may have all of the available information to make a suggestion as to resolving your problem. I hope this isn't taken the wrong way. I'm only trying to help.
good luck.
I appreciate your help and patience. I apologize ahead of time for the lack of text formatting.
Here is the information that you requested:
/sbin/lspci -v ...
00:00.0 Host bridge: VIA Technologies, Inc. VT8374 P4X400 Host Controller/AGP Bridge (rev 82)
Subsystem: VIA Technologies, Inc. VT8374 P4X400 Host Controller/AGP Bridge
Flags: bus master, 66Mhz, medium devsel, latency 8
Memory at d0000000 (32-bit, prefetchable) [size=128M]
Capabilities: <available only to root>
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge (prog-if 00 [Normal decode])
Flags: bus master, 66Mhz, medium devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 0000a000-0000afff
Memory behind bridge: e8000000-e9ffffff
Prefetchable memory behind bridge: d8000000-e7ffffff
Capabilities: <available only to root>
00:0a.0 Multimedia audio controller: Creative Labs SB Audigy LS
Subsystem: Creative Labs: Unknown device 1006
Flags: bus master, medium devsel, latency 32, IRQ 11
I/O ports at b000 [size=32]
Capabilities: <available only to root>
00:0c.0 Ethernet controller: D-Link System Inc RTL8139 Ethernet (rev 10)
Subsystem: D-Link System Inc DFE-530TX+ 10/100 Ethernet Adapter
Flags: bus master, medium devsel, latency 32, IRQ 10
I/O ports at b400 [size=256]
Memory at ea000000 (32-bit, non-prefetchable) [size=256]
Capabilities: <available only to root>
00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80)
Subsystem: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller
Flags: bus master, medium devsel, latency 32, IRQ 11
I/O ports at b800 [size=8]
I/O ports at bc00 [size=4]
I/O ports at c000 [size=8]
I/O ports at c400 [size=4]
I/O ports at c800 [size=16]
I/O ports at cc00 [size=256]
Capabilities: <available only to root>
00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
Subsystem: VIA Technologies, Inc. VT82C586/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE
Flags: bus master, medium devsel, latency 32, IRQ 11
I/O ports at d000 [size=16]
Capabilities: <available only to root>
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
Flags: bus master, medium devsel, latency 32, IRQ 11
I/O ports at d400 [size=32]
Capabilities: <available only to root>
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
Flags: bus master, medium devsel, latency 32, IRQ 11
I/O ports at d800 [size=32]
Capabilities: <available only to root>
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
Flags: bus master, medium devsel, latency 32, IRQ 11
I/O ports at dc00 [size=32]
Capabilities: <available only to root>
00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
Flags: bus master, medium devsel, latency 32, IRQ 11
I/O ports at e000 [size=32]
Capabilities: <available only to root>
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) (prog-if 20 [EHCI])
Subsystem: VIA Technologies, Inc. USB 2.0
Flags: bus master, medium devsel, latency 32, IRQ 10
Memory at ea001000 (32-bit, non-prefetchable) [size=256]
Capabilities: <available only to root>
00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800 South]
Subsystem: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800 South]
Flags: bus master, stepping, medium devsel, latency 0
Capabilities: <available only to root>
01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AS [Radeon 9600 AS] (prog-if 00 [VGA])
Subsystem: ASUSTeK Computer Inc.: Unknown device 0038
Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 11
Memory at d8000000 (32-bit, prefetchable) [size=128M]
I/O ports at a000 [size=256]
Memory at e9000000 (32-bit, non-prefetchable) [size=64K]
Capabilities: <available only to root>
01:00.1 Display controller: ATI Technologies Inc RV350 ?? [Radeon 9550] (Secondary)
Subsystem: ASUSTeK Computer Inc.: Unknown device 0039
Flags: 66Mhz, medium devsel
Memory at e0000000 (32-bit, prefetchable) [disabled] [size=128M]
Memory at e9010000 (32-bit, non-prefetchable) [disabled] [size=64K]
Capabilities: <available only to root>
Distribution: Slackware, Windows, FreeBSD, OpenBSD, Mac OS X
Posts: 5,296
Rep:
It appears as if the modules are loaded properly, 8139too, as well as mii. Have you tried a static ip address, and what is your network topology?
good luck.
I connect directly to the internet through cable modem. I have no internal network (i.e., hub, router, etc.) of any kind connected. For what it's worth, here's the output from /sbin/ifconfig
eth0 Link encap:Ethernet HWaddr 00:11:95:1D:C9:A9
inet6 addr: fe80::211:95ff:fe1d:c9a9/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:14908 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:10 Base address:0xb400
I can't ping anything other than 127.0.0.1. I'm thinking that it's just some sort of default Linux firewall or security setting that is preventing me from communicating with my ISP at boot up and receiving an IP adrress. I don't think that it's a hardware or connectivity issue. Everything seems to be working flawlessly under XP. Do you know of any sort of security mode that may be enabled by default in Linux that I should try to switch off? Is IPv6 a potential problem?
Distribution: Slackware, Windows, FreeBSD, OpenBSD, Mac OS X
Posts: 5,296
Rep:
You could try an iptables -F, that should flush any current rules. The ipv6 could be hard to setup and get going, I've never set it up. Your mileage may vary. If you would like to read up on it you can find some info here.
I just noticed that during boot up, FC3 gives the message "Disabling IRQ #10". Does anyone else ever get this? I never really thought anything of it until I noticed that my NIC is tied to IRQ #10. Is it possible that it could be an IRQ problem that is preventing my NIC from communicating successfully with my ISP through DHCP and obtaining an IP address?
The IRQ must have been the problem the whole time. I just enabled my on-board network interface through the BIOS while I was poking around in there. When I re-booted, FC3 gave the newly found onboard interface (i.e., eth1) the IRQ 10 and it gave my original D-Link NIC (i.e., eth0) IRQ 11. Now I can activate eth0 and, sure enough, eth1 fails to activate just like eth0 was failing before. I wonder why FC3 just disables an IRQ altogether like that?
Distribution: Slackware, Windows, FreeBSD, OpenBSD, Mac OS X
Posts: 5,296
Rep:
Your welcome, I'm glad you have at least a small amount of success. You might try putting the card in a different pci slot, some nics have trouble from certain pci slots. I read something about that but, it's been so long ago I can't recall where or when. It has to do with the bus, that much I remember. In any event post back if you get things going or not.
good luck.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.