-
-
Notifications
You must be signed in to change notification settings - Fork 501
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DietPi-Software | Do APT full/dist-upgrade on firstrun installs #3098
Comments
@cmessin1 What we should do is applying this full-upgrade on first boot automatically. I am not keen to do this on every software install and regular updates, since in rare cases, e.g. some conflicting repos and such, when forced/automated, it can purge packages that you actually wanted/need, even required system packages by times. But on first boot, when nothing else was installed, if is safe and upgrades the kernel to current version. |
+ DietPi-Software | Firstrun: Do a full APT upgrade (including firmware/dependency changes) on first run installs, since it is safe to do it here and to assure that all systems are lifted to the same package/firmware stage: #3098 + DietPi-Software | Firstrun: No time sync mode requires additional packages anymore, thus set it along with other AUTOINSTALL settings + DietPi-Software | Firstrun: Set defaults for automation settings missing in dietpi.txt
Firmware package upgrades are now done automatically on first run installs: b81bee4 |
Apologies in advance for the necro, but I encountered some weird network-issues on a fresh install of DietPi_RPi-ARMv8-Bullseye (installed from here) on my Raspberry Pi 4 4GB regarding packet-loss and extremely slow network-speeds. I found this issue and after setting my link-speed to 100 the network-issues were gone and I could do a Since this is a 3 year old issue it seems very strange, but perhaps something else is going on here? |
where does the RPi 4 connects to? A switch or a router? Did you tried to switch Ethernet cable? Or use a different port? |
Well, this is extremely awkward. It was a network issue. Apologies |
Hopefully this is the correct place for this.
I have found that the u-boot that ships with the current beta odroid-n2 image on the website to be an issue. The on board ethernet has massive packet loss when connected at 1G, though it is functional at 100mb.
I upgraded to the latest u-boot from the the odroid git and this resolved the issue.
I would suggest you update the u-boot in the posted image.
The text was updated successfully, but these errors were encountered: