counterpoint

  • Content Count

    8
  • Joined

  • Last visited

  1. @Werner why does Armbian use what look like Ubuntu versions for Debian based releases? That's quite confusing. Is Armbian Buster really based on Debian or Ubuntu? @Igor I'm not entirely clear what you mean, but I do have the HC1s booting from the SD card but then loading the system from the SSD. Is that what you refer to? There are many conflicting instructions on how to do this. It would be useful to have an authoritative set of instructions. Does such a thing exist? My system gives for armbianmonitor -u: http://ix.io/2zbd
  2. Thanks. It was certainly unexpected. But where does that leave me? What I'm using is Armbian Buster, which I understood to be based on Debian 10. Not Armbian Focal, which I believed was based on Ubuntu 20.04 LTS. For Debian, 10 or Buster mean the same thing. Or am I mistaken?
  3. I have two HC1s both running Armbian 10. Both of them respond to uname -r with: 4.14.187-odroidxu4 Yesterday, I rebooted one of them, and immediately started seeing errors. These turned out to be attributable to missing modules. The only directory in /lib/modules was 4.14.198-odroidxu4 which does not match the kernel version. The other HC1 still had a directory /lib/modules/4.14.187-odroidxu4. Prior to the reboot both systems were working. How can this happen? My quick solution was to copy the 4.14.187-odroidxu4 directory from the working HC1 to the failed HC1, wh
  4. Thanks for the various suggestions. I now have the solution to the problem. Perhaps my original question misled. I was creating a server that was new in the sense of being freshly created from scratch. The hardware was an HC1 that had been in use for a while for a slightly different purpose. The SSD was new, as was the SD card and the Buster image. I have also created a Debian 10 server for another purpose on a brand new HC1. It surprised me to find that I could install the Buster image prominently displayed on https://www.armbian.com/odroid-hc1/ and have ipset and ipta
  5. Thanks, Werner. My original problem was more severe than just a missing iptables module. So far as I could tell, iptables was completely unusable. And so was ipset. Since those are essential to the way I set up servers, I just couldn't use that version unless those problems could be solved. Unfortunately, I've not seen anything that solves either problem. This is my second Odroid HC1 and the first one was built with the recommended Debian 9 image. That didn't have any of these problems and has been in use for some while. But Debian 9 is getting old now, and didn't seem a sensible c
  6. Thanks, yes. It appears you are using a 5.4.51 kernel. I don't have a problem with that image. The thing that has left me puzzled is why the most prominently featured Buster image has a 4.14.187 kernel. (Page at https://www.armbian.com/odroid-hc1/)
  7. Thanks very much. Sorry for the slow response - I'm only allowed one post per 24 hours. I seem to have a solution. As mentioned above, I took the image from https://www.armbian.com/odroid-hc1/ To be more specific, I used the one with the large image at the right hand side of the page, just below the picture of an HC1. Looking more carefully, it uses kernel 4.14.y. Not being knowledgeable about kernel versions, I assumed that the highlighted image was the best to use. However, I later looked down the page, and tried using the download link https://dl.armbian.com/odroidxu4/Buster_cur
  8. I am setting up a new Odroid HC1 and have installed Armbian Buster from https://www.armbian.com/odroid-hc1/. Attempting to run iptables, I first had the problem: iptables/1.8.2 Failed to initialize nft: Protocol not supported Attempting to use legacy, I used the command: update-alternatives --set iptables /usr/sbin/iptables-legacy But then had the error: modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/4.14.180-odroidxu4/modules.dep.bin' modprobe: FATAL: Module ip_tables not found in directory /lib/modules/4.1