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

[BlueTower]

Porteus 5 (Porteus-LXDE-v5.0-x86_64.iso) does not start up on my HP EliteBook 840 Aero G8. I have setup the USB stick according to [Solved] Security Boot Fail (with Porteus 5 ISO, instead of Porteus 4 ISO) and when I select the grub entry for Porteus, the laptop just shows an empty dark screen.

It does not seem to be secure boot problem - if it was secure boot problem, grub would not even try to load Porteus 5 and would report an error. Furthermore, SLAX 15.0.0 which is also based on Slackware 15 boots up correctly.

I suspect that a display driver is missing in Porteus 5 - does Porteus 5 support Intel(R) Iris(R) Xe Graphics (that's what Windows report as display adapter)? If no, any recommendation how to add it? Thanks.

PS: the home page of Porteus still indicates "PORTEUS V>>4<<.0 RELEASED". Shouldn't this be changed to "PORTEUS V>>5<<.0 RELEASED"?

[Ed_P]

PS: the home page of Porteus still indicates "PORTEUS V>>4<<.0 RELEASED". Shouldn't this be changed to "PORTEUS V>>5<<.0 RELEASED"?

Not sure what URL you are using to access the home page but https://forum.porteus.org/ shows !!! Porteus v5.0 is released !!! on my browsers.

when I select the grub entry

Please post your grub entry.

does Porteus 5 support Intel(R) Iris(R) Xe Graphics

Porteus 5.0 supports my Dell notebook and Windows shows it has an Intel(R) Iris(R) Xe Graphics driver.

[BlueTower]

Please post your grub entry.

My grub.cfg contains the following entry:
--------------
menuentry "Porteus-LXDE-v5.0-x86_64" {
set gfxpayload=keep
linux /porteus/Porteus-LXDE-v5.0-x86_64-vmlinuz from=/porteus/Porteus-LXDE-v5.0-x86_64.iso noauto debug ---
initrd /porteus/Porteus-LXDE-v5.0-x86_64-initrd.xz
}
--------------

I tried the above also with "set gfxpayload=text" and without "set gfxpayload=keep" line, but the result is the same - black screen.

Porteus-LXDE-v5.0-x86_64.iso, Porteus-LXDE-v5.0-x86_64-vmlinuz (vmlinuz extracted from Porteus-LXDE-v5.0-x86_64.iso) and Porteus-LXDE-v5.0-x86_64-initrd.xz (initrd.xz extracted from Porteus-LXDE-v5.0-x86_64.iso) are all stored in the /porteus directory on the USB flash drive used for booting.

Porteus 5.0 supports my Dell notebook and Windows shows it has an Intel(R) Iris(R) Xe Graphics driver.

Thanks. So the problem must be somewhere else.

[Ed_P]

Your setup looks strange. Why didn't you simply copy all the ISO files to the USB drive? No renaming necessary. And are you using grub or grub2?

These are the grub2 menus for my USB drive.

Code: Select all

menuentry " Porteus 5.0 USB - AF'" --class slackware   --class icon-porteus  {

     set porteus_parms="volume=33 reboot=cold extramod=/Modules"  #;cinnamon" # changes=EXIT:/changes/porteussave.dat"

     set bootdrv=$root
     search -f /boot/syslinux/vmlinuz --set=root
     if [ $root != $bootdrv ]; then
        linux  /boot/syslinux/vmlinuz $porteus_parms
        initrd /boot/syslinux/initrd.xz
     else
        echo "----------------------------------------"
        echo USB drive NOT found.
        echo
        sleep -v -i 10
     fi
     set root=$bootdrv
     }

menuentry " Porteus 5.0 USB - EFI" --class slackware   --class icon-porteus  {

     set bootmgr=/EFI/boot/bootx64.efi          #grubx64.efi    # bootx64.efi

     set bootdrv=$root
     search -f $bootmgr --set=root
     echo bootmgr: $bookmgr
     sleep -v -i 3
     if [ $root != $bootdrv ]; then
        chainloader $bootmgr
     else
        echo "----------------------------------------"
        echo USB drive NOT found.
        echo
        sleep -v -i 10
     fi
     set root=$bootdrv
     }

[BlueTower]

I copied all the files from Porteus-LXDE-v5.0-x86_64.iso to / of the USB drive.

The USB drive uses grub from ubuntu-18.04.1-live-server-amd64.iso. Boot screen indicates "GNU GRUB version 2.02"

When " Porteus 5.0 USB - EFI" is selected it returns:
====================================================
bootmgr:
0 -----------------------------------
USB drive NOT found

<number>
====================================================

When " Porteus 5.0 USB - AF'" is selected, it returns:
====================================================
-----------------------------------
USB drive NOT found.

<number>
====================================================


I use the drive to boot Lubuntu, Slax 13 (Debian based) and Slax 15 (Slackware based) and all boot correctly.

echo bootmgr: $bookmgr

Shouldn't the above be the following?

echo bootmgr: $bootmgr

[Ed_P]

When " Porteus 5.0 USB - EFI" is selected it returns:
====================================================
bootmgr:
0 -----------------------------------
USB drive NOT found

That's because you didn't put Porteus's EFI folder in your USB drive's EFI folder. What's your USB's EFI folder look like?

When " Porteus 5.0 USB - AF'" is selected, it returns:
====================================================
-----------------------------------
USB drive NOT found.

That's because the Porteus ISO root folders are not on the root of your USB drive. What are your USB's root folders?

[kultex]

I jump on this thread instead of making a new one.

@BlueTower its very hard to tell, when you are using an existing usb stick - if you have any free stick use usbimager, etcher or rufus linux or windows - then its much easier to tell, where is the problem

And regarding to the thread "support for Intel Iris Graphics" / generally it supports Intel Iris Graphics with the modesetting or fbdev driver, but this is something like luck or no luck. I have had the same acer laptop, just some month difference in selling - one booted fine with fbdev or modesetting the other one to black screen.

normally the Xorg.0.log should have those lines with the intel driver.

Code: Select all

[    26.368] (II) LoadModule: "intel"
[    26.370] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[    26.470] (II) Module intel: vendor="X.Org Foundation"
[    26.470] 	compiled for 1.20.9, module version = 2.99.917
[    26.470] 	Module class: X.Org Video Driver
[    26.470] 	ABI class: X.Org Video Driver, version 24.1
[    26.471] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
	i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
	915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
	Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
	GM45, 4 Series, G45/G43, Q45/Q43, G41, B43

and here is the Xorg.0.log from Porteus

Code: Select all

[     9.399] (II) LoadModule: "modesetting"
[     9.399] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
[     9.443] (II) Module modesetting: vendor="X.Org Foundation"
[     9.443] 	compiled for 1.20.14, module version = 1.20.14
[     9.443] 	Module class: X.Org Video Driver
[     9.443] 	ABI class: X.Org Video Driver, version 24.1
[     9.443] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[     9.443] (++) using VT number 7

[     9.450] (II) modeset(0): using drv /dev/dri/card0
[     9.450] (WW) Falling back to old probe method for modesetting

in /usr/lib64/xorg/modules/drivers/ I find the intel_drv.so, but I have no idea until no, how to load - normally it works to make this text file

/etc/X11/xorg.conf.d/20-intel.conf

with this content:

Code: Select all

Section "Device"   
   Identifier  "Intel Graphics"
   Driver      "intel"
#  Option      "AccelMethod" "uxa"  #could also use the default "sna"
   Option      "TearFree"     "true"
EndSection

any cheatcode to load the driver?

[kultex]

ok - solved


you have to create the 20-intel.conf in /etc/X11/xorg.conf.d

and the delete following files in /etc/X11

xorg.conf
xorg.conf-modesetting
xorg.conf-vesa

and then reboot

and for developers - those files must be deleted in the iso - thez are absolutley unnecessary

[Ed_P]

Shouldn't the above be the following?

echo bootmgr: $bootmgr

Yes. Thank you. The menu boots regardless so I've never caught it.

ok - solved

Excellent.

and the delete following files in /etc/X11

xorg.conf
xorg.conf-modesetting
xorg.conf-vesa

I don't have xorg.conf in my /etc/X11 folder.

Code: Select all

guest@porteus:~$ ls -l /etc/X11
total 3
-rw-r--r-- 1 root root  22 Apr  5  2020 Xwrapper.config
drwxr-xr-x 2 root root 257 Jul 23 05:24 app-defaults/
drwxr-xr-x 2 root root  62 May 11 08:46 xinit/
drwxr-xr-x 8 root root 114 Oct  6  2021 xkb/
-rw-r--r-- 1 root root 715 Feb 23  2020 xorg.conf-modesetting
-rw-r--r-- 1 root root 708 Feb 23  2020 xorg.conf-vesa
drwxr-xr-x 2 root root   3 Jul 12 16:36 xorg.conf.d/
guest@porteus:~$ 

Did you mean xorg.conf.d?

How would one make a module that deletes files?

[kultex]

@Ed_P
I have no idea, where those conf files come from - they are definitly unnecessary.

thats Xorg.0.log without any of those files

Code: Select all

     7.524] (==) Matched modesetting as autoconfigured driver 0
[     7.524] (==) Matched fbdev as autoconfigured driver 1
[     7.524] (==) Matched vesa as autoconfigured driver 2
[     7.524] (==) Assigned the driver to the xf86ConfigLayout
[     7.524] (II) LoadModule: "modesetting"
[     7.524] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
[     7.544] (II) Module modesetting: vendor="X.Org Foundation"
[     7.544] 	compiled for 1.20.14, module version = 1.20.14
[     7.544] 	Module class: X.Org Video Driver
[     7.544] 	ABI class: X.Org Video Driver, version 24.1
[     7.544] (II) LoadModule: "fbdev"
[     7.545] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so
[     7.551] (II) Module fbdev: vendor="X.Org Foundation"
[     7.551] 	compiled for 1.20.0, module version = 0.5.0
[     7.551] 	Module class: X.Org Video Driver
[     7.551] 	ABI class: X.Org Video Driver, version 24.0
[     7.551] (II) LoadModule: "vesa"
[     7.551] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
[     7.556] (II) Module vesa: vendor="X.Org Foundation"
[     7.556] 	compiled for 1.20.10, module version = 2.5.0
[     7.556] 	Module class: X.Org Video Driver
[     7.556] 	ABI class: X.Org Video Driver, version 24.1
[     7.556] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[     7.556] (II) FBDEV: driver for framebuffer: fbdev
[     7.556] (II) VESA: driver for VESA chipsets: vesa
[     7.556] (++) using VT number 7

