2022-08-17
03:25marcanthat 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
05:15marcanand 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:16marcan(I still don't know why you don't just use our config as a reference for these things...)
05:17marcanit'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:18Glanzmannmarcan: 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:25mpsdistros like to build as much as possible of modules/drivers with =m, but for development this 'likes' to break things
05:32Glanzmannmarcan: 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:33marcanwith 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:34jannaumacsmc_gpio was built-in too so there was no missing dependency (at least at the point I asked about)
05:40Glanzmannjannau: 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 ...
07:07bluetailhad 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:07Glanzmannbluetail: I tried it and it worked for me without sound, but I'm back on 5.19 until it will be released.
07:15mpslast 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:45isoriano has joined #asahi-alt
08:32Glanzmannmps: This config boots for me https://tg.st/u/config-6.0.0-rc1-asahi-00173-g8cdf3b77a511
08:38Glanzmannisoriano: 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:39isorianoNo worries .. not mission critical just for watching my James Bond movies :-) Will give it a try
08:42leif has joined #asahi-alt
08:44leifhcitool should have deprecated ages ago. Does Debian not have bluetoothctl? If so does 'bluetoothctl list' show the controller.
08:48leifOk 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:52leifnice! yeah, it's always better to try things at the lower level first. The higher-level stuff will eventually get sorted out.
09:03isorianoBtw .. 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:05leif has quit [Quit: Leaving]
09:15isorianook sound works properly .. if you leave the bluetoothctl shell .. seems the scanning was causing the distortions
09:39isorianoWow .. so happy .. was even playing a round RTCW and it is really playable at 25xx resolutions
10:50isoriano has quit [Quit: Leaving]
10:54isoriano has joined #asahi-alt
10:57kode54 has joined #asahi-alt
11:54mpsI 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'`
12:02_jannau_depends on when you installed. asahilinux has asahi-fwextract that regenerates the vendorfw firmware.tar from all_firmware.tar.gz
12:08mpsat least driver is initialized and daemon works, rest will be on some alpine dev/user to test
13:45gaudem[m] has joined #asahi-alt
15:25leif has joined #asahi-alt
15:28Votes78 has quit [Ping timeout: 480 seconds]
15:28leif has quit []
16:06Votes78 has joined #asahi-alt
16:32Votes78 has quit [Ping timeout: 480 seconds]
16:34Votes78 has joined #asahi-alt
17:58Votes78 has quit [Ping timeout: 480 seconds]
17:59Votes78 has joined #asahi-alt
18:21_Votes78 has joined #asahi-alt
18:23Votes78 has quit [Ping timeout: 480 seconds]
18:56jannau has quit [Remote host closed the connection]
18:56_jannau_ has quit [Quit: ZNC - http://znc.in]
19:08jannau has joined #asahi-alt
19:42isorianoBut hey one thing .. if I remember correctly on Asahi I could switch screen resolutions .. are these some presets that get shipped with Asahi?
19:46_jannau_ has joined #asahi-alt
20:03Votes78 has joined #asahi-alt
20:07_Votes78 has quit [Ping timeout: 480 seconds]
20:40isoriano has quit [Quit: Leaving]
21:00isoriano has joined #asahi-alt
21:06isoriano@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:32isoriano has quit [Quit: Leaving]