Unable to setup wifi on Surface Book 2

JeffDziad · 2022-09-08 02:36:06

Hello,

Just installed arch on my Surface Book 2 and am trying to get connected to the internet. I dont have access to a ethernet port and have only been able to install packages by chrooting from a live usb after setting up a wifi connection using iwctl. Since I have a Marvell wifi device, I installed linux-firmware-marvell in adittion to linux-firmware to try to fix the issue but with no success. Before installing linux-firmware-marvell, 'ip link' only show 'lo', but after installation includes 'mlan0' which I assume to be my wireless interface.

Here are the versions of firmware I am using:
linux-firmware 20220815.8413c63-1
linux-firmware-marvell 20220815.8413c63-1

lspci -k output:

00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 08)
        Subsystem: Intel Corporation Device 2015
        Kernel driver in use: skl_uncore
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07)
        Subsystem: Microsoft Corporation Device 0028
        Kernel driver in use: i915
        Kernel modules: i915
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 08)
        Subsystem: Intel Corporation Device 2015
        Kernel driver in use: proc_thermal
        Kernel modules: processor_thermal_device_pci_legacy
00:05.0 Multimedia controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Imaging Unit (rev 01)
        Subsystem: Intel Corporation Device 2015
        Kernel driver in use: ipu3-imgu
        Kernel modules: ipu3_imgu
00:13.0 Non-VGA unclassified device: Intel Corporation Sunrise Point-LP Integrated Sensor Hub (rev 21)
        Subsystem: Intel Corporation Device 7270
        Kernel driver in use: intel_ish_ipc
        Kernel modules: intel_ish_ipc
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
        Subsystem: Intel Corporation Device 7270
        Kernel driver in use: xhci_hcd
        Kernel modules: xhci_pci
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
        Subsystem: Intel Corporation Device 7270
        Kernel driver in use: intel_pch_thermal
        Kernel modules: intel_pch_thermal
00:14.3 Multimedia controller: Intel Corporation CSI-2 Host Controller (rev 01)
        Subsystem: Intel Corporation Device 7270
        Kernel driver in use: ipu3-cio2
        Kernel modules: ipu3_cio2
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21)
        Subsystem: Intel Corporation Device 7270
        Kernel driver in use: intel-lpss
        Kernel modules: intel_lpss_pci
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21)
        Subsystem: Intel Corporation Device 7270
        Kernel driver in use: intel-lpss
        Kernel modules: intel_lpss_pci
00:15.2 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #2 (rev 21)
        Subsystem: Intel Corporation Device 7270
        Kernel driver in use: intel-lpss
        Kernel modules: intel_lpss_pci
00:15.3 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #3 (rev 21)
        Subsystem: Intel Corporation Device 7270
        Kernel driver in use: intel-lpss
        Kernel modules: intel_lpss_pci
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
        Subsystem: Intel Corporation Device 7270
        Kernel driver in use: mei_me
        Kernel modules: mei_me
00:16.4 Communication controller: Intel Corporation iTouch Controller (rev 21)
        Kernel driver in use: mei_me
        Kernel modules: mei_me
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1)
        Subsystem: Intel Corporation Device 7270
        Kernel driver in use: pcieport
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1)
        Subsystem: Intel Corporation Device 7270
        Kernel driver in use: pcieport
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1)
        Subsystem: Intel Corporation Device 7270
        Kernel driver in use: pcieport
00:1e.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO UART Controller #0 (rev 21)
        Subsystem: Intel Corporation Device 7270
        Kernel driver in use: intel-lpss
        Kernel modules: intel_lpss_pci
00:1f.0 ISA bridge: Intel Corporation Sunrise Point LPC Controller/eSPI Controller (rev 21)
        Subsystem: Intel Corporation Device 7270
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
        Subsystem: Intel Corporation Device 7270
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
        Subsystem: Intel Corporation Device 7270
        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_hda_intel, snd_soc_skl, snd_soc_avs
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
        Subsystem: Intel Corporation Device 7270
        Kernel driver in use: i801_smbus
        Kernel modules: i2c_i801
