03:23 <marcan> jannau, j`ey: thanks, pushed asahi-5.19-5 with the fixes (building the package now)

03:25 <marcan> that said: building modules as y with producer depencdencies as m is wrong. It won't explode, but you will get kernel warnings if the module isn't loaded for some reason, saying the probe thread is stuck

03:25 <marcan> fine for reproducing this problem, not actually fine to ship like that

05:11 <Glanzmann> marcan: Is CONFIG_GPIO_MACSMC the producer and CONFIG_HID_DOCKCHANNEL the consumer?

05:14 <marcan> Glanzmann: yes

05:15 <Glanzmann> marcan: Is it fine to have both as '=y'?

05:15 <marcan> and you should be building in the whole macsmc thing anyway, because that's a dependency of the framebuffer stuff right now for gpio, and presumably you want your framebuffer to work without the initramfs

05:16 <marcan> (I still don't know why you don't just use our config as a reference for these things...)

05:17 <marcan> it's fine to have everything as =y if you feel like it... module policy is up to the distro, but unless you actually understand the dependencies involved, you'd do well to follow what Asahi does to start with

05:18 <Glanzmann> marcan: Okay, both are '=y'. I want to stick as close as the debian kernel config as possible, but I'll sync the asahi config options with asahi-config.

05:18 <Glanzmann> possible*

05:18 <marcan> that's what I mean, for the Asahi-related options

05:18 <Glanzmann> I'll sync them.

05:25 <mps> distros like to build as much as possible of modules/drivers with =m, but for development this 'likes' to break things

05:32 <Glanzmann> marcan: With the dockchannel I had CONFIG_HID_DOCKCHANNEL, CONFIG_APPLE_DOCKCHANNEL and CONFIG_GPIO_MACSMC as =y most of the time the dockchannel was to fast for gpio but on once boot it was fast enough with j'eys patch it always works. But I'll sync now all asahi options with the reference config.

05:33 <marcan> with the patch it will work, but it is still wrong because if the module doesn't load it will just get stuck in the probe function forever, and warn after one minute

05:33 <marcan> it makes no sense to build in something and not its dependencies

05:33 <marcan> mps: I know, and that is exactly what I do

05:33 <marcan> everything that is =y in the asahi config is =y for a good reason

05:34 <mps> right

05:34 <jannau> macsmc_gpio was built-in too so there was no missing dependency (at least at the point I asked about)

05:35 <jannau> the wrong -EPROBE_DEFER check was the only reason it was broken

05:38 <Glanzmann> marcan: To my understanding both the were built-in.

05:39 <Glanzmann> something and the dependencies.

05:40 <Glanzmann> jannau: Yes, it was always built in. I tend to have more '=y' than '=m', but I now synced my config with the asahi reference config and put more things to =m ...

05:40 <Glanzmann> https://pbot.rmdir.de/y4jCeUr2iKWtL2QYEaJX3Q

07:04 <bluetail> anybody on the 6.0 kernel yet?

07:07 <bluetail> had tried it on my amd system and it would get stuck at initramfs... secureboot is off. So I currently install the mainline aur hope it does the 'work' for me, otherwise, I dont even know if its working on AMD yet.

07:07 <Glanzmann> bluetail: I tried it and it worked for me without sound, but I'm back on 5.19 until it will be released.

07:08 <bluetail> I see.

07:09 <Glanzmann> bluetail: https://pbot.rmdir.de/EEp9U0tJgNHyJTj51bgHWg

07:15 <mps> last night I thought to build and test 6.0-rc1 but had to work on some other tasks, hope will have time this evening for it

07:49 <isoriano> Good morning.

07:54 <mps> Glanzmann: do you have config for 6.0-rc1 kernel which boots

08:32 <Glanzmann> mps: This config boots for me https://tg.st/u/config-6.0.0-rc1-asahi-00173-g8cdf3b77a511

08:32 <Glanzmann> But I'm no longer using it, just installed the old deb to get you the config.

08:35 <mps> Glanzmann: thank you

08:38 <Glanzmann> isoriano: Good morning. So I have not tried much regarding, bluetooth, but this works for me: apt install -y bluez; https://pbot.rmdir.de/97q2ReKmty_MIGNrz_enDA

08:39 <isoriano> No worries .. not mission critical just for watching my James Bond movies :-) Will give it a try

08:44 <leif> hcitool should have deprecated ages ago. Does Debian not have bluetoothctl? If so does 'bluetoothctl list' show the controller.

08:45 <Glanzmann> leif: Does work for me, as well.

08:45 <isoriano> it does .. Controller 9C:3E:53:87:85:78 m2mbp-debian [default]

08:45 <Glanzmann> https://pbot.rmdir.de/KCByWrUNEawmp_g-6-tVcg

08:46 <isoriano> But connecting is the problem.

08:48 <leif> Ok if you type 'bluetoothctl' to go into the bluetoothctl shell, then just type 'scan on' -- hopefully you should now see your device show up here (make sure it's in pairing mode), then just 'connect mac-address'

08:49 <isoriano> https://ibb.co/jTV5S8N

08:51 <isoriano> leif, Great .. it works from the shell and connecting as you mention it!

08:52 <Glanzmann> Cool.

08:52 <leif> nice! yeah, it's always better to try things at the lower level first. The higher-level stuff will eventually get sorted out.

08:58 <isoriano> Thx .. ok, transmission seems distored in between but at least some sounds.

08:59 <j`ey> isoriano: 2.4 or 5ghz wifi?

