Linux

48332 readers

581 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

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Cannot Install openSUSE or any other Distro (lemmy.world)

submitted 11 months ago by Sandbag@lemmy.world to c/linux@lemmy.ml

14 comments fedilink hide all child comments

Howdy everyone!

Looking for some help, I am trying to install openSUSE tumbleweed, the issue is I get stuck at the boot screen, the one that says loading kernel... loading initial ramdisk...

The issue is I am not quite sure what to do to troubleshoot this, any advice would be appreciated. This also happens with every distro I try to install, I've tried Arch, Nix, openSUSE and Fedora.

you are viewing a single comment's thread
view the rest of the comments

[–] mvirts@lemmy.world 3 points 11 months ago

The messages you're getting sound like they're from the bootloader, so I think secure boot is not causing the problem... Linux should print some stuff right away when it loads, maybe check the architecture of the kernel you're trying to boot, even an error immediately after loading the kernel should print something unless the architecture is so different that it's just feeding the CPU bad instructions... Not sure how the bootloader would get installed correctly in that situation though. Is this after installation? Does the system boot from a live USB or cdrom?