You are not logged in.
Pages: 1
I recompiled my linux-pf kernel (the same version as before) to add serpent SSE2 optimized module. I also added "encrypt" and "shutdown" hooks to mkinitcpio.conf
(There are no encrypted partitions yet.). These were the only changes (other than running full system update - I do that ~every 24hours).
Since then, the kernel won't boot up. It gets stuck at "No init found"
So I booted up with plain arch kernel, and removed "init=/usr/lib/systemd/systemd" from syslinux.cfg.
No change.
So I installed systemd-sysvcompat
No change.
So I removed "encrypt" and "shutdown" hooks from mkinitcpio.conf and run
mkinitcpio -p linux-pf
No change.
I am out of ideas. Could that be caused by the extra sperpent module, which is not even being used?
Last edited by Lockheed (2014-01-05 21:53:35)
Offline
Is the root filesystem being mounted? Are you specifying the right root filesystem?
Offline
Yes. The fallback default arch kernel boots fine, and is on the same partition.
Offline
If the fallback works, the problem is that the module needed for your root file system isn't in the initramfs. It should be autodetected just fine, but if it's not, include it specifically in the MODULES= line.
Offline
It's just a plain ext4 partition. I wonder why would it not work all of the sudden.
Offline
I think the problem was solved by adding systemd hook. I did not have it before, and apparently the newest kernel won't work without it.
Offline
I think the problem was solved by adding systemd hook. I did not have it before, and apparently the newest kernel won't work without it.
Not true on both counts.
Offline
Pages: 1