I like women, femboys and girl cock.

  • 2 Posts
  • 35 Comments
Joined 1 year ago
cake
Cake day: September 25th, 2023

help-circle








  • In reality, only some Pentium 1 compatible motherboards can support enough ram for you to actually run Linux on a Pentium 1. Even if you don’t run into ram problems, you’ll run into bios related problems. I would suggest anyone trying this in 2024 to not even attempt it unless you can get a socket 7, and preferably a later socket 7 motherboard at that. The closest thing I can come up with to a reason not to drop support for 486 (the cpu before the Pentium 1) is that a 486 is a lot more possible to put on a custom pcb than a Pentium 1. Some of the more basic arm cpus aren’t even as powerful as an upper tier 486 (but better arm cpus aren’t that hard for hobbyists to get). Anyone die-hard enough to want to try to run Linux on a fully custom made computer like that would have better results using an arm or risc-V chip instead.

    I am curious why they’re dropping support for 486 but not Pentium 1, pentium 2 and anything not capable of SSE1 or later. mmx isn’t even that good but I guess gcc does technically support it.

    I wonder if they’re going to drop 486 support in gcc as well. It can still compile for 386. You have to seriously strip down the kernel to run Linux on anything that old. Maybe 486 users (all 2 of them) should switch to Temple OS.









  • I have all those settings enabled. The solution does not lie in the ui buttons. I’ve beat that horse dead. It always asks for a password and always shows that stupid fucking reconnect window that someone has to click. It’s absolutely maddening. I might have to make a system mouse clicker bot for this because there might really be no other way. I don’t know how to do that but considering how much time I’ve wasted trying to find any solution, it’s just another attempt.

    Too bad there’s not a one-time “reconnect now” command that can be attached to a script. And no, disabling the network interface and re enabling it via automated command line scripts doesn’t make it reconnect.


  • How can I make my Debian pc always stay connected to the wifi? Even if it disconnects for some reason, it needs to reconnect as soon as it can without throwing any password prompts or requiring any human intervention whatsoever. Having to click a “connect” button first counts as human intervention.

    Bering trying to figure this one out for years, don’t expect a working answer but you miss 100% of the shots you don’t take.