You are not logged in.
After doing a kernel upgrade today (in two of my systems) I noticed this error:
/proc/misc: No entry for device-mapper found
Is device-mapper driver missing from kernel?
Failure to communicate with kernel device-mapper driver.
It would seem as if I'm missing something, however both machines are working fine.
So, the question is: is the "device-mapper" referenced in the error a kernel module? If so, should install it separately or should I just ignore the message?
Thanks.
R
Last edited by ralvez (2007-03-02 00:36:53)
Offline
Same error here. I'm trying to find something on google but I am not able to find anything that is relevant.
Offline
The funny thing is that it could be something missing in our systems or something missing on the kernel we are updating ...
Matter of fact ... I never had the problem before in neither of these systems, which makes me thing that it may be something that did not get added to the kernel because it is not "that important" or some other reason.
Yes, yes ... I admit it, I have no clue how the kernel works
R
Offline
Are you both using lilo, by any chance? A number of users on IRC have mentioned this issue, all lilo users.
Offline
tomk,
You hit the nail in the head!
Both of the systems use lilo as a matter of fact.
C'mon now ... do not keep up on pins and needles... what's the "real" problem? Do you know?
R.
Offline
Yeah, I'm using Lilo
Offline
Sorry ralvez - I don't know what the problem is, and I don't use lilo, so I can't check it out. I'd recommend you post a bug report.
Offline
tomk,
I did inspect one of the boxes that use lilo and compared it to my system which uses grub and both of them have EXACTLY the same content in /proc/misc.
I also have not seen the problem until now, which makes me think it may be related to the kernel upgrade and not the boxes.
Thanks for your reply!
R
Offline
I also have this problem. I might be related to lilo as lilo was also upgraded.
Offline
Same problem here , using lilo.
Offline
I rebooted and nothing happened - meaning, it worked perfectly. Not sure why the error is showing up.
Last edited by graphic23 (2007-03-03 01:33:42)
Offline
same here ignored error system still boots fine.....
Mr Green
Offline
I've got this error too and i've noticed that now hal is not able to mount automatically usb storage devices anymore...
Offline
HAL has not worked for me since forever. I keep having to do a mknod and no one seems to know why.
I am using lilo and got the:
/sbin/lilo
/proc/misc: No entry for device-mapper found
Is device-mapper driver missing from kernel?
Failure to communicate with kernel device-mapper driver.
error.
My Brother MFC210C printer will not print. It shows all is fine, it accepts jobs but no printing. I know it's working because I could scan. Just issues with printing. Tried reinstalling but nothing.
Let's see, new kernel upgrade and lilo and that's when issues started.
Offline
lilo is the cause of /proc/misc: No entry for device-mapper found.
downgraded to previous lilo and error fixed.
still can't get usb printer going which looks like it is kernel related now or cups.
Too many upgrades to keep track of.
Offline
getting this error now:
A print error occurred. Error message received from system:
cupsdoprint -P 'MFC210C' -J '' -H 'localhost:631' -U 'root' -o ' multiple-document-handling=separate-documents-uncollated-copies orientation-requested=3' '/opt/kde/share/apps/kdeprint/testprint.ps' : execution failed with message:
client-error-not-possible
any help??
Offline
If you have the lilo error, solution is here:
http://www.archlinux.org/pipermail/arch … 13739.html
funkmuscle: Please start a new thread for your printer problem.
Offline
Offline
Yep modprobe dm-mod worked for me. I did not reboot as i forgot to lilo at all after the last kernel upgrade which killed a production server for an hour
Still, did figure out a way of getting up to a stage where I could run lilo, involved symlinks and all sorts!
Kind regards
Benedict White
Offline
modprobe dm-mod worked here! Thanks a ton for the tip
Offline
Also have lilo and the device mapper problem I have tried modprobe dm-mod, have upgraded to kde4.1.1-1 and am unable to log-in as root...not allowed...
What to do?
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Doesn't seem to be just a lilo error, as I'm using grub2.
This occurred after upgrade to kernel 3.3.4-2.
After running sudo modprobe dm-mod, then lsmod, dm-mod is nowhere to be found.
sudo grub-mkconfig -o /boot/grub/grub.cfg
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/initramfs-linux.img
/dev/mapper/control: open failed: No such device
Failure to communicate with kernel device-mapper driver.
Check that device-mapper is available in the kernel.
This is from my desktop machine which I didn't reboot before I updated grub2.
My laptop is fine, as I didn't update grub2 before rebooting, the device mapper module loads correctly.
Reverting to previous kernel to see if I can rebuild my grub.cfg correctly!
Update:
Reverted to kernel 3.3.4-1, rebuilt grub.cfg, reinstalled kernel 3.3.4-2, rebooted, dm_mod is loading correctly!
And, I didn't realize how old this thread was, oops!
Last edited by scothane (2012-05-03 20:04:50)
Offline
Hi. The update for grub2 today created a new "grub.cfg". I decided to check this by running grub-mkconfig -o test.cfg:
grub-mkconfig -o test_grub.cfg
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/initramfs-linux.img
Found memtest86+ image: /boot/memtest86+/memtest.bin
/dev/mapper/control: open failed: No such device
Failure to communicate with kernel device-mapper driver.
Check that device-mapper is available in the kernel.
No volume groups found
done
The module "dm-mod" is not available under /lib/modules with standard archlinux-kernel.
Offline
Solved: Reboot
Rationale: This seem to be happen, if grub and kernel are upgraded at same time. In that case, dm-mod can't be loaded.
Anyway I don't need dm-mod.
Offline
This just happened to me: the reason was that I upgraded packages, including the kernel, which removed the dm-mod kernel module from the directory corresponding to the current kernel, and put it into the directory of the newly installed kernel. So the current kernel could not find the module any more.
After reboot, the new kernel looks in the right directory, and everything works.
Offline