This bug was fixed in the package drbd8 - 2:8.3.7-1ubuntu2.1

---------------
drbd8 (2:8.3.7-1ubuntu2.1) lucid-proposed; urgency=low

  * Use KDIR instead of KERNELDIR variable for headers path
    - thanks Gaëtan Ferez for debugging
    - (LP: #562832)
 -- Ante Karamatic <iv...@ubuntu.com>   Mon, 19 May 2010 09:22:17 +0200

** Changed in: drbd8 (Ubuntu Lucid)
       Status: Fix Committed => Fix Released

-- 
[SRU] module drbd8 update kernel from 2.6.32-16 to 2.6.32-20
https://bugs.launchpad.net/bugs/562832
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to drbd8 in ubuntu.

Status in “dkms” package in Ubuntu: Confirmed
Status in “drbd8” package in Ubuntu: Fix Released
Status in “dkms” source package in Lucid: Won't Fix
Status in “drbd8” source package in Lucid: Fix Released

Bug description:
I have installed drbd8-utils on Ubuntu Lucid 10.04 beta 1.
 After updating the kernel to 2.6.32-20-generic, the module drbd can't be 
loaded.
I have an error during the load :

FATAL: Error inserting drbd 
(/lib/modules/2.6.32-20-generic/updates/dkms/drbd.ko): Invalid module format

Dmesg : 

[  190.376039] drbd: disagrees about version of symbol module_layout

When i update the kernel, i can just see in the log :

ubuntu-laptop dkms_autoinstaller: drbd8 (8.3.7): Installing module on kernel 
2.6.32-20-generic.

I think that the problem results from dkms program

ProblemType: Bug
Architecture: i386
Date: Wed Apr 14 09:47:41 2010
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
Package: drbd8-utils 2:8.3.7-1ubuntu1
ProcEnviron:
 LANG=fr_FR.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-20.30-generic 2.6.32.11+drm33.2
SourcePackage: drbd8
Uname: Linux 2.6.32-20-generic i686



_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-ha
Post to     : ubuntu-ha@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-ha
More help   : https://help.launchpad.net/ListHelp

Reply via email to