From f9d5b2b3914e30339a99cc90d004820d531f4981 Mon Sep 17 00:00:00 2001 From: Thomas Quinot Date: Sat, 27 Aug 2016 11:46:52 +0200 Subject: [PATCH] Add new posts and upgrade X keymap discussion --- ...upgrading-to-freebsd-10-1-release.markdown | 18 ++++++++++++-- ...-07-gdm-keyboard-layout-revisited.markdown | 21 ++++++++++++++++ ...laserjet-m1217nfw-setup-with-cups.markdown | 24 +++++++++++++++++++ 3 files changed, 61 insertions(+), 2 deletions(-) create mode 100644 source/_posts/2016-08-07-gdm-keyboard-layout-revisited.markdown create mode 100644 source/_posts/2016-08-27-hp-laserjet-m1217nfw-setup-with-cups.markdown diff --git a/source/_posts/2015-02-18-upgrading-to-freebsd-10-1-release.markdown b/source/_posts/2015-02-18-upgrading-to-freebsd-10-1-release.markdown index e6f2a5e..e9828f5 100644 --- a/source/_posts/2015-02-18-upgrading-to-freebsd-10-1-release.markdown +++ b/source/_posts/2015-02-18-upgrading-to-freebsd-10-1-release.markdown @@ -104,9 +104,23 @@ so I added the following to my setup: ``` However this happened to be a total red herring, as by default the -port configures Xorg to use devd, not HAL. +port configures Xorg to use devd, not HAL. For devd, I +[found out](http://olivier.cochard.me/bidouillage/installation-et-configuration-de-freebsd-comme-poste-de-travail#TOC-Configuration-de-la-langue-du-clavier-sans-HAL) +this is achieved +using xorg.conf options: -It appears that the X server setup is actually just fine. And indeed, +``` +Section "InputClass" + Identifier "Keyboard Defauls" + Driver "keyboard" + MatchIsKeyboard "on" + Option "XkbLayout" "fr" +EndSection +``` + +But all of this was mostly irrelevant for my setup since I add +AutoAddDevices turned off in the X server setup, and the correct +layout was hardcoded in xorg.conf. And indeed, starting it with startx yields the expected French layout. However, it appears that gnome-shell considers that whatever keymap diff --git a/source/_posts/2016-08-07-gdm-keyboard-layout-revisited.markdown b/source/_posts/2016-08-07-gdm-keyboard-layout-revisited.markdown new file mode 100644 index 0000000..1b2b627 --- /dev/null +++ b/source/_posts/2016-08-07-gdm-keyboard-layout-revisited.markdown @@ -0,0 +1,21 @@ +--- +layout: post +title: "GDM keyboard layout revisited" +date: 2016-08-07 01:38:56 +0200 +comments: true +categories: +--- + +So, I wanted to upgrade Firefox on my FreeBSD 10 workstation, +and this in turn caused some supporting libraries to be upgraded, +and this broke all sorts of things again. + +Initially gdm just segfaulted. After more manual upgrades, +it turned out to work again, except that GDM had lost all localization, +and in particular got the wrong keymap for the login screen. + +It appears that gdm_lang is no longer honored (despite still being +mentioned in /usr/local/etc/rc.d/gdm): you now need to set gdm's +locale in /usr/local/etc/gdm/locale.conf. Also note that unlike +other user-editable configuration files, this one is overwritten +each time gdm is reinstalled. diff --git a/source/_posts/2016-08-27-hp-laserjet-m1217nfw-setup-with-cups.markdown b/source/_posts/2016-08-27-hp-laserjet-m1217nfw-setup-with-cups.markdown new file mode 100644 index 0000000..f50bdd3 --- /dev/null +++ b/source/_posts/2016-08-27-hp-laserjet-m1217nfw-setup-with-cups.markdown @@ -0,0 +1,24 @@ +--- +layout: post +title: "HP Laserjet m1217nfw setup with CUPS on FreeBSD 10" +date: 2016-08-27 11:41:57 +0200 +comments: true +categories: +--- + +This is an entry level network-connected multi function printer. It +does not have a built-in Postscript interpreter. Instead, it receives +raster data through a proprietary network protocol implemented as +a closed source binary plugin to the CUPS filtering system. + +In addition to CUPS, the following ports must be installed: + * print/hplip + * print/hplip-plugin + +Once this is done, the printer can be added to CUPS. The standard +socket connection options cannot be used. Instead, the "HPLIP" transport +must be selected. The printer URI must be set manually from the output of +`hp-makeuri `. (The plugin requires an URI starting with +"hp:", and will reject any other device URI with an error message saying +"Error: This module is designed to work with HP Printers only"). +