One thing I forgot is that the LED will be on only if the switch is in the on
position _AND_ the
interface is UP.
Yes I figured that out. (eventually)
>>> dhcpcd eth1 <-low transmit power???
>> Most likely. How far are you from the AP?
>
> This is a timeout issue. I tried to apply t
I sent this to the list but I don't know if it got to the list.
On 1/14/07, evan foss <[EMAIL PROTECTED]> 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 t
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
You can get the 2.6.18 patches from
ftp://lwfinger.dynalias.org/patches. You will need the PCI-E
patch for 2.6.18.1, and will probably want the
patch_2.6.18.1_fix_leds and radio_hwenable_for_2.6.18
patches if your radio has a switch.
Thank you I will try it when I get the time.
--
http://ww
This hunk is OK, but I just want to point out that bustype is
always equal to BCM43xx_BUSTYPE_PCI ;)
The 0x53 timeouts are for an SSB-BUS.
So strictly said this hunk is a NOP.
The other hunks are OK, too. They fix real bugs.
Thanks for spotting them, Larry!
So then what fixed int's for Stephen
