Thank you Marcus. Problem solved after updating to 2.5.29.
-------------------------------- Thank you, Michael Zhang ----- Original Message ----- From: Marcus Meissner <mar...@jet.franken.de> To: zhangxiuchuan <zhangxiuch...@vip.sina.com> Cc: gphoto-devel <gphoto-devel@lists.sourceforge.net> Subject: Re: [gphoto-devel] Debian 11 issues Date: 2022-04-18 19:13 Hi, On Sat, Apr 16, 2022 at 04:26:14AM +0800, zhangxiuchuan wrote: > Hello, > > I've used gphoto2 to control DSLR cameras (Canon EOS > T3i, T7, SL3, etc.) on Debian 8~10 for years without any issues. I've been > testing my cameras on Debian 11 these days and found some issues. > > After running some basic commands like gphoto2 > --list-config on a laptop with Debian 11, the EOS T3i and SL3 are locked and > cannot be triggered by pressing the capture button, and the command gphoto2 > --set-config opcode=0 does not work which is good on Debian 8~10. Although > the EOS T7 is > not locked, gphoto2 --set-config opcode=0 doesn't work either. > > I tried these cameras on a Raspberry pi 4B with > Bullseye OS and the results were the same as on my laptop with Debian 11. > > It looks like these problems are related to Debian 11. > Is it possible to solve them? This is something related to the libgphoto2 version, we changed the logic of unlocking EOS on exit a bit over time. In 2.5.29 it is unlocking the EOS at the end, with a bit more refined code in the next release (or current libgphoto2 git). --set-config opcode=0 is not valid, there usually is a 4 digit hexnumber missing (--set-config opcode=0x1001 or similar) Ciao, Marcus
_______________________________________________ Gphoto-devel mailing list Gphoto-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gphoto-devel
