Lenovo L13 yoga 'Maybe the usb cable is bad' error when trying to register

[JJ Fullmer]

@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

[JJ Fullmer]

@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.

[JJ Fullmer]

@george1421 I was also now able to use this lenovo usb-c adapter to pxe boot other non-lenovo devices I previously wasn’t able to.
So bonus points for that.
This is on the 5.6 rt3 kernel

[george1421]

@jj-fullmer Great I’ll take bonus points whenever I can get them.

The keyboard thing has me a bit confused because that is native to the linux kernel. I made no adjustments in that area between 5.6.18 and 5.9.3 so it must be a “feature” of the linux kernel.

[george1421]

@jj-fullmer As long as you have that bzImage5618RT3 kernel queued up could you test what we are talking about in this thread: https://forums.fogproject.org/post/140103 I may have inadvertently fixed the requreiment to switch the computers from Raid-on mode to ahci to image with FOG. I know this might be a Dell specific setting, but its related to the Intel RST disk controller in raid mode. I think the lenovo systems should also have a similar setting because its an INTEL thing not a computer manufacturer thing.

Edit: Ignore this request, the 5510 I have has a sata disk in it. I just tested the kernel with a 7280 with an NVMe disk and the linux kernel does not work with this disk structure. So we are still no where in regards to a solution to this.

[JJ Fullmer]

@george1421 @Tom-Elliott
Just as an fyi related to this post. I just updated to the latest kernel from Tom (5.10.12 64bit) and it does not load up on a surface. Trying to get it just to go to the full inventory screen from the pxe menu it gets to 1% after about 15 minutes and just sits there. The kernel has been fine for all other machines just the surfaces have an issue (thus far in my testing anyway). Perhaps we can add whatever George did to the default kernel build to make sure surface’s stay supported?

[george1421]

@jj-fullmer said in Lenovo L13 yoga 'Maybe the usb cable is bad' error when trying to register:

it does not load up on a surface

Would you mind, when you have time create a video of how far its gets. I do have an older surface pro at home (circa 2015) that I could test on too. But I’d like to see at what point it freezes. Also if you change your fog configuration fog settings log level to 7 it will give us a bit more details on the FOS linux kernel startup.

[JJ Fullmer]

@george1421 well it got to

bzImage....1%

I actually had it sitting for a couple of hours. I just manually added the host in the gui and got it started imaging with the kernel you made here.
I’ll put it back to the default kernel and see what I can do.

[JJ Fullmer]

@george1421 I will got my log level to 7 and scheduled it to do an inventory task, I’ll take a video and we’ll see if it does it again on this 5.10.12 kernel

[JJ Fullmer]

@george1421 Well, perhaps it was a one time glitch or updating the bios solves the issue.

After surfaces image I have them install the latest driver pack that includes a bios update. After that happened and I tried to re-create the problem, the problem didn’t happen. I can share the video with all the log output if you still want it.

[george1421]

@jj-fullmer This appears more of it stalling out on the transfer of bzImage to the target computer than the kernel booting. At this points is still in iPXE realm because the kernel hasn’t started (what is inside bzImage) because the entire file hasn’t made it to the target computer yet.

[Sebastian Roth]

@jj-fullmer said in Lenovo L13 yoga 'Maybe the usb cable is bad' error when trying to register:

bzImage…1%

Although you seem to have this solved through a firmware update I might add that this is not cause by the kernel itself but by iPXE downloading the kernel binary from the FOG server. So messing with the kernel binary doesn’t make any difference at this stage.

[JJ Fullmer]

@sebastian-roth Well yes I see that now. It just felt like a familiar problem from whenever I change kernels. Should have just restarted and tried again before assuming something was broken though.