Search

cross-posted from: https://lemmy.ca/post/38277245

I am looking to switch to a different Linux distribution (or BSD). I currently use openSUSE Tumbleweed, which is quite nice, but I'm having issues with my USB ports and it takes a hot second to boot up.

However, the reason I'm asking here instead of going straight to DistroWatch is that my laptop has a problem. When I turn it on, it bootloops unless it's connected to power when I press the button. As such, this distribution would need to be able to handle running for weeks on end without a reboot.

I could get this repaired or replaced, but I have neither the time nor the money to spare.

So, does anyone have any suggestions? Or should I just slap Fedora Kinoite on it and call it a day?

EDIT: I went for Debian, as well as running fwupd, and it's all working now. Thanks!

Final edit: I got all the Linux stuff right but made a dumb mistake generating the image on the Windows side. Watching the VM boot right now. Thanks to all for your support!

cross-posted from: https://slrpnk.net/post/15860280

Contemplating Fedora Kinoite for work daily driver. Need to prove that I can virtualize an existing physical Windows 11 machine. Using Bazzite on a personal laptop as a host test bed.

Test host seems to be set up correctly. I layered the packages in the virtualization group, layered virtio-win (from downloaded rpm package), added my user to the libvert group, and enabled libvirtd. After a reboot or two, I can connect with the Virtual Machine Manager and define my VM.

On physical machine I used Disk2vhd to generate a vhdx. Moved that file to the test host and converted to qcow2. Copied disk image to /var/lib/libvert/images and added it as my drive image when I defined the VM.

VM starts but will not boot. Stupid question: Should I have installed virt-w

Hello, I came across zram recently and I'd like to know if I should use it, my laptop only has ~4GB of ram, and for the most part it'll only stutter when I open multiple programs or a game, so would zram be adequate in my case?

Also, would the compressing and decompressing have a significant impact on my cpu?

I use KDE on arch and would like to achieve the following behavior:

Whatever way I launch Konsole, I want it to check whether there already is a Konsole instance. If one exists, it should be brought into focus, and if no instance exists, one should be launched.

I am unable to find such an option in the Konsole settings, even though I found a roughly 1 year old forum entry mentioning such a setting. Was it removed or am I just blind? Or do I need some optional dependency?

Alternatively, it would be fine if this could simply kick in when I use my Super+K shortcut, which I've set up. Maybe there's a way to call Konsole from the terminal like that? I tried using konsole --force-reuse but it didn't seem to do the trick, and konsole --new-tab does not bring Konsole into the foreground.

Edit: Here's a script that does this, by @Audalin@lemmy.world

 undefined

    
#!/bin/bash
WIN="$(kdotool search --class org.kde.konsole | head -1)"
if [[ "$WIN" != "" ]]; then 

  

I recently bought a Drop ENTR, and I would like to use the media keys. On the drop.com website it says that using FN + the F-keys should work, but “Fn hotkeys may work with Windows operating system only.”. Well, for me it doesn’t work. Any ideas as to why that could be, or how I could go about creating a workaround?

obligatory I use arch btw

Hi, no matter how many times I click Restart & Updates..., the integrated firmware update never get's installed. Everything else does as usual, but not this one.

Is there a command line I can use to force install this?

Fedora 39.

EDIT: Solved.

My ESP /boot/efi partition originally created by Windows 11 had no space for the firmware upgrade files, so the upgrade never ran.

I fixed it by resizing it from 100MB to 200MB, now it works well.

Just in case anyone runs into this in the future, the process is unfortunately not as simple as resizing it on GParted because of a bug in libparted https://bugzilla.gnome.org/show_bug.cgi?id=649324 but there is a workaround in the comments.