Can't connect to wireless after failed Windows 10 install

Questions about WIFI networks and devices
Forum rules
Before you post please read how to get help
Post Reply
grandslam12342
Level 1
Level 1
Posts: 6
Joined: Thu Oct 22, 2020 8:53 pm

Can't connect to wireless after failed Windows 10 install

Post by grandslam12342 »

Hello, I am on Linux Mint 19.03. I tried to install Windows 10 on a separate nvme ssd, connected to wifi when prompted, but decided to quit the install after it tried forcing me to link an email or phone number to the account (this is a recent change to the process, there is literally no option to skip this unless you do not set up wifi). When I tried to resintall windows, the same thing happened, so I formatted the ssd. Then windows couldn't install, so I created a partition. Still wouldn't install, so I decided to handle changing the type of partition at a later time and just log back into my main Mint OS.

When I logged in, everything was normal except for the wifi will not detect any networks. The networks are detected and can be connected to by my phone. I tried many searches on many websites for solutions, including this site (https://easylinuxtipsproject.blogspot.c ... i.html#ID1) which I believe installed a backport version and an upstream version. None of these worked.

I am tethered to my phone via usb to get internet now. I greatly appreciate any help you can offer, thanks.
sleeper12
Level 13
Level 13
Posts: 4706
Joined: Thu May 25, 2017 3:22 pm

Re: Can't connect to wireless after failed Windows 10 install

Post by sleeper12 »

Just a guess, is secure boot on? Is so, turn it off. Check:

Code: Select all

 mokutil --sb-state 
grandslam12342
Level 1
Level 1
Posts: 6
Joined: Thu Oct 22, 2020 8:53 pm

Re: Can't connect to wireless after failed Windows 10 install

Post by grandslam12342 »

Thank you for your reply! I entered the code you provided into terminal. It gave me this response:

EFI variables are not supported on this system
sleeper12
Level 13
Level 13
Posts: 4706
Joined: Thu May 25, 2017 3:22 pm

Re: Can't connect to wireless after failed Windows 10 install

Post by sleeper12 »

Ok, not secure boot then. If you post this, it might help others to help you:

Code: Select all

 inxi -Fxxxz && rfkill list 
User avatar
Kadaitcha Man
Level 11
Level 11
Posts: 3605
Joined: Mon Aug 27, 2012 10:17 pm

Re: Can't connect to wireless after failed Windows 10 install

Post by Kadaitcha Man »

grandslam12342 wrote:
Thu Oct 22, 2020 10:05 pm
EFI variables are not supported on this system
When you reply with the terminal output that has been requested, please make sure that you enclose it in code tags [code]output.here[/code]. You'll see the code tags icon </> when you reply. It's difficult to read unformatted terminal output and some of us will just not bother attempting to read it.
Coming to a thread near you: Lots of bragging about my AMD 5950X. Currently delayed due to high demand.
It's pronounced kad-eye-cha, not kada-itcha.
grandslam12342
Level 1
Level 1
Posts: 6
Joined: Thu Oct 22, 2020 8:53 pm

Re: Can't connect to wireless after failed Windows 10 install

Post by grandslam12342 »

Thank you for the helpful advice :)

I noticed the Intel driver on Network device 2 is missing. This is odd because in Driver Manager I see 'backport-iwlwifi-dkms (open-source) version 8324-0ubuntu1~latest~ubuntu18.04.1' There is no other option aside from 'Do not use the device'. The Nvidia driver is listed as well, but irrelevant I think.

Code: Select all

anon@anon-MS-7641:~$ inxi -Fxxxz && rfkill list
System:
  Host: anon-MS-7641 Kernel: 5.4.0-52-generic x86_64 bits: 64 compiler: gcc 
  v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.4 dm: LightDM 1.26.0 
  Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic 
Machine:
  Type: Desktop Mobo: Micro-Star model: MAG X570 TOMAHAWK WIFI (MS-7C84) 
  v: 1.0 serial: <filter> UEFI [Legacy]: American Megatrends v: 1.00 
  date: 04/11/2020 
CPU:
  Topology: 12-Core model: AMD Ryzen 9 3900X bits: 64 type: MT MCP arch: Zen 
  L2 cache: 6144 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 182400 
  Speed: 2201 MHz min/max: 2200/3800 MHz boost: enabled Core speeds (MHz): 
  1: 2199 2: 2199 3: 2200 4: 2200 5: 2195 6: 2190 7: 2191 8: 2192 9: 2199 
  10: 2201 11: 2197 12: 2201 13: 2200 14: 2193 15: 2194 16: 2193 17: 2198 
  18: 2199 19: 2199 20: 2200 21: 2199 22: 2198 23: 2199 24: 2207 
Graphics:
  Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: Gigabyte 
  driver: nvidia v: 450.80.02 bus ID: 2d:00.0 chip ID: 10de:1c82 
  Display: x11 server: X.Org 1.20.8 driver: nvidia 
  unloaded: fbdev,modesetting,nouveau,vesa 
  resolution: 3840x2160~30Hz, 2560x1440~144Hz 
  OpenGL: renderer: GeForce GTX 1050 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 450.80.02 
  direct render: Yes 
Audio:
  Device-1: NVIDIA GP107GL High Definition Audio vendor: Gigabyte 
  driver: snd_hda_intel v: kernel bus ID: 2d:00.1 chip ID: 10de:0fb9 
  Device-2: AMD vendor: Micro-Star MSI driver: snd_hda_intel v: kernel 
  bus ID: 2f:00.4 chip ID: 1022:1487 
  Sound Server: ALSA v: k5.4.0-52-generic 
Network:
  Device-1: Realtek vendor: Micro-Star MSI driver: N/A port: f000 
  bus ID: 26:00.0 chip ID: 10ec:8125 
  Device-2: Intel driver: N/A port: f000 bus ID: 28:00.0 chip ID: 8086:2723 
Drives:
  Local Storage: total: 3.34 TiB used: 758.46 GiB (22.2%) 
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO 1TB size: 931.51 GiB 
  speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: 2B2QEXE7 scheme: MBR 
  ID-2: /dev/sda vendor: Samsung model: HD322HJ size: 298.09 GiB 
  speed: 3.0 Gb/s serial: <filter> rev: 1108 scheme: MBR 
  ID-3: /dev/sdb vendor: Western Digital model: WD3200AAJS-00L7A0 
  size: 298.09 GiB speed: 3.0 Gb/s serial: <filter> rev: 3E01 scheme: MBR 
  ID-4: /dev/sdc vendor: Samsung model: SSD 860 EVO 2TB size: 1.82 TiB 
  speed: 6.0 Gb/s serial: <filter> rev: 3B6Q scheme: MBR 
  ID-5: /dev/sdd type: USB model: USB DISK 3.0 size: 29.30 GiB 
  serial: <filter> rev: PMAP scheme: MBR 
Partition:
  ID-1: / size: 18.21 GiB used: 15.83 GiB (87.0%) fs: ext4 dev: /dev/sdc1 
  ID-2: /home size: 883.98 GiB used: 736.89 GiB (83.4%) fs: ext4 
  dev: /dev/sdc3 
  ID-3: swap-1 size: 5.12 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda4 
  ID-4: swap-2 size: 13.97 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sdc5 
Sensors:
  System Temperatures: cpu: 60.2 C mobo: N/A gpu: nvidia temp: 55 C 
  Fan Speeds (RPM): N/A gpu: nvidia fan: 0% 
Info:
  Processes: 388 Uptime: 6m Memory: 31.37 GiB used: 1.49 GiB (4.8%) 
  Init: systemd v: 237 runlevel: 5 Compilers: gcc: 7.5.0 alt: 7 Shell: bash 
  v: 4.4.20 running in: gnome-terminal inxi: 3.0.32 
0: hci0: Bluetooth
	Soft blocked: yes
	Hard blocked: no
sleeper12
Level 13
Level 13
Posts: 4706
Joined: Thu May 25, 2017 3:22 pm

Re: Can't connect to wireless after failed Windows 10 install

Post by sleeper12 »

While connected with tethering, do:

Code: Select all

 sudo apt install --reinstall backport-iwlwifi-dkms 
Reboot
grandslam12342
Level 1
Level 1
Posts: 6
Joined: Thu Oct 22, 2020 8:53 pm

Re: Can't connect to wireless after failed Windows 10 install

Post by grandslam12342 »

I did what was mentioned, but it did not seem to change anything. Here is the readout after following your instructions:

Code: Select all

anon@anon-MS-7641:~$ inxi -Fxxxz && rfkill list
System:
  Host: anon-MS-7641 Kernel: 5.4.0-52-generic x86_64 bits: 64 compiler: gcc 
  v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.4 dm: LightDM 1.26.0 
  Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic 
