[driverloader] Linksys WMP54g troubles in redhat 9

Dobes Vandermeer dobes at dobesland.com
Wed Nov 5 03:56:20 EST 2003


Yay!

I seem to have gotten it working.  The idea of messing with the AP
settings never occurred to me -- I thought "hell, if winXP can access it
then its accessible".  Anyhow, I changed the Ap from G-only to mixed
mode wireless and it seems to be working great.  I'd set it to G-only
because that seemed to fix some reception problems I was having with
windows XP before, but its running fast now so hopefully those problems
wont come back.  I even managed to re-enable the WEP key and disable
SSID broadcast.

Also I discovered that the card doesn't always seem to honor the
iwconfig commands I sent it, so I couldn't tell right away if a change
had broken or fixed the card.  It seems like your best bet is to make
one change, reboot, make another change, reboot, otherwise your test
isn't necessarily going to pass/fail as it should.

I'll keep you updated if things start to go awry again.

Thanks!
Dobes

On Tue, 2003-11-04 at 04:19, Linuxant support wrote:
> Hi,
> 
> can you try with the WEP key disabled?
> 
> Also, if possible, reset your AP's configuration and use the detault
> settings for the interface under Linux to see if it can attach.
> 
> Regards,
> 
> Jean-Simon Durand
> Technical specialist / Linuxant
> www.linuxant.com
> support at linuxant.com
> 
> 
> ----- Original Message ----- 
> From: "Dobes Vandermeer" <dobes at dobesland.com>
> To: <driverloader at lists.linuxant.com>
> Sent: Tuesday, November 04, 2003 1:26 AM
> Subject: [driverloader] Linksys WMP54g troubles in redhat 9
> 
> 
> 
> Hello,
> 
> I am having some of the same problems I've seen posted on the list, but
> none of the solutions have helped for me.
> 
> My main symptom seems to be this:
> 
> [root at menfin network-scripts]# ifup eth0
> 
> Determining IP information for eth0... failed.
> 
> The diagnosis file reveals that I am able to scan my network
> (dobesland).
> 
> If I attempt to join the network using
> iwconfig eth0 essid "dobesland"
> iwconfig
> 
> eth0      IEEE 802.11-DS  ESSID:""  Nickname:"menfin.localdomain"
>           Mode:Managed  Bit Rate=54Mb/s   Tx-Power=16 dBm
>           RTS thr:off   Fragment thr:off
>           Encryption key:XXXX-XXXX-XX   Encryption mode:open
>           Power Management:off
>           Link Quality:1/1  Signal level:-10 dBm  Noise level:-81 dBm
>           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>           Tx excessive retries:0  Invalid misc:0   Missed beacon:0
> 
> It returns no error but iwconfig will show "" as the essid afterwards.
> On the other hand:
> 
> iwconfig eth0 essid "any"
> iwconfig
> 
> will join a network -- but not mine!  It joins some other network in my
> building and I still can't dhcp.  This is what I get:
> 
> eth0      IEEE 802.11-DS  ESSID:"default"  Nickname:"menfin.localdomain"
>           Mode:Managed  Access Point: 00:80:C8:03:08:22  Bit Rate=11Mb/s
>           Tx-Power=14 dBm
>           RTS thr:off   Fragment thr:off
>           Encryption key:XXXX-XXXX-XX   Encryption mode:open
>           Power Management:off
>           Link Quality:1/1  Signal level:-78 dBm  Noise level:-40 dBm
>           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>           Tx excessive retries:0  Invalid misc:0   Missed beacon:0
> 
> Also, as with another post, my USB driver was sharing IRQ 5 with
> driverloader; I disabled USB in the BIOS and although the USB drivers
> failed to load the wireless network card still wont configure.
> 
> Help!
> 
> Thanks,
> Dobes
> 


More information about the driverloader mailing list