• Content Count

  • Joined

  • Last visited

About dbsharpe

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. 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.
  2. 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).
  3. 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.
  4. 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.
  5. 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.
  6. 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 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.
  7. 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).
  8. Github repository for the kernel source is at https://github.com/150balbes/Amlogic_s905-kernel and also includes the headers (source info is missing from this thread topic open post).
  9. Echoing what's been said, you need to find out what hardware you have and if any drivers are available. As an aside, the latest builds of Ubuntu focal seems to have an issue with wpa_supplicant (v2.9) on my internal adapter but its just WPA enterprise with certs, PSK seems ok.
  10. TV boxes can be anything inside despite being identical so you have to dig around. If I was in your position, I would boot into android to determine what wifi chip you have and what firmware file it uses - see this post plus whats in /sys/class/net/. The type of AMLogic hardware 'details' can be determined from this post which give you an starting point for the dtb file that is required. Wifi & BT are not guaranteed to work as per the developer/forum thread originator. Hardware can be supported one day and then the next release a bug creeps into the kernel or dts. You also need to try every dtb file.
  11. Your dmesg implies your built in wifi might be RTL8723BS but I couldnt tell you about kernel / dts support for it. Have a look at this post https://forum.armbian.com/topic/2419-armbian-for-amlogic-s905-and-s905x-ver-544/?do=findComment&comment=65706 (which you probably know anyway how to probe) and my other posts about hardware. You've not said what box/hardware you have - it may be covered by one of the other forums topics.
  12. Unfortunately, you can't guarantee 2 of the same box will have identical hardware so its pot luck. Getting a box with S905X chip historically was a good bet for Armbian but things have moved on. I'm looking at S905X3 based boxes even though there are some Armbian compatibility issues. Acquiring one 2nd hand from ebay may limit your losses if you get something too slow or incompatible. If any other forum users could make hardware recommendation, here are my key requirements: - Gigabit Ethernet - Usb ports (connect 2 external drives, mirrored with /proc/mdadm device - enough CPU & RAM to Run VNC server for virtual desktop for browser (thin client, cloud etc). Nice to have - wifi
  13. Try /amlogic/meson-gxbb-p201.dtb and then every other /amlogic/ .dtb file. Failing that, use usb ethernet or try an older armbain image. Bugs creep into the kernel and dts file so things start and stop working. Also https://forum.armbian.com/topic/7930-armbian-for-amlogic-s9xxx-kernel-5x/?do=findComment&comment=71063 might be some help.