Ubuntu
devmapper package

Incompatible libdevmapper 1.02.08 (2006-07-17)(compat) and kernel driver

Bug #107813 reported by guidol on 2007-04-19

This bug report is a duplicate of: Bug #105623: udev rules missing from udeb. Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	devmapper (Ubuntu)	New	Undecided	Unassigned

Bug Description

Due to this bug I am unable to install Feisty Fawn on my current system. The text mode installation on the i386 dvd is unable to activate my logical volumes. Here's the error I get from running lvscan manually in a vc:

/proc/misc: No entry for device-mapper found
Is device-mapper driver missing from kernel?
Failure to communicate with kernel device-mapper driver.
/proc/misc: No entry for device-mapper found
Is device-mapper driver missing from kernel?
Failure to communicate with kernel device-mapper driver.
Incompatible libdevmapper 1.02.08 (2006-07-17)(compat) and kernel driver

Revision history for this message

Dan O'Huiginn (daniel-ohuiginn) wrote on 2007-04-19:

might well be related to bug #106696, which seems to be a general problem across all hardware. But just to be sure, could you please include the following information as attachments to the bug:

1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] http://wiki.ubuntu.com/KernelTeamBugPolicies. Thanks in advance!

Revision history for this message

guidol (monk-e) wrote on 2007-04-20:

I have just tried to reinstall. It seems that this bug is related to bug #105623 which was mentioned in the releasenotes. It did indeed take 3 minutes for each LV to be configured. And since I have 5 LVs it took 15 minutes. Marked as duplicate. I did not include the information you requested because I did not think it would be necessary anymore.