does downgrading the motherboard/ram fix it?
You were already running 64 bit, right? What if you just boot with 2gb of ram?
adrian
On 30 March 2013 18:04, Joshua Isom jri...@gmail.com wrote:
I've been longing to upgrade my motherboard and ram, and with a tax refund
it came time. The
I spoke too soon, it can still degrade, it's just takes longer to
happen. This is with `ping -i .25 192.168.1.1`
64 bytes from 192.168.1.1: icmp_seq=743 ttl=64 time=1.595 ms
64 bytes from 192.168.1.1: icmp_seq=765 ttl=64 time=1.696 ms
64 bytes from 192.168.1.1: icmp_seq=771 ttl=64 time=3.118
If I drop down to one 8Gb stick, and I don't have other wifi devices
near causing interference, I can get a reliable connection and low loss.
If I have 16Gb, I can get about a minute or two of decent ping times
before it degrades to multi-second pings of the router. Even at 8Gb,
it's not
I tried updating today to the new code, it seemed to make it worse and
never get decent ping times. With the code from before, it's dependent
on boot, either it will work fine on boot or fail.
But it has to be related to the handled npkts 0 message. When I'm
getting no messages, it's
... that message is because it's scanning. :-)
Try booting it with only 2GB of physical RAM.
It may be something odd to do with how the DMA code works; the ath NIC
is a 32 bit PCI device. I need to make sure it's totally 64 bit clean
- not only 64 bit pointer clean, but all the mbufs need to be
I switched it to 4Gb shortly after you mentioned 32 bit pci. I've been
using amd64 for so long I forgot about 32 bit memory limits.
On 3/31/2013 1:38 PM, Adrian Chadd wrote:
On 31 March 2013 10:49, Joshua Isom jri...@gmail.com wrote:
I seems someone working on the kernel's already figured
From if_ath.c:2995: For some situations (eg EDMA TX completion),
there isn't a requirement for the ath_buf entries to be allocated.
The EDMA code uses malloc, but would contigmalloc work instead?
On 3/31/2013 1:38 PM, Adrian Chadd wrote:
On 31 March 2013 10:49, Joshua Isom jri...@gmail.com
Hi. I'm looking to get a netbook or small laptop for FreeBSD. I've only
run it on servers and desktops in the past, so I'm unsure about some of
the hardware requirements. I'd like to be able to connect to wifi with no
auth, wep, wpa and wpa2 and be able to fully utilize the aircrack-ng suite
of
Joshua Isom jri...@gmail.com writes:
On 3/31/2013 9:49 AM, Raphael Kubo da Costa wrote:
The first error I got was in ar9300_radio.c:90 -- clang complained
`ichan' was not being used.
I keep forgetting about this, but if you open the file go to line 89
and change the ifdef to '#if 0' it'll
The problem isn't contigmalloc, it's making sure that it gets bounced via the
local 32 bits of address space right.
I'll talk with other developers and see what the deal is with 64 bit address
space for 32 bit nics.
Thanks,
Adrian
Sent from my Palm Pre on ATamp;T
On Mar 31, 2013 3:47 PM,
Look in ath/makefile .. At the bottom. There's clang warning overrides there.
Uncomment them!
Adrian
Sent from my Palm Pre on ATamp;T
On Mar 31, 2013 11:54 AM, Raphael Kubo da Costa lt;rak...@freebsd.orggt;
wrote:
Adrian Chadd lt;adr...@freebsd.orggt; writes:
gt; I've just updated the
Old Synopsis: 20%-100% packet loss with iwn driver
New Synopsis: [iwn] 20%-100% packet loss with iwn driver
Responsible-Changed-From-To: freebsd-bugs-freebsd-wireless
Responsible-Changed-By: linimon
Responsible-Changed-When: Sun Mar 31 23:03:19 UTC 2013
Responsible-Changed-Why:
Over to
Hi,
On Sun, 31 Mar 2013 19:55:46 -
s...@tormail.org wrote:
Hi. I'm looking to get a netbook or small laptop for FreeBSD. I've
only run it on servers and desktops in the past, so I'm unsure about
some of the hardware requirements. I'd like to be able to connect to
wifi with no auth, wep,
.. anything with an Atheros PCI/PCIe chipset will work.
The only chipset I don't have support for atm is:
* AR5523, but i doubt you'll ever see this unless you still use cardbus;
* QCA9880 and derivates (11ac) - but that won't work at the moment and
likely won't do raw injection more for
14 matches
Mail list logo
