linux-kernel - Re: [PATCH 3/3] net: wireless: bcm43xx: big_buffer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200712140143.16451.mb@bu3sch.de>
Date:	Fri, 14 Dec 2007 01:43:15 +0100
From:	Michael Buesch <mb@...sch.de>
To:	"Ray Lee" <ray-lk@...rabbit.org>
Cc:	bcm43xx-dev@...ts.berlios.de, "Daniel Walker" <dwalker@...sta.com>,
	akpm@...ux-foundation.org, mingo@...e.hu,
	linux-kernel@...r.kernel.org, linux@...mer.net,
	jonathan@...masters.org, matthias.kaehlcke@...il.com,
	kjwinchester@...il.com, mbuesch@...enet.de,
	"John Linville" <linville@...driver.com>
Subject: Re: [PATCH 3/3] net: wireless: bcm43xx: big_buffer_sem semaphore to mutex

On Friday 14 December 2007 01:05:00 Ray Lee wrote:
> Okay, I had to modprobe rfkill-input and rfkill by hand, didn't
> realize that. Hopefully that'll be automatic soon. Regardless, upon
> doing so, and loading ssb and b43, it sees my card, but is still not
> fully functional. iwconfig sees:
> 
> lo        no wireless extensions.
> eth0      no wireless extensions.
> tun0      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
>           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
> 
> (eth0 is ethernet, eth1 doesn't exist -- usually it's the wireless.)
> 
> `ifconfig` doesn't see eth1 or wlan0_rename.
> 
> What else might I be doing wrong?

I don't know. Try ifconfig -a
Or tell udev to not crap up your device names.

> Regardless, perhaps scheduling 
> bcm43xx for removal in 2.6.26 is a bit premature.

Oh come on. b43 is more than a year old now. How long should we wait?
Two or three? Forever?

-- 
Greetings Michael.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/