Closed MichaIng closed 5 years ago
When is the official version of dietpi buster out?
@SimplyGardner For Raspberry Pi we will switch to Buster very soon. I think the image above is already fine, it is still based on the latest Raspbian Lite release and now since DietPi v6.25 is release, it will be automatically updated to stable DietPi code on first boot.
Only limitation I know for non-RPi4: No Kodi available yet. RPi4 works as well, but some dietpi-config settings are not yet RPi4 ready.
For x86_64 Buster images are already very stable (tested a long time in combination with DietPi testing in the past ~1.5 years), but we will officially set them to stable (and remove Stretch from download page) after official Debian Buster release (the next weeks).
For most other SBCs it will take a longer while I guess. firmware/drivers have to be Buster-ready and I expect this to take while, especially for older SBC models.
@Fourdee
VC4 modes related to this I guess: https://www.raspberrypi.org/forums/viewtopic.php?t=244596
Looks like master firmware version solves it (e.g. rpi-update
for now): https://github.com/Hexxeh/rpi-firmware/commits/master
raspi-config
currently also does not allow vc4-fkms-v3d
(Full KMS) on RPi4: https://github.com/RPi-Distro/raspi-config/blob/master/raspi-config#L1380-L1391Finally also the rpi-update notice makes it clear not NOT use rpi-update without specific reason: https://github.com/Hexxeh/rpi-firmware/commit/768ea94042bade6ea276c6cea358c9645cb5de6a
Thanks for keeping me (us, everyone) informed on these changes. The TO_DO_LIST grows :)
New RPi4-capable Buster image uploaded: https://dietpi.com/downloads/images/DietPi_RPi-ARMv6-Buster.7z
@MichaIng, Can I use apt update / upgrade only since I am with 6.25v.3 or I should pre-flash the sdcard once again? Edit: I found in other thread and one more "dietpi -update 1" which one?
@MichaIng If I use provided the experimental image, will it always stay on the "experimental" branch of updates? Or once it's stable It's just an update?
@nboyan @renarsvilnis No need to reflash the image.
The experimental image was created with v6.25 dev or beta code, to have RPi4 definitions inside. But the target Git branch was manually reverted to master (stable). You can verify via:
grep 'DEV_GITBRANCH' /DietPi/dietpi.txt
Should how: DEV_GITBRANCH=master
If you are on v6.25.3 already, then you are already on latest stable release. If the login banner just says DietPi v6.25.3 : 14:19 - Mon 07/15/19
then this is as well a prove that you are on master (stable) code, otherwise it would say e.g. DietPi v6.25.3 (beta) : 14:19 - Mon 07/15/19
.
If you are indeed not on master branch, run:
G_CONFIG_INJECT 'DEV_GITBRANCH=' 'DEV_GITBRANCH=master' /DietPi/dietpi.txt
If an update is offered (e.g. you are on v6.25.0/1/2), but the menu does not work (simply exits without update), then run dietpi-update 1
. This includes apt update+upgrade.
If no update is offered, but you e.g. want to update the firmware, run as usual: apt update && apt update
(or apt full-upgrade
, although not required on RPi for firmware updates).
thx @MichaIng
Okay, I made the RPi4-capable Buster image the default download now. No major issues reported. There is still some work to do to make e.g. dietpi-config full RPi4 compatible, e.g. 4k HDMI and separate settings for each HDMI port. So far all that is applied applies to port 1 only.
I will close this issue now. Please report bugs or requests in separate issues from now now.
Device is ordered, initial hardware detection and ID has been added: https://github.com/MichaIng/DietPi/commit/19ab1667e87b760d48414887191ed0b407f13574
Testing image available: https://github.com/MichaIng/DietPi/issues/2935#issuecomment-511226948
Twitter: https://twitter.com/DietPi_/status/1143142028148191232
Third kernel tree added, quite a bunch of data now:
Also a new set of kernel/bootloader/start/fixup files has been added, /boot is growing messy:
Oh okay, this is even a very close thing on my system:
System volume Information
and stuff like this.Only the Buster repo ships the RPi4 kernel+bootloader files, so no need to warn our RPi (Stretch) users.
Checking new Raspbian Lite image: