You are not logged in.
All:
Ever since around the time we moved to the block hook replacing a few others, I've had issues with mkinitcpio on my setup, though I can't determine why. I've reverted to the shipped mkinitcpio.conf, thinking it was my configuration causing the problem, to no avail. I receive this message:
root@Licht ~ # mkinitcpio -p linux
==> Building image from preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> ERROR: invalid kernel specified: `/boot/vmlinuz-linux'
==> Building image from preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> ERROR: invalid kernel specified: `/boot/vmlinuz-linux'I'm using mkinitcpio 0.12.0 from testing, and I'm using the default configuration. I can easily see my /boot/* files are indeed there.
Why is mkinitcpio having trouble?
Last edited by jyaworski (2013-01-12 16:55:29)
Offline
I'll mark this as solved, because I just solved it right after I posted.
It turns out, I had file 5.12 installed from when it was in testing for a brief time. Downgrading to 5.11 fixed the problem.
Offline
Offline
Thank you guys. This is why I love this distribution. I upgraded this morning, tripped over this problem, and confidently checked the forums for the answer. Bingo.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline