Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Native Airport Extreme Drivers
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3 ... 38, 39, 40, 41, 42  Next  
This topic is locked: you cannot edit posts or make replies.    Gentoo Forums Forum Index Gentoo on PPC
View previous topic :: View next topic  
Author Message
XenoTerraCide
Veteran
Veteran


Joined: 18 Jan 2004
Posts: 1418
Location: MI, USA

PostPosted: Wed Jan 31, 2007 2:05 am    Post subject: Reply with quote

apologies if this was previously answered. I actually saw an answer for it on page 2 but I think it is out of date.

Code:
bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed.
bcm43xx: core_up for active 802.11 core failed (-2)
bcm43xx: Microcode rev 0x15f, pl 0x7e (2006-07-29  05:54:02)
bcm43xx: Firmware: no support for microcode extracted from version 4.x binary drivers.
bcm43xx: core_up for active 802.11 core failed (-95)
bcm43xx: Microcode rev 0x15f, pl 0x7e (2006-07-29  05:54:02)
bcm43xx: Firmware: no support for microcode extracted from version 4.x binary drivers.
bcm43xx: core_up for active 802.11 core failed (-95)
bcm43xx: Microcode rev 0x15f, pl 0x7e (2006-07-29  05:54:02)
bcm43xx: Firmware: no support for microcode extracted from version 4.x binary drivers.
bcm43xx: core_up for active 802.11 core failed (-95)
someone solved this on page 2 by rebuilding hotplug but aren't the hotplug and coldplug scripts deprecated? I thought udev handles them now so they don't need to be run? secondly I have an HP Pavillion zv6000 I know it has a PCIE bus but I don't know if this card is on it. if is (or there's a chance that that's the problem) should I grab 2.6.20-rc6 kernel, or patch gentoo-sources 2.6.19-r5?

I have the 4318.
_________________
I don't hang out here anymore, try asking on http://unix.stackexchange.com/ if you want my help.
Back to top
View user's profile Send private message
JoseJX
Developer
Developer


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Wed Jan 31, 2007 3:39 am    Post subject: Reply with quote

No, it's not related to hotplug or udev. As the error message states, you cut your firmware from a v4 driver. Since you are using the SoftMAC driver, you need to use a v3 driver.

You can get the correct firmware from here: http://bu3sch.de/bcm43xx_fw.php

If you have a 4318, it's a regular PCI card. All of the PCI-E cards are 4311 or 4312's.
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
Back to top
View user's profile Send private message
XenoTerraCide
Veteran
Veteran


Joined: 18 Jan 2004
Posts: 1418
Location: MI, USA

PostPosted: Wed Jan 31, 2007 4:37 am    Post subject: Reply with quote

thx. easy fix. easy mistake. ;) works now. I appreciate your hard work and your willingness to be helpful.
_________________
I don't hang out here anymore, try asking on http://unix.stackexchange.com/ if you want my help.
Back to top
View user's profile Send private message
XenoTerraCide
Veteran
Veteran


Joined: 18 Jan 2004
Posts: 1418
Location: MI, USA

PostPosted: Wed Jan 31, 2007 6:38 am    Post subject: Reply with quote

I had it partially working, could list AP's but I don't not sure that I could connect. now all I get is a crash...
Code:
bcm43xx: Chip initialized
bcm43xx: 32-bit DMA initialized
bcm43xx: Keys cleared
bcm43xx: Selected 802.11 core (phytype 2)
bcm43xx: ASSERTION FAILED (radio_attenuation < 10) at: drivers/net/wireless/bcm43xx/bcm43xx_phy                                               .c:1496:bcm43xx_find_lopair()
bcm43xx: WARNING: Writing invalid LOpair (low: -72, high: -20, index: 120)
 [<f907a264>] bcm43xx_phy_lo_adjust+0x94/0x290 [bcm43xx]
 [<f907ab09>] bcm43xx_phy_lo_g_measure+0x6a9/0xd00 [bcm43xx]
 [<f906a2fe>] bcm43xx_shm_read32+0x2e/0xd0 [bcm43xx]
 [<f907d600>] bcm43xx_power_saving_ctl_bits+0x60/0x70 [bcm43xx]
 [<f906edab>] bcm43xx_periodic_work_handler+0x18b/0x440 [bcm43xx]
 [<c04ba6cb>] schedule+0x2bb/0x660
 [<c012a9d5>] run_workqueue+0x85/0x120
 [<f906ec20>] bcm43xx_periodic_work_handler+0x0/0x440 [bcm43xx]
 [<c012b05b>] worker_thread+0x11b/0x140
 [<c0116dc0>] default_wake_function+0x0/0x10
 [<c012af40>] worker_thread+0x0/0x140
 [<c012dcd4>] kthread+0xe4/0xf0
 [<c012dbf0>] kthread+0x0/0xf0
 [<c0103ae7>] kernel_thread_helper+0x7/0x10
 =======================
bcm43xx: Radio turned off
bcm43xx: DMA-32 0x0200 (RX) max used slots: 1/64
bcm43xx: DMA-32 0x02A0 (TX) max used slots: 0/512
bcm43xx: DMA-32 0x0280 (TX) max used slots: 0/512
bcm43xx: DMA-32 0x0260 (TX) max used slots: 0/512
bcm43xx: DMA-32 0x0240 (TX) max used slots: 0/512
bcm43xx: DMA-32 0x0220 (TX) max used slots: 1/512
bcm43xx: DMA-32 0x0200 (TX) max used slots: 0/512
bcm43xx: IRQ_READY timeout
bcm43xx: core_up for active 802.11 core failed (-19)
means nothing to me other than broken. whenever I try to bring eth1 up I get
Code:
SIOCSIFFLAGS: No such device

_________________
I don't hang out here anymore, try asking on http://unix.stackexchange.com/ if you want my help.
Back to top
View user's profile Send private message
JoseJX
Developer
Developer


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Sat Feb 03, 2007 1:47 am    Post subject: Reply with quote

That's not a crash, it's an assertion because the driver doesn't really support all card versions yet. It's really just a warning and something that the developers can use to find issues.

These lines:
bcm43xx: IRQ_READY timeout
bcm43xx: core_up for active 802.11 core failed (-19)

Indicate that something went wrong with the card, the easiest way to fix it is to reboot the machine. Does it work after rebooting?
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
Back to top
View user's profile Send private message
XenoTerraCide
Veteran
Veteran


Joined: 18 Jan 2004
Posts: 1418
Location: MI, USA

PostPosted: Sat Feb 03, 2007 4:28 am    Post subject: Reply with quote

well... it works sometimes, sometimes it doesn't.
_________________
I don't hang out here anymore, try asking on http://unix.stackexchange.com/ if you want my help.
Back to top
View user's profile Send private message
morbidi
n00b
n00b


Joined: 25 Dec 2002
Posts: 12

PostPosted: Sat Feb 03, 2007 4:07 pm    Post subject: Reply with quote

XenoTerraCide, what is your card version ? mine is 20 and the 3.xx version of the firmware works really fine :) I'm using it right now :)
_________________
Some Say Why, Others Say, Why not
Back to top
View user's profile Send private message
b.libbey
n00b
n00b


Joined: 19 Sep 2006
Posts: 39
Location: Canada

PostPosted: Sun Feb 04, 2007 6:29 am    Post subject: Reply with quote

I have 32-bit Windows and 64-bit Gentoo. Will the Windows driver work in Gentoo? If not, which should I use?
Back to top
View user's profile Send private message
JoseJX
Developer
Developer


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Sun Feb 04, 2007 11:23 pm    Post subject: Reply with quote

The driver firmware is platform independent. Use the firmware in the link I posted above.
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
Back to top
View user's profile Send private message
XenoTerraCide
Veteran
Veteran


Joined: 18 Jan 2004
Posts: 1418
Location: MI, USA

PostPosted: Mon Feb 05, 2007 12:25 am    Post subject: Reply with quote

sorry for taking so long to reply. it's revision 02. I've switched to OpenSuse temporarily on my laptop though. Need to learn more about "RPM based distro's".
_________________
I don't hang out here anymore, try asking on http://unix.stackexchange.com/ if you want my help.
Back to top
View user's profile Send private message
JoseJX
Developer
Developer


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Wed Feb 07, 2007 2:10 am    Post subject: Reply with quote

If you have a 4311 or 4312 please test this patch, it should improve performance on your card:
https://lists.berlios.de/pipermail/bcm43xx-dev/2007-February/003808.html
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
Back to top
View user's profile Send private message
mayday147
l33t
l33t


Joined: 22 Mar 2004
Posts: 825
Location: Bucharest, Romania

PostPosted: Thu Feb 08, 2007 6:40 pm    Post subject: Reply with quote

I have a Broadcom 4318 card and I cannot connect it in any way. I have an "Open" wireless connection. These are my logs:

Code:

localhost mayday # ls /lib/firmware/
bcm43xx_initval01.fw  bcm43xx_initval05.fw  bcm43xx_initval09.fw    bcm43xx_microcode4.fw
bcm43xx_initval02.fw  bcm43xx_initval06.fw  bcm43xx_initval10.fw    bcm43xx_microcode5.fw
bcm43xx_initval03.fw  bcm43xx_initval07.fw  bcm43xx_microcode11.fw  bcm43xx_pcm4.fw
bcm43xx_initval04.fw  bcm43xx_initval08.fw  bcm43xx_microcode2.fw   bcm43xx_pcm5.fw
localhost mayday # rmmod bcm43xx
localhost mayday # modprobe bcm43xx
localhost mayday # ifconfig eth1 up
localhost mayday # iwlist eth1 scan
eth1      No scan results
localhost mayday # iwconfig eth1 channel auto
Error for wireless request "Set Frequency" (8B04) :
    SET failed on device eth1 ; Invalid argument.
localhost mayday # iwconfig eth1 enc open
localhost mayday # iwconfig eth1 essid WiFi
localhost mayday # iwconfig eth1
eth1      IEEE 802.11b/g  ESSID:"WiFi"  Nickname:"Broadcom 4318"
          Mode:Managed  Frequency=2.484 GHz  Access Point: Invalid
          Bit Rate=1 Mb/s   Tx-Power=15 dBm
          RTS thr:off   Fragment thr:off
          Encryption key:0000-0000-0000-0000-0000-0000-00   Security mode:open
          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

localhost mayday #


Code:
dmesg

bcm43xx: ASSERTION FAILED (radio_attenuation < 10) at: drivers/net/wireless/bcm43xx/bcm43xx_phy.c:1496:bcm43xx_find_lopair()bcm43xx: WARNING: Writing invalid LOpair (low: -64, high: -89, index: 120)
 [<c01030db>] dump_trace+0x69/0x1b2
 [<c010323c>] show_trace_log_lvl+0x18/0x2c
 [<c010379f>] show_trace+0xf/0x11
 [<c01037d7>] dump_stack+0x15/0x17
 [<d89414ef>] bcm43xx_phy_lo_adjust+0x1e8/0x227 [bcm43xx]
 [<d89412e5>] bcm43xx_phy_init_pctl+0x202/0x224 [bcm43xx]
 [<d8943f48>] bcm43xx_phy_initg+0xcb7/0xd29 [bcm43xx]
 [<d8945018>] bcm43xx_phy_init+0x629/0x647 [bcm43xx]
 [<d8935ac8>] bcm43xx_chip_init+0x743/0xa3c [bcm43xx]
 [<d89371ce>] wireless_core_up+0x1ae/0x6b9 [bcm43xx]
 [<d8937a43>] bcm43xx_select_wireless_core+0x36a/0x4e5 [bcm43xx]
 [<d8937cad>] bcm43xx_init_board+0x46/0x108 [bcm43xx]
 [<c039a189>] dev_open+0x2a/0x60
 [<c0398e16>] dev_change_flags+0x47/0xe4
 [<c03c847a>] devinet_ioctl+0x251/0x557
 [<c0390acf>] sock_ioctl+0x19c/0x1c0
 [<c0150d91>] do_ioctl+0x19/0x4d
 [<c0150fc9>] vfs_ioctl+0x204/0x21b
 [<c0151013>] sys_ioctl+0x33/0x4c
 [<c0102afd>] sysenter_past_esp+0x56/0x79
 [<b7fd8410>] 0xb7fd8410
 =======================
bcm43xx: Chip initialized
bcm43xx: 32-bit DMA initialized
bcm43xx: Keys cleared
bcm43xx: Selected 802.11 core (phytype 2)
bcm43xx: ASSERTION FAILED (radio_attenuation < 10) at: drivers/net/wireless/bcm43xx/bcm43xx_phy.c:1496:bcm43xx_find_lopair()bcm43xx: WARNING: Writing invalid LOpair (low: -64, high: -89, index: 120)
 [<c01030db>] dump_trace+0x69/0x1b2
 [<c010323c>] show_trace_log_lvl+0x18/0x2c
 [<c010379f>] show_trace+0xf/0x11
 [<c01037d7>] dump_stack+0x15/0x17
 [<d89414ef>] bcm43xx_phy_lo_adjust+0x1e8/0x227 [bcm43xx]
 [<d8942364>] bcm43xx_phy_lo_g_measure+0x93d/0xb29 [bcm43xx]
 [<d8938845>] bcm43xx_periodic_work_handler+0x13a/0x320 [bcm43xx]
 [<c0120ffb>] run_workqueue+0x6f/0xa2
 [<c01214b8>] worker_thread+0xe8/0x118
 [<c0123619>] kthread+0xad/0xd8
 [<c0102e2f>] kernel_thread_helper+0x7/0x10
 =======================
ADDRCONF(NETDEV_UP): eth1: link is not ready
bcm43xx: set security called, .level = 0, .enabled = 0, .encrypt = 0
bcm43xx: set security called, .level = 0, .enabled = 0, .encrypt = 0
bcm43xx: set security called, .level = 0, .enabled = 0, .encrypt = 0
bcm43xx: set security called, .level = 0, .enabled = 0, .encrypt = 0
SoftMAC: Start scanning with channel: 1
SoftMAC: Scanning 14 channels

_________________
gentoo.ro
Back to top
View user's profile Send private message
JoseJX
Developer
Developer


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Thu Feb 08, 2007 7:35 pm    Post subject: Reply with quote

Please enable SoftMAC debugging so we can see where it's failing.
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
Back to top
View user's profile Send private message
mayday147
l33t
l33t


Joined: 22 Mar 2004
Posts: 825
Location: Bucharest, Romania

PostPosted: Thu Feb 08, 2007 9:19 pm    Post subject: Reply with quote

SoftMAC debugging was enabled. Here is dmesg after "rmmod" and "modprobe" bcm43xx:
Code:

#dmesg
bcm43xx driver
ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10
bcm43xx: Chip ID 0x4318, rev 0x2
bcm43xx: Number of cores: 4
bcm43xx: Core 0: ID 0x800, rev 0xd, vendor 0x4243, enabled
bcm43xx: Core 1: ID 0x812, rev 0x9, vendor 0x4243, enabled
bcm43xx: Core 2: ID 0x804, rev 0xc, vendor 0x4243, enabled
bcm43xx: Core 3: ID 0x80d, rev 0x7, vendor 0x4243, enabled
bcm43xx: PHY connected
bcm43xx: Detected PHY: Version: 3, Type 2, Revision 7
bcm43xx: Detected Radio: ID: 8205017f (Manuf: 17f Ver: 2050 Rev: 8)
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: ASSERTION FAILED (radio_attenuation < 10) at: drivers/net/wireless/bcm43xx/bcm43xx_phy.c:1496:bcm43xx_find_lopair()
bcm43xx: WARNING: Writing invalid LOpair (low: 127, high: 69, index: 120)
 [<c01030db>] dump_trace+0x69/0x1b2
 [<c010323c>] show_trace_log_lvl+0x18/0x2c
 [<c010379f>] show_trace+0xf/0x11
 [<c01037d7>] dump_stack+0x15/0x17
 [<d89274ef>] bcm43xx_phy_lo_adjust+0x1e8/0x227 [bcm43xx]
 [<d892915d>] bcm43xx_phy_initb6+0x6c6/0x7fa [bcm43xx]
 [<d892933b>] bcm43xx_phy_initg+0xaa/0xd29 [bcm43xx]
 [<d892b018>] bcm43xx_phy_init+0x629/0x647 [bcm43xx]
 [<d891bac8>] bcm43xx_chip_init+0x743/0xa3c [bcm43xx]
 [<d891d1ce>] wireless_core_up+0x1ae/0x6b9 [bcm43xx]
 [<d891da43>] bcm43xx_select_wireless_core+0x36a/0x4e5 [bcm43xx]
 [<d891dcad>] bcm43xx_init_board+0x46/0x108 [bcm43xx]
 [<c039b3e9>] dev_open+0x2a/0x60
 [<c039a076>] dev_change_flags+0x47/0xe4
 [<c03c8d2a>] devinet_ioctl+0x251/0x557
 [<c0391d9f>] sock_ioctl+0x19c/0x1c0
 [<c0150d91>] do_ioctl+0x19/0x4d
 [<c0150fc9>] vfs_ioctl+0x204/0x21b
 [<c0151013>] sys_ioctl+0x33/0x4c
 [<c0102afd>] sysenter_past_esp+0x56/0x79
 [<b7fa6410>] 0xb7fa6410
 =======================
