← Back to team overview

ac100 team mailing list archive

Re: Anyone missing config options in Precise

 

Am Donnerstag, 1. März 2012, 23:27:43 schrieb ah:
> Hi Marc,
> 
> modprobe is not complaining with tegra-aes, but the timeout message is
> still apearing:
> Error unlocking device: timeout (10s) waiting for cleartext device to
> show up

ok, this seem to come from udisks. Something prevents your crypt device to be 
decrypted. 

> Nothing happens for the drive, a second click on the encpryted symbol
> starts another job (cryptsetup) consuming around 50% of total CPU time.

Are dm-crypt (Crypt Target Support) and relevant crypt algos enabled?

Marc


> 
> best regards
> 
> Andreas
> 
> Am 29.02.2012 07:23, schrieb Marc Dietrich:
> > Hi Andreas,
> > 
> > Am 28.02.2012 21:33, schrieb ah:
> >> Hi there !
> >> 
> >> There seems to be a problem at least at the timeout, using decryption
> >> since my encrypted mobile disk plugged in results in error message
> >> timeout (10s) waiting for there clear text drive to show up after typing
> >> in the password.
> >> (But it works on others systems)
> > 
> > is tegra-aes loaded? The HW crypt is known to be slow. It even
> > sometimes blocked graphics output here.
> > 
> > Gruss
> > 
> > Marc
> > 
> >> Andreas
> >> 
> >> Am 27.02.2012 23:16, schrieb Jani Monoses:
> >>> I have uploaded a new package to Precise containing the changes
> >>> suggested in this thread.
> >>> 
> >>> On Mon, Feb 27, 2012 at 3:24 PM, Marc Dietrich<marvin24@xxxxxx>
> >>> 
> >>> <mailto:marvin24@xxxxxx>  wrote:
> >>>> Am Montag, 27. Februar 2012, 15:10:09 schrieb Jani Monoses:
> >>>>>> well, we can either
> >>>>>> 
> >>>>>>         - revert 11b5fe26f (CHROMIUM: dm: Add support for
> >>>>>>         devices by
> >>>>>> 
> >>>>>> PARTUUID/PARTNROFF), - export the symbol in genhd.c
> >>>>> 
> >>>>> thanks, exporting the symbol did it.
> >>>>> either of these two solutions is fine I think.
> >>>>> So we are missing patches related to this hack? How did it build
> >>>>> for Chromeos?
> >>>> 
> >>>> I guess CHROMEOS uses it build-in, so they never ran into this
> >>>> error (their hw is
> >>>> very specific, so no need to modules I guess).
> >>>> 
> >>>> grep -r CONFIG_BLK_DEV_DM chromeos
> >>>> chromeos/config/base.config:CONFIG_BLK_DEV_DM=y
> >>>> 
> >>>> I also added the"export symbol patch"  to the chromeos-ac100-3.0
> >>>> branch.
> >>>> 
> >>>> Marc
> >>> 
> >>> _______________________________________________
> >>> Mailing list:https://launchpad.net/~ac100
> >>> Post to     :ac100@xxxxxxxxxxxxxxxxxxx
> >>> <mailto:ac100@xxxxxxxxxxxxxxxxxxx>
> >>> Unsubscribe :https://launchpad.net/~ac100
> >>> More help   :https://help.launchpad.net/ListHelp
> >> 
> >> _______________________________________________
> >> Mailing list: https://launchpad.net/~ac100
> >> Post to     : ac100@xxxxxxxxxxxxxxxxxxx
> >> Unsubscribe : https://launchpad.net/~ac100
> >> More help   : https://help.launchpad.net/ListHelp


References