I've got an answer from NVIDIA:
"Our driver design, based on earlier assumptions according to
use/deployment cases at the time, packages all components together to
ensure integrity is retained as components evolve over the course of
driver development.
We are investigating the ability to enable mod
On 2018-03-30 20:02, Luca Boccassi wrote:
On Mon, 2018-03-26 at 18:45 +0200, Philipp Kern wrote:
I would like to understand better what the current set of packages
helps
with, though. It is true that I hadn't considered that you are
shipping
so many packages right now. However, you seem to also
On Mon, 2018-03-26 at 18:45 +0200, Philipp Kern wrote:
> Hi Luca,
>
> On 3/21/18 2:01 PM, Luca Boccassi wrote:
> > Isn't this sort-of-like what Ubuntu does? IIRC they lump together
> > everything into a single package unlike we do, and they are named
> > after
> > the major revision.
>
> let's sa
On Fri, 2018-03-23 at 14:54 +, Michael Schaller wrote:
> > I see. Perhaps a systemd unit with the appropriate precedences set
> > so
> > that it runs before X starts? And $something-$something for Sys-V I
> > guess :-)
>
> The more I think about it maybe this shouldn't be handled by a
> servic
Hi Luca,
On 3/21/18 2:01 PM, Luca Boccassi wrote:
> Isn't this sort-of-like what Ubuntu does? IIRC they lump together
> everything into a single package unlike we do, and they are named after
> the major revision.
let's say that even Ubuntu have not solved this problem because they
don't consider
On Thu, 2018-03-22 at 14:36 +, Michael Schaller wrote:
> > How would the switch-at-boot mechanism work?
>
> The basic idea for the switch-at-boot mechanism is that it would
> check the
> version of the loaded NVIDIA kernel module
> (/sys/module/nvidia/version) on
> boot and then select the mat
On 22.03.2018 15:43, Andreas Beckmann wrote:
> On 2018-03-22 15:36, Michael Schaller wrote:
>>> We should probably postpone this to post-390.xx if nvidia sticks to
>>> their plan to drop i386 driver support ...
>> That's the first time I've heard about that. Do you have further
>> information about
On 2018-03-22 15:36, Michael Schaller wrote:
>> We should probably postpone this to post-390.xx if nvidia sticks to
>> their plan to drop i386 driver support ...
> That's the first time I've heard about that. Do you have further
> information about that (link is fine). I also wonder how that will i
We should probably postpone this to post-390.xx if nvidia sticks to
their plan to drop i386 driver support ... that would remove a lot of
complexity, since we probably don't need proper multiarch support any
more ...
Andreas
Control: severity -1 normal
On Wed, 2018-03-21 at 08:17 +, Michael Schaller wrote:
> Please reconsider that this is merely an annoyance and that this is a
> wishlist item.
> If a NVIDIA driver security update is pushed and security updates are
> installed unattendedly then all NVIDIA user spac
On Wed, 2018-03-21 at 08:56 +0100, Philipp Kern wrote:
> On 03/20/2018 10:59 PM, Luca Boccassi wrote:
> > The problems I see are that it would make an already quite complex
> > packaging system, over which we have very little control (most of
> > it
> > it's binary blobs) even more complicated. We
I cannot remember any bug reports regarding this upgrade problem before
yours ...
-ENOTMUCHTIMETHISWEEK :-(
Andreas
On 03/20/2018 10:59 PM, Luca Boccassi wrote:
> The problems I see are that it would make an already quite complex
> packaging system, over which we have very little control (most of it
> it's binary blobs) even more complicated. We already have 2 layers of
> update-alternatives (mesa vs nvidia and
Control: severity -1 wishlist
On Tue, 2018-03-20 at 21:22 +0100, Philipp Kern wrote:
> Hi,
>
> On 2/5/18 4:26 PM, Philipp Kern wrote:
> > Since forever users of NVIDIA on Debian accepted that package
> > upgrades
> > break newly spawned binaries because the interface between the
> > client
> > li
Hi,
On 2/5/18 4:26 PM, Philipp Kern wrote:
> Since forever users of NVIDIA on Debian accepted that package upgrades
> break newly spawned binaries because the interface between the client
> library and the kernel driver is strictly versioned. The kernel module
> will emit an API mismatch error int
Source: nvidia-graphics-drivers
Since forever users of NVIDIA on Debian accepted that package upgrades
break newly spawned binaries because the interface between the client
library and the kernel driver is strictly versioned. The kernel module
will emit an API mismatch error into the kernel log an
16 matches
Mail list logo
