1. Rebooted after kernel upgrade: installation of nvidia-current driver
did not complete.
2. In run level 3, used drakx11 to change to nouveau driver. Reboot
successful but various things wanted the nvidia driver so:
3. Dowwnloaded the driver from nvidia site and ran it, but final stage
failed - unable to load nvidia-drm module.
4. A google suggested reloading kernel-desktop-devel. Used dnf to remove
it but dnf install kernel-desktop-devel-latest (or -5.15.6-2.mga8)
failed because of curl error 6 - could not resolve host www.mageia.org
!!!!
Now what?
--
Grimble
Machine 'Bach' running Plasma 5.20.4 on 5.15.6-desktop-2.mga8 kernel.
Mageia release 8 (Official) for x86_64

--- MBSE BBS v1.0.7.22 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 12/22/21 06:11, Grimble wrote:

1. Rebooted after kernel upgrade: installation of nvidia-current driver
did not complete.
2. In run level 3, used drakx11 to change to nouveau driver. Reboot successful but various things wanted the nvidia driver so:
3. Dowwnloaded the driver from nvidia site and ran it, but final stage failed - unable to load nvidia-drm module.
4. A google suggested reloading kernel-desktop-devel. Used dnf to remove
it but dnf install kernel-desktop-devel-latest (or -5.15.6-2.mga8)
failed because of  curl error 6 - could not resolve host www.mageia.org
!!!!
Now what?

Ehhh... wait until www.mageia.org is reachable.
I know waiting is painful but...

bliss

--
bliss dash SF 4 ever at dslextreme dot com

--- MBSE BBS v1.0.7.22 (GNU/Linux-x86_64)
* Origin: dis-organization (2:250/1@fidonet)

On 23/12/21 02:50, Bobbie Sellers wrote:

On 12/22/21 06:11, Grimble wrote:

1. Rebooted after kernel upgrade: installation of nvidia-current
driver did not complete.
2. In run level 3, used drakx11 to change to nouveau driver. Reboot
successful but various things wanted the nvidia driver so:
3. Dowwnloaded the driver from nvidia site and ran it, but final stage
failed - unable to load nvidia-drm module.

I haven't done it that way for years but I remember the nvidia
install would fail if the kernel headers / development files were not installed.

I would watch the command line install routine run on and then realize
I hadn't installed the Kernel headers and had to wait for the "failed" message.... totally pissed off

I have no idea how I did install the headers after that; the memory has gone


--
faeychild
Running plasmashell 5.20.4 on 5.15.6-desktop-2.mga8 kernel.
Mageia release 8 (Official) for x86_64 installed via Mageia-8-x86_64-DVD.iso


--- MBSE BBS v1.0.7.22 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 12/22/21 13:02, faeychild wrote:

On 23/12/21 02:50, Bobbie Sellers wrote:

On 12/22/21 06:11, Grimble wrote:

1. Rebooted after kernel upgrade: installation of nvidia-current
driver did not complete.
2. In run level 3, used drakx11 to change to nouveau driver. Reboot
successful but various things wanted the nvidia driver so:
3. Dowwnloaded the driver from nvidia site and ran it, but final
stage failed - unable to load nvidia-drm module.

 I haven't done it that way  for years but I remember the nvidia
install would fail if the kernel headers / development files were not installed.

 I would watch the command line install routine run on and then realize
I hadn't installed the Kernel headers and had to wait for the "failed" message.... totally pissed off

I have no idea how I did install the headers after that; the memory has
gone

Well I don't know what is going on with dnf since it is not my distribution except occassionally. I think if he has called the Noveau
driver he may have to blacklist it and remove it completely before the
correct nvidia driver can be used.
But waiting for the repository to be accessible seems to be
the way to start.

bliss

--
bliss dash SF 4 ever at dslextreme dot com

--- MBSE BBS v1.0.7.22 (GNU/Linux-x86_64)
* Origin: dis-organization (2:250/1@fidonet)

