WUSB11 ver 2.6 Driver Not Working
 

Alright my problem is probably a common one among WUSB11 ver 2.6 users

anyways my usb internet access point (WUSB11 ver 2.6 with an Atmel chipset) does not like any of the distros i have tried (ubuntu, mepis, knoppix)

i have also tried getting the drivers to work on those using the multitude of online guides. And I have tried both drivers (atmelwlan and berlios)

with Atmelwlan i cannot run the make config, it gives me and error message that there is nothing there or something of that sort, i also tried to run the confisg.sh in the ./scripts dir and it said the file that it wanted to run wasn't where it was supposed to be however it was where it said it was suppoed to be

and with Berlios i can run the make command and then i try to run the make file command and it cannot find the files in the /usr/src/ dir

i really want to move to linux however i cannot make the move without the internet


if there is a distro that supports the atmel or if my problem (which i believe stems from using a binary kernel) can be fixed without too much hassle

[EDIT]

I would prefer a 1-3 CD if i have to choose a new distro, or a distro that loads the wlan stuff first and then you can download the rest later.

any advice/help that can be given would be appreciated

i also plan on writing a tutorial for non redhat WUSB11 ver 2.6 installation if i ever get this thing working. i will give credit those who helped me on the website as well.

Also i work for a webhosting company so any advice given i will be glad to set you up with free (enriched) webhosting.

Mandrake 10 has the berlios drivers and should work fine.
Mandrake 10.1 has the drivers as well, but they are broken [on my machine].
I currently run Mepis 3.3 with berlios drivers personally compiled in.

What steps did you follow for your makes? I could walk you through the process for mepis, which is relatively simple, just takes some compile time.

i would love for you to be able to walk me through the steps

basically all i have done is taken the latest cvs and put it on there cd's to the directory, typed make, make install

and it returned errors about not finding the stuff in the directory /usr/src/2.6.xx.xx (i forgot the specifics)

Mandrake would be the distro to go with. There is one website which talks about binary relations which i think might be of help. http://www.wasab.dk/morten/blog/arch...-redhat-linux.
Good luck.

wrong link
http://www.wasab.dk/morten/blog/arch...d-redhat-linux
I too, am in a big mess.

Just to clarify, this needs to be a hard drive install that you compile the drivers into. If you are running in livecd mode this will not work.

First, the berlios drivers require the complete kernel source in order to successfully compile (this is likely where your errors stemmed from). To do this, follow steps 1, 2, 3, 4, and 7 (as root) in the KERNEL-README in /usr/src . Going that far will not install a new kernel, but will generate the complete kernel source (which you need).

KERNEL-README:
For step 4 I applied all the available patches and diffs. You can disregard steps 5 and 6, and in your case steps 8 and 9 are also unnecessary.

Step 7 will take some time, as the kernel source is LOTS of code. Depending on the machine, I generally expect ~30 minutes for this to complete.

Once that is done, then you should be able to run your original make and make install for the berlios drivers without errors.

Finally, the newly installed driver *should* now automatically recognize the adapter and you should be able to set up the connection in the "Mepis OS Center". If not, it likely needs to be loaded via modprobe like this (at a command line):
Then type:
If one of the ID numbers it outputs is "066b:2211" then type:
Otherwise if it outputs "077b:2219" then type:
and in a few moments the connection should start up.

If you have any problems/issues let me know.

EDIT: See my "Post # 10" on installing the driver firmware. The drivers won't work without the firmware.

I just checked out dchirdon's link and it refers to ndiswrapper, which is a tool for using binary drivers from Windows in Linux. The last I checked (about a month ago) ndiswrapper did not quite work with my WUSB11 windows driver, though it came far closer than previous ndiswrapper releases had.

By the way, Mepis 3.3 comes with a much more recent version of ndiswrapper than Mandrake 10.1.

last i night i complied the kernel no problems...

i cd'd into the untar'd directory
i ran 'make' (it seemed to of run through all my modules and such and no problems)
i ran 'make install' and got this

root@1[at76c503a]# make install
mkdir -p .tmp_versions
cp /lib/modules/2.6.10/build/.tmp_versions/*.mod /home/at76c503a/.tmp_versions
make -C /lib/modules/2.6.10/build SUBDIRS=/home/at76c503a MODVERDIR=/home/at76c503a/.tmp_versions \
EXTRA_CFLAGS=" -DCOMPILE_FIRMWARE_INTO_DRIVER" modules
make[1]: Entering directory `/usr/src/linux-2.6.10'
Building modules, stage 2.
MODPOST
*** Warning: "mtd_concat_destroy" [drivers/mtd/maps/sc520cdp.ko] undefined!
*** Warning: "mtd_concat_create" [drivers/mtd/maps/sc520cdp.ko] undefined!
make[1]: Leaving directory `/usr/src/linux-2.6.10'
for i in at76c503-i3861.ko at76c503-rfmd.ko at76c503-rfmd-acc.ko at76c505-rfmd.ko at76c503-i3863.ko at76c505-rfmd2958.ko at76c505a-rfmd2958.ko at76c503.ko at76_usbdfu.ko; do \
find /lib/modules/2.6.10 -name $i -exec rm -f {} {}.orig \; ;done
mkdir -p /lib/modules/2.6.10/kernel/drivers/net/wireless/at76c503
install -m 644 -o 0 -g 0 at76c503-i3861.ko at76c503-rfmd.ko at76c503-rfmd-acc.ko at76c505-rfmd.ko at76c503-i3863.ko at76c505-rfmd2958.ko at76c505a-rfmd2958.ko at76c503.ko at76_usbdfu.ko /lib/modules/2.6.10/kernel/drivers/net/wireless/at76c503
/sbin/depmod -ae

i then ran modprobe's and got this

root@1[at76c503a]# modprobe at76c503
WARNING: Error inserting at76_usbdfu (/lib/modules/2.6.10/kernel/drivers/net/wireless/at76c503/at76_usbdfu.ko): Invalid module format
FATAL: Error inserting at76c503 (/lib/modules/2.6.10/kernel/drivers/net/wireless/at76c503/at76c503.ko): Invalid module format
root@1[at76c503a]# modprobe at76_usbdfu
FATAL: Error inserting at76_usbdfu (/lib/modules/2.6.10/kernel/drivers/net/wireless/at76c503/at76_usbdfu.ko): Invalid module format
root@1[at76c503a]# lsusb
Bus 004 Device 003: ID 058f:9360 Alcor Micro Corp.
Bus 004 Device 002: ID 046d:0870 Logitech, Inc. QuickCam Express
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 002: ID 077b:2219 Linksys WUSB11 V2.6 802.11b Adapter
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 003: ID 05dc:a410 Lexar Media, Inc.
Bus 001 Device 001: ID 0000:0000
root@1[at76c503a]# modprobe at76c503a-rfmd
FATAL: Module at76c503a_rfmd not found.

any suggestions?

I saw some of that while compiling for my nvidia card in version 2.6.10 and 2.6.11 of the kernel as well. Don't know how to fix it but I reverted back to my 2.6.8.1 kernel. Don't know if you can try something like that as well? It's kind of a hassle compiling so much kernels I think and I can't say for sure if it work.

Are you running the basic Mepis 3.3 hard drive install?
Did you copy the .config file over without changing it?
And did you make sure to skip step 6 and *not* run "make xconfig"?
Did you copy all the patches over from the patches directory and apply them?

The module format error appears to typically happen when either the configuration, the compiler, or other things are "out of sync" with the running kernel. Modprobe basically thinks that the modules you compiled were made for a kernel incompatible with the one you are running.

Ideally, you should have had the same results as me, modules that work.

Oh, and "at76c503a-rfmd" was a mistake on my part. It should be "at76c503-rfmd".

I almost forgot also, once the modules do work properly you will need to download the driver firmware, found [ here ], and run its install script.

i installed simplymepis3.3

there wasn't a .config in the patches directory

i copied all the patches (and ran them)

i am guessing that the missing config is the root of the problems...is there a way to get it?

Good good. I was starting to get worried.

The .config file is there, but it is hidden. All files in Linux with a dot (.) in front of them are hidden files.

To view the hidden files from the command line type:
Or to view them in the file manager, click on the "View" menu, and select "Show Hidden Files".

With the proper .config file in place, everything should go smoothly.

will i need to recompile the kernel?

Yes. :)

crap. alright i will work on it now.

i will post again in about an hour and half with the results...