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
Akaihiryuu
l33t
l33t


Joined: 08 May 2003
Posts: 701
Location: Columbus, OH

PostPosted: Mon Apr 09, 2007 5:58 pm    Post subject: Kernel 2.6.19.7, getting closer... Reply with quote

I tried the driver again yesterday for the first time in about 6 months (using Broadcom 4306), after upgrading to vanilla-sources 2.6.19.7. It's definitely closer than it was the last time. I can associate with access points now every time usually right away (even using WEP), but my link quality is *terrible* (shows 0/100), transfer rate won't go above 1mbps, and it always drops before dhcpcd can pull an address. It still works flawlessly with ndiswrapper, so I'm assuming it's some sort of tx power issue. I'm using the driver included with the stock vanilla-sources-2.6.19.7. I really wish they'd go back to putting the driver itself in portage (thus enabling updates without patching the kernel)...I don't know how old the one in 2.6.19.7 is. Still using auto for rate, txpower, channel, etc...though I did try setting rate manually to 11M to see if that would help and it didn't.
Back to top
View user's profile Send private message
JoseJX
Developer
Developer


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Mon Apr 09, 2007 6:01 pm    Post subject: Reply with quote

Pretty old. I would use 2.6.20 + Larry's patches. Larry just started releasing seperate snapshots again, so I may re-add bcm43xx to portage.
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
Back to top
View user's profile Send private message
Akaihiryuu
l33t
l33t


Joined: 08 May 2003
Posts: 701
Location: Columbus, OH

PostPosted: Mon Apr 09, 2007 6:50 pm    Post subject: Reply with quote

JoseJX wrote:
Pretty old. I would use 2.6.20 + Larry's patches. Larry just started releasing seperate snapshots again, so I may re-add bcm43xx to portage.


That'd be great...it'd be very nice to be able to upgrade the driver without having to patch the kernel. Is the kernel softmac okay, or will that be a separate ebuild again now too?
Back to top
View user's profile Send private message
JoseJX
Developer
Developer


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Mon Apr 09, 2007 7:25 pm    Post subject: Reply with quote

It's a combined patch. I'd really rather not make a package though, what is the difficulty in compiling a new kernel and/or patching?
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
Back to top
View user's profile Send private message
koprimer
n00b
n00b


Joined: 29 Feb 2004
Posts: 63

PostPosted: Mon Apr 09, 2007 9:44 pm    Post subject: Reply with quote

Does 2.6.20 or Larry's patches fix the transmission power issues with bcm4318 cards? What does his patch fix (maybe I missed a post)? thx :)
Back to top
View user's profile Send private message
Akaihiryuu
l33t
l33t


Joined: 08 May 2003
Posts: 701
Location: Columbus, OH

PostPosted: Mon Apr 09, 2007 10:02 pm    Post subject: Reply with quote

Is there an ebuild for the patches? Or a convenient link I can use to get the kernel patches? I'm ok with going to ~x86 if I can get my wireless working without ndiswrapper.
Back to top
View user's profile Send private message
JoseJX
Developer
Developer


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Tue Apr 10, 2007 1:33 am    Post subject: Reply with quote

koprimer:
With Larry's patches you can get pretty decent rates out of all supported chipsets (4306,4311 and 4318). The 4318 still has some TX power issues, but not as bad as before.

Akaihiryuu:
No, there is no ebuild for them, but the link for Larry's patches in on the first post in this thread. You can get 2.6.20 and newer patches and 2.6.20.6 (2.6.20-gentoo-rc5) are both marked x86 stable.
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
Back to top
View user's profile Send private message
piroko
Tux's lil' helper
Tux's lil' helper


Joined: 25 Aug 2006
Posts: 77

PostPosted: Wed Apr 11, 2007 5:30 am    Post subject: Reply with quote

I can't believe I'm sitting here in my room without a PCMCIA wireless card, getting perfect wireless from my 4318. This truly is a glorious day for me. I wish I had known about Larry's wonderful patches sooner!

Jeremy
_________________
Anyone who is not confused by quantum theory does not truly understand it.
Back to top
View user's profile Send private message
koprimer
n00b
n00b


Joined: 29 Feb 2004
Posts: 63

PostPosted: Fri Apr 13, 2007 9:38 pm    Post subject: Reply with quote

JoseJX wrote:
koprimer:
With Larry's patches you can get pretty decent rates out of all supported chipsets (4306,4311 and 4318). The 4318 still has some TX power issues, but not as bad as before.


Thanks JoseJX. I went ahead and switched over to 2.6.20-gentoo-r5 with Layer's 2.6.20-6 patch. I can notice quite a bit of improvement. My connection isn't dropping as frequent and the connection seems to be a lot stronger. Also, my acpi wireless button is staying on now. I'm glad I made the switch :D
Back to top
View user's profile Send private message
Sedrik
l33t
l33t


Joined: 08 Apr 2005
Posts: 639
Location: Uppsala, Sweden

PostPosted: Sat Apr 14, 2007 7:23 pm    Post subject: Reply with quote

Having a go again with WPA-PSK

Code:
Trying to associate with 00:13:46:42:61:88 (SSID='Sedrik.net' freq=2412 MHz)
ioctl[SIOCSIWFREQ]: Invalid argument
Association request to the driver failed
Associated with 00:13:46:42:61:88
WPA: 4-Way Handshake failed - pre-shared key may be incorrect


Anyone that knows why the handshake fails? The password is correct.
_________________
From Gentoo with love
Back to top
View user's profile Send private message
ktf
n00b
n00b


Joined: 16 Apr 2007
Posts: 1

PostPosted: Mon Apr 16, 2007 5:51 am    Post subject: Reply with quote

Hi,
sorry for the n00b question, but I don't know how to patch the kernel with the larry's patch.
I've downloaded the kernel 2.6.20.7 form kernel.org and the combined_2.6.20.7.patch from larry's site, but how I use it?

Regards
Fabio
Back to top
View user's profile Send private message
Sedrik
l33t
l33t


Joined: 08 Apr 2005
Posts: 639
Location: Uppsala, Sweden

PostPosted: Mon Apr 16, 2007 10:39 am    Post subject: Reply with quote

ktf wrote:
Hi,
sorry for the n00b question, but I don't know how to patch the kernel with the larry's patch.
I've downloaded the kernel 2.6.20.7 form kernel.org and the combined_2.6.20.7.patch from larry's site, but how I use it?

Regards
Fabio


Start by reading the manual
Code:
man patch


Generally you will do something like

patch -p1 < path to patch

the p1 flag depends on where you stand, see the manual for more info.

ps: I don't hold any responsability to as the correctness of this information :D
_________________
From Gentoo with love
Back to top
View user's profile Send private message
el_Salmon
Guru
Guru


Joined: 15 Dec 2003
Posts: 327
Location: Around 2.4GHz

PostPosted: Sun Apr 29, 2007 3:10 pm    Post subject: Reply with quote

I've followed the configuration steps but I get this error when I try any "iwconfig eth2 <command>"

Quote:
SoftMAC: Associate: Scanning for networks first.
SoftMAC: Associate: failed to initiate scan. Is device up?


Quote:
$ iwconfig eth2
eth2 IEEE 802.11b/g ESSID:"l" Nickname:"Broadcom 4306"
Mode:Managed Access Point: Invalid Bit Rate:1 Mb/s
RTS thr:off Fragment thr:off
Encryption key:XXXX-XXXX-XX 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
Back to top
View user's profile Send private message
JoseJX
Developer
Developer


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Sun Apr 29, 2007 3:20 pm    Post subject: Reply with quote

Try bringing the device up first with ifconfig eth2 up, the iwlist scan. If that doesn'[t return anything, the AP can't be seen and then, can't be connected to.
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
Back to top
View user's profile Send private message
el_Salmon
Guru
Guru


Joined: 15 Dec 2003
Posts: 327
Location: Around 2.4GHz

PostPosted: Sun Apr 29, 2007 3:47 pm    Post subject: Reply with quote

Thank you for your fast answer!

I'm posting from my Mac Mini over 2.4 GHz :D
Back to top
View user's profile Send private message
Sedrik
l33t
l33t


Joined: 08 Apr 2005
Posts: 639
Location: Uppsala, Sweden

PostPosted: Sun Apr 29, 2007 9:18 pm    Post subject: Reply with quote

So new kernel is out.

Any improvements from last one? :)

Any changes in the install order, I assume that "combined_2.6.20.7.patch" is the correct patch to apply. Is there a special fix needed for bcm4311 cards like before?

thanks :)
_________________
From Gentoo with love
Back to top
View user's profile Send private message
JoseJX
Developer
Developer


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Sun Apr 29, 2007 9:21 pm    Post subject: Reply with quote

Use the appropriate patch for your kernel. Larry has released a 2.6.21 patch for 2.6.21 kernels, there is still a little bit that hasn't been accepted for 2.6.21, but will be in 2.6.22.

That said, 2.6.21 does support 4311 quite well.
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
Back to top
View user's profile Send private message
silon
n00b
n00b


Joined: 28 Jan 2006
Posts: 41

PostPosted: Fri May 04, 2007 12:14 pm    Post subject: mini-PCI Dell 1390(bcm4311) on an Inspiron M6400- SUCCESS! Reply with quote

I've finally become cool. Thanks, JoseJX, kernel-2.6.20-r7 and thanks Larry's patches. I'd also like to thank Gentoo, my parents and of course, God.

bcm4311 working. Pretty stable it seems. It took a little while to sort out what was going ary. The wpa_supplicant script appeared to bring the interface up, but no wifi-love light and no IP from dhcpcd. I also had an issue with WPA-PSK where I had to compile the TPIK encryption modules into the kernel to force it to load before the bcm43xx stuff. Yay, cause I have the internal and ExpressCard 4311.

After giving up on wireless for a while(yeah, I could have installed another OS, but am learning far more about Linux from Gentoo than others), I decided to take another look at the thread. I'm so glad I did. I'm so happy now.

24MB is fine by me for now. Any tips on tweaking the connection speed or am I really asking too much? Now, onto to look at the Netgear WG111V2 and rt8187 again.

Seriously, thanks, JoseJX and Larry and to all who shared their struggles. :D

---Infomercial to follow---
Back to top
View user's profile Send private message
Sedrik
l33t
l33t


Joined: 08 Apr 2005
Posts: 639
Location: Uppsala, Sweden

PostPosted: Sat May 05, 2007 9:33 am    Post subject: Re: mini-PCI Dell 1390(bcm4311) on an Inspiron M6400- SUCCES Reply with quote

silon wrote:
I've finally become cool. Thanks, JoseJX, kernel-2.6.20-r7 and thanks Larry's patches. I'd also like to thank Gentoo, my parents and of course, God.

bcm4311 working. Pretty stable it seems. It took a little while to sort out what was going ary. The wpa_supplicant script appeared to bring the interface up, but no wifi-love light and no IP from dhcpcd. I also had an issue with WPA-PSK where I had to compile the TPIK encryption modules into the kernel to force it to load before the bcm43xx stuff. Yay, cause I have the internal and ExpressCard 4311.

After giving up on wireless for a while(yeah, I could have installed another OS, but am learning far more about Linux from Gentoo than others), I decided to take another look at the thread. I'm so glad I did. I'm so happy now.

24MB is fine by me for now. Any tips on tweaking the connection speed or am I really asking too much? Now, onto to look at the Netgear WG111V2 and rt8187 again.

Seriously, thanks, JoseJX and Larry and to all who shared their struggles. :D

---Infomercial to follow---


You've gotten the 4311 chip working over WPA-PSK? I would like to know how. =)
_________________
From Gentoo with love
Back to top
View user's profile Send private message
aaaab130
n00b
n00b


Joined: 05 May 2007
Posts: 5

PostPosted: Sat May 05, 2007 9:20 pm    Post subject: Reply with quote

hi all

am new to gentoo etc so be nice :D

but more to the point been trying to get my wireless working for past 3 days now with no luck.

i can scan for the router but when i try and connect to it i
trying to associate with 00:16:ce:68:8b
wpa_supplicant authentication with 00:00:00:00 timed out

am running wpa_supplicant -ieth1 -Dwext - c/etc/wep_supplicant

on kernel 2.6.21

on a new dell inpiron 6400 with the re-branded boradcom wireless card

my router is Orange/wanadoo live box

anyone got any idea's
Back to top
View user's profile Send private message
aaaab130
n00b
n00b


Joined: 05 May 2007
Posts: 5

PostPosted: Sun May 06, 2007 8:50 am    Post subject: Reply with quote

just an update. well i have manged to get it working :D

only problem is i have to do thing every time i boot up 1st

wpa_supplicant -ieth1 -Dwext -B -c/etc/wpa_supplicant.conf

this will bring up eth1 for and everthing but am not getting an ip so next i

dhcpcd eth1

the auth 00:00:00 only appears to happen when i disconnect then try to reconnect the wirless i hav to reboot to get it working again

i am thinking of added the 2 commands some kind of script.
Back to top
View user's profile Send private message
FJ_Sanchez
n00b
n00b


Joined: 06 May 2007
Posts: 2
Location: Spain

PostPosted: Sun May 06, 2007 12:14 pm    Post subject: Error loading firmware on iBook G4 with 4318 Reply with quote

I've tried almost all... I've emerge hotplug and udev, I've updated the system, tried gentoo-sources, vanilla-sources, Larry's patch... And it still doesn't working for me...

I have emerge vanilla-sources (what is currently on my ppc 2.6.20.6) and applied Larry's correspond path. This is what I get:

