Jump to content

Apt Upgrade causes Rock Pi S not to boot [Armbian 24.11.1]


Recommended Posts

Posted (edited)

Hi everyone,
 

I've been working with Armbian for a while on my Rock Pi S, I got to a stable situation on version 24.11.1 with kernel 6.6.63 where everything worked perfectly... but recently this last week I applied an apt upgrade, which applied strong base modifications (linux-current-rockchip64 and dtbo going from 24.11.1 to 24.11.3), after applying this update and rebooting, I can't get it to boot again, either from the Micro SD or from the eMMC installation.


I wanted to report this bug, but I don't have a TTL cable at hand to be able to do the corresponding debugging...


I've tried to flash older versions, or even flash the 24.11.1 version again but I need the audio fix for kernel 6.6.63, which doesn't apply after the last upgrade coincidentally.


For work reasons I need to get this SBC up and running...


Any solution for this?

Thanks for all.

Edited by Truenox
  • Truenox changed the title to Apt Upgrade causes Rock Pi S not to boot [Armbian 24.11.1]
Posted

Sorry to hear this.  I should have time to look into next week.

Are you using Debian or Ubuntu?

Exactly which image did you start from?

(Can you provide a link to the image?)

 

Did you try a fresh install of the latest stable image?

 

Posted

Hello brentr,

 

I downloaded the image from the official website, right from Rock Pi S:

 

https://www.armbian.com/rockpi-s/

 

Initially and in the most stable version possible I had the noble server CLI version installed, but as it failed and I couldn't get it to boot again, I performed clean installations of both systems, both Debian Bookworm and Ubuntu Noble and in both cases the same failure occurs, after performing an apt upgrade from a clean installation and executing a reboot, it bricks and doesn't boot.

 

From the desperation of these days... I even tried Trixie and Oracular thinking that a more recent version could solve the problem, and directly these images don't work, they didn't boot either.

 

Thinking it might be a problem with the recent u-boot tool updates, I repeated this whole process, installing it on the eMMC, with the same result.

 

The feeling is that some base package has been touched, corrupting the installation. I'd like to provide the logs for further help, but as I mentioned, I don't have a TTL serial cable handy to debug, so I'll have to have one.

 

So I found myself in a loop with no way out, so I appreciate the quick response to solve this problem.

 

Thanks.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines