WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: kernel device-mapper driver  (Read 7352 times)

Offline Onyarian

  • Sr. Member
  • ****
  • Posts: 336
Re: kernel device-mapper driver
« Reply #15 on: December 01, 2013, 01:16:22 PM »
Hi Jason,

now I have had time to make some proves and the results are the same  :(

Pristine installation:
   - download dCore-5.13.11.06.iso
   - in /mnt/sda1/boot/grub/menu.lst
Quote
###dcore50###
title dcore Linux 5.0 prueba
    root (hd0,0)
    kernel /boot/dc5c/vmlinuz quiet loglevel=3 nozswap tce=sda1/dce5c
    initrd /boot/dc5c/dCore.gz

   -download to /mnt/sda1/dce5c/sce/ the files: wireless-3.8.10-tinycore.sce wireless.sce and wifi.sce
   -reboot

in prompt:
   - loadsce wireless-3.8.10-tinycore.sce
   - loadsce wireless.sce
   - loadsce wifi.sce
   - wifi.sh -- select wireless connection
   - importsce -b Xprogs
   - importsce -b flwm_topside
   - importsce -b wbar
   - importsce -b xorg-all
  - sudo vi /mnt/sda1/boot/grub/menu.lst and added:
Quote
###dcore50###
title dcore Linux 5.0 prueba
    root (hd0,0)
    kernel /boot/dc5c/vmlinuz quiet loglevel=3 nozswap tce=sda1/dce5c desktop=flwm_topside icons=wbar loop.max_loop=256
    initrd /boot/dc5c/dCore.gz
   - reboot

Now with the flwm desktop:
importsce raid-dm-3.8.10-tinycore
importsce truecrypt-gtk
importsce truecrypt

loadsce raid-dm-3.8.10-tinycore.sce
loadsce truecrypt-gtk.sce
loadsce truecrypt.sce

truecrypt
   - Create volume
      - create encrypted file container
      - standard TrueCrypt volume
      - volume location: /home/tc/prueba1
      - encryption algorithm: AES
      - encryption hash: SHA-512
      - volumen size: 30 Mb
      - password: word with 20 characters
      - filesystem type: ext2
      - I will mount the volume only on linux
      - format
and HANGS but there is a file prueba1 in /home/tc

making the same but with:
      - filesystem type: fat
      - format
and there is no error and creates a file /home/tc/prueba2

------------------------------------------

To mount one of this encrypted volume:

truecrypt
   - select file: /home/tc/prueba1 or /home/tc/prueba2
   - mount
   - password: word with 20 characters
and HANGS   >:(

Hope you can make the same steps as I did.  :(



Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9661
Re: kernel device-mapper driver
« Reply #16 on: December 01, 2013, 02:57:19 PM »
Ok, I will do my best to reproduce.

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9661
Re: kernel device-mapper driver
« Reply #17 on: December 01, 2013, 04:19:19 PM »
So simple when I started from scratch, i can't believe I missed it before, a dependency issue which is almost always the case when one copy works and another doesn't.

libssh-4 added to truecrypt deps. 

Also, I had forgot to add truecrypt to the truecrypt-gtk dependency list, added now so no need to import both truecrypt and truecrypt-gtk, one or the other will work as planned.

Offline Onyarian

  • Sr. Member
  • ****
  • Posts: 336
Re: kernel device-mapper driver
« Reply #18 on: December 02, 2013, 08:42:02 AM »
Sorry Jason, bad news.

I have deleted the truecrypts sce's and all the downloaded debs to make a newly importsce from truecrypt.

I see now that in the import is truecrypt and libssh-4 downloaded and merged.

But this don't make anything and hangs another time in the same situation, when doing an encrypted volume, and when mounting a volume.

When calling truecrypt from a terminal there is no errors when it hangs.

Can I make some other tests to identify the problem?

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9661
Re: kernel device-mapper driver
« Reply #19 on: December 02, 2013, 08:49:57 AM »
Do you have the mount package installed?  If not it may be busybox's mount.

I will check it out later today or romorrow, since something happened between me seeing it hang and it working after I installed libssh-4.

Offline Onyarian

  • Sr. Member
  • ****
  • Posts: 336
Re: kernel device-mapper driver
« Reply #20 on: December 04, 2013, 09:45:41 AM »
I importsce mount and create mount.sce but it is merged from other previously downloaded debs and nothing is downloaded to create it.

then loadsce mount, raid-dm-3.8.10-tinycore and truecrypt-gtk and nothing else as the previous hang is happen.


Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9661
Re: kernel device-mapper driver
« Reply #21 on: December 04, 2013, 03:44:34 PM »
Ok, it still works flawlessly with my full desktop installed, so I am convinced it is a dependency issue. I just have not had the time to spend to hunt it down.  I will try though as time permits.

Offline Onyarian

  • Sr. Member
  • ****
  • Posts: 336
Re: kernel device-mapper driver
« Reply #22 on: April 02, 2014, 02:18:39 PM »
Hi Jason,

I want to migrate two PC's from TC to dCore, but I need the functionality of truecrypt. Is there anything I can do to find which is the missing dep?
or perhaps I can install your full desktop to prove it.

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9661
Re: kernel device-mapper driver
« Reply #23 on: April 02, 2014, 04:01:00 PM »
I re-imported a file list that had Xprogs, xorg-all, leafpad, icewm, raid-dm-3.8.13-tinycore, and truecrypt.  Truecrypt worked as expected.  attached is my list of installed packages.

Offline Onyarian

  • Sr. Member
  • ****
  • Posts: 336
Re: kernel device-mapper driver
« Reply #24 on: April 04, 2014, 08:49:24 AM »
Thanks Jason, with your imported files it runs OK, now I have soon one PC working on your basis and my configuration. Now I am investigating more in the other PC what causes it.

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9661
Re: kernel device-mapper driver
« Reply #25 on: April 04, 2014, 08:52:06 AM »
Great, glad to hear it is working. 

Offline Onyarian

  • Sr. Member
  • ****
  • Posts: 336
Re: kernel device-mapper driver
« Reply #26 on: April 04, 2014, 10:10:11 AM »
Investigating in the other PC I found that it works when I put raid and truecrypt in onboot after Xprogs and xorg-all (before all other files in onboot).

Finally I got it. Thanks!  ;D