You are not logged in.
Working kernel is 3.0.7-1.
I installed a new kernel [3.2.6-2].
Rebooted.
It had problems. Laptop keyboard and trackpad are unresponsive.
Rebooted.
Chose **Fallback** kernel.
The new kernel booted.
I plugged in a usb keyboard (thank goodness that worked!). Reinstalled the prior working kernel [3.0.7-1].
Rebooted.
Tested and both the new and fallback kernel choices boot to 3.0.7-1.
I tried searching for this problem and a solution for it but came up empty. What did I miss?
Versions:
pacman - 4.0.2-1
Offline
Take a look at this page: https://wiki.archlinux.org/index.php/Mkinitcpio
From it:
The fallback image utilizes the same configuration file as the default image, except the autodetect hook is skipped during creation, thus including a full range of modules. The autodetect hook detects required modules and tailors the image for specific hardware, shrinking the initramfs.
So it sounds like the autodetect hook is not autodetecting your laptop keyboard. I'm not sure whether you can specify it somewhere... try searching for your laptop model on the arch forums
Welly, welly, welly, welly, welly, welly, well. To what do I owe the extreme pleasure of this surprising visit?
Offline
Okay, now I'm really confused.
You mean to tell me that the if I install a new kernel and it won't boot at all I screwed because Arch won't let me keep the prior kernel around in grub???
Pacman just deletes the entry for it and says, "Hope that works because if not, FU!"???
Offline
yep :-) Kernel management is Arch's weakest point IMO. What's even better is if you install a new kernel, it will overwrite the current modules too so you can't load/unload anything until you reboot
However, nothing is stopping you from copying the old kernel files in /boot to new names because pacman should never remove files it didn't create (and then editing GRUB/GRUB2/Syslinux/LILO etc)
Welly, welly, welly, welly, welly, welly, well. To what do I owe the extreme pleasure of this surprising visit?
Offline
Load up linux-lts and become happy again [do not forget to add it too grub]
Offline
That's not weak, that's insane for a cutting edge rolling distro.
So if I copy the iniramfs-linux.img and vmlinuz-linux files and modify the grub menu is that all I need to do?
>overwrite the current modules too
Does this mean I need to manually copy something else prior to each kernel upgrade attempt?
Offline
That's not weak, that's insane for a cutting edge rolling distro.
So if I copy the iniramfs-linux.img and vmlinuz-linux files and modify the grub menu is that all I need to do?
>overwrite the current modules too
Does this mean I need to manually copy something else prior to each kernel upgrade attempt?
Ummm... I may be wrong on the modules thing. I could have sworn that I tried this very recently due to a virtualbox issue where I needed to unload the modules. Sorry - I'm really not 100% on how to proceed
Welly, welly, welly, welly, welly, welly, well. To what do I owe the extreme pleasure of this surprising visit?
Offline
@jfb3: Out of interest, what are the sizes of your image files?
Mine are as follows:
initramfs-linux.img = 2,654,268
initramfs-linux-fallback.img = 10,939,227
Offline
-rw-r--r-- 1 root root 3011445 Feb 22 22:53 initramfs-linux-3.0.71.img
-rw-r--r-- 1 root root 10798701 Feb 22 20:21 initramfs-linux-fallback.img
-rw-r--r-- 1 root root 3011445 Feb 22 20:21 initramfs-linux.img
-rw-r--r-- 1 root root 3020080 Oct 19 15:30 vmlinuz-linux
-rw-r--r-- 1 root root 3020080 Feb 22 22:55 vmlinuz-linux-3.0.7-1
Offline