Jump to content

Daniele

Members
  • Posts

    7
  • Joined

  • Last visited

  1. Yes, probably it's broken hardware. It's a strange behaviour however, the board does not freeze and run well but some network traffic is filtered... bah.... Now I have a problem using orange pi pc microphone... D.
  2. Wait a moment: with another orange pi and the same card it worked. I try to understand what the difference is...
  3. I don't know if it's a general armbian problem, probably it's only a my problem, what I can tell you for sure is that I tried two different boards and two different sd, so I am led to exclude an hardware issue. I need help because I don't know armbian and this problem is blocking, for this reason if you (or anyone who wants) want I can share ssh access. I don't really know how to move forward with this problem...
  4. Thanks for your reply Igor, if you want I can give you ssh access to my board, so you can check by yourself the problem... let me know, thanks D. But why only for this board? I have no problem updating raspberry pi with raspbian os, and so for other linux distros I'm using. This is first time I use armbian because I have four orange pi pc boards and from what I saw this is the best OS for them. Anyway I rebooted router with no luck, there is no additional firewall between orange pi and my router Thanks D.
  5. Obviously also armbianmonitor is not able to connect to external host root@orangepipc:~# armbianmonitor -u System diagnosis information will now be uploaded to curl: (7) Failed to connect to ix.io port 80: Connection refused Please post the URL in the forum where you've been asked for. This is response of armbianmonitor -U command There is something broken with network but I can confirm that I have no problem on my LAN and that orange pi pc board correctly receive ip address from DHCP and it's able to resolve and ping external hosts... Thanks Daniele.
  6. Hi, I have and Orange Pi PC board on which I'm trying to use Armbian from yestarday, "trying" because I have several different problems on which I investigated also on this forum, but I'm unable to solve at the moment (the reason because I'm writing here). Let's start from the beginning. I downloaded the armbian image from armbian website (https://www.armbian.com/orange-pi-pc/), version I'm using now is Armbian 20.08.1 Buster with Linux 5.8.5-sunxi, but I have tried also other versions with exact same behaviour. The first problem is time synchronization root@orangepipc:~# timedatectl Local time: Thu 2020-09-03 16:34:17 CEST Universal time: Thu 2020-09-03 14:34:17 UTC RTC time: Thu 1970-01-01 07:54:18 Time zone: Europe/Rome (CEST, +0200) System clock synchronized: no NTP service: inactive RTC in local TZ: no In this forum I found that a possible solution could be uninstall/install chrony, but if I'm able to remove this I'm not able to reinstall root@orangepipc:~# apt install chrony Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: chrony 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 216 kB of archives. After this operation, 397 kB of additional disk space will be used. Err:1 http://deb.debian.org/debian buster/main armhf chrony armhf 3.4-4 Could not connect to prod.debian.map.fastly.net:80 (151.101.112.204). - connect (111: Connection refused) Could not connect to deb.debian.org:80 (151.101.114.133). - connect (111: Connection refused) E: Failed to fetch http://deb.debian.org/debian/pool/main/c/chrony/chrony_3.4-4_armhf.deb Could not connect to prod.debian.map.fastly.net:80 (151.101.112.204). - connect (111: Connection refused) Could not connect to deb.debian.org:80 (151.101.114.133). - connect (111: Connection refused) E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? In general I'm not able to use apt at all... root@orangepipc:~# apt update Err:1 http://apt.armbian.com buster InRelease Could not connect to apt.armbian.com:80 (173.45.128.12). - connect (111: Connection refused) Err:2 http://security.debian.org buster/updates InRelease Could not connect to prod.debian.map.fastly.net:80 (151.101.112.204). - connect (111: Connection refused) Could not connect to security.debian.org:80 (151.101.192.204). - connect (111: Connection refused) Could not connect to security.debian.org:80 (151.101.0.204). - connect (111: Connection refused) Could not connect to security.debian.org:80 (151.101.64.204). - connect (111: Connection refused) Could not connect to security.debian.org:80 (151.101.128.204). - connect (111: Connection refused) Err:3 http://deb.debian.org/debian buster InRelease Could not connect to prod.debian.map.fastly.net:80 (151.101.112.204). - connect (111: Connection refused) Could not connect to deb.debian.org:80 (151.101.114.133). - connect (111: Connection refused) Err:4 http://deb.debian.org/debian buster-updates InRelease Unable to connect to deb.debian.org:http: Err:5 http://deb.debian.org/debian buster-backports InRelease Unable to connect to deb.debian.org:http: Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. W: Failed to fetch http://deb.debian.org/debian/dists/buster/InRelease Could not connect to prod.debian.map.fastly.net:80 (151.101.112.204). - connect (111: Connection refused) Could not connect to deb.debian.org:80 (151.101.114.133). - connect (111: Connection refused) W: Failed to fetch http://deb.debian.org/debian/dists/buster-updates/InRelease Unable to connect to deb.debian.org:http: W: Failed to fetch http://deb.debian.org/debian/dists/buster-backports/InRelease Unable to connect to deb.debian.org:http: W: Failed to fetch http://security.debian.org/dists/buster/updates/InRelease Could not connect to prod.debian.map.fastly.net:80 (151.101.112.204). - connect (111: Connection refused) Could not connect to security.debian.org:80 (151.101.192.204). - connect (111: Connection refused) Could not connect to security.debian.org:80 (151.101.0.204). - connect (111: Connection refused) Could not connect to security.debian.org:80 (151.101.64.204). - connect (111: Connection refused) Could not connect to security.debian.org:80 (151.101.128.204). - connect (111: Connection refused) W: Failed to fetch http://apt.armbian.com/dists/buster/InRelease Could not connect to apt.armbian.com:80 (173.45.128.12). - connect (111: Connection refused) W: Some index files failed to download. They have been ignored, or old ones used instead. root@orangepipc:~# DNS resolution and ping of the server to which apt is unable to connect are working fine root@orangepipc:~# ping deb.debian.org PING debian.map.fastly.net (151.101.114.133) 56(84) bytes of data. 64 bytes from 151.101.114.133 (151.101.114.133): icmp_seq=1 ttl=52 time=36.8 ms 64 bytes from 151.101.114.133 (151.101.114.133): icmp_seq=2 ttl=52 time=37.4 ms 64 bytes from 151.101.114.133 (151.101.114.133): icmp_seq=3 ttl=52 time=37.2 ms 64 bytes from 151.101.114.133 (151.101.114.133): icmp_seq=4 ttl=52 time=38.0 ms 64 bytes from 151.101.114.133 (151.101.114.133): icmp_seq=5 ttl=52 time=37.6 ms 64 bytes from 151.101.114.133 (151.101.114.133): icmp_seq=6 ttl=52 time=36.8 ms 64 bytes from 151.101.114.133 (151.101.114.133): icmp_seq=7 ttl=52 time=38.7 ms ^X64 bytes from 151.101.114.133 (151.101.114.133): icmp_seq=8 ttl=52 time=37.3 ms 64 bytes from 151.101.114.133 (151.101.114.133): icmp_seq=9 ttl=52 time=36.5 ms ^C --- debian.map.fastly.net ping statistics --- 9 packets transmitted, 9 received, 0% packet loss, time 20ms rtt min/avg/max/mdev = 36.540/37.377/38.687/0.623 ms If i put url http://deb.debian.org/debian/dists/buster/InRelease in web browser it's working, so the problem is not server unavailability. I don't have trouble with my LAN root@orangepipc:~# ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.20.0.195 netmask 255.255.255.0 broadcast 172.20.0.255 ether 02:81:ab:f8:f0:eb txqueuelen 1000 (Ethernet) RX packets 279682 bytes 22254870 (21.2 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2114 bytes 213315 (208.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 38 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 loop txqueuelen 1000 (Local Loopback) RX packets 1 bytes 29 (29.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1 bytes 29 (29.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 I have also problem using GPIO but it's a secondary trouble for the moment. I do not know what to do, I need help because in this way Armbian is useless on my board. Thanks in advance, Daniele.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines