Bug#929521: Conficts in upgrade to 418.74-1 with optimus setup

classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#929521: Conficts in upgrade to 418.74-1 with optimus setup

ghisvail
Package: src:nvidia-graphics-drivers
Version: 418.74-1
Severity: important

Dear Debian NVIDIA maintainers,

I attempted to upgrade my laptop (a Dell Inspiron 7580 with a GeForce
MX150) running Debian Buster and configured with nvidia-driver,
bumblebee-nvidia and primus, plus the necessary 32-bit libs to run
Steam. So far, upgrades have been smooth until version 418.56-2.

Sadly, version 418.74-1 is a different story. Running `apt upgrade`
shows the following output:

```
Les paquets suivants contiennent des dépendances non satisfaites :
 nvidia-nonglvnd-vulkan-common : Est en conflit avec: libgl1-nvidia-
legacy-390xx-glvnd-glx mais 390.116-1 devra être installé
                                 Est en conflit avec: libgl1-nvidia-
legacy-390xx-glvnd-glx:i386 mais 390.116-1 devra être installé
 primus : Casse: libgl1-nvidia-legacy-390xx-glvnd-glx (>= 0) mais
390.116-1 devra être installé
          Casse: libgl1-nvidia-legacy-390xx-glvnd-glx:i386 (>= 0) mais
390.116-1 devra être installé
```

Which indicates conflicts for nvidia-nonglvnd-vulkan-common and
breakage
for Primus. What surprises me is the upgrade wishing to pull part of
the
legacy nvidia driver, whilst I am definitely using the current one.

I have also tried to just remove the whole NVIDIA stack and start over
as when I initially setup the machine. Running `apt get install
bumblebee-nvidia` shows the following output :

```
Les paquets suivants ont été installés automatiquement et ne sont plus
nécessaires :
  libegl-mesa0:i386 libegl1:i386 libgbm1:i386 libopengl0
libopengl0:i386 libwayland-server0:i386 libxcb-xfixes0:i386 nvidia-egl-
common nvidia-egl-icd nvidia-egl-icd:i386
Veuillez utiliser « sudo apt autoremove » pour les supprimer.
Les paquets supplémentaires suivants seront installés :
  bbswitch-dkms bumblebee libegl-nvidia-legacy-390xx0:i386 libegl1-
nvidia libegl1-nvidia:i386 libegl1-nvidia-legacy-390xx:i386 libgl1-
nvidia-glx libgl1-nvidia-glx:i386 libgl1-nvidia-legacy-390xx-glx:i386
  libgles-nvidia-legacy-390xx1:i386 libgles-nvidia-legacy-390xx2:i386
libglx-nvidia-legacy-390xx0:i386 libnvidia-legacy-390xx-cfg1 libnvidia-
legacy-390xx-cfg1:i386 libnvidia-legacy-390xx-eglcore:i386
  libnvidia-legacy-390xx-glcore libnvidia-legacy-390xx-glcore:i386
libnvidia-legacy-390xx-ml1 nvidia-driver-libs-nonglvnd nvidia-driver-
libs-nonglvnd:i386 nvidia-driver-libs-nonglvnd-i386:i386
  nvidia-legacy-390xx-alternative nvidia-legacy-390xx-driver-libs-
nonglvnd:i386 nvidia-legacy-390xx-kernel-dkms nvidia-legacy-390xx-
kernel-support nvidia-legacy-390xx-nonglvnd-vulkan-icd:i386
  nvidia-legacy-390xx-vdpau-driver nvidia-nonglvnd-vulkan-common
nvidia-nonglvnd-vulkan-icd nvidia-nonglvnd-vulkan-icd:i386 nvidia-
settings-legacy-390xx primus primus-libs primus-libs-ia32:i386 socat
  xserver-xorg-video-nvidia-legacy-390xx
Paquets suggérés :
  vulkan-utils:i386 vulkan-utils
Paquets recommandés :
  nvidia-legacy-390xx-driver | libnvidia-legacy-390xx-cuda1 libgl1-
nvidia-legacy-390xx-glvnd-glx | libgl1-nvidia-legacy-390xx-glx nvidia-
legacy-390xx-driver
Les paquets suivants seront ENLEVÉS :
  libgl1-nvidia-glvnd-glx libgl1-nvidia-glvnd-glx:i386 nvidia-driver-
libs nvidia-driver-libs:i386 nvidia-driver-libs-i386:i386 nvidia-
vulkan-common nvidia-vulkan-icd nvidia-vulkan-icd:i386
Les NOUVEAUX paquets suivants seront installés :
  bbswitch-dkms bumblebee bumblebee-nvidia libegl-nvidia-legacy-
390xx0:i386 libegl1-nvidia libegl1-nvidia:i386 libegl1-nvidia-legacy-
390xx:i386 libgl1-nvidia-glx libgl1-nvidia-glx:i386
  libgl1-nvidia-legacy-390xx-glx:i386 libgles-nvidia-legacy-390xx1:i386
libgles-nvidia-legacy-390xx2:i386 libglx-nvidia-legacy-390xx0:i386
libnvidia-legacy-390xx-cfg1 libnvidia-legacy-390xx-cfg1:i386
  libnvidia-legacy-390xx-eglcore:i386 libnvidia-legacy-390xx-glcore
libnvidia-legacy-390xx-glcore:i386 libnvidia-legacy-390xx-ml1 nvidia-
driver-libs-nonglvnd nvidia-driver-libs-nonglvnd:i386
  nvidia-driver-libs-nonglvnd-i386:i386 nvidia-legacy-390xx-alternative
nvidia-legacy-390xx-driver-libs-nonglvnd:i386 nvidia-legacy-390xx-
kernel-dkms nvidia-legacy-390xx-kernel-support
  nvidia-legacy-390xx-nonglvnd-vulkan-icd:i386 nvidia-legacy-390xx-
vdpau-driver nvidia-nonglvnd-vulkan-common nvidia-nonglvnd-vulkan-icd
nvidia-nonglvnd-vulkan-icd:i386 nvidia-settings-legacy-390xx primus
  primus-libs primus-libs-ia32:i386 socat xserver-xorg-video-nvidia-
legacy-390xx
0 mis à jour, 37 nouvellement installés, 8 à enlever et 0 non mis à
jour.
```

Once again, it is very suprising that apt now wants to install all
these
legacy nvidia driver packages, yet even remove `nvidia-driver-libs`.

Looking at the change log of version 418.74-1, the only item that may
be
causing this issue is : "Tune Recommends to smoothen some upgrade paths
on i386."

Should you need further information, please ask.

Cheers,
Ghislain

-- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN,
TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Reply | Threaded
Open this post in threaded view
|

Bug#929521: Conficts in upgrade to 418.74-1 with optimus setup

Luca Boccassi-3
Control: reassign 929525 src:nvidia-graphics-drivers 418.74-1
Control: forcemerge 929521 929525

On Sat, 2019-05-25 at 15:54 +0200, [hidden email] wrote:

> Package: src:nvidia-graphics-drivers
> Version: 418.74-1
> Severity: important
>
> Dear Debian NVIDIA maintainers,
>
> I attempted to upgrade my laptop (a Dell Inspiron 7580 with a GeForce
> MX150) running Debian Buster and configured with nvidia-driver,
> bumblebee-nvidia and primus, plus the necessary 32-bit libs to run
> Steam. So far, upgrades have been smooth until version 418.56-2.
>
> Sadly, version 418.74-1 is a different story. Running `apt upgrade`
> shows the following output:
>
> ```
> Les paquets suivants contiennent des dépendances non satisfaites :
>  nvidia-nonglvnd-vulkan-common : Est en conflit avec: libgl1-nvidia-
> legacy-390xx-glvnd-glx mais 390.116-1 devra être installé
>                                  Est en conflit avec: libgl1-nvidia-
> legacy-390xx-glvnd-glx:i386 mais 390.116-1 devra être installé
>  primus : Casse: libgl1-nvidia-legacy-390xx-glvnd-glx (>= 0) mais
> 390.116-1 devra être installé
>           Casse: libgl1-nvidia-legacy-390xx-glvnd-glx:i386 (>= 0)
> mais
> 390.116-1 devra être installé
> ```
>
> Which indicates conflicts for nvidia-nonglvnd-vulkan-common and
> breakage
> for Primus. What surprises me is the upgrade wishing to pull part of
> the
> legacy nvidia driver, whilst I am definitely using the current one.
>
> I have also tried to just remove the whole NVIDIA stack and start
> over
> as when I initially setup the machine. Running `apt get install
> bumblebee-nvidia` shows the following output :
>
> ```
> Les paquets suivants ont été installés automatiquement et ne sont
> plus
> nécessaires :
>   libegl-mesa0:i386 libegl1:i386 libgbm1:i386 libopengl0
> libopengl0:i386 libwayland-server0:i386 libxcb-xfixes0:i386 nvidia-
> egl-
> common nvidia-egl-icd nvidia-egl-icd:i386
> Veuillez utiliser « sudo apt autoremove » pour les supprimer.
> Les paquets supplémentaires suivants seront installés :
>   bbswitch-dkms bumblebee libegl-nvidia-legacy-390xx0:i386 libegl1-
> nvidia libegl1-nvidia:i386 libegl1-nvidia-legacy-390xx:i386 libgl1-
> nvidia-glx libgl1-nvidia-glx:i386 libgl1-nvidia-legacy-390xx-glx:i386
>   libgles-nvidia-legacy-390xx1:i386 libgles-nvidia-legacy-390xx2:i386
> libglx-nvidia-legacy-390xx0:i386 libnvidia-legacy-390xx-cfg1
> libnvidia-
> legacy-390xx-cfg1:i386 libnvidia-legacy-390xx-eglcore:i386
>   libnvidia-legacy-390xx-glcore libnvidia-legacy-390xx-glcore:i386
> libnvidia-legacy-390xx-ml1 nvidia-driver-libs-nonglvnd nvidia-driver-
> libs-nonglvnd:i386 nvidia-driver-libs-nonglvnd-i386:i386
>   nvidia-legacy-390xx-alternative nvidia-legacy-390xx-driver-libs-
> nonglvnd:i386 nvidia-legacy-390xx-kernel-dkms nvidia-legacy-390xx-
> kernel-support nvidia-legacy-390xx-nonglvnd-vulkan-icd:i386
>   nvidia-legacy-390xx-vdpau-driver nvidia-nonglvnd-vulkan-common
> nvidia-nonglvnd-vulkan-icd nvidia-nonglvnd-vulkan-icd:i386 nvidia-
> settings-legacy-390xx primus primus-libs primus-libs-ia32:i386 socat
>   xserver-xorg-video-nvidia-legacy-390xx
> Paquets suggérés :
>   vulkan-utils:i386 vulkan-utils
> Paquets recommandés :
>   nvidia-legacy-390xx-driver | libnvidia-legacy-390xx-cuda1 libgl1-
> nvidia-legacy-390xx-glvnd-glx | libgl1-nvidia-legacy-390xx-glx
> nvidia-
> legacy-390xx-driver
> Les paquets suivants seront ENLEVÉS :
>   libgl1-nvidia-glvnd-glx libgl1-nvidia-glvnd-glx:i386 nvidia-driver-
> libs nvidia-driver-libs:i386 nvidia-driver-libs-i386:i386 nvidia-
> vulkan-common nvidia-vulkan-icd nvidia-vulkan-icd:i386
> Les NOUVEAUX paquets suivants seront installés :
>   bbswitch-dkms bumblebee bumblebee-nvidia libegl-nvidia-legacy-
> 390xx0:i386 libegl1-nvidia libegl1-nvidia:i386 libegl1-nvidia-legacy-
> 390xx:i386 libgl1-nvidia-glx libgl1-nvidia-glx:i386
>   libgl1-nvidia-legacy-390xx-glx:i386 libgles-nvidia-legacy-
> 390xx1:i386 
> libgles-nvidia-legacy-390xx2:i386 libglx-nvidia-legacy-390xx0:i386
> libnvidia-legacy-390xx-cfg1 libnvidia-legacy-390xx-cfg1:i386
>   libnvidia-legacy-390xx-eglcore:i386 libnvidia-legacy-390xx-glcore
> libnvidia-legacy-390xx-glcore:i386 libnvidia-legacy-390xx-ml1 nvidia-
> driver-libs-nonglvnd nvidia-driver-libs-nonglvnd:i386
>   nvidia-driver-libs-nonglvnd-i386:i386 nvidia-legacy-390xx-
> alternative 
> nvidia-legacy-390xx-driver-libs-nonglvnd:i386 nvidia-legacy-390xx-
> kernel-dkms nvidia-legacy-390xx-kernel-support
>   nvidia-legacy-390xx-nonglvnd-vulkan-icd:i386 nvidia-legacy-390xx-
> vdpau-driver nvidia-nonglvnd-vulkan-common nvidia-nonglvnd-vulkan-icd
> nvidia-nonglvnd-vulkan-icd:i386 nvidia-settings-legacy-390xx primus
>   primus-libs primus-libs-ia32:i386 socat xserver-xorg-video-nvidia-
> legacy-390xx
> 0 mis à jour, 37 nouvellement installés, 8 à enlever et 0 non mis à
> jour.
> ```
>
> Once again, it is very suprising that apt now wants to install all
> these
> legacy nvidia driver packages, yet even remove `nvidia-driver-libs`.
>
> Looking at the change log of version 418.74-1, the only item that may
> be
> causing this issue is : "Tune Recommends to smoothen some upgrade
> paths
> on i386."
>
> Should you need further information, please ask.
>
> Cheers,
> Ghislain

