I ran a scan, it recognized then memorized my WiFi network and the authentication key, on socket 0, the other 4 sockets (1 to 4) are unused, the connection to my router is still not happening ?
I just noticed that an update of DietPi from 9.14 to 9.21 was available… but unfortunately this update does not solve my problem. And I am very surprised to notice that the command “apt update && apt dist-upgrade” does not allow this update to be carried out and that I am forced to do a “dietpi-update”…
This is not a good thing for me who likes to automate updates by Cron…
I have to lower the security of my WiFi from WPA3 to WPA2 for the connection to work ;-( While Debian 12 is WPA3 compatible !?
Another strange thing when I do a “top” command line there are 2 users connected, is this normal ?
The problem was that DietPi couldn’t connect to my WiFi network due to DietPi not supporting WPA3. Debian 12 does not support WPA3 during the installation process but in post install it works without the slightest problem unlike DietPi ? And I want to be able to use WPA3.
Yes I notice that… it’s absolutely not standard. “apt update && apt dist-upgrade” should update the entire installation, including your scripts…
As DietPi did not offer an update for Squeezelite I had to download and update it manually. I also reinstalled Shairport-sync (37) / AirPlay2 which I had installed as standard, then which I had uninstalled. I had to force the installation from the command line because I had an error with DietPi and shairport-sync (apt install shairport-sync). And I also reinstalled Roon Brigge (121) (basically installed, then deleted and reinstalled).
No, it’s a command from the apt package manager, which has nothing to do with our scripts.btw our scripts use apt too, so how could it update our scripts? They are not packages managed by apt.
I really think we have a typical layer 8 problem here, which is not a problem. The problem is, that you blame us for this.
The WPA problem is explained some posts above.
This is a volunteer project and you act like we owe you something.
If it does not fit your needs you have the free choice to use something else.
did you checked the link I shared? Did you read the blog post? It looks like WPA3 is not supported by RPi5 device or it’s RPI own firmware. This has nothing to do with DietPi or Debian because kernel as well as firmware are the original one from RPi foundation.
Unfortunately, you have not yet understood what DietPi is. It is not a separate operating system. DietPi is a set of bash scripts. Our source code is on GitHub and is updated via dietpi-update. DietPi itself has no apt packages and therefore cannot be updated via apt. No matter what your expectation is.
For most software titles, we have provided information on the update process in our Online Docs. Perhaps you should take a look there.
Depending on the software title, an update may vary. Some are updated via apt, others via the internal update functions of the software itself and still others require a reinstall.
apt dist-upgrade is supposed to update an entire Debian system, scripts included. I’m surprised that’s not the case here.
I have to use a translator to communicate with you which makes things quite painful for me, he translates as best he can…
All Linux distributions are maintained voluntarily and all users are free to choose the solutions they prefer.
When people adopt a distribution and are satisfied with it, they may also make a voluntary donation.
When people have the same synergy it gives good results, when this is not the case… I would also add that criticism must be perceived positively, it allows us to understand ourselves and do better.
LMS offers you its own update when you use it…
Thanks, I’ll look at that
Yes I saw, I use WPA3 on my computer under Debian 12… it works.
I’ll try to tinker with this ;-(
You missed what apt does and how it is working. Again DietPi is not an own operating system. DietPi is just a set of bash scripts and not managed via apt packages.
As said, this is not a limitation of Debian or DietPi. It’s how RPI developer have designed their firmware.
We are not an own distribution. DietPi is some logic and automation features in top of Debian. We don’t aim to build an own Debian based destro. More we try to reduce the system footprint and to provide some easy to use end-to-end automation for users who don’t have that deep knowledge. We built some own standardisation across different platforms, SBC and VMs. As base we use Raspbian, Armbian or Debian. Most of the images are bootstrap Debian images where we use vendor or Armbian kernel. For RPi, kernel as well as firmware are the original one provided by RPi devs. There is no single source image. It depends on target system. Best to check our build script. Nearly all our images are generated by GitHub actions.