Jump to content

noob1

Members
  • Posts

    7
  • Joined

  • Last visited

Everything posted by noob1

  1. Thanks Werner for your support. I did make a copy renamed it and changed the name inside too. This image also works okay. one thing i did differently was to use tritium-h3 as base because i felt that it represented the hardware more accurately(please correct me if im wrong) I have a few queries: 1. How can i test that all hardware is working correctly, if not then what should i do to correct them. 2. the build currently takes more than an hour to complete. Is there any way to speed this up? 3. What more i should do so that board could be added to armbian build config. Im willing to put more work into it. Thanks again for so much help.
  2. Thanks a lot Werner. DId you mean that i should make a copy the .conf file, rename the file and also adjust the name inside the file too?
  3. I have an Orange Pi Mini 2. As far as i know there is no official/ unofficial armbian build for this. there are other boards like orange pi pc, orange pi 2 and tritium h3 board whose images run fine for this board. I have also made armbian image builds with orange pi pc as target and these images work on opi mini 2. I would like to know how could i make a build exclusively for orange pi mini 2.
  4. nevermind found tritim h3 board iamge that works fine
  5. i have orange pi mini 2 board that fails to go past uboot. i used buster and focal images from here. here is the uboot snippet: U-Boot SPL 2021.04-armbian (May 06 2021 - 18:16:10 +0000) DRAM: 1024 MiB Trying to boot from MMC1 U-Boot 2021.04-armbian (May 06 2021 - 18:16:10 +0000) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi 2 DRAM: 1 GiB MMC: mmc@1c0f000: 0, mmc@1c10000: 1 Loading Environment from FAT... Card did not respond to voltage select! : -110 In: serial@1c28000 Out: serial@1c28000 Err: serial@1c28000 Net: phy interface0 eth0: ethernet@1c30000 starting USB... Bus usb@1c1b000: nothing happens after this. i have tried with different sd cards with same results. so i have a few quesions: is the board damaged? or i have used the wrong image or is there some wrong configurations as the image and boards aren't exactly identical.
  6. Armbianmonitor: http://ix.io/2ksk i too have the same problem of unmet dependencies, i did apt install wireguard-tools modprobe wireguard i also tried to do apt install wireguard-tools=1.0.20200319 to resolve the dependency but this command fails with no such version found. apt install wireguard still fails citing wireguard-tools version required is >=1.0.20200319 but 0.0.2201912 is to be installed. please guide me in correct direction.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines