-
-
Notifications
You must be signed in to change notification settings - Fork 504
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
Image | Testing updated RPi image #2613
Comments
Next issue is the ordering cycle [email protected], rc-local.service and dietpi-postboot, leading to any of those is not started. This is already fixed with v6.22. |
WireGuard install test:
|
Hi, if you need some testing on RB3+ let me know. |
@Joulinar I will link it here, when done. |
@MichaIng ok cool, will do once ready |
@Joulinar |
Ok will test it tomorrow. Anything special to test next to a clean install + WireGuard? |
@MichaIng So, I was running two cycle to test the installation. So far, I could not find any issues. Basic installation + Wireguard are running fine. Except one small think I spotted right after update to 6.21.1 `[ OK ] DietPi-Survey | Successfully sent survey data DietPi-Update [ INFO ] DietPi-Update | Current version : v6.21.1 |
@Joulinar Ah you tested WireGuard as well. It is great that obviously as well in your case the system didn't upgrade to sid. Actually I didn't apply some fix about this to the image, so be careful if you continue to use this image and if any other package from the sid repo is installed by APT, please report back.
Jep this is already fixed. Has no effect since non existing variable has the same affect as the value that was intended to be applied with this line. |
@MichaIng well I just did, Are there logs in the PI that you like to have? Just for checking? |
@Joulinar But as you are already asking, let's have a look into the boot log: Copy&paste the ~first 20 seconds, so the boot process. @Fourdee |
There you go |
@Joulinar
This was really from the image I linked above? Because I actively removed And I actively removed the boot order issue from Please verify that you did not just install the image from https://dietpi.com/downloads/images/ but the linked above.
|
@MichaIng hmm strange, Usually I downloaded the image you linked above. Strange one. As well I was not doing any manual update. Just the one that was automatically started during 1st boot. Maybe I stored the image in wrong folder on my computer and used old image to build up SD. Let me try again and use fresh image/ download. |
@Joulinar And as I already have my RPi2 back on Buster production. Might you check that I want to use the APT package from now on, but on Debian it is only available in backports, which does not exist in Raspbian: #2446 |
ok the issue was in front of computer as always. Sorry for that. Now the log with the correct image
|
@Joulinar One thing I recognized:
|
During setup, there was a "new" question regarding serialconsole. I selected to disable. Not sure if this is connected.
|
Jep, by default we have serial console enable for first boot, just in case some issue occurs, so one can use it for debugging. But since most users do not require it or even know what it is and how to use, we ask if it should be disabled 😉. |
About wpasupplicant and dbus:
EDITAgain different. ifupdown does not use any systemd unit, instead starts wpa_supplicant manually:
Done: 6231411 |
Hi, anything special you would like to be tested? |
@Joulinar If you could test some video and audio features (e.g. desktop and playing some video and/or Kodi), this would be perfect, just to assure everything hardware related is working as desired on RPi3 as well. |
ok will do this evening. |
@MichaIng I did another test and first installation is running smooth. Well done Afterwards I was running Desktop installation of Mate. I takes a while, but it finished without issues and I was able to launch it. Was testing a little bit with Firefox and Chrome on YouTube. Well its running, but not fun. It brings the Pi to his limit. But that’s how it is on such small hardware :) what I notice as well, that software installation was taking ages. But I guess it's not really related to DietPi
was pending for more than 10 minutes before it continue |
@Joulinar
Okay I will move the image in place 😃! I mark this as closed. Image released and all recognized issues solved with v6.22 code+PREP script + in the (stable v6.21) image as well manually. |
New RPi image released: REMOVED OBSOLETE LINK
Found an old SDcard. Due to some reports I'm testing our image and especially the WireGuard install to find out how it can happen that several system core packages are upgraded to
Debian Sid
.First run setup:
DietPi-PostBoot
had finished, so there seem to be some other processes/tasks interfering. However worked well finally.🈴 Plymouth service active after final login. Interfering with active console leading to annoying visual quirks.
Adding
logo.nologo
tocmdline.txt
. No change, not the reason!Checking installed packages:
plymouth
indeed installed, but not marked as manual.initramfs-tools
installed as well, even that we explicitly do not mark/install it or RPi in PREP.mountall
is marked as "required" package, depending onplymouth
which again depends oninitramfs-tools
.mountall
on RPi during PREP to have all other packages autoremoved:mountall
is not even part of Debian Stretch, no idea why it is present in Raspbian Stretch images and even marked asrequired
...https://packages.debian.org/jessie/mountall
The text was updated successfully, but these errors were encountered: