i'm running mandrake 9.1 on my new old p3. ('cause i couldn't get mdk9.2 to boot) i installed the src kernel 'cause i read i have to. (i didn't upgrade the kernel, as far as i heard i don't need to)

i succeeded to compile the acx100 driver (yes, it is the right one) but when i try to insmod all i get is unresolved_symbols

my problem is that the dwl-120+ is the only card that is connected via usb & uses the texas instruments chip. the driver says that it is still very experimental with this card. (please forgive me, i didn't choose this card myself...)

so it isn't surprising that i can't find neither anyone asking things going further than "which driver should i use" nor any how-to concerning this card...

so, finally my question: what's the cause of this unresolved_symbols when i try to insmod & what should i do?

I believe if you check the acx100 website you'll find that support for the D-Link, dwl-120+ is not yet finished. He's working on now and I, for one, am patiently waiting.

Im new at this myself. I'm using dwl 650+ with fedora. I also get unresolved_symbols after depmod in fedora, but the module works great.

http://www.houseofcraig.net/acx100_howto.php

also, after I got everything configured, I still have to do dhclient eth0 after restart. Still trying to figure that out. But, I'm learning

Copied shamelessly from my HOWTO;

"If they complain about symbolic links, you need to recompile your kernel. Edit the .config file in your kernel source directory and look for the line CONFIG_MODVERSIONS= make sure it says ``n''. If it doesn't, change the ``y'' to ``n'' and recompile your kernel. Note; you only need to remake your image! ``make bzImage''. Copy it to the correct place and reboot Linux."

Oh, and if you DO remake the kernel image, make sure you can still use the old kernel if the new one does not work!

Good luck!

DigitalVixen: i couldn't change the .conf file 'cause i didn't find any and i don't know where my kernel souce dir is 'cause installed it with an rpm, so i don't know how to recompile it either... :\

ignoring the insmod errors didn't work at all.
instead, i proceeded with craig's acx howto from the chapter "installing the module & firmware" on (to avoid the insmod-thing)

instead of acx100_pci i always used acx_usb, the last/most important steps were:
1. i edited /etc/modules.conf by adding the line
i guess this line should have been somehow different...
(use_eth_name=1 has been ignored by a warning at depmod anyway i think)

2. depmod -a without errors

3. to check the presence of a reference to the module:
the result was ok but: shouldn't the entry rather be in modules.usbmap?

4. to check if the module got loaded:
"lsmod | grep acx_usb" returns
acx_usb 131200 0 (unused)
usbcore 72992 1 [acx_usb usb-uhci]

5.ifconfig -a returns
note that neither a MAC address nor an interrupt with a base address is given...
(even if i don't know what an interrupt is: the how-to said it must be there)

so what went wrong?

to level: i know this. but the website nowhere says that it isn't working at all.

& anyway: the main thing for me is not to get it to work but to learn something by trying to get it to work. that's why i didn't only ask "what should i do" but "what's the cause of it", too.

i wanna use linux whenever it is possible, preferably always. but you have to agree with me that this isn't realistic while the internet isn't working.

that's why i try it, even if it seems impatient to you

If you haven't tried this

my 650+ would only return the right mac address after entering these commands:

iwconfig eth0 mode managed channel x essid xxxxxxxx

and

iwconfig eth0 essid xxxxxxxxx

of course, it never did return all zeros either.

I'm new at this, so this could also be completely meaningless. lol

well i didn't have the time to test it yet, but i think it won't work 'cause the problem seems to be that the card isn't detected or something like that. however, the iwconfig thing goes a step further, it concerns the connection to the access point, doesn't it?

i'd appreciate other opinions...are there any?

additionally, i'm keen on knowing why the reference to the module is in *.pcimap & not in *.usbmap & why there isn't any mac address...

Greetings,

I'm posting this using my dwl-120+ and the latest version of the acx100 driver (0.2.0pre8_plus_fixes_6), kernel 2.6.3 on Slackware 9.1 and with 128bit wep. I tell you this because it proves that it *can* be done. (got Slack?)

How? Understand first and foremost that the acx_usb module is not yet ready for "Managed" mode, meaning don't attempt to use it for connecting to your normal wireless access point or router.

Instead, I've set another machine up as what I like to call an "ad-hoc wireless router". Basically, this is a very old notebook (compaq 400cx) running Slackware 9.0, using *both* an atmel-based wireless pcmcia card and a linksys pcm100 wired card in it's slots. Using the ip forwarding howto from the tldp.org site I set up the forwarding using the example file in that howto.

My experiences with this device and the 0.2.0pre8_plus_fixes_6 version of the acx100 open source driver is that with wep (64 or 128) it can be unreliable and needs to be "re-upped" at times. Yet, without wep enabled on my 'adhoc wireless router' I've used the device for hours on end for email and internet.

if you have the spare hardware lying around to set up an ad-hoc wireless router of your own for use with this device, email me at: linux-help@houseofcraig.net and I will help you get everything set up.

craig