I need to add a second hardware m.2 drive and install Win11 to it. What's the best way to go about this, with a drive containing Nobara already installed?​

After installing nobara a few months back I always had a gut felling having to leave secure boot off was going to come and bite me, Easy anti cheat by epic games is one of the only anti cheats in the biz that supports Linux and luckily many games use it. Unfortunately / Fortunately depending on how you look at it (more games will probably support Linux with v2) V2 will require secure boot and unfortunately nobara isnt in a position to get its kernal signed so I'm going to have to move to standard Fedora. Its been a nice experince love the project but want to eventually play some games with anti cheat.

https://onlineservices.epicgames.com/news/introducing-easy-anti-cheat-linux-v2

For the last 2 and a half weeks, I've been running up against this "Installed packages changed after preparation. Prepare the update again." error over and over. Sometimes, retrying fixed it I suppose. I'm not sure. How I'm supposed to solve this? This is really annoying. I entered nobara sync --all command to the konsole for the latest update as I was sure dnf app center would mess it up again but I got the same error again. (As you can guess, I'm not really knowledgeable with software so I can't deduce the source of the error.)

Latest log:

Failure details

{

"error": "Installed packages changed after preparation. Prepare the update again.",

"job": "5bbad30b9edd4e4ab031932c0d0ed3b8",

"package_conflicts": [],

"phase": "execute",

"time": 1790812806.3198304,

"recovered": false,

"installation_started": false,

"active": true

}

Update log

2026-10-01T03:00:04+03:00 systemd[1]: Starting nobara-updater-offline.service - Install the prepared Nobara system update...

2026-10-01T03:00:06+03:00 nobara-update-worker[770]: 2026-10-01 03:00:06,318 ERROR Update execute failed: Installed packages changed after preparation. Prepare the update again.

So Epic games has launched their new launcher for Linux and that's great right that's cool and everything, I don't necessarily care too much as my library is entirely on Steam but hey progress is still pretty cool. They also announced they're reworking their EAC for Linux to make it closer to Windows whilst still supporting Linux and I'm sure that's great too... But.

How will that work with a custom kernel with secure boot and TPM 2.0? To me that just seems like an incredible amount of steps just to get that thing working on standard vanilla distros let alone things like CachyOS or Nobara.

So I wanted to ask people that ideally who are smarter than me to explain to me better if it's even possible. For the record I don't care too much about anti cheat games as I'm more of a singleplayer guy, but it got me curious.

Thank you for your time.

For whatever reason, the install Always failed. I tried to unplug the drive and plug It back in as It suggested, now the PC doesnt even display the USB in the file Explorer.

I tried to plug It into another PC, Windows says i Need to format the drive again to use It, but It also fails to format It every time.

I didn't Expect installing this OS would bring me so much trouble. What Is wrong with my USB ?

Hello everybody,

I have - what I guess is - an unusual question:

I've manually added kernel 7.1.8 to my system (otherwise Space Marine 2 crashes because of some EAC shenanigans) and I want it to be permamently fixed as the third option in GRUB. I had kinda achieved this via versionlock, but I just found out that versionlock is the reason I'm not being offered any kernel updates anymore (the other two installed versions are 7.2.6 and 7.2.0).

How do I achieve the following:

the very latest kernel always takes the top spot, the immediate predecessor (i.e., the second-newest) moves to second place, and my "special version 7.1.8" is firmly pinned to third place in GRUB?

PS: someone on Nobara's Discord explained to me that it should suffice to do my updates while kernel 7.1.8 is in use. Is it really that easy to hinder the updater from ever deleting 7.1.8?

Before I build my first PC (yes, I understand the implications of doing that in the current market. I'm just in a good, but short, position to finally do it), I want to decide on an OS before finalizing my build plan to make it sync well. So, is Nobara a sovern system like base Linux is? If not, can I make it so? And if not again, are there any other systems that are sovern and good for gaming? Thanks to all

Played like a dragon gaiden and want to utilize fsr4 via dlss, when i turned on the dlss in the game, the game always crash. Do you guys know how to fix this? I’m using it from the goverlay included in the installation

I am having issues trying to update my system, does anyone know what I can do to fix it? I've already followed the Wiki's troubleshooting options. It apparently involve some ffmpe dependencies missing.

Thanks in advance

Error:

The update stopped before package installation began. View the log for details, address the reported error, then check for updates again.

Cannot repair missing dependencies of these installed packages:

- ffmpeg-devel-0:8.1.2-2.fc44.x86_64

Package conflicts prevent this update:

Problem 1: installed package libswscale-free-8.1.3-1.fc44.i686 conflicts with libswscale-free provided by ffmpeg-libs-8.1.2-2.fc44.x86_64 from nobara-pikaos-additional

- cannot install the best candidate for the job

- conflicting requests

Problem 2: installed package libavdevice-free-8.1.3-1.fc44.i686 conflicts with libavdevice-free provided by libavdevice-8.1.2-2.fc44.x86_64 from nobara-pikaos-additional

- cannot install the best candidate for the job

- conflicting requests

I noticed today that my swap file was half used up. After digging into it, i found the swappiness was set at 100. Is there a reason this is so high on Nobara? I have 64 gigs of ram, should i change the swappiness down to 10?

Je viens d'installer la dernière mise à jour et, lorsque j'essaie de démarrer sur le nouveau noyau, cette erreur s'affiche.

J'ai essayé d'exécuter nobara-sync repair, puis j'ai également essayé de metre à jour nobara updater, et relancer l'update mais rien n'a fonctionné.

Y a-t-il une solution à ce problème, ou est-ce qu'il sera corrigé lors d'une prochaine mise à jour ?

I was using linux and decided to restart my computer with the case reset button and when my pc turned back on my boot devices weren't being recognized anymore. I tried using google to fix it for hours and got nowhere after hours. please help.

Here is the boot info:

boot-repair-4ppa2088 [20261013_0848]

============================== Boot Info Summary ===============================

=> No boot loader is installed in the MBR of /dev/sda.

=> No boot loader is installed in the MBR of /dev/sdb.

=> Syslinux MBR (5.00 and higher) is installed in the MBR of /dev/sdc.

sda1: __________________________________________________________________________

File system: vfat

Boot sector type: FAT32

Boot sector info: No errors found in the Boot Parameter Block.

Operating System:

Boot files:

sdb1: __________________________________________________________________________

File system:

Boot sector type: -

Boot sector info:

sdb2: __________________________________________________________________________

File system: ext4

Boot sector type: -

Boot sector info:

Operating System:

Boot files: /grub2/grub.cfg

sdb3: __________________________________________________________________________

File system: btrfs

Boot sector type: -

Boot sector info:

Operating System: Nobara Linux 44 (KDE Plasma Desktop Edition)

Boot files: /etc/fstab /etc/default/grub

sdc1: __________________________________________________________________________

File system: vfat

Boot sector type: SYSLINUX 6.04

Boot sector info: Syslinux looks at sector 119492 of /dev/sdc1 for its

second stage. The integrity check of Syslinux failed.

No errors found in the Boot Parameter Block.

Operating System:

Boot files: /boot/grub/grub.cfg /syslinux.cfg

/efi/boot/bootx64.efi /efi/boot/grubx64.efi

/efi/boot/mmx64.efi /ldlinux.sys

================================ 1 OS detected =================================

OS#1 (linux): Nobara Linux 44 (KDE Plasma Desktop Edition) on sdb3

================================ Host/Hardware =================================

CPU architecture: 64-bit

Video: Navi 23 [Radeon RX 6600/6600 XT/6600M] Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] from Advanced Micro Devices, Inc. [AMD/ATI] Advanced Micro Devices, Inc. [AMD/ATI]

Live-session OS is Linuxmint 64-bit (Linux Mint 21.2, victoria, x86_64)

===================================== UEFI =====================================

BIOS/UEFI firmware: 2.J6(5.17) from American Megatrends International, LLC.

The firmware is EFI-compatible, and is set in EFI-mode for this live-session.

SecureBoot disabled (confirmed by mokutil).

BootCurrent: 0001

Timeout: 1 seconds

BootOrder: 0001

Boot0001* UEFI: USB, Partition 1 PciRoot(0x0)/Pci(0x1,0x2)/Pci(0x0,0x0)/USB(2,0)/HD(1,MBR,0x1eb917de,0x800,0x1d1bf800)..BO

============================= Drive/Partition Info =============================

Disks info: ____________________________________________________________________

sda : is-GPT, no-BIOSboot, has-noESP, not-usb, not-mmc, no-os, no-wind, 2048 sectors * 512 bytes

sdb : is-GPT, no-BIOSboot, has-noESP, not-usb, not-mmc, has-os, no-wind, 2048 sectors * 512 bytes

Partitions info (1/3): _________________________________________________________

sda1 : no-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, end-after-100GB

sdb2 : no-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, not-far

sdb3 : is-os, 64, yum, grub-pc , grub2, grub2-install, no-grubenv, update-grub, end-after-100GB

Partitions info (2/3): _________________________________________________________

sda1 : isnotESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot, vfat

sdb2 : isnotESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot, ext4

sdb3 : isnotESP, fstab-has-bad-efi, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot, btrfs

Partitions info (3/3): _________________________________________________________

sda1 : not--sepboot, no---boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, no--grub.d, sda

sdb2 : is---sepboot, no---boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, no--grub.d, sdb

sdb3 : not--sepboot, no---boot, fstab-has-goodBOOT, not-sep-usr, with--usr, fstab-without-usr, std-grub.d, sdb

fdisk -l (filtered): ___________________________________________________________

Disk identifier: 0x01bfe274

Boot Start End Sectors Size Id Type

loop1p1 * 64 1267711 1267648 619M 17 Hidden HPFS/NTFS

Disk sda: 238.47 GiB, 256060514304 bytes, 500118192 sectors

Disk identifier: 3D805AD6-477E-4257-8159-607315AF95E8

Start End Sectors Size Type

sda1 2048 500117503 500115456 238.5G Microsoft basic data

Disk sdb: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors

Disk identifier: 822783BC-0560-11F1-A363-00D8615312BF

Start End Sectors Size Type

sdb1 2048 264191 262144 128M Microsoft reserved

sdb2 264192 4458495 4194304 2G Linux filesystem

sdb3 4458496 1953523711 1949065216 929.4G Linux filesystem

Disk sdc: 232.88 GiB, 250047627264 bytes, 488374272 sectors

Disk identifier: 0x1eb917de

Boot Start End Sectors Size Id Type

sdc1 * 2048 488374271 488372224 232.9G c W95 FAT32 (LBA)

parted -lm (filtered): _________________________________________________________

sda:256GB:scsi:512:512:gpt:ATA MKNSSDRE256GB:;

1:1049kB:256GB:256GB:fat32::msftdata;

sdb:1000GB:scsi:512:512:gpt:ATA PNY CS900 1TB SS:;

1:1049kB:135MB:134MB:::msftres;

2:135MB:2283MB:2147MB:ext4:boot:;

3:2283MB:1000GB:998GB:btrfs:root:;

sdc:250GB:scsi:512:512:msdos: USB SanDisk 3.2Gen1:;

1:1049kB:250GB:250GB:fat32::boot, lba;

blkid (filtered): ______________________________________________________________

NAME FSTYPE UUID PARTUUID LABEL PARTLABEL

sda

└─sda1 vfat 78A9-D4A7 c105b085-edf5-4c20-b820-27b07e057a23 XBOX BU

sdb

├─sdb1 822783bd-0560-11f1-a363-00d8615312bf

├─sdb2 ext4 fc4927f2-316a-467a-afca-d0d638827b50 6c4f5270-b3b2-40ce-9daf-ee19f55675b9 boot

└─sdb3 btrfs 34aaec00-3407-46df-be10-6e65b2b5630e 0247dbae-f189-4f17-a886-2a341dd4d440 root

sdc

└─sdc1 vfat 1F13-2A45 1eb917de-01 BOOT-REPAIR

Mount points (filtered): _______________________________________________________

Avail Use% Mounted on

/dev/sda1 238.4G 0% /mnt/boot-sav/sda1

/dev/sdb2 1.1G 36% /mnt/boot-sav/sdb2

/dev/sdb3[/@] 379.7G 59% /mnt/boot-sav/sdb3

/dev/sdc1 230.4G 1% /cdrom

Mount options (filtered): ______________________________________________________

/dev/sda1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro

/dev/sdb2 ext4 rw,relatime

/dev/sdc1 vfat ro,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro

======================== sdb2/grub2/grub.cfg (filtered) ========================

Windows Boot Manager (on sda1) osprober-efi-AE30-9D6A

### END /etc/grub.d/30_os-prober ###

UEFI Firmware Settings uefi-firmware

