Linux

47361 readers

1734 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

nooter692@lemmy.ml

AgreeableLandscape@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Clevo Laptop doesnt boot any Linux USB sticks? partitions not found, fstab errors and all? (feddit.de)

submitted 10 months ago by Pantherina@feddit.de to c/linux@lemmy.ml

6 comments fedilink hide all child comments

I am trying out a Clevo MZ41, pretty interesting machine. It is coreboot supported (Dasharo, in the future also Heads) which is exciting.

But I cant boot any live Linux? I tried Fedora Media writer and KDEs iso image writer. I tried Fedora KDE and KDE Neon (you see a trend haha) and also Ventoy.

These sticks normally always boot up, but here I get Dracut timeout, partition /root not found etc.

In the insydeH2O Bios I already disabled Secureboot entirely (not even needed, that Bios is awesome I can even deploy my own keys and all). Nothing changed.

Warning: /dev/disk/by-label/Fedora-KDE-Live-38-1-6 does not exist
Warning: /dev/root does not exist

... emergency mode ...

Anyone know whats going on here?

all 7 comments

sorted by: hot top controversial new old

[–] Psynthesis@beehaw.org 3 points 10 months ago* (last edited 10 months ago) (1 children)

I have never used those tools, I usually just dd the iso to a usb. I am assuming you are on a linux distribution already. I would download a fresh iso and verify the checksum. Then use dd to write to the usb. I use this format, and of course replace the path to iso bit and /dev/sdx (your usb)with what is relevant to your situation. Just open terminal and type

sudo dd bs=4M if=path/to/your.iso of=/dev/sdx conv=fsync oflag=direct status=progress

You probably already know but you can find the usb's specific /dev/sdx with sudo fdisk -l

[–] Pantherina@feddit.de 1 points 10 months ago

Both tools use dd underneath so this should be no problem. But I can try

[–] Spider89@lemmy.world 1 points 10 months ago (1 children)

Debian Live?

[–] Pantherina@feddit.de 1 points 10 months ago (1 children)

I dont think that will change anything. Its not the distros fault, thats the thing. I used these exact ISOs

[–] Spider89@lemmy.world 2 points 10 months ago

It may be the way the are burned.

Try using Balena Etcher or Rufus.