gcc-4.4.3-2 failed to complile/make install

[CueDev]

Hi,

I'm going to use your driver for my Microsoft USB nic (r8152 chipset) but gcc-4.4.3-2 keeps failing, i followed the 6.0/6.5 instuctions since I'm running ESXi 6.5 in my NUC.

The error I keep getting is: configure: error: cannot execute: /build/toolchain/lin64/binutils-2.20.1-1/bin/x86_64-linux-ld: check with --with-ld or env. var. DEFAULT_LINKER

Also, the link to the CentOS 5.3 iso is broken, took me ages to find an 5.3 iso and then update it with deprecated packages.

Because the link was broken I also setup CentOS 7 but fails on the exact same error.

Do you know how I can fix this issue and compile/make install this installation.

Thanks in advance.

[gomesjj]

Hi,

Please check the instructions: for 6.0 the version of binutils is 2.22.

Also, it should work just fine on CentOs 7.x, provided you have the appropriate version of glibc, binutils and gcc.

[CueDev]

Hi, Please check the instructions: for 6.0 the version of binutils is 2.22. Also, it should work just fine on CentOs 7.x, provided you have the appropriate version of glibc, binutils and gcc.

Hi, I am following the 6.0 version but it still ends up with this error.

[gomesjj]

Are you using the build script (build-r8152-2.06.0_u60.sh)? The following line will be set at the top:

LD=/build/toolchain/lin64/binutils-2.22/bin/x86_64-linux-ld

So, if you are using the script and binutils-2.22 is available you should not be getting errors about binutils-2.20.1-1.

[CueDev]

Are you using the build script (build-r8152-2.06.0_u60.sh)? The following line will be set at the top: LD=/build/toolchain/lin64/binutils-2.22/bin/x86_64-linux-ld So, if you are using the script and binutils-2.22 is available you should not be getting errors about binutils-2.20.1-1.

I can't get to that script because the compile of gcc-4.4.3-2 fails, i verified and the file exists on that exact path.

This part of the readme.md (6.0) fails cd /build/toolchain/src/gcc-4.4.3-2 bash ./install.sh

When I run ./build-r8152-2.06.0_u60.sh I get the following error's ./build-r8152-2.06.0_u60.sh: line 35: /build/toolchain/lin64/gcc-4.4.3-2/bin/x86_64-linux-gcc: No such file or directory ./build-r8152-2.06.0_u60.sh: line 37: /build/toolchain/lin64/gcc-4.4.3-2/bin/x86_64-linux-gcc: No such file or directory /build/toolchain/lin64/binutils-2.22/bin/x86_64-linux-ld: cannot find BLD/build/vmkdriver-r8152-2.06.0-CUR/release/vmkernel64/SUBDIRS/vmkdrivers/src_92/drivers/usb/net/r8152-2.06.0/r8152.o: No such file or directory /build/toolchain/lin64/binutils-2.22/bin/x86_64-linux-ld: cannot find BLD/build/vmkdriver-r8152-2.06.0-CUR/release/vmkernel64/SUBDIRS/vmkdrivers/src_92/common/vmklinux_module.o: No such file or directory

[CueDev]

Hi,

I have also downloaded your compiled vib pacckage from https://bintray.com/gomesjj/VIBs/r8152_esxi65_vib/_latestVersion

But this also generates an error when installing, steps i performed are:

1. Put server in maintenance mode
2. ssh to server en ran the following command esxcli software vib install -v r8152-2.11.0-1_vmw.650.x86_64.vib -f Getting error: [VibDownloadError] ('r8152-2.11.0-1_vmw.650.x86_64.vib', '/tmp/vibtransaction/tmp.vib', '[Errno 2] Local file does not exist: /var/log/vmware/r8152-2.11.0-1_vmw.650.x86_64.vib') url = r8152-2.11.0-1_vmw.650.x86_64.vib Please refer to the log file for more details.

[gomesjj]

Hi,

Firstly, you don't need to put the server in maintenance mode, nor do you need the "-f" flag. However, you must provide the full path to the VIB file. For example, if you've copied the VIB file to /tmp. then the command will be:

esxcli software vib install -v /tmp/r8152-2.11.0-1_vmw.650.x86_64.vib

[CueDev]

Hi, Firstly, you don't need to put the server in maintenance mode, nor do you need the "-f" flag. However, you must provide the full path to the VIB file. For example, if you've copied the VIB file to /tmp. then the command will be: esxcli software vib install -v /tmp/r8152-2.11.0-1_vmw.650.x86_64.vib

Hi,

Still getting error's when supplying the full path. This time Unknown command or namespace

[CueDev]

Hi, I fixed the installation issues of the driver.

Steps taken

1. Disable Secure Boot
2. Change software acceptance level to CommunitySupported
3. Installed the driver
4. Rebooted server

But the NIC is not reconized still, did i miss a step?

[gomesjj]

Hi,

You need to disable the vmkusb native driver with the following command, then reboot:

esxcfg-module -d vmkusb

[CueDev]

Hi, You need to disable the vmkusb native driver with the following command, then reboot: esxcfg-module -d vmkusb

Hi,

Tried both

• esxcfg-module -d vmkusb (then reboot)
• esxcli system module set -m=vmkusb -e=FALSE (then reboot)

But the NIC is still not reconized.

[gomesjj]

Hi,

Could you please post the results for both of the following commands?

lusb

vmkload_mod -l | egrep "r8152|usb"

[CueDev]

Hi,

This is the result I get [root@localhost:~] vmkload_mod -l | egrep "r8152|usb" vmkusb_nic_fling 3 800 [root@localhost:~] lusb -sh: lusb: not found [root@localhost:~] lsusb Bus 001 Device 003: ID 045e:07c6 Microsoft Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 0e0f:8003 VMware, Inc. Root Hub

I also bought a TP-Link UE300 with the realtek8153 chipset but that is also not recognized. I enabled the vmkusb module again but didnt detect anything.

[CueDev]

Hi, It is getting a little bit ridiculous to get an (supported) USB NIC working. I tried the following but no NIC is shown.

Completely reinstalled the hypervisor (nothing running on it yet) After a clean install I first tried the following:

1. Verified with esxcli software vib list that vmkusb was installed by default, this is the case.
2. Verified with esxcfg-module -l | grep "usb" that the module was present, this is the case.
3. Verified with esxcfg-module -g vmkusb that enabled was set to 1, this is the case.
4. Inserted the TP-LINK UE300 (RTL8153) and rebooted the NUC.

After the reboot I can see the device with lsusb, but it was not recognized as a NIC, verified this with esxcli network nic list only the onboard NIC (ne1000) is listed.

When this didnt work I removed the TP-LINK UE300 and tried the following:

1. I removed the vmkusb vib with esxcli software vib remove --vibname=vmkusb in Maintenance mode
2. Rebooted the NUC and verified that the module was gone with esxcfg-module -l | grep "usb" this was the case
3. I changed the acceptance value to CommunitySupported
4. I installed the r8152 vib with esxcli software vib install -v /vmfs/volumes/infra-lab-001/drivers/r8152-2.11.0-1_vmw.650.x86_64.vib
5. Inserted the Microsoft USB NIC (r8152) and rebooted the NUC.

After the reboot I can see the device with lsusb, but it was not recognized as a NIC, verified this with esxcli network nic list only the onboard NIC (ne1000) is listed.

I Honestly have no idea what to do next, waiting for a reply from you to see if this can be fixed. Otherwise it's going to be Hyper-V Server for me.

Awaiting your reply.

[gomesjj]

Hi, Your email listing the output of vmload_mod /-l shows the vmkusb_usb_fling module loaded; that’s effectively the vmkusb module plus the FreeBSD ax8179 and usb_cdc modules loaded. You need to either uninstall or disable that module too before the r8152 module will work.

Jose

[CueDev]

Hi, Your email listing the output of vmload_mod /-l shows the vmkusb_usb_fling module loaded; that’s effectively the vmkusb module plus the FreeBSD ax8179 and usb_cdc modules loaded. You need to either uninstall or disable that module too before the r8152 module will work. Jose

Hi Jose,

I will give that one last try, but shouldn't the vmkusb just recognize the TP-LINK UE300?

Will get back to you in a few minutes when I disable/remove those module

[CueDev]

Hi, Your email listing the output of vmload_mod /-l shows the vmkusb_usb_fling module loaded; that’s effectively the vmkusb module plus the FreeBSD ax8179 and usb_cdc modules loaded. You need to either uninstall or disable that module too before the r8152 module will work. Jose

