Compiling source code for a network card module

WindowsBurner · 02-14-2005, 12:30 PM

Hullo,

I've got a source file and a header file that is supposed to be the linux drivers for my new network card. Thats great....what do I do with them?

I looked through the source and found at the end a message on compiling parameters, but it doesn't work in the slightest. I've been googling for a few hours now but haven't found anything, can somebody at least point me towards a source of info? I'm gonna keep looking, but help would be appreciated.

Okay...I've created the slackware 10.1 bootdisk and the 2 rootdisks.
I then catted the "network.dsk" image to a floppy and I can run the network setup, my only problem is... how do I actually tell the system to use that module? I can prob for cards using the module, but how do I tell it to use it?

I'm kinda completely lost...*groan*

chup · 02-14-2005, 03:35 PM

Modprobe your_module ?

edit: sorry, not really helpful.

What is the name of the module you are using? And the network card?

WindowsBurner · 02-14-2005, 03:43 PM

I'm back to trying to compile the module on my slackware 10.1 comp.
This is computer is not using the card. It is in my laptop which doesn't have a cd-rom drive, which is why I'm trying to get the card to work, so I can connect to my NFS server and install slack.

I went to D-Links site to see if they could help, and they gave me a header file and source file and a gcc command to compile it, but I don't think pcmcia is configured on this computer(why would it be though..it doesn't have a cardbus or anything). And I get a huge friggin error message, I'd post the message but its to long for me to type and I can't seem to copy it over.

I'm lost, the only thing I can think of at the mo is find out if pcmcia is installed and where. Only prob is...how?

edit : Just saw the post from chup.
I can't modprobe the module because all I've got are the two rootdisks loaded in memory, slack isn't actually installed on the comp, so modprobe tells me it can't find the modules. I was trying to use the 8139too module, because I've heard/read you don't need the drivers that come with the card, you can use it instead. Which is grand and all, but when I run the network util from my network.dsk, it can't find any card using that module. I don't know how to tell to use that module anyway. *shrugs*

The card is a D-Link DFE-690TXD

WindowsBurner · 02-16-2005, 08:13 AM

Ok, everything I've read says that you need to use the 8139too driver.
Only thing is when I run the network utility from the network supplemental disk, it can't find any cards that use that module.

And when I run the pcmcia utility from the pcmcia supplemental disk, it starts the "pcmcia_core" module and the "i82365" module as well as "ds"(checked by running lsmod). The "pcmcia_core" module is being used "0" and so is "ds", I'm guessing this means their not being used,except that "pcmcia_core" is being used BY "[ds i82365]".The "i82365" module us being used "2", what does that mean? Who is using it?

I've always known linux is hard, I've had my share of troubles, but man this is ridiculous. I'm still working on it, but help would be extremely appreciated.
I've got 6 laptops to install slack to, all using the exact same card.

Thanks all,

ME

WindowsBurner · 02-16-2005, 12:04 PM

Okay, I've tried using insmod to load the module, and I get these error messages :

Code:

8139too.o.gz : unresolved symbol mii_ethtool_sset
8139too.o.gz: unresolved symbol mii_link_ok
8139too.o.gz : unresolved symbol crc32_le
8139too.o.gz : unresolved symbol mii_ethtool_gset
8139too.o.gz : unresolved symbol mii_check_media
8139too.o.gz: unresolved symbol generic_mii_ioctl
8139too.o.gz: unresolved symbol mii_nway_restart
8139too.o.gz: unresolved symbol bitreverse

Whew! Had to type that all in, hope there aren't too many error messages...

Anyways, I haven't a clue as to what this means.

ME

__J · 02-16-2005, 12:28 PM

try modprobing the module in. unresolved symbols means the module is trying to link to functions from other modules but cannot find them ( they need to be loaded also). insmod does not load the modules that are needed by the module that you are trying to load but modprobe does.

from looking at it, looks like you need the mii module loaded first before you try to load your module ( This is why they get "stacked" in the output from lsmod, one module depending on another)

EDIT: all you need to do for 8139too is :

modprobe 8139too and all will be taken care of for you

WindowsBurner · 02-16-2005, 01:29 PM

Can't modprobe it because modprobe says it can't find the module.
Even though I checked the list with "modprobe -l" and it is in the list, modprobe can't find it.

I insmoded the mii module in, and that fixed some errors but I still have :

Code:

8139too.o.gz : unresolved symbol crc32_le
8139too.o.gz: unresolved symbol bitreverse

I'm gonna look into it and see if I can figure out which module is missing.
Thanks for your input

ME

__J · 02-16-2005, 01:31 PM

insmod crc32

also run depmod -a and see if that helps with your modprobe issues

WindowsBurner · 02-16-2005, 01:37 PM

It was the crc32 module that was needed for those errors, but now I get new ones :

Code:

path/to/module/8139too.o.gz : init_module: No such device
path/to/moudle.8139too.o.gz : Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
 You may find more information in syslog or the output from dmesg

Now if you'll recall, I'm booting off of a floppy. I don't have syslog and dmesg just parrots back stuff from the last 20 or 30 commands I've run, which doesn't help at all.

Well, I'm gonna take a small break and then get cracking on it again.

Thanks all,

edit : depmod is not on the floppy __J , I can try to copy it over though. Thanks

ME

__J · 02-16-2005, 01:44 PM

does this use the realtek 8139 chipset? drivers check the hardware as they are loading and if it doesn't find the hardware it's looking for it will refuse to load.

WindowsBurner · 02-16-2005, 01:58 PM

Forgive my ignorance, but how do I check the chipset? I checked the manual but it don't say sh**.

__J · 02-16-2005, 03:28 PM

Well, normally they are on the pci bus and you can view them in the output of "lspci" but in your case with the laptop card I dunno

, you'll probably have to get the specifics off of the vendor's site.

you did say you got a driver from d-link's site didn't you?

WindowsBurner · 02-16-2005, 04:22 PM

Yeah I checked the manual and the card and anything else I can think of..but no luck.
Yes I got a driver from D-Link, but I have to compile it on my desktop machine which doesn't have any cardbus slots or pcmcia anything for that matter. And I get a friggin 2 foot long error message. Plus I've read that you CAN'T use that driver because the linux kernel doesn't support the card, and I went and checked, and the kernel doesn't support the card.