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

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

how to activate my wireless card? nmtui only shows wireless connections . . .

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

Contents

  how to activate my wireless card? nmtui only shows wireless  connections . . . Albretch Mueller <lbrtchx@gmail.com> - 2023-03-03 16:50 +0100
    Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Timothy M Butterworth <timothy.m.butterworth@gmail.com> - 2023-03-03 17:10 +0100
      Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Albretch Mueller <lbrtchx@gmail.com> - 2023-03-03 18:10 +0100
        Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Timothy M Butterworth <timothy.m.butterworth@gmail.com> - 2023-03-03 18:20 +0100
        Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Christoph Brinkhaus <c.brinkhaus@t-online.de> - 2023-03-03 18:30 +0100
          Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Albretch Mueller <lbrtchx@gmail.com> - 2023-03-03 22:50 +0100
            Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Dan Ritter <dsr@randomstring.org> - 2023-03-03 23:20 +0100
              Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Albretch Mueller <lbrtchx@gmail.com> - 2023-03-04 09:10 +0100
            Re: how to activate my wireless card? nmtui only shows wireless  connections . . . David Wright <deblis@lionunicorn.co.uk> - 2023-03-03 23:30 +0100
              Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Albretch Mueller <lbrtchx@gmail.com> - 2023-03-04 01:10 +0100
                Re: how to activate my wireless card? nmtui only shows wireless  connections . . . David Wright <deblis@lionunicorn.co.uk> - 2023-03-04 18:20 +0100
                  Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Albretch Mueller <lbrtchx@gmail.com> - 2023-03-05 03:50 +0100
                    Re: how to activate my wireless card? nmtui only shows wireless  connections . . . David Wright <deblis@lionunicorn.co.uk> - 2023-03-05 21:40 +0100
                      Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Albretch Mueller <lbrtchx@gmail.com> - 2023-03-05 22:00 +0100
                        Re: how to activate my wireless card? nmtui only shows wireless  connections . . . David Wright <deblis@lionunicorn.co.uk> - 2023-03-08 00:40 +0100
            Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Timothy M Butterworth <timothy.m.butterworth@gmail.com> - 2023-03-04 00:40 +0100
              Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Timothy M Butterworth <timothy.m.butterworth@gmail.com> - 2023-03-04 01:00 +0100
    Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Jeffrey Walton <noloader@gmail.com> - 2023-03-03 23:50 +0100
      Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Greg Wooledge <greg@wooledge.org> - 2023-03-04 00:20 +0100
        Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Jeffrey Walton <noloader@gmail.com> - 2023-03-04 07:10 +0100
          Re: how to activate my wireless card? nmtui only shows wireless  connections . . . David Wright <deblis@lionunicorn.co.uk> - 2023-03-04 18:20 +0100
            Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Jeffrey Walton <noloader@gmail.com> - 2023-03-04 19:00 +0100
              Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Curt <curty@free.fr> - 2023-03-05 18:30 +0100
                Re: how to activate my wireless card? nmtui only shows wireless connections . . . Anssi Saari <as@sci.fi> - 2023-03-05 20:30 +0100
                  Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Greg Wooledge <greg@wooledge.org> - 2023-03-05 21:10 +0100
                  Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Albretch Mueller <lbrtchx@gmail.com> - 2023-03-05 21:20 +0100
                  Re: how to activate my wireless card? nmtui only shows wireless  connections . . . David Wright <deblis@lionunicorn.co.uk> - 2023-03-05 21:40 +0100
                    Re: how to activate my wireless card? nmtui only shows wireless connections . . . Anssi Saari <as@sci.fi> - 2023-03-06 21:20 +0100
        Re: how to activate my wireless card? nmtui only shows wireless  connections . . . <tomas@tuxteam.de> - 2023-03-04 07:40 +0100

Page 1 of 2  [1] 2  Next page →

#255551 — how to activate my wireless card? nmtui only shows wireless connections . . .

$ sudo lspci | grep --ignore-case Wireless
02:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless
Network Adapter (rev 31)
$

$ sudo lshw -class network
  *-network DISABLED
       description: Ethernet interface
       product: RTL810xE PCI Express Fast Ethernet controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:01:00.0
       logical name: enp1s0
       version: 07
       serial: c0:3e:ba:26:aa:93
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix vpd cap_list ethernet physical
       configuration: broadcast=yes driver=r8169
driverversion=5.10.0-18-amd64 latency=0 link=no multicast=yes
       resources: irq:16 ioport:3000(size=256)
memory:91400000-91400fff memory:91200000-91203fff
  *-network
       description: Network controller
       product: QCA9377 802.11ac Wireless Network Adapter
       vendor: Qualcomm Atheros
       physical id: 0
       bus info: pci@0000:02:00.0
       version: 31
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list
       configuration: driver=ath10k_pci latency=0
       resources: irq:127 memory:91000000-911fffff
$

 The difference between the wired Ethernet controller and the Wireless
Network Adapter are obvious, but what is the "logical name" of the
internal wireless card, which as I read:

 https://forums.debian.net/viewtopic.php?t=136212

 is supported in the kernel since version 4.4?

 How can you go: "ip link set dev <logical name for wireless adapter>
up" when I don't even see what the logical name is?

[toc] | [next] | [standalone]

#255553

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

On Fri, Mar 3, 2023 at 10:46 AM Albretch Mueller <lbrtchx@gmail.com> wrote:

> $ sudo lspci | grep --ignore-case Wireless
> 02:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless
> Network Adapter (rev 31)
> $
>
> $ sudo lshw -class network
>   *-network DISABLED
>        description: Ethernet interface
>        product: RTL810xE PCI Express Fast Ethernet controller
>        vendor: Realtek Semiconductor Co., Ltd.
>        physical id: 0
>        bus info: pci@0000:01:00.0
>        logical name: enp1s0
>        version: 07
>        serial: c0:3e:ba:26:aa:93
>        width: 64 bits
>        clock: 33MHz
>        capabilities: pm msi pciexpress msix vpd cap_list ethernet physical
>        configuration: broadcast=yes driver=r8169
> driverversion=5.10.0-18-amd64 latency=0 link=no multicast=yes
>        resources: irq:16 ioport:3000(size=256)
> memory:91400000-91400fff memory:91200000-91203fff
>   *-network
>        description: Network controller
>        product: QCA9377 802.11ac Wireless Network Adapter
>        vendor: Qualcomm Atheros
>        physical id: 0
>        bus info: pci@0000:02:00.0
>        version: 31
>        width: 64 bits
>        clock: 33MHz
>        capabilities: pm msi pciexpress bus_master cap_list
>        configuration: driver=ath10k_pci latency=0
>        resources: irq:127 memory:91000000-911fffff
> $
>
>  The difference between the wired Ethernet controller and the Wireless
> Network Adapter are obvious, but what is the "logical name" of the
> internal wireless card, which as I read:
>

Just run `ip link` or `ip address` and it will show you the name.


>  https://forums.debian.net/viewtopic.php?t=136212
>
>  is supported in the kernel since version 4.4?
>
>  How can you go: "ip link set dev <logical name for wireless adapter>
> up" when I don't even see what the logical name is?
>
>

-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀

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

#255555

On 3/3/23, Timothy M Butterworth <timothy.m.butterworth@gmail.com> wrote:
> Just run `ip link` or `ip address` and it will show you the name.

 I had already done so, but I don't see the "logical name" or the IP
of the wireless interface on my very "temperamental" DELL Inspiron
which seems to have a mind of its own. I only see the loopback
interface, the interface for for the wired network and USB connection
through which I tether my cell phone to the WiFi network:

$ sudo ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp1s0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN
mode DEFAULT group default qlen 1000
    link/ether c0:3e:ba:26:aa:93 brd ff:ff:ff:ff:ff:ff
6: usb0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UNKNOWN mode DEFAULT group default qlen 1000
    link/ether 02:0b:37:c4:ef:fc brd ff:ff:ff:ff:ff:ff
$

 when I removed my phone I still didn't see anything.

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

#255556

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

On Fri, Mar 3, 2023 at 12:01 PM Albretch Mueller <lbrtchx@gmail.com> wrote:

> On 3/3/23, Timothy M Butterworth <timothy.m.butterworth@gmail.com> wrote:
> > Just run `ip link` or `ip address` and it will show you the name.
>
>  I had already done so, but I don't see the "logical name" or the IP
> of the wireless interface on my very "temperamental" DELL Inspiron
> which seems to have a mind of its own. I only see the loopback
> interface, the interface for for the wired network and USB connection
> through which I tether my cell phone to the WiFi network:
>
> $ sudo ip link
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
> mode DEFAULT group default qlen 1000
>     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> 2: enp1s0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN
> mode DEFAULT group default qlen 1000
>     link/ether c0:3e:ba:26:aa:93 brd ff:ff:ff:ff:ff:ff
> 6: usb0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
> state UNKNOWN mode DEFAULT group default qlen 1000
>     link/ether 02:0b:37:c4:ef:fc brd ff:ff:ff:ff:ff:ff
> $
>
>  when I removed my phone I still didn't see anything.
>

Do you have the drivers installed:

firmware-atheros/testing,testing 20230210-1 all
 Binary firmware for Qualcomm Atheros wireless cards

Tim
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀

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

#255557

Am Fri, Mar 03, 2023 at 05:01:49PM +0000 schrieb Albretch Mueller:
> On 3/3/23, Timothy M Butterworth <timothy.m.butterworth@gmail.com> wrote:
> > Just run `ip link` or `ip address` and it will show you the name.

In addition what Tim suggests:

You could run dmesg and search for ath, wifi, wlan, wlp or so.
In my case the output with a different driver is as below.

# dmesg|grep iwlwifi
[    2.635994] iwlwifi 0000:04:00.0: enabling device (0000 -> 0002)
[    2.648283] iwlwifi 0000:04:00.0: firmware: direct-loading firmware iwlwifi-8265-36.ucode
[    2.649024] iwlwifi 0000:04:00.0: loaded firmware version 36.ad812ee0.0 8265-36.ucode op_mode iwlmvm
[    2.649050] iwlwifi 0000:04:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
[    2.802163] iwlwifi 0000:04:00.0: Detected Intel(R) Dual Band Wireless AC 8265, REV=0x230
[    2.862957] iwlwifi 0000:04:00.0: base HW address: 00:e1:8c:eb:ce:bd
[    3.048206] iwlwifi 0000:04:00.0 wlp4s0: renamed from wlan0

Kind regards,
Christoph
-- 
Ist die Katze gesund
schmeckt sie dem Hund.

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

#255562

 since it was included in the Linux kernel anyway I (apparently
wrongly) thought I didn't have to install any packages. After
downloading and installing the required firmware:

$ sudo dpkg --install firmware-atheros_20210315-3_all.deb
Selecting previously unselected package firmware-atheros.
(Reading database ... 233435 files and directories currently installed.)
Preparing to unpack firmware-atheros_20210315-3_all.deb ...
Unpacking firmware-atheros (20210315-3) ...
Setting up firmware-atheros (20210315-3) ...
$

 I see:

$ sudo dmesg | grep firmware
[    1.357329] i915 0000:00:02.0: firmware: failed to load
i915/icl_dmc_ver1_09.bin (-2)
[    1.357334] firmware_class: See https://wiki.debian.org/Firmware
for information about missing firmware
[    1.357338] i915 0000:00:02.0: Direct firmware load for
i915/icl_dmc_ver1_09.bin failed with error -2
[    1.357341] i915 0000:00:02.0: [drm] Failed to load DMC firmware
i915/icl_dmc_ver1_09.bin. Disabling runtime power management.
[    1.357342] i915 0000:00:02.0: [drm] DMC firmware homepage:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915
[   44.920667] platform regulatory.0: firmware: direct-loading
firmware regulatory.db
[   44.920819] platform regulatory.0: firmware: direct-loading
firmware regulatory.db.p7s
[   48.091722] ath10k_pci 0000:02:00.0: firmware: failed to load
ath10k/pre-cal-pci-0000:02:00.0.bin (-2)
[   48.091761] ath10k_pci 0000:02:00.0: firmware: failed to load
ath10k/cal-pci-0000:02:00.0.bin (-2)
[   48.091783] ath10k_pci 0000:02:00.0: firmware: failed to load
ath10k/QCA9377/hw1.0/firmware-6.bin (-2)
[   48.091804] ath10k_pci 0000:02:00.0: firmware: failed to load
ath10k/QCA9377/hw1.0/firmware-5.bin (-2)
[   48.091825] ath10k_pci 0000:02:00.0: firmware: failed to load
ath10k/QCA9377/hw1.0/firmware-4.bin (-2)
[   48.091844] ath10k_pci 0000:02:00.0: firmware: failed to load
ath10k/QCA9377/hw1.0/firmware-3.bin (-2)
[   48.091865] ath10k_pci 0000:02:00.0: firmware: failed to load
ath10k/QCA9377/hw1.0/firmware-2.bin (-2)
[   48.091870] ath10k_pci 0000:02:00.0: Failed to find firmware-N.bin
(N between 2 and 6) from ath10k/QCA9377/hw1.0: -2
[   48.091874] ath10k_pci 0000:02:00.0: could not fetch firmware files (-2)
[   88.181411] r8169 0000:01:00.0: firmware: failed to load
rtl_nic/rtl8106e-1.fw (-2)
[   88.181497] r8169 0000:01:00.0: Direct firmware load for
rtl_nic/rtl8106e-1.fw failed with error -2
[   88.181513] r8169 0000:01:00.0: Unable to load firmware
rtl_nic/rtl8106e-1.fw (-2)
$

 but I am not sure if those dmesgs relating to the kind of card I have
(QCA9377) were from the initial start of DL (I am running a long
process I should not stop to test that), but I am sure you will easily
make sense of it.

 Why would the installation of that firmware fail and how do I fix or
troubleshoot that more in depth?

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

#255563

Albretch Mueller wrote: 
>  since it was included in the Linux kernel anyway I (apparently
> wrongly) thought I didn't have to install any packages. After
> downloading and installing the required firmware:
> 
> $ sudo dpkg --install firmware-atheros_20210315-3_all.deb
> Selecting previously unselected package firmware-atheros.
> (Reading database ... 233435 files and directories currently installed.)
> Preparing to unpack firmware-atheros_20210315-3_all.deb ...
> Unpacking firmware-atheros (20210315-3) ...
> Setting up firmware-atheros (20210315-3) ...
> $
> 
>  I see:
> 
> $ sudo dmesg | grep firmware
> [    1.357329] i915 0000:00:02.0: firmware: failed to load
> i915/icl_dmc_ver1_09.bin (-2)
> [    1.357334] firmware_class: See https://wiki.debian.org/Firmware
> for information about missing firmware
> [    1.357338] i915 0000:00:02.0: Direct firmware load for
> i915/icl_dmc_ver1_09.bin failed with error -2
> [    1.357341] i915 0000:00:02.0: [drm] Failed to load DMC firmware
> i915/icl_dmc_ver1_09.bin. Disabling runtime power management.
> [    1.357342] i915 0000:00:02.0: [drm] DMC firmware homepage:
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915
> [   44.920667] platform regulatory.0: firmware: direct-loading
> firmware regulatory.db
> [   44.920819] platform regulatory.0: firmware: direct-loading
> firmware regulatory.db.p7s
> [   48.091722] ath10k_pci 0000:02:00.0: firmware: failed to load
> ath10k/pre-cal-pci-0000:02:00.0.bin (-2)
> [   48.091761] ath10k_pci 0000:02:00.0: firmware: failed to load
> ath10k/cal-pci-0000:02:00.0.bin (-2)
> [   48.091783] ath10k_pci 0000:02:00.0: firmware: failed to load
> ath10k/QCA9377/hw1.0/firmware-6.bin (-2)
> [   48.091804] ath10k_pci 0000:02:00.0: firmware: failed to load
> ath10k/QCA9377/hw1.0/firmware-5.bin (-2)
> [   48.091825] ath10k_pci 0000:02:00.0: firmware: failed to load
> ath10k/QCA9377/hw1.0/firmware-4.bin (-2)
> [   48.091844] ath10k_pci 0000:02:00.0: firmware: failed to load
> ath10k/QCA9377/hw1.0/firmware-3.bin (-2)
> [   48.091865] ath10k_pci 0000:02:00.0: firmware: failed to load
> ath10k/QCA9377/hw1.0/firmware-2.bin (-2)
> [   48.091870] ath10k_pci 0000:02:00.0: Failed to find firmware-N.bin
> (N between 2 and 6) from ath10k/QCA9377/hw1.0: -2
> [   48.091874] ath10k_pci 0000:02:00.0: could not fetch firmware files (-2)
> [   88.181411] r8169 0000:01:00.0: firmware: failed to load
> rtl_nic/rtl8106e-1.fw (-2)
> [   88.181497] r8169 0000:01:00.0: Direct firmware load for
> rtl_nic/rtl8106e-1.fw failed with error -2
> [   88.181513] r8169 0000:01:00.0: Unable to load firmware
> rtl_nic/rtl8106e-1.fw (-2)
> $
> 
>  but I am not sure if those dmesgs relating to the kind of card I have
> (QCA9377) were from the initial start of DL (I am running a long
> process I should not stop to test that), but I am sure you will easily
> make sense of it.
> 
>  Why would the installation of that firmware fail and how do I fix or
> troubleshoot that more in depth?


It probably has not been loaded at all yet -- the messages you
are seeing are from the first 88.2 seconds after boot.

-dsr-

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

#255577

On 3/3/23, Dan Ritter <dsr@randomstring.org> wrote:
> ... the messages you
> are seeing are from the first 88.2 seconds after boot.

 Most probably and luckily no one has reported such problems, but from
the corner from which I see reality it may as well be not "after
boot". I haven't exactly timed it (I will when I get a chance, in
fact, dmesg logs should do), but booting the 16Gb RAM laptop I am
using right now with a Debian Live DVD takes definitely more than one
minute.

 Something else "weird" that I noticed is that the BIOS not only kept
a connection to a wireless network around me (which I used more than a
year ago and which password I don't even remember) but was able to
connect through it. I wonder why on earth should a BIOS be WiFi
enabled?!? but, well, these days even microwaves are! I think the only
way to deal with such matters is by physically disconnecting the
wireless card if possible and/or keeping your laptop in a (optimally
grounded) Faraday cage. Unfortunately, I can't do so right now because
my cell phone is also acting up, . . . once for just writing a poem my
connection to the Internet and cell phone didn't work for 8 months!
(hsymbolicus poems "lies ..."); so, for now, I will have to keep
"hugging the Germans".

 I really don't give a sh!t about Windows (I would just use it as test
based for my java code), but something I have noticed is that from the
Debian Live boot I can't access the internal SSD in my DELL Inspiron
box. Do you have experience with, would you suggest ways out of such
problems?

 lbrtchx

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

#255564

On Fri 03 Mar 2023 at 21:45:27 (+0000), Albretch Mueller wrote:
>  since it was included in the Linux kernel anyway I (apparently
> wrongly) thought I didn't have to install any packages. After
> downloading and installing the required firmware:
> 
> $ sudo dpkg --install firmware-atheros_20210315-3_all.deb
> Selecting previously unselected package firmware-atheros.
> (Reading database ... 233435 files and directories currently installed.)
> Preparing to unpack firmware-atheros_20210315-3_all.deb ...
> Unpacking firmware-atheros (20210315-3) ...
> Setting up firmware-atheros (20210315-3) ...
> $
> 
>  I see:
> 
> $ sudo dmesg | grep firmware
> [    1.357329] i915 0000:00:02.0: firmware: failed to load
> i915/icl_dmc_ver1_09.bin (-2)
> [    1.357334] firmware_class: See https://wiki.debian.org/Firmware
> for information about missing firmware
> [    1.357338] i915 0000:00:02.0: Direct firmware load for
> i915/icl_dmc_ver1_09.bin failed with error -2
> [    1.357341] i915 0000:00:02.0: [drm] Failed to load DMC firmware
> i915/icl_dmc_ver1_09.bin. Disabling runtime power management.
> [    1.357342] i915 0000:00:02.0: [drm] DMC firmware homepage:
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915
> [   44.920667] platform regulatory.0: firmware: direct-loading
> firmware regulatory.db
> [   44.920819] platform regulatory.0: firmware: direct-loading
> firmware regulatory.db.p7s
> [   48.091722] ath10k_pci 0000:02:00.0: firmware: failed to load
> ath10k/pre-cal-pci-0000:02:00.0.bin (-2)
> [   48.091761] ath10k_pci 0000:02:00.0: firmware: failed to load
> ath10k/cal-pci-0000:02:00.0.bin (-2)
> [   48.091783] ath10k_pci 0000:02:00.0: firmware: failed to load
> ath10k/QCA9377/hw1.0/firmware-6.bin (-2)
> [   48.091804] ath10k_pci 0000:02:00.0: firmware: failed to load
> ath10k/QCA9377/hw1.0/firmware-5.bin (-2)
> [   48.091825] ath10k_pci 0000:02:00.0: firmware: failed to load
> ath10k/QCA9377/hw1.0/firmware-4.bin (-2)
> [   48.091844] ath10k_pci 0000:02:00.0: firmware: failed to load
> ath10k/QCA9377/hw1.0/firmware-3.bin (-2)
> [   48.091865] ath10k_pci 0000:02:00.0: firmware: failed to load
> ath10k/QCA9377/hw1.0/firmware-2.bin (-2)
> [   48.091870] ath10k_pci 0000:02:00.0: Failed to find firmware-N.bin
> (N between 2 and 6) from ath10k/QCA9377/hw1.0: -2
> [   48.091874] ath10k_pci 0000:02:00.0: could not fetch firmware files (-2)
> [   88.181411] r8169 0000:01:00.0: firmware: failed to load
> rtl_nic/rtl8106e-1.fw (-2)
> [   88.181497] r8169 0000:01:00.0: Direct firmware load for
> rtl_nic/rtl8106e-1.fw failed with error -2
> [   88.181513] r8169 0000:01:00.0: Unable to load firmware
> rtl_nic/rtl8106e-1.fw (-2)
> $
> 
>  but I am not sure if those dmesgs relating to the kind of card I have
> (QCA9377) were from the initial start of DL (I am running a long
> process I should not stop to test that), but I am sure you will easily
> make sense of it.
> 
>  Why would the installation of that firmware fail and how do I fix or
> troubleshoot that more in depth?

Try removing the atheros module with:

  # rmmod ath10k_pci

(check its name in /proc/modules), and then reload it with

  # modprobe ath10k_pci

and check dmesg again.

Cheers,
David.

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

#255569

On 3/3/23, David Wright <deblis@lionunicorn.co.uk> wrote:
>
> Try removing the atheros module with:
>
>   # rmmod ath10k_pci
>
> (check its name in /proc/modules), and then reload it with
>
>   # modprobe ath10k_pci
>
> and check dmesg again.

 Bingo! Those were the steps that enable me to see the wireless
network with nmtui ...

 a) sudo rmmod ath10k_pci

 b) cat /proc/modules | grep "ath10k_pci"

 c) sudo modprobe ath10k_pci

 d) sudo ip link:

$ sudo ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
pfifo_fast state DOWN mode DEFAULT group default qlen 1000
    link/ether c0:3e:ba:26:aa:93 brd ff:ff:ff:ff:ff:ff
4: usb0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UNKNOWN mode DEFAULT group default qlen 1000
    link/ether de:79:31:21:04:06 brd ff:ff:ff:ff:ff:ff
5: wlp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
state DOWN mode DORMANT group default qlen 1000
    link/ether 4e:0b:ec:22:77:bc brd ff:ff:ff:ff:ff:ff permaddr
5c:3a:45:0a:fb:c1
$

 e) nmtui

 I will retest all the steps when I get a chance to make sure to go
through the steps from a "blank slate", new start

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

#255591

On Sat 04 Mar 2023 at 00:03:16 (+0000), Albretch Mueller wrote:
> On 3/3/23, David Wright <deblis@lionunicorn.co.uk> wrote:
> >
> > Try removing the atheros module with:
> >
> >   # rmmod ath10k_pci
> >
> > (check its name in /proc/modules), and then reload it with
> >
> >   # modprobe ath10k_pci
> >
> > and check dmesg again.
> 
>  Bingo! Those were the steps that enable me to see the wireless
> network with nmtui ...

Good to hear.

>  a) sudo rmmod ath10k_pci
> 
>  b) cat /proc/modules | grep "ath10k_pci"
> 
>  c) sudo modprobe ath10k_pci
> 
>  d) sudo ip link
> 
>  e) nmtui
> 
>  I will retest all the steps when I get a chance to make sure to go
> through the steps from a "blank slate", new start

I'll just point out that   cat /proc/modules   was added as an
afterthought in case (a) failed, so if (a) succeeds, you don't
need to do (b). There's always a chance, when removing modules,
that one is busy, or another has to be removed at the same time
as the one, because it's a dependent.

Also, now that the firmware is in place, if you repeat those steps,
you're /likely/ to find that ath10k_pci is busy, because the link
will be configured automatically in the first few seconds after
booting up.

Cheers,
David.

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

#255601

On 3/4/23, David Wright <deblis@lionunicorn.co.uk> wrote:
> Also, now that the firmware is in place, if you repeat those steps,
> you're /likely/ to find that ath10k_pci is busy, because the link
> will be configured automatically in the first few seconds after
> booting up.

 I would always go into exposed mode using a DL DVD that is what I
meant when I said "re start". So, I will need to run a dkpg script
whenever I boot it.

 sudo iwlist wlp2s0 scan | grep ESSID

 will list the wireless networks around. All I need now is a way to
somehow pass the password into the script in the command line of
through a config file so that I don't have to enter it every time. I
tried to find a way to do just that.

 How do you?

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

#255637

On Sun 05 Mar 2023 at 02:42:46 (+0000), Albretch Mueller wrote:
> On 3/4/23, David Wright <deblis@lionunicorn.co.uk> wrote:
> > Also, now that the firmware is in place, if you repeat those steps,
> > you're /likely/ to find that ath10k_pci is busy, because the link
> > will be configured automatically in the first few seconds after
> > booting up.
> 
>  I would always go into exposed mode using a DL DVD that is what I
> meant when I said "re start". So, I will need to run a dkpg script
> whenever I boot it.
> 
>  sudo iwlist wlp2s0 scan | grep ESSID
> 
>  will list the wireless networks around. All I need now is a way to
> somehow pass the password into the script in the command line of
> through a config file so that I don't have to enter it every time. I
> tried to find a way to do just that.
> 
>  How do you?

I run installed systems, so wifi passwords are either in individual
/var/lib/iwd/<ESSID>.psk files (with iwd), or collectively in
/etc/wpa_supplicant/<ifname>.conf (with wpasupplicant/systemd-networkd).

These files have go= permissions, and I don't consider them of great
enough concern to put them on an encrypted filesystem (which would
in any case need unlocking). However, you could do just that, with an
encrypted USB stick. At least you'd benefit from just one passphrase
to unlock any and all necessary secrets.

Cheers,
David.

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

#255641

On 3/5/23, David Wright <deblis@lionunicorn.co.uk> wrote:
> On Sun 05 Mar 2023 at 02:42:46 (+0000), Albretch Mueller wrote:
>> On 3/4/23, David Wright <deblis@lionunicorn.co.uk> wrote:
>> > Also, now that the firmware is in place, if you repeat those steps,
>> > you're /likely/ to find that ath10k_pci is busy, because the link
>> > will be configured automatically in the first few seconds after
>> > booting up.
>>
>>  I would always go into exposed mode using a DL DVD that is what I
>> meant when I said "re start". So, I will need to run a dkpg script
>> whenever I boot it.
>>
>>  sudo iwlist wlp2s0 scan | grep ESSID
>>
>>  will list the wireless networks around. All I need now is a way to
>> somehow pass the password into the script in the command line of
>> through a config file so that I don't have to enter it every time. I
>> tried to find a way to do just that.
>>
>>  How do you?
>
> I run installed systems, so wifi passwords are either in individual
> /var/lib/iwd/<ESSID>.psk files (with iwd), or collectively in
> /etc/wpa_supplicant/<ifname>.conf (with wpasupplicant/systemd-networkd).
>
> These files have go= permissions, and I don't consider them of great
> enough concern to put them on an encrypted filesystem (which would
> in any case need unlocking). However, you could do just that, with an
> encrypted USB stick. At least you'd benefit from just one passphrase
> to unlock any and all necessary secrets.

 Is there a way to pass the password on the command to that modprobe
or whichever utility?

 Apparently because I use DL I don't have that kind of directory structure:

$ cd /var/lib/iwd/
bash: cd: /var/lib/iwd/: No such file or directory

$ cd /var/lib/
$ ls -l
total 0
drwxr-xr-x 2 root          root             3 Dec  7  2020 alsa
drwxr-xr-x 1 root          root            60 Mar  5 06:01 apt
drwxr-xr-x 2 root          root          3262 Sep 10 11:19 aspell
drwxr-xr-x 2 avahi-autoipd avahi-autoipd    3 Sep 10 11:06 avahi-autoipd
drwxr-xr-x 1 colord        colord         100 Mar  4 23:57 colord
drwxr-xr-x 2 root          root            33 Sep 10 11:05 dbus
drwxr-xr-x 2 root          root             3 May 27  2021 dhcp
drwxr-xr-x 6 root          root            75 Sep 10 10:58 dictionaries-common
drwxr-xr-x 2 root          root            37 Sep 10 10:56 dkms
drwxr-xr-x 1 root          root           220 Mar  5 00:13 dpkg
drwxr-xr-x 3 root          root            28 Sep 10 10:57 emacsen-common
drwxr-xr-x 1 root          root            60 Mar  4 23:56 exim4
drwxr-xr-x 2 geoclue       geoclue          3 Mar 17  2021 geoclue
drwxr-xr-x 4 root          root            40 Sep 10 10:58 ghostscript
drwxr-xr-x 3 root          root            26 Sep 10 10:58 grub
drwxr-xr-x 3 root          root            26 Sep 10 11:01 hardware
drwxr-xr-x 2 root          root           815 Sep 10 11:19 ispell
drwxr-xr-x 3 root          root            28 Sep 10 11:01 libreoffice
drwxr-x--- 1 lightdm       lightdm         60 Mar  4 23:56 lightdm
drwxr-xr-x 1 root          root            60 Sep 10 11:03 live
drwxr-xr-x 1 root          root            60 Mar  5 00:00 logrotate
drwxr-xr-x 2 root          root            34 Sep 10 11:07 man-db
drwxr-xr-x 2 root          root             3 Sep  3  2022 misc
drwx------ 1 root          root           140 Mar  5 20:50 NetworkManager
drwxr-xr-x 2 root          root             3 Jun 28  2021 os-prober
drwxr-xr-x 2 root          root             3 Dec 22  2020 PackageKit
drwxr-xr-x 2 root          root           115 Sep 10 11:06 pam
drwxr-xr-x 1 root          root            60 Mar  4 23:55 plymouth
drwx------ 1 root          root            60 Sep 10 10:54 polkit-1
drwx------ 2 root          root            40 Mar  4 23:54 private
drwxr-xr-x 2 root          root            42 Sep 10 10:56 python
drwxr-xr-x 4 root          root            43 Sep 10 10:54 runit
drwxr-xr-x 1 root          root           100 Mar  5 19:55 smartmontools
drwxr-xr-x 2 root          root             3 Aug 15  2022 snmp
drwxr-xr-x 3 root          root            31 Sep 10 10:54 sudo
drwxr-xr-x 2 root          root             3 Nov 16  2020 synaptic
drwxr-xr-x 1 root          root           180 Mar  5 00:15 systemd
drwxr-xr-x 3 root          root           348 Sep 10 11:18 ucf
drwx------ 2 root          root            60 Mar  5 00:07 udisks2
drwxr-xr-x 2 root          root            76 Sep 10 11:16 uim
drwxr-xr-x 1 root          root           120 Mar  5 00:07 upower
drwxr-xr-x 2 root          root             3 Jul 10  2020 usb_modeswitch
drwxr-xr-x 2 root          root            30 Sep 10 11:05 usbutils
drwxr-xr-x 3 root          root            29 Sep 10 10:54 vim
drwxr-xr-x 2 root          root            39 Sep 10 11:15 xfonts
drwxr-xr-x 1 root          root            40 Mar  4 23:59 xkb
$

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

#255699

On Sun 05 Mar 2023 at 20:57:25 (+0000), Albretch Mueller wrote:
> On 3/5/23, David Wright <deblis@lionunicorn.co.uk> wrote:
> >
> > I run installed systems, so wifi passwords are either in individual
> > /var/lib/iwd/<ESSID>.psk files (with iwd), or collectively in
> > /etc/wpa_supplicant/<ifname>.conf (with wpasupplicant/systemd-networkd).
> >
> > These files have go= permissions, and I don't consider them of great
> > enough concern to put them on an encrypted filesystem (which would
> > in any case need unlocking). However, you could do just that, with an
> > encrypted USB stick. At least you'd benefit from just one passphrase
> > to unlock any and all necessary secrets.
> 
>  Is there a way to pass the password on the command to that modprobe
> or whichever utility?
> 
>  Apparently because I use DL I don't have that kind of directory structure:
> 
> $ cd /var/lib/iwd/
> bash: cd: /var/lib/iwd/: No such file or directory

You only don't have this directory because you have:

> drwx------ 1 root          root           140 Mar  5 20:50 NetworkManager

running your network, not iwd. As for /etc/wpa_supplicant/, NM lists
it as a dependency. I don't whether NM is scriptable, for passing in
a password, or not: I've never used it.

Cheers,
David.

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

#255567

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

On Fri, Mar 3, 2023 at 4:45 PM Albretch Mueller <lbrtchx@gmail.com> wrote:

