Now this is unique...

[Tyr-7BE]

I know I know I know...there are countless tutorials out there on how to set up your D-Link DFE 530TX. The difference between me and most of those people is that when they follow the tutorials, their machine works.
Hopefully someone will know how to solve this, cause I sure as hell don't.
I am using kernel 2.2.17. My system is Mandrake 7.2, which is supposedly fully compatible with Red Hat. I downloaded the latest drivers of pci-scan.c and via-rhine.c. I tried to compile pci-scan.c and received a HUGE number of warning and error messages (they were almost all warnings and errors in various header files of my /usr/include/linux directory (a good majority of the form "warning: data definition has no type or storageclass." and "warning: no semicolon at end of struct or union." and other things like that, among many many many others in many files, all of them being various include files). This leads me to believe that the compilation of both pci-scan.c and via-rhine.c are not getting past the include preprocessor commands. Does anyone have ANY idea what might be causing this? As I recall, I had this problem several months ago when I attempted to compile the rtl8139 driver as well when I wanted to see if it worked with my DFE 538TX (other network card) as was rumoured (I still don't know to date...I need to be able to compile modules...please help!). I also tried the red-hat method of kgcc, but still no dice...gcc told me that there was no file to compile, even though I added the extra parameters. Do I need more than what Mandrake 7.2 gives me by default in order to compile c files?

Here's what it gives me as far as ethernet goes in dmesg | more...please note that I have 2 NICs...D-Link DFE 538TX and D-Link DFE 530TX (the 530TX is the one I want working, as I KNOW for a fact that it's supported...I think the other might be as well but I'm not sure).

dmesg | more :

eth0: 8139too FastEthernet 0.9.9-2.2 Jeff Garzik <jgarzik@mandrakesoft.com>
eth0: Linux-2.2 bug reports to Jens David <dg1kjd@afthd.tu-darmstadt.de>
eth0: RealTek RTL8139 Fast Ethernet board found at 0xc503a000, IRQ 0
eth0: Chip is 'RTL-8139B' - MAC address '00:50:ba:3f:f4:2f'.
via-rhine.c:v1.08 6/24/2000 Written by Donald Becker http://www.scyld.com/network/via-rhine.html
eth1: VIA VT3043 Rhine at 0x9000, 00:50:ba:c9:53:86, IRQ 0.
eth1: MII PHY found at address 8, status 0x782d advertising 05e1 Link 0000.

and much later on (after all the USB and sound card stuff),

eth0: VIA VT3043 Rhine at 0x9000, 00:50:ba:c9:53:86, IRQ 0.
eth0: MII PHY found at address 8, status 0x782d advertising 05e1 Link 0000.

Is it normal for eth1 and eth0 to say EXACTLY the same thing? That IRQ 0 thing makes me a little suspicious too. I hate not knowing what I'm doing! The fact that the drivers are v.1.08 written in June of 2000 suggests that they're up to date (as the ones in Muzz's post in "How I did it!" were v.1.07). I, with my limited linux experience, cannot tell which is which from this. Can anybody here? Is my DFE 530TX eth0 or eth1? Something tells me it's eth1.
So basically, I can't compile the new drivers I need to run this card. Any ideas? These are just my theories, and if anybody thinks they know what's going on, PLEASE respond. All I know for sure is "it doesn't work!"
lsmod displays neither hide nor hair of any ethernet modules, leading me to believe that it's either a part of the kernel, or non-existant. If anyone has a theory and requires more info, just tell me what to get you. Any and all help on this subject is much appreciated. Thanks a lot guys and gals :)

:mad:

[ 05 February 2001: Message edited by: Tyr-7BE ]

[Molecule Man]

8139too is a 2.4 driver. In 2.2 it is rtl8139. Try insmod rtl8139 and then ifconfig eth0 up and see if that gets your network adapter working.

BTW I would check double the names on those cards. The DFE530tx and DFE530tx+ have totally different chipsets, with the plus using the rtl8139. Also I did not see any mention of the dfe538 on dlink's site, is that the correct model?

[Tyr-7BE]

ifconfig eth0 up results in some sort of message saying that a device is temporarily not available. However, modprobe eth0 results in rtl8139too being inserted (but it remains unused), and modprobe eth1 changes via-rhine from (unused) to <autoclean>. I'm not sure what autoclean is.
rtl8139too, rtl8139, and via-rhine are all .o files in /lib/modules/2.2.17-21mdk/net/ which heavily implies that the modules are already there and compiled (somehow). Can anyone help me on getting them to auto-insert at boot time and assign themselves to an eth(N) controller? Netconf doesn't do the job. I try to tell netconf to assign via-rhine to eth1, but as soon as I click ok, it goes back to the way it was before: telling me that I have no ethernet controllers.

[Tyr-7BE]

Shad: I know...it's really strange how D-Link doesn't list the DFE 538TX on its site, but records of it are available on various linux hardware-compatibility sites and lists. It's rumored to use the rtl8139 module, but I haven't been able to test it, mainly because of the fact that no matter what I do, linux tells me I have no ethernet controllers (despite the fact that dmesg tells me that they have been found and it's broadcasting their addys). I know that the DFE 538TX exists because I hold the official disk in my hands at this very moment. It's just quite uncommon.

[skweegie]

hiyas,

from the dmesg, the module drivers are detecting the card. the problem however is that no irq is assigned to those devices. most often than not, this occurs because you have "PNP OS enabled" or something similar enabled in your BIOS. this option MUST be disabled. there are other things to try, but the above is the usual culprit.

lmk how it goes...

[Molecule Man]

Usually I don't suggest this, but do you run kudzu? If not, turn it on then reboot. Also make sure your network loopback is working.

Does find and configue your NICs? No? Shutdown and take out the NICs. Power up and hopefully kudzu will prompt you to let remove the config files for them. Do that. Shutdown again and install just one card. Boot up and let kudzu configure the card. Hopefully the one will work and you can repeat.

[Tyr-7BE]

skweegie, you're the coolest guy/gal I've ever known. I'm infinitely closer to getting this thing to work!

current dmseg | more:

via-rhine.c:v1.08 6/24/2000 Written by Donald Becker http://www.scyld.com/network/via-rhine.html
eth0: VIA VT3043 Rhine at 0x9000, 00:50:ba:c9:53:86, IRQ 3.
eth0: MII PHY found at address 8, status 0x7809 advertising 05e1 Link 0000.

after a modprobe of eth0, and an ifconfig eth0 up

lsmod:

Module: Size: Used by:
via-rhine 8560 1 (autoclean)
pci-scan 2624 0 (autoclean) [via-rhine]


Thanks a whole lot :) You even got my sound card working, which I was planning on trying as soon as I got online. I'm so close now. As I see it, the module is in use, it's detecting the card correctly, now it just needs to be configured.
This may sound like the newbiest of newbie questions, but here goes. Now that I have an IRQ on my eth0, and can assign a module to it (I can do it manually...I'll wait about automatically assigning it later), how do I set it up? I went into netconf. I'm using Bell Sympatico High Speed edition ADSL. I set the hostname to sympatico.ca, the IRQ to 3, the device to eth0 and the module to via-rhine. How do I know the IP address for my network card? I'm sorry if this is a stupid question.

[Strike]

Well, with DSL, you might have to get an application for PPPoE (Point-to-Point Protocol over Ethernet). Search around for your DSL ISP in these forums and see if someone has asked a similar question. Also, you probably don't have a fixed IP (though you might), in which case you will probably be using DHCP (Dynamic Host Configuration Protocol) to obtain your IP address from one of your ISPs DHCP servers.

[Tyr-7BE]

Thank you one and thank you all! I am writing this message from my Linux Mandrake 7.2 system :) Turns out that once my eth0 was assigned an IRQ, all I had to do was download roaring penguin (http://www.roaringpenguin.com/pppoe/) and it worked beautifully :) Thank you so much to everyone who has contributed. LNO kicks *** and is a great help to all. Now that linux is up and running, I'm gonna go punch my roommate in the face because he's really annoying :) Thanks again everyone.