dbsharpe

Members
  • Content Count

    104
  • Joined

  • Last visited

 Content Type 

Forums

Member Map

Store

Crowdfunding

Applications

Calendar

Posts posted by dbsharpe


  1. 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.


  2. 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.


  3. 1 hour ago, InTheWings said:

    I've spent more than half a day trying to boot "H96 Max X3" from sdcard. :angry:

     

    I really think the Amlogic instructions section lacks a big fat warning about this. 

     

     

    Sorry, the thread starter by the author has a disclaimer:
    "For all. I don't support s905x3".
    There are specific forums for this box and AML chip.


  4. 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

  5. Edited by dbsharpe
    zcat typo


    On 8/28/2020 at 11:26 AM, jonesqpacman said:

    Please revert to old method (uEnv.ini)

    Not all SBC / STB supported new method ,my STB HG680P not booting in new method image (extlinux.conf),stuck in

    If you have an existing armbian installation, you can upkack (xzcat -d) the new installation image, mount (offset=) and copy the zImage, uInitd from BOOT and modules from ROOFTS - see this old post.
     

    It appears when you boot from sdcard, u-boot.ext is an executable chained via aml_autoscript and s905_autoscript.
    In summary, if you want the old method you will need old version of the above boot files plus the uEnv.txt (and delete u-boot.ext).
    I did this because at first I was getting "card did not respond to voltage select" errors with a dev image.
    However, it goes onto attempting to boot from LAN on eth0 including acquiring .dtb.

     

    One question somebody can help me with, what pxelinux.0 file should I use? My current pxe server (dhcpd and tftpboot) are for booting X86 clients/workstations.


  6. 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.


  7. 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.


  8. 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).

     


  9. 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.


  10. 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.

     


  11. 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.


  12. 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.


  13. 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).

  14. Edited by dbsharpe
    Additional discovery


    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).


  15. 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).


  16. 3 hours ago, dual3zw said:

    Well, using Armbian_20.02.0-rc1.037_Aml-s9xxx_bionic_current_5.5.0-rc6_desktop_20200205, on my H96 Pro H3, the wifi is not working. I took the output of dmesg on Android, it has this:

     

    Obvious question is does the file /lib/firmware/brcm/brcmfmac4334-sdio.bin exist which are part of the package linux-firmware? I don't have experience of that specific chip so can't say if the android firmware files would work in place of the armbian ones.


  17. 1 hour ago, almotra said:

     

    Without the colon and without the .d, still the same problem!

    I tried with

    - nano /etc/network/interfaces

     

    Wifi, BT & ethernet mac address have always been problematic with arm systems.
    Just google 00:15:18:01:81:31. I'd be interested to know where the aforementioned mac address comes from as I can't find it in the .dts or kernel source .h files.

    If your just using ethernet, you could use a custom boot script:

    systemctl stop NetworkManager.service
    pkill dhclient
    ifconfig eth0 down
    ifconfig eth0 hw ether 00:15:18:01:81:32
    sleep 2s
    ifconfig eth0 up
    systemctl restart NetworkManager.service
    ifdown eth0 ; ifup eth0

    may also need:

    ip rule flush
    ip rule add lookup main
    ip rule add lookup default

    before or after the code as run.


  18. 10 minutes ago, julian67 said:

    In future versions could you include a kernel headers .deb package? It would help a lot and is much preferable than the end user needing to set up a cross compile environment and repeat the work you already did. Thanks again.

    I'm prepared to be corrected but I've natively compiled the whole image including kernel under the most recent focal and bionic arm64 ubuntu distros from https://github.com/150balbes/Build-Armbian as per the authors post  so you should be able to build whatever driver needs includes & libs.


  19. 3 hours ago, gilberto said:

     

       22.116751] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4330/4 wl0: Oct 25 2011 19:34:12 version 5.90.125.104
     

     

    Assuming eth0 is working with a internet connation, try these commands in order under armbian as root (su -):

    cd /lib/firmware/brcm/
    mv /lib/firmware/brcm/brcmfmac4330-sdio.bin /lib/firmware/brcm/brcmfmac4330-sdio.bin.backup
    mv /lib/firmware/brcm/brcmfmac4330-sdio.txt /lib/firmware/brcm/brcmfmac4330-sdio.txt.backup

    wget -O brcmfmac4330-sdio.bin "https://github.com/armbian/firmware/raw/master/brcm/brcmfmac-ap6330-sdio.bin"
    wget -O brcmfmac4330-sdio.txt "https://github.com/armbian/firmware/raw/master/brcm/brcmfmac-ap6330-sdio.txt"
    rmmod   brcmfmac brcmutil
    sleep 3s ;  modprobe brcmfmac

    dmesg | grep -i ": Firmware: "

    The system should now report the following wifi firmware loaded:
    Jan 23 2013 17:46:35 version 5.90.195.114


    If this does not work, I'll describe how to determine the wifi firmware used by android but if they have the same digital file signatures, it will be no help to you.


  20. 9 hours ago, gilberto said:

    I'm trying to open the box and take a picture of the shipset wifi, I don't want to destroy it. I will lose the warranty. 

     

    the chipset appears to be.....

    Broadcom BCM4330

    https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx

    To check the status of wireless card, run

    rfkill list

    nothins is blocked hardware and software ok

     

     

    Assuming wifi hardware is functional in android, I think you need to try the firmware used in android - see ( firmware_path=/...... nvram_path=...).
    I've discovered recently that for BCM4330 wifi, brcmfmac-ap6330-sdio.bin works as a firmware file (on kernel 5.6.2 and 5.7.0-rc7) and fixes recent issues with WPA enterprise so try using  brcmfmac-ap6330-sdio.bin & nvram_ap 330.txt as replacements for brcmfmac4330-sdio.bin  & brcmfmac4330-sdio.txt respectively (in /lib/firmware/brcm).