I'm trying to compile the driver for an asound PCI NIC (model ALM2) using gcc with the following arguments : gcc -DMODULE -D__KERNEL__ -I/lib/modules/2.4.19-16mdk/build/include -Wall -Wstrict-prototypes -O6 -c FEALNX.C 2>/home/blitzkrieg/err
Those are not the same arguments that are found in the readme but they produced even more errors so i read the error log and it said that i should use
-I/lib/modules/`uname -r`/build/include
instead of -I/usr/include/linux

It did reduce the number of errors but now I think the is still some trouble with the include files, as the error log still produces many errors, beginning with this one :
In file included from /lib/modules/2.4.19-16mdk/build/include/linux/module.h:12,
from FEALNX.C:73:
/lib/modules/2.4.19-16mdk/build/include/linux/list.h:37: parse error before `new'
/lib/modules/2.4.19-16mdk/build/include/linux/list.h: In function `void __list_add(...)':

In fealnx.c, at line 73, it is an include files, namely #include <linux/module.h>

There are many such errors, so i believe the include files are not correctly referenced...

Could anyone help me with this problem, i'm still a linux

If you want the full log before or after i made the change to the arguments, ill add them.

Thx.

Have you tried the 8139too module?
The Asound PCI NIC (model ALM2) uses the 8139 realtek chip.

yes i tried modprobe 8139too and that is the output :
/lib/modules/2.4.19-16mdk/kernel/drivers/net/8139too.o: init_module: No such dev ice
Hint: insmod errors can be caused by incorrect module parameters, including inva lid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
modprobe: insmod /lib/modules/2.4.19-16mdk/kernel/drivers/net/8139too.o failed
/lib/modules/2.4.19-16mdk/kernel/drivers/net/8139too.o.gz: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including inva lid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
modprobe: insmod /lib/modules/2.4.19-16mdk/kernel/drivers/net/8139too.o.gz faile d
modprobe: insmod 8139too failed

I'm not too sure how i should interpret this....

You running slack8.0 with thw 2.4.19 kernel?

I t means the hardware cannot be found.
and is unable to load the module.
Have you tried:
lspci
and seen what it says about your pci network card. What chip it acualy is.

I use Mandrake 9.0 with kernel 2.4.19

As for lspci, here is the part concerning the NIC :
00:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8029(AS)
00:0a.0 Ethernet controller: MYSON Technology Inc: Unknown device 0803

I have 2 NIC, the first being used to connect to internet (cable modem) and the second is conected to a 2nd computer via a cross cable. The first NIC works fine so here the NIC that doesnt work is the myson one...

As for the model, I'm quite sure it is an asound ALM2, because i used it for quite a while under windows.

With kernel 2.4.19 you would use rtl8139 for your realtek chipset versus the 8139too.

You might try the ne2k-pci module.

On the first nic, the realtek chipset is an older chipset, rtl8139 or 8139too will not work with it. Look into the 8029 module for your realtek. The other nic seem not to be supported but has the chip of 0803, my advice is to pull them out and replace them with newer cards, unless you want to spend the time trying to make them work. You can pick up new asound ether controlers like at a fair price. Try http://www.partshelf.com or http://www.directron.com both carry reasonable priced ethernet cards.

The Asound ALM2 is not using the Realtek 8139 Chipset (check here -> "Support" section). The chipset on it is called Asound 8139 though, very confusing. This chipset is just an alias for the real name of it, the Myson 803(hence the lspci output). The person who first thought of naming it this way should be shot on sight IMO

About those drivers, you don't need to build it, all modern kernels have it prebuild as fealnx.o.gz. Just do a modprobe fealnx and it should work. I've had the same problems with building it, it just seems completely wrong, so it's probably made for another (old) kernel.

I have this card too and I'm experiencing some weird problem with it. It seems like it can only receive stuff, not send. I'll use this example: Box A (ip 192.168.0.1) and Box B (ip 192.168.0.2). When box B pings box A, I can see those pings on a tcpdump session on Box A, Box A thinks he is replying, as tcpdump also shows, but in fact he's not sending anything. Very weird, I'm still trying to figure out the proper module parameters, as that seems to be the problem (works fine on win2k).