Wifi device can't be found after update

I updated Fedora 34 two days ago and since then I don’t have internet access anymore on my laptop.
When I type “wifi” on the terminam no device can be found.

Wifi is working on my Windows partition btw so the device should be working fine.

Please give us a bit more infos. inxi -Fzx in terminal would be a good start.
If not available you have to install inxi.

Don’t know what happened. After several restarts and connecting my phone to my laptop to make another update it seems to work again…

1 Like

hey I am back and now I have the same problem. Similar to last time I used my Windows 10 partition before. Then I shutted my PC down and started Fedora after that again. Now I can’t find my Wifi device anymore and I am currently using my phone via USB tethering.

After using inxi -Fzx

  Kernel: 5.14.13-200.fc34.x86_64 x86_64 bits: 64 compiler: gcc 
  v: 2.35.2-6.fc34 Desktop: GNOME 40.4 
  Distro: Fedora release 34 (Thirty Four) 
  Type: Laptop System: ASUSTeK product: UX550VE v: 1.0 serial: <filter> 
  Mobo: ASUSTeK model: UX550VE v: 1.0 serial: <filter> 
  UEFI: American Megatrends v: UX550VE.307 date: 04/19/2019 
  ID-1: BAT0 charge: 47.2 Wh (99.4%) condition: 47.5/73.8 Wh (64.4%) 
  volts: 15.4 min: 15.4 model: ASUSTeK ASUS Battery status: Charging 
  Info: Quad Core model: Intel Core i7-7700HQ bits: 64 type: MT MCP 
  arch: Kaby Lake rev: 9 cache: L2: 6 MiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 44798 
  Speed: 800 MHz min/max: 800/3800 MHz Core speeds (MHz): 1: 800 2: 800 
  3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 
  Device-1: Intel HD Graphics 630 vendor: ASUSTeK driver: i915 v: kernel 
  bus-ID: 00:02.0 
  Device-2: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile] vendor: ASUSTeK 
  driver: nvidia v: 470.74 bus-ID: 01:00.0 
  Device-3: IMC Networks USB2.0 VGA UVC WebCam type: USB driver: uvcvideo 
  bus-ID: 1-4:2 
  Display: x11 server: X.Org 1.20.11 driver: loaded: modesetting,nvidia 
  unloaded: fbdev,nouveau,vesa resolution: 1920x1080~60Hz 
  OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 21.1.8 
  direct render: Yes 
  Device-1: Intel CM238 HD Audio vendor: ASUSTeK driver: snd_hda_intel 
  v: kernel bus-ID: 00:1f.3 
  Sound Server-1: ALSA v: k5.14.13-200.fc34.x86_64 running: yes 
  Sound Server-2: PulseAudio v: 14.2-rebootstrapped running: no 
  Sound Server-3: PipeWire v: 0.3.38 running: yes 
  Device-1: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel port: e000 
  bus-ID: 03:00.0 
  IF-ID-1: enp58s0u2 state: unknown speed: -1 duplex: half mac: <filter> 
  IF-ID-2: virbr0 state: down mac: <filter> 
  Device-1: Intel Bluetooth wireless interface type: USB driver: btusb 
  v: 0.8 bus-ID: 1-9:3 
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends 
  Device-2: Google Nexus/Pixel Device (tether) type: USB driver: rndis_host 
  v: kernel bus-ID: 3-2:3 
  Report: This feature requires one of these tools: hciconfig/bt-adapter 
  Local Storage: total: 476.94 GiB used: 43.94 GiB (9.2%) 
  ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLW512HMJP-00000 
  size: 476.94 GiB temp: 37.9 C 
  ID-1: / size: 214.47 GiB used: 43.63 GiB (20.3%) fs: btrfs dev: /dev/dm-0 
  mapped: luks-24d56692-edfe-4ae7-8879-80821d8fda14 
  ID-2: /boot size: 975.9 MiB used: 242.9 MiB (24.9%) fs: ext4 
  dev: /dev/nvme0n1p5 
  ID-3: /boot/efi size: 259.8 MiB used: 73.2 MiB (28.2%) fs: vfat 
  dev: /dev/nvme0n1p1 
  ID-4: /home size: 214.47 GiB used: 43.63 GiB (20.3%) fs: btrfs 
  dev: /dev/dm-0 mapped: luks-24d56692-edfe-4ae7-8879-80821d8fda14 
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) dev: /dev/zram0 
  System Temperatures: cpu: 48.0 C mobo: N/A 
  Fan Speeds (RPM): cpu: 2700 
  Processes: 430 Uptime: 4m Memory: 15.5 GiB used: 2.32 GiB (14.9%) 
  Init: systemd runlevel: 5 Compilers: gcc: 11.2.1 Packages: 30 
  note: see --pkg Shell: Bash v: 5.1.0 inxi: 3.3.06 

but entering wifi in my terminal just claims there is now device

wifi      = none (no device)

Most probably your Wi-Fi driver is Rtl8821ce

I got the solution on Reddit:

It’s Windows all over again. I disabled Fast Boot in my BIOS settings but didn’t know it needs to be disabled on Windows 10 as well: