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 ... 28, 29, 30 ... 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
JoseJX
Retired Dev
Retired Dev


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Tue Jul 04, 2006 3:32 am    Post subject: Reply with quote

martindv:
Like I said, the driver you have should work fine. If you want one with no errors (it really doesn't matter though) wl_apsta.o (version 3.130) is the correct version. You're not actually using the driver. You're using *only* the firmware with bcm43xx. You need to make sure you have SoftMAC and bcm43xx debugging turned on in your kernel and post the errors in dmesg for us to figure out what's going wrong with your setup.
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
Back to top
View user's profile Send private message
dgulotta
Tux's lil' helper
Tux's lil' helper


Joined: 09 Jan 2006
Posts: 78

PostPosted: Tue Jul 04, 2006 8:05 pm    Post subject: Reply with quote

I've gotten the driver to work sporadically with devicescape in the past, but I can't seem to get it to work at all with 2.6.17.

I'm using an iBook G4 with a Broadcom 4318 chip. I've tried gentoo-sources-2.6.17-r1 and vanilla-sources-2.6.17. Here are the commands that I am running:

modprobe bcm43xx
ifconfig eth0 up
iwlist eth0 scan | less
iwconfig eth0 channel [tried using 1,6,11, or auto, or skipping this step altogether]
iwconfig eth0 essid "MIT"
ifconfig eth0 18.241.6.209 broadcast 18.241.255.255 netmask 255.255.0.0
route add default gw 18.241.0.1

The last two commands work for my wired connection, so it's not a problem of having the wrong IP addresses or netmask.

Sometimes iwlist fails to find any access points; when this happens the dmesg output has a lot of of "ASSERTION FAILED (radio_attenuation > 10)" and "WARNING: Writing invalid LOpair" messages.

Any ideas on what is going wrong?
Back to top
View user's profile Send private message
timotheus25
Apprentice
Apprentice


Joined: 27 Dec 2005
Posts: 162
Location: *upstate* New York, USA

PostPosted: Tue Jul 04, 2006 8:45 pm    Post subject: Reply with quote

dgulotta wrote:
I've gotten the driver to work sporadically with devicescape in the past, but I can't seem to get it to work at all with 2.6.17.


I use the 2.6.17 vanilla on my PowerBook with a BCM4306 chip.
The device seldom works for me unless I explicitly set the txpower, channel, rate, AP in that order:
Code:

ifconfig eth1 down
ifconfig eth1 up
iwconfig eth1 txpower 15
iwconfig eth1 channel 6
iwconfig eth1 rate 11M
iwconfig eth1 ap any
iwconfig eth1 rate 11M
( for n in `seq 12`; sleep 10; iwconfig eth1 channel 6; done ) &

Sometimes the channel drifts to other frequencies even after setting it. So I set it every 10 seconds for the first 2 min.
Also, several bugs disappeared when compiling the kernel with ~gcc-4.1.1 instead of ~gcc-3.4.6 . Now the chip works near 100% of the time.
If the connection bandwidth seems to change to fast, slow, fast, slow, every few minutes, lower the rate or move closer to the physical AP.

To check for receiving packets on the interface, look at the RX field:
Code:

watch -n 2 -d ifconfig eth1

If you see no activity, then your device isn't fully connected, regardless of the IP you see on the interface.
_________________
http://tstotts.net/linux/gentoopb.html
http://tstotts.net/linux/gentooinsp640m.html
Back to top
View user's profile Send private message
coomac
n00b
n00b


Joined: 04 Jul 2006
Posts: 1

PostPosted: Tue Jul 04, 2006 10:11 pm    Post subject: Reply with quote

For those having problems connecting when everything seems to be set up right, make sure your network is set to broadcast the essid. I spent the past two days tinkering with the kernel, the softmac and bcm43xx modules and everything related to wlan, and never had any luck connecting - it never made it past authentication - until I broadcast my essid.
My setup: kernel 2.6.17.3, my laptop is the Acer Ferrari 4006, so I used the bcmwl564.sys firmware from the acer website (looks like the only 64 bit firmware on the list). The encryption is WEP. Also, one thing I noticed with the laptop, although the wifi led starts blinking as soon as ifconfig up is entered, wifi is not really activated unless the button is in the 'on' configuration (dmesg shows this as keycode e055). I hope this helps anyone still having trouble getting bcm43xx to work.
A hearty 'Thank You!' to everyone involved in the project.
Back to top
View user's profile Send private message
martindv
Apprentice
Apprentice


Joined: 16 Jul 2005
Posts: 171
Location: Argentina

PostPosted: Wed Jul 05, 2006 3:30 am    Post subject: Reply with quote

JoseJX wrote:
martindv:
Like I said, the driver you have should work fine. If you want one with no errors (it really doesn't matter though) wl_apsta.o (version 3.130) is the correct version. You're not actually using the driver. You're using *only* the firmware with bcm43xx. You need to make sure you have SoftMAC and bcm43xx debugging turned on in your kernel and post the errors in dmesg for us to figure out what's going wrong with your setup.


Thanks for everthing JoseJX, now i can bring the interface up.. an even scan the wireless network.. i couldent get connected yet... but it suppose its only matter of configuration.
By the way, do you know what driver should i use in WPA_SUPPLICANT for my BCM43xx?

Regards.
_________________
Gentoo Rulez

AMD Athlon XP 2800+ @2.08Ghz
Asus A7V8NX-E-Deluxe
Nvidia Nforce2 chipset
1GB Ram
ASUS GeForce N6600 256MB RAM
2 IDE HDDS @Primary/Secondary Master
1 120GB HDD @Sata Channel #0
Back to top
View user's profile Send private message
JoseJX
Retired Dev
Retired Dev


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Wed Jul 05, 2006 4:03 am    Post subject: Reply with quote

coomac:
That's a known design limitation of SoftMAC (although not broadcasting your SSID is sort of a broken interpretation of the 802.11 specs to begin with.) You can't connect with SoftMAC if your AP isn't either responding to probe requests or sending Beacons. As for the "64 bit" firmware, there is *no* difference between firmware on Windows, OSX, MIPS Linux, 64 bit or 32 bit. They will all work unless you have a manufacturer specific change in your device. We really don't know any of firmware's details other than it's machine independent since it runs completely on the card.

dgulotta:
The fixes for TX Power on the 4318 chipset are really non trivial. It's > 100k of patches that don't yet work and break the 4306 support :p. We're still trying to figure out how the TX Power is adjusted on the 4318 chipsets and until then sometimes connecting is really luck at best. Sorry, but we're working on it. Get closer to the AP and make sure your AP is the only one on the channel and you'll have better luck.

timotheus25:
What do you mean by, "the channel drifts"? Do you see the channel value changing? You should not need to set the rate to 11M, it's set to that automatically.

martindv:
The wext driver should work.
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
Back to top
View user's profile Send private message
timotheus25
Apprentice
Apprentice


Joined: 27 Dec 2005
Posts: 162
Location: *upstate* New York, USA

PostPosted: Wed Jul 05, 2006 4:33 am    Post subject: Reply with quote

JoseJX wrote:

What do you mean by, "the channel drifts"? Do you see the channel value changing? You should not need to set the rate to 11M, it's set to that automatically.


After setting the channel, I sometimes see the frequency changing on the driver. I observe this with:
Code:

watch -d -n 1 iwconfig eth1

It occurs approx. 10 seconds after setting the channel, with 2.6.16 (last all-in-one patchset before merge with official source) it occurred at almost every first-time setup after loading the kernel module. (I've always used the softmac-based drivers.) Now with 2.6.17, it is rare, and unpredictable with reproducing, otherwise I would have already filed a bug on kernel.org.

I need to set the rate for three reasons:
(1) The default on 2.6.16 was 54M on every new modprobe, and I believe on a clean boot that it is also on 2.6.17. It would do 54M even if ESSID was for 802.11b network.
(2) 11M is too high for even the DHCP request if I am very far away from the AP (need to use 1M)
(3) If the card driver loads with the rate I want, I skip setting the rate, set the WEP key, then WEP authentication on open network fails (softmac message in kern.log). But if I set the rate explicitly, even if the same, then the WEP authentication does not fail. This bug disappeared by compiling with gcc-4.1.1 instead of gcc-3.4.6. No idea why.
_________________
http://tstotts.net/linux/gentoopb.html
http://tstotts.net/linux/gentooinsp640m.html
Back to top
View user's profile Send private message
JoseJX
Retired Dev
Retired Dev


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Wed Jul 05, 2006 6:28 am    Post subject: Reply with quote

timotheus25:
Well, anything with 2.6.16 era drivers is suspect to begin with :) The 11M workaround was not merged until well into the 2.6.17 rc phase. I agree that you can have issues at 11M when far from an AP, but you shouldn't need to set the rate more than once if it's 11M you're after. For what it's worth, on my non-preempt system, setting the WEP key works fine without changing the rate. Compiling with gcc-4.1.1 should make no difference, but you could be coming up against races in SoftMAC/bcm43xx, SofTMAC is not paticularly robust. (Sorry!) Out of curiosity, exactly which card do you have? (Paste in the CoreID and Chip Revision lines from dmesg).
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
Back to top
View user's profile Send private message
jb1979
n00b
n00b


Joined: 03 Jul 2006
Posts: 4

PostPosted: Wed Jul 05, 2006 1:27 pm    Post subject: Reply with quote

JoseJX : thanks for the tip ! Indeed, the firmware was not loaded properly... Well now, it is :) My encryption is WPA. How can I set my authentification password using wpa_supplicant ?? Also, I noticed that when I bring my wifi up (LED is ON), it goes down by itself about ~ 30 sec later (LED gets OFF) !! Any clues ??

Many thanks

jb1979
Back to top
View user's profile Send private message
Akaihiryuu
l33t
l33t


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

PostPosted: Wed Jul 05, 2006 2:59 pm    Post subject: Reply with quote

Any idea when the Devicescape branch will be integrated into the mainstream kernel? I'm not impressed with softmac. By turning off preempt on my kernel, I no longer get the "card IRQ register not responding" message, but I still can't connect to anything. It sends an authentication request then usually says either "authentication response received from (my access point) but no queue item exists", or "deauthentication response received from (my access point)", or "open authentication completed with (my access point), sending association request, association request timed out (timeout is immediate, it's like it's not even trying)". Same thing happens whether trying to associate manually or using the Gentoo net.xxx init scripts. At least I'm not getting that IRQ error shutting down the card anymore, but I'm still not able to connect. I've tried everything, setting the channel/tx power manually, setting 11mbit, getting less than 5 feet from the AP, etc, and still nothing. Oh well, looks like I'm gonna be stuck on ndiswrapper for awhile longer. I just hope they don't switch the kernel to 4k stacks before this driver works for me.
Back to top
View user's profile Send private message
JoseJX
Retired Dev
Retired Dev


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Wed Jul 05, 2006 3:35 pm    Post subject: Reply with quote

jb1979:
It sounds like a dhcp client is taking down the interface after not being able to get a lease. This is the most common reason for this, I'm not sure what else might do that.

Akaihiryuu:
Devicescape is not mergable at this time and the interface is still terrible for users. It's being worked on, but will not be merged any time soon. Are you in an area with many APs? Is SoftMAC connecting to a different AP on ifconfig up? If so, then that's probably your problem, I sent a patch for that to netdev a while ago. It'll be in 2.6.18, but for now, you can try patching it yourself: http://dev.gentoo.org/~josejx/softmac-essid.patch
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
Back to top
View user's profile Send private message
earthcreed
n00b
n00b


Joined: 04 Apr 2005
Posts: 5

PostPosted: Thu Jul 06, 2006 2:28 am    Post subject: Card doesn't seem to be recognized (4312) Reply with quote

JoseJX wrote:
I really doubt that you actually have a PCI id of 0x4310, since those aren't PCI-E cards. Can you pastebin the output of lspci -vvn | grep -i 14e4? You probably have an 0x4312, stefano didn't include it in his original patch, an update will be available soon

Thanks.

It seems that I have a 4312, lspci -vvn|grep -i 14e4 outputs

Code:
01:00.0 0280: 14e4:4312 (rev 01)


I have hotplug, coldplug, udev and everything else installed. I followed the directions at the top of the thread, with kernel 2.6.17-r1 and the firmware cutter. When I load the kernel module all dmesg tells me is
Code:
bcm43xx driver

and no new interfaces appear.

Where can I find the patches for the 4312? When I boot the amd64 ubuntu live cd it can see my wireless card, and attempts to load the firmware (where it fails, but at least it can get one step farther than I currently can) so I know they are some drivers out there that can at least see my card.

On a side note, thank you all so much putting so much work into these drivers. I only considered a broadcom machine because of the work you have done. Thanks.
Back to top
View user's profile Send private message
slashdevnull
n00b
n00b


Joined: 22 Jan 2004
Posts: 10

PostPosted: Thu Jul 06, 2006 3:34 am    Post subject: Re: Card doesn't seem to be recognized (4312) Reply with quote

I seem to have exactly the same problem. The driver loads and the dmesg output is similar
Code:
bcm43xx driver


I have 2.6.17.1 with the firmware unpacked in /lib/firmware. This is also on a AMD 64 machine.

However it looks like I have a 4311, lspci -vvn|grep -i 14e4 gives me

Code:
01:00.0 0280: 14e4:4311 (rev 01)


It says it is a Dell 1390
Back to top
View user's profile Send private message
JoseJX
Retired Dev
Retired Dev


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Thu Jul 06, 2006 3:44 am    Post subject: Reply with quote

earthcreed and slashdevnull:
Ubuntu has been extremely difficult for the bcm43xx team to deal with. :p They include broken patches (such as the incomplete 4311/4312 patch) and don't enable debugging in either bcm43xx or SoftMAC. The 4311/4312 patches were written by Stefano, but none of the bcm43xx devs has a 4311/4312 to test with (they appear to be only available as mini-pci-e and none of the devs has a laptop with a mini-pci-e slot. If you know of a mini-pci-e -> pci-e card or would be willing to donate your machine, please let us know). As such, the patches don't seem to work, although there was at least one person who said it worked (unverified). The 10 piece patchset is here: http://marc.theaimsgroup.com/?l=linux-netdev&m=114805420427939&w=2 feel free to test, but no guarantees. I've spec'd as much as I can find in the original driver that's 4311/4312/pci-e specific but these cards are also hit by the same txpower issues as the 4318 series. Let us know if anything works for you, but unless you want to get your hands dirty and help to figure out what's wrong with these cards, you'll have to wait until one of the devs gets a card.

Sorry.
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
Back to top
View user's profile Send private message
slashdevnull
n00b
n00b


Joined: 22 Jan 2004
Posts: 10

PostPosted: Thu Jul 06, 2006 9:06 am    Post subject: 4311 Reply with quote

I am running gentoo on my AMD 64 laptop with the mini-pci-e card. If there is anything you require in terms of debug output I will be more than happy to provide. I will try and patch the 10 piece patch and see if my mileage varies. If any of the devs would like to try out a patch I can try it and report back.
Back to top
View user's profile Send private message
timotheus25
Apprentice
Apprentice


Joined: 27 Dec 2005
Posts: 162
Location: *upstate* New York, USA

PostPosted: Fri Jul 07, 2006 1:14 am    Post subject: Reply with quote

JoseJX wrote:

Compiling with gcc-4.1.1 should make no difference, but you could be coming up against races in SoftMAC/bcm43xx, SofTMAC is not paticularly robust. (Sorry!) Out of curiosity, exactly which card do you have? (Paste in the CoreID and Chip Revision lines from dmesg).


Code:

# dmesg | grep -i bcm43 | head -n 11
[   56.255245] bcm43xx driver
[   56.255403] bcm43xx: Chip ID 0x4306, rev 0x3
[   56.255406] bcm43xx: Number of cores: 5
[   56.255410] bcm43xx: Core 0: ID 0x800, rev 0x4, vendor 0x4243, enabled
[   56.255418] bcm43xx: Core 1: ID 0x812, rev 0x5, vendor 0x4243, disabled
[   56.255426] bcm43xx: Core 2: ID 0x80d, rev 0x2, vendor 0x4243, enabled
[   56.255434] bcm43xx: Core 3: ID 0x807, rev 0x2, vendor 0x4243, disabled
[   56.255442] bcm43xx: Core 4: ID 0x804, rev 0x9, vendor 0x4243, enabled
[   56.258698] bcm43xx: PHY connected
[   56.258709] bcm43xx: Detected PHY: Version: 2, Type 2, Revision 2
[   56.258730] bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2)
# lspci | grep -i bcm43
0001:10:12.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03)


What are the 5 cores for, and why are 3 disabled? I never noticed that before.
_________________
http://tstotts.net/linux/gentoopb.html
http://tstotts.net/linux/gentooinsp640m.html
Back to top
View user's profile Send private message
JoseJX
Retired Dev
Retired Dev


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Fri Jul 07, 2006 2:01 am    Post subject: Reply with quote

Well, this is one of the older cards with less tested code paths, but I think most of your problems have been addressed with Larry's patches that he sent to netdev. You should see better performance with 2.6.18-rc1.

As for the cores, see this page: http://bcm-specs.sipsolutions.net/core_information_registers

They are:
0: Chip Common Core - Contains information about the device and which cores are in here (Enabled to get info)
1: 802.11 Core - Wireless (Not enabled yet)
2: V.90 Core - Modem (Never enabled, we don't even have a driver to write specs for, and it's a win-modem anyway)
3: PCMCIA Core - Disabled, not in use (usually the PCI core is used even on PCMCIA Cards)
4: PCI Core - Enabled, that's how you're using the card
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
Back to top
View user's profile Send private message
slithy
Guru
Guru


Joined: 26 Nov 2005
Posts: 321
Location: Kansas

PostPosted: Fri Jul 07, 2006 8:43 pm    Post subject: Reply with quote

Boy I am having fun. I followed the steps on the first page exact.

Here is the firmware I am using:
Code:
bcm43xx-fwcutter can cut the firmware out of bcmwl5.sys

  filename :  bcmwl5.sys
  version  :  4.10.40.0
  MD5      :  30d20fc98bcfd52e1da778cf19b223d4


dmesg | grep bmc43xx:
Code:
bcm43xx driver
bcm43xx: Chip ID 0x4306, rev 0x3
bcm43xx: Number of cores: 5
bcm43xx: Core 0: ID 0x800, rev 0x4, vendor 0x4243, enabled
bcm43xx: Core 1: ID 0x812, rev 0x5, vendor 0x4243, disabled
bcm43xx: Core 2: ID 0x80d, rev 0x2, vendor 0x4243, enabled
bcm43xx: Core 3: ID 0x807, rev 0x2, vendor 0x4243, disabled
bcm43xx: Core 4: ID 0x804, rev 0x9, vendor 0x4243, enabled
bcm43xx: PHY connected
bcm43xx: Detected PHY: Version: 2, Type 2, Revision 2
bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2)
bcm43xx: Radio turned off
bcm43xx: Radio turned off


Now the fun part:
Code:
ifconfig eth1 up
segmentation fault


Oh I know, lets check dmesg:
Code:
BUG: unable to handle kernel NULL pointer dereference at virtual address 00000000
 printing eip:
f92af58d
*pde = 00000000
Oops: 0000 [#1]
Modules linked in: fglrx bcm43xx ieee80211softmac ieee80211 ieee80211_crypt intel_agp agpg
art
CPU:    0
EIP:    0060:[<f92af58d>]    Tainted: P      VLI
EFLAGS: 00010246   (2.6.17-gentoo-r1 #3)
EIP is at bcm43xx_chip_init+0x366/0x8de [bcm43xx]
eax: 00000000   ebx: f7a1cc28   ecx: c18df0c0   edx: f8838000
esi: f92c69ca   edi: 00000000   ebp: f7a1cd64   esp: f6ba9e40
ds: 007b   es: 007b   ss: 0068
Process ifconfig (pid: 8894, threadinfo=f6ba8000 task=f6b65a90)
Stack: 05000246 c192a000 00000000 00000000 62000080 33346d63 695f7878 7674696e
       35306c61 0077662e 00000000 00000000 00000000 00000000 00000000 00000000
       00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Call Trace:
 <f92b139c> bcm43xx_init_board+0x397/0xac7 [bcm43xx]  <c02f7deb> dev_open+0x2a/0x60
 <c02f6c66> dev_change_flags+0x47/0xe6  <c032312a> devinet_ioctl+0x243/0x54f
 <c02f0c8e> sock_ioctl+0x157/0x179  <c02f0b37> sock_ioctl+0x0/0x179
 <c01473de> do_ioctl+0x16/0x48  <c014760a> vfs_ioctl+0x1fa/0x211
 <c014764d> sys_ioctl+0x2c/0x43  <c0102397> sysenter_past_esp+0x54/0x75
Code: d8 e8 64 ee ff ff 85 ff 74 16 e9 8a 05 00 00 68 f2 69 2c f9 bf fe ff ff ff e8 de 0b
e6 c6 eb d9 8b 83 90 04 00 00 31 ff 8b 53 14 <8b> 30 8b 68 04 81 c2 60 01 00 00 b8 00 00 0
0 03 e8 d9 da f6 c6
EIP: [<f92af58d>] bcm43xx_chip_init+0x366/0x8de [bcm43xx] SS:ESP 0068:f6ba9e40


bcm43xx owned the system. Anyone know how to fix this?
Back to top
View user's profile Send private message
JoseJX
Retired Dev
Retired Dev


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Fri Jul 07, 2006 9:25 pm    Post subject: Reply with quote

slithy:
First, don't use 4.xx firmware, they're broken. Use wl_apsta.o instead. How much ram do you have?
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
Back to top
View user's profile Send private message
slithy
Guru
Guru


Joined: 26 Nov 2005
Posts: 321
Location: Kansas

PostPosted: Fri Jul 07, 2006 9:30 pm    Post subject: Reply with quote

I have 2x512MB, so 1024MB. Where can I get that suggested firmware? I just downloaded the windows driver for my wifi card and pulled the 4.xx from that.
Back to top
View user's profile Send private message
JoseJX
Retired Dev
Retired Dev


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Fri Jul 07, 2006 9:47 pm    Post subject: Reply with quote

SInce the link in the readme is dead, I'll post it here: http://drinus.net/airport/wl_apsta.o
Google found it pretty quickly though. :p

You may have problems with >= 1GB of ram, Broadcom only gave us 30 bits for DMA, so that could be the problem too. We'll see, try the firmware first.
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
Back to top
View user's profile Send private message
slithy
Guru
Guru


Joined: 26 Nov 2005
Posts: 321
Location: Kansas

PostPosted: Fri Jul 07, 2006 10:24 pm    Post subject: Reply with quote

Using the suggested firmware fixed that the previous problem. Thanks.
Back to top
View user's profile Send private message
jb1979
n00b
n00b


Joined: 03 Jul 2006
Posts: 4

PostPosted: Sat Jul 08, 2006 2:02 pm    Post subject: Reply with quote

Well, I can't go further without help.... I really don't know what else to try...

I'm using ndiswrapper (lsmod show that it's loaded).

Here is what gives iwconfig:

IEEE 802.11g ESSID:"MyNetwork"
Mode: Managed Frequency: 2.462 GHz Acces Point : XX:XX:XX:XX:XX:XX
Bit rate=54 Mb/s Tx-power: 25 dBm
RTS thr:off Fragment thr:off
Encryption key: MY KEY Security mode: restricted
Power management : off
Link Quality: 100/100 Signal Level: -38 dBm Noise Level: -256 dBm
Rx Invalid nwid:0 Rx invalid crypt:0 Rx invalid frag: 0
Tx excessive retries: 0 Invalid misc: 15352 Missed Beacon: 0


When I dmesg ndiswrapper i have the following bad line:

ndiswrapper (iw_set_freq:370): setting configuration failed (00010003)

What's going wrong here ?


Thanks for your help !!
Back to top
View user's profile Send private message
jb1979
n00b
n00b


Joined: 03 Jul 2006
Posts: 4

PostPosted: Sat Jul 08, 2006 2:21 pm    Post subject: Reply with quote

I
: have found a clue (I hope):


dmesg ndiswrapper gives:

pci: Bound Device 0000:03:02.0 to Driver ndiswrapper

whereas dmesg gives:

ACPI: PCI interrupt for device 0000:03:02.0 disabled

Is there a problem here and if so what should I do ??

Thanks
Back to top
View user's profile Send private message
JoseJX
Retired Dev
Retired Dev


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Sat Jul 08, 2006 4:25 pm    Post subject: Reply with quote

This thread has nothing to do with ndiswrapper, this thread is only for bcm43xx, the open driver.

Sorry.
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
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 ... 28, 29, 30 ... 40, 41, 42  Next
Page 29 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