Support for Intel(R) Iris(R) Xe Graphics?

Please reproduce your error on a second machine before posting, and check the error by running without saved changes or extra modules (See FAQ No. 13, "How to report a bug"). For unstable Porteus versions (alpha, beta, rc) please use the relevant thread in our "Development" section.
BlueTower
White ninja
White ninja
Posts: 8
Joined: 21 Nov 2018, 10:21
Distribution: Porteus 4

Support for Intel(R) Iris(R) Xe Graphics?

Post#16 by BlueTower » 29 Aug 2022, 16:07

regarding:
How do you know your grub menu is accessing the vmlinuz in the Porteus boot directory? I don't see root being set to it's drive.
I set up the USB disk so that Porteus' vmlinuz and Porteus' initrd.xz are in the root of the USB disk. See my previous comment.

regarding:
Can the vmlinuz from Porteus 4.0 be used?
Unfortunately, the same result.

regarding:
And how does one get the file's signature validated?


For Debian, there is some info at: https://wiki.debian.org/SecureBoot.

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Support for Intel(R) Iris(R) Xe Graphics?

Post#17 by Ed_P » 29 Aug 2022, 17:05

BlueTower wrote:
29 Aug 2022, 16:07
I set up the USB disk so that Porteus' vmlinuz and Porteus' initrd.xz are in the root of the USB disk.
The location's folder name is not the same as grub's address for it. :)

To verify what root is pointing to add this code to your menu.

Code: Select all

menuentry "Porteus-LXDE-v5.0-x86_64" {
	set gfxpayload=text
	echo "b4: " $root
	search -f /boot/syslinux/vmlinuz --set=root
	echo "aft: " $root
	sleep 4
	linux	/boot/syslinux/vmlinuz nomagic base_only norootcopy 3
	initrd	/boot/syslinux//initrd.xz
}
Ed

BlueTower
White ninja
White ninja
Posts: 8
Joined: 21 Nov 2018, 10:21
Distribution: Porteus 4

Support for Intel(R) Iris(R) Xe Graphics?

Post#18 by BlueTower » 29 Aug 2022, 17:44

I put the USB stick back to state described in #14.
I added additional menuentry as above in #17, except that I changed menuentry name to "Porteus-LXDE-v5.0-x86_64 (2)".
Grub boots OKs.
When selecting the new menu entry "Porteus-LXDE-v5.0-x86_64 (2)", the result is the following:
b4: hd0,msdos1
error: Secure Boot forbids loading module from (hd0,msdos1)/boot/grub/x86_64-efi/ufs2.mod.
error: Secure Boot forbids loading module from (hd0,msdos1)/boot/grub/x86_64-efi/ufs1_be.mod.
error: Secure Boot forbids loading module from (hd0,msdos1)/boot/grub/x86_64-efi/ufs1.mod.
error: Secure Boot forbids loading module from (hd0,msdos1)/boot/grub/x86_64-efi/udf.mod.
error: Secure Boot forbids loading module from (hd0,msdos1)/boot/grub/x86_64-efi/tar.mod.
error: Secure Boot forbids loading module from (hd0,msdos1)/boot/grub/x86_64-efi/sfs.mod.
error: Secure Boot forbids loading module from (hd0,msdos1)/boot/grub/x86_64-efi/romfs.mod.
error: Secure Boot forbids loading module from (hd0,msdos1)/boot/grub/x86_64-efi/reiserfs.mod.
error: Secure Boot forbids loading module from (hd0,msdos1)/boot/grub/x86_64-efi/procfs.mod.
error: Secure Boot forbids loading module from (hd0,msdos1)/boot/grub/x86_64-efi/odc.mod.
error: Secure Boot forbids loading module from (hd0,msdos1)/boot/grub/x86_64-efi/nilfs2.mod.
error: Secure Boot forbids loading module from (hd0,msdos1)/boot/grub/x86_64-efi/newc.mod.
error: Secure Boot forbids loading module from (hd0,msdos1)/boot/grub/x86_64-efi/minix_be.mod.
error: Secure Boot forbids loading module from (hd0,msdos1)/boot/grub/x86_64-efi/minix3_be.mod.
error: Secure Boot forbids loading module from (hd0,msdos1)/boot/grub/x86_64-efi/minix3.mod.
error: Secure Boot forbids loading module from (hd0,msdos1)/boot/grub/x86_64-efi/minix2_be.mod.
error: Secure Boot forbids loading module from (hd0,msdos1)/boot/grub/x86_64-efi/minix2.mod.
error: Secure Boot forbids loading module from (hd0,msdos1)/boot/grub/x86_64-efi/minix.mod.
error: Secure Boot forbids loading module from (hd0,msdos1)/boot/grub/x86_64-efi/jfs.mod.
error: Secure Boot forbids loading module from (hd0,msdos1)/boot/grub/x86_64-efi/hfs.mod.
error: Secure Boot forbids loading module from (hd0,msdos1)/boot/grub/x86_64-efi/f2fs.mod.
error: Secure Boot forbids loading module from (hd0,msdos1)/boot/grub/x86_64-efi/exfat.mod.
error: Secure Boot forbids loading module from (hd0,msdos1)/boot/grub/x86_64-efi/cpio_be.mod.
error: Secure Boot forbids loading module from (hd0,msdos1)/boot/grub/x86_64-efi/cpio.mod.
error: Secure Boot forbids loading module from (hd0,msdos1)/boot/grub/x86_64-efi/cbfs.mod.
error: Secure Boot forbids loading module from (hd0,msdos1)/boot/grub/x86_64-efi/bfs.mod.
error: Secure Boot forbids loading module from (hd0,msdos1)/boot/grub/x86_64-efi/afs.mod.
error: Secure Boot forbids loading module from (hd0,msdos1)/boot/grub/x86_64-efi/affs.mod.
error: no such device: /boot/syslinux/vmlinuz.
aft: hd0,msdos1
error: file '/boot/syslinux/vmlinuz' not found.
error: you need to load the kernel first.

