View Single Post
Community Council | Posts: 4,920 | Thanked: 12,867 times | Joined on May 2012 @ Southerrn Finland
#1180
Originally Posted by pasko View Post
Hi.
Yes, the preinit* files had read/exec permission in both cases, and the distribution of OS/partitions is the one you mentioned. I changed all permissions to 777 for both files, just in case :P

In one of the attempts I made, the message of 'Maintenance boot' was displayed, afterwards I saw some modified files (depmod,insmod, modprobe, lsmod and others according to their modification/access dates) at /sbin in Sailfish partition. I was trying something I've read Coderus wrote: tapping several times after selecting the sailfish icon.

Regarding the HW revision I think there's not much to add, but would explain the fact that none of the OSs is booting in 2nd stage (i.e: after ubiboot kernel)

The ubiboot.conf file I think is the original one, without modifications.

Regards.
Okay, as you have the default installation those things should be in order.

Basically there are 2 different cases here, booting Harmattan and booting SailfishOS.

Booting Harmattan is usually the trickier one, even Harmattan in Open Mode has some ties to the device's securety framework and problems accessing either the chipset internal functions or the mtd CAL partition will prevent booting. Also there might be something with the HW version that affect things.
One thing you could try, is to set the device in developer mode and disable the life-saver watchdogs. In some cases that has helped.

Booting SailfishOS should be easier in theory. At least booting Nemo works in cases that Harmattan won't boot and Sailfish base is built on top of Nemo.
Now, problems with Nemo/Sailfish usually are caused by incorrect extraction of the FS tarfile, which needs to be done with the --numeric-owner option to recreate the correct permissions to all files.

What is your SailfishOs version, and how did you extract it to partition 4?
 

The Following User Says Thank You to juiceme For This Useful Post: