Ehud Gavron wrote:
> ifconfig eth1 up
> 
> E
> 

No, I did that.  It didn't complain, but it didn't do anything either

$ ifconfig eth1 up
$ ifconfig eth1

eth1      Link encap:Ethernet  HWaddr 00:19:7E:41:C1:B4
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:611 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:25662 (25.0 KiB)
          Interrupt:11 Base address:0x8000

$ iwlist eth1 scan
Warning: Driver for device eth1 has been compiled with version 22
of Wireless Extension, while this program supports up to version 20.
Some things may be broken...

eth1     No scan results



> Andrew McGuinness wrote:
>> I'm not able to detect my AP with a Dell 1390 mini-pci using bcm43xx
>>
>> I appreciate that the driver is under very heavy development at the
>> moment, and I'm willing to try the bcm43 if that will help.
>>
>> Details follow:
>>
>>
>> The Acer Aspire 3680 contains the following (lspci -v)
>>
>> 03:00.0 Network controller: Broadcom Corporation Dell Wireless 1390 WLAN
>> Mini-PCI Card (rev 01)
>>     Subsystem: AMBIT Microsystem Corp. Unknown device 0422
>>     Flags: bus master, fast devsel, latency 0, IRQ 17
>>     Memory at 34100000 (32-bit, non-prefetchable) [size=16K]
>>     Capabilities: [40] Power Management version 2
>>     Capabilities: [58] Message Signalled Interrupts: Mask- 64bit-
>> Queue=0/0
>> Enable-
>>     Capabilities: [d0] Express Legacy Endpoint IRQ 0
>>     Capabilities: [100] Advanced Error Reporting
>>     Capabilities: [13c] Virtual Channel
>>
>> and from lspci -n
>>
>> 03:00.0 0280: 14e4:4311 (rev 01)
>>
>>
>> I built a 2.6.21 kernel from debian, with the combined_2.6.21.patch from
>>  lwfinger.dynalias.org
>>
>> I got the v3 firmware wl_apsta-3.130.20.0.o and used fwcutter to create
>> the .fw files in /lib/firmware
>>
>> $ dmesg | grep bcm
>>
>> bcm43xx driver
>> bcm43xx: Chip ID 0x4311, rev 0x1
>> bcm43xx: Number of cores: 4
>> bcm43xx: Core 0: ID 0x800, rev 0x11, vendor 0x4243
>> bcm43xx: Core 1: ID 0x812, rev 0xa, vendor 0x4243
>> bcm43xx: Core 2: ID 0x817, rev 0x3, vendor 0x4243
>> bcm43xx: Core 3: ID 0x820, rev 0x1, vendor 0x4243
>> bcm43xx: PHY connected
>> bcm43xx: Detected PHY: Analog: 4, Type 2, Revision 8
>> bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2)
>> bcm43xx: Radio turned off
>> bcm43xx: Radio turned off
>> bcm43xx: PHY connected
>> bcm43xx: Microcode rev 0x127, pl 0xe (2005-04-18  02:36:27)
>> bcm43xx: Radio turned on
>> bcm43xx: Radio disabled by hardware
>> bcm43xx: Chip initialized
>> bcm43xx: 32-bit DMA initialized
>> bcm43xx: Keys cleared
>> bcm43xx: Selected 802.11 core (phytype 2)
>> bcm43xx: set security called, .level = 0, .enabled = 0, .encrypt = 0
>>
>> $ iwconfig eth1 essid arobeia
>>
>> $ iwconfig eth1
>>
>> Warning: Driver for device eth1 has been compiled with version 22
>> of Wireless Extension, while this program supports up to version 20.
>> Some things may be broken...
>>
>> eth1      IEEE 802.11b/g  ESSID:"arobeia"  Nickname:"Broadcom 4311"
>>           Mode:Managed  Frequency=2.472 GHz  Access Point: Invalid
>>           Bit Rate=1 Mb/s   Tx-Power=18 dBm
>>           RTS thr:off   Fragment thr:off
>>           Encryption key:off
>>           Link Quality=0/100  Signal level=-256 dBm  Noise level=-256 dBm
>>           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>>           Tx excessive retries:0  Invalid misc:0   Missed beacon:0
>>
>>
>>
>> $ iwlist eth1 scan
>>
>> eth1     no scan results
>>
>> The "radio disabled by hardware" looks like a problem to me   ?
>>
>>
>>   

_______________________________________________
Bcm43xx-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Reply via email to