Re: urgent major problem after f39 to f40 upgrade.

On Sun, Oct 13, 2024 at 12:07 AM home user via users wrote: > > On 10/12/24 7:31 PM, Samuel Sieb wrote: > > On 10/12/24 6:13 PM, Jeffrey Walton wrote: > >> I would definitely consider some post-upgrade clean-ups as detailed in > >>

Re: urgent major problem after f39 to f40 upgrade.

On 10/12/24 7:31 PM, Samuel Sieb wrote: On 10/12/24 6:13 PM, Jeffrey Walton wrote: I would definitely consider some post-upgrade clean-ups as detailed in . At minimum, there are some old

Re: Strange behavior with F40 server iso and VM

On 13/10/24 11:17, Paolo Galtieri wrote: Folks,  this is an issue that has me frustrated.  I created a VM under VMware and VirtualBox and allocated 400GB as the disk size.  I installed the F40 server iso on the VM, and it showed the disk size as 400GB, and the install went fine.  However, when

Re: urgent major problem after f39 to f40 upgrade.

On 10/12/24 6:13 PM, Jeffrey Walton wrote: I would definitely consider some post-upgrade clean-ups as detailed in . At minimum, there are some old packages and a lot of dangling symlinks t

Re: Strange behavior with F40 server iso and VM

On Oct 12, 2024, at 20:17, Paolo Galtieri wrote: > > Folks, > this is an issue that has me frustrated. I created a VM under VMware and > VirtualBox and allocated 400GB as the disk size. I installed the F40 server > iso on the VM, and it showed the disk size as 400GB, and the install went >

Re: Strange behavior with F40 server iso and VM

On Sat, Oct 12, 2024 at 8:17 PM Paolo Galtieri wrote: > > Folks, > this is an issue that has me frustrated. I created a VM under VMware > and VirtualBox and allocated 400GB as the disk size. I installed the > F40 server iso on the VM, and it showed the disk size as 400GB, and the > install wen

Re: urgent major problem after f39 to f40 upgrade.

On Sat, Oct 12, 2024 at 8:16 PM Samuel Sieb wrote: > On 10/12/24 5:07 PM, home user via users wrote: > > [...] > >> What does "systemctl status gdm" show now? I have no idea how it got > >> disabled, but if it still is, then try "systemctl enable --now gdm". > > > > It showed "disabled". I enter

Re: Strange behavior with F40 server iso and VM

I'm using the Fedora-Server-dvd-x86_64-40-1.14.iso which I downloaded from the Fedora repository.  After I booted the system I ran df and got: pgaltieri@localhost:~$ df Filesystem  1K-blocks    Used Available Use% Mounted on /dev/mapper/fedora-root  15663104 1763300  13899804  12% /

HDR Support in KDE

HI,     With the last system update I put on (yesterday) I have been upgraded to Plasma 6.2. One of the enhancements in this version was more support for HDR, but even though my monitor is HDR there are no HDR settings in KDE System Settings. Under Gnome with Wayland there are HDR settings. Is

Re: Strange behavior with F40 server iso and VM

On 10/12/24 5:17 PM, Paolo Galtieri wrote: Folks,  this is an issue that has me frustrated.  I created a VM under VMware and VirtualBox and allocated 400GB as the disk size.  I installed the F40 server iso on the VM, and it showed the disk size as 400GB, and the install went fine.  However, w

Strange behavior with F40 server iso and VM

Folks,  this is an issue that has me frustrated.  I created a VM under VMware and VirtualBox and allocated 400GB as the disk size.  I installed the F40 server iso on the VM, and it showed the disk size as 400GB, and the install went fine.  However, when I booted the VM and looked at the disk s

Re: urgent major problem after f39 to f40 upgrade.

On 10/12/24 5:07 PM, home user via users wrote: On 10/12/24 5:35 PM, Samuel Sieb wrote: On 10/11/24 9:36 PM, home user via users wrote: On 10/11/24 9:50 PM, Samuel Sieb wrote: On 10/11/24 8:03 PM, home user via users wrote: On 10/11/2024 7:50 PM, Samuel Sieb wrote: [snip] I assumed that fo

Re: urgent major problem after f39 to f40 upgrade.

On 10/12/24 5:35 PM, Samuel Sieb wrote: On 10/11/24 9:36 PM, home user via users wrote: On 10/11/24 9:50 PM, Samuel Sieb wrote: On 10/11/24 8:03 PM, home user via users wrote: On 10/11/2024 7:50 PM, Samuel Sieb wrote: [snip] I assumed that force would make it compile again, but apparently n

Re: urgent major problem after f39 to f40 upgrade.

On 10/11/24 9:36 PM, home user via users wrote: On 10/11/24 9:50 PM, Samuel Sieb wrote: On 10/11/24 8:03 PM, home user via users wrote: On 10/11/2024 7:50 PM, Samuel Sieb wrote: [snip] I assumed that force would make it compile again, but apparently not. But anyway, the kernel modules shoul

Re: urgent major problem after f39 to f40 upgrade.

On 10/12/24 5:05 PM, Samuel Sieb wrote: On 10/12/24 3:16 PM, home user via users wrote: On 10/12/24 3:58 PM, Samuel Sieb wrote: [snip] I might be treading on old ground here, but the above output is showing that you have nouveau blacklisted so it will not start. If you are booting to a consol

Re: urgent major problem after f39 to f40 upgrade.

On 10/12/24 3:16 PM, home user via users wrote: On 10/12/24 3:58 PM, Samuel Sieb wrote: [snip] I might be treading on old ground here, but the above output is showing that you have nouveau blacklisted so it will not start. If you are booting to a console because your nvidia drivers aren't work

Re: urgent major problem after f39 to f40 upgrade.

On 10/12/24 4:46 PM, Felix Miata wrote: [snip] Try showing us input/output from: systemd-analyze critical-chain -bash.2[~]: systemd-analyze critical-chain The time when unit became active or started is printed after the "@" character. The time the unit took to start is printed after th

Re: urgent major problem after f39 to f40 upgrade.

home user users composed on 2024-10-12 13:35 (UTC-0600): > Felix Miata wrote: >> I believe what is happening to you often happens on several of my faster >> machines. >> The following represents evidence of what happens here using KDM or TDM and >> Xorg/X11: >> # egrep 'dev/dr\|Xorg.0.' /var/lo

Re: urgent major problem after f39 to f40 upgrade.

On 10/11/24 10:36 PM, home user via users wrote: On 10/11/24 9:50 PM, Samuel Sieb wrote: On 10/11/24 8:03 PM, home user via users wrote: Entered it. The screen blanked. After about a minute, the graphical login screen appeared. I was able to log in as root via the graphical login screen. I s

Re: urgent major problem after f39 to f40 upgrade.

On 10/12/24 3:58 PM, Samuel Sieb wrote: [snip] I might be treading on old ground here, but the above output is showing that you have nouveau blacklisted so it will not start. If you are booting to a console because your nvidia drivers aren't working yet allowing nouveau to be used may get you

Re: urgent major problem after f39 to f40 upgrade.

On 10/12/24 2:42 PM, home user via users wrote: On 10/12/24 2:23 AM, Stephen Morris via users wrote: On 12/10/24 14:03, home user via users wrote: On 10/11/2024 7:50 PM, Samuel Sieb wrote: [snip] I assumed that force would make it compile again, but apparently not. But anyway, the kernel mo

Re: urgent major problem after f39 to f40 upgrade.

On 10/12/24 5:46 AM, David King wrote: On 10/12/24 00:36, home user via users wrote: [snip] Earlier in this thread Jeffrey Walton suggested that you do "sudo systemctl set-default multi-user.target" to temporarily set your system to a plain console login while you troubleshoot.  Did you do thi

Re: urgent major problem after f39 to f40 upgrade.

On 10/12/24 2:23 AM, Stephen Morris via users wrote: On 12/10/24 14:03, home user via users wrote: On 10/11/2024 7:50 PM, Samuel Sieb wrote: [snip] I assumed that force would make it compile again, but apparently not. But anyway, the kernel modules should be available. What do the following

Re: urgent major problem after f39 to f40 upgrade.

On 10/11/24 11:58 PM, Felix Miata wrote: home user composed on 2024-10-11 22:36 (UTC-0600): Samuel Sieb wrote: Everything looks good.  Try running "systemctl start gdm". Entered it. The screen blanked. After about a minute, the graphical login screen appeared. I was able to log in as roo

Re: urgent major problem after f39 to f40 upgrade.

On 10/11/24 11:06 PM, Tim wrote: On Fri, 2024-10-11 at 18:47 -0600, home user via users wrote: By the way, I let memtest go through 8 tests before stopping it due to the cpu getting hot. It passed. You might want to check your cooling is adequate, then. I've left memtest running for hours an

Re: urgent major problem after f39 to f40 upgrade.

On 10/12/24 00:36, home user via users wrote: On 10/11/24 9:50 PM, Samuel Sieb wrote: On 10/11/24 8:03 PM, home user via users wrote: On 10/11/2024 7:50 PM, Samuel Sieb wrote: [snip] I assumed that force would make it compile again, but apparently not. But anyway, the kernel modules should

Re: urgent major problem after f39 to f40 upgrade.

On Oct 12, 2024, at 00:36, home user via users wrote: > > On 10/11/24 9:50 PM, Samuel Sieb wrote: >> >> Everything looks good. Try running "systemctl start gdm". > > Entered it. > The screen blanked. > After about a minute, the graphical login screen appeared. > I was able to log in as root

Re: Keyboard Repeat Under Wayland in KDE

> On 12 Oct 2024, at 09:46, Stephen Morris via users > wrote: > > Hi, > I am having an issue at the moment in Eclipse and Konsole and when > composing this message in Thunderbird, in KDE with Wayland, where when I > press the enter key it randomly inputs Enter twice. This issue doesn't

Re: urgent major problem after f39 to f40 upgrade.

On 10/12/24 1:23 AM, Stephen Morris via users wrote: On 12/10/24 14:03, home user via users wrote: On 10/11/2024 7:50 PM, Samuel Sieb wrote: [snip] I assumed that force would make it compile again, but apparently not. But anyway, the kernel modules should be available. What do the followin

Re: urgent major problem after f39 to f40 upgrade.

> On 12 Oct 2024, at 09:23, Stephen Morris via users > wrote: > > I might be treading on old ground here, but the above output is showing that > you have nouveau blacklisted so it will not start. That is the correct install when using the rpmfusion nvidia drivers. Without the black listing n

Keyboard Repeat Under Wayland in KDE

Hi,     I am having an issue at the moment in Eclipse and Konsole and when composing this message in Thunderbird, in KDE with Wayland, where when I press the enter key it randomly inputs Enter twice. This issue doesn't happen in KDE with Xorg, but at the moment that combination is unstable (KD

Re: urgent major problem after f39 to f40 upgrade.

On 12/10/24 14:03, home user via users wrote: On 10/11/2024 7:50 PM, Samuel Sieb wrote: [snip] I assumed that force would make it compile again, but apparently not. But anyway, the kernel modules should be available. What do the following commands show: cat /proc/cmdline grep -rn nouveau /e