dannydj | # 41 | 2010-11-03, 21:15 | Report

no i dont have it. i flashed via pc and flasher-3.5 using same command..

lunat | # 42 | 2010-11-03, 21:17 | Report

@Mentalist Traceur;
i do it with the flasher. but iam curious:
the sync: does it work with the nand? or do you sync for something else i am missing. [to be clear: with flashing i assume the stuff is written to the nand and i think thats what the flasher is for. and sync actually does the same thing(force writing to medium in general not nand). see my questionmarks? ]

besides: i see you flash. and i wonder does the tool somehow ensure the flashed kernel is used? i am used to either have to kexec or reboot for a kernelupdate to be complete. how does it work without that(technically) or am i missing something?.

---

Last edited by lunat; 2010-11-03 at 21:40.

Mentalist Traceur | # 43 | 2010-11-03, 21:41 | Report

I honestly have no idea what the "sync" command does. The way I understand it (amounts to what the wiki told me) it saves the changes after you've ran "flasher --local -f -k [kernel image]".

I suspect the "softupd -s --local" also has something to do with it, but I don't know what exactly it does... Unless it just prints what's going on to stdout...

Anyway, I have no idea how it works or what it works with. You just run "sync" with no options according to the instructions I followed. It's possible the first "flasher" command doesn't actually permanently flash it, or there's some watchdog that will reset it if the sync command isn't ran... *Shrug* Out of my area of expertise.

Radicalz38 | # 44 | 2010-11-03, 21:46 | Report

can matan confirm this please? will surely use the kernel if it really has all the custom modules of titan's kernel + pr 1.3 kernel patches.

sorry I maybe a programmer but I don't know a thing about kernel coding

lunat | # 45 | 2010-11-03, 22:00 | Report

in general this is simple: if you save something linux doesn't write it to disk imidiately but keeps it in memory and writes it later to disk(if mounted async) . sync writes all the stuff that is in memory to disk.

the special case flashing would be interessting.

Mentalist Traceur | # 46 | 2010-11-03, 22:12 | Report

Radicalz: One, there's this, where he says " experimental power40+PR1.3 kernel" - http://talk.maemo.org/showpost.php?p...8&postcount=15 <- in this very thread. And then there's this - where he says (first line): "The files here include source and binary for using kernel-power40 + PR1.3 patches + u-boot on N900." - http://my.svgalib.org/770/n900/u-boot/

Both of those written by Matan, so it's as much a confirmation as can be, probably, unless he reposts.

Lunat, thanks for educating me on the sync thing.

Also: I see Matan edited his instructions to cover the Flasher method instead of Fiasco-Flasher method. Love it when people are responsible and responsive like that.

---

Last edited by Mentalist Traceur; 2010-11-03 at 22:14. Reason: Forgot comment.

lunat | # 47 | 2010-11-03, 22:18 | Report

ok, back to the simple things.
as i understand it you can't get automaticly rid of it and replace it with a normal kernel. you have to do it manually. thats easy to workaround.

but whats with the pakage otherwise. does it need R&D or does it handle the whatchdogs? does it always detect the disk or does it sometimes fail? does it work with any kernel installed on the system or do need to have a special kernel installed(without patching it up)?
any clitches with nolo?

[it is devel and bugs in devel is nothing to complain about i only want to know what works and what doesn't...]

Mentalist Traceur | # 48 | 2010-11-04, 01:14 | Report

Funny enough lunat, I was just PM'ing Matan about an hour ago, and I found out that the sync command isn't actually necessary, because according to him:

In short, assuming you shutdown/reboot normally, the kernel will do the sync anyway - the sync only helps if for some reason the battery is yanked after you flash.

lunat | # 49 | 2010-11-04, 01:34 | Report

so no magic in that. one can't sync often enough!

so simplified its like this:

a) reinstall the maemo kernel(to inform the system it will be there again)
b) now the system thinks it is installed but it isn't so you flash the kernel. with something like flasher --local -f -k kernelwhereever_it_is
c) that flashes the kernel to the nand so everything is fine and you reboot to actually run it with your new(old) kernel.

that would be roughly the same i do, only that i use the flasher on the pc.
thanks a lot!

xopher | # 50 | 2010-11-04, 04:32 | Report

Couple quick questions. Does 0:3 have to be a fat partition? How might one make a boot.scr to point to first partition of mmc? Does the uboot also support boot.txt like the Pandora?

edit:

OK....to make a boot.scr you create a file and place your arguments inside it. For my example I use boot.cmd Inside that file I attempt to direct uboot to partition 3 on the SD card for uImage then to SD card partition 1 with filesystem ext2 rootfs.

This is the command will build your custom boot.scr

I keep failing with my arguments. Can anyone provide a snippet or a source where I can read about the arguments, the format of the file etc? I'm only finding copypasta examples and that doesn't help one understand what they're trying to change until it works properly.

---

Last edited by xopher; 2010-11-04 at 16:05. Reason: additional things to say and such