Finding the Perfect Linux-Compatible Computer

Let’s suppose you want to get into the Linux thing and you want to do it with a new computer. You could buy a Linux laptop or desktop from a number of different vendors including System76, Tuxedo, Dell, Lenovo and others. What if you come across a computer in a technology store how do you determine if it’s going to work with your favorite Linux distribution. You check the Hardware for Linux database or you could check with Ubuntu Certified where folks have already done the homework for you. Fedora maintains another list of certified hardware.

Today I was shopping at a prominent technology store and spotted a Dell Inspiron 3530 that was just what I was looking for and at a price I was willing to pay but I wanted to make sure that it would work with Linux so I did a quick internet search and Ubuntu Certified supplied the answer to my question. I brought this sleek new laptop home and using a Live USB with Fedora 42 KDE Plasma and quickly determined that the hardware was going to work. These databases are a great way to help users determine the likelihood that there new or used computer would be a suitable candidate for Linux.

I had Cronopete installed on the laptop I was replacing so I did a quick backup of all my files and then installed Cronopete on the new laptop. Cronopete easily restored the files and quickly I was ready to begin writing this article.

This laptop is modest but adequate and I fell in love with it as soon as I started using it. The unit has a touch screen and it works well. It is going to be more than adequate for my needs and I am grateful that I found it. Here’s a snapshot of the system using

$ inxi -b
 Host: fedora Kernel: 6.14.9-300.fc42.x86_64 arch: x86_64 bits: 64
  Desktop: KDE Plasma v: 6.3.5 Distro: Fedora Linux 42 (KDE Plasma Desktop
    Edition)
Machine:
  Type: Laptop System: Dell product: Inspiron 15 3530 v: N/A
    serial: <superuser required>
  Mobo: Dell model: 0VPMKH v: A00 serial: <superuser required> UEFI: Dell
    v: 1.15.0 date: 09/06/2024
Battery:
  ID-1: BAT0 charge: 38.9 Wh (96.3%) condition: 40.4/40.0 Wh (101.0%)
CPU:
  Info: 10-core (2-mt/8-st) 13th Gen Intel Core i5-1334U [MST AMCP]
    speed (MHz): avg: 669 min/max: 400/4600:3400
Graphics:
  Device-1: Intel Raptor Lake-P [UHD Graphics] driver: i915 v: kernel
  Device-2: Sunplus Innovation Integrated_Webcam_HD driver: uvcvideo
    type: USB
  Display: wayland server: Xwayland v: 24.1.6 compositor: kwin_wayland
    driver: gpu: i915 resolution: 1920x1080~60Hz
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.0.7
    renderer: Mesa Intel Graphics (RPL-U)
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdriinfo,
    xdpyinfo, xprop, xrandr
Network:
  Device-1: Realtek RTL8852BE PCIe 802.11ax Wireless Network
    driver: rtw89_8852be
Drives:
  Local Storage: total: 476.94 GiB used: 7.91 GiB (1.7%)
Info:
  Memory: total: 8 GiB note: est. available: 7.44 GiB used: 3.35 GiB (45.0%)
  Processes: 349 Uptime: 18m Shell: Bash inxi: 3.3.38

Switching to Linux can be an exciting journey, and having a computer that seamlessly supports your favorite distribution makes all the difference. With resources like Ubuntu Certified and Fedora’s compatibility database, finding Linux-ready hardware has never been easier. My new Dell Inspiron 3530 may be modest, but it’s exactly what I needed—reliable, responsive, and ready to power my workflow. Thanks to Cronopete, setting up was effortless, allowing me to jump right into writing. If you’re considering making the switch, remember that a little research upfront can ensure a smooth transition into the world of Linux. Happy computing!

Fedora KDE Plasma and the Curious Case of Chrome’s Muted Audio

I have been using Fedora with the KDE Plasma desktop environment for almost three months, and overall, it’s been a wonderful experience. However, I’ve encountered some issues along the way. The most recent problem involved the Chrome browser. A couple of weeks ago, Chrome stopped functioning correctly, and I couldn’t launch it even after rebooting my computer. As a solution, I uninstalled Chrome using the command line and then installed the Flatpak version. This version worked well until yesterday, when I experienced problems with audio output while trying to watch videos on YouTube and Acorn TV.

Firefox and Chromium worked on those sites, but Chrome did not. After searching online for a solution, I found several suggestions for adjusting settings within the browser. However, I could not find a fix until I discovered that KDE Plasma has a sound control feature that allows you to turn the sound on or off specifically for the Chrome browser.

First, I had to open ‘System Settings,’ which is found on the menu bar, in my case, at the bottom of the display, underneath the red arrow. System settings can also be opened from under the Fedora button to the left of the display.

Screen picture by Don Watkins CC by SA 4.0

Now that you have opened the ‘System Settings’ you need to navigate to that section of the settings that addresses the control of ‘Sounds.’

Screen picture by Don Watkins CC by SA 4.0

Upon opening the ‘Sound’ submenu,, I saw that the Chrome browser sound was muted. Unmuting was easy: I clicked on the muted control and sound was restored,, and I was able to enjoy the videos I wanted to view.

Screen picture by Don Watkins CC by SA 4.0

I’m still unsure how the sound got muted in the first place, but I’m glad I found a way to resolve the issue. The KDE Plasma desktop offers more configuration control options than any other Linux system I have used. With this complexity comes great power, but also a steep learning curve. Nonetheless, I continue to be impressed by the capabilities of both Linux and Fedora KDE Plasma.