09:00 <isoriano> 5 GHz .. BandModifier5Ghz=10

09:01 <isoriano> in /etc/iwd/main.conf

09:01 <isoriano> [Rank]

09:03 <isoriano> Btw .. just in case you are interested in Debian aarch64 use cases :-) I do not give it up .. so running illumos-aarch64 in qemu-aarch64 on debian-aarch64 :-) https://ibb.co/vkGZ1P3

09:15 <isoriano> ok sound works properly .. if you leave the bluetoothctl shell .. seems the scanning was causing the distortions

09:15 <isoriano> exit

09:15 <isoriano> exit the shell

09:24 <Glanzmann> I see. Good to know.

09:39 <isoriano> Wow .. so happy .. was even playing a round RTCW and it is really playable at 25xx resolutions

11:54 <mps> I just wanted to look at BT and see this in dmesg out `2.344168] hci_bcm4377 0000:01:00.1: Unable to load firmware; tried 'brcm/brcmbt4387c2-apple,madagascar-u.bin' and 'brcm/brcmbt4387c2-apple,madagascar.bin'`

11:55 <mps> so I need to unpack new firmware

11:55 <mps> it is /boot/efi/asahi/all_firmware.tar.gz I guess

11:56 <mps> but I'm not sure that simple tar will work

11:57 <mps> oh, looks like untar /boot/efi/vendorfw/firmware.tar will be enough

12:01 <Glanzmann> Yep, if you stub is new enought, than this is enough.

12:01 <Glanzmann> your*

12:02 <_jannau_> depends on when you installed. asahilinux has asahi-fwextract that regenerates the vendorfw firmware.tar from all_firmware.tar.gz

12:03 <_jannau_> it's a packaged version the installer's firmware code

12:04 <mps> _jannau_: yes, I know, and for alpine I used this alarm script and changed it a bit

12:05 <mps> but my experience with BT is nearly zero, didn't used for more than a decade or two

12:06 <mps> installed alpine bluez pkg, run /etc/init.d/bluetooth, run bluetoothctl, and stopped there

12:08 <mps> at least driver is initialized and daemon works, rest will be on some alpine dev/user to test

12:10 <_jannau_> depending on where you are you could scan in bluetoothctl and see if there any devices

12:20 <mps> command 'show' or 'scan on' shows 'No default controller available'

12:21 <mps> so probably need config file for daemon

12:36 <_jannau_> you might have to `power on` the controller

12:54 <mps> _jannau_: same result

12:55 <mps> I need to ask someone running alpine how to set it

15:32 <bluetail> isnt it funny that kernel 6 is called 'Hurr durr I'ma ninja sloth' ?

19:40 <isoriano> Good evening, so nothing to test tonight? :-)

19:42 <isoriano> But hey one thing .. if I remember correctly on Asahi I could switch screen resolutions .. are these some presets that get shipped with Asahi?

20:02 <mps> isoriano: I think only with m1n1

20:02 <mps> i.e. on boot and not on macbooks, but minis

21:06 <isoriano> @Glanzmann, sorry forgot to ask .. as I wanted to give my qemu-aarch64 a run and as part I setup the NIC and get the following error with the kernel you send me yesterday

21:06 <isoriano> iptables: Failed to initialize nft: Protocol not supported

21:06 <isoriano> disabled in the kernel?