Guest | Posts: n/a | Thanked: 0 times | Joined on
#251
open mode kernel compiled using n9 pr1.2 sources, added some bits to further open up Aegis (compared to docs n950 keernel), namely stuff in credp ptrace access checks
http://depositfiles.com/files/zrpgmfsqb
 
Guest | Posts: n/a | Thanked: 0 times | Joined on
#252
Originally Posted by coderus View Post
you mean using as modem? it's crap. sharing over usb networking will be much better.
that wont work, even with nat in iptables, you will need to compile and copy modules for usbnet also
 
coderus's Avatar
Posts: 6,431 | Thanked: 12,683 times | Joined on Nov 2011 @ Open Mobile Platform, Innopolis, Russia
#253
emm. sdk mode is usbnet already.
 

The Following User Says Thank You to coderus For This Useful Post:
Guest | Posts: n/a | Thanked: 0 times | Joined on
#254
Originally Posted by coderus View Post
emm. sdk mode is usbnet already.
Right, I am wrong

Working on the iptables NAT functionality, compiling kernels, and newest version of iptables. Will se later this evening if it is successfull.
 
javispedro's Avatar
Posts: 2,351 | Thanked: 5,243 times | Joined on Jan 2009 @ Barcelona
#255
Originally Posted by rainisto View Post
you would need to remove modules current-dir linking and make a new one .
There doesn't seem to be a need to do the current-dir link dance.

If one doesn't want to mess with packages (e.g. to ramboot a kernel), it is just necessary to put the proper /lib/modules/$VERSION/ dir and run depmod -a $VERSION before booting it.

(We were doing that to for example test usb host stuff)

EDIT after seeing what happened below: Also, a suggestion if you're building modules is to use a slightly different $VERSION, to avoid collision with the stock kernel. That way you can always boot back to the stock kernel if problems arise.

Last edited by javispedro; 2012-03-13 at 16:15.
 

The Following 3 Users Say Thank You to javispedro For This Useful Post:
Guest | Posts: n/a | Thanked: 0 times | Joined on
#256
Originally Posted by javispedro View Post
There doesn't seem to be a need to do the current-dir link dance.

If one doesn't want to mess with packages (e.g. to ramboot a kernel), it is just necessary to put the proper /lib/modules/$VERSION/ dir and run depmod -a $VERSION before booting it.

(We were doing that to for example test usb host stuff)
Yes, did that. Now, messing with the compiled iptables_nat (a.o) kernel modules. COpied the lot to lib/modules/2.6.32.48-dfl61-20115101/ then depmod -a 2.6.32.48-dfl61-20115101 and reboot
dmesg shows this (for iptables_nat)

Argh! Any ideas ?

Code:
[  239.609741] iptable_nat: Unknown symbol ipt_do_table
[  239.609802] iptable_nat: disagrees about version of symbol nf_register_hooks
[  239.609832] iptable_nat: Unknown symbol nf_register_hooks
[  239.610687] iptable_nat: Unknown symbol nf_conntrack_untracked
[  239.611846] iptable_nat: Unknown symbol nf_nat_packet
[  239.613555] iptable_nat: Unknown symbol __nf_ct_ext_add
[  239.613616] iptable_nat: disagrees about version of symbol register_pernet_subsys
[  239.613647] iptable_nat: Unknown symbol register_pernet_subsys
[  239.614501] iptable_nat: Unknown symbol nf_nat_setup_info
[  239.614532] iptable_nat: disagrees about version of symbol xt_register_target
[  239.614562] iptable_nat: Unknown symbol xt_register_target
[  239.614593] iptable_nat: disagrees about version of symbol nf_unregister_hooks
[  239.614624] iptable_nat: Unknown symbol nf_unregister_hooks
[  239.615447] iptable_nat: Unknown symbol ipt_unregister_table
[  239.615478] iptable_nat: disagrees about version of symbol ip_route_me_harder
[  239.615509] iptable_nat: Unknown symbol ip_route_me_harder
[  239.615539] iptable_nat: disagrees about version of symbol ip_nat_decode_session
[  239.615539] iptable_nat: Unknown symbol ip_nat_decode_session
[  239.616333] iptable_nat: Unknown symbol nf_nat_icmp_reply_translation
[  239.616394] iptable_nat: disagrees about version of symbol unregister_pernet_subsys
[  239.616424] iptable_nat: Unknown symbol unregister_pernet_subsys
[  239.616455] iptable_nat: disagrees about version of symbol ip_xfrm_me_harder
[  239.616485] iptable_nat: Unknown symbol ip_xfrm_me_harder
[  239.616485] iptable_nat: disagrees about version of symbol dst_release
[  239.616516] iptable_nat: Unknown symbol dst_release
[  239.617309] iptable_nat: Unknown symbol need_ipv4_conntrack
[  239.618103] iptable_nat: Unknown symbol ipt_register_table
[  239.618133] iptable_nat: disagrees about version of symbol xt_unregister_target
[  239.618133] iptable_nat: Unknown symbol xt_unregister_target
 
javispedro's Avatar
Posts: 2,351 | Thanked: 5,243 times | Joined on Jan 2009 @ Barcelona
#257
Wow, you used the same kernel version string! I don't want to even imagine what kind of mess your device is on now...

Just use a new, slightly different version string and start afresh. You will avoid these kinds of confusion.

EDIT: Wait. I don't understand what you are doing. You're trying to load modules in the stock kernel or something? My instructions had one last step -- to boot the _new_ kernel!

Last edited by javispedro; 2012-03-13 at 16:16.
 
javispedro's Avatar
Posts: 2,351 | Thanked: 5,243 times | Joined on Jan 2009 @ Barcelona
#258
In any case, we are now going offtopic and a few people have complained that the thread is getting noisy. For generic questions about building kernels, it would be best to open a new thread, and keep this for problems and solutions (if there are any left ) with openmode.
 

The Following User Says Thank You to javispedro For This Useful Post:
Guest | Posts: n/a | Thanked: 0 times | Joined on
#259
Originally Posted by javispedro View Post
Wow, you used the same kernel version string! I don't want to even imagine what kind of mess your device is on now...

Just use a new, slightly different version string and start afresh. You will avoid these kinds of confusion.

EDIT: Wait. I don't understand what you are doing. You're trying to load modules in the stock kernel or something? My instructions had one last step -- to boot the _new_ kernel!
Right, Not the stock kernel, I flashed the open mode kernel, compiled these modules, copied them to /lib/modules/2.6.3.... did the depmod -a 2.6...... reboot

Anyways, I will start a new thread later
 
Posts: 1,048 | Thanked: 979 times | Joined on Mar 2008 @ SF Bay Area
#260
Originally Posted by javispedro View Post
In any case, we are now going offtopic and a few people have complained that the thread is getting noisy. For generic questions about building kernels, it would be best to open a new thread, and keep this for problems and solutions (if there are any left ) with openmode.
Umm I'm sorry if this has been answered already, but has open mode been built for PR 1.2? If yes where is it?
I looked at the first comment and it talks about the op PR1.1 kernel.

I tried wading through the comments in this thread and all the talk about building the kernel made me believe that its still a work in progress.

Can you or jalyst please update the first comment so that noobs like me can get to the open mode PR 1.2?

Thanks!
__________________
qgvdial: Google Voice client. All downloads
qgvtp: Phone integration for the n900 that dials out and sends texts using qgvdial.
mosquitto: message broker that implements the MQ Telemetry Transport protocol version 3.
qgvnotify: Google voice and contacts notifier for diablo and maemo.

If you want to thank me, click the Thanks button.
If you'd like to thank my applications, vote to move them to extras.
 
Reply

Tags
aegis, open kinda

Thread Tools

 
Forum Jump


All times are GMT. The time now is 13:30.