• 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 seen various X problems when moving up through the builds. It can be down to kernel, dtb etc. If X is crashing according to fbdev in /var/log/Xorg.log, its probably the kernel or dtb (also after startx). If lightdm gtk greeter consumes 100% on 1 cpu, try to change the greeter - take some tips from https://cialu.net/how-to-solve-failed-to-start-session-with-lightdm-and-xfce/ Disabling selinux at boot fixes a lot of strange issues. At the end of the day, it seems to be better to move onto a different armbian build or back to a good one, particularly kernel files and modules.
  2. I've not seen your specific problem but with the newer builds (kernel 5.3.0-aml-g12 or dtb?) I have observed with a s905x: mmc driver does not like of my Sandisk extreme micro sd card (neither do 4.x kernels) - gives kernel crash / Call trace during startup and fails to boot selinux appears to be fully active so I have help from selinux=0 at the end of bootargs= in /boot/uEnv.ini
  3. According to /boot/config-5.3.0-aml-g12 in Ubuntu Disco, CONFIG_IPV6=m and can confirm ./kernel/net/ipv6/ipv6.ko is built. Can't see why the kernel would vary on this release.
  4. I've uploaded Armbian_5.37_S9xxx_Ubuntu_xenial_3.14.29_server_20171226.img.xz to megashares (md5sum a867b08685f25304847acfed7cc88803) - https://mega.nz/#!xqZgkQrB!g7HzYbusB0wifVxKbGwR-HPGETRvJMXyhu-u9SDy8pM If you want any others, let me know - I've got kernel 3.14.79 as well.
  5. I only have xenial, bionic and now disco builds - according to https://wiki.ubuntu.com/Releases , Ubuntu 12 pre-dates Armbian on AML tv boxes.
  6. Sorry, I only use Ubuntu and had downloaded debian by mistake. If your looking for 4.20.x kernel files only, I'd get on from yadi.sk and extract the relevant files from /boot & root:/lib/modules/4.20* and put them on your working environment.
  7. I've uploaded it to megashares - https://mega.nz/#!0jxX1KBD!iws8Ojo_zJ5K7SllQ7c7xphP8SAbanMP6YypqnMnbbM File details - Armbian_5.44_S9xxx_Ubuntu_bionic_3.14.29_mate_20180601.img.xz - 706438108 bytes, md5sum 8ee5fe48fbd0a255915b696bda170cf
  8. Don't know but this post might help determining the board type (dtb to use): https://forum.armbian.com/topic/2419-armbian-for-amlogic-s905-and-s905x-ver-544/?do=findComment&comment=66212 If not, you'll have to try every dtb and be patient - even though the screen isn't working, ethernet and usb might be - see https://forum.armbian.com/topic/2419-armbian-for-amlogic-s905-and-s905x-ver-544/?do=findComment&comment=58673
  9. I've uploaded it to megashares - https://mega.nz/#!g3xiFYgb!yzBHGRfaICeFSd7l8eJgEIdb3viHXBKuaHTNMYnrf5E File details - Armbian_5.37_S9xxx_Ubuntu_xenial_3.14.29_mate_20171226.img.xz - 843185252 bytes, md5sum aae9310959de43cdf3984d3105892bef
  10. I had issues with hostapd but I don't recall the exact problem. I got it down to the armbian kernel being a bit too new and perhaps a bug had crept in. The .config feature that wasnt working might have been multiple ssid's or higher speed wireless 802.11n. Work around was to get hostapd sources a couple of years old and compile it. I use rt2xxx based hardware and don't recommend the internal wifi devices.
  11. What driver/chip do you want to build? Your better off getting the correct kernel source from https://github.com/150balbes/Amlogic_s905-kernel (or armbian build) if its a popular driver not enabled in the current /boot/config. Search these forum threads for build instructions.
  12. Have a look at this post. It may be the firmware between android and Linux (/lib/firmware/brcm) is different and android may work better. You'll have to do some work in android working out which one is in use and which files (usually at least 2 files) and if they differ. Don't mix DTB's between distros (Android to Linux or Linux to Linux with a bit less caution).
  13. It's been the same issue for years, down to clone copies. I've got 2 T95 boxes which are S905X - one is p201, the other is p212. The only way to find out what your getting is to persuade your supplier to provide you with a copy of /system/build.prop from android (looking for build.product line)
  14. I'd say no modules are being loaded at boot possibly due to kernel name / magic not matching (uname -a on the install image kernel vs compiled kernel). Otherwise, check your using the same tool chain (shown with cat /proc/version on the target) but I've only seen that issue being pertinent with android phones running old kernels. Check you are using the correct source.
  15. Try this as a start - https://forum.armbian.com/topic/7930-armbian-for-amlogic-s9xxx-kernel-41x-ver-555/?do=findComment&comment=71135 . You will probably need output of dmesg from android to get your flash layout.