Hi,

I cannot reproduce this, the upgrade was fine on my laptop, and
installing in a chroot works fine too. Yes the 390xx series gets
installed if recommends are enabled, but that was intentional, and it's
sufficient to use --no-install-recommends and the existing series was
upgrade just fine.

--
Kind regards,
Luca Boccassi

Reply | Threaded
Open this post in threaded view
|

Bug#929521: Conficts in upgrade to 418.74-1 with optimus setup

ghisvail
Le dimanche 26 mai 2019 à 19:44 +0100, Luca Boccassi a écrit :

> Control: reassign 929525 src:nvidia-graphics-drivers 418.74-1
> Control: forcemerge 929521 929525
>
> On Sat, 2019-05-25 at 15:54 +0200, [hidden email] wrote:
> > Package: src:nvidia-graphics-drivers
> > Version: 418.74-1
> > Severity: important
> >
> > Dear Debian NVIDIA maintainers,
> >
> > I attempted to upgrade my laptop (a Dell Inspiron 7580 with a
> > GeForce
> > MX150) running Debian Buster and configured with nvidia-driver,
> > bumblebee-nvidia and primus, plus the necessary 32-bit libs to run
> > Steam. So far, upgrades have been smooth until version 418.56-2.
> >
> > Sadly, version 418.74-1 is a different story. Running `apt upgrade`
> > shows the following output:
> >
> > ```
> > Les paquets suivants contiennent des dépendances non satisfaites :
> >  nvidia-nonglvnd-vulkan-common : Est en conflit avec: libgl1-
> > nvidia-
> > legacy-390xx-glvnd-glx mais 390.116-1 devra être installé
> >                                  Est en conflit avec: libgl1-
> > nvidia-
> > legacy-390xx-glvnd-glx:i386 mais 390.116-1 devra être installé
> >  primus : Casse: libgl1-nvidia-legacy-390xx-glvnd-glx (>= 0) mais
> > 390.116-1 devra être installé
> >           Casse: libgl1-nvidia-legacy-390xx-glvnd-glx:i386 (>= 0)
> > mais
> > 390.116-1 devra être installé
> > ```
> >
> > Which indicates conflicts for nvidia-nonglvnd-vulkan-common and
> > breakage
> > for Primus. What surprises me is the upgrade wishing to pull part
> > of
> > the
> > legacy nvidia driver, whilst I am definitely using the current one.
> >
> > I have also tried to just remove the whole NVIDIA stack and start
> > over
> > as when I initially setup the machine. Running `apt get install
> > bumblebee-nvidia` shows the following output :
> >
> > ```
> > Les paquets suivants ont été installés automatiquement et ne sont
> > plus
> > nécessaires :
> >   libegl-mesa0:i386 libegl1:i386 libgbm1:i386 libopengl0
> > libopengl0:i386 libwayland-server0:i386 libxcb-xfixes0:i386 nvidia-
> > egl-
> > common nvidia-egl-icd nvidia-egl-icd:i386
> > Veuillez utiliser « sudo apt autoremove » pour les supprimer.
> > Les paquets supplémentaires suivants seront installés :
> >   bbswitch-dkms bumblebee libegl-nvidia-legacy-390xx0:i386 libegl1-
> > nvidia libegl1-nvidia:i386 libegl1-nvidia-legacy-390xx:i386 libgl1-
> > nvidia-glx libgl1-nvidia-glx:i386 libgl1-nvidia-legacy-390xx-
> > glx:i386
> >   libgles-nvidia-legacy-390xx1:i386 libgles-nvidia-legacy-
> > 390xx2:i386
> > libglx-nvidia-legacy-390xx0:i386 libnvidia-legacy-390xx-cfg1
> > libnvidia-
> > legacy-390xx-cfg1:i386 libnvidia-legacy-390xx-eglcore:i386
> >   libnvidia-legacy-390xx-glcore libnvidia-legacy-390xx-glcore:i386
> > libnvidia-legacy-390xx-ml1 nvidia-driver-libs-nonglvnd nvidia-
> > driver-
> > libs-nonglvnd:i386 nvidia-driver-libs-nonglvnd-i386:i386
> >   nvidia-legacy-390xx-alternative nvidia-legacy-390xx-driver-libs-
> > nonglvnd:i386 nvidia-legacy-390xx-kernel-dkms nvidia-legacy-390xx-
> > kernel-support nvidia-legacy-390xx-nonglvnd-vulkan-icd:i386
> >   nvidia-legacy-390xx-vdpau-driver nvidia-nonglvnd-vulkan-common
> > nvidia-nonglvnd-vulkan-icd nvidia-nonglvnd-vulkan-icd:i386 nvidia-
> > settings-legacy-390xx primus primus-libs primus-libs-ia32:i386
> > socat
> >   xserver-xorg-video-nvidia-legacy-390xx
> > Paquets suggérés :
> >   vulkan-utils:i386 vulkan-utils
> > Paquets recommandés :
> >   nvidia-legacy-390xx-driver | libnvidia-legacy-390xx-cuda1 libgl1-
> > nvidia-legacy-390xx-glvnd-glx | libgl1-nvidia-legacy-390xx-glx
> > nvidia-
> > legacy-390xx-driver
> > Les paquets suivants seront ENLEVÉS :
> >   libgl1-nvidia-glvnd-glx libgl1-nvidia-glvnd-glx:i386 nvidia-
> > driver-
> > libs nvidia-driver-libs:i386 nvidia-driver-libs-i386:i386 nvidia-
> > vulkan-common nvidia-vulkan-icd nvidia-vulkan-icd:i386
> > Les NOUVEAUX paquets suivants seront installés :
> >   bbswitch-dkms bumblebee bumblebee-nvidia libegl-nvidia-legacy-
> > 390xx0:i386 libegl1-nvidia libegl1-nvidia:i386 libegl1-nvidia-
> > legacy-
> > 390xx:i386 libgl1-nvidia-glx libgl1-nvidia-glx:i386
> >   libgl1-nvidia-legacy-390xx-glx:i386 libgles-nvidia-legacy-
> > 390xx1:i386
> > libgles-nvidia-legacy-390xx2:i386 libglx-nvidia-legacy-390xx0:i386
> > libnvidia-legacy-390xx-cfg1 libnvidia-legacy-390xx-cfg1:i386
> >   libnvidia-legacy-390xx-eglcore:i386 libnvidia-legacy-390xx-glcore
> > libnvidia-legacy-390xx-glcore:i386 libnvidia-legacy-390xx-ml1
> > nvidia-
> > driver-libs-nonglvnd nvidia-driver-libs-nonglvnd:i386
> >   nvidia-driver-libs-nonglvnd-i386:i386 nvidia-legacy-390xx-
> > alternative
> > nvidia-legacy-390xx-driver-libs-nonglvnd:i386 nvidia-legacy-390xx-
> > kernel-dkms nvidia-legacy-390xx-kernel-support
> >   nvidia-legacy-390xx-nonglvnd-vulkan-icd:i386 nvidia-legacy-390xx-
> > vdpau-driver nvidia-nonglvnd-vulkan-common nvidia-nonglvnd-vulkan-
> > icd
> > nvidia-nonglvnd-vulkan-icd:i386 nvidia-settings-legacy-390xx primus
> >   primus-libs primus-libs-ia32:i386 socat xserver-xorg-video-
> > nvidia-
> > legacy-390xx
> > 0 mis à jour, 37 nouvellement installés, 8 à enlever et 0 non mis à
> > jour.
> > ```
> >
> > Once again, it is very suprising that apt now wants to install all
> > these
> > legacy nvidia driver packages, yet even remove `nvidia-driver-
> > libs`.
> >
> > Looking at the change log of version 418.74-1, the only item that
> > may
> > be
> > causing this issue is : "Tune Recommends to smoothen some upgrade
> > paths
> > on i386."
> >
> > Should you need further information, please ask.
> >
> > Cheers,
> > Ghislain
>
> Hi,
>
> I cannot reproduce this, the upgrade was fine on my laptop, and
> installing in a chroot works fine too.

