#
…

2023-04-13

00:47zerdox has quit [Remote host closed the connection]
01:42hightower3 has joined #asahi-alt
01:49hightower2 has quit [Ping timeout: 480 seconds]
01:59zerdox has joined #asahi-alt
02:03zerdoxMichaelLong did you encounter `thread 'main' panicked at '"ftrace_branch_data_union_`? I am trying to compile the kernel finally. I found one guy in rust-for-linux zulip chat, he met this error 2 months ago. and i also googled some email from 5 april mentioning my error
02:31chadmed_zerdox: at runtime?
02:32zerdoxchadmed_: trying to genkernel
02:33chadmed_i dont think genkernel really supports rusty kernels atm, youll have to do it manually
02:33chadmed_its not that hard
02:35zerdoxdo i need to do something different in asahi case? instead of --all-ramdisk-modules
02:37chadmed_so youve built the kernel already and youre just trying to make an initramfs?
02:44zerdoxchadmed i have not yet built anything
02:46zerdoxit doesn't matter if i run genkernel or make LLVM=1. i get thread panicked while compiling kernel
02:48chadmed_hm so the compiler is panicking interesting
02:48chadmed_did you install rust-bin or rust
02:48chadmed_ah so you followed the quick start guide
02:49chadmed_can you paste the entire build log somewhere
02:49zerdoxsure. for now i'll send these 2 links
02:58zerdoxnothing interesting in logs actually. i am using default asahi kernel config just with rust enabled. my rustc and bindgen versions are exact required. i am using 16 llvm
02:58chadmed_is bindgen in your PATH?
02:59chadmed_also just building the config in /proc/config.gz wont enable the gpu or dcp. you need to go and set those options in menuconfig.
02:59zerdoxof course. /home/user/.local/share/bin/bindgen
03:00chadmed_??? it should be in $HOME/.cargo/bin
03:01zerdoxi don't like littering my $HOME
03:01zerdoxi changed CARGO_HOME and RUSTUP_HOME
03:01zerdoxthat's normal case. lol
03:02chadmed_does seem like a bindgen issue at the very least
03:02chadmed_what version of rustc have you set for the kernel source tree
03:03zerdoxhow can i see it? i've pinned rustc version as in quick start and then added rust-src component
03:03chadmed_rustc --version from inside /usr/src/linux
03:04chadmed_you should mirror this as root, idk if genkernel tries to build the kernel as root
03:04chadmed_but as a standard user you dont have write perms to /usr/src so ofc its gonna fail writing bindings there
03:04zerdoxyeah i am as root
03:05chadmed_yeah so youll need to set up the rust stuff as root and source $CARGO_HOME/env as root
03:05zerdoxrustc 1.66.0 (69f9c33d7 2022-12-12)
03:06zerdoxi've already set all this up. running make rustavailable as root gives me "rust is available "
03:07chadmed_just running through the possibilities
03:08chadmed_it does look like youve misconfigured bindgen somewhere along the line though
03:08chadmed_since its panicking in a dependency of bindgen
03:09zerdoxi haven't done any configurations to bindgen
03:09zerdoxi'll try to reinstall it...
03:09chadmed_yeah i mean the install process
03:10chadmed_you should probably just install all of this as root instead of trying to kludge its CARGO_HOME to your local user tbh
03:10chadmed_like i said from the outset it becomes very hard to offer support to people when they start doing weird nonstandard things and stuff starts breaking
03:11zerdoxwdym?... cargo_home is in user's hom directory by default
03:12chadmed_when you install as root it should install it to the root's home directory, not yours
03:12chadmed_the fact that its trying to call into bidngen from your own home dir instead of /root/.cargo/ suggests you have not set any of this up properly
03:12zerdoxok. one moment
03:29zerdoxwhich rustc: /root/.cargo/bin/rustc
03:29zerdoxwhich bindgen: /root/.cargo/bin/bindgen
03:29zerdoxrustc --version: rustc 1.66.0
03:29zerdoxbindgen --version: bindgen 0.56.0
03:29zerdoxeverything is the same. same panick. i'll now cleanup my root...
03:30chadmed_try bindgen 0.62
03:34zerdoxno Cargo.lock file published in bindgen v0.62.0
03:34zerdoxthere is nothing to install in bindgen because it has no binaries. cargo install is only for installing programs, and can't be used with libraries
03:35chadmed_the crate is called bindgen-cli
03:35zerdoxam i doing something wrong?
03:35chadmed_cargo install bindgen-cli --version ^0.62
03:39zerdoxyay. it's doing something... i will try to login to my user now and continue the work with the newer bindgen. could you please share which settings do i need to change so my gpu would work properly?
03:41chadmed_CONFIG_RUST=y, CONFIG_DRM_ASAHI=m, CONFIG_DRM_APPLE=m
03:41chadmed_youll be able to find the config options in menuconfig by searching for them
03:41chadmed_ you already have dracut installed which has the appropriate firmware and driver hooks set up from the install script, so instead of using genkernel to generate an initramfs use dracut --kver $(make -s kernelrelease)
03:50cylm has joined #asahi-alt
04:50zerdoxchadmed_: ty. i successfully compiled and applied new kernel. but as soon as i boot in, see some linux init logs and login prompt, screen goes black. nomodeset "fixes" it
04:51zerdoxidk why i am so unlucky but everything on my machine goes unexpected. sorry
04:51chadmed_oh yeah thats an xorg/dcp thing
04:52chadmed_xorg relies on features that are not present in the hardware because its not 100 quadrillion years old
04:52zerdoxxorg? i thought it's some stuff for graphical environment, like wayland
04:53chadmed_your display manager (i assume sddm) probably uses xorg so when openrc goes to start it, it causes issues
04:53chadmed_wayland works perfectly
04:53zerdoxits just tty
04:53zerdoxnothing xorg or wayland
04:53zerdoxno DMs to
04:53chadmed_oh interesting
04:53chadmed_is that reproducible
04:53chadmed_like does it happen every time you boot
04:54zerdoxprob i need to get some logs
04:54zerdoxyea i got it twicr
04:55chadmed_can you check to make sure that the display-manager service is not in any runlevel
04:55zerdoxi have not even installed any
04:56zerdoxlike i barely installed this system and trying to get hyprland work with my gpu
04:57chadmed_so before, when you booted, the system just greeted you with a tty
04:57chadmed_you didnt have hyprland starting automatically or anything
04:58chadmed_did you install the kernel manually or use genkernel
04:58zerdoxtty goes bye-bye when driver module gets loaded. seems like it
04:58zerdoxmanually
04:59chadmed_and you ran make modules_install right
04:59zerdoxi will try to do it again actually
04:59possiblemeatball has quit [Quit: Quit]
04:59chadmed_the output of asahi-diagnose would be cool pasted somewhere
04:59chadmed_and your dmesg
05:00chadmed_ill get around to patching asahi-diagnose for gentoo at some point
05:00zerdoxhow can i do it?
05:00chadmed_assuming you didnt nuke the old kernel and initramfs grub should still have a boot option for it under advanced settings
05:00chadmed_so you can boot back into a working system
05:00zerdoxi can boot back to the new kernel with nomodeset option
05:01zerdoxand yeah i can still load to the old kernel
05:01zerdoxcurrently i am booted with nomodeset
05:01chadmed_oh yeah then just run asahi-diagnose and paste the output somewhere
05:02chadmed_you can write a little shell function/alias to pipe the output of some command into tpaste
05:02chadmed_do the same with dmesg since asahi-diagnose looks for journalctl and not dmesg
05:03zerdoxtake into account that nomodeset is enabled
05:04zerdoxjust save dmesg output? i am not sure how it works
05:04chadmed_yeah dmesg is just the kernel message log so just paste the output of it
05:04zerdoxmaybe i can also ssh from my phone to the system without nomodeset so you can actually see the errors?
05:05chadmed_yeah that would be good because it hasnt loaded the dcp driver at all
05:06chadmed_so i need to see what its doing when its loading that driver
05:06zerdoxlet me know if i need to repeat without nomodeset
05:06zerdoxyeah i see
05:07zerdoxcan you give me a hint how can i do it? last time with your advice i enabled sshd
05:07zerdoxi also have termux on my phone
05:08chadmed_well you just need another machine with ssh installed, then just ssh [username]@[mac hostname/ip address]
05:08chadmed_it will ask for your password
05:08chadmed_and dump you to a shell
05:18jamespmo_ has joined #asahi-alt
05:23jamespmorgan has quit [Ping timeout: 480 seconds]
05:36chadmed_hmm that lgtm
05:39zerdoxfor the context by black i mean i get no backlight. like it's completely off, when you turn down brightness to zero on macos
05:53zerdoxis it possible that my backlight level is set to zero? just in case...
05:58chadmed_thats what i was thinking
05:59chadmed_you can try change it with the sysfs variables in ssh
06:07zerdoxchadmed_: i can't really find exact file for that
06:08chadmed_itll be in /sys/class/backlight somewhere
06:09zerdoxyeah.. but is a bunch of folders which are symlinked to each other
06:22zerdoxi've installed `light` package and it says 33.33 on apple-panel-lb and 100.00 on gpio-bl. so this is not the case
06:36chadmed_ has quit [Remote host closed the connection]
06:41zerdox has quit [Read error: Connection reset by peer]
06:42zerdox has joined #asahi-alt
07:31cylm has quit [Ping timeout: 480 seconds]
08:02jn has quit [Read error: No route to host]
08:03ktz_ has joined #asahi-alt
08:03jn has joined #asahi-alt
08:06ktz_hello, on the conversation we had on #asahi, I mounted esp on /boot/efi and installed m1n1 and u-boot-asahi, when restarting I've had the exact problem I described when the same thing happened from an alarm update. I can get to boot and get to my DE but everything is incredible sluggish and I can't even use it. I'm currently booted from alarm now
08:07ktz_my problem is that alarm at least didn't entirely replace boot.bin, it was also leaving a boot.bin.old behind which I could replace the new one with and boot back normally, but alpine doesn't do that so I need to find some other way to fix it
08:09ktz_on a positive note I'm getting no errors on dmesg and a different one when trying to start an ap on alarm. keyboard and mousepad are also working as expected
08:13mpsktz_: so you have alarm and alpine installed iiuc
08:13ktz_mps: correct
08:14mpsthis is 'calling for troubles'
08:14ktz_I'm using alpine mainly, I've got the alarm installation for situations like these just for debugging
08:15ktz_I haven't had any of those problems for months to this point and I've always had both installed
08:15mpskernels are different and by this dtb is not same
08:15ktz_on two separate machines as well
08:16ktz_should that really be a problem since there are two different esps separate for each one?
08:16mpshow do you select which ESP is read on boot?
08:17ktz_that's a good question, I assumed its correctly mapped to the corresponding one up to this point
08:17mpsi.e. which second stage m1n1 is used
08:20mps`cat /proc/device-tree/chosen/asahi,efi-system-partition` will show which ESP is used
08:21mpsalso `cat /proc/device-tree/chosen/asahi,m1n1-stage2-version`, filename tells
08:27ktz_okay I'll reboot into alpine and check it out
08:30ktz_ has quit [Remote host closed the connection]
08:32ktz has joined #asahi-alt
08:32ktzmps: both alarm and alpine use the same partition
08:33mpsktz: that could be why you have problems
08:34ktzyes, thanks for helping me find out. is there anything I can do to fix it?
08:35mpsuse just one ESP, i.e. remove one you don't need
08:36ktz has quit [Remote host closed the connection]
08:37mpson alpine you should have something like 'PARTUUID=... /boot/efi auto auto' in /etc/fstab
08:40ktz has joined #asahi-alt
08:40jannaudo you have two entries for alpine and asahi in the macos boot picker you get when you keep the power button pressed?
08:40ktz_ has joined #asahi-alt
08:41ktz_jannau: yes, I do
08:42jannauthen you should get different values in /proc/device-tree/chosen/asahi,efi-system-partition for alarm and alpine
08:42ktz_mps: no I haven't..
08:43ktz_mps: this is likely the answer to the dtbs problem
08:44mpsktz_: you should mount proper ESP for /usr/sbin/update-u-boot-asahi to work properly
08:45mpswith PARTUUID in /etc/fstab you could have proper ones mounted for alpine and alarm
08:46mpsi.e. different ESPs for different OS
08:48ktz_on alarm I'm getting contradicting output or I'm missing something?
08:49ktz_maybe that's why when upgrading via pacman kept messing up my alpine installation
08:49jannau/proc/device-tree/chosen/asahi,efi-system-partition has PARTUUID not a UUID so it might not be a problem
08:51nsklaus has joined #asahi-alt
08:51jannaucan you check if UUID and PARTUUID point to the same partition. `blkid | grep vfat`
08:56ktz_it returns false :jannau
08:56ktz_maybe this helps
08:57ktz_nvme0n1p9 is alpinelinux and nvme0n1p5 is alarm
08:57jannauyou have a mismatch. UUID of 80281940-c4e6-40d8-b83f-f509a98c9338 is 8860-08F1
08:58ktz_should fstab contain both entries?
08:58jannauyou should be fine if you change "UUID=F7C9-0138" to "PARTUUID=80281940-c4e6-40d8-b83f-f509a98c9338" in fstab
09:00ktz_this is on alarm (nvme0n1p5) shouldn't it point to nvme0n1p4 instead? the one you suggested is nvme0n1p7 instead, alpine's esp
09:01ktz_thanks for trying to help in any case
09:03jannau/proc/device-tree/chosen/asahi,efi-system-partition is what m1n1 cares about. if the OS doesn't match it will cause problems. can you verify that it differs between alarm and alpine
09:05ktz_let me do the same booted via alpine
09:05ktz_ has quit [Remote host closed the connection]
09:05ktz has quit [Remote host closed the connection]
09:12ktz has joined #asahi-alt
09:12ktzokay, this is what I gathered from alpine
09:13ktzjannau: /proc/device-tree/chosen/asahi,efi-system-partition looks the same
09:16ktz has quit [Remote host closed the connection]
09:20ktz has joined #asahi-alt
09:26zerdox has quit [Ping timeout: 480 seconds]
09:28ktzmps: any idea at least on how to fix my alpine installation? its unusable as of now after adding u-boot-asahi and m1n1 packages and having m1n1 upgraded
09:31mpsktz: no idea for stable solution. you could mount proper ESP and /usr/sbin/update-u-boot-asahi
09:31mpsand copy m1n1/boot.bin to alarm ESP
09:32mpsto have same boot.bin on both ESP
09:32ktzI just ran /usr/sbin/update-u-boot-asahi, I'll try to boot on alpine
09:32ktz has quit [Remote host closed the connection]
09:33mpsbut my real advice is 'use alpine only', not because alpine is perfect (it is not) but other distros are worse (sorry if I offend someone)
09:33_jannau_that doesn't help if both first stage m1n1 set te same "asahi,efi-system-partition"
09:34mpsor other advice is stick with one prefered distro until m1n1 can select proper ESP
09:35_jannau_no idea how that could have happened without manually breaking things
09:36_jannau_m1n1 does that. the only problems we had where distro packaging unpatched u-boot which doesn't use the slected ESP
09:37ktz has joined #asahi-alt
09:41ktzso the way to fix my issue is having alarm deleted? that won't really bring back the boot.bin version which makes my boot functional in the alpine esp, am I wrong?
09:42ktzthe m1n1 is lastly updated via alpine so even if both use it, it should likely be fine with alpine I suppose
09:43mpsas jannau told, maybe patched u-boot could help
09:43_jannau_running /usr/sbin/update-u-boot-asahi on alpine should produce a working boot.bin
09:44ktzyes but it doesn't as I just mentioned
09:44_jannau_a patched u-boot will not help as long as both installs report the same "asahi,efi-system-partition" when selected through the macos boot picker
09:45mpsktz: if you want you can install linux-asahi-edge and mesa-asahi for alpine from my private repo
09:45mpsI'm sure this combo works very fine on m1 and m1pro macbooks
09:46ktzI hadn't booted each one via macos tho, I did run distro_bootcmd to boot in alarm instead
09:46mps(time for coffee break)
09:47cylm has joined #asahi-alt
09:47_jannau_ktz: that can not work and probably explains your problems. you have to use the macos boot picker for multi alternative os support
09:53ktzokay, good to know thanks. I'll try mps' edge kernel and hopefully this fixes the issues on my alpine installation
09:54cylm_ has joined #asahi-alt
09:56cylm has quit [Ping timeout: 480 seconds]
10:07mpsthen `apk update` and rest you know
10:07ktzthanks
10:08mpsthough you will need different script which will set m1n1+dtbs+u-boot if you install linux-asahi-edge
10:09ktzdo you have it?
10:09ktzso I run this after the apk add?
10:10ktzcheck the link of the key
10:18mpsmarcan: I ported PKBUILDs for asahi-scripts and asahi-fwextract from asahi to alpine APKBUILD. but I'm not sure what to do with 'Maintainer' field. on one side all credits belongs to you because porting was easy
10:19mpsbut on other side it is not good to report to you issues for alpine
10:19mpsdon't know what to do with this field
10:20stipa is now known as Guest10828
10:20stipa has joined #asahi-alt
10:22Guest10828 has quit [Read error: Connection reset by peer]
10:23chadmedmps: i assume the convention is the maintainer of the package, not the maintainer of the code
10:24chadmedat least thats how it is with gentoo ebuilds
10:24ktz has quit [Remote host closed the connection]
10:25mpschadmed: I agree, but because PKGBUILD and APKBUILD are nearly same I though it would be polite to ask author (marcan) of these two PKBUILDs
10:26chadmedoh right the files themselves are similar
10:26chadmedtwo maintainers i guess :P
10:26mpsalpine allow only one maintainer
10:27mpsand many 'Contributor: '
10:27jamespmorgan has joined #asahi-alt
10:28_jannau_I'd sugest to take the maintainership and add a comment that it is based on the asahi PKGBUILD
10:29_jannau_the original author doesn't maintain your copy
10:29ktz has joined #asahi-alt
10:29mps_jannau_: this sounds reasonable to me, I thought to do this but again wanted to ask original author
10:30ktzI still face the same issue, boots, can open my wm but everything is unusably slow
10:31mpsktz: you use xorg?
10:31ktzno, wayland
10:32mpsand it is slow?
10:33jamespmo_ has quit [Ping timeout: 480 seconds]
10:33ktzits unusable, for instance it takes 2 sec to spawn foot and when you type a letter it registers 3+ times
10:33mpsfor me xorg and wayland are nearly same
10:33mpsapk version mesa-asahi
10:34chadmed has quit [Ping timeout: 480 seconds]
10:34ktzits the same exact issue I had with the last kernel, its not related to the upgraded kernel, its the boot.bin which causes it
10:35mps`apk version u-boot-asahi`
10:35mpsand also version of m1n1
10:36mpsare you sure you installed mesa-asahi and mesa-asahi-dri-gallium
10:37chadmed has joined #asahi-alt
10:38psykose has joined #asahi-alt
10:39ktzI was missing dri-gallium but I don't that's the cause, its related to m1n1
10:39psykoseyou would need all of the mesa-asahi-* packages as overrides, in that case you are missing mesa-asahi-dri-gallium
10:39mpsoh, you have both mesa and mesa-asahi installed, this should be possible
10:40psykosedon't think it is
10:40mpspsykose: rihgt, I meant to write 'not possible'
10:41ktzyes I see mesa-glapi-23.0.2-r2 aarch64 {mesa} (MIT SGI-B-2.0 BSL-1.0) [installed], let me replace it with the asahi version and I'll try to boot again
10:42psykoseyou need mesa-asahi-dri-gallium to have anything work pretty sure :p
10:42psykoseyou also don't have to reboot, just restart whatever you had the session in
10:42ktzI'm booted from alarm now
10:43ktzand chrooted in alpine
10:43mpsktz: you are messing my mind, never sure when you are talking about alpine or alarm
10:45ktzalways alpine, I only use alarm when I can't boot into alpine, and when booted on alarm I'm talking alpine chroot so alpine
10:45mpsbut I see from your dmesg that you booted alpine
10:46_jannau_generally don't expect graphics to work from the alpine chroot
10:46ktz has quit [Remote host closed the connection]
10:47j`ey__jannau_: you've said before that DCP is slow without the GPU right? So I guess that's what they're seeing
10:47mpsj`ey_: also I think so
10:48mpsfew days ago when I upgraded to mesa with changed UAPI version it was slow
10:49ktz has joined #asahi-alt
10:49_jannau_it slower than software rendering but not 2 seconds to launch foot slow. that could the subotimal kmsro behavior people where seeing on fedora with many kmsro drivers enabled
10:50ktzokay thank you all guys, at least I'm back on my system
10:50ktzeverything works properly
10:50mpsktz: alpine or alarm
10:50ktzwith the edge kernel and all the mesa-asahi packages
10:51ktzalpine as always hehe
10:51mpsok, you now have GPU working
10:51ktzonly thing, still missing keyboard on wm, while it works on tty
10:51mps`inxi -G` will show
10:51dottedmag has joined #asahi-alt
10:52mpsktz: are you using eudev or libudev-zero
10:53ktzhttps://0x0.st/H8rw.txt you get these as well when loading brcmfmac?
10:53mpsthen input devices should work out of the box
10:54j`ey_ktz: yeah that's normal
10:54j`ey_it tries diffferent firmware names in a row, to get the right one
10:54mpsyes, same on my machines
10:55mpsktz: do you external usb keyboard
10:56ktz has quit [Remote host closed the connection]
10:57mpsktz: btw, you now have asahi-scripts and asahi-fwextract in my apk repo
10:58ktz has joined #asahi-alt
11:00ktzmps: yes I use an external one but I'm trying to get the builtin one functioning as well so its portable, same for mousepad, not sure whats wrong with them
11:01ktzmps: should I run any of those?
11:02mpshave no idea, internal keyboard and touchpad works for me from the beginnig (year and a half ago) without problems
11:03ktzby the way is this https://gitlab.alpinelinux.org/alpine/aports/-/issues/14577 akms thing any easy to fix? psykose:
11:04ktzyes its strange, even the other firmware errors are gone from dmesg now... but still no luck. Maybe its something to do with wayland/sway in the end
11:05mpsktz: you could try to install linux-asahi-edge-dev and fix this to use it and then try to build
11:05mpsdo the wayland need some config file for libinput to work
11:05mpsi have something in sway config
11:06ktzit used to work perfectly for my previous m1 air, same sway config...
11:06mps.config/sway/config.d/input => https://tpaste.us/EJb6
11:06mpsthis works with sway
11:09mpsbtw, any better tilling WM for wayland than sway
11:11ktzdidn't work for me
11:12ktzapk add linux-asahi-edge-dev https://0x0.st/H8rl.txt by the way
11:16psykoseseems pretty self explanatory
11:20mpshm, linux-asahi-edge have CONFIG_MODULES=y
11:53ktz has quit [Remote host closed the connection]
11:57marcanmps: maintainer != author, you're the maintainer for the APKBUILD, not me
11:58marcanfeel free to note the origin of the script if you want, though I personally don't particularly care
11:58mpsmarcan: ok, thank you
11:58marcanI don't think we have a license on that repo explicitly, we probably should, but I basically consider everything in there (except for patches subject to upstream licensing) public domain for any distro to adapt as they wish
12:00mpsthat is also issue for alpine APKBUILD files
12:00marcanif we didn't have derivative PKGBUILDs in there I would add a blanket MIT-0 to the repo
12:01marcanlet me add something
12:01chadmedhopefully the patched packages go away at some point
12:01marcanwell this includes uboot-asahi which won't
12:01marcanand linux-asahi and mesa-asahi which will probably live forever as downstream bleeding edge packages if nothing else
12:03jannauack for my contributions as far as they aren't derivative
12:03marcanwas about to ask
12:04marcanand the remaining contributions are few and very trivial, so I think I can just do this
12:06jannaualso questionable if they fall at all under copyright (depending on the legislation). not much freedom to express them differently and still have working packages
12:09marcanyeah, agreed
12:09marcanbut I might as well clarify in case someone thinks they do
12:18chadmedafaict pkgbuilds are unlicenced upstream anyway
12:23psykoselicensing is enjoyed by people that sell things
12:24chadmedinformation should be free (unless it can make me a billion dollars in which case people should pay me a billion dollars for it)
12:24possiblemeatball has joined #asahi-alt
12:49mpslicenses and other intellectual property are invented as exploitation tools
12:49mpswho owns IP on wheel
12:49ChaosPrincessdisney or nestle
12:50ChaosPrincessits always one of these two
12:50mpsChaosPrincess: you make me smiling loudly
12:50mpsnice one
12:52chadmedor some company no ones ever heard of but is worth $600bn and 30% owned by palantir
12:59zerdox has joined #asahi-alt
13:29zerdox has quit [Read error: Connection reset by peer]
14:03j`ey_ is now known as j`ey
14:22zerdox has joined #asahi-alt
15:38possiblemeatball has quit [Quit: Quit]
15:39possiblemeatball has joined #asahi-alt
16:00cylm_ has quit [Quit: WeeChat 3.6]
16:05jn has quit [Remote host closed the connection]
16:06jn has joined #asahi-alt
17:23lawrence8 has joined #asahi-alt
17:29lawrence has quit [Ping timeout: 480 seconds]
17:29lawrence8 is now known as lawrence
17:58possiblemeatball has quit [Quit: Quit]
18:07avi has joined #asahi-alt
18:09avi has quit []
18:42pthariensflame has joined #asahi-alt
19:00pthariensflame has quit [Quit: Textual IRC Client: www.textualapp.com]
19:36possiblemeatball has joined #asahi-alt
21:41nsklaus has quit [Quit: ZZZzzz…]
22:04possiblemeatball has quit [Quit: Quit]
22:49chadmed_ has joined #asahi-alt
…