[driverloader] Now for the real problems...

Linuxant support (Jean-Simon) support at linuxant.com
Fri Feb 13 11:01:02 EST 2004


you seem to have put your interface configuration in
'/etc/sysconfig/network-scripts/ifcfg-wlan0'. However, your interface is
currently named "eth1". You may use the command "dldrconfig --netdevname
wlan0" to change the interface name. You will probably want to remove the
file '/etc/sysconfig/network-scripts/ifcfg-eth1' after.

Also, you should remove or comment the "CHANNEL" and "FREQ" settings in your
interface configuration file and it's generaly better to set the mode to
"Managed" instead of "Auto".

Make sure that you try with WEP disabled on your AP and your wi-fi adapter.
If possible, you should reset your AP's configuration to it's default and
test without putting any special settings (MAC address filtering, disabled
ESSID braodcast, WEP, etc.) Sometimes, it is even required to upgrade the
AP's firmware.

Since your AP does not appear in the output from "iwlist scan", it would be
a good idea to make sure everything works properly under Windows. Note if
you need to do anything special to enable the antenna. Also, you should
verify in your BIOS if there is a setting related to the wi-fi adapter.


Technical specialist / Linuxant
support at linuxant.com

----- Original Message ----- 
From: "Al Niessner" <al.niessner at gmx.net>
To: "Linuxant support (Jonathan)" <support at linuxant.com>
Sent: Thursday, February 12, 2004 12:55 PM
Subject: Re: [driverloader] Now for the real problems...

ACPI is off as is the APIC because the kernel was very unhappy with them on.
I turned of WEP and had the same problem. The drivers (from bcmwl5a.inf) are The diagnostic output is attached. You will notice when you read
through it that I have an AMD64 that I have Mandrake 9.2 i586 running on. I
wanted to solve these problems first before attempting the 64-bit case which
is going to be much harder since the module will have to handle the 32/64
as well as the Linux/Winblows transition. Thank you for the help, however.

More information about the driverloader mailing list