Hi Jose, I will give that one last try, but shouldn't the vmkusb just recognize the TP-LINK UE300? Will get back to you in a few minutes when I disable/remove those module

Just verified but non of those are installed, note that i did a full reinstall of ESXi 6.5 on the NUC before.

[gomesjj]

Hi,

No, the UE300 dev ID is not included on the fling, and I have already reported it to William and Songtao

Jose

[CueDev]

Hi, Well then I'm done with VMWare ESXi for a homelab on the NUC. I will run Hyper-V Server 2016 instead, it shouldn't be this hard to get an USB NIC up and running.

Thank you for your time.

[jaxjexjox]

Hi there,

I'm new to ESXI and I'm trying to get it working on my NUC for fun, I've stumbled across guides referencing your files. I now have ESXI 6.7 U2, I believe is the latest.

The file I have opted to download is. r8152-2.11.0-1_vmw.650.x86_64.vib

I did not put the NUC into Maint mode, but I typed in the following command.

esxcli software vib install -v /vmfs/volumes/5cc07287-31f4bd46-193 c-94c691a6857d/r8152-2.11.0-1_vmw.650.x86_64.vib -f

This spat back at me: Installation Result Message: Operation finished successfully. Reboot Required: false VIBs Installed: Realtek_bootbank_r8152_2.11.0-1_vmw.650 VIBs Removed: VIBs Skipped:

That being said, I do not (believe?) that the NIC is working,
I have read the post above by someone clearly smarter than me and done the following.

esxcli software vib list: r8152 2.11.0-1_vmw.650 Realtek CommunitySupported 2019-06-03

[root@localhost:~] esxcfg-module -l | grep "usb" vmkusb 4 516

[root@localhost:~] esxcfg-module -g vmkusb vmkusb enabled = 1 options = ''

[root@localhost:~] lsusb Bus 001 Device 005: ID 2357:0601 TP-Link Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 003: ID 0781:5151 SanDisk Corp. Cruzer Micro Flash Drive Bus 001 Device 002: ID 0603:00f2 Novatek Microelectronics Corp. Keyboard (Labtec Ultra Flat Keyboard) Bus 001 Device 001: ID 0e0f:8003 VMware, Inc. Root Hub

[root@localhost:~] esxcli network nic list Name PCI Device Driver Admin Status Link Status Speed Duplex MAC Address MTU Description

---

vmnic0 0000:00:1f.6 ne1000 Up Up 1000 Full 94:c6:91:a6:85:7d 1500 Intel Corporation Ethernet Connection (6) I219-V

I have not done the other things this person has mentioned, mostly since, again - they're clearly smarter than I am and they haven't got it working. Is it possible, TP-Link has made a new DeviceID / PCI-ID or whatever it is, meaning the driver doesn't work? Am I making a simple mistake?

I am more than happy to continue any testing if you can outline what I need to do.
Thanks for your time, sorry for bumping this thread, it seems close to the same as my issues.

[gomesjj]

Hi there,

I'm new to ESXI and I'm trying to get it working on my NUC for fun, I've stumbled across guides referencing your files. I now have ESXI 6.7 U2, I believe is the latest.

The file I have opted to download is. r8152-2.11.0-1_vmw.650.x86_64.vib

I did not put the NUC into Maint mode, but I typed in the following command.

esxcli software vib install -v /vmfs/volumes/5cc07287-31f4bd46-193 c-94c691a6857d/r8152-2.11.0-1_vmw.650.x86_64.vib -f

This spat back at me: Installation Result Message: Operation finished successfully. Reboot Required: false VIBs Installed: Realtek_bootbank_r8152_2.11.0-1_vmw.650 VIBs Removed: VIBs Skipped:

That being said, I do not (believe?) that the NIC is working, I have read the post above by someone clearly smarter than me and done the following.

esxcli software vib list: r8152 2.11.0-1_vmw.650 Realtek CommunitySupported 2019-06-03

[root@localhost:~] esxcfg-module -l | grep "usb" vmkusb 4 516

[root@localhost:~] esxcfg-module -g vmkusb vmkusb enabled = 1 options = ''

[root@localhost:~] lsusb Bus 001 Device 005: ID 2357:0601 TP-Link Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 003: ID 0781:5151 SanDisk Corp. Cruzer Micro Flash Drive Bus 001 Device 002: ID 0603:00f2 Novatek Microelectronics Corp. Keyboard (Labtec Ultra Flat Keyboard) Bus 001 Device 001: ID 0e0f:8003 VMware, Inc. Root Hub

[root@localhost:~] esxcli network nic list Name PCI Device Driver Admin Status Link Status Speed Duplex MAC Address MTU Description

vmnic0 0000:00:1f.6 ne1000 Up Up 1000 Full 94:c6:91:a6:85:7d 1500 Intel Corporation Ethernet Connection (6) I219-V

I have not done the other things this person has mentioned, mostly since, again - they're clearly smarter than I am and they haven't got it working. Is it possible, TP-Link has made a new DeviceID / PCI-ID or whatever it is, meaning the driver doesn't work? Am I making a simple mistake?

I am more than happy to continue any testing if you can outline what I need to do. Thanks for your time, sorry for bumping this thread, it seems close to the same as my issues.

HI,

From the output above I can see that the legacy USB modules are not loaded, which will happen if the new native driver (vmkusb) is running.

You need to run the following command, then reboot ESXi: esxcli system module set -m=vmkusb -e=FALSE

Regards,

Jose

[jaxjexjox]

Jose,

Thank you for the reply, it's really appreciated. That being said, I've done several things, since making that original post and if I recall, the line you've provided was one of them, yet I've had no traction regardless (yes, with a reboot)

I just re-entered that line and restarted and it hasn't worked :/ Here is lsusb -v (well just the start of the output)

Bus 001 Device 005: ID 2357:0601 TP-Link Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 3.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 9 idVendor 0x2357 TP-Link idProduct 0x0601 bcdDevice 30.00 iManufacturer 1 TP-LINK iProduct 2 USB 10/100/1000 LAN iSerial 6 000001000000 bNumConfigurations 2 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 57 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 256mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 0

[jaxjexjox]

Foolishly, I neglected to tell you WHY I provided that information.

I suspect, it's possible that Realtek / TPLink are using a new chip or identifier, hence the driver not working? (otherwise, I'm outright doing something wrong)

Does that information I've pasted from lsusb, reveal this? or should this USB adapter outright be working?

[gomesjj]

Foolishly, I neglected to tell you WHY I provided that information.

I suspect, it's possible that Realtek / TPLink are using a new chip or identifier, hence the driver not working? (otherwise, I'm outright doing something wrong)

Does that information I've pasted from lsusb, reveal this? or should this USB adapter outright be working?

Hi,

The TPLINK USB ID is correct (2357:0601) and should work out of the box. Maybe you could try using the old legacy command to disable the vmkusb module?

esxcfg-module -d vmkusb

Please reboot after running the command.

Regards

[jaxjexjox]

Alas, I ran that command and no luck.

I re-isntalled the 2.11 driver (I had 2.06 on, in desperation) - no luck.

[root@localhost:/var/log] esxcli software vib install -v /var/log/r8152-2.11.0-1_vmw.650.x86_64.vib -f Installation Result Message: Operation finished successfully. Reboot Required: false VIBs Installed: Realtek_bootbank_r8152_2.11.0-1_vmw.650 VIBs Removed: Realtek_bootbank_r8152_2.06.0-4 VIBs Skipped: [root@localhost:/var/log] esxcfg-module -d vmkusb

(Rebooted at this point, no luck)

Further outputs

[root@localhost:~] esxcfg-module -l | grep "usb" vmkusb_nic_fling 4 800 vmkusb Not Loaded [root@localhost:~] esxcfg-module -g vmkusb vmkusb enabled = 0 options = '' [root@localhost:~] lsusb Bus 001 Device 005: ID 2357:0601 TP-Link Bus 001 Device 003: ID 0781:5151 SanDisk Corp. Cruzer Micro Flash Drive Bus 001 Device 002: ID 0603:00f2 Novatek Microelectronics Corp. Keyboard (Labtec Ultra Flat Keyboard) Bus 001 Device 001: ID 0e0f:8003 VMware, Inc. Root Hub [root@localhost:~] esxcli network nic list Name PCI Device Driver Admin Status Link Status Speed Duplex MAC Address MTU Description

---

vmnic0 0000:00:1f.6 ne1000 Up Up 1000 Full 94:c6:91:a6:85:7d 1500 Intel Corporation Ethernet Connection (6) I219-V [root@localhost:~]

I've clearly done something wrong in one of the moves, hosing the hole thing right?

