public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Etaoin Shrdlu <shrdlu@unlimitedmail.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [query] kernel-2.6.24 + ndiswrapper
Date: Wed, 13 Feb 2008 23:18:49 +0100	[thread overview]
Message-ID: <200802132318.49455.shrdlu@unlimitedmail.org> (raw)
In-Reply-To: <e5e065050802131328u165dcf1bjadf847708bb19d8d@mail.gmail.com>

On Wednesday 13 February 2008, dell core2duo wrote:

> Hi all,
>  First of all thank you all.
>   Finally i  got my wireless card working with b43 drivers. But
> throughput is really low :-(.
>[cut]
> flukebox flukebox # iwconfig
> lo        no wireless extensions.
>
> eth0      no wireless extensions.
>
> wmaster0_rename  no wireless extensions.
>
> wlan0     IEEE 802.11g  ESSID:"iitk"
>           Mode:Managed  Frequency:2.442 GHz  Access Point:
> 00:11:95:D8:E3:33
>           Bit Rate=1 Mb/s   Tx-Power=27 dBm
>           Retry min limit:7   RTS thr:off   Fragment thr=2346 B
>           Encryption key:off
>           Link Quality=86/100  Signal level=-41 dBm  Noise level=-69
> dBm Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0 Tx
> excessive retries:0  Invalid misc:0   Missed beacon:0

Uhm, the solution might be as simple as doing "iwconfig wlan0 rate 54M 
fixed". However, I just noticed that the linuxwireless page about b43 
has changed since yesterday; there are new instructions regarding the 
versions of firmware and fwcutter tool to use (011), and specific info 
regarding kernel 2.6.24. Check it out:

http://linuxwireless.org/en/users/Drivers/b43

Tomorrow I too am going to try the new instructions, and read some docs 
to at least try understanding what's going on with the new driver 
architecture (the *80211 stuff).
-- 
gentoo-user@lists.gentoo.org mailing list



  reply	other threads:[~2008-02-13 22:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-09 11:17 [gentoo-user] [query] kernel-2.6.24 + ndiswrapper dell core2duo
2008-02-09 11:32 ` Ian Lee
2008-02-09 11:37   ` dell core2duo
2008-02-09 11:54 ` Etaoin Shrdlu
2008-02-09 11:40   ` dell core2duo
2008-02-09 12:12     ` Etaoin Shrdlu
2008-02-09 12:02       ` dell core2duo
2008-02-09 12:28         ` Etaoin Shrdlu
2008-02-09 21:47           ` Dan Farrell
2008-02-12 17:08             ` dell core2duo
2008-02-12 18:57               ` dell core2duo
2008-02-12 23:11                 ` Etaoin Shrdlu
2008-02-13 21:28                   ` dell core2duo
2008-02-13 22:18                     ` Etaoin Shrdlu [this message]
2008-02-13 22:37                       ` dell core2duo
2008-02-13 22:47                     ` Etaoin Shrdlu
2008-02-15 13:58             ` Iain Buchanan
2008-02-15 18:01               ` dell core2duo
2008-02-18 12:29                 ` Iain Buchanan
2008-02-18 13:07                   ` dell core2duo
2008-02-19  1:05                     ` Iain Buchanan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200802132318.49455.shrdlu@unlimitedmail.org \
    --to=shrdlu@unlimitedmail.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox