this post was submitted on 09 Nov 2023
228 points (98.3% liked)
Linux
48145 readers
1021 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!
If you're not booting with UEFI then you'll need to make sure your USB stick is 'blessed' so the BIOS can pick it up as a boot device. I dunno what the state of BIOS boot images is in 2023 but you can probably get away with finding an old BIOS compatible boot image and then use DD to capture the first few bites that has the boot blessing on it.
None of the distro images I have seen in the last few years were built for BIOS so none of those images are going to work.
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. :)
It sounds like the USB is fine. What mode is the drive controller in? It's probably IDE. I haven't fucked with this in SO long but I am guessing the south bridge controller isn't supported by the newer kernels. It looks like basic IDE is still supported. Have you tried other kernels? I'm wondering if something like Ubuntu LTS or Arch LTS would have more devices supported.
Do you know how to boot strait to the kernel and nothing else? Since this is probably IDE you can do it super easy. It sounds like you can load the kernel into memory alright so you should be able to probe the kernel once booted to see whats on
lsusbandlspcito see what's not coming up.You can probably use any recovery USB/kernel to get an idea of if you're supported or not.
https://askubuntu.com/questions/92556/how-do-i-boot-into-a-root-shell
That system is definitely 32bit only. Are you using a 32bit build?