Machine:
  Type: Desktop Mobo: Micro-Star model: MAG X570 TOMAHAWK WIFI (MS-7C84) 
  v: 1.0 serial: <filter> UEFI [Legacy]: American Megatrends v: 1.00 
  date: 04/11/2020 
CPU:
  Topology: 12-Core model: AMD Ryzen 9 3900X bits: 64 type: MT MCP arch: Zen 
  L2 cache: 6144 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 182401 
  Speed: 2199 MHz min/max: 2200/3800 MHz boost: enabled Core speeds (MHz): 
  1: 2198 2: 2198 3: 2197 4: 2196 5: 2202 6: 2192 7: 2191 8: 2200 9: 2196 
  10: 2196 11: 1861 12: 1861 13: 2199 14: 2790 15: 2198 16: 2198 17: 2194 
  18: 2200 19: 2196 20: 2196 21: 1869 22: 1866 23: 2795 24: 2203 
Graphics:
  Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: Gigabyte 
  driver: nvidia v: 450.80.02 bus ID: 2d:00.0 chip ID: 10de:1c82 
  Display: x11 server: X.Org 1.20.8 driver: nvidia 
  unloaded: fbdev,modesetting,nouveau,vesa 
  resolution: 3840x2160~30Hz, 2560x1440~144Hz 
  OpenGL: renderer: GeForce GTX 1050 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 450.80.02 
  direct render: Yes 
Audio:
  Device-1: NVIDIA GP107GL High Definition Audio vendor: Gigabyte 
  driver: snd_hda_intel v: kernel bus ID: 2d:00.1 chip ID: 10de:0fb9 
  Device-2: AMD vendor: Micro-Star MSI driver: snd_hda_intel v: kernel 
  bus ID: 2f:00.4 chip ID: 1022:1487 
  Sound Server: ALSA v: k5.4.0-52-generic 
Network:
  Device-1: Realtek vendor: Micro-Star MSI driver: N/A port: f000 
  bus ID: 26:00.0 chip ID: 10ec:8125 
  Device-2: Intel driver: N/A port: f000 bus ID: 28:00.0 chip ID: 8086:2723 
Drives:
  Local Storage: total: 3.34 TiB used: 758.46 GiB (22.2%) 
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO 1TB size: 931.51 GiB 
  speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: 2B2QEXE7 scheme: MBR 
  ID-2: /dev/sda vendor: Samsung model: HD322HJ size: 298.09 GiB 
  speed: 3.0 Gb/s serial: <filter> rev: 1108 scheme: MBR 
  ID-3: /dev/sdb vendor: Western Digital model: WD3200AAJS-00L7A0 
  size: 298.09 GiB speed: 3.0 Gb/s serial: <filter> rev: 3E01 scheme: MBR 
  ID-4: /dev/sdc vendor: Samsung model: SSD 860 EVO 2TB size: 1.82 TiB 
  speed: 6.0 Gb/s serial: <filter> rev: 3B6Q scheme: MBR 
  ID-5: /dev/sdd type: USB model: USB DISK 3.0 size: 29.30 GiB 
  serial: <filter> rev: PMAP scheme: MBR 
Partition:
  ID-1: / size: 18.21 GiB used: 15.83 GiB (87.0%) fs: ext4 dev: /dev/sdc1 
  ID-2: /home size: 883.98 GiB used: 736.89 GiB (83.4%) fs: ext4 
  dev: /dev/sdc3 
  ID-3: swap-1 size: 13.97 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sdc5 
  ID-4: swap-2 size: 5.12 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda4 
Sensors:
  System Temperatures: cpu: 61.9 C mobo: N/A gpu: nvidia temp: 54 C 
  Fan Speeds (RPM): N/A gpu: nvidia fan: 0% 
Info:
  Processes: 425 Uptime: 2m Memory: 31.37 GiB used: 914.4 MiB (2.8%) 
  Init: systemd v: 237 runlevel: 5 Compilers: gcc: 7.5.0 alt: 7 Shell: bash 
  v: 4.4.20 running in: gnome-terminal inxi: 3.0.32 
0: hci0: Bluetooth
	Soft blocked: yes
	Hard blocked: no
Driver Manager shows 'backport-iwlwifi-dkms (open-source) Version 8324-0ubuntu1~latest~ubuntu18.04.1'. I want to mention that Bluetooth is functional, so the wifi card itself doesn't seem to be an issue. Thank you for your help!
sleeper12
Level 13
Level 13
Posts: 4706
Joined: Thu May 25, 2017 3:22 pm

Re: Can't connect to wireless after failed Windows 10 install

