[Pkg-fglrx-devel] Bug#588447: Bug#588447: fglrx: fglrx module is only compiled for current kernel instead of all installed kernels

[Daniel Dehnhard]

2010/7/8 Patrick Matthäi <pmatthaei at debian.org>

> Am 08.07.2010 15:13, schrieb Daniel Dehnhard:
> > Package: fglrx-modules-dkms
> > Version: 1:10-6-1
> > Severity: normal
> > File: fglrx
> >
> >
> > I installed a new Debian Squeeze system. I have the following problem
> with the fglrx modules:
> > DKMS compiles the modules only for the currently running kernel.
> > E.g. if the kernel is updated via apt, I can see the compile messages,
> but it compiles for
> > the running kernel only. After reboot the kernel can't be loaded.
>
> You mean the module.
>

Oh, yes, module of course.


> This is a known bug and Michael wants to fix it :)
>

Good to hear.


> > With "dpkg-reconfigure fglrx-modules-dkms" I can trigger a compile for
> the now running kernel,
> > but this also removes the module for the previous kernel.
>
> This is the right behaviour.
>


Are you sure? I mean the previous kernel was not removed, it's still there.
The behaviour I expect would be like that of virtualbox-ose, the creation of
the modules for every installed kernel.
It shows that with 'dkms status': the three virtualbox modules list all
kernels, gflrx only one
(Sorry, can't paste the output at the moment as vb ose is no longer
installed).


>
>
> > If I select the previous kernel in grub and boot with that the same
> situation appears.
> >
> > If it's any help I see the same problem with Virtualbox (PUEL version
> from virtualbox.org) but it
> > works well with virtualbox-ose from the debian repositories.


>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-fglrx-devel/attachments/20100708/422b52e4/attachment.htm>