dbsharpe

Members
  • Content Count

    37
  • 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'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.
  2. 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.
  3. I have two T95's - one is p201, the other is p212. Armbian_5.73_Aml-s905_Ubuntu_bionic_default_4.20.2_desktop_20180129_img.xz (lima) contains the working dtb's. (see forum.armbian.com/topic/7930-armbian-for-amlogic-s9xxx-kernel-41x-ver-555/?do=findComment&comment=72165 )
  4. I've had to use DTB's from other Armbian builds to get snd_soc_meson working.
  5. I'd like to know - startx does not work for me so I have to boot into android to fix this as the screen resolution appears to be too low booting Armbian. Small script to solve would be nice.
  6. Can't help with the firmware problem as I've not run 5.0.0-rc4 but can you expand on the WiFi-regulatory.db issue and any fix. I've had intermittent issues with wifi AP's and this message in dmesg / syslog. Thanks.
  7. The answers are in this forum but 1. see https://forum.armbian.com/topic/7930-armbian-for-amlogic-s9xxx-kernel-41x-ver-555/?do=findComment&comment=68879 2. see /boot/config* on the target tv box. 3. depending on changes, you just copy from the buildhost modules into /lib once you've tested them and copy arch/arm64/boot /Image.gz to /boot/zImage
  8. I'd try the .dtb filename your using from another .img build (more recent). I've found this works for me. Comparing the decompiled .dts source, the only difference was positioning of some statements in the structure (TBH, I pull the /boot and /lib/modules/ files out of the image when a new one is released).
  9. I'm using a meson-gxbb-p201.dtb box and have noticed issues from version to version (i.e. sound on kernel 4.20.2) as well as screen powered off. Had to use systemctl restart lightdm.service to get the screen back. Problem are fixed by using the dtb from Armbian_5.73_Aml-s905_Ubuntu_bionic_default_4.20.2_desktop_20180129.img.xz (even though I'm running 4.20.2-aml-s9xxx kernel)
  10. What is the current status of AMAUDIO/AMAUDIO2 (audio through HDMI from 3.14.29 amlogic kernel source) into 4.2x or NEXT 5.0 kernel builds for S905?
  11. You will need to mount (/mnt) a partition in emmc with enough space and issue: dd if=/dev/zero of=/mnt/512mbfile.bin bs=1024 count=512000 which will report speed in bytes at the end. Its difficult to a read test due to the caching element but dd if=/mnt/512mbfile.bin of=/dev/null bs=1024 will give you the speed of RAM if you run read test after write!
  12. Your correct but under android or older 3.14.x kernels, aml_sd_emmc presents all the flash partitions laid out but with more recent 4.x and above kernels, meson-gxbb-mmc is one device according to /proc/partitions
  13. I've not installed on emmc as I've never used usb burning tool to unbrick a tv box. Not impressed with the write speed when mounting existing emmc flash partitions. For example on my T95 S905, the data partion mmcblk0p14 based on the android boot information can be accessed with mount -t ext4 /dev/mmcblk0 /mnt -o loop,offset=2545942528,sizelimit=5272240128 Can't suggest much with emmc apart from it will probably be a .dtb issue.
  14. If I had problems with a driver, I'd probably try going back a few kernel versions to see where the ethernet speed was OK or started faltering. The name of the module should be listed (from a shell) in /sys/class/net/<ETHERNET IF NAME>/device/uevent . If the kernel is at fault, possibly look at the source code and see if the developers/modifiers has an email address in the .c or .h files you could use to contact. I find most device problems in Armbian are related to .dtb files or firmware files. Having said that, have you tried ethtool under Armbian (assuming you get full speed when booted to android) and manually set the interface speed and duplex?
  15. I think gnthibault I've mentioned this before in forums but is it possible confusion may be occurring between duplicate partition labels? In fstab, you have LABEL=ROOTFS / and in uEnv.ini etc bootargs=root=LABEL=ROOTFS What I'm saying is the internal emmc flash and sdcard may have the same ROOTFS label. Perhaps take the sdcard and relabel the ROOT partition with tune2fs or get UUID= value from blkid (and changing boot files in /boot/ and /etc/fstab ?