You are not logged in.
Pages: 1
When I run
iwctl
station wlan0 scan
station wlan0 get-networks
I see the wifi network I want to connect to and it is using
psk
Security
when I run
station wlan0 connect SSID
where SSID is the Network name I get `Operation failed`
I am able to connect to this network on Windows 11 no problem and this machine is dual booted.
When I run
systemctl --state=running --type=service
I get
that the following services are running
dbus.service
getty@tty1.service
iwd.service
polkit.service
sshd.service
systemd-homed.service
systemd-journald.service
systemd-logind.service
systemd-networkd.service
systemd-resolved.service
systemd-timesyncd.service
systemd-udevd.service
systemd-userdbd.service
user@-.service
when running
journalctl -u iwd.service
I see the log
CMD_SET_CQM failed: Operation note supported
connect event timed out, reason=2
multiple times seemingly for everytime I try to connect
any advice on what to try?
Last edited by jpineapple (2023-08-09 03:27:48)
Offline
1. 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.
2. (if that alone didn't solve it) please post a complete system journal covering a failed attempt to connect, not bits of random excerpts that just show that things failed but provide no hint whatsoever as to why.
Online
thanks so much for your help!
Offline
1. 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.2. (if that alone didn't solve it) please post a complete system journal covering a failed attempt to connect, not bits of random excerpts that just show that things failed but provide no hint whatsoever as to why.
What does Fast Start do that prevents things from working on Linux? (curious)
System Specs:
Intel Core i5-2400 Nvidia GTX 1050ti Logitech G402 Hyperion Fury (Mouse) BestBuy Essentials USB Keyboard
Software Specifications:
Desktop Environment: KDE Plasma Window Manager: KWin Operating System: Arch Linux (btw)
Offline
"Fast start" is just hiberantion in disguise. The system never really shuts down and leaves the HW in an undefined state and your firmware thinks there's a hibernating system.
You effectively try to run two OS at the same time what leads to non-deterministic behavior and esp. the wifi is a very common victim of this.
This has actually nothing to with windows and linux, you could also not run a second windows instance at the time and you can also not hibernate arch and then "boot" fedora or so.
The only problem that's uniquely windows "fast start" is that it's the default behavior and effectively a lie that obfuscates about what's actually happening.
@jpineapple, please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Online
Pages: 1