Did you enable mutliarch (i386) in your test config?

>  Yes the 390xx series gets
> installed if recommends are enabled, but that was intentional, and
> it's
> sufficient to use --no-install-recommends and the existing series was
> upgrade just fine.
>

I wonder why the 390xx legacy drivers are being pulled now. It
definitely was not the case when I initially setup my machine with an
older version of nvidia current.

Indeed, `apt install --no-install-recommends bumblebee-nvidia primus`
does not pull the 390xx series.

Reply | Threaded
Open this post in threaded view
|

Bug#929521: Conficts in upgrade to 418.74-1 with optimus setup

Luca Boccassi-3
On Sun, 26 May 2019 at 22:45, <[hidden email]> wrote:

>
> Le dimanche 26 mai 2019 à 19:44 +0100, Luca Boccassi a écrit :
> > Control: reassign 929525 src:nvidia-graphics-drivers 418.74-1
> > Control: forcemerge 929521 929525
> >
> > On Sat, 2019-05-25 at 15:54 +0200, [hidden email] wrote:
> > > Package: src:nvidia-graphics-drivers
> > > Version: 418.74-1
> > > Severity: important
> > >
> > > Dear Debian NVIDIA maintainers,
> > >
> > > I attempted to upgrade my laptop (a Dell Inspiron 7580 with a
> > > GeForce
> > > MX150) running Debian Buster and configured with nvidia-driver,
> > > bumblebee-nvidia and primus, plus the necessary 32-bit libs to run
> > > Steam. So far, upgrades have been smooth until version 418.56-2.
> > >
> > > Sadly, version 418.74-1 is a different story. Running `apt upgrade`
> > > shows the following output:
> > >
> > > ```
> > > Les paquets suivants contiennent des dépendances non satisfaites :
> > >  nvidia-nonglvnd-vulkan-common : Est en conflit avec: libgl1-
> > > nvidia-
> > > legacy-390xx-glvnd-glx mais 390.116-1 devra être installé
> > >                                  Est en conflit avec: libgl1-
> > > nvidia-
> > > legacy-390xx-glvnd-glx:i386 mais 390.116-1 devra être installé
> > >  primus : Casse: libgl1-nvidia-legacy-390xx-glvnd-glx (>= 0) mais
> > > 390.116-1 devra être installé
> > >           Casse: libgl1-nvidia-legacy-390xx-glvnd-glx:i386 (>= 0)
> > > mais
> > > 390.116-1 devra être installé
> > > ```
> > >
> > > Which indicates conflicts for nvidia-nonglvnd-vulkan-common and
> > > breakage
> > > for Primus. What surprises me is the upgrade wishing to pull part
> > > of
> > > the
> > > legacy nvidia driver, whilst I am definitely using the current one.
> > >
> > > I have also tried to just remove the whole NVIDIA stack and start
> > > over
> > > as when I initially setup the machine. Running `apt get install
> > > bumblebee-nvidia` shows the following output :
> > >
> > > ```
> > > Les paquets suivants ont été installés automatiquement et ne sont
> > > plus
> > > nécessaires :
> > >   libegl-mesa0:i386 libegl1:i386 libgbm1:i386 libopengl0
> > > libopengl0:i386 libwayland-server0:i386 libxcb-xfixes0:i386 nvidia-
> > > egl-
> > > common nvidia-egl-icd nvidia-egl-icd:i386
> > > Veuillez utiliser « sudo apt autoremove » pour les supprimer.
> > > Les paquets supplémentaires suivants seront installés :
> > >   bbswitch-dkms bumblebee libegl-nvidia-legacy-390xx0:i386 libegl1-
> > > nvidia libegl1-nvidia:i386 libegl1-nvidia-legacy-390xx:i386 libgl1-
> > > nvidia-glx libgl1-nvidia-glx:i386 libgl1-nvidia-legacy-390xx-
> > > glx:i386
> > >   libgles-nvidia-legacy-390xx1:i386 libgles-nvidia-legacy-
> > > 390xx2:i386
> > > libglx-nvidia-legacy-390xx0:i386 libnvidia-legacy-390xx-cfg1
> > > libnvidia-
> > > legacy-390xx-cfg1:i386 libnvidia-legacy-390xx-eglcore:i386
> > >   libnvidia-legacy-390xx-glcore libnvidia-legacy-390xx-glcore:i386
> > > libnvidia-legacy-390xx-ml1 nvidia-driver-libs-nonglvnd nvidia-
> > > driver-
> > > libs-nonglvnd:i386 nvidia-driver-libs-nonglvnd-i386:i386
> > >   nvidia-legacy-390xx-alternative nvidia-legacy-390xx-driver-libs-
> > > nonglvnd:i386 nvidia-legacy-390xx-kernel-dkms nvidia-legacy-390xx-
> > > kernel-support nvidia-legacy-390xx-nonglvnd-vulkan-icd:i386
> > >   nvidia-legacy-390xx-vdpau-driver nvidia-nonglvnd-vulkan-common
> > > nvidia-nonglvnd-vulkan-icd nvidia-nonglvnd-vulkan-icd:i386 nvidia-
> > > settings-legacy-390xx primus primus-libs primus-libs-ia32:i386
> > > socat
> > >   xserver-xorg-video-nvidia-legacy-390xx
> > > Paquets suggérés :
> > >   vulkan-utils:i386 vulkan-utils
> > > Paquets recommandés :
> > >   nvidia-legacy-390xx-driver | libnvidia-legacy-390xx-cuda1 libgl1-
> > > nvidia-legacy-390xx-glvnd-glx | libgl1-nvidia-legacy-390xx-glx
> > > nvidia-
> > > legacy-390xx-driver
> > > Les paquets suivants seront ENLEVÉS :
> > >   libgl1-nvidia-glvnd-glx libgl1-nvidia-glvnd-glx:i386 nvidia-
> > > driver-
> > > libs nvidia-driver-libs:i386 nvidia-driver-libs-i386:i386 nvidia-
> > > vulkan-common nvidia-vulkan-icd nvidia-vulkan-icd:i386
> > > Les NOUVEAUX paquets suivants seront installés :
> > >   bbswitch-dkms bumblebee bumblebee-nvidia libegl-nvidia-legacy-
> > > 390xx0:i386 libegl1-nvidia libegl1-nvidia:i386 libegl1-nvidia-
> > > legacy-
> > > 390xx:i386 libgl1-nvidia-glx libgl1-nvidia-glx:i386
> > >   libgl1-nvidia-legacy-390xx-glx:i386 libgles-nvidia-legacy-
> > > 390xx1:i386
> > > libgles-nvidia-legacy-390xx2:i386 libglx-nvidia-legacy-390xx0:i386
> > > libnvidia-legacy-390xx-cfg1 libnvidia-legacy-390xx-cfg1:i386
> > >   libnvidia-legacy-390xx-eglcore:i386 libnvidia-legacy-390xx-glcore
> > > libnvidia-legacy-390xx-glcore:i386 libnvidia-legacy-390xx-ml1
> > > nvidia-
> > > driver-libs-nonglvnd nvidia-driver-libs-nonglvnd:i386
> > >   nvidia-driver-libs-nonglvnd-i386:i386 nvidia-legacy-390xx-
> > > alternative
> > > nvidia-legacy-390xx-driver-libs-nonglvnd:i386 nvidia-legacy-390xx-
> > > kernel-dkms nvidia-legacy-390xx-kernel-support
> > >   nvidia-legacy-390xx-nonglvnd-vulkan-icd:i386 nvidia-legacy-390xx-
> > > vdpau-driver nvidia-nonglvnd-vulkan-common nvidia-nonglvnd-vulkan-
> > > icd
> > > nvidia-nonglvnd-vulkan-icd:i386 nvidia-settings-legacy-390xx primus
> > >   primus-libs primus-libs-ia32:i386 socat xserver-xorg-video-
> > > nvidia-
> > > legacy-390xx
> > > 0 mis à jour, 37 nouvellement installés, 8 à enlever et 0 non mis à
> > > jour.
> > > ```
> > >
> > > Once again, it is very suprising that apt now wants to install all
> > > these
> > > legacy nvidia driver packages, yet even remove `nvidia-driver-
> > > libs`.
> > >
> > > Looking at the change log of version 418.74-1, the only item that
> > > may
> > > be
> > > causing this issue is : "Tune Recommends to smoothen some upgrade
> > > paths
> > > on i386."
> > >
> > > Should you need further information, please ask.
> > >
> > > Cheers,
> > > Ghislain
> >
> > Hi,
> >
> > I cannot reproduce this, the upgrade was fine on my laptop, and
> > installing in a chroot works fine too.
>
> Did you enable mutliarch (i386) in your test config?

