RTL8153 Compile
-
That would be wonderful and also helpful for other people having the same issue
-
@olivierlambert Created a pull request on this matter, I hope it's properly described.
-
@jokurinopoloski I reviewed your PR!
Thanks for the contribution
-
Apologies for the bump of an old topic, but is anyone aware of the existence of an updated r8152 driver that will support the r8156 (2.5gbe) chipset within xcp-ng?
I can download the driver source from realtek directly, but am not 100% on how to compile it and then have xcp-ng use it in preference to the existing driver.
-
A topic for @Andrew I think ^^
-
@FilHarr @olivierlambert Sure, I'll give it a go.
I have a USB r8153 and r8156 adapter on the way for testing. -
@FilHarr The new realtek driver builds and loads.... I'll give it a try this weekend when my new USB adapter arrives.
-
@Andrew That sounds encouraging! Happy to help out by doing some testing if that's a) possible and b) would assist.
-
@FilHarr I have the driver built and working, but I have a USB naming problem that is not safely resolved by the previous workaround method so I have not finished testing. Looks like they will be adding the new 5Gb NICs soon.
-
@Andrew I eventually managed to get v2.17.1 of the realtek driver compiled and loaded. I have an RTL8153 and an RTL8156 based USB adapter connected to my host device which are both being correctly identified (took me a while to work out how to get the updated kernel module to load on boot but figured it out in the end). Have added both networks to a VM and everything seems to be working ok (transfer speeds are as expected).
What is the issue you're seeing with the USB naming? I already had the RTL8153 USB working with the default driver and a rename rule in '70-persistent-net.rules'. Added a similar rule for the RTL8156 USB and both renames seem to be surviving reboots with the updated 2.17.1 driver.
-
-
@FilHarr The USB renaming rule works if I have one USB adapter... so I guess it's good enough for now.
-
@Andrew but just to understand: did you do something else apart recompiling the r8152 project?
-
@etomm For the code I compiled it mostly as-it (with one change to support the different XCP kernel header version). I also added three udev rule changes. One is included with the driver code. One change to stop XCP scripts changing USB ethernet names. And one that is to support static USB ethernet names and rename unknown USB ethernet devices to protect the system from conflicts.
I now have it working correctly with multiple USB ethernet adapters and stabled names that don't interfere with regular ethernet adapters. It still requires manually adding the MAC addresses and ethernet device names because XCP/Xen does not support USB ethernet devices.
-
@Andrew but I suppose that even without the udev rules, the device was still working with just the code compilation. I made it compile too, changing just a #if definition that was looking for kernel source version < 4.19.10 and mine is 4.19.0 but existing and was conflicting. Was there another code modification?
-
@Andrew said in RTL8153 Compile:
@etomm For the code I compiled it mostly as-it (with one change to support the different XCP kernel header version). I also added three udev rule changes. One is included with the driver code. One change to stop XCP scripts changing USB ethernet names. And one that is to support static USB ethernet names and rename unknown USB ethernet devices to protect the system from conflicts.
I now have it working correctly with multiple USB ethernet adapters and stabled names that don't interfere with regular ethernet adapters. It still requires manually adding the MAC addresses and ethernet device names because XCP/Xen does not support USB ethernet devices.
@Andrew would you be willing to share the udev rule changes that you made? Also, are you using 8.2 or 8.3 beta? Thank you!
