@maarten
Jep those are update persistent.
[Tutorial] How to get your NanoHatOLED to work
Re: [Tutorial] How to get your NanoHatOLED to work
great! Thanks Micha !
Re: [Tutorial] How to get your NanoHatOLED to work
Hello,
I had to recompile the kernel and then installed DietPi over it. Now it shows "Linux DietPi 4.19.25-sunxi64 #5.76 SMP" under uname.
I can't make NanoHatOLED work.
When I try "systemctl enable rc-local.service" I get this message :
dietpi@DietPi:~$ sudo systemctl enable rc-local.service
The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
instance name specified.
Any ideas?
Thanks
I had to recompile the kernel and then installed DietPi over it. Now it shows "Linux DietPi 4.19.25-sunxi64 #5.76 SMP" under uname.
I can't make NanoHatOLED work.
When I try "systemctl enable rc-local.service" I get this message :
dietpi@DietPi:~$ sudo systemctl enable rc-local.service
The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
instance name specified.
Any ideas?
Thanks
Re: [Tutorial] How to get your NanoHatOLED to work
rc-local system has changed in Debian, conflicting some old DietPi leftover. Please check for solution: https://github.com/MichaIng/DietPi/issues/2566
Re: [Tutorial] How to get your NanoHatOLED to work
Thanks for the info Micha.
Not working. Did the install, than rebooted..
But even trying to run manually it's not working.
But ... the ./NanoHatOLED is showing under htop however nothing shows at the display.
Not working. Did the install, than rebooted..
But even trying to run manually it's not working.
But ... the ./NanoHatOLED is showing under htop however nothing shows at the display.
Re: [Tutorial] How to get your NanoHatOLED to work
Same here, worked like a charm up until recently. Now it is not working anymore. Black screen.
However htop shows the deamon is runnning...
However htop shows the deamon is runnning...
Re: [Tutorial] How to get your NanoHatOLED to work
i2c not working here ...
sudo i2cdetect -y 0
Error: Could not open file `/dev/i2c-0' or `/dev/i2c/0': No such file or directory
how can I enable it ?
sudo i2cdetect -y 0
Error: Could not open file `/dev/i2c-0' or `/dev/i2c/0': No such file or directory
how can I enable it ?
Re: [Tutorial] How to get your NanoHatOLED to work
After several reboots it seems to work again. However, NanoHatOLED display starts working not immediately after (re)boot but it takes a delay...
Re: [Tutorial] How to get your NanoHatOLED to work
it's finally working fine.
Re: [Tutorial] How to get your NanoHatOLED to work
Just updated from 6.19.7 to 6.24.1 and everything is working for me, I'm assuming the more recent versions of DietPi have a workaround in place for whatever gremlins were affecting people.