pasko | # 1181 | 2014-04-15, 19:59 | Report

Hi.

Thank you again.

Regarding the Sailfish version & extract command:

sailfish.tar.bz2 is a file renamed from file vgrade-jolla-1.0.3.7.tar.bz2 (downloaded from http://images.formeego.org/n950/sailfish/ )

Regards.

P.S: I don't think I can put the device in developer mode: it won't boot Harmattan even after a fresh reflash. Bought it as 'for parts'

---

Last edited by pasko; 2014-04-15 at 20:02.

peterleinchen | # 1182 | 2014-04-15, 20:11 | Report

@pasko
Development (not the developer) equal to R&D mode (done via flasher)

About sailfish OS you should use older release not higher than 1.0.2.5 (r5.1). Higher releases will need (atm) N9-unsupported kernels...

--
but as you bought for spare parts, dont you think too something could be borked up?

---

Last edited by peterleinchen; 2014-04-15 at 20:29.

pasko | # 1183 | 2014-04-15, 20:40 | Report

Hi.

I'm starting to loose my faith. Can't activate R&D mode:

Also, I found a post in this forum from someone I think was the previous owner
I think we're duplicating efforts....
Also tried Sailfish 1.0.2.5 (r5), nothing. Will try now r5.1
Regards.

juiceme | # 1184 | 2014-04-15, 20:59 | Report

Of course, R&D mode is what I meant, mistakenly wrote "developer mode"

juiceme | # 1185 | 2014-04-15, 21:08 | Report

Yeah, it looks like the device is so borked it will not run Harmattan.

However, as long as you can start ubiboot, you can use it with Nemo or SailfishOS.

Regarding your untar command, if I remember correctly the order of the flags matters, you need to put the "double-dash" options after the -f option, like this:

sudo tar -xvzf sailfish.tar.bz2 --numeric-owner -C /media/Alt_OS/

(of course it might depend on implementation/version...)

And moreover, I'd recommend you bunzip2 the file on your linux box, copy the resulting tarfile to forex. your partition 1, unmount partitions, go to ubiboot console, mount partitions 1 & 4, and then untar the archive on device itself with:

tar -xvf /mnt/1/sailfish.tar --numeric-owner -C /mnt/4/

pasko | # 1186 | 2014-04-15, 22:45 | Report

Hi.

I made everything as you specified and it's just the same. I get your point sayin' that if it can boot ubiboot, it should also boot sailfish. However I've seen that the 2nd kernel is loaded via kexec_load().

The point is:
Are there any chances to boot directly from scratch the Sailfish kernel? That way we would eliminate the intermediate kexec_load call and hopefully solve the problem.

Or maybe I can resell it for parts again...

Regards.

pasko | # 1187 | 2014-04-15, 23:02 | Report

Hello again.

I finally managed to put the device in R&D mode.
I made it using the flasher-3.5 tool.

Now it shows a wrench in the screen

pasko | # 1188 | 2014-04-15, 23:17 | Report

Hi.
Now that I have R&D mode active: How do I disable the live-saver watchdogs?

Regards.

juiceme | # 1189 | 2014-04-16, 04:51 | Report

The answer to this is, of course both yes and no, just as to any question really...

Yes, you can easily check whether yuor device can boot directly to SailfishOS, you just need to extract your FS image to partition 2.
It doess not matter what size or how many partitions you have (unless it is at least two...), just extract the tarfile to mmcblk0p2.

The reason for this is that the N9 boot loader starts the kernel with command line parameter telling it to mount the partition 2 as the root filesystem.

The "no" part comes from the thing that even as you can boot SFOS that way, it is not very usable to you as it is
For correct operation of Wayland you need to set up the framebuffer a bit differently than wht is default, or your screen will be messed up.

The device will be fully functional, you will be able for ecample to ssh in and do everything from the console, just the graphical UI will be messed up.

Then there is the correct solution, of course, but it requires a bit more work, and of course it is the most rewarding experience for you, since it will also hopefully teach you new things

To make it fully functional, you need to patch the kernel configuration so that it will use built-in command line instead of the one given by boot loader. This is one of the things ubiboot normally does for you.

Just set the following options:

Code:

CONFIG_CMDLINE_OVERRIDE=y

CONFIG_CMDLINE="init=/sbin/init root=/dev/mmcblk0p2 rootwait rootflags=errors=remount-ro rootfstype=ext4 rw console=ttyS0,115200n8 vram=6m omapfb.vram=0:6M mtdparts=omap2-onenand:1024k(bootloader),2816k@1024k(config),16384k@3840k(kernel),2048k@20224k(log),469248k@22272k(var),32768k@491520k(moslo) gpio=cmt_apeslpx:93:sysfs:output,cmt_en:23:sysfs:init_active:output,cmt_rst_rq:88:sysfs:init_active:output,sleep_ind:92:sysfs:output"

The magic here is the bit saying vram=6m omapfb.vram=0:6M, that will tell kernel to use just one large framebuffer device instead of two smaller ones.
Of course at this point you can also define whatever you want as the rootFS device by changing the parameter root=/dev/mmcblk0p2

Then, just rebuild the kernel and flash it as your regular kernel.
The nice thing here is that you do not need to use scratchbox for building like with Harmattan kernels, you can use for example the regular Linero gnueabi toolchain that you can install in any linux box.

juiceme | # 1190 | 2014-04-16, 04:57 | Report

sudo flasher --set-rd-flags=no-omap-wd,no-ext-wd,no-lifeguard-reset