#asahi-dev · 2024-08-05 11:51
thasti^ignore#asahi-dev · 2024-08-05 11:49
thastiMikisu03#asahi-dev · 2023-01-22 21:12
thastifixed the USB ethernet dongles by shortening the wires between the USB-C cable pigtail and the PCB... now works reliably#asahi-dev · 2023-01-22 19:30
thastiyep, best guess it's just a marginal design (they were free, I probably know the reason why now...)#asahi-dev · 2023-01-22 19:26
thastii can get them to appear sometimes with the same kind of trick, but without that they don't show up#asahi-dev · 2023-01-22 19:25
thastiokay, got it to boot. turns out the dongles don't really work under macOS either#asahi-dev · 2023-01-22 19:12
thasti.. turns out macOS actually doesn't boot any longer (telling me it needs to be reinstalled)#asahi-dev · 2023-01-22 19:03
thastithis I haven't tried yet (haven't booted back into macos since I installed asahi on here)#asahi-dev · 2023-01-22 19:02
thastibut if their design was bad, that would of course to be expected :)#asahi-dev · 2023-01-22 19:02
thastii at least two have two such devices (same model, both new out of box), and both of them behave exactly the same#asahi-dev · 2023-01-22 19:00
thastiI only have one other machine to test, but it seemed to work fine there. I should be able to test another machine or two at work tomorrow #asahi-dev · 2023-01-22 18:47
thasticould that be caused by some USB-PHY setting, making the link not come up properly due to marginal signal integrity without my finger on the PCB?#asahi-dev · 2023-01-22 18:46
thastihaving an interesting issue here (m2 air, on -edge): I'm trying to use an USB-C ethernet dongle. I can only get it to enumerate reliably by placing a finger on top of the USB traces on its PCB. Without doing that, it never enumerates (and I get repeated 'Cannot enable. Maybe the USB cable is bad?' or 'config error' messages in dmesg)#asahi-dev · 2022-12-05 13:29
thastiWPA enterprise*#asahi-dev · 2022-12-05 13:29
thastimarcan: thanks, I confirm WPA3 works fine now!#asahi-dev · 2022-12-05 10:33
thastion a different note: for another (unencrypted) network, I'm getting 'brcmf_set_key_mgmt: invalid akm suite (1027090)' + 'brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)'#asahi-dev · 2022-12-05 10:17
thastineither networkmanager nor iwd are very explicit with their error messages, so that turned out to be quite the rabbit hole...#asahi-dev · 2022-12-05 10:16
thasti:)#asahi-dev · 2022-12-05 10:16
thastiyup... https://wiki.archlinux.org/title/iwd#Error_loading_client_private_key#asahi-dev · 2022-12-05 10:13
thastiany chance we can get CONFIG_PKCS8_PRIVATE_KEY_PARSER enabled in future kernel releases? I fail to connect to eduroam (wpa enterprise network) since iwd can't read private keys without the pkcs8_key_parser module..#asahi-dev · 2022-12-04 19:02
thastismoke test passed on M2 MBA :)#asahi-dev · 2022-10-29 14:34
thastithanks jannau - thought so. looks like this cw2015 driver (and in turn i3status) is broken instead.#asahi-dev · 2022-10-29 14:29
thastioh no, it's only the cw2015, the bq27xxx also does it in seconds. great#asahi-dev · 2022-10-29 14:25
thastitwo random kernel drivers I just checked (bq27xxx and cw2015) return it in minutes #asahi-dev · 2022-10-29 14:17
thasti(looking at macsmc_power.c): is it actually correct that POWER_SUPPLY_PROP_TIME_TO_EMPTY_NOW is returned in seconds, as opposed to minutes? i'm seeing in asahi that i3status tries to interpret this uevent property as minutes...