Tutorial Help - Can't detect wifi after reboot

Tutorial Help - Can't detect wifi after reboot

[Katherine Dunne]

[-- Attachment #1.1: Type: text/plain, Size: 727 bytes --]

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

Thanks for your help!
Katie

[-- Attachment #1.2: Type: text/html, Size: 776 bytes --]

Re: Tutorial Help - Can't detect wifi after reboot

[Julia Lawall]

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.

julia

Re: Tutorial Help - Can't detect wifi after reboot

[Jes Sorensen]

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

Re: Tutorial Help - Can't detect wifi after reboot

[Katherine Dunne]

[-- Attachment #1: Type: text/plain, Size: 4129 bytes --]

Forgive me if I end up not addressing your suggestions. I am new to Linux,
so I've been researching exactly what your responses mean.

When I ran dmesg | grep wlan it did not give any information.

The next thing I did was to reboot in recovery mode, then resume normal
rebooting, which connected me back to wifi.

After that I ran dmesg | grep wlan and this information seemed important:

[    8.279472] usb 1-1.6: Direct firmware load failed with error -2
[    8.280800] usb 1-1.6: Falling back to user helper
[    8.282676] Bluetooth: can't load firmware, may not work correctly
[    8.322736] wl: module license 'MIXED/Proprietary' taints kernel.
[    8.323730] Disabling lock debugging due to kernel taint
[    8.326499] wl: module verification failed: signature and/or  required
key missing - tainting kernel
[    8.329087] wl 0000:06:00.0: enabling device (0000 -> 0002)
[    8.340921] intel_rapl: domain uncore energy ctr 28408:28408 not
working, skip
[    8.359971] INFO @wl_cfg80211_attach : Registered CFG80211 phy
[    8.361506] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD
(1bcf:2b8b)
[    8.371637] input: Integrated_Webcam_HD as
/devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.5/1-1.5:1.0/input/input9
[    8.372808] usbcore: registered new interface driver uvcvideo
[    8.373989] USB Video Class driver (1.1.1)
[    8.406564] lib80211_crypt: registered algorithm 'TKIP'
[    8.500670] wlan0: Broadcom BCM4365 802.11 Hybrid Wireless Controller
6.30.223.141 (r415941)
[    8.645326] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    8.645333] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   10.288246] Bluetooth: hci0 command 0x1003 tx timeout


The wifi driver I am using is Broadcom Corporation BCM43142 802.11b/g/n
(rev 01)

With the suggestion that the wireless driver was not in the kernel I built,
I realized I didn't follow the step under Configure the Kernel. So I copied
a config file from /boot into git/kernels/staging thinking this would
include the wireless driver, but it has not solved the problem. I have the
feeling that is not what you were suggesting.



On Fri, Feb 13, 2015 at 10:04 AM, Jes Sorensen <jes.sorensen@gmail.com>
wrote:

> 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
>
>

[-- Attachment #2: Type: text/html, Size: 5171 bytes --]

Re: Tutorial Help - Can't detect wifi after reboot

[Jes Sorensen]

On 02/13/15 22:28, Katherine Dunne wrote:
> Forgive me if I end up not addressing your suggestions. I am new to Linux,
> so I've been researching exactly what your responses mean.
> 
> When I ran dmesg | grep wlan it did not give any information.
> 
> The next thing I did was to reboot in recovery mode, then resume normal
> rebooting, which connected me back to wifi.
> 
> After that I ran dmesg | grep wlan and this information seemed important:
> 
> [    8.279472] usb 1-1.6: Direct firmware load failed with error -2
> [    8.280800] usb 1-1.6: Falling back to user helper
> [    8.282676] Bluetooth: can't load firmware, may not work correctly
> [    8.322736] wl: module license 'MIXED/Proprietary' taints kernel.
> [    8.323730] Disabling lock debugging due to kernel taint
> [    8.326499] wl: module verification failed: signature and/or  required
> key missing - tainting kernel
> [    8.329087] wl 0000:06:00.0: enabling device (0000 -> 0002)
> [    8.340921] intel_rapl: domain uncore energy ctr 28408:28408 not
> working, skip
> [    8.359971] INFO @wl_cfg80211_attach : Registered CFG80211 phy
> [    8.361506] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD
> (1bcf:2b8b)
> [    8.371637] input: Integrated_Webcam_HD as
> /devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.5/1-1.5:1.0/input/input9
> [    8.372808] usbcore: registered new interface driver uvcvideo
> [    8.373989] USB Video Class driver (1.1.1)
> [    8.406564] lib80211_crypt: registered algorithm 'TKIP'
> [    8.500670] wlan0: Broadcom BCM4365 802.11 Hybrid Wireless Controller
> 6.30.223.141 (r415941)
> [    8.645326] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
> [    8.645333] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
> [   10.288246] Bluetooth: hci0 command 0x1003 tx timeout
> 
> 
> The wifi driver I am using is Broadcom Corporation BCM43142 802.11b/g/n
> (rev 01)
> 
> With the suggestion that the wireless driver was not in the kernel I built,
> I realized I didn't follow the step under Configure the Kernel. So I copied
> a config file from /boot into git/kernels/staging thinking this would
> include the wireless driver, but it has not solved the problem. I have the
> feeling that is not what you were suggesting.

OK, what you see above is a message indicating that the wifi driver is
in the kernel, it is this line:

[    8.500670] wlan0: Broadcom BCM4365 802.11 Hybrid Wireless Controller
6.30.223.141 (r415941)

If that didn't show up in your self built kernel it means the driver
wasn't built or loaded correctly.

I did a bit of searching and it looks like the 43142 is known for being
a tricky device, however I don't have any first hand experience with it.
There seems to be various drivers for it. Do you get any output if you
run this command from a system where the wifi is working:

ls -l /sys/class/net/wlan0/device/driver/module/drivers/

On my laptop it looks like with (it is using the iwlwifi driver module):

[jes@ultrasam ~]$ ls -l /sys/class/net/wlan0/device/driver/module/drivers/
total 0
lrwxrwxrwx. 1 root root 0 Feb 13 23:29 pci:iwlwifi ->
../../../bus/pci/drivers/iwlwifi

Jes


> 
> 
> On Fri, Feb 13, 2015 at 10:04 AM, Jes Sorensen <jes.sorensen@gmail.com>
> wrote:
> 
>> 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
>>
>>
> 

Re: Tutorial Help - Can't detect wifi after reboot

[Jes Sorensen]

On 02/13/15 23:32, Jes Sorensen wrote:
> On 02/13/15 22:28, Katherine Dunne wrote:
>> Forgive me if I end up not addressing your suggestions. I am new to Linux,
>> so I've been researching exactly what your responses mean.
>>
>> When I ran dmesg | grep wlan it did not give any information.
>>
>> The next thing I did was to reboot in recovery mode, then resume normal
>> rebooting, which connected me back to wifi.
>>
>> After that I ran dmesg | grep wlan and this information seemed important:
>>
>> [    8.279472] usb 1-1.6: Direct firmware load failed with error -2
>> [    8.280800] usb 1-1.6: Falling back to user helper
>> [    8.282676] Bluetooth: can't load firmware, may not work correctly
>> [    8.322736] wl: module license 'MIXED/Proprietary' taints kernel.
>> [    8.323730] Disabling lock debugging due to kernel taint
>> [    8.326499] wl: module verification failed: signature and/or  required
>> key missing - tainting kernel
>> [    8.329087] wl 0000:06:00.0: enabling device (0000 -> 0002)
>> [    8.340921] intel_rapl: domain uncore energy ctr 28408:28408 not
>> working, skip
>> [    8.359971] INFO @wl_cfg80211_attach : Registered CFG80211 phy
>> [    8.361506] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD
>> (1bcf:2b8b)
>> [    8.371637] input: Integrated_Webcam_HD as
>> /devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.5/1-1.5:1.0/input/input9
>> [    8.372808] usbcore: registered new interface driver uvcvideo
>> [    8.373989] USB Video Class driver (1.1.1)
>> [    8.406564] lib80211_crypt: registered algorithm 'TKIP'
>> [    8.500670] wlan0: Broadcom BCM4365 802.11 Hybrid Wireless Controller
>> 6.30.223.141 (r415941)
>> [    8.645326] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
>> [    8.645333] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
>> [   10.288246] Bluetooth: hci0 command 0x1003 tx timeout
>>
>>
>> The wifi driver I am using is Broadcom Corporation BCM43142 802.11b/g/n
>> (rev 01)
>>
>> With the suggestion that the wireless driver was not in the kernel I built,
>> I realized I didn't follow the step under Configure the Kernel. So I copied
>> a config file from /boot into git/kernels/staging thinking this would
>> include the wireless driver, but it has not solved the problem. I have the
>> feeling that is not what you were suggesting.
> 
> OK, what you see above is a message indicating that the wifi driver is
> in the kernel, it is this line:
> 
> [    8.500670] wlan0: Broadcom BCM4365 802.11 Hybrid Wireless Controller
> 6.30.223.141 (r415941)
> 
> If that didn't show up in your self built kernel it means the driver
> wasn't built or loaded correctly.
> 
> I did a bit of searching and it looks like the 43142 is known for being
> a tricky device, however I don't have any first hand experience with it.
> There seems to be various drivers for it. Do you get any output if you
> run this command from a system where the wifi is working:
> 
> ls -l /sys/class/net/wlan0/device/driver/module/drivers/
> 
> On my laptop it looks like with (it is using the iwlwifi driver module):
> 
> [jes@ultrasam ~]$ ls -l /sys/class/net/wlan0/device/driver/module/drivers/
> total 0
> lrwxrwxrwx. 1 root root 0 Feb 13 23:29 pci:iwlwifi ->
> ../../../bus/pci/drivers/iwlwifi

Searched a bit more and came across this:

http://www.broadcom.com/support/802.11/linux_sta.php

Looks like Broadcom is shipping a proprietary driver for the 43142 and
my guess is that Ubuntu installs it without warning you. In that case
you may have to install that on top of your self compiled kernel to get
wifi to work :( Alternatively a $10 USB device could work if you don't
want to fight with this constantly.

Jes

Re: Tutorial Help - Can't detect wifi after reboot

[Katherine Dunne]

[-- Attachment #1: Type: text/plain, Size: 4987 bytes --]

Thanks for the help, Julia and Jes, it pointed me in the direction to find
lots of information.

I fixed the wifi problem by finding this:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1358966
and downloading the package
bcmwl-kernel-source_6.30.223.248+bdcom-0ubuntu2_amd64.deb

I am still not able to find the changes that I made in a driver through
dmesg | less after rebooting.
The most recent steps I took were

cd git/kernels/staging
lsmod
git grep wl -- "*Makefile'

//This gave me a bunch of files that I didn't recognize. I wasn't sure what
to do with this information so instead I went into the driver folder and
tried to find a .c file that seemed similar to the example 'e1000_main.c'
cd drivers/net/wireless

vim atmel_pci.c

//I found the function static int atmel_pci_probe(struct pci_dev *pdev,
                                     const struct pci_device_id *pent)
and inserted printk(KERN_DEBUG "I can modify the Linux kernel!\n");

:wq
make
sudo make modules_install install
sudo reboot now
dmesg | less

when I try /I can the pattern is not found.




On Fri, Feb 13, 2015 at 8:42 PM, Jes Sorensen <jes.sorensen@gmail.com>
wrote:

> On 02/13/15 23:32, Jes Sorensen wrote:
> > On 02/13/15 22:28, Katherine Dunne wrote:
> >> Forgive me if I end up not addressing your suggestions. I am new to
> Linux,
> >> so I've been researching exactly what your responses mean.
> >>
> >> When I ran dmesg | grep wlan it did not give any information.
> >>
> >> The next thing I did was to reboot in recovery mode, then resume normal
> >> rebooting, which connected me back to wifi.
> >>
> >> After that I ran dmesg | grep wlan and this information seemed
> important:
> >>
> >> [    8.279472] usb 1-1.6: Direct firmware load failed with error -2
> >> [    8.280800] usb 1-1.6: Falling back to user helper
> >> [    8.282676] Bluetooth: can't load firmware, may not work correctly
> >> [    8.322736] wl: module license 'MIXED/Proprietary' taints kernel.
> >> [    8.323730] Disabling lock debugging due to kernel taint
> >> [    8.326499] wl: module verification failed: signature and/or
> required
> >> key missing - tainting kernel
> >> [    8.329087] wl 0000:06:00.0: enabling device (0000 -> 0002)
> >> [    8.340921] intel_rapl: domain uncore energy ctr 28408:28408 not
> >> working, skip
> >> [    8.359971] INFO @wl_cfg80211_attach : Registered CFG80211 phy
> >> [    8.361506] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD
> >> (1bcf:2b8b)
> >> [    8.371637] input: Integrated_Webcam_HD as
> >> /devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.5/1-1.5:1.0/input/input9
> >> [    8.372808] usbcore: registered new interface driver uvcvideo
> >> [    8.373989] USB Video Class driver (1.1.1)
> >> [    8.406564] lib80211_crypt: registered algorithm 'TKIP'
> >> [    8.500670] wlan0: Broadcom BCM4365 802.11 Hybrid Wireless Controller
> >> 6.30.223.141 (r415941)
> >> [    8.645326] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
> >> [    8.645333] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
> >> [   10.288246] Bluetooth: hci0 command 0x1003 tx timeout
> >>
> >>
> >> The wifi driver I am using is Broadcom Corporation BCM43142 802.11b/g/n
> >> (rev 01)
> >>
> >> With the suggestion that the wireless driver was not in the kernel I
> built,
> >> I realized I didn't follow the step under Configure the Kernel. So I
> copied
> >> a config file from /boot into git/kernels/staging thinking this would
> >> include the wireless driver, but it has not solved the problem. I have
> the
> >> feeling that is not what you were suggesting.
> >
> > OK, what you see above is a message indicating that the wifi driver is
> > in the kernel, it is this line:
> >
> > [    8.500670] wlan0: Broadcom BCM4365 802.11 Hybrid Wireless Controller
> > 6.30.223.141 (r415941)
> >
> > If that didn't show up in your self built kernel it means the driver
> > wasn't built or loaded correctly.
> >
> > I did a bit of searching and it looks like the 43142 is known for being
> > a tricky device, however I don't have any first hand experience with it.
> > There seems to be various drivers for it. Do you get any output if you
> > run this command from a system where the wifi is working:
> >
> > ls -l /sys/class/net/wlan0/device/driver/module/drivers/
> >
> > On my laptop it looks like with (it is using the iwlwifi driver module):
> >
> > [jes@ultrasam ~]$ ls -l
> /sys/class/net/wlan0/device/driver/module/drivers/
> > total 0
> > lrwxrwxrwx. 1 root root 0 Feb 13 23:29 pci:iwlwifi ->
> > ../../../bus/pci/drivers/iwlwifi
>
> Searched a bit more and came across this:
>
> http://www.broadcom.com/support/802.11/linux_sta.php
>
> Looks like Broadcom is shipping a proprietary driver for the 43142 and
> my guess is that Ubuntu installs it without warning you. In that case
> you may have to install that on top of your self compiled kernel to get
> wifi to work :( Alternatively a $10 USB device could work if you don't
> want to fight with this constantly.
>
> Jes
>
>

[-- Attachment #2: Type: text/html, Size: 6652 bytes --]

Re: [Outreachy kernel] Re: Tutorial Help - Can't detect wifi after reboot

[Julia Lawall]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1450 bytes --]



On Sat, 14 Feb 2015, Katherine Dunne wrote:

> Thanks for the help, Julia and Jes, it pointed me in the direction to find
> lots of information.
>
> I fixed the wifi problem by finding this:
> https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1358966
> and downloading the package
> bcmwl-kernel-source_6.30.223.248+bdcom-0ubuntu2_amd64.deb
>
> I am still not able to find the changes that I made in a driver through
> dmesg | less after rebooting.
> The most recent steps I took were
>
> cd git/kernels/staging
> lsmod
> git grep wl -- "*Makefile'
>
> //This gave me a bunch of files that I didn't recognize. I wasn't sure what
> to do with this information so instead I went into the driver folder and
> tried to find a .c file that seemed similar to the example 'e1000_main.c'
> cd drivers/net/wireless
>
> vim atmel_pci.c
>
> //I found the function static int atmel_pci_probe(struct pci_dev *pdev,
>                                      const struct pci_device_id *pent)
> and inserted printk(KERN_DEBUG "I can modify the Linux kernel!\n");
>
> :wq
> make
> sudo make modules_install install
> sudo reboot now
> dmesg | less
>
> when I try /I can the pattern is not found.

Is the C file that you have modified being compiled?  Go to the directory
where it is located and see if you have a .o file for it.  If not, find
some .c file for which you have a .o file and try modifying that one
instead.

julia

Re: [Outreachy kernel] Re: Tutorial Help - Can't detect wifi after reboot

[Katherine Dunne]

[-- Attachment #1: Type: text/plain, Size: 1666 bytes --]

No, it wasn't. I followed your suggestion and was able to get it to work,
thanks!

On Sat, Feb 14, 2015 at 10:53 AM, Julia Lawall <julia.lawall@lip6.fr> wrote:

>
>
> On Sat, 14 Feb 2015, Katherine Dunne wrote:
>
> > Thanks for the help, Julia and Jes, it pointed me in the direction to
> find
> > lots of information.
> >
> > I fixed the wifi problem by finding this:
> > https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1358966
> > and downloading the package
> > bcmwl-kernel-source_6.30.223.248+bdcom-0ubuntu2_amd64.deb
> >
> > I am still not able to find the changes that I made in a driver through
> > dmesg | less after rebooting.
> > The most recent steps I took were
> >
> > cd git/kernels/staging
> > lsmod
> > git grep wl -- "*Makefile'
> >
> > //This gave me a bunch of files that I didn't recognize. I wasn't sure
> what
> > to do with this information so instead I went into the driver folder and
> > tried to find a .c file that seemed similar to the example 'e1000_main.c'
> > cd drivers/net/wireless
> >
> > vim atmel_pci.c
> >
> > //I found the function static int atmel_pci_probe(struct pci_dev *pdev,
> >                                      const struct pci_device_id *pent)
> > and inserted printk(KERN_DEBUG "I can modify the Linux kernel!\n");
> >
> > :wq
> > make
> > sudo make modules_install install
> > sudo reboot now
> > dmesg | less
> >
> > when I try /I can the pattern is not found.
>
> Is the C file that you have modified being compiled?  Go to the directory
> where it is located and see if you have a .o file for it.  If not, find
> some .c file for which you have a .o file and try modifying that one
> instead.
>
> julia
>

[-- Attachment #2: Type: text/html, Size: 2474 bytes --]