Topic: NIC D-link DFE-550 TX

[Kurt Baetens]

Hello,

For the last couple of days, I've been trying to get an e-smith server (V5.1.2) up and running with the D-link NIC DFE-550 TX.
Apparently, this NIC is currently not supported by the e-smith server. So, I've compiled the driver-module (sundance.o) on the e-smith server (after installing the necessary rpm's first). All went well (compilation ok) until I tried to insert the driver-module into the kernel ('insmod sundance.o').

I received the following error-messages after doing the 'insmod sundance.o':

'sundance.o: unresolved symbol init_etherdev_Rdc6a3e7a
sundance.o: unresolved symbol skb_over_panic_RCaef9b0b
sundance.o: unresolved symbol eth_type_trans_Re1da133f
sundance.o: unresolved symbol __kfree_skb_R805843f2
sundance.o: unresolved symbol unregister_netdev_R7abfab38
sundance.o: unresolved symbol alloc_skb_R03da498f
sundance.o: unresolved symbol netif_rx_R1877ba5e
sundance.o: unresolved symbol eth_copy_and_sum_Ra2877817'

Can anybody give me clue what might be the cause of this problem. Or, even better, provide me with some feedback on how to get this NIC working on the e-smith server.

Thanks and best regards !!

Kurt.

[Grub]

Try /sbin/depmod -a

[Kurt Baetens]

Hello Grub,

Thanks for the reply, I've tried /sbin/depmod -a and got the following:

'depmod: Unresolved symbols in /lib/modules/2.2.19-7.0.8/misc/ipsec.o
depmod: Unresolved symbols in /lib/modules/2.2.19-7.0.8/scsi/megaide.o'

Any ideas  ??

Thanks in advance !!

Kurt.

[Tom Keiser]

What did you use for kernel-sources when you compiled? Darrell May has graciously posted all the compile rpms and info on his site, and you should use them rather than search the net: http://myezserver.com/downloads/mitel/contrib/dev-tools/

The error messages you are seeing (ipsec.o and megaide.o) are ones I have seen when the loadable module is compiled for a different kernel than 2.2.19-7.0.8.

Tom

Kurt Baetens wrote:
>
> Hello Grub,
>
> Thanks for the reply, I've tried /sbin/depmod -a and got the
> following:
>
> 'depmod: Unresolved symbols in
> /lib/modules/2.2.19-7.0.8/misc/ipsec.o
> depmod: Unresolved symbols in
> /lib/modules/2.2.19-7.0.8/scsi/megaide.o'
>
> Any ideas  ??
>
> Thanks in advance !!
>
> Kurt.

[Kurt Baetens]

Hello Tom,

Thanks for the reply; I've compiled the module using the following kernel-sources:

cpp-2.96-85.i386.rpm
gcc-2.96-85.i386.rpm
glibc-devel-2.2.4-24.i386.rpm
kernel-source-2.2.19-7.0.16.i386.rpm
kernel-headers-2.4.9-31.i386.rpm
make-3.79.1-5.i386.rpm

Do you think that's the problem ?
I'll give it a try with the rpm's you mentioned !

Thanks a million already !!

Kurt.

[Filippo Carletti]

Use kgcc to compile kernel modules.

[Steve]

I have a D-link DFE-550 TX.  Obviously, it won't work without adding the custom driver.

Kurt,
  How hard was it to get your D-link to work (recompile kernel, etc.)?  Do you know where any How-To's are?  I'm probably going to just buy a $10 NIC that is supported by e-smith, but would like to go ahead and use the D-link if I can.  I'm a fairly advanced user but have yet to recompile kernels.

Any links/information would be greatly appreciated!

Thanks

[Kurt Baetens]

Hello Steve,

I don't have the card working yet. I'll give it a try this evening. I'll keep you informed.

Regards,

Kurt.

[Kurt Baetens]

Hello Tom,

Thanks for the golden hint; after compiling the kernel with the correct kernel-source, I've got the NIC up and running.

I've configured it by just doing ifconfig eth0 for the moment; how can I store this configuration cause when I reboot it's disappeared again.

Thanks !!

Kurt.

[Grub]

In /etc/sysconfig/network-scripts/ifcfg-eth0

DEVICE=eth0
USERCTL=no
ONBOOT=yes
BOOTPROTO=none
IPADDR=XXX.XXX.XXX.XXX
NETMASK=XXX.XXX.XXX.XXX
NETWORK=XXX.XXX.XXX.XXX
BROADCAST=XXX.XXX.XXX.XXX


I don't know if you have to make custom-templates of that.

[Kurt Baetens]

The problem is a little different; whenever I reboot now I have to do 'insmod sundance.o' again to get the NIC up and running.

I have to get it somewhere in the startup-sequence...

Kurt.

[Grub]

oeps... ok... you can always put it in rc.sysinit.

[Kurt Baetens]

But I don't think that's the 'e-smith way' of doing things. If anybody knows the proper procedure, please let me know.

Greetz,

Kurt.

[Peter Francis]

Kurt,

After compiling the kernel and modules, you have to make the initial ram disk, and edit the LILO file.

LILO => /etc/lilo.conf
.....
......
      initrd=/boot/initrd-2.2.19.x.x.img

To make this ramdisk, you will first need to find out what the kernel in /boot is called and then use the mkinitrd command like:
# mkinitrd /boot/initrd-2.2.19.x.x.img 2.2.19.x.x

Finally run the lilo command to write these changes to the boot sector.

# lilo -v

Peter