Hello there,

I am a Linux newb, trying to get my wireless adapter work in Fedore Core3 on my Laptop. This is Compaq 2164AF (Presario 2100) Intel Pentium 4M 2.4 GHz processor and I am using Linksys WPC54G wireless card. My machine is a dual-boot notebook with Windoxs XP Professional as the default boot operating system.

I have installed NDISWRAPPER 1.2 and attempted to get the interface wlan0 constructed, after installing the driver lsbcmnds.inf, with the help of ndiswrapper -m and dhcpd commands. but wlan0 was not recognized by /sbin/iwconfig. However, I observed this too:

Ever since I started messing with Networking in Fedora Core 3, I saw eth1 as the interface showing the networking features seen from iwconfig command:

prompt%>/sbin/iwconfig eth1

eth1 IEEE 802.11-DS ESSID:"Linksys" Nickname:"localhost.localdomain"
Mode:Managed Frequency:2.457GHz Access Point: 44:44:44:44:44:44
Bit Rate=2Mb/s Tx-Power=15 dBm Sensitivity:1/3
Retry min limit:8 RTS thrff Fragment thrff
Encryption keyff
Power Managementff
Link Quality=0/92 Signal level=-68 dBm Noise level=-122 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Also I have seen dmesg printing following info about eth1:

dmesg includes following lines

eth1: Station identity 001f:0009:0001:0004
eth1: Looks like an Intersil firmware version 1.4.9
eth1: Ad-hoc demo mode supported
eth1: IEEE standard IBSS ad-hoc mode supported
eth1: WEP supported, 104-bit key
eth1: MAC address 00:02:8A:B6:AA:0B
eth1: Station name "Prism I"
eth1: ready


Problem: The wireless card is not working.
Question: What am I missing in the sequence?

Any insight please.....

Regards,
Moodamultani

Further to my query:

/sbin/iwlist eth1 ap has resulted in eth1 Interface not having any list of Peers/Access Points.

Thanks,
Moodamultani

I'm having a similar problem in FC3, with the latest CVS build. In my case,
I can't use iwpriv because it causes a kernel page fault that can't be satisfied.
When iwlist or iwconfig doesn't show the AP it means that the system hasn't
successfully made the connection.

One thing I am looking at is signal strength; it seems as though "sometimes it
works and sometimes it doesn't". Of course, that was in FC1. The FC3 rt2500
drivers (latest CVS build for 6/29/2005 and the 1.1.0-b2) both exhibit this behavior
with iwpriv.

Has anyone else seen this behavior ?