Re: bcm4318 in an HP dv5120us lappy

2007-06-04 Thread John W. Linville
On Sun, Jun 03, 2007 at 05:04:18PM -0500, Larry Finger wrote:
> John W. Linville wrote:
> >On Sat, Jun 02, 2007 at 01:39:25PM -0500, Larry Finger wrote:
> >
> >>I can only guess at why FC 7 uses the mac80211 driver.
> >
> >To wean people off of softmac's teat...
> >
> 
> That was my guess...

I just posted this to fedora-list:

https://www.redhat.com/archives/fedora-list/2007-June/msg01009.html

Hopefully that will help -- please let me know if there is anything
wrong or unclear about the info there.

Thanks,

John
-- 
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev


Re: bcm4318 in an HP dv5120us lappy

2007-06-03 Thread Larry Finger
John W. Linville wrote:
> On Sat, Jun 02, 2007 at 01:39:25PM -0500, Larry Finger wrote:
> 
>> I can only guess at why FC 7 uses the mac80211 driver.
> 
> To wean people off of softmac's teat...
> 

That was my guess...

Larry

___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev


Re: bcm4318 in an HP dv5120us lappy

2007-06-03 Thread John W. Linville
On Sat, Jun 02, 2007 at 01:39:25PM -0500, Larry Finger wrote:

> I can only guess at why FC 7 uses the mac80211 driver.

To wean people off of softmac's teat...

-- 
John W. Linville
[EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev


Re: bcm4318 in an HP dv5120us lappy

2007-06-02 Thread Larry Finger
Gene Heskett wrote:
> On Saturday 02 June 2007, Larry Finger wrote:
> 
> wlan0 IEEE 802.11g  ESSID:"ICECAP4NIGHTCAP"
>   Mode:Managed  Frequency:2.442 GHz  Access Point: 00:12:0E:12:68:D5
>   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

The MAC address is the address of the AP that it associated with. It is Cell 02 
below.

> But that AP mac address is NOT the wap11.  It should be, unless that's the 
> mac 
> of the broadcom in this lappy, 00:05:5D:F8:8D:68
> 
>> and 'iwlist scan' commands to see if your 
>> interface shows up, and if it is seeing any signals.
> 
> [EMAIL PROTECTED] network-scripts]# iwlist wlan0 scan
> wlan0 Scan completed :
>   Cell 01 - Address: 00:12:0E:5A:41:ED
> ESSID:"06B411926284"
> Mode:Master
> Channel:6
> Frequency:2.437 GHz
> Quality=174/146  Signal level=-239 dBm  Noise level=-71 
> dBm
> Encryption key:on
> Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
>   6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
>   36 Mb/s; 48 Mb/s; 54 Mb/s
> Extra:tsf=00122f23a1c2
>   Cell 02 - Address: 00:12:0E:12:68:D5
> ESSID:"05B408826277"
> Mode:Master
> Channel:6
> Frequency:2.437 GHz
> Quality=171/146  Signal level=-241 dBm  Noise level=-71 
> dBm
> Encryption key:off
> Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
>   6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
>   36 Mb/s; 48 Mb/s; 54 Mb/s
> Extra:tsf=00981721c122
>   Cell 03 - Address: 00:0F:B5:FA:9C:54
> ESSID:"dd-wrt"
> Mode:Master
> Channel:1
> Frequency:2.412 GHz
> Quality=213/146  Signal level=-216 dBm  Noise level=-71 
> dBm
> Encryption key:off
> Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
>   9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
>   48 Mb/s; 54 Mb/s
> Extra:tsf=00010a2e4181
>   Cell 04 - Address: 00:05:5D:F8:8D:68
> ESSID:"ICECAP4NIGHTCAP"
> Mode:Master
> Channel:7
> Frequency:2.442 GHz
> Quality=210/146  Signal level=-218 dBm  Noise level=-71 
> dBm
> Encryption key:on
> Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
> Extra:tsf=2e48723f
> 
> Cell 04 is my wap11.  And that mac address is correct.
> 
> I've brought the wap11 back to life with a powerdown reset.  And I've used 
> the 
> linux version of wap11gui to refresh the keys in the wap11.
> 
> I copied the old /etc/dir to a usb drive before I installed, and just went 
> and 
> got the KEYS-wlan0 file from there and installed it, copied ufcfg-eth0 to 
> ifcfg-wlan0 and modified it to set the channel, ESSID, mac address, so it now 
> looks like this:
> 
> # broadcom bcm4318 radio
> #
> DEVICE=wlan0
> BOOTPROTO=dhcp
> HWADDR=00:12:0E:12:68:D5
> ONBOOT=yes
> #TYPE=Ethernet
> TYPE=wireless
> ESSID="ICECAP4NIGHTCAP"
> CHANNEL="7"
> 
> 
> Then I copied ifup-wireless to ifup-wlan0, got brave and did an 
> "ifdown wlan0;ifup wlan0"
> It fussed about the mac address not matching, but worked!  I can now ping 
> yahoo with the cat5 unplugged.
> 
> So, go fix the mac address, wash rinse repeat.  When it works, it works 
> great, 
> but its dead for minutes at a time.

Yes, but you are using your neighbor's AP (ESSID:"05B408826277"), which is not 
encrypted. You need 
to specify the encryption key, which will keep it from connecting to the 
neighbor's unit.

Channel 7 is not a good choice for your AP, given the 2 neighboring AP's that 
use channel 6. The 
spectrum is more than +/- 2 channels away from the center; therefore the only 
non-interference is 
when channels 1, 6 and 11 are used. BTW, a patch was posted yesterday that will 
fix the quality and 
signal level numbers in iwscan and iwconfig.

Larry
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev


Re: bcm4318 in an HP dv5120us lappy

2007-06-02 Thread Larry Finger
Gene Heskett wrote:
> On Saturday 02 June 2007, Gene Heskett wrote:
>> Greetings;
>>
>> Fresh F7 install on that lappy.  Kernel is 2.6.21.1, i686 version, on a
>> powernow-k8 64 bitter.
>>
>> Whats the procedure to get this working?
> 
> Addendum:
> 
> Installing bcm43xx-fwcutter, following the instructions on berlios.de, I have 
> managed to get the radio turned on.  dmesg now reports:
> 
> ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x0D, vendor 0x4243)
> ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x09, vendor 0x4243)
> ssb: Core 2 found: PCI (cc 0x804, rev 0x0C, vendor 0x4243)
> ssb: Core 3 found: PCMCIA (cc 0x80D, rev 0x07, vendor 0x4243)
> ssb: Switching to ChipCommon core, index 0
> ssb: Switching to PCI core, index 2
> ssb: Sonics Silicon Backplane found on PCI device :06:02.0
> bcm43xx_mac80211: Broadcom 4318 WLAN found
> ssb: Switching to IEEE 802.11 core, index 1
> bcm43xx_mac80211: Found PHY: Analog 3, Type 2, Revision 7
> bcm43xx_mac80211: Found Radio: Manuf 0x17F, Version 0x2050, Revision 8
> bcm43xx_mac80211: Radio turned off
> wmaster0: Selected rate control algorithm 'simple'
> bcm43xx_mac80211: Adding Interface type 2
> ssb: Switching to PCI core, index 2
> ssb: Switching to IEEE 802.11 core, index 1
> bcm43xx_mac80211: Loading firmware version 319.102 (2005-10-15 22:46:19)
> ssb: Switching to ChipCommon core, index 0
> ssb: Switching to IEEE 802.11 core, index 1
> bcm43xx_mac80211: Radio turned on
> bcm43xx_mac80211: Radio enabled by hardware
> bcm43xx_mac80211: !WARNING! Idle-TSSI phy->cur_idle_tssi measuring failed. 
> (cur=0, tgt=62). Disabling TX power adjustment.
> bcm43xx_mac80211: Chip initialized
> bcm43xx_mac80211: 32-bit DMA initialized
> bcm43xx_mac80211: Wireless interface started
> ADDRCONF(NETDEV_UP): wlan0: link is not ready
> 
> However, it appears that neither my access point, a wap-11, or the radio in 
> the lappy is actually making any rf noise as I have a sniffer that reports 
> nothing.
> 
> Also, when system-config-network is executed after this has been achieved, 
> there is still no wlan0 available in the device or hardware list.

