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

Goto page Previous  1, 2, 3, 4, 5, 6, 7, 8, 9, 10  Next  
Reply to topic    Gentoo Forums Forum Index Gentoo on PPC
View previous topic :: View next topic  
Author Message
Sodki
Guru
Guru


Joined: 11 Aug 2003
Posts: 418
Location: London, U.K. & Lisbon, Portugal

PostPosted: Mon Dec 17, 2007 5:38 am    Post subject: Reply with quote

You should use a 2.6.24 kernel. The compilation of vanilla-sources is the same as gentoo-sources.
Back to top
View user's profile Send private message
ulissesroc
n00b
n00b


Joined: 15 Dec 2007
Posts: 8
Location: Amsterdam

PostPosted: Mon Dec 17, 2007 1:44 pm    Post subject: Reply with quote

I solved using the other driver, the one suggested in the other topic about airport extreme.

Now it works flawlessly, I am happy with it. The vanilla-sources of emerge were too old, and, since I do not know where to unpack and what to do with the new sources, I opted for the old driver.

Fine enough.

Thanks anyway.
Back to top
View user's profile Send private message
Sodki
Guru
Guru


Joined: 11 Aug 2003
Posts: 418
Location: London, U.K. & Lisbon, Portugal

PostPosted: Mon Dec 17, 2007 3:12 pm    Post subject: Reply with quote

ulissesroc wrote:
I solved using the other driver, the one suggested in the other topic about airport extreme.

Now it works flawlessly, I am happy with it. The vanilla-sources of emerge were too old, and, since I do not know where to unpack and what to do with the new sources, I opted for the old driver.

Fine enough.

Thanks anyway.

I'm glad it works for you. If you want to know more about kernel compilation, I suggest you read this: http://www.gentoo.org/doc/en/kernel-upgrade.xml
Back to top
View user's profile Send private message
ulissesroc
n00b
n00b


Joined: 15 Dec 2007
Posts: 8
Location: Amsterdam

PostPosted: Mon Dec 17, 2007 5:36 pm    Post subject: Reply with quote

Sodki wrote:
ulissesroc wrote:
I solved using the other driver, the one suggested in the other topic about airport extreme.

Now it works flawlessly, I am happy with it. The vanilla-sources of emerge were too old, and, since I do not know where to unpack and what to do with the new sources, I opted for the old driver.

Fine enough.

Thanks anyway.

I'm glad it works for you. If you want to know more about kernel compilation, I suggest you read this: http://www.gentoo.org/doc/en/kernel-upgrade.xml


[OT]
Yeah, I knew that, but my doubt was (is) what to do with the sources downloaded from kernel.org, if I just have to put them into /usr/src, and make the symbolic link /usr/src/linux, or something else was necessary.
[/OT]

Anyway, thanks for your kindness and patience. I think I will enjoy gentoo (even if I'm just a new guy coming from ubuntu :D)
Back to top
View user's profile Send private message
iElectric
n00b
n00b


Joined: 25 Dec 2007
Posts: 19

PostPosted: Tue Dec 25, 2007 7:02 pm    Post subject: Reply with quote

Hey! I am using the latest gentoo-sources (2.6.23-r5) and is there a way to support 4311 card without upgrading to some other new (2.6.24)kernel?
Back to top
View user's profile Send private message
Sodki
Guru
Guru


Joined: 11 Aug 2003
Posts: 418
Location: London, U.K. & Lisbon, Portugal

PostPosted: Tue Dec 25, 2007 11:05 pm    Post subject: Reply with quote

iElectric wrote:
Hey! I am using the latest gentoo-sources (2.6.23-r5) and is there a way to support 4311 card without upgrading to some other new (2.6.24)kernel?

I think that JoseJX already answer that, but I can't find his answer. I believe you have to use a 2.6.24 kernel. It's no big deal, actually. You can use multiple kernel options in your boot manager and, for the moment, install 2.6.24 "just for fun" and see how it goes. :D
Back to top
View user's profile Send private message
iElectric
n00b
n00b


Joined: 25 Dec 2007
Posts: 19

PostPosted: Thu Dec 27, 2007 12:36 am    Post subject: Reply with quote

I managed to install the card with ndiswrapper, i will wait for a few weeks for better support and try again :) Thanks for the advice though!
Back to top
View user's profile Send private message
JoseJX
Developer
Developer


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Mon Dec 31, 2007 2:36 pm    Post subject: Reply with quote

Actually, the wireless-2.6 'everything' branch is the preferred version, but 2.6.24 is the minimum for b43/b43legacy. You really shouldn't need to use ndiswrapper, the b43 driver is quite usable in its current state.

If you'd like to try the wireless-2.6 version, instructions for fetching the git version can be found here: http://linuxwireless.org/en/developers/Documentation/git-guide
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
Back to top
View user's profile Send private message
wuzzerd
Guru
Guru


Joined: 05 Jan 2005
Posts: 434
Location: New Mexico

PostPosted: Sat Jan 12, 2008 9:46 pm    Post subject: Reply with quote

Nice job on this JoseJX. I can finally make the junk laptop into a pure gentoo box and get rid of the ubuntu, lol.

One snag (not of gentoo origin) linux wireless org said to download
Code:
 http://downloads.openwrt.org/sources/broadcom-wl-4.80.53.0.tar.bz2


Very hard to bunzip2 that file. Changing the extension to z and using gunzip fixed that. :P

I had upgraded to the 2.6.24 kernels while getting a rather nifty RTL8187 based usb wireless working and noticed the improvement. Next I rescued the broadcom card from the trash pile, clicked on the older thread and found this one.
Back to top
View user's profile Send private message
blueillusion
Tux's lil' helper
Tux's lil' helper


Joined: 17 Jun 2004
Posts: 138

PostPosted: Wed Jan 16, 2008 7:02 am    Post subject: Reply with quote

is there a specific way in getting the b43 driver to work with wpa_supplicant?
I've had no success with it so far, and I keep getting the error: error loading driver. 'broadcom' unsupported.
using iwconfig works perfect. but i'd like to use wpa_supplicant.

I did some googling, and found that wpa_supplicant isnt built with the broadcom driver due to licensing issues.
It seems it can be done, but im not sure where to get the appropriate sources.
Back to top
View user's profile Send private message
Sodki
Guru
Guru


Joined: 11 Aug 2003
Posts: 418
Location: London, U.K. & Lisbon, Portugal

PostPosted: Wed Jan 16, 2008 10:43 am    Post subject: Reply with quote

blueillusion wrote:
is there a specific way in getting the b43 driver to work with wpa_supplicant?
I've had no success with it so far, and I keep getting the error: error loading driver. 'broadcom' unsupported.
using iwconfig works perfect. but i'd like to use wpa_supplicant.

I did some googling, and found that wpa_supplicant isnt built with the broadcom driver due to licensing issues.
It seems it can be done, but im not sure where to get the appropriate sources.

I believe you just have to emerge wpa_supplicant and configure /etc/wpa_supplicant/wpa_supplicant.conf. using wpa_supplicant is the preferred way to use the wireless cars in Gentoo, if i'm not mistaken.
Back to top
View user's profile Send private message
JoseJX
Developer
Developer


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Wed Jan 16, 2008 11:35 am    Post subject: Reply with quote

The broadcom driver for wpa_supplicant is for the closed source broadcom driver found in wireless routers. With b43/b43legacy/bcm43xx you should be using the wireless extensions driver (wext) instead. wpa_supplicant works fine here.
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
Back to top
View user's profile Send private message
Havin_it
Veteran
Veteran


Joined: 17 Jul 2005
Posts: 1085
Location: Edinburgh, UK

PostPosted: Sat Jan 26, 2008 1:33 pm    Post subject: Reply with quote

I saw that gentoo-sources-2.6.24 was released and immediately gave it a try, but unfortunately I am getting no joy with my card (Belkin F5D7010 Rev3 PCMCIA card, shipped with bcmwl5.sys ver 3.30.15.0, yes VERY old!).

