You are not logged in.

#1 2020-06-11 19:38:09

chetwisniewski
Member
Registered: 2012-03-04
Posts: 30

Kernel 5.7.2 "Error: Invalid parameter returned from vmliuz-linux"

After updating my laptop this morning it became unbootable with the error:

"Error: Invalid Parameter returned from vmlinuz-linux"

Downgrading to kernel 5.6.7 allowed me to boot again.

Kernel boot parameters:

"luks.name=bd29508c-295e-4282-b327-378b31bab56a=root luks.name=890f2eea-a499-41e3-86f7-80a109d762ac=cryptswap root=/dev/mapper/root initrd=/intel-ucode.img initrd=/initramfs-linux.img resume=/dev/mapper/cryptswap intel_iommu=on enable_guc=2 enable_psr=1 enable_fbc=0 disable_power_well=0 fastboot=1 rw"


Tried removing unnecessary parameters to no avail.

Chester

Offline

#2 2020-06-11 20:45:51

loqs
Member
Registered: 2014-03-06
Posts: 11,694

Re: Kernel 5.7.2 "Error: Invalid parameter returned from vmliuz-linux"

Offline

#3 2020-06-11 21:10:26

mcloaked
Member
From: Yorkshire, UK
Registered: 2012-02-02
Posts: 906

Re: Kernel 5.7.2 "Error: Invalid parameter returned from vmliuz-linux"

Also if the initrd is in a sub directory then backslashes are needed as in https://bbs.archlinux.org/viewtopic.php?id=256498


Mike C

Offline

#4 2020-06-11 22:16:16

chetwisniewski
Member
Registered: 2012-03-04
Posts: 30

Re: Kernel 5.7.2 "Error: Invalid parameter returned from vmliuz-linux"

Converting slashes to backslashes solved it. This is likely to come up for a LOT of people,

Offline

#5 2020-06-12 06:32:39

EdeWolf
Member
Registered: 2016-01-06
Posts: 51

Re: Kernel 5.7.2 "Error: Invalid parameter returned from vmliuz-linux"

Here as well, with backslash the system boots again. Thanks all!

Offline

#6 2020-06-12 09:27:33

mcloaked
Member
From: Yorkshire, UK
Registered: 2012-02-02
Posts: 906

Re: Kernel 5.7.2 "Error: Invalid parameter returned from vmliuz-linux"

Also somewhat of concern is the commit at https://github.com/torvalds/linux/commi … 0bd047f0f5 where it says: "Loading an initrd passed via the kernel command line is deprecated: it
is limited to files that reside in the same volume as the one the kernel itself was loaded from, and we have more flexible ways to achieve the same. So make it configurable so new architectures can decide not to enable it."  So if anyone has the initrd file on a different volume to where the kernel is then booting presumably will become impossible, particularly if an additional initrd microcode file is included as a kernel parameter.

So the question then is will there come a time when loading from an initrd kernel parameter in the arch linux kernel will not be switched on, and if so, how would arch refind users be able to boot the kernel at all?  Will this impact other bootloaders also? I don't know if this has already been though of but it would be very re-assuring to know what is being planned so that our machines will continue to boot.

I understand that arch users who use dracut instead of mkiniticpio can avoid this issue, in contrast to me where I have to have two initrd parameters with one for the microcode file, because in dracut the microcode file is  is part of the boot initrd.


Mike C

Offline

#7 2020-06-13 11:51:30

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 8,371

Re: Kernel 5.7.2 "Error: Invalid parameter returned from vmliuz-linux"

Good quesion, I'd like to know more also.

One small part I can answer ,

Will this impact other bootloaders also?

The mentioned commits all deal with initrd , commandline & EFI boot, so all bootloaders that support EFI could potentially be affected.
The archlinux microcode wiki page EFISTUB and rEFInd entries both use \ now, so that makes two affected bootloaders.

Last edited by Lone_Wolf (2020-06-13 11:51:46)


Multi-init booting with apg Openrc and systemd coexisting
Automounting : not needed, i prefer pmount
Aur helpers : makepkg + my own local repo === rarely need them

Offline

Board footer

Powered by FluxBB