@george1421 The weird keyboard issue still occurs in the debug session where I can’t do shift+page up/down scrolling. But the adapter is working to be imaged otherwise. So it does work for imaging, just may be getting the wrong keyboard layout on this lenovo l390 yoga keyboard. Not sure it’s worth diggging into.

Posts made by JJ Fullmer
-
RE: Lenovo L13 yoga 'Maybe the usb cable is bad' error when trying to register
-
RE: Lenovo L13 yoga 'Maybe the usb cable is bad' error when trying to register
@george1421 Well I’m doing it anyway, especially after it was so weird with the keyboard the first time, I figure it’s worth testing. I’m doing a debug test on one of these models with that usb-c adapter now
-
RE: Move partitions on GPT layouts - need people to test
@sebastian-roth I hope to be building our 20H2 image the start of next year. So I can do some testing along with that for sure on this then.
-
RE: Lenovo L13 yoga 'Maybe the usb cable is bad' error when trying to register
@george1421 Things got crazy last week, but I have 2 of these I intend to image by Wednesday, so I should have some tests results for this before I’m away for the holiday.
-
RE: Lenovo L13 yoga 'Maybe the usb cable is bad' error when trying to register
@george1421 I need to get this machine into production so I can’t test this right now. But I can image one of the other’s we have tomorrow and see if this kernel does the trick.
-
RE: Lenovo L13 yoga 'Maybe the usb cable is bad' error when trying to register
@george1421 It did not. I gave the bzImage5618RT3 a go and that one is working. The keyboard is also working as expected. So there’s something else in 5.9.3 that is causing an issue with this machine.
Did you change anything else other than this driver and firmware for this kernel? Would it be safe to try using this one as default for all hosts? Or is there something else in there that might cause pause? -
RE: Lenovo L13 yoga 'Maybe the usb cable is bad' error when trying to register
@george1421 So it didn’t get the the firmware load error, is says that was fine but still no ip address.
What’s also odd is it seemed to change the laptop’s keyboard behavior, I could no longer use Shift+PgUp/down to scroll through the output. It acted as if pgup was just up.
This one did load into FOS without any errors at least, just didn’t actually connect to the network. I haven’t tried messing with the mac address pass through yet.
Gonna give the 5618RT3 a try
Then I’ll try the one from a year ago if needed -
RE: Lenovo L13 yoga 'Maybe the usb cable is bad' error when trying to register
@george1421 I found the last time we did this
https://forums.fogproject.org/topic/13905/issue-with-netcard-of-dock-gen2-of-lenovo-l390/22?_=1608147371899I am actually imaging one of the l390’s at the moment (the l13 is the successor to the L390). But I’m pretty sure the problem is related to just the usb-c adapter. I’ll try the 2 you just made, starting with 5.9.3
-
RE: Lenovo L13 yoga 'Maybe the usb cable is bad' error when trying to register
@george1421 I was just reviewing some internal documentation on this dongle and it looks like we’ve gone down this road once before. I have notes about a custom kernel for this adapter where the realtek driver was modified to work with the microsoft usb-c ethernet adapter. Time to search through some old posts.
-
RE: Lenovo L13 yoga 'Maybe the usb cable is bad' error when trying to register
Here is kernel 4.19.146
This time it acted like it was going to work but never got an ip address.I’m going to try something that shouldn’t work now. This laptop has a feature to do mac address pass through which I have enabled so that the usb-c ethernet can be used for imaging on different devices without needing to remove it from fog hosts. I’m going to try disabling that and I’ll use my default 5.6.18 kernel. I can’t imagine this will change anything, but might as well try everything.
-
RE: 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
-
RE: Lenovo L13 yoga 'Maybe the usb cable is bad' error when trying to register
@george1421
Here’s the 5.6.18 kernel debug messages, slightly different, but not that different. -
RE: Lenovo L13 yoga 'Maybe the usb cable is bad' error when trying to register
@george1421 It does, but it requires a special proprietary dongle. We actually have one, but we can’t find it anywhere.
-
RE: Lenovo L13 yoga 'Maybe the usb cable is bad' error when trying to register
@george1421
There wasn’t a /var/log/syslog in the debug console, I didcat /var/log/messages
as 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
-
RE: Lenovo L13 yoga 'Maybe the usb cable is bad' error when trying to register
Actually, when I hit enter to continue it did boot into the FOS debug console
-
RE: Lenovo L13 yoga 'Maybe the usb cable is bad' error when trying to register
Photo of the output when attempting debug with test kernel
Photo of output when attempting normal deploy task with test kernel
-
RE: Lenovo L13 yoga 'Maybe the usb cable is bad' error when trying to register
@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 modes
It 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
-
RE: Lenovo L13 yoga 'Maybe the usb cable is bad' error when trying to register
@george1421 On it! Going to try it still using your test kernel
-
RE: Lenovo L13 yoga 'Maybe the usb cable is bad' error when trying to register
@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 Argument
I 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.