awef reacted to DrTune in Can we stop for a second and give credit due to the Armbian posse
I've been using Allwinner boards for the last couple of years and Armbian+forums have made this a workable thing that I promote to my friends as being The Way To Go instead of being a big fat waste of time.
Igor + Tkaiser (and anyone else forgive me if I didn't give you a shout) - You fucking rock. You really do; you've all provided amazing amounts of support for multiple kernels and userspaces and in the face of (at least) bullshit from the chip vendors, yet you are absolutely crucial to them being taken seriously.
The work from Armbian has (for me) made the difference between BananaPi, OrangePi, etc all being an unusable washout of #ShitDidn'tWork, to being something I am excited to build into things and personally promote.
Igor, Tkaiser; I've never met you but your work speaks for itself; you give a shit and you keep giving and shit and THANK YOU FOR THAT.
I just donated you some $. If you're still reading this and you're using their work, you might think about doing same. FWIW; what turned my head is seeing Igor and crew putting _years_ of work into this.
Anyway, much, much, much appreciated. From one to another; good job.
awef reacted to zador.blood.stained in Orange Pi PC+ will not boot Armbian
If Lubuntu and Raspbian use legacy u-boot then most probably it ignores card detect switch (i.e. legacy u-boot on Pine64 still boots fine)
In u-boot and SPL for sunxi devices - no, in kernel - maybe, but card presence can still be detected by polling. But this is a question of describing hardware configuration regardless of its usefullness, so if there is a CD switch of "correct" polarity, it is assumed to work.
awef reacted to martinayotte in Orange Pi zero NOR Flash
You don't need to do all this since nightly builds already provides SPI-NOR support. The only thing you have to do is changing the partitions sizes in the current DT :
You will see the MTD partitions by doing "cat /proc/mtd", and you can use flashcp from mtd-utils to write to /dev/mtd0.
awef reacted to tkaiser in DD clone boots but files are missing and with wrong permissions, why?
Always do a verify since otherwise you never know when your hardware and/or dd failed. The following might require an
apt-get install gddrescue p7zip first. And then given we're talking about an SD card available as /dev/sda it's just:
root@ubuntu:~# cat /proc/partitions major minor #blocks name 179 0 3887104 mmcblk0 179 1 3686400 mmcblk0p1 8 0 500224 sda 8 1 1024 sda1 root@ubuntu:~# md5sum /dev/sda 19d9508a47b1469dc5570c2e8507112c /dev/sda root@ubuntu:~# ddrescue /dev/sda SD-card.img SD-card.log GNU ddrescue 1.19 Press Ctrl-C to interrupt rescued: 512229 kB, errsize: 0 B, current rate: 7798 kB/s ipos: 512163 kB, errors: 0, average rate: 7214 kB/s opos: 512163 kB, run time: 1.18 m, successful read: 0 s ago Finished root@ubuntu:~# md5sum SD-card.img 19d9508a47b1469dc5570c2e8507112c SD-card.img root@ubuntu:~# 7zr a -t7z -m0=lzma -mx=9 -mfb=64 -md=32m -ms=on SD-card-19d9508a47b1469dc5570c2e8507112c.7z SD-card.img 7-Zip (A) 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18 p7zip Version 9.20 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,4 CPUs) Scanning Creating archive SD-card-19d9508a47b1469dc5570c2e8507112c.7z Compressing SD-card.img Everything is Ok root@ubuntu:~# ls -al SD-card-19d9508a47b1469dc5570c2e8507112c.7z -rw-r--r-- 1 root root 192350156 Dec 8 11:35 SD-card-19d9508a47b1469dc5570c2e8507112c.7z So you end up with a verified and compressed card image. And since MD5 hash is incuded in filename you could also check integrity after unpacking again.
TL;DR: Do not use dd to either write OS images (use Etcher!) or read from devices (use GNU ddrescue!). Using dd is ALWAYS wrong. Verify reading and writing stuff. And in case you plan to do anything that should serve as backup then TEST it afterwards.
awef reacted to chrisd in OPI Zero - Incoming SSH - Can't connect
When you have 2 nics in the same network, you need to setup source level routing. What you want is that everything which comes on eth0, should be answered on eth0. And everything which comes on wlan0 should be responded from wlan0. (Which is actually the default in Solaris, I don't know why this is not the default in Linux)
Easiest way is to define the routes in two tables, see here:
awef reacted to tkaiser in OPI Zero - Incoming SSH - Can't connect
Bummer says it all. What an attitude. I get sooooo sick of this! Unbelievable!
When ping works but SSH through Ethernet not then most probably the board is stuck in u-boot! You won't believe it but we test the stuff we provide. So if you want to do more than just complaining then grab a serial console and provide the boot log so we can reproduce the issue IF there is one and it's not just the usual issue called insufficient power supply (Zero uses Micro USB which is known to cause problems) or broken burning process or SD card.
Why do you hijack a thread about Wi-Fi related problems when you've not been able to even configure WI-Fi since your installation does not even boot?!
I'm out from now on!
awef reacted to Maeur1 in OPZero SPIdev usage
Well after using your script.bin, it seems to have the other SPI line in it (spidev1.0 and spidev0.0)! But I need to test whether it is working, so I shall try out both the NOR flash SPI and also the GPIO SPI once I get home.
Thanks for that help
EDIT: After getting home, and testing, both SPI lanes are working perfectly now! Thanks a bunch