Fedora 39 - 40

Ask Fedora
, , ,
1

Hi, first time posting so bare with me

I have an issue with the updates

I’d love to go to Fedora 40 when I think it’s ironed out the issues (one the issues of concern, people have had trouble with extended monitors, that kind of thing) I’ll be there like a shot

However, I’m waiting at the moment

When you go to updates through Discover on 39, you have this kind of nag screen telling you to update to 40.

The thing is you have to be careful, when you are trying to update, to not click something that kicks off the install of 40

Further, the update icon is there all the time, but nine times out of ten, if you click it, it’ll be just the update for 40 that’s available

Is there a way to turn the nags off until I really want to upgrade to 40?

Thank you in advance

2

From Site Help & Feedback to Ask Fedora

3

Added discover, kde and removed Site Help & Feedback, question

4

Hi and welcome to Fedora.
I think there is a simple answer to your question:

Is there a way to turn the nags off until I really want to upgrade to 40?

In about 3-4 months from now we will have Fedora 41 and although the nagging to upgrade to 40 will be gone, it will be replaced by upgrading to 41. :upside_down_face:
Fedora versions have a reasonably short lifespan. After half a year there is a new release and after (I think) 13 months
(Fedora Linux Release life cycle)
it will be abandoned which means no more updates.
So either you keep up the pace and upgrade now so you will get a few months without nags or you will have them constantly.

I installed 40 before it was officially released and it works great. I have a laptop with an external monitor attached to it, no idea if you could call that setup an extended monitor system, but it works great. No reason not to install the upgrade, or as I do it install the new version to make sure I get what I want. I have no experiences with the Fedora updater but earlier this year I tried to upgrade a neighbors laptop using a different Linux distro and as soon as the script started the screen was filled with error messages. I let it finish but booting into the newer version did of course not work so I had to do a fresh install after all. Again, I never used the Fedora updater so I can not say if it works or not, probably yes cause I see no messages here telling other wise.

This turned out longer than I first thought but I hope I made things clear for you.
Whatever you do, always make sure you have good backups of your data cause there is nothing so terrible as to (finally) have the system running again and to find out your data is gone.

Success.

5

If you boot the live USB installer image for the desktop that you use you can see if f40 works with your hardware.

If you can share system details people can comment on if they have a working version like yours. What is the output of inxi -Fzxx? Please post a pre-formatted text.

6

Hi JandeMus, I was buoyed by your confidence in F40, and I do take your point about the system’s short lifespan.

I didn’t realise that. So, I’ve been meaing to try Rsync but I didn’t get around to it yet, but now the opportunity to use it.

If I back up my system there’s little to be concerned about, so I’ll begin the back ups and bite the bullet, upgrading to F40

By the way, this is the first time I’ve joined a Linux community, despite using Linux as my prime system (I used so many distro’s, but never being quite happy with them, until Fedora)

I’m very impressed by, not only the time it took to get replies, next day, but also the quality of the advice I was given

I have a bit of a challenging illness, that affects mm mentally, so I’m not so quick and insightful as I was. I can’t tell you how much I appreciate the non-judgemental advice given to me by yourself and other users

Kudos

Marianne

7

Hi Binary Star, your advice was very welcome, because I failed to make that particular connection. It seems obvious now that you have said, that I could get the system working completely, on both monitors, before I commit. Thank you for your reply and the promptness of it.

I am going to post the results of inxi -Fzxx now, partly because I need to learn to do it, and of course I should be doing that as a matter of course every time I ask a question

If you happen to visit ths post again will you check if I’m doing it right

Thanks once again for your timely advice, I do appreciate it

Marianne

System:
  Kernel: 6.9.9-100.fc39.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.40-14.fc39
  Desktop: KDE Plasma v: 5.27.11 tk: Qt v: 5.15.13 wm: kwin_x11 dm: SDDM
    Distro: Fedora Linux 39 (KDE Plasma)
Machine:
  Type: Laptop System: PC Specialist product: GK7NR0R v: Standard
    serial: <superuser required>
  Mobo: TongFang model: GK7NR0R v: Standard serial: <superuser required>
    part-nu: 0001 UEFI: American Megatrends v: N.1.10PCS00 date: 05/29/2020
Battery:
  ID-1: BAT0 charge: 46.7 Wh (100.0%) condition: 46.7/46.7 Wh (100.0%)
    volts: 12.2 min: 11.4 model: standard serial: <filter> status: full
  Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard
    serial: <filter> charge: 55% (should be ignored) status: discharging
CPU:
  Info: 8-core model: AMD Ryzen 7 4800H with Radeon Graphics bits: 64
    type: MT MCP arch: Zen 2 rev: 1 cache: L1: 512 KiB L2: 4 MiB L3: 8 MiB
  Speed (MHz): avg: 1616 high: 4291 min/max: 1400/2900 boost: enabled cores:
    1: 1683 2: 1400 3: 1397 4: 1400 5: 4291 6: 1400 7: 1400 8: 1400 9: 1399
    10: 1396 11: 1400 12: 1700 13: 1400 14: 1400 15: 1395 16: 1400
    bogomips: 92633
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: NVIDIA TU106M [GeForce RTX 2060 Mobile] vendor: Tongfang Hongkong
    driver: nouveau v: kernel arch: Turing pcie: speed: 2.5 GT/s lanes: 8 ports:
    active: HDMI-A-1 empty: DP-1,DP-2 bus-ID: 01:00.0 chip-ID: 10de:1f15
  Device-2: AMD Renoir [Radeon Vega Series / Radeon Mobile Series]
    vendor: Tongfang Hongkong driver: amdgpu v: kernel arch: GCN-5 pcie:
    speed: 16 GT/s lanes: 16 ports: active: none off: eDP-1 empty: none
    bus-ID: 06:00.0 chip-ID: 1002:1636 temp: 44.0 C
  Device-3: Chicony HD Webcam driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 bus-ID: 3-4:4 chip-ID: 04f2:b641
  Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 23.2.7
    compositor: kwin_x11 driver: X: loaded: amdgpu,modesetting
    unloaded: fbdev,vesa dri: radeonsi gpu: amdgpu,nouveau display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96
  Monitor-1: HDMI-A-1 mapped: HDMI-1-1 pos: primary model: Samsung
    res: 1920x1080 dpi: 305 diag: 184mm (7.2")
  Monitor-2: eDP-1 mapped: eDP note: disabled model: BOE Display 0x07b6
    res: 1920x1080 dpi: 128 diag: 438mm (17.3")
  API: EGL v: 1.5 platforms: device: 0 drv: nouveau device: 1 drv: radeonsi
    device: 2 drv: swrast surfaceless: drv: nouveau x11: drv: radeonsi
    inactive: gbm,wayland
  API: OpenGL v: 4.6 compat-v: 4.3 vendor: amd mesa v: 23.3.6 glx-v: 1.4
    direct-render: yes renderer: AMD Radeon Graphics (radeonsi renoir LLVM
    17.0.6 DRM 3.57 6.9.9-100.fc39.x86_64) device-ID: 1002:1636
  API: Vulkan v: 1.3.275 surfaces: xcb,xlib device: 0 type: integrated-gpu
    driver: N/A device-ID: 1002:1636 device: 1 type: cpu driver: N/A
    device-ID: 10005:0000
Audio:
  Device-1: NVIDIA TU106 High Definition Audio vendor: Tongfang Hongkong
    driver: snd_hda_intel v: kernel pcie: speed: 2.5 GT/s lanes: 8
    bus-ID: 01:00.1 chip-ID: 10de:10f9
  Device-2: AMD Family 17h/19h HD Audio vendor: Tongfang Hongkong
    driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
    bus-ID: 06:00.6 chip-ID: 1022:15e3
  API: ALSA v: k6.9.9-100.fc39.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.0.7 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Tongfang Hongkong driver: r8169 v: kernel pcie: speed: 2.5 GT/s
    lanes: 1 port: e000 bus-ID: 02:00.0 chip-ID: 10ec:8168
  IF: enp2s0 state: down mac: <filter>
  Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie:
    speed: 5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 8086:2723
  IF: wlo1 state: up mac: <filter>
  IF-ID-1: nordlynx state: unknown speed: N/A duplex: N/A mac: N/A
Bluetooth:
  Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 bus-ID: 5-4:3 chip-ID: 8087:0029
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.2
    lmp-v: 11
Drives:
  Local Storage: total: 1.59 TiB used: 147.34 GiB (9.0%)
  ID-1: /dev/nvme0n1 model: M2 Series NVMe SSD 250G size: 232.89 GiB
    speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 32.9 C
  ID-2: /dev/nvme1n1 model: M2 Series NVMe SSD 500G size: 465.76 GiB
    speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 30.9 C
  ID-3: /dev/sda vendor: Seagate model: Expansion SW size: 931.51 GiB
    type: USB rev: 3.2 spd: 5 Gb/s lanes: 1 serial: <filter>
Partition:
  ID-1: / size: 115.87 GiB used: 16.88 GiB (14.6%) fs: btrfs dev: /dev/dm-0
    mapped: luks-e1ce4216-25b2-48c6-8ba7-8be6af0a3f52
  ID-2: /boot size: 973.4 MiB used: 448.9 MiB (46.1%) fs: ext4
    dev: /dev/nvme0n1p4
  ID-3: /boot/efi size: 96 MiB used: 42.6 MiB (44.4%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 115.87 GiB used: 16.88 GiB (14.6%) fs: btrfs
    dev: /dev/dm-0 mapped: luks-e1ce4216-25b2-48c6-8ba7-8be6af0a3f52
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 63.6 C mobo: N/A gpu: amdgpu temp: 46.0 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 32 GiB note: est. available: 30.76 GiB used: 4 GiB (13.0%)
  Processes: 675 Power: uptime: 3h 22m wakeups: 0 Init: systemd v: 254
    target: graphical (5) default: graphical
  Packages: pm: flatpak pkgs: 9 Compilers: gcc: 13.3.1 Shell: Bash v: 5.2.26
    running-in: konsole inxi: 3.3.34
9

I’ve just thought, when I mentioned ‘extended’ monitor, I got mixed up, I did mean to say ‘external’ monitor, sorry about that

Take care, Marianne

10

You will likely want to use the rpmfusion nvidia packaged drivers so that you get good Wayland support.

Your hardware should just-work on f40.

11

Added dnf-system-upgrade, f40, kde-plasma and removed kde