Yes.

> >  Yes the 390xx series gets
> > installed if recommends are enabled, but that was intentional, and
> > it's
> > sufficient to use --no-install-recommends and the existing series was
> > upgrade just fine.
> >
>
> I wonder why the 390xx legacy drivers are being pulled now. It
> definitely was not the case when I initially setup my machine with an
> older version of nvidia current.
>
> Indeed, `apt install --no-install-recommends bumblebee-nvidia primus`
> does not pull the 390xx series.

As the changelog says, it's to have a smooth update for i386 as the
mainline doesn't support it anymore.

Reply | Threaded
Open this post in threaded view
|

Bug#929521: Conflicts in upgrade to 418.74-1 with optimus setup

ghisvail
> On Sun, 26 May 2019 23:16:48 +0100 Luca Boccassi <[hidden email]>
> wrote:
> > On Sun, 26 May 2019 at 22:45, <[hidden email]> wrote:
> > >
> > > Le dimanche 26 mai 2019 à 19:44 +0100, Luca Boccassi a écrit :
> > >
> > >  Yes the 390xx series gets
> > > installed if recommends are enabled, but that was intentional,
> and
> > > it's
> > > sufficient to use --no-install-recommends and the existing series
> was
> > > upgrade just fine.
> > >
> >
> > I wonder why the 390xx legacy drivers are being pulled now. It
> > definitely was not the case when I initially setup my machine with
> an
> > older version of nvidia current.
> >
> > Indeed, `apt install --no-install-recommends bumblebee-nvidia
> primus`
> > does not pull the 390xx series.
>
> As the changelog says, it's to have a smooth update for i386 as the
> mainline doesn't support it anymore.

I wonder whether the upgrade path really is that smooth though.

Afterall, both Stefan and I experienced conflicts in the upgrade
process on the very same packages (nvidia-nonglvnd-vulkan-common and
primus). Less experienced users may not feel confident performing the
upgrade as a result, either by `synaptic` or `apt full-upgrade`

Maybe displaying an explanation for this particular upgrade via
NEWS.Debian could help? AFAIC, I was not aware that NVIDIA had indeed
dropped support for 32-bit after release 390 of the drivers.

Cheers,
Ghis

Reply | Threaded
Open this post in threaded view
|

Bug#929521: Conflicts in upgrade to 418.74-1 with optimus setup

Stefan Tsanev
I agree with Ghis, maybe a little more information before this update
could be in great use here. Some people with bumblebee and enabled
multiarch may find difficulties understanding why their system doesn't
want to continue updating anymore via apt. I sitll feel odd about this
upgrade and I'm glad, that I'm not the only one.

Greetings

2019-05-28 6:38 Гринуич+03:00, [hidden email] <[hidden email]>:

>> On Sun, 26 May 2019 23:16:48 +0100 Luca Boccassi <[hidden email]>
>> wrote:
>> > On Sun, 26 May 2019 at 22:45, <[hidden email]> wrote:
>> > >
>> > > Le dimanche 26 mai 2019 à 19:44 +0100, Luca Boccassi a écrit :
>> > >
>> > >  Yes the 390xx series gets
>> > > installed if recommends are enabled, but that was intentional,
>> and
>> > > it's
>> > > sufficient to use --no-install-recommends and the existing series
>> was
>> > > upgrade just fine.
>> > >
>> >
>> > I wonder why the 390xx legacy drivers are being pulled now. It
>> > definitely was not the case when I initially setup my machine with
>> an
>> > older version of nvidia current.
>> >
>> > Indeed, `apt install --no-install-recommends bumblebee-nvidia
>> primus`
>> > does not pull the 390xx series.
>>
>> As the changelog says, it's to have a smooth update for i386 as the
>> mainline doesn't support it anymore.
>
> I wonder whether the upgrade path really is that smooth though.
>
> Afterall, both Stefan and I experienced conflicts in the upgrade
> process on the very same packages (nvidia-nonglvnd-vulkan-common and
> primus). Less experienced users may not feel confident performing the
> upgrade as a result, either by `synaptic` or `apt full-upgrade`
>
> Maybe displaying an explanation for this particular upgrade via
> NEWS.Debian could help? AFAIC, I was not aware that NVIDIA had indeed
> dropped support for 32-bit after release 390 of the drivers.
>
> Cheers,
> Ghis
>
>

