Re: My Fedora 40 experiences

2024-05-21 Thread Stephen Morris 

On 18/5/24 18:10, John Pilkington wrote:

On 18/05/2024 03:17, Stephen Morris wrote:

On 17/5/24 22:43, John Pilkington wrote:

On 17/05/2024 13:08, francis.montag...@inria.fr wrote:

Hi.

On Thu, 16 May 2024 23:04:21 +1000 Stephen Morris wrote:

On 16/5/24 21:33, George N. White III wrote:


Many users have had problems with the akmod-nvida install. For 
470xx the
module failed to compile. For newer cards, users sometimes end up 
with
unsigned drivers. This usually means they rebooted too quickly 
(during the

window after the module was compiled but before it was signed.).


Or before the depmod done by the postintall of the kmod-nvidia-KERNEL
RPM finishes.

I have had the reboot happen too too quickly before but in this 
case I
had no control over the reboot process, it happened automatically 
when

the installs were completed.


Right: more precisely as soon as dnf system-upgrade finishes.

As said earlier on this list:

   I made a proposal to prevent that:

 kmod failed to load after upgrade Fedora using dnf system-upgrade
 https://bugzilla.redhat.com/show_bug.cgi?id=2011120

   still waiting for approval.


This morning 'dnf upgrade' on one of my boxes installed the 
470.239.06-2 versions of akmod and kmod, while the other box, having 
the -1 nersions, said there was 'nothing to do';  then packagekit 
found them and did a preliminary reboot before install.  Both boxes 
now have the -2 versions installed and running.  The process does 
take several minutes - and I did an "akmods --rebuild --force" just 
to make sure.


F40 with plasma-workspace-x11 does seem to be working well now for 
me, and can use vdpau.
How did you get Xorg working with Plasma as I can't see any group in 
dnf to install that?


The path to where I am now has been complicated, mainly because my 
nvidia hardware is 'legacy' and its 470xx driver has not claimed to 
support Wayland.  Under Wayland all cpus max out, and keyboard/mouse 
are almost unusable.  YMMV.


dnf info plasma-workspace-x11

It's in the Fedora 'updates' repo.
Thanks John. I hadn't thought about looking in the repo for that 
package, I was expecting it to be in the group package options. I'll 
install that even if for no other reason other reason than I have never 
liked Wayland. I use the 550 drivers so Wayland support is not an issue, 
I just don't like it.




The other thing I didn't like with the F40 upgrade was in F39 I had 
dnf configured to retain 5 kernels, but the F40 upgrade reset that 
back to 3.


My system has 450 MB /boot, space for only 2 kernels + rescue.
I have a 50GB /boot so I have plenty of space for 5 kernels + any rescue 
kernels that exist.


regards,
Steve


regards,
Steve



John P

--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/

List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


OpenPGP_0x594338B1DE179AB2.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: My Fedora 40 experiences

2024-05-19 Thread Samuel Sieb 

On 5/19/24 8:58 AM, Mike Wright wrote:
For the first time ever I had a need for the "rescue" kernel.  Using 
that grub entry brought up a system that required a root login.  I have 
not had a root password on any distro since I can't recall.  Oh, I 
remember, edit the command line and put it in runlevel 1.  hahahaha! 
Grampa, what's a runlevel?  I ended up booting off of a USB (ventoy is 
awesome!) to bring up some distro, mounted the borken system, did my 
magic, rebooted and was back in business.


Point being: what good is a rescue kernel when the canoe has no oars?


The rescue kernel option has all the kernel modules.  It's primarily 
useful for if you've changed hardware to something that uses different 
drivers that weren't being used before.  By default, the initramfs only 
has the drivers needed for the current hardware.


The rescue kernel option is not any different than the regular options 
for fixing a damaged fs.  There is an issue that if it can't boot, it 
asks for the root password even if that hasn't been set.  There has been 
some discussion about it, but no solutions yet.

--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: My Fedora 40 experiences

2024-05-19 Thread Mike Wright 

On 5/18/24 01:10, John Pilkington wrote:

