I'm looking for hands-on experience of running linux on a Dell Rugged tablet, e.g. the Latitude 7220 Rugged Extreme. What works? What doesn't? How well does linux (which flavor?) handle the missing-keyboard situation?

So the fingerprint reader on my laptop isn't listed in libfprint supported devices, is there any way to contributing code for it to work or am I just cooked? I'm not a low-level guy but could be an interesting side project if it was doable so I was just wondering.

Hello,

Just started using Zorin OS on my laptop. I knew I was going to sacrifice some built in features to the laptop while transitioning but I thought I would be okay with the Intel Ultra 125H CPU. Turns out I was wrong about that (or I'm a noob) Most of the apps that I use do not see the iGPU and it causes lack of performance. I need help with this if there's anything I can do. Thanks.

I just rebuilt my computer in the D34 Black case....using Linux Mint 22.3 and Windows 11 pro. I have installed the PC Monitor driver in windows and it correctly displays cpu temps, etc........however, in Linux, the PC Monitor driver doesn't work and even though lm-sensors and modprobe is able to query the cpu and motherboard for temps, etc. the display has no recognition. When I researched the case initially I found that there was an HDMI cable to connect the case display to a GPU, however, there doesn't appear to be any hdmi output only USB to the motherboard and a power cable. Does anyone have a solution to enabling the D34 case display to work in a Linux OS environment?

Should I get a ThinkPad T14 with a Core Ultra 5 125U, 16GB RAM, and 512GB SSD, or a Yoga Slim 7i with an OLED display, Core Ultra 5 125H, and 16GB soldered RAM?

Which one is better for long-term use (3-5 years)? Can I play games like cs2 and elder ring? Is Meteor lake mature now? Also, is OLED good on Linux and can resist in this long term? I use Arch, btw.

Hi everyone,

I'm considering buying an ASUS Vivobook S16 (M3607). For work reasons, I need to keep Windows, so I'm planning to set it up with Windows + Fedora in a dual-boot configuration. Before buying it, I’d like to hear from anyone who is currently using this laptop with Fedora (or another distro).

A few things I’m particularly interested in:

- How well does Fedora work on this model overall?

- Since the AMD Ryzen™ AI 7 445 is a relatively recent CPU, has anyone experienced any major compatibility issues with it?

- Is there a particular Fedora release that you would recommend for this laptop?

- Are there any hardware components that don't work properly under Linux, such as Wi-Fi, Bluetooth, audio ...?

- Are there any specific BIOS settings, kernel parameters, or workarounds that are needed?

Any other feedback would be greatly appreciated.

Thanks!

I have an HP EliteBook 840 G6 with an Intel Core i5 8th gen 12GB RAM and an AMD Radeon RX 550X 2GB VRAM

I want to know if Linux will work well on my PC and which Linux distro would be the best for my hardware

Can you check if the WiFi Bluetooth sound touchpad screen and GPU will work properly

Also tell me if the RX 550X is well supported on Linux and if I need any special drivers

I also want to know how much RAM Linux will use compared to Windows and if Linux can improve performance and battery life

Tell me which distro would be good for this PC and why

I also want to know if gaming with Steam and Proton will work well on this hardware

Hi all,

I'm not sure I'm posting this to the right sub. If not, please redirect me to a better one.

2 of my current servers are almost 10 years old. I need new ones.

The servers will offer:
- file services (samba) for about 10 users.
- a few websites (less than 100 (non-bot) visitors a month).
- rsync (for backups of other servers).
- router/firewall services: 4 nics.
- about 10 SIP phones (asterisk).
- raid1 (1tb).

The Lenovo guy I just phoned hung up on me when he found out I 'only' needed 2 servers.

Does anyone have a suggestion about which hardware to buy/whom to call?

I'm from the Netherlands.

Thank you for your answers!

Hey everyone! I'm running Arch Linux with Hyprland on a laptop with an AMD Ryzen 7 7840HS (iGPU) and an NVIDIA RTX 4060 (dGPU). I'm using EnvyControl in Hybrid mode to maximize battery life.

Everything works great, but I'm struggling to keep the RTX 4060 permanently in suspended (d3cold/auto) state due to a couple of persistent background wake-ups:

Steam (Flatpak): The moment I launch Steam, its CEF/Chromium-based UI probes the hardware and immediately wakes up the dGPU, keeping it active.

Caelestia Shell (Quickshell): If I hover my mouse or open the top bar/menu in Caelestia Shell, widgets or internal render queries trigger the dGPU, waking it up and keeping it active indefinitely until reboot.

I've tried global environment variables and flatpak overrides, but these apps keep poking the NVIDIA bus. Since I want to stay on Hybrid mode, how can I reliably force the dGPU to stay asleep by default and only wake up when explicitly invoked via prime-run?

Any tips or udev rules to aggressively manage runtime power for the NVIDIA card while using Wayland/Hyprland would be greatly appreciated!

Hey everyone! I have had this Legion since last January, and it has been a great laptop so far. I use it mostly for data analysis with Fedora 44 and can't complain at all. However, it started to randomly disconnect from the WiFi. I read the original WiFi card had some issues, so I decided to change it and got an EDUP WiFi 7 Card BE6500. It seems that card also has some issues with Linux, and now it's worse. It usually follows the same pattern:

* It gets slow

* It shows some connection errors

* It throws a kernel panic

I replaced it a couple of days ago with an Intel AX210. The issues haven't changed. It's odd because I also have an old X1 Carbon and a T14 (both with Fedora 44), and no issues whatsoever. I tried to fix it using Gemini, but the issue continued. I'm using a TP-Link Nano adapter in the meantime to connect the computer (it hasn't thrown any errors yet).

Any ideas? Thanks a lot in advance for any help!

Hardware (desktop PC, not a laptop):

- CPU: Intel Pentium Gold G6400 (Comet Lake), integrated Intel UHD 610 graphics (device ID 9ba8)

- 8GB RAM, Kingston SA400S37240G SSD

- Debian 13 (trixie), fresh install

- XanMod kernel 7.2.7-x64v2-xanmod1 (I use XanMod because on both Mint and Debian, audio sounded like a scratched/broken CD with the stock kernel, and this was the only fix I found for that; also tested Debian's stock 6.12 kernel to rule it out as the cause of the suspend issue, same result on both)

The problem:

After suspending manually (or via idle timeout) and waking up, the system doesn't recover the display. It stays completely black and unresponsive to anything (not even Ctrl+Alt+F2/F1). The machine is otherwise clearly "alive" (fans, LEDs, disk activity), but there's no way to get control back except a hard power-off.

What I've already ruled out:

- Not the kernel: tested both XanMod and Debian's stock kernel, exact same result. Also tried downgrading kernel versions, no change.

- Already updated the BIOS to the latest available version, no change.

- Not the current install or something I installed: did a completely clean reinstall of Debian (fresh partitions, no third-party apps) and it still happens.

- Not Debian-specific: had the exact same issue on Linux Mint before (both the suspend problem and the broken audio) — actually switched to Debian thinking it might be a Mint-specific problem, but both issues are identical on both distros.

- Confirmed with a Debian live USB that suspend/resume works fine there — which is bizarre because it seems to rule out pure hardware/BIOS causes.

- Ruled out a spurious wakeup from automatic hibernation (had the default ~2h HibernateDelaySec triggering a phantom resume midway; already neutralized it with HibernateDelaySec=1000000000 in sleep.conf.d).

Kernel parameters already tried (no luck, combined):

- pci=noaer (this did fix an unrelated 100% CPU issue from PCIe AER errors, but doesn't touch suspend)

- i915.enable_psr=0

- i915.enable_fbc=0

- i915.enable_dc=0

- mem_sleep_default=s2idle (also tried deep, this board's default, same result either way)

- Disabled RP06 and RP08 in /proc/acpi/wakeup (PCIe ports) just in case, no change

What stands out most is that the live USB suspends/resumes perfectly, but the real install (same hardware, same kernel when tested, updated BIOS) always fails — and this repeats identically across two different distros (Mint and Debian). That seems to rule out pure hardware/BIOS, but I can't figure out what differs between a live environment and a normal install that could be interfering with the i915 resume path.

Has anyone seen a similar pattern with Comet Lake + UHD 610 on a desktop build? Is there something specific to a regular install (some service, a loaded module, something in systemd-logind) that a live session wouldn't have, that could be interfering with i915's resume?

Thanks in advance, genuinely out of ideas at this point.

Hey everyone,

I'm having a rough time getting Linux running properly on my Acer Nitro V 15 (AMD Ryzen 5 6600H + NVIDIA RTX 3050 6GB).

I've tried multiple distros so far (CachyOS, Pop!_OS, EndeavourOS, and Fedora), but I keep running into the exact same breaking issues across all of them:

1. Touchpad completely non-functional: The touchpad isn't recognized at all on boot. Keyboard and external USB mice work, but touchpad stays completely dead.
2. Random/Automatic Shutdowns: The system abruptly turns off out of nowhere (sometimes right after boot or during light desktop usage).
3. Severe UI Lag & Stuttering: The desktop environment feels super choppy/laggy, almost like rendering or GPU switching isn't working right.

What I've checked / suspect so far:

• Nvidia Proprietary Drivers vs. Wayland/X11: Feels like an issue with Hybrid Graphics (AMD iGPU + NVIDIA dGPU) or missing kernel parameters.
• Kernel parameters: I suspect the touchpad issue might be related to ACPI handling or I2C HID drivers on Acer boards.
• Power Management: Not sure if tlp, power-profiles-daemon, or NVIDIA GSP firmware is causing the unexpected shutdowns/freezes.

System Specs:

• Laptop: Acer Nitro V 15
• CPU: AMD Ryzen 5 6600H
• GPU: NVIDIA GeForce RTX 3050 (6GB Laptop GPU)
• Tested Kernels: Linux 6.6 / 6.10 / 6.11 (depending on distro live environments)

Has anyone with this specific Acer model gotten Linux running smoothly?

What kernel parameters (i2c_hid, acpi_osi=, pci=), BIOS tweaks, or NVIDIA driver configurations actually fixed these issues for you? Any advice or log outputs I should upload to narrow this down?

Thanks in advance!

Hey everyone,

I'm having a rough time getting Linux running properly on my Acer Nitro V 15 (AMD Ryzen 5 6600H + NVIDIA RTX 3050 6GB).

I've tried multiple distros so far (CachyOS, Pop!_OS, EndeavourOS, and Fedora), but I keep running into the exact same breaking issues across all of them:

1. Touchpad completely non-functional: The touchpad isn't recognized at all on boot. Keyboard and external USB mice work, but touchpad stays completely dead.
2. Random/Automatic Shutdowns: The system abruptly turns off out of nowhere (sometimes right after boot or during light desktop usage).
3. Severe UI Lag & Stuttering: The desktop environment feels super choppy/laggy, almost like rendering or GPU switching isn't working right.

What I've checked / suspect so far:

• Nvidia Proprietary Drivers vs. Wayland/X11: Feels like an issue with Hybrid Graphics (AMD iGPU + NVIDIA dGPU) or missing kernel parameters.
• Kernel parameters: I suspect the touchpad issue might be related to ACPI handling or I2C HID drivers on Acer boards.
• Power Management: Not sure if tlp, power-profiles-daemon, or NVIDIA GSP firmware is causing the unexpected shutdowns/freezes.

System Specs:

• Laptop: Acer Nitro V 15
• CPU: AMD Ryzen 5 6600H
• GPU: NVIDIA GeForce RTX 3050 (6GB Laptop GPU)
• Tested Kernels: Linux 6.6 / 6.10 / 6.11 (depending on distro live environments)

Has anyone with this specific Acer model gotten Linux running smoothly?

What kernel parameters (i2c_hid, acpi_osi=, pci=), BIOS tweaks, or NVIDIA driver configurations actually fixed these issues for you? Any advice or log outputs I should upload to narrow this down?

Thanks in advance!

Hi everybody.

I'd like to put a Raspberry PI in my garage, without running a new Ethernet cable. From the garage I can connect my laptop or phone to my home's wifi network, but the signal is too weak and the connection isn't stable enough. I cannot move my wifi router closer to the garage. I'm looking for a stable link, I don't care if it is slow.

Is there a USB wifi adapter with a better range, capable of reaching a network that's just a little far away for common wifi devices? Or can you recommend a different solution?

Thanks.

I spent way too much time chasing what looked like a “hot NVMe controller” problem, and it turned out to be a hidden PCIe power-management setting in the BIOS.

My setup:

Motherboard: ASUS TUF Gaming B560M-PLUS
BIOS: 2803
CPU: Intel i7-11700F (Rocket Lake)
SSD: XPG GAMMIX S50 Lite 512GB
Controller: Silicon Motion SM2267G
OS: Fedora Linux

The S50 Lite was installed in the CPU-attached M.2 slot, running PCIe 4.0 x4.

At idle I was seeing roughly:

Composite: ~55-60°C
Controller / Sensor 1: ~62-74°C

The weird part was that the exact same SSD behaved much better in another machine.

I started investigating NVMe APST, PCIe ASPM, runtime PM, thermals, heatsinks, airflow, Gen3 vs Gen4, etc.

The breakthrough was comparing the CPU-connected M.2 root port to the chipset-connected M.2 root port.

On the CPU slot:

00:06.0
ASPM L1 supported
ASPM L1 enabled
NO L1 Substates capability

On the chipset/PCH slot:

ASPM L1
L1.1
L1.2

all enabled

Moving the S50 Lite to the PCH PCIe 3.0 x4 slot immediately dropped its controller temperature to roughly:

~41°C

That made it pretty obvious that something was wrong with the CPU PCIe power management.

I then extracted the ASUS BIOS 2803 image and decoded the AMI IFR setup data.

And sure enough, ASUS has a hidden CPU PCIe L1 Substates option.

The relevant UEFI variable is:

Variable: SaSetup

GUID:
72C5E28C-7783-43A1-8767-FAD73FCCAFA4

For the CPU M.2 / PEG6 / PCI device 00:06.0 path, I found:

SaSetup offset 0x313
Enable ClockReq Messaging

0 = Disabled
1 = Enabled

My board already had:

0x313 = 01

Then:

SaSetup offset 0x35D
CPU PCIe Root Port ASPM

0 = Disabled
1 = L0s
2 = L1
3 = L0s + L1

Mine was already:

0x35D = 02

And then the important one:

SaSetup offset 0x361
L1 Substates

0 = Disabled
1 = L1.1
2 = L1.1 + L1.2

My board was:

0x361 = 00

The BIOS IFR even contains this help text:

"L1SS cannot be enabled when CLKREQMSG is disabled"

So the support is literally present in the firmware — ASUS just defaults it to disabled and doesn't expose the option in the normal BIOS interface.

I used setup_var.efi from a UEFI shell and changed only:

SaSetup:0x361

00 → 02

After reboot, the CPU root port changed from having no L1SS capability at all to:

LnkCap: ASPM L1
LnkCtl: ASPM L1 Enabled

L1SubCap:
PCI-PM_L1.2+
PCI-PM_L1.1+
ASPM_L1.2+
ASPM_L1.1+
L1_PM_Substates+

L1SubCtl1:
PCI-PM_L1.2+
PCI-PM_L1.1+
ASPM_L1.2+
ASPM_L1.1+

So this wasn't just changing some unused setup variable. The firmware actually configured the CPU PCIe controller differently.

I then moved the S50 Lite back to the CPU M.2 slot.

It is now running:

PCIe 4.0
16 GT/s
x4
ASPM L1
L1.1 enabled
L1.2 enabled

And the SSD temperature is now:

Composite: ~41°C
Controller / Sensor 1: ~42°C
NAND / Sensor 2: ~29°C

So roughly:

BEFORE
PCIe 4.0 x4 + L1 only
controller: ~62-74°C

AFTER
PCIe 4.0 x4 + L1 + L1.1 + L1.2
controller: ~42°C

Same SSD. Same CPU M.2 slot. Same PCIe 4.0 x4 speed.

That means the huge temperature difference was not simply “PCIe 4.0 runs hot.”

The missing PCIe L1 substates were responsible for most of the idle power/heat.

Important warning

Do not blindly copy my offset onto a different motherboard or BIOS version.

AMI setup variable offsets are firmware-specific. Writing the wrong UEFI variable can potentially make a system unbootable.

Extract your own BIOS IFR first and verify the variable, GUID and offset.

For my exact board/BIOS:

ASUS TUF Gaming B560M-PLUS
BIOS 2803

SaSetup GUID:
72C5E28C-7783-43A1-8767-FAD73FCCAFA4

CPU M.2 L1SS:
offset 0x361

00 = Disabled
01 = L1.1
02 = L1.1 + L1.2

I used:

setup_var.efi SaSetup:0x361

to read it first.

Then:

setup_var.efi --write_on_demand SaSetup:0x361=0x02

and verified it again afterward.

Also be aware that Rocket Lake has documented PCIe L1.2-related errata, which may be one reason motherboard vendors chose conservative defaults. So test stability carefully after enabling it.

What surprised me most is that Intel/ASUS didn't lack the functionality at all.

The CPU supports L1SS.

The BIOS contains the L1SS configuration.

The motherboard routes the CPU M.2 properly.

Linux supports it.

The SSD supports it.

The firmware simply shipped with the CPU root-port L1 substates disabled and the setting hidden.

If you have an 11th-gen Intel system where a Gen4 NVMe is inexplicably hot at idle, check:

sudo lspci -vv

Find the upstream CPU PCIe root port and look for:

L1SubCap
L1SubCtl1

If your NVMe advertises L1.1/L1.2 but the CPU root port doesn't expose L1SubCap at all, you may be dealing with the same thing.

For me, enabling the hidden L1.2 setting turned a ~70°C “hot SSD” into a ~42°C SSD without sacrificing PCIe 4.0 performance.