Booting Issues

[Halfgreek]

I just receved my new PineNote 2 days ago with Debian installed and was working well with it until I woke up yesterday and the device will not boot into anything, The display remains at "Booting..." or "PineNote is Booting" and i am unable to get to Uboot or anything to see what I can do to fix it. Any Suggestions?

[bills2002]

I just receved my new PineNote 2 days ago with Debian installed and was working well with it until I woke up yesterday and the device will not boot into anything, The display remains at "Booting..." or "PineNote is Booting" and i am unable to get to Uboot or anything to see what I can do to fix it. Any Suggestions?

Did you get this resolved?
I have not used the debug dongle but if a long power reset does not fix it, then I'd dive into the debug instructions.
I did have some odd reboots after applying the last software update.  They corrected themselves luckily.

Do you get the boot menu where you see the big square buttons and you cycle through them?

Bill
ps- I have to figure out the debug dongle to try flashing some other distributions.  I think the debug dongle will help you discover if this is a software issue that a reflash may fix or if it's a hardware issue.

[Halfgreek]

Thank you for your rely. Yes I tried the long power boot and all I get is the big buttons to boot from Debian Boot OS1 or OS2, Boot Menu Entry3, or search for extlinux.config on all partitions as choices. Nothing will boot after choosing one of those options. I also tried the UART dongle , but I don't know if I need to solder the wiring as suggested on the Pine64 website. I'm not even sure that is going to fix this particular issue or not. I am not 100% sure what I am suppose to do with the dongle.

[maxaltepo]

Same issue Here
trying to make some sense on

Code:

journalctl --boot-1 info

Response

Code:

...skipping...
Dec 25 11:11:28 pinenote sudo[1097]: pam_unix(sudo:session): session opened for user root(uid=0) by user(uid=1000)
Dec 25 11:11:28 pinenote wireplumber[777]: spa.bluez5.native: RegisterProfile() failed: org.bluez.Error.NotPermitted
Dec 25 11:11:28 pinenote wireplumber[777]: spa.bluez5.midi: org.bluez.GattManager1.RegisterApplication() failed: GDBus.Error:org.bluez.Error.AlreadyExists: Already Exists
Dec 25 11:11:28 pinenote wireplumber[777]: spa.bluez5.native: RegisterProfile() failed: org.bluez.Error.NotPermitted
Dec 25 11:11:28 pinenote sudo[1097]: pam_unix(sudo:session): session closed for user root
Dec 25 11:11:29 pinenote systemd[752]: Activating special unit exit.target...
Dec 25 11:11:29 pinenote systemd[752]: Stopped target default.target - Main User Target.
Dec 25 11:11:29 pinenote systemd[752]: Stopping dbus.service - D-Bus User Message Bus...
Dec 25 11:11:29 pinenote systemd[752]: Stopping filter-chain.service - PipeWire filter chain daemon...
Dec 25 11:11:29 pinenote systemd[752]: Stopping gnome-keyring-daemon.service - GNOME Keyring daemon...
Dec 25 11:11:29 pinenote systemd[752]: Stopping mpris-proxy.service - Bluetooth mpris proxy...
Dec 25 11:11:29 pinenote systemd[752]: Stopping pipewire-pulse.service - PipeWire PulseAudio...
Dec 25 11:11:29 pinenote systemd[752]: mpris-proxy.service: Main process exited, code=exited, status=1/FAILURE
Dec 25 11:11:29 pinenote systemd[752]: mpris-proxy.service: Failed with result 'exit-code'.
Dec 25 11:11:29 pinenote systemd[752]: Stopped mpris-proxy.service - Bluetooth mpris proxy.
Dec 25 11:11:29 pinenote systemd[752]: Stopped pipewire-pulse.service - PipeWire PulseAudio.
Dec 25 11:11:29 pinenote systemd[752]: Stopping wireplumber.service - Multimedia Service Session Manager...
Dec 25 11:11:29 pinenote wireplumber[777]: wireplumber: stopped by signal: Terminated
Dec 25 11:11:29 pinenote systemd[752]: Stopped gnome-keyring-daemon.service - GNOME Keyring daemon.
Dec 25 11:11:29 pinenote systemd[752]: Stopped dbus.service - D-Bus User Message Bus.
Dec 25 11:11:29 pinenote wireplumber[777]: wireplumber: disconnected from pipewire
Dec 25 11:11:29 pinenote wireplumber[777]: pw.core: 0xaaaace130220: leaked proxy 0xaaaace27ebb0 id:3
Dec 25 11:11:29 pinenote wireplumber[777]: pw.core: 0xaaaace130220: leaked proxy 0xaaaace28e8b0 id:5
Dec 25 11:11:29 pinenote wireplumber[777]: pw.core: 0xaaaace130220: leaked proxy 0xaaaace2772f0 id:6
Dec 25 11:11:29 pinenote systemd[752]: Stopped filter-chain.service - PipeWire filter chain daemon.
Dec 25 11:11:29 pinenote systemd[752]: Stopped wireplumber.service - Multimedia Service Session Manager.
Dec 25 11:11:29 pinenote systemd[752]: wireplumber.service: Consumed 2.248s CPU time, 13.3M memory peak.
Dec 25 11:11:29 pinenote systemd[752]: Stopping pipewire.service - PipeWire Multimedia Service...
Dec 25 11:11:29 pinenote systemd[752]: Stopped pipewire.service - PipeWire Multimedia Service.
Dec 25 11:11:29 pinenote systemd[752]: Removed slice session.slice - User Core Session Slice.
Dec 25 11:11:29 pinenote systemd[752]: session.slice: Consumed 2.956s CPU time, 24.2M memory peak.
Dec 25 11:11:29 pinenote systemd[752]: Stopped target basic.target - Basic System.
Dec 25 11:11:29 pinenote systemd[752]: Stopped target paths.target - Paths.
Dec 25 11:11:29 pinenote systemd[752]: Stopped target sockets.target - Sockets.
Dec 25 11:11:29 pinenote systemd[752]: Stopped target timers.target - Timers.
Dec 25 11:11:29 pinenote systemd[752]: Closed dbus.socket - D-Bus User Message Bus Socket.
Dec 25 11:11:29 pinenote systemd[752]: Closed dirmngr.socket - GnuPG network certificate management daemon.
Dec 25 11:11:29 pinenote systemd[752]: Closed gcr-ssh-agent.socket - GCR ssh-agent wrapper.
Dec 25 11:11:29 pinenote systemd[752]: Closed gnome-keyring-daemon.socket - GNOME Keyring daemon.
Dec 25 11:11:29 pinenote systemd[752]: Closed gpg-agent-browser.socket - GnuPG cryptographic agent and passphrase cache (access for web browsers).
Dec 25 11:11:29 pinenote systemd[752]: Closed gpg-agent-extra.socket - GnuPG cryptographic agent and passphrase cache (restricted).
Dec 25 11:11:29 pinenote systemd[752]: Closed gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation).
Dec 25 11:11:29 pinenote systemd[752]: Closed gpg-agent.socket - GnuPG cryptographic agent and passphrase cache.
Dec 25 11:11:29 pinenote systemd[752]: Closed pipewire-pulse.socket - PipeWire PulseAudio.
Dec 25 11:11:29 pinenote systemd[752]: Closed pipewire.socket - PipeWire Multimedia System Sockets.
Dec 25 11:11:29 pinenote systemd[752]: Closed pk-debconf-helper.socket - debconf communication socket.
Dec 25 11:11:29 pinenote systemd[752]: Removed slice app.slice - User Application Slice.
Dec 25 11:11:29 pinenote systemd[752]: Reached target shutdown.target - Shutdown.
Dec 25 11:11:29 pinenote systemd[752]: Finished systemd-exit.service - Exit the Session.
Dec 25 11:11:29 pinenote systemd[752]: Reached target exit.target - Exit the Session.
Dec 25 11:11:29 pinenote (sd-pam)[756]: pam_unix(systemd-user:session): session closed for user user

