mub

I'm using EndeavourOS (Arch btw) with KDE plasma 6.x (Wayland), SDDM, and systemd as boot manager. I have 2 displays, one HDMI-A-1 (1080p) and one on DP-1 (Ultrawide).

When I boot the password entry cursor defaults to the HDMI display, but I want it to default to the DP-1 display.

I've tried a few things, mostly suggestions from ChatGPT. But nothing has worked. The weird thing is at boot the boot menu and boot messages all appear on DP-1, and it is set as primary in KDE and that works fine as well. It is just the logon prompt that defaults to the wrong display.

Things I've tried so far.

• Adding video=DP-1:e to the options in the systemd entry - (No effect)
• Edited /etc/sddm.conf.d/wayland.conf to run a script that did the following: kwriteconfig6 --file startkderc --group General --key PrimaryScreen DP-1 (didn't fix it, actually broke the logon process so had to remove it)

I'm just not familiar enough with how SDDM works so hoping for some good pointers to provide the answer or point me in the right direction.

I'm running EndeavourOS and Windows 11. Each OS is on a separate disk, but I have a data disk that is currently NTFS that mount in both OSes. NTFS causes problems for some things in Linux, and I'm worried it'll bork the drive for windows eventually, so I'm keen to find an alternative. I've read about the WinBTRFS driver so wondering if that is a better way to go?

I don't want to run a server with a share to access this data because it is way to slow for my needs.

I have 2 screens attached to my EndeavourOS (KDE Wayland) PC. The secondary is HDMI the primary is Display Port. The boot menu and boot messages all appear on the primary display, but once the login appears the password entry defaults to the secondary. How do I force it to default to the primary?

I recently moved to Arch (EndeavourOS) from Mint. Arch doesn't have cron installed as it uses systemd timers instead, and while I could have just installed cron that felt like a lazy answer.

Systemd timers are easy enough to use and I got it working straight away, but I bumped into a comment in the Arch wiki about using a template for the timer so it can be re-used. I'm a bit slow, so I spent a hours trying to work this out, but I couldn't find a good example. Anyway, I now have it working so I thought it would be useful for someone in the future for easy reference .

This is how you create a timer template that can be reused to run a oneshot service under a specific user. In this example it will run on the hour every hour.

Create the timer file.

sudo nano /etc/systemd/system/[email protected]

Paste the following into that file, save and close.

[Unit]
Description=Run %i every hour

[Timer]
OnCalendar=*-*-* *:00:00
Persistent=true
Unit=%i.service

[Install]
WantedBy=timers.target

Create the service file for the script or command you want to run. (using "myscript" in this example)

sudo nano /etc/systemd/system/myscript.service

Paste the following into that file, save and close.

[Unit]
Description=My Script

[Service]
User=username
group=username
Type=oneshot
ExecStart=/usr/local/bin/command -parameters

Now enable and start the timer

sudo systemctl enable [email protected]
sudo systemctl start [email protected]

Not everything actually requires a GUI, obviously. But anything that requires configuration, especially for controlling a hardware device, should have a fully functional GUI. I know Linux is all about being in control, and users should not be afraid to use the command line, but if you have to learn another bespoke command syntax and the location and structure of the related configuration files just to get something basic to work then the developer has frankly half arsed it. Developers need to provide GUI's so that their software can be used by as many people as possible. GUI's use a common language that everyone understands (is something on or off, what numeric values are allowed, what do the options mean).

Every 12 to 18 months I make an effort to switch to Linux. Right now I'm using Archlinux, and it has been a successful trip so far, except my audio is screwed, I can't use my capture card at all, I had issues with my dual displays at the start, and the is no easy way to configure my AMD graphics card for over clocking or well anything basic at all.

I'm not looking for a windows clone, I love that I can choose different desktop environments and theme many of them to death. I even like the fact there are so many distros. Choice is a big part of linux, but there is clearly a desire to get more people moving away from Windows and until that path is 95% seamless most people just won't. Right now I think Linux is 75% to 85% seamless depending on the use case and distro but adding more GUI front ends would, imho, push that well into the 90% zone.

GUI is not a dirty word, it is what makes using a new OS possible for more people.

EDIT: Good conversation all. This is genuinely not intended to be a troll post, I just feel it is good to share experiences especially on the frustations that arise from move between OSes.

Using KDE plasma, Archlinux, Pipewire, Focusrite 2i2 3rd Gen

Audio from built-in audio and via GPU into display speakers all works fine but audio through my Focusrite is badly distorted, like it is running at super-low quality.

I've spent most of today trying to work out how to make pipewire use the right bit/sample rates. It. This should be a basic GUI feature, and certainly shouldn't need to sudo edit cryptic files to configure this stuff. I use Reaper and I'll need to change bit / sample rates from time to time, so having to make with config files is just nuts. This should be a basic function available in the control panel (Like windows has had for decades). / rant

Anyway, I genuinely want to fix this problem and would really like a GUI tool for it, but a working config edit will do at this point. I can' also make a script to tweak it on demand I suppose.

There is a video that suggests building a new kernel driver for it, which is even more nuts for something so basic.

System spec - Ryzen 3700X CPU - AMD RX 7900 XT GPU

I got an AMD GPU specifically because I wanted to switch to Linux. I've done a bunch of testing over the last year while I still had an nVidia card. Now I've got an AMD GPU I feel ready but it has not gone well.

When I use multiple monitors I get a range of odd behaviours, including a white screen, lock ups, failure to display anything on second screen. I've unplugged the second screen for now and all is OK except that adaptive sync does not work properly.

When I set adaptive sync to "Always" in the settings the screen sort of flickers when I move the mouse. To be more precise the screen gets a bit brighter when the mouse is moved, then returns to previous slightly dimmer brightness when the mouse is stopped. There are no errors that I've found.

Both of those issues happen in fresh Fedora 38 and Arch Linux installs. I'm running KDE-plasma (using Wayland not X) so it seems like a KDE issue. Though I'm about to test it with a Fedora and gnome install next, though I doubt it will be any different.

EDIT: Small update. Running Arch/KDE. I have found I can get it sort of working. I boot the PC with a single monitor (my 165Hz ultrawide) and set it to 60Hz, then turn on the second (1080p 60Hz) monitor. At this point I can set the then changing the ultrawide to 165Hz and set adaptive sync to automatic, but I have to do this process everytime I turn my PC on. Also, if it goes to sleep or I want to shutdown/reboot it goes mad again and things lock up. I have to turn off the second monitor off before I reboot/shutdown, or before I goes to sleep. Then I have to go through the whole process again. Obviosuly not ideal.

EDIT2: Turns out it was the old LCD I was using as a second display. It has been around a very long time, and while it always worked OK it clearly doesn't like something about how Linux talks to it. Anyway it is working now. Though Adaptive sync on the desktop is still flickery.