• Posts

  • Joined

  • Last visited

Recent Profile Visitors

1898 profile views

lampra's Achievements

  1. To my knowledge, this option is available in armbian-config only for Ubuntu builds
  2. Just for the record here is the first "release" message archived!,1275.0.html
  3. Check the device tree. Only one change was needed I changed this in my board using armian-config `Welcome to Armbian 21.08.2 Focal with bleeding edge Linux 5.14.8-sunxi64` and reboot works
  4. I do not have any other A20 board. I will ask around my colleagues for a spare one. Though If indeed there is a spare cubietruck to be provided by any forum member I would gladly help maintain this board.
  5. Thank you for the clarifications. I do build my images or kernels from time to time, but what about newer kernel version patches? How will this work? Maybe it's not clear to me the meaning of CSC. Regarding LTS kernels, at least, say 5.10 with expected EOL in 2026, who is going to submit patches for newer kernel versions if there is no maintainer? Does this mean that if no one submits patches, the kernel will become stale?
  6. I can clearly see the point for the maintainers, but there is an issue with the old boards. For example, I have a cubietruck which I would definitely like it to keep being supported, and I could probably help to maintain it within Armbian. Though I do have only one board which works 24/7. To my understanding, I can not be a maintainer, as I can't test new releases on a productive board. So If no one has two pieces, then the board can not be supported. In this case, I expect that current owners have to freeze kernel updates and keep the board for some more months - years, or try to test and use plain Debian or other distros. Is there any other alternative?
  7. I use this script except the three last lines. For 1wire you could use this module, but you need to build it. For me it works
  8. I doubt that the maintainer tracks all discussions here. So for your benefit in the future and the benefit of the community, if you could spare some minutes (after the "next" days), go ahead and check the sources. If this is not already fixed there you could open an issue in GitHub linking here or, if you have the skills, send a pull request that resolves this issue (i.e. deletes the line).
  9. Not sure what you mean, but `armbian-config` provides experimental device tree editor. So if the difference is one added line, what happens if you delete this line in the current device tree using the editor?
  10. You can find here the uboot binaries from armbian and here the boot.cmd-src. I expect that they are no longer maintained. The binaries from openwrt should be compatible with armbian, I expect that you will need to use the armbian boot.cmd-src though, or modify it according to your needs and boot environment as described here. PS: Could you post here your current uboot version, your boot.cmd and your current uboot environment?
  11. I used the Debian manual to upgrade from Stretch to Buster but not on espressobin. You may face some minor issues with python (from 2.7 to 3) but nothing very serious on the system itself. Though, you need to check first the dependencies of other software that you have installed.IIRW, I had some issues with owncloud which I had installed before the nextcloud fork. There is also a major upgrade of uboot and boot.cmd on recent builds so you might need to flash the latest uboot also Are you booting from the sd card or from sata? You could probably try first with a dual boot system i e. set the priority in the uboot environmental variables and test the new builds for some time before upgrading your current system. Or you could keep your current system as is and try to setup/install the needed software on a new (eg 21.08) release and use dualboot if needed. About the stability, I also had issues on my v5 board, so I moved to openwrt 19.07 which is rock solid using overlay but of limited abilities. I am planning a test migration back to armbian in the next months now that the mainline kernel includes the recent patches. Openwrt has also produced uboot builds (look at the supplementary files) for recent distros
  12. My guess is that there might be some issue with the latest uboot. Similar issues were experienced previously here, but no clue of the source.
  13. I see some recent changes in the dts but probably nothing to do with sata. I also see that you have not installed the uboot package Can you provide the output of: cat /boot/armbianEnv.txt strings /boot/boot.scr strings /dev/mmcblk0 | grep "^U-Boot.*(" You might need to interrupt the last command (press Ctrl c) after a few lines of output
  14. I did the same and everything works on my cubietruck. Your Armbianmonitor is incomplete, there is no info from the previous boot that you claim no sata, so I can't help anymore.
  15. For anyone failing to build modules using the legacy bullseye image, I succeeded by creating a "source" link in the modules folder root@orangepizero2:/lib/modules/4.9.280-sun50iw9# ln -s /usr/src/linux-source-4.9.280-sun50iw9/ source root@orangepizero2:/lib/modules/4.9.280-sun50iw9# ll total 700 lrwxrwxrwx 1 root root 39 Aug 25 23:03 build -> /usr/src/linux-headers-4.9.280-sun50iw9 drwxr-xr-x 8 root root 4096 Sep 9 05:18 kernel -rw-r--r-- 1 root root 239753 Sep 9 05:19 modules.alias -rw-r--r-- 1 root root 245218 Sep 9 05:19 modules.alias.bin -rw-r--r-- 1 root root 27739 Aug 25 23:03 modules.builtin -rw-r--r-- 1 root root 12 Sep 9 05:19 modules.builtin.alias.bin -rw-r--r-- 1 root root 30895 Sep 9 05:19 modules.builtin.bin -rw-r--r-- 1 root root 24568 Sep 9 05:19 modules.dep -rw-r--r-- 1 root root 39138 Sep 9 05:19 modules.dep.bin -rw-r--r-- 1 root root 110 Sep 9 05:19 modules.devname -rw-r--r-- 1 root root 12338 Aug 25 23:03 modules.order -rw-r--r-- 1 root root 55 Sep 9 05:19 modules.softdep -rw-r--r-- 1 root root 28361 Sep 9 05:19 modules.symbols -rw-r--r-- 1 root root 34978 Sep 9 05:19 modules.symbols.bin lrwxrwxrwx 1 root root 39 Sep 9 05:18 source -> /usr/src/linux-source-4.9.280-sun50iw9/ drwxr-xr-x 3 root root 4096 Sep 9 05:19 updates