On 25 Jul 2023 17:09 +0100, from robbied...@gmail.com (Robbie Dinn): > I used dpkg-query to check what package the file > /etc/console-setup/cached_UTF-8_del.kmap might belong to. > > freon@debian:~$ dpkg-query -S > /etc/console-setup/cached_UTF-8_del.kmap.gz > dpkg-query: no path found matching pattern > /etc/console-setup/cached_UTF-8_del.kmap.gz > freon@debian:~$ > > If it is just a cached file, could you move it out of the way to see if > it gets recreated the same?
I tried this in a VM (it's nice to be able to spin up brand new, up-to-date VMs in a few minutes of hands-off time to test things; that time I spent writing a preseed configuration has certainly paid itself back since...), deleting /etc/console-setup/cached* and running dpkg-reconfigure console-setup. As far as I can tell the files were put back in /etc/console-setup, with the same contents (same cksum as the main system). Since a freshly installed system boots without printing this error message, and I imagine an error like this would have been caught during the testing and stabilization phase, I figure it's likely _something_ about my configuration which is tripping _something_ up. I just can't figure out what that might be. > The other idea was, if you have a working kmap setup in your virtual machine > install, could you "suck" the keymap settings out of that machine using the > xmodmap utility, then copy them to the broken machine and inject them into > the Xserver overriding the configured keymap (using xmodmap again?). I don't think that'd do anything particularly useful. Maybe I could, but I don't seem to have any problem with the keyboard layout in X, including at the login screen username entry; only at the text console (getty and friends). It also occured to me that since the error is printed very early during boot, maybe it was caused by something in the initrd somehow having got out of sync with the normal root file system that I'm looking at. Alas, `update-initramfs -u -k all` did regenerate initrds for all three currently installed kernels without reporting any problems, but I still got the same error on the subsequent reboot. So not _that_ simple. Still, I very much appreciate the ideas! -- Michael Kjörling 🔗 https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
