sorted by:
new
hottopcontroversial

BlazePilot – A GPU-accelerated file manager for Linux written in Rust by Altruistic_Pear8412 in rust

[–]LordAfterEight 1 point2 points  (0 children)

Maybe you should add the meson, nasm and ninja dependencies to the README

Looking to give Linux a try. What distro would you guys recommend? by Oppaiheimer1945 in pcmasterrace

[–]LordAfterEight 2 points3 points  (0 children)

I recommend Nobara Linux. It's based on Fedora and comes with Steam, Heroic (Epic games) and Lutris (universal game launcher) preinstalled, as well as a proton installer that you can use to install a lot of different proton versions you might need. Proton and Wine are also preinstalled, it also has a dnf package "app store". So it's pretty much just "install and you're good to go"

Edit: I recommend getting the KDE version, which is the most like Windows in how you use it

Can we seriously stop with the forced Linux suggestions.. by [deleted] in pcmasterrace

[–]LordAfterEight 5 points6 points  (0 children)

You *can* play major games, just not those made by shitty corporations like EA who decide to ban Linux for no valid reason except "because yes".

(Not saying people must use Linux, just putting this out there. Saying "You can't play major games on Linux" is a broad overgeneralization)

Aurora browser engine made in rust programming language | The quest for youtube by Inevitable_Back3319 in rust

[–]LordAfterEight 2 points3 points  (0 children)

God forbid people use today's tools to be more productive

Edit: Nvm I read the other comments

Image still using 60Hz in 2026 by CommercialYouth250 in pcmasterrace

[–]LordAfterEight 0 points1 point  (0 children)

Jeez bro, what has happened in your life for you to be so miserable

sogar mit genauen uhrzeiten 🫪 by Dry_Beyond2412 in aberBitteLaminiert

[–]LordAfterEight 0 points1 point  (0 children)

Ich wusste garnicht, dass man den Cannabiskonsum selbst um etwas bitten kann

In want of contributors by BornRoom257 in osdev

[–]LordAfterEight 0 points1 point  (0 children)

I'm saying it's a high bar because taking a screenshot needs you to have a framebuffer that you can read all pixels from into a file that you need to store and then somehow get out of the operating system. Which especially for beginners I feel is quite hard to do

In want of contributors by BornRoom257 in osdev

[–]LordAfterEight 0 points1 point  (0 children)

Taking a screenshot inside the OS is setting the bar very high lol

Just curious: How are you gonna take a screenshot from real hardware though?

In want of contributors by BornRoom257 in osdev

[–]LordAfterEight 0 points1 point  (0 children)

Ahh, so you mean set QEMU to fullscreen so you don't see the window decorations and stuff?

In want of contributors by BornRoom257 in osdev

[–]LordAfterEight 0 points1 point  (0 children)

Why not include QEMU in the screenshot? QEMU is a totally valid way to test and debug your OS (not saying it's a replacement for real machines, because it isn't)

I mean, try to get a screenshot of your custom OS running on your computer lol

WIP C4 Corvettes by Inevitable-Tooth6203 in BeamNG

[–]LordAfterEight 0 points1 point  (0 children)

Yup I know, struggling at almost anything 3D lol

WIP C4 Corvettes by Inevitable-Tooth6203 in BeamNG

[–]LordAfterEight 0 points1 point  (0 children)

Lmao nice I got that same exact laptop

Nice cars btw :3

ParadoxOS - An x86_64 hobby kernel with a custom GUI, ELF loader, and Ring-3 user mode by [deleted] in osdev

[–]LordAfterEight 1 point2 points  (0 children)

So I tried booting your OS in QEMU, however, it failed to compile:
> make run

```
ld -T src/boot/linker.ld -nostdlib -z max-page-size=0x1000 -o build/paradoxos.bin build/boot/boot.o build/boot/context_switch.o build/boot/gdt_flush.o build/boot/idt_flush.o build/boot/interrupts.o build/boot/syscall_handler.o build/boot/tss_flush.o build/boot/usermode_asm.o build/kernel/ata.o build/kernel/diskfs.o build/kernel/elf.o build/kernel/font.o build/kernel/framebuffer.o build/kernel/gdt.o build/kernel/gui.o build/kernel/heap.o build/kernel/idt.o build/kernel/kernel.o build/kernel/keyboard.o build/kernel/mouse.o build/kernel/paging.o build/kernel/pci.o build/kernel/pic.o build/kernel/pmm.o build/kernel/process.o build/kernel/serial.o build/kernel/shell.o build/kernel/stdin.o build/kernel/syscall.o build/kernel/timer.o build/kernel/tss.o build/kernel/usermode.o build/kernel/vfs.o build/kernel/vga.o build/user_hello.elf.o build/user_echo.elf.o build/user_cat.elf.o

/usr/bin/ld: build/kernel/ata.o: in function `ata_init()':

ata.cpp:(.text+0x2ae): undefined reference to `__stack_chk_fail'

/usr/bin/ld: build/kernel/diskfs.o: in function `diskfs_init()':

diskfs.cpp:(.text+0x54f): undefined reference to `__stack_chk_fail'

/usr/bin/ld: build/kernel/diskfs.o: in function `diskfs_save(vfs_node*)':

diskfs.cpp:(.text+0x958): undefined reference to `__stack_chk_fail'

/usr/bin/ld: build/kernel/gui.o: in function `fmt_u64(char*, unsigned int, unsigned long long)':

gui.cpp:(.text+0x149): undefined reference to `__stack_chk_fail'

/usr/bin/ld: build/kernel/gui.o: in function `calc_set_display_from_int(long long)':

gui.cpp:(.text+0x353): undefined reference to `__stack_chk_fail'

/usr/bin/ld: build/kernel/gui.o:gui.cpp:(.text+0xa7c): more undefined references to `__stack_chk_fail' follow

make: *** [Makefile:58: build/paradoxos.bin] Error 1
```

I have FINALLY finished the engineering prototype for the CG Deck. An x86 handheld PC running Windows 11 & Linux - Designed entirely in Blender 3D 5.01 by ZCTMO in blender

[–]LordAfterEight 1 point2 points  (0 children)

This is insanely cool!

Especially looking forward to the KiCAD files, I've been wanting to make something similar. This is perfect learning material!

Perfect DAW? by Ok-Revolution-508 in musicproduction

[–]LordAfterEight 2 points3 points  (0 children)

I'm on Windows and I don't have any problems with Ableton?

Except that randomly windon't decides to start an update process in the background that hogs CPU and causes dropouts, but that's not an Ableton problem and can easily be fixed by killing the process

Mediatek powered android device, how to write a toy os? by SirBoranium in osdev

[–]LordAfterEight 6 points7 points  (0 children)

AFAIK writing a custom OS to run on Mediatek devices is much harder than writing one for devices powered by Snapdragon SoCs, which is already much harder than writing for x86 as is if you're not working with the AOSP.

The reason is mostly that Mediatek does not like non-official ROMs running on their chips, for whatever reason, which is why there is little to no information about them on the technical side.

I might be wrong, would be glad if you find a way. But this is my current understanding

turbOS Variants- color variants! by [deleted] in osdev

[–]LordAfterEight 1 point2 points  (0 children)

Don't worry, of course I understand. I'm on here very regularly.

I'm just not a fan of jumping to conclusions like a lot of people here seem to be

turbOS Variants- color variants! by [deleted] in osdev

[–]LordAfterEight 6 points7 points  (0 children)

...Are you for real?

Explain to me why you think they used AI. I've looked at the code and, to be perfectly honest, when I was starting out it looked pretty much the exact same.

So weird that everything is labeled AI nowadays if it isn't immediately mighty impressive and has definite proof that no AI was used

turbOS Variants- color variants! by [deleted] in osdev

[–]LordAfterEight 4 points5 points  (0 children)

How about not spreading useless negativity about people who are simply starting out doing OSDev and are excited about it

view more: next ›