guidol

Just came across this
Might be useful for developers
Improved Optimization/speed and wear leveling of software on SD Cards
https://lwn.net/Articles/428584/
It's an older report...but it might help since devices are getting bigger and the need to keep the cards alive longer is getting more and more important
My take on the document is that 4MB blocks or when writing the image
Write to SD card using Linux:
- Find the device (eg: /dev/sdb1) you need to write to by using blkid or mount.
- Double check that you have the correct dev path for your SD card (eg: /dev/sdb1).
- Unmount the SD card and all its partitions by using umount /dev/sdb?.
- Write the image using dd if=/path/to/DietPi_vXX.img of=/dev/sdb.

sudo dd if=/path/to/DietPi_vXX.img of=/dev/sdb bs=4096
or

sudo dd if=/path/to/DietPi_vXX.img of=/dev/sdb bs=4M

The question was a hint, because some did wrote that only etcher could do a verfify.
 
Sure, not all Win32 DiskImager installations on this planet get autoupdated, so I did wrote about the NEWEST version with links for Windows-download!
The verify doesnt start automatically, but its only one click after write without selecting drive or image
(auto-verify could be a request for the next version).
 
I often do search informations via google an do help many people here in the forum - so I am not only do write questions, I also try to give answers.

Given the number of boards that can support higher CPU clocks (e.g., Nano Pi Neo 2, Plus2, Core2, OPi Zero Plus, OPi Zero Plus2 w/H/W MOSFET fix, etc.) it'd be great to be able to do this with overlays, rather than introduce a combinatorial explosion of board DTBs (i.e., per-board 1.1GHz max, 1.3GHz max, 1.4GHz max).
 
I have made some test override overlays to add the regulator and extend the CPU operating table (e.g., adding additional CPU core clock frequencies).  This works fine - one can just add the desired overlays in armbianEnv.txt and the new clock speeds appear and work:
... overlay_prefix=sun50i-h5 overlays=spi-spidev usbhost2 usbhost3 gpio-regulator-1.3v cpu-clock-1.3GHz param_spidev_spi_bus=1 ... However the problem is that one can't reliably run these boards at the higher clock rates without adjusting the thermal-zone cooling-map for the higher speeds.  Unfortunately device tree overlays don't appear to support thermal zones (at least I can't get them to compile with these present ).
 
I'm interested if anyone might have any ideas to to manage this.  Just brainstorming here, but perhaps we could make the default cooling-map for the H5 a bit more conservative, and then it could cover the introduction of the higher possible clock rates?  Or perhaps we could remove some slower entries from the H5 default clock operating table to allow for the addition of the optional higher clock rates (to better correspond to the default H5 cooling-map)?
 
Again, the nice thing about the overlay route is that we wouldn't have to change the 1.1GHz Armbian H5 default, so operation will be reliable.  But if users want to try speeding up their boards (whatever brand, VDD regulator, etc.), then they can just add an overlay or two and voila the higher speeds will be enabled.
 

how about the verify-function of the newest win32 disk imager?

https://forum.odroid.com/viewtopic.php?f=53&t=947
http://dn.odroid.com/DiskImager_ODROID/Win32DiskImager-odroid-v1.3.zip

or

https://sourceforge.net/projects/win32diskimager/files/
https://sourceforge.net/projects/win32diskimager/files/latest/download?source=files
 
 
Image Writer for Microsoft Windows Release 1.0.0 - The "Holy cow, we made a 1.0 Release" release. ============= New Features: ============= Verify Image - Now you can verify an image file with a device. This compares the image file to the device, not the device to the image file (i.e. if you write a 2G image file to an 8G device, it will only read 2G of the device for comparison). Additional checksums - Added SHA1 and SHA256 checksums.  

for Windows I do like the USB Image Tool (USB-IT) from
https://www.alexpage.de/usb-image-tool/
 
because it will startup much faster than the BIG etcher - and USB-IT is working fine for me since more than 2 years
 

The Answer is yes
Pin 2 or 4 for 5V and Pin 6 for GND
To find out where Pin 1 (Square) is - see the backside of the PCB - Pin 1 is a soldered square.

when disconnected console port,I mean 
"CP2102 USB TTL " not connected to PC USB;but "CP2102 USB TTL " still connected to Orange pi one UART0;
then usually it will auto go to uboot cli prompt >>
 
when I pulled out "CP2102 USB TTL "  wires from UART0 ,then I can boot fine.
problem solved.
 
Thanks

https://github.com/armbian/build/commit/8aacc920dac3f23e28d7dcc6cc666eb2c73db48f
One down. Thanks.

Spent a working day on this. https://www.armbian.com/nanopi-k1-plus/ Most of the things works. BT is not enabled, DVFS is coming in 4.18.y, ...

WOW!!! I'm very very very happy..
 
Problem solved.
 
For Mainline, do this
 1) alsamixer
2) press TAB (Make sure it falls to F4: CAPTURE)
3) Move to Mic1 (Use arrow keys)
4) Press SPACE and (L R Capture will appear)
 
I just needed to enable LINE IN on alxamixer.

I dont think you have to check the card, because most likely its caused by log2ram whcih is used ba armbian.
I also got "no space" in /var/log with my Pihole, because log2ram was set to 50MB in /etc/default/log2ram (50MB Ram-Disk)
 
@Igor is working with some other developers on a ZRAM option to replace this.
 