On 23/12/21 08:29, Bobbie Sellers wrote:

    Well I don't know what is going on with dnf since it is not my distribution except occassionally.   I think if he has called the Noveau driver he may have to blacklist it and remove it completely before the correct nvidia driver can be used.
    But waiting for the repository to be accessible seems to be
the way to start.

    bliss

DNF appeared on my radar when I had to run a print driver install script.
I was expecting RPM files and was a mighty annoyed by its hijacking
appearance especially when the script fell over due to DNF errors

I did say more than a FEW words

I believe you are correct about blacklisting as well..

Back in the days of CL nvidia installation, I don't think the nouveau
driver existed..

Also if Grimble gets the nouveau driver running there is a option to
install the "proprietary" driver through MCC. This may work as it could automatically resolve any dependencies

--
faeychild
Running plasmashell 5.20.4 on 5.15.6-desktop-2.mga8 kernel.
Mageia release 8 (Official) for x86_64 installed via Mageia-8-x86_64-DVD.iso


--- MBSE BBS v1.0.7.22 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 12/22/21 20:12, faeychild wrote:

On 23/12/21 08:29, Bobbie Sellers wrote:

     Well I don't know what is going on with dnf since it is not my
distribution except occassionally.   I think if he has called the Noveau >> driver he may have to blacklist it and remove it completely before the
correct nvidia driver can be used.
     But waiting for the repository to be accessible seems to be
the way to start.

     bliss

DNF appeared on my radar when I had to run  a print driver install script.
I was expecting RPM files and was a mighty annoyed by its hijacking appearance  especially when the script fell over due to DNF errors

I did say more  than a FEW words

I believe you are correct about blacklisting as well..

Back in the days of CL nvidia installation, I don't think the nouveau
driver existed..

I believe that noveau has been around since Mandriva.
I used to use the Mandriva repository via a nice GUI but not as nice as
Synaptic which I use on PCLinuxOS
CLI installs were not needed 99.9% of the time, I did have to
go through the blacklisting procedure one time. I used an nvidia
graphics chip set in an old Compaq(HP)laptop.

Also if Grimble gets the nouveau driver running there is a option to
install the "proprietary" driver through MCC. This may work as it could automatically resolve any dependencies

Good luck, to Grimble and a joyous Noel to you, faeychild

bliss - brought to you by the power and ease of PCLinuxOS
and a minor case of hypergraphia

--
bliss dash SF 4 ever at dslextreme dot com

--- MBSE BBS v1.0.7.22 (GNU/Linux-x86_64)
* Origin: dis-organization (2:250/1@fidonet)

On 23/12/21 16:40, Bobbie Sellers wrote:

    I believe that noveau has been around since Mandriva.
    I used to use the Mandriva repository via a nice GUI but not as nice as Synaptic which I use on PCLinuxOS
    CLI installs were not needed 99.9% of the time,  I did have to
go through the blacklisting procedure one time.  I used an nvidia
graphics chip set in an old Compaq(HP)laptop.

Some old memories are surfacing here and lacking any reliability, of course.
I was trying to remember why the CL install was used at all and that
"run" script for the nvidia driver and run level 3
I had almost forgotten, "telinit3" I think??

Maybe it predates Mandriva. May have been Mandrake or RedHat
Long ago and a galaxy far away.
Oh Dear! I do feel old


--
faeychild
Running plasmashell 5.20.4 on 5.15.6-desktop-2.mga8 kernel.
Mageia release 8 (Official) for x86_64 installed via Mageia-8-x86_64-DVD.iso


--- MBSE BBS v1.0.7.22 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 23.12.2021 at 23:33, faeychild scribbled:

On 23/12/21 16:40, Bobbie Sellers wrote:
=20

=C2=A0=C2=A0=C2=A0=C2=A0I believe that noveau has been around since Ma=

ndriva.

=C2=A0=C2=A0=C2=A0=C2=A0I used to use the Mandriva repository via a ni=

ce GUI but not

as nice as Synaptic which I use on PCLinuxOS
=C2=A0=C2=A0=C2=A0=C2=A0CLI installs were not needed 99.9% of the time=

,=C2=A0 I did have to

go through the blacklisting procedure one time.=C2=A0 I used an nvidia=

=20

graphics chip set in an old Compaq(HP)laptop. =20

=20
=20
Some old memories are surfacing here and lacking any reliability, of
course. I was trying to remember why the CL install was used at all
and that "run" script for the nvidia driver and run level 3
I had almost forgotten, "telinit3" I think??

That was for the proprietary ATi driver, if I recall correctly. Setting
up the Nvidia driver used to be easy, before Nvidia became Invidious. :p

--=20
With respect,
=3D Aragorn =3D


--- MBSE BBS v1.0.7.22 (GNU/Linux-x86_64)
* Origin: A noiseless patient Strider (2:250/1@fidonet)

On 12/22/21 09:11, Grimble wrote:

1. Rebooted after kernel upgrade: installation of nvidia-current driver
did not complete.
2. In run level 3, used drakx11 to change to nouveau driver. Reboot successful but various things wanted the nvidia driver so:
3. Dowwnloaded the driver from nvidia site and ran it, but final stage failed - unable to load nvidia-drm module.
4. A google suggested reloading kernel-desktop-devel. Used dnf to remove
it but dnf install kernel-desktop-devel-latest (or -5.15.6-2.mga8)
failed because of  curl error 6 - could not resolve host www.mageia.org
!!!!
Now what?

I don't use dnf, so I can't help you with problems with that. However...

The kernel update from the last 2-3 days was for kernel 5.15.10-1. You
need the devel package for that one.

The devel package for 5.15.6-2 won't work to build the nvidia driver for
the 5.15.10-1 kernel. If you had kernel-desktop-devel-latest for the
previous kernel installed, it and the corresponding devel package should
have been updated to 5.15.10-1 at that time.

But, if somehow along the line you removed the "latest" devel package,
it would NOT be updated automatically, and the nvidia driver and any
other dkms drivers would refuse to build.

BTW, there is a new nvidia-current driver going through Mageia QA
testing right now. If it passes, it should hit your favorite mirror
before long.

TJ

--- MBSE BBS v1.0.7.22 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 23/12/21 23:44, Aragorn wrote:

That was for the proprietary ATi driver, if I recall correctly. Setting
up the Nvidia driver used to be easy, before Nvidia became Invidious. :p

And insidious :-) I've never used ATI Maybe they collude on install scripts
I dread the the event if the update ever fails (like Grimble) and i am
stuck without graphics.

The recovery process is in copious notes on the HD and not in a hard
copy "brain book" like Bit twister has.
I would be stuffed and I have an update pending this morning. A new
kernel which always includes the remote possibility of a nvidia problem.
So far I have been lucky.

--
faeychild
Running plasmashell 5.20.4 on 5.15.6-desktop-2.mga8 kernel.
Mageia release 8 (Official) for x86_64 installed via Mageia-8-x86_64-DVD.iso


--- MBSE BBS v1.0.7.22 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 24.12.2021 at 08:15, faeychild scribbled:

On 23/12/21 23:44, Aragorn wrote:
=20

That was for the proprietary ATi driver, if I recall correctly.
Setting up the Nvidia driver used to be easy, before Nvidia became Invidious. :p=20

And insidious :-) I've never used ATI Maybe they collude on
install scripts

ATi was acquired by AMD a long time ago now, and although there were
some problems with regard to the driver source code at first due to non-disclosure agreements, AMD have in the meantime managed to
open-source all of their drivers. =20

They do still have a proprietary driver =E2=80=94 amdgpu-pro =E2=80=94 but = there is
actually very little that you'd need that driver for. For 95% of the
users, the free amdgpu and radeon drivers will do just fine.

I dread the the event if the update ever fails (like Grimble) and i
am stuck without graphics.
=20
The recovery process is in copious notes on the HD and not in a hard=20
copy "brain book" like Bit twister has.
I would be stuffed and I have an update pending this morning. A new=20
kernel which always includes the remote possibility of a nvidia
problem. So far I have been lucky.

I have left all of that behind me. My current daily driver =E2=80=94 this machine here =E2=80=94 has onboard Intel graphics, and they are perfectly f= ine
for all my needs. I can watch movies in UHD (1920*1080), I've got 3D
effects in Plasma, and I'm not a gamer, so I don't need any high-end
graphics adapters. =20

But if I did, then I'd go for AMD. Nvidia is consistently refusing to collaborate with the Linux kernel developers =E2=80=94 which AMD and Intel = have
proven to be both technically possible and perfectly good for business =E2= =80=94
so Nvidia can go to hell for all I care.

--=20
With respect,
=3D Aragorn =3D


--- MBSE BBS v1.0.7.22 (GNU/Linux-x86_64)
* Origin: A noiseless patient Strider (2:250/1@fidonet)

On 22/12/2021 15:50, Bobbie Sellers wrote:

On 12/22/21 06:11, Grimble wrote:

1. Rebooted after kernel upgrade: installation of nvidia-current
driver did not complete.
2. In run level 3, used drakx11 to change to nouveau driver. Reboot
successful but various things wanted the nvidia driver so:
3. Dowwnloaded the driver from nvidia site and ran it, but final stage
failed - unable to load nvidia-drm module.
4. A google suggested reloading kernel-desktop-devel. Used dnf to
remove it but dnf install kernel-desktop-devel-latest (or
-5.15.6-2.mga8) failed because of  curl error 6 - could not resolve
host www.mageia.org
!!!!
Now what?

Ehhh... wait until www.mageia.org is reachable.
    I know waiting is painful but...

    bliss

Follow-up: Not as bad as I feared.
1. Forgot that the network doesn't automatically come up in fall-back
mode. Managed to get the nVidia driver compiled and installed
(--uninstall was the magic) - inxi -G confirms it, but boot up doesn't
proceed beyond the log-in screen. Reminiscent of my problems a month ago.
2. startx with root sign -in works perfectly

So I guess I'll have to follow the procedure Dave H proposed last time.
Leave it until after the weekend anyway.
Happy Christmas/Holiday/Hannukah/Whatever to all

--
Grimble
Registered Linux User #450547
Machine 'Bach' running Plasma 5.20.4 on 5.15.6-desktop-2.mga8 kernel.
Mageia release 8 (Official) for x86_64

--- MBSE BBS v1.0.7.22 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 23/12/2021 14:50, TJ wrote:

On 12/22/21 09:11, Grimble wrote:

1. Rebooted after kernel upgrade: installation of nvidia-current
driver did not complete.
2. In run level 3, used drakx11 to change to nouveau driver. Reboot
successful but various things wanted the nvidia driver so:
3. Dowwnloaded the driver from nvidia site and ran it, but final stage
failed - unable to load nvidia-drm module.
4. A google suggested reloading kernel-desktop-devel. Used dnf to
remove it but dnf install kernel-desktop-devel-latest (or
-5.15.6-2.mga8) failed because of  curl error 6 - could not resolve
host www.mageia.org
!!!!
Now what?

I don't use dnf, so I can't help you with problems with that. However...

TJ

Thanks TJ, dnf wasn't the problem, I use it all the time. It was just
that the network wasn't up.
As you see elsewhere, Ive succeeded with the driver, but it wasn't my
only problem.
Best wishes,

--
Grimble
Registered Linux User #450547
Machine 'Bach' running Plasma 5.20.4 on 5.15.6-desktop-2.mga8 kernel.
Mageia release 8 (Official) for x86_64

--- MBSE BBS v1.0.7.22 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 12/24/21 07:11, Aragorn wrote:

On 24.12.2021 at 08:15, faeychild scribbled:

On 23/12/21 23:44, Aragorn wrote:

That was for the proprietary ATi driver, if I recall correctly.
Setting up the Nvidia driver used to be easy, before Nvidia became
Invidious. :p

And insidious :-) I've never used ATI Maybe they collude on
install scripts

ATi was acquired by AMD a long time ago now, and although there were
some problems with regard to the driver source code at first due to non-disclosure agreements, AMD have in the meantime managed to
open-source all of their drivers.

They do still have a proprietary driver — amdgpu-pro — but there is actually very little that you'd need that driver for. For 95% of the
users, the free amdgpu and radeon drivers will do just fine.

The amdgpu driver is the only one seeing much development these days,
but it seems to work nicely. Mageia did have a bit of a problem with
sddm and one group of AMD cards a year ago. This was the "transitional"
group of cards that for a long time worked with radeon, but
experimentally with amdgpu. Mageia was using radeon with those, but when
the sddm login screen acted up, the switch to amdgpu cured it. Strangely enough, the older cards that won't work with amdgpu don't have the same problem with the radeon driver and sddm.

I dread the the event if the update ever fails (like Grimble) and i
am stuck without graphics.

The recovery process is in copious notes on the HD and not in a hard
copy "brain book" like Bit twister has.
I would be stuffed and I have an update pending this morning. A new
kernel which always includes the remote possibility of a nvidia
problem. So far I have been lucky.

I have left all of that behind me. My current daily driver — this
machine here — has onboard Intel graphics, and they are perfectly fine
for all my needs. I can watch movies in UHD (1920*1080), I've got 3D
effects in Plasma, and I'm not a gamer, so I don't need any high-end
graphics adapters.

But if I did, then I'd go for AMD. Nvidia is consistently refusing to collaborate with the Linux kernel developers — which AMD and Intel have proven to be both technically possible and perfectly good for business —
so Nvidia can go to hell for all I care.

I have one AMD-based machine with older AMD onboard graphics. At the
time I acquired the used motherboard, I didn't find out until later that Libreoffice had a problem with older AMD graphics, so I bought an nvidia
card for it.

It worked OK, but then came the news that nvidia wouldn't support it any
more, so I dumped it and bought a very cheap used AMD card on eBay. It's
an HD 8490, and still uses the radeon driver. But the thing is, when I
run benchmarks to test graphics updates, this card consistently out
performs the onboard Intel graphics of even my newest machine.

I have another, equally inexpensive, that I bought for an older
Intel-based machine, because the older GPU just wasn't really good
enough. That one was an HD 8570, just over the line into amdgpu
territory. When I run those same benchmarks on that machine, it gets the
best scores of any I have.

And no messing around with building drivers. I'll NEVER go back to
nvidia, unless they make a radical change to their Linux policies.

TJ

--- MBSE BBS v1.0.7.22 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 24/12/21 23:11, Aragorn wrote:

I have left all of that behind me. My current daily driver — this
machine here — has onboard Intel graphics, and they are perfectly fine
for all my needs. I can watch movies in UHD (1920*1080), I've got 3D
effects in Plasma, and I'm not a gamer, so I don't need any high-end
graphics adapters.

But if I did, then I'd go for AMD. Nvidia is consistently refusing to collaborate with the Linux kernel developers — which AMD and Intel have proven to be both technically possible and perfectly good for business —
so Nvidia can go to hell for all I care.

Agreed!
Unless one is a gamer then the super graphics card is overkill

I don't know why I cling to mine

It is Christmas morning here, slightly ahead of the rest of you

Merry Christmas

Regards
--
faeychild
Running plasmashell 5.20.4 on 5.15.10-desktop-1.mga8 kernel.
Mageia release 8 (Official) for x86_64 installed via Mageia-8-x86_64-DVD.iso


--- MBSE BBS v1.0.7.22 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)