maemo.org - Talk

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Alternatives (https://talk.maemo.org/forumdisplay.php?f=36)
-   -   Mer v0.6 released (https://talk.maemo.org/showthread.php?t=26310)

solca 2009-01-20 23:36

Re: Mer v0.6 released
 
Quote:

Originally Posted by fanoush (Post 258928)
I think it was already -l but don't remember for sure. I used two patches for kernel 2.6.22, one adding atags support and second one exporting it in two files in /proc/atags directory. Then I used kexec-tools 1.101 maybe with some additional patches.

Now I have tried it with userspace kexec-nit tool from http://guug.org/nit/kexec/ and found it expects /proc/atags to be a file which is how it is done in recent kernels. I combined previous patches with https://dev.openwrt.org/browser/trun...atch?rev=13613 and now the userspace tool compiled by solca loads the kernel fine and when trying to execute it from fully booted Diablo system (not good idea) it turns screen black and hangs. So I guess it tries to run it but hopefully new kernel just doesn't like current state of hardware. I'll try to run it from initfs so less hardware gets initialized.

Did you try putting your NIT in R&D mode _and_ enable the serial-console flag? It only works this way but it is not ideal, if we could find the cause why it hangs without it...

solca 2009-01-20 23:45

Re: Mer v0.6 released
 
Quote:

Originally Posted by qole (Post 258748)
You'll probably get a response something like this or this.

Well Mer is a combination of Ubuntu and newers Maemo, instead of Ubuntu it could be any other as OpenEmbedded, OpenWRT, etc. I think is easier for Stskeeps base it on Ubuntu because the Debian heritage simpliflyng all Mer package management. IMHO there should be another category for Maemo based alternatives as it doesn't fall in the Debian category...

Too it is important again IMHO a Mer subcategory in alternatives because remember that Freemantle will only work on newer hardware and in the future ppl will like newer releases for N770 and N8x0 devices and _ONLY_ Mer will fill that hole and it could be a mess ppl posting Mer questions in all places /me thinks.

Benson 2009-01-21 00:41

Re: Mer v0.6 released
 
Quote:

Originally Posted by solca (Post 258942)
Well Mer is a combination of Ubuntu and newers Maemo, instead of Ubuntu it could be any other as OpenEmbedded, OpenWRT, etc. I think is easier for Stskeeps base it on Ubuntu because the Debian heritage simpliflyng all Mer package management. IMHO there should be another category for Maemo based alternatives as it doesn't fall in the Debian category...

Too it is important again IMHO a Mer subcategory in alternatives because remember that Freemantle will only work on newer hardware and in the future ppl will like newer releases for N770 and N8x0 devices and _ONLY_ Mer will fill that hole and it could be a mess ppl posting Mer questions in all places /me thinks.

First, this habitual misspelling is getting annoying:
s/Freemantle/Fremantle/

WRT forum trees, I wonder if Mer, being Maemo-based, shouldn't get its own category on a level with OS200x, not a subcategory of alternatives? (Maybe not now, but certainly with 1.0 release?)

Benson 2009-01-21 00:46

Re: Mer v0.6 released
 
Quote:

Originally Posted by bongo (Post 258933)
What about performance? How fast is Mer?

About 400 MHz. :rolleyes:

Since you can't do much with Mer yet, I'm not sure how you expect us to measure performance. I think (I've no measurements!) that Mer is somewhat longer in booting, but I really don't boot my tablet very often. I have never successfully dpkg-buildpackaged anything in OS2008, so I can't compare that.

Stare at the home screen faster? Maybe.

Khertan 2009-01-21 08:26

Re: Mer v0.6 released
 
Hi !

I think really that this really a lost of time !!!
Why don't you use your time to do better things for user ? Like better apps ?

:)

I'm joking ! Thanks for the good work !

I ve many hope in this mer project. I see that there is only a few people doing this good work ! And the project is well managed !

Thanks !!!!!!!

fanoush 2009-01-21 09:06

Re: Mer v0.6 released
 
Quote:

Originally Posted by solca (Post 258939)
Did you try putting your NIT in R&D mode _and_ enable the serial-console flag? It only works this way but it is not ideal, if we could find the cause why it hangs without it...

Did not try. Might be related to power management then. Serial console basically turns any sleep modes off. When it doesn't work, it might help to try something like
- disable dyntick + sleep_while_idle (in linuxrc)
hopefully this might be enough if r&d flags + serial console flags helps but maybe you already tried this?
- do not play with cpufreq governor (also in linuxrc)
- disable unneded drivers in kernel to get as little hardware initialized as possible (cpufreq is not needed at all and messes with various clocks, ...)

Basically we need only stripped down kernel (no matter which version) that could load any main kernel from flash or mmc via kexec (something like LAB (Linux As Bootloader) idea for iPaq). I was thinking about putting such mini kernel before main kernel in kernel partition so it could load the main one transparently as default choice to keep maximum compatibility. The mer/bootmenu install procedure could then read the main one, prepend our small one and put them back. Most probably the small one would need also some initial ramdisk userspace for the menu. But I guess you already though about it too.

solca 2009-01-21 19:31

Re: Mer v0.6 released
 
Quote:

Originally Posted by fanoush (Post 259027)
Did not try. Might be related to power management then. Serial console basically turns any sleep modes off.

Not quite correct, in older kernels it used to not let trigger sleep modes when serials were enabled per the UART clocks, really recent kernels have some bright UART clock management that sleep when serial inactivity is detected so full PM applies.

The kexec hang problem have to do with initialization delay timings, when serial-console is enabled in the R&D flags the new kernel will boot slightily slower but it does the trick and works, without it won't boot just hang.

FYI I was able to kexec a kernel without serial-console flag when I insert printk delays in the kexeced kernel which could be useful to discover what's wrong but I didn't progress further, obviously this is not a solution as one will have to replace distro kernels with kernels with delay mods which is _wrong_.

daperl 2009-01-21 19:49

Re: Mer v0.6 released
 
Quote:

Originally Posted by solca (Post 259134)
FYI I was able to kexec a kernel without serial-console flag when I insert printk delays in the kexeced kernel which could be useful to discover what's wrong but I didn't progress further, obviously this is not a solution as one will have to replace distro kernels with kernels with delay mods which is _wrong_.

I realize this isn't a solution, but can you document what you did here. This is great progress and there's an outside chance that I could help. Thanks.

Stskeeps 2009-01-21 20:59

Re: Mer v0.6 released
 
Quote:

Originally Posted by Khertan (Post 259014)
Hi !

I think really that this really a lost of time !!!
Why don't you use your time to do better things for user ? Like better apps ?

:)

For that good comment from Khertan, ;) :

http://bsd.tspre.org/~stskeeps/mer-homediskfree.png
http://bsd.tspre.org/~stskeeps/mer-homediskfree2.png

fanoush 2009-01-21 21:18

Re: Mer v0.6 released
 
Quote:

Originally Posted by solca (Post 259134)
Not quite correct, in older kernels it used to not let trigger sleep modes when serials were enabled per the UART clocks, really recent kernels have some bright UART clock management that sleep when serial inactivity is detected so full PM applies.

so 2.6.21 from latest Diablo is old or recent regarding this serial code? I guess still the old one. I forgot you run recent kernels so the one doing the kexec for you was not the old one. I'm trying this with 2.6.21.

Quote:

Originally Posted by solca (Post 259134)
FYI I was able to kexec a kernel without serial-console flag when I insert printk delays in the kexeced kernel

I see. What about delay just before jumping to new kernel or what about switching to slower CPU clock before?


All times are GMT. The time now is 10:02.

vBulletin® Version 3.8.8