jock

  • Content Count

    579
  • Joined

  • Last visited

Reputation Activity

  1. Like
    jock got a reaction from Attilatilla in CSC Armbian for RK3288 TV Box boards (Q8)   
    @Attilatilla Ok, fixed the device tree and updated the legacy kernel images in the first post.
    They are still for testing, but seems to work fine so far with the media installer for tinkerboard in the apt repositories (don't remember the actual package, just search for tinkerboard and you'll probably find with ease).
    I tried only the debian minimal image and Kodi was starting fine. Did not try any video though.
     
    Feel free to report here!
  2. Like
    jock got a reaction from hexdump in Planned changes to the TV Box area   
    I'm always happy about tidying up things, and tv boxes section is still far from being ideal. Honestly I don't know if it is a wise idea to have a section "TV Boxes running Armbian" and I explain why: it could work well with serious and proper brand products, but if you mean to tidy up the forum against the chinese brands, well, we have to face the reality that cheap chinese tv boxes don't have any proper nomenclature. Often you get a recognizable pattern, sometimes you don't. This is especially true for the cheapest products and so things that have the same market name may have a different hardware, either "just" the wifi chip or a completely different board with another SoC. Anyway, trying is costless, so let's try it
     
    Personally I maintain the rk322x and rk3288-xt-q8l-v10 (xt-q8l-v10 is a rk3288 tv box board) CSC threads and so far I have to say I never had to ask a moderator to delete a post or ban a person. We never faced any major inconveniences with users, yet people has been very collaborative in some cases that we brought up hardware support remotely (esp8089 wifi support, for example) and very often people sends device trees to be analyzed. The rk322x thread has been a great source of fun
     
    IMHO they work well because:
    the subject is clear - since most of the problems are related to the hardware, bringing in many architectures in the same place will incredibly increase confusion. One architecture and its related kernels, that's more than enough. the first post covers the basics - though I have to say that preparing such pages to be simple and effective took a lot of time and effort - it is terribly useful for users. Most people read this and finds their way. Some don't read the first page, so you kindly redirect there, some skilled or unskilled people read the first page, don't get it and post. They get attention as long as they show to be collaborative. If they acts like childish leeches they will just get ignored. the thread is a linear history of what happened and when - except for the first page which is often updated with the "must read" infos, reading the last 2/3 pages of the thread are enough to get up to date stay within the armbian rules - it means that even if they are tv boxes, they fit and integrate into the armbian ecosystem as much as possible. For example: if FAT is not supported by armbian (yet it is, but that's an example ), don't use your own hacky thing to make a FAT partition but bring FAT support into armbian; if the board uses some firmware, don't put the firmware somewhere hidden but commit the firmware to armbian-firmware repository and fix the thing with a generic patch, and so on... It's harder, but it's better and brings much better cooperation at all levels and people will find the stable board/box images in the right place (the Download page), not elsewhere.  
    Getting back of the tv box club, I share my wonders about how it could be arranged - that's just an idea, it could be totally wrong...
    Along with the "Overview" and "General chat" sections, since there are just 3 major vendors they could be put as main tv box club sections.
    Overview is cool because it's a "what's new" overview page. I consult it often and finds it very useful to spot recent posts that may be interesting.
    General Chat is where newbie people will probably post, along with generic threads and posts asking for help. There I would put a pinned "FAQ" and "must read, forums rules" thread.
     
    The three vendors sections (Rockchip, AmLogic, Allwinner) will be less touched by newbies which don't even know what Rockchip/Allwinner/AmLogic are; people with just a tiny bit of experience instead would post vendor specific questions in the vendor sections.
    I would put the "CSC megathreads" in the vendor specific sections. People who wants to cooperate to support some chip of that vendor or talk about that vendor could freely do that in the vendor section; if interesting discussions arise (like happened in the recent past for S905X3), threads could be pinned or CSC support materializes for a tv box/board/architecture, there could be a pinned thread for that too.
    As an example, S905X3 tv boxes don't have CSC support, but may have a pinned thread (one pinned thread for one architecture) to let people discuss about it in one place, decent tv boxes (Beelink S922 ones just popped in my mind) may have a separate pinned thread if there is a CSC maintainer for that board if there is discussion or enough interest about.
     
  3. Like
    jock got a reaction from pro777 in CSC Armbian for RK3288 TV Box boards (Q8)   
    @Attilatilla Ok, fixed the device tree and updated the legacy kernel images in the first post.
    They are still for testing, but seems to work fine so far with the media installer for tinkerboard in the apt repositories (don't remember the actual package, just search for tinkerboard and you'll probably find with ease).
    I tried only the debian minimal image and Kodi was starting fine. Did not try any video though.
     
    Feel free to report here!
  4. Like
    jock got a reaction from Werner in INSTALL OS ON TV BOX H96MAX - HELP   
    @Joãobt If you're going to follow @SteeMan suggestion, please report here your experience!
  5. Like
    jock reacted to SteeMan in Newbie, advice requested, which Android TV box under $30 is good starter?   
    Moved you post to the TV Box club.  You should read:  https://forum.armbian.com/topic/16407-please-read-first
    Generally you are not going to find any Android TV boxes that will meet your needs with the armbian builds that you can install on them currently.  They were great for headless servers, or light desktop/browser use.  But you aren't going to find good video playback support currently in general and especially not at the price point you are looking at.  Just trying to set your expectations.  If you already had a box and wanted to experiment, I would say go ahead, but if you haven't yet bought something, you are likely going to be disappointed by the current state of armbian on TV boxes - the first clue to that state is that they aren't supported devices.
  6. Like
    jock reacted to NicoD in Box86 on the RK3399 with Armbian Reforged   
    Hi all.
    @Salvador Liébana has made a preview Armbian image with many emulators preinstalled.
    Also Box86 with which you can play x86 Windows games and x86 Linux games.
    Also running some Windows programs is possible with this.

    Download Armbian Forged : https://drive.google.com/file/d/1gQtgWz2pH2TX9Qs_bcDU9zn7w4edfcVf/view?fbclid=IwAR0SRSC8M_1_qm825n4Bd7bqjLmO30qTpFo73qQQga-TC_LRuc2BVFcGzKU

    Here my video about Windows games on the preview build.

    Here some videos of @Salvador Liébana himself.
     
     
     
  7. Like
    jock got a reaction from JMCC in RK3399 Legacy Multimedia Framework   
    Hello, my armsoc fork has some bits here and there to allow working fullscreen acceleration with Mali proprietary drivers on mainline kernel using dumb buffers instead of private Ioctls for rockchip, allwinner and amlogic.
    On rockchip it works fine also with the legacy 4.4 kernel too.
    Hardware cursor works fine, just switch to HWCURSOR_API_PLANE the attribute here
     
    The reason why it is currently set to software cursor is to allow the cursor work on rk322x.
    rk322x has only two hardware planes and one plane is forcefully used as primary, so just one hardware plane is left for use.
    Current rk322x-legacy armbian variant has a patch that allocates the spare hardware plane as overlay, so if I set armsoc to use hardware cursor, the cursor just disappears because there is no hardware cursor plane!
     
    A smarter logic in armsoc would be to run over all the DRM planes looking for the hardware cursor one and use it. Otherwise, in case no hardware cursor plane is present, just use the software cursor.
     
    To say it all, almost all rockchip SoCs (including rk3288, rk3339, rk3328 and rk322x) have a special dedicated hardware plane capable of up to 128x128 pixels just to be used for the cursor, so you don't have to sacrifice a general purpose hardware plane. I made an incomplete WIP patch for and it partially works, but has issues that cannot be fixed without changing some surrounding code
  8. Like
    jock got a reaction from Lambert in RK3318 device (Magicsee N5 Nova 4g/64g) with dead NAND   
    Glad to read that. Strange you had to write the trust.img and uboot.mg back onto the sdcard, they are already installed in the same position you burned again. Strange, I will check the scripts but thanks for reporting!
     
    Ok, an amount of sectors of the eMMC are gone. I suggest you to erase it and leave it alone.
    Once the eMMC is erased, you may try to burn the armbian image I gave you on the sdcard, it should boot directly.
  9. Like
    jock reacted to Lambert in RK3318 device (Magicsee N5 Nova 4g/64g) with dead NAND   
    I was run Multitool at last!
    It could only start this way:
    1. Rufus+Multitool.img
    2. dd if=trust.img of=/dev/sdb seek=24576
    3. dd if=uboot.img of=/dev/sdb seek=16384
     

  10. Like
    jock got a reaction from Lambert in RK3318 device (Magicsee N5 Nova 4g/64g) with dead NAND   
    Odd.
    I read the log in the post above and the line SdmmcInit=0 NOT PRESENT says that the sdcard is not detected at all.
    Can't say anything more at the moment, you need to use the maskrom mode if you want to proceed further.
  11. Like
    jock reacted to jeanrhum in Implement Device Tree Editor   
    First pull request for me: https://github.com/armbian/config/pull/123
    It is a basic implementation with my humble knowledge in bash. It may be improved by experts if possible.
    I tested on my armbian dev config and it seems to work. I hope to have follow the right way to make a PR since it is my first one.
  12. Like
    jock reacted to Myy in Armbian v20.11.y Bugfix release(s)   
    I'm currently finishing the last features for builders, like :
    the ability to provide a list of packages to uninstall before generating the image; limiting the desktops selection menus to the ones supported by Armbian and the architecture; parsing the distribution info from configuration files.  
    I also went back to a clean Armbian fork, https://github.com/Miouyouyou/build/tree/desktop , so that pull requests are 'doable'. I still need to re-arrange the changes into specific branches to make pull requests "nicer" and also :
    add documentation for the new features; remove the whole debug messages mess; refactor a good part of the new code.
  13. Like
    jock got a reaction from Igor in Armbian v20.11.y Bugfix release(s)   
    Tested, works, merged!
  14. Like
    jock reacted to fabiobassa in CSC Armbian for RK322X TV Boxes   
    @Maker39
    not more than yesterday, in private chat @jock and me we were saying that this 3ad is SUPER because many others users, such as you actively help people.
    This is right spirit of a forum
  15. Like
    jock reacted to Maker39 in CSC Armbian for RK322X TV Boxes   
    @zero48, With people like @jock and @fabiobassa , this board couldn't win this fight
    Congratulations on your success
     
    I was rooting for you, but nothing could help
  16. Like
    jock got a reaction from fabiobassa in CSC Armbian for RK322X TV Boxes   
    @zero48
    Apparently you have emmc and not NAND flash, so use the other instructions
  17. Like
    jock got a reaction from zero48 in CSC Armbian for RK322X TV Boxes   
    Unless you have rtl8189etv as wifi chip you don't need that.
    Just configure the board with rk322x-config so can you get back soon to spend some time with your family
  18. Like
    jock reacted to megaduo in CSC Armbian for RK322X TV Boxes   
    The wireless is fully working with overlays=wlan-alt-wiring wlan8189-etv-al.Thanks again!!!!!!!!!
     
  19. Like
    jock got a reaction from Lambert in RK3318 device (Magicsee N5 Nova 4g/64g) with dead NAND   
    You may try this very work in progress build effort made by @fabiobassa, @hexdump and me.
     
    Burn it on a sdcard and try, but your mileage may vary
  20. Like
    jock got a reaction from zero48 in CSC Armbian for RK322X TV Boxes   
    I don't understand what's wrong with your setup, but did you decompress the multitool (that's its name), as suggested by @fabiobassa before burning on the sdcard? If you are burning the .xz archive as is it will certainly never work!
     
    Also in Windows you must see the MULTITOOL FAT partition on the sdcard, otherwise you're doing it wrong.
     
  21. Like
    jock got a reaction from zero48 in CSC Armbian for RK322X TV Boxes   
    It happens because when you burn the multitool image on the sdcard, the FAT partition is 2GB large by default. The partition is then enlarged the first time you boot the multitool on the box to fit the whole size of the sdcard itself.
    Once you boot the multitool in the box, you can then plug again the sdcard on your computer and the FAT partition will be as large as the sdcard.
     
    There two strange things though:
    * the images for rk322x are all less than 2gb in size, so if you are not putting more than one image on the sdcard you should be fine even with default partition size
    * AFAIK, rk3229 with 4Gb of RAM cannot exist, probably 4Gb of RAM are just on the label of the box
     
  22. Like
    jock reacted to fabiobassa in CSC Armbian for RK322X TV Boxes   
    @zero48
     
    as already @Maker39 said you don 't need nothing to start from sd but the sd itself
    Mee too I always use win32disk imager so first extract the content of the xz file and burn it with win32imager
  23. Like
    jock reacted to Maker39 in CSC Armbian for RK322X TV Boxes   
    Try Rufus https://rufus.ie/
     I always keep "Rufus", "Win32 Disk Imager" and "HP USB Disk Storage Format Tool" handy for recording images.
    And you no need press "magic button" for boot with Multitool .
  24. Like
    jock got a reaction from Anung Un Rama in CSC Armbian for RK322X TV Boxes   
    Good news, expecially for @nokirunner and @DaviMesquita
     
    Finally we managed to make the ssv6x5x driver work on the ssv6256p chipset and it turns out the it is also working pretty well. I removed most of the logging messages it was spamming on the dmesg log, now it is much more silent and it is ok this way. Teaming with @fabiobassa we optimized performances quite a bit, so expect ~60 Mbit/s at least on optimal setups. It works on both 2.4Ghz and 5Ghz bands.
     
    The driver will be included in the armbian images soon, but in the meantime anyone can test it.
    Download ssv6x5x.koand put it into /lib/modules/$(uname -r)/kernel/drivers/net/wireless Download ssv6x5x-wifi.cfgand put it into /lib/firmware Download ssv6x5x-sw.bin and put it into /lib/firmware Run depmod -a Add blacklist ssv6051 in /etc/modprobe.d/blacklist-rk322x-box.conf (ssv6051 and ssv6x5x kernel modules clashes, we need to blacklist ssv6051 for the other to work) Reboot!  
    Any testing report is appreciated!
     
  25. Like
    jock got a reaction from jaum20 in CSC Armbian for RK322X TV Boxes   
    If you followed the instructions, the patch applies and you still don't get the device recognized you should first start getting the VID/PID of the device and see if it fits into the list covered by the patch. Also be sure to install the kernel correctly (both the kernel image and the modules). I'm not very into bluetooth so can't help with the command line tools to get the info you need, but I quite sure you can find something around for that.