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: <4761E5D6.7040801@lwfinger.net>
Date:	Thu, 13 Dec 2007 18:09:26 -0800
From:	Larry Finger <larry.finger@...inger.net>
To:	Michael Buesch <mb@...sch.de>
CC:	Ray Lee <ray-lk@...rabbit.org>, Daniel Walker <dwalker@...sta.com>,
	matthias.kaehlcke@...il.com, mbuesch@...enet.de,
	linux-kernel@...r.kernel.org, bcm43xx-dev@...ts.berlios.de,
	linux@...mer.net, kjwinchester@...il.com, jonathan@...masters.org,
	akpm@...ux-foundation.org, mingo@...e.hu
Subject: Re: [PATCH 3/3] net: wireless: bcm43xx: big_buffer_sem semaphore
 to	mutex

Michael Buesch wrote:
> 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?

Your udev rules are screwed up. In /etc/udev/rules.d/70-persistent-net.rules, you should have a line 
that looks like

SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:1a:73:6b:28:5a", ATTR{type}=="1", NAME="eth1"

with the MAC address for your device. You probably have the ATTR{type}=="1" clause missing.

Larry
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