On Mon, Nov 08, 2010 at 02:30:57PM -0800, Russ Allbery wrote:
> > Unfortunately it does not work.
>
> Well, that's not true as a general statement,
It was not intended as general statement - I just forgot the "for me".
Otherwise I would have filed a more detailed bug report. I was hoping
for the docs first ...
> We'll need some additional debugging information from you, such as what
> the exact apt output was when you upgraded the kernel headers package to
> the version corresponding to your new kernel (DKMS should have triggered
> and told you what you were doing). If you've switched to nouveau, I'm not
> sure if you want to go back and reproduce the problem to provide that
> output. If you are, let us know; if not, we'll probably have to close
> this as unreproducible unless someone else can duplicate the problem.
The bug report was just about the misleading hint to the doc - if this
is fixed I'm fine.
However, if it is helpful I might switch back and try again (but not
before the weekend). It might even be that the *installation* itself
was working - the kernel module just did not loaded. I had some strange
dmesg output after modprobe-ing it which said I migh thave loaded
another module (which was actually not the case).
If you would tell me precisely what I should try to give the most
helpful information (removing / purging what package(s) and reinstalling
which ones) I'm willing to do the debugging work.
Kind regards and thanks for your support
Andreas.
--
http://fam-tille.de
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
