Has anyone else noticed this problem ?

The current usbboot.img (dated Jan 17, 2021), in slackware64-current boots OK to do an install, etc...

However, this command line is not booting the existing HDD install but rather boots the USB stick just as if that command line was not tried.

boot: huge.s root=/dev/sda1 rdinit= ro

usbboot.img in slackware64-14.2 (dated Jun 24, 2016), works perfectly with that command line.

Same result with both 'dd' to copy the image to the USB stick or with usbimg2disk.sh

Yes, I've noticed it today with the Jan 20th usbboot.img. It is odd that root can no longer be booted by that command.

OK, it's not just me.

There does not seem to be an email address 'published' for contacting Patrick.
(which is understandable 'cus he'd be getting a million emails a day) ;-)

Does anyone know how we can notify him of this 'bug' ?

Don't worry he will see this thread.

1 members found this post helpful.

Forgot to mention.... There is a secondary less severe problem which exists with both the USB boot and with the install DVD boot.

Even though the hardware clock is set to the correct date/time...
when the machine is booted to either the install USB or the install DVD
(without the aforementioned command line for booting the existing system),
the date/time is set to exactly 24hrs in the past.

Booting the v14.2 USB stick or the v14.2 install DVD _with_ the aforementioned command line and
now being in the existing system... the date/time are correct as were set in the hardware clock.

And of-course, when booting to the existing system on HDD the date/time are correct.

Well... it ain't fixed yet... problem still persists with today's usbboot.img

/slackware64-current/usb-and-pxe-installers/usbboot.img 27-Jan-2021 20:42 57M

Hi,

I think your issue is related to these:
1. https://www.linuxquestions.org/quest...so-4175687793/
2. https://www.linuxquestions.org/quest...-a-4175687446/

The solution suggested by @gus3 works perfectly:

For instance, for sda1 it would be:

This behavior was introduced with Kernel 5.10.x.

1 members found this post helpful.

In my case, last week I tried to boot my laptop using usbboot.img but it doesn't boot at all. So I created a full slackware iso, then isohybrid it. It worked fine.

Ah ha.... that works perfectly.

Thank You !!!

Sooooo.... the only thing that needs to be changed is the screen message needs to be changed from 'rdinit=' to 'initrd='

boot: huge.s root=/dev/sda1 initrd= ro
____________________________^^^^^^^___

Thanks again

This thread has a working solution (even if I had to adapt it):
https://www.linuxquestions.org/quest...re-4175671086/

Instead you should use the slightly different commandline which is used in -current:

2 members found this post helpful.