Note: I added more info in the OP

geteilt von: https://discuss.tchncs.de/post/52933193 (OP)

A few days ago I noticed, that my system disc (~120gb) is almost maxed out. Since almost everything that takes up considerable disc space resides on my 2 discs, I started investigating, supported by ChatGPT. Turns out I've been running on a writable snapshot that keeps growing with each update. Again, important stuff is on my other discs, so reinstalling Linux allover would be a inconvenience, but no problem. Yet, I'd like to try repairing current installation, if only for the lessons learned.

I let ChatGPT summarize everything as a post so you don't have to deal with my half-educated gibberish:

du -xh --max-depth=1 / only shows ~16 GB used, but df -h reports ~113 GB used. Root, /var, /usr, /home, etc. are all on the same Btrfs filesystem. Snapper is enabled.

I confirmed that Btrfs snapshots are consuming the space, but I’m stuck with a writable snapshot (#835) that is currently mounted, so I can’t delete it from the running system.

To make things worse:

GRUB menu does not appear (Shift/Esc does nothing)

The system still boots into Linux, but I can’t select older snapshots

I tried repairing from an Ubuntu live USB, but:

NVMe device names differ from the installed system

Chroot fails with /bin/bash or /usr/bin/env not found

Likely because /usr is a separate Btrfs subvolume and not mounted

At this point I’m trying to:

Properly mount all Btrfs subvolumes from a live system

Chroot into the installed system

Delete old Snapper snapshots

Reinstall GRUB so the menu works again

If anyone has step-by-step guidance for recovering openSUSE Tumbleweed with Btrfs snapshots and broken GRUB access, I’d really appreciate it. I’m comfortable with the command line but want to avoid making things worse.

Hope someone can make something of it and help me fix my system.

The code can be found by clicking here. Save it as mini95.c, then compile this with "gcc mini95.c -lX11 -o mini95".

Just some coverage of a few systems from Jesse at distrowatch. Sadly, neither MenuetOS nor Sparky CDE go anywhere due to issues.

How do you guys actually learn how to fix certain things? Its mind boggling how one can visit a forum and there's people saying "oh yeah just run -c xhhkrk ()<>[] bbbhjl and that will fix your sound issue"

Like WHERE do you even start? I hate having to look things up all the time when everyone else on windows "just works". Copying commands off forums endlessly doesn't really help you learn.

Example, installed cachyos on an older laptop, but sound and screen dimming will not work. I have no ides where to even begin with that. I feel like a windows user could at least poke around control panel and probably fix the issue but its way harder with linux.

I have had luck with almost everything working with mint on my desktop (except vr, oculus is a nighmare to get working) and have been running that about a year. If I had to set it all up again id have to re look up everything I forgot since then..

If there was something like man but easier to parse through, that would be immensely helpful. Like for my sound issue, if there was a better organized manual that I could look under "sound" and see the inner workings laid out and common issues, thats what we need. Otherwise people are going to be terrified of linux because its so hard.

I'm on Ubuntu. I'm trying to get Jellyfin working. I tried it with the app center and it's in a folder that i can't access. Also the path directories aren't recognized, so i said fuck it and deleted the app.

Now i type "sudo apt update" and get this:

Error: Malformed entry 1 in list file /etc/apt/sources.list.d/jellyfin.list ([option] no value) Error: The list of sources could not be read.

The Wine team is proud to announce that the stable release Wine 11.0 is now available.

This release represents a year of development effort, around 6,300 individual changes, and more than 600 bug fixes. It contains a large number of improvements that are listed below. The main highlights are the NTSYNC support and the completion of the new WoW64 architecture.

The source is available at https://dl.winehq.org/wine/source/11.0/wine-11.0.tar.xz

Binary packages for various distributions will be available from the respective download sites.

You will find documentation here.

Wine is available thanks to the work of many people. See the file AUTHORS for the complete list.

What's new in Wine 11.0

WoW64

• The new WoW64 mode that was first introduced as experimental feature in Wine 9.0 is considered fully supported, and essentially has feature parity with the old WoW64 mode.

• 16-bit applications are supported in the new WoW64 mode.

• It is possible to force an old WoW64 installation to run in new WoW64 mode by setting the variable WINEARCH=wow64. This requires the prefix to have been created as 64-bit (the default).

• Pure 32-bit prefixes created with WINEARCH=win32 are deprecated, and are not supported in new WoW64 mode.

• The wine64 loader binary is removed, in favor of a single wine loader that selects the correct mode based on the binary being executed. For binaries that have both 32-bit and 64-bit versions installed, it defaults to 64-bit. The 32-bit version can then be launched with an explicit path, e.g. wine c:\\windows\\syswow64\\notepad.exe.

Synchronization / Threading

• The NTSync Linux kernel module is used when available, to improve the performance of synchronization primitives. The needed kernel module is shipped with the Linux kernel starting from version 6.14.

• Thread priority changes are implemented on Linux and macOS. On Linux, this is constrained by the system nice limit, and current distributions require some configuration to change the nice hard limit to a negative value (in the -19,-1 range, where -5 is usually enough, and anything lower is not recommended). See man limits.conf(5) for more information.

• NTDLL synchronization barriers are implemented.

• On macOS, the %gs register is swapped in the syscall dispatcher. This avoids conflicts between the Windows TEB and the macOS thread descriptor.

Kernel

• NT Reparse Points are implemented, with support for the mount point and symlink types of reparse points.

• Write Watches take advantage of userfaultfd on Linux if available, to avoid the cost of handling page faults in user space.

• NT system calls use the same syscall numbering as recent Windows, to support applications that hardcode syscall numbers.

• On ARM64, there is support for simulating a 4K page size on top of larger host pages (typically 16K or 64K). This works for simple applications, but because it is not possible to completely hide the differences, more demanding applications may not work correctly. Using a 4K-page kernel is strongly recommended.

Graphics

• The OSMesa dependency is removed, and OpenGL bitmap rendering is implemented with the hardware accelerated OpenGL runtime.

• The EGL OpenGL backend is extended, and used by default on the X11 platform. The GLX backend is deprecated but remains available, and is used as fallback if EGL isn't available. It can also be forced by setting the value UseEGL=N in the HKCU\Software\Wine\X11 Driver registry key.

• The VK_KHR_external_memory_win32, VK_KHR_external_semaphore_win32, VK_KHR_external_fence_win32, VK_KHR_win32_keyed_mutex extensions and the related D3DKMT APIs are implemented.

• In new WoW64 mode, OpenGL buffers are mapped to 32-bit memory space using Vulkan extensions if available.

• Front buffer OpenGL rendering is emulated for platforms that don't support it natively.

• OpenGL context sharing implementation in wglShareLists is improved.

• The Vulkan API version 1.4.335 is supported.

• Image metadata handling is better supported in WindowsCodecs.

• Many more conversions between various pixel formats are supported in WindowsCodecs.

Desktop integration

• X11 Window Manager integration is improved: window activation requests are sent to the Window Manager, and the EWMH protocol is used to keep the X11 and the Win32 active windows consistent.

• Exclusive fullscreen mode is supported, and D3D fullscreen mode is improved, especially improving older DDraw games.

• Shaped and color-keyed windows are supported in the experimental Wayland driver.

• Performance of several windowing-related functions is improved, using shared memory for communication between processes.

• Clipboard support is implemented in the Wayland driver.

• Input Methods are supported in the Wayland driver.

Direct3D

• Hardware decoding of H.264 video through Direct3D 11 video APIs is implemented over Vulkan Video. Note that the Vulkan renderer must be used. As in previous Wine versions, the Vulkan renderer can be used by setting renderer to vulkan using the Direct3D registry key or WINE_D3D_CONFIG environment variable.

• Direct3D 11 sampler minimum/maximum reduction filtering is implemented if GL_ARB_texture_filter_minmax is available (when using the GL renderer) or VK_EXT_sampler_filter_minmax (when using the Vulkan renderer).

• The following legacy Direct3D features are implemented for the Vulkan renderer:

  • Point size control.
  • Point sprite control.
  • Vertex blending.
  • Fixed-function bump mapping.
  • Color keying in draws.
  • Flat shading.
  • Alpha test.
  • User clip planes.
  • Several resource formats.

  Additionally, the bundled copy of vkd3d-shader includes many improvements for Shader Model 1, 2, and 3 shaders, including notably support for Shader Model 1 pixel shaders and basic Shader Model 1 texturing. The Vulkan renderer is not yet at parity with the GL renderer, and is therefore not yet the default.

Direct3D helper libraries

• D3DXSaveSurfaceToFileInMemory is reimplemented for PNG, JPEG and BMP files, enabling support for formats and other edge cases not supported by WindowsCodecs. It also supports saving surfaces to TARGA files.

• D3DX 11 texture loading functions are implemented, using code shared with earlier D3DX versions.

• Box filtering is supported in all versions.

• D3DXSaveTextureToFileInMemory supports saving textures to DDS files.

• D3DX 9 supports reading 1-bit, 2-bit, and 4-bit indexed pixel formats, as well as the CxV8U8 format.

• D3DX 10 and 11 support compressing and decompressing BC4 and BC5 formats.

• D3DX 10 and 11 support generating mipmap levels while loading textures.

• ID3DXEffect::SetRawValue() is partially implemented.

• ID3DXSkinInfo::UpdateSkinnedMesh() is implemented.

Input / HID devices

• Compatibility with more Joystick devices is improved through the hidraw backend. Per-vendor and per-device registry options are available to selectively opt into the hidraw backend.

• Force feedback support is improved, with increased compatibility for joysticks and driving wheels, and better performance.

• Better support for gamepads in the Windows.Gaming.Input API and with the evdev backend when SDL is not available or disabled.

• There is a configuration tab for the Windows.Gaming.Input API in the Game Controllers Control Panel applet.

• DirectInput compatibility with older games that use action maps and device semantics is improved.

• More device enumeration APIs from Windows.Devices.Enumeration and cfgmgr32 are implemented.

Bluetooth

• The Bluetooth driver supports scanning and configuring host device discoverability, with some basic support for pairing via both the API and a wizard. At this point, this is only supported on Linux systems using BlueZ.

• Bluetooth radios and devices (both classic and low-energy) are visible to Windows applications.

• Applications can make low-level RFCOMM connections to remote devices using winsock APIs.

• There is initial support for Bluetooth Low Energy (BLE) Generic Attribute Profile (GATT) services and characteristics, making them visible through the Win32 BLE APIs.

Scanner support

• DAT_IMAGENATIVEXFER is supported.

• Scanner selection and configuration are saved in the registry.

• TWAIN 2.0 API for scanning is implemented, which allows scanning to work in 64-bit applications.

• Multi-page and Automatic Document Feed scans are supported.

• There is a user interface showing scanning progress and error messages.

• The scanner user interface no longer blocks the application using it.

• Windows-native scanner drivers can be loaded if they're installed in Wine.

Multimedia

• The Multimedia Streaming library implements a custom allocator for DirectDraw streams, reducing the number of buffer copies required for filters which support a downstream custom allocator.

• Dynamic format change is supported in the DMO Wrapper, AVI Decoder, and GStreamer-based demuxer and transform filters.

• GStreamer-based demuxer filters support the Indeo 5.0 codec.

• The DirectSound Renderer filter more properly signals end-of-stream. Previously end-of-stream could be signaled too early, clipping the end of an audio stream.

• The ASF Reader filter supports seeking.

• The AVI Decoder filter supports nontrivial source and destination rectangles.

DirectMusic

• SoundFont(SF2) supports more features:

  • Parsing of preset, instrument and default modulators.
  • Layering support required for many SF2 instruments.
  • Reuse of downloaded waves and zero-copy access sample data to prevent out-of-memory errors.
  • Instrument normalization.

• The Synthesizer is improved:

  • The latency clock is derived from the master clock to fix uneven playback in certain tracks.
  • Voice shutdown is instant and the synth better handles channel pressure events and LFO connections.
  • Setting the volume is supported and is automatically done when creating a synth or adding a port.

• The DX7 version of the Style form is supported.

• Cache management improvements in the loader.

• More MIDI meta events are supported.

Mono / .NET / WinRT

• XNA4 applications run based on SDL3, and render using the new SDL_GPU API by default.

• A text layout engine supporting System.Windows.Documents APIs is added to WPF (Windows Presentation Framework).

• Theming works in Windows Forms.

• WinRT metadata files can be generated by widl, and there is an initial implementation of the loader classes.

• WinRT C++ exceptions are supported.

Internationalization

• Locale data is generated from the Unicode CLDR database version 48. The following additional locales are supported: bqi-IR, bua-RU, cop-EG, ht-HT, kek-GT, lzz-TR, mww-Hmnp-US, oka-CA, pi-Latn-GB, pms-IT, sgs-LT, suz-Deva-NP, and suz-Sunu-NP,

• Unicode character tables are based on version 17.0.0 of the Unicode Standard.

• The timezone data is based on version 2025a of the IANA timezone database.

Internet and networking

• MSHTML exposes DOM attributes as proper DOM nodes in standards-compliant mode.

• JavaScript typed arrays are supported.

• The MSHTML objects DOMParser, XDomainRequest and msCrypto are implemented.

• Ping is implemented for ICMPv6.

Databases

• MSADO supports writing changes to the database.

• Most of the MSADO Recordset functions are implemented.

• ODBC remaps Unicode strings to support ANSI-only Win32 drivers.

Debugging

• The PDB file loader in DbgHelp is reimplemented, to support large files (> 4G), faster loading, and use fewer memory resources.

• NT system calls can be traced with WINEDEBUG=syscall. Unlike WINEDEBUG=relay, this is transparent to the application, and avoids breaking applications that hook system call entry points.

• It is possible to generate both DWARF and PDB debug information in a single build.

Builtin applications

• The Audio tab of WineCfg allows configuring the default MIDI device.

• The Command Prompt tool cmd can create reparse points with mklink /j, and display them in directory listings.

• The Command Prompt tool cmd supports more complex instructions, and file name auto completion in interactive prompt.

• The Console Hosting application conhost supports F1 and F3 keys for history retrieval.

• The timeout application is implemented.

• The find tool supports options /c (display match count) and /i (case insensitive matches).

• The whoami tool supports output format specifiers.

• There is a basic implementation of the subst command

• There is an initial implementation of the runas tool.

Miscellaneous

• Common Controls version 5 and version 6 are fully separated DLLs, and v6-only features are removed from the v5 DLL for better compatibility.

• The PBKDF2 key derivation algorithm is supported in BCrypt.

• The well-known shell folders UserProgramFiles, AccountPictures and Screenshots are supported.

Development tools

• The IDL compiler can generate Windows Runtime metadata files (.winmd) with the --winmd option

• The winedump tool supports dumping MUI resources, syscall numbers, embedded NE modules, and large PDB files (>4G).

• The wine/unixlib.h header is installed as part of the development package, as a first step towards supporting use of the Unixlib interface in third-party modules. This is still a work in progress.

Build infrastructure

• The X11-derived install-sh script is reimplemented in C, to enable installing several files in a single program invocation. This speeds up the file copying phase of make install by an order of magnitude.

• Compiler exceptions are used to implement __try/__except blocks when building with Clang for 64-bit MSVC targets.

• The WineHQ Gitlab CI supports ARM64 builds.

Bundled libraries

• The LLVM Compiler-RT runtime library version 8.0.1 is bundled, and used when building modules in MSVC mode.

• The TomCrypt library version 1.18.2 is bundled and used to implement cryptographic primitives in the RsaEnh and BCrypt modules.

• Vkd3d is updated to the upstream release 1.18.

• Faudio is updated to the upstream release 25.12.

• FluidSynth is updated to the upstream release 2.4.2.

• LCMS2 is updated to the upstream release 2.17.

• LibMPG123 is updated to the upstream release 1.33.0.

• LibPng is updated to the upstream release 1.6.51.

• LibTiff is updated to the upstream release 4.7.1.

• LibXml2 is updated to the upstream release 2.12.10.

• LibXslt is updated to the upstream release 1.1.43.

External dependencies

• The OSMesa library is no longer used. OpenGL bitmap rendering is implemented using EGL instead.

• The HwLoc library is used for CPU detection on FreeBSD.

Devices: Bazzite Laptop, GrapheneOS Pixel 9, Boox Tab X

I'm annoyed with the functionality of KDEConnect at present. I very much like the concept, but there is friction preventing what should be a convenience from reaching its potential. Right now, I can mount the filesystem of connected devices on my laptop, but every time I do so I have to bypass an access restricted sign and do Ctrl+L to append storage/emulated/0 to the IP address of the connected device to actually access the mounted filesystem. Further, if there is more than one device, the two filesystems are practically indistinguishable from one another: I just spent about 5 minutes digging through the pictures on my tablet before I realized I was browsing the wrong device

1. Is there a way to automatically append storage/emulated/0 every time the device is mounted?

2. Is there a way to rename the filesystems so that I can easily distinguish between my phone and tablet?

Some other problems less directly important to what I would like to incorporate into my workflow:

I occasionally experience strange, unexplained disconnections/refusals to connect with the kdeconnect protocol, despite being connected by wifi, bluetooth, direct usb tether, or any combination thereof. This problem is infrequent and intermittent, and the only consistent solution seems to be restarting the affected device (usually the pixel).

3. Am I missing something about connecting devices; is there a log I can check for some kind of device error?

I'd appreciate some way to stream the screen from one device to another. Nothing major, but it would have been convenient a couple of times now, and it seems like an obvious addition to the capabilities.

4. Is something like that in the works? If not, what is the reason it's not? What would allow me to do this?

I’ve recently installed Mint on a clean partition, and set up dual booting to always prefer that partition over the Win10 one (on a separate sdd). At the moment I’m trying Mint for the very first time, seeing how I like it. And truth be told, it’s quite good! However I’ve had 2 system crashes in the last 2 days, and some games crash without an error log (old world went straight to desktop while mid-turn, and ghost of Tsushima crashed after I paused the game when pressing start).

I’d love to be more knowledgeable and figure this out by myself, but I can’t find a starting point to determine what went wrong in any of these instances.

Are there execution logs or actual error logs that I can check somewhere?

I switched fully to Linux from Windows (on my desktop) about 4 months ago. I'm a very old Linux user, I did my first install in '98 using Slackware, built an in-house web server for a company that hired me. But I've always been a "host my Linux servers on Digital Ocean" type of Linux user versus "desktop Linux user" and if I'm being honest, I switched to all FOSS everything years ago, so the only real reason I stayed on Windows was:

Gaming.

It was about five months ago my wife bought me a Steam Deck for my birthday. I was kinda mad about it, I thought it was too grandiose of a gift, but you know yeah, it was fucking rad. And I love it. It didn't take but a couple of weeks of use before I realized that Steam's coup was nearly complete. I knew it meant that Linux was now ready for prime time among gamers like me (who don't give a damn about multiplayer, nor kernel-level anti-cheat). I knew I could get Windows out of my life.

I didn't know what pitfalls awaited. My Windows machine was aging (Ryzen 3 3300X, RTX 3060) but still serviceable. I had another machine sitting in the living room that I used when really desperate (the wife was playing BG3 on the 3060), but it was getting waaaay too old to be practical (FX 6300, GTX 1050Ti). So I decided to modestly upgrade the living room machine, install Linux on it and use it instead of Windows and see how it went. If all went well, I'd wipe Windows.

I upgraded the living room machine (Ryzen 5 3600, RTX 5070, which required new mobo and RAM so I upgraded to 32G DDR4 3600 from my previous 16G and installed a 1TB NVMe in lieu of the HDD) - my timing could not have been more fortuitous, even though this was older, cheaper stuff, it was all nearly half the cost that it is now). On this machine, I installed Linux.

It didn't just go great. It went flawlessly. Everything works, with minimal intervention. I chose Mint because I didn't want an atomic distro, but I wanted something as friendly as possible for my wife's sake. All games are playing, from all sources. Steam, Epic, Gog, standalone. I play Elite Dangerous with a VKB/STECS setup and I was certain it was going to be a nightmare to setup. It wasn't. I ultimately had a single Windows program I couldn't live without (Notepad++) but it runs under Wine with zero issues.

There was only one thing left that I hadn't tackled that I was certain was going to be the real nightmare. Honestly, it didn't actually matter that much, which is why I left it for last. But I have an OG Vive, and I had heard it could be challenging. It wasn't. Installed Steam VR, launched it and it worked out of the gate as beautifully as it did on Windows, except better, because with a 5070 behind it, I could run everything on "VR Ultra" settings and it didn't even break a sweat. Holy shit, this is awesome!

I will be wiping the Windows machine tomorrow. Fuck Microsoft. Fuck ads. Fuck subscriptions. Fuck closed source gated off bullshit in general.

Thank you for coming to my TED talk.

I am still a relatively new Linux user, had tried Garuda and Bazzite on my Acer Gaming laptop 2021 (Intel integrated + Nvidia 3070 dgpu- muxless) back in July but neither worked, i kept getting weird freezes and nothing would open. Had no clue what the issue was and had zero Linux knowledge. So after a frustrating few days and many, many, many reboots I gave up. Reinstalled shitty Windows 10 again and that was that. Felt defeated lol.

Fast forward to November, the itch to go back to Linux was growing something fierce. Decided to follow some good advice from a friend, installed Pop OS and fuck, it worked like a charm. Fell in love and haven't looked back at Windows since.

Kept learning new things and picking up more knowledge about the terminal and was beginning to use quite a few commands without any fear. The terminal is class, feel like hackerman meme lol. I soon realised though that I was actually only using my Nvida gpu for everything, rendering and games etc. So decided to try hybrid. However i soon realised Steam wouldn't open, anything that i asked to run the discrete card would not actually run the Nvidia card. Tried removing the open drivers and replacing with the closed. Some things worked temporarily but I simply couldnt figure it out and decided to settle for manually switching between integrated and nvidia for different tasks. Handy feature on Pop OS 22.04.

Anyway, got the stupid distro hopping itch and started jumping about lol. Tried Cachy. Same issue with Nvidia card so bounced. Tried Nobara. Same again but stayed longer and tried few kernel PCI tricks using grubby (advice from somebody much more knowledgeable). That worked for a day or so but always kept going back to crashing the nvidia card (and was only able to use my Intel integrated card). So went back to Pop OS (my Linux safe space lol). Was almost ready to settle for my lot in life (in regards to this stupid Acer Nvidia laptop lol).

Throughout all this, I had been reading the Arch wiki off and on, and at first it may as well be gobbledegook. But after couple months of using Linux you just start picking things up a lot more, words that had no meaning before, soon made sense and you begin to have the basics down. I had been reading about this GSP firmware thing really late one night and then forgot next day and only remembered few days later. Apparently this GSP firmware that comes with the Nvidua driver can screw some of the older Nvidia cards and so disabling it, while using the closed driver can help some older machines. So earlier tonight, tried it on Pop just messing about and it worked. So I thought, fuck it, Nobara was brilliant, lets try that again and try and find out how this is done on Nobara.

Switched to Nobara, followed some stuff from the wiki and forums, did the commands, then rebuilt the akmods and regenerated the Drakut program. And hybrid graphics works fucking perfectly now!!! Fuck me, it feels amazing to have finally sorted a solution to an issue I was ready to give up on after trying to sort it for a couple weeks! And I also have to say, if I had simply gotten that answer the first night I went searching, I would be absolutely none the wiser about all the things I learnt through trial and error, through learning on the wiki and on forums etc.

Sorry for the long rant lol, just wanted to share a minor but personal triumph. After all that, I can really see how awesome Linux is. I honestly feel that I've learnt more about computers within the last few months on Linux, than I did in the last 15 years using Windows!

If anybody out there is thinking of trying Linux, you should absolutely give it a go! Jump in and have some fun! Make sure you back up any important data. But don't be afraid to make mistakes. Honestly that can be fun, figuring that out! There really are some great distros out there!

Linux4life motherfuckers!

Peace!

I recently decided that I want my resume to look better than the result of libreoffice. I installed texlive from the default trixie repository, and it works for the very simplest cases. However, trying to render a template which depends on CurVe resulted in an error about missing sty files.

By installing texlive from source, and installing CurVe to the working directory, I was able to fix that problem. However, there is still an error, and it appears to be an error in apa.bbx, a downstream dependency that comes with texlive. The error is

Package keyval Error: usenarrator undefined.

I'm not sure what I can do about this. I'm not very experienced with latex, mostly just using the default style as a convenient way to format math. Would swapping it for html be a recommended solution? Is there a good way from the command line to export html to pdf?

Most servers around the world run Linux. The same goes for almost all supercomputers. That's astonishing in a capitalist world where absolutely everything is commodified. Why can't these big tech companies manage to sell their own software to server operators or supercomputers? Why is an open, free project that is free for users so superior here?

cross-posted from: https://lemmy.world/post/41331598

I am trying to use a Thermaltake Blacx Duet (ST0015) HDD Docking Station with my Linux computers (Linux Mint and Ubuntu, all latest).

I have a SATA disk plugged in one of the bays and when I connect it to a USB port with its cable (everything is brand new) nothing happens.

lsusb returns:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub Bus 001 Device 003: ID 046d:082d Logitech, Inc. HD Pro Webcam C920 Bus 001 Device 004: ID 046d:0ac4 Logitech, Inc. G535 Wireless Gaming Headset Bus 001 Device 005: ID 046d:c53a Logitech, Inc. PowerPlay Wireless Charging System Bus 001 Device 006: ID 046d:c547 Logitech, Inc. USB Receiver Bus 001 Device 007: ID 26ce:01a2 ASRock LED Controller Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub

The only message in dmesgrelated to usb is:

[ 474.891877] usbcore: registered new interface driver usb-storage

which I understand means that the usb-storage module is loaded.

Same behavior in Ubuntu.

Does this mean that the hardware is just incompatible or is there anything more I can try?

New year, new OS for this M1 MacBook Air! I've been using Asahi Linux (via the flagship Fedora Asahi Remix) for a few weeks now. It's been my everyday laptop and I'm really impressed with how it's ...

TL;DR: Mozilla has a new CEO and a new mission: transform Firefox into an AI browser. That has run into some snags, as Firefox users don’t seem that interested in AI. Mozilla is forging ahead, utilizing deceptive patterns (previously known as dark patterns) to nag and annoy people into enabling AI features. You can see this in the introduction of Link Previews, an extremely invasive anti-feature that exists solely to push AI into your experience.

To improve Android-application function on the go, AOSP-derivatives (LineageOS, GrapheneOS, /e/OS, CalyxOS, etc.) are also tolerated, at least on the phone. This because so many people say mobile Linux (PostmarketOS, Sailfish OS, etc.) is not so nice yet in daily phone use.

This question didn't come from me originally, but I'll add my context anyway:
I come from Ubuntu (eww, Canonical) and Android (eww, Google, nope!).

I currently have Linux Mint with Cinnamon desktop on the laptop, and because of the bugs, I've been considering moving to something else with KDE (serious desktop UI), maybe OpenSUSE because its roots are so European.

I tried Fedora with Gnome on a tablet I had 2025, which seemed fine on a touchscreen, unlike Fedora with KDE.

My phone runs /e/OS with the default Nextcloud hosted by Murena (the company behind /e/OS), which is fine, and I appreciate that /e/OS can be bought pre-installed, and that it supports bootloader re-locking (against pickpockets) on many devices (Fairphone and Shiftphone of the European ones).

Special thanks to Firefox for a unified experience through a Mozilla-account. More of this kind of unification would be welcome.

Hey everyone! I'm finally fed up with Win11 and the bullshit that comes with it for the PC it's on.

It's being used as a Jellyfin+arr stack, qbit, Immich, and gaming PC for the living room.

I'm currently in the process of backing up all my important info and am doing research on which distro to use.

I don't mind tinkering, but for this PC, stability is key. I don't want to have to go in and update it every week... I want this one to work with minimal maintenance on my part.

I'd likely update it a few times a year, knowing me.

A few hardware specs:

MSI mobo (I've learned that UEFI can be a pain), 10600k, 2070 gpu, and will have a pool of 3x8tb drives that I would like to have in raid5 (or something similar) for storage (movies, TV shows, and Immich libraries), the OS will have its own drive, and I have a separate SSD that I have been using to store programs, games, yml's for docker, and other such things that get accessed more frequently, but aren't crucial if lost.

I've kinda narrowed it down to either Bazzite or CachyOS.

I've heard that Bazzite can be a little more locked down, which I'm not a fan of, but CachyOS has features I will likely never touch (schedulers, kernels, etc...).

I don't want an upkeep heavy OS. I'm moving away from windows for that reason. Win11 has been a nightmare for me with constant reboots and things not loading up until after I log in. Not to mention driver conflicts and all the other BS that's come with it.

So... What say the hive mind? Is Bazzite going to be too tinker-proof, or is CachyOS just way too much work? Or do I have it all wrong with my perception of both?

Thanks!

Ps: this will be my first full commit to Linux. I've dabbled in the past and am no stranger to CLI... So this will likely be a stepping stone into getting my primary PC onto Linux. Go easy on me lol

New year, new OS for this M1 MacBook Air!

I've been using Asahi Linux (via the flagship Fedora Asahi Remix) for a few weeks now. It's been my everyday laptop and I'm really impressed with how it's held up. Battery life is amazing, and the ARM Linux experience is fine for everyday use.

This video walks through how I installed Fedora Asahi Remix in December 2025, the process might change in the future and if it does, I might revisit it here or in a blog- watch for pinned comments I guess!

Important links:

• Asahi Linux project: https://asahilinux.org/
• Asahi Linux docs: https://asahilinux.org/docs/
• Asahi Linux "supported devices" page: https://asahilinux.org/fedora/#device-support

Links to help support unsponsored videos like these... Patreon and Ko-Fi members get access to my Discord/Matrix server where I hang out:

• Patreon: https://patreon.com/VeronicaExplains
• Ko-Fi: https://ko-fi.com/VeronicaExplains
• Buy a shirt: https://vkc.sh/merch
• Download my music: https://thestopbits.bandcamp.com/

Chapters:
0:00 What is Asahi Linux in the first place?
2:15 Installation caveats
3:27 Actually installing Asahi Linux on real hardware
7:34 About the experience
11:06 Asahi is awesome

#linux #apple #fedora

i really wanna have all of them. long neck tux is very funny

listenonrepeat.com was up for years until last month, when it mysteriously went offline. I haven't found any sites like it. I could just paste in a youtube link and have it play right away, and choose the start and end times for looping, and it had a count for how many times you played the song, as well viewing history (with start & end times saved) so you could easily listen to previous songs.