when I boot into fedora I am getting no internet and no way to enable it whereas I dont remember this happening on prior kernels7.0.3 is my prior kernel fedora 44 kde
right now it works properly and I am connected to wifi and can turn it on or off as I wish
when it breaks there is no way to somehow reenable it and it only breaks on boot
Do you want to use ethernet or is WiFi your only option? We will need more details to understand your issue, but there are some simple things to check:
make sure both Fedora and vendor firmware are fully updated so you aren’t chasing a problem that has been solved. Recent kernels often require changes to vendor firmware – not all vendors update promptly; some care even less about their linux users.
many systems can enable networking with minimal drivers at boot (so cubicle farms can netboot and manage systems during off hours) – for some models you need to disable networking at boot – other models require enabling network at boot.
the journal collects massive amounts of detail. It takes some effort to filter out irrelevant details to focus attention on a particular problem, but if you are managing your own system it is important to know how to use journalctl – see: https://docs.fedoraproject.org/en-US/quick-docs/viewing-logs/.
Note that journalctl and similar output should be posted as web-discoverable pre-formatted text using the </> button. This helps get the attention of a wider audience both due to web searches and ensuring that the text can be read using text-to-speech for visually impaired (often older, very experienced) linux users.
just happened again on Operating System: Fedora Linux 44
KDE Plasma Version: 6.7.5
KDE Frameworks Version: 6.30.0
Qt Version: 6.11.2
Kernel Version: 7.2.5-200.fc44.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 7600 6-Core Processor
Memory: 32 GiB of RAM (30.5 GiB usable)
Graphics Processor 1: NVIDIA GeForce RTX 4060
Graphics Processor 2: AMD Ryzen 5 7600 6-Core Processor
Manufacturer: ASRock
Product Name: A620M-HDV/M.2+
so updating didnt fix the issue (although it seems to be happening a lot less often since it is first time happened on Kernel Version: 7.2.5)
and btw when internet was off I ran
journalctl -u NetworkManager --since “20 minutes ago”
Sep 17 21:16:31 fedora systemd[1]: Starting NetworkManager.service - Network Manager…
Sep 17 21:16:31 fedora NetworkManager[1020]: [1789668991.6868] NetworkManager (version 1.56.1-2.fc44) is starting… (boot:31e73ebc-63fa-4>
Sep 17 21:16:31 fedora NetworkManager[1020]: [1789668991.6869] Read config: /etc/NetworkManager/NetworkManager.conf, /usr/lib/NetworkManag>
Sep 17 21:16:31 fedora NetworkManager[1020]: [1789668991.6901] manager[0x55bd056b3a90]: monitoring kernel firmware directory '/lib/firmwar>
Sep 17 21:16:31 fedora NetworkManager[1020]: [1789668991.7574] hostname: hostname: using hostnamed
Sep 17 21:16:31 fedora NetworkManager[1020]: [1789668991.7585] dns-mgr: init: dns=systemd-resolved rc-manager=unmanaged (auto), plugin=sys>
Sep 17 21:16:31 fedora NetworkManager[1020]: [1789668991.7598] manager[0x55bd056b3a90]: rfkill: Wi-Fi hardware radio set enabled
Sep 17 21:16:31 fedora NetworkManager[1020]: [1789668991.7598] manager[0x55bd056b3a90]: rfkill: WWAN hardware radio set enabled
Sep 17 21:16:31 fedora NetworkManager[1020]: [1789668991.7642] Loaded device plugin: NMTeamFactory (/usr/lib64/NetworkManager/1.56.1-2.fc4>
Sep 17 21:16:31 fedora NetworkManager[1020]: [1789668991.7645] Loaded device plugin: NMAtmManager (/usr/lib64/NetworkManager/1.56.1-2.fc44>
Sep 17 21:16:31 fedora NetworkManager[1020]: [1789668991.7759] Loaded device plugin: NMWifiFactory (/usr/lib64/NetworkManager/1.56.1-2.fc4>
Sep 17 21:16:31 fedora NetworkManager[1020]: [1789668991.7784] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/1.56.1-2.fc>
Sep 17 21:16:31 fedora NetworkManager[1020]: [1789668991.7787] Loaded device plugin: NMWwanFactory (/usr/lib64/NetworkManager/1.56.1-2.fc4>
Sep 17 21:16:31 fedora NetworkManager[1020]: [1789668991.7788] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Sep 17 21:16:31 fedora NetworkManager[1020]: [1789668991.7789] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Sep 17 21:16:31 fedora NetworkManager[1020]: [1789668991.7789] manager: Networking is enabled by state file
Sep 17 21:16:31 fedora NetworkManager[1020]: [1789668991.7790] settings: Loaded settings plugin: keyfile (internal)
Sep 17 21:16:31 fedora NetworkManager[1020]: [1789668991.7803] dhcp: init: Using DHCP client ‘internal’
Sep 17 21:16:31 fedora NetworkManager[1020]: [1789668991.7804] manager: (lo): new Loopback device (/org/freedesktop/NetworkManager/Devices>
Sep 17 21:16:31 fedora NetworkManager[1020]: [1789668991.7808] device (lo): state change: unmanaged → unavailable (reason 'connection-ass>
Sep 17 21:16:31 fedora NetworkManager[1020]: [1789668991.7810] device (lo): state change: unavailable → disconnected (reason 'connection->
Sep 17 21:16:31 fedora NetworkManager[1020]: [1789668991.7812] device (lo): Activation: starting connection ‘lo’ (7390a779-4b18-42ec-9098->
Sep 17 21:16:31 fedora NetworkManager[1020]: [1789668991.7817] manager: (enp8s0): new Ethernet device (/org/freedesktop/NetworkManager/Dev>
Sep 17 21:16:31 fedora NetworkManager[1020]: [1789668991.7818] device (enp8s0): state change: unmanaged → unavailable (reason ‘managed’, >
Sep 17 21:16:31 fedora NetworkManager[1020]: [1789668991.9629] bus-manager: acquired D-Bus service “org.freedesktop.NetworkManager”
not sure if it will help or what should I ran when it happens to find out whats wrong
although there may be some other difference between what happened earlier and now since now pc for some reason has forgot its passwords to wifi networks (just to be clear when that bug happens you cant see any wifi networks but on the next login all passwords were forgotten which didnt happen earlier and different browsers all logged out all my users so maybe it was not the same bug as on 7.1.3 causing it (maybe the fact that my pc was powered off (there was few seconds long power outage) today may have caused some issues)
Many lines in your journalctl output were truncated and end in >. Adding —no-hostname —no-pager options reduces the line length and wraps remaining overly long lines. For terminal output, use the <\> “pre-formatted text” button.