jock

@some0ne in the first page there is the updated multitool version. For some reason a closed source binary blob, on some very rare boards, turns off or put the board in suspend. The reason is not known, since something happens in a closed source blob. I don't know if it is your situation, but it looks something that already happened.

It would be nice to have a proper kernel driver for such device. As far as I remember, it uses a i2c-like bus with some minor differences; I looked into some time ago, but had to give up due to not enough time, but a proper driver would wire the led chip hardware with the kernel led framework to exploit all the kernel triggers and goodies.

Hello, I don't think any tv box has a microphone or microphone header anywhere. Some SBCs instead have the microphone on-board (like some Orange Pi boards)

Very weird, if the kernel module is loaded, there should be the device under /dev too. From dmesg I see something suspicious: [ 1249.869135] usbcore: registered new interface driver ch341 [ 1249.869317] usbserial: USB Serial support registered for ch341-uart [ 1249.869609] ch341 1-1.3:1.0: ch341-uart converter detected [ 1249.872306] usb 1-1.3: ch341-uart converter now attached to ttyUSB0 [ 3599.906107] input: BRLTTY 6.5 Linux Screen Driver Keyboard as /devices/virtual/input/input20 [ 3599.919207] usb 1-1.3: usbfs: interface 0 claimed by ch341 while 'brltty' sets config #1 [ 3599.921891] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0 [ 3599.921965] ch341 1-1.3:1.0: device disconnected so perhaps brltty is clashing with the usb device. If you are not using a braille device, you can try uninstalling it

Yes Yes, but you won't get any lima or panfrost anyway, 4.4 is way too old kernel. Also Panfrost is of no use, since it does not support Utgard (Mali-400) but only Midgard and above

I bet: your internal flash is NAND and you are installing the image in the internal flash. Read the first page for more info. Use sdcard and mainline kernel if you don't want up to date kernel and opensource drivers.

@Jaisere Hello, I wonder why you are using an image with the legacy 4.4 kernel, which I don't maintain anymore. That is an ancient kernel supplied by the vendor and it is several years old; the vendor (rockchip) maintained up to a couple of years ago, but now it is totally deprecated and unmantained. The only usefulness for that kernel is that it works with the internal NAND flash. Use images with current kernel (at the moment, current version is 6.1), which is mainline kernel. It does not support NAND, but it is maintained and supports practically everything.

@ego worker journal rotation is normal, the disconnection of the USB devices are typical of tv boxes adapted to do something else: tv boxes are not able to supply too much power and if the USB devices are not low power, they often disconnect. Nb: please put logs in a spoiler section, not code

Ah ok, thanks for this, I'll keep in mind with newer versions.

@ego worker Now I'm checking edge 6.6.7 kernel and it works like a charm: made some stress tests with openssl speed -multi 4 while running KDE and hardware video decoding with no particular issues My eMCP reads at most at 28.4mb/s in DDR mode, sometimes also times out, but it is a scrap board with plenty of issues; decent and non-abused eMCPs read up to 90mb/s in DDR mode.

But that's not a supported setup for ubuntu jammy or debian bookworm with this repository, perhaps it is better to discuss in a separate thread?

@ego worker during my tests the board was stable with days of uptime, but when some tasks were run it hang as well. Could not really understand where is the issue, but I did not dedicate any time to it. What overlays did you enable? R29s are very limited, they have no power regulators for cpu and logic so voltage is fixed. For this reason, cpu, ddr and gpu frequencies cannot scale up to nominal frequencies.

vo=gpu-next fails on my setups, but the rk3288 tinkerboard-s was one of my test beds and it did not show any reset issue. Also other boards did not show any particular stability issues.

Use the multitool and install the "Jump start" feature, then you should be able to boot from either sdcard or usb.

Mostly trial and error; if the board is well known and someone already discovered it or if you have the original dtb you can look there

@haven Cool workaround, thanks! Can be also useful to pinpoint the bug/missing feature

Read the first post of the main thread about rk3318, there is an alternative firmware for your wifi you may want to try

@Le Best Noob Thanks for the photos. It looks like a quite a standard rk3229 board, in fact looking into the device tree it uses the same led wiring of mxq_rk3229, which is led-conf2; the only thing doubt is that the leds may be switched in polarity: when set to on, they turn off, and viceversa.

Yeah, USB3 is quite sensitive to interferences, and when the board is not designed nor realized with particular care, that's what you get. rk322x thread is filled with these minor and major issues and when people asks what they can do, the best answer is always "next time buy a properly supported SBC, whose specifications are clear and has been tested for proper support". I always say that tv boxes are very nice for toying around - I find it very funny to reverse engineer them. You may even be lucky and get stability for your project, but if you're not a power user with more than average experience and knowledge you will easily have troubles of some sort sooner or later.

Which is a false statement. You talk that way only because you don't know what is there behind. I run the rk322x and rk33x8 thing for years and perhaps I'm more informed than you. Tv boxes have been always a discussion theme in the past with the armbian "management board". People with more experience than me noted, years ago, that they would be way too costly and practically unmaintainable by project members if community would not be involved in their management. That's true: their hardware changes constantly, market names that means nothing, plenty of revisions for the same "board" with different wirings and different hardware parts. You can't set a supporting level when you get a situation like this. For that reason dedicated forum sections and Community Supported Configuration (CSC) boads were introduced, and support is given by community itself with a "best effort" fashion. Tv box and alike configurations are always accepted into armbian, but only as CSC boards. Also rk322x family is there only for tvboxes. Wiping out all csc boards and families and forum section and maintainance would be much easier for everyone. Perhaps it is somehow true, but still is challenging to deal when your opponent "cheats" in every possible way (scrap or defective parts, false advertisement, etc...)

Actually I don't know, but I think that tv box manufacturers do little to nothing adjustment on their android images. I think they deal with the software as little as they can do. Despite there are dozen of tv box brands out there, all of them have the same exact software, the only difference is the device tree to adapt little differences of the boards here and there. Software support costs, and costs a lot, and tv box manufacturers have to keep the price as down as possible.

Perhaps because they benefit of huge software support without giving anything in return? You can object that that tv box manufacturers never asked for that software support, which is true, but let's imagine tv box community support ceases immediately, how many people would buy tv box crap and how many people would instead buy an SBC to do their experiments, tests and projects? I puzzled myself dozen of times with that question, and that's the main reason I stay stick with lower end tv box devices only. Which is not scientifical and statistically significant way to deduce the global quality. Yet you just take a look to some tv box boards to see the poor quality of soldering, the recycle of passive components, the general low quality of the traces (sdio wifi complaints mostly) and the scrap emmc/ddr components, that often fail to reach the rated performances. And no, not anyone has a soldering station and is capable of swapping a broken emmc with new one, also because the emmc is not the failing part here (I have tv boxes with half-working ddr parts, half working ethernet due to poor chokes, outdated wifi chips, and so on...)

@Energokom I absolutely don't condemn people - that would be a quite dumb position as long as I maintain a couple of tv box ports of discrete appeal - but indeed I condemn the endorsment. The point I wanted to make clear was not what YOU, as a person, did for armbian: as you say, armbian is an opensource project and free for everyone. The point is that tv box manufacturers do nothing for armbian. If users don't want or can't contribute it's ok, because donations are volountary. But if manufacturers don't contribute as well, who will? At the end there will just be nothing because non-profit is one thing but charity is another one. Charity is not sustainable in the long run, and not anyone is willing to. For the same law of conservation of energy you stated, tv box manufacturers takes energy from the system and gives little to nothing back; users perhaps partially mitigate, donating something back to the project, but why actively endorsing entities whose behaviour is neutral at best and parasitic at worst?

@Le Best Noob looks like your board is a new one; could you please post a couple of photos of the front and back?

You should not advise to buy shit, they are cheaper because: * they are made of scrap parts, that often break after very short usage (see the emmc in the rk3318 thread) * they have no kind of warranty * the power supply is a joke, made of cheap components and very lousy - switching power supplies are one of the thing the more they weight the better; confront with a quality 5V/2A power supply and see the difference * the HDMI cable is crap quality, often not capable to transfer CEC or collects any kind of interference at 1080p/4K * the case is a bit of plastic, with little to no design for heat dissipation - right now I have a rk322x board here withing its case that reaches 97°C while simply installing a package with apt... * many sorts of limitations to keep them as cheap as possible: no sd card UHS mode, no real shutdown/suspend, USB ports have limited power: be prepared to have headaches if you try to attach something that requires just a tiny bit more power like an external hard drive. * wifi is a lottery and clearly tells you the general quality: you can find freshly made boards with wifi chips discontinued years ago! Most of all: they have absolutely no software support; if you are able to run armbian on your tv boxes it is because some people within armbian and other projects spent their time for the fun of making it. Tv box makers don't care at all, they just need to sell their cheap shit to make some profit. Some (not all) SBC makers at least in some way provide support, but tv box makers are mostly parasitic and should not be endorsed. Now that you stated that about 20 pcs of different tv boxes run armbian, may I also ask you what you did in change for that for armbian? Because tv box makers obviously did nothing for armbian, still keeping up the servers infrastructure and the general maintenance cost real money to real people, and who pays that?