• Content Count

  • Joined

  • Last visited

About SteeMan

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. I was just happy it succeeded. I will be trying other combinations over the next few days (I am doing a test from sd on the same box I ran last night right now). I'll report more data points when I can.
  2. Success! Native build on TX3 X3 (s905x3) emmc of bionic server image took 208 minutes
  3. So I need a new install of a current image, and I can't use an environment that has been upgraded? Correct? I will try that when I have a chance. Thanks
  4. If your question is must you update, the answer is no. However, I wouldn't understand why you would not want to update. One of the reasons to adopt Armbian is because it should provide you with regular security updates and critical bug fixes, like any regular linux distribution on an x86 platform. Armbian isn't just a static firmware that gets something running on a box/sbc but a more mainstream linux experience with updates. Anyone who runs systems (especially exposed to the public internet) should in my opinion be concerned with security updates and fixes as a priority. Now having said that, the base ubuntu or debian will get you security updates and fixes for the majority of the system, however linux kernel updates will come from Armbian. While support for those kernel updates for Balbes TV box builds has improved significantly over the last few months, there may still be an occasional issue.
  5. I pulled you latest Build-Armbian tree yesterday to attempt a native build on some of my hardware. I got the following error: ... DTC arch/arm/dts/rk3399-rockpro64.dtb SHIPPED dts/dt.dtb FDTGREP dts/dt-spl.dtb CAT u-boot-dtb.bin Image Type: Rockchip RK33 (SD/MMC) boot image Data Size: 73728 bytes warning: TCG doesn't support requested feature: CPUID.01H:ECX.vmx [bit 5] /lib64/ No such file or directory warning: TCG doesn't support requested feature: CPUID.01H:ECX.vmx [bit 5] /lib64/ No such file or directory [ error ] ERROR in function compile_uboot [ ] [ error ] U-boot file not found [ uboot.img ] [ o.k. ] Process terminated (I was attempting the following build: Full OS Image, arm-64, bionic, server, standard). Should your Build-Armbian github repo be working for native builds? I haven't tried to debug this error yet, just wanted to check with you if you felt this should work given what you have checked into your github repository.
  6. SteeMan

    X96 mini

    The X96 mini should contain the Amlogic s905w cpu. You should follow the instruction in the first post the following thread:
  7. SteeMan

    MX4N box

    This box supposedly has a rockchip 3229 cpu, so you can either follow the instructions in this post: or this post:
  8. I suspect your box only has 1GB ram despite what you think it has. See the following post about fake box specs: Only way to tell is to open the box and see what memory chips are installed on the board.
  9. I should have looked a bit closer at what you did, you were root so that wasn't the issue. You really need to learn basic linux commands. 'cd dtb' is what you wanted to do, not 'cd /dtb'
  10. You need to either be root (sudo su root) or sudo the actions you want because only root has permissions on the files in /boot
  11. Yes while running from sd card you should be able to do: $ mount | grep mmc /dev/mmcblk1p2 on / type ext4 (rw,noatime,errors=remount-ro,data=writeback) /dev/mmcblk1p1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro) /dev/mmcblk1p2 on /var/log.hdd type ext4 (rw,noatime,errors=remount-ro,data=writeback) (If your device is standard you should see that your sc card is device /dev/mmcblk1 with two mounted partitions p1 = /boot and p2 = /) $ ls /dev/mmcblk* /dev/mmcblk1 /dev/mmcblk1boot1 /dev/mmcblk1p2 /dev/mmcblk1boot0 /dev/mmcblk1p1 /dev/mmcblk1rpmb /dev/mmcblk2 /dev/mmcblk2boot1 /dev/mmcblk2p2 /dev/mmcblk2boot0 /dev/mmcblk2p1 /dev/mmcblk2rpmb (Again if your device is standard you should see both mmcblk1 and mmcblk2 - with mmcblk2 being your emmc) $ mkdir tmp $ sudo mount /dev/mmcblk2p1 tmp (mount the first partition of mmcblk2 to ./tmp - this will mount the emmc boot directory to tmp) $ cd tmp $ ls tmp (you should see the contents of your emmc boot directory here, now you can edit the uEnv.txt file, copy to this directory any dtb you wish, etc) $ umount /dev/mmcblk2p1 (un-mount the disk when you are done, shutdown, pull the sd card and reboot to emmc)
  12. Actually my original suggestion a few posts ago was to try all of the g12/sm1 dtbs and find the one that works best for your hardware. To test the different DTBs, you will need to use the working sd card you have from earlier. Edit the uEnv.txt file and try rebooting with that sd card using the different dtb. When you find the dtb file that works best for you, you can either reinstall that entire environment to emmc by using the script (but doing so will overwrite everything you have on emmc), or while running from the sd card, mount the /boot partition on the emmc and edit the uEnv.txt file on the emmc directly. The command you are using to set the network speed (ethtool -s) does not persistently make that change, so you will need to do that after every reboot. I'm sure you could google and find a way to make that change persistent, but if you can get it working without manual changes it would be better for you.
  13. Have you tried all of the dtb files to see if any of them support your ethernet setup without needing to make manual changes? From above it looks like you are using: meson-g12a-x96-max-no-cvbs.dtb. I would suggest you try meson-g12a-x96-max-rmii.dtb which is a 100Mb ethernet version of the meson-g112a-x96-max.dtb file. Good to see that you have made overall progress today on your box.
  14. I would say that this will be the most difficult requirement to meet. It is very hit and miss (my experience is mostly miss) whether you will be able to get wifi working on any particular box. If you are able to, use wired ethernet and you will be much more successful, or alternatively purchase inexpensive usb wifi dongles that have linux mainline support. In addition to the poor support by the wide variety of wifi chips in these boxes by mainline linux, you can purchase identical looking boxes that have different internals, so just because you have something working on one box (or someone else does) doesn't mean it will also work for another identical looking box because it has a different wifi chip inside.
  15. You should not need to do anything with the u-boot file at this point as the file should already exist (as long as you copied instead of moved the file earlier) All you should need to do is: sudo /root/ Although what I do is become root and run from the root directory: sudo su root cd root ./