View Single Post
Community Council | Posts: 4,920 | Thanked: 12,867 times | Joined on May 2012 @ Southerrn Finland
#9
Update... It seems that I may not need to build the kernel to fix this.

With help from Hurrian and this posting by javispedro http://talk.maemo.org/showthread.php...81#post1178281
I managed to remove the problematic aegisfs mounts from my device.

However, this seems to be like trying to rip bubblegum out from your hair, as I tried remounting the encrypted home, again a new problem came up. The dreaded "(Transport endpoint is not connected)" hit me again and device stays in reboot loop.

It looks like that some remains of aegis still try to access /home/user, even as the mounts have been removed.

This time it is "devicelockd" that wants to mess up the system:


Oct 16 09:41:26 (2012) devicelockd: aegis_common.cpp(387): ERROR creation of '/home/user' failed (Transport endpoint is not connected)
Oct 16 09:41:26 (2012) devicelockd: aegis_storage.cpp(314): ERROR cannot create directory '/home/user/.aegis/ps/Pe/'
Oct 16 09:41:26 (2012) devicelockd: aegis_storage.cpp(809): ERROR init_storage: cannot bind storage '/home/user/.aegis/ps/Pe/' to file
Oct 16 09:41:26 (2012) devicelockd: aegis_storage.cpp(1250): ERROR get_files: access denied
Oct 16 09:41:26 (2012) devicelockd: aegis_crypto.cpp(1996): ERROR aegis_crypto_decrypt: bb5_fprot_decrypt('AID::com.nokia.maemo.devicelock .') returned -4
Oct 16 09:41:26 (2012) devicelockd: aegis_crypto.cpp(1997): ERROR aegis_crypto_decrypt: BB5 ERROR(-1) lib=-1 rom=0 pa=37
Oct 16 09:41:26 (2012) devicelockd: aegis_crypto.cpp(1996): ERROR aegis_crypto_decrypt: bb5_fprot_decrypt('AID::com.nokia.maemo.devicelock .') returned -4
Oct 16 09:41:26 (2012) devicelockd: aegis_crypto.cpp(1997): ERROR aegis_crypto_decrypt: BB5 ERROR(-1) lib=-1 rom=0 pa=37
Oct 16 09:41:26 (2012) devicelockd: aegis_crypto.cpp(1996): ERROR aegis_crypto_decrypt: bb5_fprot_decrypt('AID::com.nokia.maemo.devicelock .') returned -4
Oct 16 09:41:26 (2012) devicelockd: aegis_crypto.cpp(1997): ERROR aegis_crypto_decrypt: BB5 ERROR(-1) lib=-1 rom=0 pa=37


What is the function of devicelockd?
Can it be safely disabled, from the daemon name I guess it is related to the device locking and that does not work in open mode anyway... From the error messages it looks like the access point it needs to work on is defined statically inside some library and hence cannot easily be modified to point somewhere else.

Here is again syslog of the relevant boot attempt:
http://www.swagman.org/juice/n9_syslog_16.10.2012

Last edited by juiceme; 2012-10-16 at 13:12. Reason: Fixed broken link