Yoga 260 w/RTL8153 freeze (or black screen) after init.xz loads
First of all thank you all for your fog excellency! I am having a similar issue as:
I am using ubuntu 14.04 and SVN Revision: 5937. Same symptom when legacy booting but sudburr seems to have had success with UEFI. However, I cannot seem to get these Yoga 260’s to load past the fog menu. I have used fog with these dongles on the Thinkpad Yoga S1 last year (700+). Using UEFI boot and no kernel parameters, I can get to fog menu, I make a selection and it hangs after (blank sreen with a backlight if there is no task or what “init.xz…ok” and freeze if I have a task scheduled. If I enter ipxe.efi or snp.efi or snponly.efi I receive “ipxe.efi…No such file or directory” and if I navigate to IPaddress/fog/service/ipxe/ I do not see the referenced files.
All I see is
[IMG] bg.png 2016-07-22 12:22 21K
Should I see my ipxe.efi listed here ? I am hoping for some guidance on the next steps to troubleshoot …thank you!
@drewski Good job!! Yes the FOSL usb can be removed once the FOS engine starts. The usb is only the delivery system for the FOS engine. FOS runs out of memory once loaded.
Success!! Thank you kindly. We ended up using the ThinkPad OneLink+ to RJ45 Adapters for the deployment but they let me keep a laptop to test the FOSL usb. I have learned a valuable lesson for the next time. Thank you for incredible help and assistance. One question, can the FOSL usb safely be removed after the task has started ?
Thank you all and Cheers!
There is another option that is a possibility. I have put together a way to boot into the FOS engine (the OS that runs on the target computer for capturing and deploying images) using a usb boot stick. https://forums.fogproject.org/topic/7727/building-usb-booting-fos-image
Since you are on svn 5937 this should work with your install of FOG. If you can’t/don’t want to create the image file I have one at work I can upload to my google drive. But the idea is to manually register your target computer then schedule a capture or deploy task, then boot from the usb stick and select the capture/deploy image option. The FOS engine should boot from the usb stick and start doing its job. If you forget to schedule the capture/deploy on the FOG server but boot from the usb stick you will see a warning message about a missing type variable.
Thanks for the replies! Thank you for the clarification on the file locations. Secure boot and security chip are both disabled. Updated to 1.3.0-rc2 and have the same symptoms. I actually have a firmware newer than what is posted on lenovo’s site (1.43) but I downgraded one to the latest posted on lenovo.com (1.42) and tested with the same results. Pinging the laptop results in “host unreachable” as soon as I make my selection or deploy image.
New development, we received the (FRU) service Part Number: 03X7014, NIC/VGA adapter today and that works out of the box. At this point we will likely purchase new dongles as we are in a crunch to get these laptops out. I am willing to try any suggestions as long as we have the laptops in the shop.
Do I set my log level in the “Host Kernel Arguments?”
Wayne Workman last edited by
I remember seeing a post a while ago where there was no display, but the FOS engine was still working fine. I’m not saying that is the case here, but I would be interesting to know.
If kernel log level is set to zero, nothing will display.
ipxe.efi would be in /tftpboot. This image is the iPXE boot kernel.
The FOS engine files (bzImage/inits) are in /var/www/html/fog/service/ipxe
In your case, have you disabled secure boot?
I would also update the 1.3.0-rc1 (or shortly rc2) and then try again. I know there is a discrepancy between svn versions and git versions. I just want to make sure you are on the latest release before trying to debug this too far. Also make sure you have the latest firmware on these lenovos.
Just one comment, make sure that the lenovo is actually frozen and not running with no display. Try to watch for the IP address issued by dhcp to the target computer and then give it about 1 minute then try to ping the target from a second computer. I remember seeing a post a while ago where there was no display, but the FOS engine was still working fine. I’m not saying that is the case here, but I would be interesting to know.