Forums

H Viviers
H Viviers
Offline
Resolved
0 votes
I don't have any extra ports on the motherboard for a NIC so I got a s7-rtl8153 USB to LAN adapter. Sadly it is not detected by ClearOS. How do I go about installing it?
https://okoya.up.seesaa.net/image/S7-RTL8153.jpg
Friday, August 14 2020, 10:45 AM
Share this post:
Responses (15)
  • Accepted Answer

    H Viviers
    H Viviers
    Offline
    Monday, August 17 2020, 07:41 AM - #Permalink
    Resolved
    0 votes
    It looks like we have a winner.
    I deleted the file I created and it looks like its working now.
    Thanks for the support. Learnt a lot.
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, August 15 2020, 04:11 PM - #Permalink
    Resolved
    0 votes
    You can see the NIC being recognised and the driver loaded:
    [    1.208453] usb 2-1.6: new high-speed USB device number 3 using ehci-pci
    [ 1.294962] usb 2-1.6: New USB device found, idVendor=0bda, idProduct=8153, bcdDevice=30.00
    [ 1.294968] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=6
    [ 1.294971] usb 2-1.6: Product: USB 10/100/1000 LAN
    [ 1.294974] usb 2-1.6: Manufacturer: Realtek
    [ 1.294977] usb 2-1.6: SerialNumber: 000001
    and
    [    1.498739] r8152 2-1.6:1.0 eth0: v1.09.9

    I don't understand why, when you create a /etc/sysconfig/network-scripts/ifcfg-enp0s29u1u6 with the contents I gave earlier that it does not show in the webconfig on a refresh. Can you try again? Even an empty file causes the interface to show up in the IP Settings screen when you do a refresh.

    What does "ls -og /sys/class/net" give?

    [edit]
    You can create the file just with:
    touch /etc/sysconfig/network-scripts/ifcfg-enp0s29u1u6

    [/edit]
    The reply is currently minimized Show
  • Accepted Answer

    H Viviers
    H Viviers
    Offline
    Saturday, August 15 2020, 02:49 PM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    I've just tested and adding the file without even a NIC works and makes it show up in the webconfig. All you need to do is refresh the IP Settings page. No need to reboot even. Make sure the file name and DEVICE match the NIC name from dmesg.


    Still nothing. Here is the rest of the dmesg. Hopefully this will help.
    Attachments:
    The reply is currently minimized Show
  • Accepted Answer

    H Viviers
    H Viviers
    Offline
    Saturday, August 15 2020, 02:48 PM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    I've just tested and adding the file without even a NIC works and makes it show up in the webconfig. All you need to do is refresh the IP Settings page. No need to reboot even. Make sure the file name and DEVICE match the NIC name from dmesg.


    Still nothing. Here is the rest of the dmesg.
    The reply is currently minimized Show
  • Accepted Answer

    Friday, August 14 2020, 09:25 PM - #Permalink
    Resolved
    0 votes
    I've just tested and adding the file without even a NIC works and makes it show up in the webconfig. All you need to do is refresh the IP Settings page. No need to reboot even. Make sure the file name and DEVICE match the NIC name from dmesg.
    The reply is currently minimized Show
  • Accepted Answer

    Friday, August 14 2020, 09:14 PM - #Permalink
    Resolved
    0 votes
    I'll have to give it a try tomorrow as I think it should give something in the webconfig without even having a valid NIC.
    The reply is currently minimized Show
  • Accepted Answer

    H Viviers
    H Viviers
    Offline
    Friday, August 14 2020, 08:14 PM - #Permalink
    Resolved
    0 votes
    I created the file /etc/sysconfig/network-scripts/ifcfg-enp0s29u1u6
    Copied your code into it and restarted. Still nothing in the webconfig.

    Installed app-network with yum update app-network --enablerepo=clearos-updates-testing,
    also no joy.
    The reply is currently minimized Show
  • Accepted Answer

    Friday, August 14 2020, 02:28 PM - #Permalink
    Resolved
    0 votes
    dmesg will only show someting on boot (in the logs) or when something is plugged in.

    If I were to gamble, enp0s29u1u6 is your USB NIC and is not configured. It probably is not showing in the webconfig because a /etc/sysconfig/network-scripts/ifcfg-enp0s29u1u6 has not been created. Why, I don't know. You can try installing the version of app-network in clearos-updates-testing and see it it fixes it. It has bugs in it so do not use it if you have an upstream VLAN (not common).

    The other thing to do is create the file manually and in it put something like:
    DEVICE=enp0s29u1u6
    TYPE="Ethernet"
    ONBOOT="yes"
    USERCTL="no"
    BOOTPROTO="static"
    IPADDR="172.22.22.1"
    NETMASK="255.255.255.0"
    This should get it to show up and you can then configure it
    The reply is currently minimized Show
  • Accepted Answer

    H Viviers
    H Viviers
    Offline
    Friday, August 14 2020, 01:24 PM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    So it is loading the correct driver. What does "ip link show"?
    if you unplug it and re-plug it in (perhaps to a different port), what does the command "dmesg" show (near the bottom) referring to the device?


    /root$ ip link show

    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,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether 00:e0:4c:23:06:e2 brd ff:ff:ff:ff:ff:ff
    3: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether 8c:89:a5:e2:30:27 brd ff:ff:ff:ff:ff:ff
    4: enp0s29u1u6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:e0:4a:6a:22:d6 brd ff:ff:ff:ff:ff:ff

    ==========================================================
    dmesg

    [ 9.932679] AVX version of gcm_enc/dec engaged.
    [ 9.932682] AES CTR mode by8 optimization enabled
    [ 9.936313] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni)
    [ 9.936354] alg: No test for __generic-gcm-aes-aesni (__driver-generic-gcm-aes-aesni)
    [ 9.946625] snd_hda_intel 0000:00:1b.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
    [ 9.946661] snd_hda_intel 0000:00:1b.0: irq 28 for MSI/MSI-X
    [ 10.004170] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC887-VD: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line
    [ 10.004174] snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
    [ 10.004176] snd_hda_codec_realtek hdaudioC0D0: hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
    [ 10.004178] snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0
    [ 10.004180] snd_hda_codec_realtek hdaudioC0D0: inputs:
    [ 10.004182] snd_hda_codec_realtek hdaudioC0D0: Front Mic=0x19
    [ 10.004185] snd_hda_codec_realtek hdaudioC0D0: Rear Mic=0x18
    [ 10.004187] snd_hda_codec_realtek hdaudioC0D0: Line=0x1a
    [ 10.023140] input: HDA Intel PCH Front Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input6
    [ 10.023315] input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input7
    [ 10.023854] input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input8
    [ 10.024446] input: HDA Intel PCH Line Out as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
    [ 10.025095] input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
    [ 10.074175] intel_rapl: Found RAPL domain package
    [ 10.074178] intel_rapl: Found RAPL domain core
    [ 10.074181] intel_rapl: Found RAPL domain uncore
    [ 10.074186] intel_rapl: RAPL package 0 domain package locked by BIOS
    [ 11.212999] Adding 4063228k swap on /dev/mapper/clearos-swap. Priority:-2 extents:1 across:4063228k FS
    [ 11.926174] XFS (sda1): Mounting V5 Filesystem
    [ 12.825522] XFS (sda1): Ending clean mount
    [ 13.235237] type=1305 audit(1597400871.297:3): audit_pid=686 old=0 auid=4294967295 ses=4294967295 res=1
    [ 13.819193] RTL8211B Gigabit Ethernet r8169-100:00: attached PHY driver [RTL8211B Gigabit Ethernet] (mii_bus:phy_addr=r8169-100:00, irq=-2)
    [ 13.893764] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
    [ 15.534885] libphy: r8169-100:00 - Link is Up - 100/Full
    [ 15.534898] IPv6: ADDRCONF(NETDEV_CHANGE): enp1s0: link becomes ready
    [ 18.169957] RTL8211E Gigabit Ethernet r8169-200:00: attached PHY driver [RTL8211E Gigabit Ethernet] (mii_bus:phy_addr=r8169-200:00, irq=-2)
    [ 18.347352] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
    [ 21.638193] libphy: r8169-200:00 - Link is Up - 1000/Full
    [ 21.638205] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
    [ 22.631084] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
    [ 22.926159] Netfilter messages via NETLINK v0.30.
    [ 22.929087] ip_set: protocol 7
    [ 22.943053] PPP generic driver version 2.4.2
    [ 22.951786] PPP MPPE Compression module registered
    [ 23.224446] ip6_tables: (C) 2000-2006 Netfilter Core Team

    I can't see any reference to the adapter.
    I am currently remotely accessing from home so moving to another port is not possible.
    The reply is currently minimized Show
  • Accepted Answer

    Friday, August 14 2020, 01:02 PM - #Permalink
    Resolved
    0 votes
    So it is loading the correct driver. What does "ip link show"?
    if you unplug it and re-plug it in (perhaps to a different port), what does the command "dmesg" show (near the bottom) referring to the device?
    The reply is currently minimized Show
  • Accepted Answer

    H Viviers
    H Viviers
    Offline
    Friday, August 14 2020, 12:24 PM - #Permalink
    Resolved
    0 votes
    /root$ lsmod | egrep '(cdc_ether|r8152)'

    r8152 55236 0
    mii 14434 1 r8152


    /root$ rmmod cdc_ether
    rmmod: ERROR: Module cdc_ether is not currently loaded
    The reply is currently minimized Show
  • Accepted Answer

    H Viviers
    H Viviers
    Offline
    Friday, August 14 2020, 12:18 PM - #Permalink
    Resolved
    0 votes
    The first line.
    The reply is currently minimized Show
  • Accepted Answer

    Friday, August 14 2020, 12:07 PM - #Permalink
    Resolved
    0 votes
    From googling, it needs the r8152 driver but Linux often installs the cdc_ether driver instead. What do you get from:
    lsmod | egrep '(cdc_ether|r8152)'
    If it shows the cdc_ether driver, what happens if you do:
    rmmod cdc_ether
    modprobe r8152
    The reply is currently minimized Show
  • Accepted Answer

    H Viviers
    H Viviers
    Offline
    Friday, August 14 2020, 11:44 AM - #Permalink
    Resolved
    0 votes
    No probs. I thought the one did not go through.

    This is the lsusb output. I believe its the first one.

    Bus 002 Device 003: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter
    Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
    Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 001 Device 004: ID 03f0:0024 HP, Inc KU-0316 Keyboard
    Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
    Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    The reply is currently minimized Show
  • Accepted Answer

    Friday, August 14 2020, 11:37 AM - #Permalink
    Resolved
    0 votes
    New posters have the first couple of posts moderated. I am deleting your other post.

    From the command "lsusb", what is the line for the NIC?
    The reply is currently minimized Show
Your Reply