search

NeonGeckoCom / neon_debos

Debos build files for Neon OS
Apache License 2.0
1 stars 8 forks source link

[BUG] Mark2 recommended img - shutdown error(s) #147

Open Olzeke51 opened 7 months ago

Olzeke51 commented 7 months ago

Description

Using a microsdc or a USBstick - 1) I get rPi console error messages ; 2) upon pwr cycling/restart usually get 3 reboots then other errors a) gui not started -but ssh/mana works b) will get 1 'hey neon'/green ring -no response * admin.log.gz audio.log.gz bus.log.gz enclosure.log.gz gui.log.gz log2ram.log.gz neon-utils.log.gz ngi_user_info.yml.gz ' situation.5.gz ' skills.log.gz uid-msg_2024-04-21_10-03-12.png.gz voice.log.gz

Steps to Reproduce

start with a fresh 'recommended_mark2.iso' copied via ddrescue -d -f will use ssh , mana say-to "run updates" , use mana say-to "yes" to acknowledge audio prompt and it updates, 'neon ai is ready" - mana works with audio feedback/green ring **attempted an ovos-docker install and was told I had a network connection that failed the install

Relevant Code

No response

Other Notes

No response

Olzeke51 commented 7 months ago

okay - I started debian-neon-image-rpi4_2024-04-08_16_58.img.xz from a USB-stick (created by rPi imager) had a serial console connected to default pi ttyS0 (afaict) and got this info on it: [I assumed it was on shutdown !!]

neon login: [  173.321815] ext3: Unknown parameter 'uid'
[  173.336118] ext2: Unknown parameter 'uid'
[  173.340502] ext4: Unknown parameter 'uid'
[  173.345618] squashfs: Unknown parameter 'uid'

More information - that's all Gary

Olzeke51 commented 7 months ago

Still Mark2 image but the 24.4.08 version ; both recommended & 4.08 have the 'uid' error found in the systemd journal logs a possible source for it - - see attached portion of the journal

sysd_uid.txt

Olzeke51 commented 7 months ago

upgraded to 24.5.1b1

did a 'shutdown' from the pulldown menu had 5 (or 6?) of these reboots: after a gui image of 'something went wrong'

[   26.316279] register platform device 'asoc-simple-card': 0

Debian GNU/Linux 12 neon ttyS0

neon login: [   49.376108] watchdog: watchdog0: watchdog did not stop!
[   49.499460] systemd-shutdown[1]: Could not detach loopback /dev/loop0: Device or resource busy
[   49.508367] watchdog: watchdog0: watchdog did not stop!
[   49.515854] systemd-shutdown[1]: Failed to finalize loop devices, ignoring.
[   49.615383] reboot: Restarting system with command 'now'

finally got to a gui image 'unable to start gui' and this was on the rpi-console output

[   26.417581] register platform device 'asoc-simple-card': 0

Debian GNU/Linux 12 neon ttyS0

neon login: [  128.817686] ext3: Unknown parameter 'uid'
[  128.824383] ext2: Unknown parameter 'uid'
[  128.837875] ext4: Unknown parameter 'uid'
[  128.842219] squashfs: Unknown parameter 'uid'
NeonDaniel commented 5 months ago

Searching for this, I don't think the "uid" logs are related to any issue; I see them also in working images. I'm not sure where those arise from, but it doesn't appear to be in any of this code and should be safe to ignore as the file systems have all been mounted by the time they're showing up in dmesg