Click to See Complete Forum and Search --> : DFE-530TXS nightmare


-=AOD=-
01-30-2003, 05:59 PM
hey all. I've been through hell trying to get my d-link DFE-530TXS to work. after looking around i know it runs on D-links own DL1005B chip which i beleive is based on sundance. KDE's PCI info displays the chip as a D-link sundance something (can't remember specifically im in windows). i've made a config script and compiled it with the kernel configuration util in slackware enabling sundance ethernet cards but i still can't get netconfig to find it. im attacthed to a router and use DHCP, slackware linux kernel 2.4.18 any suggestions?

mdwatts
01-30-2003, 06:36 PM
A few of our standard questions/suggestions.

Does

lsmod (list loaded modules)

show your ethernet card module as being loaded?

ifconfig

list both lo and eth0?

Ensure you have PnP OS disabled in the bios as this is the number one cause of PCI devices not being detected and configured properly.

Icarus
01-30-2003, 07:01 PM
If it is loaded, does ifconfig display an IP addess? If not try dhcpd or dhclient (I'm not sure which one Slack uses)

Okie
01-30-2003, 07:08 PM
i have a computer with a D-Link-530 and several Linux distros identify it as a rtl8139 and it runs great...

also known as a 8139too

DMR
01-30-2003, 07:25 PM
Originally posted by Okie
i have a computer with a D-Link-530 and several Linux distros identify it as a rtl8139 and it runs great...

also known as a 8139too Oakie,

There are a few different generations/flavors/versions of chipsets used in the DFE-530 product line- the DFE-530TXS in particular chipset does use the "sundance" driver.


-=AOD=-,

Definitely try my esteemed colleague (:D) mdwatts' suggestions and post the results.

Also- when your system first boots, look for messages/errors concerning "eth0" and tell us what they are.

-=AOD=-
01-31-2003, 04:26 AM
hey guys.

lsmod shows no ethernet, just soundcore,pcmcia-core, and ide-scsi.

ifconfig only shows lo

as for boot messages i dont know how to scroll up to read everthing but near the bottom it says:

attempthing to configure eth0 by contacting a DHCP server
dhcpd[57]dhcpstart: ioctl SIOCGIFHWADDR: No such device

the kernel only seems to have support for "sundance alta". could this be part of the prob? i looked pretty thoroughly on the web for info and i did find some site talking about sundance patches. i just have no clue how i would patch the code.

hope you guys can figure this **** out. having linux without the internet is like having an ice cream cone and standing in front of a locked baskin robbins.

mdwatts
01-31-2003, 10:13 AM
Originally posted by DMR

Definitely try my esteemed colleague (:D) mdwatts' suggestions and post the results.


Ah shucks... :o

-=AOD=- ... Did you try any other our suggestions?


SIOCGIFHWADDR: No such device


Usually indicates a resource conflict. Have you disabled PnP OS in the bios?

If that doesn't work, try moving your ethernet card to another slot.

DMR
01-31-2003, 01:37 PM
As mdwatts asks: what have you tried so far? In general, you need to try all of the suggestions we give you, and then repost with the exact results. If we don't know what you have or haven't done it will take us longer to fix the problem. Sooo:

1. Turn off Plug-N-Play in your BIOS. If that doesn't work move the card to another PCI slot.

2. Run the following command and post the result:
lspci -vv|grep Ether (The "E" in Ether needs to be capitalized)

3. Run the following command and post the result:
ifconfig -a

4. You need to load the sundance module; run the following two commands in the order given:

depmod -ae
modprobe sundance
(I'm not positive that "sundance" is the exact name of the sundance module, but I'm pretty sure it is)

5. If you get no errors from "modprobe", you should see "sundance" in the list of loaded modules returned by:

lsmod

6. If so, put the following line in your /etc/modules.conf file to automagically load the module at bootup:

alias eth0 sundance


Walk through those steps and tell us exactly what you get.

Also, you might take a look in /var/log/messages to see if there are any errors concerning eth0 or the sundance module. Posting the output of the following command might help as well:

dmesg

-=AOD=-
01-31-2003, 08:09 PM
DMR:

i followed your instructions, it found the module identified the card. i added the line to the modules.conf and all works well now. i write to you from within linux :) thx alot guys

DMR
01-31-2003, 09:04 PM
Wonderful- glad we could help!

:)