TeraByte Unlimited

December 14, 2023

A new version of the x64 Linux Boot Disk has been released that removes DRM and Framebuffer chipset specific support.


------------------------------ ----------------------Original Message ------------------------------------------------------------
If you experience a hang with UDEV booting 3.63 please try using the following kernel parameter:

blklst1=nvidiafb

For syslinux, you enter the menu choice plus that:

2 blklst1=nvidiafb

for grub, use "e" to edit and add to the end of the linux line:

example:

linux /vmlinuz uefimode=yes switchx=yes iflkmap=us ktl=qwerty iflbflag=3 blklst1=nvidiafb

Note the extra spaces after iflbflag - those need to stay in place.

If it's an older system, you can probably use the 686 version instead of the x64 version as well.

For what it's worth, you have other kernel parameter options for diagnosing issues:

udevstart=0 prevents launching udev
udevdebug=both|udev|trigger
udevsettle=n where n is seconds

My 4 year old computer has this issue. "Waiting for udev to complete...."
I don't have Nvidia hardware.
IFL 686 doesn't boot. Needs 64-bit UEFI.
I tried the above suggestions without success.

My 2 year old computer is fine with IFL 3.63.

Same issue as Brian: "Waiting for udev to complete...." with no Nvidia hardware.

Intel Core i5-1240P (Alder Lake-H/P, L0)
Intel Iris Xe Graphics (Alder Lake-P 682 GT2) - Integrated Graphics Controller

To test if it's the framebuffer chipset items, boot with "udevstart=0" (kernel parameter), then when at a command prompt (with a normal non-usb keyboard), mc /lib/modules

Go in the kernel folder, go to drivers, go to video, delete (f8) the fbdev directory. Then exit mc (f10), type "/etc/rc.d/udev start" at the command line and see if it still hangs.

I must have made a mistake yesterday. I use a USB mouse and keyboard.

udevstart=0

IFL loads into the GUI but the USB mouse and keyboard don't work.

I tried udevstart=0 then at a command prompt
mc /lib/modules

grub> error can't find "mc"

you have to use a normal keyboard, not usb. better yet, I can have you download a test if interested...

A new version of the x64 Linux Boot Disk has been released that removes DRM and Framebuffer chipset specific support.

I just tried the Nonet version. All OK. Thank you.

The new build has sorted the udev issue, however my system receives multiple Processing iflbflag=2, attempt:1 (optical disc) and (iso on *) messages, each time with a fail result on the (iso on HDD) then eventually boots to a CUI.

Edit: Ignore the CUI comment - I downloaded the wrong file! The iflbflag=2 messages persist however, slowing down the boot process. It does boot to a GUI eventually and is fully functional.

Those messages always existed as it searches for itself. How many show up? Anyway you can create a report "createreport" and send it to support to see if it shows something.