01:00.0 Ethernet controller: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac Wireless
        Subsystem: Device 0007:045e
        Kernel driver in use: mwifiex_pcie
        Kernel modules: mwifiex_pcie
02:00.0 3D controller: NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] (rev a1)
        Subsystem: Microsoft Corporation Device 0024
        Kernel driver in use: nouveau
        Kernel modules: nouveau
03:00.0 Non-Volatile memory controller: SK hynix PC401 NVMe Solid State Drive 256GB
        Subsystem: SK hynix PC401 NVMe Solid State Drive 256GB
        Kernel driver in use: nvme
        Kernel modules: nvme

ip link output:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: mlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 70:bc:10:65:ec:89 brd ff:ff:ff:ff:ff:ff

dmesg | grep wifi output:

[    3.289569] mwifiex_pcie 0000:01:00.0: quirk reset_d3cold enabled
[    3.289672] mwifiex_pcie 0000:01:00.0: enabling device (0000 -> 0002)
[    3.289924] mwifiex_pcie: PCI memory map Virt0: 0000000088628830 PCI memory map Virt2: 00000000f67804cc
[    4.671857] mwifiex_pcie 0000:01:00.0: info: FW download over, size 723540 bytes
[    5.632377] mwifiex_pcie 0000:01:00.0: WLAN FW is active
[    5.765293] mwifiex_pcie 0000:01:00.0: info: MWIFIEX VERSION: mwifiex 1.0 (15.68.19.p21)
[    5.765296] mwifiex_pcie 0000:01:00.0: driver_version = mwifiex 1.0 (15.68.19.p21)

Let me know if I need to provide more information and I'll do it as fast as I can. My ultimate goal is to be able to connect to wifi and bluetooth devices using the gui, however, being a newbie is making that rather difficult. And to be extra clear, I just want to get wifi working on my device. I gave up on attempting to setup the gui side of things in hopes of trying to get my wireless interface to be recognized by arch.

Thanks much

loqs · 2022-09-08 02:43:34

After mlan0 appeared were you able to discover any access points using it?

JeffDziad · 2022-09-08 02:50:27

loqs wrote:

After mlan0 appeared were you able to discover any access points using it?

doing iw dev mlan0 scan | less gives me an empty output

Last edited by JeffDziad (2022-09-08 02:50:54)

loqs · 2022-09-08 02:56:41

Does `iw dev` produce any output?

Trilby · 2022-09-08 02:59:49

Networking works in the live usb? If so, check what kernel drivers are in use for the wireless card in that environment.

JeffDziad · 2022-09-08 03:01:47

loqs wrote:

Does `iw dev` produce any output?

iw dev outputs bash: iw: command not found

loqs · 2022-09-08 03:15:14

Which network manager were you planning on using? Without iw installed another tool will be needed to see if any access points are detected and it will be easiest to use whatever tool you plan on using.

Last edited by loqs (2022-09-08 03:15:30)

JeffDziad · 2022-09-08 03:27:52

Trilby wrote:

Networking works in the live usb? If so, check what kernel drivers are in use for the wireless card in that environment.

I was able to setup wifi using iwctl in the live environment. I tried doing lsmod to see what modules are being used but I can only see maybe half of the output since the rest goes off the screen.

Live Environment lsmod (not complete)
https://img.onl/bJ5Zr6

Installed Environment lsmod (complete)

