Linux

48222 readers

1026 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

Linux devices not connecting to wifi [CLOSED] (feddit.de)

submitted 6 months ago* (last edited 6 months ago) by SomeBoyo@feddit.de to c/linux@lemmy.ml

12 comments fedilink hide all child comments

All my devices seem to have problems connecting to my homes router. This problem appears only on linux and only on my router. All other networks work flawlessly. My router is a CH7466CE.

EDIT: My router seems to have unfucked itself.

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

[–] Max_P@lemmy.max-p.me 5 points 6 months ago (2 children)

I'd start by pulling NetworkManager, wpa_supplicant and iwd logs (journalctl -u networkmanager.service --since -2h and so on). Check dmesg as well.

[–] SomeBoyo@feddit.de 1 points 6 months ago (1 children)

both don't show anything weird

[–] Max_P@lemmy.max-p.me 2 points 6 months ago

I'd still paste it, redacting SSID and MAC addresses.

Even if it's just info messages, it'll still give us an idea of what it does or doesn't do.

I saw the other comment thread about using a static IP sometimes fixing it. We should see that DHCP attempt in the logs. Maybe it succeeds, maybe it's like "btw the router handed me option 42 and I don't know how to deal with that", maybe it's using the wrong DHCP client (dhclient vs dhcpd) but clues are clues.

Could also tail the entire system log (journalctl -f) so you'll see live output of every service. Maybe it connects fine but something else immediately kicks in and breaks it.