[     7.579] (II) modeset(0): using drv /dev/dri/card0
[     7.579] (WW) Falling back to old probe method for fbdev
[     7.579] (II) Loading sub module "fbdevhw"
[     7.579] (II) LoadModule: "fbdevhw"
[     7.580] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
[     7.597] (II) Module fbdevhw: vendor="X.Org Foundation"
[     7.597] 	compiled for 1.20.14, module version = 0.0.2
[     7.597] 	ABI class: X.Org Video Driver, version 24.1
[     7.597] (II) modeset(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[     7.597] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
[     7.597] (==) modeset(0): RGB weight 888
[     7.597] (==) modeset(0): Default visual is TrueColor
[     7.597] (II) Loading sub module "glamoregl"
[     7.597] (II) LoadModule: "glamoregl"
[     7.597] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
[     7.642] (II) Module glamoregl: vendor="X.Org Foundation"
[     7.642] 	compiled for 1.20.14, module version = 1.0.1
[     7.642] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    10.543] (II) modeset(0): glamor X acceleration enabled on Mesa Intel(R) HD Graphics 620 (KBL GT2)
[    10.543] (II) modeset(0): glamor initialized
[    10.544] (II) modeset(0): Output eDP-1 has no monitor section
[    10.545] (II) modeset(0): Output DP-1 has no monitor section
[    10.548] (II) modeset(0): Output HDMI-1 has no monitor section
[    10.548] (II) modeset(0): Output DP-2 has no monitor section
[    10.559] (II) modeset(0): EDID for output eDP-1
[    10.559] (II) modeset(0): Manufacturer: LGD  Model: 577  Serial#: 0
[    10.559] (II) modeset(0):

