after a kernel upgrade my modules are gone, and of course I need to reboot to
be able to load the new modules. The thing is, before I reboot I need to copy my
new kernel and initramfs to the EFI partition, which requires me loading the vfat module,
which is now gone...
As far as I can tell, I am going to need a secondary OS (or live cd) to solve this....,
I think this is a design bug... any ideas?
Luckily I had tried to recompile the kernel a week ago and had a copy of the modules in another directory.
Otherwise I would be in trouble, this should be solved.
Add the efi partition to fstab, so it gets mounted at boot time. If your bootloader supports non-.efi named kernels (rEFInd does), you could simply bind the directory you put the kernels into onto /boot at boot time, so that you don't need to manually copy the kernel + images each time you update it.
For example, I have the following in my fstab:
UUID=DA2E-688C /mnt/efi vfat defaults 0 2 /mnt/efi/EFI/arch /boot none bind 0 0
Last edited by WorMzy (2013-03-28 16:41:34)
Mobo: ASUS P8Z77-V PRO // Processor: Intel Core i7-3770K 3.4GHz // GFX: nVidia GeForce GTX 970 Ti // RAM: 32GB (4x 8GB) Corsair DDR3 (@ 2133MHz) // Storage: 1x 3TB Seagate SATAII 5x 1TB Samsung SATAII, 2x 120GB Corsair SSD
Making lemonade from lemons since 2015.
Thank you, it is a solution which I will implement, though maybe a warning of some sort should be made so this doesnt happen to unwary users.