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
Still no real replacement for x11vnc. I tried krfb on plasma with wayland and it simply did not work. krdc just fails silently and tigervnc says the screen framebuffer is null size.

Someone tell me I'm doing something wrong. That I'm missing something. I don't know how Wayland apologists can keep insisting how it's "ready" despite lacking basic functionality after a million years.
 

1765269669199.png

1765269638032.png

HDR bros, we're coming home.
 
Last edited:
Thoughts on NixOS?
Too much effort, not enough gain. One of the reasons I haven't used guix, is because it's based on the same concepts. And it's just putting a ton of complication on something I find much simpler with a traditional package manager.

If you are doing some kind of development that needs to do reproducible builds, in different containerized environments. It's probably great, and might save you a lot of effort. If you want to use your computer like a normal person it's going to eventually make doing something trivial into a task that takes hours, if not days to work out.
 
So what can we do. We can likely do a LD_PRELOAD and make it wait so that things execute in order. LD_PRELOAD allows custom libarys to be loaded before anyhing else. An example would be "LD_PRELOAD=./libshmemfix.so /philips/apps/philips"
Normal Computer user: OK guys turns out I need to get GCC 4.2. Oh there is no mipsel binary online? I guess Ill have to build it. im sure that will be easy.
2 Weeks later
Myfeelingsrightnow.png

I never thought compiling a old version of GCC would be this fucking annoying .
So lets go over the problem shall we.

The problem is that I need to build GCC 4.2 in order to compile a LD_PRELOAD I made.

Thats it... sounds easy right...

Ive spent the last day trying this shit. Eventually I learned that compiling even on a container in modern Debian would be impossible. Even after finding old builds of gcc to work with.
So we need to get a container of debian Lenny a ancient debian version.
Keep in mind this is after over 5 HOURS of attempting to compile.
Alright so now that we got Debian Lenny in a container lets build GCC 4.2. Its finally over
Just so you know I have already spent 5 hours previously getting to the this point before making a entirely new container image.
LETS DO THIS...
1765228562485.png
Remember when I said I just need to compile GCC. That was a LIE. I also need to compile mipsel assembler and linker.
Alright so now that weve done that we can install it.
1765229699222.png
WHAT!!!!

OK I FINALLY FIXED THAT FINALLY WE CAN COMPILE IT
1765233276214.png
OK OK OK THIS IS THE LAST TIME I CAN FINALLY SAY WE FIXED IT
1765234173295.png
MOTHERFUCKER!!!!
Alright alright this is the final time... This time its going to work
1765243868501.png
Ok we finally fixed that. We can compile now Its finally over oh my gosh its over FINALLY I CAN COMPILE THIS SHIT YESSSSSSSSSSSSSSSSSSSS
1765287425314.png
1765287468088.png
OK OK OK OK OK I HAVE FINALLY FIXED THIS ONE OK. WE CAN FINALLY COMPILE IT
1765287820365.png
No we cant. No we cant.

Alright thats fine. Thats fine. Im fine. I do not want to blow up a orphange. Everything is fine I am happy.

Ok I fixed it I can say with 100000% certainty that we can compile this now
1765287965923.png
1765288002283.png


Alright...... I think I can say this is finally it.... FINALLY its over.... after all this pain and suffering.... its over. We won. Its finished.
Lets run the final make command.

1765290177971-png.8267111

Thats ok.... Thats Ok.... Thats ok....
Ok this time its finally done. everything is defined were finally back oh my gosh
1765291978053.png
Screenshot From 2025-12-09 08-46-40.png

You want to know the worst part that just happened.

My container crashed. And because this is not a fully set up podman I have to reinstall ALL MY PACKAGES VIA APT AND MOVE MY MIPSEL BINUTILS ASSEMBLER BACK.
1765291978059.png
So after ALL OF THAT me reinstalling ALL THE PACKAGES THAT I NEED, reinstalling my mips linker back into the correct folder and also installing gmp back. We can continue.
After a few more of the same errors I figured out what was happening. The wrapper was messing up and failing to figure out when to use the normal x86 as and the mipsel-linux-gnu as command. So for example when it should had been using the mipsel version of as provided by binutils it was using the x86 version.... After manually telling it to use the mipsel version... Well you can already guess what im about to fucking tell you happened
1765291978172.png

Alright so after that we have a new problem.
1765291978179.png
I did that. I did EXACTLY THAT. multiple times and it keeps telling me that things changed even though they litterally DID NOT CHANGE AT FUCKING ALL...

I finally managed to fix it and we can FINALLY AFTER ALL OF THIS COMPILE1765291978203.png
Screenshot From 2025-12-09 08-46-40.png

The worst part is that this was the furthest we had gotten it compiled like a SHIT TON OF FILES.
After this I finally FINALLY GOT IT COMPILED SHIT I GOT IT WORKING I CANT BELIEVE IT.

Just so you know I went through ALOT more problems that I failed to mention here, this is consiserded a CONDENSED version of everything I fucking went through.

And now do you want to know the worst part. What all that pain and suffering to get that version of GCC working. It was so I could compile this
1765292395226.png
All of this for 26 lines......

What ive learned from all of this is that just because you provide the source code for something does NOT mean its archived or preserved. older versions of GGC are a fucking NIGHTMARE to compile and soon enough they will become lost to time without those dependiences and systems. Its basically a fossil not a living artifact.

Anyways we are finally able to compile my LD_PRELOAD.
1765293825076.png
Lets put the file into our rootfs folder and then rebuild our newrootfs image(Yes everytime I place a new file I have to rebuild the rootfs)
1765293865734.png
and lets start our qemu VM and try this now
1765293925948.png

and now lets run the commands I always have to run after every startup

Code:
busybox-mipsel mount -t sysfs sysfs /sys
busybox-mipsel mdev -s
busybox-mipsel mkdir /mnt/jffs0/
busybox-mipsel mkdir /mnt/jffs1/
busybox-mipsel  mount -t ext2 /dev/sdb /mnt/jffs0
busybox-mipsel mount -t ext2 /dev/sdc /mnt/jffs1
busybox-mipsel mount -t proc proc /proc
busybox-mipsel insmod /shmemipc_drv.ko
busybox-mipsel insmod /mmappokes.ko
busybox-mipsel mdev -s

and now its time to see if it worked
 

Attachments

  • 1765291764089.png
    1765291764089.png
    90 KB · Views: 10
  • 1765291763992.png
    1765291763992.png
    55.3 KB · Views: 3
  • 1765291764095.png
    1765291764095.png
    14.4 KB · Views: 3
  • 1765291763984.png
    1765291763984.png
    56.6 KB · Views: 3
  • 1765291574692.png
    1765291574692.png
    244 KB · Views: 4
  • 1765291574791.png
    1765291574791.png
    90 KB · Views: 5
  • 1765291574699.png
    1765291574699.png
    56.6 KB · Views: 5
  • 1765291574798.png
    1765291574798.png
    14.4 KB · Views: 3
  • 1765291417901.png
    1765291417901.png
    244 KB · Views: 5
  • 1765291417979.png
    1765291417979.png
    90 KB · Views: 3
  • 1765291763978.png
    1765291763978.png
    244 KB · Views: 3
  • 1765291829860.png
    1765291829860.png
    14.4 KB · Views: 6
  • 1765291830015.png
    1765291830015.png
    64.6 KB · Views: 5
  • 1765291829854.png
    1765291829854.png
    90 KB · Views: 3
  • 1765291829956.png
    1765291829956.png
    248.8 KB · Views: 4
  • 1765291829963.png
    1765291829963.png
    59.4 KB · Views: 3
  • 1765291417889.png
    1765291417889.png
    15.4 KB · Views: 6
  • 1765290838614.png
    1765290838614.png
    77.1 KB · Views: 5
  • 1765290838620.png
    1765290838620.png
    15.4 KB · Views: 4
  • 1765287376385.png
    1765287376385.png
    9.4 KB · Views: 4
  • 1765229671194.png
    1765229671194.png
    11.6 KB · Views: 3
  • 1765229668662.png
    1765229668662.png
    11.6 KB · Views: 3
  • 1765228467732.png
    1765228467732.png
    8.8 KB · Views: 3
  • 1765287397251.png
    1765287397251.png
    73.9 KB · Views: 3
  • 1765290217486.png
    1765290217486.png
    77.1 KB · Views: 3
  • 1765290177971.png
    1765290177971.png
    32.1 KB · Views: 413
  • 1765290177978.png
    1765290177978.png
    77.1 KB · Views: 2
  • 1765289529692.png
    1765289529692.png
    32.1 KB · Views: 3
  • 1765289520345.png
    1765289520345.png
    32.1 KB · Views: 8
  • 1765288143543.png
    1765288143543.png
    32.1 KB · Views: 26