Module                  Size  Used by
snd_seq_dummy          16384  0
snd_hrtimer            16384  1
snd_seq                94208  7 snd_seq_dummy
snd_seq_device         16384  1 snd_seq
btusb                  65536  0
btrtl                  28672  1 btusb
btbcm                  24576  1 btusb
btintel                45056  1 btusb
btmtk                  16384  1 btusb
bluetooth             876544  6 btrtl,btmtk,btintel,btbcm,btusb
ecdh_generic           16384  1 bluetooth
snd_soc_avs           172032  0
snd_soc_skl           217088  0
snd_soc_hdac_hda       28672  1 snd_soc_skl
snd_hda_ext_core       36864  3 snd_soc_avs,snd_soc_hdac_hda,snd_soc_skl
joydev                 28672  0
mousedev               24576  0
snd_soc_sst_ipc        20480  1 snd_soc_skl
snd_soc_sst_dsp        40960  1 snd_soc_skl
snd_soc_acpi_intel_match    69632  1 snd_soc_skl
snd_soc_acpi           16384  2 snd_soc_acpi_intel_match,snd_soc_skl
snd_hda_codec_hdmi     86016  1
intel_tcc_cooling      16384  0
snd_soc_core          393216  3 snd_soc_avs,snd_soc_hdac_hda,snd_soc_skl
hid_sensor_gyro_3d     20480  0
hid_sensor_accel_3d    20480  0
hid_sensor_rotation    20480  0
x86_pkg_temp_thermal    20480  0
hid_sensor_als         20480  0
intel_powerclamp       20480  0
snd_hda_codec_realtek   167936  1
snd_compress           28672  1 snd_soc_core
coretemp               20480  0
ac97_bus               16384  1 snd_soc_core
hid_sensor_trigger     20480  9 hid_sensor_gyro_3d,hid_sensor_als,hid_sensor_accel_3d,hid_sensor_rotation
snd_pcm_dmaengine      16384  1 snd_soc_core
industrialio_triggered_buffer    16384  1 hid_sensor_trigger
snd_hda_codec_generic    98304  1 snd_hda_codec_realtek
kfifo_buf              16384  1 industrialio_triggered_buffer
hid_sensor_iio_common    20480  5 hid_sensor_gyro_3d,hid_sensor_trigger,hid_sensor_als,hid_sensor_accel_3d,hid_sensor_rotation
ledtrig_audio          16384  1 snd_hda_codec_generic
industrialio          106496  7 industrialio_triggered_buffer,hid_sensor_gyro_3d,hid_sensor_trigger,kfifo_buf,hid_sensor_als,hid_sensor_accel_3d,hid_sensor_rotation
kvm_intel             385024  0
snd_hda_intel          61440  4
iTCO_wdt               16384  0
hid_sensor_hub         32768  6 hid_sensor_gyro_3d,hid_sensor_trigger,hid_sensor_iio_common,hid_sensor_als,hid_sensor_accel_3d,hid_sensor_rotation
surface_platform_profile    16384  0
snd_intel_dspcfg       36864  3 snd_soc_avs,snd_hda_intel,snd_soc_skl
intel_pmc_bxt          16384  1 iTCO_wdt
kvm                  1130496  1 kvm_intel
hid_multitouch         32768  0
irqbypass              16384  1 kvm
platform_profile       16384  1 surface_platform_profile
crct10dif_pclmul       16384  1
intel_ishtp_hid        28672  0
crc32_pclmul           16384  0
snd_intel_sdw_acpi     20480  1 snd_intel_dspcfg
mac_hid                16384  0
iTCO_vendor_support    16384  1 iTCO_wdt
8250_dw                24576  0
mei_pxp                20480  0
mei_hdcp               24576  0
usbhid                 73728  0
intel_rapl_msr         20480  0
nouveau              2768896  1
ghash_clmulni_intel    16384  0
snd_hda_codec         188416  6 snd_hda_codec_generic,snd_soc_avs,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek,snd_soc_hdac_hda
mwifiex_pcie           57344  0
aesni_intel           380928  0
snd_hda_core          118784  9 snd_hda_codec_generic,snd_soc_avs,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_hda_codec_realtek,snd_soc_hdac_hda,snd_soc_skl
crypto_simd            16384  1 aesni_intel
snd_hwdep              16384  1 snd_hda_codec
gpio_keys              24576  0
i915                 3121152  39
surface_gpe            20480  0
cryptd                 28672  2 crypto_simd,ghash_clmulni_intel
mwifiex               339968  1 mwifiex_pcie
mxm_wmi                16384  1 nouveau
snd_pcm               172032  11 snd_soc_avs,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_compress,snd_soc_core,snd_soc_skl,snd_hda_core,snd_pcm_dmaengine
rapl                   16384  0
wmi                    45056  2 mxm_wmi,nouveau
snd_timer              49152  3 snd_seq,snd_hrtimer,snd_pcm
processor_thermal_device_pci_legacy    16384  0
drm_ttm_helper         16384  1 nouveau
intel_cstate           20480  0
ipu3_cio2              57344  0
drm_buddy              20480  1 i915
processor_thermal_device    20480  1 processor_thermal_device_pci_legacy
ipu3_imgu             241664  0
i2c_i801               45056  0
snd                   126976  20 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_compress,snd_soc_core,snd_pcm
cfg80211             1089536  1 mwifiex
ttm                    94208  3 drm_ttm_helper,i915,nouveau
intel_uncore          217088  0
videobuf2_dma_sg       20480  2 ipu3_cio2,ipu3_imgu
processor_thermal_rfim    16384  1 processor_thermal_device
intel_lpss_pci         28672  2
pcspkr                 16384  0
i2c_smbus              20480  1 i2c_i801
soundcore              16384  1 snd
mei_me                 53248  2
processor_thermal_mbox    16384  2 processor_thermal_rfim,processor_thermal_device
atomisp_gmin_platform    40960  0
videobuf2_memops       20480  1 videobuf2_dma_sg
intel_lpss             16384  1 intel_lpss_pci
drm_display_helper    180224  2 i915,nouveau
intel_xhci_usb_role_switch    16384  0
intel_ish_ipc          32768  0
videobuf2_v4l2         40960  2 ipu3_cio2,ipu3_imgu
rfkill                 32768  5 bluetooth,cfg80211
ov8865                 40960  1
ov5693                 28672  1
mei                   172032  5 mei_hdcp,mei_pxp,mei_me
roles                  16384  1 intel_xhci_usb_role_switch
intel_pch_thermal      20480  0
idma64                 20480  0
ov7251                 36864  0
processor_thermal_rapl    20480  1 processor_thermal_device
cec                    81920  2 drm_display_helper,i915
intel_ishtp            69632  2 intel_ishtp_hid,intel_ish_ipc
v4l2_fwnode            32768  4 ipu3_cio2,ov7251,ov5693,ov8865
intel_rapl_common      32768  2 intel_rapl_msr,processor_thermal_rapl
videobuf2_common       86016  5 ipu3_cio2,videobuf2_v4l2,videobuf2_dma_sg,ipu3_imgu,videobuf2_memops
vfat                   24576  1
intel_skl_int3472_tps68470    20480  0
intel_soc_dts_iosf     20480  1 processor_thermal_device_pci_legacy
intel_gtt              28672  1 i915
v4l2_async             32768  5 v4l2_fwnode,ipu3_cio2,ov7251,ov5693,ov8865
tps68470_regulator     16384  0
videodev              307200  8 v4l2_async,ipu3_cio2,ov7251,videobuf2_v4l2,ov5693,videobuf2_common,ov8865,ipu3_imgu
clk_tps68470           16384  0
fat                    98304  1 vfat
mc                     69632  9 v4l2_async,videodev,ipu3_cio2,ov7251,videobuf2_v4l2,ov5693,videobuf2_common,ov8865,ipu3_imgu
intel_skl_int3472_discrete    20480  0
surfacepro3_button     20480  0
surface_dtx            28672  0
surface_aggregator_registry    16384  0
video                  61440  2 i915,nouveau
surface_acpi_notify    24576  0
surface_hotplug        20480  0
int3400_thermal        20480  0
int3403_thermal        20480  0
surface_aggregator    163840  4 surface_acpi_notify,surface_dtx,surface_platform_profile,surface_aggregator_registry
soc_button_array       20480  0
acpi_tad               20480  0
acpi_thermal_rel       16384  1 int3400_thermal
int340x_thermal_zone    20480  2 int3403_thermal,processor_thermal_device
dptf_power             16384  0
acpi_pad               24576  0
lzo_rle                16384  8
pkcs8_key_parser       16384  0
crypto_user            24576  0
fuse                  176128  1
zram                   45056  2
bpf_preload            24576  0
ip_tables              36864  0
x_tables               57344  1 ip_tables
ext4                 1015808  1
crc32c_generic         16384  0
crc16                  16384  2 bluetooth,ext4
mbcache                16384  1 ext4
jbd2                  188416  1 ext4
nvme                   61440  2
crc32c_intel           24576  2
nvme_core             180224  3 nvme
xhci_pci               20480  0
xhci_pci_renesas       24576  1 xhci_pci

