Re: cryptsetup failed to access temporary keystore device

2011-06-04 Thread Alex Hornung
It would be helpful if you could provide some more information,
specifically:

a) dmesg (up to the moment when this happens)
b) kldstat
c) dmsetup ls


Cheers,
Alex

On 03/06/11 22:18, Pierre Abbat wrote:
 # cryptsetup luksFormat /dev/da8s0e
 WARNING!!! Possibly insecure memory, missing mlockall()
 
 WARNING!
 
 This will overwrite data on /dev/da8s0e irrevocably.
 
 Are you sure? (Type uppercase yes): YES
 Enter LUKS passphrase:
 Verify passphrase:
 Failed to access temporary keystore device.
 
 When I dump it, there are no keyslots in use. What's wrong? This is the 
 external drive on the USB cable; I have created a Hammer filesystem on 
 another partition.
 
 Pierre


Re: DragonFlyBSD on Alix board

2011-06-04 Thread Michael Neumann

On 06/03/2011 02:15 PM, Stefano Marinelli wrote:

Hello everybody,
i've an Alix board and it's been running Netbsd for around one year. Never a 
problem. I'd like to try DragonFlyBSD on it, because of hammer, since the board 
is mainly working as a small backup server (using usb disks). It seems I have 
problems,anyway : I can install everything  on the CF on my PC (via usb 
adapter) and I can boot from it without problems. Using qemu, i could also 
check that the serial console is working, trying to boot directly from the CF. 
But when putting the CF on the Alix, it just reaches the boot0 stage, waits 
some seconds for the OS choice, and then tries to go on (I see the char going 
to new line) but stops there. It seems it can't find the boot1 stage. How could 
i solve/debug it? The cf is the same i used for Netbsd, so i am sure it works 
perfectly.
I've also tried to install FreeBSD (using DragonFly BSD's same boot stuff) and 
it works perfectly.


Have you setup the serial console correctly?

I have an alix board myself, and never succeeded in setting up DragonFly 
on it... but I didn't try too long.


Regards,

  Michael


Re: DragonFlyBSD on Alix board

2011-06-04 Thread Stefano Marinelli
 Have you setup the serial console correctly?
 
 I have an alix board myself, and never succeeded in setting up DragonFly on 
 it... but I didn't try too long.

I did, but the problem is that it seems it doesn't get to the boot1 stage. Goes 
to boot0, waits the 10 seconds, select the first option (correct one) and stops 
there.
Same CF on qemu (giving the -nographic output, so console simulated one) works 
perfectly.

Stefano


Re: cryptsetup failed to access temporary keystore device

2011-06-04 Thread Pierre Abbat
On Saturday 04 June 2011 06:37:28 Alex Hornung wrote:
 It would be helpful if you could provide some more information,
 specifically:

 a) dmesg (up to the moment when this happens)
 b) kldstat
 c) dmsetup ls

# dmsetup ls
crypt   (255, 504430599)
# kldstat
Id Refs AddressSize Name
 1   17 0xc010 88a9d4   kernel
 21 0xc098b000 26ce4linux.ko
 31 0xc09b2000 78d04acpi.ko
 41 0xc0a2b000 134ccahci.ko
 51 0xc0a3f000 97cc ehci.ko
 62 0xc0a49000 b9f8 dm.ko
 71 0xcc74d000 a000 linprocfs.ko
 81 0xccf44000 9000 i915.ko
 91 0xccf4d000 13000drm.ko
101 0xcd26 18000dm_target_crypt.ko
111 0xd2e8 12000ext2fs.ko

dmesg is attached.

Pierre

-- 
La sal en el mar es más que en la sangre.
Le sel dans la mer est plus que dans le sang.


dmesg.gz
Description: GNU Zip compressed data


Re: cryptsetup failed to access temporary keystore device

2011-06-04 Thread Alex Hornung
The issue, as far as I can tell, is with the usb stack. The
contigmalloc_map failures in dmesg just after creating the dm volume
probably come from somewhere there.

I'm not sure how to work around this, you could probably try on a
freshly rebooted system or without ehci.

Regards,
Alex


On 04/06/11 18:52, Pierre Abbat wrote:
 On Saturday 04 June 2011 06:37:28 Alex Hornung wrote:
 It would be helpful if you could provide some more information,
 specifically:

 a) dmesg (up to the moment when this happens)
 b) kldstat
 c) dmsetup ls
 
 # dmsetup ls
 crypt   (255, 504430599)
 # kldstat
 Id Refs AddressSize Name
  1   17 0xc010 88a9d4   kernel
  21 0xc098b000 26ce4linux.ko
  31 0xc09b2000 78d04acpi.ko
  41 0xc0a2b000 134ccahci.ko
  51 0xc0a3f000 97cc ehci.ko
  62 0xc0a49000 b9f8 dm.ko
  71 0xcc74d000 a000 linprocfs.ko
  81 0xccf44000 9000 i915.ko
  91 0xccf4d000 13000drm.ko
 101 0xcd26 18000dm_target_crypt.ko
 111 0xd2e8 12000ext2fs.ko
 
 dmesg is attached.
 
 Pierre
 


test: please delete

2011-06-04 Thread Steve