Stuck at bg.png / Issues with Lenovo X1 Carbon (6th gen) & Lenovo Onelink+ dock (RTL8135 USB)
-
@Shadow00Caster Just problem after problem… man.
You are most likely going to run into one that we can’t just throw out.
Can you please provide a photo of where it’s hanging now?
-
@Wayne-Workman
Image: http://i.imgur.com/ipu55xH.jpgOutput from boot.php in browser:
#!ipxe
set fog-ip 10.1.1.254
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
cpuid --ext 29 && set arch x86_64 || set arch i386
goto get_console
:console_set
colour --rgb 0x00567a 1 ||
colour --rgb 0x00567a 2 ||
colour --rgb 0x00567a 4 ||
cpair --foreground 7 --background 2 2 ||
goto MENU
:alt_console
cpair --background 0 1 ||
cpair --background 1 2 ||
goto MENU
:get_console
console --picture http://10.1.1.254/fog/service/ipxe/ --left 100 --right 80 && goto console_set || goto alt_console
:MENU
menu
colour --rgb 0xff0000 0 ||
cpair --foreground 1 1 ||
cpair --foreground 0 3 ||
cpair --foreground 4 4 ||
item --gap Host is NOT registered!
item --gap – -------------------------------------
item fog.local Boot from hard disk
item fog.memtest Run Memtest86+
item fog.reginput Perform Full Host Registration and Inventory
item fog.reg Quick Registration and Inventory
item fog.deployimage Deploy Image
item fog.multijoin Join Multicast Session
item fog.sysinfo Client System Information (Compatibility)
choose --default fog.local --timeout 5000 target && goto ${target}
:fog.local
sanboot --no-describe --drive 0x80 || goto MENU
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=10.1.1.254/fog/ consoleblank=0 rootfstype=ext4 loglevel=4
imgfetch init_32.xz
boot || goto MENU
:fog.memtest
kernel memdisk iso raw
initrd memtest.bin
boot || goto MENU
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=10.1.1.254/fog/ consoleblank=0 rootfstype=ext4 loglevel=4
imgfetch init_32.xz
boot || goto MENU
:fog.reginput
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=10.1.1.254/fog/ consoleblank=0 rootfstype=ext4 loglevel=4 mode=manreg
imgfetch init_32.xz
boot || goto MENU
:fog.reg
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=10.1.1.254/fog/ consoleblank=0 rootfstype=ext4 loglevel=4 mode=autoreg
imgfetch init_32.xz
boot || goto MENU
:fog.deployimage
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param qihost 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:fog.multijoin
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param sessionJoin 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:fog.sysinfo
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=10.1.1.254/fog/ consoleblank=0 rootfstype=ext4 loglevel=4 mode=sysinfo
imgfetch init_32.xz
boot || goto MENU
:bootme
chain -ar http://10.1.1.254/fog/service/ipxe/boot.php##params ||
goto MENU
autoboot -
@Shadow00Caster It’s dying while trying to download the kernel and init from the server.
I keep thinking this is some sort of memory issue on the device, I’ve been thinking that the whole time through this thread. Like it just can’t handle the files with this boot ROM you’re using.
I’d suggest trying other boot ROMs. You have it in BIOS mode, so you have a lot of solid ones to try. Basically you can try any file inside
/tftpboot
that doesn’t end with.efi
and isn’tdefault.ipxe
Just go through all of them, one by one. Make sure you completely turn off the device between each try. -
@Shadow00Caster Also please provide the output of this:
ls -lat /var/www/html/fog/service/ipxe
-
@Wayne-Workman said in Stuck at bg.png / Issues with Lenovo X1 Carbon (6th gen) & Lenovo Onelink+ dock (RTL8135 USB):
@Shadow00Caster It’s dying while trying to download the kernel and init from the server.
We had another poster a while ago with the same exact issue. During debugging we commented out the bg.png file and the issue moved to the next file that got downloaded. I can’t seem to find that in the forum yesterday on how we solved that issue. I was thinking that at that time the OP was using dnsmasq and somehow was pulling and old iPXE kernel.
-
From what I see in the picture it is not trying to load the kernel but still hanging on the image. As the setting was blanked in the web gui it just says
http://10.1.1.254/fog/service/ipxe/
without any filename in the end. So blanking the setting has not helped. As George said you can go ahead and edit PHP files to comment out thatconsole ...
line./var/www/html/fog/lib/fog/bootmenu.class.php
(line 873). -
@Sebastian-Roth @george1421
I commented out the line and was able to get to the boot menu, as soon as I hit perform full registration its just a black screen with bzImage… 0% at the bottom.@Wayne-Workman
I tried a few of the different ROMs, mostly to the same conclusion :/.
Output of ls:
root@fog:~# ls -lat /var/www/fog/service/ipxe/
total 48684
-rwxr-xr-x 1 fog www-data 6995328 Aug 2 13:56 bzImage32
-rwxr-xr-x 1 fog www-data 7097776 Aug 2 13:56 bzImage
-rw-r–r-- 1 fog www-data 16501540 Aug 2 13:56 init_32.xz
-rw-r–r-- 1 fog www-data 18507592 Aug 2 13:56 init.xz
-rw-r–r-- 1 fog www-data 1221 Aug 2 13:55 advanced.php
-rw-r–r-- 1 fog www-data 21280 Aug 2 13:55 bg.png
-rw-r–r-- 1 fog www-data 719 Aug 2 13:55 boot.php
-rw-r–r-- 1 fog www-data 234697 Aug 2 13:55 grub.exe
-rw-r–r-- 1 fog www-data 25340 Aug 2 13:55 memdisk
-rw-r–r-- 1 fog www-data 1839104 Aug 2 13:55 memtest.bin
-rw-r–r-- 1 fog www-data 20958 Aug 2 13:55 refind.conf
-rw-r–r-- 1 fog www-data 205192 Aug 2 13:55 refind.efi
drwxr-xr-x 3 fog www-data 4096 Aug 2 13:55 .
drwxr-xr-x 3 www-data www-data 4096 Aug 2 13:55 …
drwxr-xr-x 2 fog www-data 4096 Aug 2 13:55 oldAt this point I think I am just going to old school this thing since it’s the only instance of this particular machine and every other machine that I image regularly has no issues.
-
@Shadow00Caster That is what we saw in the other thread. The download issue just moved to the next item downloaded.
How many of these systems do you need to image? I have a way to boot the FOS engine via usb and bypass all of the iPXE logic.
-
Boy does this thread sound familiar
-
@Shadow00Caster You might want to try changing the device to UEFI and see if ipxe.efi works for you? But possibly it does not even netboot in UEFI mode?!?!
-
@Shadow00Caster Any news on this?