Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #173771 > unrolled thread

WiFi works during install, not after

Back to article view | Back to linux.debian.user

Contents

  WiFi works during install, not after Carl Fink <carl@finknetwork.com> - 2016-10-23 23:10 +0200
    Re: WiFi works during install, not after <tomas@tuxteam.de> - 2016-10-24 10:20 +0200
      Re: WiFi works during install, not after Jude DaShiell <jdashiel@panix.com> - 2016-10-25 05:20 +0200
    Fwd: WiFi works during install, not after Carl Fink <carl@finknetwork.com> - 2016-10-25 03:20 +0200
      Re: Fwd: WiFi works during install, not after deloptes <deloptes@gmail.com> - 2016-10-25 09:00 +0200
        Re: Fwd: WiFi works during install, not after Carl Fink <carl@finknetwork.com> - 2016-10-25 15:30 +0200
          Re: Fwd: WiFi works during install, not after Patrick Bartek <nemommxiv@gmail.com> - 2016-10-25 18:50 +0200
            Re: Fwd: WiFi works during install, not after Carl Fink <carlf@panix.com> - 2016-10-26 19:20 +0200
              Re: Fwd: WiFi works during install, not after Brian <ad44@cityscape.co.uk> - 2016-10-26 20:40 +0200
                Re: Fwd: WiFi works during install, not after Carl Fink <carl@finknetwork.com> - 2016-10-27 03:10 +0200
                  Re: Fwd: WiFi works during install, not after Brian <ad44@cityscape.co.uk> - 2016-10-27 12:10 +0200
              Re: Fwd: WiFi works during install, not after Patrick Bartek <nemommxiv@gmail.com> - 2016-10-27 03:10 +0200
    Re: WiFi works during install, not after Brian <ad44@cityscape.co.uk> - 2016-10-25 10:50 +0200
      Re: WiFi works during install, not after Carl Fink <carl@finknetwork.com> - 2016-10-25 15:40 +0200
        Re: WiFi works during install, not after Brian <ad44@cityscape.co.uk> - 2016-10-25 16:30 +0200
          Re: WiFi works during install, not after Carl Fink <carl@finknetwork.com> - 2016-10-25 18:40 +0200
            Re: WiFi works during install, not after Brian <ad44@cityscape.co.uk> - 2016-10-25 18:50 +0200
              Re: WiFi works during install, not after Carl Fink <carlf@panix.com> - 2016-10-26 19:00 +0200
                Re: WiFi works during install, not after Brian <ad44@cityscape.co.uk> - 2016-10-26 19:20 +0200
                  Re: WiFi works during install, not after Carl Fink <carlf@panix.com> - 2016-10-26 19:30 +0200
                    Re: WiFi works during install, not after Lisi Reisz <lisi.reisz@gmail.com> - 2016-10-29 16:30 +0200
                      Re: WiFi works during install, not after Brian <ad44@cityscape.co.uk> - 2016-10-29 16:40 +0200
                      Re: WiFi works during install, not after Carl Fink <carl@finknetwork.com> - 2016-10-29 16:40 +0200
                        Re: WiFi works during install, not after Lisi Reisz <lisi.reisz@gmail.com> - 2016-10-29 18:30 +0200
                          Re: WiFi works during install, not after Brian <ad44@cityscape.co.uk> - 2016-10-29 21:20 +0200
                            Re: WiFi works during install, not after Lisi Reisz <lisi.reisz@gmail.com> - 2016-10-29 23:30 +0200

Page 1 of 2  [1] 2  Next page →

#173771 — WiFi works during install, not after

So I have a ThinkPad Yoga 11s ultrabook.

