kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: me@tobin.cc (Tobin C. Harding)
To: kernelnewbies@lists.kernelnewbies.org
Subject: wifi not detected. Ubuntu 16.04.1 4.8.0.39-generic
Date: Tue, 28 Feb 2017 12:28:18 +1100	[thread overview]
Message-ID: <20170228012818.GA3322@eros> (raw)
In-Reply-To: <CAKF=xo+zXKB7VbbcAX+hqJs67WgKfUMM4buuinKmNy0ioyMx5g@mail.gmail.com>

On Thu, Feb 23, 2017 at 11:49:39AM -0800, Vasu M wrote:
> Hi,
> 
> Not sure if this is a correct forum to discuss but I am facing an issue on
> Ubuntu 16.04.1 64 bit kernel 4.8.0-39-generic using wifi adapter
> AR2413/AR241 which is running ATH5K version 4.8.0.39-generic. If this is
> not the correct alias, please excuse and suggest the right alias.

4.8.0.39-generic is not currently supported. Perhaps you could try
upgrading to a supported kernel. The Ubuntu 16.04 LTS installs 4.4.0
on my machine. You may like to try compiling a newer custom kernel.

See https://www.kernel.org/ for list of supported kernels.

Good luck,
Tobin.

> 
> After a cold reboot, the NM is not detecting the WIFI. Machine is not able
> to recover from this. I also restarted network manager and reloaded the
> driver but didn't fix the issue.
> 
> Tried:
> sudo rmmod -f ath5k
> (got a msg --  disconnected - you are offline)
> sudo rfkill unblock all
> sudo modprobe ath5k (Nothing happened)
> 
> When i check the /etc/modprobe.d/blacklist-ath_pci.conf, I see the
> following -
> 
> #For some Atheros 5K RF MACs, the madwifi driver loads but fails to
> #correctly initialize the hardware, leaving it in a state from which ath5k
> #cannot recover. To prevent this condition, stop madwifi from loading by
> #default. Use Jockey to select one driver or the other. (Ubuntu #315056,
> #323830)
> blacklist ath_pci
> 
> There are some bugs reported in the past but I don't come across anything
> that was reported in the latest kernel which is similar. Not sure if this
> is a bug still lurking around but I found someone reporting a similar
> problem here -
> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1569590.
> 
> Any guidance is much appreciated.
> 
> Thanks,
> Vasu

> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


-- 
Tobin Harding
http://tobin.cc

      reply	other threads:[~2017-02-28  1:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-23 19:49 wifi not detected. Ubuntu 16.04.1 4.8.0.39-generic Vasu M
2017-02-28  1:28 ` Tobin C. Harding [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170228012818.GA3322@eros \
    --to=me@tobin.cc \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).