Reply | Threaded
Open this post in threaded view
|

Bug#929521: Conflicts in upgrade to 418.74-1 with optimus setup

Andreas Beckmann-4
On 2019-05-28 09:40, Stefan Tsanev wrote:
> I agree with Ghis, maybe a little more information before this update
> could be in great use here. Some people with bumblebee and enabled
> multiarch may find difficulties understanding why their system doesn't
> want to continue updating anymore via apt. I sitll feel odd about this
> upgrade and I'm glad, that I'm not the only one.

In most cases you would not care about the removed support for i386. You
would care about removed support for your GPU - you will get notified
about this (news (always) and debconf (if legacy hardware present) and
that you need to switch to the legacy driver.
amd64 + foreign arch i386 is not (yet) part of our test matrix ...

Could someone please define the minimal set of packages to be installed
for a working optimus setup, as there is probably no metapackage
covering that. I.e. something that I can run in a minimal chroot to test
upgrades afterwards. I need this for both stretch and buster. (And an
upgrade from stretch usually should result in the buster set being
installed.)

e.g.

stretch# apt-get install --install-recommends bumblebee-nvidia


Thanks

Andreas

Reply | Threaded
Open this post in threaded view
|

Bug#929521: Conflicts in upgrade to 418.74-1 with optimus setup

Luca Boccassi-3
On Wed, 2019-05-29 at 12:25 +0200, Andreas Beckmann wrote:

> On 2019-05-28 09:40, Stefan Tsanev wrote:
> > I agree with Ghis, maybe a little more information before this
> > update
> > could be in great use here. Some people with bumblebee and enabled
> > multiarch may find difficulties understanding why their system
> > doesn't
> > want to continue updating anymore via apt. I sitll feel odd about
> > this
> > upgrade and I'm glad, that I'm not the only one.
>
> In most cases you would not care about the removed support for i386.
> You
> would care about removed support for your GPU - you will get notified
> about this (news (always) and debconf (if legacy hardware present)
> and
> that you need to switch to the legacy driver.
> amd64 + foreign arch i386 is not (yet) part of our test matrix ...
>
> Could someone please define the minimal set of packages to be
> installed
> for a working optimus setup, as there is probably no metapackage
> covering that. I.e. something that I can run in a minimal chroot to
> test
> upgrades afterwards. I need this for both stretch and buster. (And an
> upgrade from stretch usually should result in the buster set being
> installed.)
>
> e.g.
>
> stretch# apt-get install --install-recommends bumblebee-nvidia
>
>
> Thanks
>
> Andreas
Hi, this should be the list:

bbswitch bumblebee bumblebee-nvidia primus primus-libs primus-libs-ia32
nvidia-driver-libs-nonglvnd nvidia-driver-libs-nonglvnd-i386

--
Kind regards,
Luca Boccassi

signature.asc (499 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Bug#929521: Conflicts in upgrade to 418.74-1 with optimus setup

Andreas Beckmann-4
On 07/06/2019 18.12, Luca Boccassi wrote:
> Hi, this should be the list:
>
> bbswitch bumblebee bumblebee-nvidia primus primus-libs primus-libs-ia32
> nvidia-driver-libs-nonglvnd nvidia-driver-libs-nonglvnd-i386

Is this documented somewhere?

This can be minimized to
  apt-get install --install-recommends \
    nvidia-driver-libs-nonglvnd bumblebee-nvidia primus
if i386 is available as a foreign architecture.

That makes me think: should we have a primus-nvidia metapackage that
depends on these packages?

Which component in this stack did not work with libgl1-nvidia-glvnd-glx?
According to the existing Breaks this should be primus ...

Running
  apt-get install --install-recommends bumblebee-nvidia primus
in a minimal *stretch* chroot results in the installation of
  nvidia-driver nvidia-driver-libs libgl1-glvnd-nvidia-glx ...
which does not give a working setup?

Running
  apt-get install --install-recommends bumblebee-nvidia primus
in a minimal *buster* chroot results in the installation of
nvidia-kernel-dkms, but no driver or library components, which does not
sound useful either.

I'll send some piuparts logs to this bug later, dropping all Cc:s.
Testing stretch->buster upgrades with
* foreign arch i386 enabled and
* --install-recommends enabled
of the package set nvidia-driver-libs-nonglvnd bumblebee-nvidia primus
did not show problems. It pulled in some legacy-390xx packages, but not
the 390xx driver itself. It will be hard to reproduce the problem people
exerienced with some transient set of packages from testing installed.

We will probably have to review the Depends/Recommends/Suggests in the
bumblebee and primus packages ... to better cope with the driver:i386
removal.


Andreas

Reply | Threaded
Open this post in threaded view
|

Bug#929521: Conflicts in upgrade to 418.74-1 with optimus setup

Andreas Beckmann-4
On 11/06/2019 00.21, Andreas Beckmann wrote:
> I'll send some piuparts logs to this bug later, dropping all Cc:s.

This is a piuparts log upgrading from stretch (amd64 + foreign: i386) to
buster, with --install-recommends enabled of the package list
  nvidia-driver-libs-nonglvnd bumblebee-nvidia primus bbswitch
I do not see misbehavior in this case, but perhaps someone else can spot
something ...


Andreas

nv.5.log.gz (169K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Bug#929521: Conflicts in upgrade to 418.74-1 with optimus setup

Luca Boccassi-3
In reply to this post by Andreas Beckmann-4
On Tue, 2019-06-11 at 00:21 +0200, Andreas Beckmann wrote:

> On 07/06/2019 18.12, Luca Boccassi wrote:
> > Hi, this should be the list:
> >
> > bbswitch bumblebee bumblebee-nvidia primus primus-libs primus-libs-
> > ia32
> > nvidia-driver-libs-nonglvnd nvidia-driver-libs-nonglvnd-i386
>
> Is this documented somewhere?
>
> This can be minimized to
>   apt-get install --install-recommends \
>     nvidia-driver-libs-nonglvnd bumblebee-nvidia primus
> if i386 is available as a foreign architecture.
>
> That makes me think: should we have a primus-nvidia metapackage that
> depends on these packages?
>
> Which component in this stack did not work with libgl1-nvidia-glvnd-
> glx?
> According to the existing Breaks this should be primus ...
>
> Running
>   apt-get install --install-recommends bumblebee-nvidia primus
> in a minimal *stretch* chroot results in the installation of
>   nvidia-driver nvidia-driver-libs libgl1-glvnd-nvidia-glx ...
> which does not give a working setup?
>
> Running
>   apt-get install --install-recommends bumblebee-nvidia primus
> in a minimal *buster* chroot results in the installation of
> nvidia-kernel-dkms, but no driver or library components, which does
> not
> sound useful either.
>
> I'll send some piuparts logs to this bug later, dropping all Cc:s.
> Testing stretch->buster upgrades with
> * foreign arch i386 enabled and
> * --install-recommends enabled
> of the package set nvidia-driver-libs-nonglvnd bumblebee-nvidia
> primus
> did not show problems. It pulled in some legacy-390xx packages, but
> not
> the 390xx driver itself. It will be hard to reproduce the problem
> people
> exerienced with some transient set of packages from testing
> installed.
>
> We will probably have to review the Depends/Recommends/Suggests in
> the
> bumblebee and primus packages ... to better cope with the driver:i386
> removal.
>
>
> Andreas
In theory, "apt install bumblebee-nvidia" should do the right thing.
The problem is that we can't depend directly from primus-libs to
nvidia-driver-libs-nonglvnd as the former is in main and the latter in
non-free, so at the moment we try to "nudge" apt with breaks and
suggests:

Breaks:
 libgl1-nvidia-glvnd-glx (>= 0),
 nvidia-driver-libs (>= 0),
 libgl1-nvidia-legacy-390xx-glvnd-glx (>= 0),
 nvidia-legacy-390xx-driver-libs (>= 0),
Suggests:
 nvidia-driver-libs-nonglvnd | nvidia-legacy-390xx-driver-libs-nonglvnd

This obviously doesn't seem to work reliably all the time...

Originally the point of bumblebee and primus in main was that they were
needed for the noveau stack as well. But nowadays as far as I know
DRI_PRIME is the better choice for noveau, for recent hardware. I
wonder if we should simply move primus and bumblebee to non-free so
that we can have a working set of dependencies?

But also note that upstream is going to deprecate non-glvnd after 430,
so optimus users will be stuck with whatever legacy release we cut
before that:

https://devtalk.nvidia.com/default/topic/1032650/linux/unix-graphics-feature-deprecation-schedule/

--
Kind regards,
Luca Boccassi

signature.asc (499 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Bug#929521: Conflicts in upgrade to 418.74-1 with optimus setup

Andreas Beckmann-4
On 11/06/2019 12.21, Luca Boccassi wrote:

> On Tue, 2019-06-11 at 00:21 +0200, Andreas Beckmann wrote:
>> On 07/06/2019 18.12, Luca Boccassi wrote:
>>> Hi, this should be the list:
>>>
>>> bbswitch bumblebee bumblebee-nvidia primus primus-libs primus-libs-
>>> ia32
>>> nvidia-driver-libs-nonglvnd nvidia-driver-libs-nonglvnd-i386
>>
>> Is this documented somewhere?
>>
>> This can be minimized to
>>   apt-get install --install-recommends \
>>     nvidia-driver-libs-nonglvnd bumblebee-nvidia primus
>> if i386 is available as a foreign architecture.
>>
>> That makes me think: should we have a primus-nvidia metapackage that
>> depends on these packages?

I've now prepared such a metapackage in git. Does this look sensible?
The description was copied from bumblebee-nvidia which is probably not
optimal. Perhaps you can tune it a bit.

Andreas

Reply | Threaded
Open this post in threaded view
|

Bug#929521: Conflicts in upgrade to 418.74-1 with optimus setup

Luca Boccassi-3
On Wed, 31 Jul 2019 at 21:32, Andreas Beckmann <[hidden email]> wrote:

>
> On 11/06/2019 12.21, Luca Boccassi wrote:
> > On Tue, 2019-06-11 at 00:21 +0200, Andreas Beckmann wrote:
> >> On 07/06/2019 18.12, Luca Boccassi wrote:
> >>> Hi, this should be the list:
> >>>
> >>> bbswitch bumblebee bumblebee-nvidia primus primus-libs primus-libs-
> >>> ia32
> >>> nvidia-driver-libs-nonglvnd nvidia-driver-libs-nonglvnd-i386
> >>
> >> Is this documented somewhere?
> >>
> >> This can be minimized to
> >>   apt-get install --install-recommends \
> >>     nvidia-driver-libs-nonglvnd bumblebee-nvidia primus
> >> if i386 is available as a foreign architecture.
> >>
> >> That makes me think: should we have a primus-nvidia metapackage that
> >> depends on these packages?
>
> I've now prepared such a metapackage in git. Does this look sensible?
> The description was copied from bumblebee-nvidia which is probably not
> optimal. Perhaps you can tune it a bit.
>
> Andreas

Hi,

Thanks - looks good to me, even the description seems fine.

Thanks!