+- PINE64 (https://forum.pine64.org)
+-- Forum: ROCK64 (https://forum.pine64.org/forumdisplay.php?fid=85)
+--- Forum: Linux on Rock64 (https://forum.pine64.org/forumdisplay.php?fid=88)
+--- Thread: 0.7.8 Linux release from ayufan for Rock64 (/showthread.php?tid=6309)
RE: 0.7.8 Linux release from ayufan for Rock64 - Luke - 09-05-2018
Quote:<lukasz> ayufan: any word on a new Rock64 and Pro release ?
<ayufan2> lukasz: soon, tm
<ayufan2> I got new boards, and started using NAS. It works great.
<ayufan2> I also wait for FAN to tune it.
<ayufan2> I will likely push a lot of small improvements that adds extra things: 10gbps support.
RE: 0.7.8 Linux release from ayufan for Rock64 - KC7NOA - 10-13-2018
(09-05-2018, 02:54 AM)Luke Wrote:Quote:<lukasz> ayufan: any word on a new Rock64 and Pro release ?
<ayufan2> lukasz: soon, tm
<ayufan2> I got new boards, and started using NAS. It works great.
<ayufan2> I also wait for FAN to tune it.
<ayufan2> I will likely push a lot of small improvements that adds extra things: 10gbps support.
Glad to hear it I'll be getting my pine64pro soon enough and I plan to put it through its Paces for SDR Radio interest.
Is the Mali 400 drivers included in the xenial 18.04 image or is there a lot that still needs to be done?
RE: 0.7.8 Linux release from ayufan for Rock64 - Averell - 10-17-2018
Hello,
no one mentioned a problem I had on two different installations of this Debian Stretch minimal : although I used several times :
Code:
dpkg-reconfigure keyboard-configurationthe keyboard layout does not change and remains the English one.
In /etc/default/keyboard, I have the right values :
XKBMODEL = "pc105"
XKBLAYOUT = "fr"
I tried different settings with no effect.
Answer to my question
The answer is that setupcon is missing. Without it, the console cannot make use of the keyboard settings.
may be there are other ways, but the way I found to install it is to install : console-setup
After that
Code:
sudo setupconAnd the keyboard is French.
RE: 0.7.8 Linux release from ayufan for Rock64 - brox - 11-09-2018
Guys, I have 2 problems with stretch-minimal-rock64-0.7.9-1067 (boot from eMMC)
1. During ssh login I see before command prompt:
Quote:-bash: warning: setlocale: LC_ALL: cannot change locale (ru_RU.UTF-8)
How to add my locale properly?
2. I don't see how /tmp is mounted.
mount command returns:
Quote:sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=2007204k,nr_inodes=501801,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=401844k,mode=755)
/dev/mmcblk0p7 on / type ext4 (rw,relatime)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
/dev/mmcblk0p6 on /boot/efi type vfat (rw,relatime,sync,fmask=0022,dmask=0022,codepage=936,iocharset=utf8,shortname=mixed,errors=remount-ro)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=401840k,mode=700,uid=1000,gid=1000)
No mentions of /tmp here. But somehow I need to set /tmp executable.
Please help!
RE: 0.7.8 Linux release from ayufan for Rock64 - evilbunny - 11-09-2018
(11-09-2018, 04:39 AM)brox Wrote: Guys, I have 2 problems with stretch-minimal-rock64-0.7.9-1067 (boot from eMMC)
1. During ssh login I see before command prompt:
Quote:-bash: warning: setlocale: LC_ALL: cannot change locale (ru_RU.UTF-8)
How to add my locale properly?
You can modify the below commands and it'll work then
Code:
sed -i -e "s/# en_US.UTF-8 UTF-8/en_US.UTF-8 UTF-8/" /etc/locale.gen
echo "LANG="en_US.UTF-8"">/etc/default/locale
dpkg-reconfigure --frontend=noninteractive locales
update-locale LANG=en_US.UTF-8Quote:2. I don't see how /tmp is mounted.
mount command returns:
<snip>
No mentions of /tmp here. But somehow I need to set /tmp executable.
Please help!
df -h is so much more useful, but tmp isn't mounted, it defaults to residing on the root partition.
RE: 0.7.8 Linux release from ayufan for Rock64 - brox - 11-09-2018
(11-09-2018, 06:20 AM)evilbunny Wrote:Thanks! It works nowCode:sed -i -e "s/# en_US.UTF-8 UTF-8/en_US.UTF-8 UTF-8/" /etc/locale.gen
echo "LANG="en_US.UTF-8"">/etc/default/locale
dpkg-reconfigure --frontend=noninteractive locales
update-locale LANG=en_US.UTF-8Quote:df -h is so much more useful, but tmp isn't mounted, it defaults to residing on the root partition.
RE: 0.7.8 Linux release from ayufan for Rock64 - thewonderer - 01-13-2019
Hoping for some new builds soon as the last pre-release (0.7.11) Ubuntu 18.04, crashed after a few hours... I did note that the performance seemed better and the copying over network via SMB share was much improved (still not getting anywhere near the 100MB/s throughput though)....
RE: 0.7.8 Linux release from ayufan for Rock64 - Ice - 01-27-2019
Hi Guys, my RTC PCF8523(https://www.adafruit.com/product/3386) is not working on the Rock64.
It is working on the RPI3B:
root@rpi3b01:~# uname -a
Linux rpi3b01 4.14.79-v7+ #1159 SMP Sun Nov 4 17:50:20 GMT 2018 armv7l GNU/Linux
root@rpi3b01:~# modinfo rtc-pcf8523
filename: /lib/modules/4.14.79-v7+/kernel/drivers/rtc/rtc-pcf8523.ko
license: GPL v2
description: NXP PCF8523 RTC driver
author: Thierry Reding <thierry.reding@avionic-design.de>
srcversion: 88403DCB7B29428A4B359BE
alias: i2c:pcf8523
alias: of:N*T*Cnxp,pcf8523C*
alias: of:N*T*Cnxp,pcf8523
depends:
intree: Y
name: rtc_pcf8523
vermagic: 4.14.79-v7+ SMP mod_unload modversions ARMv7 p2v8
root@rpi3b01:~# i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
It works and being used.
root@rock64:~# uname -a
Linux rock64 4.4.154-1128-rockchip-ayufan-g61b4b1151f9a #1 SMP Tue Dec 25 14:31:31 UTC 2018 aarch64 GNU/Linux
root@rock64:~# modinfo rtc-pcf8523
filename: /lib/modules/4.4.154-1128-rockchip-ayufan-g61b4b1151f9a/kernel/drivers/rtc/rtc-pcf8523.ko
license: GPL v2
description: NXP PCF8523 RTC driver
author: Thierry Reding <thierry.reding@avionic-design.de>
alias: i2c:pcf8523
alias: of:N*T*Cnxp,pcf8523*
depends:
vermagic: 4.4.154-1128-rockchip-ayufan-g61b4b1151f9a SMP mod_unload aarch64
Enabling i2c0:
root@rock64:~# enable_dtoverlay i2c0 i2c@ff150000 okay
Applying...
/dts-v1/;
/ {
fragment@0 {
target-path = "/i2c@ff150000";
__overlay__ {
status="okay";
};
};
};
Warning (unit_address_vs_reg): Node /fragment@0 has a unit name, but no reg property
Applied!
Right now it the RTC module is not plugged in:
root@rock64:~# i2cdetect -y 0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f
10: 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f
20: 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f
30: -- -- -- -- -- -- -- -- 38 39 3a 3b 3c 3d 3e 3f
40: 40 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f
70: 70 71 72 73 74 75 76 77
If I add the RTC PCF8523. It does not pop at 0x68 as on my RPI3B.
What else should be done in order to get the RTC module working?
Thnx for your help!
RE: 0.7.8 Linux release from ayufan for Rock64 - mcerveny - 01-27-2019
(01-27-2019, 03:19 AM)Ice Wrote:Code:root@rock64:~# i2cdetect -y 0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f
10: 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f
20: 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f
30: -- -- -- -- -- -- -- -- 38 39 3a 3b 3c 3d 3e 3f
40: 40 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f
70: 70 71 72 73 74 75 76 77
- Check I2C bus and protocol description.
- Check ROCK64 schema.
- Check your gadget (Schema is missing, I hope that it is using 3.3V not 5V).
- Check "i2cdetect" output.
- Something is missing or wrong ? Yes, pullup resistors are missing on I2C0_SDA/I2C0_SCL (to 3.3V not 5V).
RE: 0.7.8 Linux release from ayufan for Rock64 - Ice - 02-01-2019
(01-13-2019, 10:06 PM)thewonderer Wrote: Hoping for some new builds soon as the last pre-release (0.7.11) Ubuntu 18.04, crashed after a few hours... I did note that the performance seemed better and the copying over network via SMB share was much improved (still not getting anywhere near the 100MB/s throughput though)....
Dear Guys,
I bought a new test/final RTC. It is a DS3231+AT24C32 RTCM and working fine at 3.3V!
root@rock64:/lib/modules/4.4.154-1128-rockchip-ayufan-g61b4b1151f9a/kernel/drivers/rtc# uname -a && modinfo rtc_ds1307
Linux rock64 4.4.154-1128-rockchip-ayufan-g61b4b1151f9a #1 SMP Tue Dec 25 14:31:31 UTC 2018 aarch64 GNU/Linux
filename: /lib/modules/4.4.154-1128-rockchip-ayufan-g61b4b1151f9a/kernel/drivers/rtc/rtc-ds1307.ko
license: GPL
description: RTC driver for DS1307 and similar chips
alias: i2c:rx8025
alias: i2c:pt7c4338
alias: i2c:mcp7941x
alias: i2c:mcp7940x
alias: i2c:m41t00
alias: i2c:ds3231
alias: i2c:ds1340
alias: i2c:ds1388
alias: i2c:ds1339
alias: i2c:ds1338
alias: i2c:ds1337
alias: i2c:ds1307
depends:
vermagic: 4.4.154-1128-rockchip-ayufan-g61b4b1151f9a SMP mod_unload aarch64
Enable i2c0:
enable_dtoverlay i2c0 i2c@ff150000 okay
Tell the kernel that a DS3231 is using the i2c-0:
echo ds1307 0x68 > /sys/class/i2c-adapter/i2c-0/new_device
Read the HW clock:
root@rock64:/lib/modules/4.4.154-1128-rockchip-ayufan-g61b4b1151f9a/kernel/drivers/rtc# hwclock -r -D --rtc /dev/rtc1
hwclock from util-linux 2.29.2
Using the /dev interface to the clock.
Last drift adjustment done at 1549029470 seconds after 1969
Last calibration done at 1549029470 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2019/02/01 14:26:37
Hw clock time : 2019/02/01 14:26:37 = 1549031197 seconds since 1969
Time since last adjustment is 1727 seconds
Calculated Hardware Clock drift is 0.000000 seconds
2019-02-01 15:26:36.139249+0100
Detecting i2c:
root@rock64:/lib/modules/4.4.154-1128-rockchip-ayufan-g61b4b1151f9a/kernel/drivers/rtc# i2cdetect -y 0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- 57 -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
So the Rock64 board is working fine!