so xorg decides best, which driver it will take - you are less at risk to boot to a black screen

[kultex]

here my previous /etc/X11 folder.

Code: Select all

guest@porteus:~$ ls -l /etc/X11
total 17
-rw-r--r-- 1 root root   22 Apr  5  2020 Xwrapper.config
drwxr-xr-x 2 root root  257 Jun 30 07:11 app-defaults/
drwxr-xr-x 2 root root   50 Jan 15  2022 xinit/
drwxr-xr-x 8 root root  114 Oct  6  2021 xkb/
-rw-r--r-- 1 root root  715 Feb 23  2020 xorg.conf-modesetting
-rw-r--r-- 1 root root  708 Feb 23  2020 xorg.conf-vesa
drwxr-xr-x 2 root root 4096 Aug 21 05:53 xorg.conf.d/
-rw-r--r-- 1 root root  715 Feb 23  2020 xorg.conf

EDIT: - I booted in Always Fresh mode and you are correct - there is no xorg.conf - it is the same file as xorg.conf-modesetting, so I must have produced it by myself?????

[kultex]

I had the problem, that after 2nd reboot, I had a very strange resolution with the intel driver (720x405) - ok it would be possible to change with ARandR after each boot, so easier it is to create a .xprofile file in the /home directory with the correct resolution - ARandR gives you the possibilities - in my case

Code: Select all

xrandr --output eDP-1 --mode 1920x1080 --rate 60

[kultex]

@BlueTower

try this grub entry - this is working for me (How to create a porteus 5.0 hybrid usb drive?) - but I dont know, if it finds the modules, which are in /Porteus - unril now, very limited knowledge about Grub2

Code: Select all

menuentry "Porteus-LXDE-v5.0-x86_64" {
set gfxpayload=keep
linux /porteus/Porteus-LXDE-v5.0-x86_64-vmlinuz from=/porteus/Porteus-LXDE-v5.0-x86_64.iso nomagic base_only norootcopy
initrd /porteus/Porteus-LXDE-v5.0-x86_64-initrd.xz
}

[BlueTower]

Hello Ed_P and kultex,

first of all, sorry for responding so late - I was busy with something else.

@Ed_P:

you were right - I used incorrect EFI directory (EFI directory from ubuntu-18.04.1-live-server-amd64.iso, instead EFI directory from Porteus-LXDE-v5.0-x86_64.iso).

However, when I removed EFI and boot of ubuntu-18.04.1-desktop-amd64.iso from root of the USB stick and instead copied EFI, boot, porteus from Porteus-LXDE-v5.0-x86_64.iso to the root of the USB stick, and tried to boot from the USB stick, my notebook states "Selected boot image did not authenticate. Please enter to attempt to boot to next device". My notebook has secure boot enabled and I am unable to disable it.

In the mean time, my notebook stops accepting EFI from ubuntu-18.04.1-live-server-amd64.iso (which also starts resulting into "Selected boot image did not authenticate. Please enter to attempt to boot to next device") but accepts EFI from ubuntu-18.04.6-live-server-amd64.iso.

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
}

My notebook now boots grub without any error but when selecting the entry "Porteus-LXDE-v5.0-x86_64" in grub, grub states:

error: /vmlinuz has invalid signature.
error: you need to load the kernel first.

Press any key to continue

From the above, my conclusion is the solution as in [Solved] Security Boot Fail no longer works (at least on my notebook).

@kultex: I think I was on wrong track from beginning. The problem is not caused by missing display driver but by secure boot.

[Ed_P]

error: /vmlinuz has invalid signature.

Can the vmlinuz from Porteus 4.0 be used?

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

From the above, my conclusion is the solution as in [Solved] Security Boot Fail no longer works (at least on my notebook).

Bummer.

Added in 10 minutes 46 seconds:
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.

Code: Select all

search -f /boot/syslinux/vmlinuz --set=root