I can't connect to my wireless AP in FC5, why am I unable to activate my wireless.

ruggersway · 05-07-2006, 10:24 PM

Here is as much of my config as I can think to offer, if there is anything else that would help let me know and I'll provide it.

kernel
[root@localhost ~]# uname -r
2.6.16-1.2111_FC5
(with this kernel I was able to successfully install ndiswrapper and add the windows driver which I then uninstalled when I realized my card used a PRISM chipset)

lspci yields
00:0b.0 Network controller: Intersil Corporation ISL3890 [Prism GT/Prism Duette] (rev 01)

in network manager this only lists modes to 11Mbps, my wireless is 54Mbps is it recognizing incorrectly or the wrong prism driver? An internet search tells me I have XG600 miniPCI wireless, which uses PRISM GT chipset.

[root@localhost ~]# iwconfig
lo no wireless extensions.

eth0 NOT READY! ESSID

ff/any
Mode:Managed Channel:0 Access Point: Not-Associated
Tx-Power=31 dBm Sensitivity=0/200
Retry min limit:0 RTS thr=0 B Fragment thr=0 B
Encryption key

ff
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

eth1 no wireless extensions.

sit0 no wireless extensions.

I've tried manually setting ESSID through iwconfig, also through Network Configuration gui as well as the other wireless settings. I get
Error for wireless request "Set Bit Rate" (8B20) :
SET failed on device eth0 ; Input/output error.
when I "ifup eth0".

I'm not sure what else to try here. I've tried manually entering all the information for my AP and still get nothing. I've search through lots of forums and am probably just missing what I am looking for, I'd appreciate it if someone could walk me through this. Thanks.

leosgb · 05-09-2006, 03:58 PM

Well the "eth0 NOT READY!" message there when you run iwconfig means there is something wrong w/ the driver you are using. Maybe you could switch back to ndiwsrapper and windows drivers and test to see if it works. Maybe your device is not supported by the prism driver. Try that for now, if it works you shouldnt worry about using the "total linux" solution, ie, the prism driver, ok? I use the windows drivers for my intel wireless and it works perfectly well. Good luck!