Nokia & AEGIS open-mode - Page 20 - maemo.org

qole | # 191 | 2012-03-11, 02:31 | Report

I'm so impatient!

I'm glad to hear that the problems are not insurmountable!

What worries me is that I won't be able to do an OTA to 1.2 from 1.1 OM, so I'll have to back up, flash to 1.2, then flash 1.2 OM kernel, then restore from my 1.1 OM backup. What issues might I encounter doing this?

I guess I'll find out... I'll post as always when I do.

javispedro | # 192 | 2012-03-11, 04:46 | Report

Ok, so there's something new I wasn't aware of. There's a flag introduced with PR1.2 that gets set to 1 when you boot a unsigned kernel, and won't be cleared until you completely erase the device. Probably done to close yet another of the Aegis bugs.

(They say this flag is stored in the CAL area, and that the CAL partition is now marked read only somehow. Well, no idea how. It was not protected in previous firmware releases because I know of at least one N9 that was bricked by writing to CAL.)

This means that even if you boot the vainilla or any other kernel once, you will be prevented from going back to closed mode until the next reflash

In any case, a reflash is usually necessary to avoid triggering the certificates problem, so no big deal for those that want to "live" using the open mode kernel.

But it is something to consider if you were not planning a reflash...

Last edited by javispedro; 2012-03-11 at 04:52.

The Following 2 Users Say Thank You to javispedro For This Useful Post:
pelago, YavkatA

nieldk | # 193 | 2012-03-11, 07:02 | Report

good to see you javispedro.
I guess our mistake was compiling the 'usual' Linux way make rm581_defconfig, make. But then again, it was my believe this is what dpkg-buildpackage actually does.
What I, and others, want, besides openmode patch, is.
IPtables NAT support
compatwireless compiled to this kernel, which I believe also requires some Netfilter changes in the kernel (for packet injection)
compile (or try to) the N900 modded drivers, that enables packetinjection.
Will give it a shot with buildpackage.

The Following 2 Users Say Thank You to For This Useful Post:
-Tyler-, danramos

danramos | # 194 | 2012-03-11, 07:28 | Report

Originally Posted by javispedro View Post

This means that even if you boot the vainilla or any other kernel once, you will be prevented from going back to closed mode until the next reflash

You keep using the word "vainilla" repeatedly. Do you mean 'vanilla' (implying a plain and simple flavor of something), or is that a funny word made from the combination of vain and vanilla or something? Genuinely curious about the etymology of 'vainilla' here if it isn't a mistake.

Edit: After saying outloud, "Man! I wish there was a way I could look up information on the Internet." and Googled it, I have come to find out that "vainilla" is a Spanish version of the word "vanilla"... although, to English speakers, "vainilla" in the context of reports of failures to get the open kernel working DOES seem like an appropriately funny combination of 'vain' attempts at a 'vanilla' kernal.

Last edited by danramos; 2012-03-11 at 07:37.

The Following 2 Users Say Thank You to danramos For This Useful Post:
javispedro, joerg_rw

nieldk | # 195 | 2012-03-11, 07:55 | Report

Originally Posted by danramos View Post

You keep using the word "vainilla" repeatedly. Do you mean 'vanilla' (implying a plain and simple flavor of something), or is that a funny word made from the combination of vain and vanilla or something? Genuinely curious about the etymology of 'vainilla' here if it isn't a mistake.

Edit: After saying outloud, "Man! I wish there was a way I could look up information on the Internet." and Googled it, I have come to find out that "vainilla" is a Spanish version of the word "vanilla"... although, to English speakers, "vainilla" in the context of reports of failures to get the open kernel working DOES seem like an appropriately funny combination of 'vain' attempts at a 'vanilla' kernal.

Now THATS funny

cheers!

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

coderus | # 196 | 2012-03-11, 08:33 | Report

okay, dpkg-buildpackage ends, my kernel now inside kernel deb package? just need to unpack it and use in flasher? right? or i can find image outside deb after compilation?

and what about config? which config should i edit?

Last edited by coderus; 2012-03-11 at 09:01.

nieldk | # 197 | 2012-03-11, 11:07 | Report

Originally Posted by coderus View Post

okay, dpkg-buildpackage ends, my kernel now inside kernel deb package? just need to unpack it and use in flasher? right? or i can find image outside deb after compilation?

and what about config? which config should i edit?

If you need to change the .config (eg, to add netfiler stuff or other) the 'easy' way around I would say, is to edit ./kernel/arch/arm/configs/rm581_defconig
Do changes to C-sources directly in the kernel folders
dpkg-buildpackage
and the resulting zImage will be in ./debian/build/kernel/arch/arm/boot/zImage

EDIT: Dont forget to do 'apt-get install fiasco-gen'

Last edited by nieldk; 2012-03-11 at 11:50.

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

coderus | # 198 | 2012-03-11, 12:25 | Report

okay, i see, zImage here, thanks =)
did you tried your patches?

nieldk | # 199 | 2012-03-11, 13:01 | Report

Originally Posted by coderus View Post

okay, i see, zImage here, thanks =)
did you tried your patches?

Been a bit disturbed (wife was out and I home with Kids), but compiling as I write. Testing in an hour or so

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

coderus | # 200 | 2012-03-11, 13:50 | Report

oh, of course, but i will be very thankful to see nat working today. it will help me tomorrow.