You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 Re: Installation » ASCII on RPi1 fails to boot » 2019-08-16 00:41:55
Sounds like a problem when flashing the image. Maybe a corrupted SD?
I'm not sure how similar is a Raspberry Pi B+ compared to the original Raspberry but I had one with Devuan Jessie working. I took the SD card and successfully flashed Devuan Ascii with this image: https://ftp.nluug.nl/pub/os/Linux/distr … pi1.img.xz using this command
xzcat devuan_ascii_2.0.0_armel_raspi1.img.xz | sudo dd of=/dev/sdb
syncThis is the output of neofetch:
..,,;;;::;,.. root@devuan
`':ddd;:,. -----------
`'dPPd:,. OS: Devuan GNU/Linux ascii armv6l
`:b$$b`. Model: Raspberry Pi Model B Plus Rev 1.2
'P$$$d` Kernel: 4.14.44+
.$$$$$` Uptime: 6 minutes
;$$$$$P Packages: 274
.:P$$$$$$` Shell: bash 4.4.12
.,:b$$$$$$$;' CPU: ARMv6-compatible rev 7 (v6l) (1) @ 0.7
.,:dP$$$$$$$$b:' Memory: 17MB / 465MB
.,:;db$$$$$$$$$$Pd'`
,db$$$$$$$$$$$$$$b:'` ████████████████████████
:$$$$$$$$$$$$b:'`
`$$$$$bd:''`
`'''` Maybe tomorrow I could try the same SD on a Raspberry Pi 1 if I can get one.
#2 Re: Installation » Motorola Droid 4 » 2019-08-09 16:50:12
run Devuan with custom kernel
Do you mean with this image?
https://ftp.nluug.nl/pub/os/Linux/distr … id4.img.xz
With "vanilla Devuan" I was talking about it. I guess it has at least some of the drivers for the Droid.
I'll give deboostrap a try (didn't know about it) with that image if that's what you meant.
Thanks
#3 Re: Installation » Motorola Droid 4 » 2019-08-06 14:12:06
Well Maemo Leste is awfully slow on the Droid 4, the interface lags so much is barely usable. Wifi works and a I can connect to it through SSH which is considerable faster than using the terminal emulator on the phone. I will try to get rid of the desktop environment and install I3 insted. Still I would like to know how to run the vanilla Devuan image for this phone (tried to use the same method for Maemo Leste but it didn't work).
Have you considered a Raspberry Pi?
I don't think that would work for me as I would have to carry a Raspberry Pi with a battery, the phone and maybe the router, or forget abouth the phone and have the raspberry with a screen and keyboard: but that would also be too bulky.
#4 Re: Installation » Motorola Droid 4 » 2019-08-03 19:05:05
have you looked at Maemo leste yet?
I haven't and I will try it, however I want vanilla Devuan on the phone to use it as a mini laptop of sorts. I don't care if I can't use it as a phone. That being said if for example Maemo leste let's me install applications from Devuan's repository and generally fool around like I do with my others systems, all the better.
I will try it and report back.
Thanks.
#5 Installation » Motorola Droid 4 » 2019-08-02 16:07:06
- d1str0
- Replies: 6
Hi,
I've bought an used Motorola Droid 4 to use as a very compact system on the go. Mostly for scripting and writing emails. Since I have Devuan on everything else I decided to give it a try on it, but looking at the images for this hardware I realized I have no idea how to install it.
I have dd the image to a SD card, but what's next?
The phone is rooted an currently has Lineage OS.
Thanks.
#6 Re: Other Issues » cryptsetup on embedded » 2019-06-04 19:05:40
Sorry mate.
I really had to have this system up and running so I accepted the "D" (for now) and flashed a SD card with Armbian. I would have to set some time aside for this in the future, or maybe buy another Banana Pi M1 to test it out.
I will update this thread when I have it working.
Thanks for your help.
#7 Re: Other Issues » cryptsetup on embedded » 2019-05-28 23:53:03
No changes in /proc/crypto after loading those modules?
No major difference.
This is what is new:
< name : aes
< driver : aes-arm
< module : aes_arm
< priority : 200
< refcnt : 1
< selftest : passed
< internal : no
< type : cipher
< blocksize : 16
< min keysize : 16
< max keysize : 32#8 Re: Other Issues » cryptsetup on embedded » 2019-05-26 18:28:41
you can check for supported encryption schemes
cat /proc/crypto shows nothing regarding xts. This is the whole output:
name : hmac(sha256)
driver : hmac(sha256-neon)
module : hmac
priority : 250
refcnt : 3
selftest : passed
internal : no
type : shash
blocksize : 64
digestsize : 32
name : sha224
driver : sha224-generic
module : sha256_generic
priority : 0
refcnt : 1
selftest : passed
internal : no
type : shash
blocksize : 64
digestsize : 28
name : sha256
driver : sha256-generic
module : sha256_generic
priority : 0
refcnt : 1
selftest : passed
internal : no
type : shash
blocksize : 64
digestsize : 32
name : sha224
driver : sha224-neon
module : sha256_arm
priority : 250
refcnt : 1
selftest : passed
internal : no
type : shash
blocksize : 64
digestsize : 28
name : sha256
driver : sha256-neon
module : sha256_arm
priority : 250
refcnt : 3
selftest : passed
internal : no
type : shash
blocksize : 64
digestsize : 32
name : sha224
driver : sha224-asm
module : sha256_arm
priority : 150
refcnt : 1
selftest : passed
internal : no
type : shash
blocksize : 64
digestsize : 28
name : sha256
driver : sha256-asm
module : sha256_arm
priority : 150
refcnt : 1
selftest : passed
internal : no
type : shash
blocksize : 64
digestsize : 32
name : hmac(sha1)
driver : hmac(sha1-generic)
module : hmac
priority : 0
refcnt : 3
selftest : passed
internal : no
type : shash
blocksize : 64
digestsize : 20
name : stdrng
driver : sun4i_ss_rng
module : kernel
priority : 300
refcnt : 1
selftest : passed
internal : no
type : rng
seedsize : 24
name : ecb(des3_ede)
driver : ecb-des3-sun4i-ss
module : kernel
priority : 300
refcnt : 1
selftest : passed
internal : no
type : skcipher
async : no
blocksize : 8
min keysize : 24
max keysize : 24
ivsize : 8
chunksize : 8
walksize : 8
name : cbc(des3_ede)
driver : cbc-des3-sun4i-ss
module : kernel
priority : 300
refcnt : 1
selftest : passed
internal : no
type : skcipher
async : no
blocksize : 8
min keysize : 24
max keysize : 24
ivsize : 8
chunksize : 8
walksize : 8
name : ecb(des)
driver : ecb-des-sun4i-ss
module : kernel
priority : 300
refcnt : 1
selftest : passed
internal : no
type : skcipher
async : no
blocksize : 8
min keysize : 8
max keysize : 8
ivsize : 0
chunksize : 8
walksize : 8
name : cbc(des)
driver : cbc-des-sun4i-ss
module : kernel
priority : 300
refcnt : 1
selftest : passed
internal : no
type : skcipher
async : no
blocksize : 8
min keysize : 8
max keysize : 8
ivsize : 8
chunksize : 8
walksize : 8
name : ecb(aes)
driver : ecb-aes-sun4i-ss
module : kernel
priority : 300
refcnt : 1
selftest : passed
internal : no
type : skcipher
async : no
blocksize : 16
min keysize : 16
max keysize : 32
ivsize : 16
chunksize : 16
walksize : 16
name : cbc(aes)
driver : cbc-aes-sun4i-ss
module : kernel
priority : 300
refcnt : 1
selftest : passed
internal : no
type : skcipher
async : no
blocksize : 16
min keysize : 16
max keysize : 32
ivsize : 16
chunksize : 16
walksize : 16
name : sha1
driver : sha1-sun4i-ss
module : kernel
priority : 300
refcnt : 1
selftest : passed
internal : no
type : ahash
async : no
blocksize : 64
digestsize : 20
name : md5
driver : md5-sun4i-ss
module : kernel
priority : 300
refcnt : 1
selftest : passed
internal : no
type : ahash
async : no
blocksize : 64
digestsize : 16
name : crc32
driver : crc32-generic
module : kernel
priority : 100
refcnt : 1
selftest : passed
internal : no
type : shash
blocksize : 1
digestsize : 4
name : crc32c
driver : crc32c-generic
module : kernel
priority : 100
refcnt : 6
selftest : passed
internal : no
type : shash
blocksize : 1
digestsize : 4
name : aes
driver : aes-generic
module : kernel
priority : 100
refcnt : 1
selftest : passed
internal : no
type : cipher
blocksize : 16
min keysize : 16
max keysize : 32
name : des3_ede
driver : des3_ede-generic
module : kernel
priority : 100
refcnt : 1
selftest : passed
internal : no
type : cipher
blocksize : 8
min keysize : 24
max keysize : 24
name : des
driver : des-generic
module : kernel
priority : 100
refcnt : 1
selftest : passed
internal : no
type : cipher
blocksize : 8
min keysize : 8
max keysize : 8
name : sha1
driver : sha1-generic
module : kernel
priority : 0
refcnt : 3
selftest : passed
internal : no
type : shash
blocksize : 64
digestsize : 20
name : md5
driver : md5-generic
module : kernel
priority : 0
refcnt : 1
selftest : passed
internal : no
type : shash
blocksize : 64
digestsize : 16
name : digest_null
driver : digest_null-generic
module : kernel
priority : 0
refcnt : 1
selftest : passed
internal : no
type : shash
blocksize : 1
digestsize : 0
name : compress_null
driver : compress_null-generic
module : kernel
priority : 0
refcnt : 1
selftest : passed
internal : no
type : compression
name : ecb(cipher_null)
driver : ecb-cipher_null
module : kernel
priority : 100
refcnt : 1
selftest : passed
internal : no
type : blkcipher
blocksize : 1
min keysize : 0
max keysize : 0
ivsize : 0
geniv : <default>
name : cipher_null
driver : cipher_null-generic
module : kernel
priority : 0
refcnt : 1
selftest : passed
internal : no
type : cipher
blocksize : 1
min keysize : 0
max keysize : 0
name : rsa
driver : rsa-generic
module : kernel
priority : 100
refcnt : 1
selftest : passed
internal : no
type : akcipherAlso, check whether xts and ecb modules are loaded
Before running cryptsetup luksOpen neither is loaded. After that, only xts is loaded. I can load ecb with modprobe, but cryptsetup gives me the same error.
Did you use a devuan sunxi image for the installation?
Yes I did.
Thanks for your help.
#9 Other Issues » cryptsetup on embedded » 2019-04-22 16:42:17
- d1str0
- Replies: 6
Hi,
I just have successfully installed Devuan on a Banana Pi M1, but while trying to open and mount a encrypted hard drive, I get this message:
root@devuan:~# cryptsetup luksOpen /dev/sda5 asdf
Enter passphrase for /dev/sda5:
device-mapper: reload ioctl on failed: No such file or directory
Failed to setup dm-crypt key mapping for device /dev/sda5.
Check that kernel supports aes-xts-plain64 cipher (check syslog for more info).Syslog says:
Apr 22 16:30:22 devuan kernel: [ 2650.630456] device-mapper: table: 254:0: crypt: Error allocating crypto tfm
Apr 22 16:30:22 devuan kernel: [ 2650.637462] device-mapper: ioctl: error adding target to tableI'm guessing the kernel doesn't support the encryption scheme. What can I do in this case?
Thanks.
Pages: 1
Board footer