On 18/05/2024 03:17, Stephen Morris wrote:

On 17/5/24 22:43, John Pilkington wrote:

On 17/05/2024 13:08, francis.montag...@inria.fr wrote:

Hi.

On Thu, 16 May 2024 23:04:21 +1000 Stephen Morris wrote:

On 16/5/24 21:33, George N. White III wrote:


Many users have had problems with the akmod-nvida install. For 
470xx the
module failed to compile. For newer cards, users sometimes end up 
with
unsigned drivers. This usually means they rebooted too quickly 
(during the

window after the module was compiled but before it was signed.).


Or before the depmod done by the postintall of the kmod-nvidia-KERNEL
RPM finishes.


I have had the reboot happen too too quickly before but in this case I
had no control over the reboot process, it happened automatically when
the installs were completed.


Right: more precisely as soon as dnf system-upgrade finishes.

As said earlier on this list:

   I made a proposal to prevent that:

 kmod failed to load after upgrade Fedora using dnf system-upgrade
 https://bugzilla.redhat.com/show_bug.cgi?id=2011120

   still waiting for approval.


This morning 'dnf upgrade' on one of my boxes installed the 
470.239.06-2 versions of akmod and kmod, while the other box, having 
the -1 nersions, said there was 'nothing to do';  then packagekit 
found them and did a preliminary reboot before install.  Both boxes 
now have the -2 versions installed and running.  The process does 
take several minutes - and I did an "akmods --rebuild --force" just 
to make sure.


F40 with plasma-workspace-x11 does seem to be working well now for 
me, and can use vdpau.
How did you get Xorg working with Plasma as I can't see any group in 
dnf to install that?


The path to where I am now has been complicated, mainly because my 
nvidia hardware is 'legacy' and its 470xx driver has not claimed to 
support Wayland.  Under Wayland all cpus max out, and keyboard/mouse are 
almost unusable.  YMMV.


dnf info plasma-workspace-x11

It's in the Fedora 'updates' repo.



The other thing I didn't like with the F40 upgrade was in F39 I had 
dnf configured to retain 5 kernels, but the F40 upgrade reset that 
back to 3.


My system has 450 MB /boot, space for only 2 kernels + rescue.


For the first time ever I had a need for the "rescue" kernel.  Using 
that grub entry brought up a system that required a root login.  I have 
not had a root password on any distro since I can't recall.  Oh, I 
remember, edit the command line and put it in runlevel 1.  hahahaha! 
Grampa, what's a runlevel?  I ended up booting off of a USB (ventoy is 
awesome!) to bring up some distro, mounted the borken system, did my 
magic, rebooted and was back in business.


Point being: what good is a rescue kernel when the canoe has no oars?

If you need space get rid of the rescue kernel.

IMHO
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: My Fedora 40 experiences

2024-05-18 Thread John Pilkington 

On 18/05/2024 03:17, Stephen Morris wrote:

On 17/5/24 22:43, John Pilkington wrote:

On 17/05/2024 13:08, francis.montag...@inria.fr wrote:

Hi.

On Thu, 16 May 2024 23:04:21 +1000 Stephen Morris wrote:

On 16/5/24 21:33, George N. White III wrote:


Many users have had problems with the akmod-nvida install. For 
470xx the

module failed to compile. For newer cards, users sometimes end up with
unsigned drivers. This usually means they rebooted too quickly 
(during the

window after the module was compiled but before it was signed.).


Or before the depmod done by the postintall of the kmod-nvidia-KERNEL
RPM finishes.


I have had the reboot happen too too quickly before but in this case I
had no control over the reboot process, it happened automatically when
the installs were completed.


Right: more precisely as soon as dnf system-upgrade finishes.

As said earlier on this list:

   I made a proposal to prevent that:

 kmod failed to load after upgrade Fedora using dnf system-upgrade
 https://bugzilla.redhat.com/show_bug.cgi?id=2011120

   still waiting for approval.


This morning 'dnf upgrade' on one of my boxes installed the 
470.239.06-2 versions of akmod and kmod, while the other box, having 
the -1 nersions, said there was 'nothing to do';  then packagekit 
found them and did a preliminary reboot before install.  Both boxes 
now have the -2 versions installed and running.  The process does take 
several minutes - and I did an "akmods --rebuild --force" just to make 
sure.


F40 with plasma-workspace-x11 does seem to be working well now for me, 
and can use vdpau.
How did you get Xorg working with Plasma as I can't see any group in dnf 
to install that?


The path to where I am now has been complicated, mainly because my 
nvidia hardware is 'legacy' and its 470xx driver has not claimed to 
support Wayland.  Under Wayland all cpus max out, and keyboard/mouse are 
almost unusable.  YMMV.


dnf info plasma-workspace-x11

It's in the Fedora 'updates' repo.



The other thing I didn't like with the F40 upgrade was in F39 I had dnf 
configured to retain 5 kernels, but the F40 upgrade reset that back to 3.


My system has 450 MB /boot, space for only 2 kernels + rescue.


regards,
Steve



John P

--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: My Fedora 40 experiences

2024-05-17 Thread Stephen Morris 

On 18/5/24 09:19, Jeffrey Walton wrote:



On Thu, May 16, 2024 at 5:46 AM Stephen Morris 
 wrote:


I used dnf to system-upgrade to F40, which downloaded all the
relevant
packages, and then I rebooted through dnf.
The restart updated all the packages and automatically rebooted
when it
was finished.
[...]
This was a lot of work to resolve, and is the worst experience
I've had
with any fedora system upgrade.


Next time, you should consider following 
. 
It has never failed me.
That was the instructions I followed, except for step 4 as I wasn't 
asked to verify the import keys.
Some of my issues were also relative to configurations and settings that 
I had in F39 were wiped with the F40 upgrade.
The one thing those instructions don't elaborate on is when things like 
Plasma won't start apparently because of UEFI issues when the UEFI keys 
that were registered with F39 were still registered after the upgrade.


regards,
Steve



Jeff

--
___
users mailing list --users@lists.fedoraproject.org
To unsubscribe send an email tousers-le...@lists.fedoraproject.org
Fedora Code of 
Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines
List 
Archives:https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report 
it:https://pagure.io/fedora-infrastructure/new_issue


OpenPGP_0x594338B1DE179AB2.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: My Fedora 40 experiences

2024-05-17 Thread Stephen Morris 

On 17/5/24 22:43, John Pilkington wrote:

On 17/05/2024 13:08, francis.montag...@inria.fr wrote:

Hi.

On Thu, 16 May 2024 23:04:21 +1000 Stephen Morris wrote:

On 16/5/24 21:33, George N. White III wrote:


Many users have had problems with the akmod-nvida install. For 
470xx the

module failed to compile. For newer cards, users sometimes end up with
unsigned drivers. This usually means they rebooted too quickly 
(during the

window after the module was compiled but before it was signed.).


Or before the depmod done by the postintall of the kmod-nvidia-KERNEL
RPM finishes.


I have had the reboot happen too too quickly before but in this case I
had no control over the reboot process, it happened automatically when
the installs were completed.


Right: more precisely as soon as dnf system-upgrade finishes.

As said earlier on this list:

   I made a proposal to prevent that:

 kmod failed to load after upgrade Fedora using dnf system-upgrade
 https://bugzilla.redhat.com/show_bug.cgi?id=2011120

   still waiting for approval.


This morning 'dnf upgrade' on one of my boxes installed the 
470.239.06-2 versions of akmod and kmod, while the other box, having 
the -1 nersions, said there was 'nothing to do';  then packagekit 
found them and did a preliminary reboot before install.  Both boxes 
now have the -2 versions installed and running.  The process does take 
several minutes - and I did an "akmods --rebuild --force" just to make 
sure.


F40 with plasma-workspace-x11 does seem to be working well now for me, 
and can use vdpau.
How did you get Xorg working with Plasma as I can't see any group in dnf 
to install that?


The other thing I didn't like with the F40 upgrade was in F39 I had dnf 
configured to retain 5 kernels, but the F40 upgrade reset that back to 3.


regards,
Steve



John P



--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/

List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


OpenPGP_0x594338B1DE179AB2.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: My Fedora 40 experiences

2024-05-17 Thread Jeffrey Walton 
On Thu, May 16, 2024 at 5:46 AM Stephen Morris 
wrote:

> I used dnf to system-upgrade to F40, which downloaded all the relevant
> packages, and then I rebooted through dnf.
> The restart updated all the packages and automatically rebooted when it
> was finished.
> [...]
> This was a lot of work to resolve, and is the worst experience I've had
> with any fedora system upgrade.
>

Next time, you should consider following <
https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/>.
It has never failed me.

Jeff
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: My Fedora 40 experiences

2024-05-17 Thread John Pilkington 

On 17/05/2024 13:08, francis.montag...@inria.fr wrote:

Hi.

On Thu, 16 May 2024 23:04:21 +1000 Stephen Morris wrote:

On 16/5/24 21:33, George N. White III wrote:



Many users have had problems with the akmod-nvida install. For 470xx the
module failed to compile. For newer cards, users sometimes end up with
unsigned drivers. This usually means they rebooted too quickly (during the
window after the module was compiled but before it was signed.).


Or before the depmod done by the postintall of the kmod-nvidia-KERNEL
RPM finishes.


I have had the reboot happen too too quickly before but in this case I
had no control over the reboot process, it happened automatically when
the installs were completed.


Right: more precisely as soon as dnf system-upgrade finishes.

As said earlier on this list:

   I made a proposal to prevent that:

 kmod failed to load after upgrade Fedora using dnf system-upgrade
 https://bugzilla.redhat.com/show_bug.cgi?id=2011120

   still waiting for approval.


This morning 'dnf upgrade' on one of my boxes installed the 
470.239.06-2 versions of akmod and kmod, while the other box, having 
the -1 nersions, said there was 'nothing to do';  then packagekit found 
them and did a preliminary reboot before install.  Both boxes now have 
the -2 versions installed and running.  The process does take several 
minutes - and I did an "akmods --rebuild --force" just to make sure.


F40 with plasma-workspace-x11 does seem to be working well now for me, 
and can use vdpau.


John P



--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: My Fedora 40 experiences

2024-05-17 Thread Francis . Montagnac 
Hi.

On Thu, 16 May 2024 23:04:21 +1000 Stephen Morris wrote:
> On 16/5/24 21:33, George N. White III wrote:

>> Many users have had problems with the akmod-nvida install. For 470xx the
>> module failed to compile. For newer cards, users sometimes end up with
>> unsigned drivers. This usually means they rebooted too quickly (during the
>> window after the module was compiled but before it was signed.).

Or before the depmod done by the postintall of the kmod-nvidia-KERNEL
RPM finishes.

> I have had the reboot happen too too quickly before but in this case I 
> had no control over the reboot process, it happened automatically when 
> the installs were completed.

Right: more precisely as soon as dnf system-upgrade finishes.

As said earlier on this list:

  I made a proposal to prevent that:

kmod failed to load after upgrade Fedora using dnf system-upgrade
https://bugzilla.redhat.com/show_bug.cgi?id=2011120

  still waiting for approval.

-- 
francis
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: My Fedora 40 experiences

2024-05-16 Thread Stephen Morris 

On 16/5/24 22:13, John Pilkington wrote:

On 16/05/2024 12:33, George N. White III wrote:
On Thu, May 16, 2024 at 6:46 AM Stephen Morris 
mailto:samor...@netspace.net.au>> wrote:


    I used dnf to system-upgrade to F40, which downloaded all the 
relevant

    packages, and then I rebooted through dnf.


Did you do all the steps in 
>? 



    The restart updated all the packages and automatically rebooted 
when it

    was finished.
    When the grub menu was displayed after the reboot it was obvious 
that

    the upgrade did not update the grub config as there was no entry to
    boot
    off the F40 installed kernel.
    I booted to the display manager which I think is still gdm, and the
    first thing I noticed there was the "plasma on xorg" selection 
had been
    removed but the "Gnome on xorg" and "Gnome Classic on xorg" were 
still

    there.
    I selected the "Plasma" entry and booted into Plasma.
    Having loaded Plasma I then went into the system entries menu and 
went

    through all the options again, and it was obvious from this that the
    display options I had configured with F39 had been wiped with F40. I
    configured the display settings again and set the new HDR option 
as I

    have a HDR monitor.
    After the configuration changes I rebuilt the grub menus using
    grub2-mkconfig to get a boot entry for the new kernel, and rebooted.
    With the reboot from the new kernel, and for that matter any of the
    older kernels, I got a message that the nvidia driver was not 
found and

    it was falling back to the nouveau driver, I don't know how as the
    nvidia driver was black listed in the grub menus.


Which nvidia driver was blacklisted (nouveau or nvidia-???)? There 
have been
problems with older Nvidia cards.  Were you using nouveau on F39 or 
nvidia, and
how did you install the nvidia driver (there are multiple sites with 
different installers).
My old iMac uses 470xx from rpmfusion, which was initially in 
no-maintainer status
and required a simple patch to run on current kernels.  Last I check 
the driver was in

testing.

  From the display manager I loaded Plasma as I did after the first
    upgrade boot, and Plasma displayed a black screen and never went any
    further, irrespective of how long I left it for, and the only way I
    could get out of that state was to use the physical reset button 
on the

    computer.
    On reboot, if I selected "Gnome" or "Gnome on Xorg", gnome would 
start
    up quite happily, but logging out and starting Plasma would still 
hang

    the computer.
    So rebooting again to the display manager login screen, I used
    ctrl+alt+F2 to switch to a terminal login process. Logging into the
    terminal the first thing I did was use mokutil to check the uefi 
status
    and it told me that uefi was disabled even though it was enabled 
in the

    bios.
    I checked whether the signing key was enrolled and it was, but the
    system wasn't using the nvidia driver even though it was 
installed, and

    a reinstall of kmod-nvidia and akmod-nvidia did nothing to alleviate
    the
    issue.


Many users have had problems with the akmod-nvida install.  For 470xx
the module failed to compile.  For newer cards, users sometimes end up
with unsigned drivers.  This usually means they rebooted too quickly 
(during

the window after the module was compiled but before it was signed.).

    So I uninstalled the kmod-nvidia module, and did a force 
re-enroll of
    the uefi signed key (potentially with a new key), and then 
rebooted to
    go through the mokutil enrolment required at boot. This did not 
resolve

    the Plasm start issue, so I loaded Gnome.
    Once in Gnome I started Firefox Nightly to do some net searches 
to see
    if I could find a solution, and the one thing that did happen at 
this

    point was the boot did not display the "falling back to nouveau"
    message, but the start of firefox displayed a message that a gpu
    couldn't be found on pci. Looking for a resolution to this I 
found an

    entry about, as part of installed nvidia drivers, to ensure the gpu
    firmware was also installed.
    So I did a dnf install nvidia-gpu-firmware which was then 
installed as

    it hadn't been already.


If you had installed nvidia-??? from a 3rd party repo the Fedora 
firmware

package might not be required, but it is needed for nouveau.

    After installing the firmware I rebooted and started Plasma, which
    successfully started without issues, and when I checked the video
    driver
    it was finally using the nvidia driver.
    This was a lot of work to resolve, and is the worst experience 
I've had

    with any fedora system upgrade.


Blame Nvidia for forcing Fedora into convoluted workarounds instead of
helping make older hardware work on current kernels.

Rp

Re: My Fedora 40 experiences

2024-05-16 Thread Stephen Morris 


On 16/5/24 21:33, George N. White III wrote:
On Thu, May 16, 2024 at 6:46 AM Stephen Morris 
 wrote:


I used dnf to system-upgrade to F40, which downloaded all the
relevant
packages, and then I rebooted through dnf.


Did you do all the steps in 
?

I did, except step 4 as I wasn't asked to verify the imported key.


