gcc-4.4.3-2 failed to complile/make install #1
Comments
|
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. |
|
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 When I run ./build-r8152-2.06.0_u60.sh I get the following error's |
|
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:
|
|
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 |
|
Hi, Steps taken
But the NIC is not reconized still, did i miss a step? |
|
Hi, You need to disable the vmkusb native driver with the following command, then reboot: esxcfg-module -d vmkusb |
Hi, Tried both
But the NIC is still not reconized. |
|
Hi, Could you please post the results for both of the following commands? lusb vmkload_mod -l | egrep "r8152|usb" |
|
Hi, This is the result I get 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. |
|
Hi, Completely reinstalled the hypervisor (nothing running on it yet)
After the reboot I can see the device with lsusb, but it was not recognized as a NIC, verified this with When this didnt work I removed the TP-LINK UE300 and tried the following:
After the reboot I can see the device with lsusb, but it was not recognized as a NIC, verified this with I Honestly have no idea what to do next, waiting for a reply from you to see if this can be fixed. Awaiting your reply. |
|
Hi, 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. |
|
Hi, No, the UE300 dev ID is not included on the fling, and I have already reported it to William and Songtao Jose |
|
Hi, Thank you for your time. |
|
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. 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 This spat back at me: That being said, I do not (believe?) that the NIC is working, esxcli software vib list: [root@localhost:~] esxcfg-module -l | grep "usb" [root@localhost:~] esxcfg-module -g vmkusb [root@localhost:~] lsusb [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 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. I am more than happy to continue any testing if you can outline what I need to do. |
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: Regards, Jose |
|
Jose, Thank you for the reply, it's really appreciated. I just re-entered that line and restarted and it hasn't worked :/ Bus 001 Device 005: ID 2357:0601 TP-Link |
|
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 |
|
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 (Rebooted at this point, no luck) Further outputs [root@localhost: 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'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 |
|
Sorry, I installed that for testing too, which command to remove that? |
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. |
|
This again didn't work believe it or not, truly baffling. Something must be fundamentally broken. |
|
I have decided to re-follow the NUC Blog guide, word for word, I've entirely re-installed ESXi Enable execution policy, add VMWare module to powershell. Install ESXi, should be done.... Diagnosis: [root@localhost:~] esxcli software vib list [root@localhost:~] lsusb [root@localhost:~] esxcfg-module -l | grep "usb" [root@localhost:~] esxcli network nic list Build 13644319 |
|
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. |
|
esxcfg-module -l | grep r8152 Produced no result, so presumably not loaded. Got this Also [root@localhost:~] vmkload_mod r8152 Resulting in this, in the second log window. (sorry, long one) . root@localhost:~] tail -f /var/log/vmkernel.log |
|
Hi Can you confirm that the usbnet module is actually running? For you previous listing I can only see usb and usb-storage. If it's not running, please use the following command to start the module: vmkload_mod usbnet And then, the following command to load the r8152 module: vmkload_mod r8152 If the usbnet module doesn't start, then there's something wrong with your installation. Otherwise, if both modules start OK, then you might want to mark them to load at boot (they might not for some reason): esxcfg-module -e usbnet Note: please tail vmkernel.log for any errors. |
|
[root@localhost: I think we've finally got some answers! Question is why the guide doesn't outline this requirement (and so many others haven't mentioned it, perhaps something has changed)? Everything perfect, except those 2 commands to keep it at boot? didn't work? Hmmm |
|
Hi, I am glad it's working now, but I don't know why the usbnet module is not loading automatically in your case. Once the vmkusb module is disabled, the legacy modules (usb, usbnet and usb-storage) should all load automatically. By the way, this GitHub entry is related to how to compile the drivers, not how to use them. If you would like to read about the drivers and what should or should not be running, please have a look at my blog: https://www.devtty.uk/homelab/Want-a-USB-Ethernet-driver-for-ESXi-You-can-have-two/ Note that I have installed and tested the drivers on all versions of ESXi from 5.1, and I have never experienced any issues. Particularly from version 6.5, when the vmkusb native module was introduced, I have never seen the legacy modules not load like this once vmkusb is disabled. |
|
I found some articles, on how to force SSH to be on, upon reboot which I did manage to figure out. I may adapt the code in those articles to force the module to load. (I haven't tested the NIC but it seems to have progressed further) I'll mess around, at least I know how to fix it on a reboot, which should in theory be rare! Thank you. |
|
Hi,
I wonder if you would be willing to test a modified version of the VIB to see if we can resolve the issue with the usbnet module?
Regards,
Jose
… On 7 Jun 2019, at 13:51, jaxjexjox ***@***.***> wrote:
I found some articles, on how to force SSH to be on, upon reboot which I did manage to figure out.
I may adapt the code in those articles to force the module to load. (I haven't tested the NIC but it seems to have progressed further)
I'll mess around, at least I know how to fix it on a reboot, which should in theory be rare!
Thank you.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#1?email_source=notifications&email_token=AEMV5ERNC5R4DYNYTAYWMHDPZJKWFA5CNFSM4G3TYGR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXFXHOA#issuecomment-499872696>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEMV5ETNOIZBK7T2Q5MLMJDPZJKWFANCNFSM4G3TYGRQ>.
|
|
Totally happy to - if you like I could just give you SSH access, you seem trustworthy enough. |
|
(If I'm to do it just drop me some comprehensive instructions on what to do, if I stick with this install, or roll a fresh one with your file) |
|
Hi, Yes, it would be an uninstall of the r8152 VIB, followed by a reboot, then install the new one. Please send an email to gomesjj at devtty.co.uk and I will respond with instructions and the new VIB. If the problem is resolved, then I will upload the new VIB to Bintray. Jose |
|
My goal is to extend the r8152 with new devices, before that I want to verify whether I could use the development code from github with devices listed as tested. I) vmkload_mod -l | grep r8152 II) vmkload_mod -l | grep usb /var/log/vmkernel.log log says module r8152 ... If you closely look into the vmkernel.log it displays lot of warnings. Appreciate help in this. Thanks, |
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_LINKERAlso, 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.
The text was updated successfully, but these errors were encountered: