Hey, I’m also ArsonButCute@lemmy.dbzer0.com

Don’t DM me without permission please.

  • 8 Posts
  • 36 Comments
Joined 8 months ago
cake
Cake day: January 8th, 2026

help-circle
  • There’s way too much info here to parse.

    Can we get the output of:
    lspci | grep Network && lspci | grep Wireless && lspci | grep Bluetooth && lsusb | grep Bluetooth && lsusb | grep Wireless && rfkill
    This is the first step to diagnosing issues with your wireless radios such as wifi and bluetooth. This command (you can copy and paste it into a terminal, this command is totally safe, but normally you shouldn’t copy commands you don’t understand) will probe your PCI devices and USB devices to find anything matching the words “Network”, “Wireless”, or “Bluetooth”, then it will run the “rfkill” command, which will tell us if these devices are “blocked” or “unblocked”. If they are “blocked”, you will need to “unblock” them.

    To “unblock” your devices, using the number under “ID” as reported by the rfkill command instead of %ID%, run the following (this one cannot be copy-pasted, you must type it manually to ensure the correct command is entered):
    sudo rfkill unblock %ID%

    If this doesn’t help:
    You may have updated everything except your ‘linux-headers’. Headers are special files that teach the kernel how to talk to userspace programs. Sometimes they’re important for your drivers to work correctly. It would be worth running dpkg --list | grep linux-headers and seeing that you have an option that matches with the version supplied by uname -r. If you lack a matching header, manually install it via the apt package manager from the command line. It is as simple as sudo apt install linux-headers

    Also, forgive my intrusion on your personal choices, but I would strongly recommend using Chromium or Ungoogled-Chromium unless you have a use-case for real full-fat Google Chrome. Google Chrome is an egregious piece of malware under the definition supplied by the Free Software Foundation.




  • I used plasma for nearly a decade and only recently switched off of it because I wanted to try something different. I moved over to GNOME for a bit, and while it was nice, I kept running into issues with customization, specifically Gnome Extensions are a pain in my ass.

    I moved to cosmic a few weeks ago on my desktop rig, which is my server, but is also for gaming. I don’t want this one to feel like an “office” machine, and cosmic does a great job of feeling like just a computer. On my laptop, which I use for development, I prefer a stable “no-bullshit” interface, as such I use MATE there. MATE, if you’re unfamiliar, is the successor to Gnome2. It is a more traditional desktop experience, using familiar idioms. Customization is limited (out of box) compared to the more major DE’s like KDE and GNOME













  • If I may make a recommendation for gaming on that machine:

    Have a windows install on a second partition/drive.

    Windows’ graphics drivers are generally better are reallocating system ram to be used as vram, IME the Linux drivers generally are unwilling to allocate more than is absolutely necessary to run a desktop and a few gui apps. This is one of the biggest complaints for example with Nvidia’s *nix drivers, which don’t allow ram sharing and only use what’s dedicated to the video card in hardware. Of course you’re on a team blue rig, my experience won’t transfer there but I assume it’s likely a similar issue.



  • Hi Saithe, I’ve cloned your repo and am trying interact with it but I’m not getting any sort of feedback from it.

    Maybe I’m wildly misunderstanding how this works.

    I’ve added args from hivemm-design.txt such as “m0” or “q1” or “x”, both passing them directly on line 5 of dbglua and by passing them as args when calling dbglua. In all cases, dbglua returns ‘ok’ and no changes occur to the game state.

    Attempting to pass any arguments by any method using the “–release” flag when running and using clientlua instead of dbglua results in the app panicking in lexer_system.

    I’m not the greatest with rust or I’d try to debug myself. I can read it, I can’t write it though.

    If you’d like I can gather some logs and submit them on your issue tracker @ git.gay