All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes.sorensen@gmail.com>
To: Julia Lawall <julia.lawall@lip6.fr>,
	 Katherine Dunne <kdunne@mail.ccsf.edu>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: Tutorial Help - Can't detect wifi after reboot
Date: Fri, 13 Feb 2015 13:04:21 -0500	[thread overview]
Message-ID: <54DE3CA5.80602@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1502131808180.2995@hadrien>

On 02/13/15 12:12, Julia Lawall wrote:
> On Fri, 13 Feb 2015, Katherine Dunne wrote:
> 
>> I have been going through the tutorial, using Ubuntu 14.04.1
>> I am at the point under Test Your Changes under Modifying a Driver on Native
>> Linux.
>> Since rebooting, my computer can't detect wifi.
>> I noticed on rebooting a new message appeared "Bluetooth TX [hex address]
>> timeout," but after disabling bluetooth per another tutorial's suggestion,
>> the message does not appear, and there is still no wifi detected.
>>
>> The last time I succesfully rebooted and had a wifi connection was right
>> before cloning the staging repository in the Tool Set Up section.
>> Would it be helpful to list the commands that I've run between my two reboot
>> times?
>> The driver I modified was /drivers/net/hamradio/baycom_epp.c
> 
> Perhaps the kernel you are compiling does not have the wifi driver that
> the ubuntu kernel uses for your laptop?  Maybe it would help to use lspci
> with your ubuntu setup to see what wifi driver you are using, and then to
> see if that is in the configuration of the one that you are compiling?
> One could also wonder if the driver you modified is selected in the
> configuration of the kernel you are modifying.  When you compiled your
> kernel, did you get a file drivers/net/hamradio/baycom_epp.o?  If you did
> not, then your probably has nothing to do with your change, because you
> change is not even in the compiled kernel.  But they are probably not
> related in any case.

The wireless card could be either PCI or USB or SDIO, so if you run
'iw dev' as root, it should tell you the state of your device.

If nothing shows up in the output, try 'dmesg | grep wlan' and see if it
shows something.

It is very possible that you didn't include the wireless driver in the
kernel you built, as Julia points out.

Cheers,
Jes



  reply	other threads:[~2015-02-13 18:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-13 17:04 Tutorial Help - Can't detect wifi after reboot Katherine Dunne
2015-02-13 17:12 ` Julia Lawall
2015-02-13 18:04   ` Jes Sorensen [this message]
2015-02-14  3:28     ` Katherine Dunne
2015-02-14  4:32       ` Jes Sorensen
2015-02-14  4:42         ` Jes Sorensen
2015-02-14 18:30           ` Katherine Dunne
2015-02-14 18:53             ` [Outreachy kernel] " Julia Lawall
2015-02-14 19:44               ` Katherine Dunne

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=54DE3CA5.80602@gmail.com \
    --to=jes.sorensen@gmail.com \
    --cc=julia.lawall@lip6.fr \
    --cc=kdunne@mail.ccsf.edu \
    --cc=outreachy-kernel@googlegroups.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.