2022-11-22
00:10c10l has quit [Quit: Bye o/]
00:17c10l has joined #asahi-dev
00:19user982492 has joined #asahi-dev
01:37weitcis has joined #asahi-dev
01:42StupidYui has quit [Ping timeout: 480 seconds]
02:14nico_32_ has joined #asahi-dev
02:19nico_32 has quit [Read error: Connection reset by peer]
02:21weitcis has quit [Remote host closed the connection]
02:28weitcis has joined #asahi-dev
02:33Dcowprepared apple-cpufreq for power-profiles-daemon, so now we (I) can switch governors in DE ;)
02:38user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
03:30chadmedall the governors kinda suck with heterogeneous systems except for schedutil, especially once we sort out EAS
03:33nicolas17ah gnome, that looks suspiciously similar to macOS control center in overall design :P
03:34nicolas17chadmed: I bet there's a bunch of userspace work to be done too, like hinting the scheduler to run "background" tasks on e-cores
03:37Dcowchadmed: I am not that aware of overall state, but I get used to switch power profiles from UI on my previous laptop. Also, in lina's streams she get valuable performace boost after switching to 'performace' (I think schedutil is default one). So, there is difference, at least right now.
03:38nicolas17speaking of which, how can I manually make a process run only on e-cores or only on p-cores? CPU affinity?
03:42nicolas17I had cases like a queue of task X to run on each of a dozen files, and when each is done, enqueue task Y to run on the result of that... and if X is slower than Y, then the Y queue could starve, and maybe running X on p-cores and Y on e-cores could improve overall utilization
03:43DcowI'll clean up and push later, but in case someone very intrested or want to review (my C is rusty, so ...)
03:51mac456 has joined #asahi-dev
03:52marcan"powersave" is pretty much useless unless you literally want to throttle apps into being slower to save some battery, which is rarely an actual useful choice
03:53marcanit only works if you're actively using the CPUs. if you're just doing normal bursty desktop work, "schedutil" is likely to save more power.
03:54marcanondemand/conservative are legacy stuff for ancient platforms and are completely useless here
03:55chadmedthe other thing is that only schedutil takes into account each core's capacity for work. all the others have no awareness of heterogeneity which makes them doubly useless here
03:56marcanI assume the scheduler still knows about core capacity even if you use that cpufreq governor
03:58chadmedbut youre mad if you daily performance, especially with energy prices the way they are :P
04:03marcanok, I think we're going to punt the jack initial hang thing until later, it's trivial enough to just include in the release notes
04:07mac456 has quit [Ping timeout: 480 seconds]
04:07chadmedbroken UCM handling and no the safety situation hasnt changed since the m2 machine let the magic smoke out
04:09chadmedthe UCM stuff is needed for headphone jack hotplug switching and to automatically set some stuff in alsamixer so that users dont need to faff about in it
04:11chadmedno its needed for pulse to know where the hardware mixer is for the headphone jack and stuff like that too
04:11tpw_rulesi guess i'm thinking what is there to switch if only the headphone jack works. but there is stuff like bt i guess
04:13marcanhttps://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/752 is the upstream MR
04:16Dcow has quit [Ping timeout: 480 seconds]
04:17marcansven: I'm guessing we should disable dcpext for now, I think it breaks the display subsystem when it fails to probe?
04:26mac456 has joined #asahi-dev
04:39mac456 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
04:51marcanI'm going to carry a libinput patch (in lieu of a whole new package) for the MTP quirk. hopefully we can upstream that quickly.
05:09marcanworked after a cold boot. I know we bork with drivers lacking firmware update. I really need to figure out how to cold reset it properly...
05:10mac456 has joined #asahi-dev
05:27nicolas17 has quit [Quit: Konversation terminated!]
05:34capta1nt0ad has quit [Remote host closed the connection]
05:50Graypup_ has quit [Quit: meow]
05:50Graypup_ has joined #asahi-dev
05:58bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
06:17Graypup_ has quit [Quit: meow]
06:18Graypup_ has joined #asahi-dev
06:18mac456 has quit [Ping timeout: 480 seconds]
06:20kode54 has quit [Quit: Ping timeout (120 seconds)]
06:21kode54 has joined #asahi-dev
06:30cylm has quit [Quit: WeeChat 3.6]
06:41weitcis has quit [Remote host closed the connection]
06:51bisko has joined #asahi-dev
06:53weitcis has joined #asahi-dev
07:09weitcis_ has joined #asahi-dev
07:10weitcis has quit [Read error: Connection reset by peer]
07:15weitcis_ has quit [Remote host closed the connection]
07:48SSJ_GZ has joined #asahi-dev
07:50bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
07:50marcansven: it was just the entry in the device tree, which I think jannau had in a bits branch at some point? I wasn't sure why that was there
07:59StupidYui has joined #asahi-dev
08:08phiredo most of the bugs will occour around boot, connect, disconnect and screen sleep/wake? Or is it just flakly 100% of the time?
08:09svenfor me it was mostly in those cases but I haven’t even used this with anything more than a tty yet
08:13marcanif nothing else comes up, I think we're good for release, I just need to write the progress report
08:13bisko has joined #asahi-dev
08:13phirethough, more important for me and my daily driving is 4k pages + gpu. I haven't caught up with the current situation, but my understanding is those are on completly seperate expermental branches, and probally fundementally incompatable without hacking at mm?
08:14marcangpu uses the shmem allocator which is deep kernel code assuming the page size, so fixing that will probably be "fun"
08:15marcanI guess lina could either drop the shmem helper entirely or hack on a flag to somehow ensure 16K backing pages, but I'm not even sure how practical that is given the idea of shmem
08:17svenit’s quite neat actually. I just haben rebased it because people kept using it and preparing it for end users despite me telling them not so
08:21marcanphire: if we make it easy for people to use 4K kernels people will stop fixing broken 16K apps
08:22marcanI don't want to do that until the GPU stuff is shipping and lina gets around to figuring out a solution for the page size issue
08:23marcanphire: and to be clear, the shmem stuff is literally tmpfs, so you're talking about making the kernel's core tmpfs/shmem code support some kind of page folio business / aligned allocations (it already supports huge pages but that's special), or replacing it with something else
08:24phireguess I'd need to do so much research if I want to help push mixed page support. I haven't actually done any kernel dev in like 15 years, so I'm a bit lost
08:27phireI'm kind of with you that I want broken 16k apps to be fixed. But some apps are never going to support 16k pages, so I'm gready and want both
08:28marcanyes, but those apps are all foreign/emulated apps and 99% of that category is games and so there's no point until the GPU stuff is there and supports 4K pages
08:28mpssven: nice, where is your rebased 4K patch (I need sometimes to use f2fs and boot older kernels when working with mmc/sdcard for my arm SBCs)
08:32marcanbecause F2FS is solidly in the "no excuse to be broken on 16K" list and I have zero interest in supporting or providing 4K support for that
08:33marcanif anything F2FS's continued brokenness is all the more reason to delay 4K support, because it means 16K-broken code still exists
08:33mpsI don't ask sven to work on it (or you), just asked if it is published somewhere, nothing else
08:34marcanno, other than the fact that 16K HW / 16K kernel / 4K user is a much harder problem than 16K HW / 4K kernel / 4K user
08:35mpsyes, I understand you, and because that I don't want to force anyone to work on my 'pet peaves'
08:37marcanpowerpc people said they failed at getting people to fix userspace for larger page size support. even Red Hat gave up on ARM I think, for desktop stuff.
08:38marcanthe result is a better ecosystem for everyone, and I'm in no rush to stop giving them reasons to improve ;)
08:38marcanso sorry, it's going to be 16K until we run out of software that doesn't support it that isn't an emulator of some sort
08:50arnd_ has quit []
08:50arnd has joined #asahi-dev
08:51MajorBiscuit has joined #asahi-dev
08:52chadmedim suspicious that no ones added new broken software to the list on the wiki. i feel like therell be a point that we hit a critical mass of users and that list will just explode with stuff
08:52r0ni has quit [Remote host closed the connection]
08:52chadmedor, more likely, everyone just does everything through a browser these days and chromium is now fixed
08:55MajorBiscuit has quit []
08:58dottedmagIsn't it pretty uncommon to rely on page size? allocators care, and jemalloc is fixed (so we might have a trickle of less-known software that embeds jemalloc), JIT-compilers care and they are fixed too. This leaves games/emulators.
09:00MajorBiscuit has joined #asahi-dev
09:02chadmedeven on the x86 side this sort of never-got-updated-to-work-with-the-spec type stuff comes up sometimes
09:04chadmedi spent about 8 hours trying to figure out why a brother printer driver would just silently drop print data and spit out blank pages a while ago and it turned out to be because their linux drivers, even for new printers, are 32 bit only
09:05chadmedthis isnt documented anywhere and it felt like going back to the 2000s, having to google _just_ the right phrase to find the _one_ forum post that says "yeah you need lib32 or it just silently fails"
09:05chadmedtherell be plenty of stuff like this that people will want fixed once there are users trying to run it
09:06amarioguy2 has joined #asahi-dev
09:10amarioguy has quit [Ping timeout: 480 seconds]
09:15marcanit's a seriously viable solution too, given what I've heard about upcoming GPU virtualization stuff
09:15marcanlike you could seriously just run games in a thin VM and use 9p or whatever to share the filesystem and the GPU stuff to share GEM buffers with the host and it all probably will just work with the right amount of duct tape and feel like native apps
09:16marcan(tl;dr on the new gpu virt stuff if I understood it correctly: just run the native driver in the VM and paravirtualize the UAPI)
09:17mazas long as you don't trap too much, there is no reason why a VM would be too slow. device assignment solves that. you just get extra SW complexity to manage a stage-2 on the IOMMU side.
09:17marcanyou'd trap for the equivalent of every guest GPU submission ioctl, which is already a trap anyway, so probably a not-terrible constant factor
09:18mazhmmm. there is HW out there that doesn't require a trap on submission (the HW implements VFs to can be directly controlled by the guest).
09:19marcanand can be implemented safely as long as you can map guest contexts to host contexts, since by definition at that layer you already need safe context isolation
09:20marcanit just means each guest process looks like a host process as far as the GPU is concerned, and you can have as many VMs and guest processes as you want
09:20marcanyes, but this is in principle portable to most modern GPU drivers with little work, because it's based on the existing process isolation concept
09:22marcanand on the host side I think you can even get away with minor or no kernel changes depending on the driver? not sure
09:25mazthe thing I really dislike about this is that you are creating a Linux-specific API at the hypervisor level. if the hypervisor needs to interpret this, that's a pretty large attack surface. mujltiply this by the number of CPU architectures out there...
09:27marcanI'm not sure if there's some minor mm stuff to deal with, but I don't see much of a surface on the host hypervisor kernel
09:27marcan(other than the existing UAPI attack surface which... well, let's just say doesn't have a great track record on legacy GPUs, but that's already a big problem VMs or not, and maybe Lina's Rust driver will do better there)
09:28mazas I said, if this is just about a kick all the way down to userspace, and for userspace to peek at a shared buffer, there is 0 effort on the hypervisor side, which suits me.
09:28marcanI haven't read up on this in detail but AIUI all of the significant shenanigans would be in the qemu/guest kernel side, to forward those ioctls and manage buffer mapping
09:30marcanI'm not sure how mapping guest memory works? I think the GPU stuff just uses mmap(), so you'd need a way to forward such a mmap() on the host into guest IPA space (and then the guest would forward it into a given process' VA space)
09:30marcan(I'm sure there's fun memory usage accounting issues here but eh, that's a solvable problem)
09:34marcanI just look forward to this hopefully solving the 4K problem in a way that is much more likely to be a good solution for people playing games on asahi :p
09:35mazah, talking about graphics. has there been a significant change in the asahi kernel between 6.0 and 6.1 that makes X trip over on M2?
09:36mazyeah, it's not a fresh install. everything is working well with 6.0, and I compiled my own 6.1 kernel. all OK except for X (VTs are OK).
09:40marcanalright, I have a progress report to write, let's see if I can get it done in a couple hours
09:44tobhe_ is now known as tobhe
09:58leitao has joined #asahi-dev
10:06leitao has quit [Ping timeout: 480 seconds]
10:11Mrmaxmeier has quit [Quit: Ping timeout (120 seconds)]
10:11Mrmaxmeier has joined #asahi-dev
10:12wiizzard has quit [Quit: Bridge terminating on SIGTERM]
10:12m5zs7k has quit [Max SendQ exceeded]
10:12MajorBiscuit has quit [Max SendQ exceeded]
10:12m5zs7k has joined #asahi-dev
10:12MajorBiscuit has joined #asahi-dev
10:19Dementor has quit [Quit: Ping timeout (120 seconds)]
10:19Dementor has joined #asahi-dev
10:22_jannau_marcan: USB3 benchmark: Susperspeed+ Gen 2x1 (10 Gbps, jmicron based) nvme ssd adapter: 920 MB/s (M1), 990 MB/s (M1 Max/M2) (sequenctial read), faster than the same HW under macOS
10:24_jannau_feel free to. I measured around 750 MB/s on macOS but didn't spend effort to validate that
10:24svenunfortunately atcphy probably can't take credit for that since it's likely just something more efficient inside dwc3 or vfs or whatever :D
10:25svenI do configure atcphy to usb3-only while xnu always uses usb3+dp unless you coerce it but I really doubt that makes a difference
10:38phire has quit [Quit: No Ping reply in 180 seconds.]
10:39phire has joined #asahi-dev
10:48phire has quit [Quit: No Ping reply in 180 seconds.]
10:48j`eywith the USB3/atc etc changes, is the DT still compatible if you dont build the new drivers? seemed like u-boot had issues with the DT and the ATC node
10:50phire has joined #asahi-dev
10:52Dcow has joined #asahi-dev
10:52svenI think some of them are hacks and/or legacy code because they didn't want to implement a phy
10:52Dcow has quit []
10:53phire has quit []
10:55Dcow has joined #asahi-dev
10:55phire has joined #asahi-dev
10:58phire has quit []
10:59phire has joined #asahi-dev
11:03phire has quit []
11:05phire has joined #asahi-dev
11:07turo has quit []
11:08ChaosPrincessas ChaosPrincess, thats it
11:09phire has quit []
11:10turo has joined #asahi-dev
11:10marcanChaosPrincess: any comments on it? personally I think you did a really good job mapping out the "magic" bits and such. it's a simple driver but I want to highlight that a lot of effort goes into these things too.
11:10phire has joined #asahi-dev
11:12ChaosPrincessmy previous kernel work was trying to port the wii linux from 2.something kernels to newer, without much success, so you can say its the first :P
11:13ChaosPrincessand for RE - 1. run m1n1, 2. poke at macos, 3. bang head against desk a lot. 4. ?????? 5. profit, sometimes
11:14ChaosPrincessthey/them, but do not care much, use whatever.
11:19marcan(it's also used during restores and looks like an iPhone then, though they crippled it to USB2 only at some point for some reason)
11:20ChaosPrincessisn't that tb networking, not usb device mode?
11:20ChaosPrincessbut that is usb4 only, no?
11:21ChaosPrincesswhat device class then?
11:21ChaosPrincessi know about tb host to host networking, but usb is new to me
11:21marcanapple used to have their own bespoke ethernet nonsense in the bad old iPhone days but I assume it's standard now
11:22phire has quit [Quit: No Ping reply in 180 seconds.]
11:22ChaosPrincessthats certainly a way to implement it
11:27phire has joined #asahi-dev
11:32phire has quit [Quit: No Ping reply in 180 seconds.]
11:34capta1nt0ad has joined #asahi-dev
11:39phire has joined #asahi-dev
11:42phire has quit []
11:44phire has joined #asahi-dev
11:47phire has quit []
11:55povikit doesn't seem to be anything broken in kernel, at least as far i can tell, speaker-test does work while pulseaudio is locked up trying to resume
11:56tobhe_ has joined #asahi-dev
12:01tobhe has quit [Ping timeout: 480 seconds]
12:01phire has joined #asahi-dev
12:14phire has quit [Quit: No Ping reply in 180 seconds.]
12:15povikno idea, haven't seen it either (or is that the youtube playback stuck issue from way back?)
12:17phire has joined #asahi-dev
12:18jannauit looks similar to the youtube being issue, i.e. it reproduces the behavior. pipewire doesn't show the same behavior on the same machine
12:19povikanyway commenting out load-module suspend-on-idle (or similar) in pulseaudio conf works as a workaround
12:19tobhe has joined #asahi-dev
12:21tobhe_ has quit [Ping timeout: 480 seconds]
12:24phire has quit [Quit: No Ping reply in 180 seconds.]
12:26rowanG337 has joined #asahi-dev
12:28phire has joined #asahi-dev
12:28phire has quit []
12:29sentinal8473 has joined #asahi-dev
12:44eiln has joined #asahi-dev
12:58eiln has quit [Quit: Page closed]
13:04jannaumarcan: notes for the dcp part of the progress report: https://www.jannau.net/asahi/asahi-progress-dcp.txt feel free to edit as you like
13:05marcanalready wrote everything up lol https://gist.github.com/marcan/a04dbffc4ed29abd5e39c4651f980d5d
13:07phire has joined #asahi-dev
13:12phire has quit []
13:12marcanpovik, sven, ChaosPrincess, jannau, chadmed and whoever else wants, feel free to review if you have some time
13:14phire has joined #asahi-dev
13:15svenplease just don't mention external displays very prominently yet. i've already had at least three very enthusiastic people asking me in /msg how to set that up who didn't quite realize how broken it is right now
13:17sentinal8473 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
13:19marcanrephrased a bit: It also paves the way for the (still incomplete) external display support (over Type C/DisplayPort) that Sven has been working on, [...]
13:20phire has quit [Quit: No Ping reply in 180 seconds.]
13:22chadmedmy eyes literally glazed over, dunno how much of that to attribute to being sick, being exhausted, or 1000 iq humour
13:25phire has joined #asahi-dev
13:28phire has quit []
13:31povik> (though they won't be able to use hardware volume controls, but since the data format is 24-bit PCM, software volume control is perfectly acceptable here).
13:31phire has joined #asahi-dev
13:32jannaufor the 2nd-stage m1n1 update maybe mention https://www.mail-archive.com/tech@openbsd.org/msg72613.html in addition to "linux packages"
13:35ChaosPrincesslgtm on the post, just need a clickbait title :P
13:36phire has quit []
13:37povik> sometimes the headphones won't work if initially connected on boot, or after an idle period.
13:37phire has joined #asahi-dev
13:38povikalthough not sure if we can do that easily -- i assume old pulseaudio configuration is retained on package upgrade
13:40povikhm, so if we do the change to default conf now, new installs would have the workaround but we wouldn't be able to remove it for users in the future once the underlying issue is fixed
13:42phire has quit [Quit: No Ping reply in 180 seconds.]
13:44phire has joined #asahi-dev
13:46kujegersorry to interrupt, but pipewire does not suffer from the problem, did I read that correctly? if so, maybe suggest switching to it?
13:46amarioguy2thanksgiving break coming up, should be able to get those sep docs much more up to speed
13:46amarioguy2 is now known as amarioguy
13:50_jannau_last second switching to pipewire seems to be a bad idea as well. it seems to works for me though
13:51phire has quit [Quit: No Ping reply in 180 seconds.]
13:52_jannau_patching pulseaudio looks like the preferable option even if that is hard-coding no-suspend instead of reading it from the config. we can control that via package updates
13:53phire has joined #asahi-dev
13:54poviki found out unsuspend is never called, neither sink_set_state_in_io_thread_cb with PA_SINK_RUNNING
13:59phire has quit [Quit: No Ping reply in 180 seconds.]
14:00phire has joined #asahi-dev
14:01marcanI already fixed one PA bug that's been there for a year, I don't know why it's so broken for us but I'm not getting much confidence on the future of PA
14:05phire has quit []
14:07phire has joined #asahi-dev
14:08chadmed_ has joined #asahi-dev
14:11DcowI got keyboard issues after s2idle on -edge/j316c a few times. it's basically render keyboard unusable, looks like it's repeating space character infinitely. It's impossible to switch to another tty from GDM(due keyboard not working) so I didn't obtain dmesg yet.
14:12sentinal8473 has joined #asahi-dev
14:15Dcowmarcan: I will post there once I get dmesg logs. I though now it's a good time to just say it out loud.
14:19marcanhttps://gist.github.com/marcan/a04dbffc4ed29abd5e39c4651f980d5d updated with PipeWire story
14:20zzywysmmps: the solution to the f2fs problem seems obvious to me: submit a patch that doesn't let you enable CONFIG_F2FS_FS if CONFIG_ARM64_16K_PAGES or CONFIG_ARM64_64K_PAGES is enabled
14:26mpszzywysm: no, I already talked with drivers authors, one of them told me that they would probably fix f2fs to work with 16K pages but didn't 'defined' when
14:26zzywysmmps: in the meantime, the kernel config system should accurately reflect the (lack of) code compatibility
14:29chadmed_ has quit [Remote host closed the connection]
14:36sentinal8473 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
14:41joske has joined #asahi-dev
14:42chadmed_ has joined #asahi-dev
14:42joskemarcan: read the progres report, and as always, well written and very detailed. Even though I'm following asahi development closely, I still learned a lot!
14:43kh has joined #asahi-dev
14:44khRegarding f2fs on 16k https://android-review.googlesource.com/c/platform/system/core/+/2244154
14:46marcanI think I'm going to sync asahi-dev to asahi now, looks like that path is well-tested enough
14:47svenokay, maybe let me rephrase that: it won't even allow you to mount pages created on a 4k kernel when you're running a 16k kernel
14:48khYeah but people previously were saying that f2fs should be blocked on 16k kernels altogether...
14:50svenalso, does that even touch the kernel? it looks like it just changes something in the userspace tools
14:52khYes that's a change to a userspace tool and I don't think there's any kernel changes required for it
14:53marcanI think we can drop the mkinitcpio override right? I have systems with a newer one that work fine
14:54sentinal8473 has joined #asahi-dev
14:56marcanasahi-dev synced to asahi, pulseaudio overrides dropped, and PKGBUILDs repo now has a `stable` branch synced to main at this point
14:57jannaumarcan: yes, mkinitcpio can be dropped, there was an mkinitcpio upstream release with compressed kernel support, which we don't even need anymore
14:58joske has quit [Quit: Leaving]
14:59mpskh: I hope that when asahi get merged to mainline then f2fs developers will have more incetive to make it working with 16K pages. At least one of them (Chao Yu) told me in private mail that he is interested to make it work
15:05jannauah, yes. I made no change to restore the brightness on reactivating the display. curse of not using a device where the problem occurs
15:21chadmed_ has quit [Remote host closed the connection]
15:36sentinal8473 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
15:45DarkShadow44 has quit [Quit: ZNC - https://znc.in]
15:45DarkShadow44 has joined #asahi-dev
15:49opticronone nit on the release post, ChaosPrincess' and ChaosPrincess's both exist in the "Backlight, Book I" chapter and I think the latter is correct
16:22rowanG337 has quit [Remote host closed the connection]
16:33ChaosPrincessSplit into Enable/output enable, and pointing out that reading back the current state is possible did help.
16:53beeblebrox has quit [Ping timeout: 480 seconds]
17:02uallas has joined #asahi-dev
17:03uallas has left #asahi-dev [#asahi-dev]
17:22kh has quit [Quit: Konversation terminated!]
17:27jannauit still turns off the backlight completely but I think kde guesses the correct backlight
17:32jannauis it probed after 10 seconds? could be probe dependencies inferred from the devicetree and giving up after 10 seconds
17:39marcannot sure where the delay comes from, but I found the OF code that scans the properties and creates device links
18:04marcanalso I think my M1 MBA was getting pretty warm in sleep mode and I think eating battery... methinks there's a problem here, need to debug
18:11___nick___ has joined #asahi-dev
18:12___nick___ has quit []
18:14___nick___ has joined #asahi-dev
18:32rqou_ has joined #asahi-dev
18:34rqou_sven: re backlog question about usb3 in device mode: when you had first posted atcphy months and months ago, gadget mode did *not* work (neither usb2 nor usb3). i have not tested the current version
18:39millenialhacker has joined #asahi-dev
18:39millenialhackerqq: Has anyone experienced keyboard/mouse problems when booting Asahi 6.1 RC3?
18:40millenialhackerI'm unable to login on my Macbook Pro M1 Pro
18:42millenialhackerweird thing, it used to work fine a week ago, I just worked on OSX this week, and now when I tried to boot keyboard doesn't work.
18:42millenialhackerI rebooteed three times, all of them the same
18:44millenialhackerbefore that I got a weird wifi card error, so no network, but keyboard worked, I rebooted to solve wifi/bt error, and wifi boot up properly but no keyboard / mouse once I landed in GDM.
18:44millenialhackeras400, control + alt + FXX does not work either
18:44millenialhackerkeyboard works fine until grub
18:44millenialhackerafter grub boots Linux it's gone
18:45millenialhackerGentoo hates me :D
18:45millenialhackerI can connect an external keyboard, but I just wanted to know if it was a known issue
18:58millenialhacker has quit [Remote host closed the connection]
19:00millenialhacker has joined #asahi-dev
19:00leitao has joined #asahi-dev
19:02leitao has quit []
19:03amarioguy2 has joined #asahi-dev
19:09MajorBiscuit has quit [Ping timeout: 480 seconds]
19:09stsmwg has joined #asahi-dev
19:24millenialhacker has quit [Ping timeout: 480 seconds]
19:29nicolas17 has joined #asahi-dev
19:50tobhe_ has joined #asahi-dev
19:51millenialhacker has joined #asahi-dev
19:55tobhe has quit [Ping timeout: 480 seconds]
20:00millenialhacker has quit [Ping timeout: 480 seconds]
20:14millenialhacker has joined #asahi-dev
20:25tobhe has joined #asahi-dev
20:28tobhe_ has quit [Ping timeout: 480 seconds]
20:28jvzr has joined #asahi-dev
20:41millenialhacker has quit [Ping timeout: 480 seconds]
20:49svenokay, wtf, I just had access to the tbt pcie and everything else but now I rebooted and now the same kernel results in SErrors again?!
20:51mkurz has joined #asahi-dev
20:53millenialhacker has joined #asahi-dev
20:55jluthra has quit [Remote host closed the connection]
20:56jluthra has joined #asahi-dev
21:01leitao has joined #asahi-dev
21:01millenialhacker has quit [Ping timeout: 480 seconds]
21:08___nick___ has quit [Ping timeout: 480 seconds]
21:11mkurz has quit [Quit: Leaving]
21:18millenialhacker has joined #asahi-dev
21:19amarioguy2 has quit [Ping timeout: 480 seconds]
21:26leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
21:26millenialhacker has quit [Ping timeout: 480 seconds]
21:28cyrozapHi, all! I just read the recent progress report, and the part about the ASMedia firmware loading functionality really interested me. I've been working on my own ASMedia USB host controller RE project for a couple years now (https://github.com/cyrozap/asmedia-xhc-re), and from my research, the only ASMedia USB host controllers I found that include hardware-based firmware upload over PCIe (functionality
21:28cyrozapdocumented here: https://github.com/cyrozap/asmedia-xhc-re/blob/59708d5b5eb17593f6f5459f2bf20b73e90b159d/doc/src/index.adoc#code-ram-write-access, example code here: https://github.com/cyrozap/asmedia-xhc-re/blob/59708d5b5eb17593f6f5459f2bf20b73e90b159d/tools/asm_tool.py#L156-L213) are the ASM1042A and ASM1142--the others (ASM1042, ASM2142/ASM3142, and ASM3242) either lack the functionality in hardware
21:28cyrozapor they have it disabled by default. So, I have a few questions: 1) Which ASmedia USB host controller is Apple using in their devices? 2) Has the firmware upload protocol that Apple is using been documented anywhere? 3) Which Apple models contain these ASMedia USB host controllers? 4) Is there a way to download the macOS XNU kernel binary (which the post said contains the ASMedia firmware) directly
21:32svenpovik: soc for stuff that will only ever run on apple Silicon SoCs (e.g. rtkit), platform for things that are also useful for older apple machines (x86 macs etc.) imho
21:32povikcyrozap: ad 2) https://github.com/AsahiLinux/linux/commit/893f672e78d075fbb7b4530ffc190173dc700871
21:33tobhe_ has joined #asahi-dev
21:34millenialhacker has joined #asahi-dev
21:38beeblebrox has joined #asahi-dev
21:38tobhe has quit [Ping timeout: 480 seconds]
21:40jannaucyrozap: ifixit says asm3142 for the 4 port 24" imac https://www.ifixit.com/Teardown/iMac+M1+24-Inch+Teardown/142850#s288729 not sure about the mac studio. those are the two models which have the asmedia usb host controller
21:42beeblebrox has quit []
21:45amarioguy2 has joined #asahi-dev
21:47wikwity has joined #asahi-dev
21:50beeblebrox has joined #asahi-dev
21:50cyrozappovik, jannau: Thank you both, that's really helpful information! I'm surprised to see they're using a bog-standard ASM3142, and not some special part customized by Apple. And the mask ROM firmware version (0x010250090816, normally written like 160809_50_02_01) confirms that, since that's the same version I see with the ASM2142 and ASM3142 chips I have.
21:57amarioguy2 has quit [Ping timeout: 480 seconds]
22:01ChaosPrincessMade a step 1 to having a 'reboot to macos' command - nvram read/write tool. seems to be working, but i do not recommend using it if you are not ready to do a dfu restore https://github.com/WhatAmISupposedToPutHere/asahi-nvram
22:07millenialhacker has quit [Ping timeout: 480 seconds]
22:12ChaosPrincessabsolutely none, i do not have a m2
22:13amarioguy2 has joined #asahi-dev
22:15wikwity has quit [Remote host closed the connection]
22:22cyrozapOh, interesting... Looking at the kernel code, it looks like ASMedia moved the direct MMIO access functionality from the PCI config space to BAR0. And so the only other differences in the process are really just some MMIO address and bit field changes, which makes sense since the ASM2142 and later use a different range of addresses for their MMIO compared to the ASM1142 and earlier. And I know for
22:22cyrozapcertain that those BAR0 registers are accessing MMIO because the registers accessed through them (e.g., https://github.com/AsahiLinux/linux/blob/893f672e78d075fbb7b4530ffc190173dc700871/drivers/usb/host/xhci-pci-asmedia.c#L222-L223) match the ones I've documented (https://github.com/cyrozap/asmedia-xhc-re/blob/59708d5b5eb17593f6f5459f2bf20b73e90b159d/data/regs-asm2142.yaml#L108-L173).
22:24millenialhacker has joined #asahi-dev
22:27jvzr has quit [Remote host closed the connection]
22:28cyrozapSo, uh, thanks, Apple, for using functionality in ASMedia's newer host controllers that no other system vendors seem to be using. And big thanks to marcan for doing the RE work on that--you've saved me a lot of time and energy :)
22:30ChaosPrincessi do not think thats possible, os picker is actually full macos that runs the 'os picker' app, which then sets the apple equivalent of BootNext and reboots
22:31cyrozapbtw, if anyone has any questions about the ASMedia USB host controllers, I've done a lot of in-depth RE of them, so feel free to ask!
22:38millenialhacker has quit [Ping timeout: 480 seconds]
22:53millenialhacker has joined #asahi-dev
23:02stsmwg has quit [Quit: Lost terminal]
23:12millenialhacker has quit [Ping timeout: 480 seconds]
23:12SSJ_GZ has quit [Ping timeout: 480 seconds]
23:48loop0 has joined #asahi-dev
23:50weitcis has joined #asahi-dev
23:53amarioguy2 has quit [Ping timeout: 480 seconds]
23:56millenialhacker has joined #asahi-dev
23:57loop0 has quit [Quit: WeeChat 3.7.1]
23:58weitcis_ has joined #asahi-dev
23:59weitcis has quit [Read error: Connection reset by peer]