Press any key to continue...
I took a photo of the boot screen and wrote the text above based on the photo, so there might be some spelling errors.

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Support for Intel(R) Iris(R) Xe Graphics?

Post#19 by Ed_P » 29 Aug 2022, 18:12

BlueTower wrote:
29 Aug 2022, 17:44
I took a photo of the boot screen and wrote the text above based on the photo
That's a lot of typing BlueTower. :lol:

I don't understand how your USB drive doesn't have a /boot folder from Porteus.
Ed

BlueTower
White ninja
White ninja
Posts: 8
Joined: 21 Nov 2018, 10:21
Distribution: Porteus 4

Support for Intel(R) Iris(R) Xe Graphics?

Post#20 by BlueTower » 29 Aug 2022, 18:21

regarding:
I don't understand how your USB drive doesn't have a /boot folder from Porteus.
In #14, I said that /boot (and /EFI as well) is from ubuntu-18.04.6-live-server-amd64.iso (to make sure that notebook boots grub without "Selected boot image did not authenticate. Please enter to attempt to boot to next device"):
So, I set up the USB stick from scratch again:
- /porteus contains /porteus from Porteus-LXDE-v5.0-x86_64.iso
- /vmlinuz contains /boot/syslinux/vmlinuz from Porteus-LXDE-v5.0-x86_64.iso
- /initrd.xz contains /boot/syslinux/initrd.xz from Porteus-LXDE-v5.0-x86_64.iso
- /EFI contains /EFI from from ubuntu-18.04.6-live-server-amd64.iso
- /boot contains /boot from from ubuntu-18.04.6-live-server-amd64.iso except /boot/grub/grub.cfg which contains:

Code: Select all

if loadfont /boot/grub/font.pf2 ; then
	set gfxmode=auto
	insmod efi_gop
	insmod efi_uga
	insmod gfxterm
	terminal_output gfxterm
fi

set menu_color_normal=white/black
set menu_color_highlight=black/light-gray

set timeout=5