I enabled both b43 and b43legacy (JoseJX has previously suggested I should be able to use b43 but I thought better try both, disabled softmac, and chose Y to using Netlink interface. See below some bits of config:
Code:
pengi ~ # grep -i 80211 /usr/src/linux/.config
CONFIG_CFG80211=y
CONFIG_NL80211=y
CONFIG_MAC80211=y
CONFIG_MAC80211_RCSIMPLE=y
# CONFIG_MAC80211_DEBUGFS is not set
CONFIG_MAC80211_DEBUG=y
CONFIG_MAC80211_VERBOSE_DEBUG=y
CONFIG_MAC80211_LOWTX_FRAME_DUMP=y
CONFIG_MAC80211_DEBUG_COUNTERS=y
CONFIG_MAC80211_IBSS_DEBUG=y
CONFIG_MAC80211_VERBOSE_PS_DEBUG=y
CONFIG_IEEE80211=y
CONFIG_IEEE80211_DEBUG=y
CONFIG_IEEE80211_CRYPT_WEP=y
CONFIG_IEEE80211_CRYPT_CCMP=y
CONFIG_IEEE80211_CRYPT_TKIP=y
# CONFIG_IEEE80211_SOFTMAC is not set
# CONFIG_WLAN_PRE80211 is not set
CONFIG_WLAN_80211=y
pengi ~ # grep -i b43 /usr/src/linux/.config
CONFIG_B43=m
CONFIG_B43_PCI_AUTOSELECT=y
CONFIG_B43_PCICORE_AUTOSELECT=y
CONFIG_B43_PCMCIA=y
CONFIG_B43_DEBUG=y
CONFIG_B43_DMA=y
CONFIG_B43_PIO=y
CONFIG_B43_DMA_AND_PIO_MODE=y
# CONFIG_B43_DMA_MODE is not set
# CONFIG_B43_PIO_MODE is not set
CONFIG_B43LEGACY=m
CONFIG_B43LEGACY_PCI_AUTOSELECT=y
CONFIG_B43LEGACY_PCICORE_AUTOSELECT=y
CONFIG_B43LEGACY_DEBUG=y
CONFIG_B43LEGACY_DMA=y
CONFIG_B43LEGACY_PIO=y
CONFIG_B43LEGACY_DMA_AND_PIO_MODE=y
# CONFIG_B43LEGACY_DMA_MODE is not set
# CONFIG_B43LEGACY_PIO_MODE is not set   


On boot or card insertion, the device seems to come up okay, but association doesn't get anywhere. Also neither of the LEDs on the device lights (under bcm43xx both were constantly lit). The b43 driver is chosen automatically, but I also tried forcing use of b43legacy and the result was the same. The firmware I used for both drivers were the wl_apsta*.o recommended on the bcm43xx documentation.

Here's some output:
Code:
Jan 26 12:50:29 pengi b43-phy0: Broadcom 4306 WLAN found
Jan 26 12:50:29 pengi b43-phy0 debug: Found PHY: Analog 2, Type 2, Revision 2
Jan 26 12:50:29 pengi b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2
Jan 26 12:50:29 pengi phy0: Selected rate control algorithm 'simple'

...

Jan 26 12:50:32 pengi b43-phy0 debug: Loading firmware version 351.126 (2006-07-29 05:54:02)
Jan 26 12:50:34 pengi b43-phy0 debug: Chip initialized
Jan 26 12:50:34 pengi b43-phy0 debug: 30-bit DMA initialized
Jan 26 12:50:34 pengi b43-phy0 debug: Wireless interface started
Jan 26 12:50:34 pengi HW CONFIG: channel=1 freq=2412 phymode=2
Jan 26 12:50:34 pengi b43-phy0 debug: Adding Interface type 2
Jan 26 12:50:34 pengi HW CONFIG: channel=1 freq=2412 phymode=2
Jan 26 12:50:34 pengi phy0: TX to low-level driver (len=42) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:30:bd:fc:0b:06 A3=ff:ff:ff:ff:ff:ff
Jan 26 12:50:34 pengi HW CONFIG: channel=2 freq=2417 phymode=2
Jan 26 12:50:35 pengi phy0: TX to low-level driver (len=42) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:30:bd:fc:0b:06 A3=ff:ff:ff:ff:ff:ff
Jan 26 12:50:35 pengi HW CONFIG: channel=3 freq=2422 phymode=2
Jan 26 12:50:35 pengi phy0: TX to low-level driver (len=42) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:30:bd:fc:0b:06 A3=ff:ff:ff:ff:ff:ff
Jan 26 12:50:35 pengi HW CONFIG: channel=4 freq=2427 phymode=2
Jan 26 12:50:35 pengi phy0: TX to low-level driver (len=42) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:30:bd:fc:0b:06 A3=ff:ff:ff:ff:ff:ff
Jan 26 12:50:35 pengi HW CONFIG: channel=5 freq=2432 phymode=2
Jan 26 12:50:35 pengi phy0: TX to low-level driver (len=42) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:30:bd:fc:0b:06 A3=ff:ff:ff:ff:ff:ff
Jan 26 12:50:35 pengi HW CONFIG: channel=6 freq=2437 phymode=2
Jan 26 12:50:35 pengi phy0: TX to low-level driver (len=42) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:30:bd:fc:0b:06 A3=ff:ff:ff:ff:ff:ff
Jan 26 12:50:35 pengi HW CONFIG: channel=7 freq=2442 phymode=2
Jan 26 12:50:35 pengi phy0: TX to low-level driver (len=42) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:30:bd:fc:0b:06 A3=ff:ff:ff:ff:ff:ff
Jan 26 12:50:35 pengi HW CONFIG: channel=8 freq=2447 phymode=2
Jan 26 12:50:35 pengi phy0: TX to low-level driver (len=42) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:30:bd:fc:0b:06 A3=ff:ff:ff:ff:ff:ff
Jan 26 12:50:35 pengi HW CONFIG: channel=9 freq=2452 phymode=2
Jan 26 12:50:35 pengi phy0: TX to low-level driver (len=42) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:30:bd:fc:0b:06 A3=ff:ff:ff:ff:ff:ff
Jan 26 12:50:35 pengi HW CONFIG: channel=10 freq=2457 phymode=2
Jan 26 12:50:35 pengi phy0: TX to low-level driver (len=42) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:30:bd:fc:0b:06 A3=ff:ff:ff:ff:ff:ff
Jan 26 12:50:35 pengi HW CONFIG: channel=11 freq=2462 phymode=2
Jan 26 12:50:35 pengi phy0: TX to low-level driver (len=42) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:30:bd:fc:0b:06 A3=ff:ff:ff:ff:ff:ff
Jan 26 12:50:35 pengi HW CONFIG: channel=1 freq=2412 phymode=2
Jan 26 12:50:35 pengi HW CONFIG: channel=11 freq=2462 phymode=2
Jan 26 12:50:35 pengi wlan0: Initial auth_alg=0
Jan 26 12:50:35 pengi wlan0: authenticate with AP 00:17:3f:0d:66:c2
Jan 26 12:50:35 pengi phy0: TX to low-level driver (len=30) FC=0x00b0 DUR=0x013a A1=00:17:3f:0d:66:c2 A2=00:30:bd:fc:0b:06 A3=00:17:3f:0d:66:c2
Jan 26 12:50:35 pengi wlan0: RX authentication from 00:17:3f:0d:66:c2 (alg=0 transaction=2 status=0)
Jan 26 12:50:35 pengi wlan0: authenticated
Jan 26 12:50:35 pengi wlan0: associate with AP 00:17:3f:0d:66:c2
Jan 26 12:50:35 pengi phy0: TX to low-level driver (len=55) FC=0x0000 DUR=0x013a A1=00:17:3f:0d:66:c2 A2=00:30:bd:fc:0b:06 A3=00:17:3f:0d:66:c2
Jan 26 12:50:35 pengi wlan0: RX AssocResp from 00:17:3f:0d:66:c2 (capab=0x401 status=0 aid=4)
Jan 26 12:50:35 pengi wlan0: associated
Jan 26 12:50:35 pengi phy0: Added STA 00:17:3f:0d:66:c2
Jan 26 12:50:37 pengi HW CONFIG: channel=1 freq=2412 phymode=2
Jan 26 12:50:37 pengi phy0: TX to low-level driver (len=49) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:30:bd:fc:0b:06 A3=ff:ff:ff:ff:ff:ff
Jan 26 12:50:37 pengi HW CONFIG: channel=2 freq=2417 phymode=2
Jan 26 12:50:37 pengi phy0: TX to low-level driver (len=49) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:30:bd:fc:0b:06 A3=ff:ff:ff:ff:ff:ff
Jan 26 12:50:37 pengi rc-scripts: WARNING:  net.wlan0 has started but is inactive
Jan 26 12:50:37 pengi HW CONFIG: channel=3 freq=2422 phymode=2
Jan 26 12:50:37 pengi phy0: TX to low-level driver (len=49) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:30:bd:fc:0b:06 A3=ff:ff:ff:ff:ff:ff
Jan 26 12:50:37 pengi rc-scripts: WARNING:  ntp-client is scheduled to start when net.wlan0 has started.
Jan 26 12:50:37 pengi rc-scripts: WARNING:  sshd is scheduled to start when net.wlan0 has started.
Jan 26 12:50:37 pengi HW CONFIG: channel=4 freq=2427 phymode=2
Jan 26 12:50:37 pengi phy0: TX to low-level driver (len=49) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:30:bd:fc:0b:06 A3=ff:ff:ff:ff:ff:ff
Jan 26 12:50:37 pengi HW CONFIG: channel=5 freq=2432 phymode=2
Jan 26 12:50:37 pengi phy0: TX to low-level driver (len=49) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:30:bd:fc:0b:06 A3=ff:ff:ff:ff:ff:ff
Jan 26 12:50:37 pengi HW CONFIG: channel=6 freq=2437 phymode=2
Jan 26 12:50:37 pengi phy0: TX to low-level driver (len=49) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:30:bd:fc:0b:06 A3=ff:ff:ff:ff:ff:ff
Jan 26 12:50:37 pengi HW CONFIG: channel=7 freq=2442 phymode=2
Jan 26 12:50:38 pengi phy0: TX to low-level driver (len=49) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:30:bd:fc:0b:06 A3=ff:ff:ff:ff:ff:ff
Jan 26 12:50:38 pengi HW CONFIG: channel=8 freq=2447 phymode=2
Jan 26 12:50:38 pengi phy0: TX to low-level driver (len=49) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:30:bd:fc:0b:06 A3=ff:ff:ff:ff:ff:ff
Jan 26 12:50:38 pengi HW CONFIG: channel=9 freq=2452 phymode=2
Jan 26 12:50:38 pengi phy0: TX to low-level driver (len=49) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:30:bd:fc:0b:06 A3=ff:ff:ff:ff:ff:ff
Jan 26 12:50:38 pengi HW CONFIG: channel=10 freq=2457 phymode=2
Jan 26 12:50:38 pengi cron[6589]: (CRON) STARTUP (V5.0)
Jan 26 12:50:38 pengi phy0: TX to low-level driver (len=49) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:30:bd:fc:0b:06 A3=ff:ff:ff:ff:ff:ff
Jan 26 12:50:38 pengi HW CONFIG: channel=11 freq=2462 phymode=2
Jan 26 12:50:38 pengi phy0: TX to low-level driver (len=49) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:30:bd:fc:0b:06 A3=ff:ff:ff:ff:ff:ff
Jan 26 12:50:38 pengi HW CONFIG: channel=11 freq=2462 phymode=2
Jan 26 12:50:38 pengi wlan0: dropped data frame to not associated station 00:00:00:00:00:00

...

Jan 26 12:51:06 pengi kdm: :0[6631]: pam_unix(kde:session): session opened for user robin by (uid=0)
Jan 26 12:51:37 pengi b43-phy0 debug: Using hardware based encryption for keyidx: 0, mac: ff:ff:ff:ff:ff:ff
Jan 26 12:51:37 pengi HW CONFIG: channel=1 freq=2412 phymode=2
Jan 26 12:51:37 pengi phy0: TX to low-level driver (len=49) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:30:bd:fc:0b:06 A3=ff:ff:ff:ff:ff:ff


One other thing: as well as wlan0, I also have another device called wmaster0 that appears in ifconfig. Eh?

Please help. Will jump through any hoops you suggest, and post whatever other info/config/logs you want to see.
Back to top
View user's profile Send private message
Havin_it
Veteran
Veteran


Joined: 17 Jul 2005
Posts: 1085
Location: Edinburgh, UK

PostPosted: Mon Jan 28, 2008 12:19 am    Post subject: Reply with quote

Hmm... worse still, it seems bcm43xx doesn't work either with this kernel. I disabled mac80211 and both the b43* modules and enabled softmac and bcm43xx, but the results were the same as with the others.

I do wonder after this if the problem is something unrelated... are there any other kernel config items that could have an effect here?

Really would appreciate any suggestions or guidance. I'm looking at having to replace this card if I can't get it back in business soon.

[EDIT: I had said I didn't have LED Triggers support in my kernel config, but I just found it...]
Back to top
View user's profile Send private message
Raftysworld
Apprentice
Apprentice


Joined: 27 Feb 2005
Posts: 236
Location: Snohomish, WA

PostPosted: Mon Jan 28, 2008 3:51 pm    Post subject: Reply with quote

I'm having a similar problem to what a previous poster was having. I have a bcm4306, revision 3, but it loads the b43 module automatically (rather than b43legacy). I have the firmware installed. When I scan, it does detect my network. However, it doesn't give me a bitrate... and when I try to bring up the network, it fails and has the following error:

ADDRCONF(NETDEV_UP): wlan0: link is not ready

Any ideas??
_________________
emerge --info
Portage 2.1.4 (default-linux/x86/dev/2007.1, gcc-4.2.2, glibc-2.7-r1, 2.6.24-gentoo i686)
Back to top
View user's profile Send private message
sian
Apprentice
Apprentice


Joined: 26 Jan 2004
Posts: 288

PostPosted: Mon Jan 28, 2008 10:09 pm    Post subject: Reply with quote

Hello all,

I tried to upgrade to kernel 2.6.24 and I use ndiswrapper 1.51 to connect my laptop to internet (bcm4318).
I also tried with the native driver from the kernel but eth1 was not recognized (on my laptop eth1 is the wifi interface).


Here is my dmesg :
Code:

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
b43-phy0 debug: DebugFS (CONFIG_DEBUG_FS) not enabled in kernel config
phy0: Selected rate control algorithm 'simple'
phy0: Failed to initialize wep
b43: probe of ssb0:0 failed with error -12
EXT3 FS on hda3, internal journal
usbcore: registered new interface driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial Driver core
drivers/usb/serial/usb-serial.c: USB Serial support registered for
PocketPC PDA
drivers/usb/serial/ipaq.c: USB PocketPC PDA driver v0.5
usbcore: registered new interface driver ipaq
Adding 1807304k swap on /dev/hda2.  Priority:-1 extents:1
across:1807304k
ndiswrapper version 1.51 loaded (smp=yes, preempt=no)
usbcore: registered new interface driver ndiswrapper


and ifconfig eth1 up gives :
Code:

eth1: unknown interface: No such device



Do you have any clue ?

Regards and thanks in advance.
_________________
Kernel : 2.6.32 - E17 - OpenRC-0.61 - gcc-4.4.3
Back to top
View user's profile Send private message
coolsnowmen
Veteran
Veteran


Joined: 30 Jun 2004
Posts: 1479
Location: No.VA

PostPosted: Tue Jan 29, 2008 12:55 am    Post subject: Reply with quote

sian wrote:
I tried to upgrade to kernel 2.6.24 and I use ndiswrapper 1.51 to connect my laptop to internet (bcm4318).
I also tried with the native driver from the kernel but eth1 was not recognized (on my laptop eth1 is the wifi interface).
...


isn't this being answered, or already answered in you OTHER FORUM POST!
http://forums.gentoo.org/viewtopic-t-652685.html

and you havn't responded to some of the much needed information yet.
_________________
emerge: there are no ebuilds to satisfy "moo"
Back to top
View user's profile Send private message
sian
Apprentice
Apprentice


Joined: 26 Jan 2004
Posts: 288

PostPosted: Tue Jan 29, 2008 7:35 pm    Post subject: Reply with quote

@coolsnowmen:
you are right. I should not have do this but then I thought I should have post here.
_________________
Kernel : 2.6.32 - E17 - OpenRC-0.61 - gcc-4.4.3
Back to top
View user's profile Send private message
Havin_it
Veteran
Veteran


Joined: 17 Jul 2005
Posts: 1085
Location: Edinburgh, UK

PostPosted: Tue Jan 29, 2008 8:04 pm    Post subject: Reply with quote

Hello again... I have bcm43xx working again on 2.4.24-gentoo, and even got brief success with ndiswrapper (after leaving it standing for 2 hours :? ), but b43 still will not budge. Here's the dmesg from inserting the card after boot:
Code:
pccard: CardBus card inserted into slot 0
yenta EnE: chaning testregister 0xC9, 04 -> 04
PCI: Enabling device 0000:03:00.0 (0000 -> 0002)
ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:03:00.0 to 64
ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x04, vendor 0x4243)
ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x05, vendor 0x4243)
ssb: Core 2 found: PCMCIA (cc 0x80D, rev 0x02, vendor 0x4243)
ssb: Core 3 found: V90 (cc 0x807, rev 0x02, vendor 0x4243)
ssb: Core 4 found: PCI (cc 0x804, rev 0x09, vendor 0x4243)
ssb: Sonics Silicon Backplane found on PCI device 0000:03:00.0
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'
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
Registered led device: b43-phy0:tx
Registered led device: b43-phy0:rx
b43-phy0 debug: Wireless interface started
HW CONFIG: channel=1 freq=2412 phymode=2
b43-phy0 debug: Adding Interface type 2
HW CONFIG: channel=1 freq=2412 phymode=2
phy0: TX to low-level driver (len=42) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:30:bd:fc:0b:06 A3=ff:ff:ff:ff:ff:ff
HW CONFIG: channel=2 freq=2417 phymode=2
phy0: TX to low-level driver (len=42) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:30:bd:fc:0b:06 A3=ff:ff:ff:ff:ff:ff
HW CONFIG: channel=3 freq=2422 phymode=2
phy0: TX to low-level driver (len=42) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:30:bd:fc:0b:06 A3=ff:ff:ff:ff:ff:ff
HW CONFIG: channel=4 freq=2427 phymode=2
phy0: TX to low-level driver (len=42) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:30:bd:fc:0b:06 A3=ff:ff:ff:ff:ff:ff
HW CONFIG: channel=5 freq=2432 phymode=2
phy0: TX to low-level driver (len=42) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:30:bd:fc:0b:06 A3=ff:ff:ff:ff:ff:ff
HW CONFIG: channel=6 freq=2437 phymode=2
phy0: TX to low-level driver (len=42) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:30:bd:fc:0b:06 A3=ff:ff:ff:ff:ff:ff
HW CONFIG: channel=7 freq=2442 phymode=2
phy0: TX to low-level driver (len=42) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:30:bd:fc:0b:06 A3=ff:ff:ff:ff:ff:ff
HW CONFIG: channel=8 freq=2447 phymode=2
phy0: TX to low-level driver (len=42) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:30:bd:fc:0b:06 A3=ff:ff:ff:ff:ff:ff
HW CONFIG: channel=9 freq=2452 phymode=2
phy0: TX to low-level driver (len=42) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:30:bd:fc:0b:06 A3=ff:ff:ff:ff:ff:ff
HW CONFIG: channel=10 freq=2457 phymode=2
phy0: TX to low-level driver (len=42) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:30:bd:fc:0b:06 A3=ff:ff:ff:ff:ff:ff
HW CONFIG: channel=11 freq=2462 phymode=2
phy0: TX to low-level driver (len=42) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:30:bd:fc:0b:06 A3=ff:ff:ff:ff:ff:ff
HW CONFIG: channel=1 freq=2412 phymode=2


