this post was submitted on 09 Nov 2023
241 points (98.0% liked)
Linux
48081 readers
1004 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by AlpΓ‘r-Etele MΓ©der, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
There's nothing like that is enabled AFAIK, I"m not even sure this board has UEFI (only Legacy BIOS). It's an Acer Veriton M421G brand PC, with a Phenom II X4 945 CPU.
Not even sure it's compatible with the OS, but this boot device issue was strange, tho. (had the same problem booting up a partition manager software from floppy that is based on Visopsys)
But will double check everything. Thanks for the tip!
I dd-ed the image straight to the HDD. grub started and booted off from it. lots of messages of PCI devices, I guess some kind of scan. after a while the screen went white, and a bit later the logs of the kernel panic appeared at the top, with the message it could't find a device to boot from.
so, it seems that the kernel itself didn't see the hdd it just booted from - standard IDE PATA disk, 120GB. Used dd from a gparted live disc.
First, I resized the partition on the disk to the full, at the next try I left it, as-is.
Both times the same result; the BIOS boots into Serenity, white screen, then kernel panic, couldn't find a device to boot from.
Thing is, there are 2 DVD drives (IDE and SATA) and a floppy drive attached to the PC, dunno if they can cause any problem. And 1GB memory.
this was yesterday, and since then I haven't got tieme to fiddle with it, but will. :)
What do you mean by that?
I used x86_64 build, and my CPU is 64-bit. (Ran 64-bit Windows and different Linux systems on it before)
Thanks for the tip, but I know, what I was talking about π
I use IDE HDD with this machine. The mobo has several SATA ports, but my HDD is IDE, it's not a mistake.
Tho, that setting is, indeed is IDE, so I might set it to AHCI for Serenity, but the drive is still hoiked into the IDE bus.
But if the problem is the fact, that I'm trying to use IDE and should try with a SATA drive, I'll look into it as soon as I can.
And thanks for co-piloting ;)
At the weekend I'll have some time to fiddle with it.
I think I'll try to boot Serenity first from USB, check if it wants to boot at all. Maybe I'll got an Arduino to use as serial monitor to check the log.
Then move on to flashing the grub image to the HDD, again, with a different IDE drive. if thst doesn't work, I'll find a SATA HDD and flash that.
I really wanna see this OS boot on real hardware. Then take a good lookaround and develop or port something for it :)
This part actually makes me wonder... Do you think SerenityOS uses the Linux kernel? Because it does not, it's its own completely separate thing. And the hardware support for anything other than the standard emulated machine is very iffy, so it doesn't seem too surprising that it would get tripped up by something on an old computer.
If anything went wrong with its USB stack for example, the kernel would have no way to find the root filesystem that's stored on a USB drive.