RTL8153 Compile
-
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 modversionsAnd 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 modversionsAnd 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 modversionsIt 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.koand tweaking udev rules to correctly detect it. -
Man I am here trying. I got the rules in aswell as the driver selected and loaded. pif-list says no for currently attached?
-
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.
Where does xCenter pull these stats from?
-
@geant90 you will need to do a
xe pif-scanif the NIC was not present during installation.Also, please share exact vendor id of your NIC. You can obtain it from
lspci -vordmesg -
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?
-
@geant90 Just wanted to know that you are seeing the same ID 2357:0601.
If
#ifconfigshows it correctly and the networking is working fine, you can scan it via XCP-NG-Center or# xe pif-introduceto let XAPI know about it.Does your
#xsconsoleshow 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.
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:
- copies rules and .ko appropriate places and updates
- 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
-
@geant90 I would ping @borzel to see if he knows about this behavior. Your
#ifconfigshows 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
- XCP-NG-Center
- #xsconsole -> Display NICS
- #xe pif-param-list
BTW, did you try XOA product, its a web based alternative to XCP-NG-Center with added automated functions?
-
[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): disabledHeres the picture of NIC
xscone Display + xcenterI 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? -
@geant90 so its XAPI itself that does not recognize the interface being online.
Whats the
#ethtool -i ethXandethtool ethXoutput look like?Usually on pif-scan the interface (if online) should get registered. And does
#dmesgshows that interface is now online when you plug a LAN into it? -
[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?
-
Ah! You will have to do a
#interface-renameoperation 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. -
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!
-
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 3.4.0.2-NAPI 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'
-
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
-
@geant90 awesome
I'm sure the relevant team shall bring a resolution.