By now I have extended (on systems with >= 5122MB of Ram) the log2ram size to 150-250MB (depending on the System Ram).
Now my Pihole is working fine without getting "out of space"
root@bpi-a20(192.168.6.3):~# more /etc/default/log2ram # configuration values for the log2ram service # # enable the log2ram service? ENABLED=true # # size of the tmpfs mount SIZE=250M # # use rsync instead of cp -r # requires rsync installed, may provide better performance # due to copying only new and changed files USE_RSYNC=true #  
 

for Windows I do like the USB Image Tool (USB-IT) from
https://www.alexpage.de/usb-image-tool/
 
because it will startup much faster than the BIG etcher - and USB-IT is working fine for me since more than 2 years
 

for Windows I do like the USB Image Tool (USB-IT) from
https://www.alexpage.de/usb-image-tool/
 
because it will startup much faster than the BIG etcher - and USB-IT is working fine for me since more than 2 years
 

Our target for Allwinner is to get 4.18.y operational and 4.17.y servers only to prepare patches, as a temporal version. 

I haven't had a board fail yet.  Maybe I'm too nice to them...  

HI, If you want to get DNS IPs obtained from DHCP just add # before "dns=none" line in NetworkManager.conf file. It worked for me. 

not for the NanoPi A64 with armbian - but somebody is working on a kernel 4.4.111 at
http://www.friendlyarm.com/Forum/viewtopic.php?f=53&t=1543

Thank You. The first letter was a number. now i have a new password for my router. but it is curious with the number at the beginning.

I was not able to change resolution on mainline, but thanks a lot for pointing to the right patch.
The patch still has wrong parameters for 1024x768. After changing them to appropriate values (according to timings calculator), green box disappeared and hdmi sound becаme perfectly clear.
Pull request #1013

"sudo" is applied only on the left part of ">", right part still under normal user ...
Another way to do it is, but not really elegant :
 
echo "255" | sudo tee -a /sys/class/leds/orangepi\:red\:status/brightness
 
Another way could be :
 
echo "255" | sudo dd of=/sys/class/leds/orangepi\:red\:status/brightness

12 Hours later its still running (at a room temperatur of 28 degree):
Time        CPU    load %cpu %sys %usr %nice %io %irq   CPU  C.St.
10:29:57: 1200MHz  0.11   0%   0%   0%   0%   0%   0% 40.3°C  0/8
10:30:02: 1200MHz  0.10   3%   2%   0%   0%   0%   0% 42.1°C  0/8
10:30:07: 1200MHz  0.09   1%   0%   0%   0%   0%   0% 39.7°C  0/8
10:30:12: 1200MHz  0.08   0%   0%   0%   0%   0%   0% 40.7°C  0/8
10:30:17: 1200MHz  0.08   0%   0%   0%   0%   0%   0% 42.1°C  0/8
10:30:22: 1200MHz  0.07   0%   0%   0%   0%   0%   0% 37.8°C  0/8
10:30:27: 1200MHz  0.06   0%   0%   0%   0%   0%   0% 40.4°C  0/8
10:30:32: 1200MHz  0.06   0%   0%   0%   0%   0%   0% 39.9°C  0/8
10:30:38: 1200MHz  0.05   0%   0%   0%   0%   0%   0% 40.7°C  0/8
10:30:43: 1200MHz  0.05   0%   0%   0%   0%   0%   0% 39.8°C  0/8
10:30:48: 1200MHz  0.05   1%   0%   0%   0%   0%   0% 38.1°C  0/8
10:30:53: 1200MHz  0.04   0%   0%   0%   0%   0%   0% 40.4°C  0/8
10:30:58: 1200MHz  0.04   0%   0%   0%   0%   0%   0% 41.5°C  0/8
10:31:03: 1200MHz  0.04   2%   1%   0%   0%   0%   0% 41.1°C  0/8
10:31:08: 1200MHz  0.03   2%   2%   0%   0%   0%   0% 39.4°C  0/8
 

Update:
 

Tried to boot the 4.17 kernel on NanoPC T4. Works, but same issues as Firefly RK3399 above.
 
It seems that RK3399's upstream support still needs some time to complete, especially for newer boards.

https://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git/
 
Got this kernel booted up successfully (tag v4.18-rockchip-drivers-2). Haven't confirmed what's working and what's not.

Yes.  Actually I ended up commenting out the "&hdmi" block, the "&mixer0" block, and the "&sound_hdmi" block (I don't need audio support either):
/* &hdmi { status = "okay"; }; &mixer0 { status = "okay"; }; */ &r_pio { wifi_wake: wifi_wake@0 { pins = "PL7"; function = "irq"; bias-pull-up; }; }; /* &sound_hdmi { status = "okay"; }; */  
 

It's been a long time since I've looked at the boot/reboot messages on my OPi Zero +2, but when I first was trying it I noticed that all of the HDMI-related drivers were segfaulting at reboot, causing it to hang.  Given that I'm using these boards headless, I didn't need HDMI enabled, so I disabled these drivers via the DT.  This solved all of my reboot crashes/hangs.  If you want to try this, you can edit "sun50i-h5-orangepi-zero-plus2.dts" as before, and comment out the "&hdmi" block.
 
(Yes, I know it would be better to determine root cause for the crashes and fix that, etc. etc. but this is an easy workaround )