<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><br></div><div class="gmail_quote">2016-07-16 4:45 GMT-03:00 Neil Bothwick <span dir="ltr"><<a href="mailto:neil@digimed.co.uk" target="_blank">neil@digimed.co.uk</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><span class="">On Fri, 15 Jul 2016 19:59:51 -0300, Facundo Curti wrote:<br> <br> > > Why do you want DKMS whereas you already compile your own kernel?<br> <br> </span><span class="">> Because I have a module that is outside the kernel tree:<br> <br> </span>You don't need DKMS for that, either re-emerge the module manually after<br> compiling a new kernel or run emerge @module-rebuild. If the module is<br> not in portage, manually reinstall it for each new kernel.<br> <br> DKMS is for people that don't get involved in compiling kernels or<br> modules, it is for users of binary distros.<br> <span class=""><font color="#888888"><br> <br> --<br> Neil Bothwick<br> <br> Walking on water and writing software to specification is easy if they're<br> frozen.<br> </font></span></blockquote></div><br></div><div class="gmail_extra">It is not in portage. It is a unique module. Edited by me in the source code.</div><div class="gmail_extra"><br></div><div class="gmail_extra">But how can I install the module without dkms? usually I make this automatically with dkms :S</div><div class="gmail_extra"><br></div></div>