Last edited:
I'm an Ubuntu user since ~2016. I'm decently competent but not much.

I also use Ubuntu server for a command line machine that runs constantly.

I'm getting spooked by Canonical and other weird Wayland and forced Rust stuff happening with the distro and I'm strongly considering moving off. I won't pretend to know exactly what's going on there, but I'm happy to have a nebulus excuse to push me to move off of troon software.

What sort of distros should I look into that has similar JustWorks and hardware support as Ubuntu/Debian but is unlikely to have these kinds of troon problems any time soon?
 
Just so you know I went through ALOT more problems that I failed to mention here, this is consiserded a CONDENSED version of everything I fucking went through.
This is "toolkit development" which is the crucial first step to developing one's own Linux distro. You gotta be pretty light skinned to make it this far.
 
I'm an Ubuntu user since ~2016. I'm decently competent but not much.

I also use Ubuntu server for a command line machine that runs constantly.

I'm getting spooked by Canonical and other weird Wayland and forced Rust stuff happening with the distro and I'm strongly considering moving off. I won't pretend to know exactly what's going on there, but I'm happy to have a nebulus excuse to push me to move off of troon software.

What sort of distros should I look into that has similar JustWorks and hardware support as Ubuntu/Debian but is unlikely to have these kinds of troon problems any time soon?
Probably Debian? My server was originally going to be a Debian server but at the time the Intel Arc A310 just came out and Debian 12 didn't have drivers for it and I wasn't familiar enough with installing newer kernels to try. If Ubuntu 26.04 is really fucked up I'll probably switch back to Debian, most important crap is in docker containers so it should just take a weekend or two to get set up again. Off hand I know NPM will be cranky because it stores the certificates in /etc/letsencrypt on the host and I have to look up how to migrate that over so NPM doesn't just crash on start.
 
Probably Debian? My server was originally going to be a Debian server but at the time the Intel Arc A310 just came out and Debian 12 didn't have drivers for it and I wasn't familiar enough with installing newer kernels to try. If Ubuntu 26.04 is really fucked up I'll probably switch back to Debian, most important crap is in docker containers so it should just take a weekend or two to get set up again. Off hand I know NPM will be cranky because it stores the certificates in /etc/letsencrypt on the host and I have to look up how to migrate that over so NPM doesn't just crash on start.
Does Debian use X11. That would be the easiest possible migration for me
 
Thoughts on NixOS?
I couldn't find it trustworthy anymore and left because the founder cucked to trannies. Prior to that, I used it for over two years and thought it was alright. Personally, after a month or two every non-declarative OS install just feels... bloated and trashed? Nix scratched that itch but most of what you'd learn won't be applicable elsewhere since it's non-standard abstractions on abstractions

I keep hearing Guix and Ansible are better so I've been meaning to look into those
 
Last edited:
Normal Computer user: OK guys turns out I need to get GCC 4.2. Oh there is no mipsel binary online? I guess Ill have to build it. im sure that will be easy.
As fun as containers are, I have to say I think I would have just gone and done:
In a VM. Obviously not sure it would have been any easier. Although you probably could have just slowly run Debian mipsel in qemu like you do for the TV OS and compiled there.

One suggestion when playing with containers. Each time you get to a "working" point. Go and update your Containerfile/Dockerfile and rebuild the container from that point. That way all the dependencies are baked in and you don't get nearly as annoyed when it blows up and you have to restart it anyway.
 
When I say the jumper I mean the one on the board, it says "3.3v" "5v" and you need to make sure it's set correctly. The wires should be connected before connecting the USB side of the adapter so there's no chance of shorting live wires. Obviously the TV should also be off.
Jumper? where the hell did they say anything about a jumper. I saw your message yesterday and was wondering that but like did not want to seem stupid.
I mean its only 3.3V and if there is a ground already why do we need a jumper. I thought we could just use gpio cables right. I mean im not a electrical engineer and like I could be saying the equivalent of "Yeah that fork seems good enough to put in the socket"


WAIT oh you mean board as in the usb UART circut., OOOH
 
All CMOS parts will be <2.5V by the end of the decade
 
Does Debian use X11. That would be the easiest possible migration for me
debian uses whatever you want. It's not exactly a just works distro like ubuntu or mint. So you decide what desktop you are going to run on it. You can pick something niggerlicious like kde or gnome. Or you can pick something less gay like xfce cinnamon, or mate.

The "just werks" distros will always have a problem. By their nature, they are filled with a bunch of software, that was chosen for you. Which is fine if you like everything they pick. But if it's filled with a ton of stuff you don't want, it can quickly become more annoying running one of those distros, than if you started from somewhere more minimal and installed the things you wanted. Or better yet, if something you happen to be using decided to go in a direction you don't like, you aren't tied to that software, you can easily completely remove it, and use something else.
 
debian uses whatever you want. It's not exactly a just works distro like ubuntu or mint. So you decide what desktop you are going to run on it. You can pick something niggerlicious like kde or gnome. Or you can pick something less gay like xfce cinnamon, or mate.

The "just werks" distros will always have a problem. By their nature, they are filled with a bunch of software, that was chosen for you. Which is fine if you like everything they pick. But if it's filled with a ton of stuff you don't want, it can quickly become more annoying running one of those distros, than if you started from somewhere more minimal and installed the things you wanted. Or better yet, if something you happen to be using decided to go in a direction you don't like, you aren't tied to that software, you can easily completely remove it, and use something else.
Thanks for the responses!

I've noticed that it's an unpopular opinion, but I like GNOME desktop. It's frozen up on me a few times though.
I do like Ubuntu's default software (as of 2020 LTS) but I'm starting to consider that this may soon change and I'll get shafted again just like with Win 10.
I'm not the type who uses Linux to rice up my machine, I just want it to do what I want it to.

Do you have a suggestion for a Debian getting started guide that you agree with? I'd like a place to get started with reading up in it.
 
Bought a new laptop, somehow never considered that hidpi would be a problem for XFCE.

Begrudgingly using KDE via KDE Neon to cover for that, wanting to make it easier to remap the retarded copilot key, and hardware support. Plasma shell sure does like to crash a lot...
 
Thanks for the responses!

I've noticed that it's an unpopular opinion, but I like GNOME desktop. It's frozen up on me a few times though.
I do like Ubuntu's default software (as of 2020 LTS) but I'm starting to consider that this may soon change and I'll get shafted again just like with Win 10.
I'm not the type who uses Linux to rice up my machine, I just want it to do what I want it to.

Do you have a suggestion for a Debian getting started guide that you agree with? I'd like a place to get started with reading up in it.
I'd have to take a look at what's available again. Just some general advice. Debian has a few different installers available on their download page from what I remember. So look at what the different ones offer. Some are more advanced, some are less so.

Installing debian itself isn't too complicated, since it does use an installer for all the options. Although it might not be a bad idea to have something nearby to do a websearch about something if you don't fully understand what a certain part is asking you to do.

I almost want to say they have a calemares installer available for Debian, but I can't remember if they do for sure. I think they do its just hidden somewhere on their downloads page. If you use that it will be the simplest of everything.
 
Back
Top Bottom