srx

I've spent hours today playing with dtb parameters and whatnot.
So far nothing.
Yes, Android dtb and dtb in this image are different. But I can not just copy-paste it. It is all related and pretty difficult to understand.
 
All I have is dmesg saying that SD card appeared, it is detected. Even partitions are detected and then it dissapears. But why it dissapears?
SDXC card seems to appear, then dissapear, then appear again...
[ 88.606168] mmc0: new high speed SDHC card at address aaaa [ 88.607742] mmcblk0: mmc0:aaaa SP32G 29.7 GiB [ 88.610100] mmcblk0: p1 p2 [ 89.637741] mmc0: card aaaa removed [ 89.731537] mmc0: error -84 whilst initialising SD card [ 90.824315] mmc0: error -84 whilst initialising SD card [ 91.912485] mmc0: error -84 whilst initialising SD card Keeps repeating the last message about once per second. /.../ Another card: [ 441.699628] mmc0: new high speed SDXC card at address aaaa [ 441.701190] mmcblk0: mmc0:aaaa SR64G 59.5 GiB [ 441.706375] mmcblk0: unable to read partition table [ 441.707109] mmc0: card aaaa removed [ 441.709786] udevd[2335]: inotify_add_watch(7, /dev/mmcblk0, 10) failed: No such file or directory [ 441.815132] mmc0: new high speed SDXC card at address aaaa [ 441.816655] mmcblk0: mmc0:aaaa SR64G 59.5 GiB [ 441.819250] mmcblk0: p1 p2 [ 441.890260] blk_update_request: I/O error, dev mmcblk0, sector 124735472 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [ 441.957930] blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [ 442.031386] blk_update_request: I/O error, dev mmcblk0, sector 8 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [ 442.034128] blk_update_request: I/O error, dev mmcblk0, sector 8 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0  
EDIT:
 
The same card/image/kernel that gives endless -84 errors boots just fine in another device.
I just changed dtb to match hardware and started it up in Nexbox A95X (s905x/2GB/8GB). No errors, starts just fine.
 
In A95X F3 Air (S905x3/4GB/32GB) still no luck.
I have no time to do more research at the moment. Maybe I'll try again next weekend.

That is because /boot is on FAT32 filesystem but update wants to make hardlinks and FAT32 does not support it.
For it to work /boot needs to be on ext filesystem but uBoot needs FAT32. So you can not covert it to ext.
 
Other than that it is just as every other Debian/Ubuntu and updating is the same.
 
How I did get around it?
* Make alternate boot directory somewhere else
* copy/rsync contents of /boot into that directory
* umount /boot
* bind mount new directory to /boot
* update kernel
* umount /boot
* mount normal /boot again
* copy/rsync contents of alternate boot to /boot
 
In the end you have updated kernel...
If you read my posts above, you see that I had some problems and I think that something went wrong when I updated kernel last time.
So there is some risk involved.
 
I am not sure if there is any way to make it possible to update kernel without any such workarounds.