RTL8153 Compile

  • How can I get 4.14.78?

    Can you send me that r8152.ko v1.09.9

  • 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?

  • This post is deleted!

  • 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?

  • XCP-ng Team

    @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

  • 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.

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

  • XCP-ng Team

    @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"?

  • @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

  • XCP-ng Team

    @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?

  • @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):
                        netmask ( RO):
                        gateway ( RO):
        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?

  • XCP-ng Team

    @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?

  • @r1

    [root@CNP-MOBILE ~]# ethtool -i side-373-eth0
    driver: r8152
    version: v2.10.00 (2018/03/16)
    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
            Supported pause frame use: No
            Supports auto-negotiation: Yes
            Advertised link modes:  10baseT/Half 10baseT/Full
                                    100baseT/Half 100baseT/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?

  • XCP-ng Team

    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.

  • @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!

  • @r1 @borzel

    Ladies and gentlemen we have struck gold.

    [root@XenServer-TestNIC ~]# interface-rename --list
    ERROR    [2018-11-05 12:36:24] Can't generate current state for interface '{'Driver': 'r8152', 'Permanent MAC': '50:3E:AA:85:B6:AE', 'Bus Info': 'usb-0000:00:14.0-2', 'BIOS device': {'all_ethN': 'eth1', 'physical': ''}, 'Assigned MAC': '50:3E:AA:85:B6:AE', 'Firmware version': '', 'Driver version': 'v2.10.00 (2018/03/16)', 'Kernel name': 'side-9065-eth1'}' - Unrecognised PCI address 'usb-0000:00:14.0-2'
    Name  MAC                PCI              ethN  Phys  SMBios       Driver  Version       Firmware
    eth0  a0:d3:c1:06:ed:a1  0000:00:19.0[0]  eth0  em1   Onboard LAN  e1000e  0.13-4
    [root@XenServer-TestNIC ~]#

    So it looks like it has a problem being a usb device. Time to find out what can be done to over come this.

    Unrecognised PCI address 'usb-0000:00:14.0-2'

  • XCP-ng Team

    Yayy! It's more clear. The rename script is probably only looking for PCI device, not USB one. Now, we'll have to find where this code is written and improve it 🙂

  • XCP-ng Team

    @geant90 awesome 👏 👏 I'm sure the relevant team shall bring a resolution.

  • XCP-ng Team

  • @r1 @olivierlambert @stormi

    In interface-rename python I see it imports xcp.pci and others. Maybe if it is edited to import usb as well then using an if command we can get it to also recognize a pci address for examaple 'usb-0000:00:14.0-2 (if usb-xxxx:xx:xx:x-x then refer to usb location. Will play around now. For now I wonder if a simple edit to the script would get it working. usb-0000:00:14.0-2 does in fact refer to to the proper pci address of the usb controller @ 00:14.0 I wonder if for reporting purposes using a if command to strip away usb-0000:00:14.0-2 to 0000:00:14.0-2 or possibly 0000:00:14.0 would be enough for it to comply with xapi then with a proper eth name it will report correctly refresh xcenter appropriately. Since it can be matched with permanent MAC it in theory would be able to function as that just displays NIC. Then if that is successful I can see if it would cause conflict with two reporting same PCI location. Which from looking at the script it should not as that is just reporting to the end user usable info which we really don't care as we are aware it is a usb device then could simply find out which to be specific. This does not effect the driver which is already communicating properly and the device is functioning fine it just cannot determine that bus location.

Log in to reply

XCP-ng Pro Support

XCP-ng Pro Support