Linux

48002 readers

1010 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

[Help] Could not create moklistrt: Volume full on booting up with both fedora and ventoy (lemmy.kya.moe)

submitted 1 year ago by gurapo@lemmy.kya.moe to c/linux@lemmy.ml

7 comments fedilink hide all child comments

Why hello there fellow tuxers. I hope I am not posting this in the wrong spot, I am still a little new to this type of social media.

I have installed fedora today on my pc. However, after a successful install and a single successful boot, the pc just stopped booting both the pen (with ventoy) and fedora.

Both the pen and fedora print the same error.
Windows still works normally.
My EFI partition is 512mb long and still has half its space left.
I can't chroot into fedora and reinstall grub, because the pen stopped working.
I don't have Secure Boot enabled.

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

[–] gurapoku@lemmy.ml 3 points 1 year ago

To answer the first question, likely not. The answer to the second question is I am pretty sure. In my bios, I have secure boot control as disabled and secure boot grayed out on the "Not Active" setting