SteeMan
-
Posts
1459 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by SteeMan
-
-
Moved post to Libre Renegade forum
-
Do you have the boot log from the uart port? If so please post, if not I'd suggest you capture the boot console messages to see which step of the boot process is taking the time.
-
This board isn't a supported by Armbian. Moved to Community Supported/Unmaintained section of forums.
-
The contents of those packages are not isolated to /boot. For example the linux-image packages installes the kernel modules in /usr/lib/modules, and linux-u-boot puts binary information on the boot disk that isn't in the file system (it is on the raw disk). So it isn't as simple as copying a few files to /boot. But without knowing if this is a kernel issue or a uboot issue it is difficult to guess where to start.
-
First off, (and you likely know this already), Armbian doesn't support userspace upgrades to newer distributions. (But they usually work in my experience). Second, you are running on a board that Armbian doesn't support. It is a community supported board, which means that no Armbian resources are put in this board, it is soley maintained (or not maintained) by volunteers in the community.
On to your issue. You are going to need to capture the boot log to see where it is failing to boot. You need to hook up a usb uart connector to your board to capture the boot output.
I would also suggest trying to fresh install on your board to make sure that your target release actually works on your board at all (don't want to spend a lot of time debugging an upgrade issue, if it isn't an upgrade issue, and is just an issue in the current release).
-
@ReneHegewald I'll add a couple of points to what @Werner has already mentioned.
The board you are using RockPi 5B is not supported by Armbian. It is Community supported. That means Armbian doesn't have any resources that work on this board. All support for the board is done by community members like you. There generally is little that happens to community supported boards. Usually someone will submit some work to get the board initially setup and then shortly after disappear and nothing happens to the board again until it stops building at all and then it gets dropped. Unfortunately this is the reality of support for these boards. You are using software for free and it takes significant resources (both money and time) to make a board work well. There are very few people that are willing to donate a hundred hours of time to work on getting a board fully supported and maintain it over time with no compensation. Unfortunately the manufactures of these boards take advantage of the open source community. They in house initially do some minimum work to get something running, then once released move on to their next board and don't support the software and hope the open source community does it for free.
The best thing you can do, is build up your skills and contribute back to the community in exchange for the free software you are using.
-
35 minutes ago, PmProd379 said:
On github.com.
What link on github? There are alot of non-armbian builds out there that are named armbian.
-
@PmProd379Armbian_24.5.0_amlogic_s905x3_bullseye_5.15.152_server_2024.03.16.img.gz
That is not an Armbian build. No Armbian builds have that name. Where did you download that from?
-
If you want to dig deeper into this, you will need to find the uart pins on the board, hookup USB uart connector and capture the boot messages to see what is actually happening when booting.
Since I don't have this board nor know of anyone that has tried running Armbian on that board.
-
I haven't seen any reports of users having success with that particular cpu, so I have no idea if it will work.
What build are you using?
-
Moved to correct forum and added rock64 tag.
-
Actually the forums are what you want to follow. The forums are the board issue logging system. Github issues are only for build system issues. If the r2s and r2s plus are boards you can help with (they are community maintained and don't have any Armbian staff support). You can fix issues on them and submit PRs to improve them.
-
@Thom Debian Buster (aka Debian 10) was EOL 2022-09-10 (and it ends its extended support life 2024-06-30). Armbian hasn't supported Buster with updates for a long time and recently set its status to EOL. You can ignore the error message, as there would be no updates to get from Armbian anyway. You need to move to a more current supported distribution.
-
@Caio Lima Viana If you post pictures of the front and back of your board, someone on here may be able to identify the uart connection points
-
-
My suggestion since I assume you don't have an armbianmonitor output from before your upgrade, would be to use armbian-config and go back to a 6.1 kernel and see if it is the kernel that is causing the difference. If so then provide an armbianmonitor output with the old kernel and look at the memory info in the output to see where the difference is.
-
@lululombard I think this whole discussion needs to be moved to a new thread as this thread is about the Banana PI. Can you state what you are trying to accomplish? I can then move these posts to a new thread named according to what you are trying to do. It seems as if you are just trying to use 3d accelleration (which should be present for rk3399 out of the box on recent kernels). I think you may be following very old instructions that are no longer relevant. So again state what you are trying to accomplish with your RockPro64.
-
@lululombard So the historic images for the RockPro64 still exist in the archives. So I was going to suggest that you could extract the kernel from the images and manually apply the kernel. But in looking at the images, and your request above, it looks like the images contain the rockchip64 kernel and you are wanting to use the media kernel. I'm not sure why that is, as I'm not aware of the media kernel every being supported for this board. But you could take that strategy of finding an historic image for a board that supported the media kernel, and copy over the relevant files (/boot/dtb, /boot/Image, /boot/uinitrd and /lib/modules/<kernel>)
-
@lululombard There haven't been any updates coming from Armbian on buster for a while now. So just remove the repository or ignore the messages.
-
The Armbian repository has moved focal to EOL. That only means you will no longer receive any updates for the Armbian specific packages (like kernel, uboot, etc). Ubuntu still supports Focal for a couple more months so you will still receive any package updates that Ubuntu releases for userspace packages. But in a couple of months that will end as well. So you should be planning an upgrade to something more current as focal is now 4 years old.
-
-
@KanexMarcus I only have two suggestions: Try different SD cards (especially a lower capacity card if you are using a high capacity sd card. Try other dtb files. I don't have that box so can't help beyond generic suggestions.
-
How many times do I have to say, it isn't possible to do with Armbian builds. Armbian does not have a uboot for your TV Box. So there is no way for you to boot from something other than your emmc unless you have a uboot built for your box. And since Armbian doesn't produce such code, we can't help you here.
-
There is no current TV Box work being done to support s805 nor has there been for years.
Radxa Pi Zero does not boot from eMMC if USB drive is connected
in Radxa Zero
Posted
@Sab44 please submit a PR with this change