The Following User Says Thank You to juiceme For This Useful Post: | ||
![]() |
2014-04-13
, 17:22
|
Posts: 290 |
Thanked: 385 times |
Joined on Jan 2012
@ Madrid, Spain
|
#1172
|
![]() |
2014-04-13
, 17:36
|
Posts: 290 |
Thanked: 385 times |
Joined on Jan 2012
@ Madrid, Spain
|
#1173
|
![]() |
2014-04-13
, 21:25
|
|
Posts: 4,118 |
Thanked: 8,901 times |
Joined on Aug 2010
@ Ruhrgebiet, Germany
|
#1174
|
The Following User Says Thank You to peterleinchen For This Useful Post: | ||
![]() |
2014-04-13
, 22:33
|
Posts: 290 |
Thanked: 385 times |
Joined on Jan 2012
@ Madrid, Spain
|
#1175
|
That's even easier, with ubiboot you do not need harmattan at all if you choose not to use it.
You can even have your own partition layout, even delete all partitions and create just one to hold your SailfishOS, to get easy access to full filesystem
Boot OS/kernel selection failed! Please run a maintanance boot
![]() |
2014-04-14
, 07:27
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#1176
|
Only once it showed the text message:
Code:Boot OS/kernel selection failed! Please run a maintanance boot
I'm starting to think there's a problem between bootmanager and actual OS/Kernel loading since it is happening the same with Sailfish and Harmattan, or even a hardware problem...
The weird thing is that I can boot/telnet/tinker into the device with ubiboot (i.e: when connected to usb cable), and all files/partitions, etc. look ok. I've even been able to see the logs/dmesg files generated by ubiboot.
Can this be related to the CAL or mtd NAND mentioned for the first option?
The Following User Says Thank You to juiceme For This Useful Post: | ||
![]() |
2014-04-14
, 15:57
|
Posts: 290 |
Thanked: 385 times |
Joined on Jan 2012
@ Madrid, Spain
|
#1177
|
The Following User Says Thank You to pasko For This Useful Post: | ||
![]() |
2014-04-15
, 05:39
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#1178
|
Hi.
Here's what I did to generate the log files:
1.- Boot the device connected to usb
2.- Disconnect from USB, boot menu appears.
3.- Select Sailfish OS
3.- Black screen..... waith 2 minutes and turn-off via power button
4.- Reconnect USB. Device boots again
5.- Copy logs from mmcblk0p1:/boot/ (Nokia N9 partition)
And this is all
The tar file in the attachment contains both ubiboot.dmesg and ubiboot.log
The Following User Says Thank You to juiceme For This Useful Post: | ||
![]() |
2014-04-15
, 16:17
|
Posts: 290 |
Thanked: 385 times |
Joined on Jan 2012
@ Madrid, Spain
|
#1179
|
I assume here that you have your Harmattan on p2 and SailfisOS on p4, right?
Also, please can you post your ubiboot.conf.
There is one thing also which caugth my eye, which might be relevant or not; The HW revision of your device is 1507 which is fairly rare AFAIK and as I checked my logs, there were previously some reports that some people could not boot 2nd-level kernel with it.
The Following User Says Thank You to pasko For This Useful Post: | ||
![]() |
2014-04-15
, 19:32
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#1180
|
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.
The Following User Says Thank You to juiceme For This Useful Post: | ||
Then ubiboot the broken device, create partitions and restore the data from tarfiles.
There's just one caveat; the dead device must not have broken CAL or boot partitions on the mtd NAND, since there is no way you can safely rewrite those areas under Open Mode.
You can even have your own partition layout, even delete all partitions and create just one to hold your SailfishOS, to get easy access to full filesystem