diff --git a/source/_posts/2014-11-22-debian-jessie-on-dell-precision-m4800.markdown b/source/_posts/2014-11-22-debian-jessie-on-dell-precision-m4800.markdown index 01f8b67..daf0c4e 100644 --- a/source/_posts/2014-11-22-debian-jessie-on-dell-precision-m4800.markdown +++ b/source/_posts/2014-11-22-debian-jessie-on-dell-precision-m4800.markdown @@ -43,3 +43,13 @@ Support for smart-card reader ----------------------------- `apt-get install pcscd` + +Network +------- + +Disable [IPv6 Privacy Extensions](https://home.regit.org/2011/04/ipv6-privacy/) +```plain /etc/sysctl.conf +# Disable IPv6 "Privacy extensions" (random SLAAC addresses) +net.ipv6.conf.all.use_tempaddr=0 +net.ipv6.conf.default.use_tempaddr=0 +``` 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 df18e0c..e6f2a5e 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 @@ -48,6 +48,9 @@ It is a real shame that users essentially have no choice but switching from the default syscons to the "new" (unfinished, far from functionally complete) vt console driver. +The X mouse cursor occasionnally disappears for some unidentified +reason. Alt-Tab brings it back. + DRI --- diff --git a/source/_posts/2015-03-05-bizarre-packet-filtering-on-ovh-kimsufi-server.markdown b/source/_posts/2015-03-05-bizarre-packet-filtering-on-ovh-kimsufi-server.markdown index e1487e2..25dcc62 100644 --- a/source/_posts/2015-03-05-bizarre-packet-filtering-on-ovh-kimsufi-server.markdown +++ b/source/_posts/2015-03-05-bizarre-packet-filtering-on-ovh-kimsufi-server.markdown @@ -68,6 +68,12 @@ and all analysis elements in my possession have been conveyed to them, to no avail so far: the machine has been essentially unusable for the past two months and counting. +**Update 2015-03-20** OVH say they identified a problem and are working on +a fix. No more SSH failure observed since 2015-03-18 in the afternoon, +so apparently the fix did work. Still waiting for a post-mortem explanation +as to what went wrong, and why it took them so long to ackonwledge, +investigate, and resolve the problem. + Acknowledgements ================ diff --git a/source/_posts/2015-03-12-gphoto-fails-to-connect-to-canon-eos-20d.markdown b/source/_posts/2015-03-12-gphoto-fails-to-connect-to-canon-eos-20d.markdown new file mode 100644 index 0000000..b7e0c40 --- /dev/null +++ b/source/_posts/2015-03-12-gphoto-fails-to-connect-to-canon-eos-20d.markdown @@ -0,0 +1,39 @@ +--- +layout: post +title: "GPhoto2 fails to connect to Canon EOS 20D" +date: 2015-03-12 18:43:21 +0100 +comments: true +categories: +--- + +For the past few months, [Digikam](https://www.digikam.org/) +(and the underlying [GPhoto2](http://gphoto.sourceforge.net/) library) +failed to connect to my Canon EOS 20D camera: + +``` +canon/canon/usb.c (2): Initializing the (USB) camera. +canon/canon/usb.c (2): canon_usb_camera_init() +canon/canon/usb.c (2): canon_usb_identify: USB ID match 0x04a9:0x30eb (model name "Canon:EOS 20D (normal mode)") +gp_context_status (2): Detected a 'Canon:EOS 20D (normal mode)'. +Detected a 'Canon:EOS 20D (normal mode)'. +gp_port_usb_msg_read (3): Reading message (request=0xc value=0x55 index=0x0 size=1=0x1)... +gp_port_usb_msg_read (3): Read 0 = 0x0 out of 1 bytes USB message (request=0xc value=0x55 index=0x0 size=1=0x1) (empty hexdump of empty buffer) +gp_context_error (0): Could not establish initial contact with camera + +*** Error *** +Could not establish initial contact with camera +gp_port_close (2): Closing port... +gp_context_error (0): An error occurred in the io-library ('Unknown error'): No error description available +``` + +Upgrading various components of my system did not help, so I ended up +suspecting a possible issue with the USB stack, which prompted a +[major OS upgrade]({% post_url 2015-02-18-upgrading-to-freebsd-10-1-release %}) +from which I am still slowly recovering. + +It turned out that the upgrade did not help. Further investigation and +debugging finally allowed me to zero in on the cause of the problem, +which turned out to be a bug in libgphoto2... which coincidentally +got [fixed](http://sourceforge.net/p/gphoto/code/15384/) +hours before I identified it on my own. +