Reply
Thread Tools
Posts: 697 | Thanked: 137 times | Joined on Jul 2012 @ Hillerød, DK
#921
Originally Posted by peterleinchen View Post




Yep, trapped by some android relict (like me):
Code:
 
~ diff /home/user/preinit.txt  /home/user/preinit_ubiboot.txt
--- /home/user/preinit.txt
+++ /home/user/preinit_ubiboot.txt

-modprobe g_ether
-sleep 1
-/sbin/ifconfig usb0 192.168.2.15 up
-
Just comment these 3 lines and it will be fine (I guess).

Ups! 'developer' in trouble
What you mean 'comment these 3 lines'? from file preinit copy to preinit_ubiboot but where?

Edit: Same place in preinit_ubiboot as in preinit!
__________________
OK

Last edited by Garp; 2013-12-08 at 16:56.
 
peterleinchen's Avatar
Posts: 4,118 | Thanked: 8,901 times | Joined on Aug 2010 @ Ruhrgebiet, Germany
#922
Oops myself. Should have known
By commenting I meant
change the line(s) from
Code:
ifconfig bla bla ...
to
Code:
#ifconfig bla bla ...
in preinit of the non-ubiboot device.
Hereby the code will not be executed.

Possible could be also to copy the original preinit file (10661 bytes) from ubiboot device to the other. But idk if that may break sillyboot or something else.
__________________
SIM-Switcher, automated SIM switching with a Double (Dual) SIM adapter
--
Thank you all for voting me into the Community Council 2014-2016!

Please consider your membership / supporting Maemo e.V. and help to spread this by following/copying this link to your TMO signature:
[MC eV] Maemo Community eV membership application, http://talk.maemo.org/showthread.php?t=94257

editsignature, http://talk.maemo.org/profile.php?do=editsignature
 

The Following User Says Thank You to peterleinchen For This Useful Post:
Posts: 697 | Thanked: 137 times | Joined on Jul 2012 @ Hillerød, DK
#923
Originally Posted by peterleinchen View Post
Oops myself. Should have known
By commenting I meant
change the line(s) from
Code:
ifconfig bla bla ...
to
Code:
#ifconfig bla bla ...
in preinit of the non-ubiboot device.
Hereby the code will not be executed.

Possible could be also to copy the original preinit file (10661 bytes) from ubiboot device to the other. But idk if that may break sillyboot or something else.
Afraid of misunderstandings here!
The problems are in N9 with preinit_ubiboot file not N9 with preinit file!
So changes have to be made in the file named preinit_ubiboot (in N9 with no silliboot file!)?
__________________
OK

Last edited by Garp; 2013-12-08 at 23:49.
 
Community Council | Posts: 4,920 | Thanked: 12,867 times | Joined on May 2012 @ Southerrn Finland
#924
@Garp, there is something I did not think about but it might be quite simple if you indeed have 2 devices;

So, you have one with ubiboot, and one without, right?
And when you say that MfE does not work with ubiboot, you actually mean it does not work in the device with ubiboot, but it works in the other device, right?

Consider then, the problem might not be in ubiboot at all, it might be in the Harmattan installation of the device you have ubiboot on...?

There is an easy way to make sure if this is so;
Just flash the L2-fixed kernel to the device with ubiboot, to bypass your ubiboot setup. When the device boots, check if you still have problems with MfE. If so, then the problem clearly is in Harmattan and not ubiboot. After that you can just flash back the ubiboot kernel and ubiboot will be re-enabled.
 

The Following 2 Users Say Thank You to juiceme For This Useful Post:
Posts: 697 | Thanked: 137 times | Joined on Jul 2012 @ Hillerød, DK
#925
Originally Posted by juiceme View Post
@Garp, there is something I did not think about but it might be quite simple if you indeed have 2 devices;

So, you have one with ubiboot, and one without, right?
And when you say that MfE does not work with ubiboot, you actually mean it does not work in the device with ubiboot, but it works in the other device, right?

Consider then, the problem might not be in ubiboot at all, it might be in the Harmattan installation of the device you have ubiboot on...?

There is an easy way to make sure if this is so;
Just flash the L2-fixed kernel to the device with ubiboot, to bypass your ubiboot setup. When the device boots, check if you still have problems with MfE. If so, then the problem clearly is in Harmattan and not ubiboot. After that you can just flash back the ubiboot kernel and ubiboot will be re-enabled.
You are right nearly all the way but not at last:
The kernel in N9 without ubiboot is 'your' kernel l2fix dmesg | head showing juiceme and the same kernel are in n9 with ubiboot together with the plus kernel BUT same problem in this N9 no matter which kernel i use?
__________________
OK
 
Community Council | Posts: 4,920 | Thanked: 12,867 times | Joined on May 2012 @ Southerrn Finland
#926
Originally Posted by Garp View Post
You are right nearly all the way but not at last:
The kernel in N9 without ubiboot is 'your' kernel l2fix dmesg | head showing juiceme and the same kernel are in n9 with ubiboot together with the plus kernel BUT same problem in this N9 no matter which kernel i use?
Did you try what I suggested?
I believe the problem is not kernel, and not ubiboot, I believe you have problem in your Harmattan OS of the second device.

Just flash it with L2-fixed kernel, and try how it works without ubiboot.

Your ubiboot setup will not disappear, everything will be just as it was when you flash it again with ubiboot kernel.
 

The Following User Says Thank You to juiceme For This Useful Post:
Posts: 697 | Thanked: 137 times | Joined on Jul 2012 @ Hillerød, DK
#927
Originally Posted by juiceme View Post
Did you try what I suggested?
I believe the problem is not kernel, and not ubiboot, I believe you have problem in your Harmattan OS of the second device.

Just flash it with L2-fixed kernel, and try how it works without ubiboot.

Your ubiboot setup will not disappear, everything will be just as it was when you flash it again with ubiboot kernel.
Thanks, I see you are right no connection without Ubiboot and same kernel l2fix (juice)? What then?

And other problem my memory! sorry but the kernel in the other N9 is not l2fix but harmattan pr13@openmode - meaning Nitdroid old kernel!
__________________
OK

Last edited by Garp; 2013-12-09 at 00:54.
 
Community Council | Posts: 4,920 | Thanked: 12,867 times | Joined on May 2012 @ Southerrn Finland
#928
Originally Posted by Garp View Post
Thanks, I see you are right no connection without Ubiboot and same kernel l2fix as in the other N9? What then?
Obviously, you have done some tweak/mod/thing or installed something that conflicts with MfE. It's very difficult to tell from this far, but you have another device where it works, so you can compare them

What I'd do first, is I'd look at the syslog if there's some obvious errors or funny writings when you start up MfE. I'd also try to uninstall/reinstall the SW to see if it makes any difference.

Last resort of course is to reflash the device, that will sure fix it, but it is a tedious work as you always need to install everything there after the flashing.
 

The Following User Says Thank You to juiceme For This Useful Post:
Posts: 697 | Thanked: 137 times | Joined on Jul 2012 @ Hillerød, DK
#929
Originally Posted by juiceme View Post
Obviously, you have done some tweak/mod/thing or installed something that conflicts with MfE. It's very difficult to tell from this far, but you have another device where it works, so you can compare them

What I'd do first, is I'd look at the syslog if there's some obvious errors or funny writings when you start up MfE. I'd also try to uninstall/reinstall the SW to see if it makes any difference.

Last resort of course is to reflash the device, that will sure fix it, but it is a tedious work as you always need to install everything there after the flashing.
Due to my mistake written above could it be the l2fix kernel?
The SW is that the MfE account or..?
__________________
OK

Last edited by Garp; 2013-12-09 at 01:17.
 
Posts: 69 | Thanked: 50 times | Joined on Mar 2012
#930
how do i set ubiboot up to boot sailfish, image extracted to alt_os partition, please and thanks
 
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 09:49.