Figured I’d do the pre-setup before I went to bed, so I’ve run the grep command and put the board_name from that output such that the patch now reads thus:
Nice. Also it occurred to me that there might be a way to set that quirk through the kernel command line instead of having to compile a patched kernel. I haven’t had a chance to look it up though.
Edit: I couldn’t find anything obvious. This behaviour is buried pretty deep.
I’d like to try to get it upstream, and that seems like the sanest way to do it.
You might need to be on linux 6.5+ for this patch to apply, and if you could verify that it’s still broken on 6.6 without the patch, that would be nice.
I’ve been using Wayland sessions as default since plasma 5.22 came around, and with other window managers before that too. Everything that has ever been broken for me, was broken because of X11 or XWayland. I’d rather take a considerably better experience with an occasional issue, that an experience that is held together by candy wrappers and hot glue, and is widely considered obsolete
Im in the same boat. Been using wayland since around that version or a little later and it has only been uphill (except for right now since i am on the development build and Qt broke itself causing the system config menu to fail to load 80% of KCMs, but this is my fault for switching to alpha software lol)
Are you talking about wlr-randr? Because its –transform argument only accepts normal|90|180|270|flipped|flipped-90|flipped-180|flipped-270, not any transformation matrix. Maybe its just a limitation of the command line tool and it could be modified, I don’t know, I haven’t been too deep in the code or the protocol specifications. It also looks like it only works with wlroots based compositor.
My experience with Nvidia+ Wayland was… Less than desirable. Enough to make me pickup an AMD card.
However, once I did that my experience instantly better. Hell, even X11 worked better - I was never able to get the desktop to stay at a consistent 60FPS (I’m still on a 60Hz panel which I’m just now getting around to upgrading shortly) in X until I moved to my AMD card.
The 545 driver update just made things so much worse. So I’d say Wayland+Nvidia is not great (for others it works fine so maybe it’s down to what card you have?) however on my AMD card (and my old MacBook with Intel integrated graphics) it’s fantastic.
I stopped using Gentoo because compiling everything was a major waste of time, but I have missed world files since then. This is a great reason to reconsider Gentoo for my next machine.
Can the file be split into different files like in Gentoo? I used to have different files for basic stuff, gaming, hardware specific, etc, so I could keep the parts of the Configs I wanted from one machine to another.
If so I’ll definitely check it out, been meaning to try Alpine since for what I understand it’s not GNU, right? Which should put a final nail in the GNU+Linux copy pasta hahahah.
I don’t think apk would check multiple files for the world. But you could maintain them outside the apk mechanisms, just concatenating them into a single file, with tup/make/sh/whatever.
Makes sense, I actually have a tool for that sort of thing that I wrote for i3 configs (it’s called CFC and it’s here in case you want to use it gitlab.com/Nibodhika/cfc )
Alpine Linux is the most sane distro I tried. The absence of glibc brought limitations unfortunately, but it is the fault of developers that uses that shit instead of pure libc.
(Perhaps) unrelated background informationxD , I started writing a reply yesterday and it got unwieldy real quick. So, I got discouraged and not long after I fell asleep. In the morning, I was surprised to see that a lot of your questions still weren’t answered, so I mustered some motivation and here it is. Don’t expect a very thorough response, but you should find enough pointers to make this work.
Preface:
Last summer I tried dualbooting Windows 10 and Fedora Silverblue and succeeded. So I will be sharing my experiences based on that. I don’t know if doing this with Windows 11 will be different and/or more challenging (or not).
It’s also got an Nvidia GTX 4060 in it, which will probably not be optimal from what I hear (so any tips on that are much appreciated as well!).
Yup, the gist of it would be that Nvidia’s proprietary drivers are not found in the native repos of most distros. This also applies to Fedora. However, you should be able to acquire the proprietary drivers by following the instructions found on RPM Fusion. But, Nvidia’s proprietary drivers are known to not play nice and might require you to get into the nitty gritty later down the line to save your system. Don’t get me wrong; some people never have issues, but unfortunately this doesn’t apply to everybody. Therefore, it’s very good to approach this cautiously. If, instead, you’d prefer a managed solution; so one in which your input is left to a bare minimum but somehow Nvidia’s proprietary drivers are installed and (at times) fixed by some black magic shenanigans (or just good engineering) going on in the background, then look no further than uBlue’s Nvidia images. Delving further into what uBlue is and why IMO you should consume Fedora Silverblue through it would be out of scope for this comment.
How would I go about actually shrinking Windows 11 down to make space for Fedora? Is “partitioning” the right word to use here?
So, unfortunately I don’t quite remember what I did exactly. But I can’t imagine I would do anything beyond the following two scenarios:
I just did what I always do and used GParted to shrink the size of the Windows 10 installation.
I used Windows’ own tool to do the shrinking (assuming they even offer something to that effect).
After I shrink the partition, is it then just a matter of running the installer and using automatic partitioning with the unused space left over after shrinking Windows?
If memory serves me right, automatic partitioning by Fedora’s Anaconda installer was for some reason undesirable. I don’t remember the specifics, but it’s likely either one of the following:
It straight up took hold of the entire disk and thus wanted to remove Windows.
Issues related to the bootloader; either it just forgot about it or tried to coexist with Windows’ bootloader or tried to hijack Windows’ bootloader. Nonetheless, all of these might result into some issues later down the line. Therefore, ideally, it should have its own separate bootloader (or at least one it shares with other non-Fedora(-based) distros).
Therefore, I did something slightly different. If I recall correctly, one should adhere to the following instructions:
After you’ve shrunk the Windows partition, make a new partition (preferably using GParted) with the following specifics:
512MB (in size)
Set as file system "fat32"
Give the partition the “boot” and “esp” flags
Reboot into Fedora Silverblue/Kinoite’s installer and when you get to the screen found below:
First select the disk you’d like to perform the installation on and then select Custom (optional: you’re free to choose the “Encrypt my data” option as well). After you’ve done this, press “Done” in the upper-left corner.
A new screen should appear, in here I selected “Click here to create them automatically.”. This should apply the default partitioning on the empty disk space. However there are a couple of things to keep track off:
Ensure that nothing from your Windows partitions is touched.
This includes the EFI partition of your Windows; if Fedora wants to do anything with it, then ensure it remains untouched.
By default, at least in my case, a new EFI partition specifically for Fedora Silverblue wasn’t made. This is where the earlier created partition using GParted will play an important role;
Select the earlier created 512MB partition
Mount Point: change it from blank/empty to /boot/efi
File System: Set it to EFI System Partition
Ensure the checkbox with “Reformat” that’s found to the right of the selection box for “File System:” is enabled/blue/checked
I don’t recall what I did exactly with the selection box under “Device Type:”, but it likely was Standard Partition. I didn’t encrypt it.
(Optional) You should have noticed that this screen also enables one to create partitions. There’s a chance I created mine using this instead of GParted, but that would mean I would have departed from my ways. If the method in which the partition is created with GParted didn’t work and you don’t know why, then it’s at least worth trying to create the partition here instead.
After you’re done with the previous screen, select “Done” in the upper-left corner. This should prompt a popup screen that summarizes the changes. Ensure that this doesn’t do something strange to your Windows partitions and make sure that it looks otherwise as you’d expect. If you’re done, then select “Accept Changes”.
The rest of the installation should progress like how you’d expect from there.
(Post-install) Depending on how you’d like to have GRUB (read: default bootloader on Fedora) configured, you might have to do a thing or two to ensure you can access both Fedora Silverblue/Kinoite and Windows however suits you best.
I’d also love to know what kind of issues the docs are actually warning about as far as dual-booting. Will Windows wipe the bootloader on update or will Silverblue / Kinoite wipe Windows out somehow? If it’s Silverblue wiping Windows out, that may cause me to go with a different distro - but if Windows wipes Silverblue, it’ll be annoying but not a deal breaker
As long as the EFI partitions are separated, there’s nothing to worry about. And if anything, it’s Windows that might wipe out whatever Linux distro you’re dualbooting.
I plan to use Silverblue / Kinoite for development exclusively, so everything will be on GitHub.
Grab a USB with enough capacity (8 GB at the bare minimum), and use Ventoy to create a bootable USB drive out of it. Then, put the .iso files for both GParted and Fedora Silverblue (or uBlue) into the designated location (read: partition called “Ventoy”).
Regarding Ventoy, ensure to set it up specifically for your needs (GPT vs MBR, SecureBoot or not etc).
linux
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.