#asahi · 2024-02-04 02:02
chadmedyou need to set EXPERT=1 on the installer. you will not get any support for broken stuff. #asahi · 2024-02-04 02:01
chadmedderek_: you can but its deprecated and does not currently receive asahi package updates #asahi · 2024-02-03 13:50
chadmedbut it should work regardless#asahi · 2024-02-03 13:50
chadmedi personally cant stand tap to click so i dont use it #asahi · 2024-02-03 13:44
chadmedalso did you restart your session#asahi · 2024-02-03 13:40
chadmedim pretty sure the driver/touchpad firmware sends a click event itself anyway, which means we need to implement the functionality to change the trackpad's idea of that threshold#asahi · 2024-02-03 13:39
chadmedwe need to work on that#asahi · 2024-02-03 13:39
chadmedlibinput has some vestigial support for so-called clickpads but its immature and not exposed in any DE yet#asahi · 2024-02-03 13:39
chadmedit cant be changed and has nothing to do with that libinput attribute#asahi · 2024-02-03 13:38
chadmedyeah this is what im trying to get at #asahi · 2024-02-03 13:35
chadmedis a click actually being registered at the "wrong" threshold? #asahi · 2024-02-03 13:30
chadmedi dont think changing the haptic is actually implemented yet #asahi · 2024-02-03 13:30
chadmedalso please check that the click is actually registered by libinput as a mouse click and not just the haptic#asahi · 2024-02-03 13:29
chadmeddid you trigger a reload of udev? #asahi · 2024-02-03 13:09
chadmedits not going to be dmi because these machines dont have dmi #asahi · 2024-02-03 13:05
chadmedsorry i misinterpreted what you were trying to do #asahi · 2024-02-03 13:05
chadmedoh actually it should#asahi · 2024-02-03 13:03
chadmedthe driver does not support this yet #asahi · 2024-02-02 12:20
chadmedin both cases it was just the lcd that cracked#asahi · 2024-02-02 12:20
chadmedthere was no externally visible damage so they just put it down as a defect covered under australian consumer law#asahi · 2024-02-02 12:19
chadmedi was a student at the time for both of them so they just replaced them #asahi · 2024-02-02 12:17
chadmedive not had a single apple device actually just outright fail#asahi · 2024-02-02 12:16
chadmedPaulFerster: fwiw one of the devices i needed replacing was because i dropped a 25kg dumbbell on it, and the other was because i stepped on it#asahi · 2024-02-02 11:06
chadmedtheyve replaced two of my devices for free no questions asked outside of their warranty periods even#asahi · 2024-02-02 11:06
chadmeddepends on the country but apple are _usually_ really good about this outside the US #asahi · 2024-01-31 20:56
chadmednicolas17: havent really measured it, its probably inconsequential though#asahi · 2024-01-30 12:38
chadmedmcgoe: after crunching for like 5 months to get FAR out the door folks are quite understandably a bit tired. stuff is constantly happening though and no ones going anywhere :) #asahi · 2024-01-28 00:28
chadmedplease just use 5ghz wifi in the meantime#asahi · 2024-01-28 00:28
chadmedtheres no point reporting the issue, its been reported scores of times #asahi · 2024-01-28 00:28
chadmedbt coex has been broken forever and we know about it#asahi · 2024-01-25 07:03
chadmedi assume theres a race between resetting the volume to 1.0 and setting the plugin control ports#asahi · 2024-01-25 07:03
chadmedthe problem is it _also_ does change the channel volume but then reset it to 1.0 after its done#asahi · 2024-01-25 07:02
chadmedit basically just says when a client tries to change the volume of the sink, check if the volume controls are mapped to a plugin control port and pass the value to that#asahi · 2024-01-25 07:01
chadmedi dont really understand that code its a clusterfuck of a kludge and probably racy or something#asahi · 2024-01-25 07:01
chadmedcould be something up with the equal loudness volume remapping thing wim added#asahi · 2024-01-25 07:01
chadmedj`ey: i was awake but at work :p #asahi · 2024-01-21 20:47
chadmedas400: working on it#asahi · 2024-01-19 22:23
chadmedas400: i am now#asahi · 2024-01-18 09:24
chadmedemotion?#asahi · 2024-01-13 08:49
chadmedthe modules are loaded but i cant see any of the expected output in your kernel messages... #asahi · 2024-01-13 08:49
chadmedmadokaiii: im honestly not quite sure. i find it incredibly odd that there are no sound cards available at all via alsa. something weird is going on there#asahi · 2024-01-13 06:07
chadmedthere is a flag you can pass to dnf to prefer the COPR but i cant remember what it is#asahi · 2024-01-13 06:07
chadmedthose errors are most likely because the virtualised kernel (libkrunfw) doesnt have virtio-snd and virtio-gpu. if the version of libkrunfw that ended up installed came from the main fedora repos, this can happen#asahi · 2024-01-13 06:04
chadmedc10l: are you using the versions from the COPR? that error comes from the VM itself and refers to the virtio devices, not your host system's dri/snd #asahi · 2024-01-12 22:09
chadmedmadokaii: well for starters your machine has tas2770 in it anyway#asahi · 2024-01-11 01:49
chadmedlook at the bluetooth driver make sure you understand what its doing etc#asahi · 2024-01-11 01:49
chadmedhead over to #asahi-dev to ask specific questions about stuff like that. in general you should probably familiarise yourself with kernel development first#asahi · 2024-01-11 01:43
chadmed"yaks in need of shaving" #asahi · 2024-01-11 01:39
chadmedhttps://alx.sh/w#asahi · 2024-01-11 01:39
chadmedbut beyond that basically just find a feature you want that isn't being worked on, get acquainted with the tooling, and start developing