Linux

48313 readers

695 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

After trying secure boot out, my Ethernet connections don't work anymore? (feddit.de)

submitted 1 year ago by Rhabuko@feddit.de to c/linux@lemmy.ml

10 comments fedilink hide all child comments

Hey. Short story: I activated Secure boot on my MSI Mainboard and bootet in my new Debian. I realized that I had no wired internet connection and rebooted the system to deactivate secure boot again. Problem is that now my whole Ethernet is borked? I don't get a connection in Debian or my older OpenSuse partition and the Debian install USB stick says that the connection doesn't work. Of course I deinstallieren Windows and now this happens. Tried already a different cable . Any idea what I could do?

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

[–] edinbruh@feddit.it 10 points 1 year ago* (last edited 1 year ago)

Run dmesg and see if you find anything suspicious of the cause. If you find something like "blah blah... Ethernet... Blah blah... Key was rejected by service" or similar, it's due to secureboot.

If this is actually related to secureboot your drivers are most likely not in tree and installed via dkms, so they need to be signed or secureboot won't allow them. You can setup a machine-owner-key to sign them yourself, and you can setup dkms to automatically sign them using that key. The instructions are on dkms' readme. After setting up you need to run dkms autoinstall or manually reinstall the drivers to trigger the automatic signing.

Edit: I just noticed you said you deactivated secure boot... I have no clue. But for future reference, you can sign your modules to work with secure boot, it's not a bad idea.