Re: [arch-general] Kernel 3.13
On 01/26/2014 02:17 PM, Dave wrote: Jonathan Hudson jh+a...@daria.co.uk wrote: When you upgrade to kernel 3.13, pacman considerately informs you that you must have a keyboard hook in mkinitcpio.conf. What you're not told is that if you have an AT keyboard, you also need to ensure that the atkbd module is loaded, otherwise you probably won't have a working keyboard on reboot. -jh Do you subscribe to arch-dev-public? It's under discussion there and saved me. Yes, and I am still unclear what is required to insure that an appropriate module is loaded for a normal laptop/desktop. I already include 'keyboard' in HOOKS -- is that all that is needed or are there additional specific modules that need to be probed? Does HOOKS=.. keyboard.. insure the atkbd module will be loaded/probed? I vote for a solution that insures a keyboard is always probed/detected/provided if one exists whether that is shipping a modules-load.d fragment or leaving it built-in. From the discussion, a manual probing seems like a bad answer. -- David C. Rankin, J.D.,P.E.
Re: [arch-general] Kernel 3.13
Am 28.01.2014 09:07, schrieb David C. Rankin: Yes, and I am still unclear what is required to insure that an appropriate module is loaded for a normal laptop/desktop. Nothing. The keyboard should simply. I already include 'keyboard' in HOOKS This is only required if you want to use the keyboard in early userspace, which 90% of the time, you don't even have to (encrypted root is one popular exception, handling a failsafe shell is another). The 'keyboard' hook has been in the defaullt configuration for a a while now. I vote for a solution that insures a keyboard is always probed/detected/provided If your keyboard doesn't work out of the box with 3.13-2, please add a comment to the appropriate bug report [1] (that is for everyone - comment on that bug if you have keyboard problems with 3.13-2). Everything else is just a waste of time. [1] https://bugs.archlinux.org/task/38671 signature.asc Description: OpenPGP digital signature
[arch-general] Uninstalling single package from i686 archroot without cleaning
All, The i686 archroot on the x86_64 box worked perfectly building i686 TDE. However, as I tweak packages, I need to 'uninstall' a package from the rw-layer without cleaning the entire archroot. Since this is i686 on a x86_64 box how do I properly chroot the archroot so that I can run pacman -R package name? Can I somehow: mount --bind some_dev $CHROOT/dev mount -t proc none $CHROOT/proc mount -t sysfs none $CHROOT/sys cd $CHROOT some_chroot_cmd So that the i686 system will be functional enough to remove a package? I have seen the Arch64_FAQ page discussing the linux32 wrapper working with i686 chroots created by installing with i686 ISO quickinstall, but this setup is just an i686 archroot. (will it work?) I want to avoid cleaning the archroot or deleting and recreating a new one just to test minor changes to package content adjustments due the setup requiring several hundred dependencies and packages to rebuild. What say the experts? -- David C. Rankin, J.D.,P.E.
