Results 1 to 10 of 10

Thread: Ethernet (NetworkManager) Troubles

  1. #1
    Join Date
    Nov 2020
    Location
    USA
    Posts
    18

    Default Ethernet (NetworkManager) Troubles

    Afternoon!

    I have a ThinkPad T14 that has two Gigabit Ethernet interfaces: one via USB-C, one RJ45 jack.

    Running Tumbleweed, using NetworkManager and KDE.

    The problem is that the machine does not "see" RJ45 cables that are plugged in. Not even "dmesg --follow" shows any activity. And of course, no lights on the physical RJ45 port.

    It has no problem connecting to USBC ethernet (when docked) but does not recognize ethernet cables in the RJ45 dock.

    I have tried adding a connection through the KDE "Connections" panel for RJ45, but this only results in working sometimes.

    Funny enough, WiFi is the most reliable connection for this machine! More than RJ45, which seems odd.

    Connection
    InterfaceID
    Note
    RJ45 enp5s0 Does not work on physical connect
    USBC enp2s0f0 works fine on physical connect


    In Ubuntu Live USB, the port works fine with the same cable configuration without fail.


    How do I structure NetworkManager to work with this interface? Or barring that, how do I reset NetworkManager, outside of a clean TW install (I'd rather not do that)?



    Thank you for your help and time with this problem!
    只要努力,就能成功
    With hard work, success is possible.

  2. #2
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    23,519
    Blog Entries
    1

    Default Re: Ethernet (NetworkManager) Troubles

    Some hardware details first please...
    Code:
    /usr/sbin/hwinfo --netcard
    With an ethernet cable connected to the interface of interest, run
    Code:
    ip link
    Code:
    /usr/sbin/ethtool enp5s0
    Code:
    nmcli d
    Post the output here for others to review and advise next steps.
    openSUSE Leap 15.3; KDE Plasma 5

  3. #3
    Join Date
    Nov 2020
    Location
    USA
    Posts
    18

    Default Re: Ethernet (NetworkManager) Troubles

    Thank you for the help! Here is the hardware dump.

    I separated the commands with _______ lines for ease of reading. The WLAN SSID and MAC addresses have been obscured, otherwise this is the output of each command as I see it with superuser privileges.



    Code:
    _______________________________
    hwinfo --netcard
    
    07: PCI 300.0: 0282 WLAN controller
      [Created at pci.386]
      Unique ID: hAO_.mxT2IIe1w3C
      Parent ID: aYFK.agxBQzoh2J5
      SysFS ID: /devices/pci0000:00/0000:00:02.3/0000:03:00.0
      SysFS BusID: 0000:03:00.0
      Hardware Class: network
      Model: "Intel Wi-Fi 6 AX200"
      Vendor: pci 0x8086 "Intel Corporation"
      Device: pci 0x2723 "Wi-Fi 6 AX200"
      SubVendor: pci 0x8086 "Intel Corporation"
      SubDevice: pci 0x0080 
      Revision: 0x1a
      Driver: "iwlwifi"
      Driver Modules: "iwlwifi"
      Device File: wlp3s0
      Features: WLAN
      Memory Range: 0xfd700000-0xfd703fff (rw,non-prefetchable)
      IRQ: 92 (no events)
      HW Address: XX:XX:XX:XX:XX
      Permanent HW Address: XX:XX:XX:XX
      Link detected: yes
      WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140
      WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472 5.18 5.2 5.22 5.24 5.26 5.28 5.3 5.32 5.5 5.52 5.54 5.56 5.58 5.6 5.62 5.64 5.66 5.68 5.7
      WLAN encryption modes: WEP40 WEP104 TKIP CCMP
      WLAN authentication modes: open sharedkey wpa-psk wpa-eap
      Module Alias: "pci:v00008086d00002723sv00008086sd00000080bc02sc80i00"
      Driver Info #0:
        Driver Status: iwlwifi is active
        Driver Activation Cmd: "modprobe iwlwifi"
      Config Status: cfg=no, avail=yes, need=no, active=unknown
      Attached to: #17 (PCI bridge)
    
    14: PCI 200.0: 0200 Ethernet controller
      [Created at pci.386]
      Unique ID: jbRH.B4Xffpo7KuE
      Parent ID: jDmU.agxBQzoh2J5
      SysFS ID: /devices/pci0000:00/0000:00:02.2/0000:02:00.0
      SysFS BusID: 0000:02:00.0
      Hardware Class: network
      Model: "Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller"
      Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
      Device: pci 0x8168 "RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller"
      SubVendor: pci 0x17aa "Lenovo"
      SubDevice: pci 0x5081 
      Revision: 0x0e
      Driver: "r8169"
      Driver Modules: "r8169"
      Device File: enp2s0f0
      I/O Ports: 0x3400-0x34ff (rw)
      Memory Range: 0xfd814000-0xfd814fff (rw,non-prefetchable)
      Memory Range: 0xfd800000-0xfd803fff (rw,non-prefetchable)
      IRQ: 88 (no events)
      HW Address: <MAC ADDRESS>
      Permanent HW Address: <MAC ADDRESS>
      Link detected: no
      Module Alias: "pci:v000010ECd00008168sv000017AAsd00005081bc02sc00i00"
      Driver Info #0:
        Driver Status: r8169 is active
        Driver Activation Cmd: "modprobe r8169"
      Config Status: cfg=no, avail=yes, need=no, active=unknown
      Attached to: #38 (PCI bridge)
    
    35: PCI 500.0: 0200 Ethernet controller
      [Created at pci.386]
      Unique ID: D2Iq.op7FVDs35EB
      Parent ID: AXjq.agxBQzoh2J5
      SysFS ID: /devices/pci0000:00/0000:00:02.6/0000:05:00.0
      SysFS BusID: 0000:05:00.0
      Hardware Class: network
      Model: "Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller"
      Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
      Device: pci 0x8168 "RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller"
      SubVendor: pci 0x17aa "Lenovo"
      SubDevice: pci 0x5081 
      Revision: 0x15
      Driver: "r8169"
      Driver Modules: "r8169"
      Device File: enp5s0
      I/O Ports: 0x2000-0x2fff (rw)
      Memory Range: 0xfd504000-0xfd504fff (rw,non-prefetchable)
      Memory Range: 0xfd500000-0xfd503fff (rw,non-prefetchable)
      IRQ: 90 (no events)
      HW Address: <MAC ADDRESS>
      Permanent HW Address: <MAC ADDRESS>
      Link detected: no
      Module Alias: "pci:v000010ECd00008168sv000017AAsd00005081bc02sc00i00"
      Driver Info #0:
        Driver Status: r8169 is active
        Driver Activation Cmd: "modprobe r8169"
      Config Status: cfg=no, avail=yes, need=no, active=unknown
      Attached to: #30 (PCI bridge)
    
    75: USB 00.0: 0200 Ethernet controller
      [Created at usb.122]
      Unique ID: Uax2.zk3P+8oih3E
      Parent ID: UfPf.Z91JH6i5f_D
      SysFS ID: /devices/pci0000:00/0000:00:08.1/0000:07:00.3/usb5/5-1/5-1.1/5-1.1:1.0
      SysFS BusID: 5-1.1:1.0
      Hardware Class: network
      Model: "Lenovo USB-C Dock Ethernet"
      Hotplug: USB
      Vendor: usb 0x17ef "Lenovo"
      Device: usb 0xa387 "USB-C Dock Ethernet"
      Revision: "31.03"
      Serial ID: "301000001"
      Driver: "r8152"
      Driver Modules: "r8152"
      Device File: enp7s0f3u1u1
      HW Address: <MAC ADDRESS>
      Permanent HW Address: <MAC ADDRESS>
      Link detected: yes
      Module Alias: "usb:v17EFpA387d3103dc00dsc00dp00icFFiscFFip00in00"
      Driver Info #0:
        Driver Status: r8152 is active
        Driver Activation Cmd: "modprobe r8152"
      Config Status: cfg=new, avail=yes, need=no, active=unknown
      Attached to: #50 (Hub)
    
    __________________________________
    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: enp2s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
        link/ether {MAC ADDRESS} brd ff:ff:ff:ff:ff:ff
    
    3: enp5s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
        link/ether [MAC ADDRESS] brd ff:ff:ff:ff:ff:ff
    
    4: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
        link/ether [MAC ADDRESS] brd ff:ff:ff:ff:ff:ff
    
    5: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
        link/ether [MAC ADDRESS] brd ff:ff:ff:ff:ff:ff
    No data available
    
    ______________________________
    
    nmcli d
    
    DEVICE          TYPE      STATE                   CONNECTION 
    wlp3s0          wifi      connected               <WLAN ID>     
    virbr0          bridge    connected (externally)  virbr0     
    p2p-dev-wlp3s0  wifi-p2p  disconnected            --         
    enp2s0f0        ethernet  unavailable             --         
    enp5s0          ethernet  unavailable             --         
    lo              loopback  unmanaged               --      
    
    ____________________
    ethtool enp5s0
    
    netlink error: No data available
    netlink error: No such device
    netlink error: device not present
    只要努力,就能成功
    With hard work, success is possible.

  4. #4
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    6,630

    Default AW: Ethernet (NetworkManager) Troubles

    Post:
    Code:
    zypper se -si r8168

  5. #5
    Join Date
    Nov 2020
    Location
    USA
    Posts
    18

    Default Re: Ethernet (NetworkManager) Troubles

    There doesn't seem to be anything in my repos matching R8168...

    I've included the repo list as well, using all the standard (and some extra) enabled repos.


    Code:
    ~$ zypper se -si r8168
    
    No matching items found.
    
    
    ~$ zypper lr
    
    # | Alias                            | Name                       | Enabled | GPG Check | Refresh
    --+----------------------------------+----------------------------+---------+-----------+--------
    1 | download.opensuse.org-non-oss    | Main Repository (NON-OSS)  | Yes     | (r ) Yes  | Yes
    2 | download.opensuse.org-oss        | Main Repository (OSS)      | Yes     | (r ) Yes  | Yes
    3 | download.opensuse.org-tumbleweed | Main Update Repository     | Yes     | (r ) Yes  | Yes
    4 | google-chrome                    | google-chrome              | Yes     | (r ) Yes  | Yes
    5 | nordvpn                          | nordvpn                    | Yes     | (r ) Yes  | Yes
    6 | openSUSE-20210302-0              | openSUSE-20210302-0        | No      | ----      | ----
    7 | packman                          | Packman                    | Yes     | (r ) Yes  | Yes
    8 | repo-debug                       | openSUSE-Tumbleweed-Debug  | No      | ----      | ----
    9 | repo-source                      | openSUSE-Tumbleweed-Source | No      | ----      | ----
    只要努力,就能成功
    With hard work, success is possible.

  6. #6
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    23,519
    Blog Entries
    1

    Default Re: Ethernet (NetworkManager) Troubles

    Quote Originally Posted by orbvs View Post
    There doesn't seem to be anything in my repos matching R8168...
    Sauerland's repo can be added using...
    Code:
    sudo zypper addrepo https://download.opensuse.org/repositories/home:Sauerland/openSUSE_Leap_15.3/home:Sauerland.repo
    Code:
    sudo zypper refresh
    Install package...
    Code:
    sudo zypper install r8168
    ...then restart.
    Last edited by deano_ferrari; 15-Oct-2021 at 14:04.
    openSUSE Leap 15.3; KDE Plasma 5

  7. #7
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    6,630

    Default AW: Ethernet (NetworkManager) Troubles

    But the question is:
    why do the 2 cards not working with r8169?

    Post also as root:
    Code:
    journalctl -b | grep -Ei 'r816|firmware|enp2s|enp5s'
    @deano_ferrari
    Packman has the same packages, so no need to add my Repo, because less Repos are often more....... I am sometime a little bit faster in updating but packages are the same.....
    When using my Repo please use the Hardware branch:
    https://download.opensuse.org/reposi...USE_Leap_15.3/
    There are only hardware packages and not all others.
    Last edited by Sauerland; 15-Oct-2021 at 14:13.

  8. #8
    Join Date
    Nov 2020
    Location
    USA
    Posts
    18

    Default Re: Ethernet (NetworkManager) Troubles

    Here is the output of the journalctl -b command:

    I really appreciate your help with this!

    Code:
    Oct 15 12:03:14 <hostname> kernel: Spectre V2 : Enabling Restricted Speculation for firmware calls
    Oct 15 12:03:14 <hostname> kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
    Oct 15 12:03:14 <hostname> kernel: acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge
    Oct 15 12:03:14 <hostname> kernel: psmouse serio2: trackpoint: Elan TrackPoint firmware: 0x11, buttons: 3/3
    Oct 15 12:03:15 <hostname> kernel: xhci_hcd 0000:06:00.0: failed to load firmware renesas_usb_fw.mem, fallback to ROM
    Oct 15 12:03:15 <hostname> kernel: [drm] Loading DMUB firmware via PSP: version=0x01010019
    Oct 15 12:03:15 <hostname> kernel: [drm] Found VCN firmware Version ENC: 1.16 DEC: 5 VEP: 0 Revision: 3
    Oct 15 12:03:15 <hostname> kernel: amdgpu 0000:07:00.0: amdgpu: Will use PSP to load VCN firmware
    Oct 15 12:05:16 <hostname> kernel: r8169 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control
    Oct 15 12:05:16 <hostname> kernel: libphy: r8169: probed
    Oct 15 12:05:16 <hostname> kernel: r8169 0000:02:00.0 eth0: RTL8168ep/8111ep, 00:2b:67:e7:a4:94, XID 502, IRQ 89
    Oct 15 12:05:16 <hostname> kernel: r8169 0000:02:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko]
    Oct 15 12:05:16 <hostname> kernel: r8169 0000:05:00.0: can't disable ASPM; OS doesn't have ASPM control
    Oct 15 12:05:16 <hostname> kernel: r8169 0000:05:00.0: enabling device (0000 -> 0003)
    Oct 15 12:05:16 <hostname> kernel: libphy: r8169: probed
    Oct 15 12:05:16 <hostname> kernel: r8169 0000:05:00.0 eth1: RTL8168h/8111h, 00:2b:67:e7:a4:93, XID 541, IRQ 91
    Oct 15 12:05:16 <hostname> kernel: r8169 0000:05:00.0 eth1: jumbo features [frames: 9194 bytes, tx checksumming: ko]
    Oct 15 12:05:16 <hostname> kernel: iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-64.ucode failed with error -2
    Oct 15 12:05:16 <hostname> kernel: iwlwifi 0000:03:00.0: loaded firmware version 63.c04f3485.0 cc-a0-63.ucode op_mode iwlmvm
    Oct 15 12:05:16 <hostname> NetworkManager[2550]: <info>  [1634324716.8154] manager[0x562523288040]: monitoring kernel firmware directory '/lib/firmware'.
    Oct 15 12:05:17 <hostname> kernel: r8169 0000:02:00.0 enp2s0f0: renamed from eth0
    Oct 15 12:05:17 <hostname> NetworkManager[2550]: <info>  [1634324717.2401] device (eth0): interface index 2 renamed iface from 'eth0' to 'enp2s0f0'
    Oct 15 12:05:17 <hostname> kernel: r8169 0000:05:00.0 enp5s0: renamed from eth1
    Oct 15 12:05:17 <hostname> NetworkManager[2550]: <info>  [1634324717.3081] device (enp2s0f0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
    Oct 15 12:05:17 <hostname> kernel: Generic FE-GE Realtek PHY r8169-0-200:00: attached PHY driver (mii_bus:phy_addr=r8169-0-200:00, irq=MAC)
    Oct 15 12:05:17 <hostname> kernel: r8169 0000:02:00.0 enp2s0f0: Link is Down
    Oct 15 12:05:17 <hostname> NetworkManager[2550]: <info>  [1634324717.4999] device (eth1): interface index 3 renamed iface from 'eth1' to 'enp5s0'
    Oct 15 12:05:17 <hostname> NetworkManager[2550]: <info>  [1634324717.5001] device (enp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
    Oct 15 12:05:17 <hostname> kernel: Generic FE-GE Realtek PHY r8169-0-500:00: attached PHY driver (mii_bus:phy_addr=r8169-0-500:00, irq=MAC)
    Oct 15 12:05:17 <hostname> kernel: r8169 0000:05:00.0 enp5s0: Link is Down
    Oct 15 12:05:17 <hostname> kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
    Oct 15 12:05:18 <hostname> kernel: Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
    Oct 15 12:05:19 <hostname> kernel: Bluetooth: hci0: Waiting for firmware download to complete
    Oct 15 12:05:19 <hostname> kernel: Bluetooth: hci0: Firmware loaded in 1660813 usecs
    Oct 15 12:05:19 <hostname> kernel: Bluetooth: hci0: Firmware revision 0.3 build 164 week 35 2021
    Oct 15 12:05:23 <hostname> iscsiadm[3261]: iscsiadm: Could not get list of targets from firmware. (err 21)
    Oct 15 12:05:24 <hostname> systemd[1]: Startup finished in 5.477s (firmware) + 36.189s (loader) + 1.924s (kernel) + 2min 1.154s (initrd) + 9.452s (userspace) = 2min 54.198s.
    Oct 15 12:08:42 <hostname> NetworkManager[2550]: <info>  [1634324922.5945] audit: op="statistics" interface="enp2s0f0" ifindex=2 args="500" pid=4486 uid=1000 result="success"
    Oct 15 12:08:42 <hostname> NetworkManager[2550]: <info>  [1634324922.5967] audit: op="statistics" interface="enp5s0" ifindex=3 args="500" pid=4486 uid=1000 result="success"
    Oct 15 12:08:42 <hostname> NetworkManager[2550]: <info>  [1634324922.6222] audit: op="statistics" interface="enp5s0" ifindex=3 args="500" pid=4486 uid=1000 result="success"
    Oct 15 12:08:42 <hostname> NetworkManager[2550]: <info>  [1634324922.6243] audit: op="statistics" interface="enp5s0" ifindex=3 args="500" pid=4486 uid=1000 result="success"
    Oct 15 12:38:10 <hostname> systemd[1]: Starting Firmware update daemon...
    Oct 15 12:38:12 <hostname> systemd[1]: Started Firmware update daemon.
    Oct 15 12:54:42 <hostname> NetworkManager[2550]: <info>  [1634327682.5185] device (enp2s0f0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
    Oct 15 12:54:42 <hostname> NetworkManager[2550]: <info>  [1634327682.6734] device (enp5s0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
    Oct 15 13:22:54 <hostname> NetworkManager[2550]: <info>  [1634329374.3262] device (enp2s0f0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
    Oct 15 13:22:54 <hostname> kernel: Generic FE-GE Realtek PHY r8169-0-200:00: attached PHY driver (mii_bus:phy_addr=r8169-0-200:00, irq=MAC)
    Oct 15 13:22:54 <hostname> NetworkManager[2550]: <info>  [1634329374.4810] device (enp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
    Oct 15 13:22:54 <hostname> kernel: r8169 0000:02:00.0 enp2s0f0: Link is Down
    Oct 15 13:22:54 <hostname> kernel: Generic FE-GE Realtek PHY r8169-0-500:00: attached PHY driver (mii_bus:phy_addr=r8169-0-500:00, irq=MAC)
    Oct 15 13:22:54 <hostname> kernel: r8169 0000:05:00.0 enp5s0: Link is Down
    Oct 15 14:10:52 <hostname> NetworkManager[2550]: <info>  [1634332252.1242] device (enp2s0f0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
    Oct 15 14:10:52 <hostname> NetworkManager[2550]: <info>  [1634332252.2852] device (enp5s0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
    Oct 15 14:10:52 <hostname> kernel: r8169 0000:05:00.0 enp5s0: Link is Down
    Oct 15 14:25:53 <hostname> NetworkManager[2550]: <info>  [1634333153.2626] device (enp2s0f0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
    Oct 15 14:25:53 <hostname> kernel: Generic FE-GE Realtek PHY r8169-0-200:00: attached PHY driver (mii_bus:phy_addr=r8169-0-200:00, irq=MAC)
    Oct 15 14:25:53 <hostname> NetworkManager[2550]: <info>  [1634333153.4140] device (enp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
    Oct 15 14:25:53 <hostname> kernel: r8169 0000:02:00.0 enp2s0f0: Link is Down
    Oct 15 14:25:53 <hostname> kernel: Generic FE-GE Realtek PHY r8169-0-500:00: attached PHY driver (mii_bus:phy_addr=r8169-0-500:00, irq=MAC)
    Oct 15 14:25:53 <hostname> kernel: r8169 0000:05:00.0 enp5s0: Link is Down
    只要努力,就能成功
    With hard work, success is possible.

  9. #9
    Join Date
    Nov 2020
    Location
    USA
    Posts
    18

    Default Re: AW: Ethernet (NetworkManager) Troubles

    Quote Originally Posted by Sauerland View Post
    But the question is:
    why do the 2 cards not working with r8169?
    I think the device is working, but there is some configuration issue. I can get the ethernet to light up, but only sometimes and only by adding a connection in KDE Settings > Connections > Add Wired Connection.

    That works about 30% of the time to bring "up" an ethernet connection. Which leads me to think this is software based, and not firmware.


    If it remains stubborn, I might resort to re-installing Tumbleweed. The machine is going to need to interface with a lot of LAN equipment soon, and a working ethernet port is a must.
    只要努力,就能成功
    With hard work, success is possible.

  10. #10
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    23,519
    Blog Entries
    1

    Default Re: AW: Ethernet (NetworkManager) Troubles

    Quote Originally Posted by Sauerland View Post
    @deano_ferrari
    Packman has the same packages, so no need to add my Repo, because less Repos are often more....... I am sometime a little bit faster in updating but packages are the same.....
    When using my Repo please use the Hardware branch:
    https://download.opensuse.org/reposi...USE_Leap_15.3/
    There are only hardware packages and not all others.
    Good to know. Maybe you should consider adjusting the recommended instructions accordingly...
    https://software.opensuse.org/downlo...&package=r8168
    openSUSE Leap 15.3; KDE Plasma 5

Tags for this Thread

Posting Permissions

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