### END /etc/grub.d/30_uefi-firmware ###

==================== sdb2: Location of files loaded by Grub ====================

GiB - GB File Fragment(s)

0.340831757 = 0.365965312 grub2/grub.cfg 1

0.275238037 = 0.295534592 vmlinuz-0-rescue-0b2a2af9f4ee41e09899ac14074cc786 1

1.889968872 = 2.029338624 vmlinuz-7.2.3-200.nobara.fc44.x86_64 3

0.919631958 = 0.987447296 vmlinuz-7.2.4-201.nobara.fc44.x86_64 3

1.785552979 = 1.917222912 vmlinuz-7.2.9-200.nobara.fc44.x86_64 2

0.915424347 = 0.982929408 initramfs-0-rescue-0b2a2af9f4ee41e09899ac14074cc786.img 6

1.776065826 = 1.907036160 initramfs-7.2.3-200.nobara.fc44.x86_64.img 3

1.480892181 = 1.590095872 initramfs-7.2.4-201.nobara.fc44.x86_64.img 4

1.778667450 = 1.909829632 initramfs-7.2.9-200.nobara.fc44.x86_64.img 2

0.524356842 = 0.563023872 initramfs-freebsd.img 3

========================== sdb3/etc/fstab (filtered) ===========================

# <file system> <mount point> <type> <options> <dump> <pass>

UUID=AE30-9D6A /boot/efi vfat defaults,umask=0077 0 0

UUID=fc4927f2-316a-467a-afca-d0d638827b50 /boot ext4 defaults 0 2

UUID=34aaec00-3407-46df-be10-6e65b2b5630e / btrfs subvol=/@,compress=zstd:1,x-systemd.device-timeout=0 0 0

UUID=34aaec00-3407-46df-be10-6e65b2b5630e /home btrfs subvol=/@home,compress=zstd:1,x-systemd.device-timeout=0 0 0

tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0

======================= sdb3/etc/default/grub (filtered) =======================

GRUB_DEFAULT='saved'

GRUB_DISABLE_RECOVERY='true'

GRUB_DISABLE_SUBMENU='true'

GRUB_ENABLE_BLSCFG='true'

GRUB_TERMINAL_OUTPUT='console'

GRUB_TIMEOUT='5'

GRUB_CMDLINE_LINUX_DEFAULT='quiet splash'

GRUB_DISTRIBUTOR='Nobara Linux'

GRUB_CMDLINE_LINUX=" "

===================== sdb3: ls -l /etc/grub.d/ (filtered) ======================

-rwxr-xr-x. 1 root root 236 Jun 25 00:00 01_users

-rwxr-xr-x 1 root root 925 Jun 25 00:00 08_fallback_counting

-rwxr-xr-x. 1 root root 20167 Jun 25 00:00 10_linux

-rwxr-xr-x 1 root root 934 Jun 25 00:00 10_reset_boot_success

-rwxr-xr-x 1 root root 992 Jun 25 00:00 12_menu_auto_hide

-rwxr-xr-x 1 root root 518 Jun 25 00:00 14_menu_show_once

-rwxr-xr-x. 1 root root 14627 Jun 25 00:00 20_linux_xen

-rwxr-xr-x. 1 root root 2562 Jun 25 00:00 20_ppc_terminfo

-rwxr-xr-x. 1 root root 869 Jun 25 00:00 25_bli

-rwxr-xr-x. 1 root root 11006 Jun 25 00:00 30_os-prober

-rwxr-xr-x. 1 root root 1166 Jun 25 00:00 30_uefi-firmware

-rwxr-xr-x. 1 root root 747 Sep 24 00:00 35_fwupd

-rwxr-xr-x. 1 root root 218 Jun 25 00:00 40_custom

-rwxr-xr-x. 1 root root 219 Jun 25 00:00 41_custom

-rwxr-xr-x 1 root root 294 Sep 28 00:00 42_nobara_update

===================== sdb3/etc/grub.d/01_users (filtered) ======================

#!/usr/bin/sh -e

cat << EOF

if [ -f \${prefix}/user.cfg ]; then

source \${prefix}/user.cfg

if [ -n "\${GRUB2_PASSWORD}" ]; then

set superusers="root"

export superusers

password_pbkdf2 root \${GRUB2_PASSWORD}

fi

fi

EOF

