gounthar

Members
  • Content count

    19
  • Joined

  • Last visited

About gounthar

  • Rank
    Member

Recent Profile Visitors

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

  1. gounthar

    A64 and the 3.10 kernel

    Thanks @guidol, I will have a look at it.
  2. gounthar

    Quick review of NanoPi Fire3

    Thanks a lot @wtarreau, I feel more confident about buying this board now.
  3. gounthar

    A64 and the 3.10 kernel

    Any news about the A64 support? I was thinking of getting a NanoPi A64...
  4. gounthar

    Quick review of NanoPi Fire3

    The review is really interesting, and I was about to buy one of these boards. I asked a few questions at the TechSales, and got one interesting answer: I hope it will be enough if the power source comes from a Raspberry Pi power supply... If this doesn't work, what kind of power supply could I buy to plug in the "DuPont line" (I guess it means the GPIO)? Thanks.
  5. gounthar

    orange pi one connect hdmi vga adapter?

    I bought two, and the first one doesn't work at all for the OrangePi One Plus (but works for the Raspberry Pi). The second one works for the two of them...
  6. The first package downgrade went fine. Unfortunately, the second one does not exist in version 5.31. Which version should I use? sudo apt install linux-u-boot-orangepizero-next=5.31 Reading package lists... Done Building dependency tree Reading state information... Done E: Version '5.31' for 'linux-u-boot-orangepizero-next' was not found root@openstf-orangepi-zero:~# sudo apt install linux-u-boot-orangepizero-next Reading package lists... Done Building dependency tree Reading state information... Done linux-u-boot-orangepizero-next is already the newest version (5.38). 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. Thanks.
  7. Thanks to @raschid for giving me the link of this thread, as I may have the same kind of problem with my OrangePi Zero. Is there anything specific to armbian to monitor the memory usage, or a good old /proc/meminfo is the info to use? I know my Zero uses swap, which is a bad thing, but it looks like the discussion about using zram on Armbian for small memory SBC is not over... Here is the diagnosis.
  8. Hi, now that I have Docker up and running, I am facing new problems. After some time, the Zero stops working. I am connected with ssh, and the console is stuck. The port 22 seems to be still opened for nmap, but I can't open a new ssh session anymore. I was trying to monitor it with armbianmonitor -m, and I saw the processor throttling with the temperature rising. Up to 62°C, it stays at 1200MHz, then it goes down to 960MHz, and I saw it once at 480 around 72°C. As I thought that my problems were linked to the heat, I then used a fan and the temperatures stayed at max around 63°C and the CPU at 1200MHz. But the problem still happens. After 7 minutes or so, the Zero stops working: 07:29:57: 1200MHz 3.18 71% 15% 0% 0% 55% 0% 57.2°C 0/8 07:30:11: 1200MHz 6.35 65% 11% 8% 0% 45% 0% 63.0°C 0/8 07:30:17: 1200MHz 5.75 29% 8% 19% 0% 1% 0% 62.1°C 0/8 07:30:22: 1200MHz 5.37 28% 11% 15% 0% 1% 0% 62.4°C 0/8 07:30:27: 1200MHz 5.10 28% 8% 17% 0% 1% 0% 62.7°C 0/8 07:30:32: 1200MHz 4.77 22% 4% 17% 0% 0% 0% 62.6°C 0/8 07:30:38: 1200MHz 4.47 28% 6% 19% 0% 2% 0% 61.0°C 0/8 Time CPU load %cpu %sys %usr %nice %io %irq CPU C.St. 07:30:43: 1200MHz 4.19 21% 6% 14% 0% 0% 0% 63.5°C 0/8 07:30:48: 1200MHz 3.94 23% 9% 10% 0% 2% 0% 62.4°C 0/8 07:30:54: 1200MHz 3.70 8% 4% 1% 0% 1% 0% 60.6°C 0/8 07:30:59: 1200MHz 3.48 23% 5% 14% 0% 2% 0% 61.3°C 0/8 07:31:04: 1200MHz 3.29 29% 5% 21% 0% 1% 0% 62.7°C 0/8 07:31:09: 1200MHz 3.18 27% 7% 17% 0% 2% 0% 63.0°C 0/8 07:31:15: 1200MHz 3.17 36% 9% 12% 0% 13% 0% 61.2°C 0/8 07:31:21: 1200MHz 2.91 9% 6% 0% 0% 2% 0% 60.6°C 0/8 07:31:27: 1200MHz 2.68 32% 10% 4% 0% 16% 0% 61.7°C 0/8 07:31:32: 1200MHz 2.71 18% 9% 5% 0% 2% 0% 60.1°C 0/8 07:31:37: 1200MHz 2.49 8% 4% 2% 0% 0% 0% 60.6°C 0/8 07:31:48: 1200MHz 2.29 29% 12% 1% 0% 14% 0% 61.0°C 0/8 07:32:46: 1200MHz 4.86 78% 32% 0% 0% 45% 0% As you can see in the logs, the load is heavy, but the temperature is low. What could I check to know more about these crashes? Is there a message I could find in the logs after rebooting? Is there anything I could use to know more about that? Is there anything I could do to prevent that? Thanks.
  9. After several reboots, docker seem to work now (without any further modifications). Go figure... docker images REPOSITORY TAG IMAGE ID CREATED SIZE <none> <none> b12376e7113c About a minute ago 7.79MB armhf/alpine latest 15ed6d4bf10d 12 months ago 3.6MB
  10. Hi, I'm very happy to have my OrangePi Zero working (at last!) with Armbian. It looks like docker installed properly on the latest Armbian Stretch mainline kernel 4.14.y, but for some reason, it won't start. Here are the logs I have: systemctl enable docker Synchronizing state of docker.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable docker root@orangepizero:~# systemctl start docker Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details. root@orangepizero:~# systemctl status docker.service ● docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2018-06-03 12:43:49 UTC; 8s ago Docs: https://docs.docker.com Process: 20147 ExecStart=/usr/bin/dockerd -H fd:// (code=exited, status=1/FAILURE) Main PID: 20147 (code=exited, status=1/FAILURE) CPU: 990ms Jun 03 12:43:48 orangepizero systemd[1]: docker.service: Unit entered failed state. Jun 03 12:43:48 orangepizero systemd[1]: docker.service: Failed with result 'exit-code'. Jun 03 12:43:49 orangepizero systemd[1]: docker.service: Service hold-off time over, scheduling restart. Jun 03 12:43:49 orangepizero systemd[1]: Stopped Docker Application Container Engine. Jun 03 12:43:49 orangepizero systemd[1]: docker.service: Start request repeated too quickly. Jun 03 12:43:49 orangepizero systemd[1]: Failed to start Docker Application Container Engine. Jun 03 12:43:49 orangepizero systemd[1]: docker.service: Unit entered failed state. Jun 03 12:43:49 orangepizero systemd[1]: docker.service: Failed with result 'exit-code'. root@orangepizero:~# uname -a Linux orangepizero 4.14.14-sunxi #1 SMP Thu Jan 25 12:20:57 CET 2018 armv7l GNU/Linux Is there anything I can do to get it working? Here are the diagnosis: diagnosis. Thanks.
  11. Today, I finally managed to get it running. Don't ask why, I didn't change anything... But I am now logged (and have other issues).
  12. Very kind of yours to let me know. Thanks a lot! Edit: I received the cable today, and nothing happened when I plugged it in. Is there any other kernel version that can handle it?
  13. Hi, I bought a OrangePi Zero, burned the latest image on a good SD card, and started it. I bought a hat with a video output, but I don't have the right cables yet. So... I'm trying to set it up without any display for the time being. It looks like the port 22 is not opened, or any other ports, depending on the nmap command I use: $ nmap -sS -O -PI -PT 192.168.0.15 Starting Nmap 7.50 ( https://nmap.org ) at 2018-06-01 07:33 ope Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn Nmap done: 1 IP address (0 hosts up) scanned in 5.05 seconds $ ssh root@192.168.0.15 ssh: connect to host 192.168.0.15 port 22: Connection timed out At one time, I plugged it in my Windows machine, and it was seen as a serial gadget. I tried to contact it with Putty, but never managed to start a session. Does anynone have the reference of a cable/adapter I could plug in it so that I can log from my PC onto it? Thanks a lot.