*** This bug is a duplicate of bug 106696 ***
https://bugs.launchpad.net/bugs/106696
** This bug has been marked a duplicate of bug 106696
Failure to auto-load dm-mod kernel module
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Hi
I just experienced the same issue. Had to run modprobe dm_mod to
resolve.
# cat /proc/version
Linux version 2.6.24-16-generic (bui...@palmer) (gcc version 4.2.3
(Ubuntu 4.2.3-2ubuntu7)) #1 SMP Thu Apr 10 13:23:42 UTC 2008
# cat /etc/issue
Ubuntu 8.04.2 \n \l
Hope this info helps.
--
gutsy
** Changed in: devmapper (Ubuntu)
Importance: Undecided => Low
Status: New => Confirmed
--
gutsy: libdevmapper 1.02.20 and kernel driver incompatible
https://bugs.launchpad.net/bugs/178889
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Same issue in Hardy amd64
--
gutsy: libdevmapper 1.02.20 and kernel driver incompatible
https://bugs.launchpad.net/bugs/178889
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
I had the same problem and 'modprobe dm_mod' fixed it
--
gutsy: libdevmapper 1.02.20 and kernel driver incompatible
https://bugs.launchpad.net/bugs/178889
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
I'm had the same problem. It seems like dm_mod isn't getting autoloaded
and if it's not loaded, then cryptsetup reports an incompatible
libdevmaper.
Trying doing "modprobe dm_mod" first and see if hte problem doesn't go
away?
--
gutsy: libdevmapper 1.02.20 and kernel driver incompatible
https:/
Hi!
What version of Ubuntu are you usiing? Hardy?
Thanks
--
gutsy: libdevmapper 1.02.20 and kernel driver incompatible
https://bugs.launchpad.net/bugs/178889
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
Hmm, saw what looks like it could have been a fix in
http://ubuntuforums.org/showthread.php?p=4038422#post4038422 that apparently
worked for somebody. When I tried the patch the result was:
sudo cryptmount --prepare secret
[sudo] password for gary:
enter password for target "secret":
device-