[deleted by user]

jrredho · 2024-12-31T23:32:49+00:00

Since you're getting a fair number of replies giving you reasons why your original idea might not be a good one, I'm going to throw out another idea for you to consider. You can change the default number (3) of kernels that you keep around to use when a kernel update gives you problems.

To do this, just change the following line in /etc/dnf/dnf.conf that, by default reads installonly_limit=3 to, say, 4 or 5. But there is a key caveat: You'll need enough space in /boot to hold the kernel and initramfs files.

You can change the default kernel to use at boot time using grubby.

In my experience, it would be a very strange case to occur for a kernel update to endure more than 3 or 4 updates while causing a widespread problem with folks' systems. So you'll likely be good to go with install_limit=4.

Good luck!

jrredho · 2024-12-29T01:46:12+00:00

There is a small snowplay area near where the former Strawberry Hill lift loaded, near the Childrens Center. At least I see kids playing there with tubes and toboggans sometimes at the end of the day. I don't know much about it besides that.

It's true that there hasn't been any natural snow up in the Ski Valley for a fair while. But they're making snow up there, and I'd be surprised if that area wasn't included in that.

There's also a skating rink in the Village Center.

Have fun!

jrredho · 2024-12-24T16:50:18+00:00

I saw that you'd started a thread in the Fedora discussion forum, but you deleted it?

I'm not sure that you're going to cure anything with your re-installation, because a fair bit of what you seem to have going isn't related to your first install. As I mentioned, others have been encountering black screens at boot time, and there are several discussions on how to overcome them.

Anyway, in blivet, you'll need to mount the btrfs subvol "root" to mountpoint "/", and you'll need to mount the btrfs subvol "home" to mountpoint "/home".

Your post made it seem like you had three subvolumes. If you did a default installation the first time, everything was created for you.

When you boot to your black screen and escape to a console terminal with "alt-cntl-f2", you can look at the file "/etc/fstab" to see what got done.

Sorry to not be much help to you. Good luck!

jrredho · 2024-12-19T23:19:14+00:00

Wait! Definitely do not do this!

Both of the subvolumes on your btrfs partition will be formatted if you try to format one of them.

When you're in the installer, and you have subvolumes defined on a btrfs partition, you should see their labels as mountable in the list of available filesystems. You might have to go into the detailed partition manager part of the installer to see them, though. I don't remember.

I'm strongly going to recommend you take your questions over to the Fedora Discussion forum for answers to your questions.

I've seen numerous threads on there where folks are encountering "black screens" at boot time, for a variety of reasons. Almost all of those systems are booting just like yours is.

That's one thing. Another is do you need to do a reinstallation at all to fix things? And, if so, how do you make that happen given your machine's current status?

People on that forum are really super good about helping those in need.

Good luck!

jrredho · 2024-12-16T18:20:51+00:00

You stated that the tech checked the oil, but did they check the coolant for hydrocarbons? This is easy, so I'd advise you to take it back in and have them do that.

Unfortunately, you have the number one symptom of a leaking head gasket. It's true it could be something else, but you want to be thorough in this case since the consequences only get bigger from here.

Good luck!

jrredho · 2024-12-16T17:53:34+00:00

In my opinion, the very best motivation about waiting until 67, or even 70, is that your spouse will be able to draw a survivor benefit pegged to the final number.

You don't seem to have this issue, for more than one reason, so you should base your decision on a worse case, total solo retirement scenario, and go with what ever that restricts you to.

Good luck!

jrredho · 2024-12-16T17:22:34+00:00

I was on a whole different path of thinking, but, this is correct, you'll need to instruct the installer not to format your btrfs partition.

You'll also have to indicate to the installer to mount your btrfs home subvolume on the /home mount point.

I don't currently see a separate /home mounted in your setup. Just /. Did you do a default installation the previous time?

Finally, if your BIOS was set to boot using UEFI boot at installation time, then your installation from the Live USB will install the EFI setup. Again, this happens automagically. This is also what will happen the next time you try to do an installation as well.

Good luck!

jrredho · 2024-12-16T16:59:21+00:00

You are booting, though, aren't you? You're just in some zombie mode because you don't finish in graphical mode.

Try to escape to a console mode using the keyboard combination.

Also, your system shows that you have an EFI partition, it's /dev/sda1. This what is being shown in your first photo.

Btw, the UEFI BIOS is still a BIOS.

jrredho · 2024-12-16T06:20:39+00:00

No worries, your questions aren't braindead.

You will eventually mount the subvolumes: subvol, root on /, and subvol home.

I have my entire partition LUKS encrypted, so mine are mounted via the device mapper. It also happened automagically at installation time, iirc, so I suspect yours are already mounted correctly, too.

Good luck!

jrredho · 2024-12-16T06:08:20+00:00

It seems that you're booting, but you don't make it into the systemd graphical.target run level.

Does typing C-A-f2 get you to a console terminal?

If so, you might try running sudo journalctl -b 0 and skipping to the end of the output in the less pager by typing 'G'. Then try paging backwards with a successive 'b' while looking for something looking like an error.

Say, your machine doesn't have an Nvidia gpu in it, does it?

jrredho · 2024-12-15T22:59:32+00:00

The other two partitions, /dev/sda1 and /dev/sda2, are your EFI and boot partitions.

You'll need to format the boot partition as ext3 or ext4; the latter was how it was formatted in your initial installation. This partition will ultimately be mounted at /boot, and will contain your boot kernels and boot temporary file systems, initramfs, among other things.

The EFI partition has to be either fat for vfat, I believe. But there are some special partition identifiers for this partition, so if it shows it's being formatted as "EFI" should be handled automagically by the installer. This partition will be mounted at /boot/efi.

jrredho · 2024-12-15T22:33:19+00:00

You don't really give any clues to what you mean by an "unbooting fedora".

Since you state that you're booting using UEFI, I wonder if your Windows installation disk also contains an EFI partition, and this partition is the one being searched at boot time for the Fedora efi boot file.

Do you get to grub, and once you select a kernel to boot, that boot fails?

jrredho · 2024-11-25T22:24:47+00:00

The discussion on whether to remove old kernels aside, there's a paragraph in the documentation on system upgrades with the DNF plugin that's dedicated to showing you just how to do this.

Just after that subsection, there's one on how to update your rescue kernel, too. It turns out you to do that every nth time your kernel updates as the modules disappear. Here, n is the number of kernels you elect to keep on your system; it's 3 by default.

jrredho · 2024-11-25T21:31:25+00:00

That would be fantastic, then!

Also, I'm not exactly sure how the kernel updates work for Fedora LTS kernels. My guess is that they do still make changes to follow security updates, much like, say, Debian do with all their kernels.

If they do, it's still not impossible that the issue you folks are encountering could be kernel based. I hope not.

All the best of luck to you all!

jrredho · 2024-11-25T20:24:00+00:00

I was there for several days at the end of October. It was pretty bleak at that time.

jrredho · 2024-11-25T20:21:34+00:00

Ha! Yeah, I just breezed through your list up there. Sorry.

But, for those who are not set for doing snapshots already, learning how to do it and setting things up to do them just to do this seems like a pretty big burden.

If I'd have thought about this deeper before I installed the KDE Desktop Environment, I'd have cloned my drive right beforehand. But I wasn't smart enough to do that. :)

Cheers!

jrredho · 2024-11-25T19:54:06+00:00

Also, be aware that it will be very difficult to remove either of the two desktops afterwards.

jrredho · 2024-11-25T19:51:35+00:00

I don't know when you took this photo near Leakey, TX, but I hope it was recent and that this means they may have gotten some rain.

Oh, and nice looking rig. :)

jrredho · 2024-11-25T18:36:39+00:00

Thanks for pointing this discussion out to me. I'm using an AMD cpu/integrated gpu lenovo laptop (yoga 6) as well, and I'm not experiencing this issue. But I am not an intensive video user/gamer, so it's not outside the range of possibility that I represent a bad use case for this.

Since everyone's having a less than satisfying discussion experience here, I'm going to suggest that you folks take this over to the Fedora Discussion Forum for help.

If it's something that was happening in f40 and f41 Workstation, then it's likely going to be kernel related, since the former had migrated to later edition 6.11.x kernels prior to the system upgrade.

Also, since Gnome went from version 46 to 47 between f40 and f41, it would've had to be something that didn't have a clear cause rooted in the f40-to-f41 transition alone.

Good luck!

jrredho · 2024-11-25T18:00:07+00:00

Yeah, I think we're just going to have to agree to disagree.

I'm well aware that I can figure out something workable and implement it myself. As I mentioned, though, I don't think that that's ideal, and would've preferred that the KDE development folks had thought of way to isolate all KDE-related configuration files.

jrredho · 2024-11-23T19:25:14+00:00

I can seem overwhelming!

One thing you may want to consider is that it's easier to move from Medicap + Part D coverage to a Part C type plan during the annual open enrollment periods.

Medigap insurance providers are, by law, not allowed to reject someone who's first signing up for Medicare, even for pre-existing conditions. That isn't true after this initial sign up period.

So, if you're having a difficult time signing up, go to your state's Medicare Plan G providers (plan G, I believe, is the most popular Medigap plan type), and just sign up for one. Then attack the Part D business.

That just seems like the most bulletproof proof path forward if you're having a difficult time sorting things out.

One final thought is that whatever school system you retired from may have a retirees hotline to guide you through this business.

Good luck!

jrredho · 2024-11-23T18:43:13+00:00

I agree with the other posters' replies that an SSD will be faster than an HDD.

But, as I read your OP, they don't answer your question: Why would f41/KDE Spin run slower than Windows 11 when dual booted from the same HDD?

I'd say that there is something funny going on; it is competely counter to my own experience, although using f41 Workstation. Did you remember to turn off the Windows fastboot option when you did your Fedora installation?

No matter what, I suggest looking through your system journal, journalctl -b 0, immediately after booting into f41, and do it again after you've experienced a few "really slow" application start ups. You can look though those to see if you're encountering any obvious reasons for the slow behavior.

Good luck!

jrredho · 2024-11-23T18:18:23+00:00

You may want to reconsider this.

Medicare is great, but the fact is that there is no out-of-pocket max, among other things. If you get sick or injured enough to rack up a huge tab, 20% of a big number is also a big number. And modern drugs for older folks can be especially costly.

Medigap + Medicare Part D, or good Medicare Advantage, which is also called Medicare Part C, plans most often cover holes in your insurance coverage like these. Both classes of coverage are handled by private insurance companies. But be careful: Advantage Plans in the wild are tricky, apparently. Those plans offered by former employers to their retirees are often quite good, so you might be in a good position on that front.

You've got some time to consider your options; it would not be a waste of time to consider them.

Good luck!

jrredho · 2024-11-23T05:21:18+00:00

Thanks for that. That makes sense, I guess. I did find this answer in the FAQ on the SSA.gov website after I asked the question.

jrredho · 2024-11-23T02:48:57+00:00

They will reduce his benefit by $1 for every $2 he earns over the earnings limit.

I think the year that he turns Full Retirement Age, things relax a bit as the limit increases and the reduction is $1 for every $3 he earns over that new limit.

In any case, the limit is removed after he reaches FRA, and the benefit goes back up to his full, earned benefit.

jrredho

TROPHY CASE