Dev1 Galaxy Forum / System starts without modules following an upgrade

Re: System starts without modules following an upgrade

dummy@example.com (TheLancashireman) — Mon, 26 Feb 2024 20:43:13 +0000

I just solved a similar problem by downgrading eudev and libeudev from 3.2.14 to 3.2.12.

See this comment and those preceding it: https://dev1galaxy.org/viewtopic.php?pid=48499#p48499

Re: System starts without modules following an upgrade

dummy@example.com (golinux) — Mon, 22 Jan 2024 23:19:20 +0000

There might also be usrmerge related issues before the dust settles and some could be quite annoying . . .

Re: System starts without modules following an upgrade

dummy@example.com (rolfie) — Mon, 22 Jan 2024 22:38:44 +0000

Then you were lucky for two years. Too bad. Try again tomorrow ...

Re: System starts without modules following an upgrade

dummy@example.com (dudg) — Mon, 22 Jan 2024 22:30:00 +0000

Yeah I know that but I had no other issues for more than 2 years of using ceres and this popped up all of a sudden

Re: System starts without modules following an upgrade

dummy@example.com (rolfie) — Mon, 22 Jan 2024 22:14:54 +0000

Well, you should expect that ceres sometimes does break ... Its unstable. Try again tomorrow.

Re: System starts without modules following an upgrade

dummy@example.com (dudg) — Mon, 22 Jan 2024 21:29:53 +0000

I have just tried insmod /usr/lib/modules/6.5.0-3-amd64/kernel/drivers/gpu/drm/i915/i915.ko but it fails with:

ERROR: could not insert module /usr/lib/modules/6.5.0-3-amd64/kernel/drivers/gpu/drm/i915/i915.ko: Unknown symbol in module

System starts without modules following an upgrade

dummy@example.com (dudg) — Mon, 22 Jan 2024 21:18:04 +0000

Hello everyone,

My ramdisks have just been rendered moduleless. Booting into two of my kernels (6.6.11 and 6.5.0-5) results in a blinking cursor followed by an initramfs shell with a message that the search for rootfs has timed-out. Indeed, `df` doesn't show my root partition and in addition, the `/proc/modules` file is completely empty.

Fortunetely, my third kernel (6.5.0-3) actually starts init (sysv) and allows me to log into my user account. This kernel also lacks some of the modules, namely `iwl` and `i915`.

My rootfs is on ext4 and I'm on ceres.

---

All of this has happened after I tried to perform an upgrade. A new kernel (6.6.11) was about to be configured but during the ramdisk generation the `mkinitramfs` complained about missing /sbin commands and apt reported errors for:

* cpio
* linux-image-6.6.11-amd64
* linux headers-6.6.11-amd64
* linux-image-amd64
* linux headers-amd64

I linked `modprobe`, `modinfo` and `mt-gnu` from /usr/sbin but unfortunetely, it only changed the error to:

Error processing package linux-headers-6.6.11-amd64 (--configure):
	dependency problems - leaving unchanged

After that, I rebooted the machine into the 6.6.11 kernel and got greeted with kernel panic (unable to mount rootfs). Fortunetely, the 6.5.0-3 was working without a few modules and I proceeded to install `usrmerge` thinking that it may help.

The installation first errored out stating that `/lib/udev/rules.d/60-ffado.rules` and `/lib/modules/6.6.11-amd64/modules.alias.bin` are both in `/` and `/usr`. I resolved the issue manualy and was able to install the `usrmerge` package. I ran `update-initramfs` for 6.5.0-5 and 6.6.11 kernels and now both are booting without modules loaded.

I suspect that during an upgrade, some of the modules were not transfered out of the `/usr` and now `update-initramfs` and the 6.5.0-3 kernel are just not picking them up.

Is it possible to bring system back to a normal state or have I completely doomed it?

Best regards.