If I copy over the firmware-realtek package, Debian can install just 
fine over the WiFi connection. (I don't have wired internet at my home.)

After install, everything is fine, except I can't connect to the WiFi. I 
know it's possible because the installer does it!

The wlan0 interface exists and is up, but "dhclient wlan0" ends up 
assigning 169.169.254.8.192, which is not a routable address. As you 
might expect, attempts to ping/connect to external systems via IP 
address fail with "Destination host unreachable" and of course, DNS 
lookups universally fail.

This ultrabook is supposed to have the rtl8723au chipset, which is a USB 
802.11/Bluetooth chipset that for some reason Lenovo used in the laptop, 
with an inside-the-case-only USB connection.

The firmware-realtek package is installed on the ultrabook.

Interestingly, the rtl8723au module is NOT loaded, and "modprobe 
rtl8723au" fails with a message about the module not being found, even 
though it's right there if I "locate rtl8723au", in the drivers/staging 
directory. Maybe the staging area isn't used by default? I confess I 
don't remember how to change the path that is searched for loadable modules.

Any insights would be most gratefully received.

-- 
Carl Fink
carl@finknetwork.com

[toc] | [next] | [standalone]

#173784

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sun, Oct 23, 2016 at 05:09:06PM -0400, Carl Fink wrote:
> So I have a ThinkPad Yoga 11s ultrabook.
> 
> If I copy over the firmware-realtek package, Debian can install just
> fine over the WiFi connection. (I don't have wired internet at my
> home.)
> 
> After install, everything is fine, except I can't connect to the
> WiFi. I know it's possible because the installer does it!

Yes, this is an irritating aspect of Debian installation. But, to
be honest, I don't know how one could do better, since the kernel
at installation doesn't need to be the finally installed kernel.

You have to make the firmware available to the installer at install
time in a directory /firmware in some removable media. The installer
usually stops to give you a chance to do that. If I read it correctly,
the installer looks somewhere below /media, where the removable
media is found.

See also [2] and [3] for more background and alternatives.

> The wlan0 interface exists and is up, but "dhclient wlan0" ends up
> assigning 169.169.254.8.192, which is not a routable address. As you
> might expect, attempts to ping/connect to external systems via IP
> address fail with "Destination host unreachable" and of course, DNS
> lookups universally fail.

Yeah (I think there's one 169 too much). This is a link-locak address,
after RFC3927. I try to keep my nets free of those ;-)

> This ultrabook is supposed to have the rtl8723au chipset, which is a
> USB 802.11/Bluetooth chipset that for some reason Lenovo used in the
> laptop, with an inside-the-case-only USB connection.

Sic transit gloria mundi ;-/

regards

[1] https://wiki.debian.org/Firmware#Firmware_during_the_installation
[2] https://raphaelhertzog.com/2011/03/14/missing-firmware-in-debian-learn-how-to-deal-with-the-problem/
[3] https://wiki.debian.org/DebianInstaller/NetbootFirmware

- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlgNw0wACgkQBcgs9XrR2kZddwCfYY+MiNH1iZYqdRk58LY3Wf5A
Y3EAnAhyB2nUWBEPeNpCiNgArhrD59sz
=HO0l
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#173808

On Mon, 24 Oct 2016, tomas@tuxteam.de wrote:

> Date: Mon, 24 Oct 2016 04:16:12
> From: tomas@tuxteam.de
> To: Carl Fink <carl@finknetwork.com>
> Cc: Debian Users <debian-user@lists.debian.org>
> Subject: Re: WiFi works during install, not after
> Resent-Date: Mon, 24 Oct 2016 08:16:29 +0000 (UTC)
> Resent-From: debian-user@lists.debian.org
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Sun, Oct 23, 2016 at 05:09:06PM -0400, Carl Fink wrote:
>> So I have a ThinkPad Yoga 11s ultrabook.
>>
>> If I copy over the firmware-realtek package, Debian can install just
>> fine over the WiFi connection. (I don't have wired internet at my
>> home.)
>>
>> After install, everything is fine, except I can't connect to the
>> WiFi. I know it's possible because the installer does it!
>
> Yes, this is an irritating aspect of Debian installation. But, to
> be honest, I don't know how one could do better, since the kernel
> at installation doesn't need to be the finally installed kernel.
>
> You have to make the firmware available to the installer at install
> time in a directory /firmware in some removable media. The installer
> usually stops to give you a chance to do that. If I read it correctly,
> the installer looks somewhere below /media, where the removable
> media is found.
>
> See also [2] and [3] for more background and alternatives.
>
>> The wlan0 interface exists and is up, but "dhclient wlan0" ends up
>> assigning 169.169.254.8.192, which is not a routable address. As you
>> might expect, attempts to ping/connect to external systems via IP
>> address fail with "Destination host unreachable" and of course, DNS
>> lookups universally fail.
>
> Yeah (I think there's one 169 too much). This is a link-locak address,
> after RFC3927. I try to keep my nets free of those ;-)
>
>> This ultrabook is supposed to have the rtl8723au chipset, which is a
>> USB 802.11/Bluetooth chipset that for some reason Lenovo used in the
>> laptop, with an inside-the-case-only USB connection.
>
> Sic transit gloria mundi ;-/
>
> regards
>
> [1] https://wiki.debian.org/Firmware#Firmware_during_the_installation
> [2] https://raphaelhertzog.com/2011/03/14/missing-firmware-in-debian-learn-how-to-deal-with-the-problem/
> [3] https://wiki.debian.org/DebianInstaller/NetbootFirmware
>
> - -- tom?s
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
>
> iEYEARECAAYFAlgNw0wACgkQBcgs9XrR2kZddwCfYY+MiNH1iZYqdRk58LY3Wf5A
> Y3EAnAhyB2nUWBEPeNpCiNgArhrD59sz
> =HO0l
> -----END PGP SIGNATURE-----
>
Debian already has lots of freedesktop.org stuff in it, so why not add 
netctl and make dialog package a dependency of it?  True you don't get 
wifi working at start up after install, but a few commands and you make 
your network profile and are up on the internetwith netctl.  To make 
network profiles you run wifi-menu -o and scan and select networks then 
key in your passphrase and if all goes well get returned to the command 
prompt.  Then as root or equivalent netctl switch-to `netctl list`.  If 
that command exits with no complaints reboot and you should have 
internet.  The only thing is, if your network runs into problems you'll 
need to shut the network interface down or no more internet until that's 
done.  You're effectively jammed.

>

--

[toc] | [prev] | [next] | [standalone]

#173805

[Multipart message — attachments visible in raw view] — view raw

So, I gather no one has any insights and I should just file a bug against
... firmware-realtek? The installer? Can anyone maybe suggest which package
the bug should be filed against?

Thanks.
Carl

-------- Forwarded Message --------
Subject: 	WiFi works during install, not after
Resent-Date: 	Sun, 23 Oct 2016 21:09:25 +0000 (UTC)
Resent-From: 	debian-user@lists.debian.org
Date: 	Sun, 23 Oct 2016 17:09:06 -0400
From: 	Carl Fink <carl@finknetwork.com>
To: 	Debian Users <debian-user@lists.debian.org>



So I have a ThinkPad Yoga 11s ultrabook.

If I copy over the firmware-realtek package, Debian can install just
fine over the WiFi connection. (I don't have wired internet at my home.)

After install, everything is fine, except I can't connect to the WiFi. I
know it's possible because the installer does it!

The wlan0 interface exists and is up, but "dhclient wlan0" ends up
assigning 169.169.254.8.192, which is not a routable address. As you
might expect, attempts to ping/connect to external systems via IP
address fail with "Destination host unreachable" and of course, DNS
lookups universally fail.

This ultrabook is supposed to have the rtl8723au chipset, which is a USB
802.11/Bluetooth chipset that for some reason Lenovo used in the laptop,
with an inside-the-case-only USB connection.

The firmware-realtek package is installed on the ultrabook.

Interestingly, the rtl8723au module is NOT loaded, and "modprobe
rtl8723au" fails with a message about the module not being found, even
though it's right there if I "locate rtl8723au", in the drivers/staging
directory. Maybe the staging area isn't used by default? I confess I
don't remember how to change the path that is searched for loadable modules.

Any insights would be most gratefully received.

-- 
Carl Fink
carl@finknetwork.com

[toc] | [prev] | [next] | [standalone]

#173810

Carl Fink wrote:

> So, I gather no one has any insights and I should just file a bug against
> ... firmware-realtek? The installer? Can anyone maybe suggest which
> package the bug should be filed against?
> 
> Thanks.
> Carl
> 
> -------- Forwarded Message --------
> Subject:      WiFi works during install, not after
> Resent-Date:  Sun, 23 Oct 2016 21:09:25 +0000 (UTC)
> Resent-From:  debian-user@lists.debian.org
> Date:         Sun, 23 Oct 2016 17:09:06 -0400
> From:         Carl Fink <carl@finknetwork.com>
> To:   Debian Users <debian-user@lists.debian.org>
> 
> 
> 
> So I have a ThinkPad Yoga 11s ultrabook.
> 
> If I copy over the firmware-realtek package, Debian can install just
> fine over the WiFi connection. (I don't have wired internet at my home.)
> 
> After install, everything is fine, except I can't connect to the WiFi. I
> know it's possible because the installer does it!
> 
> The wlan0 interface exists and is up, but "dhclient wlan0" ends up
> assigning 169.169.254.8.192, which is not a routable address. As you
> might expect, attempts to ping/connect to external systems via IP
> address fail with "Destination host unreachable" and of course, DNS
> lookups universally fail.
> 
> This ultrabook is supposed to have the rtl8723au chipset, which is a USB
> 802.11/Bluetooth chipset that for some reason Lenovo used in the laptop,
> with an inside-the-case-only USB connection.
> 
> The firmware-realtek package is installed on the ultrabook.
> 
> Interestingly, the rtl8723au module is NOT loaded, and "modprobe
> rtl8723au" fails with a message about the module not being found, even
> though it's right there if I "locate rtl8723au", in the drivers/staging
> directory. Maybe the staging area isn't used by default? I confess I
> don't remember how to change the path that is searched for loadable
> modules.
> 
> Any insights would be most gratefully received.
> 

Perhaps you get a different kernel version after install. What are the
messages in your syslog? 
Do you have the firmware also after installation?

[toc] | [prev] | [next] | [standalone]

#173833

On Tue, Oct 25, 2016 at 08:46:41AM +0200, deloptes wrote:

> Perhaps you get a different kernel version after install. 

Very possible. Does not exonerate the installer, IMO.

> What are the messages in your syslog?  

I'll check when I get home--I don't use my personal system at work.

>Do you have the firmware also after installation?

Yes.
-- 
Carl Fink                           nitpicking@nitpicking.com 

Read my blog at blog.nitpicking.com.  Reviews!  Observations!
Stupid mistakes you can correct!

[toc] | [prev] | [next] | [standalone]

#173845

On Tue, 25 Oct 2016 09:27:22 -0400 Carl Fink <carl@finknetwork.com>
wrote:

> On Tue, Oct 25, 2016 at 08:46:41AM +0200, deloptes wrote:
> 
> > Perhaps you get a different kernel version after install. 
> 
> Very possible. Does not exonerate the installer, IMO.
> 
> > What are the messages in your syslog?  
> 
> I'll check when I get home--I don't use my personal system at work.
> 
> >Do you have the firmware also after installation?
> 
> Yes.

I've been following your problem.  Had something similar happen years
ago.

Have you checked if you installed "Laptop Tools" which includes wifi
packages? They usually don't get installed automatically.

Have you tried manually shutting down wifi and manually connecting?

Try purging the firmwareware and reinstalling.

B

[toc] | [prev] | [next] | [standalone]

#173875

On 10/25/2016 12:48 PM, Patrick Bartek wrote:
> I've been following your problem.  Had something similar happen years
> ago.
>
> Have you checked if you installed "Laptop Tools" which includes wifi
> packages? They usually don't get installed automatically.
>
> Have you tried manually shutting down wifi and manually connecting?
>
> Try purging the firmwareware and reinstalling.
>

I just purged and reinstalled firmware-realtek. Now I get the syslog 
messages,
Oct 26 13:08:38 devuan-nitpicking kernel: [  357.907437] rtl8723au: 
Loading firmware rtlwifi/rtl8723aufw_B.bin
Oct 26 13:08:38 devuan-nitpicking kernel: [  357.907503] rtl8723au 
2-1.7:1.2: firmware: direct-loading firmware rtlwifi/rtl8723aufw_B.bin

Still no connection, though.

The only laptop tools in apt-cache search results are for 
laptop-mode-tools, which doesn't seem to apply. Could you clarify?

I've tried configuring the network multiple ways with no success. Can 
you point me to instructions for the manual connection method you're 
describing?

wicd-gtk detects all local networks (SSIDs) and whether they require 
encryption, but then still fails to connect to any of them.

Appreciate the attempt to help.

Carl

[toc] | [prev] | [next] | [standalone]

#173882

On Wed 26 Oct 2016 at 13:15:24 -0400, Carl Fink wrote:

> On 10/25/2016 12:48 PM, Patrick Bartek wrote:
> >I've been following your problem.  Had something similar happen years
> >ago.
> >
> >Have you checked if you installed "Laptop Tools" which includes wifi
> >packages? They usually don't get installed automatically.
> >
> >Have you tried manually shutting down wifi and manually connecting?
> >
> >Try purging the firmwareware and reinstalling.
> >
> 
> I just purged and reinstalled firmware-realtek. Now I get the syslog
> messages,
> Oct 26 13:08:38 devuan-nitpicking kernel: [  357.907437] rtl8723au: Loading
		  ^^^^^^^^^^^^^^^^^^^^^^^^
		  ^^^^^^^^^^^^^^^^^^^^^^^^

Debian derivatives are one thing, a fork of Debian is another.
Personally, I draw the line at -user support for something which
has its own support channels.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#173889

On 10/26/2016 02:37 PM, Brian wrote:
> Debian derivatives are one thing, a fork of Debian is another.
> Personally, I draw the line at -user support for something which
> has its own support channels.
>
Fair enough. I should mention that I got identical results installing 
Debian, then tried Devuan hoping it would work differently. It seems the 
Devuan developers haven't changed whatever package bungles this.

Interestingly, FWIW, Debian Mint DOES work. I could just break down and 
reinstall that, but I was hoping to help by reporting the bug, if 
nothing else.

-- 
Carl Fink
carl@finknetwork.com

[toc] | [prev] | [next] | [standalone]

#173899

On Wed 26 Oct 2016 at 21:03:22 -0400, Carl Fink wrote:

> On 10/26/2016 02:37 PM, Brian wrote:
> >Debian derivatives are one thing, a fork of Debian is another.
> >Personally, I draw the line at -user support for something which
> >has its own support channels.
> >
> Fair enough. I should mention that I got identical results installing
> Debian, then tried Devuan hoping it would work differently. It seems the
> Devuan developers haven't changed whatever package bungles this.

Your initial message was reasonably clear on what you had done:

 > If I copy over the firmware-realtek package, Debian can install
 > just fine over the WiFi connection. (I don't have wired internet
 > at my home.)

Do we assume you copied *firmware files* over to /lib on the installer?
This would fit the fact you got a WiFi connection.

 > After install, everything is fine, except I can't connect to the
 > WiFi. I know it's possible because the installer does it!

You installed the Xfce4 task. After rebooting, /etc/network/interfaces
will be empty (apart from a loopback entry). It is not copied over to
the new install because the task brings in networkmanager and this
should have been set up for you to give a WiFi connection. Any *useful*
bug report would include the relevant portion of the installer's syslog,
networkmanager's configuration and the state of the networking stack.

To have d-i's /e/n/i copied over you can boot the installer with

 netcfg/target_network_config=ifupdown

on its kernel command line. That would be as good a test for basic
networking as any.

 > Interestingly, the rtl8723au module is NOT loaded, and
 > "modprobe rtl8723au"fails with a message about the module
 > not being found, ........

By now you will be aware the module's name is r8723au. You also know
booting the machine loads the module and the chip's firmware. In
principle you should be able to set up a WiFi connection with your
chosen software.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#173890

On Wed, 26 Oct 2016 13:15:24 -0400 Carl Fink <carlf@panix.com> wrote:

> On 10/25/2016 12:48 PM, Patrick Bartek wrote:
> > I've been following your problem.  Had something similar happen
> > years ago.
> >
> > Have you checked if you installed "Laptop Tools" which includes wifi
> > packages? They usually don't get installed automatically.
> >
> > Have you tried manually shutting down wifi and manually connecting?
> >
> > Try purging the firmwareware and reinstalling.
> >
> 
> I just purged and reinstalled firmware-realtek. Now I get the syslog 
> messages,
> Oct 26 13:08:38 devuan-nitpicking kernel: [  357.907437] rtl8723au:
                              ^^^^^^^^^ 
> Loading firmware rtlwifi/rtl8723aufw_B.bin
> Oct 26 13:08:38 devuan-nitpicking kernel: [  357.907503] rtl8723au
                             ^^^^^^^^^ 
> 2-1.7:1.2: firmware: direct-loading firmware rtlwifi/rtl8723aufw_B.bin

Are you running Jessie or the Devuan no-systemd fork of it?  Are your
repositories Debian or Devuan ones?

> Still no connection, though.

Check if you have iwconfig and dhclient installed.  Use iwconfig in a
terminal to try to connect. .

> The only laptop tools in apt-cache search results are for 
> laptop-mode-tools, which doesn't seem to apply. Could you clarify?

It's a selection during the install where you pick to install, for
example, the Base System, a desktop, various servers, etc.  It's
usually the last on the list and includes various packages useful on a
laptop like various wifi tools.

> I've tried configuring the network multiple ways with no success. Can 
> you point me to instructions for the manual connection method you're 
> describing?

'man iwconfig' should get you started.  Be sure to "man" the other tools
listed at the bottom.

> wicd-gtk detects all local networks (SSIDs) and whether they require 
> encryption, but then still fails to connect to any of them.

I've never used it, but if it detects wireless broadcasts and fails to
connect, it's probably not the problem.  See if iwconfig works.

B

[toc] | [prev] | [next] | [standalone]

#173814

On Sun 23 Oct 2016 at 17:09:06 -0400, Carl Fink wrote:

> So I have a ThinkPad Yoga 11s ultrabook.
> 
> If I copy over the firmware-realtek package, Debian can install just fine
> over the WiFi connection. (I don't have wired internet at my home.)
> 
> After install, everything is fine, except I can't connect to the WiFi. I
> know it's possible because the installer does it!

Did you install a desktop *during* the installation?
 
> The wlan0 interface exists and is up, but "dhclient wlan0" ends up assigning
> 169.169.254.8.192, which is not a routable address. As you might expect,
> attempts to ping/connect to external systems via IP address fail with
> "Destination host unreachable" and of course, DNS lookups universally fail.
> 
> This ultrabook is supposed to have the rtl8723au chipset, which is a USB
> 802.11/Bluetooth chipset that for some reason Lenovo used in the laptop,
> with an inside-the-case-only USB connection.
> 
> The firmware-realtek package is installed on the ultrabook.
> 
> Interestingly, the rtl8723au module is NOT loaded, and "modprobe rtl8723au"
> fails with a message about the module not being found, even though it's
> right there if I "locate rtl8723au", in the drivers/staging directory. Maybe
> the staging area isn't used by default? I confess I don't remember how to
> change the path that is searched for loadable modules.
> 
> Any insights would be most gratefully received.

Firmware and module names are not necessarily the same. Look at the
output of 'lsmod'.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#173834

On Tue, Oct 25, 2016 at 09:45:41AM +0100, Brian wrote:
> On Sun 23 Oct 2016 at 17:09:06 -0400, Carl Fink wrote:

> > Interestingly, the rtl8723au module is NOT loaded, and "modprobe rtl8723au"
> > fails with a message about the module not being found, even though it's
> > right there if I "locate rtl8723au", in the drivers/staging directory. Maybe
> > the staging area isn't used by default? I confess I don't remember how to
> > change the path that is searched for loadable modules.
> > 
> > Any insights would be most gratefully received.
> 
> Firmware and module names are not necessarily the same. Look at the
> output of 'lsmod'.

Notice what I quoted above? I did look at lsmod.
-- 
Carl Fink                           nitpicking@nitpicking.com 

Read my blog at blog.nitpicking.com.  Reviews!  Observations!
Stupid mistakes you can correct!

[toc] | [prev] | [next] | [standalone]

#173836

On Tue 25 Oct 2016 at 09:38:16 -0400, Carl Fink wrote:

> On Tue, Oct 25, 2016 at 09:45:41AM +0100, Brian wrote:
> > On Sun 23 Oct 2016 at 17:09:06 -0400, Carl Fink wrote:
> 
> > > Interestingly, the rtl8723au module is NOT loaded, and "modprobe rtl8723au"
> > > fails with a message about the module not being found, even though it's
> > > right there if I "locate rtl8723au", in the drivers/staging directory. Maybe
> > > the staging area isn't used by default? I confess I don't remember how to
> > > change the path that is searched for loadable modules.
> > > 
> > > Any insights would be most gratefully received.
> > 
> > Firmware and module names are not necessarily the same. Look at the
> > output of 'lsmod'.
> 
> Notice what I quoted above? I did look at lsmod.

I did notice. You are assuming the name of the module is "rtl8723au".
There is no such module in staging - as your modprobe command tells
you. Could we look at your 'lsmod' too?

I also noticed you failed to respond to my first question. This was
actually the more important one. The answer could provide you with
the insight you want.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#173844

On Tue, Oct 25, 2016 at 03:27:44PM +0100, Brian wrote:
> 
> I did notice. You are assuming the name of the module is "rtl8723au".
> There is no such module in staging - as your modprobe command tells
> you. Could we look at your 'lsmod' too?

Except that as I said, locate DOES find a module of that name in staging.
-- 
Carl Fink                           nitpicking@nitpicking.com 

Read my blog at blog.nitpicking.com.  Reviews!  Observations!
Stupid mistakes you can correct!

[toc] | [prev] | [next] | [standalone]

#173846

On Tue 25 Oct 2016 at 12:35:52 -0400, Carl Fink wrote:

> On Tue, Oct 25, 2016 at 03:27:44PM +0100, Brian wrote:
> > 
> > I did notice. You are assuming the name of the module is "rtl8723au".
> > There is no such module in staging - as your modprobe command tells
> > you. Could we look at your 'lsmod' too?
> 
> Except that as I said, locate DOES find a module of that name in staging.

Does it? Module names end in .ko. On jessie:

 brian@desktop:~/unprint$ locate rtl8723au
 /lib/modules/3.16.0-4-686-pae/kernel/drivers/staging/rtl8723au
 /lib/modules/3.16.0-4-686-pae/kernel/drivers/staging/rtl8723au/r8723au.ko

My other question requires only a "yes" or "no" answer. It is possible
any response to yours could open up a world of wonder.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#173871

Brian (and list):

I actually went back to the archive 
(https://lists.debian.org/debian-user/2016/10/msg00852.html) and I can't 
locate your first message containing the mysterious "first question".

It also isn't in my mailbox.

Could you perhaps repeat?

Carl Fink

On 10/25/2016 12:48 PM, Brian wrote:
> On Tue 25 Oct 2016 at 12:35:52 -0400, Carl Fink wrote:
>
>> On Tue, Oct 25, 2016 at 03:27:44PM +0100, Brian wrote:
>>> I did notice. You are assuming the name of the module is "rtl8723au".
>>> There is no such module in staging - as your modprobe command tells
>>> you. Could we look at your 'lsmod' too?
>> Except that as I said, locate DOES find a module of that name in staging.
> Does it? Module names end in .ko. On jessie:
>
>   brian@desktop:~/unprint$ locate rtl8723au
>   /lib/modules/3.16.0-4-686-pae/kernel/drivers/staging/rtl8723au
>   /lib/modules/3.16.0-4-686-pae/kernel/drivers/staging/rtl8723au/r8723au.ko
>
> My other question requires only a "yes" or "no" answer. It is possible
> any response to yours could open up a world of wonder.
>

[toc] | [prev] | [next] | [standalone]

#173878

On Wed 26 Oct 2016 at 12:57:54 -0400, Carl Fink wrote:

> Brian (and list):
> 
> I actually went back to the archive
> (https://lists.debian.org/debian-user/2016/10/msg00852.html) and I can't
> locate your first message containing the mysterious "first question".
> 
> It also isn't in my mailbox.
> 
> Could you perhaps repeat?

Certainly. No problem.

  > Did you install a desktop *during* the installation?

(It was in https://lists.debian.org/debian-user/2016/10/msg00819.html)

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#173879

Thanks.

I actually remember seeing it now that you remind me.

Define "desktop". I set up Xfce4.

Carl

On 10/26/2016 01:19 PM, Brian wrote:
> On Wed 26 Oct 2016 at 12:57:54 -0400, Carl Fink wrote:
>
>> Brian (and list):
>>
>> I actually went back to the archive
>> (https://lists.debian.org/debian-user/2016/10/msg00852.html) and I can't
>> locate your first message containing the mysterious "first question".
>>
>> It also isn't in my mailbox.
>>
>> Could you perhaps repeat?
> Certainly. No problem.
>
>    > Did you install a desktop *during* the installation?
>
> (It was in https://lists.debian.org/debian-user/2016/10/msg00819.html)
>

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | linux.debian.user

csiph-web