From: Matthias Bethke <matthias@towiski.de>
To: gentoo-mips@lists.gentoo.org
Subject: Re: [gentoo-mips] Qube2 can't load CoLo
Date: Tue, 5 Jun 2007 00:24:54 +0200 [thread overview]
Message-ID: <20070604222453.GC8207@huxley.cablesurf.de> (raw)
In-Reply-To: <464C40DB.408@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2823 bytes --]
Hi Andrew,
on Thursday, 2007-05-17 at 06:47:39, you wrote:
> That sounds suspiciously like you forgot to enable tmpfs support in your
> kernel.
Indeed, that's what it was 8-] It's working just fine now, thanks!
I'm still fighting with the recent 2.6.20 as it doesn't seem to
recognize my disk, but 2.6.17 is fine as well so far. Just dm-crypt is
*very* strange:
| cryptsetup -s256 luksFormat /dev/hda5
|
| WARNING!
| ========
| This will overwrite data on /dev/hda5 irrevocably.
|
| Are you sure? (Type uppercase yes): YES
| Enter LUKS passphrase:
| Verify passphrase:
| Command successful.
| ann ~ # cryptsetup luksDump /dev/hda5
| automatic header conversion from 0.99 to 0.991 triggeredLUKS header information for /dev/hda5
|
| Version: 1
| Cipher name: aes
| Cipher mode: cbc-essiv:sha256
| Hash spec: sha1
| Payload offset: 2056
| MK bits: 256
| MK digest: 0a 1d c0 9b 6a 49 38 d1 f2 44 d4 e6 7e 53 2e 06 54 5d b7 9e
| MK salt: 7b 88 7b 2a 7a 46 5c 97 72 93 3a 13 be db 61 f9
| 9c ca fb 60 fb d3 86 d2 67 aa e9 c5 9a 3b e8 62
| MK iterations: 0
| UUID: d3001762-dede-4634-aaf5-9005c34702b0
|
| Key Slot 0: ENABLED
| Iterations: 11658
| Salt: c9 0c 45 1f b5 83 46 ee 4f 09 10 f9 b6 40 8e ea
| 76 62 e3 f3 ed dc 4f 93 f4 ac 89 91 b0 83 26 55
| Key material offset: 8
| AF stripes: 4000
| Key Slot 1: DISABLED
| Key Slot 2: DISABLED
| Key Slot 3: DISABLED
| Key Slot 4: DISABLED
| Key Slot 5: DISABLED
| Key Slot 6: DISABLED
| Key Slot 7: DISABLED
| ann ~ # cryptsetup luksDump /dev/hda5
| /dev/hda5 is not a LUKS partition
| Command failed.
/dev/hda5 is not mounted or anything, and the second luksDump command
came just a second after the first one. WTF?!
And BTW, HD performance leaves much to be desired---is this normal for
a 250 MHz MIPS? My 68040/40 Amiga did not much worse over its 7 MHz bus:
| ann ~ # dd if=/dev/zero bs=1M of=/dev/hda5
| dd: writing `/dev/hda5': No space left on device
| 1871+0 records in
| 1870+0 records out
| 1961132544 bytes (2.0 GB) copied, 208.289 s, 9.4 MB/s
| ann ~ # hdparm /dev/hda
|
| /dev/hda:
| multcount = 32 (on)
| IO_support = 1 (32-bit)
| unmaskirq = 1 (on)
| using_dma = 1 (on)
| keepsettings = 0 (off)
| readonly = 0 (off)
| readahead = 256 (on)
| geometry = 19846/16/63, sectors = 20005650, start = 0
I was planning to put a partly crypted drive from my HPPA box in there,
and I hoped at about twice the clock it would perform better...
cheers!
Matthias
--
I prefer encrypted and signed messages. KeyID: FAC37665
Fingerprint: 8C16 3F0A A6FC DF0D 19B0 8DEF 48D9 1700 FAC3 7665
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-06-04 22:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 8:56 [gentoo-mips] Qube2 can't load CoLo Matthias Bethke
2007-05-17 6:40 ` Kumba
2007-05-17 11:04 ` Matthias Bethke
2007-05-17 11:47 ` Andrew Gaffney
2007-06-04 22:24 ` Matthias Bethke [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070604222453.GC8207@huxley.cablesurf.de \
--to=matthias@towiski.de \
--cc=gentoo-mips@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox