maemo.org - Talk - SailfishOS on Sony Z3 Compact Tablet

maemo.org - Talk (https://talk.maemo.org/index.php)

- SailfishOS (https://talk.maemo.org/forumdisplay.php?f=52)

- - SailfishOS on Sony Z3 Compact Tablet (https://talk.maemo.org/showthread.php?t=97691)

Re: SailfishOS on Sony Z3 Compact Tablet

Finally success...:D

Thank for your helps

Re: SailfishOS on Sony Z3 Compact Tablet

Quote:

Originally Posted by monkeyisland (Post 1553598)

Finally success...:D

Thank for your helps

Ok, so you have a 32gb scorpion_windy? You should be able to extend the data partition if it is only showing up 16gb total.

Re: SailfishOS on Sony Z3 Compact Tablet

okay have you got a how to?
I checked for flashing in recovery. Twrp Partition was roundabout 26 GB.
in system / Memory only 11 from 16GB?

Re: SailfishOS on Sony Z3 Compact Tablet

Quote:

Originally Posted by persmule (Post 1543861)

If another card with the following content in installed, the system can boot successfully:

With further observation, I detect that the content of /run/systemd/boot-status/ (supposed to be filled by /usr/lib/startup/get-initial-bootstate, launched with initial-bootstate.service) will be deleted if a larger SD card is installed during boot time, and autologin@.service will fail due to lack /run/systemd/boot-status/bootstate.

At this point, I can manually restart initial-bootstate.service and start-user-session.service sequentially via SSH to launch the GUI.

Current I cannot trace which program deletes the content of /run/systemd/boot-status/. Does anyone have any idea about how to walkaround this?

Re: SailfishOS on Sony Z3 Compact Tablet

Quote:

Originally Posted by persmule (Post 1555207)

With further observation, I finally and correctly detect that some SD card makes udev units spend more time to initialize. If systemd-udev-settle.service gets launched after initial-bootstate.service because of this, the latter will fail to fill the content of /run/systemd/boot-status/, causing a failed boot.

Currently this race condition can be solved by copying /lib/systemd/system/initial-bootstate.service to /etc/systemd/system/, and making it run after systemd-udev-settle.service, as the diff below shows:

Code:

--- /lib/systemd/system/initial-bootstate.service        2018-12-06 09:45:32.000000000 +0800

+++ /etc/systemd/system/initial-bootstate.service        2019-03-17 00:37:25.421035649 +0800

@@ -6,7 +6,7 @@

 [Unit]

 Description=Get initial bootstate

 DefaultDependencies=no

-After=local-fs.target systemd-tmpfiles-setup.service

+After=local-fs.target systemd-tmpfiles-setup.service systemd-udev-settle.service

 Before=dsme.service

 Conflicts=shutdown.target

 ConditionPathExists=/run/systemd/boot-status

Finally, enable the modified unit by running:

Code:

# systemctl enable initial-bootstate.service

Re: SailfishOS on Sony Z3 Compact Tablet

Interesting! Thanks for investgating, I'll try and get that added to the adaptation

Re: SailfishOS on Sony Z3 Compact Tablet

Hello,

When can we expect the newest version of SFOS on Z3Tablet compact? Is it safe to upgrade now, by using "version --dup"?

Re: SailfishOS on Sony Z3 Compact Tablet

Quote:

Originally Posted by GCR (Post 1555767)

Hello,

When can we expect the newest version of SFOS on Z3Tablet compact? Is it safe to upgrade now, by using "version --dup"?

Still waiting on updated targets on OBS and I haven't tested updating yet so its still squarely in the 'you can if you dare' territory

Re: SailfishOS on Sony Z3 Compact Tablet

OBS Targets have been updated, and i've tested dupping on my scorpion_windy, so it looks like 3.0.2.8 is good to go!