Jump to content

Povl H. Pedersen

  • Posts

    21
  • Joined

  • Last visited

 Content Type 

Forums

Member Map

Store

Crowdfunding

Applications

Everything posted by Povl H. Pedersen

  1. But maybe one vendor could be convinced to pay for support, and become the preferred TV-box vendor
  2. If what balbes150 is doing is just dropping support, then everything is fine with me. Forked what I believe are the relevant github projects. My current boxes are running fine, but really wanted an upgrade before moving more onto it. I have 3 S905x3 boxes BTW. If balbes150 is pulling everything offline, and releasing intentionally destructive builds, as I read it, then it is bad. Now, Amlogic is an american company, and I really would expect them to fork over some money to help Armbian. They likely spent money getting Android running. I would like everybody to reach out to Amlogic, and try to have them send money in the direction of Armbian. I guess that is the easiest way to get more support. The cheap chine copycats likely do not want to put money in that direction. Personally, I buy TV boxes because they are way better value for money than the Pi 4. For less money I get a faster CPU, I get eMMC onboard, I get hardware crypto support (Raspberry foundation did not license that), I get a box, and I get a PSU. So the TV boxes are way better value for money. Now, if the Armbian project would recommend brands or models of TV boxes (they seems to be best value for money due to mass market production), I would plan that for future purchases. Maybe some vendor (Beelink whatever ?) would be willing to contribute money for Armbian support. For me, I need 64-bit, 4GB memory, 1 Gbit, ethernet, preferable WiFi, quad-core - good performing CPU not too hot, Hardware crypto, USB 3.0. Don't really care about graphics/sound, as they run headless. And I can do without the I/O of the Pi, using ESP32 for sensor integration. OrangePi, Odroid C4 etc are valid options. But way more expensive. Have some hot running, not too good performing OrangePi devices. Only using one for my 3D printer. I likely do not have the skills and surely not the time to take over support. But as long as we have the current release to start from, then I am happy. Then I can always look at upgrading the kernel if I need. Otherwise, I will just have a stable running box (I hope) for many years to come. Saving the environment lots of CO2 compared to my old AMD x86 based server.
  3. Introducing creeping errors / timebombs in systems is so anti-community/ OSS as it can be. I understand if you drop support, even drop it completely. It works, or it doesn't work. If I had to pay you $10 for a license, I would do that, I have no problem with that. I have created a couple smaller OSS projects as well, and contributed to soma larger ones, but not spent nearly the amount of time you have. I understand the amount of effort that goes into OSS. But you destroying other peoples work because they used software based on Open Source if not a good thing to do, and might actually be illegal in many countries.
  4. My H96max crashed today. Would not boot. is there any way, apart from full reinstall to get it bootable again ? it would only come up with the android recovery. could reboot from SD and create data backup. But still takes time to get the rest of what I need installed. HomeAssistant, so mostly docker containers. But my HA backup is a bit old. But I do have the data dirs but it is not the same.
  5. USB Burn tool worked fine. Read somewhere that I needed the cables, so had them in the bin with all my other recovery interfaces / cables. Now, I have a feeling that I could have used fatload of the image from uboot, and then written to eMMC. Had a little doubt if I should write the image at address 0 or 0x100 ? Nobody tried this ? Should be pretty easy to copy eMMC with dd - to the USB, and then fatload / write it back from uBoot. At least in theory. I know for most people UART access is scary, but now I have my Dupont cables soldered on the pads.
  6. How to do that ? I assume fatload image (made with dd), and then write it to eMMC ? But how to I write it to eMMC ? Can I boot the USB and use Linux to restore eMMC ?
  7. Here it is. Now I am also getting intrigued and want to learn a bit more about u-boot. I assume the addresses to use comes from the hardware docs ? I have included printenv as well below. Also has some addresses. I can not write the dtb. Partition table error. So I likely need to know what commands to use to boot from the USB, and then when booted, use the install script to repartion eMMC. I can read files into memory with fatload etc. And use that to read a device tree and set ftd address as seen far below And the printenv Store dtb fails:
  8. I can do usb start, fatls etc - So how do I get on from here, assuming the dtb is bad ? (aml-storage etc not found). Possible some fatload and booti (boot Linux image) ? I have loaded dtb, and fdt print works. Bot I do not know which addresses and parameters to use for everything. fatload the uInitrd to 0x20000000 and booti 0x20000000 fails. g12a_u215_v1#booti 0x20000000 libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND [rsvmem] fdt get prop fail. Bad Linux ARM64 Image magic! I am completely new to u-boot, so need a little more help / pointers in the right direction
  9. Booted, made backup, tried to to fresh install. Always booted with SD = / and /boot Made things worse, recovered and installed with the s905 script. Seems now things are wrong. Can't find DTB. Any idea how to recover now ? Still boots u-boot and loads a file from sdcard And seems I can interrupt u-boot process and go interactive. I do have another equivalent box, still new-in-box, so I have a eMMC image backuup there. Also a snapshot = TWRP backup
  10. Thanks, I picked another existing DTB, and that worked for booting. Now I need to install latest snapshot after getting backup. And will put it in /boot
  11. Just checked dpkg log, no kernel upgrade, but linux-image-current-arm-64 is the one at fault. It owns /boot/dtb Now, how do I upgrade everything ? Is there an easy way ? I run almost nothing but HomeAssistant, so I can of course create a HA backup, and read back in on a new system. That is trivial. But I do not necessarily know all the other stuff I set up. I know for sure I do have an outgoing VPN connection to my cloud server that is reverse proxy to my Home Assistant. I do plan to run DHCP/DNS on it, and my USB weather station, and other things for my home automation. Possible even video surveillance - Playing with motion detectors covering camera FoV, so I do not need a constant stream inflow. So we need a way to upgrade. One reason I picked 905x3 is that it performs well for the price according to: https://androidpctv.com/comparative-amlogic-s905x3/ Way better than H6 and RK3328. I am not looking at $100+ devices, then we are close to Intel land, and I would end up in the $250-300 range because I would got for a 8250u or better then. So I am looking at sub $50 boxes for best price/performance/watt.
  12. It is supported by this distro, and thanks for that. eMMC install works, and there is even an install-aml-sxxx script. What is recommended chipset for good performance if I want something else ? The issue is, that /boot/dtb was renamed to /dtb.old and since my dtb was not in, it would not boot. Booting from SD also was not good before I pointed uEnv on card to a standard dtb which I could use to boot. Seems like SD boot switched to eMMC
  13. I am also on H96 Max, with the custom DTB from this thread. apt upgrade today also killed my box. ANd for some reason my SD card also had 2 blank partitions. Did not figure that out before after I had soldered UART wires onto the board. Anybody knows what package destroyed things ? We need to get the maintainer to fix it to stop bricking devices. Currently in the process of burning new SD
  14. Using the UART I get to some recovery. Now, how can I save data, find out what is wrong, and start from scratch ?
  15. I have a dead H96 Max, S905x3, 4GB/128GB. After an apt upgrade and reboot it never came to life. I use the Single Image, boot from eMMC. WIll not boot recovery either (pin in audio slot pressing the buttin). Red LED is on. fter 5s or so TV stops saying no signal and goes to an almost dark screen that becomes black. Also tried with SD card, with and without recovery button. Guess a hardware issue ? Will I get anything usable from soldering a serial port connection ? eMMC is marked SDINAFF4-128G, made in Taiwan, so possible a Sandisk quality component. But they etched the brand name away. Most annoying is that I lost all the data, was using it as a generic Linux box.
  16. I am running this distro on my H96 Max (S905X3), 4/128GB for about a month now. I am running into problems with exec format error on 32-bit ARM (v7l), and have had a few github projects fix their code so their arm64 aka aarch64 is actually 64-bit. But some things I can not recompile, most important libwidevinecdm needed for streaming video. Is the missing support for 32-bit binaries a kernel configuration ? Or is it a real hardware limitation ? This page seems to indicate it can run 32-bit stuff. https://androidpctv.com/comparative-amlogic-s905x3/ - there it is running 32-bit only. This page indicates it should be possible in general
  17. H96 Max box here, S905X4, 4GB RAM, 128 (116?) GB eMMC. Boot fine from SD card. used DTB found page 7 this thread. Ran ./install-aml.sh - everything looks fine. But, it ill not find anything to boot when I reboot / power cycle. After the flash it will not clean boot the SD card either. Only solution is pressing the reset button in the AV jack. Any help to get it to boot from internal eMMC please. I do see the 4+0 records in/out, indicating boot sector is written. But it just gives me the spinning logo to show it is loading or looking for something. I even tried to make the eMMC FAT partition bootable in disk. Just for info, my built-in eMMC is mmcblk2 while installing. Not sure if the numbering changes anything ? root@arm:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT mmcblk1 179:0 0 29.8G 0 disk ├─mmcblk1p1 179:1 0 256M 0 part /boot └─mmcblk1p2 179:2 0 29.3G 0 part / mmcblk2 179:32 0 116.5G 0 disk ├─mmcblk2p1 179:33 0 244M 0 part └─mmcblk2p2 179:34 0 115.6G 0 part mmcblk2boot0 179:64 0 4M 1 disk mmcblk2boot1 179:96 0 4M 1 disk zram0 254:0 0 50M 0 disk /var/log zram1 254:1 0 1G 0 disk [SWAP]
  18. Answer to myself (and others) - you need the right dtb. Did that, and it boots. Found in the single Armbian image thread. Only issue now is funny colors, and that it reboots (nice shutdown) on entering root password. Tried using ssh and I am asked to change password. Strange behaviour. No way to install to eMMC - tools not included - tried eoan. Now trying Bionic. Both aoen and bionic fails to reboot from SD. Goes in a reboot loop. Powercycle and it boots ok. Next problem, no install menu option, and no nano-installs script. You have to look in the homedir of root :-)
  19. Just got an H96 Max X3 (S905X3 based). 4GB RAM, 128GB eMMC. So a great Linux box (or so I thought). It does not boot from the SD as far as I can see. I managed to use the TWRP for Android 9 by booting in recovery mode, and do have a copy of everything. Tried to run the AML-Autoscript. I has to be renamed to UpdatePackage.zip to be found from updater (I made a copy, and copied aml_autoscript and aml_autoscript.cmd to start with UpdatePackage as well. No luck. When it reboots to update, I get errors as below. Any help/pointers welcome. Google is not much of a help here. Seems to be a Lenovo thing mostly. And I can not find anything in association to aml-config Supported API: 3 charge_status 2, charged 1, status SUCCAESS, capacity 100 Finding update package Opening update package E: Block map file too short: 3 E: Map of '@/cache/recovery/block.map' failed E: failed to map file Installation aborted
  20. Is there an updated distro for the RK3188 ? (Quad core A9, ARMv7) I have been looking around but not been able to find something newer than Ubuntu 12.02, or an old Linuxium Found this old stick in a drawer, and want to repurpose it to a headless Linux box. 2GB RAM. My goal would be to run Home Assistant on it, which does run on the Pi 3 Model B. So I assume the 20% better performance of the A53 would be offset a bit by having twice the RAM. I think it is better to repurpose it than to throw it out.
×
×
  • Create New...