bcm43xx: ASSERTION FAILED (radio_attenuation < 10) at: drivers/net/wireless/bcm43xx/bcm43xx_phy.c:1496:bcm43xx_find_lopair()
bcm43xx: WARNING: Writing invalid LOpair (low: 127, high: 69, index: 120)
 [<c01030db>] dump_trace+0x69/0x1b2
 [<c010323c>] show_trace_log_lvl+0x18/0x2c
 [<c010379f>] show_trace+0xf/0x11
 [<c01037d7>] dump_stack+0x15/0x17
 [<d89274ef>] bcm43xx_phy_lo_adjust+0x1e8/0x227 [bcm43xx]
 [<d8929e69>] bcm43xx_phy_initg+0xbd8/0xd29 [bcm43xx]
 [<d892b018>] bcm43xx_phy_init+0x629/0x647 [bcm43xx]
 [<d891bac8>] bcm43xx_chip_init+0x743/0xa3c [bcm43xx]
 [<d891d1ce>] wireless_core_up+0x1ae/0x6b9 [bcm43xx]
 [<d891da43>] bcm43xx_select_wireless_core+0x36a/0x4e5 [bcm43xx]
 [<d891dcad>] bcm43xx_init_board+0x46/0x108 [bcm43xx]
 [<c039b3e9>] dev_open+0x2a/0x60
 [<c039a076>] dev_change_flags+0x47/0xe4
 [<c03c8d2a>] devinet_ioctl+0x251/0x557
 [<c0391d9f>] sock_ioctl+0x19c/0x1c0
 [<c0150d91>] do_ioctl+0x19/0x4d
 [<c0150fc9>] vfs_ioctl+0x204/0x21b
 [<c0151013>] sys_ioctl+0x33/0x4c
 [<c0102afd>] sysenter_past_esp+0x56/0x79
 [<b7fa6410>] 0xb7fa6410
 =======================
bcm43xx: ASSERTION FAILED (radio_attenuation < 10) at: drivers/net/wireless/bcm43xx/bcm43xx_phy.c:1496:bcm43xx_find_lopair()
bcm43xx: WARNING: Writing invalid LOpair (low: 127, high: 69, index: 120)
 [<c01030db>] dump_trace+0x69/0x1b2
 [<c010323c>] show_trace_log_lvl+0x18/0x2c
 [<c010379f>] show_trace+0xf/0x11
 [<c01037d7>] dump_stack+0x15/0x17
 [<d89274ef>] bcm43xx_phy_lo_adjust+0x1e8/0x227 [bcm43xx]
 [<d89272e5>] bcm43xx_phy_init_pctl+0x202/0x224 [bcm43xx]
 [<d8929f48>] bcm43xx_phy_initg+0xcb7/0xd29 [bcm43xx]
 [<d892b018>] bcm43xx_phy_init+0x629/0x647 [bcm43xx]
 [<d891bac8>] bcm43xx_chip_init+0x743/0xa3c [bcm43xx]
 [<d891d1ce>] wireless_core_up+0x1ae/0x6b9 [bcm43xx]
 [<d891da43>] bcm43xx_select_wireless_core+0x36a/0x4e5 [bcm43xx]
 [<d891dcad>] bcm43xx_init_board+0x46/0x108 [bcm43xx]
 [<c039b3e9>] dev_open+0x2a/0x60
 [<c039a076>] dev_change_flags+0x47/0xe4
 [<c03c8d2a>] devinet_ioctl+0x251/0x557
 [<c0391d9f>] sock_ioctl+0x19c/0x1c0
 [<c0150d91>] do_ioctl+0x19/0x4d
 [<c0150fc9>] vfs_ioctl+0x204/0x21b
 [<c0151013>] sys_ioctl+0x33/0x4c
 [<c0102afd>] sysenter_past_esp+0x56/0x79
 [<b7fa6410>] 0xb7fa6410
 =======================
bcm43xx: Chip initialized
bcm43xx: 32-bit DMA initialized
bcm43xx: Keys cleared
bcm43xx: Selected 802.11 core (phytype 2)
bcm43xx: ASSERTION FAILED (radio_attenuation < 10) at: drivers/net/wireless/bcm43xx/bcm43xx_phy.c:1496:bcm43xx_find_lopair()
bcm43xx: WARNING: Writing invalid LOpair (low: 127, high: 69, index: 120)
 [<c01030db>] dump_trace+0x69/0x1b2
 [<c010323c>] show_trace_log_lvl+0x18/0x2c
 [<c010379f>] show_trace+0xf/0x11
 [<c01037d7>] dump_stack+0x15/0x17
 [<d89274ef>] bcm43xx_phy_lo_adjust+0x1e8/0x227 [bcm43xx]
 [<d8928364>] bcm43xx_phy_lo_g_measure+0x93d/0xb29 [bcm43xx]
 [<d891e845>] bcm43xx_periodic_work_handler+0x13a/0x320 [bcm43xx]
 [<c0120ffb>] run_workqueue+0x6f/0xa2
 [<c01214b8>] worker_thread+0xe8/0x118
 [<c0123619>] kthread+0xad/0xd8
 [<c0102e2f>] kernel_thread_helper+0x7/0x10
 =======================
bcm43xx: set security called, .level = 0, .enabled = 0, .encrypt = 0
bcm43xx: set security called, .level = 0, .enabled = 0, .encrypt = 0
bcm43xx: set security called, .level = 0, .enabled = 0, .encrypt = 0
bcm43xx: set security called, .level = 0, .enabled = 0, .encrypt = 0
SoftMAC: Start scanning with channel: 1
SoftMAC: Scanning 14 channels
SoftMAC: Scanning finished

Code:

#ifconfig eth1 down
#ifconfig eth1 up
SIOCSIFFLAGS: No such device


Code:

#dmesg
SoftMAC: Scanning 14 channels
SoftMAC: Scanning finished
SoftMAC: Start scanning with channel: 1
SoftMAC: Scanning 14 channels
SoftMAC: Scanning finished
SoftMAC: Start scanning with channel: 1
SoftMAC: Scanning 14 channels
SoftMAC: Scanning finished
bcm43xx: Radio turned off
bcm43xx: DMA-32 0x0200 (RX) max used slots: 0/64
bcm43xx: DMA-32 0x02A0 (TX) max used slots: 0/512
bcm43xx: DMA-32 0x0280 (TX) max used slots: 0/512
bcm43xx: DMA-32 0x0260 (TX) max used slots: 0/512
bcm43xx: DMA-32 0x0240 (TX) max used slots: 0/512
bcm43xx: DMA-32 0x0220 (TX) max used slots: 252/512
bcm43xx: DMA-32 0x0200 (TX) max used slots: 0/512
bcm43xx: IRQ_READY timeout
bcm43xx: core_up for active 802.11 core failed (-19)


Is there any chance to be an IRQ conflict? I changed one PCI slot already and still the same, but if it looks like an IRQ conflict I could change with one slot on a time.
_________________
gentoo.ro
Back to top
View user's profile Send private message
JoseJX
Developer
Developer


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Fri Feb 09, 2007 3:08 am    Post subject: Reply with quote

You need this patch:
https://lists.berlios.de/pipermail/bcm43xx-dev/2007-February/003796.html
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
Back to top
View user's profile Send private message
mayday147
l33t
l33t


Joined: 22 Mar 2004
Posts: 825
Location: Bucharest, Romania

PostPosted: Fri Feb 09, 2007 7:58 am    Post subject: Reply with quote

I used that patch but still the same problem.
BTW I don't know if I patched correctly: I modified only the "#define BCM43xx_IRQWAIT_MAX_RETRIES 50" in the kernel source (2.6.19.2) and then recompiled the kernel. Is this correct?
_________________
gentoo.ro
Back to top
View user's profile Send private message
JoseJX
Developer
Developer


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Fri Feb 09, 2007 8:15 am    Post subject: Reply with quote

Yes, it should be changed to 100. Can you try setting it to 1000 and also apply this patch?
https://lists.berlios.de/pipermail/bcm43xx-dev/2007-February/003821.html

I would like to see how many times it takes for your card to come back. Try to see if you can reproduce the IRQ problem and then tell me how many cycles it took each time you tried.
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
Back to top
View user's profile Send private message
mayday147
l33t
l33t


Joined: 22 Mar 2004
Posts: 825
Location: Bucharest, Romania

PostPosted: Fri Feb 09, 2007 1:46 pm    Post subject: Reply with quote

Still the same.
Code:

bcm43xx: It took 17 tries to set IRQ_READY
bcm43xx: Microcode rev 0x127, pl 0xe (2005-04-18  02:36:27)
bcm43xx: Radio turned on
bcm43xx: ASSERTION FAILED (radio_attenuation < 10) at: drivers/net/wireless/bcm43xx/bcm43xx_phy.c:1496:bcm43xx_find_lopair()bcm43xx: ASSERTION FAILED (radio_attenuation < 10) at: drivers/net/wireless/bcm43xx/bcm43xx_phy.c:1496:bcm43xx_find_lopair()bcm43xx: ASSERTION FAILED (radio_attenuation < 10) at: drivers/net/wireless/bcm43xx/bcm43xx_phy.c:1496:bcm43xx_find_lopair()bcm43xx: Chip initialized
bcm43xx: 32-bit DMA initialized
bcm43xx: Keys cleared
bcm43xx: Selected 802.11 core (phytype 2)
bcm43xx: ASSERTION FAILED (radio_attenuation < 10) at: drivers/net/wireless/bcm43xx/bcm43xx_phy.c:1496:bcm43xx_find_lopair()bcm43xx: set security called, .level = 0, .enabled = 0, .encrypt = 0


PS Am I suppose to config /etc/conf.d/wireless and conf.d/net?
PPS. Should I upgrade to 2.6.20?

edit: The problem is that "iwlist scan" reports no results, as ifconfig enables eth1 successfully after rmmod and modprobe bcm43xx.
_________________
gentoo.ro
Back to top
View user's profile Send private message
JoseJX
Developer
Developer


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Fri Feb 09, 2007 2:33 pm    Post subject: Reply with quote

No... it's better. Last time you had this fatal error:

bcm43xx: IRQ_READY timeout
bcm43xx: core_up for active 802.11 core failed (-19)

I don't see it this time, so that problem is fixed. You should definitely upgrade to 2.6.20, but if iwlist isn't reporting any results, you probably have a wifi button. Larry's latest patchset should include a fix for displaying the status of the button better. You may also need an ACPI button support application such as acer_acpi.
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
Back to top
View user's profile Send private message
mayday147
l33t
l33t


Joined: 22 Mar 2004
Posts: 825
Location: Bucharest, Romania

PostPosted: Fri Feb 09, 2007 6:18 pm    Post subject: Reply with quote

I have upgraded to 2.6.20 but still no luck:

Code:

localhost mayday # dmesg -c
localhost mayday # rmmod bcm43xx
localhost mayday # modprobe bcm43xx
localhost mayday # ifconfig eth1 up
SIOCSIFFLAGS: No such device
localhost mayday # dmesg

bcm43xx driver
ACPI: PCI Interrupt 0000:00:0c.0[A] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10
bcm43xx: Chip ID 0x4318, rev 0x2
bcm43xx: Number of cores: 4
bcm43xx: Core 0: ID 0x800, rev 0xd, vendor 0x4243
bcm43xx: Core 1: ID 0x812, rev 0x9, vendor 0x4243
bcm43xx: Core 2: ID 0x804, rev 0xc, vendor 0x4243
bcm43xx: Core 3: ID 0x80d, rev 0x7, vendor 0x4243
bcm43xx: PHY connected
bcm43xx: Detected PHY: Version: 3, Type 2, Revision 7
bcm43xx: Detected Radio: ID: 8205017f (Manuf: 17f Ver: 2050 Rev: 8)
bcm43xx: Radio turned off
bcm43xx: Radio turned off
bcm43xx: PHY connected
bcm43xx: It took 17 tries to set IRQ_READY
bcm43xx: Microcode rev 0x127, pl 0xe (2005-04-18  02:36:27)
bcm43xx: Radio turned on
bcm43xx: ASSERTION FAILED (radio_attenuation < 10) at: drivers/net/wireless/bcm43xx/bcm43xx_phy.c:1496:bcm43xx_find_lopair()bcm43xx: WARNING: Writing invalid LOpair (low: -96, high: 69, index: 120)
 [<d891864f>] bcm43xx_phy_lo_adjust+0x1e8/0x227 [bcm43xx]
 [<c0114373>] release_console_sem+0x1a1/0x1a9
 [<d891a2bc>] bcm43xx_phy_initb6+0x6c6/0x7fa [bcm43xx]
 [<d891a49a>] bcm43xx_phy_initg+0xaa/0xd29 [bcm43xx]
 [<c024eec0>] __delay+0x6/0x7
 [<d8911cb0>] bcm43xx_radio_selectchannel+0x45c/0x468 [bcm43xx]
 [<d891c177>] bcm43xx_phy_init+0x629/0x647 [bcm43xx]
 [<d8915ab1>] bcm43xx_radio_turn_on+0x1d1/0x1e2 [bcm43xx]
 [<d890b68c>] bcm43xx_write_initvals+0x56/0x89 [bcm43xx]
 [<d890cd02>] bcm43xx_chip_init+0x756/0xa4f [bcm43xx]
 [<c014c90d>] link_path_walk+0xa5/0xaf
 [<c0130002>] mempool_resize+0x0/0x13e
 [<c011adb4>] do_timer+0x4f6/0x707
 [<d890e361>] wireless_core_up+0x188/0x693 [bcm43xx]
 [<d890bda7>] bcm43xx_switch_core+0x27/0x38 [bcm43xx]
 [<d890bd35>] _switch_core+0x7c/0xc7 [bcm43xx]
 [<d890ebd8>] bcm43xx_select_wireless_core+0x36c/0x4e9 [bcm43xx]
 [<d890bda7>] bcm43xx_switch_core+0x27/0x38 [bcm43xx]
 [<d891ca72>] bcm43xx_pctl_init+0xf0/0x12e [bcm43xx]
 [<d890ee53>] bcm43xx_init_board+0x50/0x111 [bcm43xx]
 [<c039557e>] dev_open+0x2a/0x60
 [<c039425b>] dev_change_flags+0x47/0xe4
 [<c03c365b>] devinet_ioctl+0x251/0x56e
 [<c03951a8>] dev_ifsioc+0x113/0x3e1
 [<c024f8bf>] copy_to_user+0x2d/0x42
 [<c038bf19>] sock_ioctl+0x19f/0x1be
 [<c038bd7a>] sock_ioctl+0x0/0x1be
 [<c014e3a1>] do_ioctl+0x19/0x4d
 [<c03eafc9>] do_page_fault+0x277/0x510
 [<c014e5d9>] vfs_ioctl+0x204/0x21b
 [<c014e623>] sys_ioctl+0x33/0x4c
 [<c0102a8c>] sysenter_past_esp+0x5d/0x81
 =======================
bcm43xx: ASSERTION FAILED (radio_attenuation < 10) at: drivers/net/wireless/bcm43xx/bcm43xx_phy.c:1496:bcm43xx_find_lopair()bcm43xx: WARNING: Writing invalid LOpair (low: -96, high: 69, index: 120)
 [<d891864f>] bcm43xx_phy_lo_adjust+0x1e8/0x227 [bcm43xx]
 [<d891afc8>] bcm43xx_phy_initg+0xbd8/0xd29 [bcm43xx]
 [<d891c177>] bcm43xx_phy_init+0x629/0x647 [bcm43xx]
 [<d8915ab1>] bcm43xx_radio_turn_on+0x1d1/0x1e2 [bcm43xx]
 [<d890b68c>] bcm43xx_write_initvals+0x56/0x89 [bcm43xx]
 [<d890cd02>] bcm43xx_chip_init+0x756/0xa4f [bcm43xx]
 [<c014c90d>] link_path_walk+0xa5/0xaf
 [<c0130002>] mempool_resize+0x0/0x13e
 [<c011adb4>] do_timer+0x4f6/0x707
 [<d890e361>] wireless_core_up+0x188/0x693 [bcm43xx]
 [<d890bda7>] bcm43xx_switch_core+0x27/0x38 [bcm43xx]
 [<d890bd35>] _switch_core+0x7c/0xc7 [bcm43xx]
 [<d890ebd8>] bcm43xx_select_wireless_core+0x36c/0x4e9 [bcm43xx]
 [<d890bda7>] bcm43xx_switch_core+0x27/0x38 [bcm43xx]
 [<d891ca72>] bcm43xx_pctl_init+0xf0/0x12e [bcm43xx]
 [<d890ee53>] bcm43xx_init_board+0x50/0x111 [bcm43xx]
 [<c039557e>] dev_open+0x2a/0x60
 [<c039425b>] dev_change_flags+0x47/0xe4
 [<c03c365b>] devinet_ioctl+0x251/0x56e
 [<c03951a8>] dev_ifsioc+0x113/0x3e1
 [<c024f8bf>] copy_to_user+0x2d/0x42
 [<c038bf19>] sock_ioctl+0x19f/0x1be
 [<c038bd7a>] sock_ioctl+0x0/0x1be
 [<c014e3a1>] do_ioctl+0x19/0x4d
 [<c03eafc9>] do_page_fault+0x277/0x510
 [<c014e5d9>] vfs_ioctl+0x204/0x21b
 [<c014e623>] sys_ioctl+0x33/0x4c
 [<c0102a8c>] sysenter_past_esp+0x5d/0x81
 =======================
bcm43xx: ASSERTION FAILED (radio_attenuation < 10) at: drivers/net/wireless/bcm43xx/bcm43xx_phy.c:1496:bcm43xx_find_lopair()bcm43xx: WARNING: Writing invalid LOpair (low: -96, high: 69, index: 120)
 [<d891864f>] bcm43xx_phy_lo_adjust+0x1e8/0x227 [bcm43xx]
 [<d8918445>] bcm43xx_phy_init_pctl+0x202/0x224 [bcm43xx]
 [<d891b0a7>] bcm43xx_phy_initg+0xcb7/0xd29 [bcm43xx]
 [<d891c177>] bcm43xx_phy_init+0x629/0x647 [bcm43xx]
 [<d8915ab1>] bcm43xx_radio_turn_on+0x1d1/0x1e2 [bcm43xx]
 [<d890b68c>] bcm43xx_write_initvals+0x56/0x89 [bcm43xx]
 [<d890cd02>] bcm43xx_chip_init+0x756/0xa4f [bcm43xx]
 [<c014c90d>] link_path_walk+0xa5/0xaf
 [<c0130002>] mempool_resize+0x0/0x13e
 [<c011adb4>] do_timer+0x4f6/0x707
 [<d890e361>] wireless_core_up+0x188/0x693 [bcm43xx]
 [<d890bda7>] bcm43xx_switch_core+0x27/0x38 [bcm43xx]
 [<d890bd35>] _switch_core+0x7c/0xc7 [bcm43xx]
 [<d890ebd8>] bcm43xx_select_wireless_core+0x36c/0x4e9 [bcm43xx]
 [<d890bda7>] bcm43xx_switch_core+0x27/0x38 [bcm43xx]
 [<d891ca72>] bcm43xx_pctl_init+0xf0/0x12e [bcm43xx]
 [<d890ee53>] bcm43xx_init_board+0x50/0x111 [bcm43xx]
 [<c039557e>] dev_open+0x2a/0x60
 [<c039425b>] dev_change_flags+0x47/0xe4
 [<c03c365b>] devinet_ioctl+0x251/0x56e
 [<c03951a8>] dev_ifsioc+0x113/0x3e1
 [<c024f8bf>] copy_to_user+0x2d/0x42
 [<c038bf19>] sock_ioctl+0x19f/0x1be
 [<c038bd7a>] sock_ioctl+0x0/0x1be
 [<c014e3a1>] do_ioctl+0x19/0x4d
 [<c03eafc9>] do_page_fault+0x277/0x510
 [<c014e5d9>] vfs_ioctl+0x204/0x21b
 [<c014e623>] sys_ioctl+0x33/0x4c
 [<c0102a8c>] sysenter_past_esp+0x5d/0x81
 =======================
bcm43xx: Chip initialized
bcm43xx: 32-bit DMA initialized
bcm43xx: Keys cleared
bcm43xx: Selected 802.11 core (phytype 2)
bcm43xx: ASSERTION FAILED (radio_attenuation < 10) at: drivers/net/wireless/bcm43xx/bcm43xx_phy.c:1496:bcm43xx_find_lopair()bcm43xx: WARNING: Writing invalid LOpair (low: -96, high: 69, index: 120)
 [<d891864f>] bcm43xx_phy_lo_adjust+0x1e8/0x227 [bcm43xx]
 [<d89194c3>] bcm43xx_phy_lo_g_measure+0x93c/0xb28 [bcm43xx]
 [<d890b296>] bcm43xx_shm_read32+0x2c/0xa1 [bcm43xx]
 [<d891c378>] bcm43xx_power_saving_ctl_bits+0x48/0x5f [bcm43xx]
 [<d890f9a7>] bcm43xx_periodic_work_handler+0x116/0x2fd [bcm43xx]
 [<d890f891>] bcm43xx_periodic_work_handler+0x0/0x2fd [bcm43xx]
 [<c011fae7>] run_workqueue+0x70/0x101
 [<c0120030>] worker_thread+0x105/0x12e
 [<c01119dd>] default_wake_function+0x0/0xc
 [<c011ff2b>] worker_thread+0x0/0x12e
 [<c012220c>] kthread+0xa0/0xc8
 [<c012216c>] kthread+0x0/0xc8
 [<c0102d8b>] kernel_thread_helper+0x7/0x10
 =======================
SoftMAC: Associate: Scanning for networks first.
SoftMAC: Scanning finished: scanned 14 channels starting with channel 1
SoftMAC: Associate: Scanning for networks first.
SoftMAC: Scanning finished: scanned 14 channels starting with channel 1
SoftMAC: Associate: Scanning for networks first.
SoftMAC: Scanning finished: scanned 14 channels starting with channel 1
SoftMAC: Unable to find matching network after scan!
bcm43xx: Radio turned off
bcm43xx: DMA-32 0x0200 (RX) max used slots: 0/64
bcm43xx: DMA-32 0x02A0 (TX) max used slots: 0/512
bcm43xx: DMA-32 0x0280 (TX) max used slots: 0/512
bcm43xx: DMA-32 0x0260 (TX) max used slots: 0/512
bcm43xx: DMA-32 0x0240 (TX) max used slots: 0/512
bcm43xx: DMA-32 0x0220 (TX) max used slots: 42/512
bcm43xx: DMA-32 0x0200 (TX) max used slots: 0/512
bcm43xx: IRQ_READY timeout
bcm43xx: core_up for active 802.11 core failed (-19)

localhost mayday # uname -a
Linux localhost 2.6.20 #1 Fri Feb 9 18:59:31 EET 2007 i686 AMD Athlon(tm) XP 1600+ GNU/Linux
localhost mayday # iwconfig
eth0      no wireless extensions.

lo        no wireless extensions.

eth1      IEEE 802.11b/g  ESSID:off/any  Nickname:"Broadcom 4318"
          Mode:Managed  Frequency=2.484 GHz  Access Point: Invalid
          Bit Rate=1 Mb/s
          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



PS What do you mean by wifi button?
_________________
gentoo.ro
Back to top
View user's profile Send private message
JoseJX
Developer
Developer


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Fri Feb 09, 2007 6:38 pm    Post subject: Reply with quote

Okay, it's still failing in the same place. Perhaps you do have a conflict, but I can't say for sure, I'm a PowerPC person. :p Maybe play with ACPI.

A wifi button is a button on your computer that enables/disables the wireless card. What kind of computer is this?
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
Back to top
View user's profile Send private message
mayday147
l33t
l33t


Joined: 22 Mar 2004
Posts: 825
Location: Bucharest, Romania

PostPosted: Fri Feb 09, 2007 7:54 pm    Post subject: Reply with quote

It is an Athloon XP+ 1600, but I don't have any wifi button. This Asus cards works like a charm on Windows, though.
_________________
gentoo.ro
Back to top
View user's profile Send private message
mayday147
l33t
l33t


Joined: 22 Mar 2004
Posts: 825
Location: Bucharest, Romania

PostPosted: Fri Feb 09, 2007 8:11 pm    Post subject: Reply with quote

Do you think is it possible that I've chosen the wrong firmware? Should I try anotherone?
Also is it possible to work with ndiswrapper?
_________________
gentoo.ro
Back to top
View user's profile Send private message
JoseJX
Developer
Developer


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Fri Feb 09, 2007 8:19 pm    Post subject: Reply with quote

No, there is no difference between most firmware. I cannot comment on ndiswrapper, you'll have to take ndiswrapper questions to another thread.
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
Back to top
View user's profile Send private message
mayday147
l33t
l33t


Joined: 22 Mar 2004
Posts: 825
Location: Bucharest, Romania

PostPosted: Fri Feb 09, 2007 9:09 pm    Post subject: Reply with quote

You have been right about ACPI. I disabled it in the kernel and now it works. Thank you very much for your effort.
PS Is the 11Mb/s the upper speed bcm43xx driver works for now?
PPS Do I really need ACPI reenabled? as I don't use any sensors at all.
_________________
gentoo.ro
Back to top
View user's profile Send private message
Display posts from previous:   
This topic is locked: you cannot edit posts or make replies.    Gentoo Forums Forum Index Gentoo on PPC All times are GMT
Goto page Previous  1, 2, 3 ... 38, 39, 40, 41, 42  Next
Page 39 of 42

 
Jump to:  
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