marcan changed the topic of #asahi to: Asahi Linux: porting Linux to Apple Silicon macs | Not ready for end users / self contained install yet. Soon. | General project discussion | GitHub: https://alx.sh/g | Wiki: https://alx.sh/w | Topics: #asahi-dev #asahi-re #asahi-gpu #asahi-stream #asahi-offtopic | Keep things on topic | Logs: https://alx.sh/l/asahi
mrkajetanp has quit [Ping timeout: 480 seconds]
yuyichao has quit [Ping timeout: 480 seconds]
al3xtjames3 has joined #asahi
al3xtjames has quit [Read error: Connection reset by peer]
al3xtjames3 is now known as al3xtjames
hendry has quit [Quit: WeeChat 3.4]
hendry has joined #asahi
zamadatix has joined #asahi
<zamadatix>
Is uninstall to do a clean slate re-install as simple as clearing out the volume or are there more steps to do it properly?
<chadmed>
(ive made changes to the FIRs since the last bunch, these ones are a bit nicer
<chadmed>
also theres an installer script that does everything automatically for you
kov has quit [Quit: Coyote finally caught me]
kov has joined #asahi
jochum_ has joined #asahi
jochum has quit [Ping timeout: 480 seconds]
marvin24_ has joined #asahi
marvin24 has quit [Ping timeout: 480 seconds]
<bluetail[m]>
chadmed: The DSP will only apply to the internal speakers, right? If I were to use a interface, it wouldn't receive the changes, right?
<marcan>
yes
<marcan>
either way the way this is done now isn't likely to be the way we actually do it in the long term
<chadmed>
i mean all that really needs to change is for pipewire and wireplumber to actually provide features we need, like hiding an interface
<chadmed>
i dont see an issue long-term with the architecture of this setup other than its not totally seamless to the end user, which again is just pipewire/wireplumber lacking features
<chadmed>
i watched the entirety of kiagiadakis's presentation on managing streams via wireplumber scripts and nothing it can do is really what we want which really sucks
gladiac has joined #asahi
the_lanetly_052 has joined #asahi
the_lanetly_052 has quit [Ping timeout: 480 seconds]
<marcan>
yeah, that's what I mean, we need pw/wireplumber feature changes to automate it
<marcan>
and ideally the DSP description should be somewhat decoupled from that single sound system
<marcan>
the problem we're trying to solve here isn't "decent audio for macbooks", it's "linux still doesn't have any kind of database/configuration system for speaker DSP at all"
<bluetail[m]>
It’s a privilege to converse with you all. Love you.
<tmlind>
mps: i configured my m1 air lid open/close with the busybox acpi scripts along what pmos does for n900 slider, see the files at http://muru.com/linux/m1/etc/
<tmlind>
mps: afaik the acpi.map works only if busybox is started as acpid
<tmlind>
not sure what's the best way to deal with this for other distros that don't use busybox acpid
MajorBiscuit has joined #asahi
<mps>
tmlind: yes, that is how I do set events handlers for different things on my machines, and I think it is right method for busybox acpid
<mps>
tmlind: interesting thing is that I also set nearly same scripts for slider on n900
<mps>
tmlind: other (non busybox based) distros uses acpid2 package, and it is added in alpine few months ago (so also in postmarketOS) so it can be also used but the config is different
<tmlind>
mps: ok
<mps>
you are using pmOS on M1 or alpine?
<mps>
tmlind: ^
<mps>
on alpine busybox acpid applet is symlink to busybox and it is started by default after alpine is installed with setup-alpine
<tmlind>
mps: no, just plain alpine but using the pmos n900 slider config
<tmlind>
mps: hmm yeah i just untarred and run some parts of the setup scripts..
* tmlind
bbl
<mps>
tmlind: I started writing guide about using acpi.map and scripts about events handling with BB acpid about year ago but didn't finished yet
<mps>
as usual, I don't finish much of my writings :)
ChaosPrincess has joined #asahi
OwOwA has joined #asahi
<tmlind>
mps: well at least the events are somewhat documented in that pmos pull req
<tmlind>
anybody have experimental patches or info somewhere on the m1 backlight brightness?
<tmlind>
other than the 0 and 1 values that is :)
<j`ey>
nope
<tmlind>
ok, maybe it's some pmic pwm controller?
<firefox317>
tmlind, nope its controlled by the dcp, if you are talking about the backlight of the screen
<tmlind>
firefox317: ok yeah the lcd backlight brightness
<firefox317>
tmlind, yep so thats controlled by the dcp. We do have an initial driver for dcp written by alaysa and jannau, so it might not be to hard to add the required functionality
Major_Biscuit has joined #asahi
<tmlind>
firefox317: ok, additionally to dcp, i guess it could be there is some lcd bridge chip or i2c device too with pwm and dcp only controls the gpio for the bridge?
<bluetail[m]>
Is it possible to automatically connect to Bluetooth devices once they are visible? On macOS itself it isn’t, only through Automator.
<j`ey>
BT doesn't work yet
<bluetail[m]>
but given bt isn’t yet supported…
<bluetail[m]>
I know. But would it be technically possible?
MajorBiscuit has quit [Ping timeout: 480 seconds]
<bluetail[m]>
scenario is pretty straightforward. Capturing MIDI
<psykose>
macos can't autopair once you turn on a device?
<psykose>
(without extras)
<bluetail[m]>
no
<bluetail[m]>
It isn’t possible
<psykose>
lol, both linux and windows and phones and .. support that
<bluetail[m]>
you have to have Ministudio open and click a connect button each time and once connected leave the device on always
<bluetail[m]>
its stupid
<bluetail[m]>
midi studio *
<j`ey>
my BT headphones re connect automatically
OwOwA has quit [Ping timeout: 480 seconds]
<bluetail[m]>
They do? Perhaps this only applies to non audio devices like MIDI KEYBOARDS
<firefox317>
tmlind, yeah that might be the case indeed. The only interface we can see is the dcp, so how it actually controls the backlight is a black box and also doesnt matter anyway
<bluetail[m]>
My Roland fp30 can’t connect to a device itself. Instead another device has to connect to it for comms
<bluetail[m]>
j`ey: A Thomann.de salesperson probably will tell me I would require to instead use the usb cable or get some weird usb device that allows to be programmed to auto connect the bit midi itself and transmits to the Mac.
<mps>
I guess backlight could be in some registers which control PWM in mvram
<bluetail[m]>
that isn’t an option cause the Mac is 6m away. I know I could also hide a raspberry nearby but it would mean more clutter
sheepgoose_ has quit [Ping timeout: 480 seconds]
kameks has joined #asahi
<tmlind>
firefox317: yeah sounds the lcd backlight brightness is hidden in the dcp firmware then
myon9821 has joined #asahi
myon98 has quit [Ping timeout: 480 seconds]
chadmed has quit [Ping timeout: 480 seconds]
chadmed has joined #asahi
PaterTemporalis has joined #asahi
shenki has joined #asahi
hizon has quit [Remote host closed the connection]
jn has quit [Read error: Connection reset by peer]
jn has joined #asahi
apg has joined #asahi
apg has quit [Quit: Leaving]
zopieux has quit [Ping timeout: 480 seconds]
yuyichao has quit [Ping timeout: 480 seconds]
zopieux has joined #asahi
<Glanzmann>
c
<matthewayers[m]>
chadmed: the readme for asahi-audio is priceless :)
kameks has quit [Ping timeout: 480 seconds]
yuyichao has joined #asahi
<Glanzmann>
kov: Just saw your comment about d-i. Have to test it. Will fix it. Btw. did the dm-crypt work for you?
<kov>
Glanzmann, yes! installed debian on a friend's Air with it this weekend, thank you!
<kov>
he was a bit too eager and selected 'use the entire disk' though, so a DFU restore had to be performed xD
<bluetail[m]>
matthewayers: I think so too. It’s a good thing to share.
<mps>
does anyone know how to disable boot on keypress or lid open on macos 12.1
<mps>
and remove chime on boot
<j`ey>
removing the boot chime is via system prefences > audio, 'play startup sound'
<j`ey>
something like that
<mps>
j`ey: ah, thanks. (I tried with nvram, heh)
<marcan>
Glanzmann: < kov> he was a bit too eager and selected 'use the entire disk' though, so a DFU restore had to be performed xD <- FYI, this is the kind of thing why I'm not going to add your installer to the list until we have an "user-contributed, unsupported" heading for them
<marcan>
I'm happy to add user-contributed images, but people need to understand they are not supported by the project nor do we vouch for them
<kov>
marcan, tbf I think Glanzmann's installer image is not d-i, it should be a lot safer, we used d-i because we wanted encryption and I believe that is not possible atm with the debian rootfs approach
<marcan>
ah, I thought it was his guide
<kov>
marcan, his guide has 3 pieces, the asahi installer one, which does simple partition creation + rootfs unpacking, a debian live one, which I use as my usb rescue boot whenever I break something, and a debian installer image for anyone who wants to do their own custom installation
<kov>
marcan, that said I understand having the user-contributed thing, especially after reading your post on being very careful with the user's system
<marcan>
:)
<Glanzmann>
kov: Uh abot the 'DFU restore' part ...
<Glanzmann>
marcan: As kov explained I have currently 4 different methods of installing Debian in the wiki. The preferred method is using your asahi installer and does more or less the same thing you do for alarm.
<marcan>
still, hope you see where I'm coming from here
<Glanzmann>
kov: If you feel comfortable about adding debian to the installer_data.json with whatever heading you like to that would be nice, but if not, I'll just provide a copy of your installer with the edited json as long as it helpful like it currently is.
<Glanzmann>
marcan: Of course, I got the point.
<Glanzmann>
s/kov/marcan/g
<Glanzmann>
marcan: At the moment i see from the logs that 3-7 people install Debian using the asahi installer.
<Glanzmann>
per day*
<leah2>
actually it's one person that fucks up their system a lot *duck*
<Glanzmann>
leah2: Nope, I see the different IPs. Some come per v4, some per v6 from different parts of the world.
<leah2>
:)
<opticron>
Glanzmann, ah, nice stats! that's higher than I'd expect at this stage
<mps>
Glanzmann: you spy on your users ;p
<opticron>
and 2 were me :D
eroux has quit [Remote host closed the connection]
<mps>
immychan[m]: I worked some years with GDPR people and learned that any unnecesary data collection is spying, be it intentional or not
<sven>
i don't necessarily agree, but depending on which lawyer you ask GDPR possibly already defines an IP address as personally identifiable data fwiw
<mps>
sven: yes
<marcan>
FWIW the Asahi CDN logs are properly anonymized for GDPR compliance
<mps>
personally I don't care, so Glanzmann you are free to spy on me :)
creechy has joined #asahi
<daniels>
marcan: and yeah, anything using xkbcommon (not the X server) can do overlays, but ideally for common things they’d be upstream in the common definitions, not in random downstream
<daniels>
marcan: what specifically did you have in mind?
<marcan>
there's no sane jp(mac) keyboard layout for one, everything upstream is broken in some way
<marcan>
either capslock is wrong, or it's kana, or it doesn't have a backslash key
<marcan>
depending on how you do it
<marcan>
(it's also extremely confusing how the layouts and the symbols for the applealu stuff interact)
<marcan>
oh and the eisuu/kana keys are wrong most of the time too
<daniels>
yeah, that should be fixed for sure
<daniels>
is applealu actually still completely compatible up to M1?
<marcan>
I'm not entirely sure what applealu is supposed to be :-)
<daniels>
presumably AlBook era?
<daniels>
istr they changed the layouts about then
<marcan>
but yeah, without backslash, it's obviously not usable
<marcan>
of course the keyboard *physically* has no backslash, but that's only because Apple is stupid
<marcan>
on macos you can toggle ¥ into typing \, and get the other one with option+, except the terminal always defaults to backslash, which is a mess
<daniels>
ah, that's interesting
<marcan>
here in the real world, either ¥ is always backslash (JIS style, jp(106) in xkb) or ¥ is ¥ and backslash is the unshifted underscore key (which is how it is labeled in OADG109A keyboards, jp(OADG109A) in xkb)
<marcan>
but neither of those layouts has a mac variant
<marcan>
jp(mac) is... kana mode
<daniels>
I was going to say - and this is absolutely not to deflect from how shit the XKB rules syntax is - that one of the biggest problems is that people look at keyboards and say 'this is obviously dumb as hell, the correct thing to do is $thing, no-one else could ever possibly want anything else'
<marcan>
which is ridiculous and almost nobody here uses for anything
<daniels>
then before you know it we have multiple layouts for Icelandic Dvorak
<daniels>
anyway, what you want to do is to ignore the part files, and just look at build/rules/evdev
<marcan>
well, considering xkb can't magically do the nonsense macOS does, the next best thing is make the special keys do the right thing and then let users pick between 106 and OADG109A modes, which is what they'll be used to from other machines anyway
<daniels>
I mean you _can_ make it do that
<marcan>
make it do a different thing in terminal apps?
<marcan>
:)
<daniels>
you cannot do that, no :P
<marcan>
you know this is all microsoft's fault, right?
<daniels>
I meant wrt Option acting as a secondary shift for defined keys
<marcan>
where even in unicode mode, to this day, \ renders as ¥ if you have a japanese locale
<daniels>
I have to admit I'm not well-versed in history or use of Japanese keyboards
<marcan>
so most japanese people don't *know* what a backslash is
<daniels>
dealing with European keyboard politics was enough to make me abandon input
<marcan>
and I get emails with currency denominated in backslash
<daniels>
haha
<marcan>
apple tries to do the right thing in the OS with font rendering, but the keyboard is still weird because of this
<daniels>
brilliant
<daniels>
so, looking at build/rules/evdev, you end up with keycodes/evdev + macintosh_vndr/macintosh(jisevdev) which just fixes kana and is harmless
<daniels>
then you end up with symbols/macintosh_vndr/jp(usmac), where usmac does everything correctly _but_ it also overrides AE13 -> [yen,bar], and you'd like it to be [backslash,bar] right?
<Glanzmann>
mps: I'll never spy on me, because I only have debian images in my server.
<Glanzmann>
s/on me/on you/g
<marcan>
daniels: the problem is replace key <AB11> { [ underscore ] };
<daniels>
marcan: oh?
<marcan>
that was originally key <AB11> { [ backslash, underscore] };
<marcan>
which is the OADG109A version
<marcan>
however, some people might prefer the AE13 -> backslash,bar version
<marcan>
which is what jp(106) does
<marcan>
(which is actually the default)
<marcan>
my normal PC keyboard is OADG109A, most are these days
<marcan>
so if you want what's printed on the keycaps on the vast majority of machines today, you want that
<marcan>
however, jp(106) is the default because microsoft
<marcan>
and then apple kind of went with JIS plus that option hack, but most Linux users probably would rather have either of the above two modes
<daniels>
mm, I was going to say 'but if you're using your normal PC keyboard then just use the evdev model, not the mac model'
<marcan>
especially considering the _ key having no shifted variant is completely silly
<daniels>
but I'm assuming you're going to counter here with 'I'm actually using both'
<daniels>
in which case, yeah, you have to pick one and eat the cognitive dissonance
<marcan>
I mean, I'm talking about people coming from the PC world
<marcan>
if you want to do what macos does then we need the option thing, but then that kind of clashes with the whole "macos doesn't do keybindings like linux does"
<daniels>
as someone who types US on a UK keyboard, I can sympathise with ignoring the keycaps
<marcan>
and if you want to fix *that* you need userspace daemons (which is how people actually do it)
<marcan>
but given we can't do that in xkb, I argue the reasonable thing to offer by default is "provide a layout that matches the keycaps without trying to do fancy third level shifts that don't fit into the standard linux modifier model, and stick backslash somewhere sane"
<marcan>
where the two options for "somewhere sane" are replacing ¥ or putting it where it would be on every other PC keyboard
<marcan>
daniels: there's also the Fn thing, any ideas about what to do with that?
<marcan>
the driver properly reports it in evdev, and also synthesizes Fn+top bar = Fxx keys, and Fn+arrow keys = paging/home/end keys in-kernel (although that can be disabled)
<marcan>
the latter is probably a decent idea given that having those keys missing kind of sucks, and most people wouldn't want to do anything else there
<marcan>
but that still leaves Fn+everything else unused
<marcan>
problem is evdev Fn is >255 so Xorg can't see it
<daniels>
once you've built and installed xkeyboard-config, you can use xkbcommon's tools to poke at it, e.g. /build-x86-64/compile-keymap --include ~/x/xkb/xkeyboard-config/foo/usr/local/share/X11/xkb --rules evdev --model applealu_jis --layout jp --option apple:jp_oadg109
<marcan>
pc106 should be AE13
<daniels>
(or some of the other ones to test)
<daniels>
ah yeah, good point
<daniels>
as for 'what about Fn?', there are two options
<daniels>
there are a few (laptop mainly) HID specials in the kernel which fake up the relevant keycodes for you by handling Fn, much like up/down
<marcan>
fwiw I had already done the ~same thing except as layout variants instead of options :-)
<daniels>
they get away with that because they're all multimedia keys, which have no interaction with modifiers etc
<marcan>
but it's in a git repo that is in a machine that's not booted right now
<daniels>
heh
<daniels>
usually for stuff like that you try to stick it as options rather than variants; you can only have a single variant active at a time, so most 'I want this thing, but with this one small tweak' go in as options
<marcan>
yeah, makes sense
<marcan>
the only remaining confusing thing is jp(mac) has, if nothing else, a terrible name
<marcan>
it should probably be called "Japanese (Macintosh, Kana)" or something
<daniels>
back to Fn - if you can fake up a fixed set of multimedia keys in the kernel, then great - if not then you're in to adding a new keytype, which definitely gets a little bit fun within XKB. but Wayland can handle it completely perfectly, it's only Xorg-native stuff that struggles
<daniels>
and, well, easy fix for that
<marcan>
because right now if you select it ンラナ トカチスカ カンセニミキ リニノイ カクニト
<marcan>
("you start typing like this", no, that is not legible in japanese either)
<marcan>
(I actually don't know and have never met any japanese computer users that use kana mode)
<daniels>
yeah, steering people towards better defaults, and giving them better prompts to work with, is definitely doable
<marcan>
so Fn, the HID codes the top row reports are indeed Fx, but the keycaps say they are actually media keys unshifted and F-keys with Fn, though on macOS you can swap them if you want
<marcan>
the hid-apple driver does the same, defaulting to mapping to media keys unshifted and Fx with Fn, but you can swap it via module arg, or disable the conversion entirely
<daniels>
my XPS randomly flips between whether media or Fx is the unshifted mode, which is always a pleasure
<marcan>
heh
<daniels>
anyway, I would file an issue/MR on xk-c with something that steers people by default to something as close to possible as what macOS does ootb, with a note about the backslash-happy variants, and then following that notes and opinions about the various modes
<marcan>
surde
<marcan>
*sure
<daniels>
'I have looked at a keyboard and I have ideas on a better way to do things' is usually not the best start in that repo; 'here's what the native OS does on that device and this gets us as close as practically possible to it, with an explanation of the tweaks' is A+++ merge on sight
<marcan>
I mean, I think I got close to option #2 in this conversation? :)
<daniels>
yep! exactly, just suggesting how to frame it
<daniels>
lmk if you need any more eyes on XKB stuff, or a shoulder to cry on
<marcan>
haha, sure :)
<marcan>
and then I need to hack up calamares to preconfigure the keyboard model properly on the macbooks... which is also going to require some extra devicetree shenanigans to forward the layout from the ADT... (as we just confirmed in #asahi-dev)
<kettenis>
I don't think any of the spi/hid/keyboard/touchpad stuff was submitted updtream yet, is it?
<marcan>
nope
<marcan>
well, the spi controller was
<marcan>
but not merged yet
<mps>
Glanzmann: no worries, I'm just kidding a little
<brentr123[m]>
anyone know if asahi alpha is ready?
<immychan[m]>
Depends what you mean by “ready”
<j`ey>
brentr123[m]: it isnt
<j`ey>
brentr123[m]: there will be an announcement
coderobe has quit [Remote host closed the connection]
brigarian[m] has joined #asahi
brigarian[m] has left #asahi [#asahi]
<marcan>
PSA: pushed a m1n1 bugfix that affects stage 1. I *could* work around it in stage 2, but this doesn't affect normal u-boot chainload cases yet. however, it will break SEP once we get there.
<marcan>
so if you were thinking of leaving your existing stage 1 lying around for months, might want to do one final update
<marcan>
installer has been updated (just m1n1, also sets the partition UUID in lowercase now)
<_jannau_>
would it make sense to pass the 1st stage m1n1 version to the 2nd stage?
the_lanetly_052 has joined #asahi
<marcan>
I thought of doing that at some point
<marcan>
but to be honest, it's probably not necessary
Major_Biscuit has quit []
Fabrcio[m] has joined #asahi
mavericks5 has joined #asahi
artemist has quit [Ping timeout: 480 seconds]
mavericks has quit [Ping timeout: 480 seconds]
mavericks5 is now known as mavericks
Sellerie1 has joined #asahi
Sellerie has quit [Ping timeout: 480 seconds]
Sellerie1 is now known as Sellerie
<j`ey>
mps: I didnt boot using uboot, but yes display worked
<mps>
j`ey: could you post me kernel config?
<j`ey>
mps: mine is too cut down to be useful, but all the same options should work
<mps>
I upgraded m1n1 and u-boot to latest
<j`ey>
only the sound drivers changed really
<mps>
j`ey: I think I have to find proper FB and DRM combo
<j`ey>
whatever previously worked should still
m6wiq has joined #asahi
coderobe has joined #asahi
<mps>
hm, lets try
Sellerie9 has joined #asahi
Sellerie has quit [Ping timeout: 480 seconds]
Sellerie9 is now known as Sellerie
<mps>
hm, no luck
<j`ey>
mps: so you get the u-boot screen, and then after it boots the kernel it goes blank?
<Glanzmann>
mps: Rebuilding now and let you know if it works for me.
<Glanzmann>
povik: In the old version the audio jack output control in alsamixer was doing something, but now I can change it to whatever I want and the output volume does not change: https://tg.st/u/screenshot-air-2022-03-15-19_50_05.png
<Glanzmann>
You probably already know that, just in case you don't.
<Glanzmann>
mps: Yes, that is the log of the kernel build among other things with that config.
the_lanetly_052 has quit [Ping timeout: 480 seconds]
sheepgoose_ has joined #asahi
<matthewayers[m]>
Does anyone know how I can connect to internet using a captive portal and wpa supplicant?
<opticron>
matthewayers[m], captive portals shouldn't matter to wpa_supplicant
<Glanzmann>
matthewayers[m]: You open a browser and browse to log.me.in or blog.fefe.de
<opticron>
that's all router-side stuff, so it just looks like a normal open or wpa[2] connection to supplicant
<opticron>
there were some different errors on the last kernel
<sven>
that’s just a new print in the nvme code
<sven>
that command always failed because apple’s not following the spec there and I never got around to add a quirk because there’s already a fallback
<opticron>
fair enough
<opticron>
I also see a few errors with the wifi, but those are the same as last kernel (and it still works just fine)
<opticron>
I can paste the exact text somewhere, but the summary is ...firmware: failed ot update device address ret -52, p2pdev: set p2p_disc error, ...add_iface: add iface p2p-dev-wlp1s0f type 10 fialed err=-52
<opticron>
man, my fingers really can't fing
<matthewayers[m]>
Looks like my 14” MBP cannot find the audio jack output device
<matthewayers[m]>
Any suggestions? I’m on Debian Bookworm
<Glanzmann>
matthewayers[m]: Can you paste your dmesg to tg.st/p ?
<opticron>
I haven't tried audio on mine, but I have the same laptop
<opticron>
I'm mostly interested the speakers, but I guess I should poke the jack
<Glanzmann>
matthewayers[m]: Install pavucontrol and alsamixer and umute everything that is mute.
<Glanzmann>
matthewayers[m]: I need to press F6 to selec the second sound card.
<opticron>
yeah, I don't see a second device in alsamixer
<Glanzmann>
opticron: Strange. Can you paste your dmesg to tg.st/p ?
<Glanzmann>
matthewayers[m]: Yours look very similiar to opticron. The sound card appears not to be detected. Maybe something with the device trees, maybe something else.
<povik>
because jack isn't supported on the 2021 macbooks (and speakers are behind that DT edit on your own risk)
<opticron>
yeah, I'll avoid destroying my speakers for the moment :D
<povik>
although i am surprised the card (although empty) isn't registered at all
<Glanzmann>
opticron: Just to verify, I thought you have the 2020 model?
<povik>
14" is 2021, t600x
<matthewayers[m]>
I have the 2021 14" Macbook Pro with M1 Max silicon
<Glanzmann>
Okay, I just saw it.
<opticron>
yeah, we both have the 2021 14"
<Glanzmann>
povik: Thank you for the explanation.
<povik>
np
<matthewayers[m]>
povik: Thank you for helping us not destroy our speakers :)
<povik>
matthewayers[m]: haha, you're welcome!
sheepgoose has joined #asahi
sheepgoose_ has quit [Ping timeout: 480 seconds]
gladiac has quit [Quit: k thx bye]
m6wiq1 has joined #asahi
m6wiq has quit [Ping timeout: 480 seconds]
___nick___ has quit [Ping timeout: 480 seconds]
<s1gtrap[m]>
uh, I guess I screwed up when installing because now I have a full ext4 part with no way of extending it: can't be done from asahi, doesn't seem to be any tools for this on macos so unless there's bootable live media available somewhere?