MAVr

Hello everyone!
 
I would like to express my deepest gratitude to Dieter for the great work he has done to find out the cause of the problem.
I had a similar problem. And I confirm that in the above way you can revive the work of BananaPi Pro
 
So:
1) you need to remove the MicroSD and in any Linux system (for example, by booting from Ubuntu-LifeCD or other), edit the file /boot/armbianEnv.txt, specifying the correct UUID of our MicroSD to the rootdev parameter. It is better not to remove the value for loading from HDD/SDD, but to comment it out
For example:
##/mmcblk0/mmcblk0p1 #rootdev=UUID=2027b0d6-b106-4f62-b4ea-6280cdcf0a23 ##/dev/sda1 rootdev=UUID=8204db71-090a-44b5-84cb-dd55d9110fed 2) insert MicroSD back and start. We enter the system and launch the command "armbian-config", select "Systems" -> "DTC" from the menu.
2a) DO NOT REPEAT. First I tried in the "ahci-5v" section to change the ""status =" disabled "" parameter to ""status ="enabled "". Rebooted but it didn't help. Returned the parameter back.
2b) look for the "sata@1c18000" section and delete the line "target-supply = <0x24>;" in it. To the request to save the answers "Y", to the request to overwrite the file - we also confirm "Y" and reboot.
3) After rebooting, the "lsblk" command will already show our HDD/SSD available.
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT sda           8:0    0  55,9G  0 disk └─sda1        8:1    0  55,9G  0 part / mmcblk0     179:0    0   7,5G  0 disk └─mmcblk0p1 179:1    0   7,4G  0 part /media/mmcboot zram0       254:0    0 483,7M  0 disk [SWAP] 4) Again edit the file /boot/armbianEnv.txt, uncommenting the "rootdev" parameter for the UUID of our HDD/SDD and commenting it out for MicroSD.
5) Reboot and enjoy again the work of our BananaPi Pro. When updating the kernel, you will have to repeat everything again. Maybe if, after the update, you immediately edit the dtc and then reboot, then the problem will not be reproduced.
 
I express my gratitude to everyone who unsubscribed in this thread - thanks to you, I was able not to freak out and delete all my data, but to restore the performance of my system. I think it would be a good idea to solidify this topic so that other colleagues can quickly find it and restore their devices to work. But I would like the developers to fix this. Thank you for a good product, albeit with problems.
 
Good luck to all!

Hello everyone!
 
I would like to express my deepest gratitude to Dieter for the great work he has done to find out the cause of the problem.
I had a similar problem. And I confirm that in the above way you can revive the work of BananaPi Pro
 
So:
1) you need to remove the MicroSD and in any Linux system (for example, by booting from Ubuntu-LifeCD or other), edit the file /boot/armbianEnv.txt, specifying the correct UUID of our MicroSD to the rootdev parameter. It is better not to remove the value for loading from HDD/SDD, but to comment it out
For example:
##/mmcblk0/mmcblk0p1 #rootdev=UUID=2027b0d6-b106-4f62-b4ea-6280cdcf0a23 ##/dev/sda1 rootdev=UUID=8204db71-090a-44b5-84cb-dd55d9110fed 2) insert MicroSD back and start. We enter the system and launch the command "armbian-config", select "Systems" -> "DTC" from the menu.
2a) DO NOT REPEAT. First I tried in the "ahci-5v" section to change the ""status =" disabled "" parameter to ""status ="enabled "". Rebooted but it didn't help. Returned the parameter back.
2b) look for the "sata@1c18000" section and delete the line "target-supply = <0x24>;" in it. To the request to save the answers "Y", to the request to overwrite the file - we also confirm "Y" and reboot.
3) After rebooting, the "lsblk" command will already show our HDD/SSD available.
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT sda           8:0    0  55,9G  0 disk └─sda1        8:1    0  55,9G  0 part / mmcblk0     179:0    0   7,5G  0 disk └─mmcblk0p1 179:1    0   7,4G  0 part /media/mmcboot zram0       254:0    0 483,7M  0 disk [SWAP] 4) Again edit the file /boot/armbianEnv.txt, uncommenting the "rootdev" parameter for the UUID of our HDD/SDD and commenting it out for MicroSD.
5) Reboot and enjoy again the work of our BananaPi Pro. When updating the kernel, you will have to repeat everything again. Maybe if, after the update, you immediately edit the dtc and then reboot, then the problem will not be reproduced.
 
I express my gratitude to everyone who unsubscribed in this thread - thanks to you, I was able not to freak out and delete all my data, but to restore the performance of my system. I think it would be a good idea to solidify this topic so that other colleagues can quickly find it and restore their devices to work. But I would like the developers to fix this. Thank you for a good product, albeit with problems.
 
Good luck to all!

Hello everyone!
 
I would like to express my deepest gratitude to Dieter for the great work he has done to find out the cause of the problem.
I had a similar problem. And I confirm that in the above way you can revive the work of BananaPi Pro
 
So:
1) you need to remove the MicroSD and in any Linux system (for example, by booting from Ubuntu-LifeCD or other), edit the file /boot/armbianEnv.txt, specifying the correct UUID of our MicroSD to the rootdev parameter. It is better not to remove the value for loading from HDD/SDD, but to comment it out
For example:
##/mmcblk0/mmcblk0p1 #rootdev=UUID=2027b0d6-b106-4f62-b4ea-6280cdcf0a23 ##/dev/sda1 rootdev=UUID=8204db71-090a-44b5-84cb-dd55d9110fed 2) insert MicroSD back and start. We enter the system and launch the command "armbian-config", select "Systems" -> "DTC" from the menu.
2a) DO NOT REPEAT. First I tried in the "ahci-5v" section to change the ""status =" disabled "" parameter to ""status ="enabled "". Rebooted but it didn't help. Returned the parameter back.
2b) look for the "sata@1c18000" section and delete the line "target-supply = <0x24>;" in it. To the request to save the answers "Y", to the request to overwrite the file - we also confirm "Y" and reboot.
3) After rebooting, the "lsblk" command will already show our HDD/SSD available.
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT sda           8:0    0  55,9G  0 disk └─sda1        8:1    0  55,9G  0 part / mmcblk0     179:0    0   7,5G  0 disk └─mmcblk0p1 179:1    0   7,4G  0 part /media/mmcboot zram0       254:0    0 483,7M  0 disk [SWAP] 4) Again edit the file /boot/armbianEnv.txt, uncommenting the "rootdev" parameter for the UUID of our HDD/SDD and commenting it out for MicroSD.
5) Reboot and enjoy again the work of our BananaPi Pro. When updating the kernel, you will have to repeat everything again. Maybe if, after the update, you immediately edit the dtc and then reboot, then the problem will not be reproduced.
 
I express my gratitude to everyone who unsubscribed in this thread - thanks to you, I was able not to freak out and delete all my data, but to restore the performance of my system. I think it would be a good idea to solidify this topic so that other colleagues can quickly find it and restore their devices to work. But I would like the developers to fix this. Thank you for a good product, albeit with problems.
 
Good luck to all!

Hello everyone!
 
I would like to express my deepest gratitude to Dieter for the great work he has done to find out the cause of the problem.
I had a similar problem. And I confirm that in the above way you can revive the work of BananaPi Pro
 
So:
1) you need to remove the MicroSD and in any Linux system (for example, by booting from Ubuntu-LifeCD or other), edit the file /boot/armbianEnv.txt, specifying the correct UUID of our MicroSD to the rootdev parameter. It is better not to remove the value for loading from HDD/SDD, but to comment it out
For example:
##/mmcblk0/mmcblk0p1 #rootdev=UUID=2027b0d6-b106-4f62-b4ea-6280cdcf0a23 ##/dev/sda1 rootdev=UUID=8204db71-090a-44b5-84cb-dd55d9110fed 2) insert MicroSD back and start. We enter the system and launch the command "armbian-config", select "Systems" -> "DTC" from the menu.
2a) DO NOT REPEAT. First I tried in the "ahci-5v" section to change the ""status =" disabled "" parameter to ""status ="enabled "". Rebooted but it didn't help. Returned the parameter back.
2b) look for the "sata@1c18000" section and delete the line "target-supply = <0x24>;" in it. To the request to save the answers "Y", to the request to overwrite the file - we also confirm "Y" and reboot.
3) After rebooting, the "lsblk" command will already show our HDD/SSD available.
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT sda           8:0    0  55,9G  0 disk └─sda1        8:1    0  55,9G  0 part / mmcblk0     179:0    0   7,5G  0 disk └─mmcblk0p1 179:1    0   7,4G  0 part /media/mmcboot zram0       254:0    0 483,7M  0 disk [SWAP] 4) Again edit the file /boot/armbianEnv.txt, uncommenting the "rootdev" parameter for the UUID of our HDD/SDD and commenting it out for MicroSD.
5) Reboot and enjoy again the work of our BananaPi Pro. When updating the kernel, you will have to repeat everything again. Maybe if, after the update, you immediately edit the dtc and then reboot, then the problem will not be reproduced.
 
I express my gratitude to everyone who unsubscribed in this thread - thanks to you, I was able not to freak out and delete all my data, but to restore the performance of my system. I think it would be a good idea to solidify this topic so that other colleagues can quickly find it and restore their devices to work. But I would like the developers to fix this. Thank you for a good product, albeit with problems.
 
Good luck to all!

Hello everyone!
 
I would like to express my deepest gratitude to Dieter for the great work he has done to find out the cause of the problem.
I had a similar problem. And I confirm that in the above way you can revive the work of BananaPi Pro
 
So:
1) you need to remove the MicroSD and in any Linux system (for example, by booting from Ubuntu-LifeCD or other), edit the file /boot/armbianEnv.txt, specifying the correct UUID of our MicroSD to the rootdev parameter. It is better not to remove the value for loading from HDD/SDD, but to comment it out
For example:
##/mmcblk0/mmcblk0p1 #rootdev=UUID=2027b0d6-b106-4f62-b4ea-6280cdcf0a23 ##/dev/sda1 rootdev=UUID=8204db71-090a-44b5-84cb-dd55d9110fed 2) insert MicroSD back and start. We enter the system and launch the command "armbian-config", select "Systems" -> "DTC" from the menu.
2a) DO NOT REPEAT. First I tried in the "ahci-5v" section to change the ""status =" disabled "" parameter to ""status ="enabled "". Rebooted but it didn't help. Returned the parameter back.
2b) look for the "sata@1c18000" section and delete the line "target-supply = <0x24>;" in it. To the request to save the answers "Y", to the request to overwrite the file - we also confirm "Y" and reboot.
3) After rebooting, the "lsblk" command will already show our HDD/SSD available.
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT sda           8:0    0  55,9G  0 disk └─sda1        8:1    0  55,9G  0 part / mmcblk0     179:0    0   7,5G  0 disk └─mmcblk0p1 179:1    0   7,4G  0 part /media/mmcboot zram0       254:0    0 483,7M  0 disk [SWAP] 4) Again edit the file /boot/armbianEnv.txt, uncommenting the "rootdev" parameter for the UUID of our HDD/SDD and commenting it out for MicroSD.
5) Reboot and enjoy again the work of our BananaPi Pro. When updating the kernel, you will have to repeat everything again. Maybe if, after the update, you immediately edit the dtc and then reboot, then the problem will not be reproduced.
 
I express my gratitude to everyone who unsubscribed in this thread - thanks to you, I was able not to freak out and delete all my data, but to restore the performance of my system. I think it would be a good idea to solidify this topic so that other colleagues can quickly find it and restore their devices to work. But I would like the developers to fix this. Thank you for a good product, albeit with problems.
 
Good luck to all!

Confirm that a fresh install of Armbian_21.08.3_Bananapipro_focal_current_5.10.60 does not get a visible sata connection (BananaPi Pro).
This cmd line followed by a reboot enables the sata (same is in first post, just all in one line).
apt install linux-image-current-sunxi=21.05.6 armbian-firmware=21.05.8 linux-dtb-current-sunxi=21.05.6  
Dieter
 
Hi again, 
more findings:
It is sufficient to downgrade the device tree:
apt install linux-dtb-current-sunxi=21.05.6 I had compared the kernel config (find current config in /proc/config.gz), no changes regarding sata. Only a very few changes, mostly adding drivers as module.
 
So far I had no time to compare the device tree yet. Someone wrote he did that but did not find relevant changes. Well, I hope he was wrong :-).
 
 
BTW: the next line will reverse the changes.
apt full-upgrade  
PS: Running a kernel with a different device tree is not recommend, I did it only to hunt down the issue a bit.
 
Dieter
 
And more info:
Some people wrote that these events show up in the syslog and searched in that direction.
ahci-sunxi 1c18000.sata: supply ahci not found, using dummy regulator ahci-sunxi 1c18000.sata: supply phy not found, using dummy regulator ahci-sunxi 1c18000.sata: supply target not found, using dummy regulator Since I was convinced these messages are normal, I double checked with working sata and they are there as well.
 
Dieter
 
Decompiled the DT, then compared.
This is a difference regarding sata:
sata@1c18000 { clocks = <0x02 0x31 0x02 0x7a>; compatible = "allwinner,sun4i-a10-ahci"; interrupts = <0x00 0x38 0x04>; phandle = <0x5f>; reg = <0x1c18000 0x1000>; status = "okay"; target-supply = <0x24>; }; This line is new in latest version:
target-supply = <0x24>; It is not unlikely that this line causes the issue.
The 0x24 points to item ahci-5v and that is disabled.
ahci-5v { compatible = "regulator-fixed"; enable-active-high; gpio = <0x19 0x01 0x08 0x00>; phandle = <0x24>; regulator-boot-on; regulator-max-microvolt = <0x4c4b40>; regulator-min-microvolt = <0x4c4b40>; regulator-name = "ahci-5v"; status = "disabled"; }; No change for this item between the versions.
I do not know how to enable it (yet). Any ideas ?
 
This is how I extracted the DT and decompiled:
copy "/sys/firmware/devicetree" to my worksation running "dtc --in-format fs base --out-format dts --out dt.dts --symbols --auto-alias --phandle both  --sort" use meld to compare both versions Dieter