Finally got around top putting F7 on my lappy & need a radio
Gene Heskett
gene.heskett at verizon.net
Mon Jun 4 13:25:48 UTC 2007
I'm sorry but I'm going to abuse at least 2 people and a mailing list.
But I'm at the end of my rope and losing my grip on this.
On Sunday 03 June 2007, Sebastian Gottschall wrote:
>Gene Heskett schrieb:
>> On Sunday 03 June 2007, Sebastian Gottschall wrote:
>>> Gene Heskett schrieb:
>>>> On Sunday 03 June 2007, Sebastian Gottschall wrote:
>>>>>> Yes, and I have used it before. The light at the far end of the
>>>>>> tunnel that is on coming is that I'm not using the stuff in
>>>>>> /lib/firmware at all when I'm using bcm43xx_mac80211?
>>>>>>
>>>>>> This might explain much.
>>>>>
>>>>> this explains everything. the broadcom card wont work if the firmware
>>>>> isnt loaded.
Re the code you sent: I haven't done any more yet with that code, and
probably won't when its so booby-trapped.
However, I have that lappy booted to its XP install ATM, and while it
sees the ESSID of both the card in the dd-wrt, and the neighbors too,
it cannot connect, and according to the log of dd-wrt, it never gets
as far as a DCHPREQUEST. So I still think a major part of the problem
is that dd-wrt isn't even accepting any incoming packets from ath0.
I'm looking at the properties of it under windows, and its using
BCMWL5.SYS as a driver, version 4.10.40.1. It also says the device is
working properly.
IRQ=21, memory range C024000-C025FFF.
I just now restricted both dd-wrt and the lappy to 11mbs. A new connection
attempt isn't being logged by dd-wrt when I tell it to connect. I have even
re-entered the wep key several times in the windows requester.
I don't think its transmitting even under windows as I've triggered a scan on
my sniffer several times while windows says its trying to connect without it
showing up. I _think_ I'm seeing the beacon from the dd-wrt. Only thing I
can do to confirm that is to turn it off. Which I just did, and no signals
were detected while windows was attempting a connection.
So I'm going to clean up and take the lappy to where I bought it, along with
a 3 year warranty, and see if they can make it work.
But before that, I rebooted it back to f7, and did an rmmod on ndiswrapper,
which was not showing any users in the lsmod list, renamed the bcm43xx and
mac80211 directories in /lib/modules to be correct, then did a
modprobe bcm43xx, and that loaded a totally different set of drivers!
[root at diablo ~]# lsmod|grep 80211
ieee80211softmac 35137 1 bcm43xx
ieee80211 35081 2 bcm43xx,ieee80211softmac
ieee80211_crypt 10049 1 ieee80211
mac80211 136005 0
cfg80211 12105 1 mac80211
But an ifup wlan0 still fails, but leaves the led on. A second attempt turns
it off instantly. I presume I could re-enable it by rmmoding that list and
modprobing bcm43xx would re-enable, but having done that dozens of times over
the last few days, why bother.
Rebooted again after renaming that stuff so it can find it during the bootup,
and I get the original modules loaded, which are:
[root at diablo ~]# lsmod|grep 80211
bcm43xx_mac80211 397857 0
ssb 35012 1 bcm43xx_mac80211
mac80211 136005 1 bcm43xx_mac80211
cfg80211 12105 1 mac80211
So which 'set' of these am I supposed to be running?
Humm, bcm43xx_mac80211 is still in the blacklist too. And that's confusing
too, the instuctions at the top of that file says the module name alone on
a line, but every module listed in that file has the word 'blacklist' in
front of it, so each line is 2 words. Hello right hand? Meet left hand.
Somebody needs to clarify that.
And I just found that ndiswrapper was loaded, and rmmod'ing it turned the
radio off, fixed that line in modprobe.conf and reboot again and it _should_
be back to stock F7 stuffs. Rebooted again.
And its already turned the radio off & the boot is hung till dhclient times
out.
And its loaded yet another configuration of modules:
rc80211_simple 8257 1
bcm43xx_mac80211 397857 0
ssb 35012 1 bcm43xx_mac80211
8139too 29249 0
mac80211 136005 2 rc80211_simple,bcm43xx_mac80211
Can anyone on the fedora list tell me what the hell is going on here?
Mmm, microcode missing, and indeed it is, I'd forgotten I'd cleaned that
tree out when I tried to install ndiswrapper. And, ndiswrapper wants to
get its files from bcmwl5.inf, whereas bcm43xx-fwcutter wants to get them
from BCMWL5.SYS. Dunno if they co-exist peacefully. I just redid the
"bcm43xx-fwcutter -w /lib/firmware BCMWL5.SYS", and rebooted.
What I do see is that both set mode and set rate are invalid options
according to whatever is trying to bring up wlan0 during the boot.
If I set mode=Managed that's legal, but no rate= is legal according to
iwconfig.
The avahi-daemon, and all the NetworkManager stuff is turned off. I have
more than enough troubles here without some silent butler second guessing
me.
And NOW its back to original.
Complete with these messages, which were generated when I ran the script listed below:
Jun 4 08:49:37 diablo kernel: ACPI: PCI interrupt for device 0000:06:02.0 disabled
Jun 4 08:49:38 diablo kernel: ACPI: PCI Interrupt 0000:06:02.0[A] -> GSI 21 (level, low) -> IRQ 22
Jun 4 08:49:38 diablo kernel: ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x0D, vendor 0x4243)
Jun 4 08:49:38 diablo kernel: ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x09, vendor 0x4243)
Jun 4 08:49:38 diablo kernel: ssb: Core 2 found: PCI (cc 0x804, rev 0x0C, vendor 0x4243)
Jun 4 08:49:38 diablo kernel: ssb: Core 3 found: PCMCIA (cc 0x80D, rev 0x07, vendor 0x4243)
Jun 4 08:49:38 diablo kernel: ssb: Switching to ChipCommon core, index 0
Jun 4 08:49:38 diablo kernel: ssb: Switching to PCI core, index 2
Jun 4 08:49:38 diablo kernel: ssb: Sonics Silicon Backplane found on PCI device 0000:06:02.0
Jun 4 08:49:38 diablo kernel: bcm43xx_mac80211: Broadcom 4318 WLAN found
Jun 4 08:49:38 diablo kernel: ssb: Switching to IEEE 802.11 core, index 1
Jun 4 08:49:38 diablo kernel: bcm43xx_mac80211: Found PHY: Analog 3, Type 2, Revision 7
Jun 4 08:49:38 diablo kernel: bcm43xx_mac80211: Found Radio: Manuf 0x17F, Version 0x2050, Revision 8
Jun 4 08:49:38 diablo kernel: bcm43xx_mac80211: Radio turned off
Jun 4 08:49:39 diablo kernel: bcm43xx_mac80211: Adding Interface type 2
Jun 4 08:49:39 diablo kernel: ssb: Switching to PCI core, index 2
Jun 4 08:49:39 diablo kernel: ssb: Switching to IEEE 802.11 core, index 1
Jun 4 08:49:39 diablo kernel: ssb: Switching to ChipCommon core, index 0
Jun 4 08:49:39 diablo kernel: ssb: Switching to IEEE 802.11 core, index 1
Jun 4 08:49:39 diablo kernel: bcm43xx_mac80211: Radio turned on
Jun 4 08:49:39 diablo kernel: bcm43xx_mac80211: Radio enabled by hardware
Jun 4 08:49:39 diablo kernel: bcm43xx_mac80211: !WARNING! Idle-TSSI phy->cur_idle_tssi measuring failed. (cur=0, tgt=62). Disabling TX power adjustment.
Jun 4 08:49:39 diablo kernel: bcm43xx_mac80211: Chip initialized
Jun 4 08:49:39 diablo kernel: bcm43xx_mac80211: 32-bit DMA initialized
Jun 4 08:49:39 diablo kernel: bcm43xx_mac80211: Wireless interface started
Jun 4 08:49:39 diablo kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jun 4 08:49:39 diablo dhclient: wmaster0: unknown hardware address type 801
Jun 4 08:49:39 diablo dhclient: dhclient(5491) is already running - exiting.
Jun 4 08:49:39 diablo dhclient:
Jun 4 08:49:39 diablo dhclient: This version of ISC DHCP is based on the release available
Jun 4 08:49:39 diablo dhclient: on ftp.isc.org. Features have been added and other changes
Jun 4 08:49:39 diablo dhclient: have been made to the base software release in order to make
Jun 4 08:49:39 diablo dhclient: it work better with this distribution.
Jun 4 08:49:39 diablo dhclient:
Jun 4 08:49:39 diablo dhclient: Please report for this software via the Red Hat Bugzilla site:
Jun 4 08:49:39 diablo dhclient: http://bugzilla.redhat.com
Jun 4 08:49:39 diablo dhclient:
Jun 4 08:49:39 diablo dhclient: exiting.
Jun 4 08:49:39 diablo dhclient: wmaster0: unknown hardware address type 801
Jun 4 08:49:39 diablo dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jun 4 08:49:39 diablo dhclient: dhclient(5491) is already running - exiting.
Jun 4 08:49:39 diablo dhclient:
Jun 4 08:49:39 diablo dhclient: This version of ISC DHCP is based on the release available
Jun 4 08:49:39 diablo dhclient: on ftp.isc.org. Features have been added and other changes
Jun 4 08:49:39 diablo dhclient: have been made to the base software release in order to make
Jun 4 08:49:39 diablo dhclient: it work better with this distribution.
Jun 4 08:49:39 diablo dhclient:
Jun 4 08:49:39 diablo dhclient: Please report for this software via the Red Hat Bugzilla site:
Jun 4 08:49:39 diablo dhclient: http://bugzilla.redhat.com
Jun 4 08:49:39 diablo dhclient:
Jun 4 08:49:39 diablo dhclient: exiting.
Jun 4 08:49:40 diablo kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Jun 4 08:49:43 diablo dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jun 4 08:49:47 diablo dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jun 4 08:49:54 diablo dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
Jun 4 08:49:58 diablo dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
Jun 4 08:50:04 diablo dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Jun 4 08:50:09 diablo ntpd[2500]: Listening on interface #7 wlan0, fe80::214:a5ff:fe75:32c9#123 Enabled
Jun 4 08:50:12 diablo dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
Jun 4 08:50:15 diablo dhclient: No DHCPOFFERS received.
Jun 4 08:50:15 diablo dhclient: Trying recorded lease 192.168.71.129
Jun 4 08:50:18 diablo kernel: bcm43xx_mac80211: Removing Interface type 2
Jun 4 08:50:18 diablo kernel: bcm43xx_mac80211: Wireless interface stopped
Jun 4 08:50:18 diablo kernel: bcm43xx_mac80211: DMA-32 0x0200 (RX) max used slots: 1/64
Jun 4 08:50:18 diablo kernel: bcm43xx_mac80211: DMA-32 0x02A0 (TX) max used slots: 0/128
Jun 4 08:50:18 diablo kernel: bcm43xx_mac80211: DMA-32 0x0280 (TX) max used slots: 0/128
Jun 4 08:50:18 diablo kernel: bcm43xx_mac80211: DMA-32 0x0260 (TX) max used slots: 0/128
Jun 4 08:50:18 diablo kernel: bcm43xx_mac80211: DMA-32 0x0240 (TX) max used slots: 0/128
Jun 4 08:50:18 diablo kernel: bcm43xx_mac80211: DMA-32 0x0220 (TX) max used slots: 22/128
Jun 4 08:50:18 diablo kernel: bcm43xx_mac80211: DMA-32 0x0200 (TX) max used slots: 0/128
Jun 4 08:50:18 diablo kernel: bcm43xx_mac80211: Radio turned off
Jun 4 08:50:18 diablo kernel: ssb: Switching to ChipCommon core, index 0
Jun 4 08:50:18 diablo kernel: ssb: Switching to IEEE 802.11 core, index 1
Jun 4 08:50:18 diablo kernel: bcm43xx_mac80211: Radio turned off
Whoinhell is wmaster0?
===========the script===========
#!/bin/bash
ifdown wlan0
echo interface down, removing driver
rmmod bcm43xx_mac80211 rc80211_simple ssb mac80211
echo drivers removed, now killing dhclient with a killall
killall dhclient
echo dhclient killed now modprobing bcm43xx_mac80211
modprobe bcm43xx_mac80211
lsmod |grep 80211
echo done now ifup wlan0
ifup wlan0
============
which may not be correct, but is the best I can do without 100's of reboots,
and at 72, I'd, like to get this working within my remaining lifetime. If
someone can improve on it, I'm all eyes to read any corrections.
Using kwifimanager, I changed the mode to Master thinking that might
bring up a beacon I can sniff, but a connection attempt turned the radio
off instantly. Now a scan for networks using that tool shows 4 of them,
with 2 of them below 10% quality, but doesn't show the "mode" of operation
for any of them. In that regard, I believe kwifimanager is broken.
>which linux distro do you use?
Fedora 7.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Alimony is the high cost of leaving.
More information about the fedora-list
mailing list