-
-
Notifications
You must be signed in to change notification settings - Fork 496
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
Update from DietPi version 6.2 to 6.35 generate issue #4385
Comments
Hi, by default DietPi will perform an update to latest version always on first boot. For this a valid internet connection is required to complete first initial setup. Once initial setup completes, the SBC can be operated without network connection as well. But if I understood correctly,. initial setup did not complete. Correct? |
Many thanks for your report. Is there a reboot done after/during the automated update? |
Initial Setup without network connection completes, softwar update do
not complete and i can operate with the board without any further issue.
After reboot automatic software updates get launched again so i need to
skip it every time and this is not feasible for our applicaiton.
If i let the automatic update to run it gets completed successfuly and
dietpi version gets upgraded from 6.2 to 6.35 but this
DietPi-Login | Waiting for DietPi-RAMDISK to finish mounting DietPi to
RAM...
error gets generated after login.
I tested this installation serveral times, and it's fully repetitive.
The issue gets generated either i let the board update immediately at
first installation time or if i let the update run after first
installation without network.
Bests
…------ Messaggio originale ------
Da: "Joulinar" ***@***.***>
A: "MichaIng/DietPi" ***@***.***>
Cc: "orotarobas" ***@***.***>; "Author"
***@***.***>
Inviato: 17/05/2021 12:25:51
Oggetto: Re: [MichaIng/DietPi] Update from DietPi version 6.2 to 6.35
generate issue (#4385)
Hi,
by default DietPi will perform an update to latest version always. For
this a valid internet connection is required on first boot to complete
first initial setup. Once initial setup completes, the SBC can be
operated without network connection as well.
But if I understood correctly,. initial setup did not complete.
Correct?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#4385 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATBDF6XOXWLK6IRADVXSMRLTODVK7ANCNFSM45AFEPHQ>.
|
You need a valid internet connection to complete initial setup, otherwise it will re-run on every reboot trying to complete the setup |
yes, that's clear
the problem is that once i provide the internet connection and the
initial setup is completed then
DietPi-Login | Waiting for DietPi-RAMDISK to finish mounting DietPi to
RAM...
gets generated.
So the question is, how to perform initial update without having this
issue generated??
…------ Messaggio originale ------
Da: "Joulinar" ***@***.***>
A: "MichaIng/DietPi" ***@***.***>
Cc: "orotarobas" ***@***.***>; "Author"
***@***.***>
Inviato: 17/05/2021 12:34:41
Oggetto: Re: [MichaIng/DietPi] Update from DietPi version 6.2 to 6.35
generate issue (#4385)
You need a valid internet connection to complete initial setup,
otherwise it will re-run on every reboot trying to complete the setup
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#4385 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATBDF6WPDOV25HTTSMZTVX3TODWMDANCNFSM45AFEPHQ>.
|
The image is ancient, so not sure whether the update path is still intact. Let me explain what "should" happen:
In your case it didn't seem to happen like that, so please tell us how it differs, at best with the related console output, copy&pasted here, or as screenshot, or the log file: |
Actually, your NanoPi NEO image should support the NEO Core as well. Not 100% sure if the internal eMMC as system partition works, but worth to give it a try, have much newer Linux and Debian version and avoid the ancient update path: https://dietpi.com/downloads/images/DietPi_NanoPiNEO-ARMv7-Buster.7z |
As i stated in first email i already try that
the problem with that image is that not sound card are detected, even if
i configured by dietpi-config tool.
So which is better to debug audio driver not working or old version
update not working??
…------ Messaggio originale ------
Da: "MichaIng" ***@***.***>
A: "MichaIng/DietPi" ***@***.***>
Cc: "orotarobas" ***@***.***>; "Author"
***@***.***>
Inviato: 17/05/2021 13:08:09
Oggetto: Re: [MichaIng/DietPi] Update from DietPi version 6.2 to 6.35
generate issue (#4385)
Actually, your NanoPi NEO image should support the NEO Core as well.
Not 100% sure if the internal eMMC as system partition works, but worth
to give it a try, have much newer Linux and Debian version and avoid
the ancient update path:
https://dietpi.com/downloads/images/DietPi_NanoPiNEO-ARMv7-Buster.7z
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#4385 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATBDF6V52Q4Y3ITGPULCDELTOD2JTANCNFSM45AFEPHQ>.
|
I'd go with the new image and debugging the sound card issue. Does it have an onboard sound chip or is it an attached USB DAC? I see it has audio I/O pins, but not sure whether this means onboard chip or not. The other issue with the ancient image is that it's Debian Stretch, where we drop support for this year. But if you have the console output or log, we could have a look into this as well, as if there is a bug in the update path, it would be good to fix it. |
Allwinner H3 has integrated audio codec, we need to use the integrated
mic input.
what log files do you need to check it out?
Bests
…------ Messaggio originale ------
Da: "MichaIng" ***@***.***>
A: "MichaIng/DietPi" ***@***.***>
Cc: "orotarobas" ***@***.***>; "Author"
***@***.***>
Inviato: 17/05/2021 13:15:55
Oggetto: Re: [MichaIng/DietPi] Update from DietPi version 6.2 to 6.35
generate issue (#4385)
I'd go with the new image and debugging the sound card issue. Does it
have an onboard sound chip or is it an attached USB DAC? I see it has
audio I/O pins, but not sure whether this means onboard chip or not.
The other issue with the ancient image is that it's Debian Stretch,
where we drop support for this year.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#4385 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATBDF6SV4DIIEAW4R4HMDGLTOD3GXANCNFSM45AFEPHQ>.
|
Could you post the logfile at |
There you go.
Bests
…------ Messaggio originale ------
Da: "ravenclaw900" ***@***.***>
A: "MichaIng/DietPi" ***@***.***>
Cc: "orotarobas" ***@***.***>; "Author"
***@***.***>
Inviato: 17/05/2021 13:39:51
Oggetto: Re: [MichaIng/DietPi] Update from DietPi version 6.2 to 6.35
generate issue (#4385)
Could you post the logfile at
/var/tmp/dietpi/logs/dietpi-firstrun-setup.log?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#4385 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATBDF6TV3XL5ROUBPJQAVS3TOD6APANCNFSM45AFEPHQ>.
|
Pls can you attach the log on GitHub directly as it is missing if you send it via email. Thx |
Hope this works |
Okay and when you login now, you still see the "DietPi-Login | Waiting for DietPi-RAMDISK to finish mounting DietPi to RAM..." message? |
No, this version of OS has troubles with the audio driver do not detect any
audio peripheral.
The problem with RAM disk arise with another version.
But previously you suggested to check the audio driver bug instead of RAM
bug.
Do you want me to install the old version that generates the RAM issue??
Il lun 17 mag 2021, 20:59 MichaIng ***@***.***> ha scritto:
… Okay and when you login now, you still see the "DietPi-Login | Waiting for
DietPi-RAMDISK to finish mounting DietPi to RAM..." message?
Because the log file indicates that the code is up-to-date, which means
that there should be no check the RAMdisk anymore 🤔.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#4385 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATBDF6RQLCAYPXBSZ6TBRJLTOFRQDANCNFSM45AFEPHQ>
.
|
Ah okay, no all fine then, lets check the audio issue. As it's the H3 onboard chip, the kernel should contain the driver. Can you please the output of:
|
Here is consolle output:
dmesg | grep -E '(audio|snd|sound)'
[ 0.000000] Kernel command line:
root=UUID=b57cc6e3-8ac3-425b-acd0-eb5dec85d0f3 rootwait rootfstype=ext4
console=ttyS0,115200 hdmi.audio=EDID:0
disp.screen0_output_mode=1920x1080p60 consoleblank=0 loglevel=4
ubootpart=2d99deeb-01 ubootsource=mmc
usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u
sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16
[ 3.658155] No soundcards found.
aplay -l
aplay: device_list:272: no soundcards found...
…------ Messaggio originale ------
Da: "MichaIng" ***@***.***>
A: "MichaIng/DietPi" ***@***.***>
Cc: "orotarobas" ***@***.***>; "Author"
***@***.***>
Inviato: 17/05/2021 21:35:18
Oggetto: Re: [MichaIng/DietPi] Update from DietPi version 6.2 to 6.35
generate issue (#4385)
Ah okay, no all fine then, lets check the audio issue. As it's the H3
onboard chip, the kernel should contain the driver. Can you please the
output of:
aplay -l
dmesg | grep -E '(audio|snd|sound)'
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#4385 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATBDF6WQG7APHBHVGSFXQW3TOFVXNANCNFSM45AFEPHQ>.
|
okay i'll try to install the old version then to check if everything is
smooth.
…------ Messaggio originale ------
Da: "MichaIng" ***@***.***>
A: "MichaIng/DietPi" ***@***.***>
Cc: "orotarobas" ***@***.***>; "Author"
***@***.***>
Inviato: 18/05/2021 15:21:16
Oggetto: Re: [MichaIng/DietPi] Update from DietPi version 6.2 to 6.35
generate issue (#4385)
Fixed the issue with old images. Basically all DietPi versions prior to
v6.17 had v7 applied as core version so that no new update was found on
restart: b1de551
<b1de551>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#4385 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATBDF6V3KPHNQU3DC4R5IITTOJSUZANCNFSM45AFEPHQ>.
|
No wait this won't work yet! It will work when v7.2 has been released. And while it's good to have this fixed, it's not worth to actively install a Debian Stretch based image. Let's see if we can get audio working on the new one. |
okay, waiting for your good to go then.
I posted the log output of sound issue with newer image meanwhile.
…------ Messaggio originale ------
Da: "MichaIng" ***@***.***>
A: "MichaIng/DietPi" ***@***.***>
Cc: "orotarobas" ***@***.***>; "Author"
***@***.***>
Inviato: 18/05/2021 15:29:07
Oggetto: Re: [MichaIng/DietPi] Update from DietPi version 6.2 to 6.35
generate issue (#4385)
>okay i'll try to install the old version then to check if everything
>is
>smooth.
>
No wait this won't work yet! It will work when v7.2 has been released.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#4385 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATBDF6XSLTSUI7XT3F3EXMDTOJTSHANCNFSM45AFEPHQ>.
|
Okay, please edit You find all device tree overlays in You seem to know the board already, but for others, here is the GPIO/pin layout: http://wiki.friendlyarm.com/wiki/index.php/NanoPi_NEO_Core#Layout |
Did the modifications and i can confirm everything works smooth.
i have my last three questions then we're all set
I need to setup the board so our application gets launched automatically
at board boot, reading the docs i tried a couple of config but something
odd:
1) if i select option 14 i setup the script in
/var/lib/dietpi/dietpi-autostart/custom.sh, it works properly but only
after login (which i have to perform manually)
2) I run dietpi-config and selected option 7 but it still requires me to
enter login credentials after boot and do not perform the script i
configured at point 1
Please let me know how to sort this out
Last question is about mac address:
if i perform cat /sys/class/net/eth0/address i notice mac address
changes after every reboot.
I was assuming it shoud be fixed and unique by hardware transceiver, can
you explain why?
Bests
…------ Messaggio originale ------
Da: "MichaIng" ***@***.***>
A: "MichaIng/DietPi" ***@***.***>
Cc: "orotarobas" ***@***.***>; "Author"
***@***.***>
Inviato: 18/05/2021 15:45:35
Oggetto: Re: [MichaIng/DietPi] Update from DietPi version 6.2 to 6.35
generate issue (#4385)
Okay, please edit /boot/armbianEnv.txt and append analog-codec to the
overlays= line, then reboot. Onboard audio seems to be disabled by
default on H3 boards with this kernel/device tree setup, the related
device tree overlay enables it.
You find all device tree overlays in /boot/dtb/overlay/, the ones with
sun8i-h3- prefix, enabling further features. Add the name without
prefix and file extension to the /boot/armbianEnv.txt overlays line, so
e.g. "uart1" to enable the 1st UART device for serial console or such.
You seem to know the board already, but for others, here is the
GPIO/pin layout:
http://wiki.friendlyarm.com/wiki/index.php/NanoPi_NEO_Core#Layout
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#4385 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATBDF6R5L3ZOHZEVYVTWHOTTOJVP7ANCNFSM45AFEPHQ>.
|
Option 7 still requires you to manually login? Or do you speak of SSH? Note that this means login at local terminal console TTY1, so the one you reach when connecting a screen and keyboard. SSH autologin would need to be configured with the SSH client, the server has no charge on this. When choosing option 7, away from option 14, the custom script service is removed, so that is expected, but as said, autologin is not required for it to start. If the task you need to run is not a long-term background job, you can have it executed as well by adding a script to
The changing MAC address is indeed something common on those Allwinner SoCs: #3618
Replacing If those have no effect, then there is a second solution:
Same here, replacing |
Sorry for my late answer
1) i can confirm /var/lib/dietpi/dietpi-autostart/custom.sh works
autonomously, it was just a matter of initial delay
2)i'm using debug terminal consolle on TTYS0, the default one, and
option 7 doesn't work, do not allow me to autologin
3)i checked mac setup as you suggested and i can confirm it works
so 1+3 solves our need, thanks for your precious support we can move on
to production with our board NanoPI Dietpi powered.
Bests
…------ Messaggio originale ------
Da: "MichaIng" ***@***.***>
A: "MichaIng/DietPi" ***@***.***>
Cc: "orotarobas" ***@***.***>; "Author"
***@***.***>
Inviato: 19/05/2021 22:27:50
Oggetto: Re: [MichaIng/DietPi] Update from DietPi version 6.2 to 6.35
generate issue (#4385)
/var/lib/dietpi/dietpi-autostart/custom.sh should actually run
interdependently of the login. It might be a coincidence that it ran
afterwards, but when you wait a little longer it should run by itself.
It is an own systemd service (systemctl status dietpi-autostart_custom)
that runs independently from the login.
Option 7 still requires you to manually login? Or do you speak of SSH?
Note that this means login at local terminal console TTY1, so the one
you reach when connecting a screen and keyboard. SSH autologin would
need to be configured with the SSH client, the server has no charge on
this. When choosing option 7, away from option 14, the custom script
service is removed, so that is expected, but as said, autologin is not
required for it to start.
If the task you need to run is not a long-term background job, you can
have it executed as well by adding a script to
/var/lib/dietpi/postboot.d. This can be also the custom.sh you used
before:
mv /var/lib/dietpi/dietpi-autostart/custom.sh /var/lib/dietpi/postboot.d/custom.sh
The changing MAC address is indeed something common on those Allwinner
SoCs: #3618 <#3618>
First please try to set it via boot config by adding the following two
lines to /boot/armbianEnv.txt:
ethaddr <mac_address>
eth1addr <mac_address>
Replacing <mac_address> with the actual one you want to have, at best
the currently used one so that it's assured to be a valid mac. Then
reboot.
If those have no effect, then there is a second solution:
echo 'SUBSYSTEM=="net", KERNEL=="eth0", ACTION=="add", RUN+="ip l set dev eth0 address <mac_address>"' > /etc/udev/rules.d/99-eth0-mac.rules
Same here, replacing <mac_address> with the actual one you want to
have.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#4385 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATBDF6V35OTDPQSAPKN3QNTTOQNMNANCNFSM45AFEPHQ>.
|
Okay that makes sense. The console autologin sets this up on tty1 only, not ttyS0. But you could manually setup autologin there:
But this has no effect on any
Did editing |
The upgrade issue for old images has been solved. I'm marking this hence as closed. Feel free to reopen if required. |
Hello
i tried again the installation beginning from old image but it still
fails.
…------ Messaggio originale ------
Da: "MichaIng" ***@***.***>
A: "MichaIng/DietPi" ***@***.***>
Cc: "orotarobas" ***@***.***>; "Author"
***@***.***>
Inviato: 02/06/2021 15:48:33
Oggetto: Re: [MichaIng/DietPi] Update from DietPi version 6.2 to 6.35
generate issue (#4385)
The upgrade issue for old images has been solved. I'm marking this
hence as closed. Feel free to reopen if required.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#4385 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATBDF6Q3FHSNW252H3CTLLDTQYZDDANCNFSM45AFEPHQ>.
|
Can you share the output of the install process up to where it failed? |
Here are all the logs files. dietpi-firstrun-setup.log |
The download if the version file failed, but there is no related curl error message. From the error prompt, you should be able to exit to the shell. Would be interesting to try manually downloading this file from there: cd /tmp
curl -sSfL https://raw.githubusercontent.com/MichaIng/DietPi/master/.update/version -o version
echo $? # check exit code |
Creating a bug report/issue
Required Information
I'm using NanPi Neo Core for our industrial embedded application, I can succesfuly install the dietpi image provided on the manufacturer repo here https://drive.google.com/file/d/1FTJpsptgWkUFHprD1RLUBXOSCXyVaLWH/view?usp=sharing.
If I perform the installaton without any network connection, and the system boots properly.
Since at boot the tool dietpi-software gets automatically invoked, if i connect the network interface the dietpi gets updated to the newer version 6.35, but after that after login i start getting this message:
"DietPi-Login | Waiting for DietPi-RAMDISK to finish mounting DietPi to RAM..."
this keeps going in an infinite loop till i press control-C.
Since the application needs to be autolaunched after board boot this behaviour is not acceptable, so i would like to know how to prevent dietpi-software to be automatically invoked.
I tried also to use the new dietpi version built for Nanopi Neo, but that version has issues with audio drivers that the 6.2/6.35 doesn't have.
The text was updated successfully, but these errors were encountered: