Staars

Members
  • Content Count

    17
  • Joined

  • Last visited

About Staars

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Welcome to ARMBIAN 5.71 user-built Ubuntu 18.04.1 LTS 4.9.138-rtd1295 System load: 1.15 1.02 0.73 Up time: 15 min Memory usage: 4 % of 1631MB IP: CPU temp: 46°C Usage of /: 6% of 15G It is somehow patchable, to be continued ...
  2. Just some additional infos: Starting points were https://en.opensuse.org/HCL:Zidoo_X9S and the "new" repo from the bananapi side. After soldering some wires directly to the PCB I tried to gain some info on the machine itself, which has some sort of dual boot to android and a "rescue linux" with kernel 4.1.x. The chained boot process was already described by afaerber and at least we can save the u-boot-environment on the device, which I only tested with the bootdelay so far, because I do not want to brick anything at the moment. Then I played with the banana build system, which I am not used too. In parallel I created 2 repos with the kernel and u-boot in order to build it with the armbian build system and I could compile it rather soon. But I could not boot anything at that time. After that came the trial-and-error part, which will continue for some time. In short: After trying out the awfully slow ymodem for kernel load, I ended in writing kernel and dtb to the start of a sd card and load it by hand in the "first" u-boot. I adapted the arminian build process to write both things to the image instead of the usual u-boot. So things works like that: 1. Power-on with serial connected, interrupt first u-boot with ESC. 2. Use the following commands: sd read $kernel_loadaddr 800 954a sd read $fdt_loadaddr a440 5d fdt addr $fdt_loadaddr fdt resize b2ndbc 3. The last line continues the boot process, which must be interrupted again with a key press, then: setenv bootargs earlycon=uart8250,mmio32,0x98007800 console=ttyS0,115200 noinitrd root=/dev/mmcblk0p1 rootfs=ext4 init=/sbin/init bootr That's basically all I know at the moment and the quest continues. If I do not brick/destroy the box (which could happen), I plan to upgrade the kernel repo to 4.9.150 and if this works out, I hope to find a way to create an easier boot process.
  3. Hi, after reading the very entertaining thread regarding the BPI-W2 and the following opening of the bsp-kernel on github, I became curious and when prices dropped for the Lake-1-TV-Box, I decided to play around with it. Without very much documentation there was a bunch of trial and error and still many things are not absolutely clear to me, but finally I could boot an armbian build today: _ _ _ | | __ _| | _____ / | | | / _` | |/ / _ \ | | | |__| (_| | < __/ | | |_____\__,_|_|\_\___| |_| Welcome to ARMBIAN 5.68 user-built Ubuntu 18.04.1 LTS 4.9.119-rtd1295 System load: 1.49 0.74 0.31 Up time: 3 min Memory usage: 4 % of 1631MB IP: CPU temp: 46°C Usage of /: 11% of 7.2G [ General system configuration (beta): armbian-config ] New to Armbian? Check the documentation first: https://docs.armbian.com Thank you for choosing Armbian! Support: www.armbian.com This is still connected over the serial port and completely untested. I had to use the strange chained double-u-boot and load kernel and dtb manually (from raw sd card sectors), so it is not even close to alpha. But it seems, that this can be improved. I plan to make a repeatable build config, but do not expect some really usable stuff anytime soon. The situation with the lack of mainline support was already discussed in the other thread and the future does not look very bright here. This is more or less a personal playground at the moment. But if anyone is interested, you can leave comments or questions here.
  4. Staars

    Armbian for tv box Z28

    Okay, I did not know this. I thought, that every RK3328 will not boot from sdmmc0ext, because the z28pro2/16 behaves that way. There must be another reason for the inability of the z28pro to NOT boot from SD. So I made an incorrect assumption. Thanks for the info.
  5. Staars

    Armbian for tv box Z28

    AFAIK it is impossible to boot a RK3328-box with GBit-Lan from SD-card. So You can not boot the Alfawise Z28 Pro 2/16 to Armbian without destroying your Android installation. The only theoritical chance would be, to develop a Multiboot-U-Boot for this very special purpose, but this is not really a serious suggestion. BTW, I had the opposite version in mind (boot Android on SD-card from our Armbian Installation), but even writing an Android-image to an SD-card is quite cumbersome.
  6. Staars

    Compil ffmpeg for RK3328 (v88 mini 3)

    NVENC = NVidia Encoder -> So the answer is No.
  7. Staars

    Armbian usable on RK TV-Boxes?

    I only have a rough idea ATM, but I hope it is possible, to build an image with a very bare-bone DTS and then activate the variable nodes via DT-overlay in a script with some kind of underlying data base. The postulated script would check, if and how the system responds to a node activation (something like successful modprobe or not) and then test another node if needed. The fixed nodes are (probably) eMMC, "normal" USB, AUDIO- and VIDEO-Stuff. The variable nodes are LAN, UART, SDMMC and USB-connected Wifi/BT which in many defined cases rule out each other. For instance Gbit always means you can not have SDMMC1 (and UART0) and that's why you do not have real multi-boot from SD-Card on Gbit-TV-Boxes (at least I'm pretty sure ). One thing that makes it even more complicated is, that the currently used u-boot has some hard coded settings (see my SDMMC0EXT-Patch for z28pro), which will very likely require the use of at least 2 "generic" images for Gbit- and Non-Gbit-Boxes. Of course we would need different images for DDR3 vs DDR4 too. Summarized: I like the idea of having as few different images as possible, but it would be a big amount of work and maybe it is not possible that way.
  8. Staars

    Armbian usable on RK TV-Boxes?

    I agree. While I am quite happy with the current state of the z28pro-Image in Armbian (and I invested a lot of time) it is quite useless for many potential users because you would need one particular image for (nearly) every rk3328-box. It would be better, if we could develop in a more modular approach and I think this is possible. Beside that, I still hate this annoying maskrom-thing
  9. Yes, that is pretty much what has also crossed my mind. My best guess regarding disabling Wifi/BT: rfkill. Or the other way around, if not for what else is rfkill for? It is the only purpose of the program I know.
  10. BT is connected as HCI-UART via ttyS2 and thatswhy it conflicts with the external serial console. You can not have both (i think). When I was preparing the BT-packages, i wondered if it makes sense to only activate the BT-device, when the user has already installed the bluez package (for instance via armbian-config). This should be easy to implement and the „average“ user will probably install the bluetooth package that way. For server-only users BT will be useless,in most scenarios but at the moment they get the device activated and lose the external serial port. What do you think?
  11. For the z28pro: If you want to disable WLAN and BT and you want to to do it in the DTS, you only need to disable SDMMC0 (not SDMMC0EXT). A while ago I played a little bit with the device tree overlays on my z28 pro and used the script from ayufan. If I remember right, I needed a newer version of the device tree compiler. But it worked. Another way to deactivate WLAN is to blacklist the r8822bs driver or you can use "sudo rfkill block wlan (or bluetooth or all)". I expect, that you cannot unblock bluetooth with rfkill (reboot needed).
  12. Staars

    Armbian for tv box Z28

    Regarding the Gb-Lan-problems I recognized a declining speed, which occurred quite frequently after some time. And because there were some similar reports for the Rock64 on other sites, I assumed it was a general problem of the RK3328. But this might be wrong, because another aspect is, that the LAN-Port on this box is as strong as the grip of the hand of Mr. Burns . This thing is the most sloppiest Port I've ever seen. You don't feel a click, when you plug the cable in. In the end it is possible, that I only face a mechanical problem here. Beside that, I think it is a nice little box and if the onboard devices are useable for your needs, it is relatively cheap.
  13. Staars

    Armbian for tv box Z28

    BT should work now on the z28pro. Everything is in the repo now and you can make a test build.
  14. Staars

    Librecomputer Renegade RK3328

    I think, it could be the board specific ddr4-patch, which was made for the "old" board name and now resides in the incorrect subdir.
  15. Staars

    Armbian for tv box Z28

    I did some random and unstructered tests to put some load on the box. So I installed Node-Red which worked flawlessly and after that downloaded and compiled OpenCV 3.4 (again on the box) which worked out without any problem (inkl. a short python test). I tested only headless via SSH and had only one disconnection to the system while typing in the python console (and doing virtually nothing). Beside that I had not a single crash and the system feels very responsive. After the cumbersome installation (Android -> Kernel 4.4.112 (via flashing) -> Kernel 4.15.0 (via unstable wifi-USB on the box ) the installation works de facto out-of-the-box and meanwhile the mainline support seems to be pretty well now.