Your message dated Sat, 12 Dec 2009 16:56:20 +0100
with message-id <[email protected]>
and subject line Re: [Pkg-dkms-maint] Bug#560822: dkms: please autorebuild
modules when new kernel images are installed
has caused the Debian Bug report #560822,
regarding dkms: please autorebuild modules when new kernel images are installed
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
560822: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560822
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
package: dkms
version: 2.1.0.1-4
severity: important
hi, i just upgraded to the linux 2.6.32 package today and noticed that
my kernel modules (virtualbox and fglrx) had not been rebuilt for the
new version. it would be very nice if dkms did this automagically.
also, this limitatation could have a significant impact (which is why i
rated this bug important) in the future if a kernel ABI change occurs
in the stable release since dkms modules for that new ABI will not be
available. this would be a big headache to manually deal with;
whereas, it would be much easier to implement autorebuilding in
unstable now before dkms enters stable.
best wishes,
mike
--- End Message ---
--- Begin Message ---
On Saturday 12 December 2009 11:40:04, Michael Gilbert wrote:
> dkms status had said:
>
> # dkms status
> fglrx, 9-11, 2.6.31-2-amd64, x86_64: installed
>
> i looked through /var/log/messages and saw something that said
> 'dkms_autobuild: missing linux-headers-2.6.32', so i installed
> the headers. now the module is built during boot and loaded:
>
> # dkms status
> fglrx, 9-11, 2.6.32-trunk-amd64, x86_64: installed
>
> so, it looks like the solution is to make sure that the correct headers
> are installed alongside new kernel updates when using dkms.
Exactly. :)
Closing the bug.
David
--
. ''`. Debian developer | http://wiki.debian.org/DavidPaleino
: :' : Linuxer #334216 --|-- http://www.hanskalabs.net/
`. `'` GPG: 1392B174 ----|---- http://snipr.com/qa_page
`- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
_______________________________________________
Pkg-dkms-maint mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/pkg-dkms-maint
