SteeMan
-
Posts
1387 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Community Map
Posts posted by SteeMan
-
-
An external usb wifi adapter should generally work. The key being that the linux kernal has the required driver/module to support that usb driver. Generally any common wifi adapter will have linux kernel support. I would avoid trying to get the cheapest usb wifi adapter you can find, as those are more likely in my experience to not have linux support.
Making sure that I am providing a complete answer to your question, the lack of support for the internal wifi on TV boxes is unrelated to support for any specific usb wifi adapter.
-
Your box only has 1GB. If you googled the part number on you memory chip from the photos (D9PSC) you could have found from specs that these are 2Gb chips and you have four on the board. So 4x 2Gb = 8Gb = 1GB
-
Please read the first post in the following thread: https://forum.armbian.com/topic/12656-csc-armbian-for-rk322x-tv-boxes
-
multitool is something that @jock has created for his CSC builds. It has nothing to do with builds by balbes150
-
All the 'install multiboot' process is doing (whether through the reset button or update app) is running the uboot script aml_autoscript located in /boot in the image. If you can get into uboot via a serial interface you can run these commands directly. They are setting uboot environment variables to tell the boot process to look for armbian before trying to boot the android partition.
-
install-aml.sh is a pretty simple shell script. Just look at what it does and compare.
-
Since it is just a shell script, you can pipe the output to a file
-
So you can run from SD fine. That may be the best you can do. The various boxes can have very different ways they setup their emmc and it may not be possible to run your box from emmc. A log from running the install_aml.sh script would be helpful to see.
-
What you are reporting doesn't make sense. There isn't anything that should be preventing the android os from booting after you enable multiboot. Let alone needing to reinstall the android firmware. When you say the 'backup and restore thing' what exactly are you doing?
-
(Moved post to a more appropriate location)
You will need to provide more information than just a screen shot. Lets start with the TV Box you have, what dtb you are using, etc. I think I saw in another thread you mention that you are sucessfully running a box from the SD card, so I'm not sure what your actual problem is.
-
Assuming the label is correct this is an s905x cpu (would have to remove the heat sink from the CPU to be 100% certain).
Then you should use: u-boot-s905x-s912 and try all the meson-gxl-s905x-* dtbs (but start with meson-gxl-s905x-nexbox-a95x).
Don't worry about the install to emmc yet, make sure everything else is running fine first. But if you eventually do want to try it would be: install-aml.sh
-
Attach a picture of both sides of the board to this thread
-
It could be either CPU. Manufacturers produce many varients of a tv box over time, changing the components to what's cheapest at the moment. So two identically labeled tv boxes can have different components. I would recommend opening the box and looking at the physical CPU to get your answer.
-
Please read: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first
So you understand the level of TV Box support currently
-
2 hours ago, boxmeister said:
If anyone can point me to what fille/script i need to run id be more than happy.
This is covered in the last paragraph of the TV Box FAQ entry: Installation Instructions for TV Boxes with Amlogic CPUs
-
There is only one image available if you are following the instructions in the FAQ.
What images are you trying and what instructions are you following? You have provided no useful information for anyone to help you.
-
13 hours ago, MX10.AC2N said:
How can we solve this problem with the / boot partition in FAT during updates??
Thank again..
You should report that as a bug to the maintainer of the code you are onstalling. I have reported (and submitted patches) for similar issues in Armbian code.
-
TV boxes are not supported by the Armbian project. Thus you posted this originally in the wrong forum. I moved your post to the TV Box forums.
You don't mention much in the way of useful debugging information, like what build are you using. But I would recommend reading through the threads in this forum for your cpu and you should find help there.
-
You can't use an android dtb. dtbs are kernel specific. So a dtb coded to a vendor supplied android kernel isn't going to work with a mainline kernel.
-
13 hours ago, Massive Box said:
So I wonder if I could just erase the boot partition on my eMMC
Do not do that as you will brick your box. Amlogic based TV Boxes only boot from emmc (except in rare cases).
20 hours ago, Massive Box said:No. boot.ini isn't even used by the balbes multiboot process.
I asked earlier if you could boot from an sd card (as that should work since you originally booted that way before installing on emmc). Again, I will repeat myself, don't expect to be able to boot from usb, that doesn't work on many amlogic based boxes.
13 hours ago, Massive Box said:the Windows utility I'm running in a Virtual Box with USB passthrough
What utility are you running?
-
What version do you currently have installed? (armbian and kernel versions)
If you don't have a reset button, how did you enable multiboot in the first place?
Have you ever run armbian from usb on this box? (not all boxes will support booting from usb)
Does booting armbian from sdcard work?
-
OK, now that you have the latest build, I would recommend that you start over. Reinstall a fresh android firmware and then try again. Because you used an old build, that caused you to set uboot variables that are not correct for the latest build.
Also, it looks like you are using either the wrong dtb or the wrong u-boot.ext. Since the dtb you mentioned above is for an s905x cpu (meson-gxl-s905x-p212.dtb) but you are using the s905x2 uboot.ext (rename u-boot-s905x2-s912 to u-boot.ext)
-
If you aren't going to follow the instructions on this site, which would include running the version the instructions point to, then I'm not able to help you. You are trying to run a version that is different in many ways than the one the instructions are designed for. Please try again with the correct build if you would like my help.
-
I'm still not understanding what instructions you are using nor what build you are using.
I want to correct a couple of items in your previous post. You don't seem to be looking at the correct aml_autoscript as the 20.10_xxx_5.9.0 build doesn't have a line like setenv bootfromnand 0.
You mention modifying boot.ini, but that isn't a step that needs to be done.
So again, I ask, what build are you using and what instructions are you trying to follow?
Finally, if you have a working console that you can access the u-boot command line from, then you should be able to just enter the commands one by one as they appear in the aml_autoscript file.
Installation issues TVBOX MINIX U9-H
in Amlogic CPU Boxes
Posted
You apparently didn't read the FAQ post carefully as this is addressed:
Note2: 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 attemping the install. coreelec changes the boot environment in ways that are incompatible with these armbian builds.