From Newsgroup: alt.os.linux.fedora

I have 39 and when I go to upgrade it gets about 10% through then it says:

==
Could not depsolve transaction; 1 problem detected:
Problem: package kernel-modules-6.3.4-201.fc38.x86_64 from @System requires kernel-uname-r = 6.3.4-201.fc38.x86_64, but none of the providers can be installed
- conflicting requests
==

Maybe I missed a Kernel update somewhere before it hit EOL ?

--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.fedora

"UFO" <tech@parts-link.net> writes:

I have 39 and when I go to upgrade it gets about 10% through then it says:

Problem: package kernel-modules-6.3.4-201.fc38.x86_64 from @System
requires kernel-uname-r = 6.3.4-201.fc38.x86_64, but none of the
providers can be installed

You say you have 39, but seems you have parts of kernel 38 installed.
Assuming you still haven't updated, try the following:

sudo dnf erase $(rpm -q -a | grep "^kernel.*38" | grep -v -e $(uname -r) -e headers -e macros

-- HASM
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.fedora


Yes, well the boot menu has about the last (5) versions of Fedora
selectable. I was figuring you could just boot to any of those
but never tried it. Each time I upgraded, it left the prior menu
item there and added the new version to the list.

You say you have 39, but seems you have parts of kernel 38 installed. Assuming you still haven't updated, try the following:

sudo dnf erase $(rpm -q -a | grep "^kernel.*38" | grep -v -e
$(uname -r) -e headers -e macros

-- HASM

--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.fedora

I pasted that command into the terminal command line,
nothing seemed to happen. The next line was not showing the [user@fedora:] typical command prompt it was just a ">" with a solid block flashing on and off
and it stopped. If you hit return, it would just make another prompt that looks like that.

I saw the boot menu is showing about (4) options for other versions of 38
after previous updates were installed. The last line is a rescue
environment.

I booted to the last option for 38, and when it finished, I was pretty much
in 39
and again had the same issue with that command in terminal.

--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.fedora

I pasted that command into the terminal command line,
nothing seemed to happen.

One of the greps is waiting for input, probably the last one.
Run this instead:

sudo dnf erase $(rpm -q -a | grep "^kernel" | grep -v -e $(uname -r) -e headers -e macros

After this the only kernel rpms in your system should be the one for the running kernel. If you're updating via "dnf upgrade" then you'll need
to run the "refresh" step again, if not using "dnf upgrade" upgrade the
same way you tried before.

Or you could try deleting the offending rpm directly:

sudo dnf erase kernel-modules-6.3.4-201.fc38.x86_64

-- HASM
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.fedora


The first line did the same thing, the 2nd one worked,
and it upgraded however the first boot says (2) services
fail to run and they loop forever with that message after
a period of time.

I will post them here next time I boot.

"HASM" <hasm@example.invalid> wrote in message news:87ttiaw5i6.fsf@127.0.0.1...

I pasted that command into the terminal command line,
nothing seemed to happen.

One of the greps is waiting for input, probably the last one.
Run this instead:

sudo dnf erase $(rpm -q -a | grep "^kernel" | grep -v -e $(uname -r) -e headers -e macros

After this the only kernel rpms in your system should be the one for the running kernel. If you're updating via "dnf upgrade" then you'll need
to run the "refresh" step again, if not using "dnf upgrade" upgrade the
same way you tried before.

Or you could try deleting the offending rpm directly:

sudo dnf erase kernel-modules-6.3.4-201.fc38.x86_64

-- HASM

--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.fedora


Ok it says FAIL in a continual loop stating these failed to start:

auditd.service
cups.service



--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.fedora


Found this place had a similar problem and fixed it:

https://forums.linuxmint.com/viewtopic.php?t=412337

Would I be interrupting the normal boot process by holding
a function key to get at the command prompt?

Should I try their fix or do u recommend something else? Thanks.
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.fedora

HASM <hasm@example.invalid> scripsit:

I pasted that command into the terminal command line,
nothing seemed to happen.

One of the greps is waiting for input, probably the last one.
Run this instead:

#v+
sudo dnf erase $(rpm -q -a | grep "^kernel" | grep -v -e $(uname -r) -e headers -e macros
^^(1) ^^(2) ^(2)
#v-

Unbalanced command substitution parantheses, the should be a closing one
at the line end.

Sorry for the late reply,
--
Regards Florian; German native by language, trying to improve
his English, Latina, Fran|oais, Espa|#ol and Polski skills.
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.fedora

Florian Rehnisch <fmr@sdf.org> writes:

HASM <hasm@example.invalid> scripsit:
#v+
sudo dnf erase $(rpm -q -a | grep "^kernel" | grep -v -e $(uname -r) -e headers -e macros
^^(1) ^^(2) ^(2) Unbalanced command substitution parantheses, the should be a closing one
at the line end.

Just checked my alias for the above and the closing parenthesis is there!
Must have been a copy/paste failure, sorry.

-- HASM
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.fedora


Hmm, could you give me a screenshot posted on maybe https://imgbb.com/
site showing a command prompt window with the entire command typed in?

#v+
sudo dnf erase $(rpm -q -a | grep "^kernel" | grep -v -e $(uname -r) -e headers -e macros
^^(1) ^^(2) ^(2)
#v-

--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.fedora

Hmm, could you give me a screenshot posted on maybe https://imgbb.com/
site showing a command prompt window with the entire command typed in?

sudo dnf erase $(rpm -q -a | grep "^kernel" | grep -v -e $(uname -r)
-e headers -e macros

Alternatively you could use the "official" fedora suggestion, here:

https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/#sect-clean-up-old-kernels

-- HASM
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.fedora

Well earlier in the thread, I booted to an older version in the Grub menu to get in to that version to get to the command prompt, but now its just
saying the version is no longer supported and stops dead.

I decided to try a fresh install from a Ver 40 disc so I burned one from the file I downloaded
online called : Fedora-Workstation-Live-x86_64-40-1.14

It booted to Grub ok from the CD, then when I chose either the direct love load or the media test
it went to a flashing prompt in the upper left of the screen and the had
light on the desktop stayed lit constantly
while the busy light on the DVD drive flashed rapidly.

I thought it was a bad burn, but slower speed did same thing. I alternately tried
another download mirror and burned from that but same problem

alt-control-del made the verbose screen come up and it was saying something like a bad sector on the
media. Its brand new CDR burned at 2x speed, very slow so must be the ISO is corrupt?

--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.fedora


So I looked around and there is a Ver 41 and
its in a KDE Plasma type flavor, so I will try that
ISO and see if I have better luck.


--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.fedora


Same thing with this CD too...did they ditch legacy hardware recently?
Seems to have trouble reading the media, but I can see the folders fine
in a Windows OS, looks like it burned fine.
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.fedora

Ok it worked, I had to leave it in there in that weird state,
like it was froze but it was I guess actually doing something.
Would be neat to have a verbose splash screen or something
so u know it didnt lock up. Must be a new looking boot loader.
--- Synchronet 3.21d-Linux NewsLink 1.2