View Single Post
Community Council | Posts: 4,920 | Thanked: 12,867 times | Joined on May 2012 @ Southerrn Finland
#3
Originally Posted by plolic View Post
Is the boot process looking for a different startup file with the latest version?
AFAIK all prepared SFOS ot Nemo filesystem images have the bootable kernel in /boot/bzImage (which then again is a symlink to the actual kernel in same directory)

You can check if it exists correctly for example by mounting your ALT_OS directory in harmattan and looking there:
~ # mount /dev/mmcblk0p4 /mnt/
~ # ls -la /mnt/boot/
total 9584
drwxr-xr-x 2 root root 4096 Dec 28 2013 .
drwxr-xr-x 21 root root 4096 Dec 28 2013 ..
lrwxrwxrwx 1 root root 33 Jan 1 1970 System.map -> System.map-2.6.32.20130129.1-n950
-rw------- 1 root root 1294961 Nov 21 2013 System.map-2.6.32.20130129.1-n950
lrwxrwxrwx 1 root root 30 Jan 1 1970 bzImage -> vmlinuz-2.6.32.20130129.1-n950
lrwxrwxrwx 1 root root 30 Jan 1 1970 cmdline -> cmdline-2.6.32.20130129.1-n950
-rw-r--r-- 1 root root 54 Nov 21 2013 cmdline-2.6.32.20130129.1-n950
-rw-r--r-- 1 root root 56241 Nov 21 2013 config-2.6.32.20130129.1-n950
-rwxr-xr-x 1 root root 2823888 Nov 21 2013 vmlinuz-2.6.32.20130129.1-n950



Originally Posted by plolic View Post
What does the command "mount /dev/mmcblk0p4" mean and does it create a partition at a particular size...maybe too small?
The mount command does not create any partitions, it just makes a pre-created partition available to you at certain location.
If you have created your ALT_OS partition (mmcblk0p4) using the default splitter script on the Moslo or ubiboot repair console, then the size of the partition is 4GB which is well suitable for SFOS installation.

I rather suspect something went wrong for you when you extracted the FS image to your partition.
 

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