Jump to content

dbsharpe

Members
  • Posts

    118
  • Joined

  • Last visited

Everything posted by dbsharpe

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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).
  6. 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).
  7. 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.
  8. 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.
  9. 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.
  10. 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
  11. 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.
  12. The only stretch I have is Armbian_5.44_S9xxx_Debian_stretch_3.14.29_xfce_20180601.img.xz and I've uploaded it to https://mega.nz/file/ArB2iQaL#iiPzjAjSFjLTdeq-OZt_kwYhjoXeDam9Xq0E_5PfNVc 760820516 bytes on disk with md5sum de4c8de5f5a360b8d41e67c32a9cf90d.
  13. I have the following images I can share but they are Ubuntu: Armbian_5.78_Aml-s905_Ubuntu_bionic_next_5.1.0-rc5-next-20190416-gde3c659c8-dirty_desktop.img.xz (no zram module) Armbian_5.86_Aml-s905_Ubuntu_bionic_default_5.1.0_desktop_20190514.img.xz Armbian_5.91_Aml-s905_Ubuntu_bionic_default_5.1.0_desktop_20190708_s905_s905x_s912.img.xz Armbian_5.94_Aml-g12_Ubuntu_bionic_default_5.2.1_desktop_20190821.img.xz Armbian_5.96_Aml-g12_Ubuntu_bionic_default_5.3.0-rc8_desktop_20190910_s905x2_s922.img.xz Armbian_5.96_Aml-g12_Ubuntu_disco_default_5.3.0-rc8_desktop_20190910_s905x2_s922.img.xz
  14. I'm not familiar with your Wetek Play 2 hardware so I can't give a definitive answer. Generally, BT doesn't work (so get a $1 USB BT dongle) in Armbian and wifi is patchy. I found for my specific hardware that the firmware files are incorrect (and still are 2 years later) - see this page. To figure this out, you will need to boot into android, find the module load command (ie in my case insmod/modprobe dhd.ko firmware_path=/...... nvram_path=/......) and find all the firmware files. Compare what you have with what armbian /var/log/syslog reports.
  15. To build the whole image, see https://github.com/150balbes/Build-Armbian but its a bit involved. You can google forum.armbian + github.com/150balbes/Amlogic_s905-kernel which is just the kernel. Can't tell you what branch of this kernel source tree to use and can't say if all the required patches are there (as they may be applied in the Build-Armbian repo).
  16. Have a look at https://forum.armbian.com/topic/12162-single-armbian-image-for-rk-aml-aw/page/10/?tab=comments#comment-96403 So that will be selinux=0 at the end of the APPEND= line in /boot/uEnv.txt It's only a work around but it would be nice to get a fix.
  17. The only debian ones I have are: Armbian_19.11.3_Aml-g12_buster_legacy_5.3.0_desktop_20191126_debian.img.xz Armbian_5.44_S9xxx_Debian_stretch_3.14.29_xfce_20180601.img.xz If its something from this year, try the single image TV box forum page.
  18. Can you be a bit more specific, perhaps quoting full image file names, kernel level etc? I have a number of 'archive' images but mainly Ubuntu.
  19. I've done this (upgrading just kernel) previously and you need all the other /boot files from the 'new' (5.6-rc7 ) image. I've not worked out which files are key but you need u-boot*, emmc*, *autoscript_* etc. AFAIK, kernel and initrd should be named /boot/zImage & /boot/uInitrd still. Best to make sure the 'new' (5.6-rc7 ) fresh image boots from a fresh sdcard first and then work from that, which you've probably done.
  20. Can't comment on your specific hardware but see point 3. of https://forum.armbian.com/topic/2419-armbian-for-amlogic-s905-and-s905x-ver-544/?do=findComment&comment=58673 I have TWRP custom recovery on one of my tv boxes so I can issue the reboot update command from a shell in recovery.
  21. The kernel is at https://github.com/150balbes/Amlogic_s905-kernel (and therefore headers) but from previous posts by the developer, the source updates are not pushed online to github until some time afterwards. I don't think all patches are in the github kernel source as the bootable images are built with https://github.com/150balbes/Build-Armbian which seems to apply additional patches when you cook your own armbain images. IMHO, separate headers would be too much work but prompt up to date kernel source would be nice.
  22. Hi, I've uploaded it to megashares: https://mega.nz/#!N3AUWYQa!_IFkdHuTdh7Ynp9sLzaVyVj3BwDKJJRD7YFOlSEF6H0 Size on disk is 813558412 bytes and has an md5sum of 9d8a0b0868f51a6fcf33ca2bcbad6097.
  23. See this post about selinux and apply it to the relevant boot cmd file. https://forum.armbian.com/topic/7930-armbian-for-amlogic-s9xxx-kernel-5x/?do=findComment&comment=91407 and check selinux is disabled with sestatus command. I've found .dtb, sdcard & selinux causes most issues currently with armbian builds.
  24. Had the same issue at boot - https://forum.armbian.com/topic/7930-armbian-for-amlogic-s9xxx-kernel-5x/?do=findComment&comment=91407 From historical observations of the forum, the SD card is always blamed as faulty. A bug seems to have cropped in to kernel & dtb. 3.14.xx kernels don't have a problem with the sd card.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines