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
View attachment 8442814
Bootloader has been FULLY implemented to stand on its knees.
Current thing its doing? Waiting for the IR remote to register a POWER button being pressed on a remote to then transition to starting the vmlinux and then move forward. Yes its gotten THAT far.
View attachment 8442847
Successfully mounted the NAND. Removed OOB bytes to make it run and then ran it from ram while keeping a FULL copy with OOB and wrote registers to read there whenever it wanted to offically read itself. and then started EXECUTION at everything from ram. Transitioning to the software.

It found what it was looking for and is able to run. Next im going to be making a REMOTE to work in qemu. If anyone wants to see the binaries to try out themselves with a NAND dump message me. If you want to see how it works. TRACKING DOWN these nand dumps was a pain.

One of the most obscure hardware platforms ever to be sold. Undocumented and lost to time. FOUND and reverse engineered. By someone who did not even know what a VMLINUX was 3 months ago or what a BUS was. AND got it running in QEMU.
This is by far the worst explanation in this series
Current boot process is this
  1. Register PCI registers. These are custom coded implementation of intercepting and responding when it attempts to READ a register. These control IMPORTANT stuff but not as important as the other one
  2. Register PCIXIO registers. These are custom coded implementation of intercepting and responding when it attempts to READ a register in this zone that belongs to PCIXIO, these mostly control the NAND and how the bootloader/linux/whatever is ran communicates with it.
  3. Register the UART for it.
  4. Register the KSEG for the pcixio/NAND. these are just a FASTER way to access things that the system software on this TV uses sometimes.
  5. All these HAVE to be designed accounting for WHAT the software wants, We can't change it only design it around the hardware and what would happen on a REAL machine
  6. Finally we can start SETTING UP everything by running instructions in the machine. We need to do a FEW things BEFORE we pass things to the TVS bootloader and have it run. It expects a few things. This is why I coded a "PREbootloader"
  7. start in PREBOOTLOADER mode, this is MY setup that sets everything up for it to well CONTINUE to the ACTUAL SONY tv bootloader
  8. TAKE THE PFLASH. take all its bytes and REMOVE the OOB bytes so we can just get the PURE instructions.
  9. Move that into ram
  10. then after that DO THE SAME THING BUT without removing the OOB bytes. We are not going to be executing instructions here this is just where the NORMAL NAND is suppose to go that the TV accesses. Yes the bootloader is stored in the NAND and its reading itself, however the bootloader is being executed in RAM where the OOB bytes are removed and where it handles stuff using the other MAIN copy as a way to access things.
  11. FINALLY start at ram starting the First stage Sony bootloader. executing the FIRST tv instructions.

Any confusion you have from this is my fault as a explainer rather than your fault as a reader. Take that as note.

Now normally the BOOTLOADER is not the FIRST thing that happens rather there is a separate chip that acts as a BIOS(not a fancy menu one just one that sets everything up) and THEN jumps to the bootloader.

Now because we ALREADY set everything up this is USELESS in our case but ill reverse engineer it just for curiosity.

1768780021939.png
Its stored on a EPPROM that get this. Is not mips assembly. Ill give you three guesses what it is because not even I KNEW.. Remember 2009-2010 tv one of the VERY LAST non smart tvs ever produced.

Its 8051 assembly for the 8051 like PROCESSOR. from the EXACT year of 1980.

Yeah bet you did not guess that
But man on a kiwi site about farms. I thought that this TV was MIPS? Why is the EPPROM and bios using code for a processor from 1980?
Very good question. Its because there is a SECOND processor that does the operations and sets everything up and THEN runs the MAIN BIG BOY mips PNX8543 processor.

It appears to start here
1768780316165.png
SUPRISNGLY enough this is NOT written in hand assembly but rather this code is 100% made by a C like compiler. I can tell by the way the functions are non humanly structured that this is NOT written by man.

1768780369540.png
1768780662062.png
OK so do not ask me to explain this but ill give my best GUESS
Its most likely CLEARING everything for execution, setting the 8501s processor values to nothing and then MOVING the contents of FLASH into ram by reading the MAIN area much like what WERE doing in QEMU...(Chatgpt ALSO appears to agree with my explanation and i made sure NOT to tell it what I think before asking)
1768780782337.png
Hmm. the 8502 assembly code is apparently NEWER than the vmlinux AND is NEWER than the bootloader? intresting.g
1768780864712-png.8443022

Intresting these are NEVER referenced or called... Maybe there unused or maybe the bootloader READS The epprom to use it.
SO WAIT. why would these be here if under normal execution from the start it NEVER reaches this?
WAIT is there a ENTIRE second program in here? Like a normal bios and then a OTHER program within it?
That would.... explain a lot acutally.
(EDIT NO)

SO wait if this is a STANDBY program? Why is the BOOTLOADER waiting for a power on button? Wouldn't that be handled by well the program labeled STANDBY PROGRAM? Well rather my theory is that the 8051 SETS up the PNX-8543 mips cpu and the CPU goes into bootloader mode waiting for a RAM address to be changed.

Than the 8051 processor HANDLES when the remote is pressed and CHANGES a value in ram when it gets pushed. Allowing it to run seperately not not have the Mips CPU scan remote buttons after EVERY instruction.

This aligns with the bootloader just WAITING there doing a timer interrupt waiting 1ms every time in a loop

1768782526171.png
1768782545709.png
Anyways lets view more in this EPPROM
It also appears to run alongside the MIPS cpu as we established but also it checks POWER issues and can shut off the TV in the event of a POWER issue

1768782868299.png
If your interested in this and want view it yourself go ahead ill send you the files msg me.
 

Attachments

  • 1768779388136.png
    1768779388136.png
    64.3 KB · Views: 13
  • 1768780864712.png
    1768780864712.png
    86.9 KB · Views: 635
Last edited:
You have the worst luck with hardware than anyone else in this thread and that's not to discredit your struggles, genuinely sucks, sometimes the hardware simply wasn't meant to be. I don't have anything remotely remarkable just a cheap mini pc and a cheap ass single monitor set up. Hopefully you can find a good middle ground in all this.
Not giving up yet. I got this computer specifically to run linux. I'm going to run Kubuntu one more time. It ran well from what I remembered, but I really enjoy Cinnamon's design. If Kubuntu shits itself or something then I'll go Bazzite although I really don't want to go to arch since Debian gets more mainstream support.
 
Not giving up yet. I got this computer specifically to run linux. I'm going to run Kubuntu one more time. It ran well from what I remembered, but I really enjoy Cinnamon's design. If Kubuntu shits itself or something then I'll go Bazzite although I really don't want to go to arch since Debian gets more mainstream support.

Debian Sid is a bit more sane than Arch in ways.
 
I'm nearing 40 with shitty eyes and using a 3k widescreen monitor at 100% scaling with no problem. Thanks for making me feel better I guess
That's the craziest thing to me. I've always had good eyesight. Never needed glasses. And Idk 1080 looks good to me.
Bootloader has been FULLY implemented to stand on its knees.
Dear feeder says give up on doing all this work yourself and use ai for it goyim.

Debian Sid is a bit more sane than Arch in ways.
I just did a screenshot with an ai summary because I don't feel like outlining the big differences. For myself the thing I like about arch is the changes from upstream are very minimal. When I've tried using debian. It was one of the biggest annoyances for me. Debian is from my perspective very opinionated way of doing things got in the way of how I wanted to do things And that made using it annoying.

1768804936381.png

A lot of people probably won't care or notice that. And the people that do likely will only notice for similar reasons that I did.
 
I'm curious friends: am I the only one who has had consistent issues with systemd since its introduction?

I've been using Slackware on and off for over 20 years and to date, I have never had one lock up/hang during boot-up or shutdown - but every time I've trialed a distro for a few months using systemd (CentOS, X/ubuntu, Fedora, Debian), I always end up having to hold the power button to shut down and reboot.

I don't tinker much, and I never really subscribed to the systemd hate train, but my eyes don't deceive me. Slackware never has failed me, but all the other "modern" distributions have in some way.
Maybe it's my aging ape brain, but I also couldn't make any fucking sense of systemd's documentation.
 
I've been using Slackware on and off for over 20 years and to date, I have never had one lock up/hang during boot-up or shutdown - but every time I've trialed a distro for a few months using systemd (CentOS, X/ubuntu, Fedora, Debian), I always end up having to hold the power button to shut down and reboot.
Systemd has some very bizarre ways of dealing with, for example, encrypted home directories, that always seem to fail in annoying ways. I'm skeptical that such things add any real security- certainly not enough to justify leaving a system powered up where pigs could get a hold of it.
 
Systemd has some very bizarre ways of dealing with, for example, encrypted home directories, that always seem to fail in annoying ways. I'm skeptical that such things add any real security- certainly not enough to justify leaving a system powered up where pigs could get a hold of it.
Maybe that's it? I've always run full LUKS/LVM (swap, home, root, var). I can't remember specifically where it would shit out but it was intermittent. I admit that the fact it happened when I'm running default made me just walk away and revert back to Slackware. Couldn't be fucked wrestling with it.

re: encryption, I'm not so much worried about the police. I shutdown often and don't have a target on my back. If I did cop a breach, I'd just rip the power cord out with reckless abandon.
I'm more worried about some brain dead nigger or gypsy breaking in to my house and stealing my PC or laptop when I'm not at home.
 

1768854558970.png
How I'd imagine Brodie's response if he were being more than 55% honest:
"Sorry but I'm either never trying it or I'll try to make them look bad under the guise of being "neutral" in a video, they're the imbec- I m-mean supported by that fascist je- I m-m-meeeeeeeean too politically motivated compared to other projects. That's why more than half of my recent content has been Wayland only. SO STOP TALKING ABOUT XLIBRE AND FOCUS ON TROON PROJECTS MADE BY MY FRIENDS!!!!!!"
 
I've had one too many cases of my computer not shutting down properly, so I think I'm gonna try something systemd-less. Leaning towards Artix OpenRC. Are there any practical day to day differences when using something not based on systemd?
Depends on what you use. You might need to write a couple services yourself on some things that don't provide services for the other init's. Which isn't too hard if you know how to write a shell script. Most other init's use something along the lines of shell scripts for writing services.

Other than that the differences, are how they handle user services, and the commands they use.
 

View attachment 8446599
How I'd imagine Brodie's response if he were being more than 55% honest:
"Sorry but I'm either never trying it or I'll try to make them look bad under the guise of being "neutral" in a video, they're the imbec- I m-mean supported by that fascist je- I m-m-meeeeeeeean too politically motivated compared to other projects. That's why more than half of my recent content has been Wayland only. SO STOP TALKING ABOUT XLIBRE AND FOCUS ON TROON PROJECTS MADE BY MY FRIENDS!!!!!!"

All the stinkditchware guzzling comments are organic I'm sure.
 
I've had one too many cases of my computer not shutting down properly, so I think I'm gonna try something systemd-less. Leaning towards Artix OpenRC. Are there any practical day to day differences when using something not based on systemd?
What system is this? I have the same issues with a MSI Trident 3 with 10th gen Intel and a Nvidia 1660 Super. I still haven't tracked down the cause, though I might try Venderfoul Wolf next as it doesn't use systemd
 
What system is this? I have the same issues with a MSI Trident 3 with 10th gen Intel and a Nvidia 1660 Super. I still haven't tracked down the cause, though I might try Venderfoul Wolf next as it doesn't use systemd
I have a 10th gen Intel, ASRock board and RX 6700. I used to have a 1660 ti and thought it was Nvidia driver problems, but I've had it happen even now with my AMD card and no Nvidia drivers.
 
I have a 10th gen Intel, ASRock board and RX 6700. I used to have a 1660 ti and thought it was Nvidia driver problems, but I've had it happen even now with my AMD card and no Nvidia drivers.
Havr you set the kernel command line to disable intel cstates? I believe intel 10th gen had a problem with that.

Add this to the kernel command line (or maybe double check that it's the right thing but im like 90% sure thid is it)

intel_idle.max_cstate=0

Edit: i can double check later tonight when I have time.
 
Havr you set the kernel command line to disable intel cstates? I believe intel 10th gen had a problem with that.

Add this to the kernel command line (or maybe double check that it's the right thing but im like 90% sure thid is it)

intel_idle.max_cstate=0

Edit: i can double check later tonight when I have time.
Double checked and added to grub and rebooted. Seems to have properly disabled the Intel idle driver so fingers crossed it fixes that rather annoying problem. Ended up borking something in my /home folder switching from LMDE to Venderfoul Wolf to Mint so I had to backup the important stuff and wipe my home partition

For fucks sake, on my 10th gen computer I need to disable Intel idle otherwise it crashes on sleep, and on my 6th gen laptop I have to disable vt-x otherwise it hangs on shutdown. Intel is actually pretty shitty for Linux if you get the wrong one. Intel 12th and 13th gen overheat... How is AMD? Maybe I should go Ryzen for my next system.
 
Last edited:
Double checked and added to grub and rebooted. Seems to have properly disabled the Intel idle driver so fingers crossed it fixes that rather annoying problem. Ended up borking something in my /home folder switching from LMDE to Venderfoul Wolf to Mint so I had to backup the important stuff and wipe my home partition

For fucks sake, on my 10th gen computer I need to disable Intel idle otherwise it crashes on sleep, and on my 6th gen laptop I have to disable vt-x otherwise it hangs on shutdown. Intel is actually pretty shitty for Linux if you get the wrong one. Intel 12th and 13th gen overheat... How is AMD? Maybe I should go Ryzen for my next system.
The one amd I had is pretty good. I dont think i ran into anything I can think of. The only thing I didn't like is the temperature wasn't as fine grained as intel. Showing me the temp of each core. Just the average. But that's really not important.

To be fair to intel. The older models worked well. The only problem is they're old and support is going to get worse over time. But things that came out around the haswell era have never given me problems.
 

xorg says in their irc they may make a main git branch to do some of the stuff xlibre did for them
you mean undo? reading that I thought it would be the opposite of what it was.

Either way. I've seen the people that stuck around with xorg complain so much about the xlibre guys commits. But using xlibre, and using xorg. Xlibre has tended to work better for me. The only thing I've noticed with xlibre is you will get abi warnings for certain things. But I haven't noticed it having any actual effect.
 
Back
Top Bottom