Code:
bcm43xx driver
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: Analog: 3, Type 2, Revision 7
bcm43xx: Detected Radio: ID: 8205017f (Manuf: 17f Ver: 2050 Rev: 8)
bcm43xx: Radio turned off
bcm43xx: Radio turned off
udevd-event[9481]: run_program: exec of program '/sbin/udev_run_hotplugd' failed
udevd-event[9482]: run_program: exec of program '/sbin/udev_run_devd' failed
udev-net.sh: /etc/init.d/net.eth1: does not exist or is not executable


As you can see I also gets errors from udev (at startup and power off I get a lot equals)... I've installed hotplug and rc-update add hotplug default (and boot)...

When I do:

Code:
# ifconfig eth1 up
bcm43xx: PHY connected
udevd-event[3163]: run_program: exec of program '/sbin/udev_run_hotplugd' failed
udevd-event[3164]: run_program: exec of program '/sbin/udev_run_devd' failed
bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed.
bcm43xx: core_up for active 802.11 core failed (-2)
SIOCSIFFLAGS: No such file or directory


The firmware is in /lib/firmware (all the files extracted with fwcutter from my MacOSX installation).

Can anyone helps me?
Back to top
View user's profile Send private message
FJ_Sanchez
n00b
n00b


Joined: 06 May 2007
Posts: 2
Location: Spain

PostPosted: Mon May 07, 2007 9:46 am    Post subject: Solved Reply with quote

The problem was with udev, I made a fresh Gentoo 2006.1 install and after I updated all the system and world. The proble is that udev scripts weren't updated as should... So I didn't have any reference to firmware loading in udev rules script. I had to unmerge, delete /etc/udev directory and emerge again udev (I tried regenerating it, but /etc/udev/rules.d dir never changed).

Hope this help more people.

P.S. Should I report this like a bug?
Back to top
View user's profile Send private message
-Craig-
Guru
Guru


Joined: 03 Jun 2004
Posts: 333

PostPosted: Tue May 08, 2007 10:55 pm    Post subject: Reply with quote

After modprobe:
Code:

bcm43xx driver
ACPI: PCI Interrupt 0000:01:03.0[A] -> Link [LNKB] -> GSI 5 (level, low) -> IRQ 5
bcm43xx: Chip ID 0x4306, rev 0x3
bcm43xx: Number of cores: 5
bcm43xx: Core 0: ID 0x800, rev 0x4, vendor 0x4243
bcm43xx: Core 1: ID 0x812, rev 0x5, vendor 0x4243
bcm43xx: Core 2: ID 0x80d, rev 0x2, vendor 0x4243
bcm43xx: Core 3: ID 0x807, rev 0x2, vendor 0x4243
bcm43xx: Core 4: ID 0x804, rev 0x9, vendor 0x4243
bcm43xx: PHY connected
bcm43xx: Detected PHY: Analog: 2, Type 2, Revision 2
bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2)
bcm43xx: Radio turned off
bcm43xx: Radio turned off


Code:

bcm43xx: PHY connected
bcm43xx: Microcode rev 0x127, pl 0xe (2005-04-18  02:36:27)
bcm43xx: Radio turned on
bcm43xx: Radio enabled by hardware
bcm43xx: Chip initialized
bcm43xx: 30-bit DMA initialized
bcm43xx: Keys cleared
bcm43xx: Selected 802.11 core (phytype 2)


# iwlist eth3 scanning
Code:

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

eth3      Scan completed :
          Cell 01 - Address: 00:18:9A:FF:F6:23
                    ESSID:"test"
                    Protocol:IEEE 802.11bg
                    Mode:Master
                    Channel:6
                    Encryption key:on
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
                              11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
                              48 Mb/s; 54 Mb/s
                    Quality=80/100  Signal level=-75 dBm  Noise level=-72 dBm
                    Extra: Last beacon: 244ms ago


It seems to work! I'm just wondering why the message "Warning: Driver for device eth3 has been compiled with version 22" ... appears...any hints?
Back to top
View user's profile Send private message
Sedrik
l33t
l33t


Joined: 08 Apr 2005
Posts: 639
Location: Uppsala, Sweden

PostPosted: Wed May 09, 2007 7:13 am    Post subject: Reply with quote

-Craig- wrote:
...
It seems to work! I'm just wondering why the message "Warning: Driver for device eth3 has been compiled with version 22" ... appears...any hints?


I would guess that it is because you are using the newly released 22 kernel but the wireless-tools package doesn't support it yet? Anyway that's my wild guess.

I get the same error message btw, everything seems to work fine tough
_________________
From Gentoo with love
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 2 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