Any idea how to view all of lsmod on live environment?

loqs · 2022-09-08 03:30:46

What happens when you use iwctl from the installed system after mlan0 appeared?

JeffDziad · 2022-09-08 03:31:45

loqs wrote:

Which network manager were you planning on using? Without iw installed another tool will be needed to see if any access points are detected and it will be easiest to use whatever tool you plan on using.

I was planning on using plasma-nm that I found here --> https://wiki.archlinux.org/title/Networ … KDE_Plasma. I assume that it was graphical since it mentions adding it as a widget to the taskbar. I guess it wouldn't hurt to get that installed.

Trilby · 2022-09-08 03:32:29

You can use a pager (e.g., `less`) but looking at lsmod is the wrong approach. `lspci -k` as in your first post shows which module is in use. My question was which modules is used by the wireless hardware in the live usb system (or if that's what we saw in post #1, what is listed in the installed system).

JeffDziad · 2022-09-08 03:42:56

loqs wrote:

What happens when you use iwctl from the installed system after mlan0 appeared?

My god, I tried that before and it hung on "Waiting for IWD to start...." and I assumed that something was amiss. I just realized that I have to enable and start iwd through systemctl. I'm now able to see networks and try to connect to them but it appears its getting stuck at connecting.

station wlan0 show in iwctl outputs this:

[iwd]# station wlan0 show
                                 Station: wlan0                               *
--------------------------------------------------------------------------------
  Settable  Property              Value
--------------------------------------------------------------------------------
            Scanning              no
            State                 connecting
            Connected network     My-Home-SSID
            No IP addresses       Is DHCP client configured?

JeffDziad · 2022-09-08 03:50:14

Trilby wrote:

You can use a pager (e.g., `less`) but looking at lsmod is the wrong approach. `lspci -k` as in your first post shows which module is in use. My question was which modules is used by the wireless hardware in the live usb system (or if that's what we saw in post #1, what is listed in the installed system).

I see, my bad. Post #1 is my installed environment and not my live.

lspci -k on my live gives me this:
https://img.onl/Pr4cxB

which looks the same for the most part as my first post. however, I cannot be sure since I can only see the bottom portion of the output.

Slithery · 2022-09-08 05:52:14

You can upload the full output of a command by using a pastebin service.

Trilby · 2022-09-08 12:48:36

Yes, the same kernel driver is in use - so the driver is not the issue, just the (mis)use of the connection tools is. If your wireless interface is indeed called mlan0 then running iwctl to connect to wlan0 will not get you anywhere.

Perhaps there was a udev rule or similar on the iso that renames mlan devices to wlan names; but in any case, you'd need to do a similar renaming, or connect to mlan0.

Last edited by Trilby (2022-09-08 12:49:54)

JeffDziad · 2022-09-08 22:25:30

Trilby wrote:

Yes, the same kernel driver is in use - so the driver is not the issue, just the (mis)use of the connection tools is. If your wireless interface is indeed called mlan0 then running iwctl to connect to wlan0 will not get you anywhere.
Perhaps there was a udev rule or similar on the iso that renames mlan devices to wlan names; but in any case, you'd need to do a similar renaming, or connect to mlan0.

This sounded like great advice. However when I ran ip a in my terminal I got this back:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 70:bc:10:65:ec:89 brd ff:ff:ff:ff:ff:ff

It seems that my wifi interface is now named wlan0. The only thing I did between yesterday and today was start and enable systemd-resolved and iwd.service service's. I tried connecting through iwctl again but I'm still stuck at connecting. I found this out by trying to temporarily rename my wifi interface using this command: ip link set mlan0 name wlan0, but it errored saying that mlan0 was not found. Am I missing something here?? Would creating a new udev rule at /etc/udev/rules.d be a better way to find out if something is amiss?

loqs · 2022-09-08 22:29:23

Any output in the journal related to the connection attempt?

JeffDziad · 2022-09-08 22:41:00

loqs wrote:

Any output in the journal related to the connection attempt?

I didn't see anything in journalctl -b regarding wifi. But I tried to use iwctl again and now I'm able to connect to home wifi. I don't know exactly what fixed this since my wifi interface just magically started showing up as wlan0. But I do know I enabled and started systemd-resolved and iwd.service service's so Im just guessing that was my issue. I'm going to try to get plasma-nm to work so I can have a gui way of connecting to wifi instead of using iwctl everytime I want to connect to wifi.

Trilby · 2022-09-08 22:41:35

JeffDziad wrote:

The only thing I did between yesterday and today was start and enable systemd-resolved and iwd.service service's.

I suspect you also installed iwd which would account for the change in interface name. Iwd disables the so-called "predictable" interface naming of systemd which changes the reliably predictable kernel name of wlan0 into any number of other interface name strings. In your hardware's case, it would seem systemd was renaming it mlan0 - but iwd is now preventing that rename, so you are back at wlan0 as seen in your ip output.

JeffDziad wrote:

I found this out by trying to temporarily rename my wifi interface using this command: ip link set mlan0 name wlan0, but it errored saying that mlan0 was not found. Am I missing something here?? Would creating a new udev rule at /etc/udev/rules.d be a better way to find out if something is amiss?

No, nevermind all the naming issues - that was a red herring: my apologies. With iwd installed, you are back to working with wlan0. The only requirement is that when you try to connect with any networking tool you must connect to the interface as it is displayed in `ip a` output. Previously you tried to connect to wlan0 when the interface name was mlan0, but that's no longer an issue.

JeffDziad · 2022-09-09 02:48:44

Unfortunately, I'm now having other bizarre issues with iwd. I restarted my laptop to see if I was still able to connect to the internet automatically, and I was. However, some sites do not load and I get "Hmm. We're having trouble finding that site" in firefox. I'm still able to access sites like googe.com and archlinux.com, but other sites just wont load and it makes me think something is wrong with DNS. Additionally, a very small but weird thing I noticed is that when I check my known-networks in iwctl, my last connection date-time is a day ahead. Don't know if that is a clue or not, just thought it was curious given how glitchy everything feels.

I should also add that when sleeping and waking my device, my connection gets severed and I have to manually connect to the network using iwctl. However, when I restart, my connection get automatically established.

Last edited by JeffDziad (2022-09-09 02:52:11)

Arch Linux

#1 2022-09-08 02:36:06

Unable to setup wifi on Surface Book 2

#2 2022-09-08 02:43:34

Re: Unable to setup wifi on Surface Book 2

#3 2022-09-08 02:50:27

Re: Unable to setup wifi on Surface Book 2

#4 2022-09-08 02:56:41

Re: Unable to setup wifi on Surface Book 2

#5 2022-09-08 02:59:49

Re: Unable to setup wifi on Surface Book 2

#6 2022-09-08 03:01:47

Re: Unable to setup wifi on Surface Book 2

#7 2022-09-08 03:15:14

Re: Unable to setup wifi on Surface Book 2

#8 2022-09-08 03:27:52

Re: Unable to setup wifi on Surface Book 2

#9 2022-09-08 03:30:46

Re: Unable to setup wifi on Surface Book 2

#10 2022-09-08 03:31:45

Re: Unable to setup wifi on Surface Book 2

#11 2022-09-08 03:32:29

Re: Unable to setup wifi on Surface Book 2

#12 2022-09-08 03:42:56

Re: Unable to setup wifi on Surface Book 2

#13 2022-09-08 03:50:14

Re: Unable to setup wifi on Surface Book 2

#14 2022-09-08 05:52:14

Re: Unable to setup wifi on Surface Book 2

#15 2022-09-08 12:48:36

Re: Unable to setup wifi on Surface Book 2

#16 2022-09-08 22:25:30

Re: Unable to setup wifi on Surface Book 2

#17 2022-09-08 22:29:23

Re: Unable to setup wifi on Surface Book 2

#18 2022-09-08 22:41:00

Re: Unable to setup wifi on Surface Book 2

#19 2022-09-08 22:41:35

Re: Unable to setup wifi on Surface Book 2

#20 2022-09-09 02:48:44

Re: Unable to setup wifi on Surface Book 2

Board footer