i915 didn't work after dist upgrade until linux-firmware was manually reinstalled

[s.illes79]

Few days ago upgraded from 23.10 to 24.04

After upgrade nvidia drivers broke I couldn't even log in. I fixed that by purging and reinstall.

Now I can only log in to XOrg, cannot to Wayland is just black screen.

gnome-shell is using 200-800 % cpu, when doing anything ... like opening gnome settings, using spottily

System temperature is very high because of this, laptop is hardly usable.

Everything was normal in 23.10.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gnome-shell 46.0-0ubuntu5.1
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue May 28 13:42:17 2024
DisplayManager: gdm3
InstallationDate: Installed on 2022-12-08 (537 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1)
RelatedPackageVersions: mutter-common 46.0-1ubuntu9
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to noble on 2024-05-22 (6 days ago)

[Daniel van Vugt (vanvugt)]

Please try uninstalling:

'<email address hidden>', 'freon@UshakovVasilii_Github.yahoo.com', '<email address hidden>', '<email address hidden>', '<email address hidden>'

Or more simply:

  cd ~/.local/share/gnome-shell/
  rm -rf extensions

and then log in again.

[Daniel van Vugt (vanvugt)]

Oh actually it sounds like the problem might be that hardware acceleration isn't working:

[ 35.899866] tuxedo org.gnome.Shell.desktop[3332]: error: Kernel is too old (4.16+ required) or unusable for Iris.
[ 35.899866] tuxedo org.gnome.Shell.desktop[3332]: Check your dmesg logs for loading failures.
[ 36.085749] tuxedo org.gnome.Shell.desktop[3332]: error: Kernel is too old (4.16+ required) or unusable for Iris.
[ 36.085749] tuxedo org.gnome.Shell.desktop[3332]: Check your dmesg logs for loading failures.
[ 36.085749] tuxedo org.gnome.Shell.desktop[3332]: libEGL warning: egl: failed to create dri2 screen
[ 36.088736] tuxedo org.gnome.Shell.desktop[3332]: error: Kernel is too old (4.16+ required) or unusable for Iris.
[ 36.088736] tuxedo org.gnome.Shell.desktop[3332]: Check your dmesg logs for loading failures.
[ 36.088736] tuxedo org.gnome.Shell.desktop[3332]: libEGL warning: egl: failed to create dri2 screen
[ 36.091930] tuxedo org.gnome.Shell.desktop[3332]: error: Kernel is too old (4.16+ required) or unusable for Iris.
[ 36.091930] tuxedo org.gnome.Shell.desktop[3332]: Check your dmesg logs for loading failures.
[ 36.091930] tuxedo org.gnome.Shell.desktop[3332]: libEGL warning: egl: failed to create dri2 screen

So either something went wrong with the dist upgrade or the Nvidia drivers (which are not present now) somehow broke the Intel drivers.

[Daniel van Vugt (vanvugt)]

Please run:

  journalctl -b0 > journal.txt

and attach the resulting file here.

[s.illes79 (s-illes79-gmail)]

tried intel, on-demand and nvidia prime mode. None works correct
Loads of firmware is missing. see nvidia.txt

[s.illes79 (s-illes79-gmail)]

Same issue reported here: https://askubuntu.com/questions/1514352/ubuntu-24-04-with-nvidia-driver-libegl-warning-egl-failed-to-create-dri2-scre

Looks like the solution/hack might be to copy drivers from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915

I noticed:
|W: Possible missing firmware /lib/firmware/i915/mtl_gsc_1.bin for module i915

ls -l /lib/firmware/i915/mtl_huc_gsc.bin*
-rw-r--r-- 1 root root 143249 Apr 10 00:14 /lib/firmware/i915/mtl_huc_gsc.bin.zst

files are there but zipped.

[s.illes79 (s-illes79-gmail)]

I can confirm that manually copying the i915 firmware
from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915
to /lib/firmware/i915

regenerate initramfs and reboot.

All normal.

So upgrade broke the 915 firmware package.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Juerg Haefliger (juergh)]

The firmwares are present so the problem is somewhere else. It looks like the firmwares are not pulled into the initrd, in fact initramfs-tools claims they're not there. Huh?

[Juerg Haefliger (juergh)]

> /depmod: WARNING: could not open modules.builtin.modinfo at /var/tmp/mkinitramfs_VLAT7G/lib/modules/6.8.0-31-generic: No such file or directory

Hm.

[Juerg Haefliger (juergh)]

Do you have broken packages? Can you post the output of 'dpkg -l'?

[Juerg Haefliger (juergh)]

It looks like your initramfs-tools is too old and can't handle compressed firmwares.

[s.illes79 (s-illes79-gmail)]

Attatched

[Juerg Haefliger (juergh)]

> ii initramfs-tools 2:0.140ubuntu13.4-tux1 all generic modular initramfs generator (automation)

That's not an Ubuntu package. Ubuntu's version in Noble is 0.142ubuntu25.1. Where does it come from?
$ apt-cache policy initramfs-tools

[s.illes79 (s-illes79-gmail)]

 apt-cache policy initramfs-tools
initramfs-tools:
  Installed: 2:0.140ubuntu13.4-tux1
  Candidate: 2:0.140ubuntu13.4-tux1
  Version table:
 *** 2:0.140ubuntu13.4-tux1 100
        100 /var/lib/dpkg/status
     0.142ubuntu25.1 500
        500 http://es.archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages
     0.142ubuntu25 500
        500 http://es.archive.ubuntu.com/ubuntu noble/main amd64 Packages

I have https://github.com/tuxedocomputers/tuxedo-control-center installed since it's a tuxedo laptop
maybe that pulled in it?

[Juerg Haefliger (juergh)]

Don't know but it seems to come from here:
https://deb.tuxedocomputers.com/ubuntu/dists/jammy/

Check your /etc/apt/sources.list and /etc/apt/sources.list.d/*.list files and remove the tuxedo jammy repos or replace them with the noble repos (which seems to exist: https://deb.tuxedocomputers.com/ubuntu/dists/noble/).

You also need to manually remove or upgrade all stale packages from the tuxedo jammy repo.

Finally, you should complain to tuxedo that they break machines that are dist upgraded. For initramfs-tools they chose a package version that will never ever upgrade to anything that Ubuntu provides. And they abandoned that package in later releases so it is stuck at this old version. Bad.

[s.illes79 (s-illes79-gmail)]

yup, not good. reported it here:

https://github.com/tuxedocomputers/tuxedo-control-center/issues/401

Thanks for the help to figure this out