The restart updated all the packages and automatically rebooted
when it
was finished.
When the grub menu was displayed after the reboot it was obvious that
the upgrade did not update the grub config as there was no entry
to boot
off the F40 installed kernel.
I booted to the display manager which I think is still gdm, and the
first thing I noticed there was the "plasma on xorg" selection had
been
removed but the "Gnome on xorg" and "Gnome Classic on xorg" were
still
there.
I selected the "Plasma" entry and booted into Plasma.
Having loaded Plasma I then went into the system entries menu and
went
through all the options again, and it was obvious from this that the
display options I had configured with F39 had been wiped with F40. I
configured the display settings again and set the new HDR option as I
have a HDR monitor.
After the configuration changes I rebuilt the grub menus using
grub2-mkconfig to get a boot entry for the new kernel, and rebooted.
With the reboot from the new kernel, and for that matter any of the
older kernels, I got a message that the nvidia driver was not
found and
it was falling back to the nouveau driver, I don't know how as the
nvidia driver was black listed in the grub menus.


Which nvidia driver was blacklisted (nouveau or nvidia-???)?  There 
have been
problems with older Nvidia cards.  Were you using nouveau on F39 or 
nvidia, and
how did you install the nvidia driver (there are multiple sites with 
different installers).
My old iMac uses 470xx from rpmfusion, which was initially in 
no-maintainer status
and required a simple patch to run on current kernels. Last I check 
the driver was in

testing.
Sorry, I meant the nouveau driver was blacklisted. I have always used 
the nvidia driver from rpmfusion as I have needed the hardware 
acceleration the nvidia driver provides. I was using the nvidia driver 
in F39 both via kmod-nvidia and akmod-nvidia for backup.


 From the display manager I loaded Plasma as I did after the first
upgrade boot, and Plasma displayed a black screen and never went any
further, irrespective of how long I left it for, and the only way I
could get out of that state was to use the physical reset button
on the
computer.
On reboot, if I selected "Gnome" or "Gnome on Xorg", gnome would
start
up quite happily, but logging out and starting Plasma would still
hang
the computer.
So rebooting again to the display manager login screen, I used
ctrl+alt+F2 to switch to a terminal login process. Logging into the
terminal the first thing I did was use mokutil to check the uefi
status
and it told me that uefi was disabled even though it was enabled
in the
bios.
I checked whether the signing key was enrolled and it was, but the
system wasn't using the nvidia driver even though it was
installed, and
a reinstall of kmod-nvidia and akmod-nvidia did nothing to
alleviate the
issue.


Many users have had problems with the akmod-nvida install.  For 470xx
the module failed to compile.  For newer cards, users sometimes end up
with unsigned drivers.  This usually means they rebooted too quickly 
(during

the window after the module was compiled but before it was signed.).
I have had the reboot happen too too quickly before but in this case I 
had no control over the reboot process, it happened automatically when 
the installs were completed. I'm using the 550 driver as that is one the 
system selected for my RTX 3080 graphics card.


So I uninstalled the kmod-nvidia module, and did a force re-enroll of
the uefi signed key (potentially with a new key), and then
rebooted to
go through the mokutil enrolment required at boot. This did not
resolve
the Plasm start issue, so I loaded Gnome.
Once in Gnome I started Firefox Nightly to do some net searches to
see
if I could find a solution, and the one thing that did happen at this
point was the boot did not display the "falling back to nouveau"
message, but the start of firefox displayed a message that a gpu
couldn't be found on pci. Looking for a resolution to this I found an
entry about, as part of installed nvidia drivers, to ensure the gpu
firmware was also installed.
So I did a dnf install nvidia-gpu-firmware which was then
installed as
it hadn't been already.


If you had installed nvidia-??? from a 3rd party repo the Fedora firmware
package might not be required, bu

Re: My Fedora 40 experiences

2024-05-16 Thread John Pilkington 

On 16/05/2024 12:33, George N. White III wrote:
On Thu, May 16, 2024 at 6:46 AM Stephen Morris > wrote:


I used dnf to system-upgrade to F40, which downloaded all the relevant
packages, and then I rebooted through dnf.


