2020-08-13, 09:47 AM
(2020-08-13, 07:51 AM)Rooco Wrote:(2020-08-12, 09:10 PM)Max1947 Wrote: No, I haven't changed anything. The same problem is reproduced:
https://i.imgur.com/V2sEpLd.png
https://i.imgur.com/FDpf96l.png
https://i.imgur.com/Jwct16Z.png
https://i.imgur.com/rD6w1ip.png
PI4 + Hat v1 + MCS
I can't reproduce your issue. Tested tonight on several systems/configurations, multiple reboot cycles. Do you have the issue if MCS is not attached as well?
Let's do some debugging...
To get more debugging information, we need to load the driver with debug information enabled. This can be done using the following commands in a terminal.
We kill all processes that uses the driver (except "node", this automatically respawns):
~/moitessier/scripts/kill
Now we can list all processes that are still using the moitessier driver. Only "node" should be listed.
lsof /dev/moitessier.*
We kill "node" and immediately after that we need to unload the driver. You need to be very fast with the rmmod command, otherwise node will be started automatically again. Maybe you need to try several times.
pkill node
sudo rmmod moitessier
We load the driver with debugging information enabled. The specified module is used for the Pi 4 and the latest kernel version. If using a different Pi version, you need to use the proper module.
sudo insmod moitessier/modules/moitessier_5.4.51-v7l+.ko DEBUG_LEVEL=13
Store the kernel messages in a file and send it to me.
dmesg > dmesg.txt
We also might do a remote session via VNC or TeamViewer.
Regards,
Thomas
Hi Thomas, I am attaching "dmesg.txt" as requested (what I was able to do with copy / paste). Can you use AnyDesk to connect with my computer? (https://anydesk.com/en/downloads/linux). As you can see from the photo it becomes a hard job to disconnect the HAT (with the fear of ruining everything) however I will try to put it on Pi3 alone for other tests, maybe after you have connected with my desktop ... wait for news!
https://i.imgur.com/ZyXXuTh.jpg
https://i.imgur.com/1E31Z2J.png