Bug#1005311: This bug also affects experimental version 510.47.03-1

2022-02-23 Thread Christian Weeks
This bug also affects experimental version 510.47.03-1 - it looks like the
dependencies need updating on the experimental driver as well.



Bug#1005311: forcing dependency is not enough, at least for optirun

2022-02-23 Thread Aniol Martí
On Mon, 14 Feb 2022 20:31:33 +0100 Gianluigi Tiesi  
wrote:

optirun glxinfo

optirun glxinfo
[ 1566.529702] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) Unable to locate/open config directory: 
"/etc/bumblebee/xorg.conf.d"


[ 1566.529735] [ERROR]Aborting because fallback start is disabled.


in xorg log:

[  1566.527] (II) NVIDIA dlloader X Driver  470.103.01  Thu Jan  6 12:18:33 UTC 
2022
[  1566.527] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[  1566.529] (EE) No devices detected.
[  1566.529] (EE)
Fatal server error:
[  1566.529] (EE) no screens found(EE)
[  1566.529] (EE)

perhaps nvidia module loads:

[ 1566.540788] nvidia :01:00.0: enabling device ( -> 0003)
[ 1566.540886] nvidia :01:00.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=none:owns=none
[ 1566.587576] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  470.103.01  Thu 
Jan  6 12:10:04 UTC 2022



I solved it manually setting the BusID in /etc/bumblebee/xorg.conf.nvidia.

To find the BusID run `lspci | egrep 'VGA|3D'`. You will get something 
like "03:00.0". Then, add BusID "PCI:03:00:0" to 
/etc/bumblebee/xorg.conf.nvidia (note that you need to change the dot to 
a colon).


After doing this primusrun worked again.



Bug#1005311:

2022-02-19 Thread KeyofBlueS
Hi, I tested the nvidia legacy 340.108-12+b1 driver with
xserver-xorg-core 2:21.1.3-2+b1 (xorg-video-abi-25) and it seems it's
working fine by just adding:

Section "ServerFlags"
  Option "IgnoreABI" "1"
EndSection

in /etc/X11/xorg.conf.d/20-nvidia.conf


Is there hope that the legacy 340.108 driver will still be supported
by debian sid? Andreas Beckmann? please?

Thanks and best regards.


Bug#1005311: forcing dependency is not enough, at least for optirun

2022-02-14 Thread Gianluigi Tiesi

optirun glxinfo

optirun glxinfo
[ 1566.529702] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) Unable to locate/open config directory: 
"/etc/bumblebee/xorg.conf.d"


[ 1566.529735] [ERROR]Aborting because fallback start is disabled.


in xorg log:

[  1566.527] (II) NVIDIA dlloader X Driver  470.103.01  Thu Jan  6 12:18:33 UTC 
2022
[  1566.527] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[  1566.529] (EE) No devices detected.
[  1566.529] (EE)
Fatal server error:
[  1566.529] (EE) no screens found(EE)
[  1566.529] (EE)

perhaps nvidia module loads:

[ 1566.540788] nvidia :01:00.0: enabling device ( -> 0003)
[ 1566.540886] nvidia :01:00.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=none:owns=none
[ 1566.587576] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  470.103.01  Thu 
Jan  6 12:10:04 UTC 2022


--
Gianluigi Tiesi 
Chief Technology Officer
Netfarm S.r.l. - https://www.netfarm.it/
Free Software: https://oss.netfarm.it/

Q: Because it reverses the logical flow of conversation.
A: Why is putting a reply at the top of the message frowned upon?



Bug#1005311: marked as done (xserver-xorg-video-nvidia: Package has unmet dependencies)

2022-02-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Feb 2022 22:49:33 +
with message-id 
and subject line Bug#1005311: fixed in nvidia-graphics-drivers 470.103.01-2
has caused the Debian Bug report #1005311,
regarding xserver-xorg-video-nvidia: Package has unmet dependencies
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1005311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005311
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xserver-xorg-video-nvidia
Version: 470.103.01-1
Severity: important

When I try to install the nvidia-driver package, I get a unmet dependency
error. xserver-xorg-video-nvidia can't be installed because of unmet
depedencies (see below).

sudo apt install xserver-xorg-video-nvidia
Package lists are read... Done
Dependency tree is built... Done
Status information is read... Done
Some packages could not be installed. This may mean that
that you have requested an impossible situation or, if you are using the
unstable distribution, that some required packages have not been built
yet or
that
have not been built or have not left Incoming yet.
The following information may help you resolve the situation:

The following packages have unfulfilled dependencies:
  xserver-xorg-video-nvidia : Depends on: xorg-video-abi-24 or
     xorg-video-abi-23 but is not
installable or
     xorg-video-abi-20 but is not
installable or
     xorg-video-abi-19 is not
installable or
     xorg-video-abi-18 but cannot be
installed or
     xorg-video-abi-15 but cannot be
installed or
     xorg-video-abi-14 is not
installable or
     xorg-video-abi-13 but cannot be
installed or
     xorg-video-abi-12 but cannot be
installed or
     xorg-video-abi-11 is not
installable or
     xorg-video-abi-10 is not
installable or
     xorg-video-abi-8 is not
installable
or
     xorg-video-abi-6.0 but not
installable
  Depends on: xserver-xorg-core (<
2:1.20.99) but
2:21.1.3-2 should be installed
  Recommends: nvidia-driver (>= 470.103.01) but
should not be installed
  Recommends: nvidia-vdpau-driver (>=
470.103.01)
but should not be installed
  Recommends: nvidia-kernel-dkms (=
470.103.01-1)
but should not be installed or
     nvidia-kernel-470.103.01
  Recommends: nvidia-settings (>= 470) but
should
not be installed
E: Problems cannot be corrected, you have retained broken packages.

The problem are unmet dependecies

sudo apt install nvidia-driver
Package lists are read... Done
Dependency tree is built... Done
Status information is read... Done
Some packages could not be installed. This may mean that
that you have requested an impossible situation or, if you are using the
unstable distribution, that some required packages have not been built
yet or
that
have not been built or have not left Incoming yet.
The following information may help you resolve the situation:

The following packages have unfulfilled dependencies:
  xserver-xorg-video-nvidia : Depends on: xorg-video-abi-24 or
     xorg-video-abi-23 but is not
installable or
     xorg-video-abi-20 but is not
installable or
     xorg-video-abi-19 is not
installable or
     xorg-video-abi-18 but cannot be
installed or
     xorg-video-abi-15 but cannot be
installed or
     xorg-video-abi-14 is not
installable or
     xorg-video-abi-13 but cannot be
installed or
     xorg-video-abi-12 but cannot be
installed or
     xorg-video-abi-11 is not
installable or
     xorg-video-abi-10 is not
installable or
     xorg-video-abi-8 is not

Bug#1005311:

2022-02-13 Thread Magnus Ekdahl
Thanks Dan,

$apt download xserver-xorg-video-nvidia nvidia-driver
$sudo dpkg -i --force-depends nvidia-driver*.deb
$sudo dpkg -i --force-depends xserver-xorg-video-nvidia*.deb

is indeed a workaround.

kind regards
Magnus


Den sön 13 feb. 2022 kl 15:54 skrev Dan Chokola :

> > This has been open for almost 2 days now. Is there a workaround for this 
> > bug?
>
> I used `dpkg --force-depends ...` to install the nvidia packages I needed
> alongside the current version of Xorg and all has been working fine for the
> past few days. If there is a difference in the ABI, it hasn't caused me any
> trouble yet.
>
> --
> Dan Chokola
>


-- 
Magnus Ekdahl


Bug#1005311:

2022-02-13 Thread Dan Chokola
> This has been open for almost 2 days now. Is there a workaround for this bug?

I used `dpkg --force-depends ...` to install the nvidia packages I needed
alongside the current version of Xorg and all has been working fine for the
past few days. If there is a difference in the ABI, it hasn't caused me any
trouble yet.

-- 
Dan Chokola


Bug#1005311: Workaround

2022-02-12 Thread Magnus Ekdahl
This has been open for almost 2 days now. Is there a workaround for this
bug?

-- 
Magnus Ekdahl