Date: Fri, 19 Feb 2016 20:23:28 +0100 From: Tino Engel <tino.engel@hotmail.com> To: "pyunyh@gmail.com" <pyunyh@gmail.com> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: RE: Support for Killer E2400 Ethernet Message-ID: <DUB109-W99D4D77FA57EA21A1AAA1798A00@phx.gbl> In-Reply-To: <20160219012612.GA1267@michelle.fasterthan.co.kr> References: <DUB109-W140BA030126A753EEE1E8F398AF0@phx.gbl>, <20160219012612.GA1267@michelle.fasterthan.co.kr>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks very much for the quick reply. So let me shed some words on your input: First: Limiting the memory size did not help at all=2C nothing changed. Unfortunetly I cannot post the whole results of the sysctl=2C since I canno= t get this box into the net=2C and it is quite too much to type it by hand. Is there any special value you are interested in? Then I applied your patch. The requested output is: alc0: DMA CFG : 0x0c347c54 The bad thing: The error still persists. :( It always writes "DMA write error" now followed by "DMA CFG : ..." One more thing: The ping -s command results in the same error as trying to fetch something = from the internet. Do you have any further ideas? Thanks! From: pyunyh@gmail.com Date: Fri=2C 19 Feb 2016 10:26:12 +0900 To: tino.engel@hotmail.com Subject: Re: Support for Killer E2400 Ethernet CC: freebsd-net@freebsd.org On Thu=2C Feb 18=2C 2016 at 04:17:30PM +0100=2C Tino Engel wrote: >=20 >=20 >=20 > Hello all=2C > I am trying to establish support for the Killer E2400 ethernet adapter. > I am following the approach that works for the linux driver=2C which is b= asically:- Add the E2400 device ID- Copy all device related stuff from the = E2200 > What works:- DHCP- Ping any host in the internet > What does not work:- Downloading stuff using "fetch"- Setup pkg- Therefor= e cannot browse since I even cannot install pkg in order to obtain a browse= r > The error message I continously receive is "alc0: DMA write error". > I have so far played with all the loader tunables and sysctls supported b= y the alc driver=2C but no improvement of the situation. > Any ideas how to proceed? =20 Due to lack of access to Killer E2200 controller=2C alc(4) was not fully tested for the controller. One user also reported that alc(4) shows DMA errors as you saw. To narrow down the issue=2C could you please add the following to /boot/loader.conf file and test it again if your system has more than 4GB memory? =20 hw.physmem=3D"3G" =20 The tunable above will limit system memory to 3GB. Also show me the output of "sysctl dev.alc.0.stats" before and after running "ping -s 1472 remote_ip_addr" command. (Note=2C the ping command with -s option requires root privilege and you have to reboot to take changes effect). =20 If limiting system memory have no effect=2C could you try attached patch and let me know whether it makes any difference? The patch will print "alc0: DMA CFG : 0xXXXXXXXX". Let me know the value of XXXXXXXX. =20 Thanks. _______________________________________________=0A= freebsd-net@freebsd.org mailing list=0A= https://lists.freebsd.org/mailman/listinfo/freebsd-net=0A= To unsubscribe=2C send any mail to "freebsd-net-unsubscribe@freebsd.org" = =
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DUB109-W99D4D77FA57EA21A1AAA1798A00>