axeleroy
-
Posts
26 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by axeleroy
-
-
Oh, I thought you were the bidder. Unfortunately that would be unfair to them if I chose to send it to you and delete the listing 😕
-
I set up international shipping when I created the listing but it is no longer there.
And... lo and behold, there are arbitrary requirements for selling internationally on eBay…
QuoteBefore you can sell internationally, you'll need to:
- Have an eBay account in good standing
- Have earned at least 10 feedback points as a seller
- Have made your first successful sale more than 90 days ago
I'm not sure how that would work if you chose to be delivered with Colissimo, gave your address in the Netherlands (if eBay even allows you to) and I sent it as Colissimo International 🤔
-
I would rather sell through eBay
-
I don't remember which revision got the fix and what revision my board is. But I was able to use the 2.5gig without issue
-
Shipping cost will depend on whether you live in Europe or not. Western Europe is €25, Eastern Europe is €34 and rest of the world is €66.
https://www.laposte.fr/tarif-colissimo (look for the 5kg pricing)
-
Hello there,
I'm selling my Helios64 if anyone is interested: https://www.ebay.com/itm/275966274774I would very much like it if it did not end up as e-waste 😬
-
Hello,
My NAS becomes unresponsive every time I run a somewhat CPU-intensive task: indexing photos in photoprism, importing followings in Mastodon… or just browsing Mastodon.
Is it expected of the Rockchip RK3399 or can I improve the situation with the right CPUfreq config ?
For context, here is my CPUfreq config and kernel (I have yet to update):
axel@helios64:~$ cat /etc/default/cpufrequtils ENABLE="true" GOVERNOR=performance MAX_SPEED=1200000 MIN_SPEED=1200000 axel@helios64:~$ uname -a Linux helios64 5.10.21-rockchip64 #21.02.3 SMP PREEMPT Mon Mar 8 01:05:08 UTC 2021 aarch64 GNU/Linux
Thanks!
-
Hello,
I have been holding onto kernel 5.10 (5.10.21-rockchip64 to be exact) for a while as it has been pretty stable for me and also because I heard bad feedback from newer kernels on the Helios 64.
But with the recent discovery of the DirtyPipe exploit (which has been introduced in Linux 5.8), I might be looking to upgrade to the latest Armbian kernel (which contains a fix to the vulnerability).
So, my question to fellow Helios64 users is: have you encountered any issue with kernel 5.15, especially when using OpenMediaVault 5, Docker, MergerFS and NFS?
-
On 5/8/2021 at 9:54 PM, FloBaoti said:
For people running fine, are you using 2.5G NIC ?
I do, and this interface crashes every few days. I setup a cron to check every minute and down&up it if necessary.
I'm using the 2.5Gbps NIC exclusively with a 2.5Gbps switch for a month with no issues so far.
-
My Helios is stable, running LUKS, MergerFS, SnapRAID, OMV and 9 Docker containers from SD Card and with 3 HDDs.
Although in order to get a stable system I had to lock CPU frequency at 1.2GHz, otherwise CPU intensive tasks (like SnapRAID's scrub) would cause my Helios to reboot.
================================================================================ = System information ================================================================================ Linux helios64 5.10.21-rockchip64 #21.02.3 SMP PREEMPT Mon Mar 8 01:05:08 UTC 2021 aarch64 GNU/Linux ================================================================================ = Uptime ================================================================================ 12:25:17 up 8 days, 1:18, 0 users, load average: 0.01, 0.10, 0.15 ================================================================================ = openmediavault information ================================================================================ Release: 5.6.2-1 Codename: Usul ================================================================================ = openmediavault plugins ================================================================================ ii openmediavault-backup 5.2.4 all backup plugin for OpenMediaVault. ii openmediavault-flashmemory 5.0.8 all folder2ram plugin for OpenMediaVault ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive ii openmediavault-luksencryption 5.0.2 all OpenMediaVault LUKS encryption plugin ii openmediavault-minidlna 5.0.5 all OpenMediaVault miniDLNA (DLNA server) plugin ii openmediavault-omvextrasorg 5.6 all OMV-Extras.org Package Repositories for OpenMediaVault ii openmediavault-snapraid 5.0.7 all snapraid plugin for OpenMediaVault. ii openmediavault-unionfilesystems 5.1.2 all Union filesystems plugin for OpenMediaVault. ii openmediavault-wol 3.4.2 all OpenMediaVault WOL plugin
PS: don't mind the uptime, I had to reboot to apply an update. Otherwise no problem since mid-February.
-
Hi, quick update: no reboots in the two weeks following the frequency tweak. Reboot still happened shortly after my February 11 post (but before I applied gprovost's advice).
-
-
It happened again.
Should I try updating to the Armbian version that jiust came out?
When should I run armbianmonitor (whenever I can or just after a reboot?) and what should I be looking for (because nothing seems odd to me, but I'm not that of an advanced user)Thanks !
-
Oh, I didn't know about this utility. Here are the logs: http://ix.io/2Ok2
-
Hi,
I'm very pleased with my Helios 64, but since I updated to Armbian 20.11.6 (from 20.08.11 or 21, not really sure) it reboots at random times: it can run fine for over two weeks and reboot twice in 36 hours, always when idling.
It's running OMV as well a multiple Docker containers: PiHole, Wireguard, Nginx, Transmission, restic-server and n8n.
Is it a common issue? What fixes do you recommend? What should I look for to diagnose the issue?
Thank you.
Edit: forgot to mention that I'm using SnapRAID and mergerFS, as well as NFS shares.
-
Great, thank you!
-
That what I thought as I read on the forums that the logs were in ramdisk, but I am confused since syslog had entries from before the reboot, as if there was an exception for this file (though I guess I'm probably wrong).
How can I make the logs persistent, at least temporarily? I also had reboots when trying to backup OMV using openmediavault-backup and dd, I would like to diagnose those too (though I stop using dd in favor of borgbackup). -
Hello there,
My board had just rebooted with no notice, so I wanted to take a look at /var/log/syslog in order to diagnose the issue, but for some reason, there are no logs between Dec 30 and the moment my board rebooted.
Why are logs missing? What do I need to do in order to keep them the next time my board reboots? Also, am I looking at the right place to diagnose reboots?
Thanks for you help!PS1: My board is the Helios64 and I'm running Armbian 20.11.4 Buster with OMV 5.
PS2: I know there is an Helios64 Club, though I did not choose to post there as I'm not sure if this issue is specific to that board. -
Since OMV alters so much of Debian/Armbian, I would recommend deploying the Docker container. Docker also has the benefit of using any port you want.
If you want an easy to use GUI, you can install Portainer using OMV-Extras (in the left menu, then under the Docker tab of OMV-Extras).
-
Welp, I removed the SD card and it did not boot to eMMC.
Spoilerpicocom v2.2
port is : /dev/ttyUSB0
flowcontrol : none
baudrate is : 1500000
parity is : none
databits are : 8
stopbits are : 1
escape is : C-a
local echo is : no
noinit is : no
noreset is : no
nolock is : no
send_cmd is : sz -vv
receive_cmd is : rz -vv -E
imap is :
omap is :
emap is : crcrlf,delbs,Type [C-a] [C-h] to see available commands
Terminal ready
[ 5681.802401] reboot: Power down
[ 5�DDR Version 1.24 20191016
In
channel 0
CS = 0
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
change freq to 416MHz 0,1
Channel 0: LPDDR4,416MHz
Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB
Channel 1: LPDDR4,416MHz
Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB
256B stride
channel 0
CS = 0
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
channel 0, cs 0, advanced training done
channel 1, cs 0, advanced training done
change freq to 856MHz 1,0
ch 0 ddrconfig = 0x101, ddrsize = 0x40
ch 1 ddrconfig = 0x101, ddrsize = 0x40
pmugrf_os_reg[2] = 0x32C1F2C1, stride = 0xD
ddr_set_rate to 328MHZ
ddr_set_rate to 666MHZ
ddr_set_rate to 928MHZ
channel 0, cs 0, advanced training done
channel 1, cs 0, advanced training done
ddr_set_rate to 416MHZ, ctl_index 0
ddr_set_rate to 856MHZ, ctl_index 1
support 416 856 328 666 928 MHz, current 856MHz
OUT
Boot1: 2019-03-14, version: 1.19
CPUId = 0x0
ChipType = 0x10, 254
SdmmcInit=2 0
BootCapSize=100000
UserCapSize=14910MB
FwPartOffset=2000 , 100000
mmc0:cmd8,20
mmc0:cmd5,20
mmc0:cmd55,20
mmc0:cmd1,20
mmc0:cmd8,20
mmc0:cmd5,20
mmc0:cmd55,20
mmc0:cmd1,20
mmc0:cmd8,20
mmc0:cmd5,20
mmc0:cmd55,20
mmc0:cmd1,20
SdmmcInit=0 1
StorageInit ok = 67773
SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit read PBA: 0x1404
SecureInit read PBA: 0x1804
SecureInit read PBA: 0x1c04
SecureInit ret = 0, SecureMode = 0
atags_set_bootdev: ret:(0)
GPT 0x3380ec0 signature is wrong
recovery gpt...
GPT 0x3380ec0 signature is wrong
recovery gpt fail!
LoadTrust Addr:0x4000
No find bl30.bin
No find bl32.bin
Load uboot, ReadLba = 2000
Load OK, addr=0x200000, size=0xdcfd8
RunBL31 0x40000
NOTICE: BL31: v1.3(debug):42583b6
NOTICE: BL31: Built : 07:55:13, Oct 15 2019
NOTICE: BL31: Rockchip release version: v1.1
INFO: GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3
INFO: Using opteed sec cpu_context!
INFO: boot cpu mask: 0
INFO: plat_rockchip_pmu_init(1190): pd status 3e
INFO: BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK
ERROR: Error initializing runtime service opteed_fast
INFO: BL31: Preparing for EL3 exit to normal world
INFO: Entry point address = 0x200000
INFO: SPSR = 0x3c9
U-Boot 2020.07-armbian (Oct 13 2020 - 16:49:59 +0200)SoC: Rockchip rk3399
Reset cause: POR
DRAM: 3.9 GiB
PMIC: RK808
SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
MMC: mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environmentIn: serial
Out: serial
Err: serial
Model: Helios64
Revision: 1.2 - 4GB non ECC
Net: eth0: ethernet@fe300000
scanning bus for devices...
Hit any key to stop autoboot: 0
Card did not respond to voltage select!
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
## Executing script at 00500000
Wrong image format for "source" command
SCRIPT FAILED: continuing...
starting USB...
Bus usb@fe380000: USB EHCI 1.00
Bus dwc3: usb maximum-speed not found
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb@fe380000 for devices... 1 USB Device(s) found
scanning bus dwc3 for devices... 4 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) foundDevice 0: unknown device
scanning bus for devices...Device 0: unknown device
Speed: 1000, full duplex
BOOTP broadcast 1
DHCP client bound to address 192.168.0.110 (2 ms)
*** ERROR: `serverip' not set
Cannot autoload with TFTPGET
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/01-64-62-66-d0-03-7c
Speed: 1000, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0A8006E
Speed: 1000, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0A8006
Speed: 1000, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0A800
Speed: 1000, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0A80
Speed: 1000, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0A8
Speed: 1000, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0A
Speed: 1000, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0
Speed: 1000, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C
Speed: 1000, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-rk3399-helios64
Speed: 1000, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-rk3399
Speed: 1000, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm
Speed: 1000, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default
Speed: 1000, full duplex
*** ERROR: `serverip' not set
Config file not found
Speed: 1000, full duplex
BOOTP broadcast 1
DHCP client bound to address 192.168.0.110 (3 ms)
*** ERROR: `serverip' not set
Cannot autoload with TFTPGET
Speed: 1000, full duplex
BOOTP broadcast 1
DHCP client bound to address 192.168.0.110 (1 ms)
*** ERROR: `serverip' not set
Cannot autoload with TFTPGET
=> DDR Version 1.24 20191016 -
Hello,
I just tried to copy my Armbian install from the SD Card to the eMMC, but I'm not sure it has been successful, how can I be sure?
For information, I also encrypted my HDDs using LUKS and I use MergerFS to pool their data.
Boot sequence from serial console
SpoilerDDR Version 1.24 20191016
In
soft reset
SRX
channel 0
CS = 0
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x18
MR4=0x2
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
change freq to 416MHz 0,1
Channel 0: LPDDR4,416MHz
Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB
Channel 1: LPDDR4,416MHz
Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB
256B stride
channel 0
CS = 0
MR0=0x18
MR4=0x82
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x18
MR4=0x2
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
channel 0, cs 0, advanced training done
channel 1, cs 0, advanced training done
change freq to 856MHz 1,0
ch 0 ddrconfig = 0x101, ddrsize = 0x40
ch 1 ddrconfig = 0x101, ddrsize = 0x40
pmugrf_os_reg[2] = 0x32C1F2C1, stride = 0xD
ddr_set_rate to 328MHZ
ddr_set_rate to 666MHZ
ddr_set_rate to 928MHZ
channel 0, cs 0, advanced training done
channel 1, cs 0, advanced training done
ddr_set_rate to 416MHZ, ctl_index 0
ddr_set_rate to 856MHZ, ctl_index 1
support 416 856 328 666 928 MHz, current 856MHz
OUT
Boot1: 2019-03-14, version: 1.19
CPUId = 0x0
ChipType = 0x10, 323
SdmmcInit=2 0
BootCapSize=100000
UserCapSize=14910MB
FwPartOffset=2000 , 100000
mmc0:cmd5,20
SdmmcInit=0 0
BootCapSize=0
UserCapSize=61056MB
FwPartOffset=2000 , 0
StorageInit ok = 66065
SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit read PBA: 0x1404
SecureInit read PBA: 0x1804
SecureInit read PBA: 0x1c04
SecureInit ret = 0, SecureMode = 0
atags_set_bootdev: ret:(0)
GPT 0x3380ec0 signature is wrong
recovery gpt...
GPT 0x3380ec0 signature is wrong
recovery gpt fail!
LoadTrust Addr:0x4000
No find bl30.bin
No find bl32.bin
Load uboot, ReadLba = 2000
Load OK, addr=0x200000, size=0xdcfd8
RunBL31 0x40000
NOTICE: BL31: v1.3(debug):42583b6
NOTICE: BL31: Built : 07:55:13, Oct 15 2019
NOTICE: BL31: Rockchip release version: v1.1
INFO: GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3
INFO: Using opteed sec cpu_context!
INFO: boot cpu mask: 0
INFO: plat_rockchip_pmu_init(1190): pd status 3e
INFO: BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK
ERROR: Error initializing runtime service opteed_fast
INFO: BL31: Preparing for EL3 exit to normal world
INFO: Entry point address = 0x200000
INFO: SPSR = 0x3c9
U-Boot 2020.07-armbian (Oct 13 2020 - 16:49:59 +0200)SoC: Rockchip rk3399
Reset cause: RST
DRAM: 3.9 GiB
PMIC: RK808
SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
MMC: mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environmentIn: serial
Out: serial
Err: serial
Model: Helios64
Revision: 1.2 - 4GB non ECC
Net: eth0: ethernet@fe300000
scanning bus for devices...
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
3185 bytes read in 5 ms (622.1 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 1
166 bytes read in 5 ms (32.2 KiB/s)
16452750 bytes read in 700 ms (22.4 MiB/s)
27275776 bytes read in 1156 ms (22.5 MiB/s)
79946 bytes read in 10 ms (7.6 MiB/s)
2698 bytes read in 8 ms (329.1 KiB/s)
Applying kernel provided DT fixup script (rockchip-fixup.scr)
## Executing script at 09000000
## Loading init Ramdisk from Legacy Image at 06000000 ...
Image Name: uInitrd
Image Type: AArch64 Linux RAMDisk Image (gzip compressed)
Data Size: 16452686 Bytes = 15.7 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
Booting using the fdt blob at 0x1f00000
Loading Ramdisk to f4f35000, end f5ee5c4e ... OK
Loading Device Tree to 00000000f4eb9000, end 00000000f4f34fff ... OKStarting kernel ...
openmediavault 5.5.14-1 (Usul) helios64 ttyS2Output from df
Spoileraxel@helios64:~$ df
Filesystem 1K-blocks Used Available Use% Mounted on
udev 1869984 0 1869984 0% /dev
tmpfs 389128 10396 378732 3% /run
/dev/mmcblk0p1 60910176 5312260 54945884 9% /
tmpfs 1945632 0 1945632 0% /dev/shm
tmpfs 5120 0 5120 0% /run/lock
tmpfs 1945632 0 1945632 0% /sys/fs/cgroup
tmpfs 1945632 12 1945620 1% /tmp
folder2ram 1945632 14632 1931000 1% /var/log
folder2ram 1945632 0 1945632 0% /var/tmp
folder2ram 1945632 484 1945148 1% /var/lib/openmediavault/rrd
folder2ram 1945632 724 1944908 1% /var/spool
folder2ram 1945632 13988 1931644 1% /var/lib/rrdcached
folder2ram 1945632 4 1945628 1% /var/lib/monit
folder2ram 1945632 1288 1944344 1% /var/cache/samba
/dev/mapper/sda-crypt 2883204744 1150794608 1732393752 40% /srv/dev-disk-by-label-parity1
/dev/mapper/sdb-crypt 2883204744 1127952968 1755235392 40% /srv/dev-disk-by-label-data1
/dev/mapper/sdc-crypt 2883204744 1127947312 1755241048 40% /srv/dev-disk-by-label-data2
tmpfs 389124 0 389124 0% /run/user/1000
pool0:65b1923f-43cc-499b-b4c3-265b982c7f8a 5766409488 2255900280 3510476440 40% /srv/65b1923f-43cc-499b-b4c3-265b982c7f8a/etc/fstab
Spoileraxel@helios64:~$ cat /etc/fstab
UUID=a79a14c0-3cf4-4fb9-a6c6-838571351371 / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 1
tmpfs /tmp tmpfs defaults,nosuid 0 0
# >>> [openmediavault][...]
-
19 hours ago, flower said:
Maybe its an ip conflict?
apt-get install arp-scan
arp-scan --localnet -lI switched to eth1 to install it, then switched back to eth0 and ran arp-scan.
There are lots of reference to my decommissioned Raspberry Pi on 192.168.0.110. Turns out I forgot to delete the ARP binding on my router to make sure my old Pi was given 192.168.0.110.
PEBKAC…Thanks a lot anyway!
-
Forgot to add ifconfig output, it might be useful
root@helios64:~# ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.0.110 netmask 255.255.255.0 broadcast 192.168.0.255 inet6 fe80::5550:854d:6ad0:b6d7 prefixlen 64 scopeid 0x20<link> ether 64:62:66:d0:03:7c txqueuelen 1000 (Ethernet) RX packets 390 bytes 60863 (59.4 KiB) RX errors 0 dropped 1 overruns 0 frame 0 TX packets 384 bytes 35588 (34.7 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 27 eth1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether 64:62:66:d0:03:7d txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 32 bytes 2640 (2.5 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 32 bytes 2640 (2.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
I also did further testing:
- When pinging from my router, I get a timeout (set to 2000ms)
- When pinging my desktop and laptop computers from the Helios64, I get a response.
- When pinging its IP (192.168.0.110) from the Helios64, I get a response.
- When pinging the Helios from my desktop and laptop, I get a response.
-
Hello,
After I had issues with DNS resolution on my Helios64, I flashed a brand new Armbian image and now I cannot seem to connect to any devices on the network.
I tried pinging my computer, router and 8.8.8.8 without success (which I can from my computers or router). I literally just I set root's password.I literally have no idea why this is happening. Every other computer in the network are working fine and the Helios64 has no problem the first few days I used it.
Big thanks to anyone willing to help me!
---
Version: Armbian 20.08.13 Debian 10 Buster (Kernel 5.8.16)
DHCP config:
- Default gateway: 192.168.0.1 (my router's IP)
- Primary DNS: 80.67.169.12 (DNS from https://en.wikipedia.org/wiki/French_Data_Network)
- Secondary DNS: 192.168.1.1 (my ISP's router)
My router's DHCP is set to give 192.168.0.110 to my Helio64's MAC address.
Kobol Helios64 on Sale
in Rockchip
Posted
I would really like to but unfortunately I don't meet eBay's criterion for selling internationally, I only can add domestic shipping options...