Astralixi OS Megathread

When you compile the kernel it also compiles modules that need to be on the system also. The panel for example is a module, if you don’t have that module in the correct location on the system where the kernel can find it you won’t have no screen output.
If you compile the modules into the kernel for the uConsole, it compiles to around 80 MB.

1 Like

Do you have a kernel binary available? Or is there any way you could compile it into a binary for me, as you know the most out of all of us.

I can compile you a working kernel with all modules compiled into the kernel. I’m pretty busy so give me a day or two.

Thank you so much!

Astralixi OS won’t be possible without the help from the community.

In the mean time, I will start working on some apps for the next version, and an app API so that users can contribute their own apps.

Start developing AstralixiOS apps now (even though the OS isn’t out yet)

Hey everyone,

So AstralixiOS isn’t released yet, and the version that actually supports user-made apps is even further away. But I figured there’s no reason you can’t start writing apps right now, so I put together an API and some documentation for it.

The idea is that when app support does land, you’ll already have something ready to go. The API is written in Python and uses only the standard library, so you don’t need anything special installed to start playing with it.

Here’s what’s available:

  • astralixios_api.py - the actual API file you import in your app
  • Making TUI Apps.md - a guide that explains how to use it, the rules for apps, and how submission will work

You can grab both from here.

A few things worth knowing

Apps have to be TUI only. TUI is Terminal User Interface, basically an advanced CLI with very basic graphics. No GUI windows, no tkinter popups, nothing like that. Just the terminal with basic graphics.

Apps also have to be a single .py file and use only the Python Standard Library. No pip installs.

The API was made using Claude, where I basically had it act as an employee working on the project. Because of that there might be mistakes or things that don’t quite fit right. If you spot anything wrong, weird, or missing, please point it out and I’ll fix it. That’s kind of the whole point of sharing it early.

Why bother now?

Honestly just so the app library isn’t empty on launch. If a few people have apps ready to go when the OS actually ships, that’s way better than waiting until release and starting from zero.

Let me know what you think, and if you run into any issues with the API itself just reply here or open an issue.

Thanks.

wow that was a lot to write

he’s just vibe imaging… been spamming on the subreddit for quite a while now then here

1 Like

We already know him. This is his second attempt here.

2 Likes

Didn’t use AI for imaging. Google searching and AI is different (i didn’t use search overview) just hopped from forum to forum to stack overflow.

App Ideation:

I would actually really appreciate this as well. I’ve been having an awful time with Arch Linux ARM lately since the packages have circular dependencies and most of the AUR refuses to install on a non-amd64 system. It’d be nice to run with a simple rootfs, no package manager except pkgsrc, and play with different inits and things. Having the kernel live in the boot partition and not depend on anything in the root tree would make this project much easier.

2 Likes

@trinity @Astrox Here’s a kernel with only the overlays and the kernel with the modules compiled into it. everything just goes in the boot partition.

2 Likes

Thanks a lot! What file system is it using? Is it FAT32?

Yep the boot partition uses fat32

1 Like

I love Rex’s work for the kernel, and there’s nothing I dislike about it, so don’t take this as me avoiding your kernel (I will still 100% use it for the pre-release and maybe even the first full release) but:

License Section 7b edited

Okay, so I have all the files I need.

How in the world do I build them into a .img. :sob:

Coding an OS is enjoyable, building one together is not.

MISSION FAILED

Any help would be appreciated.
If I built it properly, hooray to me, but then that means there is something wrong with printing to the screen after Nuitka compiled, and I added it to the .img.

AstralixiOS is now Open Source

1 Like

Hey everyone!

So as you all already know, AstralixiOS is now open source and all the files you need to build it into a .img are up and available.

I really need some help though. Every time I build it, it just boots into a black screen and I honestly have no idea why. I’ve been stuck on it for a while now and I think some fresh eyes would really help. If anyone could try building it themselves or has seen this kind of issue before, please let me know what you find.

Any help at all is seriously appreciated, even if it’s just pointing me in the right direction. Hopefully we can get it to actually boot properly together!

Thanks heaps :slight_smile:

i took a look at your image and found the first glaring problem. you didn’t copy over all the overlays for the pi4 or any for the pi5. i just dropped them in for all the pis you can remove pi3 and down.
you also didn’t have the overlay to activate the uconsoles hardware, i added a new config.txt. it now boots… kinda
you got a ways to go but this will give you a new place to continue from…

2 Likes