this is after a reboot not even an update
the note was sleeping after 10 secs when using so decided to reboot and BAM!! no desktop now XD
if there is any idea of how to address/debug the issue please let me know

[bills2002]

Any luck on getting your desktop back?

I am trying to get the dongle working...to get to rkdeveloptool...to reflash to stock.
From linux minicom dongle works...if the PN boots (not to desktop but acts like it's going there). I can get a login and use it.
The dongle has yet to show me any of the u-boot console except garbage characters.
Still fighting it.

---

To expand on my boot issues:
- apt-get update, install, ... to attempt to get X11 going
- switched off autologin in wayland/gnome/settings
- lost wayland ie no desktop
- would boot show some text, flash the squares Pine 64 background
- tried dongle
- had dongle working for a bit for the OS ie I got on, found I had wifi, and scp'd some stuff off. (linux debian 12 desktop, minicom)
- never saw u-boot stuff in minicom. When it was supposed to show...got corrupted characters
- Followed the instructions and ran bash install_stable_1056mhz_uboot.sh
- I think this is what killed the dongle from working
- now no matter what I boot how, I just get to the u-boot selection screen, end up on a Pine64 squares but nothing shows up on the serial console.

$400 is a lot to shell out for this. We must have a method to reset back to zero. Possibly a fixed rom and a reset button. Perhaps a SD card?
Should not be able to brick a device given the steps above.

Help?

[vlagged]

Same issue Here
trying to make some sense on

Code:

journalctl --boot-1 info

Thanks for showing up with logs, so this is with UART dongle root connection? It is somewhat incredible that between session start and session end for root only bluetooth error appear in logs, like that would be a required device/serivice..