>  since it was included in the Linux kernel anyway I (apparently
> wrongly) thought I didn't have to install any packages. After
> downloading and installing the required firmware:
>
> $ sudo dpkg --install firmware-atheros_20210315-3_all.deb
> Selecting previously unselected package firmware-atheros.
> (Reading database ... 233435 files and directories currently installed.)
> Preparing to unpack firmware-atheros_20210315-3_all.deb ...
> Unpacking firmware-atheros (20210315-3) ...
> Setting up firmware-atheros (20210315-3) ...
> $
>
>  I see:
>
> $ sudo dmesg | grep firmware
> [    1.357329] i915 0000:00:02.0: firmware: failed to load
> i915/icl_dmc_ver1_09.bin (-2)
> [    1.357334] firmware_class: See https://wiki.debian.org/Firmware
> for information about missing firmware
> [    1.357338] i915 0000:00:02.0: Direct firmware load for
> i915/icl_dmc_ver1_09.bin failed with error -2
> [    1.357341] i915 0000:00:02.0: [drm] Failed to load DMC firmware
> i915/icl_dmc_ver1_09.bin. Disabling runtime power management.
> [    1.357342] i915 0000:00:02.0: [drm] DMC firmware homepage:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915
> [   44.920667] platform regulatory.0: firmware: direct-loading
> firmware regulatory.db
> [   44.920819] platform regulatory.0: firmware: direct-loading
> firmware regulatory.db.p7s
> [   48.091722] ath10k_pci 0000:02:00.0: firmware: failed to load
> ath10k/pre-cal-pci-0000:02:00.0.bin (-2)
> [   48.091761] ath10k_pci 0000:02:00.0: firmware: failed to load
> ath10k/cal-pci-0000:02:00.0.bin (-2)
> [   48.091783] ath10k_pci 0000:02:00.0: firmware: failed to load
> ath10k/QCA9377/hw1.0/firmware-6.bin (-2)
> [   48.091804] ath10k_pci 0000:02:00.0: firmware: failed to load
> ath10k/QCA9377/hw1.0/firmware-5.bin (-2)
> [   48.091825] ath10k_pci 0000:02:00.0: firmware: failed to load
> ath10k/QCA9377/hw1.0/firmware-4.bin (-2)
> [   48.091844] ath10k_pci 0000:02:00.0: firmware: failed to load
> ath10k/QCA9377/hw1.0/firmware-3.bin (-2)
> [   48.091865] ath10k_pci 0000:02:00.0: firmware: failed to load
> ath10k/QCA9377/hw1.0/firmware-2.bin (-2)
> [   48.091870] ath10k_pci 0000:02:00.0: Failed to find firmware-N.bin
> (N between 2 and 6) from ath10k/QCA9377/hw1.0: -2
> [   48.091874] ath10k_pci 0000:02:00.0: could not fetch firmware files (-2)
> [   88.181411] r8169 0000:01:00.0: firmware: failed to load
> rtl_nic/rtl8106e-1.fw (-2)
> [   88.181497] r8169 0000:01:00.0: Direct firmware load for
> rtl_nic/rtl8106e-1.fw failed with error -2
> [   88.181513] r8169 0000:01:00.0: Unable to load firmware
> rtl_nic/rtl8106e-1.fw (-2)
> $
>
> An easier way to check is: sudo dmesg | grep wlan
[    9.760888] rtw_8822ce 0000:02:00.0 wlo1: renamed from wlan0


>  but I am not sure if those dmesgs relating to the kind of card I have
> (QCA9377) were from the initial start of DL (I am running a long
> process I should not stop to test that), but I am sure you will easily
> make sense of it.
>
>  Why would the installation of that firmware fail and how do I fix or
> troubleshoot that more in depth?
>


-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀

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

#255568

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

On Fri, Mar 3, 2023 at 6:36 PM Timothy M Butterworth <
timothy.m.butterworth@gmail.com> wrote:

>
>
> On Fri, Mar 3, 2023 at 4:45 PM Albretch Mueller <lbrtchx@gmail.com> wrote:
>
>>  since it was included in the Linux kernel anyway I (apparently
>> wrongly) thought I didn't have to install any packages. After
>> downloading and installing the required firmware:
>>
>> $ sudo dpkg --install firmware-atheros_20210315-3_all.deb
>> Selecting previously unselected package firmware-atheros.
>> (Reading database ... 233435 files and directories currently installed.)
>> Preparing to unpack firmware-atheros_20210315-3_all.deb ...
>> Unpacking firmware-atheros (20210315-3) ...
>> Setting up firmware-atheros (20210315-3) ...
>> $
>>
>>  I see:
>>
>> $ sudo dmesg | grep firmware
>> [    1.357329] i915 0000:00:02.0: firmware: failed to load
>> i915/icl_dmc_ver1_09.bin (-2)
>> [    1.357334] firmware_class: See https://wiki.debian.org/Firmware
>> for information about missing firmware
>> [    1.357338] i915 0000:00:02.0: Direct firmware load for
>> i915/icl_dmc_ver1_09.bin failed with error -2
>> [    1.357341] i915 0000:00:02.0: [drm] Failed to load DMC firmware
>> i915/icl_dmc_ver1_09.bin. Disabling runtime power management.
>> [    1.357342] i915 0000:00:02.0: [drm] DMC firmware homepage:
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915
>> [   44.920667] platform regulatory.0: firmware: direct-loading
>> firmware regulatory.db
>> [   44.920819] platform regulatory.0: firmware: direct-loading
>> firmware regulatory.db.p7s
>> [   48.091722] ath10k_pci 0000:02:00.0: firmware: failed to load
>> ath10k/pre-cal-pci-0000:02:00.0.bin (-2)
>> [   48.091761] ath10k_pci 0000:02:00.0: firmware: failed to load
>> ath10k/cal-pci-0000:02:00.0.bin (-2)
>> [   48.091783] ath10k_pci 0000:02:00.0: firmware: failed to load
>> ath10k/QCA9377/hw1.0/firmware-6.bin (-2)
>> [   48.091804] ath10k_pci 0000:02:00.0: firmware: failed to load
>> ath10k/QCA9377/hw1.0/firmware-5.bin (-2)
>> [   48.091825] ath10k_pci 0000:02:00.0: firmware: failed to load
>> ath10k/QCA9377/hw1.0/firmware-4.bin (-2)
>> [   48.091844] ath10k_pci 0000:02:00.0: firmware: failed to load
>> ath10k/QCA9377/hw1.0/firmware-3.bin (-2)
>> [   48.091865] ath10k_pci 0000:02:00.0: firmware: failed to load
>> ath10k/QCA9377/hw1.0/firmware-2.bin (-2)
>> [   48.091870] ath10k_pci 0000:02:00.0: Failed to find firmware-N.bin
>> (N between 2 and 6) from ath10k/QCA9377/hw1.0: -2
>> [   48.091874] ath10k_pci 0000:02:00.0: could not fetch firmware files
>> (-2)
>> [   88.181411] r8169 0000:01:00.0: firmware: failed to load
>> rtl_nic/rtl8106e-1.fw (-2)
>> [   88.181497] r8169 0000:01:00.0: Direct firmware load for
>> rtl_nic/rtl8106e-1.fw failed with error -2
>> [   88.181513] r8169 0000:01:00.0: Unable to load firmware
>> rtl_nic/rtl8106e-1.fw (-2)
>> $
>>
>> An easier way to check is: sudo dmesg | grep wlan
> [    9.760888] rtw_8822ce 0000:02:00.0 wlo1: renamed from wlan0
>
>
>>  but I am not sure if those dmesgs relating to the kind of card I have
>> (QCA9377) were from the initial start of DL (I am running a long
>> process I should not stop to test that), but I am sure you will easily
>> make sense of it.
>>
>>  Why would the installation of that firmware fail and how do I fix or
>> troubleshoot that more in depth?
>>
>
>
> ath10k/QCA9377/hw1.0/firmware-6.bin (-2)
[   48.091804] ath10k_pci 0000:02:00.0: firmware: failed to load
ath10k/QCA9377/hw1.0/firmware-5.bin (-2)
[   48.091825] ath10k_pci 0000:02:00.0: firmware: failed to load
ath10k/QCA9377/hw1.0/firmware-4.bin (-2)
[   48.091844] ath10k_pci 0000:02:00.0: firmware: failed to load
ath10k/QCA9377/hw1.0/firmware-3.bin (-2)
[   48.091865] ath10k_pci 0000:02:00.0: firmware: failed to load
ath10k/QCA9377/hw1.0/firmware-2.bin (-2)
[   48.091870] ath10k_pci 0000:02:00.0: Failed to find firmware-N.bin
(N between 2 and 6) from ath10k/QCA9377/hw1.0: -2

