#
…

2021-10-06

00:28tomtastic has quit [Quit: ZNC - https://znc.in]
00:28tomtastic has joined #asahi
01:15yuyichao_ has joined #asahi
02:28doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
02:32phiologe has joined #asahi
02:35marcanPMP is the power metrics thing, yes, but I haven't looked at that part of the interface
02:35PhilippvK has quit [Ping timeout: 480 seconds]
02:36marcanpowertop should work to the extent that its interfaces are supported currently
02:36marcane.g. its device-pm stats should work with my pmgr driver and its cpufreq stats should work with my cluster-pstate driver
02:37marcanbut no raw power numbers yet, that would come from PMP (and maybe SMC for the overall battery stat? unsure)
03:08sajattack[m] has joined #asahi
03:11aead has joined #asahi
03:23sajattack[m]Hey everyone, really interesting project you have here. Can't say I'm a fan of Apple hardware, but I am a fan of linux and reverse engineering and I thought this would be an interesting place to be a fly on the wall at the very least. Looking forward to following your progress. Cheers.
03:34marvin24 has joined #asahi
03:37marvin24_ has quit [Ping timeout: 480 seconds]
03:59kov has quit [Quit: Coyote finally caught me]
03:59kov has joined #asahi
04:06psykose has quit [Ping timeout: 480 seconds]
04:07psykose has joined #asahi
04:36darkapex has quit [Read error: Connection reset by peer]
04:36darkapex has joined #asahi
05:05rkjnsn[m]Does the DCP handling display enumeration and EDID decoding mean that daisy-chained DisplayPort are unlikely to work under Asahi, even if the underlying hardware technically supports it?
06:44tomtastic_ has joined #asahi
06:47tomtastic has quit [Ping timeout: 480 seconds]
06:56marcanrkjnsn[m]: what do you mean by daisy-chained?
06:57marcanbut yes, our external display support should basically match macOS, as that is largely offloaded to DCP
06:57marcanhowever, I'm not sure the hardware would support much more than what DCP exposes
07:01rkjnsn[m]DisplayPort cable running from my laptop to monitor 1, second cable running from monitor 1 to monitor 2 (both monitors supporting DisplayPort 1.2's MST functionality). On my 2015 MBP, Linux sees both monitors, and I can extend my desktop to both of them. If I boot into macOS, however, it only sees one monitor and the displays mirror each other.
07:02rkjnsn[m]Oliver Graff: Yes.
07:04ograff(I have no useful technical answer, trying to spin up on the project! Just love helping find diagrams to clarify things :) )
07:09rkjnsn[m]I think I read that macOS supports MST to some extent for the case of a single high-res monitor driven by two DisplayPort streams, but for some reason they never implemented support for driving two monitors via MST.
07:10* svenjust hopes the M1x/M2/whatever will support two external screens on the macbooks
07:10marcanrkjnsn[m]: that's DisplayPort MST, which I'm pretty sure is not supported by the hardware
07:10svenbut for the M1 I kinda expect that we'll be stuck with a single display just like macOS is
07:10marcanthere is only a single display controller for the external display
07:10marcanit's not a DCP thing
07:12tomtastic has joined #asahi
07:13izzyisles[m]Have M1 air, driving 2 ext monitors using displaylink via dell d6000 docking station. More displays possible via displaylink.
07:13rkjnsn[m]Yes. For the M1X, at least (I'm planning on buying a 16"), I was originally hoping that the hardware would still support MST for the single panel, dual stream monitors that macOS *does* support, and perhaps Linux would be able to leverage that for dual displays like on the 2015 MPB.
07:13arsven: the thing i'm amazed about, is that on the m1 mini, if you want 2 displays, only one of them can be on usbc→dp
07:14svensure, but that's unrelated. displaylink is essentially just a display-controller-over-usb3
07:14svenar: yeah... that's because they hooked up the internal display output to a dp->hdmi converter for the first display. and the external display output is hooked up to both usb-c ports :/
07:15arI've used 2×4k displays via a displaylink docking station 2 jobs ago, and it was a pain. even dragging an empty notepad window around was laggy
07:15tomtastic_ has quit [Ping timeout: 480 seconds]
07:15marcandisplaylink is just a USB device, nothing magic there
07:15marcanthat will work on any system with USB
07:15sveni accidentally bought a tb3 dock with displaylink first. they macOS driver is also painful at best
07:15sven*their
07:15armarcan: assuming the drivers actually work ;)
07:16ariirc at one point their linux drivers spewed logs to dmesg… encrypted
07:19arahael has quit [Quit: WeeChat 2.7.1]
07:19sventhat reminds me of some logs from some 3rd party component i had to look at for $some-former-employer. i assumed they were just corrupted because i had to XOR each char with 1 but when i sent a bug report they were seriously surprised I could read their "encrypted log files"
07:31aleasto has joined #asahi
08:18tomtastic_ has joined #asahi
08:22tomtastic has quit [Ping timeout: 480 seconds]
08:24MagMell[m]Does the mu-one/linux 20211005 branch have merged NVME support? I still can't find any NVME disks here
08:30j_eyMagMell[m]: it does
08:35GlanzmannMagMell[m]: On which hardware are you trying?
08:35MagMell[m]Glanzmann: Mac mini M1
08:37GlanzmannMagMell[m]: Strange. Do you want to upload me the kernel and I try on mine?
08:37chadmedif youre not using an initramfs youll have to say Y to it, not M
08:37GlanzmannMagMell[m]: These instructions work for me: https://ab34.de/u/asahi.txt
08:37MagMell[m]Glanzmann: wait
08:38MagMell[m]but i set CMDLINE
08:39MagMell[m]s/but i set CMDLINE/but I set CMDLINE as root=/dev/nvme0n1p3 rootwait/
08:39GlanzmannMagMell[m]: This asahi.macho includes a kernel and an initramfs?
08:40MagMell[m]Glanzmann: I did follow here, but I changed the config a bit, I was afraid that something was missing
08:40MagMell[m]Glanzmann: includes kernel, no initramfs
08:42j_eyyou dont have BLK_DEV_NVME_APPLE in there
08:42MagMell[m]I just rebase a 4k iommu patch, I don't know if it has anything to do with this?
08:43MagMell[m]j_ey: ok thx
08:43chadmedthat config is missing a bunch of options that should be there
08:44j_eyyou need to =y all the new options that are added in the commits on that 2021... branch
08:44MagMell[m]I'd better refer to ab34's config, thanks
08:44sventhey should default to y if you select ARCH_APPLE
08:45chadmedsven: it is selected, i think some things messed up when he rebased
08:45GlanzmannMagMell[m]: Btw, do you have a rootfs already on the nvme?
08:47MagMell[m]Glanzmann: rootfs is there, I just tried to switch over from corellium's kernel
08:49GlanzmannMagMell[m]: Have you tried to boot with my kernel?
08:50MagMell[m]Glanzmann: no, I only tried the repo inside ab34/asahi.txt
08:50MagMell[m]s/inside/in/
08:52GlanzmannMagMell[m]: When you run git describe head in that repo do you get v5.14-rc5-11989-g1ba6f2dff23b?
08:55MagMell[m]Glanzmann: ```root@s-50bd0792 [ linux@20211005 ] ! git describe HEAD
08:55MagMell[m]v5.14-rc5-12255-ga87b378accea
08:55MagMell[m]s/root@s-50bd0792//, s/[ linux@20211005 ] ! git describe HEAD//
08:55GlanzmannI see. I did a git pull, rebuilding and trying to reproduce, let you know how it went.
08:56MagMell[m]But here I rebase the three patches of 4k iommu on the 20211005 branch, this information should not help
08:58j_eyMagMell[m]: that's already in that branch
08:58MagMell[m]j_ey: in20211005?
08:58MagMell[m]> <@_oftc_j_ey:matrix.org> Mag Mell: that's already in that branch
08:58MagMell[m] * in 20211005?
08:58sventhat's an old version of the DART driver
08:59svenit did support 4k pages but not in a sane way
08:59svenyou just want the code that's upstream instead
08:59GlanzmannMagMell[m]: I get a kernel panic.
08:59sven4k page support is not there yet, that needs additional work
09:00j_eybut that's not needed for nvme
09:00sveni'd just recommend to stick to 16k kernel for now unless you have a good reason for 4k
09:00sveni'm pretty sure DCP won't work on 4k kernel right now either
09:01j_eyI thought alyssa was using 4K..
09:02sveni think that's her screen resolution and not her kernel page size :D
09:03chadmedLMAO chuckling rn
09:04GlanzmannMagMell[m]: I managed to build a kernel using alyssa's branch 20211003. I updated the instructions: https://ab34.de/u/asahi.txt (Press Ctrl+r in your browser)
09:05GlanzmannThat works, I build from scratch (including m1n1)
09:06Glanzmannx works as well.
09:06chadmednow try wayland :D
09:10GlanzmannMagMell[m]: If it doesn't work for you, let me know, than I help you with it.
09:11Glanzmannj_ey / sven : alyssa seems to use 16k pages: CONFIG_ARM64_16K_PAGES=y
09:11svenyeah, as i said: dcp wouldn't work with 4k pages even with my patches right now
09:11j_eyOk, my bad
09:13MagMell[m]Glanzmann: I'll try it now by pressing alyssa config first
09:13MagMell[m]First try 16k can work, and then according to this slowly adjust it
09:14sven4k will not work right now no matter you do
09:14j_eysven: not even if you patch it to make it work? :P
09:14GlanzmannMagMell[m]: I also used alyssa config from the webserver with the expired ssl certificate.
09:15svenj_ey: fair enough :D
09:20povik has joined #asahi
09:26chadmedwill fex work without 4k pages? intuition tells me no, but im yet to try it
09:30nsklauschadmed: i'm answering a bit on the side but, it seems the team (through sven) is working on making 4k kernel for asahi, and marcan also expressed interest in making fex work on asahi, so down the road fex should be made to work on asahi one way or another
09:31nsklausmy own interest about having fex running on M1 is gaining ability to run wine
09:34chadmedyeah well the only showstopper i foresee is that amd64 uses 4k pages and as such binaries will expect 4k pages and will probably segfault when they see incorrect memory alignment. whether or not fex is able to present 4x 4k pages to an amd64 binary in a single 16k page, whether thats even technically feasible, or whether there exists some other workaround is beyond me though (and why i asked)
09:34nsklausthe other day marcan was saying that 16k kernel would be a problem for things like wine, and sven replied there were already 4k kernel for asahi, although a work in progress
09:34chadmedi expect that fex will run just fine on the M1 using sven's 4k patches though
09:34arahael has joined #asahi
09:36nsklauswe'll see with time how things turn out, but i'd say it seems there's hope for both 4k kernel and fex running on asahi
09:36chadmedregardless, gentoo support for AArch64 is, for my use case, mature so the only thing id need fex for at all is running counter-strike which is an experiment i hope to have time for once im done with uni for the year
09:38j_eyanyone else interested in VoidLinux on the m1?
09:39nsklausvoid and artix too
09:39chadmedi have a friend who would
09:44chadmedmarcan seems pretty keen on spinning up an arch root fs already so no worries there
09:45miniI actually have genuinely thought about using a m1 mac mini as a low power high performance home router - especially once thunderbolt works
09:47chadmedi had intended to do one for gentoo like genpi64 but i think the fact that everything is being upstreamed makes installing gentoo similar enough to the amd64 handbook that it shouldnt really need any extra work once youve got a stage3 expanded into the root partition, which you can do from macos.
09:49MagMell[m]s/My payload: http://athome.utopiosphere.net:2345/asahi.macho with alyssa config/My payload: http://athome.utopiosphere.net:2345/asahi.macho (kernel with alyssa config)/
09:50tylo1 has quit [Ping timeout: 480 seconds]
09:51j_eychadmed: its a shame theres no handbook yet though
09:51MagMell[m]s/My payload: http://athome.utopiosphere.net:2345/asahi.macho with alyssa config/My payload: http://athome.utopiosphere.net:2345/asahi.macho (kernel with mu-one/linux no rebase and alyssa config)/
09:52tylo1 has joined #asahi
09:52chadmedj_ey: i dont think its a good idea for anyone to try write an arm64 handbook. every platform is so different at this stage that the whole thing will just be littered with quirks and "only do this step if youre using the namajeff computing 69420 board" notes that it would be practically worthless. now that apple has popularised arm workstations, maybe the ecosystem can settle on a platform/boot standard and a handbook
09:52chadmedcould be written
09:53GlanzmannMagMell[m]: I can reproduce your issue on my system. But do you have used alyssa's tree?
09:53j_eychadmed: at least most of the install / setup phases could be similar
09:54Glanzmannj_ey: I think its just a matter of which rootfs to extract.
09:54chadmedas it stands though, the entire process of installing is similar enough to amd64 that once youve written a short article on how to get a kernel booted on $DEVICE then its all very much the same once youve got a stage3 on to the device's mass storage
09:54MagMell[m]Glanzmann: I use mu-one/linux 20211005 branch
09:55GlanzmannMagMell[m]: I used 20211003. Let me retry with 20211005.
10:01tylo1 has quit [Ping timeout: 480 seconds]
10:02GlanzmannMagMell[m]: Try my kernel and see if it works for you: https://ab34.de/u/Image.gz
10:02GlanzmannMagMell[m]: I'm building on Debian stable (bullseye).
10:02MagMell[m]I wonder if you don't specify the root here, will it show the available root partitions?
10:02GlanzmannMagMell[m]: Yes, it does.
10:03GlanzmannShould I reboot and try to be absolutly sure?
10:03MagMell[m]No, I trying...
10:04everslick has quit [Remote host closed the connection]
10:04everslick has joined #asahi
10:05GlanzmannI tried, scrolls down to fast, I can put a hdmi grabber inbetween.
10:07svenpretty sure at least the dtb in that file is wrong. it also doesn't seem to be compiled with ans nvme support
10:08svenhrm. or maybe it is
10:09svener, wait. i think i messed up. let me check again
10:10GlanzmannMagMell[m]: yes, it does. See video of hdmi grabber: https://ab34.de/u/output.mkv
10:12GlanzmannMagMell[m]: I would follow the steps to the point, get a working version, than deviate to whatever you want to do.
10:13MagMell[m]Glanzmann: I'm wondering if I should get a USB 3.0 cable, now I'm using kmutil to write the payload in, and then the kernel wrote the root path, but it's still very strange, my compiled kernel shows that the available root partition is empty
10:13MagMell[m]* I'm using `kmutil, * kmutil` to
10:13MagMell[m]* I'm using `kmutil, * kmutil` to, * root path (using `CMDLINE`), but
10:15svenMagMell[m]: the device tree in your payload is wrong
10:15GlanzmannMagMell[m]: I use a usb 3 cable from an amd64 box to the m1n1.
10:15svenit doesn't contain any nodes for usb, nvme, etc.
10:15svenyou must use the device tree from the mu-one branch if you want this to work
10:15Glanzmannsven: How did you extract the payload?
10:15MagMell[m]sven: oh...
10:16svenGlanzmann: vim + xxd
10:16Glanzmannsven: I see. :-)
10:16j_eyGlanzmann: by reverse engineering
10:16j_eysven cant get enough of it!
10:16GlanzmannI thought you have fancy tool for that.
10:16j_eybinwalk could do it maybe?
10:17* svensometimes compiles code just to be able to look at it in objdump or something to strip away annoying abstractions :D
10:17chadmedMagMell: alyssa uses an initramfs if im not mistaken, so its possible that she has some of the things you need set to Y built as modules and loaded by her initramfs
10:17j_eysven: >:D
10:17chadmedyoull need to tailor your config accordingly
10:17svenpretty sure it's just the devicetree that's wrong
10:17chadmednamely, build BLK_DEV_APPLE_NVME set to * not M in menuconfig
10:18Glanzmannchadmed: She, does _not_.
10:18j_eyGlanzmann: nice, I think then you can use dd with offset=N to get the dtb out
10:18j_eyGlanzmann: oh, apparently binwalk can extract
10:19Glanzmannj_ey: Yes, it can, just did it.
10:27chadmedawesome, congrats :D
11:19yrlf has quit [Quit: The Lounge - https://thelounge.chat]
11:20yrlf has joined #asahi
11:21yrlf has quit []
11:22yrlf has joined #asahi
11:55povikalyssa: finally got myself a full computer per your suggestion the other day
11:55poviknow i can do
11:55povikroot@rootfs:~# apt-get install alsa-tools
11:55povikalso, the trick to running in hypervisor was masking the right devices in DT
11:55povikm1n1 only does that for you in the ADT of course
11:56rowang077[m] nani I thought the internal speaker would be something like just beeps but this is actual "real" audio?
11:57povikif you mean the proof of concept driver in m1n1, then that is real audio
11:57povikdont know of any other speaker
11:57marcaninternal beep speakers have never been a thing on macs
11:58marcanI think even the very first one had a real speaker with real PCM audio
11:59rowang077[m]I see. Cool 🙂
12:00alyssaj_ey: "I thought alyssa was using 4K.." ....lol
12:00alyssangl I wouldn't mind a 16k display :-p
12:00alyssachadmed: FEX is not released and neither is Asahi. Give it time.
12:01alyssapovik: good :-)
12:02alyssachadmed: I use an initramfs containing the broadcom wifi firmware and that's it. And if you're not doing wifi, you can skip that.
12:05povikuh, i want alsa-utils not alsa-tools
12:18c10l has joined #asahi
12:51tylo1 has joined #asahi
12:54chadmed has quit [Remote host closed the connection]
12:54chadmed has joined #asahi
12:59tylo1 has quit [Ping timeout: 480 seconds]
13:37yuyichao_ has quit [Ping timeout: 480 seconds]
13:43alyssaok, I have now run out of excuses to not do my homework right now..
13:43alyssai have the next 5 hours blocked off for it. will it get done? sigh
14:10chadmed has quit [Remote host closed the connection]
14:11chadmed has joined #asahi
14:25jbowen has quit [Ping timeout: 480 seconds]
14:27jbowen has joined #asahi
14:37jbowen has quit [Ping timeout: 480 seconds]
14:38jbowen has joined #asahi
14:50jbowen has quit [Ping timeout: 480 seconds]
14:57jbowen has joined #asahi
15:07jbowen has quit [Ping timeout: 480 seconds]
15:18povik has quit [Quit: Page closed]
15:20jbowen has joined #asahi
15:30yuyichao_ has joined #asahi
16:22tylo1 has joined #asahi
16:33yuyichao has joined #asahi
16:37yuyichao_ has quit [Ping timeout: 480 seconds]
16:38jbowen has quit [Ping timeout: 480 seconds]
16:48Glanzmannalyssa: Next time ask me, I'll give you reason not to make homeworks. For example, I tried the Xserver hdmi hotplug. Still not working. :-)
16:49alyssaGlanzmann: glances between pile of LaTeX+notebooks and Linux tree with DCP driver
16:49* alyssasweats
17:03___nick___ has joined #asahi
17:17uncannedbean has joined #asahi
17:17uncannedbean has left #asahi [#asahi]
17:20Glanzmannalyssa: Go ahead and do your homework, you'll have the rest of your life for writing drivers. :-)
17:22alyssaI also have the rest of my life to learn...
17:23ZestOfBeans has joined #asahi
17:25ZestOfBeans has quit []
17:31Glanzmannalyssa: You'll do that anyway. :-)
17:33ZestOfBeans has joined #asahi
17:33ZestOfBeans has quit []
17:35jbowen has joined #asahi
17:52ZestOfBeans has joined #asahi
18:05ZestOfBeans has quit [Remote host closed the connection]
18:06ZestOfBeans has joined #asahi
18:07ZestOfBe_ has joined #asahi
18:08ZestOfBe_ has quit [Remote host closed the connection]
18:09ZestOfBe_ has joined #asahi
18:14ZestOfBeans has quit [Ping timeout: 480 seconds]
18:17ZestOfBe_ has quit [Ping timeout: 480 seconds]
18:22yuyichao_ has joined #asahi
18:24kubes has joined #asahi
18:25yuyichao has quit [Ping timeout: 480 seconds]
18:33ZestOfBeans has joined #asahi
18:36nsklausanyone knows a nice way to move macos away from internal storage to external hdd ? (if possible keep it bootable on the external device, if it is plugged in)
18:43ZestOfBeans has quit [Ping timeout: 480 seconds]
18:45nico_32M1 is not able to boot from external device
18:46VinDuvThe safest way would probably be to install macOS on the external device, and at first boot, use the migration assistant to copy the data from the internal storage
18:46VinDuvbut yes, the M1 needs a pre-boot partition on internal storage to be able to boot from external AIUI
18:47VinDuvNot sure if it’s easy to remove the “internal” macOS install without rendering the “external” one unbootable…
18:47arndI did manage to boot macOS from an external thunderbolt drive, the entire OS other than the pre-boot partition can be on that in principle, you just can't boot Linux that way (yet), and you can't do it on a non-thunderbolt USB drive
18:48nsklausnico_32: i think i made a bootable macos big sur 11.2 on an external device a few month ago. the boot loader may need to be on the internal device but beside that it is possible to have the whole macos on an external device and boot it
18:50nsklausi was thinking of migrating the already installed macos from internal storage to an external one, but if it get cumbersome to do, then maybe i'll just nuke it all and make a fresh install on an external drive.. and have linux only on internal storage (in addition to the 1TR partition for actualy booting)
18:52ZestOfBeans has joined #asahi
18:54MagMell[m]This is usb3 known issue?
18:55arndnsklaus: not sure you can actually do a fresh install to an external drive without having a working macos on the internal one.
19:02MagMell[m]<MagMell[m]> "image.png" <- No...my ssd is dead :(
19:03erincandescent has quit [Remote host closed the connection]
19:04erincandescent has joined #asahi
19:06nsklausarnd: when i tried having a macos installed on an external drive a few months ago, i also had another copy of it on the internal drive, so you may be right about this, i'll have to try it to confirm if it's possible or not to have only one install of macos and have it on external drive
19:07nsklausmy ideal setting would be to have macos on an external drive, just in case i happen to need it, (but i don't plan to particulary use it much) and have maximum space for linux on the internal drive
19:08nsklaushaving both macos and linux on the internal disk is too much waste of space for my taste
19:12arndyes, definitely. there is a good chance it actually works, I just mentioned it so you don't accidentally break something important if you rely on it and it doesn't work
19:14svenMagMell[m]: fwiw, there is no usb3 support yet. the usb c ports only support usb 2 for now
19:16svenah, or maybe you used the usb a ports. those support usb 3 already
19:17MagMell[m]sven: Is this in mu-one/linux 20211003?
19:18JTL has quit [Remote host closed the connection]
19:18sven"this"?
19:18sventhe only kernel that currently supports usb 3 on the usb c ports is corellium's
19:23MagMell[m]sven: oh, ok
19:26nsklausarnd: i understand, thanks for telling
19:28yuyichao has joined #asahi
19:31ifthenelse has quit [Quit: Ping timeout (120 seconds)]
19:32yuyichao_ has quit [Ping timeout: 480 seconds]
19:38ifthenelse has joined #asahi
19:38JTL has joined #asahi
19:46kubes has quit [Quit: Leaving]
19:50ZestOfBeans has quit [Ping timeout: 480 seconds]
20:00ZestOfBeans has joined #asahi
20:00GlanzmannMagMell[m]: You ssd should be nvme... not sda.
20:01yuyichao_ has joined #asahi
20:01MagMell[m]Glanzmann: It's because my SSD is connected to a USB3 box
20:03GlanzmannOic. I thought you use the internal nvme.
20:04yuyichao has quit [Ping timeout: 480 seconds]
20:08ZestOfBeans has quit [Ping timeout: 480 seconds]
20:51ZestOfBeans has joined #asahi
20:58ZestOfBe_ has joined #asahi
20:58yuyichao has joined #asahi
21:01yuyichao_ has quit [Ping timeout: 480 seconds]
21:04ZestOfBeans has quit [Ping timeout: 480 seconds]
21:19tylo1 has quit [Ping timeout: 480 seconds]
21:40ZestOfBe_ has quit []
21:41Nspace has joined #asahi
21:41tylo1 has joined #asahi
21:43Nspace has quit []
21:43___nick___ has quit [Ping timeout: 480 seconds]
21:54yuyichao_ has joined #asahi
21:56doggkruse has joined #asahi
21:57yuyichao has quit [Ping timeout: 480 seconds]
21:59jbowen has quit [Quit: leaving]
22:12alyssaMagMell[m]: all the USB support in mu-one/linux is sven's code, not corellium's
22:13alyssaso.. no usb 3 on the type-c's, but also close to mainline now
22:18aleasto has quit [Quit: Konversation terminated!]
22:39doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
22:50yuyichao_ has quit [Quit: Konversation terminated!]
22:50doggkruse has joined #asahi
22:50doggkruse has quit []
22:51yuyichao has joined #asahi
22:54doggkruse has joined #asahi
23:10doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
23:17yuyichao_ has joined #asahi
23:21yuyichao has quit [Ping timeout: 480 seconds]
…