*** This bug is a duplicate of bug 2155202 ***
https://bugs.launchpad.net/bugs/2155202
Thanks José, duplicate status makes sense.
To answer your question: I do not mean that the Discourse post is wrong
or incomplete as the policy announcement. I mean discoverability at the
point where affected users are likely to encounter the problem.
In practice, a Jammy / Mint 21.3 user with a Kepler card may not know to
look for that Discourse post before running normal package or driver-
manager updates. From the user side, `nvidia-driver-470` still looks
like the relevant package name, but the transition can lead toward 535,
which this hardware cannot use.
So the useful extra documentation would be somewhere closer to the
migration path, for example:
1. a note in the affected Launchpad bug / release-update context;
2. guidance in or near `ubuntu-drivers` / Driver Manager output where possible;
3. package or upgrade notes warning that 470 to 535 is not a functional
migration for Kepler hardware;
4. clear mention that affected users should choose between nouveau, the NVIDIA
`.run` legacy installer with its risks, or holding/pinning existing packages at
their own risk.
I understand there is no hardware detection mechanism in apt, and that
Canonical/Ubuntu is retiring the packaged 470 branch. My main point is
that the failure mode is currently surprising: the package name suggests
“470”, but the resulting path can point users at a branch that their GPU
will ignore.
Thanks for clarifying the intended policy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2155424
Title:
Question: nvidia-driver-470 on Jammy resolves to 535 on GTX 760;
should users be directed to 470-server instead?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2155424/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
