Moklev
-
Posts
69 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by Moklev
-
-
-
Yes Giulio, it's probably the kernel... no version after 6.1.x works
-
Armbian 24.2 is broken on Orange PI PC2 (Debian Bookworm CLI)
Latest stable community release:
With update 23.11 -> 24.2 the orange pi pc2 no longer starts.
I tried a new sd installation and it too does not appear on the network. Right now I don't have a serial cable to check but it is possible that the network driver is missing or not working.
SD, SBC and PSU are 100% working: a revert to 23.11.2 makes it work perfectly.
-
30 minutes ago, tkaiser said:
I was asking for armbianmonitor -u output but got only a redacted/censored variant (the line numbers are there for a reason). I was asking for what's the output of 'free -m' NOW. As in 'with your vm.swappiness=30 or 60 setting). Instead you rebooted (why?! You can adjust vm.swappiness all the time, no reboot needed).
It's a problem, "armbianmonitor -u" is broken, all free service (pastebin, ghostbin, etc...) are limited to 512kB-1,5MB. Now is not possibile to upload all necessary data.
30 minutes ago, tkaiser said:Providing 'free -m' output directly after a reboot is pointless as you see ZERO swapping happened. And providing a log containing information from 14.36.28 until 14.53.31 is pointless too.
Ok
Yesterday you started monitoring. Now you report having switched from vm.swappiness=30 to 100. But you're able to report that with 100 settings your board froze and even RPi Monitor web page not being accessible. So you tested within the last 29 hours already twice with 100 settings and were able to report your board crashing (since you talk about '3-12 h' -- if these 3-12h is some anecdotical story from days ago I'm not interested in. It's only relevant what happens now with some monitoring installed able to provide insights).
SBC is crashed on 20.09 (boot at 13:05, crashed at 15:35*), on 21.09 (boot at 14.00 then crashed at 17.37*) and on 22.09 (boot at 13:35 then crashed at 23.12*). (*): timestamp of the last picture shooted and processed. Sunday (23.09) I've changed the vm.swappiness to 30 and the problem has been solved.
Now I need the following directions to help you:
- when to run the "free -m" command
- how to send the log if armbianmonitor does not work
- how long to run the indicated scripts
I need at least 1 or 2 weeks to do everything...
-
vm.swappiness=100
https://ghostbin.com/paste/vrt5t
With vm.swappiness=30: system work fine
With wm.swappiness=100: system work fine for a random time (3-12 h), then hang with ssh unreachable, yellow ethernet led fixed on, pihole/motioneye/rpi monitor web pages unreachables.
Hardware: OrangePI Zero v1.4 - Sandisk uSD 16GB U1 A1 (checked, good healt) EXT4 - Toshiba USB Stick 32GB (checked, good healt) F2FS, USB PSU FriendlyARM 5V/3A (checked, good healt).
-
First log (reduced because too large): Orange Pi Zero (vm.swappiness=30)
-
Debian 9.5 AMD/Microserver (vm.swappiness=60)
iostat.log
root@tubserver:~# cat iostat.log Linux 4.17.0-0.bpo.3-amd64 (tubserver) 27/09/2018 _x86_64_ (2 CPU) avg-cpu: %user %nice %system %iowait %steal %idle 0,09 0,01 0,15 0,29 0,00 99,45 Device: tps kB_read/s kB_wrtn/s kB_read kB_wrtn sda 1,55 24,94 27,24 21613817 23605307 sdb 1,23 4,76 27,24 4122642 23605307 md3 0,22 0,77 0,13 669789 109496 md1 0,00 0,00 0,00 2304 0 md2 0,36 26,05 19,72 22569513 17083692 md0 1,55 2,89 7,29 2501781 6313004 sdc 0,18 1,12 1,80 973561 1560460 zram0 0,01 0,00 0,03 2660 29588 zram1 0,01 0,00 0,04 2904 38420 avg-cpu: %user %nice %system %iowait %steal %idle 0,10 0,00 0,15 0,73 0,00 99,02 Device: tps kB_read/s kB_wrtn/s kB_read kB_wrtn sda 2,81 0,05 68,93 28 41359 sdb 2,77 0,00 68,93 0 41359 md3 0,00 0,00 0,00 0 0 md1 0,00 0,00 0,00 0 0 md2 0,00 0,00 0,00 0 0 md0 4,50 0,05 68,74 28 41244 sdc 0,00 0,00 0,00 0 0 zram0 0,00 0,01 0,00 4 0 zram1 0,00 0,00 0,00 0 0free.log
root@tubserver:~# cat free.log gio 27 set 2018, 11.22.53, CEST total used free shared buff/cache available Mem: 1743 257 123 26 1362 1278 Swap: 2776 55 2721 gio 27 set 2018, 11.24.12, CEST total used free shared buff/cache available Mem: 1743 258 121 26 1363 1276 Swap: 2776 55 2721 gio 27 set 2018, 11.27.01, CEST total used free shared buff/cache available Mem: 1743 260 155 26 1327 1274 Swap: 2776 54 2722 gio 27 set 2018, 11.37.01, CEST total used free shared buff/cache available Mem: 1743 260 154 26 1328 1274 Swap: 2776 54 2722Tomorrow for OPZ/Armbian data... both for vm.swappiness=30 and 100 (and armbianmonitor -u)
-
1 hour ago, tkaiser said:
Do you use this board to boil water? 75°C SoC temperature reported at boot? [...]
After warm reboot... ~70-72°C it's a badly reported temperature, correct value -measured with a Fluke thermometer- is ~65°C on the SOC heatsink. It's normal, the scb works as a visual motion analizer (1 h264 hd stream) 24/7 since mid 2017.
QuoteHopefully it still works but in your situation I would immediately install RPi-Monitor using
armbianmonitor -rYes, I've starting monitoring...
QuoteZram is a kernel thing and not related to any userland stuff at all. In other words: you have the same set of problems on a MicroServer and an ARM SBC running different software stacks? Are SBC and MicroServer connected to the same power outlet?
They are not... totally different purpose or software stacks... and power outlet.
Anyway now my OPZ works stable again with Armbian 5.60 (with vm.swappiness set to 30-60).
-
The good thing: reducing the value to 30 (vm.swappiness = 30) seems to solve the problem. Now I got ~22 h uptime without any hang...
The bad one: an heavy zram usage on my AMD/Debian 9.5 microserver freeze the system (both gnome shell and ssh). :-|
I think zram has some problems with Debian...
-
2 hours ago, ag123 said:
vm.swappiness = 100
check in /etc/sysctl.conf if it is defined there you may like to reduce that value to 50 (or even for tests 0) to see if it made a difference
Interesting... I'll change swap threshold to a more conservative value to 30 and I'll test it for 24/48h.
-
Still stability issues on stable v5.60 (v5.59 upgraded to 5.60). I can not have an uptime over 3-12 hours (it is not reachable via ssh or webgui).
SD and psu are OK. The system run stable on old v5.38 (january 2018) with same setup for weeks.
Orange Pi Zero 512/v1.4 system log:
-
All right! Native zRAM implementation work very well in Armbian (next) v5.59 (tested on my Pi Zero and PC2).EDIT (problem with v5.60 and vm.swappiness = 100):
-
My Orange Pi PC2 work fine with Stretch (mainline, 4.14.48) between 35 and 65 °C. I got only a minor (but annoying) problem: the board start overheating after a shutdown (sudo shutdown -h now) and reach >70 °C after few minutes. Is it a kernel problem? Or a hardware design fault?
-
They have released the first version (07_2018)
-
https://forum.armbian.com/topic/7502-ov5640-on-mainline-kernel/
-
Me too... with an old HP z400 Workstation (Xeon W3530, 12GB ECC DDR3 and a SSD Crucial MX300) build process is quite fast.
-
-
12 hours ago, jernej said:
H5 has mali 450, which needs different binding and different userspace library.
Yes...
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/gpu/arm,mali-utgard.txt -
Bootlin has released the new blobs (32&64 bit, X11/fbdev/Wayland, r6p2/r8p1).
-
It looks like Yong Deng's patch for V3s CSI.
+// SPDX-License-Identifier: GPL-2.0 +/* + * Copyright (c) 2011-2018 Magewell Electronics Co., Ltd. (Nanjing) + * All rights reserved. + * Author: Yong Deng <yong.deng@magewell.com> + */
Here:
https://www.spinics.net/lists/linux-media/msg130006.html
http://linux-sunxi.org/Linux_mainlining_effort
-
On 6/17/2018 at 11:45 PM, @lex said:
Today I had a chance to test OV5640 on mainline kernel 4.17.2 and see the status of OV5640 and CSI drivers, thanks to FE work and the author of the driver (help name here...). I tested on NanoPi K1 Plus (H5) to verify the images in very low light conditions, so don't expect good quality. [...]
This sounds very interesting!
But ... I can not find the interface driver (sun6i_csi). This is the Maxime Ripard's patch to mailine kernel or another one?
For the testing: I've a Orange Pi PC2 H5 and a OV5647 NoIR CSI. -
(disclaimer) No itention to make a Frankendebian (https://wiki.debian.org/DontBreakDebian) but ubuntu package "zram-config" works perfectly.
I tested it for two weeks in a: Orange PI Zero 512MB Armbian Stretch 5.40 4.14.18, Orange PI PC2 Armbian Stretch 5.40 4.14.18, AMD Sempron microserver Debian Stretch 9.4 4.9.0-6-amd64.
A short tutorial:
1. Download zram-config package (it's a universal package, it does not matter the architecture in use)
wget http://de.archive.ubuntu.com/ubuntu/pool/universe/z/zram-config/zram-config_0.5_all.deb
2. Install it
sudo dpkg -i zram-config_0.5_all.deb
3. Remove the installer
rm zram-config_0.5_all.deb
4. Check vm.swappiness
cat /proc/sys/vm/swappiness
(must be 60, default)
5. If not (i.e. "cat /proc/sys/vm/swappiness" return "1" ) change it to "60"
sudo nano /etc/sysctl.conf
and add "vm.swappiness=60" at the end of file
... and reboot
6. check zRAM service
sudo zramctl
NAME ALGORITHM DISKSIZE DATA COMPR TOTAL STREAMS MOUNTPOINT
/dev/zram0 lzo 437,8M 5,2M 1,4M 1,9M 2 [SWAP]
/dev/zram1 lzo 437,8M 5,2M 1,4M 1,9M 2 [SWAP]7. (optional) change lzo compression to lz4
sudo nano /usr/bin/init-zram-swapping
# initialize the devices
for i in $(seq ${NRDEVICES}); do
DEVNUMBER=$((i - 1))
echo $mem > /sys/block/zram${DEVNUMBER}/disksize
mkswap /dev/zram${DEVNUMBER}
swapon -p 5 /dev/zram${DEVNUMBER}
doneto...
# initialize the devices
for i in $(seq ${NRDEVICES}); do
DEVNUMBER=$((i - 1))
echo lz4 > /sys/block/zram${DEVNUMBER}/comp_algorithm
echo $mem > /sys/block/zram${DEVNUMBER}/disksize
mkswap /dev/zram${DEVNUMBER}
swapon -p 5 /dev/zram${DEVNUMBER}
done8. restart the service
sudo systemctl restart zram-config.service
9. check new compression algorithm
sudo zramctl
NAME ALGORITHM DISKSIZE DATA COMPR TOTAL STREAMS MOUNTPOINT
/dev/zram0 lz4 437,8M 5,2M 1,4M 1,9M 2 [SWAP]
/dev/zram1 lz4 437,8M 5,2M 1,4M 1,9M 2 [SWAP]10. check the zRAM priority over file swap
cat /proc/swaps
zRAM devices must be at priority "5", swap file at "-1" or "-2"
11. finish
:-)
-
On 5/4/2018 at 7:21 PM, CNLohr said:
Do you have any recommendations for SBCs with a better GPU and not a lot of $$? The Mali400 MP2 was sufficient for VR, I figured the 450 MP4 would be overkill.
An Asus Tinkerboard (Mali-T764) or a Rock64 (Mali-450MP4)?
With a quite good support:
http://opensource.rock-chips.com/wiki_Status_Matrix
On 5/4/2018 at 7:21 PM, CNLohr said:Still want to point out - my current question is how to install the Rockchip Mali Userspace blobs. I can't seem to figure out any configuration that produces a functioning Mali driver.
Try to build r6 driver by Free Electrons:
https://github.com/mripard/sunxi-mali
Kernel module:
git clone https://github.com/mripard/sunxi-mali.git
cd sunxi-mali
export CROSS_COMPILE=$TOOLCHAIN_PREFIX
export KDIR=$KERNEL_BUILD_DIR
export INSTALL_MOD_PATH=$TARGET_DIR
./build.sh -r r6p2 -b
./build.sh -r r6p2 -i... and the userspace driver:
git clone https://github.com/free-electrons/mali-blobs.git
cd mali-blobs
cp -a r6p2/fbdev/lib/lib_fb_dev/lib* $TARGET_DIR/usr/libPay attention:
"In order to build the kernel module, you'll need a functional DRM driver. If you have that already, you'll need the options CONFIG_CMA and CONFIG_DMA_CMA enabled in your kernel configuration."
-
52 minutes ago, chwe said:
It's about the Zero Plus2 H3 not the 'original zero'..
Ops... :)
Zero plus 2 is the H5 version? CPUFreq is in WIP stage also for the H5... all H boards have problem scaling down in idle with kernel 4.14.
Armbian 24.2 is broken on Orange PI PC2
in Allwinner sunxi
Posted
No, it's not 🙂
If you need something stable and safe, don't waste money on these crappy chinese sbc.
Buy a LP Intel like a Dell Wise 5070 on ebay (~80/90€ with a Celeron J, 4/8GB RAM and a SSD) and install Debian o CentOS. is rock-solid and requires only 5/8 Watt.