[Pkg-dkms-maint] Bug#586725: closed by Michael Gilbert <michael.s.gilbert at gmail.com> (re: dkms attempts to install modules in wrong order)

Jan Muszynski debianbugs at jancm.org
Sat Aug 21 03:50:01 UTC 2010


What you show is virtualbox-ose. Compare to PUEL. And no, you can't
say it's a bug in the PUEL implementation. Note that when you run
/etc/init.d/vboxdrv setup it:
1) Does use dkms if it's available
2) Explicitly processes the drivers in order
Anyway:

ls /var/lib/dkms
dkms_dbversion  nvidia  vboxdrv  vboxnetadp  vboxnetflt

apt-show-versions -a virtualbox-3.2
virtualbox-3.2 3.2.8-64453~Debian~lenny install ok installed
virtualbox-3.2 3.2.8-64453~Debian~lenny lenny download.virtualbox.org
No testing version
No unstable version
virtualbox-3.2/lenny uptodate 3.2.8-64453~Debian~lenny


The issue that I originally filed this on obviously isn't critical.
For my own purposes I can easily correct this. The general issue
remains though. What order should the various dkms modules get
compiled in? I think the only logical order is sorted alpha, since if
there are modules with inter-related dependencies that would be what
they logically would use. For other, standalone, modules the order
doesn't matter so it's no harm no foul.

Bottom line it's a simple change and I don't see how it could possibly
hurt anything, so I'm unable to understand the resistance/reluctance
to implement it.



On Tue, Aug 17, 2010 at 8:03 PM, Debian Bug Tracking System
<owner at bugs.debian.org> wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the dkms package:
>
> #567460: dkms attempts to install modules in wrong order
>
> It has been closed by Michael Gilbert <michael.s.gilbert at gmail.com>.
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Michael Gilbert <michael.s.gilbert at gmail.com> by
> replying to this email.
>
>
> --
> 567460: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567460
> Debian Bug Tracking System
> Contact owner at bugs.debian.org with problems
>
>
> ---------- Forwarded message ----------
> From: Michael Gilbert <michael.s.gilbert at gmail.com>
> To: 586725-done at bugs.debian.org, 567460-done at bugs.debian.org
> Date: Tue, 17 Aug 2010 23:00:28 -0400
> Subject: re: dkms attempts to install modules in wrong order
> forcemerge 586725 567460
> thanks
>
> this must have been a virtualbox issue.  as of at least 3.2.8 they now
> only have one dkms directory, and i assume they've set that up in a way
> that installs modules in the correct order:
>
> $ ls /var/lib/dkms
> dkms_dbversion  virtualbox-ose
>
> if this hasn't fixed the problem, please reopen the bug.
>
> thanks,
> mike
>
>
>
> ---------- Forwarded message ----------
> From: Jan Muszynski <debianbugs at jancm.org>
> To: Debian Bug Tracking System <submit at bugs.debian.org>
> Date: Mon, 21 Jun 2010 19:59:36 -0400
> Subject: dkms attempts to install modules in wrong order
> Package: dkms
> Version: 2.1.1.2-3
> Severity: normal
> Tags: patch
>
> This shows up, on my system, when trying to build the modules for virtualbox (PUEL). There are 3 modules, and they need to be built in a specific order (the others depend on the first to build correctly). If dkms processes the modules in sorted sequence everything is fine. Otherwise I have to manually get the modules to build. Here's an example of what I mean:
>
> 'find "$dkms_tree" -maxdepth 1 -mindepth 1 -type d' returns, on my system:
> /var/lib/dkms/vboxnetadp
> /var/lib/dkms/vboxnetflt
> /var/lib/dkms/nvidia
> /var/lib/dkms/vboxdrv
>
> The 2 vboxnet modules dpend on the vboxdrv module in order to compile correctly, so this ends up failing. After patching the autoinstaller to pipe the results through a sort the order becomes:
> /var/lib/dkms/nvidia
> /var/lib/dkms/vboxdrv
> /var/lib/dkms/vboxnetadp
> /var/lib/dkms/vboxnetflt
>
> And this works just fine. Patch attached. Need anything else please let me know.
> TIA
> -jcm
>
> -- System Information:
> Debian Release: squeeze/sid
>  APT prefers testing
>  APT policy: (900, 'testing'), (100, 'unstable'), (1, 'experimental')
> Architecture: i386 (i686)
>
> Kernel: Linux 2.6.34-02.i386vanilla (PREEMPT)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
>
> Versions of packages dkms depends on:
> ii  build-essential              11.5        Informational list of build-essent
> ii  dpkg-dev                     1.15.7.2    Debian package development tools
> ii  gcc                          4:4.4.4-2   The GNU C compiler
> ii  make                         3.81-8      An utility for Directing compilati
> ii  module-init-tools            3.12~pre2-3 tools for managing Linux kernel mo
>
> Versions of packages dkms recommends:
> ii  fakeroot                    1.14.4-1     Gives a fake root environment
> ii  linux-headers-2.6.32-5-686  2.6.32-15    Header files for Linux 2.6.32-5-68
> ii  linux-headers-2.6.34-0.dmz. 2.6.34-43    Header files for Linux 2.6.34-0.dm
> ii  linux-headers-2.6.34-02.i38 2010.163.jcm Header files related to Linux kern
> ii  linux-image-2.6.32-5-686 [l 2.6.32-15    Linux 2.6.32 for modern PCs
> ii  linux-image-2.6.34-0.dmz.12 2.6.34-43    Linux 2.6.34 for modern PCs
> ii  linux-image-2.6.34-02.i386v 2010.163.jcm Linux kernel binary image for vers
> ii  lsb-release                 3.2-23.1     Linux Standard Base version report
> ii  menu                        2.1.43       generates programs menu for all me
> ii  patch                       2.6-2        Apply a diff file to an original
> ii  sudo                        1.7.2p7-1    Provide limited super user privile
>
> dkms suggests no packages.
>
> -- Configuration Files:
> /etc/kernel/prerm.d/dkms changed [not included]
>
> -- no debconf information
>
>





More information about the Pkg-dkms-maint mailing list