[gomesjj]

Alas, I ran that command and no luck.

I re-isntalled the 2.11 driver (I had 2.06 on, in desperation) - no luck.

[root@localhost:/var/log] esxcli software vib install -v /var/log/r8152-2.11.0-1_vmw.650.x86_64.vib -f Installation Result Message: Operation finished successfully. Reboot Required: false VIBs Installed: Realtek_bootbank_r8152_2.11.0-1_vmw.650 VIBs Removed: Realtek_bootbank_r8152_2.06.0-4 VIBs Skipped: [root@localhost:/var/log] esxcfg-module -d vmkusb

(Rebooted at this point, no luck)

Further outputs

[root@localhost:~] esxcfg-module -l | grep "usb" vmkusb_nic_fling 4 800 vmkusb Not Loaded [root@localhost:~] esxcfg-module -g vmkusb vmkusb enabled = 0 options = '' [root@localhost:~] lsusb Bus 001 Device 005: ID 2357:0601 TP-Link Bus 001 Device 003: ID 0781:5151 SanDisk Corp. Cruzer Micro Flash Drive Bus 001 Device 002: ID 0603:00f2 Novatek Microelectronics Corp. Keyboard (Labtec Ultra Flat Keyboard) Bus 001 Device 001: ID 0e0f:8003 VMware, Inc. Root Hub [root@localhost:~] esxcli network nic list Name PCI Device Driver Admin Status Link Status Speed Duplex MAC Address MTU Description

vmnic0 0000:00:1f.6 ne1000 Up Up 1000 Full 94:c6:91:a6:85:7d 1500 Intel Corporation Ethernet Connection (6) I219-V [root@localhost:~]

I've clearly done something wrong in one of the moves, hosing the hole thing right?

Hi,

If the output above is correct (don't know why some lines are stricken through) the vmkusb_nic_fling module is installed. You cannot have that installed and at the same time try to use legacy modules. The vmkusb_nic_fling is essentially vmkusb with the addition of FreeBSD drivers for ASIX and Realtek USB Ethernet adapters.

Please not that the vmkusb_nic_fling does not support TPLINK adapters, so if you want to use the r8152 module you will need to uninstall (or disable) this module too.

Regards

[jaxjexjox]

Sorry, I installed that for testing too, which command to remove that? Thanks once more.

[gomesjj]

Sorry, I installed that for testing too, which command to remove that? Thanks once more.

You can remove the VIB with the following command:

esxcli software vib remove -n vmkusb_nic_fling

Or, you can simply disable it:

esxcfg-module -d vmkusb_nic_fling

You need to reboot after either of the commands above is run.

[jaxjexjox]

This again didn't work believe it or not, truly baffling. Something must be fundamentally broken. Anything left I can do? The driver is compatible with U2 right?

[jaxjexjox]

I have decided to re-follow the NUC Blog guide, word for word, I've entirely re-installed ESXi https://nucblog.net/2018/11/installing-esxi-on-a-bean-canyon-nuc/

Enable execution policy, add VMWare module to powershell. Use special script to pull down ozip files. Run special command to pull out VMKUSB and inject the 2.11 Realtek, then compile into an ISO Burn ISO to USB key Replace weaslin.t00 file

Install ESXi, should be done....

Diagnosis:

[root@localhost:~] esxcli software vib list r8152 2.11.0-1_vmw.650 Realtek CommunitySupported 2019-06-07

[root@localhost:~] lsusb Bus 002 Device 002: ID 2357:0601 TP-Link

[root@localhost:~] esxcfg-module -l | grep "usb" usb 5 164 usb-storage 1 80

[root@localhost:~] esxcli network nic list vmnic0 0000:00:1f.6 ne1000 Up Up 1000 Full 94:c6:91:a6:85:7d 1500 Intel Corporation Ethernet Connection (6) I219-V

Build 13644319 I don't understand :/ ? Am I missing something here?

[gomesjj]

I am not sure what's going on here… Could you please look at the vmkernel.log file for any clues? You can search the log for entries related to the r8152 module.

Also, please confirm if the module is loaded at all:

esxcfg-module -l | grep r8152

If the module is not loaded, please try to load it manually while tailing vmkernel.log, by running the following command on one terminal:

tail -f /var/log/vmkernel.log

And this on another:

vmkload_mod r8152

Please make a note of any errors (if any) that appear on the log.