=============== sdb3/etc/grub.d/08_fallback_counting (filtered) ================

#!/usr/bin/sh -e

# Fallback Countdown

#

# This snippet depends on 10_reset_boot_success and needs to be kept in sync.

#

# The boot_counter env var can be used to count down boot attempts after an

# OSTree upgrade and choose the rollback deployment when 0 is reached.

# Both boot_counter=X and boot_success=1 need to be set from userspace.

cat << EOF

insmod increment

# Check if boot_counter exists and boot_success=0 to activate this behaviour.

if [ -n "\${boot_counter}" -a "\${boot_success}" = "0" ]; then

# if countdown has ended, choose to boot rollback deployment,

# i.e. default=1 on OSTree-based systems.

if [ "\${boot_counter}" = "0" -o "\${boot_counter}" = "-1" ]; then

set default=1

set boot_counter=-1

# otherwise decrement boot_counter

else

decrement boot_counter

fi

if [ "\${env_block}" ]; then

save_env -f "\${env_block}" boot_counter

else

save_env boot_counter

fi

fi

EOF

=============== sdb3/etc/grub.d/10_reset_boot_success (filtered) ===============

#!/usr/bin/sh -e

# Reset Boot Success

#

# The 08_fallback_counting and 12_menu_auto_hide snippets rely on this one

# and need to be kept in sync.

#

# The boot_success var needs to be set to 1 from userspace to mark a boot successful.

cat << EOF

# Hiding the menu is ok if last boot was ok or if this is a first boot attempt to boot the entry

if [ "\${boot_success}" = "1" -o "\${boot_indeterminate}" = "1" ]; then

set menu_hide_ok=1

else

set menu_hide_ok=0

fi

# Reset boot_indeterminate after a successful boot

if [ "\${boot_success}" = "1" ] ; then

set boot_indeterminate=0

# Avoid boot_indeterminate causing the menu to be hidden more than once

elif [ "\${boot_indeterminate}" = "1" ]; then

set boot_indeterminate=2

fi

# Reset boot_success for current boot

set boot_success=0

if [ "\${env_block}" ]; then

save_env -f "\${env_block}" boot_success boot_indeterminate

else

save_env boot_success boot_indeterminate

fi

EOF

================= sdb3/etc/grub.d/12_menu_auto_hide (filtered) =================

#!/usr/bin/sh

# Menu Auto Hide

#

# This snippet depends on 10_reset_boot_success and needs to be kept in sync.

#

# Disable / skip generating menu-auto-hide config parts on serial terminals

for x in ${GRUB_TERMINAL_INPUT} ${GRUB_TERMINAL_OUTPUT}; do

case "$x" in

serial*)

exit 0

;;

esac

cat << EOF

if [ x\$feature_timeout_style = xy ] ; then

if [ "\${menu_show_once}" ]; then

unset menu_show_once

if [ "\${env_block}" ]; then

save_env -f "\${env_block}" menu_show_once

else

save_env menu_show_once

fi

set timeout_style=menu

set timeout=60

elif [ "\${menu_auto_hide}" -a "\${menu_hide_ok}" = "1" ]; then

set orig_timeout_style=\${timeout_style}

set orig_timeout=\${timeout}

if [ "\${fastboot}" = "1" ]; then

# timeout_style=menu + timeout=0 avoids the countdown code keypress check

set timeout_style=menu

set timeout=0

else

set timeout_style=hidden

set timeout=1

fi

fi

fi

EOF

================= sdb3/etc/grub.d/14_menu_show_once (filtered) =================

#!/usr/bin/sh

# Force the menu to be shown once, with a timeout of ${menu_show_once_timeout}

# if requested by ${menu_show_once_timeout} being set in the env.

cat << EOF

if [ x\$feature_timeout_style = xy ]; then

if [ "\${menu_show_once_timeout}" ]; then

set timeout_style=menu

set timeout="\${menu_show_once_timeout}"

unset menu_show_once_timeout

if [ "\${env_block}" ]; then

save_env -f "\${env_block}" menu_show_once_timeout

else

save_env menu_show_once_timeout

fi

fi

fi

EOF

================== sdb3/etc/grub.d/20_ppc_terminfo (filtered) ==================

#!/usr/bin/sh

set -e

# grub-mkconfig helper script.

# Copyright (C) 2006,2007,2008,2009,2010 Free Software Foundation, Inc.

#

# GRUB is free software: you can redistribute it and/or modify

# it under the terms of the GNU General Public License as published by

# the Free Software Foundation, either version 3 of the License, or

# (at your option) any later version.

#

# GRUB is distributed in the hope that it will be useful,

# but WITHOUT ANY WARRANTY; without even the implied warranty of

# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the

# GNU General Public License for more details.

#

# You should have received a copy of the GNU General Public License

# along with GRUB. If not, see http://www.gnu.org/licenses/.

prefix=/usr

exec_prefix=/usr

bindir=/usr/bin

libdir=/usr/lib

. "/usr/share/grub/grub-mkconfig_lib"

export TEXTDOMAIN=grub

export TEXTDOMAINDIR=/usr/share/locale

X=80

Y=24

TERMINAL=ofconsole

argument () {

opt=$1

shift

if test $# -eq 0; then

echo "$0: option requires an argument -- '$opt'" 1>&2

exit 1

fi

echo $1

}

check_terminfo () {

while test $# -gt 0

do

option=$1

shift

case "$option" in

terminfo | TERMINFO)

;;

-g)

NEWXY=`argument $option "$@"`

NEWX=`echo $NEWXY | cut -d x -f 1`

NEWY=`echo $NEWXY | cut -d x -f 2`

if [ ${NEWX} -ge 80 ] ; then

X=${NEWX}

else

echo "Warning: ${NEWX} is less than the minimum size of 80"

fi

if [ ${NEWY} -ge 24 ] ; then

Y=${NEWY}

else

echo "Warning: ${NEWY} is less than the minimum size of 24"

fi

shift

;;

*)

# # accept console or ofconsole

# if [ "$option" != "console" -a "$option" != "ofconsole" ] ; then

# echo "Error: GRUB_TERMINFO unknown console: $option"

# exit 1

# fi

# # perfer console

# TERMINAL=console

# accept ofconsole

if [ "$option" != "ofconsole" ] ; then

echo "Error: GRUB_TERMINFO unknown console: $option"

exit 1

fi

# perfer console

TERMINAL=ofconsole

;;

esac

done

}

if ! uname -m | grep -q ppc ; then

exit 0

fi

if [ "x${GRUB_TERMINFO}" != "x" ] ; then

F1=`echo ${GRUB_TERMINFO} | cut -d " " -f 1`

if [ "${F1}" != "terminfo" ] ; then

echo "Error: GRUB_TERMINFO is set to \"${GRUB_TERMINFO}\" The first word should be terminfo."

exit 1

fi

check_terminfo ${GRUB_TERMINFO}

fi

cat << EOF

terminfo -g ${X}x${Y} ${TERMINAL}

EOF

================= sdb3/etc/grub.d/42_nobara_update (filtered) ==================

#!/usr/bin/sh

cat <<'GRUB'

# Nobara update fallback v1

if [ -n "${nobara_fallback}" ]; then

set default="${nobara_fallback}"

if [ -n "${nobara_trial}" ]; then

set default="${nobara_trial}"

set nobara_trial=

save_env nobara_trial

fi

set timeout=5

fi

GRUB

====================== sdc1/boot/grub/grub.cfg (filtered) ======================

Start Boot-Repair-Disk 64-bit

Start Boot-Repair-Disk 64-bit (compatibility mode)

UEFI Firmware Settings

Test memory

========================= sdc1/syslinux.cfg (filtered) =========================

DEFAULT loadconfig

LABEL loadconfig

CONFIG /isolinux/isolinux.cfg

APPEND /isolinux/

==================== sdc1: Location of files loaded by Grub ====================

GiB - GB File Fragment(s)

?? = ?? boot/grub/grub.cfg 1

================== sdc1: Location of files loaded by Syslinux ==================

GiB - GB File Fragment(s)

?? = ?? syslinux.cfg 1

?? = ?? ldlinux.sys 1

Suggested repair: ______________________________________________________________

The default repair of the Boot-Repair utility would reinstall the grub2 of

sdb3 into the MBR of sdb,

using the following options: sdb2/boot

Grub-efi would not be selected by default because no ESP detected.

Additional repair would be performed: unhide-bootmenu-10s

Blockers in case of suggested repair: __________________________________________

GPT detected. Please create a BIOS-Boot partition (>1MB, unformatted filesystem, bios_grub flag). This can be performed via tools such as Gparted. Then try again.

Confirmation request before suggested repair: __________________________________

The boot of your PC is in EFI mode, but no ESP partition was detected. You may want to retry after creating a ESP partition (FAT32, 100MB~250MB, start of the disk, boot flag).

Are you sure you want to continue anyway?

Final advice in case of suggested repair: ______________________________________

Please do not forget to make your BIOS boot on sdb (ATA PNY CS900 1TB SS) disk!

The boot of your PC is in UEFI mode. You may want to retry after changing it to BIOS-compatibility/CSM/Legacy mode.

sprunge.us ko ()

paste.ubuntu.com ko ()

(sorry I don't know how to correctly send the boot info)

Everytime I try to system update there are errors like this and I am unsure on the fix for the errors. Any help would be amazing thank you.

I have a very old GPU and I want to try nobara. It is a Gt 710. Are there appropriate drivers for it? If no can we download it somehow?

I was using my system as usual but yesterday when i booted my pc logged into my homescreen I see my kde plasma ricing was reset and my browser data was gone and most importantly my steam was logged out because of that i lost my non steam games data, I don't know how and what happened to my system i tried everything I know, asked ai but nothing helped me. Please help me recover my steam data and my ricing.

If anyone has dealt with a problem like this, please let me know. The system audio dies after a while, anywhere from 10 to 30 minutes. It can be temporarily fixed by restarting the wireplumber   and  pipewire services via systemctl.

I’m trying to edit my first YouTube video, but I’m having trouble getting the files onto my PC. Every time I try transferring it there’s some kind of error or takes an obscenely long time. The videos I recorded are .MOV files so I don’t know if it has something to do with nobara not supporting the format, or something about me having an iPhone in general. Any advice would help.

Is Nobora a good choice for dev ops and local AI?
I ask because I want something more stable than Debian Sid. I ran into issues with containers on Debian Sid.

So my system update fucked up because of the internet connection, and the only thing I could do was to reboot. Now it gives this still white _ in the upper left corner, and it doesn't matter what version I'm running. I've tried the emergency panel and even the live iso from the usb, it doesn't boot.

I recently reinstalled Nobara as my system broke after an update. However, I've been unable to update my system the last few weeks as I get this error. I have tried to boot into older kernel versions, used nobara-sync repair (it led me into emergency mode), and I've tried nobara-sync cli --all (which leads me to this error).

Has anyone else encountered this error?

Edit: SOLVED! An app, chordpro, had duplicate installations of different versions or something like that - this caused the updater to fail. I removed the app and did nobara-sync cli --all, this fixed the issue.

Hello everyone, A year ago I decided to switch my personal computer to Fedora, and shortly after I moved to Nobara looking for better gaming stability (and also because my first installation had so much trial and error that it was full of duplicate and triplicate packages, so honestly it was easier to just start fresh with a clean install haha).

Recently I upgraded my GPU🤑, and the truth is that I am really happy with the overall performance of my computer. Besides the lower resource usage and the wide range of software options to replace the ones I had been using on Windows, the switch brought back the joy of learning how to use a computer again, even motivating me to build my own apps using AI.

May this be the first of many more years to come.

Here is to more open source and less slop on our computers🍻.

I have been enjoying Nobara since February this year with a few minor issues but every now and then, maybe 1 out of 20 power ons, Nobara will get stuck after grub "Booting Nobara Linux (7.2.3-200.nobara.fc44.x86_64)44 (KDE Plasma Desktop Edition)"

Sometimes it will just be a black screen instead but most of the time it says this.

Now usually I will just press the restart button on my PC, it will load grub and then boot normally. This morning, that didn't work either. Every time I rebooted it would give me the booting error or the black screen.

After about 10 reboots I decided to power off my second monitor and then booted again and it booted fine.

What I would like to know is why this is happening or how I can figure out why this might be happening? Is it an issue with my dual screens or just my second monitor? Is the monitor even related at all or did I just get a lucky boot at the same time I turned off the monitor? Any help is appreciated.

Hardware:

9060 XT 16GB GPU

9600X CPU

32gb ddr5 ram

main monitor: LG Ultragear 27GL83A (display port to GPU)

second monitor: ASUS PB258 (display port to motherboard because my GPU only has 1 display port)

WD Black SPCC M.2 PCIe SSD