dbsharpe

  • Content Count

    118
  • Joined

  • Last visited

Posts posted by dbsharpe

  1. 12 minutes ago, segv said:

     

    Unfortunately it now says "LABEL=ROOTFS does not exist" :-(

    I don't see why it would have disappeared but I shall try to debug this tomorrow.

     

    You may have seen some other messages skipping past at boot complaining about mmcblk meaning the dbt/kernel is not recognising the sdcard or its controller. In single user mode, busybox blkid and cat /proc/partitions may show them missing.

  2. 11 hours ago, ndthuan95 said:

    Hi, i tried and it works, thanks.

    But i think its not stable, internet speed is slow, just around 50-100KB/s, in android its 1200KB/s

    Btw, i did not see nvram_ap6330.txt in armbian, so i copied that file from android, is that ok?

    Looks like the nvram file is now brcmfmac-ap6330-sdio.txt in focal Ubuntu package armbian-firmware
    according to apt-file search brcmfmac-ap6330-sdio.txt .
    There are various versions of brcmfmac4330-sdio.bin (and others with different file names) so experiment with different ones to see which is best. I don't know if the ones in packages armbian-firmware, armbian-firmware-ful & linux-firmware are identical.
    You will probably find a few different ones in under android /etc/wifi which you could try - you'll have to rename etc the binary file to brcmfmac4330-sdio.bin. See also this previous post.

     

  3. 12 minutes ago, ryuchaing said:

     

    I already managed to start Armbian_20.10_Arm-64_focal_current_5.9.0_desktop with meson-gxm-q20.dtb and it is the only one that worked for me, the ethernet connection, the WiFi and Bluetooth does not work for me.

     

    The tv box name (TX3 mini) like a lot of boxes has little relation to the hardware inside.
    Try this forum post - seems to have worked for quite a few different boxes having wifi issues.

  4. 46 minutes ago, Dragao said:

    It throws an error "sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set" 

     

     

     

    I've seen these permission issue posts a few times before but never had them myself or know why they occur.
    stat /usr/bin/sudo on my system shows 4755 owned by root.

    After logging in, try the su - command instead of sudo winch will switch you to root (or login as root).
    See this link about single user mode to change permissions (chmod 4755 /usr/bin/sudo ; chown roor:root /usr/bin/sudo).
    Bit elementary but the only help I can offer.

  5. 3 hours ago, odin said:

    I am getting this error for wifi anyideas?
    [   10.999555] ath10k_sdio mmc2:0001:1: Failed to find firmware-N.bin (N between 2 and 6) from ath10k/QCA9377/hw1.0: -2

    When I had wifi and firmware issues in Armbian, I used the firmware found running under Android.
    I'd also look at the linux kernel source code for the particular module loaded to find out the firmware file names, usually defined in the .h header files

  6. 13 minutes ago, Bozza said:

    It is an exfat drive, which I have now found out that it doesn't support symlinks.

    Without formatting to exfat is there a way to use simulated symlinks instead? Perhaps hard links?

    If it was NTFS (and not a FAT derivation that has a size limit of about 4Gb file size), I would suggest creating an empty file about 20Gb in size with dd if=/dev/zero of=./20gb_filesystem.img.ext4 bs=4k iflag=fullblock,count_bytes count=20G . Format the file with  mkfs.ext4 ./20gb_filesystem.img.ext4 and mount with mount ./20gb_filesystem.img.ext4 /mnt which will give you a linux filesystem in a file.

  7. 12 minutes ago, Bozza said:

    Operation not permitted

     

    "

    Is the disk under /media/root/Seagate NTFS? It needs to be Linux ext3/4 etc and make sure
    /media/root/Seagate/armbianbuild has chmod a+rwx to rule out any permissions issues.

    If I was encountering issues I could not fix, I'd use strace -f -o /tmp/trace-build.txt ./compile.sh and examine

    /tmp/trace build.txt at the end.

  8. 11 minutes ago, iKPYT said:

    Thank you for the information.
    But I didn't get it, are you building on a TV box? I think using flash devices for multiple rewriting is not a good idea in terms of flash resource limitations.
    I am building on a computer with an HDD drive

    Yes, I am building on a H96 max x3 TV box (AML S905X3) running Focal arm64.
    You can build on a tv box running Armbian booted from sdcard but the location for storage before issuing the command git clone https://github.com/150balbes/Build-Armbian should be internal flash/EMMC/NAND, high speed external wired storage or network storage (ie from your 'computer').
    About 10Gb needed. Might take half a day.

  9. 18 hours ago, iKPYT said:

    However, an attempt to build a version for TV-box ends in failure.

    git clone https://github.com/150balbes/Build-Armbian
    ./compile.sh

     

    Why doesn't this work, what am I doing wrong?

     

    At the same time these post appeared, I was able to natively compile balbes150 Armbian under Focal arm-64/aarch64.  Haven't tried recently.

    Top tip, make sure CCACHE isn't using slow sdcard storage. I used a H96 max x3 and pointed it to a folder in /tmp as it boots with RAM Memory: 2429544K/3535872K available.

  10. 1 hour ago, czosnekltd said:

    Maybe I found the source of the problem with RDP not working:
     

    Can you get around as this?

    As far as packages go, I find focal seems to have less than bionic. As a work around for other none specific packages, you could download the from the bionic repo with wget and install with dpgk.
    If you get complaints about dependcies, you could manualy copy in the files after extracting them from the package with ar x pkg.deb ; tar -xvf data.tar.xz

  11. 19 hours ago, Rajesh said:

     

    I would like to add a wifi device driver to the Build-Armbain code to build it with the kernel. The driver source is for ssv6x5x which is working on ARMv7 devices.

     

     

    Having taken a quick look at the ssv6x5x sources available, there is no way you'll get a 3.4.x kernel driver working on
    a 5.x system as the interfaces have changed. Anyway, wifi drivers beginning s**** are pretty much toxic on this forum and other aftermaket O/S boards.

  12. 5 hours ago, Vasy said:

    from Armbian_5.44_S9xxx_Ubuntu_bionic_3.14.29_mate_20180729.img that seemed to detect all memory). Still no luck.  I have no UART interface :(Please tell me, is there an available uboot version for the latest armbian releases that can detect the memory fine? Many thanks.

    In the absence of a u-boot file, this is how I was able to work round it but you still need to boot from sdcard but run root from flash.
    You will need to restore an operable android image with USB Burning Tool or restore full backup of internal flash.

    On my p201 S905X device, I was able to format all (most) of the internal flash apart from the first 108Mb (arbitrary value)
    which excludes the bootloader  (something like mke2fs -F  -t ext4 -m 0  -L ROOT_EMMC  -E offset=113246208  /dev/mmcblk1 [ -< device for internal flash]  )
                                                     
    You can get your flash layout from dmesg after booting into android. You will also need to know how to unpack & pack  uInitrd. Your custom boot uInitrd will get overwritten if you install or upgrade certain debian packages.
    I no longer have the RAM issue and was able to make some use of those fake microsd cards I've collected over
    the years.

  13. I don't have much experience of booting and running from internal flash but the usual forum response to such failure is that you have NAND and not EMMC in your tv box.
    Assuming /dev/mmcblk1p1 and /dev/mmcblk1p2 file systems are good, you could work around by booting off sdcard but mount /dev/mmcblk1p2 as your root file system. Check internal flash /etc/fstab is OK and modify /uEnv.txt on the sdcard to point to flash /dev/mmcblk1p2 (APPEND=root=LABEL=ROOT_EMMC).

     

  14. 43 minutes ago, Gaurav said:

    "unable to mount udisk: no file or directory

    Failed to open /udisk/aml_autoscript.zip"

     

     

    Personally, I encourage my tv box to boot into Armbian by issuing the command 'reboot update' in a shell terminal under android or power up with the toothpick method (poke the button inside the A/V port).
    After that, make sure your flash sticks /uEnvv.txt is correct with a just the irelevant lines commented out apart from the ones used.
    You may have to read page 1 of this thread again regarding u-boot after checking uEnv.txt about 10 times.

  15. 1 hour ago, Rajesh said:

     

    You are lucky to have that working. I have a TX3 mini with ssv6501 and could never make it work.

     

    I also have a QBox (S905X) having exact same situation as you see with BCM4330. The dmsg messages are exactly same.

     

    I tried this but it does not work for me.

    mv /lib/firmware/brcm/brcmfmac4330-sdio.txt /lib/firmware/brcm/brcmfmac4330-sdio.txt.old
    ln -s  /lib/firmware/brcm/nvram_ap6330.txt  /lib/firmware/brcm/brcmfmac4330-sdio.txt

     

    The config.txt has these content:

    PM=0
    nv_by_chip=1 \
    43362 1 nvram_ap6210.txt
    43430 0 nvram_ap6212.txt

     

    So I tried linking nvram_ap6210.txt and nvram_ap6212.txt but it doesn't help.

     

    Guess there is more to it than I can perceive.

     

    -R

     

    On your qbox, which is probably p212, you might find this post of use:

    I don't think /lib/firmware/brcm/config.txt is used in linux currently.

     

  16. 30 minutes ago, winit_a said:

    Tonix TX3 Mini   WIFI don't work

    how to config

    Armbian_20.07_Arm-64_focal_current_5.7.9.img.xz

     

    info Tonix 3 mini

    used firmware TX3Mini-20181210.img can boot armbian

    if used TX3Mini-S905W-20191008.img firmware boot into android recovery only can't boot armbian

     

    I've had one of these boxes but didn't run Armbian on it. The one I had was p281 and the copy of Android dmesg I have seems to indicate a TLL901X chip. I sold it as wifi support seemed lacking on libreelec.
    The Android system backup I have has many wifi chips to choose from in /system/lib/libhardware_legacy.so (according to /usr/bin/strings).
    You could start by looking at this post if your lucky and it is actually a broadcom chip.

    Also, you need to look in dmesg or /var/log/syslog for "firmware" regarding any load messages.

  17. I've managed to install Armbain to EMMC (internal storeage) for the first time (Armbian_20.06.0_Arm-64_focal_dev_5.8.0-rc3_desktop_20200629.img) on my 8/2Gb s905x p201 box by following install-aml-s905-emmc.sh by hand, line by line and it boots reliably from internal flash but with reduced RAM.

    Can anyone provide a bootloader/uboot for s905x 2Gb as mine is only showing about 800Mb  after flashing with /root/u-boot/u-boot-s905/u-boot.img .
    I'm able to build u-boot source and BayLibre u-boot but no idea what the output does.

  18. On 7/3/2020 at 3:14 PM, dbsharpe said:

    I've been considering for some time bootstrapping from sdcard but mounting the internal flash as root.
    If the /data partition is big enough, you could rm * everything and copy partition 2 from the sdcard.
    I'd assume the init script in /boot/uInitrd would need modifying as the root= argument in /boot/uEnv.txt APPEND= only accepts devices, uuid & labels (AFAIK).
    Note putting single in uEnv.txt APPEND boots to a shell at runlevel 1 which may help debugging etc.

     

    After considering, I'm currently running armbian Ubuntu Focal on internal flash (just the android /data partition) but bootstraping a p212 s905x from sdcard by making the following mods:

    uInitrd -> initrd:/bin/mount replace with ROOTFS/bin/mount  binary
    uInitrd -> initrd:/scripts/local  replace the line
           mount ${roflag} ${FSTYPE:+-t ${FSTYPE} }${ROOTFLAGS} ${ROOT} ${rootmnt}
    with
           /bin/mount -t ext4 /dev/mmcblk1 ${rootmnt} -o loop,offset=2545942528,sizelimit=5272240128

    copy sdcard ROOTFS to mounted flash and edit
    /etc/fstab  -> comment out #LABEL=ROOTFS  and add
    /dev/mmcblk1  / ext4 loop,offset=2545942528,sizelimit=5272240128

    If I return to booting from sdcard and running ROOTFS on sdcard, does anyone have any experience of how my box will behave if I issue these commands:

    mke2fs -t ext4  /dev/mmcblk1 ; sync ; reboot   (internal flash is /dev/mmcblk1).

  19. On 7/3/2020 at 2:06 PM, Rajesh said:

     

    @balbes150 If this has NAND and not eMMC, is there a workaround to create new partitions on the device. Thank you very much for useful tips.

     

    --Rajesh

     

     

    I've been considering for some time bootstrapping from sdcard but mounting the internal flash as root.
    If the /data partition is big enough, you could rm * everything and copy partition 2 from the sdcard.
    I'd assume the init script in /boot/uInitrd would need modifying as the root= argument in /boot/uEnv.txt APPEND= only accepts devices, uuid & labels (AFAIK).
    Note putting single in uEnv.txt APPEND boots to a shell at runlevel 1 which may help debugging etc.

     

    Edit ... additonal notes:

    1. Single user mode without mounting any disk file systems:
    APPEND=rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 single
    (with HDMI and usb keyboard, you can access a console).

     

    2. With some AML tv boxes, the kmsg error:
    ;EXT4-fs warning (device loop0): ext4_enable_quotas:5944: Failed to enable quota tracking (type=0, err=-3). Please run e2fsck to fix.
    may occur. This is error comes from kernel fs/ext4/super.c and is probably due to a module not being loaded early at boot (or some other sysfs tweak) to understand file system quotas.
    Work around is to mount the partition with losetup and reformat it with mke2fs -t ext4 (e2fsck does not fix it).

  20. 2 hours ago, Pank007 said:

    Hi, I am new to this forum and have been trying to follow the instruction to install Armbian on my Mecool K1 Pro. I have tried different dtb's but still no luck in booting into Armbian below is the link to the message that I keep getting.

     

     

    Initially after watching some recent youtube videos about Armbian, you need to check you've commented out all the lines FDT= * APPEND above # rk-3399 at the top of /uEnv.txt

    You will need to try all (amlogic) dtbs (I assume, don't have Mecool K1 Pro). Also check this page.

    Personally, I boot into (sdcard) Armbian by issuing the command reboot update in a shell from android (app).