The Linux Thread - The Autist's OS of Choice

  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
Recently installed Linux 22.3 and I'm super disappointed that the scaling is still fucked. Set both monitors at 125% and half my windows will cone up super tiny, with the mouse shrinking to the same scale.

Games are just as fucked, with the 3 I tested loading up at 30 fps with some wack ass resolution and even when I set it right the field of view is shit.
 
Dr. Geronimo said:
Recently installed Linux 22.3 and I'm super disappointed that the scaling is still fucked. Set both monitors at 125% and half my windows will cone up super tiny, with the mouse shrinking to the same scale.

Games are just as fucked, with the 3 I tested loading up at 30 fps with some wack ass resolution and even when I set it right the field of view is shit.
Click to expand...
I tried fractional scaling when I installed Linux Mint only to be disappointed at how inconsistent it was.

I can work around it somewhat by increasing font sizes, but regardless...
 
Having a weird issue I'm not sure how to solve... I switched from windows to fedora a few months back and it's been pretty smooth, overall happy with it. I've been able to configure and fix everything so far, except this.

When I boot, I get a message that RDSEED32 is broken. I'm on amd cpu/gpu and I found some forums saying amd pushed some drivers or firmware to fix this in december, but I only started getting this issue in the last week or two. I can still boot and login, but it takes MUCH longer than before. But the bigger issue is that half the time I get kicked back to the login screen after 2-3 minutes of using the system, and then get no input from m+kb until I force shut down.

So on boot it's a tossup whether the system will remain usable for the session. I've tried setting a command in GRUB "clearcpuid=rdseed" as described in troubleshooting info online, but it doesn't seem to have an effect. Updated all drivers and kernels as well. Any ideas?
 
Linux mint 22.3, solid update, no unwelcome bugs thus far and even the volume icon getting stuck during media playback had been fixed.

The menu is a take it or leave it, a lot closer to XFCEs whiskermenu due to the inclusion of a user account picture.

Mint 23 I suspect is when the differences I've seen in LMDE will pick up in the mainline.
 
Nickel Silver said:
I tried fractional scaling when I installed Linux Mint only to be disappointed at how inconsistent it was.

I can work around it somewhat by increasing font sizes, but regardless...
Click to expand...
One of the reasons people that use wayland do so (besides it working fine for their other use cases), is because it often handles fractional scaling better than xorg. Which makes some sense. When the compositor, display server (if you want to call it that in the case), and the window manager are all one thing. They will tend to be able to work together in a much smoother way than 2 or 3 separate things. That have to do it. The place where you might run into problems with the application not handling it properly is using applications that are xorg only, because they have to run through xwayland. Although, at this point, it's pretty easy to run wayland only in most cases.

(Physiognamy Czech) said:
When I boot, I get a message that RDSEED32 is broken. I'm on amd cpu/gpu and I found some forums saying amd pushed some drivers or firmware to fix this in december, but I only started getting this issue in the last week or two. I can still boot and login, but it takes MUCH longer than before. But the bigger issue is that half the time I get kicked back to the login screen after 2-3 minutes of using the system, and then get no input from m+kb until I force shut down.
Click to expand...
A quick search. I saw that the problem has to do with the microcoe version. I would either see if you can find a newer version of the amd-ucode (or whatever you need for your specific processor), or try downgrding it to an older version, and check if that works a bit better. I have no idea if you can handle that with just the fedora repos, or if you would need to manually download the microcode. From what I've seen the only "fix" in the actual kernel is this.

The kernel mitigates this by disabling the RDSEED32 feature at the CPUID level, preventing user-space applications from using the vulnerable instruction. This change was implemented in Linux kernel 6.18-rc4 and backported to stable 6.17.8-arch1 and similar distributions. The fix is not a permanent solution but a temporary workaround until a proper microcode update is available
Click to expand...
But from what I'm seeing if you get the mainline linux-firmware. It should have the fix in that microcode. But it hasn't been released in the stable version. So again, I'm not familiar enough with fedora, to know if there is a way to do that without having to manually download it yourself. Like if there is a testing repo or something.

But what I'm seeing about the fix already being in the mainline linux-firmware branch could be wrong. But it's what I would try.
 
I'm surprised a lot of the people here are still willing to use the site. I've seen quite a few people saying they are going to drop "x" program, after they start adding rust. Meanwhile this site is running rust for portions of it. The chat is completely written in rust (as far as I know it's all rust for that), and I wouldn't be surprised if there are smaller portions of the site that have some rust components.
 
Nickel Silver said:
I tried fractional scaling when I installed Linux Mint only to be disappointed at how inconsistent it was.

I can work around it somewhat by increasing font sizes, but regardless...
Click to expand...
Yeah I shouldn't have to do that much work just to get a program to recognize my resolution

Going to try Zorin next and if that doesn't work out I guess I'm locked into Kubuntu
 
prollyanotherlurker said:
I'm surprised a lot of the people here are still willing to use the site. I've seen quite a few people saying they are going to drop "x" program, after they start adding rust. Meanwhile this site is running rust for portions of it. The chat is completely written in rust (as far as I know it's all rust for that), and I wouldn't be surprised if there are smaller portions of the site that have some rust components.
Click to expand...
I was gonna say at least they know that those parts weren't written by a faggot but then I realized Josh wrote them.
 
(Physiognamy Czech) said:
Having a weird issue I'm not sure how to solve... I switched from windows to fedora a few months back and it's been pretty smooth, overall happy with it. I've been able to configure and fix everything so far, except this.

When I boot, I get a message that RDSEED32 is broken. I'm on amd cpu/gpu and I found some forums saying amd pushed some drivers or firmware to fix this in december, but I only started getting this issue in the last week or two. I can still boot and login, but it takes MUCH longer than before. But the bigger issue is that half the time I get kicked back to the login screen after 2-3 minutes of using the system, and then get no input from m+kb until I force shut down.

So on boot it's a tossup whether the system will remain usable for the session. I've tried setting a command in GRUB "clearcpuid=rdseed" as described in troubleshooting info online, but it doesn't seem to have an effect. Updated all drivers and kernels as well. Any ideas?
Click to expand...
Have you updated your BIOS as well?
 
prollyanotherlurker said:
I'm surprised a lot of the people here are still willing to use the site. I've seen quite a few people saying they are going to drop "x" program, after they start adding rust. Meanwhile this site is running rust for portions of it. The chat is completely written in rust (as far as I know it's all rust for that), and I wouldn't be surprised if there are smaller portions of the site that have some rust components.
Click to expand...
I don't use chat because I'm not a homo, which coincidentally filters out all use of rust.
 
prollyanotherlurker said:
I'm surprised a lot of the people here are still willing to use the site. I've seen quite a few people saying they are going to drop "x" program, after they start adding rust. Meanwhile this site is running rust for portions of it. The chat is completely written in rust (as far as I know it's all rust for that), and I wouldn't be surprised if there are smaller portions of the site that have some rust components.
Click to expand...
It really comes down to a simple sort of mathematics; Am I willing to tolerate tranny-coded Rust bullshit in exchange for a given service?



For most things the answer I reach is no. For the farms, which offers me a unique service I cannot find elsewhere, the answer is yes.
 
prollyanotherlurker said:
I'm surprised a lot of the people here are still willing to use the site. I've seen quite a few people saying they are going to drop "x" program, after they start adding rust. Meanwhile this site is running rust for portions of it. The chat is completely written in rust (as far as I know it's all rust for that), and I wouldn't be surprised if there are smaller portions of the site that have some rust components.
Click to expand...
Its not about the language itself, its about the culture that usually makes use of it. KF could be built on FORTAN, as long as its admin is based, its backbone cannot be zogged. Only thing that irks me is the code he's open sourced thus far has (to my knowledge) all been MIT(rash) licensed, hence why its only 80% based. Were it AGPL, it'd be a flat 100%.
 
Ferryman said:
Its not about the language itself, its about the culture that usually makes use of it. KF could be built on FORTAN, as long as its admin is based, its backbone cannot be zogged. Only thing that irks me is the code he's open sourced thus far has (to my knowledge) all been MIT(rash) licensed, hence why its only 80% based. Were it AGPL, it'd be a flat 100%.
Click to expand...
kiwiflare is open source?
 
As I understood it, the point of using Rust was to trigger all the troons and genderspecials who use it.

They invade women's spaces all the time. They've had countless hug boxes that ban or suppress dissenters. But they can't stop you from writing code in "their" language.
 
Baguette Child said:
It really comes down to a simple sort of mathematics; Am I willing to tolerate tranny-coded Rust bullshit in exchange for a given service?
Click to expand...
Ferryman said:
Its not about the language itself, its about the culture that usually makes use of it. KF could be built on FORTAN, as long as its admin is based, its backbone cannot be zogged. Only thing that irks me is the code he's open sourced thus far has (to my knowledge) all been MIT(rash) licensed, hence why its only 80% based. Were it AGPL, it'd be a flat 100%.
Click to expand...
The problem is. These projects didn't just get tranny code when they started adding rust to them. They already did have it. And they've had trannies writing code for them for years. In one way or another.

But people only seem to decide it's time to move to something else when they add rust. As if it makes much of a difference if a tranny wrote the code in rust or they wrote the code in C.

Or are people only against tranny code when it's rust? Lol. Either way you could look at these organizations, and see the trannies were already inside the house. It's nothing new.
hog cranking frog said:
Don't care about the language so much as I do silly rewrites for no reason.
Click to expand...
I agree, it is silly. And in some cases a bad decision. Like for instance, adding it to apt. Because it does hurt the portability of the tool. But at the same time, if I'm a debian user on x86, I still wouldn't have a problem using it just because they added rust to the codebase.

It's just annoying to me that it's pushed so hard and I think it's a dumb decision to make a c project into a mixed codebase project or rewrite it.

and yeah. I also don't like the mit licensing thing. Although it's not something I care about in a way where I'm going to not use software because it's MIT. I don't like seeing projects go from gpl to mit, or some other cuck license though like the bsd ones.
 
prollyanotherlurker said:
and yeah. I also don't like the mit licensing thing. Although it's not something I care about in a way where I'm going to not use software because it's MIT. I don't like seeing projects go from gpl to mit, or some other cuck license though like the bsd ones.
Click to expand...
The bigger issue is the second point, the noncuck > cuck license pipeline. Rewrite-it-in-rust projects are cancerous because they take GPLed code and convert it to corporate-friendly cuck licenses. I can't really see it as being anything other than subversive corporate EEE jewry. People doing RIIR are either useful idiots baited by the push for making rust the "hot new thing" because of memory safety o algo, trannies that get off on subverting things because it is in the troon's very nature to take something and make it ugly, or actual, direct corporate employees doing it as part of their 9-5. People writing Rust stuff from scratch is fine of course, there is nothing wrong with using the language itself. I would have no issue with RIIR if it was mostly GPL/AGPL instead of MITrash.
 
Without trying to get too into the weeds about licenses (because realistically, nobody will change a pre-established point of view), I would like to mention that there are two distinct and in my opinion valid reasons for using permissive/cuck licenses (MIT, BSD, ISC2, Public domain etc).

One, some people don't ideologically like the restrictions the GPL comes with. I would say most of the older developers that refuse to use GPL fall in this category.

Two, there is a pragmatic case to be made about a middle ground in which the best solution for the average person that uses a (usually corporate) software is to keep it under a cuck license. This is because if you do something correctly and securely, and permit companies to use that code without jumping through GPL-sized hoops, then the end product is more secure.

That is all of course without dismissing the GPL arguments either, I would generally say it just depends on personal beliefs at the end of the day. It's probably best if there's a balance between the two, because if either side gets too much power then it will probably lead to it hurting the OSS community in general.
 
You must log in or register to reply here.
Back
Top Bottom