Hi,
I complied the kernel buitin broadcom drivers. So now, I have a interface
named "wlan0_rename".
But things are still not working for me.
------------------------------------------------------------------------------------
flukebox flukebox # iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
sit0 no wireless extensions.
ip6tnl0 no wireless extensions.
eth1 no wireless extensions.
wlan0_rename IEEE 802.11g ESSID:""
Mode:Managed Channel:0 Access Point: Not-Associated
Tx-Power=0 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Encryption key:off
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
flukebox flukebox # /etc/init.d/net.wlan0_rename start
* Starting wlan0_rename
* /etc/conf.d/wireless is deprecated
* Please put all settings in /etc/conf.d/net
* /etc/conf.d/wireless is deprecated
* Please put all settings in /etc/conf.d/net
* Starting wpa_supplicant on wlan0_rename ...
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not
supported [
ok ]th param 5 value 0x1 -
* Starting wpa_cli on wlan0_rename
...
[ ok ]
* Backgrounding ...
------------------------------------------------------------------------------------
I guess "param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported "
this has something to do with wpa_suplicant.
can somebody help me out here ??
Also, is there any way to change my interface name wlan0_rename to wlan0 or
eth1 ??
TIA,
flukebox
On Feb 10, 2008 3:17 AM, Dan Farrell <[EMAIL PROTECTED]> wrote:
> On Sat, 9 Feb 2008 13:28:39 +0100
> Etaoin Shrdlu <[EMAIL PROTECTED]> wrote:
>
> > > BTW,
> > > I am more interested to get things working. Quality would be my
> > > second priority.
> >
> > As I said before, I did not have any problem (unfortunately, I cannot
> > access the hardware now and check the bandwidth issue).
>
> I have not yet gotten the new driver to work, though admittedly I
> didn't have much time to try and so went for ndiswrapper pretty
> quickly.
>
> has anyone had luck with this driver recently?
> --
> [email protected] mailing list
>
>
