#
…

2023-01-04

00:37chadmed has quit [Ping timeout: 480 seconds]
00:43hertz has joined #asahi-dev
00:45amarioguy2 has joined #asahi-dev
00:51amarioguy has quit [Ping timeout: 480 seconds]
00:59blazra2 has joined #asahi-dev
01:06blazra has quit [Ping timeout: 480 seconds]
01:06blazra2 is now known as blazra
01:20marcanlol he actually said good bye
01:22marcanguess he couldn't handle me pointing out that his patch series commits all the same sins my patch did, after he lectured me about it?
01:23marcanseriously, what the actual fsck is up with some kernel developers/maintainers
01:23marcanthis is beyond stupid
01:26psykosewasn't rmk the same person helping you with some patch submission before a couple months back
01:32marcanyes, he was
01:32marcanand *he* gave up on *that* one
01:32marcanthis time he's part of the problem
01:34psykoseit's all a flat circle in the end eh :-)
01:34psykosea spiral of insanity until you yourself will turn into one of these, one day :p
01:36marcanyeah no, I'll give up on the project before turning into one of them thanks
01:38psykosei hope so too :) never like seeing people become what they dislike, it's sad
02:30chadmed has joined #asahi-dev
02:44chadmed has quit [Ping timeout: 480 seconds]
02:56chadmed has joined #asahi-dev
03:53chadmed has quit [Ping timeout: 480 seconds]
03:53jackhill has quit [Remote host closed the connection]
05:18jluthra has quit [Remote host closed the connection]
05:19jluthra has joined #asahi-dev
05:30chadmed has joined #asahi-dev
06:14hertz has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
06:14chadmed has quit [Quit: Konversation terminated!]
06:14chadmed has joined #asahi-dev
06:21cylm_ has joined #asahi-dev
07:12bps has joined #asahi-dev
07:12SSJ_GZ has joined #asahi-dev
07:36whomst has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
07:39lewurm has quit [Ping timeout: 480 seconds]
07:40chadmed has quit [Remote host closed the connection]
07:47lewurm has joined #asahi-dev
07:48kevans91 has quit [Ping timeout: 480 seconds]
07:53bps has quit [Ping timeout: 480 seconds]
08:08chadmed has joined #asahi-dev
08:16amarioguy has joined #asahi-dev
08:19amarioguy2 has quit [Ping timeout: 480 seconds]
08:59bps has joined #asahi-dev
09:32bluetail1 has joined #asahi-dev
09:39bluetail has quit [Ping timeout: 480 seconds]
09:39bluetail1 is now known as bluetail
09:54svenmarcan: nvme nvme0: Identify NS List failed (status=0xb) seems to present in the T2 logs as well (e.g. https://bbs.archlinux.org/viewtopic.php?id=281389). they probably also need that NVME_QUIRK_IDENTIFY_CNS quirk
09:56marcansven: can't really test on one of those right now, but yeah I can just send it blind and see what happens
09:56svenyeah, no access to any t2 mac here either
09:58svenlet me poke the t2 people to see if they can test some 6.2-rc
10:17mps has quit [Quit: Lost terminal]
10:21mps has joined #asahi-dev
10:42hertz has joined #asahi-dev
11:20svenfrom the t2 folks: for 6.2.0-rc3-00010-g69b41ac87e4a nvme nvme0: Identify NS List failed (status=0xb) in dmesg and only /dev/nvme0 exists
11:20sventhey'll test the patch next and reply with tested-by if that quirk fixes it again
12:05chadmed has quit [Remote host closed the connection]
12:08chadmed has joined #asahi-dev
12:17chadmed has quit [Remote host closed the connection]
12:22chadmed has joined #asahi-dev
12:42marcanmaz: 6.2-rc2 rebase pushed (that was more painful than usual)
12:49lewurm has quit [Ping timeout: 480 seconds]
13:02gladiac has joined #asahi-dev
13:10mazmarcan: thanks for that, much appreciated. yeah, between wifi and nvme, it looked positively awful. and I totally ignored rust...
13:11maznow off to rebase NV...
13:17chadmedthe patch count went down \o/
13:33lewurm has joined #asahi-dev
14:33chadmed has quit [Remote host closed the connection]
14:42chadmed has joined #asahi-dev
14:43chadmed has quit []
14:48amarioguy has quit [Remote host closed the connection]
15:15amarioguy has joined #asahi-dev
15:19axboemarcan: works ;)
15:23kevans91 has joined #asahi-dev
15:24gladiac has quit [Quit: k thx bye]
15:31mps6.2-rc2 also works fine here on m1pro
15:35bcrumb has joined #asahi-dev
15:35bcrumb has quit []
15:36___nick___ has joined #asahi-dev
15:36___nick___ has quit []
15:38___nick___ has joined #asahi-dev
15:41yumasi_ has joined #asahi-dev
15:56mazmarcan: we're in business (at least for PCIe, WiFi and nvme, can't tell about the rest as the machine sits closed on a shelf)
15:57mazmarcan: 4 L2 VMs in an L1 VM, all fine so far!
16:01maznowhere as crazy as Thunderbolt+USB3+DP. actually, positively trivial compared to it! ;-)
16:01ChaosPrincesswhich machines support nested virt, only m2 or earlier ones too?
16:03mazm2 only
16:09kettenism2 is basically the only hardware with nested virtualization that is available to mere mortals isn't it?
16:12svenspeaking of thunderbolt, I think I bring up at least one of those NHI rx/txrings now but then something gets stuck
16:13svenand i'm really trying to avoid writing a tracer so far to see how apple deviates from the standard there *sigh*
16:13lewurm has quit [Ping timeout: 480 seconds]
16:13mazkettenis: more or less. Graviton-3 has NV, but the implementation is buggy (you can deadlock the CPU). Some of the announced Marvell stuff with Neoverse-N2 does have NV too (not tried)
16:14mazkettenis: and then there is the stuff that exists but that we cannot talk about, because it is sekrit.
16:15kettenisI don't care about unobtainium ;)
16:18lewurm has joined #asahi-dev
16:22mazkettenis: this is why I stopped working on NV for a whole year. too painful working on the model. I've made more progress in 3 weeks with some HW than in the two previous years. probably ran 10^9 more cycles too.
16:30lewurm has quit [Ping timeout: 480 seconds]
16:37bps has quit [Ping timeout: 480 seconds]
16:39marcanmaz: the rust bit was not *super* painful to merge as far as big messy merges go, but I'm more worried that the RfL tree hasn't been rebased ever as far as I know, because although they can certainly keep merging mainline in, picking things out for upstreaming is going to become an exponential mess that way
16:40marcanI first tried a rebase but gave up on that real quick, since there are like 900 patches in that tree including tons of junk and early development history that just needs to be thrown away
16:41lewurm has joined #asahi-dev
16:50yumasi_ has quit [Remote host closed the connection]
16:51lewurm has quit [Ping timeout: 480 seconds]
17:01hightower2 has quit [Ping timeout: 480 seconds]
17:05mpsoh, 6.2-rc2 produce strange harmonics in my headphone on m1pro
17:13lewurm has joined #asahi-dev
17:23hightower2 has joined #asahi-dev
17:41systwi_ has joined #asahi-dev
17:47systwi has quit [Ping timeout: 480 seconds]
17:51marcanpushed the kernel to asahi-dev, please test :)
17:57Telessia_ has joined #asahi-dev
17:59Telessia_ has quit []
18:01lawrence has quit [Quit: The Lounge - https://thelounge.chat]
18:08whomst has joined #asahi-dev
18:14bcrumb has joined #asahi-dev
18:15bcrumb has quit []
18:21bcrumb has joined #asahi-dev
18:29Cyrinuxmarcan on m2 air, suspend looks broken, after resume well turn screen on, but then its like disk is dont accessible anymore, if I was in a shell, if a type a command, i get no response, also wifi dont resume.
18:30Cyrinuxan audio over jack is broken also, but it was already say upper.
18:33lawrence has joined #asahi-dev
18:34bcrumb has quit [Quit: WeeChat 3.7.1]
18:44kh has joined #asahi-dev
18:45kh> but then its like disk is dont accessible anymore, if I was in a shell
18:45khI have the same issue on M1 MBP (j293) too
18:53kh has quit [Read error: Connection reset by peer]
19:04cylm_ has quit [Ping timeout: 480 seconds]
19:30WindowPa- has joined #asahi-dev
19:35WindowPain has quit [Ping timeout: 480 seconds]
19:36amarioguylmao apple hw really does have that "polish" lot of other hw does
19:36amarioguyserror errata notwithstanding
19:36amarioguy(though yes it also does have it's many many many quirks - see ATC and TBT)
19:37amarioguylot of other hw does not*
19:51amarioguy has quit [Remote host closed the connection]
21:08___nick___ has quit [Ping timeout: 480 seconds]
21:56hightower2 has quit [Ping timeout: 480 seconds]
22:04jannaucs42l83 headphone jack audio (j274) sounds fine with asahi-wip
22:05hightower2 has joined #asahi-dev
22:11SSJ_GZ has quit [Ping timeout: 480 seconds]
22:15mkurz has joined #asahi-dev
22:43chadmed has joined #asahi-dev
22:44chadmedasahi-wip busts sleep on j314
22:44chadmedeverything else seems to work fine though
22:47jannauchadmed: headphone audio? cs42l84 on j375 and j493 has annoying noise
22:48mpsalso on j316s
22:49chadmedno annoying noise but it sounds wrong
22:49mpsI could check tomorrow on j293
22:49chadmedwell there is squealing but that seems more like a side effect
22:50chadmedsounds like a clock somewhere is out of sync
22:50chadmedi have working speakers though ;)
22:50mpsI don't know terms for these sound issue but it is annoyin
22:52chadmedwhen i hear "annoying sound" i think "noise in the background"
22:53mpshm, best i can call it is distortion
22:53chadmedyeah thats a better descriptor of whats going on
22:54chadmedif sleep works for everyone else though i mightve screwed up by kernel config so ill look into that later
22:54j`eychadmed: no, others are having suspend issues
22:56jannaumy understanding was that suspend had issues in general
22:57chadmedive been ignoring my a11y requirements and dailying gentoo over the holidays and with my tas2764 patches its been working fine
22:58chadmedtheres a bit of jank in terms of the kb not waking the machine up and the screen seemingly coming back on randomly at some point but the machine suspends and resumes and i dont lose any hardware
23:02jannauthe keyboard (driver) doesn't yet work as wakeup source but that shouldn't have changed
23:03mkurz has quit [Quit: Leaving]
23:05j`eyI think that was in response to 'suspend had issues in general'
23:06chadmedik its not supposed to work and im fine with it but i was just laying out that i havent really had "issues in general" beyond that, which is an annoyance at worst
23:15jannauah, I misunderstood. I see now that it is completely broken. after resume it seems impossible to create new processes
23:15chadmedyeah its broken now in new, much worse ways :P
23:17jannauhmm, looks like nvme resume is broken. "nvme nvme0: Device not ready; aborting reset, CSTS=0x9"
23:17chadmedyeah i thought it might be nvme
23:17chadmedmy intel macbook exhibits the same behaviour if you dont disable d3cold for the nvme controller
23:17chadmedobviously thats not our problem here because we're not on pci
23:18jannaubut that might be only my tree, still working on dcp/sleep on top of asahi-wip
23:20chadmedi get a broken kde session and am unable to log in to any other tty (it hangs after i input my username)
23:20chadmedwhich seems like an unavailable rootfs
…