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 ... 9, 10, 11 ... 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
zeuss1414
Guru
Guru


Joined: 23 Mar 2004
Posts: 490

PostPosted: Wed Jan 04, 2006 2:25 pm    Post subject: Reply with quote

Quote:
Have you looked in wpa_supplicant.conf.example?? Does the WEP only example not work from there?


I try the wep.conf in the example directory of wpa_supplicant source but it use 64bit Wep key and I dont find how to repalce it by 128bit wep key
Back to top
View user's profile Send private message
ed-209
n00b
n00b


Joined: 26 Dec 2005
Posts: 2

PostPosted: Wed Jan 04, 2006 5:46 pm    Post subject: No AP found Reply with quote

This works flawlessly up until the point that I need to scan for the AP. It absolutely has not found it ever. I've tried fwcutter on multiple drivers and even tried a few different softMACs with no luck. The AP is a westell 327W. While it has a ESSID, WEP and WPA are deactivated.

Channel 6
Mode Mixed
4x Support Disabled
Hide SSID Disabled
wireless security: disabled
MAC Filtering: disabled
Beacon Period: 200
RTS Threshold: 2347 (iwconfig shows RTS trx: off for eth2)
Fragmentation Threshold: 2346
Preamble Algorithm: Always Long
Slot Time Algorithm: Local STA's
PBCC Algorithm: Enhanced Dynamic
ERP Protection Algorithm: Always Off
Supported Rates b: Basic: 1M Yes: 2M 5.5M 11M 22M
Supported Rates g: 6M 9M 12M 18M 24M 36M 48M 54M

I do suspect my AP because inserting the mods is flawless, no dmesg indications of any problem except one, something about ASSERTION FAILED: (radio attenuation < 10) in phy, something about find_lopair(). I assume this is because the NIC is turned off when the mod is inserted. Any help with this issue would be appreciated.

Regards,
ed-209
Back to top
View user's profile Send private message
mhershbe
n00b
n00b


Joined: 07 Oct 2004
Posts: 9
Location: Gainesville, FL

PostPosted: Wed Jan 04, 2006 7:30 pm    Post subject: Reply with quote

tanawana wrote:
mhershbe:
Code:
bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed.


Ever get passed this?? Seems I have the same troubles and results you have come up with, and am quite stuck now.


tanawana wrote:

mhershbe:

Code:
bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed.



Ever get passed this?? Seems I have the same troubles and results you have come up with, and am quite stuck now.


I didn't. I have a builtin broadcom card with pciid: 14e4:4318 (rev 02).

I have used fwcutter to extract microcode for every driver I could find, including the drivers in the README. I did not extract drivers from the listed windows executables, however.

This error seems to be pervasive for me, even though the file "bcm43xx_microcode5.fw" exists in /lib/firmware with the other files.

Good luck.
Compaq V2424NR Turion64 Broadcom 4318.


Negative, still a no go here. I really have nothing left to try that I am aware of. Anyone have any other ideas for success???
Back to top
View user's profile Send private message
bz31
Tux's lil' helper
Tux's lil' helper


Joined: 20 Apr 2005
Posts: 108

PostPosted: Wed Jan 04, 2006 8:21 pm    Post subject: Reply with quote

mhershbe, tanawana, ...:
Just an idea, maybe doesn't help.
I don't know how udev and hotplug work on gentoo.
On my debian unstable, to upgrade to package udev >= 0.070 must remove the package hotplug because hotplug is now part of udev.


Last edited by bz31 on Wed Jan 04, 2006 8:28 pm; edited 1 time in total
Back to top
View user's profile Send private message
zeuss1414
Guru
Guru


Joined: 23 Mar 2004
Posts: 490

PostPosted: Wed Jan 04, 2006 8:25 pm    Post subject: Reply with quote

Finally I configure my home net to use WPA but now the sta_up.sh script work without error.
I had the default gateway but when I want to ping my ibook from another computer I got :
Code:

 ping 192.168.1.102
PING 192.168.1.102 (192.168.1.102) 56(84) bytes of data.
From 192.168.1.5 icmp_seq=1 Destination Host Unreachable
From 192.168.1.5 icmp_seq=2 Destination Host Unreachable
From 192.168.1.5 icmp_seq=3 Destination Host Unreachable
From 192.168.1.5 icmp_seq=5 Destination Host Unreachable
From 192.168.1.5 icmp_seq=6 Destination Host Unreachable
From 192.168.1.5 icmp_seq=7 Destination Host Unreachable
From 192.168.1.5 icmp_seq=8 Destination Host Unreachable
From 192.168.1.5 icmp_seq=9 Destination Host Unreachable
From 192.168.1.5 icmp_seq=10 Destination Host Unreachable
From 192.168.1.5 icmp_seq=12 Destination Host Unreachable
From 192.168.1.5 icmp_seq=13 Destination Host Unreachable


And tcpdump display :
Code:
tcpdump "host 192.168.1.102"
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
21:17:33.905805 arp who-has 192.168.1.102 tell fixe.rambaldi.biz
21:17:34.917852 arp who-has 192.168.1.102 tell fixe.rambaldi.biz
21:17:35.917911 arp who-has 192.168.1.102 tell fixe.rambaldi.biz
21:17:36.917976 arp who-has 192.168.1.102 tell fixe.rambaldi.biz
21:17:37.962048 arp who-has 192.168.1.102 tell fixe.rambaldi.biz
21:17:38.962108 arp who-has 192.168.1.102 tell fixe.rambaldi.biz
21:17:39.962173 arp who-has 192.168.1.102 tell fixe.rambaldi.biz
21:17:40.990237 arp who-has 192.168.1.102 tell fixe.rambaldi.biz
21:17:41.990301 arp who-has 192.168.1.102 tell fixe.rambaldi.biz
21:17:42.990358 arp who-has 192.168.1.102 tell fixe.rambaldi.biz


I don't know what to do !!
Back to top
View user's profile Send private message
zeuss1414
Guru
Guru


Joined: 23 Mar 2004
Posts: 490

PostPosted: Wed Jan 04, 2006 8:36 pm    Post subject: Reply with quote

Yeah now it works, I just launch wpa_passphrase again and modify my wpa_suplicant.conf.

Thanks to the develloper for her very good job and for the help everyone :lol: :lol: :lol:
Back to top
View user's profile Send private message
Fugee47
Apprentice
Apprentice


Joined: 25 Nov 2004
Posts: 196
Location: Germany

PostPosted: Thu Jan 05, 2006 6:22 pm    Post subject: Reply with quote

has anyone got kismet working ? i have read that there is support in the svn-version of kismet.

Fugee



Excellent work !!!!
Back to top
View user's profile Send private message
lordfirebird
n00b
n00b


Joined: 24 May 2004
Posts: 43

PostPosted: Fri Jan 06, 2006 5:51 am    Post subject: Reply with quote

I am in the same boat as mhershbe and tanawana.

Code:

bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed.


I'm beginning to suspect it is an AMD64 issue. We may even want to report it upstream? I'm running a Compaq Presario V2000 with an Turion64 and the same card (BCM4318) as mshershbe. When I run sta_up.sh I get the same errors as well. (SIOC... whatever... I lost what it was, it's the exact same as mhershbe's though)

Anyway, I think I might take a break at pounding away at it for a bit, or maybe try softMAC to see if that would work. I'll keep checking in and hopefully the problem with get a solution eventually!
Back to top
View user's profile Send private message
JoseJX
Retired Dev
Retired Dev


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Fri Jan 06, 2006 6:43 am    Post subject: Reply with quote

It's not an AMD64 problem, there have been plenty of people for whom it works fine. Check your hotplug config and make sure that you've put the firmware in the directory it's supposed to be found.
_________________
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: 1172
Location: Edinburgh, UK

PostPosted: Fri Jan 06, 2006 11:51 am    Post subject: Reply with quote

Hi, I just received the 2.6.15-gentoo sources on ~x86 and would like to give this a shot at some point. Can I just check if I am correct on the following:

1) Using softMAC you can use WEP with wireless-tools (wpa-supplicant is not needed) but you need to patch the kernel for this

2) Using devicescape you can use WEP or WPA, but you need to use wpa-supplicant in either case

I am interested to move to WPA also eventually, but I am not gonna try to do both at the same time. I'm trying to decide which to do first...
Back to top
View user's profile Send private message
scoobydu
Veteran
Veteran


Joined: 16 Feb 2003
Posts: 1076
Location: 'Mind the Gap'

PostPosted: Fri Jan 06, 2006 3:01 pm    Post subject: Reply with quote

Havin_it wrote:
Hi, I just received the 2.6.15-gentoo sources on ~x86 and would like to give this a shot at some point. Can I just check if I am correct on the following:

1) Using softMAC you can use WEP with wireless-tools (wpa-supplicant is not needed) but you need to patch the kernel for this

2) Using devicescape you can use WEP or WPA, but you need to use wpa-supplicant in either case

I am interested to move to WPA also eventually, but I am not gonna try to do both at the same time. I'm trying to decide which to do first...



1) Yes, except you don't need to patch the kernel, only build module and insert (see instructions in first post, kernel patch is for dscape)

2) Yes, and yes with wpa_supplicant needing to be patched, as well as a kernel patch being applied too.

Why people use WEP any more is beyond me, but by all means give it a try ;) it'll be another AP for me to use on my travels 8)
_________________
Tyan Tiger K8W, 2xOpteron 240,Powerbook5,6 15" 1.5g, Macbook Black 2g, Mac Mini 1g, Ipod P60g.
| Linux - From a windows user perspective|
Back to top
View user's profile Send private message
Havin_it
Veteran
Veteran


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

PostPosted: Sat Jan 07, 2006 12:46 pm    Post subject: Re: WEP with softmac Reply with quote

scoobydu wrote:
1) Yes, except you don't need to patch the kernel, only build module and insert (see instructions in first post, kernel patch is for dscape)


I was wondering why I'd thought otherwise and looked over the thread again, found this post (on about page 8). Can you confirm/deny?

Anarchy wrote:
As the patch was sent to ml most are not aware. WEP support is possible with softmac if you patch the ieee80211 stack in your vanilla-2.6.15_rc7 sources for example. I have put the patch up on my devspace so have at it!! http://dev.gentoo.org/~anarchy/ieee80211.patch Once you patch and compile follow same instructions on first page to bring up the interface, configure eth? I have noticed auto negotiate rate is not working so 11M is safe bet for right now. I have had it as high as 36M when sitting right on top of AP. This uses softmac NOT dscape for those of you who might become confused :) Have fun.

In case your wondering I am posting this from my bcm4318 with wep enabled :p

eth1 IEEE 802.11b/g ESSID:"2WIRE972" Nickname:"Anarchy"
Mode:Managed Frequency=2.462 GHz Bit Rate=12 Mb/s Tx-Power=2346 dBm
RTS thr:off Fragment thr:off
Encryption key:xxxx-xxxx-xx Security mode:open

Of course I am not gonna provide my key but that gives you an example!!


Has this changed? Perhaps Anarchy, if reading, can confirm. This might be a factor in the build problem I'm having. I'm following the steps from page 1 but using yesterday's snapshots, not svn. Softmac built without any bad messages, fwcutter gave me this:

Code:
pengi bcm43xx-fwcutter-20060106 # /usr/local/bin/fwcutter /mnt/win_d/bcmwl5.sys .
fwcutter can cut the firmware out of /mnt/win_d/bcmwl5.sys
  filename :  bcmwl5.sys
  version  :  3.30.15.0
  MD5      :  ebf36d658d0da5b1ea667fa403919c26

extracting bcm43xx_microcode2.fw ...
extracting bcm43xx_microcode4.fw ...
extracting bcm43xx_microcode5.fw ...
*****: Sorry, it's not posible to extract "bcm43xx_microcode11.fw".
*****: Extracting firmware from an old driver is bad. Choose a more recent one.
*****: Luckily bcm43xx driver doesn't include microcode11 uploads at the moment.
*****: But this can be added in the future...
extracting bcm43xx_pcm4.fw ...
extracting bcm43xx_pcm5.fw ...
extracting bcm43xx_initval01.fw ...
extracting bcm43xx_initval02.fw ...
extracting bcm43xx_initval03.fw ...
extracting bcm43xx_initval04.fw ...
extracting bcm43xx_initval05.fw ...
extracting bcm43xx_initval06.fw ...
extracting bcm43xx_initval07.fw ...
*****: Sorry, initval08 is not available in driver file "/mnt/win_d/bcmwl5.sys".
*****: Extracting firmware from an old driver is bad. Choose a more recent one.
*****: Luckily bcm43xx driver doesn't include initval08 uploads at the moment.
*****: But this can be added in the future...
extracting bcm43xx_initval09.fw ...
extracting bcm43xx_initval10.fw ...


Then got the following when I tried to make the driver:

Code:
pengi bcm43xx-fwcutter-20060106 # cd /usr/src/bcm43xx/bcm43xx-20060106
pengi bcm43xx-20060106 # SOFTMAC_DIR=/usr/src/bcm43xx/ieee80211softmac-20060106 make
make -C /lib/modules/2.6.15-gentoo/build M=/usr/src/bcm43xx/bcm43xx-20060106 modules
make[1]: Entering directory `/usr/src/linux-2.6.15-gentoo'
  CC [M]  /usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.o
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c: In function `bcm43xx_release_firmware':
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c:2230: error: structure has no member named `firmware_norelease'
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c:2232: error: structure has no member named `ucode'
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c:2233: error: structure has no member named `ucode'
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c:2234: error: structure has no member named `pcm'
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c:2235: error: structure has no member named `pcm'
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c:2236: error: structure has no member named `initvals0'
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c:2237: error: structure has no member named `initvals0'
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c:2238: error: structure has no member named `initvals1'
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c:2239: error: structure has no member named `initvals1'
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c: In function `bcm43xx_request_firmware':
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c:2250: error: structure has no member named `ucode'
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c:2254: error: structure has no member named `ucode'
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c:2263: error: structure has no member named `pcm'
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c:2268: error: structure has no member named `pcm'
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c:2277: error: structure has no member named `initvals0'
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c:2308: error: structure has no member named `initvals0'
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c:2315: error: structure has no member named `initvals0'
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c:2321: error: structure has no member named `initvals1'
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c:2343: error: structure has no member named `initvals1'
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c:2350: error: structure has no member named `initvals1'
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c: In function `bcm43xx_upload_microcode':
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c:2380: error: structure has no member named `ucode'
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c:2381: error: structure has no member named `ucode'
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c:2390: error: structure has no member named `pcm'
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c:2391: error: structure has no member named `pcm'
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c: In function `bcm43xx_upload_initvals':
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c:2438: error: structure has no member named `initvals0'
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c:2439: error: structure has no member named `initvals0'
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c:2440: error: structure has no member named `initvals1'
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c:2441: error: structure has no member named `initvals1'
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c:2442: error: structure has no member named `initvals1'
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c: In function `bcm43xx_remove_one':
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c:4473: error: structure has no member named `ucode'
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c: In function `bcm43xx_chip_reset':
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c:4493: error: structure has no member named `firmware_norelease'
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c:4496: error: structure has no member named `firmware_norelease'
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c: In function `bcm43xx_suspend':
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c:4547: error: structure has no member named `firmware_norelease'
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c:4549: error: structure has no member named `firmware_norelease'
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c: At top level:
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c:658: warning: 'bcm43xx_disassociate' defined but not used
/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.c:687: warning: 'bcm43xx_associate' defined but not used
make[2]: *** [/usr/src/bcm43xx/bcm43xx-20060106/bcm43xx_main.o] Error 1
make[1]: *** [_module_/usr/src/bcm43xx/bcm43xx-20060106] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.15-gentoo'
make: *** [modules] Error 2


I have also tried SOFTMAC_DIR=/usr/src/bcm43xx (the parent dir of the three sets of source) which seemed to match closer the path given on page 1 - no different. Any idea what I'm doing wrong?

scoobydu wrote:
Why people use WEP any more is beyond me, but by all means give it a try ;) it'll be another AP for me to use on my travels 8)


You'll have to get past the guard-dogs downstairs first ;) Nah seriously, if I were looking for a free ride I'd probably pick my neighbours who don't encrypt at all. I though about being helpful and telling them, but I might need the service myself someday :twisted:
Back to top
View user's profile Send private message
Havin_it
Veteran
Veteran


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

PostPosted: Sat Jan 07, 2006 5:03 pm    Post subject: Reply with quote

WORKING! I am now up and running with a relative minimum of fuss. I tried one of the newer revisions of the driver (the Belkin card only used Broadcom chips up to card Rev3, which is what I had) from a Dell package. I also updated my snapshots to today's (20060107). Result, got one less complaint from fwcutter:
Code:
pengi fwcutter # /usr/local/bin/fwcutter "/mnt/win_c/Documents and Settings/robin/Desktop/R83097/IR/bcmwl5.sys"
fwcutter can cut the firmware out of /mnt/win_c/Documents and Settings/robin/Desktop/R83097/IR/bcmwl5.sys
  filename :  bcmwl5.sys
  version  :  3.40.73.0
  MD5      :  52d67c5465c01913b03b7daca0cc4077

extracting bcm43xx_microcode2.fw ...
extracting bcm43xx_microcode4.fw ...
extracting bcm43xx_microcode5.fw ...
*****: Sorry, it's not posible to extract "bcm43xx_microcode11.fw".
*****: Extracting firmware from an old driver is bad. Choose a more recent one.
*****: Luckily bcm43xx driver doesn't include microcode11 uploads at the moment.
*****: But this can be added in the future...
extracting bcm43xx_pcm4.fw ...
extracting bcm43xx_pcm5.fw ...
extracting bcm43xx_initval01.fw ...
extracting bcm43xx_initval02.fw ...
extracting bcm43xx_initval03.fw ...
extracting bcm43xx_initval04.fw ...
extracting bcm43xx_initval05.fw ...
extracting bcm43xx_initval06.fw ...
extracting bcm43xx_initval07.fw ...
extracting bcm43xx_initval08.fw ...
extracting bcm43xx_initval09.fw ...
extracting bcm43xx_initval10.fw ...


Everthing after that went off successfully, though there are still a lot of 'undefined' warnings during make bcm43xx. Also the 'commit' suffix when issuing iwconfig commands (maybe this isn't so important anyway, sometimes I needed it with ndiswrapper) gives the following error:

Code:
pengi bcm43xx # iwconfig eth1 key <my key> commit
Error for wireless request "Commit changes" (8B00) :
    SET failed on device eth1 ; Operation not supported.


The commands still work anyway so this doesn't upset much ;)

Would it be worth trying even newer revs of the bcmwl5 driver, to see if that fwcutter error can be quashed? Or would too-new firmware likely break compatibility with my older card?

Sidenote: Neither of the LEDs on the card is doing anything. Is this normal?
Back to top
View user's profile Send private message
darklesi
n00b
n00b


Joined: 23 Jul 2004
Posts: 12
Location: Portugal

PostPosted: Sat Jan 07, 2006 7:17 pm    Post subject: Reply with quote

darklesi wrote:
i have notice that dhcp works fine with cisco ap's and others but not with linksys ... i saw that more ppl have problems with linksys ap's and i was wondering if any of you have discovered a reason for this?

Thanks and sorry for my bad english :o


Hi there ... I just want to report that with the last changes in the softmac driver i was able to solve it. Btw i tested the devicescape version too and it works just fine.

Good job ppl ;)

Cheers
Back to top
View user's profile Send private message
ruben
Guru
Guru


Joined: 04 Jul 2003
Posts: 462

PostPosted: Sat Jan 07, 2006 7:28 pm    Post subject: Reply with quote

darklesi wrote:
Hi there ... I just want to report that with the last changes in the softmac driver i was able to solve it. Btw i tested the devicescape version too and it works just fine.

Did you change the sta_up.sh script to use dhcp? I also have a Linksys router, and i think that dhcp worked when i did not use encryption. Now however, on both softmac and devicescape, i can't get it to work. When can the dhcp broadcast be done? I tried it after the sta_up.sh script. Are you using it without encryption? I'm using WEP encryption.
Back to top
View user's profile Send private message
tbone
n00b
n00b


Joined: 01 Oct 2002
Posts: 4

PostPosted: Sat Jan 07, 2006 7:50 pm    Post subject: Reply with quote

I see that some people continue to have problems loading the firmware depite putting it in the correct directory and also having udev and hotplug running.
I tried a number of drivers and still got this message after doing ifconfig eth0 up:

bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed.

I noticed that someone mentioned having coldplug running as well. I emerged this and set it to start at boot. Suddenly everything worked! I am sending this wirelessly!

Hope this helps.
Back to top
View user's profile Send private message
bz31
Tux's lil' helper
Tux's lil' helper


Joined: 20 Apr 2005
Posts: 108

PostPosted: Sat Jan 07, 2006 7:53 pm    Post subject: Reply with quote

ruben:
You don't need to run the script sta_up.sh.
I use add_sta, iwconfig, ifconfig and wpa_supplicant. See the last 20 lines of sta_up.sh.
Back to top
View user's profile Send private message
loorbaer
n00b
n00b


Joined: 07 Jan 2006
Posts: 1

PostPosted: Sat Jan 07, 2006 10:49 pm    Post subject: Reply with quote

Hi there,

I decided to try the dscape stack. Patching the kernel and the wpa_supplicant was no problem at all , also booted the new kernel and loaded the modules "rate_control" and "80211" successfully. but when I try to compile bcm43xx_dscape driver (date: 07012006) I get the following error message:
Quote:

make -C /lib/modules/2.6.15/build M=/usr/src/bcm43xx-dscape-20060107 modules
make[1]: Entering directory `/usr/src/linux-2.6.15'
CC [M] /usr/src/bcm43xx-dscape-20060107/bcm43xx_dma.o
/usr/src/bcm43xx-dscape-20060107/bcm43xx_dma.c: In function `dma_tx_fragment':
/usr/src/bcm43xx-dscape-20060107/bcm43xx_dma.c:755: error: structure has no member named `req_tx_status'
/usr/src/bcm43xx-dscape-20060107/bcm43xx_dma.c:756: error: structure has no member named `rate_ctrl_probe'
make[2]: *** [/usr/src/bcm43xx-dscape-20060107/bcm43xx_dma.o] Error 1
make[1]: *** [_module_/usr/src/bcm43xx-dscape-20060107] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.15'
make: *** [modules] Error 2

It would be nice, if somebody can summerize the two approaches to a newbie compatible howto (e.g. for the gentoo-wiki) about installing those drivers.


thx in advance
loorbaer[/quote]
Back to top
View user's profile Send private message
lordfirebird
n00b
n00b


Joined: 24 May 2004
Posts: 43

PostPosted: Sun Jan 08, 2006 8:00 am    Post subject: Kernel Panic! Reply with quote

So, I setup the hotplug and put in the firmware as said to do. (Doing the dscape method) And then patched wpa_supplicant (0.4.7) all good and proper like. However, now, when the script reached the part that it runs.

wpa_supplicant -B -Ddscape -ista0 -c/etc/wpa_supplicant.conf

I get a kernel panic! Right after the wpa_supplicant message it says:
FIXME wpa_driver_dscape_set_countermeasures entered

Then I get the following panic message and have to manually reset the computer. (Have to manually type it out)

Code:

skb_over_panic: text:ffffffff8808eb5b len:0 put:82 head:ffff6100168d010 data:ffff8100168dd062 tail:ffff8100168dd000 end:ffff8100168dd080 dev:<NULL>
----------- [cut here ] --------- [please bite here ] ---------
Kernel BUG at net/core/skbuff.c:94
invalid operand: 0000 [1]
CPU 0
Modules linked in: bcm43xx snd_seq_oss snd_seq_device snd_seq... (The rest of the alsa modules)
Pid: 0, comm: swapper Not tainted 2.6.15-rc7 #2

.......


On second thought, if anyone wants me to get the whole thing I'll do it. However, I think the key line is the one that mentions skbuff. I had to make the modification said in earlier posts to get the driver working in the 64-bit kernel.

Quote:
Actually, it worked fine on my 64-bit machine. I had to patch /usr/src/linux/include/linux/skbuff.h. I don't have a patch file, but you have to find the declaration for struct sk_buff and change cb[40]; to cb[48];.


I'm running the mainline vanilla kernel (pulled out of portage)... and other than that I'm a newbie as to what more information to give. =) All the patching went cleanly... and the sk_buff thing I did manually... and I just checked and it has been set to cb[48]. Should I maybe try different firmware or stuff like that? Anyway, help appreciated and I'll gladly give any info that is needed upon request.

Thanks,
-Kyle

Update:
I switched to the firmware to the wl_aptra.o firmware mentioned earlier in the forum and I no longer get a kernel panic. However, now when the script reachs "ifconfig wlan0.11 up" I get the error "SIOCSIFFLAGS: No such file or directory"... so.. still not working is bottom line I guess. ;)


Last edited by lordfirebird on Sun Jan 08, 2006 8:33 am; edited 1 time in total
Back to top
View user's profile Send private message
garryma
n00b
n00b


Joined: 08 Jan 2006
Posts: 2

PostPosted: Sun Jan 08, 2006 8:17 am    Post subject: /usr/src/linux/include/net/ieee80211.h Reply with quote

loorbaer wrote:
Hi there,

/usr/src/bcm43xx-dscape-20060107/bcm43xx_dma.c:755: error: structure has no member named `req_tx_status'
/usr/src/bcm43xx-dscape-20060107/bcm43xx_dma.c:756: error: structure has no member named `rate_ctrl_probe'
loorbaer
[/quote

modify struct ieee80211_tx_status
add 2 lines
unsigned int rate_ctrl_probe:1;
unsigned int req_tx_status:1;
Back to top
View user's profile Send private message
lordfirebird
n00b
n00b


Joined: 24 May 2004
Posts: 43

PostPosted: Sun Jan 08, 2006 8:46 am    Post subject: Re: Kernel Panic! Reply with quote

lordfirebird wrote:
So, I setup the hotplug and put in the firmware as said to do. (Doing the dscape method) And then patched wpa_supplicant (0.4.7) all good and proper like. However, now, when the script reached the part that it runs.

wpa_supplicant -B -Ddscape -ista0 -c/etc/wpa_supplicant.conf

I get a kernel panic! Right after the wpa_supplicant message it says:
FIXME wpa_driver_dscape_set_countermeasures entered

Then I get the following panic message and have to manually reset the computer. (Have to manually type it out)

Code:

skb_over_panic: text:ffffffff8808eb5b len:0 put:82 head:ffff6100168d010 data:ffff8100168dd062 tail:ffff8100168dd000 end:ffff8100168dd080 dev:<NULL>
----------- [cut here ] --------- [please bite here ] ---------
Kernel BUG at net/core/skbuff.c:94
invalid operand: 0000 [1]
CPU 0
Modules linked in: bcm43xx snd_seq_oss snd_seq_device snd_seq... (The rest of the alsa modules)
Pid: 0, comm: swapper Not tainted 2.6.15-rc7 #2

.......


On second thought, if anyone wants me to get the whole thing I'll do it. However, I think the key line is the one that mentions skbuff. I had to make the modification said in earlier posts to get the driver working in the 64-bit kernel.

Quote:
Actually, it worked fine on my 64-bit machine. I had to patch /usr/src/linux/include/linux/skbuff.h. I don't have a patch file, but you have to find the declaration for struct sk_buff and change cb[40]; to cb[48];.


I'm running the mainline vanilla kernel (pulled out of portage)... and other than that I'm a newbie as to what more information to give. =) All the patching went cleanly... and the sk_buff thing I did manually... and I just checked and it has been set to cb[48]. Should I maybe try different firmware or stuff like that? Anyway, help appreciated and I'll gladly give any info that is needed upon request.

Thanks,
-Kyle

Update:
I switched to the firmware to the wl_aptra.o firmware mentioned earlier in the forum and I no longer get a kernel panic. However, now when the script reachs "ifconfig wlan0.11 up" I get the error "SIOCSIFFLAGS: No such file or directory"... so.. still not working is bottom line I guess. ;)


P.P.S: It would have helped if I had ran make installfw with the new firmware :P It still gives the kernel panic with different firmware.
Back to top
View user's profile Send private message
darklesi
n00b
n00b


Joined: 23 Jul 2004
Posts: 12
Location: Portugal

PostPosted: Sun Jan 08, 2006 9:49 am    Post subject: Reply with quote

ruben wrote:
darklesi wrote:
Hi there ... I just want to report that with the last changes in the softmac driver i was able to solve it. Btw i tested the devicescape version too and it works just fine.

Did you change the sta_up.sh script to use dhcp? I also have a Linksys router, and i think that dhcp worked when i did not use encryption. Now however, on both softmac and devicescape, i can't get it to work. When can the dhcp broadcast be done? I tried it after the sta_up.sh script. Are you using it without encryption? I'm using WEP encryption.


Hi ... I forgot to mention that softmac was tested with an open network and devicescape with an WPA. However, dhcp could be working in old releases of softmac but i had some problems in my head and i didn't much time to test this. So i tested and as nobody reported that was resolved i took the liberty to do that ;).

Change the sta_up.sh? no ... i get it to work in the same way of bz31
bz31 wrote:
ruben:
You don't need to run the script sta_up.sh.
I use add_sta, iwconfig, ifconfig and wpa_supplicant. See the last 20 lines of sta_up.sh.
Back to top
View user's profile Send private message
ruben
Guru
Guru


Joined: 04 Jul 2003
Posts: 462

PostPosted: Sun Jan 08, 2006 1:55 pm    Post subject: Reply with quote

@bz31 & @darklesi:
I'm sure you mean it well and I appreciate you trying to help, but it honestly doesn't help me much. I already looked at the source for sta_up.sh, and tried to somewhere fit in the dhcp, but so far it doesn't work. Maybe I should better describe what I did. So if you manually do what sta_up.sh does, you get something like:
Code:
1. killall wpa_supplicant 2>/dev/null
2. add_sta wlan0 sta0
3. iwconfig wlan0.11 mode managed
4. ifconfig wlan0.11 up
5. ifconfig sta0 hw ether mac-from-wireless-card
6. ifconfig sta0 192.168.1.111
7. ifconfig sta0 up
8. iwconfig sta0 mode managed
9. wpa_supplicant -B -Ddscape -ista0 -c/etc/wpa_supplicant.conf
10. route add default gw 192.168.1.1

I clearly don't want 6, so I dropped 6 from the former. Then, between 7 and 8, I tried "dhclient sta0", but that does not work. Then I thought, wpa_supplicant (configured to use WEP) is something standing between sta0 and wlan0, right? So, I did 1 to 9, except 6, and after 9, I do "dhclient sta0". Does not work either. Then I was wondering whether maybe the dhcp needs to be done from the 'physical' interface and I tried "dhclient wlan0.11". Not working either. So, either I'm doing something wrong, or either it's still not working with my particular access point (Linksys WRT54G v2).
Back to top
View user's profile Send private message
bz31
Tux's lil' helper
Tux's lil' helper


Joined: 20 Apr 2005
Posts: 108

PostPosted: Sun Jan 08, 2006 2:29 pm    Post subject: Reply with quote

ruben wrote:
... or either it's still not working with my particular access point (Linksys WRT54G v2).

Maybe you should retry dhcp using the latest svn bcm43xx_dscape.
I have just re-tested dhcp. It woks for the first time for me ! (AP D-Link DI 624+).
Back to top
View user's profile Send private message
Havin_it
Veteran
Veteran


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

PostPosted: Sun Jan 08, 2006 3:27 pm    Post subject: Reply with quote

Blimey - I just tried monkeying with one of the newer drivers in ndiswrapper, that didn't work, now it's puking on the driver I was using previously. Looks like there's no going back now 8O so let me wish Godspeed to the devs in getting bcm43xx fine-tuned and into Portage..!

I tried doing other things to replace wlan0 with eth1 and ndiswrapper with bcm43xx:

- added "alias eth1 bcm43xx" to /etc/modules.conf
- added "bcm43xx" to /etc/modules.autoload.d/kernel-2.6
- replaced wlan0 with eth1 in /etc/conf.d/wireless
- made a net.eth1 link in /etc/init.d/ and added it to default runlevel (removing net.wlan0)

The result is that on boot, eth1 is ifconfig'ed, the routes and DNS are setup, but the iwconfigs (key and essid) aren't set. Also I have yet to see whether roaming profiles will work - I guess not, as these are set per-ESSID.
I would also just say that, contrary to Anarchy's findings, in my case the speed (54Mbps) *was* auto-detected. (Unless iwconfig LIES!)

Still, it's very pleasing to see such a reliable result already. Things can only get better!

Now, about those LEDs - anyone else got lights yet?
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 ... 9, 10, 11 ... 40, 41, 42  Next
Page 10 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