Page 9 of 10 FirstFirst ... 78910 LastLast
Results 81 to 90 of 93

Thread: Have NO internet! Can not get new wifi adapter [supposedly Linux-friendly] to work

  1. #81
    Join Date
    Jun 2010
    Beans
    433

    Re: Have NO internet! Can not get new wifi adapter [supposedly Linux-friendly] to wor

    Quote Originally Posted by jeremy31 View Post
    The new firmware should be in use as the driver will load it if it is found in /lib/firmware/rtlwifi
    Move the entire folder [with all the various things in it] to /lib/firmware/rtlwifi?

    Quote Originally Posted by jeremy31 View Post
    The last script result you posted shows that the wifi switched between the router and the extender device, it might be worth shutting the extender off
    See if network-manager-gnome is installed
    Will do/try (but if memory serves me network-manager-gnome is installed, but will check again). But the extender is really boosting the signal....the problem as mentioned now is I see LOTS of bytes coming and going - but all programs claim they can not find the server!?!?!?!? - so I get no internet connection.

    .....but as I was trying various things, something strange happened: eth0 and eth1 are now listed as 'unclaimed' and don't show up......how do I 'claim' them again? Thanks.
    Code:
     sudo lshw -C network; lsb_release -a; uname -a; sudo rfkill list; sudo iwlist scan | egrep 'chan|sid'
    
      *-network               
             description: Wireless interface
             product: RTL8812AE 802.11ac PCIe Wireless Network Adapter
             vendor: Realtek Semiconductor Co., Ltd.
             physical id: 0
             bus info: pci@0000:04:00.0
             logical name: wlp4s0
             version: 01
             serial: 04:d4:c4:13:c1:51
             width: 64 bits
             clock: 33MHz
             capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
             configuration: broadcast=yes driver=rtl8821ae driverversion=4.15.0-70-generic firmware=N/A latency=0 link=yes multicast=yes wireless=IEEE 802.11
             resources: irq:38 ioport:ee00(size=256) memory:fbefc000-fbefffff
        *-network UNCLAIMED
             description: Ethernet controller
             product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
             vendor: Realtek Semiconductor Co., Ltd.
             physical id: 0
             bus info: pci@0000:07:00.0
             version: 03
             width: 64 bits
             clock: 33MHz
             capabilities: pm msi pciexpress msix vpd bus_master cap_list
             configuration: latency=0
             resources: ioport:be00(size=256) memory:fbaff000-fbafffff memory:fbaf8000-fbafbfff memory:fbb00000-fbb1ffff
        *-network UNCLAIMED
             description: Ethernet controller
             product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
             vendor: Realtek Semiconductor Co., Ltd.
             physical id: 0
             bus info: pci@0000:08:00.0
             version: 03
             width: 64 bits
             clock: 33MHz
             capabilities: pm msi pciexpress msix vpd bus_master cap_list
             configuration: latency=0
             resources: ioport:ae00(size=256) memory:fb8ff000-fb8fffff memory:fb8f8000-fb8fbfff memory:fb900000-fb91ffff
        *-network:0 DISABLED
             description: Ethernet interface
             physical id: 1
             logical name: virbr0-nic
             serial: 52:54:00:2b:2f:a7
             size: 10Mbit/s
             capabilities: ethernet physical
             configuration: autonegotiation=off broadcast=yes driver=tun driverversion=1.6 duplex=full link=no multicast=yes port=twisted pair speed=10Mbit/s
        *-network:1 DISABLED
             description: Ethernet interface
             physical id: 2
             logical name: wwx001e101f0000
             serial: 00:1e:10:1f:00:00
             capabilities: ethernet physical
             configuration: broadcast=yes driver=huawei_cdc_ncm driverversion=22-Aug-2005 firmware=Huawei CDC NCM device link=no multicast=yes
      LSB Version:   core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
      Distributor ID: Ubuntu
      Description:   Ubuntu 16.04.6 LTS
      Release:       16.04
      Codename:      xenial
      Linux-GA-X58A-UD7 4.15.0-70-generic #79~16.04.1-Ubuntu SMP Tue Nov 12 14:01:10 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
    
      0: phy0: Wireless LAN
              Soft blocked: no
              Hard blocked: no
      virbr0-nic  Interface doesn't support scanning.
      
      virbr0    Interface doesn't support scanning.
      
      wwx001e101f0000  Interface doesn't support scanning.
      
      lo        Interface doesn't support scanning.
    Last edited by crazybear; 1 Week Ago at 06:12 PM.

  2. #82
    Join Date
    Jun 2010
    Beans
    433

    Re: Have NO internet! Can not get new wifi adapter [supposedly Linux-friendly] to wor

    network-manager-gnome is installed. Still need to know what to move to /lib/firmware/rtlwifi.

    Latest: https://paste.ubuntu.com/p/DmRzDjsSYg/

  3. #83
    Join Date
    Jun 2010
    Beans
    433

    Re: Have NO internet! Can not get new wifi adapter [supposedly Linux-friendly] to wor

    I'm in Ubuntu now, and today the internet has been stable. So, maybe the lack of a visible/usable network manager IS (part of?) the problem. Just my hunch. In terminal I typed NetworkManager and was told I had to be root; but when I added sudo at the front it did nothing and said NetworkManager not found....but it shows in Synaptic as installed in the form you suggested, above.

    However, I have eth0 and eth1 listed as unclaimed and without any MAC addresses! How did that happen?! And how do I correct it? I use LAN connection to the internet much more than wifi and will need them for other purposes, as well!

    Code:
     $ ip addr show
    1: lo:<LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWNgroup default qlen 1000
        link/loopback00:00:00:00:00:00 brd 00:00:00:00:00:00
        inet 127.0.0.1/8scope host lo
           valid_lftforever preferred_lft forever
        inet6 ::1/128scope host 
           valid_lftforever preferred_lft forever
    2: wlp4s0:<BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UPgroup default qlen 1000
        link/ether04:d4:c4:13:c1:51 brd ff:ff:ff:ff:ff:ff
        inet192.168.1.37/24 brd 192.168.1.255 scope global dynamic wlp4s0
           valid_lft74311sec preferred_lft 74311sec
        inet6fe80::ece0:7976:b160:de97/64 scope link 
           valid_lftforever preferred_lft forever
    3: wwx001e101f0000:<BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN groupdefault qlen 1000
        link/ether00:1e:10:1f:00:00 brd ff:ff:ff:ff:ff:ff
    4: virbr0:<NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueuestate DOWN group default qlen 1000
        link/ether00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
        inet192.168.122.1/24 brd 192.168.122.255 scope global virbr0
           valid_lftforever preferred_lft forever
    5: virbr0-nic:<BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWNgroup default qlen 1000
        link/ether52:54:00:2b:2f:a7 brd ff:ff:ff:ff:ff:ff
    
    
    $ sudo lshw -Cnetwork
    [sudo] password for : 
      *-network              
           description:Wireless interface
           product:RTL8812AE 802.11ac PCIe Wireless Network Adapter
           vendor:Realtek Semiconductor Co., Ltd.
           physical id:0
           bus info:pci@0000:04:00.0
           logical name:wlp4s0
           version: 01
           serial:04:d4:c4:13:c1:51
           width: 64bits
           clock: 33MHz
           capabilities:pm msi pciexpress bus_master cap_list ethernet physical wireless
          configuration: broadcast=yes driver=rtl8821aedriverversion=4.15.0-70-generic firmware=N/A ip=192.168.1.37latency=0 link=yes multicast=yes wireless=IEEE 802.11
           resources:irq:36 ioport:ee00(size=256) memory:fbefc000-fbefffff
      *-networkUNCLAIMED
           description:Ethernet controller
           product:RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           vendor:Realtek Semiconductor Co., Ltd.
           physical id:0
           bus info:pci@0000:07:00.0
           version: 03
           width: 64bits
           clock: 33MHz
           capabilities:pm msi pciexpress msix vpd bus_master cap_list
          configuration: latency=0
           resources:ioport:be00(size=256) memory:fbaff000-fbafffffmemory:fbaf8000-fbafbfff memory:fbb00000-fbb1ffff
     *-network UNCLAIMED
           description:Ethernet controller
           product:RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           vendor:Realtek Semiconductor Co., Ltd.
           physical id:0
           bus info:pci@0000:08:00.0
           version: 03
           width: 64bits
           clock: 33MHz
           capabilities:pm msi pciexpress msix vpd bus_master cap_list
          configuration: latency=0
           resources:ioport:ae00(size=256) memory:fb8ff000-fb8fffffmemory:fb8f8000-fb8fbfff memory:fb900000-fb91ffff
      *-network:0DISABLED
           description:Ethernet interface
           physical id:1
           logical name:wwx001e101f0000
           serial:00:1e:10:1f:00:00
           capabilities:ethernet physical
          configuration: broadcast=yes driver=huawei_cdc_ncmdriverversion=22-Aug-2005 firmware=Huawei CDC NCM device link=nomulticast=yes
      *-network:1DISABLED
           description:Ethernet interface
           physical id:2
           logical name:virbr0-nic
           serial:52:54:00:2b:2f:a7
           size:10Mbit/s
           capabilities:ethernet physical
          configuration: autonegotiation=off broadcast=yes driver=tundriverversion=1.6 duplex=full link=no multicast=yes port=twisted pairspeed=10Mbit/s
    Last edited by crazybear; 6 Days Ago at 10:16 PM.

  4. #84
    Join Date
    Jun 2010
    Beans
    433

    Re: Have NO internet! Can not get new wifi adapter [supposedly Linux-friendly] to wor

    Please all....the wifi is now working well - thanks...but somehow I made eth0 and eth1 disappear!....they are listed as UNCLAIMED. Please, how do I fix this. I need them!! the MAC address they had can be found in the second window.

    Code:
     $ ip addr show
    1: lo:<LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWNgroup default qlen 1000
        link/loopback00:00:00:00:00:00 brd 00:00:00:00:00:00
        inet 127.0.0.1/8scope host lo
           valid_lftforever preferred_lft forever
        inet6 ::1/128scope host 
           valid_lftforever preferred_lft forever
    2: wlp4s0:<BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UPgroup default qlen 1000
        link/ether04:d4:c4:13:c1:51 brd ff:ff:ff:ff:ff:ff
        inet192.168.1.37/24 brd 192.168.1.255 scope global dynamic wlp4s0
           valid_lft74311sec preferred_lft 74311sec
        inet6fe80::ece0:7976:b160:de97/64 scope link 
           valid_lftforever preferred_lft forever
    3: wwx001e101f0000:<BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN groupdefault qlen 1000
        link/ether00:1e:10:1f:00:00 brd ff:ff:ff:ff:ff:ff
    4: virbr0:<NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueuestate DOWN group default qlen 1000
        link/ether00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
        inet192.168.122.1/24 brd 192.168.122.255 scope global virbr0
           valid_lftforever preferred_lft forever
    5: virbr0-nic:<BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWNgroup default qlen 1000
        link/ether52:54:00:2b:2f:a7 brd ff:ff:ff:ff:ff:ff
    
    
    $ sudo lshw -Cnetwork
    [sudo] password for : 
      *-network              
           description:Wireless interface
           product:RTL8812AE 802.11ac PCIe Wireless Network Adapter
           vendor:Realtek Semiconductor Co., Ltd.
           physical id:0
           bus info:pci@0000:04:00.0
           logical name:wlp4s0
           version: 01
           serial:04:d4:c4:13:c1:51
           width: 64bits
           clock: 33MHz
           capabilities:pm msi pciexpress bus_master cap_list ethernet physical wireless
          configuration: broadcast=yes driver=rtl8821aedriverversion=4.15.0-70-generic firmware=N/A ip=192.168.1.37latency=0 link=yes multicast=yes wireless=IEEE 802.11
           resources:irq:36 ioport:ee00(size=256) memory:fbefc000-fbefffff
      *-networkUNCLAIMED
           description:Ethernet controller
           product:RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           vendor:Realtek Semiconductor Co., Ltd.
           physical id:0
           bus info:pci@0000:07:00.0
           version: 03
           width: 64bits
           clock: 33MHz
           capabilities:pm msi pciexpress msix vpd bus_master cap_list
          configuration: latency=0
           resources:ioport:be00(size=256) memory:fbaff000-fbafffffmemory:fbaf8000-fbafbfff memory:fbb00000-fbb1ffff
     *-network UNCLAIMED
           description:Ethernet controller
           product:RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           vendor:Realtek Semiconductor Co., Ltd.
           physical id:0
           bus info:pci@0000:08:00.0
           version: 03
           width: 64bits
           clock: 33MHz
           capabilities:pm msi pciexpress msix vpd bus_master cap_list
          configuration: latency=0
           resources:ioport:ae00(size=256) memory:fb8ff000-fb8fffffmemory:fb8f8000-fb8fbfff memory:fb900000-fb91ffff
      *-network:0DISABLED
           description:Ethernet interface
           physical id:1
           logical name:wwx001e101f0000
           serial:00:1e:10:1f:00:00
           capabilities:ethernet physical
          configuration: broadcast=yes driver=huawei_cdc_ncmdriverversion=22-Aug-2005 firmware=Huawei CDC NCM device link=nomulticast=yes
      *-network:1DISABLED
           description:Ethernet interface
           physical id:2
           logical name:virbr0-nic
           serial:52:54:00:2b:2f:a7
           size:10Mbit/s
           capabilities:ethernet physical
          configuration: autonegotiation=off broadcast=yes driver=tundriverversion=1.6 duplex=full link=no multicast=yes port=twisted pairspeed=10Mbit/s
    
    
    how they were...
    
      *-network
           description: Ethernet interface
           product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           vendor: Realtek Semiconductor Co., Ltd.
           physical id: 0
           bus info: pci@0000:07:00.0
           logical name: eth1
           version: 03
           serial: 00:24:1d:ce:b6:64
           size: 10Mbit/s
           capacity: 1Gbit/s
           width: 64 bits
           clock: 33MHz
           capabilities: pm msi pciexpress msix vpd bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
           configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=rtl_nic/rtl8168d-2.fw latency=0 link=no multicast=yes port=MII speed=10Mbit/s
           resources: irq:16 ioport:be00(size=256) memory:fbaff000-fbafffff memory:fbaf8000-fbafbfff memory:fbb00000-fbb1ffff
      *-network
           description: Ethernet interface
           product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           vendor: Realtek Semiconductor Co., Ltd.
           physical id: 0
           bus info: pci@0000:08:00.0
           logical name: eth0
           version: 03
           serial: 00:24:1d:ce:b6:66
           size: 10Mbit/s
           capacity: 1Gbit/s
           width: 64 bits
           clock: 33MHz
           capabilities: pm msi pciexpress msix vpd bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
           configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=rtl_nic/rtl8168d-2.fw latency=0 link=no multicast=yes port=MII speed=10Mbit/s
           resources: irq:17 ioport:ae00(size=256) memory:fb8ff000-fb8fffff memory:fb8f8000-fb8fbfff memory:fb900000-fb91ffff
    Last edited by crazybear; 5 Days Ago at 08:00 PM.

  5. #85
    Join Date
    May 2014
    Location
    /home
    Beans
    8,187
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Have NO internet! Can not get new wifi adapter [supposedly Linux-friendly] to wor

    Post results for
    Code:
    dkms status; modinfo r8168; grep r8169 /etc/modprobe.d/*; ls /lib/firmware/rtlwifi

  6. #86
    Join Date
    Jun 2010
    Beans
    433

    Re: Have NO internet! Can not get new wifi adapter [supposedly Linux-friendly] to wor

    Code:
    $ dkms status; modinfo r8168; grep r8169 /etc/modprobe.d/*; ls /lib/firmware/rtlwifi
    oem-audio-hda-daily-lts-xenial, 0.201904020820~ubuntu16.04.1: added
    modinfo: ERROR: Module r8168 not found.
    /etc/modprobe.d/blacklist.conf:blacklist r8169
    rtl8188efw.bin           rtl8192eu_wowlan.bin     rtl8723bu_nic.bin
    rtl8188eufw.bin          rtl8192sefw.bin          rtl8723bu_wowlan.bin
    rtl8192cfw.bin           rtl8712u.bin             rtl8723defw.bin
    rtl8192cfwU_B.bin        rtl8723aufw_A.bin        rtl8723fw_B.bin
    rtl8192cfwU.bin          rtl8723aufw_B.bin        rtl8723fw.bin
    rtl8192cufw_A.bin        rtl8723aufw_B_NoBT.bin   rtl8812aefw.bin
    rtl8192cufw_B.bin        rtl8723befw_36.bin       rtl8812aefw_wowlan.bin
    rtl8192cufw.bin          rtl8723befw.bin          rtl8821aefw_29.bin
    rtl8192cufw_TMSC.bin     rtl8723bs_ap_wowlan.bin  rtl8821aefw.bin
    rtl8192defw.bin          rtl8723bs_bt.bin         rtl8821aefw_wowlan.bin
    rtl8192eefw.bin          rtl8723bs_nic.bin        rtl8822befw.bin
    rtl8192eu_ap_wowlan.bin  rtl8723bs_wowlan.bin
    rtl8192eu_nic.bin        rtl8723bu_ap_wowlan.bin
    Last edited by crazybear; 5 Days Ago at 07:57 PM.

  7. #87
    Join Date
    May 2014
    Location
    /home
    Beans
    8,187
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Have NO internet! Can not get new wifi adapter [supposedly Linux-friendly] to wor

    Code:
    sudo sed -i 's/blacklist r8169/#blacklist r8169/' /etc/modprobe.d/blacklist.conf
    Reboot, the firmware you downloaded is in the correct spot for the wireless driver to use it

  8. #88
    Join Date
    Jun 2010
    Beans
    433

    Re: Have NO internet! Can not get new wifi adapter [supposedly Linux-friendly] to wor

    Great! Thanks! Almost done, I think....now I only need to rename the logical name back to what they were and is standard.... How does one do that? Now they have names like enp7s0 and enp8s0

    Code:
     *-network               
           description: Wireless interface
           product: RTL8812AE 802.11ac PCIe Wireless Network Adapter
           vendor: Realtek Semiconductor Co., Ltd.
           physical id: 0
           bus info: pci@0000:04:00.0
           logical name: wlp4s0
           version: 01
           serial: 04:d4:c4:13:c1:51
           width: 64 bits
           clock: 33MHz
           capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
           configuration: broadcast=yes driver=rtl8821ae driverversion=4.15.0-72-generic firmware=N/A ip=192.168.1.24 latency=0 link=yes multicast=yes wireless=IEEE 802.11
           resources: irq:40 ioport:ee00(size=256) memory:fbefc000-fbefffff
      *-network
           description: Ethernet interface
           product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           vendor: Realtek Semiconductor Co., Ltd.
           physical id: 0
           bus info: pci@0000:07:00.0
           logical name: enp7s0
           version: 03
           serial: 00:24:1d:ce:b6:64
           capacity: 1Gbit/s
           width: 64 bits
           clock: 33MHz
           capabilities: pm msi pciexpress msix vpd bus_master cap_list rom ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
           configuration: autonegotiation=on broadcast=yes driver=r8168 driverversion=8.047.02-NAPI latency=0 link=no multicast=yes port=twisted pair
           resources: irq:33 ioport:be00(size=256) memory:fbaff000-fbafffff memory:fbaf8000-fbafbfff memory:fbb00000-fbb1ffff
      *-network
           description: Ethernet interface
           product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           vendor: Realtek Semiconductor Co., Ltd.
           physical id: 0
           bus info: pci@0000:08:00.0
           logical name: enp8s0
           version: 03
           serial: 00:24:1d:ce:b6:66
           size: 100Mbit/s
           capacity: 1Gbit/s
           width: 64 bits
           clock: 33MHz
           capabilities: pm msi pciexpress msix vpd bus_master cap_list rom ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
           configuration: autonegotiation=on broadcast=yes driver=r8168 driverversion=8.047.02-NAPI duplex=full ip=192.168.1.88 latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s
           resources: irq:34 ioport:ae00(size=256) memory:fb8ff000-fb8fffff memory:fb8f8000-fb8fbfff memory:fb900000-fb91ffff
      *-network DISABLED
           description: Ethernet interface
           physical id: 1
           logical name: virbr0-nic
           serial: 52:54:00:2b:2f:a7
           size: 10Mbit/s
           capabilities: ethernet physical
           configuration: autonegotiation=off broadcast=yes driver=tun driverversion=1.6 duplex=full link=no multicast=yes port=twisted pair speed=10Mbit/s

  9. #89
    Join Date
    Jan 2006
    Location
    Sunny Southend-on-Sea
    Beans
    6,995
    Distro
    Kubuntu 18.04 Bionic Beaver

    Re: Have NO internet! Can not get new wifi adapter [supposedly Linux-friendly] to wor

    Predictable Network Interface Names

    Why?

    The classic naming scheme for network interfaces applied by the kernel is to simply assign names beginning with "eth0", "eth1", ... to all interfaces as they are probed by the drivers. As the driver probing is generally not predictable for modern technology this means that as soon as multiple network interfaces are available the assignment of the names "eth0", "eth1" and so on is generally not fixed anymore and it might very well happen that "eth0" on one boot ends up being "eth1" on the next. This can have serious security implications, for example in firewall rules which are coded for certain naming schemes, and which are hence very sensitive to unpredictable changing names.


    To fix this problem multiple solutions have been proposed and implemented. For a longer time udev shipped support for assigning permanent "ethX" names to certain interfaces based on their MAC addresses. This turned out to have a multitude of problems, among them: this required a writable root directory which is generally not available; the statelessness of the system is lost as booting an OS image on a system will result in changed configuration of the image; on many systems MAC addresses are not actually fixed, such as on a lot of embedded hardware and particularly on all kinds of virtualization solutions. The biggest of all however is that the userspace components trying to assign the interface name raced against the kernel assigning new names from the same "ethX" namespace, a race condition with all kinds of weird effects, among them that assignment of names sometimes failed. As a result support for this has been removed from systemd/udev a while back.


    Another solution that has been implemented is "biosdevname" which tries to find fixed slot topology information in certain firmware interfaces and uses them to assign fixed names to interfaces which incorporate their physical location on the mainboard. In a way this naming scheme is similar to what is already done natively in udev for various device nodes via /dev/*/by-path/ symlinks. In many cases, biosdevname departs from the low-level kernel device identification schemes that udev generally uses for these symlinks, and instead invents its own enumeration schemes.


    Finally, many distributions support renaming interfaces to user-chosen names (think: "internet0", "dmz0", ...) keyed off their MAC addresses or physical locations as part of their networking scripts. This is a very good choice but does have the problem that it implies that the user is willing and capable of choosing and assigning these names.


    We believe it is a good default choice to generalize the scheme pioneered by "biosdevname". Assigning fixed names based on firmware/topology/location information has the big advantage that the names are fully automatic, fully predictable, that they stay fixed even if hardware is added or removed (i.e. no reenumeration takes place) and that broken hardware can be replaced seamlessly. That said, they admittedly are sometimes harder to read than the "eth0" or "wlan0" everybody is used to. Example: "enp5s0"
    None but ourselves can free our minds

  10. #90
    Join Date
    Aug 2005
    Location
    South Carolina, USA
    Beans
    24,966
    Distro
    Ubuntu 19.10 Eoan Ermine

    Re: Have NO internet! Can not get new wifi adapter [supposedly Linux-friendly] to wor

    now I only need to rename the logical name back to what they were and is standard.... How does one do that? Now they have names like enp7s0 and enp8s0
    Why? The standard today is predictable interface naming. The standard a few years ago, when I had only a few white hairs, was eth0, eth1, etc.

    Is there any reason you can name, other than 'that's the way we've always done it', that eth0 is better than enp7s0?

    There is only one thing that you can absolutely count on in computer science: change. The Linux kernel and its wrapper, Ubuntu, are changing every day. I recommend that you embrace it.
    "Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, Ph.D., Sc.D.

Page 9 of 10 FirstFirst ... 78910 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •