Arch Linux

Heresyte

Member

Registered: 2008-07-10

Posts: 19

x

x

Last edited by Heresyte (2025-03-03 06:51:18)

kjon

Member

From: Temuco, Chile

Registered: 2008-04-16

Posts: 398

Re: x

boot your fallback image,
at root prompt regenerate your initcpio image with:

mkinitcpio -p kernel26

reboot and problem solved.

---

They say that if you play a Win cd backward you hear satanic messages. That's nothing! 'cause if you play it forwards, it installs windows.

iBertus

Member

From: Greenville, NC

Registered: 2004-11-04

Posts: 2,228

Re: x

To be more specific, it's not a fallback kernel, but rather a fallback ramdisk image. The standard ramdisk image is built to only have the modules needed by your hardware while the fallback image includes pretty much everything. As kjon said, rebuilding the standard image should autodetect modules and fix the issue.

Heresyte

Member

Registered: 2008-07-10

Posts: 19

Re: x

x

Last edited by Heresyte (2025-03-03 06:51:46)

bangkok_manouel

Member

From: indicates a starting point

Registered: 2005-02-07

Posts: 1,556

Re: x

i guess you'll have to add the needed module to your /etc/mkinitcpio.conf, otherwise you'll most likely get the same issue when the next kernel update will arrive. In addition, you've built your image with all modules, which is, well, harmless but maybe not the lightest option.

toad

Member

From: if only I knew

Registered: 2008-12-22

Posts: 1,775

Website

Re: x

At the risk of being hanged, drawn and quartered, for resurrecting an old thread I wish to state the obvious for the uninitiated - you (as indeed I and everybody else) will have to remount the drive to be writeable.

I stumbled over it and so may somebody else...

There is a special warning telling you how to, but nevertheless here it is again:

mount -n -o remount,rw /dev/sdxX /

---

never trust a toad...
::Grateful ArchDonor::
::Grateful Wikipedia Donor::