Jump to content

FRANK333

Members
  • Posts

    64
  • Joined

  • Last visited

Posts posted by FRANK333

  1.  

    on orange pizero ,i installed pm-utils and with the pm-suspend command i put it in suspend .

    If I try to wake it up , with etherwake or other WOL programs (which send magic packets in LAN to the pizero's macadress) the pizero will not wake up .

    Do you know any tricks?

  2. ok thanks, 

    i solved it , no need to change kernel ,

    i added in /boot/armbianEnv.txt overlay_prefix=sun50i-h5 which is specific for orange pi zero plus , overlays appeared in armbian-config i selected them ,

    i inserted the pa gpio corresponding to the pin connected to the 1wire sensor and everything works.

     

  3. To control from terminal a remote orangepizeroplus in case of lockup, I connected the otg to the USB port of a second Opi0+ modifying a usb cable to which I disconnected the power cables (+red and -black).
    I gave these commands on the orange to monitor:

    # 	
    echo "g_serial" >> /etc/modules
    mkdir -p /etc/systemd/system/serial-getty@ttyGS0.service.d
    
    nano /etc/systemd/system/serial-getty@ttyGS0.service.d/10-switch-role.conf
    #add 2 lines save and exit
    [Service]
    ExecStartPre=-/bin/sh -c "echo 2 > /sys/bus/platform/devices/sunxi_usb_udc/otg_role"
    	
    systemctl --no-reload enable serial-getty@ttyGS0.service
    echo "ttyGS0" >> /etc/securetty
    reboot

    on the second orange connected to the network, I made a simple script of serial activation:

    simple script chmod +x,it disconnects with ctrl+a and then d
    
    #!/bin/bash
    dmesg | grep tty
    sudo chmod 666 /dev/ttyACM0
    echo "defscrollback 5000" > .screenrc  is 5,000 lines enough?
    screen /dev/ttyACM0 115200

    Everything works but in dmesg I have this warning:

    cdc_acm 3-1:2.0: ttyACM0: USB ACM device
    musb-hdrc musb-hdrc.2.auto: request 0000000019a4bba3 not queued to ep1in.

     

    Sometimes after exiting the console I can't login again and I have to restart the service.

    Someone, can explain me the problem or how to solve it?

     

     

  4. hello igor, if i understand well then, wireguard client is already integrated, how do i pass the authentication data to connect to the server on the vps. using the wireguard-manager script i also have this anomaly

    Spoiler

    Job for unbound.service failed because the control process exited with error code.
    See "systemctl status unbound.service" and "journalctl -xe" for details.
    Job for unbound.service failed because the control process exited with error code.
    See "systemctl status unbound.service" and "journalctl -xe" for details.
    invoke-rc.d: initscript unbound, action "start" failed.
    ● unbound.service - Unbound DNS server
         Loaded: loaded (/lib/systemd/system/unbound.service; enabled; vendor preset: enabled)
         Active: activating (auto-restart) (Result: exit-code) since Sun 2021-11-21 13:34:03 CET; 38ms ago
           Docs: man:unbound(8)
        Process: 4747 ExecStartPre=/usr/lib/unbound/package-helper chroot_setup (code=exited, status=0/SUCCESS)
        Process: 4770 ExecStartPre=/usr/lib/unbound/package-helper root_trust_anchor_update (code=exited, status=0/SUCCESS)
        Process: 4777 ExecStart=/usr/sbin/unbound -d $DAEMON_OPTS (code=exited, status=1/FAILURE)
       Main PID: 4777 (code=exited, status=1/FAILURE)
    Processing triggers for systemd (245.4-4ubuntu3.13) ...
    Processing triggers for man-db (2.9.1-1) ...
    Processing triggers for libc-bin (2.31-0ubuntu9.2) ...
    659
    Removed /etc/systemd/system/multi-user.target.wants/systemd-resolved.service.
    Removed /etc/systemd/system/dbus-org.freedesktop.resolve1.service.

     

  5. Armbianmonitor:

    I wanted to install wireguard, I launched wireguard-monitor but the script did not work and gave me these errors,

    .....
    Building dependency tree       
    Reading state information... Done
    E: Unable to locate package linux-headers-5.10.60-sunxi64
    E: Couldn't find any package by glob 'linux-headers-5.10.60-sunxi64'
    E: Couldn't find any package by regex 'linux-headers-5.10.60-sunxi64'
    Reading package lists... Done
    .....

    should I upgrade to a new kernel, or is there any other way?

     

  6. good evening,

    on orange pzero+ with debian10 i tried to install docker with the procedure of the armbian manual, but the installation fails.

    do you know how to solve?

    apt-get remove docker docker-engine docker.io containerd runc
    apt-get install apt-transport-https ca-certificates curl gnupg-agent software-properties-common
    curl -fsSL https://download.docker.com/linux/debian/gpg | apt-key add -
    add-apt-repository "deb [arch=arm64] https://download.docker.com/linux/debian $(lsb_release -cs) stable"
    apt update
    apt-get install docker-ce docker-ce-cli containerd.io
    result:
    ● docker.service - Docker Application Container Engine
       Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
      Drop-In: /etc/systemd/system/docker.service.d
               └─override.conf
       Active: activating (auto-restart) (Result: exit-code) since Sun 2021-11-07 19:36:34 CET; 54ms ago
         Docs: https://docs.docker.com
      Process: 10722 ExecStart=/usr/bin/dockerd -H fd:// -H tcp://0.0.0.0:2736 (code=exited, status=1/FAILURE)
     Main PID: 10722 (code=exited, status=1/FAILURE)
    dpkg: error processing package docker-ce (--configure):
     installed docker-ce package post-installation script subprocess returned error exit status 1
    Processing triggers for man-db (2.8.5-2) ...
    Processing triggers for systemd (241-7~deb10u8) ...
    Errors were encountered while processing:
     docker-ce
    E: Sub-process /usr/bin/dpkg returned an error code (1)
    root@server:~# service docker status
    ● docker.service - Docker Application Container Engine
       Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
      Drop-In: /etc/systemd/system/docker.service.d
               └─override.conf
       Active: failed (Result: exit-code) since Sun 2021-11-07 19:38:39 CET; 9min ago
         Docs: https://docs.docker.com
      Process: 11195 ExecStart=/usr/bin/dockerd -H fd:// -H tcp://0.0.0.0:2736 (code=exited, status=1/FAILURE)
     Main PID: 11195 (code=exited, status=1/FAILURE)
    
    Nov 07 19:38:39 server systemd[1]: docker.service: Service RestartSec=2s expired, scheduling restart.
    Nov 07 19:38:39 server systemd[1]: docker.service: Scheduled restart job, restart counter is at 7.
    Nov 07 19:38:39 server systemd[1]: Stopped Docker Application Container Engine.
    Nov 07 19:38:39 server systemd[1]: docker.service: Start request repeated too quickly.
    Nov 07 19:38:39 server systemd[1]: docker.service: Failed with result 'exit-code'.
    Nov 07 19:38:39 server systemd[1]: Failed to start Docker Application Container Engine.

     

  7. @Stuart Naylor I like this board because it has an M2 port that accepts the quectel em160 modem, with armbian and the appropriate management software you can build a cheap and very fast modem with about 1Gb of bandwidth. Too bad it doesn't have a second ethernet port. I will definitely buy it if it has armbian compatibility it costs 35USD.

     

  8. On 9/25/2019 at 11:26 AM, jhoney said:

    If you boot from SPI (speaking from head, not sure) we search for boot.cmd on various devices, starting from ... I don't know. I was not doing much with booting from SPI and I am not aware of the defaults, but I am sure its possible to boot directly SPI -> SATA/USB.

     

    [edit out spam links]

    jhoney, uboot finds the .cmd file on the hdd, but this file is not written correctly (it seems to be an exact copy of the one on the sd) and then repeats for about ten times the operation and then freezes.
    If I could write the .cmd file correctly as it happens for the orangePizero+ it would work.

  9. continues my battle with U-boats, and I appeal to anyone who knows anything.
    Reading on the forum I found this command to control U-boot strings /dev/mtd0 | grep U-Boot and the result I wrote it in the spoiler below.
    I did not understand exactly what it means surely is an error during the installation of U-boot that I did with these commands : flash_erase /dev/mtd0 0 128
    flashcp /usr/lib/linux-u-boot-next-orangepizero_5.90_armhf/u-boot-sunxi-with-spl.bin /dev/mtd0
    Last experiment I compared the script nand-sata install on OP0 and OP0+ but I did not notice differences so the lack of recognition of the spi is to be found upstream.

    Spoiler

    1625704885_Schermatadel2019-09-1320_33_27.thumb.png.54c2faccefc65a0e29f8d5bdbf068caf.png

     

  10. Spoiler

    usb_boot=usb start; if usb dev ${devnum}; then devtype=usb; run scan_dev_for_boot_part; fi

     

    scan_dev_for_boot_part=part list ${devtype} ${devnum} -bootable devplist; env exists devplist || setenv devplist 1; for distro_bootpart in ${devplist}; do if fstype ${devtype} ${devnum}:${distro_bootpart} bootfstype; then run scan_dev_for_boot; fi; done; setenv devplist

     

    scan_dev_for_boot=echo Scanning ${devtype} ${devnum}:${distro_bootpart}...; for prefix in ${boot_prefixes}; do run scan_dev_for_extlinux; run

     

    scan_dev_for_scripts; done;run scan_dev_for_efi;

     

     

     

    => run scan_dev_for_extlinux
    Found extlinux/extlinux.conf
    Invalid filesystem: 0x43100000
    SCRIPT FAILED: continuing...
    => run scan_dev_for_scripts
    Found U-Boot script boot.scr.uimg
    ## Executing script at 43100000
    Wrong image format for "source" command
    SCRIPT FAILED: continuing...
    Found U-Boot script boot.scr
    ## Executing script at 43100000
    Wrong image format for "source" command
    SCRIPT FAILED: continuing...
    =>

    I've tried these

  11. here I copied the directory /boot and changed UUID (there was already written the UUID of the hdd)

    Spoiler

    => usb start

     


    => ls usb 0 /boot
    <DIR>       4096 .
    <DIR>       4096 ..
    <SYM>         17 dtb
    <DIR>      12288 dtb-4.19.62-sunxi
    <DIR>       4096 overlay-user
                 230 armbianEnv.txt
                   0 armbianEnv.txt.out
                1536 armbian_first_run.txt.template
              230454 boot.bmp
                3726 boot.cmd
                3798 boot.scr
                4882 boot-desktop.png
              162659 config-4.19.62-sunxi   
    <SYM>         17 dtb.old
             8128198 initrd.img-4.19.62-sunxi
             3299149 System.map-4.19.62-sunxi
    <SYM>         21 uInitrd
             8128262 uInitrd-4.19.62-sunxi  
             7497384 vmlinuz-4.19.62-sunxi  
    <SYM>         21 zImage
                   0 .next

     


    => run usb_boot

    IDE device 0: Vendor: Maxtor 6 Rev: 0811 Prod: Y080L0
                Type: Hard Disk
                Capacity: 78167.2 MB = 76.3 GB (160086528 x 512)
    ** Bad device specification usb -bootable **
    Scanning usb :1...
    Found U-Boot script /boot/boot.scr
    data abort
    pc : [<5ffa9612>]          lr : [<5ffa905d>]
    reloc pc : [<4a02b612>]    lr : [<4a02b05d>]
    sp : 5bf57500  ip : 00000003     fp : 00000005
    r10: 5bfbc930  r9 : 5bf5dee0     r8 : 00000001
    r7 : 5bf60e48  r6 : 5af56040     r5 : 5bf57528  r4 : 00000022
    r3 : 0000005c  r2 : 5af560a3     r1 : 5bf60eb4  r0 : 5af5609f
    Flags: nzCv  IRQs off  FIQs off  Mode SVC_32
    Code: 4630fd7f 81f0e8bd e7d84606 bf082b2f (f822235c)
    Resetting CPU ...

    resetting ...

     

  12. Hello Martinayotte ,
    Departed from a clean installation,
    I cleaned up both hdd and µSD and installed armbian on hdd with the appropriate option in armbian-config.
    Of course if I restart the OP0 with the µSD inserted everything works fine.

     

    I gave the commands you wrote above these are the results (without µSD insertd).

    Spoiler

    => usb start

    => ls usb 0 /
    <DIR>       4096 .
    <DIR>       4096 ..
    <DIR>       4096 bin
    <DIR>       4096 boot
    <DIR>       4096 dev
    <DIR>       4096 etc
    <DIR>       4096 home
    <DIR>       4096 lib
    <DIR>       4096 lost+found
    <DIR>       4096 media
    <DIR>       4096 mnt
    <DIR>       4096 opt
    <DIR>       4096 proc
    <DIR>       4096 root
    <DIR>       4096 run
    <DIR>       4096 sbin
    <DIR>       4096 selinux
    <DIR>       4096 srv
    <DIR>       4096 sys
    <DIR>       4096 tmp
    <DIR>       4096 usr
    <DIR>       4096 var
    =>


    => ls usb 0 /boot
    <DIR>       4096 .
    <DIR>       4096 ..

     

     

    => run usb_boot

    IDE device 0: Vendor: Maxtor 6 Rev: 0811 Prod: Y080L0
                Type: Hard Disk
                Capacity: 78167.2 MB = 76.3 GB (160086528 x 512)
    ** Bad device specification usb -bootable **
    Scanning usb :1...

     

     

     

     

  13. Hi, umiddelb,
    I tried to clean up the nor spi and recharge an old U-boat but I didn't notice any difference.
    I noticed a strange thing U-boot when it starts and finds the USB disk looks for a file boot.env not finding it continues finding boot.cmd processes it with error and restarts (this probably because boot.cmd is the one written on the sd card. Even if I recompiled and modified it) . The matter becomes more and more complicated ...

     

     

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines