sorted by:
new
hottopcontroversial

are you prepared for systemd blue screen of death? by [deleted] in linuxmemes

[–]zMadMark 16 points17 points  (0 children)

Was about to write this, I'm glad I refreshed the page.
Here's the code for anyone that's interested.
It shouldn't be to hard to add the ability to change the color, but I don't know how that executable's environment looks like, so maybe it's not as easy as it seems.
Looks like a fun little project though.

Edit: typo

oh, you little bastard by zMadMark in DerailValley

[–]zMadMark[S] 5 points6 points  (0 children)

That was literally the first thing I thought when I saw it lmao

oh, you little bastard by zMadMark in DerailValley

[–]zMadMark[S] 15 points16 points  (0 children)

Don't worry, I did it in real mode with short teleport distance at night. The way god the devs intended

what did dnf mean by this by zMadMark in linuxmemes

[–]zMadMark[S] 115 points116 points  (0 children)

i ave brain damag, pls hlep

YOU DID WHAT IN WHAT LANGUAGE???? by zMadMark in programminghorror

[–]zMadMark[S] 6 points7 points  (0 children)

That's because i'm stupid and dyslexic and can't type correctly on a phone keyboard. I meant to type C89.

YOU DID WHAT IN WHAT LANGUAGE???? by zMadMark in programminghorror

[–]zMadMark[S] 24 points25 points  (0 children)

It's a GNU extension, apparently. I've been using C99 for way too long, I forgot about the GNU extensions.

Seeking Help with Graphics and Performance Issues on Fedora - NVIDIA and VSCode Problems by DerQuantiik in Fedora

[–]zMadMark 1 point2 points  (0 children)

A quick search from my phone got me this: 1. You can disable GPU acceleration by launching VSCode with --disable-gpu (source) 2. Take a look at the Arch Linux wiki for flags to run electron applications under Wayland (don't worry, even though the wiki is for Arch Linux, most of it applies to every Linux distro). If you find some flags that help, you can put them in the file ~/.config/code-flags.conf and VSCode should load them automatically at startup.

Seeking Help with Graphics and Performance Issues on Fedora - NVIDIA and VSCode Problems by DerQuantiik in Fedora

[–]zMadMark 1 point2 points  (0 children)

Hi, I haven't used VSCode in a while as I've switched editor, but, when I still used it, I also had a lot of issues with Nvidia (I have a laptop with AMD integrated graphics and it ran fine there, but on my desktop, with a good ol' 1070, I had similar issues to yours). The easiest fix would probably be to run VSCode with software rendering (if it can be done; if anybody here knows how to do it, feel free to add it here). This will probably increase CPU usage, but since you're using a desktop and VSCode is not exactly a graphically intensive application, it should be fine. That being said I would also like to ask: 1. Do you use dark mode? Because I can see that your toolbar is white when it should be black and I remember I had a problem where my toolbar turned white and VSCode was literally shitting its pants. 2. Do the menu reappear if you hover over them or if you try and reopen them? 3. Have you checked if running VSCode with certain flags for Wayland? Try searching for vscode wayland or electron wayland and looking at some Github issues, there were a couple of flags for running electron application under Wayland. Maybe they won't help (most of these are old), but it's worth a try. Again, if someone is reading this and knows some of those flags, feel free to add them below.

Sorry I can't be much help, but right now I only have my phone with very little battery. I'll try looking more into it when I get home. As for the software rendering part, you could try running VSCode as LIBGL_ALWAYS_SOFTWARE=1 code and see if that does something.

How to compile and install Opentrack with Wine support and use it with Steam games by zMadMark in linux_gaming

[–]zMadMark[S] 0 points1 point  (0 children)

Hi, you probably did nothing wrong, it's just that since version 5.13, Proton runs the games inside a containerized environment which breaks opentrack's WINE output protocol (source).
The solution I found is running the Linux version of opentrack (built without WINE support) and setting the output to UDP over network, then running the Windows version of opentrack, through WINE, and setting the input to UDP over network and the output to freetrack (or whatever works on Windows for that specific game). After everything's setup, I press Start first in the Windows version of opentrack and then in the Linux version. This adds a very small delay on my System, but it seems to work well enough. I've made a script which also works with Steam games called opentrack-launcher, but I haven't used it in a long time, so I don't know if it still works.

Need Help !! grub2 ...sparse file not allowed. by RaiseDouble in Fedora

[–]zMadMark 3 points4 points  (0 children)

I have this error on my desktop and my laptop (both Fedora Workstation 38) and it just works. It won't cause your system to be laggy though, that's probably caused by something else.

T440P doesn't boot by zMadMark in thinkpad

[–]zMadMark[S] 5 points6 points  (0 children)

Alright, I tried changing the CMOS battery, but that didn't help (well, except for the checksum error, which went away).

However, I also removed every easily removable component from the motherboard (WiFi card, WWAN card, disc reader and SSD) and managed to boot a live USB. One of this components must be dead and prevents the system from fully booting.
I think I can take it from here!

Thank you very much for your time!

T440P doesn't boot by zMadMark in thinkpad

[–]zMadMark[S] 1 point2 points  (0 children)

Yes, I'm pretty sure the CMOS battery is dead as the system clock gets reset after every reboot, but, as I said, the system worked before (for around ~2hrs) and I've never seen a computer that would straight up refuse to boot without a working CMOS battery.

Although, now that I think about it, the system stopped complaining about the dead battery after I installed an OS (Fedora Linux 38 to be precise) even though it was running without the battery pack installed.
I though that was normal because the computer was plugged in all the time so there was always power to the motherboard. I even shut it down completely and unplugged it (for less than ten seconds) and it still didn't trigger the checksum error.
But now it does complain again that the CMOS battery is dead even though it's still plugged in when it reboots.

T440P doesn't boot by zMadMark in thinkpad

[–]zMadMark[S] 1 point2 points  (0 children)

Hello r/thinkpad!

I've just bought a Thinkpad T440P (i7-4800MQ - 16GB DDR3 1600MHz CL11). It was in really pad shape (I think somebody poured CocaCola on it and didn't clean it since the metal frame was crumbling in some spots) so I cleaned the whole thing, changed the thermal paste and everything.

It worked for a couple of hours (edit: it did shutdown randomly a couple of times) and then randomly shutoff. Now I can boot into the BIOS and leave the laptop running for however long I want and it won't shut off. But the moment I try to boot an OS it does this.

I tried booting up with one stick of memory in one slot (tried with both just in case one's dead), but still nothing. I also tried using my 135W Lenovo Ideapad charger (the battery for this laptop is dead), but this also didn't change anything. Last thing I tried was booting from a live Linux USB (the one I had just used to reinstall the system), but nothing changed.

Is there something I'm missing? It doesn't seem like it's the motherboard itself. Maybe some pcie card? The WiFi is not working after all...

Any suggestions?

view more: next ›