The Following User Says Thank You to juiceme For This Useful Post: | ||
![]() |
2013-05-07
, 17:52
|
|
Posts: 592 |
Thanked: 1,603 times |
Joined on Apr 2010
@ Berlin / Germany
|
#22
|
Yep, did that already.
But.once.again.checked.it.out.
Result:
l2fix: no SIP
standard open mode: no SIP
e-yes nitdroid: no SIP
stock Harmattan kernel: working SIP
going back to l2fix.openmode: no SIP
All with ubiboot, but I cannot think of loading 2nd stage kernel being the cause. Or?
One more detail, which make me sure it is not related to my provider but to kernel (and maybe other may check this also): even with an internal FRITZ!Box account behaviour is the same.
![]() |
2013-05-07
, 19:40
|
Posts: 1,067 |
Thanked: 2,383 times |
Joined on Jan 2012
@ Finland
|
#23
|
![]() |
2013-05-08
, 22:12
|
|
Posts: 4,118 |
Thanked: 8,901 times |
Joined on Aug 2010
@ Ruhrgebiet, Germany
|
#24
|
The Following User Says Thank You to peterleinchen For This Useful Post: | ||
![]() |
2013-05-09
, 05:59
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#25
|
Heureka!
Found the culprit. and solved it.
Details after discussion with juiceme ...
![]() |
2013-05-15
, 18:42
|
|
Posts: 592 |
Thanked: 1,603 times |
Joined on Apr 2010
@ Berlin / Germany
|
#26
|
Heureka!
Found the culprit. and solved it.
Details of discussion with juiceme ...
![]() |
2013-05-15
, 20:10
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#27
|
![]() |
2013-05-15
, 20:33
|
|
Posts: 4,118 |
Thanked: 8,901 times |
Joined on Aug 2010
@ Ruhrgebiet, Germany
|
#28
|
![]() |
2013-05-16
, 07:59
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#29
|
@juiceme
Are you going to give us (erm: me) the configurable partition possibility? As I would like to switch to ubiboot-02, but was waiting for some updates. Otherwise I will now go with current revision and modify again to my needs (especially I would like to try to boot Harmattan from /dev/mmcblk0p5 ...
The Following User Says Thank You to juiceme For This Useful Post: | ||
![]() |
2013-05-16
, 08:42
|
Moderator |
Posts: 6,215 |
Thanked: 6,400 times |
Joined on Nov 2011
|
#30
|
The Following 2 Users Say Thank You to thedead1440 For This Useful Post: | ||
When ubiboot (or other kexec-like boot loader) is used, the first stage kernel gets this "good initialization". When the 2nd stage kernl boots, device drivers have been running and HW is not in pristine state any longer. Even as the kernel itself gets a fresh start all the devices remain in the state the previous kernel left them.
So, If you could start the same kernel both with ubiboot and flashed directly, and after it had booted up attempt to use SIP call.
Take /var/log/syslog and dmesg from both cases. Also the ubiboot.dmesg might be good even though I think it's the target kernels logs that are important.
Then, of course debugging the SIP call itself, I am not that familiar with it but indeed you could traceroute the destination, check your iptables etc..