Why all the fear?
Hey Geekos, First of all, sorry for this cross-post, but it is relevant to all of the lists specified. I am just wondering if my experience is so much different, or if I use the distro differently than other users, that it seems so much stable for me. Often i see people recommending against "zypper dup", recommending "tumbleweed-cli" instead of "zypper dup", using "opi" for codecs install instead of 1-click install on opensuse-community, and so on, because the system "could" or "will for sure" break at some time. Why there is a need for all this fancy and new stuff and is it possible that these combinations and diversity increases possibility for issues? Given all of these, I should have had my home machines broken already a million times and burned to death. - I am using Tumbleweed - I have all these repositories enabled: [1] (yes, no priorities currently) - I have "zypper dup", "zypper inr", "zypper ve" in my daily cron job - I have enabled vendor changes in zypper conf - I have disabled multiversion.kernel in zypper conf (keeps kernel packages with their dependencies and/or DKMS clean and working) - I have disabled snapper as a whole - I have installed some VMWare software from their crappy .run packages, which means some parts are compiled from source During my over-15 years-long experience with *SUSE, i never experienced an unbootable system or a serious issue, except: - Nvidia driver issues before they were packaged for *SUSE and you had to use the .run installation ( ancient SaX2 times, before Xorg autoconfiguration ). On my gaming system i have just enabled nvidia repos and forgot about it. - Akonadi issues because of my experiments with bleeding edge mariadb in combination with my mailbox containing few million e-mails, also many years back - Btrfs issues (total system crash) when it was unstable and i had enabled snapper an ran out of space - which was resolved by reinstall and re-mounting my /home/ (i am not using snapper since then) So my question is - have the RPM dependencies gone weaker than they were "before" or something? Could that combination of all the emergency safe features, like btrfs snapshots in combination with multiversion kernel and/or packages, tumbleweed-cli, opi, etc...? Why are RPM deps not enough to keep the system solid anymore? My experience with *SUSE has always been rock-solid-stable and one of the very few things i do manually from time to time is firing up yast2 sw_single, removing unmaintained packages and checking change-logs of some packages i am interested/care of. Take this as a congrats and thanks for all the maintainers, developers and everyone taking care. And most importantly, the OBS, which does pretty neat job with automatic package dependencies and all that stuff. One more time - thank you OBS and all the people developing and working on it! :) And while i am doing this braindump, please revive SUSE Studio :P :) And last, but not least - thanks Packman people :) [1]: https://paste.opensuse.org/view/raw/38599835 Regards, Gryffus
No fear here. While I do run zypper dup only manually, and now and then do check the list here *before* doing so ;^>, I do find Tumbleweed plus zypper the most stable installation since I use Linux (which is more than 28 years now). I especially like the rock solid way zypper handles dependencies with a multitude of repositories (I have 17 enabled). I leave snapper installed. Sometimes it's handy to have old files around to compare. But I've only done one rollback so far (using TW since 2016, by now on 6 machines, including one Pi4). That was due to some nvidia failure, too. Plus some smaller ones, like old sddm cache crashing it after the update. There's also issues sometimes with unresolvable dependencies, where I'm asked for a choice how to resolve. I prefer that over taking one choice automatically, as I *know* that would not be my choice in at least some cases. But there we are already in the field of 'stable for whom?' The above cases I regard as minor glitches - newbies might well break into sweat over some of them. In that respect, stability is (also) a question of experience, IMO. Nevertheless, the 'makers' are doing an absolutely fabulous job with TW!
* Peter Suetterlin
No fear here. While I do run zypper dup only manually, and now and then do check the list here *before* doing so ;^>, I do find Tumbleweed plus zypper the most stable installation since I use Linux (which is more than 28 years now). I especially like the rock solid way zypper handles dependencies with a multitude of repositories (I have 17 enabled). I leave snapper installed. Sometimes it's handy to have old files around to compare. But I've only done one rollback so far (using TW since 2016, by now on 6 machines, including one Pi4). That was due to some nvidia failure, too. Plus some smaller ones, like old sddm cache crashing it after the update.
There's also issues sometimes with unresolvable dependencies, where I'm asked for a choice how to resolve. I prefer that over taking one choice automatically, as I *know* that would not be my choice in at least some cases.
But there we are already in the field of 'stable for whom?' The above cases I regard as minor glitches - newbies might well break into sweat over some of them. In that respect, stability is (also) a question of experience, IMO.
Nevertheless, the 'makers' are doing an absolutely fabulous job with TW!
Also my experiences and kudos to the 'makers'. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
On 6/2/22 07:50, Patrick Shanahan wrote:
* Peter Suetterlin
[06-02-22 07:40]: No fear here. While I do run zypper dup only manually, and now and then do check the list here *before* doing so ;^>, I do find Tumbleweed plus zypper the most stable installation since I use Linux (which is more than 28 years now). I especially like the rock solid way zypper handles dependencies with a multitude of repositories (I have 17 enabled). I leave snapper installed. Sometimes it's handy to have old files around to compare. But I've only done one rollback so far (using TW since 2016, by now on 6 machines, including one Pi4). That was due to some nvidia failure, too. Plus some smaller ones, like old sddm cache crashing it after the update.
There's also issues sometimes with unresolvable dependencies, where I'm asked for a choice how to resolve. I prefer that over taking one choice automatically, as I *know* that would not be my choice in at least some cases.
But there we are already in the field of 'stable for whom?' The above cases I regard as minor glitches - newbies might well break into sweat over some of them. In that respect, stability is (also) a question of experience, IMO.
Nevertheless, the 'makers' are doing an absolutely fabulous job with TW!
Also my experiences and kudos to the 'makers'.
The above matches my experience. For a period of time, my nVidia graphics adapter did not work with neauvue, thus I had to grapple with fixing the proprietary driver because the nVidia developers were ALWAYS slow in making the changes required by kernel API changes. Fortunately, my experience maintaining VirtualBox helped. Now, my G04 graphics adapter works with the kernel driver. :) I must admit that seeing a 'sudo zypper dup' calling for 2 or 3 thousand new packages could be frightening, but knowing that the snapshot has been vetted by QA makes it easier. Larry
been using linux since it was alpha in 1994 , and switched to suse as my
primary os since ver 6.1 , and followed its many changes , ups and downs
over the years to TW
love the os , many thanks to all the devs over the years
its fair to say i also do a zypper dup , rather than the kde install
updates on the task bar , maybe it would be a good idea to incorporate the
zypper dup functionality within that ,
and as for nvidia drivers , well since nvidia have open sourced there
drivers maybe we can start to see them integrated into yast sometime saving
the proprietary install , hopefully without licencing issues
David
On Thu, 2 Jun 2022 at 16:26, Larry Finger
* Peter Suetterlin
[06-02-22 07:40]: No fear here. While I do run zypper dup only manually, and now and
On 6/2/22 07:50, Patrick Shanahan wrote: then do
check the list here *before* doing so ;^>, I do find Tumbleweed plus zypper the most stable installation since I use Linux (which is more than 28 years now). I especially like the rock solid way zypper handles dependencies with a multitude of repositories (I have 17 enabled). I leave snapper installed. Sometimes it's handy to have old files around to compare. But I've only done one rollback so far (using TW since 2016, by now on 6 machines, including one Pi4). That was due to some nvidia failure, too. Plus some smaller ones, like old sddm cache crashing it after the update.
There's also issues sometimes with unresolvable dependencies, where I'm asked for a choice how to resolve. I prefer that over taking one choice automatically, as I *know* that would not be my choice in at least some cases.
But there we are already in the field of 'stable for whom?' The above cases I regard as minor glitches - newbies might well break into sweat over some of them. In that respect, stability is (also) a question of experience, IMO.
Nevertheless, the 'makers' are doing an absolutely fabulous job with TW!
Also my experiences and kudos to the 'makers'.
The above matches my experience. For a period of time, my nVidia graphics adapter did not work with neauvue, thus I had to grapple with fixing the proprietary driver because the nVidia developers were ALWAYS slow in making the changes required by kernel API changes. Fortunately, my experience maintaining VirtualBox helped. Now, my G04 graphics adapter works with the kernel driver. :)
I must admit that seeing a 'sudo zypper dup' calling for 2 or 3 thousand new packages could be frightening, but knowing that the snapshot has been vetted by QA makes it easier.
Larry
On 6/3/22 20:11, David Powell wrote:
been using linux since it was alpha in 1994 , and switched to suse as my primary os since ver 6.1 , and followed its many changes , ups and downs over the years to TW love the os , many thanks to all the devs over the years
its fair to say i also do a zypper dup , rather than the kde install updates on the task bar , maybe it would be a good idea to incorporate the zypper dup functionality within that , and as for nvidia drivers , well since nvidia have open sourced there drivers maybe we can start to see them integrated into yast sometime saving the proprietary install , hopefully without licencing issues
I started using SuSE because it had reiserfs built in. If you have ever waited while fssck fixed a 20 or 40 MB disk with an ext2 fs after a crash, you know how valuable it was to have a journaling file system. I had come from the DEC world, where such file systems were standard. I think I started with the 5.X versions. Of course, I switched to ext3, and then ext4 as soon as those file systems were available. Whenever I need to load one of the other distros for some reason, I am very thankful for SuSE of openSUSE, no matter what it is called. If nVidia had open-sourced their drivers, they would be a part of the kernel the way that Intel i915 drivers are. YaST would not be involved. The nouveau project has been a tour de force in that they did no reverse engineering. Everything was generated by observing what changed in the display when the display memory was manipulated. A difficult way, but free of any legal problems. Larry
""If nVidia had open-sourced their drivers, they would be a part of the
kernel the
way that Intel i915 drivers are."" news is
https://github.com/NVIDIA/open-gpu-kernel-modules and
https://github.com/NVIDIA/open-gpu-kernel-modules/releases/tag/515.48.07
although personally i have not had time to upgrade or test these drivers ,
but it is official
On Sat, 4 Jun 2022 at 03:54, Larry Finger
been using linux since it was alpha in 1994 , and switched to suse as my
os since ver 6.1 , and followed its many changes , ups and downs over
On 6/3/22 20:11, David Powell wrote: primary the years
to TW love the os , many thanks to all the devs over the years
its fair to say i also do a zypper dup , rather than the kde install updates on the task bar , maybe it would be a good idea to incorporate the zypper dup functionality within that , and as for nvidia drivers , well since nvidia have open sourced there drivers maybe we can start to see them integrated into yast sometime saving the proprietary install , hopefully without licencing issues
I started using SuSE because it had reiserfs built in. If you have ever waited while fssck fixed a 20 or 40 MB disk with an ext2 fs after a crash, you know how valuable it was to have a journaling file system. I had come from the DEC world, where such file systems were standard. I think I started with the 5.X versions. Of course, I switched to ext3, and then ext4 as soon as those file systems were available.
Whenever I need to load one of the other distros for some reason, I am very thankful for SuSE of openSUSE, no matter what it is called.
If nVidia had open-sourced their drivers, they would be a part of the kernel the way that Intel i915 drivers are. YaST would not be involved. The nouveau project has been a tour de force in that they did no reverse engineering. Everything was generated by observing what changed in the display when the display memory was manipulated. A difficult way, but free of any legal problems.
Larry
and sorry i ment as a yast package (rpm) not a part of yast directly
david
On Sat, 4 Jun 2022 at 04:31, David Powell
""If nVidia had open-sourced their drivers, they would be a part of the kernel the way that Intel i915 drivers are."" news is https://github.com/NVIDIA/open-gpu-kernel-modules and https://github.com/NVIDIA/open-gpu-kernel-modules/releases/tag/515.48.07 although personally i have not had time to upgrade or test these drivers , but it is official
On Sat, 4 Jun 2022 at 03:54, Larry Finger
wrote: been using linux since it was alpha in 1994 , and switched to suse as my primary os since ver 6.1 , and followed its many changes , ups and downs over
On 6/3/22 20:11, David Powell wrote: the years
to TW love the os , many thanks to all the devs over the years
its fair to say i also do a zypper dup , rather than the kde install updates on the task bar , maybe it would be a good idea to incorporate the zypper dup functionality within that , and as for nvidia drivers , well since nvidia have open sourced there drivers maybe we can start to see them integrated into yast sometime saving the proprietary install , hopefully without licencing issues
I started using SuSE because it had reiserfs built in. If you have ever waited while fssck fixed a 20 or 40 MB disk with an ext2 fs after a crash, you know how valuable it was to have a journaling file system. I had come from the DEC world, where such file systems were standard. I think I started with the 5.X versions. Of course, I switched to ext3, and then ext4 as soon as those file systems were available.
Whenever I need to load one of the other distros for some reason, I am very thankful for SuSE of openSUSE, no matter what it is called.
If nVidia had open-sourced their drivers, they would be a part of the kernel the way that Intel i915 drivers are. YaST would not be involved. The nouveau project has been a tour de force in that they did no reverse engineering. Everything was generated by observing what changed in the display when the display memory was manipulated. A difficult way, but free of any legal problems.
Larry
sorry for another post on the subject , the official announcement is at
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-mod...
although it may leave a void for legacy cards needing the older non
opensouce drivers still
david
On Sat, 4 Jun 2022 at 04:35, David Powell
and sorry i ment as a yast package (rpm) not a part of yast directly
david
On Sat, 4 Jun 2022 at 04:31, David Powell
wrote: ""If nVidia had open-sourced their drivers, they would be a part of the kernel the way that Intel i915 drivers are."" news is https://github.com/NVIDIA/open-gpu-kernel-modules and https://github.com/NVIDIA/open-gpu-kernel-modules/releases/tag/515.48.07 although personally i have not had time to upgrade or test these drivers , but it is official
On Sat, 4 Jun 2022 at 03:54, Larry Finger
wrote: been using linux since it was alpha in 1994 , and switched to suse as my primary os since ver 6.1 , and followed its many changes , ups and downs over
to TW love the os , many thanks to all the devs over the years
its fair to say i also do a zypper dup , rather than the kde install updates on the task bar , maybe it would be a good idea to incorporate the zypper dup functionality within that , and as for nvidia drivers , well since nvidia have open sourced there drivers maybe we can start to see them integrated into yast sometime saving
On 6/3/22 20:11, David Powell wrote: the years the
proprietary install , hopefully without licencing issues
I started using SuSE because it had reiserfs built in. If you have ever waited while fssck fixed a 20 or 40 MB disk with an ext2 fs after a crash, you know how valuable it was to have a journaling file system. I had come from the DEC world, where such file systems were standard. I think I started with the 5.X versions. Of course, I switched to ext3, and then ext4 as soon as those file systems were available.
Whenever I need to load one of the other distros for some reason, I am very thankful for SuSE of openSUSE, no matter what it is called.
If nVidia had open-sourced their drivers, they would be a part of the kernel the way that Intel i915 drivers are. YaST would not be involved. The nouveau project has been a tour de force in that they did no reverse engineering. Everything was generated by observing what changed in the display when the display memory was manipulated. A difficult way, but free of any legal problems.
Larry
supprisingly without effort , already using the 515 driver it must of
updated last week on my zapper dup (had not noticed), from the enabled
nvidia repo , was expecting a day or so messing arround installing the hard
way
maybe linux nvidia driver install problems are the new thing of the past
:)
david
On Sat, 4 Jun 2022 at 04:50, David Powell
sorry for another post on the subject , the official announcement is at https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-mod...
although it may leave a void for legacy cards needing the older non opensouce drivers still
david
On Sat, 4 Jun 2022 at 04:35, David Powell
wrote: and sorry i ment as a yast package (rpm) not a part of yast directly
david
On Sat, 4 Jun 2022 at 04:31, David Powell
wrote: ""If nVidia had open-sourced their drivers, they would be a part of the kernel the way that Intel i915 drivers are."" news is https://github.com/NVIDIA/open-gpu-kernel-modules and https://github.com/NVIDIA/open-gpu-kernel-modules/releases/tag/515.48.07 although personally i have not had time to upgrade or test these drivers , but it is official
On Sat, 4 Jun 2022 at 03:54, Larry Finger
wrote: been using linux since it was alpha in 1994 , and switched to suse as my primary os since ver 6.1 , and followed its many changes , ups and downs over the years to TW love the os , many thanks to all the devs over the years
its fair to say i also do a zypper dup , rather than the kde install updates on the task bar , maybe it would be a good idea to incorporate the zypper dup functionality within that , and as for nvidia drivers , well since nvidia have open sourced there drivers maybe we can start to see them integrated into yast sometime saving
On 6/3/22 20:11, David Powell wrote: the
proprietary install , hopefully without licencing issues
I started using SuSE because it had reiserfs built in. If you have ever waited while fssck fixed a 20 or 40 MB disk with an ext2 fs after a crash, you know how valuable it was to have a journaling file system. I had come from the DEC world, where such file systems were standard. I think I started with the 5.X versions. Of course, I switched to ext3, and then ext4 as soon as those file systems were available.
Whenever I need to load one of the other distros for some reason, I am very thankful for SuSE of openSUSE, no matter what it is called.
If nVidia had open-sourced their drivers, they would be a part of the kernel the way that Intel i915 drivers are. YaST would not be involved. The nouveau project has been a tour de force in that they did no reverse engineering. Everything was generated by observing what changed in the display when the display memory was manipulated. A difficult way, but free of any legal problems.
Larry
Am Samstag, 4. Juni 2022, 03:11:40 CEST schrieb David Powell:
and as for nvidia drivers , well since nvidia have open sourced there drivers maybe we can start to see them integrated into yast sometime saving the proprietary install , hopefully without licencing issues
Don't get too excited about this... II just tried that opensourced driver on two computers. #1: has a GTX 1050 (GP107) which should be supported by the open source driver - but it turns out it wasnt. #2: has a GTX 1650 Ti mobile (TU117M) - also not supported: the output in dmesg when I try to load the driver talks about the open source driver being only for "data center GPUs", so I guess that means it is only usable for CUDA usage but not as an actual graphics driver for desktop systems. Ah well, at least the binary driver is easy to install. And by that I dont mean running the binary installer, nvidia has been offering the binary driver AS RPM PACKAGES installable with yast/zypper for ... decades. Cheers MH -- Mathias Homann Mathias.Homann@openSUSE.org Jabber (XMPP): lemmy@tuxonline.tech Matrix: @mathias:eregion.de IRC: [Lemmy] on freenode and ircnet (bouncer active) keybase: https://keybase.io/lemmy gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102
On Sat 04 Jun 2022 08:27:58 AM CDT, Mathias Homann wrote:
Am Samstag, 4. Juni 2022, 03:11:40 CEST schrieb David Powell:
and as for nvidia drivers , well since nvidia have open sourced there drivers maybe we can start to see them integrated into yast sometime saving the proprietary install , hopefully without licencing issues
Don't get too excited about this...
II just tried that opensourced driver on two computers.
#1: has a GTX 1050 (GP107) which should be supported by the open source driver - but it turns out it wasnt.
#2: has a GTX 1650 Ti mobile (TU117M) - also not supported: the output in dmesg when I try to load the driver talks about the open source driver being only for "data center GPUs", so I guess that means it is only usable for CUDA usage but not as an actual graphics driver for desktop systems.
Ah well, at least the binary driver is easy to install. And by that I dont mean running the binary installer, nvidia has been offering the binary driver AS RPM PACKAGES installable with yast/zypper for ... decades.
Cheers MH
Hi For #2, did you add the modprobe.d "options nvidia NVreg_OpenRmEnableUnsupportedGpus=1" Runs here fine on my T400, just no power management so runs at full speed. -- Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890) Tumbleweed 20220602 | GNOME Shell 42.2 | 5.18.1-1-default HP Z440 | Xeon E5-2690 V3 X24 @ 2.60GHz | AMD RX550/Nvidia Quadro T400 up 22:11, 2 users, load average: 0.22, 0.27, 0.21
The GTX1050 is not supported. I use the nouveau modules on all cards including 2 FTX1050 and a GTX560 Ti. The github source README.md file lists all that is supported. I have a GTX1650 Ti which is listed. I built the source but have not yet tried using it. Regards Sid. On 04/06/2022 07:27, Mathias Homann wrote:
Am Samstag, 4. Juni 2022, 03:11:40 CEST schrieb David Powell:
and as for nvidia drivers , well since nvidia have open sourced there drivers maybe we can start to see them integrated into yast sometime saving the proprietary install , hopefully without licencing issues Don't get too excited about this...
II just tried that opensourced driver on two computers.
#1: has a GTX 1050 (GP107) which should be supported by the open source driver - but it turns out it wasnt.
#2: has a GTX 1650 Ti mobile (TU117M) - also not supported: the output in dmesg when I try to load the driver talks about the open source driver being only for "data center GPUs", so I guess that means it is only usable for CUDA usage but not as an actual graphics driver for desktop systems.
Ah well, at least the binary driver is easy to install. And by that I dont mean running the binary installer, nvidia has been offering the binary driver AS RPM PACKAGES installable with yast/zypper for ... decades.
Cheers MH
-- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks
On 6/4/22 01:27, Mathias Homann wrote:
Don't get too excited about this...
II just tried that opensourced driver on two computers.
#1: has a GTX 1050 (GP107) which should be supported by the open source driver - but it turns out it wasnt.
#2: has a GTX 1650 Ti mobile (TU117M) - also not supported: the output in dmesg when I try to load the driver talks about the open source driver being only for "data center GPUs", so I guess that means it is only usable for CUDA usage but not as an actual graphics driver for desktop systems.
Ah well, at least the binary driver is easy to install. And by that I dont mean running the binary installer, nvidia has been offering the binary driver AS RPM PACKAGES installable with yast/zypper for ... decades.
Cheers MH
Almost one of those "Too Good To Be True" moments. I suspect that even releasing source for older graphics cards would essentially provide the core of what nvidia does with its chips. You would think they would want the help of 100,000 additional coders for free, but their business model relies on extracting every last $$ from the gamers out there (and to a growing extent on harnessing all those wonderful cores in the parallel world, unless block-chain doesn't pan out) Here is to hoping next time it's something Linus can put in the kernel... -- David C. Rankin, J.D.,P.E.
from what i hear , from a leaked nvidia (shareholder presentation)
meeting recently , nvidia is making more $$ from the server side AI than
"gaming" gaming in "" as seems they know but wont say how much sailes of
rtx cards went to bitcoin miners but do know , and the crash of bit coin is
going to affect that in the coming months/years , so for us the outlook is
, firstly theres going to be a glut of rtx ex mining secondhand cards on
the market , that will affect new sails , and the hyped gpu prices are
already dropping , by next year maybe we will see rtx cards cheap enough to
upgrade to for most , linux well yea they need to do something that stops
there "oppinion" that most secondhand builders will use it on "old"
hardware , and want to have some competition over amd on that , as for the
drivers and code , seems the "confidential " core code has been moved from
the drivers into the cards bios on the newer cards to allow them to open
source the drivers without affecting there "3rd party NDA's " on the secret
bits , $$$ like any company is the goal , but it is customer satisfaction
and product function that is what in the end gets that , its easy to pick
on nvidia for that , but remeber amd,intel,etc are all in for the same
thing $$$, its taken time for nvidia to accept this is what users want
/need , and not doing it will long term affect that , long term with
community input i think most of the driver issues will be fixed /resolved ,
hopfully , then maybe linus will concidder including it in the kernel,
in the meantime its going to take a while for the community knowledge on
the drivers to build up and let's users write some good HOWTO's and install
issues and solutions to appear in forums etc for them
atm im doing game dev with UE5 ,, the min requirement for the game is
rtx20 or above , only getting 12fps in 4k on a rtx3080 in the editor atm
but its not optimised yet , but 1 to 2 years time when its released maybe
this is will be average for pc gaming not the top, linux compatible and
developing it on my TW system , but as it installed without issue i
cant say i found any solutions i needed to fix in doing it . unlike the 3
weeks it took getting ue5 editor to compile and work native in TW and not
flatpack
david
On Sun, 5 Jun 2022 at 08:32, David C. Rankin
On 6/4/22 01:27, Mathias Homann wrote:
Don't get too excited about this...
II just tried that opensourced driver on two computers.
#1: has a GTX 1050 (GP107) which should be supported by the open source driver - but it turns out it wasnt.
#2: has a GTX 1650 Ti mobile (TU117M) - also not supported: the output in dmesg when I try to load the driver talks about the open source driver being only for "data center GPUs", so I guess that means it is only usable for CUDA usage but not as an actual graphics driver for desktop systems.
Ah well, at least the binary driver is easy to install. And by that I dont mean running the binary installer, nvidia has been offering the binary driver AS RPM PACKAGES installable with yast/zypper for ... decades.
Cheers MH
Almost one of those "Too Good To Be True" moments. I suspect that even releasing source for older graphics cards would essentially provide the core of what nvidia does with its chips.
You would think they would want the help of 100,000 additional coders for free, but their business model relies on extracting every last $$ from the gamers out there (and to a growing extent on harnessing all those wonderful cores in the parallel world, unless block-chain doesn't pan out)
Here is to hoping next time it's something Linus can put in the kernel...
-- David C. Rankin, J.D.,P.E.
participants (9)
-
David C. Rankin
-
David Powell
-
Larry Finger
-
Lukáš Krejza
-
Malcolm
-
Mathias Homann
-
Patrick Shanahan
-
Peter Suetterlin
-
Sid Boyce