menuentry "Porteus-LXDE-v5.0-x86_64" {
	set gfxpayload=text
	linux	/vmlinuz nomagic base_only norootcopy 3
	initrd	/initrd.xz
}
I.e. from Porteus-LXDE-v5.0-x86_64.iso, I took only:
- /boot/syslinux/vmlinuz which is in USB stick placed as /vmlinuz (i.e. single file in /)
- /boot/syslinux/initrd.xz which is in USB stick placed as /initrd.xz (i.e. single file in /)
- /porteus which is in USB stick placed as /porteus (i.e. directory in /)

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Support for Intel(R) Iris(R) Xe Graphics?

Post#21 by Ed_P » 05 Sep 2022, 17:32

My errors are similar to yours with my Porteus 5.0 USB drive, ubuntu-22.04.1-desktop-amd64.iso and my Dell notebook when I try to boot with Secure Boot enabled. :(

Code: Select all

 :
 :
error: Secure Boot forbids loading module from (hd0,msdos1)/boot/grub/x86_64-efi/afs.mod.
error: Secure Boot forbids loading module from (hd0,msdos1)/boot/grub/x86_64-efi/affs.mod.
 hd0,msdos1error: bad shim signature
error: you need to load the kernel first.
I noticed there is an EFI Secure Boot option for validating files which is set On on the Dell's boot menu which may be causing the problem but turning it off defeats the purpose of using the Ubuntu boot files.

When copying the Ubuntu boot files to the USB drive there was an error about Owner not being copied. Whether that's the cause of the problem I don't know at this point. And if it is I don't know how to fix it. :(

My grub.cfg file for Porteus 5.0 is basically the same as the one I posted here: [Solved] Security Boot Fail :)
Ed

beny
Full of knowledge
Full of knowledge
Posts: 2086
Joined: 02 Jan 2011, 11:33
Location: italy

Support for Intel(R) Iris(R) Xe Graphics?

Post#22 by beny » 05 Sep 2022, 18:07


User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Support for Intel(R) Iris(R) Xe Graphics?

Post#23 by Ed_P » 05 Sep 2022, 18:48

Interesting links beny. Thanks. :friends:
Ed

beny
Full of knowledge
Full of knowledge
Posts: 2086
Joined: 02 Jan 2011, 11:33
Location: italy

Support for Intel(R) Iris(R) Xe Graphics?

Post#24 by beny » 05 Sep 2022, 20:48


User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Support for Intel(R) Iris(R) Xe Graphics?

Post#25 by Ed_P » 05 Sep 2022, 21:27

Now I'm getting confused. :ROFL:

Added in 1 day 8 hours 38 minutes 16 seconds:
It seems mokutil requires each user to manage secure boot keys, unique to his machine. The user has very complex and abstract tasks to perform and on a machine he can't boot Porteus on due to Secure Boot being enabled makes the task impossible. Ubuntu boots on machines with or without Secure Boot enabled.
Ed

beny
Full of knowledge
Full of knowledge
Posts: 2086
Joined: 02 Jan 2011, 11:33
Location: italy

Support for Intel(R) Iris(R) Xe Graphics?

Post#26 by beny » 07 Sep 2022, 16:02

hi Ed_P the mokutil i think you don't have to use it try first the shim keys with grub and report if work for you

User avatar
AcnapyxoB
Samurai
Samurai
Posts: 191
Joined: 24 Dec 2014, 10:15
Distribution: Porteus 5.01
Location: Planet Earth

Support for Intel(R) Iris(R) Xe Graphics?

Post#27 by AcnapyxoB » 08 Jan 2023, 08:31

Ed_P wrote:
05 Sep 2022, 17:32
My errors are similar to yours with my Porteus 5.0 USB drive, ubuntu-22.04.1-desktop-amd64.iso and my Dell notebook when I try to boot with Secure Boot enabled.
Is there any movement on the topic ?
For me everything worked perfectly (with EFI/boot from ubuntu-18.04.1 Ed_P solution) until last Windows 10 update!
Porteus v5.01 KDE x86_64

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Support for Intel(R) Iris(R) Xe Graphics?

Post#28 by Ed_P » 09 Jan 2023, 06:05

I've haven't done anything with it.
Ed

Post Reply