[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: wireless adapter recommendation



Default User(xyzzyx@sbcglobal.net) is reported to have said:

<--<snip>-->

> Thanks to all for your replies.  
> 
> I am trying to set up a Netgear MA111 (v1) usb wireless adapter on a
> desktop system, later to set up on a laptop if it works on the desktop
> system. 

Sorry but I have to ask as you did not mention what you have done to
get ready to install the software.

Did you do 

aptitude install linux-wlan-ng linux-wlan-ng-source linux-wlan-ng-firmware
and most important linux-wlan-ng-doc

then did you read the file
/usr/share/doc/linux-wlan-ng/firmware/NEWS.Debian.gz
or do 
man  linux-wlan-ng-build-firmware-deb

if you did the above then, while connected to the net, did you execute
the file mentioned there that downloads the necessary firmware files from
the the linux-wlan.org site?

Did you read the docs in /usr/share/linux-wlan-ng?

Then if the answer to all of the above, did you look at the config
files in /etc/wlan and edit, if necessary, the wlan.conf file?

> 
> lsusb says:
> Bus 001 Device 003: ID 0846:4110 NetGear, Inc. MA111 WiFi (v1)
> Bus 001 Device 002: ID 058f:9254 Alcor Micro Corp. Hub
> Bus 001 Device 001: ID 0000:0000
> 
> http://linux-wless.passys.nl says that linux-wlan-ng should work with
> this adapter.

<http://www.linux-wlan.org> also says that the MA111 works with
linux-wlan-ng.

NOTE:  Prior to running module-assistant, you must have a kernel
source file and a kernel headers file installed.

ie in my case

VT1 root-3-TESTING:# dpkg -l linux-source* linux-header* |grep ^i
ii  linux-headers-2.6.18-4                 2.6.18.dfsg.1-12 Common header files for Linux 2.6.18
ii  linux-headers-2.6.18-4-k7              2.6.18.dfsg.1-12 Header files for Linux 2.6.18 on AMD K7
ii  linux-source-2.6.18                    2.6.18.dfsg.1-12 Linux kernel source for version 2.6.18 with


> I did:
> - install module-assistant
> - run module-assistant prepare
> - run module-assistant auto-install linux-wlan-ng
> - reboot
When you run m-a it compiles the software and creates .deb files.
Make sure that they are then installed, either by m-a or by you.
The linux-wlan-*.deb files will be in the /usr/src directory.

After running m-a and installing all of the packages I get

ii  linux-wlan-ng                      0.2.7+dfsg-2   utilities for wireless prism2 cards
ii  linux-wlan-ng-firmware             0.2.7+dfsg-2   firmware files used by the linux-wlan-ng dri
ii  linux-wlan-ng-firmware-files       0.2.7+dfsg-2   firmware files used by the linux-wlan-ng dri
ii  linux-wlan-ng-modules-2.6.18t40    0.2.7+dfsg-2   drivers for wireless prism2 cards
ii  linux-wlan-ng-source               0.2.7+dfsg-2   linux-wlan-ng driver

As this is linux.  There is no need to reboot.

Oh, have you installed the dhcp3-client package?  You need that for
DHCP.

<--<snip>-->
removed dmesg listing
> 
> (NOTE: eth0 is a wired pci card connection, works fine, uses tulip
> driver).  
> 
> Notice from dmesg these lines: 
> prism2usb_init: prism2_usb.o: 0.2.5 Loaded
> prism2usb_init: dev_info is: prism2_usb
> usbcore: registered new driver prism2_usb

I do not see the wlan entry in the ifconfig output.  There should be 
scripts in /etc/network/if.up.d and post-down.d that start/stop the
device as soon as it is plugged in or ifup/ifdown wlan are executed.
They depend on a file you have to create in /etc/wlan.  

Here is what I see when the USB adapter is up

#iwconfig
lo        no wireless extensions.

sit0      no wireless extensions.

wlan0     IEEE 802.11-b  ESSID:"Mtntop_AP"  Nickname:"Mtntop_AP"
          Mode:Managed  Frequency:2.437 GHz  Access Point: 00:0F:B5:11:37:1F
          Bit Rate:11 Mb/s   Tx-Power:18 dBm
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:off
          Link Quality=25/92  Signal level=-65 dBm  Noise level=-90 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0
# ifconfig
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:4 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:280 (280.0 b)  TX bytes:280 (280.0 b)

wlan0     Link encap:Ethernet  HWaddr 00:0A:E9:09:02:27
          inet addr:192.168.1.9  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::20a:e9ff:fe09:227/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:73 errors:0 dropped:0 overruns:0 frame:0
          TX packets:64 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:13163 (12.8 KiB)  TX bytes:11254 (10.9 KiB)

and my /etc/network/interfaces file is

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback
   up route add -net 127.0.0.0 netmask 255.0.0.0 dev lo
    down route del -net 127.0.0.0 netmask 255.0.0.0 dev lo

# The primary network interface
# Ashton USB Dongle
#   NOTE:  all setup for this USB Dongle is is in /etc/wlan/
#   and the startup script in /etc/network/if-pre-up.d/linux-wlan-ng-pre-up
#   and down with the /etc/network/if-post-down.d/linux-wlan-ng-post-down
auto wlan0
iface wlan0 inet dhcp


Hope I didn't miss anything.  It's late so if you need more help, we are here.

Regards

Wayne

-- 
Your mouse has moved.  Windows needs to be restarted for the
changes to take effect.  [OK]
_______________________________________________________



Reply to: