Sascha Curth

Vielen Dank, hat geklappt. Ich habe die Prozedur gleich noch auf meinem Blog dokumentiert. https://www.sascha-curth.de/news/2020-08-18-Raspberry_und_Tinkerforge.html

Hallo, anscheinend bin ich in der selben Situation. Kernel: 5.4.51-v7+ #1333 SMP Mon Aug 10 16:45:19 BST 2020 armv7l GNU/Linux brickd --version: 2.4.1 2020-08-18 11:17:26.944215 <E> <gpio_sysfs.c:129> Could not open '/sys/class/gpio/gpio7/direction': ENOENT (2) 2020-08-18 11:17:26.944879 <W> <hardware.c:56> Still 6 stack(s) connected 2020-08-18 11:17:26.945067 <W> <event.c:138> Leaking generic event source (handle: 17, name: bricklet-stack-notification, events: 0x0001) at index 0 2020-08-18 11:17:26.945128 <W> <event.c:138> Leaking generic event source (handle: 20, name: bricklet-stack-notification, events: 0x0001) at index 1 2020-08-18 11:17:26.945165 <W> <event.c:138> Leaking generic event source (handle: 23, name: bricklet-stack-notification, events: 0x0001) at index 2 2020-08-18 11:17:26.945203 <W> <event.c:138> Leaking generic event source (handle: 26, name: bricklet-stack-notification, events: 0x0001) at index 3 2020-08-18 11:17:26.945248 <W> <event.c:138> Leaking generic event source (handle: 29, name: bricklet-stack-notification, events: 0x0001) at index 4 2020-08-18 11:17:26.945284 <W> <event.c:138> Leaking generic event source (handle: 32, name: bricklet-stack-notification, events: 0x0001) at index 5 2020-08-18 11:17:26.945328 <I> <main_linux.c:538> Brick Daemon 2.4.1 stopped -> wie kann ich das Problem jetzt lösen? Die Version 2.4.1 funktioniert nicht in der Kombination.