XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    RTL8153 Compile

    Scheduled Pinned Locked Moved
    Development
    14
    88
    23.4k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R
      r1 XCP-ng Team
      last edited by

      @geant90 do you have product name/URL? We can make a proper installer (rpm) for its driver then.

      Its definitely important to have as large as hardware support available and I'm sure allowing USB NICs will help community to get along well.

      1 Reply Last reply Reply Quote 0
      • G
        geant90
        last edited by

        I am currently using a TP-Link TL-UE300 USB3.0 to Gigabit adapter. it is a RTL8153 chipset. Something is going on with Realtek's website that it is showing up in Chinese with a 404 error. I guess they are having some server issues as of this week. Anyways I downloaded the driver previously and have uploaded it here:

        Driver RTL8152

        The RTL8153 uses the updated RTL8152 driver and confirmed the Device IDs are in there.

        When attempting to make the .ko it will fail on the virgin r8152.c
        After untaring the file edit r8152.c
        Edit the file in an editor and add in line 31 (diff command 31a32,36 to enter the 5 lines after 31)
        Credit to Luiz Otavio de Lima Rodrigues comment on pcsuggest.com

        // missing in mii.h
        #if !defined BMCR_SPEED10
        #define BMCR_SPEED10 0x0000 /* Select 10Mbps */
        #endif

        As it is missing a defined BMCR_SPEED10

        And the make in the DDK will create the .ko succesfully. PM your address or I can PayPal gift you and you could order it yourself.

        Here is a generic ebay RTL8153 which is $8.61USD
        RTL8153 Ebay

        I am going to try some other things now.

        1 Reply Last reply Reply Quote 0
        • R
          r1 XCP-ng Team
          last edited by r1

          @geant90 from the source I could build r8152.ko but its not packaged as rpm, will need a spec file, but thats optional atm. You can install this in updates and do a # insmod /lib/modules/4.4.0+10/updates/r8152.ko to load it. Default modprob will load a different newer driver.

          I saw 50-usb-realtek-net.rules given in the source, which I think you are supposed to copy in /etc/udev/rules.d/ and reboot.

          1 Reply Last reply Reply Quote 0
          • R
            r1 XCP-ng Team
            last edited by

            I was checking what's available in the default kernel

            [root@xcp-ng-kernel ~]# modinfo r8152
filename:       /lib/modules/4.4.0+10/kernel/drivers/net/usb/r8152.ko
license:        GPL
description:    Realtek RTL8152/RTL8153 Based USB Ethernet Adapters
author:         Realtek linux nic maintainers <nic_swsd@realtek.com>
srcversion:     275BB427D5468F1A7C4952D
alias:          usb:v0955p09FFd*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v0955p09FFd*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v17EFp304Fd*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v17EFp304Fd*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v17EFp7205d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v17EFp7205d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v04E8pA101d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v04E8pA101d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v0BDAp8153d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v0BDAp8153d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v0BDAp8152d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v0BDAp8152d*dc*dsc*dp*icFFisc*ip*in*
depends:        mii
intree:         Y
vermagic:       4.4.0+10 SMP mod_unload modversions

            And in an experimental kernel

            [root@xcp-ng-rjv ~]# modinfo /lib/modules/4.9.0+0/kernel/drivers/net/usb/r8152.ko 
filename:       /lib/modules/4.9.0+0/kernel/drivers/net/usb/r8152.ko
version:        v1.08.9
license:        GPL
description:    Realtek RTL8152/RTL8153 Based USB Ethernet Adapters
author:         Realtek linux nic maintainers <nic_swsd@realtek.com>
srcversion:     AC6057A94C471403609426E
alias:          usb:v0955p09FFd*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v0955p09FFd*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v13B1p0041d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v13B1p0041d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v17EFp304Fd*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v17EFp304Fd*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v17EFp7205d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v17EFp7205d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v04E8pA101d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v04E8pA101d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v0BDAp8153d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v0BDAp8153d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v0BDAp8152d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v0BDAp8152d*dc*dsc*dp*icFFisc*ip*in*
depends:        mii
intree:         Y
vermagic:       4.9.0+0 SMP mod_unload modversions

            And in a may be possible future kernel

            [root@f6029920339a wip-kernel-4.14.78]# modinfo /root/rpmbuild/BUILD/kernel-4.14.78/drivers/net/usb/r8152.ko
