pfeerick

There is a regression in recent versions preventing the Pine64 Sopine modules to run on the Clusterboard.
 
It always required a network fix for getting the dhcp requests to come though, but since recent versions (newer than Armbian 20.11.3) this fix stopped working.
 
Further details here: https://forum.pine64.org/showthread.php?tid=13866
 
Edit: this issue is resolved. Works with kernel 5.10.60 right now.

Any idea where did this non-removable change come from? I checked the DTS file https://github.com/armbian/build/blob/master/packages/blobs/sunxi/a64/pine64so.dts#L2117 but the non-removable flag is still there in sdmmc@01c0f000 section. But then some changes in DTS files are introduced by kernel patches apparently. The only patch that removes the flag is this one https://github.com/armbian/build/blob/0cdffb29b07305209efb12cf3b5ac6032d3a1153/patch/kernel/archive/sunxi-5.4/patch-5.4.46-47.patch#L44 from 24 March but the Armbian runs Linux 5.10.21-sunxi64 so I can't see how it's even relevant... I would like to create a PR to fix this but I'm a bit confused here.

@SecT0uchIf you are able to mount the image on another system then you could make the update in place
 
Something along the lines of (adjust paths to suit your setup)
mkdir /tmp/image mount -v -o offset=4194304 -t ext4 /Path/To/Armbian_21.02.3_Pine64so_focal_current_5.10.21.img /tmp/image dtc -O dtb -o /tmp/image/boot/allwinner/dtb/sun50i-a64-sopine-baseboard.dtb -b 0 sun50i-a64-sopine-baseboard.dts umount /tmp/image  
Then write the image as usual
 
You can mount this from another Linux system. from WSL2 or whatever, as long as you have the dtc command avaialble. 

Dude, see the suggestions by @dippywood the latest version is 21.02.1
The broken package can be held back with
echo "linux-dtb-current-sunbix64 hold" | sudo dpkg --set-selections  

In my stupidity when renaming my temporary files I used the wrong extension - the file previously attached is the DTS.
 
So, here it is, with the proper extension.
 
I have asked for a new brain for my birthday! 
sun50i-a64-sopine-baseboard.dts

So, here's the problem, and its resolution:
 
Comparing the decompiled DTBs for the SOPine for 21.02.1 and 21.02.3, diff gives me 
565d564 < non-removable; 600c599 < max-frequency = <0xbebc200>; --- > max-frequency = <0x8f0d180>; 681a681,682 > phys = <0x2d 0x00>; > phy-names = "usb"; 691a693,694 > phys = <0x2d 0x00>; > phy-names = "usb";  
Working through these show that only the first of these seems to make a difference. The definition for mmc@1c0f000 no longer contained the 'non-removable' entry. 
 
Therefore, inserting "non-removable;" at line 565 of sun50i-a64-sopine-baseboard.dts and compiling to /boot/dtb/allwinner/sun50i-a64-sopine-baseboard.dtb resolves this issue.
 
I can supply a patched focal image if requested.
 
 

Any chance you can share the patched version of the dts.  Will make it easier to add it back into armbian build

I also got the same email, three days ago now ... three failed attempts from London UK, and three from Finland... not even the right continent... needless to say, nice long new password generated.

@Ash Martin @Werner @guidol  You do know that this thread is about a BETTER software than Etcher, right?
And you do know we recommend USBimager OVER Etcher, right?
 
If not, I recommend to read the first couple posts of this thread. Instead of misleading people @Ash Martin  just be quiet. It is not as if you had to comment every post.

I say we go and change the recommendation to USBImager and leave Etcher there as "also usable, but includes spyware"  

I received an email notification same as title of this post 2 days ago.  Just now I changed my password.  But I thought I would make a post to see if anyone else might have been targeted (as I am a Moderator), especially any other Admins or Moderators.
 
I am going to ping everyone I can think of (actually, I simply use the list here) below, but please add anyone else who I miss.
 
@Igor @lanefu @Werner @TonyMac32 @SteeMan @soerenderfor @pfeerick @NicoD @JMCC @balbes150 @_r9

Same as I do

38 views and one like. So at the moment the majority of people is for this change

Mods should be able to apply Solved prefix to topics now.

OK, you are free to do whatever you want. But this is a thread about using my media script with Armbian legacy kernel. If you want to do something different, please don't discuss it here.

I wasn't updating index file until all files are present on all mirrors. Now I pushed index update which will take up to 24-48h (not sure since we are doing 1st time) to update all mirrors. If we would update all at once, people will be receiving errors - file not found - all the time ... updating index from server one, then redirector points to another mirror - where files are not yet - error. Now files are everywhere, but index is somewhere still old.
 
Anyway, things are in automated motion now.

Hello Igor,
since years i seed Armbian torrents but i noticed that i'm running out of space.
My hdd was 248GB till now...
 
Looking for further information and saw in the first post is written 512GB.
Maybe you can add a big ">NOTE!< since Version 20.05.xx you need 512GB free space".
 
Also after you installed transmission by ->Software ->Softy ->Transmission you get asked to seed Armbian torrents.
Here a screen:
 

 
You have to change the number from 80GB to 512GB.
 
Just my thinking about this..
 
Markus

Serial and power mux board is ready for ordering. However before I do so, I need to wait till SD card mux board redesign is complete at least overall idea is “approved”.
 
As previously written the major change is to switch from simple SDI interface towards SDIO one allowing full speed communication with card. This requires 8 pins thus not only mux board but also card adapter tuning. 
Recently idea under consideration is to move SD mux board away from stacking and make it more alike USB Mass Storage device. 

Nice. But one 2x5 connector shall have long legs. To allow interconnection between boards/ stacking of them on top of SBC

One test board from this topic will be installed at this location and another at my desk and elsewhere. We will try to join them.

After test boards come, some more coding has to be done. Also to have better overview over the test process. Currenlty test results looks like this: https://dl.armbian.com/_test-reports/2020-05-03_15.57.22.html Its still more or less a data collection without any proper analysis ...

PCB's are in the mail - now component ordering: can someone double check and update original BOM with latest changes. We want operational boards, right?  

Probably not, but you are welcome to find out.

@JMCC The video is ready.
I don't think it will get too many views. But it can help other frustrated users
Thanks for the help.
 

In case you wonder where you get views:
 

armbian-firmware = minimal blobs that are needed that on-board wireless function + few popular ones = https://github.com/armbian/firmware 
- full = + everything else https://kernel.googlesource.com/pub/scm/linux/kernel/git/firmware/linux-firmware.git
 
You can install one of those, while source package, headers and armbian-config are optional. Also armbian-firmware if your will not be running any wireless.

Kernel = image + dtb package. Those are the core.