Lenovo L13 yoga 'Maybe the usb cable is bad' error when trying to register
-
@george1421 I’m now trying the 4.19.146 64bit kernel from tom via the fog web gui kernel update page
-
@george1421
Here’s the 5.6.18 kernel debug messages, slightly different, but not that different.
-
@george1421 The one off kernel.
-
@jj-fullmer sorry I had an update “Duh, and blind. It is missing a hardware driver. SO this last images was that from the one-off kernel or from the FOG standard kernel?”
-
@george1421 It does, but it requires a special proprietary dongle. We actually have one, but we can’t find it anywhere.
-
@jj-fullmer Interesting that this computer has an intel ethernet nic in it.
Duh, and blind. It is missing a hardware driver. SO this last images was that from the one-off kernel or from the FOG standard kernel?
-
@george1421
There wasn’t a /var/log/syslog in the debug console, I didcat /var/log/messagesas that was there and the most interesting bit was at the bottom, it’s a bit much to type out manually at the moment.I took photos at the sections where I saw warnings
-
Actually, when I hit enter to continue it did boot into the FOS debug console
-
Photo of the output when attempting debug with test kernel
Photo of output when attempting normal deploy task with test kernel
-
@george1421 First notes are it says at the start
ucsi_acpi USBC000:00 con1: failed to register alternate modes
ucsi_acpi USBC000:00 con2: failed to register alt modesIt didn’t get into debug mode, gonna try again with the normal kernel, and if that doesn’t go into debug then I’ll try the latest 4.x
-
@george1421 On it! Going to try it still using your test kernel
-
@jj-fullmer I wonder if there is nic card firmware missing. This is telling me its now loading and talking to the network adapter, its having a problem fully communicating with it. When you have time boot into debug mode and then search /var/logs/syslog for that network adapter and see if there are any hints in there to why its not happy.
-
@george1421
Sorry for the delay, things are a bit crazy. Finally got a chance to give this a try
Getting a different error now/bin/cat: /sys/class/net/enp0s20f0u2/carrier: Invalid ArgumentI queued up the host to be imaged, booted into fog, it loaded the test kernel, then gave this error like 20 times, the said it failed to get an IP via DHCP and then paused with a press enter to continue.
Gonna try with the normal 5.6.18 kernel again.
-
@jj-fullmer Ok I looked and the realtek driver has been in the linux kernel for a while (sorry just closed the page and don’t remember). That is also a very old driver in the official linux kernel. I patched a one off kernel with the updated realtek driver for the 8125 adapter.
https://drive.google.com/file/d/1zcQvZNkick_Q4DyHKL9_X8dSXHjkN_BD/view?usp=sharing
Download this and save as bzImage5618RT into /var/www/html/fog/service/ipxe directory. Then update the host definition to use this kernel (or just change the global kernel from bzImage to bzImage5618RT. It is the same kernel as the official FOG kernel except I’ve patched the kernel with the updated realtek drivers.
-
Hardware IDS:
USB\VID_17EF&PID_720C&REV_3000 USB\VID_17EF&PID_720CVendor, the name of the device in windows is
Lenovo USB-C to Ethernet Adapterbut the driver provider and the Manufacturer is listed as Realtek -
@jj-fullmer From a windows computer will you give me the vendor and hardware ID of that network adapter? I’ll look up to see if that driver is in the FOG kernel.
