Creating a kernel module has nothing in common with not booting a system, 
unless you get a kernel panic or similar.

I tried to reproduce and I have been able to do so.

I also talked with upstream, they will make some changes in making the dkms 
more robust, but nothing should have changed in this
particular release.

cheers,

G.




Il Sabato 24 Ottobre 2015 13:33, Salvo Tomaselli <tipos...@tiscali.it> ha 
scritto:



It is the only recent package that touched kernel modules.
Il 24/ott/2015 12:09, "Ritesh Raj Sarraf" <r...@researchut.com> ha scritto:

Control: tag -1 +moreinfo
>Control: severity -1 normal
>
>
>For a bug with severity "critical", you should provide appropriate
>information. Otherwise it does not justify the severity.
>
>
>Your logs have nothing mentioned about vbox. So I don't understand how
>you'd point this as a vbox problem.
>
>
>On Fri, 2015-10-23 at 11:14 +0200, Salvo Tomaselli wrote:
>> Dear Maintainer,
>>
>> apparently upgrading virtualbox messed with my custom built kernel's
>> modules,
>> and so if I boot with that kernel I no longer have a video card and I
>> am not
>> able to start Xorg.
>>
>> Also, the text on my console is unusually huge.
>--
>Ritesh Raj Sarraf
>RESEARCHUT - http://www.researchut.com
>"Necessity is the mother of invention."
>
>

Reply via email to