View previous topic :: View next topic |
Author |
Message |
Sodki Guru
Joined: 11 Aug 2003 Posts: 419 Location: London, U.K. & Lisbon, Portugal
|
Posted: Sun Feb 03, 2008 12:16 pm Post subject: |
|
|
GreyVicious wrote: | I have similar problem, using 2.6.24-zen1 and b43, WiFi: BCM94311MCG (rev 01), HP 530 laptop. For me Wireless is always on, I can't turn it off, switch on notebook doesn't work. |
I have the opposite problem. My wireless is always off and I can't seem to turn it on without going into MacOSX. |
|
Back to top |
|
|
lordcris Apprentice
Joined: 09 Jul 2002 Posts: 248
|
Posted: Sun Feb 03, 2008 2:02 pm Post subject: |
|
|
damoncf wrote: | I did. Here is what my Networking --> Wireless looks like
Code: |
[*] Improved wireless configuration API │ │
│ │ [*] nl80211 new netlink interface support │ │
│ │ [*] Wireless extensions │ │
│ │ [*] Generic IEEE 802.11 Networking Stack │ │
│ │ [ ] Enable full debugging output │ │
│ │ [*] IEEE 802.11 WEP encryption (802.1x) │ │
│ │ [*] IEEE 802.11i CCMP support │ │
│ │ [ ] IEEE 802.11i TKIP encryption │ │
│ │ │ │
│ │
|
And here is my Device Drivers -->Network device support --> Wireless lan
Code: |
[ ] Wireless LAN (pre-802.11) │ │
│ │ [*] Wireless LAN (IEEE 802.11) │ │
│ │ [ ] Marvell 8xxx Libertas WLAN driver support │ │
│ │ [ ] IEEE 802.11 for Host AP (Prism2/2.5/3 and WEP/TKIP/CCMP) │ │
│ │
|
I do not see what they are talking about on the first page.
Damon |
enable "Prompt for development and/or incomplete code/drivers " under "General Setup" |
|
Back to top |
|
|
slackline Veteran
Joined: 01 Apr 2005 Posts: 1471 Location: /uk/sheffield
|
Posted: Mon Feb 04, 2008 9:34 pm Post subject: |
|
|
I'm scratching my head over this. I had everything working fine under 2.6.23-gentoo-r5 with ndiswrapper, upgraded to 2.6.23-gentoo-r6 and the network card stopped working. Not a problem I thought, 2.6.24-gentoo has just hit the tree so I'll do a kernel upgrade and switch to the in-kernel broadcom drivers and kill two birds then get stoned....
...or so I thought (still haven't had that smoke).
Have followed the kernel configuration to the letter, emerged net-wireless/b43-fwcutter-010 and then installed the wl_apsta_mimo.o from broadcom-wl-4.150.10.5 and everything installs fine.
Rebooted but the wireless network failed to detect.
Checked /var/log/dmesg and have...
Code: |
# grep -i broadcom /var/log/dmesg -A30
b43-phy0: Broadcom 4306 WLAN found
b43-phy0 debug: Found PHY: Analog 2, Type 2, Revision 2
b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2
phy0: Selected rate control algorithm 'simple'
ACPI: PCI Interrupt 0000:00:1f.5[B] -> Link [LNKB] -> GSI 10 (level, low) -> IRQ 10
PCI: Setting latency timer of device 0000:00:1f.5 to 64
intel8x0_measure_ac97_clock: measured 55419 usecs
intel8x0: clocking to 48000
EXT3 FS on hda3, internal journal
ndiswrapper version 1.51 loaded (smp=no, preempt=yes)
kjournald starting. Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on hda4, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Adding 999928k swap on /dev/hda2. Priority:-1 extents:1 across:999928k
|
So it appears that the card is detected and bought up on booting, however, dmesg at the prompt gives...
Code: |
# dmesg
ivers/net/wireless/b43/dma.c:1098 parse_cookie()
Pid: 0, comm: swapper Tainted: P 2.6.24-gentoo #3
[<e8118779>] b43_dma_handle_txstatus+0xa9/0x460 [b43]
[<e8105a8c>] b43_interrupt_tasklet+0x34c/0x840 [b43]
[<c012a7e9>] insert_work+0x49/0x70
[<c01204c7>] tasklet_action+0x27/0x60
[<c0120422>] __do_softirq+0x42/0x90
[<c0120496>] do_softirq+0x26/0x30
[<c01206c5>] irq_exit+0x35/0x40
[<c0105f17>] do_IRQ+0x47/0x80
[<c010444f>] common_interrupt+0x23/0x28
[<c0110000>] wakeup_code+0x0/0xde
[<c02960be>] acpi_processor_idle+0x22c/0x392
[<c01025cf>] cpu_idle+0x3f/0x60
[<c056eab5>] start_kernel+0x205/0x290
[<c056e380>] unknown_bootoption+0x0/0x1e0
=======================
WARNING: at drivers/net/wireless/b43/dma.c:1095 parse_cookie()
Pid: 0, comm: swapper Tainted: P 2.6.24-gentoo #3
[<e811874d>] b43_dma_handle_txstatus+0x7d/0x460 [b43]
[<e8105a8c>] b43_interrupt_tasklet+0x34c/0x840 [b43]
[<c012a7e9>] insert_work+0x49/0x70
[<c01204c7>] tasklet_action+0x27/0x60
[<c0120422>] __do_softirq+0x42/0x90
[<c0120496>] do_softirq+0x26/0x30
[<c01206c5>] irq_exit+0x35/0x40
[<c0105f17>] do_IRQ+0x47/0x80
[<c010444f>] common_interrupt+0x23/0x28
[<c0110000>] wakeup_code+0x0/0xde
[<c02960be>] acpi_processor_idle+0x22c/0x392
[<c01025cf>] cpu_idle+0x3f/0x60
[<c056eab5>] start_kernel+0x205/0x290
[<c056e380>] unknown_bootoption+0x0/0x1e0
=======================
WARNING: at drivers/net/wireless/b43/dma.c:1098 parse_cookie()
Pid: 0, comm: swapper Tainted: P 2.6.24-gentoo #3
[<e8118779>] b43_dma_handle_txstatus+0xa9/0x460 [b43]
[<e8105a8c>] b43_interrupt_tasklet+0x34c/0x840 [b43]
[<c012a7e9>] insert_work+0x49/0x70
[<c01204c7>] tasklet_action+0x27/0x60
[<c0120422>] __do_softirq+0x42/0x90
[<c0120496>] do_softirq+0x26/0x30
[<c01206c5>] irq_exit+0x35/0x40
[<c0105f17>] do_IRQ+0x47/0x80
[<c010444f>] common_interrupt+0x23/0x28
[<c0110000>] wakeup_code+0x0/0xde
[<c02960be>] acpi_processor_idle+0x22c/0x392
[<c01025cf>] cpu_idle+0x3f/0x60
[<c056eab5>] start_kernel+0x205/0x290
[<c056e380>] unknown_bootoption+0x0/0x1e0
=======================
WARNING: at drivers/net/wireless/b43/dma.c:1095 parse_cookie()
Pid: 0, comm: swapper Tainted: P 2.6.24-gentoo #3
[<e811874d>] b43_dma_handle_txstatus+0x7d/0x460 [b43]
[<e8105a8c>] b43_interrupt_tasklet+0x34c/0x840 [b43]
[<c012a7e9>] insert_work+0x49/0x70
[<c01204c7>] tasklet_action+0x27/0x60
[<c0120422>] __do_softirq+0x42/0x90
[<c0120496>] do_softirq+0x26/0x30
[<c01206c5>] irq_exit+0x35/0x40
[<c0105f17>] do_IRQ+0x47/0x80
[<c010444f>] common_interrupt+0x23/0x28
[<c0110000>] wakeup_code+0x0/0xde
[<c02960be>] acpi_processor_idle+0x22c/0x392
[<c01025cf>] cpu_idle+0x3f/0x60
[<c056eab5>] start_kernel+0x205/0x290
[<c056e380>] unknown_bootoption+0x0/0x1e0
=======================
WARNING: at drivers/net/wireless/b43/dma.c:1098 parse_cookie()
Pid: 0, comm: swapper Tainted: P 2.6.24-gentoo #3
[<e8118779>] b43_dma_handle_txstatus+0xa9/0x460 [b43]
[<e8105a8c>] b43_interrupt_tasklet+0x34c/0x840 [b43]
[<c012a7e9>] insert_work+0x49/0x70
[<c01204c7>] tasklet_action+0x27/0x60
[<c0120422>] __do_softirq+0x42/0x90
[<c0120496>] do_softirq+0x26/0x30
[<c01206c5>] irq_exit+0x35/0x40
[<c0105f17>] do_IRQ+0x47/0x80
[<c010444f>] common_interrupt+0x23/0x28
[<c0110000>] wakeup_code+0x0/0xde
[<c02960be>] acpi_processor_idle+0x22c/0x392
[<c01025cf>] cpu_idle+0x3f/0x60
[<c056eab5>] start_kernel+0x205/0x290
[<c056e380>] unknown_bootoption+0x0/0x1e0
=======================
WARNING: at drivers/net/wireless/b43/dma.c:1095 parse_cookie()
Pid: 0, comm: swapper Tainted: P 2.6.24-gentoo #3
[<e811874d>] b43_dma_handle_txstatus+0x7d/0x460 [b43]
[<e8105a8c>] b43_interrupt_tasklet+0x34c/0x840 [b43]
[<c012a7e9>] insert_work+0x49/0x70
[<c01204c7>] tasklet_action+0x27/0x60
[<c0120422>] __do_softirq+0x42/0x90
[<c0120496>] do_softirq+0x26/0x30
[<c01206c5>] irq_exit+0x35/0x40
[<c0105f17>] do_IRQ+0x47/0x80
[<c010444f>] common_interrupt+0x23/0x28
[<c0110000>] wakeup_code+0x0/0xde
[<c02960be>] acpi_processor_idle+0x22c/0x392
[<c01025cf>] cpu_idle+0x3f/0x60
[<c056eab5>] start_kernel+0x205/0x290
[<c056e380>] unknown_bootoption+0x0/0x1e0
=======================
WARNING: at drivers/net/wireless/b43/dma.c:1098 parse_cookie()
Pid: 0, comm: swapper Tainted: P 2.6.24-gentoo #3
[<e8118779>] b43_dma_handle_txstatus+0xa9/0x460 [b43]
[<e8105a8c>] b43_interrupt_tasklet+0x34c/0x840 [b43]
[<c012a7e9>] insert_work+0x49/0x70
[<c01204c7>] tasklet_action+0x27/0x60
[<c0120422>] __do_softirq+0x42/0x90
[<c0120496>] do_softirq+0x26/0x30
[<c01206c5>] irq_exit+0x35/0x40
[<c0105f17>] do_IRQ+0x47/0x80
[<c010444f>] common_interrupt+0x23/0x28
[<c0110000>] wakeup_code+0x0/0xde
[<c02960be>] acpi_processor_idle+0x22c/0x392
[<c01025cf>] cpu_idle+0x3f/0x60
[<c056eab5>] start_kernel+0x205/0x290
[<c056e380>] unknown_bootoption+0x0/0x1e0
=======================
WARNING: at drivers/net/wireless/b43/dma.c:1095 parse_cookie()
Pid: 0, comm: swapper Tainted: P 2.6.24-gentoo #3
[<e811874d>] b43_dma_handle_txstatus+0x7d/0x460 [b43]
[<e8105a8c>] b43_interrupt_tasklet+0x34c/0x840 [b43]
[<c012a7e9>] insert_work+0x49/0x70
[<c01204c7>] tasklet_action+0x27/0x60
[<c0120422>] __do_softirq+0x42/0x90
[<c0120496>] do_softirq+0x26/0x30
[<c01206c5>] irq_exit+0x35/0x40
[<c0105f17>] do_IRQ+0x47/0x80
[<c010444f>] common_interrupt+0x23/0x28
[<c0110000>] wakeup_code+0x0/0xde
[<c02960be>] acpi_processor_idle+0x22c/0x392
[<c01025cf>] cpu_idle+0x3f/0x60
[<c056eab5>] start_kernel+0x205/0x290
[<c056e380>] unknown_bootoption+0x0/0x1e0
=======================
WARNING: at drivers/net/wireless/b43/dma.c:1098 parse_cookie()
Pid: 0, comm: swapper Tainted: P 2.6.24-gentoo #3
[<e8118779>] b43_dma_handle_txstatus+0xa9/0x460 [b43]
[<e8105a8c>] b43_interrupt_tasklet+0x34c/0x840 [b43]
[<c012a7e9>] insert_work+0x49/0x70
[<c01204c7>] tasklet_action+0x27/0x60
[<c0120422>] __do_softirq+0x42/0x90
[<c0120496>] do_softirq+0x26/0x30
[<c01206c5>] irq_exit+0x35/0x40
[<c0105f17>] do_IRQ+0x47/0x80
[<c010444f>] common_interrupt+0x23/0x28
[<c0110000>] wakeup_code+0x0/0xde
[<c02960be>] acpi_processor_idle+0x22c/0x392
[<c01025cf>] cpu_idle+0x3f/0x60
[<c056eab5>] start_kernel+0x205/0x290
[<c056e380>] unknown_bootoption+0x0/0x1e0
=======================
WARNING: at drivers/net/wireless/b43/dma.c:1095 parse_cookie()
Pid: 0, comm: swapper Tainted: P 2.6.24-gentoo #3
[<e811874d>] b43_dma_handle_txstatus+0x7d/0x460 [b43]
[<e8105a8c>] b43_interrupt_tasklet+0x34c/0x840 [b43]
[<c012a7e9>] insert_work+0x49/0x70
[<c01204c7>] tasklet_action+0x27/0x60
[<c0120422>] __do_softirq+0x42/0x90
[<c0120496>] do_softirq+0x26/0x30
[<c01206c5>] irq_exit+0x35/0x40
[<c0105f17>] do_IRQ+0x47/0x80
[<c010444f>] common_interrupt+0x23/0x28
[<c0110000>] wakeup_code+0x0/0xde
[<c02960be>] acpi_processor_idle+0x22c/0x392
[<c01025cf>] cpu_idle+0x3f/0x60
[<c056eab5>] start_kernel+0x205/0x290
[<c056e380>] unknown_bootoption+0x0/0x1e0
=======================
WARNING: at drivers/net/wireless/b43/dma.c:1098 parse_cookie()
Pid: 0, comm: swapper Tainted: P 2.6.24-gentoo #3
[<e8118779>] b43_dma_handle_txstatus+0xa9/0x460 [b43]
[<e8105a8c>] b43_interrupt_tasklet+0x34c/0x840 [b43]
[<c012a7e9>] insert_work+0x49/0x70
[<c01204c7>] tasklet_action+0x27/0x60
[<c0120422>] __do_softirq+0x42/0x90
[<c0120496>] do_softirq+0x26/0x30
[<c01206c5>] irq_exit+0x35/0x40
[<c0105f17>] do_IRQ+0x47/0x80
[<c010444f>] common_interrupt+0x23/0x28
[<c0110000>] wakeup_code+0x0/0xde
[<c02960be>] acpi_processor_idle+0x22c/0x392
[<c01025cf>] cpu_idle+0x3f/0x60
[<c056eab5>] start_kernel+0x205/0x290
[<c056e380>] unknown_bootoption+0x0/0x1e0
=======================
WARNING: at drivers/net/wireless/b43/dma.c:1095 parse_cookie()
Pid: 0, comm: swapper Tainted: P 2.6.24-gentoo #3
[<e811874d>] b43_dma_handle_txstatus+0x7d/0x460 [b43]
[<e8105a8c>] b43_interrupt_tasklet+0x34c/0x840 [b43]
[<c012a7e9>] insert_work+0x49/0x70
[<c01204c7>] tasklet_action+0x27/0x60
[<c0120422>] __do_softirq+0x42/0x90
[<c0120496>] do_softirq+0x26/0x30
[<c01206c5>] irq_exit+0x35/0x40
[<c0105f17>] do_IRQ+0x47/0x80
[<c010444f>] common_interrupt+0x23/0x28
[<c0110000>] wakeup_code+0x0/0xde
[<c02960be>] acpi_processor_idle+0x22c/0x392
[<c01025cf>] cpu_idle+0x3f/0x60
[<c056eab5>] start_kernel+0x205/0x290
[<c056e380>] unknown_bootoption+0x0/0x1e0
=======================
WARNING: at drivers/net/wireless/b43/dma.c:1098 parse_cookie()
Pid: 0, comm: swapper Tainted: P 2.6.24-gentoo #3
[<e8118779>] b43_dma_handle_txstatus+0xa9/0x460 [b43]
[<e8105a8c>] b43_interrupt_tasklet+0x34c/0x840 [b43]
[<c012a7e9>] insert_work+0x49/0x70
[<c01204c7>] tasklet_action+0x27/0x60
[<c0120422>] __do_softirq+0x42/0x90
[<c0120496>] do_softirq+0x26/0x30
[<c01206c5>] irq_exit+0x35/0x40
[<c0105f17>] do_IRQ+0x47/0x80
[<c010444f>] common_interrupt+0x23/0x28
[<c0110000>] wakeup_code+0x0/0xde
[<c02960be>] acpi_processor_idle+0x22c/0x392
[<c01025cf>] cpu_idle+0x3f/0x60
[<c056eab5>] start_kernel+0x205/0x290
[<c056e380>] unknown_bootoption+0x0/0x1e0
=======================
WARNING: at drivers/net/wireless/b43/dma.c:1095 parse_cookie()
Pid: 0, comm: swapper Tainted: P 2.6.24-gentoo #3
[<e811874d>] b43_dma_handle_txstatus+0x7d/0x460 [b43]
[<e8105a8c>] b43_interrupt_tasklet+0x34c/0x840 [b43]
[<c012a7e9>] insert_work+0x49/0x70
[<c01204c7>] tasklet_action+0x27/0x60
[<c0120422>] __do_softirq+0x42/0x90
[<c0120496>] do_softirq+0x26/0x30
[<c01206c5>] irq_exit+0x35/0x40
[<c0105f17>] do_IRQ+0x47/0x80
[<c010444f>] common_interrupt+0x23/0x28
[<c0110000>] wakeup_code+0x0/0xde
[<c02960be>] acpi_processor_idle+0x22c/0x392
[<c01025cf>] cpu_idle+0x3f/0x60
[<c056eab5>] start_kernel+0x205/0x290
[<c056e380>] unknown_bootoption+0x0/0x1e0
=======================
WARNING: at drivers/net/wireless/b43/dma.c:1098 parse_cookie()
Pid: 0, comm: swapper Tainted: P 2.6.24-gentoo #3
[<e8118779>] b43_dma_handle_txstatus+0xa9/0x460 [b43]
[<e8105a8c>] b43_interrupt_tasklet+0x34c/0x840 [b43]
[<c012a7e9>] insert_work+0x49/0x70
[<c01204c7>] tasklet_action+0x27/0x60
[<c0120422>] __do_softirq+0x42/0x90
[<c0120496>] do_softirq+0x26/0x30
[<c01206c5>] irq_exit+0x35/0x40
[<c0105f17>] do_IRQ+0x47/0x80
[<c010444f>] common_interrupt+0x23/0x28
[<c0110000>] wakeup_code+0x0/0xde
[<c02960be>] acpi_processor_idle+0x22c/0x392
[<c01025cf>] cpu_idle+0x3f/0x60
[<c056eab5>] start_kernel+0x205/0x290
[<c056e380>] unknown_bootoption+0x0/0x1e0
=======================
WARNING: at drivers/net/wireless/b43/dma.c:1095 parse_cookie()
Pid: 0, comm: swapper Tainted: P 2.6.24-gentoo #3
[<e811874d>] b43_dma_handle_txstatus+0x7d/0x460 [b43]
[<e8105a8c>] b43_interrupt_tasklet+0x34c/0x840 [b43]
[<c012a7e9>] insert_work+0x49/0x70
[<c01204c7>] tasklet_action+0x27/0x60
[<c0120422>] __do_softirq+0x42/0x90
[<c0120496>] do_softirq+0x26/0x30
[<c01206c5>] irq_exit+0x35/0x40
[<c0105f17>] do_IRQ+0x47/0x80
[<c010444f>] common_interrupt+0x23/0x28
[<c0110000>] wakeup_code+0x0/0xde
[<c02960be>] acpi_processor_idle+0x22c/0x392
[<c01025cf>] cpu_idle+0x3f/0x60
[<c056eab5>] start_kernel+0x205/0x290
[<c056e380>] unknown_bootoption+0x0/0x1e0
=======================
WARNING: at drivers/net/wireless/b43/dma.c:1098 parse_cookie()
Pid: 0, comm: swapper Tainted: P 2.6.24-gentoo #3
[<e8118779>] b43_dma_handle_txstatus+0xa9/0x460 [b43]
[<e8105a8c>] b43_interrupt_tasklet+0x34c/0x840 [b43]
[<c012a7e9>] insert_work+0x49/0x70
[<c01204c7>] tasklet_action+0x27/0x60
[<c0120422>] __do_softirq+0x42/0x90
[<c0120496>] do_softirq+0x26/0x30
[<c01206c5>] irq_exit+0x35/0x40
[<c0105f17>] do_IRQ+0x47/0x80
[<c010444f>] common_interrupt+0x23/0x28
[<c0110000>] wakeup_code+0x0/0xde
[<c02960be>] acpi_processor_idle+0x22c/0x392
[<c01025cf>] cpu_idle+0x3f/0x60
[<c056eab5>] start_kernel+0x205/0x290
[<c056e380>] unknown_bootoption+0x0/0x1e0
=======================
WARNING: at drivers/net/wireless/b43/dma.c:1095 parse_cookie()
Pid: 0, comm: swapper Tainted: P 2.6.24-gentoo #3
[<e811874d>] b43_dma_handle_txstatus+0x7d/0x460 [b43]
[<e8105a8c>] b43_interrupt_tasklet+0x34c/0x840 [b43]
[<c012a7e9>] insert_work+0x49/0x70
[<c01204c7>] tasklet_action+0x27/0x60
[<c0120422>] __do_softirq+0x42/0x90
[<c0120496>] do_softirq+0x26/0x30
[<c01206c5>] irq_exit+0x35/0x40
[<c0105f17>] do_IRQ+0x47/0x80
[<c010444f>] common_interrupt+0x23/0x28
[<c0110000>] wakeup_code+0x0/0xde
[<c02960be>] acpi_processor_idle+0x22c/0x392
[<c01025cf>] cpu_idle+0x3f/0x60
[<c056eab5>] start_kernel+0x205/0x290
[<c056e380>] unknown_bootoption+0x0/0x1e0
=======================
WARNING: at drivers/net/wireless/b43/dma.c:1098 parse_cookie()
Pid: 0, comm: swapper Tainted: P 2.6.24-gentoo #3
[<e8118779>] b43_dma_handle_txstatus+0xa9/0x460 [b43]
[<e8105a8c>] b43_interrupt_tasklet+0x34c/0x840 [b43]
[<c012a7e9>] insert_work+0x49/0x70
[<c01204c7>] tasklet_action+0x27/0x60
[<c0120422>] __do_softirq+0x42/0x90
[<c0120496>] do_softirq+0x26/0x30
[<c01206c5>] irq_exit+0x35/0x40
[<c0105f17>] do_IRQ+0x47/0x80
[<c010444f>] common_interrupt+0x23/0x28
[<c0110000>] wakeup_code+0x0/0xde
[<c02960be>] acpi_processor_idle+0x22c/0x392
[<c01025cf>] cpu_idle+0x3f/0x60
[<c056eab5>] start_kernel+0x205/0x290
[<c056e380>] unknown_bootoption+0x0/0x1e0
=======================
WARNING: at drivers/net/wireless/b43/dma.c:1095 parse_cookie()
Pid: 0, comm: swapper Tainted: P 2.6.24-gentoo #3
[<e811874d>] b43_dma_handle_txstatus+0x7d/0x460 [b43]
[<e8105a8c>] b43_interrupt_tasklet+0x34c/0x840 [b43]
[<c012a7e9>] insert_work+0x49/0x70
[<c01204c7>] tasklet_action+0x27/0x60
[<c0120422>] __do_softirq+0x42/0x90
[<c0120496>] do_softirq+0x26/0x30
[<c01206c5>] irq_exit+0x35/0x40
[<c0105f17>] do_IRQ+0x47/0x80
[<c010444f>] common_interrupt+0x23/0x28
[<c0110000>] wakeup_code+0x0/0xde
[<c02960be>] acpi_processor_idle+0x22c/0x392
[<c01025cf>] cpu_idle+0x3f/0x60
[<c056eab5>] start_kernel+0x205/0x290
[<c056e380>] unknown_bootoption+0x0/0x1e0
=======================
WARNING: at drivers/net/wireless/b43/dma.c:1098 parse_cookie()
Pid: 0, comm: swapper Tainted: P 2.6.24-gentoo #3
[<e8118779>] b43_dma_handle_txstatus+0xa9/0x460 [b43]
[<e8105a8c>] b43_interrupt_tasklet+0x34c/0x840 [b43]
[<c012a7e9>] insert_work+0x49/0x70
[<c01204c7>] tasklet_action+0x27/0x60
[<c0120422>] __do_softirq+0x42/0x90
[<c0120496>] do_softirq+0x26/0x30
[<c01206c5>] irq_exit+0x35/0x40
[<c0105f17>] do_IRQ+0x47/0x80
[<c010444f>] common_interrupt+0x23/0x28
[<c0110000>] wakeup_code+0x0/0xde
[<c02960be>] acpi_processor_idle+0x22c/0x392
[<c01025cf>] cpu_idle+0x3f/0x60
[<c056eab5>] start_kernel+0x205/0x290
[<c056e380>] unknown_bootoption+0x0/0x1e0
=======================
printk: 52 messages suppressed.
b43-phy0: Radio turned off by software
b43-phy0 debug: Removing Interface type 2
b43-phy0 debug: Wireless interface stopped
b43-phy0 debug: DMA-32 0x0200 (RX) max used slots: 0/64
b43-phy0 debug: DMA-32 0x02A0 (TX) max used slots: 0/128
b43-phy0 debug: DMA-32 0x0280 (TX) max used slots: 0/128
b43-phy0 debug: DMA-32 0x0260 (TX) max used slots: 0/128
b43-phy0 debug: DMA-32 0x0240 (TX) max used slots: 0/128
b43-phy0 debug: DMA-32 0x0220 (TX) max used slots: 88/128
b43-phy0 debug: DMA-32 0x0200 (TX) max used slots: 0/128
|
...and at the end the interface is stopped.
Strangely though the interface is still listed...
Code: |
# iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wmaster0 no wireless extensions.
wlan0 IEEE 802.11g ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=off
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
|
...but it seems to no longer support scanning (which it used to when I used ndiswrapper to insert the module)...
Code: |
# iwlist scan
lo Interface doesn't support scanning.
eth0 Interface doesn't support scanning.
wmaster0 Interface doesn't support scanning.
wlan0 Interface doesn't support scanning : Network is down
|
Does anyone know what might be happening here? I'm stumped (not that I've ever done any deep debugging of the kernel to even know where to begin).
Cheers
slack |
|
Back to top |
|
|
lordcris Apprentice
Joined: 09 Jul 2002 Posts: 248
|
Posted: Mon Feb 04, 2008 10:06 pm Post subject: |
|
|
slack---line wrote: | I'm scratching my head over this. I had everything working fine under 2.6.23-gentoo-r5 with ndiswrapper, upgraded to 2.6.23-gentoo-r6 and the network card stopped working. Not a problem I thought, 2.6.24-gentoo has just hit the tree so I'll do a kernel upgrade and switch to the in-kernel broadcom drivers and kill two birds then get stoned....
...or so I thought (still haven't had that smoke).
Have followed the kernel configuration to the letter, emerged net-wireless/b43-fwcutter-010 and then installed the wl_apsta_mimo.o from broadcom-wl-4.150.10.5 and everything installs fine.
|
hi,
for kernel 2.6.24 you should use net-wireless/b43-fwcutter-009 and install the broadcom-wl-4.80.53.0 firmware. |
|
Back to top |
|
|
slackline Veteran
Joined: 01 Apr 2005 Posts: 1471 Location: /uk/sheffield
|
Posted: Mon Feb 04, 2008 10:50 pm Post subject: |
|
|
lordcris wrote: |
hi,
for kernel 2.6.24 you should use net-wireless/b43-fwcutter-009 and install the broadcom-wl-4.80.53.0 firmware. |
Thanks for the quick reply.
Dropped back the firmware and b43-fwcutter as suggested, and after clearing out the 4.150 files from /lib/firmware/b43/ the warnings previously mentioned have disappeared, but the interface is still stopped automatically...
Code: |
b43-phy0: Broadcom 4306 WLAN found
b43-phy0 debug: Found PHY: Analog 2, Type 2, Revision 2
b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2
phy0: Selected rate control algorithm 'simple'
ACPI: PCI Interrupt 0000:00:1f.5[B] -> Link [LNKB] -> GSI 10 (level, low) -> IRQ 10
PCI: Setting latency timer of device 0000:00:1f.5 to 64
intel8x0_measure_ac97_clock: measured 55438 usecs
intel8x0: clocking to 48000
EXT3 FS on hda3, internal journal
ndiswrapper version 1.51 loaded (smp=no, preempt=yes)
kjournald starting. Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on hda4, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Adding 999928k swap on /dev/hda2. Priority:-1 extents:1 across:999928k
tg3: eth0: Link is up at 100 Mbps, full duplex.
tg3: eth0: Flow control is on for TX and on for RX.
b43-phy0 debug: Loading firmware version 351.126 (2006-07-29 05:54:02)
b43-phy0 debug: Chip initialized
b43-phy0 debug: 30-bit DMA initialized
b43-phy0 debug: Wireless interface started
b43-phy0 debug: Adding Interface type 2
b43-phy0: Radio turned off by software
b43-phy0 debug: Removing Interface type 2
b43-phy0 debug: Wireless interface stopped
b43-phy0 debug: DMA-32 0x0200 (RX) max used slots: 0/64
b43-phy0 debug: DMA-32 0x02A0 (TX) max used slots: 0/128
b43-phy0 debug: DMA-32 0x0280 (TX) max used slots: 0/128
b43-phy0 debug: DMA-32 0x0260 (TX) max used slots: 0/128
b43-phy0 debug: DMA-32 0x0240 (TX) max used slots: 0/128
b43-phy0 debug: DMA-32 0x0220 (TX) max used slots: 2/128
b43-phy0 debug: DMA-32 0x0200 (TX) max used slots: 0/128
|
...and scanning still isn't supported. I normally have essid broadcasting disable on my router, but have enabled it till I get this sorted. My wife's laptop connects fine, so the wireless network is up and running and a site scan from the router config page reveals there are five other networks broadcasting essid, but my laptop can see none of them because the hardware has been stopped
Code: |
# iwlist wlan0 scanning essid slack
wlan0 Interface doesn't support scanning : Network is down
|
Is there any more info I need to provide to help resolve this? I've not changed any of the configuration in /etc/conf.d/net so it should be a config problem (although all of the above is telling me its still at the hardware/driver problem stage).
Cheers,
slack |
|
Back to top |
|
|
lordcris Apprentice
Joined: 09 Jul 2002 Posts: 248
|
Posted: Mon Feb 04, 2008 10:57 pm Post subject: |
|
|
[quote="slack---line"] lordcris wrote: |
Code: |
# iwlist wlan0 scanning essid slack
wlan0 Interface doesn't support scanning : Network is down
|
Is there any more info I need to provide to help resolve this? I've not changed any of the configuration in /etc/conf.d/net so it should be a config problem (although all of the above is telling me its still at the hardware/driver problem stage).
Cheers,
slack |
try
Code: | /etc/init.d/net.wlan0 start |
( /etc/init.d/net.wlan0 is a symlink to /etc/init.d/net.lo
create it if it is not there)
then emerge net-wireless/wpa_supplicant and use wpa_gui to join your network. |
|
Back to top |
|
|
slackline Veteran
Joined: 01 Apr 2005 Posts: 1471 Location: /uk/sheffield
|
Posted: Mon Feb 04, 2008 11:15 pm Post subject: |
|
|
lordcris wrote: |
try
Code: | /etc/init.d/net.wlan0 start |
( /etc/init.d/net.wlan0 is a symlink to /etc/init.d/net.lo
create it if it is not there)
|
Already tried this (well '$ /etc/init.d/net.wlan0 restart' actually) and it just results in a repeat of the same message...
Code: |
# /etc/init.d/net.wlan0 restart
* Starting wlan0
* Configuring wireless network for wlan0
* no access points found
* Trying to force preferred in case they are hidden
* Failed to associate with any preferred access points on wlan0
* Couldn't find any access points on wlan0
* Failed to configure wireless for wlan0 [ !! ]
wright neil # dmesg | tail -n30
b43-phy0 debug: Loading firmware version 351.126 (2006-07-29 05:54:02)
b43-phy0 debug: Chip initialized
b43-phy0 debug: 30-bit DMA initialized
b43-phy0 debug: Wireless interface started
b43-phy0 debug: Adding Interface type 2
b43-phy0: Radio turned off by software
b43-phy0 debug: Removing Interface type 2
b43-phy0 debug: Wireless interface stopped
b43-phy0 debug: DMA-32 0x0200 (RX) max used slots: 0/64
b43-phy0 debug: DMA-32 0x02A0 (TX) max used slots: 0/128
b43-phy0 debug: DMA-32 0x0280 (TX) max used slots: 0/128
b43-phy0 debug: DMA-32 0x0260 (TX) max used slots: 0/128
b43-phy0 debug: DMA-32 0x0240 (TX) max used slots: 0/128
b43-phy0 debug: DMA-32 0x0220 (TX) max used slots: 2/128
b43-phy0 debug: DMA-32 0x0200 (TX) max used slots: 0/128
b43-phy0 debug: Loading firmware version 351.126 (2006-07-29 05:54:02)
b43-phy0 debug: Chip initialized
b43-phy0 debug: 30-bit DMA initialized
b43-phy0 debug: Wireless interface started
b43-phy0 debug: Adding Interface type 2
b43-phy0: Radio turned off by software
b43-phy0 debug: Removing Interface type 2
b43-phy0 debug: Wireless interface stopped
b43-phy0 debug: DMA-32 0x0200 (RX) max used slots: 0/64
b43-phy0 debug: DMA-32 0x02A0 (TX) max used slots: 0/128
b43-phy0 debug: DMA-32 0x0280 (TX) max used slots: 0/128
b43-phy0 debug: DMA-32 0x0260 (TX) max used slots: 0/128
b43-phy0 debug: DMA-32 0x0240 (TX) max used slots: 0/128
b43-phy0 debug: DMA-32 0x0220 (TX) max used slots: 2/128
b43-phy0 debug: DMA-32 0x0200 (TX) max used slots: 0/128
|
..so the firmware is loaded and then stopped again.
lordcris wrote: |
then emerge net-wireless/wpa_supplicant and use wpa_gui to join your network. |
When I try wpa_gui it fails to connect to the network, even if I specify the correct essid I'm told "Failed to enable network in wpa_supplicant configuration (could be because I've not got support in the kernel, but haven't checked yet). But this should work with the config I have since it did previously using ndiswrapper to manually insert the module.
Code: |
# wpa_gui
Failed to open control connection to wpa_supplicant.
PING failed - trying to reconnect
PING failed - trying to reconnect
PING failed - trying to reconnect
PING failed - trying to reconnect
PING failed - trying to reconnect
PING failed - trying to reconnect
PING failed - trying to reconnect
PING failed - trying to reconnect
PING failed - trying to reconnect
PING failed - trying to reconnect
PING failed - trying to reconnect
PING failed - trying to reconnect
PING failed - trying to reconnect
PING failed - trying to reconnect
|
Cheers for your help,
slack |
|
Back to top |
|
|
lordcris Apprentice
Joined: 09 Jul 2002 Posts: 248
|
Posted: Tue Feb 05, 2008 12:02 am Post subject: |
|
|
slack---line wrote: | lordcris wrote: |
try
Code: | /etc/init.d/net.wlan0 start |
( /etc/init.d/net.wlan0 is a symlink to /etc/init.d/net.lo
create it if it is not there)
|
Already tried this (well '$ /etc/init.d/net.wlan0 restart' actually) and it just results in a repeat of the same message...
Code: |
# /etc/init.d/net.wlan0 restart
* Starting wlan0
* Configuring wireless network for wlan0
* no access points found
* Trying to force preferred in case they are hidden
* Failed to associate with any preferred access points on wlan0
* Couldn't find any access points on wlan0
* Failed to configure wireless for wlan0 [ !! ]
wright neil # dmesg | tail -n30
b43-phy0 debug: Loading firmware version 351.126 (2006-07-29 05:54:02)
b43-phy0 debug: Chip initialized
b43-phy0 debug: 30-bit DMA initialized
b43-phy0 debug: Wireless interface started
b43-phy0 debug: Adding Interface type 2
b43-phy0: Radio turned off by software
b43-phy0 debug: Removing Interface type 2
b43-phy0 debug: Wireless interface stopped
b43-phy0 debug: DMA-32 0x0200 (RX) max used slots: 0/64
b43-phy0 debug: DMA-32 0x02A0 (TX) max used slots: 0/128
b43-phy0 debug: DMA-32 0x0280 (TX) max used slots: 0/128
b43-phy0 debug: DMA-32 0x0260 (TX) max used slots: 0/128
b43-phy0 debug: DMA-32 0x0240 (TX) max used slots: 0/128
b43-phy0 debug: DMA-32 0x0220 (TX) max used slots: 2/128
b43-phy0 debug: DMA-32 0x0200 (TX) max used slots: 0/128
b43-phy0 debug: Loading firmware version 351.126 (2006-07-29 05:54:02)
b43-phy0 debug: Chip initialized
b43-phy0 debug: 30-bit DMA initialized
b43-phy0 debug: Wireless interface started
b43-phy0 debug: Adding Interface type 2
b43-phy0: Radio turned off by software
b43-phy0 debug: Removing Interface type 2
b43-phy0 debug: Wireless interface stopped
b43-phy0 debug: DMA-32 0x0200 (RX) max used slots: 0/64
b43-phy0 debug: DMA-32 0x02A0 (TX) max used slots: 0/128
b43-phy0 debug: DMA-32 0x0280 (TX) max used slots: 0/128
b43-phy0 debug: DMA-32 0x0260 (TX) max used slots: 0/128
b43-phy0 debug: DMA-32 0x0240 (TX) max used slots: 0/128
b43-phy0 debug: DMA-32 0x0220 (TX) max used slots: 2/128
b43-phy0 debug: DMA-32 0x0200 (TX) max used slots: 0/128
|
..so the firmware is loaded and then stopped again.
lordcris wrote: |
then emerge net-wireless/wpa_supplicant and use wpa_gui to join your network. |
When I try wpa_gui it fails to connect to the network, even if I specify the correct essid I'm told "Failed to enable network in wpa_supplicant configuration (could be because I've not got support in the kernel, but haven't checked yet). But this should work with the config I have since it did previously using ndiswrapper to manually insert the module.
Code: |
# wpa_gui
Failed to open control connection to wpa_supplicant.
PING failed - trying to reconnect
PING failed - trying to reconnect
PING failed - trying to reconnect
PING failed - trying to reconnect
PING failed - trying to reconnect
PING failed - trying to reconnect
PING failed - trying to reconnect
PING failed - trying to reconnect
PING failed - trying to reconnect
PING failed - trying to reconnect
PING failed - trying to reconnect
PING failed - trying to reconnect
PING failed - trying to reconnect
PING failed - trying to reconnect
|
Cheers for your help,
slack |
it is not a firmware problem.
it's a configuration problem.
use this guide
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=4&chap=4#doc_chap2
for your card you sould insert
wpa_supplicant_wlan0="-Dwext" # For generic wireless
once net.wlan0 is up you have to run wpa_gui
if you want to use if without wpa_suplicant
just do
Code: | modprobe b43
ifconfig eth0 down
ifconfig wlan0 down
ifconfig wlan0 up
iwconfig wlan0 channel 1 #your channel
iwconfig wlan0 essid your_ssid
dhcpcd -t 30 wlan0 &
|
|
|
Back to top |
|
|
slackline Veteran
Joined: 01 Apr 2005 Posts: 1471 Location: /uk/sheffield
|
Posted: Tue Feb 05, 2008 7:58 am Post subject: |
|
|
lordcris wrote: |
it is not a firmware problem.
it's a configuration problem.
use this guide
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=4&chap=4#doc_chap2
for your card you sould insert
wpa_supplicant_wlan0="-Dwext" # For generic wireless
once net.wlan0 is up you have to run wpa_gui
if you want to use if without wpa_suplicant
just do
Code: | modprobe b43
ifconfig eth0 down
ifconfig wlan0 down
ifconfig wlan0 up
iwconfig wlan0 channel 1 #your channel
iwconfig wlan0 essid your_ssid
dhcpcd -t 30 wlan0 &
|
|
Well the thing is I haven't turned on WPA/WPA2/WEP at all on the router (have been using it for well over three e
years and have never bothered with it, I use MAC filtering and limit the number of DHCPs available), so I don't see why I now need to use WPA to connect (although you do give a manual method for connecting without)?
I don't understand why my /etc/conf.d/net is now seemingly ignored?
Code: |
# more /etc/conf.d/net
# This blank configuration will automatically use DHCP for any net.*
# scripts in /etc/init.d. To create a more complete configuration,
# please review /etc/conf.d/net.example and save your configuration
# in /etc/conf.d/net (this file :]!).
# eth0 - network point (general ethernet)
config_eth0=( "dhcp" )
dhcpcd_eth0="-t 10"
dhcp_eth0="release"
# wlan0 - wireless network card
#
# For configuration details please refer to...
#
# http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?full=1#book_part4
module=( "wireless" )
preferred_aps=( "slack" )
associate_order=( "forceany" )
channel=( "9" )
config_wlan0=( "dhcp" )
dhcpcd_wlan0=( "-t 30" )
dhcp_wlan0=( "release")
|
The thing that stands out for me in dmesg is...
Code: |
b43-phy0: Radio turned off by software
|
How do I find out what software is turning the radio off on the card, since it is after this that the interface is stopped?
Thanks again for your help,
slack |
|
Back to top |
|
|
slackline Veteran
Joined: 01 Apr 2005 Posts: 1471 Location: /uk/sheffield
|
Posted: Tue Feb 05, 2008 8:24 am Post subject: |
|
|
Okay, have configured things to use the wpa_supplicant module and my /etc/conf.d/net now looks like...
Code: |
modules=( "wpa_supplicant" )
preferred_aps=( "slack" )
associate_order=( "forceany" )
channel=( "9" )
config_wlan0=( "dhcp" )
dhcpcd_wlan0=( "-t 30" )
dhcp_wlan0=( "release")
|
but the preferred_aps=( "slack" ) still seems to be ignored since I now get....
Code: |
# /etc/init.d/net.wlan0 start
* Starting wlan0
* Starting wpa_supplicant on wlan0 ...
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported [ ok ]th param 5 value 0x1 -
* Starting wpa_cli on wlan0 ... [ ok ]
* Backgrounding ...
# iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wmaster0 no wireless extensions.
wlan0 IEEE 802.11g ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=off
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
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:0F:1F:43:6B:43
inet addr:192.168.1.104 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:681 errors:0 dropped:0 overruns:0 frame:0
TX packets:623 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:547387 (534.5 Kb) TX bytes:108476 (105.9 Kb)
Interrupt:11
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:122 errors:0 dropped:0 overruns:0 frame:0
TX packets:122 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:8688 (8.4 Kb) TX bytes:8688 (8.4 Kb)
wlan0 Link encap:Ethernet HWaddr 00:90:96:A8:F0:EA
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
wmaster0 Link encap:UNSPEC HWaddr 00-90-96-A8-F0-EA-4C-80-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
|
So a few things
- Some operation is attempted (ioctl?) that isn't supported.
- iwconfig doesn't show any association with the specified access point
- I've never seen the wmaster0 device before (I read url that deleting /etc/udev/rules.d/70-persistent-net.rules might help, which I tried, its been regenerated, but not made any difference).
Which in turn raises the obvious questions...
- Any idea whats failing with regards to the ioctl messages?
- Any ideas why the configuration that I used to use is no longer recognised?
- Can anyone suggest what wmaster0 is and where its come from?
Cheers
slack |
|
Back to top |
|
|
Sodki Guru
Joined: 11 Aug 2003 Posts: 419 Location: London, U.K. & Lisbon, Portugal
|
Posted: Tue Feb 05, 2008 10:51 am Post subject: |
|
|
slack---line wrote: | Well the thing is I haven't turned on WPA/WPA2/WEP at all on the router (have been using it for well over three e
years and have never bothered with it, I use MAC filtering and limit the number of DHCPs available), so I don't see why I now need to use WPA to connect (although you do give a manual method for connecting without)? |
You should really consider using WPA encryption on your wireless router. Mac filtering, hidden SSIDs or WEP can be cracked in less than two minutes. None the less, wpa_supplicant is a great way to configure your wireless connections, even if you don't use WPA. wpa_supplicant is great and supports it all!
Quote: | The thing that stands out for me in dmesg is...
Code: | b43-phy0: Radio turned off by software |
How do I find out what software is turning the radio off on the card, since it is after this that the interface is stopped? |
You have the same problem that I have: your wireless card is off and won't work until it's turned on. I really don't know how to turn my card on on Linux, which makes it unusable. Do you have any switch on your computer that turns the wireless link on and off? |
|
Back to top |
|
|
slackline Veteran
Joined: 01 Apr 2005 Posts: 1471 Location: /uk/sheffield
|
Posted: Tue Feb 05, 2008 11:04 am Post subject: |
|
|
Sodki wrote: |
You should really consider using WPA encryption on your wireless router. Mac filtering, hidden SSIDs or WEP can be cracked in less than two minutes. None the less, wpa_supplicant is a great way to configure your wireless connections, even if you don't use WPA. wpa_supplicant is great and supports it all!
|
Perhaps, but at the end of the day WPA can be cracked (although I believe its by brute force, so it takes longer). I'm not really that bothered, no one round where I live is particularly savvy enough to do stuff. I do regularly (once a week or so) check who's connected to the network and notice the difference if someone is piggybacking and using lots of p2p as my ISP throttle connections if there is high-bandwidth (noticeably when I'm using p2p). Aside form that I use SSH for remote access and all sites where I'm doing anything that requires security use SSL.
No problem with using wpa_supplicant as a module over iwconfig or wireless-tools, it seems to be getting me a bit further anyway
Sodki wrote: |
Quote: | The thing that stands out for me in dmesg is...
You have the same problem that I have: your wireless card is off and won't work until it's turned on. I really don't know how to turn my card on on Linux, which makes it unusable. Do you have any switch on your computer that turns the wireless link on and off? |
|
There are some hotkeys for turning it on, but I've never got round to configuring them at all, so they shouldn't be affecting this.
The thing is that it does seem to start (see the lines from dmesg that preceed the Radio being turned off in th previous messages). |
|
Back to top |
|
|
slackline Veteran
Joined: 01 Apr 2005 Posts: 1471 Location: /uk/sheffield
|
Posted: Thu Feb 07, 2008 2:27 pm Post subject: |
|
|
slack---line wrote: |
The thing is that it does seem to start (see the lines from dmesg that preceed the Radio being turned off in th previous messages). |
I've been playing around with the configuration and currently have...
/etc/wpa_supplicant/wpa_supplicant.conf: |
ap_scan=2
network={
ssid="slack"
bssid=00:0C:41:36:B5:9C
scan_ssid=1
key_mgmt=NONE
priority=-9999999
}
|
/etc/conf.d/net: |
modules=( "wpa_supplicant" )
preferred_aps=( "slack" )
associate_order=( "forceany" )
channel=( "9" )
wpa_supplicant_wlan0="-Dwext"
iwconfig_wlan0="txpower on"
config_wlan0=( "dhcp" )
dhcpcd_wlan0=( "-t 30" )
dhcp_wlan0=( "release")
|
I now have...
iwconfig: |
# iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wmaster0 no wireless extensions.
wlan0 IEEE 802.11g ESSID:"slack"
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=27 dBm
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
|
But can not get things to associate, or even return a list of available access points...
wpa_supplicant: |
# wpa_supplicant -d -Dwext -iwlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf
Initializing interface 'wlan0' conf '/etc/wpa_supplicant/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant/wpa_supplicant.conf' -> '/etc/wpa_supplicant/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant/wpa_supplicant.conf'
ap_scan=2
Priority group -9999999
id=0 ssid='slack'
Initializing interface (2) 'wlan0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf
capabilities: key_mgmt 0xf enc 0xf
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:90:96:a8:f0:ea
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - wpa_driver_wext_set_drop_unencrypted
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - Setting scan request: 0 sec 100000 usec
Added interface wlan0
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
State: DISCONNECTED -> SCANNING
Trying to associate with SSID 'slack'
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: clearing own WPA/RSN IE
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x0 - State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
Setting authentication timeout: 60 sec 0 usec
EAPOL: External notification - portControl=ForceAuthorized
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b1a len=13
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b19 len=8
Received 0 bytes of scan results (0 BSSes)
Scan results: 0
|
I know that my wireless network is working since another laptop can connect and use it fine. The routers site scan also reports four or five other networks broadcasting essid's.
iwlist scan wrote: |
# iwlist scan
lo Interface doesn't support scanning.
eth0 Interface doesn't support scanning.
wmaster0 Interface doesn't support scanning.
wlan0 No scan results
|
Is there something in my configuration that I need to change/add/remove?
Cheers,
slack |
|
Back to top |
|
|
lineagle n00b
Joined: 23 Dec 2007 Posts: 3
|
Posted: Thu Feb 07, 2008 6:36 pm Post subject: Firmware site seems to be down |
|
|
Just a note, it looks like http://linuxwireless.org/en/users/Drivers/bcm43xx is down. This is not a problem for me as I have already extracted the firmware for my driver on another partition. However I thought I'd let everyone else know . |
|
Back to top |
|
|
akub Tux's lil' helper
Joined: 03 Aug 2004 Posts: 123 Location: Poland, Olkusz/Gliwice
|
Posted: Sun Feb 10, 2008 2:44 pm Post subject: |
|
|
i don't know what is happening i read that bcm4306 is fully supported but it isn't, bcm4318 was better supported under bcm43xx rather than bcm4306 in b43
kernel 2.6.24.1
Code: |
akub jakub # lspci -n | grep 14e4:43
03:00.0 0280: 14e4:4320 (rev 03)
|
and dmesg:
Code: |
pccard: CardBus card inserted into slot 0
PCI: Enabling device 0000:03:00.0 (0000 -> 0002)
ACPI: PCI Interrupt 0000:03:00.0[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
PCI: Setting latency timer of device 0000:03:00.0 to 64
b43-phy2: Broadcom 4306 WLAN found
b43-phy2 debug: Found PHY: Analog 2, Type 2, Revision 2
b43-phy2 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2
b43-phy2 debug: DebugFS (CONFIG_DEBUG_FS) not enabled in kernel config
phy2: Selected rate control algorithm 'simple'
ssb: Sonics Silicon Backplane found on PCI device 0000:03:00.0
b43-phy2 debug: Loading firmware version 351.126 (2006-07-29 05:54:02)
b43-phy2 debug: Chip initialized
b43-phy2 debug: 30-bit DMA initialized
b43-phy2 debug: Wireless interface started
b43-phy2 debug: Adding Interface type 2
|
network is very unstable when I go to another room (about 8m from router) net is dead
ping to router take way too long from 3ms to 730ms!
greets _________________ http://gps-y.pl/
http://goralevent.pl/
Last edited by akub on Fri Apr 18, 2008 12:28 pm; edited 1 time in total |
|
Back to top |
|
|
slackline Veteran
Joined: 01 Apr 2005 Posts: 1471 Location: /uk/sheffield
|
Posted: Wed Feb 13, 2008 7:52 am Post subject: |
|
|
Well, I seem to have resolved this myself.
I decided to try going back to using iwconfig to configure the card as I had originally with ndiswrapper inserting the module.
What do you know it worked! Goodbye ndiswrapper
lsmod: |
# lsmod
Module Size Used by
snd_seq 44336 0
snd_pcm_oss 34336 0
snd_mixer_oss 14016 1 snd_pcm_oss
snd_intel8x0 28124 0
snd_ac97_codec 95268 1 snd_intel8x0
ac97_bus 1664 1 snd_ac97_codec
snd_pcm 63176 3 snd_pcm_oss,snd_intel8x0,snd_ac97_codec
snd_timer 18628 2 snd_seq,snd_pcm
snd_page_alloc 7496 2 snd_intel8x0,snd_pcm
b43 132964 0
|
dmesg: |
b43-phy0 debug: Loading firmware version 351.126 (2006-07-29 05:54:02)
b43-phy0 debug: Chip initialized
b43-phy0 debug: 30-bit DMA initialized
b43-phy0 debug: Wireless interface started
b43-phy0 debug: Adding Interface type 2
ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:0c:41:36:b5:9c
wlan0: RX authentication from 00:0c:41:36:b5:9c (alg=0 transaction=2 status=0)
wlan0: authenticated
wlan0: associate with AP 00:0c:41:36:b5:9c
wlan0: RX AssocResp from 00:0c:41:36:b5:9c (capab=0x401 status=0 aid=1)
wlan0: associated
wlan0: switched to short barker preamble (BSSID=00:0c:41:36:b5:9c)
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:0c:41:36:b5:9c
wlan0: RX authentication from 00:0c:41:36:b5:9c (alg=0 transaction=2 status=0)
wlan0: authenticated
wlan0: associate with AP 00:0c:41:36:b5:9c
wlan0: RX ReassocResp from 00:0c:41:36:b5:9c (capab=0x401 status=0 aid=1)
wlan0: associated
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:0c:41:36:b5:9c
wlan0: RX authentication from 00:0c:41:36:b5:9c (alg=0 transaction=2 status=0)
wlan0: authenticated
wlan0: associate with AP 00:0c:41:36:b5:9c
wlan0: RX ReassocResp from 00:0c:41:36:b5:9c (capab=0x401 status=0 aid=1)
wlan0: associated
wlan0: no IPv6 routers present
|
/etc/conf.d/net: |
# wlan0 - wireless network card
#
# For configuration details please refer to...
#
# http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?full=1#book_part4
module=( "wireless" )
config_AP=( "00:0C:41:36:B5:9C" )
config_ESSID=( "slack" )
preferred_aps=( "slack" )
associate_order=( "forceany" )
channel=( "9" )
iwconfig_wlan0="txpower on"
config_wlan0=( "dhcp" )
dhcpcd_wlan0=( "-t 30" )
dhcp_wlan0=( "release")
|
|
|
Back to top |
|
|
Sedrik l33t
Joined: 08 Apr 2005 Posts: 655 Location: Uppsala, Sweden
|
Posted: Fri Feb 15, 2008 9:20 am Post subject: |
|
|
Hi all
For some reason my card if called wlan0_rename is this normal? How can I fix this, udev is sad and tells me that my system has problem assigning persistent names for it :/ _________________ From Gentoo with love |
|
Back to top |
|
|
ONEEYEMAN Advocate
Joined: 01 Mar 2005 Posts: 3613
|
Posted: Sun Feb 17, 2008 7:27 pm Post subject: |
|
|
JoseJX,
Thank you for keep working on this.
I have a question after all those quietness from me...
The instruction update indicates that I need to use 2.6.24. Is it refers to the gentoo- or vanilla-sources?
The current x86-stable kernel is 2.6.23-gentoo-r8. Is all that apply here?
Thank you. |
|
Back to top |
|
|
Sodki Guru
Joined: 11 Aug 2003 Posts: 419 Location: London, U.K. & Lisbon, Portugal
|
Posted: Sun Feb 17, 2008 7:54 pm Post subject: |
|
|
ONEEYEMAN wrote: | The instruction update indicates that I need to use 2.6.24. Is it refers to the gentoo- or vanilla-sources? |
Any 2.6.24 kernel package will do, either vanilla-sources or gentoo-sources. |
|
Back to top |
|
|
JoseJX Retired Dev
Joined: 28 Apr 2002 Posts: 2774
|
Posted: Sun Feb 17, 2008 11:54 pm Post subject: |
|
|
Sedrik wrote: | Hi all
For some reason my card if called wlan0_rename is this normal? How can I fix this, udev is sad and tells me that my system has problem assigning persistent names for it :/ |
You can fix this by updating your udev rules. Simply delete /etc/udev/rules.d/70-persistent-net.rules and let udev rebuild this file. _________________ Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml |
|
Back to top |
|
|
lordcris Apprentice
Joined: 09 Jul 2002 Posts: 248
|
Posted: Mon Feb 18, 2008 1:41 pm Post subject: |
|
|
Code: | wlan0 IEEE 802.11g ESSID:"lordcrisN1"
Mode:Managed Frequency:2.412 GHz Access Point: 00:17:3F:3B:65:9E
Bit Rate=1 Mb/s Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Encryption key:73FE-AE53-AAAA-462B-7777-150D-AAAA-149A-3E79-CCCC-B49E-87E2-AAAA-BCD6-0802-AAAA [2]
Link Quality=94/100 Signal level=-55 dBm Noise level=-69 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0 |
hello,
is it ok to have bitrate of only 1 MB/s?
thank you |
|
Back to top |
|
|
Danger7789 n00b
Joined: 18 Feb 2008 Posts: 12
|
Posted: Mon Feb 18, 2008 3:10 pm Post subject: |
|
|
so i've been trying to get my wireless working on my new gentoo install for the past dayish. my card is a bcm4318 and is such a pain in linux ...
ok so i managed to follow these instructions and not get any bad output from the commands. my question is now what do i do? it doesn't seem to have activated my wireless card in either iwconfig or ifconfig ... am i missing something?
here's a bunch of system information...
uname -a:
Code: |
Linux patrik-gentoo 2.6.24-gentoo-r2 #4 SMP Sun Feb 17 23:35:34 EST 2008 i686 AMD Athlon(tm) 64 Processor 3500+ AuthenticAMD GNU/Linux
|
dmesg:
Code: |
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 264k freed
Linux agpgart interface v0.102
b43-phy0: Broadcom 4318 WLAN found
b43-phy0 debug: Found PHY: Analog 3, Type 2, Revision 7
b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 8
phy0: Selected rate control algorithm 'simple'
phy0: Failed to initialize wep
b43: probe of ssb0:0 failed with error -12
EXT3 FS on hda2, internal journal
Adding 979956k swap on /dev/hda3. Priority:-1 extents:1 across:979956k
eth0: link down
ADDRCONF(NETDEV_UP): eth0: link is not ready
|
ifconfig:
Code: |
eth0 Link encap:Ethernet HWaddr 00:0F:B0:BF:8D:6A
inet addr:169.254.223.81 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:18 Base address:0x6400
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
|
iwconfig:
Code: |
lo no wireless extensions.
eth0 no wireless extensions.
sit0 no wireless extensions.
|
i used the following versions of b43-fwcutter-011 and broadcom-wl-4.80.53.0 and followed the instructions under "You are using the b43 driver from linux-2.6.24" on the page http://linuxwireless.org/en/users/Drivers/bcm43xx.
the eth0 is my wired network and works fine when plugged into my router, but i'm on a laptop and wireless just makes sence. also eth0 fails in dmesg because i wasn't plugged in when i booted ... and i have no idea what sit0 is, maybe this is what was enabled?
any tips? thanks
Danger |
|
Back to top |
|
|
gringo Advocate
Joined: 27 Apr 2003 Posts: 3793
|
Posted: Mon Feb 18, 2008 4:06 pm Post subject: |
|
|
@Danger7789 : i´d say the interface isn´t up or maybe just not configured correctly, check with ifconfig -a.
cheers _________________ Error: Failing not supported by current locale |
|
Back to top |
|
|
Danger7789 n00b
Joined: 18 Feb 2008 Posts: 12
|
Posted: Mon Feb 18, 2008 5:09 pm Post subject: |
|
|
ifconfig -a spits out what it did before along with an entry for sit0, which i've included by copying lo and changing relavent parts as i'm posting from my desktop.
Code: |
sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
|
a few things to note are that there were no options for 'Enable LED triggers' or 'Broadcom 43xx PCMCIA device support' when i was configuring my kernel. My laptop does have an LED that shows that the hardware is on, is does not light up in gentoo. i had the same problem using ndiswrapper in ubuntu. i had to boot into my windows partition to enable the card and reboot into linux. this time however, having the light enabled for the card seems to be having no effect.
i'm going to do a bit of poking around in the kernel to try and enable the PCMCIA option. found the LED triggers option just now, must have just missed that one.
Danger |
|
Back to top |
|
|
Danger7789 n00b
Joined: 18 Feb 2008 Posts: 12
|
Posted: Mon Feb 18, 2008 5:21 pm Post subject: |
|
|
ya the PCMCIA option for the BCM43xx driver support only shows when the
Bus options --->
<*> PCCARD (PCMCIA/CardBus) support
is set.
recompiling kernel right now, be back shortly.
EDIT:
nope, didn't seem to change any of the results i've posted before.
ideas?
oh and can anyone clarify these to lines in the dmesg output?
Code: |
phy0: Failed to initialize wep
b43: probe of ssb0:0 failed with error -12
|
Danger |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|