SteeMan
-
Posts
1460 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by SteeMan
-
-
17 hours ago, SteeMan said:
And if you have any questions or issues you should post them there.
Did you no read what I wrote? If you want help that thread is where you need to post your question/issue.
-
You should be following the instructions in this thread:
https://forum.armbian.com/topic/26978-csc-armbian-for-rk3318rk3328-tv-box-boards
And if you have any questions or issues you should post them there.
-
post moved to correct location
-
Providing logs with
armbianmonitor -uhelps with troubleshooting and significantly raises chances that issue gets addressed.
-
31 minutes ago, Victorhtf said:
EDIT: After post my reply I tried to use the exactly same DTB as you said. And it worked.
The reason this would work is that you really have a s905L2 cpu. This wouldn't be the first time that a TV Box vendor and/or parts supplier changed the markings on a chip to give the impression it is something else.
-
Providing logs with
armbianmonitor -uhelps with troubleshooting and significantly raises chances that issue gets addressed.
-
Providing logs with
armbianmonitor -uhelps with troubleshooting and significantly raises chances that issue gets addressed.
-
GPT is something the Armbian build framwork supports, not currently the default, but here is a list of boards that use it:
grep -i gpt *
armsom-sige7.csc:IMAGE_PARTITION_TABLE="gpt"
armsom-w3.csc:IMAGE_PARTITION_TABLE="gpt"
bananapir2pro.csc:IMAGE_PARTITION_TABLE="gpt"
fxblox-rk1.wip:IMAGE_PARTITION_TABLE="gpt"
hinlink-h28k.csc:IMAGE_PARTITION_TABLE="gpt"
hinlink-h88k.csc:IMAGE_PARTITION_TABLE="gpt"
hinlink-ht2.csc:IMAGE_PARTITION_TABLE="gpt"
indiedroid-nova.csc:declare -g IMAGE_PARTITION_TABLE="gpt"
jp-tvbox-3566.tvb:IMAGE_PARTITION_TABLE="gpt"
khadas-edge2.conf:declare -g IMAGE_PARTITION_TABLE="gpt"
mangopi-m28k.csc:IMAGE_PARTITION_TABLE="gpt"
mixtile-blade3.wip:declare -g IMAGE_PARTITION_TABLE="gpt"
nanopct6.wip:IMAGE_PARTITION_TABLE="gpt"
nanopi-r5c.csc:IMAGE_PARTITION_TABLE="gpt"
nanopi-r5s.wip:IMAGE_PARTITION_TABLE="gpt"
nanopi-r6s.conf:IMAGE_PARTITION_TABLE="gpt"
odroidm1.conf:IMAGE_PARTITION_TABLE="gpt"
orangepi3b.csc:IMAGE_PARTITION_TABLE="gpt"
orangepi5.conf:IMAGE_PARTITION_TABLE="gpt"
orangepi5-plus.conf:IMAGE_PARTITION_TABLE="gpt"
panther-x2.csc:IMAGE_PARTITION_TABLE="gpt"
quartz64a.csc:IMAGE_PARTITION_TABLE="gpt"
quartz64b.csc:IMAGE_PARTITION_TABLE="gpt"
radxa-e25.wip:IMAGE_PARTITION_TABLE="gpt"
rock-3a.conf:IMAGE_PARTITION_TABLE="gpt"
rock-5a.wip:IMAGE_PARTITION_TABLE="gpt"
rock-5b.conf:IMAGE_PARTITION_TABLE="gpt"
rock-5-cmio.csc:IMAGE_PARTITION_TABLE="gpt"
station-m2.csc:IMAGE_PARTITION_TABLE="gpt"
station-m3.csc:IMAGE_PARTITION_TABLE="gpt"
station-p2.csc:IMAGE_PARTITION_TABLE="gpt"
xiaomi-elish.conf:IMAGE_PARTITION_TABLE="gpt" -
-
There are images on the download page, but the OrangePi One is in the Community Maintained status there. I think @Stephen Graf question them becomes why is is listed as Community Maintained when it is a .conf, not a .csc?
-
28 minutes ago, Werner said:
Usually the filesystem expands itself across the whole sdcard on first boot...odd.
That was my thought as well, odd.
@Jedge Can you reproduce the problem? As Werner stated, on first boot the filesystem on the SD card is supposed to be expanded to take up the entire card. Do you have smaller SD cards you could try, curious if the card size is triggering an issue.
-
-
Moved out of TV Boxes to Standard Support forum. The vim2 I believe is standard support as it is .conf but there is no subsection for vim2 so I moved it to the vim3 section.
-
I just want to add a few comments to this whole dtb overlay discussion.
First I want to thank all of you involved in this discussion. You all have different view points and I think are tackling a very difficult problem to which there is no perfect solution. What comes out of this discussion should be applied to the other soc families as well, as they all suffer from some form of this issue as there is no standard in place that works for all use cases well. From what I have seen, good minds are thinking this through and I expect a good result to follow.
The reason I am commenting at all, is because in my role as forum moderator, the basic question: "How do I enable feature x on my board" is one of, if not the most commonly asked question by end users of the forum. And when the answer is 'just write a dtb overlay', you have lost 95% of those users as they do not have the skills/knowledge to do that. The status of the dtb overlay's across Armbian supported and community maintained boards is poor. There is no standardization from family to family or board to board. And no testing of what does exist to ensure that it works. Now I'm not saying that all of this needs to be solved in what comes out of this design discussion. I'm just saying from my perspective as a moderator that this is an area that can use some attention, and in doing so, please try to make the end result usable by the typical end user of an sbc, trying to do common things. I realize also that I'm saying this when I only use these boards as servers and don't personally need any of the functionality the overlays provide. But as a forum moderator, I see the mismatch between what is being done and some common use cases that end users are looking for.
-
Moved to a new post, instead of reopening a thread that is over a year old.
-
On 1/14/2024 at 5:12 PM, sam_uk said:
Because the other thread was in the wrong place, so it got locked.
The other thread got locked because your post was inappropriate. Unless you intend to develop and maintain the Armbian support for this board, there isn't any reason to post this information here. Igor in your other post pointed you to the following link: https://docs.armbian.com/Process_Contribute/
If you intend to develop Armbian support for this new board, and wish to use this thread as a place to document your work, then this is an appropriate use of the forums. If not this post will eventually get locked as well, as you aren't asking any question to be addressed by users of the forum.
-
-
-
27 minutes ago, Mr. Fennec said:
there is no subthread for orangepipc.
That is because this board is not supported, and you were posting in the supported boards section of the forum.
-
Also, good detective work figuring this out.
-
You should be able to change the title if you want. I think all you need to do is double click on the title at the top of the thread as the thread author
-
Then that is the thread you should be asking your question, not starting a new thread.
-
Have you followed the instructions in the official rk322x thread:
The link to builds you included above is some archived stuff, not current.
-
S905X TV box bricked after installing to emmc
in General Chat
Posted
Lets start with some basic information: What build are you using? What installation instructions are you using?