atmelusbdrivers.dsl wlan wifi usb driver
Topic: atmelusbdrivers.dsl wlan wifi usb driver
started by: telephone
Posted by telephone on Nov. 09 2005,17:27http://distro.ibiblio.org/pub/linux/distributions/damnsmall/mydsl/testing/atmelusbdrivers.dsl.info
i found out elsewhere on the web that
my usb wlan-wifi device
is compatible to atmel.
all i should do
change or add my vendor id and product id
in a config file,
where atmel devices are listed.
how to update read-only knoppix kernel-files?
( for ex. after update-modules from root)
some help to one of the topics?
main topic is to make the atmel-driver think my devive # and product # is an atmel product
or where to contact the driver author ?
Posted by tempestuous on Nov. 16 2005,12:00Be aware that this driver was compiled for the 2.4.26 kernel, so is good for DSL versions 0.8.0 - 1.5.
From version 2.0 the driver is useless, and will be removed from the mydsl downloads soon.
Regarding compatibility - check here - < http://at76c503a.berlios.de/devices.html >
Your adaptor (whose brand and model number you didn't mention) may be best supported by this driver ... or the Sourceforge atmelwlandriver.
Don't worry about changing a config file - this is only for automated loading. Do this (assuming this driver is correct) -
## Install the driver. In EmelFM select atmelusbdrivers.dsl and press "MYDSL"
## or the manual way - open an xterminal,
## first we need to become superuser
## now we need to run "depmod", which is easy with a HD install,
## but difficult with the liveCD because much of the filesystem is read-only.
## so for a liveCD we need to make certain files writeable with the next 18 lines of code
cp modules.dep tmp1
cp modules.generic_string tmp2
cp modules.pcimap tmp3
cp modules.isapnpmap tmp4
cp modules.usbmap tmp5
cp modules.parportmap tmp6
cp modules.ieee1394map tmp7
cp modules.pnpbiosmap tmp8
rm -rf modules.dep modules.generic_string modules.pcimap modules.isapnpmap modules.usbmap modules.parportmap modules.ieee1394map modules.pnpbiosmap
mv tmp1 modules.dep
mv tmp2 modules.generic_string
mv tmp3 modules.pcimap
mv tmp4 modules.isapnpmap
mv tmp5 modules.usbmap
mv tmp6 modules.parportmap
mv tmp7 modules.ieee1394map
mv tmp8 modules.pnpbiosmap
## map the new modules
## Now load the driver
## if no error messages, this should create a network interface, wlan0
## you can check this by running "ifconfig -a"
## now set up the wireless network
iwconfig wlan0 essid MY_ESSID key 1234567890 mode managed
## for automatic IP
pump -i wlan0
## or for static IP
## modify /etc/resolv.conf to include your nameservers
#ifconfig wlan0 192.168.0.xx
#route add default gw 192.168.0.1 wlan0 # or whatever your router's IP is
Obviously, replace "MY_ESSID" with your SSID and "123467890" with your WEP key.
MAKING IT PERMANENT with a liveCD or Frugal install.
This driver package can be reinstalled at each boot with the boot parameter -
"mydsl=hda1" (or sda1, or floppy, etc)
Of course, the all-important "depmod" process is still required.
A neat way to achieve this automatically is to list the files that depmod modifies in /home/dsl/.filetool.lst,
then run "Backup" from DSLpanel > Backup/Restore.
First, set up the driver and make sure it's working.
Now add the following entries to /home/dsl/.filetool.lst -
(don't dare delete the "home/dsl/.filetool.lst" and "/home/dsl/.xfiletool.lst" entries)
Run "Backup" from DSLpanel > Backup/Restore
Boot with the boot parameters -
mydsl=hda1 restore=hda1 (or sda1, or floppy, etc)
Posted by telephone on Dec. 11 2005,12:56thanks a lot! excellent reply
what other hardware usb-wlan device do you recommend
which works out of the box either in knoppix or here with dsl?
instead of saving some bucks i could save hours hassling with drivers
all other iwconfig parameters i tried failed as well
any help? any idea? what painless device should i buy?
DSL 2.0 and higher
what driver should i give a test for this device again?
Posted by tempestuous on Dec. 12 2005,00:59This (BerliOS) atmelusbdriver should be compatible with your Siemens Gigaset USB, and you followed the correct process, but the driver appears to have failed to create a network interface .... although perhaps you should try again and just try to run "iwconfig" (not "iwconfig wlan0"). Perhaps the network interface that is created is not "wlan0" but something else?
Also you could try the atmelwlandrivers instead, < ftp://ibiblio.org/pub....ers.dsl >
These are also compatible with your device. There are several different drivers in this package, the correct one for you is usbvnetr. So instructions are the same as above, except that the module to load is usbvnetr (instead of at76c503-rfmd), and the interface name is atml0 (instead of wlan0).
I won't be compiling any more drivers for DSL2.0.
For "out-of-the-box" support for wireless devices, aim for a device that already has a driver available in the distribution. DSL has Prism2/2.5/3 drivers built-in. They work great with my D-Link DWL-122 USB adaptor, though this is only a b-mode device.
For g-mode support, DSL has the Prism54 driver, but the firmware and firmware.agent files are missing. See here for how to get these files -
< http://damnsmalllinux.org/cgi-bin....;t=8943 >
And this driver does not support USB devices.
This site lists what chipsets are in what model devices < http://linux-wless.passys.nl/ >
Posted by telephone on Dec. 13 2005,13:04no such device
same result with atmelwlandrivers
iwconfig with various parameters like wlan0, wlan1, atml0, atml, always: no such device
root@ttyp0[2.4.26]# modprobe usbvnetr
root@ttyp0[2.4.26]# iwconfig usbvnetr
usbvnetr No such device
root@ttyp0[2.4.26]# modprobe usb
modprobe: Can't locate module usb
root@ttyp0[2.4.26]# modprobe usbvnetr
lo no wireless extensions.
ppp0 no wireless extensions.
thanks for the device-hint.