it looks like your kernel version and module versions are the same. I’m not an authority on linux, i’ll admit. But, as El Corazon says, ‘just to make sure.’
It could be there is some other dependency not satisfied, so i would try an update and full-grade. As always, WMMV.

Tim

Read More...

I struggled with this problem for some time and found a solution or rather the reason it happens. Let me explain and hopefully it will help someone.

My problem manifested itself a little different. With all my usb/serial devices plugged in and powered at the time I booted the pi, all was good, sometimes. If I unplugged/plugged in a device, my dev rules where ignored. They would show up connected to gpiochipN or somewhere in the usb bus. Just as an aside, I also have a PoleMaster that could be started as a regular user under one os kernel, but after an upgraded could only be started as root. Udev rules where a constant source of wasted time and effort.

The breakthrough came after much research, trial, error, and a revelation. The revelation? The kernel version and module versions where not the same. I had a recent kernel with no matching modules directory. Verify with :

uname -r
ls /lib/modules

The solution was simple and this is right from raspberrypi.org
First, update your system's package list by entering the following command:
sudo apt update
Next, upgrade all your installed packages to their latest versions with the following command:
sudo apt full-upgrade
Note that full-upgrade is used in preference to a simple upgrade, as it also picks up any dependency changes that may have been made.

This really made a difference in the performance of my rig all around, besides fixing the udev and PoleMaster problems. In fact I doubt I will be doing any hardware upgrades soon, I'm that happy with the way it is working. I did add an rtc to my pi's for $8 US each.

Tim

Read More...