Bernie_O

Hi @ww9rivers, I am still running Kernel 4.11.5 because of random freezes with newer kernels. is your Banana Pi still up and running without freezes? Uptime is 4 weeks now, isn’t it? How exactly did you issue the ping command so that it kept running after logging out? With nohup or through a cronjob on reboot?

Thanks for the quick reply

I want to downgrade the kernel because auf random freezes on my Banana Pi and was following this tutorial to downgrade to Mainline stable kernel (Armbian 5.31): At apt.armbian.com I can find all required packages except for: linux-firmware-image-next-sunxi According to the linked thread I need this package otherwise the system may not start anymore. Could someone tell me where to find that package? Thanks :-)

I switched to Kernel 4.19.57 on my Banana Pi M1 and can confirm that kworker eats 15-20% cpu constantly. Could get rid of it with: modprobe -r sun4i_gpadc sun4i_gpadc_iio With that I also lost thermal monitoring. However I found another source for thermal measurement calculated with: ( (in_temp_raw + in_temp_offset) / 10 ): /sys/bus/iio/devices/iio:device0/in_temp_raw /sys/bus/iio/devices/iio:device0/in_temp_offset /sys/bus/iio/devices/iio:device0/in_temp_scale While the scale seems to be wrong (it is only 10, not 100), it is a quite similar measurement like the one which

Have a look at line 119: https://github.com/armbian/build/blob/master/config/templates/customize-image.sh.template#L119

cd /path/to/mountpoint/folder iozone -e -I -a -s 100M -r 1k -r 2k -r 4k -r 16k -r 128k -r 512k -r 1024k -r 16384k -i 0 -i 1 -i 2

I used this command to mount with write caching disabled: mount_exfat -o nodev,nosuid,noowners,noasync /dev/disk2s1 testmount still similar output (see attached file "storage-report"). Grml... I then did a very basic sequential test of writing 5GB to get a rough idea of sequential speed with: sh-3.2# time sh -c "dd if=/dev/zero of=testfile bs=100k count=50k && sync" 51200+0 records in 51200+0 records out 5242880000 bytes transferred in 61.054574 secs (85872027 bytes/sec) real 1m2.059s user 0m0.114s sys 0m2.953s So the sequential write speed

I was also really surprised by the numbers. In the Terminal I navigated to a folder on the SD card and then issued the command. In a testing run I could see that there are temporary files created and deleted in that folder. So to me it looks like it was running on the SD Card. I have no idea how to switch caching off on Mac OS. Is there anything else I can do to prove that the test is running on the SD Card? The Card is plugged into the internal SD Card Reader of my MacBook Pro 11,4 (15 inch, mid 2015). EDIT: I‘ll try this, when I get back home after work to

I saw that you tested a SanDisk Extreme Pro 64GB - A2 card with ext4 and didn't get the expected results (https://github.com/ThomasKaiser/Knowledge/blob/master/articles/A1_and_A2_rated_SD_cards.md) I tested my SanDisk Extreme Pro A2 256GB micro with A2 logo (bought beginning of October 2018), formatted ExFAT under MacOS 10.14 (iozone installed via homebrew). I thought this might be interesting for you: Test 1: random random bkwd record stride

No, I didn't run into any problems (not even non-severe ones). I did everything in a differen order though: - I changed /etc/apt/sources.list to point to Debian stretch repositories - apt-get update && apt-get dist-upgrade - then I did reboot the system - after couple of days I noticed that I maybe should also upgrade the armbian related packages and posted my questions above - I proceeded like pointed out above with upgrading stretch- (and purging jessie-) armbian related packages That was it. System is running nicely thanks to the good work the ar

Well... At least I did not. Upgraded two Banana Pis without any issues.

If you are using mainline kernel this might help:

Installed 5.38 (mainline) on two Banana Pi. Both have /boot on SD and system (Debian Stretch) on SATA. Both up and running after a reboot (required to activate kernel 4.14.15). No problems so far. I can confirm ~10% CPU load by kworker though. Thanks for Armbian and keep up the good work! EDIT: Sorry, that was misleading: I did not do a fresh install from an image. Both Banana Pi were upgraded from Armbian 5.36

Now that you wrote that, I also remember, that it took quite a while for the „freeze“ to disappear. So all you have to do is being patient ;-)

I also had this problem after updating to 5.36. I then noticed a permission error in /var/log/syslog. Once I corrected the permissions of the appropriate path/file the welcome-screen did not „hang“ anymore with old information. Unfortunately I can‘t remember which path or file I had to change the permissions, but it was clear when I saw the error in syslog. Hope that helps at least for that „hanging“-with-old-information issue.