Date: Thu, 28 Jul 2016 15:19:50 -0400 From: Mason Loring Bliss <mason@blisses.org> To: FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Disappointment with wifi... Message-ID: <20160728191950.GF4313@blisses.org>
next in thread | raw e-mail | index | archive | help
--oxour8c+zPVguRmP
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Hi all. I'm coming to you with a minor existential crisis. :)
I've got a Thinkpad T420, initially purchased as my best bet for FreeBSD
hardware compatibility. For wifi it has Centrino Advanced-N 6205 [Taylor
Peak].
I did a fresh install of 11.0-BETA2 the other day, and that worked well
enough, up to and including finding local wifi and initially connecting.
However, on boot, dhclient keeps saying, repeatedly:
send_packet: Network is down
send_packet: No buffer space available
=2E..and of course my network is largely unusable this way. It seems to come
and go, but I can't predict it.
I know it's a volunteer project, and I know that laptops aren't a priority,
especially as compared with servers, but I'd really like for this to work.
The last time I tried to tackle something like this myself, however, it went
badly - I had an onboard Realtek gigabit NIC, and the best I could get was a
brute-force reset of the driver when it would fall over. I made an initial
effort to compare the (functionally flawless, as far as I could see) Linux
driver with ours, but I quickly got lost. I've never attained the lofty
heights of kernel hacking and I completely lacked context to understand the
code.
What would you folks recommend, given a strong interest in seeing FreeBSD
support my T420 well enough for me to be able to use fully? Running FreeBSD
in an interactive role is going to be the best way for me to maintain my
interest in pushing it forward, finding pain points to bring up, etc., and
this laptop is one of my most heavily-used systems, as I'm using it whenever
I'm not at a desk. I could just go back to RHEL on it, but I'd like to take
the opportunity to address this issue and make the world a better place.
It looks like we've had support for this chip for a while... I see it
mentioned a number of times in SVN:
http://svnweb.freebsd.org/base/head/sys/dev/iwn/if_iwn.c?view=3Dlog
Revision 285234 from last year looks interesting... It notes issues with
HT40. I see my local network using HT20, so I would expect this to not
describe my issue, but it does make me wonder if there's anything I can set
to influence driver behaviour. Nothing jumps out at me from iwn(4).
Thanks in advance for ideas and direction.
--=20
Mason Loring Bliss (( If I have not seen as far as others, it is because
mason@blisses.org )) giants were standing on my shoulders. - Hal Abels=
on
--oxour8c+zPVguRmP
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCgAGBQJXmlrWAAoJEJ6yV3B27yVVArYP/0fT/1KoFgRT8MlW/WqeyR9H
c8Pws61VxTwOcNdmMwxPWTn8kfh7J5HYabI6T6vJjSdxIWo4YAT5PQN3jq+ZMfyN
GbDfH+fFOXFMI31i1bDSIF1DjnCOi2a0vg5cNbA140RrhsYUpAbMjGPHvCsPuXeE
nzb4MZ1Ax6qGKscBmN/NocOG0RFU/Vf9Sql4Sn6iPyogOEHHM1vRvPxeMKRI+RwK
y086jLlqa27bzV9Sq7EQN5GkbrjmVUquHaBpMRhD4W8nmpgCB88DN+Ah1Q9bCe5E
LLBk9CqmkmVsEMo89cVp2GcfHGLFp0fhUuTElo6JKEe2uSwdQAAN7G2qtz5aZofx
IKEUmzJkG86YWR/VbnnBx9PGbGsZN41pEveqPEQhKTolLrtWzBmKsggAzpHHsAQB
OEHhU9/+/wNRvlf02sCmNjJ3+I4yHvX4Y+cSRvOX56mblcHYuQ8ttSl9mPvXuWN6
j4j8QspHW0/5np0sWer9GkeciRErONx9ouykQPfu+nUkl4MF4OXfpRBP2p6w9iSb
FmKIshSs/V/8aGvQUqckm2+7YDcbz2yM8ASd9jEk0siEqAMHD/WkPV9+noqsumVM
XDP6kp5W4wWC9gATN9zoaxGSihQz1rJH6kE3bq3icb72Oh8jceTPZhaaiowp8iAd
WY1k+Slzc97lwP2c4KZY
=3Qyr
-----END PGP SIGNATURE-----
--oxour8c+zPVguRmP--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160728191950.GF4313>