[driverloader] Now for the real problems...
Linuxant support (Jonathan)
support at linuxant.com
Mon Feb 16 18:33:07 EST 2004
please make sure that your access point broadcast it's ESSID and also make
sure that MAC address filtering is off. It is also important that the access
point channel should be between 1 and 11. As long as your access point
doesn't show up in the output of 'iwlist scanning' you won't be able to
Technical specialist / Linuxant
support at linuxant.com
On Saturday 14 February 2004 15:45, you wrote:
> ifcfg-wlan0 is just a place holder that never gets started -- it is a
> backup of how I think the wireless should be configured. There is also
> an ifcfg-eth1 which matched the alias in modules.conf (given below)
> alias eth0 via-rhine
> probeall usb-interface usb-uhci
> probeall scsi_hostadapter ide-scsi
> above snd-via82xx snd-pcm-oss
> alias sound-slot-0 snd-via82xx
> alias eth1 driverloader
> When I want to test the wireless, I do an 'ifup eth1' so I really think
> it is safe to leave ifcfg-wlan0 alone.
> ifcfg-eth1 has its WEP turned off and I have turned off WEP on the AP.
> I removed the FREQ and CHANNEL settings in the ifcfg-eth1. No changes
> when attempting to use wireless.
> Lastly, all works well from XP. In XP, I hit Fn-F2 and a little light
> comes on indicating that the RF is active. When I press Fn-F2 in Linux,
> the same light goes and the kernel CPU usage soars to 70-100%. So,
> something is happening. Just not the right something.
> What I really need is an RF spectrum analyzer to see if the card is
> really becoming active and at what frequency.
> On Fri, 2004-02-13 at 08:01, Linuxant support (Jean-Simon) wrote:
> > Hi,
> > 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.
> > Regards,
> > Jean-Simon
> > Technical specialist / Linuxant
> > www.linuxant.com
> > 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 184.108.40.206. 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 bit
> > as well as the Linux/Winblows transition. Thank you for the help,
> > however.
More information about the driverloader