ringwormgo-organization/ringos

ringOS source code

ringos's Issues

Why not Makefile clone the bootloader automaticly?

Is your feature request related to a problem? Please describe.
I'm always frustrated when people just don't follow the instruction and read the documentation.

Describe the solution you'd like
Why don't just put the cloning in the Makefile?

Describe alternatives you've considered
During build, it will check for the bootloader folder and if it does not exist, it will clone the repo

Additional context
None

LockOS should be locked ;)

Add Makefile for BIOS version, and guide to compile and use

You should add a makefile, it is easier to compile your operating system. Also, add the guide to compile and use.

Unable to build beta17

Describe the bug
i CDed into ringOS-Beta17 and ran make buildimg and it tries to go to ../gnu-efi??? should'nt it go to ringOS-Beta17-bootloader?

Version of ringOS
Beta17

Expected behavior
This not to happen

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

ringOSY NON-DOCKER ENVIROMENT BUG

If you complie ringOSY outside Docker you can't boot on real hardware

Make .sh build script for Fedora / CentOS (Stream) / RHEL

Hi,

I'm currently running Centstream 9 and I'm having problems when building ringOS from source because it only support building on Debian or Debian-based distribution. The shell script for building ringOS doesn't support Fedora-based distribution including Centstream, RHEL, Alma, Rocky. Can you make a specified shell script for them?

Suggestion: you can make a script called configure-debian(.sh) and configure-rhel(.sh) and the configure(.sh) script to detect if it is Debian or Fedora/RHEL based distribution. Those script throw information about the current operating system to know how to build it. The build.sh or Makefile will choose the way to build based on the info about operating system. configure scripts are optionally use to install required packages.

Hope my issue will be fixed soon.

(real hardware) OS stopes booting and freezes

Describe the bug
I got the OS to boot on real hardware, but it showed the PCI stuff and then the task bar and it froze. No mouse, no keyboard, nothing, just frozen as if it was displaying an image. And also, there was an error:

An error occurred while attempting to load BMP file!
Loading file from media!
Could not load BMP image

Version of ringOS
Commit 476

Expected behavior
Everything to work

Screenshots
Cant add rightnow

Additional context

Hardware

1. Ram

• Type: DDR3
• Speed: 3.666GHz
• Total: 6144MB
• Slot1: 2048MB
• Slot2: 4096MB

2. Laptop

• Samsung NP300E5X-S01IN

3. GPU

• Intel integrated graphics
• Nvidia GeForce 610M 1GB DDR3

4. Processor:

• Model: Intel Core i5 (3rd Generation)
• Clock Speed: 2.5GHz
• Cores: 2

5. Connected Storage:

• Sata HHD
• Sata SSD
• Sata Disk Drive
• USB pen drive

ringOS GUI stopes working after resizing the window

Describe the bug
I went into the settings and resized the OVMF screen size and now it is not booting (almost like my old issue, but i opened a new one)

Version of ringOS
Beta17

Expected behavior
nothing to happen and everything to work

Screenshots
See my last issue

Additional context
It happens only is i resize it smaller than the image.

Beta17 not booting compleatly

Describe the bug
Bootloader says "GOP Located" and reboots and sometimes it shows Could not load BMP image. but the image is in the ISO.

Version of ringOS
Beta17

Expected behavior
it to load

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Clicking mouse wheel crashes ringOS (QEMU)

Describe the bug
When booting ringOS (in QEMU), I clicked mouse wheel and kernel panic screen poped-uo.

Version of ringOS
Stable version 2.0.0

Expected behavior
For mouse wheel to not crash ringOS

Screenshots

Additional context
No additional context

Can't boot in VMWare, VirtualBox and Hyper-V

Hyper-V:

Vbox:

Sorry I dont have vmware captures

ringOS Limine make dosen't work

When I tried to compile ringOS Limine it didn't work. I followed all of the instructions but it couldn't compile.

Here are some of the issues:
1. limine/limine-s2deploy dosen't exist
Error below;

   limine/limine-s2deploy barebones.iso
   make: limine/limine-s2deploy: No such file or directory
   make: *** [GNUmakefile:40: barebones.iso] Error 127

2. When limine-s2deploy is manually created it still doesn't compile (tried it with sudo it still didn't work)
Error below;

   make: limine/limine-s2deploy: Permission denied
   make: *** [GNUmakefile:40: barebones.iso] Error 127

Uppercase signs don't work

Describe the bug
When i try "!" it shows "TM"

Version of ringOS
ringos stable 1

Expected behavior
it to show !

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Mouse does not work in builder

Version of ringOS
what ever the builder gives

Unexpected behavior
mouse to not work

Expected behavior
mouse to work

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

ringOS will crash if I click the mouse in VirtualBox

Unable to build ringOS-Beta17 image from existing Makefile

Describe the bug
When working on compiling an image for ringOS-Beta17 I am unable to successfully build them image using the existing Makefile. The kernel compiles and links successfully when the command "make kernel" is issued from within the ringOS-Beta17 directory. When I then issue the "make buildimg" command I receive the following output:

wmthornton@vostro-3500:~/Desktop/source/repos/ringOS/ringOS-Beta17$ make buildimg
dd if=/dev/zero of=bin/ringOS.img bs=512 count=93750
93750+0 records in
93750+0 records out
48000000 bytes (48 MB, 46 MiB) copied, 0.705147 s, 68.1 MB/s
mformat -i bin/ringOS.img -F ::
mmd -i bin/ringOS.img ::/EFI
mmd -i bin/ringOS.img ::/EFI/BOOT
mcopy -i bin/ringOS.img ../gnu-efi/x86_64/bootloader/main.efi ::/EFI/BOOT
../gnu-efi/x86_64/bootloader/main.efi: No such file or directory
make: *** [Makefile:61: buildimg] Error 1

What steps do I need to take to successfully compile and build the image on Ubuntu 20.04? The directories that the Makefile is referencing do not exist in the repository so I'm unsure what to do next.

Version of ringOS
Beta17

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots

Additional context
When I attempt to build the bootloader code contained in the "ringOS-Beta17-bootloader" it fails to compile so I don't even have the correct bootloader to build an image with.