I was ignoring your request until you got the firmware installed and loaded! 
That is very well 
documented.

I have no idea what to expect from system-config-network. Questions regarding 
Fedora-specific 
utilities belong on a Fedora mailing list. You should use (as root) the 
iwconfig and 'iwlist scan' 
commands to see if your interface shows up, and if it is seeing any signals.

If your sniffer doesn't show any output from the AP, then either (a) your 
sniffer is broken, (b) the 
wireless in your AP is turned off, or (c) the SSID of your AP is hidden. If you 
have chosen (c) for 
security reasons, turn it back on - there is no real advantage.

I can only guess at why FC 7 uses the mac80211 driver. Be aware that the 
probability of it working 
"out of the box" is slim to none. If you are willing to patch the driver, you 
might get some limited 
success.

Larry
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev


Re: bcm4318 in an HP dv5120us lappy

2007-06-02 Thread Gene Heskett
On Saturday 02 June 2007, Gene Heskett wrote:
>Greetings;
>
>Fresh F7 install on that lappy.  Kernel is 2.6.21.1, i686 version, on a
>powernow-k8 64 bitter.
>
>Whats the procedure to get this working?

Addendum:

Installing bcm43xx-fwcutter, following the instructions on berlios.de, I have 
managed to get the radio turned on.  dmesg now reports:

ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x0D, vendor 0x4243)
ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x09, vendor 0x4243)
ssb: Core 2 found: PCI (cc 0x804, rev 0x0C, vendor 0x4243)
ssb: Core 3 found: PCMCIA (cc 0x80D, rev 0x07, vendor 0x4243)
ssb: Switching to ChipCommon core, index 0
ssb: Switching to PCI core, index 2
ssb: Sonics Silicon Backplane found on PCI device :06:02.0
bcm43xx_mac80211: Broadcom 4318 WLAN found
ssb: Switching to IEEE 802.11 core, index 1
bcm43xx_mac80211: Found PHY: Analog 3, Type 2, Revision 7
bcm43xx_mac80211: Found Radio: Manuf 0x17F, Version 0x2050, Revision 8
bcm43xx_mac80211: Radio turned off
wmaster0: Selected rate control algorithm 'simple'
bcm43xx_mac80211: Adding Interface type 2
ssb: Switching to PCI core, index 2
ssb: Switching to IEEE 802.11 core, index 1
bcm43xx_mac80211: Loading firmware version 319.102 (2005-10-15 22:46:19)
ssb: Switching to ChipCommon core, index 0
ssb: Switching to IEEE 802.11 core, index 1
bcm43xx_mac80211: Radio turned on
bcm43xx_mac80211: Radio enabled by hardware
bcm43xx_mac80211: !WARNING! Idle-TSSI phy->cur_idle_tssi measuring failed. 
(cur=0, tgt=62). Disabling TX power adjustment.
bcm43xx_mac80211: Chip initialized
bcm43xx_mac80211: 32-bit DMA initialized
bcm43xx_mac80211: Wireless interface started
ADDRCONF(NETDEV_UP): wlan0: link is not ready

However, it appears that neither my access point, a wap-11, or the radio in 
the lappy is actually making any rf noise as I have a sniffer that reports 
nothing.

Also, when system-config-network is executed after this has been achieved, 
there is still no wlan0 available in the device or hardware list.

So whats next folks?

Thanks for any help anyone can offer.

-- 
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)
Boycott meat -- suck your thumb.
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev


bcm4318 in an HP dv5120us lappy

2007-06-02 Thread Gene Heskett
Greetings;

Fresh F7 install on that lappy.  Kernel is 2.6.21.1, i686 version, on a 
powernow-k8 64 bitter.

Whats the procedure to get this working?

-- 
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)
"Bite off, dirtball."
Richard Sexton, [EMAIL PROTECTED]
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev