I’ve trying to connect to wireless network with no luck. I have a 64bit HP desktop with a wireless card “Linksys Wireless-G PCI Adapter (WMP54G)”
The output of the command dmesg | less showed a lot of firmware issues so I installed NDISwrapper, I installed the XP drive (i actually tried two different) with no luck.
Here is the output of some commands
/sbin/lspci
03:08.0 Network controller: RaLink RT2561/RT61 802.11g PCI
Subsystem: Linksys WMP54G ver 4.1
Flags: bus master, slow devsel, latency 32, IRQ 16
Memory at fddf0000 (32-bit, non-prefetchable) [size=32]
Capabilities: <access denied>
Kernel driver in use: rt61pci
Kernel modules: rt61pci
At this point I wonder if <access denied> has something to do with my problem.
/bin/lspci -n
03:08.0 0280: 1814:0301
After installing NDISwrapper and the driver, the firware messages were gone!
dmesg | less
ACPI: PCI Interrupt 0000:03:08.0[A] -> Link [APC1] -> GSI 16 (level, low) -> IRQ 16
phy0: Selected rate control algorithm ‘pid’
Adding 2104472k swap on /dev/sda1. Priority:-1 extents:1 across:2104472k
/usr/sbin/iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wmaster0 no wireless extensions.
wlan0 IEEE 802.11g ESSID:""
Mode:Managed Channel:0 Access Point: Not-Associated
Tx-Power=0 dBm
Retry min limit:7 RTS thr: off Fragment thr=2352 B
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
At the bottom left of the screen, there are two PCs with a red X on it, if I right click “wireless networks” appears shaded out so I tried /usr/sbin/iwlist scan and…
lo Interface doesn’t support scanning.
eth0 Interface doesn’t support scanning.
wmaster0 Interface doesn’t support scanning.
wlan0 Interface doesn’t support scanning : Network is down
My network card is activated “at boot”, but it doesn’t show up in YaST under Hardware of Network Services. So far I can only think of: the card is not supported yet by kernel, there is some kind of problem with the 64bit version o there is another firmware problem.[/size]