Did you do all the steps in 
>?


The restart updated all the packages and automatically rebooted when it
was finished.
When the grub menu was displayed after the reboot it was obvious that
the upgrade did not update the grub config as there was no entry to
boot
off the F40 installed kernel.
I booted to the display manager which I think is still gdm, and the
first thing I noticed there was the "plasma on xorg" selection had been
removed but the "Gnome on xorg" and "Gnome Classic on xorg" were still
there.
I selected the "Plasma" entry and booted into Plasma.
Having loaded Plasma I then went into the system entries menu and went
through all the options again, and it was obvious from this that the
display options I had configured with F39 had been wiped with F40. I
configured the display settings again and set the new HDR option as I
have a HDR monitor.
After the configuration changes I rebuilt the grub menus using
grub2-mkconfig to get a boot entry for the new kernel, and rebooted.
With the reboot from the new kernel, and for that matter any of the
older kernels, I got a message that the nvidia driver was not found and
it was falling back to the nouveau driver, I don't know how as the
nvidia driver was black listed in the grub menus.


Which nvidia driver was blacklisted (nouveau or nvidia-???)?  There have 
been
problems with older Nvidia cards.  Were you using nouveau on F39 or 
nvidia, and
how did you install the nvidia driver (there are multiple sites with 
different installers).
My old iMac uses 470xx from rpmfusion, which was initially in 
no-maintainer status
and required a simple patch to run on current kernels.  Last I check the 
driver was in

testing.

  From the display manager I loaded Plasma as I did after the first
upgrade boot, and Plasma displayed a black screen and never went any
further, irrespective of how long I left it for, and the only way I
could get out of that state was to use the physical reset button on the
computer.
On reboot, if I selected "Gnome" or "Gnome on Xorg", gnome would start
up quite happily, but logging out and starting Plasma would still hang
the computer.
So rebooting again to the display manager login screen, I used
ctrl+alt+F2 to switch to a terminal login process. Logging into the
terminal the first thing I did was use mokutil to check the uefi status
and it told me that uefi was disabled even though it was enabled in the
bios.
I checked whether the signing key was enrolled and it was, but the
system wasn't using the nvidia driver even though it was installed, and
a reinstall of kmod-nvidia and akmod-nvidia did nothing to alleviate
the
issue.


Many users have had problems with the akmod-nvida install.  For 470xx
the module failed to compile.  For newer cards, users sometimes end up
with unsigned drivers.  This usually means they rebooted too quickly 
(during

the window after the module was compiled but before it was signed.).

So I uninstalled the kmod-nvidia module, and did a force re-enroll of
the uefi signed key (potentially with a new key), and then rebooted to
go through the mokutil enrolment required at boot. This did not resolve
the Plasm start issue, so I loaded Gnome.
Once in Gnome I started Firefox Nightly to do some net searches to see
if I could find a solution, and the one thing that did happen at this
point was the boot did not display the "falling back to nouveau"
message, but the start of firefox displayed a message that a gpu
couldn't be found on pci. Looking for a resolution to this I found an
entry about, as part of installed nvidia drivers, to ensure the gpu
firmware was also installed.
So I did a dnf install nvidia-gpu-firmware which was then installed as
it hadn't been already.


If you had installed nvidia-??? from a 3rd party repo the Fedora firmware
package might not be required, but it is needed for nouveau.

After installing the firmware I rebooted and started Plasma, which
successfully started without issues, and when I checked the video
driver
it was finally using the nvidia driver.
This was a lot of work to resolve, and is the worst experience I've had
with any fedora system upgrade.


Blame Nvidia for forcing Fedora into convoluted workarounds instead of
helping make older hardware work on current kernels.

Rpmfusion is having difficulties finding volunteers to package software.
Fewer volunte

Re: My Fedora 40 experiences

2024-05-16 Thread George N. White III 
On Thu, May 16, 2024 at 6:46 AM Stephen Morris 
wrote:

> I used dnf to system-upgrade to F40, which downloaded all the relevant
> packages, and then I rebooted through dnf.
>

Did you do all the steps in <
https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/>?


> The restart updated all the packages and automatically rebooted when it
> was finished.
> When the grub menu was displayed after the reboot it was obvious that
> the upgrade did not update the grub config as there was no entry to boot
> off the F40 installed kernel.
> I booted to the display manager which I think is still gdm, and the
> first thing I noticed there was the "plasma on xorg" selection had been
> removed but the "Gnome on xorg" and "Gnome Classic on xorg" were still
> there.
> I selected the "Plasma" entry and booted into Plasma.
> Having loaded Plasma I then went into the system entries menu and went
> through all the options again, and it was obvious from this that the
> display options I had configured with F39 had been wiped with F40. I
> configured the display settings again and set the new HDR option as I
> have a HDR monitor.
> After the configuration changes I rebuilt the grub menus using
> grub2-mkconfig to get a boot entry for the new kernel, and rebooted.
> With the reboot from the new kernel, and for that matter any of the
> older kernels, I got a message that the nvidia driver was not found and
> it was falling back to the nouveau driver, I don't know how as the
> nvidia driver was black listed in the grub menus.
>

Which nvidia driver was blacklisted (nouveau or nvidia-???)?  There have
been
problems with older Nvidia cards.  Were you using nouveau on F39 or nvidia,
and
how did you install the nvidia driver (there are multiple sites with
different installers).
My old iMac uses 470xx from rpmfusion, which was initially in no-maintainer
status
and required a simple patch to run on current kernels.  Last I check the
driver was in
testing.


>  From the display manager I loaded Plasma as I did after the first
> upgrade boot, and Plasma displayed a black screen and never went any
> further, irrespective of how long I left it for, and the only way I
> could get out of that state was to use the physical reset button on the
> computer.
> On reboot, if I selected "Gnome" or "Gnome on Xorg", gnome would start
> up quite happily, but logging out and starting Plasma would still hang
> the computer.
> So rebooting again to the display manager login screen, I used
> ctrl+alt+F2 to switch to a terminal login process. Logging into the
> terminal the first thing I did was use mokutil to check the uefi status
> and it told me that uefi was disabled even though it was enabled in the
> bios.
> I checked whether the signing key was enrolled and it was, but the
> system wasn't using the nvidia driver even though it was installed, and
> a reinstall of kmod-nvidia and akmod-nvidia did nothing to alleviate the
> issue.
>

Many users have had problems with the akmod-nvida install.  For 470xx
the module failed to compile.  For newer cards, users sometimes end up
with unsigned drivers.  This usually means they rebooted too quickly
(during
the window after the module was compiled but before it was signed.).


> So I uninstalled the kmod-nvidia module, and did a force re-enroll of
> the uefi signed key (potentially with a new key), and then rebooted to
> go through the mokutil enrolment required at boot. This did not resolve
> the Plasm start issue, so I loaded Gnome.
> Once in Gnome I started Firefox Nightly to do some net searches to see
> if I could find a solution, and the one thing that did happen at this
> point was the boot did not display the "falling back to nouveau"
> message, but the start of firefox displayed a message that a gpu
> couldn't be found on pci. Looking for a resolution to this I found an
> entry about, as part of installed nvidia drivers, to ensure the gpu
> firmware was also installed.
> So I did a dnf install nvidia-gpu-firmware which was then installed as
> it hadn't been already.
>

If you had installed nvidia-??? from a 3rd party repo the Fedora firmware
package might not be required, but it is needed for nouveau.


> After installing the firmware I rebooted and started Plasma, which
> successfully started without issues, and when I checked the video driver
> it was finally using the nvidia driver.
> This was a lot of work to resolve, and is the worst experience I've had
> with any fedora system upgrade.
>

Blame Nvidia for forcing Fedora into convoluted workarounds instead of
helping make older hardware work on current kernels.

Rpmfusion is having difficulties finding volunteers to package software.
Fewer volunteers have access to older hardware and those that do are
getting old themselves and may be dealing with the problems facing older
people in our society, so rpmfusion falls down in their priority list.

-- 
George N. White III
--
___
users mailing