and here's the wpa_supplicant output from starting the interface with its initscript:
Code:
pengi ~ # /etc/init.d/net.wlan0 start
 * Service net.wlan0 starting
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'
ctrl_interface='/var/run/wpa_supplicant'
ap_scan=2
fast_reauth=1
Line: 16 - start of a new network block
ssid - hexdump_ascii(len=7):
     72 65 61 67 65 6e 74                              reagent
mode=0 (0x0)
proto: 0x1
key_mgmt: 0x2
pairwise: 0x8
group: 0x8
PSK (ASCII passphrase) - hexdump_ascii(len=25): [REMOVED]
priority=10 (0xa)
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Line: 28 - start of a new network block
ssid - hexdump_ascii(len=7):
     64 6f 6e 67 6c 65 64                              dongled
mode=1 (0x1)
scan_ssid=1 (0x1)
proto: 0x1
pairwise: 0x1
key_mgmt: 0x4
group: 0x2
wep_key0 - hexdump(len=13): [REMOVED]
wep_tx_keyidx=0 (0x0)
priority=1 (0x1)
Line: 47 - start of a new network block
ssid - hexdump_ascii(len=10):
     6a 6f 6c 6c 79 6a 75 64 67 65                     jollyjudge
key_mgmt: 0x4
priority=3 (0x3)
Line: 53 - start of a new network block
ssid - hexdump_ascii(len=25):
     42 65 6c 6b 69 6e 5f 47 5f 50 6c 75 73 5f 4d 49   Belkin_G_Plus_MI
     4d 4f 5f 41 41 39 31 42 41                        MO_AA91BA