Post by sleeper12 »

What does this show:

Code: Select all

 lspci -nnk | grep -iA3 net 
grandslam12342
Level 1
Level 1
Posts: 6
Joined: Thu Oct 22, 2020 8:53 pm

Re: Can't connect to wireless after failed Windows 10 install

Post by grandslam12342 »

Code: Select all

anon@anon-MS-7641:~$ lspci -nnk | grep -iA3 net
26:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. Device [10ec:8125] (rev 04)
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7c84]
	Kernel modules: r8169
28:00.0 Network controller [0280]: Intel Corporation Device [8086:2723] (rev 1a)
	Subsystem: Intel Corporation Device [8086:0084]
	Kernel modules: iwlwifi
2a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device [1022:1485]
Thanks for your help! I'm wondering if maybe a clean install is in order, or if that is too drastic?
User avatar
Larry78723
Level 10
Level 10
Posts: 3027
Joined: Wed Jan 09, 2019 7:01 pm
Location: Jasper County, SC, USA

Re: Can't connect to wireless after failed Windows 10 install

Post by Larry78723 »

The below is quoted from the Intel website https://wireless.wiki.kernel.org/en/use ... rs/iwlwifi
If you have a dual-boot machine with a recent version of Windows and start seeing problems during initialization of the WiFi device when booting Linux, the problem could be due to the “fast startup” feature on Windows.

With this feature enabled, Windows don't really shut down the entire system, but leaves things partially running so you can start the machine faster again. Try to disable this option, on Windows 10 it should be in “Control Panel→Hardware and Sound→Power Options→System Settings”, then disable the “Fast Startup” option in “Shutdown Settings”. This will cause Windows to fully shutdown and may solve the issue.
Could the failed install be causing the problem?

Also, have a look at the firmware section, about 2/3 down the page.


NOTE: If you want windows on that machine, it must be installed before LM.
Image
sleeper12
Level 13
Level 13
Posts: 4706
Joined: Thu May 25, 2017 3:22 pm

Re: Can't connect to wireless after failed Windows 10 install

Post by sleeper12 »

You can also try:

Code: Select all

 sudo modprobe iwlwifi 
grandslam12342
Level 1
Level 1
Posts: 6
Joined: Thu Oct 22, 2020 8:53 pm

Re: Can't connect to wireless after failed Windows 10 install

Post by grandslam12342 »

To sleeper: I put the code into terminal. After entering my password, my wifi did not seem to be enabled, and no output was produced.

To larry: I was not able to fully install windows, so I cannot check those settings. I did delete whatever was partially installed of windows by formatting the nvme drive (several times, still cannot get this working right). Could those options be found under the MSI Bios settings?

I tried to download and install the firmware listed in the section you mentioned. I may have not done it correctly, but I did not see any changes after I did so.

Do I need to install windows first if I am not dual booting on the same SSD? Mint is on a physically different SSD.

Thanks for the replies!
User avatar
Larry78723
Level 10
Level 10
Posts: 3027
Joined: Wed Jan 09, 2019 7:01 pm
Location: Jasper County, SC, USA

Re: Can't connect to wireless after failed Windows 10 install

Post by Larry78723 »

My understanding is that in order to dual boot, windows10 needs to be installed first if you're installing in UEFI mode. That may not be true, I don't dual boot. Someone who does should really answer that question.
Image
cretsiah
Level 2
Level 2
Posts: 60
Joined: Wed Jul 22, 2020 5:44 am

Re: Can't connect to wireless after failed Windows 10 install

Post by cretsiah »

Do I need to install windows first if I am not dual booting on the same SSD? Mint is on a physically different SSD.
this might depend on how you are accessing the disks to boot

1) using grub to select os to boot(doesnt matter if on different disks)
2) via the bios boot options (in my case F12)

in the case of option 2, you would generally want to have other os booting drives disconnected during the install of each individual OS.

however that shouldnt affect wifi unless windows has become even more insufferable with the "we will take ownership of your seperately purchased gear " attitude.

I know win10 is nasty because it even likes to upset win7 / win10 dual boots. even with fast startup turned off. no joke i would have to boot into win10, sometimes do nothing, sometimes do an update just so i could stop win7 from crashing..... the problem is on that system win10 was buggy at best, kept losing graphics card drivers for crying out loud and the only way to fix that was to boot into win7 FFS....

i also noticed you appeared to be running MBR setups, so was wondering when you said you formatted the drives you also formatted MBR?
Post Reply

Return to “Wireless”