Hi all,

Edit: I use the KDE spin of Fedora 40 (updated after I posted this) and have a Windows 10 partition. However, I am not able to boot into Windows as it doesn’t show up in GRUB.

I’ve been encountering some frustrating issues with my Fedora Linux installation and I’m hoping someone here might be able to offer some guidance or solutions. I’m gonna post them all in this thread - please tell me if I should break each issue into individual

  1. Time Setting: I’ve noticed that my system time doesn’t seem to be setting correctly, even when I have automatic time synchronization enabled. The time in my BIOS is correct. Even when I try to set the time manually, it reverts back to the wrong settings.

  2. Persistent Wi-Fi Password Prompts: Despite having saved my Wi-Fi password in the connection settings within KDE, I’m constantly being asked to re-enter it every time I connect. It’s a bit of a hassle, My credentials are saved.

  3. Browser Rendering Issues: When using both Chrome and Firefox on Fedora, I’ve noticed that certain websites, like Arduino.cc, don’t load images or schematics properly. For example, when I try to access https://docs.arduino.cc/built-in-examples/basics/Blink/ the images fail to load. Strangely, I don’t encounter this problem when using the same browsers on my Windows desktop. I have also tried to start Firefox in “fail safe” mode without addons enable but it does not make solve the issue.

  4. Dual Boot Trouble: During the installation process, I managed to break my dual boot to Windows, which didn’t happen when I initially tried out Linux Mint. The Linux Mint installer automatically managed to make my system dual boot through GRUB. However, I probably messed up in the Fedora installation process, and now I don’t know how to fix it.

  5. Driver Discovery: Despite enabling RPM Fusion for the Nvidia Driver, I cannot find the driver in the Discover app. Is there a step I might be missing, or a different approach I should take to locate and install the Nvidia driver?

My hwinfo, using hwinfo --short:, removed keyboard, mouse etc.

cpu:

11th Gen Intel(R) Core(TM) i7-1185G7

graphics card:

nVidia TU117M [GeForce MX450]

Intel TigerLake-LP GT2 [Iris Xe Graphics]

sound:

Intel Tiger Lake-LP Smart Sound Technology Audio Controller

storage:

Samsung Electronics NVMe SSD Controller PM9A1/PM9A3/980PRO

network:

wlp0s20f3 Intel Wi-Fi 6 AX201

enp0s31f6 Intel Ethernet Connection (13) I219-LM

network interface:

enp0s31f6 Ethernet network interface

lo Loopback network interface

wlp0s20f3 Ethernet network interface

disk:

/dev/nvme0n1 Samsung Electronics NVMe SSD Controller PM9A1/PM9A3/980PRO

/dev/zram0 Disk

partition:

/dev/nvme0n1p1 Partition

/dev/nvme0n1p2 Partition

/dev/nvme0n1p3 Partition

/dev/nvme0n1p4 Partition

/dev/nvme0n1p5 Partition

/dev/nvme0n1p6 Partition

/dev/nvme0n1p7 Partition
  • narc0tic_bird
    6·
    7 months ago

    1. If you dual-boot into Windows, that’s probably what sets the time. Linux expects the time in the BIOS to be set to UTC by default, Windows does not. You can change some registry entry in Windows so it uses UTC as well.

    2. Might be related to 5.

    3. Discover is (mostly) for GUI applications. Follow this guide to install the NVIDIA driver.

    • alephEnglish
      3·
      7 months ago

      For #1, I found it easier to force the Linux installation to use local time instead of UTC by running the following in a terminal:

      timedatectl set-local-rtc 1 --adjust-system-clock

    • deczzz@lemmy.dbzer0.comOP
      1·
      7 months ago

      The problem is that I am not able to boot into Windows. I don’t have the option when I boot into GRUB. My thinking is that it does not have to do with windows setting the time.

  • boredsquirrel@slrpnk.net
    2·
    7 months ago

    You may find more help on https://discussion.fedoraproject.org

    First: please mention “I am dual booting the Fedora KDE spin with Windows” at the top, to make things clearer :)

    But lets see.

    1.

    It’s e the time in my BIOS is correct.

    Dont understand that sentence. But this may be a typical windows thing, as Windows is changing the BIOS time to the one used, while Linux normally keeps the BIOS time normal and uses the offset (like UTC+3).

    Have a look at this page, ItsFoss is awesome

    timedatectl set-local-rtc 1

    2.

    This sounds like a KDE Wallet issue.

    Under systemsettings, see your KDE Wallet settings. Do you have a wallet set as default, that was created by default?

    The default wallet uses your login password and gets opened with the login from SDDM. If you changed your login password, or something else, this doesnt work.

    In the network settings, did you select “save password for this user (encrypted)” or “save password for all users (unencrypted)”? For wifi passwords you could use that as a fallback, its actually more secure in some scenarios afaik, as only plasma can read it.

    3.

    You are using an nVidia card, did you install any drivers? Nvidia didnt care for linux way too long. You may want to install them manually.

    As your system is fresh, and as you need Nvidia drivers, I highly recommend switching to universal blue. Their kinoite-nvidia image has all the drivers and settings, and if something breaks, it is at their end and you will not get the update.

    I really cant recommend some hacky way to install the drivers, blacklist nouveau, enable the drivers etc.

    ublue.it

    I use kinoite-main daily, it is awesome. Atomic/image based Fedora is way better.

    Note though that dualbooting is not as easy it seems.

    (The rpm-ostree variants are now called “Atomic Desktops” but not long, in the past the GNOME “Fedora Silverblue” was the most dominant)

    4.

    Linux Mint uses legacy boot and is not secureboot compatible. Fedora should actually cause less problems.

    Search on Fedora Discuss, this is also a common problem with a fix.

    5.

    Discover only shows graphical apps, you install it from the Terminal (Konsole).

    But as I said, I do not recommend installing NVidia drivers on your own on Fedora, as it has too many updates and sometimes drivers break. This happens way too often.

    Also to use them you will need to make some more small changes to some files, it is not complex but a few steps.

    I recommend kinoite-nvidia by ublue, or as ublue has this as their main variant, Aurora:

    https://getaurora.dev/

    • deczzz@lemmy.dbzer0.comOP
      1·
      7 months ago

      Thanks for your detailed reply.

      1. The solution for setting the clock seem to work! Awesome.

      2. I don’t have kWallet enabled but saving the password as unencrypted in the network settings.

      3. Hmm, I just installed akmod-nvidia.x86_64 with dnf. Tried to run nvidia-settings in terminal. I get this error:

      ERROR: NVIDIA driver is not loaded

(nvidia-settings:14910): GLib-GObject-CRITICAL **: 14:10:49.551: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

** (nvidia-settings:14910): CRITICAL **: 14:10:49.552: ctk_powermode_new: assertion '(ctrl_target != NULL) && (ctrl_target->h != NULL)' failed
          1. I guess I need to hop distro again! :( But it will probably be faster than fixing
      • boredsquirrel@slrpnk.net
        1·
        7 months ago
        1. Then maybe try to use Kwallet. Create a new one using KwalletManager, use blowfish, set your login password. In systemsettings enable it as default.

        The process is overcomplicated poorly.

        1. The steps are more. As I said, you need to blacklist the opensource nouveau (which seem to work well but not completely) and set the.proprietary ones to be loaded. UBlue does that for you.
  • Guenther_Amanita@feddit.de
    2·
    7 months ago

    I think a lot of these problems (time settings, etc.) are because of Windows.

    Maybe get a second drive and install Aurora or Bazzite on that.
    Nvidia drivers and other stuff is included ootb and Fedora Atomic images always were way smoother than the KDE spin in my experience.

  • Chemical Wonka@discuss.tchncs.deEnglish
    1·
    6 months ago

    I tried out Fedora days ago and faced so many problems that I switch to Manjaro. Never going back to Fedora. I opened Super Tuz Kart and my CPU reached 90% and the fans on maximum. I had installed all drivers and nothing solved my problem .

    • deczzz@lemmy.dbzer0.comOP
      1·
      7 months ago

      Yes. I actually got another issue. abrt-applet “encounters a problem”. No idea why or what the application is all about.

      • TurtlePower
        1·
        7 months ago

        So I’m still a newb myself, so my terminology and all that is very lacking so bear with me. abrt-applet is your crash tool. You can use it to report crashes. Am I correct in that you are using Fedora KDE Plasma spin? If yes, upgrade to 40 (it will also upgrade to Plasma 6). It’s had quite a number of updates since it released, so while it is still working out the kinks, if you upgrade and then update it, you’ll get far fewer of those crashes. They will still happen— for me it’s usually Discover that crashes, but if you start the program again, it’ll work. Sometimes you have to let things “settle” before trying to rip open multiple programs at a time. Plasma 6 also has a better crash reporting tool, too. Two things when you do the upgrade: do it from the console and make sure you update all your drivers and everything before you start the upgrade.

  • skeletorsass [she/her]@hexbear.net
    1·
    7 months ago

    Time issue: is Windows using UTC time? If it is not:

    Open regedit in windows

    Navigate HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation

    Create new QWORD here, RealTimeIsUniversal as name

    Set value 1

    Reboot

    • deczzz@lemmy.dbzer0.comOP
      1·
      7 months ago

      I cannot boot into Windows, see point 4. But thanks anyway - might fix the problem if I would be able to boot into Windows.

  • potkulautapaprika@sopuli.xyz
    1·
    7 months ago

    My five cents, you need to set both windows and Linux using the same time base, otherwise it’s just being few hours in the past or future when you boot win(at least 10).

    For the not giving you a dual boot entry, you need to have windows drive mounted so grub’s os-prober finds it, as an aside systemd-boot just picks it up automagically.

    And for point 2: yea definitely a kwallet thing, I have no idea how to wrangle that bastard to do my bidding.