Networking Forums  

Go Back   Networking Forums > Networking Newsgroups > Linux Networking

How to get my wireless adapter work?

Reply
 
Thread Tools Display Modes
  #1  
Old 05-23-2004, 05:57 AM
Default Re: How to get my wireless adapter work?



Shanyu Zhao <(E-Mail Removed)> wrote:

> I have a IBM T40 laptop but never got my wireless adapter work in
> Redhat linux 9.0. I know that my wireless adapter is Cisco Aironet 350
> Mini-Pci


> The LED for the wireless adapter never lit up.
>
> Anyone has experience about this situation? Please help me out.


Please show the output of the following commands as root.

ifconfig

iwconfig

lsmod

lspci

--
Cameron Kerr
(E-Mail Removed) : http://nzgeeks.org/cameron/
Empowered by Perl!


Cameron Kerr
Reply With Quote
  #2  
Old 05-23-2004, 08:02 AM
Shanyu Zhao
Guest
 
Posts: n/a
Default How to get my wireless adapter work?

Hi,

I have a IBM T40 laptop but never got my wireless adapter work in
Redhat linux 9.0. I know that my wireless adapter is Cisco Aironet 350
Mini-Pci, and I found a driver for linux which support Aironet 350
MPI(stands for mini-pci, somebody says so) from cisco website, but
when I installed the driver and the utilities, I still couldn't get it
work. When I tried to bring out the main configuration UI, I only got
"radio not found", a sign for not correctly installing the driver,
according to the trouble shooting of cisco documentation. The LED for
the wireless adapter never lit up.

Anyone has experience about this situation? Please help me out.

Thanks,

Shanyu
Reply With Quote
  #3  
Old 05-23-2004, 10:55 PM
Shanyu Zhao
Guest
 
Posts: n/a
Default Re: How to get my wireless adapter work?

Thanks, see below:

Cameron Kerr <(E-Mail Removed)> wrote in message news:<(E-Mail Removed)>...
> Shanyu Zhao <(E-Mail Removed)> wrote:
>
> > I have a IBM T40 laptop but never got my wireless adapter work in
> > Redhat linux 9.0. I know that my wireless adapter is Cisco Aironet 350
> > Mini-Pci

>
> > The LED for the wireless adapter never lit up.
> >
> > Anyone has experience about this situation? Please help me out.

>
> Please show the output of the following commands as root.
>
> ifconfig


eth0 Link encap:Ethernet HWaddr 00:09:6B:53:75:11
inet addr:192.168.2.106 Bcast:192.168.2.255
Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:28937 errors:0 dropped:0 overruns:0 frame:0
TX packets:21642 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:37600258 (35.8 Mb) TX bytes:2296925 (2.1 Mb)
Interrupt:11 Base address:0x8400 Memory:c0220000-c0240000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:13256 errors:0 dropped:0 overruns:0 frame:0
TX packets:13256 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:697608 (681.2 Kb) TX bytes:697608 (681.2 Kb)

> iwconfig


lo no wireless extensions.

eth0 no wireless extensions.


> lsmod


Module Size Used by Tainted: P
i810_audio 27720 0 (autoclean)
ac97_codec 13640 0 (autoclean) [i810_audio]
soundcore 6404 2 (autoclean) [i810_audio]
airo 98976 0 (autoclean) (unused)
radeon 116132 0
e1000 50604 1
ipt_REJECT 3928 2 (autoclean)
iptable_filter 2412 1 (autoclean)
ip_tables 15096 2 [ipt_REJECT iptable_filter]
sg 36524 0 (autoclean)
sr_mod 18136 0 (autoclean)
microcode 4668 0 (autoclean)
ide-scsi 12208 0
scsi_mod 107160 3 [sg sr_mod ide-scsi]
ide-cd 35708 0
cdrom 33728 0 [sr_mod ide-cd]
nls_iso8859-1 3516 2 (autoclean)
nls_cp437 5116 2 (autoclean)
vfat 13004 2 (autoclean)
fat 38808 0 (autoclean) [vfat]
keybdev 2944 0 (unused)
mousedev 5492 1
hid 22148 0 (unused)
input 5856 0 [keybdev mousedev hid]
usb-uhci 26348 0 (unused)
ehci-hcd 19976 0 (unused)
usbcore 78784 1 [hid usb-uhci ehci-hcd]
ext3 70784 1
jbd 51892 1 [ext3]


> lspci


00:00.0 Host bridge: Intel Corp.: Unknown device 3340 (rev 03)
00:01.0 PCI bridge: Intel Corp.: Unknown device 3341 (rev 03)
00:1d.0 USB Controller: Intel Corp. 82801DB USB (Hub #1) (rev 01)
00:1d.1 USB Controller: Intel Corp. 82801DB USB (Hub #2) (rev 01)
00:1d.2 USB Controller: Intel Corp. 82801DB USB (Hub #3) (rev 01)
00:1d.7 USB Controller: Intel Corp. 82801DB USB EHCI Controller (rev
01)
00:1e.0 PCI bridge: Intel Corp. 82801BAM/CAM PCI Bridge (rev 81)
00:1f.0 ISA bridge: Intel Corp.: Unknown device 24cc (rev 01)
00:1f.1 IDE interface: Intel Corp.: Unknown device 24ca (rev 01)
00:1f.3 SMBus: Intel Corp. 82801DB SMBus (rev 01)
00:1f.5 Multimedia audio controller: Intel Corp. 82801DB AC'97 Audio
(rev 01)
00:1f.6 Modem: Intel Corp. 82801DB AC'97 Modem (rev 01)
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon
Mobility M7 LW [Radeon Mobility 7500]
02:00.0 CardBus bridge: Texas Instruments PCI1250 PC card Cardbus
Controller (rev 01)
02:00.1 CardBus bridge: Texas Instruments PCI1250 PC card Cardbus
Controller (rev 01)
02:01.0 Ethernet controller: Intel Corp.: Unknown device 101e (rev 03)
02:02.0 Network controller: AIRONET Wireless Communications Cisco
Aironet Wireless 802.11b
Reply With Quote
  #4  
Old 05-24-2004, 02:15 AM
Shanyu Zhao
Guest
 
Posts: n/a
Default Re: How to get my wireless adapter work?

The detail of the output of lspci is:

02:02.0 Network controller: AIRONET Wireless Communications Cisco
Aironet Wireless 802.11b
Subsystem: AIRONET Wireless Communications: Unknown device
5000
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV+ VGASnoop-
ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort-
<MAbort- >SERR- <PERR-
Latency: 64 (1000ns min, 1000ns max), cache line size 08
Interrupt: pin A routed to IRQ 11
Region 0: I/O ports at 8000 [size=256]
Region 1: Memory at c0210000 (32-bit, non-prefetchable)
[size=16K]
Region 2: Memory at c0400000 (32-bit, non-prefetchable)
[size=4M]
Expansion ROM at <unassigned> [disabled] [size=2M]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=2 PME-
Capabilities: [48] Vital Product Data


Should I set something with setpci?


Cameron Kerr <(E-Mail Removed)> wrote in message news:<(E-Mail Removed)>...
> Shanyu Zhao <(E-Mail Removed)> wrote:
>
> > I have a IBM T40 laptop but never got my wireless adapter work in
> > Redhat linux 9.0. I know that my wireless adapter is Cisco Aironet 350
> > Mini-Pci

>
> > The LED for the wireless adapter never lit up.
> >
> > Anyone has experience about this situation? Please help me out.

>
> Please show the output of the following commands as root.
>
> ifconfig
>
> iwconfig
>
> lsmod
>
> lspci

Reply With Quote
  #5  
Old 05-24-2004, 03:21 AM
Cameron Kerr
Guest
 
Posts: n/a
Default Re: How to get my wireless adapter work?

Shanyu Zhao <(E-Mail Removed)> wrote:

>> iwconfig

>
> lo no wireless extensions.
>
> eth0 no wireless extensions.


Hmmm, it would appear that there are no wireless interfaces at all. What
interfaces does 'ifconfig -a' show?

You said you downloaded (, compiled?) and installed "utilities". Can you
please be more specific. Perhaps you installed something you would have
been better to install from a package, rather than by source.

--
Cameron Kerr
(E-Mail Removed) : http://nzgeeks.org/cameron/
Empowered by Perl!
Reply With Quote
  #6  
Old 05-24-2004, 04:47 AM
Marcus Brutus
Guest
 
Posts: n/a
Default Re: How to get my wireless adapter work?

Reply With Quote
  #7  
Old 05-28-2004, 04:58 AM
Shanyu Zhao
Guest
 
Posts: n/a
Default Re: How to get my wireless adapter work?

Now I can get my cisco aironet mini pci card power on but it cannot
get an IP Address through DHCP.

After install the newest driver provided by cisco (v2.1), I should
run:
$ modprobe mpi350
Warning: loading /lib/modules/2.4.20-8/kernel/drivers/net/mpi350.o
will taint the kernel: no license See
http://www.tux.org/lkml/#export-tainted for information about tainted
modules
Module mpi350 loaded, with warnings

That's why I can't config my adapter in the above.

Now the light is on which indicating the wireless adapter is work, and
I can use the utility "acu" to set the SSID and WEP password etc. But
after I configed it, the configuration UI display:
350 series is not associated.
after a little while:
350 series is associated to IP address 0.0.0.0

When I use ifconfig, the wireless adapter is not list unless I run:
$ifconfig eth1 up
now when I use ifconfig I got:
$ifconfig
eth0 Link encap:Ethernet HWaddr 00:09:6B:53:75:11
inet addr:192.168.2.105 Bcast:192.168.2.255
Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:245 errors:0 dropped:0 overruns:0 frame:0
TX packets:294 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:160976 (157.2 Kb) TX bytes:56579 (55.2 Kb)
Interrupt:11 Base address:0x8400 Memory:c0220000-c0240000

eth1 Link encap:Ethernet HWaddr 00:02:8A:9B:09:48
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:11 Base address:0x8000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:3728 errors:0 dropped:0 overruns:0 frame:0
TX packets:3728 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:190352 (185.8 Kb) TX bytes:190352 (185.8 Kb)

When I monitored my access point, it just says it received wireless
connection, but not DHCP requirement.

When I use dhclient to get an IP address for my eth1, I got:
$dhclient eth1
Internet Software Consortium DHCP Client V3.0pl1
Copyright 1995-2001 Internet Software Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

/sbin/dhclient-script: configuration for eth1 not found.
Listening on LPF/eth1/00:02:8a:9b:09:48
Sending on LPF/eth1/00:02:8a:9b:09:48
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 12
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
/sbin/dhclient-script: configuration for eth1 not found.
then it fails.

When using redhat-config-networks I can't see eth1, so I just wondered
where redhat configed eth1. Which config file is in charge of this?

btw, what is the difference between:
ifconfig eth1 up
and
ifup eth1

Anyone can help me out? Thanks a lot!
Reply With Quote
  #8  
Old 06-04-2004, 06:10 AM
DerekM
Guest
 
Posts: n/a
Default Re: How to get my wireless adapter work?

I'm in the same place with very similar symptoms. Have you figured it out yet?



(E-Mail Removed) (Shanyu Zhao) wrote in message news:<(E-Mail Removed). com>...
> Now I can get my cisco aironet mini pci card power on but it cannot
> get an IP Address through DHCP.
>
> After install the newest driver provided by cisco (v2.1), I should
> run:
> $ modprobe mpi350
> Warning: loading /lib/modules/2.4.20-8/kernel/drivers/net/mpi350.o
> will taint the kernel: no license See
> http://www.tux.org/lkml/#export-tainted for information about tainted
> modules
> Module mpi350 loaded, with warnings
>
> That's why I can't config my adapter in the above.
>
> Now the light is on which indicating the wireless adapter is work, and
> I can use the utility "acu" to set the SSID and WEP password etc. But
> after I configed it, the configuration UI display:
> 350 series is not associated.
> after a little while:
> 350 series is associated to IP address 0.0.0.0
>
> When I use ifconfig, the wireless adapter is not list unless I run:
> $ifconfig eth1 up
> now when I use ifconfig I got:
> $ifconfig
> eth0 Link encap:Ethernet HWaddr 00:09:6B:53:75:11
> inet addr:192.168.2.105 Bcast:192.168.2.255
> Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:245 errors:0 dropped:0 overruns:0 frame:0
> TX packets:294 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:160976 (157.2 Kb) TX bytes:56579 (55.2 Kb)
> Interrupt:11 Base address:0x8400 Memory:c0220000-c0240000
>
> eth1 Link encap:Ethernet HWaddr 00:02:8A:9B:09:48
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
> Interrupt:11 Base address:0x8000
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:3728 errors:0 dropped:0 overruns:0 frame:0
> TX packets:3728 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:190352 (185.8 Kb) TX bytes:190352 (185.8 Kb)
>
> When I monitored my access point, it just says it received wireless
> connection, but not DHCP requirement.
>
> When I use dhclient to get an IP address for my eth1, I got:
> $dhclient eth1
> Internet Software Consortium DHCP Client V3.0pl1
> Copyright 1995-2001 Internet Software Consortium.
> All rights reserved.
> For info, please visit http://www.isc.org/products/DHCP
>
> /sbin/dhclient-script: configuration for eth1 not found.
> Listening on LPF/eth1/00:02:8a:9b:09:48
> Sending on LPF/eth1/00:02:8a:9b:09:48
> Sending on Socket/fallback
> DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6
> DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 12
> No DHCPOFFERS received.
> No working leases in persistent database - sleeping.
> /sbin/dhclient-script: configuration for eth1 not found.
> then it fails.
>
> When using redhat-config-networks I can't see eth1, so I just wondered
> where redhat configed eth1. Which config file is in charge of this?
>
> btw, what is the difference between:
> ifconfig eth1 up
> and
> ifup eth1
>
> Anyone can help me out? Thanks a lot!

Reply With Quote
  #9  
Old 06-05-2004, 04:55 AM
DerekM
Guest
 
Posts: n/a
Default Re: How to get my wireless adapter work?

OK,

After a reboot, somehow the mpi350 device automagically showed up in
the hardware list in redhat-config-network. I went through the add
device wizard to add a wireless card, chose another device, manually
configured the IRQ setting, and entered the wireless settings. After
the device is created, you can edit the config to point to the proper
hardware.

the device became active and successfully grabbed an IP address. The
IP doesn't show up in the cisco acu utility, but network functionality
works. I also had to disable the wired device in order to get the
packets sent out of the proper device.



(E-Mail Removed) (DerekM) wrote in message news:<(E-Mail Removed). com>...
> I'm in the same place with very similar symptoms. Have you figured it out yet?
>
>
>
> (E-Mail Removed) (Shanyu Zhao) wrote in message news:<(E-Mail Removed). com>...
> > Now I can get my cisco aironet mini pci card power on but it cannot
> > get an IP Address through DHCP.
> >
> > After install the newest driver provided by cisco (v2.1), I should
> > run:
> > $ modprobe mpi350
> > Warning: loading /lib/modules/2.4.20-8/kernel/drivers/net/mpi350.o
> > will taint the kernel: no license See
> > http://www.tux.org/lkml/#export-tainted for information about tainted
> > modules
> > Module mpi350 loaded, with warnings
> >
> > That's why I can't config my adapter in the above.
> >
> > Now the light is on which indicating the wireless adapter is work, and
> > I can use the utility "acu" to set the SSID and WEP password etc. But
> > after I configed it, the configuration UI display:
> > 350 series is not associated.
> > after a little while:
> > 350 series is associated to IP address 0.0.0.0
> >
> > When I use ifconfig, the wireless adapter is not list unless I run:
> > $ifconfig eth1 up
> > now when I use ifconfig I got:
> > $ifconfig
> > eth0 Link encap:Ethernet HWaddr 00:09:6B:53:75:11
> > inet addr:192.168.2.105 Bcast:192.168.2.255
> > Mask:255.255.255.0
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:245 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:294 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:100
> > RX bytes:160976 (157.2 Kb) TX bytes:56579 (55.2 Kb)
> > Interrupt:11 Base address:0x8400 Memory:c0220000-c0240000
> >
> > eth1 Link encap:Ethernet HWaddr 00:02:8A:9B:09:48
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:100
> > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
> > Interrupt:11 Base address:0x8000
> >
> > lo Link encap:Local Loopback
> > inet addr:127.0.0.1 Mask:255.0.0.0
> > UP LOOPBACK RUNNING MTU:16436 Metric:1
> > RX packets:3728 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:3728 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:190352 (185.8 Kb) TX bytes:190352 (185.8 Kb)
> >
> > When I monitored my access point, it just says it received wireless
> > connection, but not DHCP requirement.
> >
> > When I use dhclient to get an IP address for my eth1, I got:
> > $dhclient eth1
> > Internet Software Consortium DHCP Client V3.0pl1
> > Copyright 1995-2001 Internet Software Consortium.
> > All rights reserved.
> > For info, please visit http://www.isc.org/products/DHCP
> >
> > /sbin/dhclient-script: configuration for eth1 not found.
> > Listening on LPF/eth1/00:02:8a:9b:09:48
> > Sending on LPF/eth1/00:02:8a:9b:09:48
> > Sending on Socket/fallback
> > DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6
> > DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 12
> > No DHCPOFFERS received.
> > No working leases in persistent database - sleeping.
> > /sbin/dhclient-script: configuration for eth1 not found.
> > then it fails.
> >
> > When using redhat-config-networks I can't see eth1, so I just wondered
> > where redhat configed eth1. Which config file is in charge of this?
> >
> > btw, what is the difference between:
> > ifconfig eth1 up
> > and
> > ifup eth1
> >
> > Anyone can help me out? Thanks a lot!

Reply With Quote
  #10  
Old 06-06-2004, 01:34 AM
Hactar
Guest
 
Posts: n/a
Default Re: How to get my wireless adapter work?

In article <(E-Mail Removed) >,
DerekM <(E-Mail Removed)> wrote:
> After a reboot, somehow the mpi350 device automagically showed up in
> the hardware list in redhat-config-network. I went through the add
> device wizard to add a wireless card, chose another device, manually
> configured the IRQ setting, and entered the wireless settings. After
> the device is created, you can edit the config to point to the proper
> hardware.
>
> the device became active and successfully grabbed an IP address. The
> IP doesn't show up in the cisco acu utility, but network functionality
> works. I also had to disable the wired device in order to get the
> packets sent out of the proper device.


I have a Thinkpad T40 also, and your posts were the proof that 'it can work'
that I needed to junk XP and install Linux on it. (I really need
networking; I would use wired, but my location makes it infeasible, and at
school it has to be wireless.)

I have the Knoppix 3.4 CD, which can load either kernel 2.4.26 or
2.6.something. Under 2.6, it should be safe to mount hda1 (NTFS) rw,
correct? Also, do you know of anything that'll change this:

hda1
|_____________|
|-------------------|
hda

to this:

hda1 hda2
|______|______|
|-------------------|
hda

? That last bit (that's not in a partition) is where IBM keep their recovery
info, in case I want to return the drive to stock. If I can't do that, I
guess I'll trash XP.

--
-eben (E-Mail Removed)m home.tampabay.rr.com/hactar
SAGITTARIUS: All your friends are laughing behind your back... kill
them. Take down all those naked pictures of Ernest Borgnine you've got
hanging in your den. -- Weird Al, _Your Horoscope for Today_
Reply With Quote
Reply

Tags
adapter, wireless, work

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT. The time now is 03:58 PM.


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.