Works fine.
Thank you, Adrian
On Friday 19 April 2013 14:57:12 Adrian Chadd wrote:
> Hi!
>
> Ok, please update to -HEAD and retest!
>
>
>
> adrian
>
> On 19 April 2013 06:26, Adrian Chadd wrote:
> > oo good to know! let me setup the chainmask info whether or not
> > the 11n option is set
Hi!
Ok, please update to -HEAD and retest!
adrian
On 19 April 2013 06:26, Adrian Chadd wrote:
> oo good to know! let me setup the chainmask info whether or not
> the 11n option is set.
>
> thanks!
>
>
> adrian
>
> On 19 April 2013 04:08, Artyom Mirgorodskiy
> wrote:
>> Adrian, I found th
oo good to know! let me setup the chainmask info whether or not
the 11n option is set.
thanks!
adrian
On 19 April 2013 04:08, Artyom Mirgorodskiy
wrote:
> Adrian, I found the problem.
>
> I'm use ath as module, so ATH_ENABLE_11N is not defined. When I define
> ATH_ENABLE_11N - everything w
Adrian, I found the problem.
I'm use ath as module, so ATH_ENABLE_11N is not defined. When I define
ATH_ENABLE_11N - everything work.
Artyom Mirgorodskiy
On Friday 19 April 2013 13:27:21 wrote:
Updated. However I did not see chainmask information.
See attached
On Friday 19 April 2013 00:57
Hi,
I've just committed some changes to -HEAD. Please update to the latest
-HEAD and paste me the ath0 dmesg output.
It will include the chainmask information.
Thanks,
Adrian
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailm
Ok. I'll add some tidyups to head tonight and then add some more verbose
logging.
I don't have any 64 bit machines to test ar9287 on atm.
Sent from my Palm Pre on AT&T
On Apr 18, 2013 3:52 PM, Artyom Mirgorodskiy
wrote:
Nothing :(
On Thursday 18 April 2013 15
Nothing :(
On Thursday 18 April 2013 15:22:49 Adrian Chadd wrote:
> Hm! I wonder..
>
> Edit if_athvar.h - change sc_rxchainmask and sc_txchainmask in
> ath_softc to be uint32_t, rather than int.
>
> See if that helps.
>
>
>
> Adrian
>
> On 18 April 2013 15:20, Artyom Mirgorodskiy
> wrote:
>
On 18 April 2013 15:54, Artyom Mirgorodskiy
wrote:
> Nothing :(
Ok, so I wonder now whether we're actually getting the right chainmask
at startup.
edit if_ath.c, look for 'ath_hal_getrxchainmask()'
After the rx/tx chainmask is fetched,a dd this:
device_printf(sc->sc_dev, "%s: RX chainmask=0x%x
Hm! I wonder..
Edit if_athvar.h - change sc_rxchainmask and sc_txchainmask in
ath_softc to be uint32_t, rather than int.
See if that helps.
Adrian
On 18 April 2013 15:20, Artyom Mirgorodskiy
wrote:
> See attached
>
>
>
> On Thursday 18 April 2013 15:08:36 Adrian Chadd wrote:
>
>> On 18 April
On 18 April 2013 15:07, Artyom Mirgorodskiy
wrote:
> See attached
>
What the hell? Those masks are really wrong.
Try adding this line after it:
ath_hal_printf(ah, "%s: pcap rx=0x%x, tx=0x%x; configured rx=0x%x,
tx=0x%x\n", __func__, pCap->halRxChainMask, pCap->halTxChainMask,
rx_chainmask, tx_c
On 18 April 2013 14:43, Artyom Mirgorodskiy
wrote:
> Did not work.
>
Hm. Ok.
Let's add some debugging:
inside of ar5416SetChainMasks(), let's add a printf() at the -end- of
the function:
ath_hal_printf(ah, "%s: txchainmask=0x%x, rxchainmask=0x%x\n",
__func__, AH5416(ah)->ah_tx_chainmask, AH541
Did not work.
On Thursday 18 April 2013 13:58:23 Adrian Chadd wrote:
> On 18 April 2013 13:33, Artyom Mirgorodskiy
> wrote:
> > Yes. I tested 247287 and it breaks.
>
> Hm.
>
> Well, not much changed there.
>
> Try going to 247287 (ie, the broken revision), but revert
> head/sys/dev/ath/ath_hal
On 18 April 2013 13:33, Artyom Mirgorodskiy
wrote:
> Yes. I tested 247287 and it breaks.
Hm.
Well, not much changed there.
Try going to 247287 (ie, the broken revision), but revert
head/sys/dev/ath/ath_hal/ar5416/ar5416_xmit.c to 247286.
See if that fixes it.
Adrian
Yes. I tested 247287 and it breaks.
On Thursday 18 April 2013 13:31:29 Adrian Chadd wrote:
> On 18 April 2013 11:58, Artyom Mirgorodskiy
> wrote:
> > Yes, HEAD everything else except the wifi code (ath).
> >
> > Last working revision is 247286. So problem in revision 247287.
>
> That's really od
On 18 April 2013 11:58, Artyom Mirgorodskiy
wrote:
> Yes, HEAD everything else except the wifi code (ath).
>
> Last working revision is 247286. So problem in revision 247287.
That's really odd. It behaves perfectly fine on my system.
You've tested 247287 and it breaks?
Adrian
_
On Thursday, April 18, 2013 12:41:53 pm Adrian Chadd wrote:
>
> ... Why would it differ for the same machine, different kernel?
I can't tell you why, but if you compare the full dmesg's you will see
that several devices all changed their BIOS-assigned IRQs because the BIOS
decided to shuffle the
Yes, HEAD everything else except the wifi code (ath).
Last working revision is 247286. So problem in revision 247287.
On Thursday 18 April 2013 10:42:15 Adrian Chadd wrote:
> Hm, so -HEAD everything else except the wifi code?
>
> That's really odd. I updated to -HEAD this morning just to test th
Hm, so -HEAD everything else except the wifi code?
That's really odd. I updated to -HEAD this morning just to test the
AR9287 for you and it was peachy!
Adrian
On 18 April 2013 10:36, Artyom Mirgorodskiy
wrote:
> Yes
>
>
>
> On Thursday 18 April 2013 10:30:33 Adrian Chadd wrote:
>
> On head?
>
Yes
On Thursday 18 April 2013 10:30:33 Adrian Chadd wrote:
On head?
Adrian
Sent from my Palm Pre on AT&T
Artyom MirgorodskiyOn Apr 18, 2013 10:06 AM,
wrote:
I tried to check out revision 245031 (only sys/dev/ath) and got a working WiFi.
I'll try to find a bro
On head?
Adrian
Sent from my Palm Pre on AT&T
On Apr 18, 2013 10:06 AM, Artyom Mirgorodskiy
wrote:
I tried to check out revision 245031 (only sys/dev/ath) and got a working WiFi.
I'll try to find a broken revision.
On Thursday 18 April 2013 11:37:17 John
I tried to check out revision 245031 (only sys/dev/ath) and got a working WiFi.
I'll try to find a broken revision.
On Thursday 18 April 2013 11:37:17 John Baldwin wrote:
> On Thursday, April 18, 2013 11:22:38 am Adrian Chadd wrote:
> > Ok, the relevant / interesting bit:s. John, any ideas?
>
>
... Why would it differ for the same machine, different kernel?
Adrian
Sent from my Palm Pre on AT&T
On Apr 18, 2013 8:40 AM, John Baldwin wrote:
On Thursday, April 18, 2013 11:22:38 am Adrian Chadd wrote:
> Ok, the relevant / interesting bit:s. John, any ideas?
Only t
On Thursday, April 18, 2013 11:22:38 am Adrian Chadd wrote:
> Ok, the relevant / interesting bit:s. John, any ideas?
Only that this means absolutely nothing? These are the values the BIOS wrote
into the registers which we use as hints about whether or not ACPI lies about
which interrupts are us
Ok, the relevant / interesting bit:s. John, any ideas?
HEAD:
pcib2: irq 18 at device 28.2 on pci0
pcib0: allocated type 3 (0xe050-0xe05f) for rid 20 of pcib2
pcib2: domain0
pcib2: secondary bus 10
pcib2: subordinate bus 10
pcib2: memory decode 0xe050-0xe
Sigh.
Someone's broken the bus or interrupt handling code between -9 and
-head. Or ACPI, for all I know. It may even be something to do with
RFKILL.
Can you please boot verbosely, both on -9 and -head? you don't have to
do anything - just capture the logfile /var/run/dmesg.boot and attach
them he
No interrupts at all:
interrupt total rate
irq1: atkbd0 474 1
irq9: acpi0 95 0
irq22: ehci1 504 1
irq23: ehci01037 3
irq256: hpet0:t0
I've just tested -HEAD on a WB197 (AR9287 + bluetooth.) It works fine.
I think it's very likely something to do with the bus enumeration. Can
you do a vmstat -i, see if you've seen any ath interrupts?
adrian
___
freebsd-wireless@freebsd.org mailing li
Ok, no obvious errors during scanning that would explain this.
Hm!
I'll stick an AR9287 in a test laptop today and give it a whirl.
Adrian
On 18 April 2013 06:41, Artyom Mirgorodskiy
wrote:
> See attached
>
>
>
>
>
> Preloaded elf obj module "/boot/kernel/if_ath.ko" at 0x80d2aef8.
>
>
See attached
Preloaded elf obj module "/boot/kernel/if_ath.ko" at 0x80d2aef8.
Preloaded elf obj module "/boot/kernel/if_ath_pci.ko" at 0x80d2db10.
ath0: mem 0xe050-0xe050 irq 18 at device 0.0 on pci10
ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
ath0: 11g rates: 1Mbps 2Mbp
Hm, paste the relevant dmesg lines from the boot into here?
I'll reboot into an AR9287 today and see what happened.
Thanks,
Adrian
On 18 April 2013 06:25, Artyom Mirgorodskiy
wrote:
> Hi
> I just updated to FreeBSD-current and found that the WiFi does not work on my
> laptop.
> ifconfig wla
30 matches
Mail list logo