You are not logged in.
Pages: 1
Hey,
I cannot boot my computer (I get a kernel panic) unless I use the fallback initrd image.
Does this have any effect on the operation of my computer after the booting process?
(such as unnecessary modules loaded, etc.)
And in general - can someone explain the difference between the fallback image and the regular one?
Thanks
Fiod
Offline
I remember looking over a file during installation when installing the fallback image... perhaps /etc/mkinitcpio.d/kernel26-fallback.conf?
That might give you a start
Offline
/boot/kernel26.img --> stripped down in size by autodetect
/boot/kernel26-fallback.img --> contains all modules of subsystems
Copied from Arch Wiki on Configuring mkinitcpio
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Online
iirc I had the same problem, solved it by booting with the fallback initrd,
once booted, I regenerated the kernel26 initrd image, e.g
# mkinitcpio -k $(uname -r)
# mkinitcpio -k $(uname -r) -g /boot/kernel26.img
- Judge a pig competition? But I'm no super genius... or are I?
Offline
Pages: 1