filename:       /root/rpmbuild/BUILD/kernel-4.14.78/drivers/net/usb/r8152.ko
version:        v1.09.9
license:        GPL
description:    Realtek RTL8152/RTL8153 Based USB Ethernet Adapters
author:         Realtek linux nic maintainers <nic_swsd@realtek.com>
srcversion:     0B28043322357B23314507D
alias:          usb:v2357p0601d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v2357p0601d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v0955p09FFd*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v0955p09FFd*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v13B1p0041d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v13B1p0041d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v17EFp7214d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v17EFp7214d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v17EFp720Cd*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v17EFp720Cd*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v17EFp7205d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v17EFp7205d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v17EFp3069d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v17EFp3069d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v17EFp3062d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v17EFp3062d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v17EFp304Fd*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v17EFp304Fd*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v04E8pA101d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v04E8pA101d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v045Ep07C6d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v045Ep07C6d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v045Ep07ABd*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v045Ep07ABd*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v0BDAp8153d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v0BDAp8153d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v0BDAp8152d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v0BDAp8152d*dc*dsc*dp*icFFisc*ip*in*
alias:          usb:v0BDAp8050d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v0BDAp8050d*dc*dsc*dp*icFFisc*ip*in*
depends:        mii
intree:         Y
name:           r8152
vermagic:       4.14.78 SMP mod_unload modversions

            It looks like the product is 2357:0601 and its driver is natively available in 4.14.X kernel.

            Check ->

            alias:          usb:v2357p0601d*dc*dsc*dp*ic02isc06ip00in*
alias:          usb:v2357p0601d*dc*dsc*dp*icFFisc*ip*in*

            For now, you will have to continue using the compiled r8152.ko and tweaking udev rules to correctly detect it.

            1 Reply Last reply Reply Quote 0
            • G
              geant90
              last edited by

              Man I am here trying. I got the rules in aswell as the driver selected and loaded. pif-list says no for currently attached?

              1 Reply Last reply Reply Quote 0
              • G
                geant90
                last edited by

                How can I get 4.14.78?

                Can you send me that r8152.ko v1.09.9

                1 Reply Last reply Reply Quote 0
                • G
                  geant90
                  last edited by

                  Got a bit more progress. So it does not work in xCenter gui but looking at ifconfig I have statistic and after assign an ip address got it to respond to ping. It does not make a xenbridge though?

                  1 Reply Last reply Reply Quote 0
                  • G
                    geant90
                    last edited by

                    This post is deleted!
                    1 Reply Last reply Reply Quote 0
                    • G
                      geant90
                      last edited by

                      Looks like it has been working all along just xCenter not showing it correctly.

                      ![0_1541229437535_usbnic.PNG](Uploading 100%)

                      Where does xCenter pull these stats from?

                      1 Reply Last reply Reply Quote 0
                      • R
                        r1 XCP-ng Team
                        last edited by

                        @geant90 you will need to do a xe pif-scan if the NIC was not present during installation.

                        Also, please share exact vendor id of your NIC. You can obtain it from lspci -v or dmesg

                        G 1 Reply Last reply Reply Quote 0
                        • G
                          geant90
                          last edited by

                          I did. I even deleted and reintroduce with mac but no luck. Where does the dash get that information the pif is showing connected in command with the uuid but not in gui.

                          1 Reply Last reply Reply Quote 0
                          • G
                            geant90 @r1
                            last edited by

                            @r1 Do you mean the already known 2357:0601?

                            1 Reply Last reply Reply Quote 0
                            • R
                              r1 XCP-ng Team
                              last edited by

                              @geant90 Just wanted to know that you are seeing the same ID 2357:0601.

                              If #ifconfig shows it correctly and the networking is working fine, you can scan it via XCP-NG-Center or # xe pif-introduce to let XAPI know about it.

                              Does your #xsconsole show it under "Display NICs"?

                              1 Reply Last reply Reply Quote 0
                              • G
                                geant90
                                last edited by

                                @r1 I did do a scan. It detects it and adds to xcenter but list as disconnected. The console shows it but unknown and not connected. It does operate just fine as is but I would love for it to be as compatible as possible and we are so close.

                                Various Info

                                Check out that link.

                                So Xen scans and detects the usbnic fine. Adds under device but no data is populated. pif-list command shows device is currently attatched. In xCenter I configure an addition network with ip as seen @ .92 and it works fine. When I do a pif-param-list I beleive xCenter gets the info from there. Most of it is missing. ifconfig shows all the right info. If I can somehow find out where does pif get this info I could modify it to call info from ifconfig and whatever else necesarry. After I get this figure out I will also have it always get same interface name.

                                So far to get this easily working on others it would just need a script that:

                                1. copies rules and .ko appropriate places and updates
                                2. PLAN: Persistent inf name for xen
                                  3)PLAN: Get pif for device to get the needed info from ifconfig as it has all necesarry data. so it appears as any other NIC. So far it is working as it should
                                1 Reply Last reply Reply Quote 0
                                • R
                                  r1 XCP-ng Team
                                  last edited by r1

                                  @geant90 I would ping @borzel to see if he knows about this behavior. Your #ifconfig shows correct info, can assign ip and works fine but XCP-NG-Center says its disconnected.
                                  You say #xe pif-* works fine.

                                  XCP-NG-Center gets data from XAPI, the same API used by xe, so it would be a very rare case that the info produced is mismatching.

                                  Can you share screenshot of Host NICs from

                                  1. XCP-NG-Center
                                  2. #xsconsole -> Display NICS
                                  3. #xe pif-param-list

                                  BTW, did you try XOA product, its a web based alternative to XCP-NG-Center with added automated functions?

                                  G 1 Reply Last reply Reply Quote 0
                                  • G
                                    geant90 @r1
                                    last edited by

                                    @r1

                                    [root@CNP-MOBILE ~]# xe pif-param-list uuid=f4cab341-1f20-d9e6-4164-627debe5f03f
uuid ( RO)                       : f4cab341-1f20-d9e6-4164-627debe5f03f
                     device ( RO): side-373-eth0
                        MAC ( RO): 50:3e:aa:85:a7:ac
                   physical ( RO): true
                    managed ( RO): true
         currently-attached ( RO): true
                        MTU ( RO): 1500
                       VLAN ( RO): -1
             bond-master-of ( RO):
              bond-slave-of ( RO): <not in database>
      sriov-physical-PIF-of ( RO):
       sriov-logical-PIF-of ( RO):
       tunnel-access-PIF-of ( RO):
    tunnel-transport-PIF-of ( RO):
                 management ( RO): false
               network-uuid ( RO): 4f2d9638-59ae-6ce7-b36d-fea5eeb13d01
         network-name-label ( RO): Pool-wide network associated with side-373-eth0
                  host-uuid ( RO): af183f35-2629-4472-9538-90c2b37dca85
            host-name-label ( RO): CNP-MOBILE
      IP-configuration-mode ( RO): Static
                         IP ( RO): 192.168.91.92
                    netmask ( RO): 255.255.255.0
                    gateway ( RO): 192.168.91.1
    IPv6-configuration-mode ( RO): None
                       IPv6 ( RO):
               IPv6-gateway ( RO):
       primary-address-type ( RO): IPv4
                        DNS ( RO):
                 properties (MRO): gro: on
               capabilities (SRO):
                io_read_kbs ( RO): <unknown>
               io_write_kbs ( RO): <unknown>
                    carrier ( RO): false
                  vendor-id ( RO):
                vendor-name ( RO):
                  device-id ( RO):
                device-name ( RO):
                      speed ( RO): 0 Mbit/s
                     duplex ( RO): unknown
            disallow-unplug ( RW): false
               pci-bus-path ( RO):
               other-config (MRW): management_purpose: Extra
       igmp-snooping-status ( RO): disabled

                                    Heres the picture of NIC
                                    xscone Display + xcenter

                                    I know about XOA, use it at work. For this test machine I built a fresh XenServer 7.6 As I hope to get it working as natural as possible. That way if it works in XS it'll work in XCP-NG and XOA. As again goal is so it works for everywhere after a script shell install.
                                    Do you happen to have a usb nic woring in xen? Screen shots for comparison?

                                    1 Reply Last reply Reply Quote 0
                                    • R
                                      r1 XCP-ng Team
                                      last edited by

                                      @geant90 so its XAPI itself that does not recognize the interface being online.

                                      Whats the #ethtool -i ethX and ethtool ethX output look like?

                                      Usually on pif-scan the interface (if online) should get registered. And does #dmesg shows that interface is now online when you plug a LAN into it?

                                      G 1 Reply Last reply Reply Quote 0
                                      • G
                                        geant90 @r1
                                        last edited by

                                        @r1

                                        [root@CNP-MOBILE ~]# ethtool -i side-373-eth0
driver: r8152
version: v2.10.00 (2018/03/16)
firmware-version:
bus-info: usb-0000:00:14.0-1
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no

[root@CNP-MOBILE ~]# ethtool side-373-eth0
Settings for side-373-eth0:
        Supported ports: [ MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supported pause frame use: No
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Advertised pause frame use: Symmetric Receive-only
        Advertised auto-negotiation: Yes
        Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                             100baseT/Half 100baseT/Full
                                             1000baseT/Half 1000baseT/Full
        Link partner advertised pause frame use: No
        Link partner advertised auto-negotiation: Yes
        Speed: 1000Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 32
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: pumbg
        Wake-on: g
        Current message level: 0x00007fff (32767)
                               drv probe link timer ifdown ifup rx_err tx_err tx_queued intr tx_done rx_status pktdata hw wol
        Link detected: yes
[root@CNP-MOBILE ~]#

                                        Hmm just noticed for my other interface that works fine where it says Ports for the result of #ethtool under the USB#Gig NIC it says MII and the other working NIC says Twisted pair!?!? I know what a MII but could it be that? Anyone has working media interface to rule that out?

                                        1 Reply Last reply Reply Quote 0
                                        • R
                                          r1 XCP-ng Team
                                          last edited by

                                          Ah! You will have to do a #interface-rename operation to rename your side-373-eth0 to eth1, then XAPI will recognize it. Can you try it, I don't have exact command around but you can check with its help or code.

                                          G 1 Reply Last reply Reply Quote 1
                                          • G
                                            geant90 @r1
                                            last edited by

                                            @r1

                                            Man that is exactly what I was thinking about 4-5 hours ago driving to work. I was thinking maybe it has something to do with Xserver only recognizing calling NIC names "ethx" The only reason I had not tried it was because I wanted to ensure functionality before renaming to something persistent. Will keep you posted. Because it does pull the same stats matching from my function NIC. Will attempt after lunch!

                                            1 Reply Last reply Reply Quote 1
                                            • First post
                                              Last post