• Content Count

  • Joined

  • Last visited

About lrrr

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Which patches are you using to enable sf command for SPI? The mainline Allwinner A10 SPI driver does not work with sun8i. The only driver I've found to work is this older fork. fork: info: It's been awhile since I've used an official armbian image. IIRC besides kernel related files, it's just overlays, bootscripts, and dtbs. Also, a couple of armbian related files that need to be kept if you want the armbian OS scripts to work (armbian-config, etc).
  2. GPL guarantees the source code, which allows *you* to modify Armbian. If you want Synaptic as default, fork and modify source. Source code is available by clicking the downloads > source links on the menu. Have fun.
  3. Is there an "official" way to install openwrt to spiflash? About the only thing I've found for installing to spiflash, is this:
  4. For brief info on the services: head -n3 /lib/systemd/system/armbian* I've found them not to be necessary but YMMV. Have a look at the commented scripts in '/usr/lib/armbian' to see which services you might want (or need).
  5. There is no official sdcard image but the attached script will create a image for the OrangePi Zero/R1. It uses daily generated files from Debian daily-images and considered testing/unstable. SDcard image creation: You will need basic Linux/Debian and dosfs utils. No su/root needed. Run the script to generate sdcard image for writing to sdcard. Optionally, if you want ssh network-console access, add preseed.cfg to same directory as script. See attached preseed.cfg and example-preseed.txt . Basic installation: Once the installer is started, it runs completel
  6. Does dpkg-divert not work for some reason? dpkg-divert --add /etc/default/cpufrequtils
  7. I usually use the cached rootfs in cache/rootfs. Extract, then mount pseudo-filesystems and copy over static qemu like you posted. Quick hacks are good if they get the job done. Another easy way to get chroot with and do things manually: #!/bin/sh echo "Entering chroot for $1 $2 $3" bash Before you exit chroot, copy your debs/files with another shell, network, etc.
  8. Add your code to userpatches/ Also of interest is userpatches/lib.config. Should be info in the documentation.
  9. Used ext2fsd for years when I used to dual boot with Windows. Never encountered any problems. Tried it the other day before posting. No problems accessing the sdcard and adding my custom configuration to armbian_first_run.txt.
  10. It would be nice if the SDK could easily build deb packages, similar to openwrt's SDK. I checked into but didn't mess with distcc setup. Larger projects will need distcc or much patience. This is sort of what I do to "cross-compile" deb packages. You still need to build an image but you don't have to use it. You can just copy your deb packages over to target os. To get make install results into deb package, you need to use some sort of debian package builder. Many options, guides, and tutorials are available online. The example below uses d
  11. @botfapIMO, users who cannot access ext4 fs need a GUI wizard but the tool should not be required for users who can access ext4 fs. It's feature creep, all because the average Armbian user cannot find a way to access the file system. There are ways to access ext4 from Windows (ext2fsd) and Mac (macfuse). Also, you have VM's and Linux Live USB/CD.
  12. @botfap A script generator would do most of the work, generate a config script, find offset in image and insert. Could be script based like yours or a statically linked binary, or dynamic linked with a GUI. One could do something similar with a static sized text file, such as armbian_first_run.txt, that is padded with whitespace instead of zeros. But armbian-firstrun-config doesn't do much. @tkaiser No filesystem required to mount, just rw access to the image file. I admit, it's hacky but doesn't require much changes to build. Just throwing some ideas out
  13. Here is a couple of more ways I was messing around with. 1) Create a static sized "binary" shell script on the image with a special header. Find the header and inject script. Simple working example. # Something like this would be added to official SDK. For testing add to userpatches/ # add 25k binary script ACI=/boot/ printf "#ARMBIAN_CUSTOMIZE_IMAGE_PLACEHOLDER" > $ACI OFFSET=$(du -b $ACI | awk {'print $1'}) dd if=/dev/zero of=$ACI bs=1 count=25k conv=notrunc seek=$OFFSET # modify armbian-firstrun-config and add txt file to exec $ACI
  14. I would do something similar to Armbian SDK and userpatches/ Add script to setup chroot (mounts,qemu-static,etc) using pre-built image. For example, if userpatches/ exists, copy to chroot and exec or drop to chroot for manual configuration. Then, cleanup. It would be more versatile as you could exec binaries on the image, like dpkg-reconfigure, etc. You could even use armbian-config but hardware detection would be based on host hardware, not the target.
  15. Here is a slightly cleaner approach. Download lib.config,, to userpatches. Most options are already set in lib.config. The resulting image is close to a basic chroot install with the minimal armbian packages needed for booting. Options: REMOVE_SYSTEMD in to use systemd or not. PACKAGE_LIST* in lib.config will determine which armbian based configs are added to the image. There are a few optimizations, that might be of interest, which are not included. Some are located in the SDK under packages/bsp/common/usr/lib/armbian/*