<amw>
Do you know if any debian developer is interested in putting that together? or where to discuss it?
<steev>
probably best discussed in #asahi-alt and i thought glanzman(sp?) script already builds a deb
<steev>
but if you wanted to do it yourself, you'd do something like https://steev.net/posts/2021/09/misc-bits/ (after you put the 200+ patches into the debian/patches/whatever folders, and added all 200+ to the series file so they apply in the correct order)
<steev>
if you have the list of the 200+ patches somewhere, i'd take a look at them, at a minimum
nuh^ has quit [Ping timeout: 480 seconds]
<amw>
steev: I was just chatting with glanzman on #asahi-alt and he said to try #asahi and perhaps wookey
<amw>
I currently do use glanzman's script and it mostly works well - had a trouble last time but think it was a failed patched that blocked 4K patch being applied
<Tramtrist>
Something I've wondered is if Apple devs are lurking here or elsewhere reading marcan info or following the progress which is why they made the changes which assist asahi in its efforts
<Tramtrist>
(hey Apple folks!)
<nicolas17>
Tramtrist: I have seen at least 1 Apple dev in the stream chat
<Tramtrist>
ah thats a good sign
<steev>
i'd poke my buddy at Apple and ask, but once he went there... he disappeared forever
<nicolas17>
steev: lol that's quite common
<Tramtrist>
hah ya
Bai-Chiang has quit [Ping timeout: 480 seconds]
<Tramtrist>
Seems those changes would not have happened by chance
<amw>
I was wondering if there were any plans / thoughts that might see the debian installer support it for bookworm as my M1 works for lots of usages e.g. kernel development
<steev>
amw: sounds like you're volunteering to make it happen :D
<amw>
I'm happy to help - but I'm not even a debian developer!
<steev>
you don't need to be to work on it
<Tramtrist>
And.... to be more conspiratorial about it.. what was the process like internally within Apple to move changes that would only benefit 3rd party.. There had to be some kind of cojoling or conversation there
<steev>
they accept merge requests
<amw>
Yeah but I think it's pretty important to have a relevant person to talk with / submit to
<steev>
well there are tons of #debian- channels on the network
<amw>
Ok - thanks I'll start querying around on the relevant sounding ones and see what turns up.
<steev>
you'd submit the merge request, and then make changes and whatnot based on the code review
Brainium has joined #asahi
<steev>
it's open source, you don't have to have anyone's permission to work on it
PhilippvK has joined #asahi
phiologe has quit [Ping timeout: 480 seconds]
Brainium has quit [Quit: Konversation terminated!]
marvin24_ has joined #asahi
marvin24 has quit [Ping timeout: 480 seconds]
pyropeter1 has joined #asahi
Stroller has quit [Quit: Stroller]
nuh^ has joined #asahi
PyroPeter_ has quit [Ping timeout: 480 seconds]
doggkruse has joined #asahi
Erus_Iluvatar has quit [Ping timeout: 480 seconds]
rvalue has quit [Remote host closed the connection]
rvalue has joined #asahi
<dottedmag>
telegra
<dottedmag>
sorry, wrong window
doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<marcan>
Tramtrist: we've had apple folks chatting in this channel before
<marcan>
some of the changes that help us also help advanced macOS use cases, like the command line tooling to set the boot volume stuff
<marcan>
the raw image stuff though, I'm somewhat convinced the engineer in charge of re-working how kmutil/iBoot works with machos (which prompted all that) snuck it in for us, perhaps with some vaguely plausible excuse
<marcan>
it's not exactly controversial so I could see it just slipping by without a whole pile of management approval
<marcan>
not even sure if it's in the manpage yet?
<marcan>
yeah, it isn't :-)
<marcan>
so that one *is* undocumented (not that we hard-depend on it, I could work out the missing macho metadata to make the old documented way work again if it goes away)
<marcan>
ah, but --help does show it
<marcan>
so I guess that counts as documented
<marcan>
(vs. e.g. some of the advanced csrutil modes which are completely undocumented/secret)
bisko has joined #asahi
<nicolas17>
there's some macos daemons that have a manpage but it's just the template :P
<nicolas17>
I don't have a mac handy atm, but according to a manpage db online... "man cloudpaird", "man tbtool" are just unmodified templates
qeeg_ has quit [Remote host closed the connection]
eroux has quit [Remote host closed the connection]
<mps>
marcan: nice
<mps>
though now I use upstream stable u-boot release
eroux has joined #asahi
<marcan>
if you don't use our release branch, you don't have the magic ESP handling, so unless you patch that in yourself, your builds are not multi-install compatible.
<marcan>
(if you're doing a distro, please, please test multiple installs)
<mps>
you mean '/proc/device-tree/chosen/asahi,efi-system-partition'
<marcan>
yes
<marcan>
I mean *using* that
<marcan>
in u-boot
<mps>
I have it
<marcan>
yes
<marcan>
but does your u-boot use it to find the efi binary?
<mps>
I mean I have it with upstream u-boot
<marcan>
yes
<marcan>
but it's not *using* it
<mps>
aha
<marcan>
if you don't have that patch, and you do 2 installs, both u-boots will try to boot the 1st install
<mps>
hmm, this maybe explains ktz_[m] problem few days ago
<marcan>
jannau, kettenis: was there a good reason why we're not upstreaming that yet?
<mps>
marcan: thanks again, tomorrow with new m1pro I will do it 'right way'
<_jannau_>
planned/ongoing work to change how distro-boot is implemented in u-boot. I want to look into implementing it using efibootmgr
<mps>
_jannau_: does efibootmgr require some persistent storage for variables?
<_jannau_>
not for the case we want to support: boot "/EFI/BOOTAA64.EFI" from the matched ESP. the plan would be to build the variables for that on the fly
<mps>
not sure how that will work but I trust you that you know solution
<VinDuv>
could efibootmgr edit the u-boot variables files on the ESP?
<_jannau_>
I don't know yet if it will work
<_jannau_>
not sure if we want to or can support u-boot variable files on the esp. Our single use case is to boot "/EFI/BOOTAA64.EFI" from the matched ESP. anything else is not supported
eeqk[m] has joined #asahi
qeeg_ has joined #asahi
qeeg has quit [Read error: Connection reset by peer]
patricedelafon[m] is now known as lamreguez[m]
<whynothugo>
My bluetooth headphones connect and immediately disconnect. Any ideas what could be wrong? I have all the same pipewire packages I use on amd64.
<ar>
whynothugo: "journalctl --full --follow --unit=bluetooth.service" says anything interesting when you try to connect?
<ar>
whynothugo: or "journalctl --full --follow --user --unit=pipewire.service"?
<whynothugo>
bluetoothd[712]: src/device.c:load_gatt_db() No cache for C8:7B:23:XX:XX:XX
<whynothugo>
bluetoothd[712]: profiles/deviceinfo/deviceinfo.c:read_pnpid_cb() Error reading PNP_ID: Invalid pdu length received
<sven>
is pulseaudio installed and running?
<ar>
sven: but why PA, when there's PW?
<sven>
dunno, it’s the thing I used
<ar>
whynothugo: have you tried re-pairing?
<sven>
otherwise please run btmon and paste that somewhere
<CatDentures>
hi, long time follower of the project, first time posting. I decided to take the plung on my M1 iMac and like it so far. just got my magic keyboard and trackpad paired :D
<qyliss_>
congratulations :)
<CatDentures>
thanks!
<CatDentures>
I saw on the Feature Support that keyboard and trackpad for M1 iMac had n/a so was nervous, but with some work at the terminal I got them both working fine
<j`ey>
that means the laptop kb/trackpad, hence n/a!
MajorBiscuit has joined #asahi
<CatDentures>
oh, so it's not referencing the kb/trackpad for the iMac in the iMac column?
<j`ey>
they're just bluetooth right?
<CatDentures>
yes
<CatDentures>
oh, duh, gotcha, bluetooth is it's own entry, kb/trackpad that are bluetooth fall under that. I misread the table
<whynothugo>
sven: Pipewire is installed and running
<whynothugo>
ar: I just tried connecting, not pairing.
<ar>
whynothugo: was the device paired on this linux install before?
Erus_Iluvatar has joined #asahi
nuh^ has quit [Remote host closed the connection]
<whynothugo>
It was never pair, lemme try pairing ar
<ar>
sven: bluetooth on asahi doesn't share the pairing keys with macos, no?
<sven>
that would be surprising
<whynothugo>
Pairing fails immediately: gi.repository.GLib.GError: g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.UnknownObject: Method "Pair" with signature "" on interface "org.bluez.Device1" doesn't exist
<whynothugo>
I do not believe keys can be shared, they should be unreadable by Linux. Also, never paired on Mac.
<whynothugo>
Yeah, I think if I had paired the device with macOS before that would be problematic -- I have not.
<whynothugo>
Ocasionally some mag stutter when playing music. Need to figure out if this is Firefox or what the issue is.
<_jannau_>
whynothugo: are you connected to a 2.4GHz wlan?
<whynothugo>
2412Mhz, yes.
<whynothugo>
Need to figure out how to change that.
<sven>
that’s the issue.
<sven>
Bluetooth/WiFi coexistence doesn’t work yet
<sven>
as a workaround you can switch to 5 GHz for now
<whynothugo>
Oh, right, hardware-assisted coexistence support is a thing. I'd forgotten.
<whynothugo>
Yeah, I'll have to figure out how to tell iwctl to prefer 5Ghz.
<sven>
yeah, and it appears to be some apple-specific thing according to marcan
<sven>
luckily it’s in the WiFi driver and thus not my problem 😌
qeeg_ has quit [Remote host closed the connection]
<marcan>
dottedmag: correct
<dottedmag>
thnx
<marcan>
sven: (we think)
<marcan>
;)
qeeg_ has joined #asahi
<marcan>
but yeah probably
<sven>
ive actually looked at Bluetooth trace while connected to a 2.4 GHz network again and didn’t see anything in there
everfree has quit [Quit: leaving]
everfree has joined #asahi
the_lanetly_052 has joined #asahi
nehsou^ has joined #asahi
dviola has joined #asahi
LinuxM1 has joined #asahi
guillaume_g has quit [Ping timeout: 480 seconds]
<ChaosPrincess>
does anyone know of a way to pass username/password to kmutil w/o having to type it in?
guillaume_g has joined #asahi
mosica has joined #asahi
<VinDuv>
You can pass the "y" and the username on stdin, but not the password
mosica has left #asahi [Leaving]
<mabiola>
exit
mabiola has quit [Quit: leaving]
<dottedmag>
Does it read password from tty? Then maybe expect(1) if it is present?
MajorBiscuit has quit [Quit: WeeChat 3.5]
qeeg_ has quit [Remote host closed the connection]
qeeg_ has joined #asahi
LinuxM1 has quit [Quit: Leaving]
qeeg_ has quit [Remote host closed the connection]
qeeg_ has joined #asahi
TiangangYang[m] has joined #asahi
dingodoppelt_ has quit [Quit: ZNC 1.9.x-git-170-9be0cae1 - https://znc.in]
dingodoppelt has joined #asahi
hendry has joined #asahi
qeeg__ has joined #asahi
qeeg_ has quit [Remote host closed the connection]
Bai-Chiang has joined #asahi
CatDentures has quit [Quit: leaving]
MajorBiscuit has joined #asahi
VinDuv_ has joined #asahi
VinDuv has quit [Ping timeout: 480 seconds]
VinDuv_ is now known as VinDuv
Moprius has joined #asahi
rann_ has quit []
rann has joined #asahi
<amarioguy>
maz: i did some very very very initial testing, and i *think* (not 100% sure on this but it's pretty likely) that m2/t8112 actually supports the maintenance IRQs
<amarioguy>
(specifically i found while doing stuff with m1n1 that ICH_MISR_EL2 is implemented, seems to be configurable and the register changes pretty much exactly as the spec says it should change)
<amarioguy>
(furthermore having maintenance interrupts pending and enabling virtual interrupts results in an interrupt storm as there's no handling for maintenance irqs in m1n1)
<amarioguy>
now i'm not 100% sure if this is enough to imply that the hack used for m1/m1 pro is no longer necessary (or even if i tested for the right thing) but honestly the interrupt storm after setting ICH_MISR_EL2 didn't seem like something that should happen unless maintenance irqs are supported outright
guillaume has joined #asahi
guillaume_g has quit [Ping timeout: 480 seconds]
Moprius has quit [Quit: bye]
Guest6943 has quit []
DragoonAethis has joined #asahi
mosica has joined #asahi
mini0n has joined #asahi
nicolas17 has joined #asahi
qeeg__ has quit [Remote host closed the connection]
qeeg__ has joined #asahi
babble has joined #asahi
farghal has joined #asahi
Stroller has joined #asahi
babble has quit [Remote host closed the connection]
babble has joined #asahi
return_db[m] has joined #asahi
mosica has left #asahi [Leaving]
Bai-Chiang has quit [Quit: Konversation terminated!]
farghal has quit [Ping timeout: 480 seconds]
Bai-Chiang has joined #asahi
return_db[m] is now known as skliio091L[m]
zotanmew has quit [Ping timeout: 480 seconds]
duban has quit [Ping timeout: 480 seconds]
zotanmew has joined #asahi
babble has quit [Read error: Connection reset by peer]
nehsou^ has quit [Ping timeout: 480 seconds]
duban has joined #asahi
doggkruse has joined #asahi
babble has joined #asahi
babble_ has joined #asahi
babble has quit [Read error: Connection reset by peer]
PrasanthOmanakuttan[m] has joined #asahi
guillaume has quit []
rvalue has quit [Remote host closed the connection]
rvalue has joined #asahi
farghal has joined #asahi
doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
doggkruse has joined #asahi
babble_ has quit []
farghal has quit [Quit: farghal]
MajorBiscuit has quit [Ping timeout: 480 seconds]
doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
babble has joined #asahi
doggkruse has joined #asahi
babble has quit [Quit: byeeeee]
babble has joined #asahi
zz812 has quit []
z812 has joined #asahi
qeeg__ has quit [Remote host closed the connection]
qeeg__ has joined #asahi
the_lanetly_052 has quit [Ping timeout: 480 seconds]