It looks like your hardware is not supported by the firmware. If you are
installing Debian 11 you can try backports, but as debian 12 will be out in
the next few months I would just install Debian 12.

https://cdimage.debian.org/images/unofficial/non-free/images-including-firmware/bookworm_di_alpha1+nonfree/amd64/iso-dvd/

I am running Bookworm on two of my PC's. My notebook because it does not
have working drivers for HDMI Sound or my WiFi in Debian 11 and my set top
box so I can use KDE Plasma Big Screen.

Tim



> --
> ⢀⣴⠾⠻⢶⣦⠀
> ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
> ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
> ⠈⠳⣄⠀⠀
>


-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀

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

#255565

On Fri, Mar 3, 2023 at 10:46 AM Albretch Mueller <lbrtchx@gmail.com> wrote:
>
>  [...]
> $ sudo lshw -class network
>   *-network DISABLED
>        description: Ethernet interface
>        product: RTL810xE PCI Express Fast Ethernet controller
>        vendor: Realtek Semiconductor Co., Ltd.
>        physical id: 0
>        bus info: pci@0000:01:00.0
>        logical name: enp1s0
>        version: 07
>        serial: c0:3e:ba:26:aa:93
>        width: 64 bits
>        clock: 33MHz
>        capabilities: pm msi pciexpress msix vpd cap_list ethernet physical
>        configuration: broadcast=yes driver=r8169
> driverversion=5.10.0-18-amd64 latency=0 link=no multicast=yes
>        resources: irq:16 ioport:3000(size=256)
> memory:91400000-91400fff memory:91200000-91203fff
>   *-network
>        description: Network controller
>        product: QCA9377 802.11ac Wireless Network Adapter
>        vendor: Qualcomm Atheros
>        physical id: 0
>        bus info: pci@0000:02:00.0
>        version: 31
>        width: 64 bits
>        clock: 33MHz
>        capabilities: pm msi pciexpress bus_master cap_list
>        configuration: driver=ath10k_pci latency=0
>        resources: irq:127 memory:91000000-911fffff
> $
>
>  The difference between the wired Ethernet controller and the Wireless
> Network Adapter are obvious, but what is the "logical name" of the
> internal wireless card, which as I read:
>
>  https://forums.debian.net/viewtopic.php?t=136212
>
>  is supported in the kernel since version 4.4?
>
>  How can you go: "ip link set dev <logical name for wireless adapter>
> up" when I don't even see what the logical name is?

The "logical name" is a Consistent Name, and it is provided by
biosdevname. Also see
https://linux.dell.com/files/whitepapers/consistent_network_device_naming_in_linux.pdf
.

The 'p' is a pci bus, the 's' is a slot number. Since the interface
does not move around once installed, the interface will always have
the same name like 'enp4s0'.

ifconfig will give you the names:

$ ifconfig
enp4s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ...

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        ...

wlp3s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ...

Jeff

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

#255566

On Fri, Mar 03, 2023 at 05:45:54PM -0500, Jeffrey Walton wrote:
> The 'p' is a pci bus, the 's' is a slot number. Since the interface
> does not move around once installed, the interface will always have
> the same name like 'enp4s0'.

That's a wonderful idea, but it doesn't quite work in practice.  There are
ways that a "predictable" interface name may change.  A BIOS/firmware
upgrade can do it.  Adding or removing devices can also do it, in
some cases.  They don't even have to be network interfaces.

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

#255575

On Fri, Mar 3, 2023 at 6:10 PM Greg Wooledge <greg@wooledge.org> wrote:
>
> On Fri, Mar 03, 2023 at 05:45:54PM -0500, Jeffrey Walton wrote:
> > The 'p' is a pci bus, the 's' is a slot number. Since the interface
> > does not move around once installed, the interface will always have
> > the same name like 'enp4s0'.
>
> That's a wonderful idea, but it doesn't quite work in practice.  There are
> ways that a "predictable" interface name may change.  A BIOS/firmware
> upgrade can do it.  Adding or removing devices can also do it, in
> some cases.  They don't even have to be network interfaces.

Yeah, that's udev and systemd screwing things up.

Jeff

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

Page 1 of 2  [1] 2  Next page →

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

csiph-web