SteeMan
-
Posts
1703 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by SteeMan
-
-
Don't know, as I am fine with using the IP address so never researched further. I suspect it is a timing issue between DNS starting and wireguard starting.
-
1 hour ago, BOFFBOY said:
Nov 30 00:05:18 orangepi5-plus wg-quick[1338]: Name or service not known: `myipaddresshereremoved.com:51820'
This is likely the error you are running into. Is that your valid domain name for your wireguard server?
I have had issues with wireguard starting before DNS name resolution is in place which I resolved by using IP addresses in the wireguard config files instead of domain names.
-
Have you tried what I suggested to you previously? https://forum.armbian.com/topic/27210-how-to-install-armbian-to-amlogic-s805-android-box/#findComment-163422
-
So according to your last comment you are using a custom dtb file. You do know that installing a new kernel version deletes the entire dtb directory and replaces it with what is shipped with that kernel version?
So if you have a custom dtb it may be the issue that it is being removed during the upgrade. You need to put a custom dtb file in a location not under /boot/dtb.
I don't know if this is your issue or not, but I thought of that based on the information in your last post.
Another suggestion, is to put a current image on an SD card and see that that boots. That way you can determine if the issue is with the current code, or something that is happening during the apt upgrade.
-
All you should need to do is the standard debian process to apply updates regularly: apt update followed by: apt upgrade
-
1 hour ago, Hans Kurscheidt said:
just to learn, that I'm stuck again w/ Armbian. something w/ "unknown compression"
-
9 minutes ago, Lucas Vasconcelos said:
So, I saw the option to use the su reboot reset command in a YouTube video.
I honestly have no idea if the mechanism behind that android command will work in the current aml-s9xx-box Community Armbian builds. I've never tested that method, nor have any familiarity with how it works.
-
1 hour ago, Lucas Vasconcelos said:
One note is that the chip is labeled S905L, even though the advertisement claims it's an S905X2, and the hardware verification app also indicates S905X2.
Very common. I'd bet it is an S905L and the Android firmware is reporting false information. Happens all the time on cheap TV boxes. They will also falsely report the RAM and storage amounts falsely too.
-
1 hour ago, Lucas Vasconcelos said:
To attempt the boot, I am using an Android terminal app with the command:
su reboot update
But it always goes to the recovery screen. I also tried through the update app, but the USB drives or SD cards I used do not appear in the Android TV Box, even though their folders show up in the recovery menu.
This isn't in the installation instructions you referenced. Why are you trying to do this?
-
Moved post from Supported to Community Maintained and adjusted the tag to reflect the correct board
-
According to your armbianmonitor output you are not using Armbian but an Ophub build. Ophub is a fork of Armbian, they do not participate in Armbian development nor these forums. You need to direct your question to their forums/support.
-
Moved to community support section and added BPI M1 tag.
-
22 minutes ago, Hans Kurscheidt said:
OK, I can certainly do this, but is this supposed 2b the "normal way" or isn't there an issue w/ signing the package, so that "normal" apt ops would do the trick?
I think you have to go back to earlier in this thread where Igor stated:
20 hours ago, Igor said:From this I can only see that you are using a code that is not supported on a hardware that is not supported.
I think there is information you are not including about your setup. The first screenshot indicates you are/were running Buster as the screenshot says "Debian end of life (Buster)". Then later screenshots indicate you are running Bullseye. It looks like you have attempted to upgrade from Buster to Bullseye during this process. Armbian doesn't support userspace upgrades. An error in doing an upgrade like that would potentially leave your apt signing keys out of sync.
-
@Wizzard The boot environment is stored on emmc. So when you boot (enable multiboot via holding the reset button) that is setting certain variables in the u-boot environment and persisting them there (which is on emmc). That is why you only need to press the reset button the first time you boot Armbian or any other distribution. But the way that the distributions setup the boot environment are different (and usually not compatible) - even the Armbian legacy stuff from balbes150 changed how it was done (in incompatible ways) a number of times over the years.
So without knowing what has been changed in the u-boot environment that is stored on emmc, it is impossible to really support people. So there is a check in the Armbian code that looks for certain changes that indicate something else has run and then fails the boot.
-
Find the android firmware and restore according to manufactured instructions. Is the non helpful answer. You are going to have to Google search how it can be done for your specific box.
But at the end of the day, what are you trying to accomplish? It is likely that that custom fork works better than Armbian will on that TV box. As it looks like that fork was created to get wifi and other things for that box working. Using generic Armbian you most likely won't have Wifi or many other features working. (Have you read the TV box faq on what to expect from Armbian)
-
@Wizzard where do you see Armbian in that url?
Looking at that GitHub link, that is clearly a fork of Armbian. That build has 175 changed files from the Armbian version it was forked from. You could say that it used a three year old version of the Armbian build framework, but the image built has no similarities to the aml-s9xx-box Armbian community builds you are trying to install.
-
4 hours ago, Wizzard said:
Sunvellt95zplus_Debian_sid_5.12.9_xfce.img
That is not an Armbian build. Where did you get that build from? The Armbian download pages?
-
@Wizzard Notice it says "run" not "installed on emmc". Running from SD card is running it. If you have run another non-Armbian build (which you have from the SD card) then you need to reinstall android firmware to run Armbian. That isn't a guarantee that Armbian will work, but is a necessary place to start from.
-
37 minutes ago, Wizzard said:
Sorry, how did you manage to boot it? I am trying the latest community build Armbian_community_25.2.0-trunk.13_Aml-s9xx-box_bookworm_current_6.6.60_minimal.img and it does not boot at all.
Are you following the installation instructions linked to from the download page: https://www.armbian.com/amlogic-s9xx-tv-box/
The most common issue is people ignoring the following: "Note: If you have previously run other distributions on the box such as coreelec the below installation will not work. You will need to restore the original android firmware before attempting the install. coreelec changes the boot environment in ways that are incompatible with these Armbian builds."
So have you previously used any build other than a genuine armbian build downloaded from the official download page? If so, you need to reinstall a clean android firmware to reset the environment to what the armbian build expects.
-
4 hours ago, dreamlayers said:
Why is so much of the eMMC unused at the start? In the old script, the first partition starts at 700M (M = million bytes), and in Armbian 23.11.1, that has been increased to 1000M.
It has been 1000M since the aml-s9xx-box community builds were introduced two years ago. (https://github.com/armbian/build/commit/8dcab2be64c253ed6554fbcd32d901ed6c882ead#diff-4ab8640d43fd31e3a33d5d74c4723e7004b0aeb107b4d573597c2be4221a654f)
The value was inherited from the previous work done by balbes150.
The reason that this space is preserved on the emmc is because various parts of the native android u-boot use various data in this space, and it seems to vary on different tv boxes how much space is being used. There are android partitions that store things like the android boot screen, etd. Over time by trial and error this 1000M safety buffer was chosen as seeming to work on all (or at least most) tv boxes.
-
I would suggest you consider a hybrid approach. Boot partition on SD and root partition on emmc. Leave the uboot on the SD card and only transition the rest to emmc. You get the benefits of performance you are looking for (as everything other than uboot is running from emmc), but you don't have the complexities of switching your boot environment from SD to emmc all in a script. Basically you on first boot need to format your emmc, copy the root filesystem over and adjust your fstab and armbianenv.txt entries to point to the new location of your root partion. Now that itself doesn't come with protential issues, but that is a valid way to have Armbian configured (I think it is an option in armbian-install to have boot and root partitions on different media).
There is a script that the amlogic tv box builds use: https://github.com/armbian/build/blob/main/config/optional/boards/aml-s9xx-box/_packages/bsp-cli/root/install-aml.sh
This script is just a fairly simple example of the steps involved in moving from SD to emmc, with some very specific amlogic tvbox stuff mixed in. It may be a good starting point to think from (as opposed to armbian-install which is a lot more complex as it is generically handling a bunch of different requirements)
-
9 hours ago, going said:
This will be a fork that will return the code to the parent project https://github.com/armbian/build ?
Or is it planned to be developed as an independent project based on this branch?
I was thinking of asking the same question.
Personally my feeling is if you are planning on helping Armbian by working to incorporate your efforts back into Armbian then I strongly encourage your efforts. But I would recommend working with the Armbian developers on how you plan to do this, as it can be frustrating for you if you put in a lot of work into something, only to find disagreement from the Armbian community about how you are implementing something that might prevent it from being accepted.
If your intention isn't to incorporate your work back into Armbian, then you are creating just another fork (like the many that already exist), which you are entitled to do since this is open source. But in that case I would request that you not use the limited Armbian resources to do that (i.e. our developers and infrastructure like these forums). These forums are for Armbian developers and users, not for use by forks of Armbian that just attempt to take from Armbian without contributing back.
-
You need to be more specific on the CPU. What you have mentioned is a type of cpus, you need to specify the exact CPU you are interested in. Also you need to specify the exact box you are considering as well.
And also you need to explain what you are looking to use the box for. Note tjay even the best supported boxes don't have everything working. So often wifi won't work and don't expect to use these as desktop computer replacements. But they often work well for servers.
-
Please share the source dts along with the binary format. That way someone, perhaps you, can submit a PR and have it incorporated into Armbian.
vontar x3, S905x3 does not boot after apt upgrade
in Amlogic CPU Boxes
Posted
multiboot means different things in different contexts. But in this context it is the process that is used for amlogic based tv boxes to get the native Android uboot on the emmc to boot armbian from SD card. The process is to press the reset button with the SD card inserted which causes the native uboot to look for a certain file on the SD card which is then read and adjusts the uboot environment so that future boots will first boot from the SD card.