have now booted first time the debian buster image with new r64-board
power consumption is about 4.6w in default configuration (no pcie/wifi/bt active) while running apt upgrade (4.0w in idle)…after powerdown: 4.8w something is strange here
first thing i’ve noticed was readonly rootfs because of wrong uuid in /etc/fstab
root@bpi-iot-ros-ai:~# blkid
/dev/mmcblk1p1: LABEL_FATBOOT="BPI-BOOT" LABEL="BPI-BOOT" UUID="1539-6609" TYPE=
"vfat" PARTUUID="e43da9c5-01"
/dev/mmcblk1p2: LABEL="BPI-ROOT" UUID="80463388-3170-483b-ac00-378b69a7a277" TYP
E="ext4" PARTUUID="e43da9c5-02"
fstab:
UUID=c1401c29-e4d8-4924-8799-8b0f3a77b79b / ext4 defaults,noatime,nodiratime,com
mit=600,errors=remount-ro 0 1
tmpfs /tmp tmpfs defaults,nosuid 0 0
after i’ve fixed this (with vi because nano is currently unusable on serial, also tried with “resize” and changing $TERM) i got a rw-rootfs
on first apt update i got errors about not-yet-valid release file…this is because the system clock is wrong. this can be quick-fixed by
date -s '2019-10-11'
maybe anybody have an idea about nano (and some menus from apt/dpkg looking strange/no cursor/selection visible).
i expect there is any wrong console setting
root@bpi-iot-ros-ai:~# stty -a
speed 115200 baud; rows 24; columns 120; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>; eol2 = <undef>; swtch = <undef>; start = ^Q;
stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; discard = ^O; min = 1; time = 0;
-parenb -parodd -cmspar cs8 hupcl -cstopb cread -clocal -crtscts
-ignbrk brkint ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff -iuclc -ixany imaxbel -iutf8
opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0
isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt echoctl echoke -flusho -extproc
on ssh it works, tried setting same console settings, but this does not help…seems to be another problem…
it should be noted that debian buster is the armbian-version not the debian basic version…maybe nano is broken there
replaced rootfs with bootstrapped rootfs from original debian buster does not show this nano-issue