Date: Sun, 31 Mar 2013 12:49:48 -0500 From: Joshua Isom <jrisom@gmail.com> To: Adrian Chadd <adrian@freebsd.org> Cc: "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org> Subject: Re: ath not working after a motherboard and ram upgrade Message-ID: <5158773C.4080201@gmail.com> In-Reply-To: <CAJ-VmomBT=BeAbNEs2o8vOH9cwdwvEzmY=%2B_O1EUYF4s68F_9g@mail.gmail.com> References: <51578BAC.4090608@gmail.com> <CAJ-Vmo=ztG4%2BREqAC=x-pKkr7PpV=Wk8ZBKZ2u3HM1rwxLgOqQ@mail.gmail.com> <515826B9.6070509@gmail.com> <51585558.8040202@gmail.com> <CAJ-VmomBT=BeAbNEs2o8vOH9cwdwvEzmY=%2B_O1EUYF4s68F_9g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I seems someone working on the kernel's already figured out how to deal with this. The hw.physmem sysctl can be set at boot time, with 2Gb it seems to be working fine. I reinstalled all the sticks, and it's working fine with the sysctl set to 2Gb. On 3/31/2013 12:29 PM, Adrian Chadd wrote: > ... 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 in the > lower 32 bits of physical memory :) > > > > > Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5158773C.4080201>