key_mgmt: 0x4
priority=1 (0x1)
Line: 59 - start of a new network block
ssid - hexdump_ascii(len=13):
     66 6f 6f 74 6c 69 67 68 74 73 62 61 72            footlightsbar
key_mgmt: 0x4
priority=2 (0x2)
Line: 65 - start of a new network block
ssid - hexdump_ascii(len=8):
     42 61 72 20 41 6c 62 61                           Bar Alba
scan_ssid=1 (0x1)
proto: 0x1
key_mgmt: 0x2
pairwise: 0x8
group: 0x8
PSK (ASCII passphrase) - hexdump_ascii(len=10): [REMOVED]
priority=2 (0x2)
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 10
   id=0 ssid='reagent'
Priority group 3
   id=2 ssid='jollyjudge'
Priority group 2
   id=4 ssid='footlightsbar'
   id=5 ssid='Bar Alba'
Priority group 1
   id=1 ssid='dongled'
   id=3 ssid='Belkin_G_Plus_MIMO_AA91BA'
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:30:bd:fc:0b:06
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
Daemonize..
 * WARNING:  net.wlan0 has started but is inactive


Does this show anything useful? It's only in the wpa output that there are any errors that I can easily see, but what do they mean?
Back to top
View user's profile Send private message
lordcris
Apprentice
Apprentice


Joined: 09 Jul 2002
Posts: 248

PostPosted: Wed Jan 30, 2008 5:40 pm    Post subject: Reply with quote

Sodki wrote:
JoseJX wrote:
As for why it's not working, you probably need to have it rename the device to wlan0 instead of eth1. You can change this by changing the device name in /etc/udev/rules.d/70-persistent-net.rules

Thank you, I didn't know that my wireless network interface could't have that name (ethX). I followed your advice and this is what I get now:

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 ]


I googled a bit about that error, but I only found people that got that error and could still establish a wireless connection, so I didn't worry much. Unfortunately, I'm still not able to make my wireless card work:

Code:
# iwlist wlan0 scan
wlan0     No scan results


dmesg has a strange message, though:

Code:
b43-phy1 debug: Removing Interface type 2
b43-phy1 debug: Wireless interface stopped
b43-phy1 debug: DMA-32 0x0200 (RX) max used slots: 1/64
b43-phy1 debug: DMA-32 0x02A0 (TX) max used slots: 0/128
b43-phy1 debug: DMA-32 0x0280 (TX) max used slots: 0/128
b43-phy1 debug: DMA-32 0x0260 (TX) max used slots: 0/128
b43-phy1 debug: DMA-32 0x0240 (TX) max used slots: 0/128
b43-phy1 debug: DMA-32 0x0220 (TX) max used slots: 22/128
b43-phy1 debug: DMA-32 0x0200 (TX) max used slots: 0/128
b43-phy1 debug: Loading firmware version 351.126 (2006-07-29 05:54:02)
b43-phy1 debug: Chip initialized
b43-phy1 debug: 30-bit DMA initialized
b43-phy1 debug: Wireless interface started
b43-phy1 debug: Adding Interface type 2
b43-phy1: Radio turned off by software
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:14:f2:8f:52:12
wlan0: authenticate with AP 00:14:f2:8f:52:12
wlan0: authenticate with AP 00:14:f2:8f:52:12
wlan0: authentication with AP 00:14:f2:8f:52:12 timed out


Radio turned off by software? Is that why I can't list any wireless networks? Also, I don't recognize the MAC address of that AP, could be from a neighbour. But if the radio is off, how could he "catch" a MAC address?



i have exactly the same problem



Code:
an 30 18:38:52 powerbook wlan0: Initial auth_alg=0
Jan 30 18:38:52 powerbook wlan0: authenticate with AP 00:17:3f:3b:65:9e
Jan 30 18:38:52 powerbook wlan0: authenticate with AP 00:17:3f:3b:65:9e
Jan 30 18:38:52 powerbook wlan0: authenticate with AP 00:17:3f:3b:65:9e
Jan 30 18:38:52 powerbook wlan0: authentication with AP 00:17:3f:3b:65:9e timed out



did someone solve it?


###################

p.s.

i didn't use the correct firmware for kernel 2.6.24

Code:
If you are using kernel 2.6.24(-rc) (or earlier - but not the compat package) you need http://downloads.openwrt.org/sources/broadcom-wl-4.80.53.0.tar.bz2

now it works.
tnx


Last edited by lordcris on Thu Jan 31, 2008 4:32 pm; edited 1 time in total
Back to top
View user's profile Send private message
GreyVicious
n00b
n00b


Joined: 21 Jan 2008
Posts: 14
Location: Rybnik, PL

PostPosted: Thu Jan 31, 2008 2:16 am    Post subject: Reply with quote

Hi,

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. Does anyone met with this problem? Is there a solution? It worked in 2.6.23 with bcm43xx driver.
Back to top
View user's profile Send private message
Massimo B.
Veteran
Veteran


Joined: 09 Feb 2005
Posts: 1230
Location: PB, Germany

PostPosted: Sat Feb 02, 2008 11:38 pm    Post subject: Reply with quote

Hello. I use sys-kernel/gentoo-sources-2.6.24. For the PowerBook5,8 the hardware is:
Code:
# lspci -n | grep 14e4:43
0001:10:11.0 0280: 14e4:4318 (rev 02)
As firmware I installed broadcom-wl-4.80.53.0.
I modprobe b43, set the essid and use ifconfig to set the IP. But I can't get a signal.
log:
Feb  2 23:53:52 [kernel] udev: renamed network interface wlan0 to eth2
Feb  2 23:53:52 [udev-net.sh] /etc/init.d/net.wmaster0: does not exist or is not executable
Feb  2 23:53:58 [rc-scripts] Couldn't find any access points on eth2
Feb  2 23:53:58 [rc-scripts] Failed to configure wireless for eth2
Feb  2 23:53:58 [kernel] b43-phy3: Radio turned off by software
dmesg:
eth2: Initial auth_alg=0
eth2: authenticate with AP 00:d1:cc:e5:60:ff
eth2: Initial auth_alg=0
eth2: authenticate with AP 00:d1:cc:e5:60:ff
b43-phy3 debug: Removing Interface type 2
b43-phy3 debug: Wireless interface stopped
b43-phy3 debug: DMA-32 0x0200 (RX) max used slots: 1/64
b43-phy3 debug: DMA-32 0x02A0 (TX) max used slots: 0/128
b43-phy3 debug: DMA-32 0x0280 (TX) max used slots: 0/128
b43-phy3 debug: DMA-32 0x0260 (TX) max used slots: 0/128
b43-phy3 debug: DMA-32 0x0240 (TX) max used slots: 0/128
b43-phy3 debug: DMA-32 0x0220 (TX) max used slots: 4/128
b43-phy3 debug: DMA-32 0x0200 (TX) max used slots: 0/128
b43-phy3 debug: Loading firmware version 351.126 (2006-07-29 05:54:02)
b43-phy3 debug: Chip initialized
b43-phy3 debug: 32-bit DMA initialized
b43-phy3 debug: Wireless interface started
b43-phy3 debug: Adding Interface type 2
b43-phy3: Radio turned off by software

The associated AP in iwconfig is correct but the signal is 0 and ping to that access point doesn't work. Another gentoo (iBook,hermes) aside connects fine.
_________________
ppc:PowerBook5,8 15"(1440)-G4/1.67,2G | amd64:Acer Z5610 (Core2QuadQ8200),i5-3470 | amd64-prefix:OpenSuse | Lila-Theme
Back to top
View user's profile Send private message
damoncf
Guru
Guru


Joined: 05 Oct 2004
Posts: 388
Location: US OH

PostPosted: Sun Feb 03, 2008 2:27 am    Post subject: Reply with quote

Can someone help me I have gone through the 2.6.24 kernel and cannot find anything for wireless bcm43xx. Can someone tell me if there is something I have to enable to have them show up.

Damon
Back to top
View user's profile Send private message
lordcris
Apprentice
Apprentice


Joined: 09 Jul 2002
Posts: 248

PostPosted: Sun Feb 03, 2008 2:29 am    Post subject: Reply with quote

damoncf wrote:
Can someone help me I have gone through the 2.6.24 kernel and cannot find anything for wireless bcm43xx. Can someone tell me if there is something I have to enable to have them show up.

Damon


look at he firs page of this post.

http://forums.gentoo.org/viewtopic-t-547687-postdays-0-postorder-asc-start-0.html
Back to top
View user's profile Send private message
damoncf
Guru
Guru


Joined: 05 Oct 2004
Posts: 388
Location: US OH

PostPosted: Sun Feb 03, 2008 2:57 am    Post subject: Reply with quote

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
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo on PPC All times are GMT
Goto page Previous  1, 2, 3, 4, 5, 6, 7, 8, 9, 10  Next
Page 7 of 10

 
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