From: Larry Finger <larry.finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
To: evan foss <evanfoss-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org
Subject: Re: [PATCH V2] bcm43xx: Fix failure to deliver PCI-E interrupts
Date: Sun, 14 Jan 2007 17:54:30 -0600 [thread overview]
Message-ID: <45AAC2B6.50902@lwfinger.net> (raw)
In-Reply-To: <4a55afb80701132228q2e264606mf8948a45507e59ea-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
evan foss wrote:
> Results so far....
> In a word Wow. It still doesn't work but I suspect that is could just
> be my configuration. Power levels are not being reported correctly all
> the time iwlist works but nothing else to my knowledge. I remember
> there being talk of power level reporting patches. Is there anything I
> can try adding. For the first time in a long time it does associate
> with AP's but I can't dhcpcd eth1. I am using an access point next
> door. Mine is down. I will test it with a good one at school on
> Tuesday.
>
> ####To recap I am on...
> MFG: Compaq V3000 (V3019US)
> CPU: AMD Turion 64 x2
> Kernel: linux-2.6.18-gentoo-r2
> I have SMP on and I am in 64 bit.
> BCM Chip: BCM4311
> BCM FW: V3 Sorry I don't recall exactly what version
>
> ####Patches used
> patch_2.6.18.1_fix_leds
> patch_2.6.18.1_for_PCI-E
> radio_hwenable_for_2.6.18
To get signal levels reported correctly, you also need patch_2.6.18.1_signal_quality.
> ####The following work
> ifconfig eth1 up
> iwconfig eth1 essid NAME channel #
> kismet -c bcm43xx,eth1,bcm43xx
> iwlist eth1 scan <-the power levels are reported here
>
> ####The following don't work
> iwconfig <-the power levels are reported as always being 0
> kismet <-no power levels are reported
> LED <-always off (I have a slider switch on the front to turn radio on/off)
This one needs watching. The LED has worked on previous computers.
> dhcpcd eth1 <-low transmit power???
Most likely. How far are you from the AP?
> #####The following don't work but might be my fault (I will get back
> to you later on these)
> dhcpcd eth1
>
> #####example bad iwconfig power level reporting
> eth1 IEEE 802.11b/g ESSID:"linksys" Nickname:"Broadcom 4311"
> Mode:Managed Frequency=2.437 GHz Access Point: 00:16:B6:43:DE:C4
> Bit Rate=1 Mb/s Tx-Power=18 dBm
> RTS thr:off Fragment thr:off
> Encryption key:off
> 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
The received signal and noise levels should be fixed by the patch listed above.
Larry
next prev parent reply other threads:[~2007-01-14 23:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-12 18:08 [PATCH V2] bcm43xx: Fix failure to deliver PCI-E interrupts Larry Finger
[not found] ` <45a7ceb2.m02aaCgouBsadVk/%Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2007-01-12 18:50 ` Stephen Sinclair
[not found] ` <9b3e2dc20701121050p52e13d92r1ec78e1881bbed3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-01-12 19:01 ` Michael Buesch
[not found] ` <200701122001.45546.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
2007-01-12 19:27 ` Larry Finger
[not found] ` <45A7F501.9080202@docksud.com.ar>
2007-01-12 22:59 ` evan foss
[not found] ` <4a55afb80701121459q4f23083t6f92a7e3bc85ccb1-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-01-14 6:28 ` evan foss
[not found] ` <4a55afb80701132228q2e264606mf8948a45507e59ea-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-01-14 18:14 ` evan foss
2007-01-14 23:54 ` Larry Finger [this message]
2007-01-12 18:53 ` Michael Buesch
[not found] ` <200701121953.44630.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
2007-01-12 19:18 ` evan foss
2007-01-12 19:30 ` Larry Finger
[not found] ` <1168881379.2481.46.camel@flanders.rdu.redhat.com>
[not found] ` <45ABC0D5.3060008@lwfinger.net>
[not found] ` <4a55afb80701151502q7bf8bbabp7507a42f072efd29@mail.gmail.com>
[not found] ` <45AC41C4.2070401@lwfinger.net>
2007-01-18 12:52 ` evan foss
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=45AAC2B6.50902@lwfinger.net \
--to=larry.finger-tq5ms3gmjblk1umjsbkqmq@public.gmane.org \
--cc=Bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org \
--cc=evanfoss-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.