09-30-2020, 10:34 AM
(This post was last modified: 10-13-2020, 02:17 PM by wdt.
Edit Reason: correction
)
>I'm now pretty sure it's not software at all but the mis-positioned magnet problem
well, it is quite easy to test, JUST DON"T CLOSE LID
That is, when you are about to go to sleep, suspend computer, close lid HALFWAY,
check in morning
The magnet has an effect when lid is about 2" from closed, and when all the way closed, re-awakes
(mine, at least)
echo fe330000.sdhci >/sys/bus/platform/drivers/sdhci-arasan/unbind ,,,(with emmc switched on again, of course)
lsblk |grep boot
If this last gives 2 (or 3) lines, there is your emmc, even tells you which mmcblkX, (one with boot0, boot1)
then new/different uboot OR blank
--edit--
There is a possibility that it is using /boot from emmc and / from SD,, this is quite bad, MUST be fixed
/boot should be on SD if booting from SD, comes from identical fs labels, confuses kernel
With manjaro, usually blk1 is SD,, blk2 is emmc
well, it is quite easy to test, JUST DON"T CLOSE LID
That is, when you are about to go to sleep, suspend computer, close lid HALFWAY,
check in morning
The magnet has an effect when lid is about 2" from closed, and when all the way closed, re-awakes
(mine, at least)
echo fe330000.sdhci >/sys/bus/platform/drivers/sdhci-arasan/unbind ,,,(with emmc switched on again, of course)
lsblk |grep boot
If this last gives 2 (or 3) lines, there is your emmc, even tells you which mmcblkX, (one with boot0, boot1)
then new/different uboot OR blank
--edit--
There is a possibility that it is using /boot from emmc and / from SD,, this is quite bad, MUST be fixed
/boot should be on SD if booting from SD, comes from identical fs labels, confuses kernel
With manjaro, usually blk1 is SD,, blk2 is emmc