User talk:Okias

Updated Architecture on Asus Eee Pad

Hi Okias I just recently saw your edit regarding the architecture of the Asusu Eee Pas: https://wiki.postmarketos.org/wiki/ASUS_Eee_Pad_Transformer_(asus-tf101) I just had the same issue with the samsung Galaxy Ace II x: it was armhf but the chip supports armv7. The problem here is that the port ist still for amrhf architecture. So if we just change it in the wiki, it is different in the wiki then how it is for the moment. Maybe it would make sense to add an information for this in the wiki. I am working on changing the port of the Galaxy Ace II x to armv7 and when I have finished I will change the information, so that noone is confused. How do you think about this ?

Someone could be confused, but more confusing is to have armhf in wiki, where should be _real_ device architecture. That device uses old arch, at least someone notice sooner (why am I build for armhf when it's armv7).. IMHO. Not sure about making more clear it uses armhf, but in reality it's armv7 :( haven't find any pretty solution for that.

Definitely see your point. When I am right, at the beginning there was no support of armv7 but for armhf. Anyway, maybe I will open an issue abou that on gitlab.

Installation to userdata on grouper

Hi. I was just wondering how did you manage to find out what partition to dd to? i have been trying to figure it out. thanks

EDIT: never mind figured it out. I will update the wiki

Flashing grouper rootfs to the right device

Hey, (I think) I just found an easier way to find the userdata block device. Instead of running df to check for the /dev/block/mmcblk0pXX path, we can target /dev/block/platform/sdhci-tegra.3/by-name/UDA directly. Learned it from Lineage OS fstab.

Furthermore, the df method doesn't give that info once pmOS is already installed.

Tested it with my grouper, can you test this on your tilapia?:

(twrp grouper) # ls -l /dev/block/platform/sdhci-tegra.3/by-name/
lrwxrwxrwx    1 root     root            20 Aug 18 14:49 APP -> /dev/block/mmcblk0p3
lrwxrwxrwx    1 root     root            20 Aug 18 14:49 CAC -> /dev/block/mmcblk0p4
lrwxrwxrwx    1 root     root            20 Aug 18 14:49 LNX -> /dev/block/mmcblk0p2
lrwxrwxrwx    1 root     root            20 Aug 18 14:49 MDA -> /dev/block/mmcblk0p8
lrwxrwxrwx    1 root     root            20 Aug 18 14:49 MSC -> /dev/block/mmcblk0p5
lrwxrwxrwx    1 root     root            20 Aug 18 14:49 PER -> /dev/block/mmcblk0p7
lrwxrwxrwx    1 root     root            20 Aug 18 14:49 SOS -> /dev/block/mmcblk0p1
lrwxrwxrwx    1 root     root            20 Aug 18 14:49 UDA -> /dev/block/mmcblk0p9
lrwxrwxrwx    1 root     root            20 Aug 18 14:49 USP -> /dev/block/mmcblk0p6

Roboe (talk) 16:36, 18 August 2022 (UTC)

Edit: hmmm, doesn't seem to work for flashing, it fails by 36% (same behaviour in two different tries):

$ adb push /tmp/postmarketOS-export/asus-grouper.img /dev/block/platform/sdhci-tegra.3/by-name/UDA
adb: error: failed to copy '/tmp/postmarketOS-export/asus-grouper.img' to '/dev/block/platform/sdhci-tegra.3/by-name/UDA': remote No space left on device
/tmp/postmarketOS-export/asus-grouper.img: 0 ...ushed. 1.3 MB/s (513084240 bytes in 374.761s)

And, in fact, the partition seems to disappear from /dev/block/platform/sdhci-tegra.3/by-name/. So... well. It's still easier to run adb shell ls -l /dev/block/platform/sdhci-tegra.3/by-name/UDA to get the /dev/block/mmcblk0pXX device, though.

Roboe (talk) 18:26, 18 August 2022 (UTC)