Hi,
>Well I had no modules for framebuffer, so Xorg would not run because of "no
>video card" and no modules for network interfaces.
we don't provide any graphical kernel module AFAIK, so I don't think we can mess
with framebuffer.
TBH we have a guest module that might have some graphical
> Creating a kernel module has nothing in common with not booting a system,
unless you get a kernel panic or similar.
Well I had no modules for framebuffer, so Xorg would not run because of "no
video card" and no modules for network interfaces.
--
Salvo Tomaselli
"Io non mi sento obbligato a
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
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,
It is the only recent package that touched kernel modules.
Il 24/ott/2015 12:09, "Ritesh Raj Sarraf" ha scritto:
> Control: tag -1 +moreinfo
> Control: severity -1 normal
>
>
> For a bug with severity "critical", you should provide appropriate
> information. Otherwise it
Package: virtualbox-source
Version: 5.0.8-dfsg-1
Severity: critical
Justification: breaks the whole system
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
6 matches
Mail list logo