So, after EndeavourOS’s GRUB comitted suicide, me being too stupid to understand chroot despite wiki “tutorials” and the community rather trolling & gaslighting me instead of helping I decided to give Nobara a go. Usually I am a Plasma KDE guy, but thought since it’s been a long time I try it out, especially since you can have it in a more classic configuration those days again, even though I’d miss out of Wallpaper Engine.
Unfortunately my experience has been nothing but awful. A bunch of random bullet points of my experience:
- I had real trouble connecting my BT headphones. At first it was “connected”, but not really. Tried a fresh pairing mode, but then it showed two headphones. Then it connected, but as soon as I tried to adjust the audio input / output settings it lost audio again and I had to repeat it yet again. Now it works, and I decided to never touch the audio settings ever again.
- “Files” is constantly crashing. Using the search? Crash. Going backwards? Crash. Try to do “something”? Crash. Do nothing? Probably also crash (hyperbolic).
- “Files” data transfer for copying & deleting files is slow as hell for whatever reason (on decent Samsung SSDs mind you).
- “Files” cannot multitask. If you’re copying, scanning, deleting or whatever, it won’t do anything else until that process is done.
- “Files” and other Gnome applications frequently bug out if you try too many things at once, freezing or crashing them.
- “Files”, or even Gnome as a whole, is so incredibly scrapped for features to achieve its simplistic look, that it lacks actual functionality.
- Gnome’s settings are also missing for everything, or hidden in a gazillion different config menus, some of which I already forgot how to access again.
- Scaling scales not just the UI, but also 3D applications like games, reducing their actual resolution and making them blurry. The UI seemed to be blurry as well.
- Mullvad VPN’s tray icon somehow turned into some three dots with a weird background.
- In the tray menu there’s also a VPN toggle, which shows Mullvad, but being turned off. Turning it on disables my connection and I have to reconnect through Mullvad, which turns the toggle off again. No way to remove the redundant toggle as far as I can tell, but maybe it’s in some hidden settings menu that I have yet to find.
- OpenRGB in this does not work with my NZXT Hue 2 Ambient. Keeps asking for resize zones, which according to a search should not be necessary, and wasn’t necessary with the one I used in EOS either. Selecting any color just turns the LEDs off.
- Launching the Battle.net launcher through Lutris it also opens some ghost “OpenGL Renderer” application with it, taking up space on the task bar.
- Battle.net launcher can’t be maximized without constantly resetting or displaying information beneath the task bar.
- Can’t launch .sh files unless I explicitly right click & Run as program.
- Unfortunately it then launches with an additional empty terminal window, yet again taking up space on the task bar.
- Had to create a new FF profile because using my old one somehow was unusable in regards to its performance.
- The weather location for the little clock thingy apparently can’t find anything, city or country, except some locations that aren’t near me.
- Can’t remove my own review in the Software center for one of the apps that I did prematurely.
- Tray area also has this little tiling menu. I tried tiling, hated it. Couldn’t find a way to remove that icon to save space on the task bar.
- After a lot of apps started to hang I tried restarting, just to be left in a blackscreen and the PC not shutting down. Had to hard reset to restart.
- No EurKey keyboard layout. There’s a ‘German (US)’ one that’s close but it’s missing symbols.
- Maybe probably more things that I can’t recall right now.
And that’s just after a few hours of usage. I was making fun of the tiny issues in KDE before, but if I have to choose between that and this disaster then I’m probably going to switch to the KDE edition, if I cannot find solutions to all this. I really don’t understand how people can deal with it? Or am I somehow the only one?
I think it would help if you showed us the output of
inxi -bin a terminal.In what way exactly? My issues aren’t caused by my system being a 20 year old potato, if that’s what you’re thinking.
System:
Host: ***** Kernel: 6.3.10-203.fsync.fc38.x86_64 arch: x86_64 bits: 64
Desktop: GNOME v: 44.2 Distro: Nobara release 38 (Thirty Eight)
Machine:
Type: Desktop Mobo: Micro-Star model: Z490-A PRO (MS-7C75) v: 1.0
serial: <superuser required> UEFI: American Megatrends v: 2.80
date: 01/30/2021
CPU:
Info: 6-core Intel Core i5-10400F [MT MCP] speed (MHz): avg: 4000
min/max: 800/4300
Graphics:
Device-1: AMD Navi 23 [Radeon RX 6650 XT / 6700S 6800S] driver: amdgpu
v: kernel
Display: wayland server: X.Org v: 23.1.2 with: Xwayland v: 23.1.2
compositor: gnome-shell driver: dri: radeonsi gpu: amdgpu
resolution: 1920x1080~144Hz
API: OpenGL v: 4.6 Mesa 23.1.3 renderer: AMD Radeon RX 6650 XT (navi23
LLVM 15.0.7 DRM 3.52 6.3.10-203.fsync.fc38.x86_64)
Network:
Device-1: Realtek RTL8125 2.5GbE driver: r8169
Drives:
Local Storage: total: 9.1 TiB used: 1.65 TiB (18.1%)
Info:
Processes: 483 Uptime: 6h 44m Memory: available: 31.25 GiB
used: 14.95 GiB (47.8%) Shell: Bash inxi: 3.3.27When people complain about crashes, that is usually the first thing that springs to mind. Of course, your hardware is fairly new, so I think you should be good in that respect. The problem might just be a Xwayland/Gnome thing, now that I think about it.
Nobara being an independent side project based on Fedora and not a full-blown distro on its own - YMMV on all kinds of issues.
That said I’m running Nobara KDE on my desktop and everything has been working great. You should give it a try just to see how many of your issues are specific to Nobara gnome.
I don’t really understand why you find chrooting hard or what’s wrong with the tutorials you found. Can you point out which step of it is difficult. this is the first tutorial I get for Manjaro, is there something missing or left ambiguous?
I use btrfs + encryption. The tutorials just state “you have to do this and that”, but not exactly what any of that means or how I apply it to my system, since the commands obviously need tinkering to make sense for my specific use case. It’s not really a step by step, but a step by step jump to step X for this and then to step Y for that but make sure to do “something you don’t understand / know” to be sure that “something you also don’t know”. It’s basically all just a cryptic mess if you don’t know any of it beforehand and I don’t think the authors have tested their tutorials on people without prior background knowledge.
What is your goal?
There are 3 main distributions
- Arch which aims to take the latest cut of everything. If you have time to keep your desktop updated and need that extra 1fps in a game, its a great choice.
- Debian aims for stability, this means your drivers and text editor might be … 2 years old! But if it works on install it will stay working
- Red Hat Enterprise Linux aims for stability but will try to backport drivers. I honestly believe its packaged to always pull in gtk. It aims to provide tools to encourage people into support contracts.
Almost everything else is downstream of those with a twist. For example
- Ubuntu is downstream Debian with 6 month release schedule, non-free enabled by default and other deviations to encourage people into support contracts.
- Mint is downstream Ubuntu with the deviations removed.
Stuff that isn’t downstream tends to have a highly specific purpose. Fedora started life as upstream RHEL, now it seems to be Red Hat’s research plaything (e.g. immutable sounds cool, lets try it in Fedora).
My advice is go to one of the big 3, try them and only bother with one of the million down stream distributions if there is a Unique Selling Point for something you actually care about.
My goal is to have a functional desktop with good gaming capabilities.
EOS / Arch was that until it nuked itself, something that not even Manjaro managed to do, which, for all its bad reputation, had much less issues in a much longer time frame of use. It’s not really about having “that extra 1 FPS in a game”, but to ensure actual game compatibility, including for titles that aren’t 2 years old.Try opensuse tumbleweed. It is a bit like arch(rolling release and such) but has more testing and less breakage. It has pretty good KDE support, a very good configuration tool and is one of the most secure distros in its base installation. Also good for gaming imho.
@FaeDrifter
Tried to install it on my old laptop for testing and the installer just gives me this warning before installing:“Boot from mbr does not work together with btrfs filesystem ang gpt disk label without bios_grub partition. To fix this issue, - create a bios_grub partition, or - use any Ext filesystem for boot partition, or - do not install stage 1 to MBR.”
I really have no idea what it wants. I used the guided partitioning so I would expect it to handle that for me? Also, why do they not have a working live environment to test it before installation? Honestly not a great start.
Edit: Oof. So I just tried to install it on my desktop, first one failed tremendously and didn’t boot. Tried again and wiping the partitions proper instead of “on demand” of the garbage installer. Got a system, try to switch down to 1080p and it gives me this super stretched pancake resolution instead. Hell no.
You booted in bios legacy mode and tried to install to a gpt formatted disk without a dedicated /boot partition would be my guess.
It’s messed up, probably a bios setting related to uefi. Aeon is still in beta and doesn’t handle edge cases that well.
As for your second issue sounds like a waylaid issue with switching resolutions, usually simply relogging fixes that.
You make it sound as if these are distribution issues, these are either weird bios settings or post install issues with a very recent compositor version. Do you think opensuse ships its own drivers or window managers?
I booted in bios legacy mode?
What “weird bios options” could an old 2009 laptop bios possibly have, that are used by default on top of that and never caused any sort of issues with any other Linux distro before? The only ones that didn’t run on that thing were both Nobara variants, which is likely more of an old gpu issue.I’ve had many wayland issues on other distros before, but never this specific one. It’s usually the same on every one, like blurry scaling, scaling affecting games, fsync causing frequent few seconds long blackscreens, or just a lot of game specific stuff. The issue here did not fix itself even after a reboot. I really don’t care where the issue stems from, I can only say that this was very unique to OpenSUSE.
Well the fact that you don’t understand the issue is part of it. See there are several ways disks can be partitioned and several ways a bios can go about finding kernels to boot on said disks, all of this applies to windows as well btw.
- Bios legacy + MBR partitioned with a bootloader written into the first 512 bytes of a disk and the bios being directed to that disk. This is the old way of doing it.
- UEFI + GPT partition scheme. Here you have one or more partition marked as bios+uefi, formatted in fat32, that the bios will comb for boot entries. It’s the modern way of doing this.
What you have is probably a mix of the two. It’s likely that one of your linux installs partitioned your disk as GPT while your your system still boots in bios legacy. The installer is now getting mixed signals, one one hand the bios is detected as legacy mode, on the other it’s looking at a GPT partition table. Now technically you probably could write the bootloader just like in option 1., but if you ever change your bios to uefi mode, which is required for modern operating systems like windows you would end up with an non bootable system. And not just in a “oopsie, I need to boot a rescue disk and fix this”-kind of way but a “we need to nuke the entire partition table and start over”-kind of way.
So what the Suse installer is telling you is that you really should use a /boot partition if installing on a GPT partition table.
Btw if you check the correct option at install time(the one about using the entire harddrive) it should automatically create a MBR partitioned disk for you which avoids this issue as it’s not a ungodly mix of 1. and 2.
This error isn’t a bug, it’s a feature pointing out a serious problem with your machines setup(the one below the OS level). Yes you can probably ignore it, as other distros might or might not, but it’s generally not a good idea. SuSE has a couple of these hang ups since it has an enterprise background and takes some things more serious than other distros. For example having closed ports for printers in the active on default firewall being one stellar example of this. It cause no end of issues for people struggling to setup their printers, that being said it is a security issue and opensuse decided it wasn’t going to sacrifice security of every system because some people want to use a printer.
So what the Suse installer is telling you is that you really should use a /boot partition if installing on a GPT partition table.
Why is it telling ME that when I trusted the partitioning to the installer? I really don’t understand how that should be my fault for the partitioner to act faulty. And btw. there’s only two options: 1) to erase the disk if needed and 2) erase the entire disk anyway. I selected the second one because the first one didn’t even work at all, so from my perspective it should have not used any potential GPT partitions that the previous distro could’ve potentially created, but erased the entire thing and start from scratch with everything it would need, including a valid boot partition. If OpenSUSE, for some reason, requires me to wipe my drive clean BEFORE I even start the installer, then they should specify that beforehand - or provide a less antique installer that can actually do it itself.
