Ugo Riboni

Members
  • Content Count

    8
  • Joined

  • Last visited

  1. In the latest image for NanoPi M1 Plus, I enable the analog audio I/O on the card by adding overlays=analog-codec in /boot/armbianEnv.txt But the microphone on the card is disabled by default, because the ALSA control "Mic1 Playback Switch" is set to false by default on the card. Worse still, this mixer control does not appear in the alsamixer GUI, and the only way to set to true is to use the amixer command line utility, for example with: amixer cset name="Mixer Capture Switch" on on I can do this inside a first boot script, and then ALSA will persist the state between reboots. But does not seem ideal, and took me a very long time to figure out why the microphone was disabled in the first place. Is there a way to have this control appear in the GUI, and for it to be enabled by default when the overlay is loaded ?
  2. Fair enough. My main concern was the extra disk space, bandwidth and time needed for the first build, but you are right, it's survivable and not a critical problem. One question I have if I go down this road is: how do I replicate exactly the configuration of one of the pre-built images ? Is the .conf file used to generate one of the downloadable images available anywhere ?
  3. Thanks Igor. Correct me if I'm wrong, but doesn't this option require that I build everything at least once, and only affects what happens on the following runs ?
  4. Hello everyone, I have been using a pre-built Armbian image on a Nanopi M1 Plus and I have been very happy with it. However I have several modifications specific to my usage of the board (setup some files in /etc/, create default users, install or remove some packages, etc.) that I would like to add to the image in a repeatable way. By repeatable I mean that I could add the set of scripts/patches/packages etc. to source control so that other people could them rebuild the same exact image. All of the advice I have found searching the forum points to this process https://docs.armbian.com/Developer-Guide_User-Configurations/ But it does require rebuilding the whole image, including the kernel, which is very cumbersome and totally unnecessary for my use case, as 95% of what is in the stock image is good for me and I don't actually need to compile anything. So what I am doing right now is to loop mount the image, copy or edit the files that I need changed, then use qemu to chroot into the image and install the packages I need. But it does not feel clean and I wonder if there is a better way using Armbian scripts/tools to accomplish something similar. Any suggestions ?
  5. Just for the record, I just had this issue happening to me on a nanopi M1 plus board, with kernel 4.5.6 The /boot/armbianEnv.txt had entries from syslog pasted into it and missing most of the default content that enabled the right device tree overlays. Is there any way to prevent this from happening rather than detecting the issue and restoring the file ?
  6. Thanks Igor ! I tried the ubuntu image and the few things I tested so far (i2c, audio input) work quite well. I'll keep testing and report in other threads if I find any issues.
  7. Ah, thanks a lot for the information ! Probably the links from the board page should be removed or fixed, then.
  8. Hello everyone, Apologies if this is not the right forum for this questions, but could not find any more appropriate one after some searching. I get an HTTP 404 when I try to access the pre-built images for the nanopi m1 plus from the board page. I know the board is EOS but for other EOS boards I can still download the images. Is there any reason why this board seems to have disappeared completely ?