06:46 <Glanzmann> isoriano: Do you have a one liner to reproduce the issue, what does 'iptables -L -n' say?

06:59 <Glanzmann> isoriano: All ipv4/ipv6 netfilter options are enabeld as built-in or module.

08:03 <isoriano> Good morning. @Glanzmann output is: iptables: Failed to initialize nft: Protocol not supported

09:37 <isoriano> And while testing ... i thought I give my oldskool demo a run on this nice architecture .. hoep you like some oldskool demos.

09:37 <isoriano> https://www.youtube.com/watch?v=U9n3Hisz8Q0

09:45 <mps> Glanzmann: on which machine you tested kernel 6.0-rc1? mb air?

10:49 <Glanzmann> mps: mb air m1.

10:52 <Glanzmann> isoriano: Can you send me the qemu command that you're trying to run?

10:53 <Glanzmann> isoriano: For me iptables -L -n and iptables -L -n -t nat work without an error message.

10:53 <mps> Glanzmann: ah, I'm trying on m1pro

10:54 <mps> will take m1 mbp and try on it

10:59 <j`ey> isoriano: hey cool demo! 43FPS without GPU support! :P

11:10 <mps> Glanzmann: yes, 6.0-rc1 boot fine on m1 mbp, but not on m1pro macbook

11:12 <Glanzmann> mps: I see.

11:12 <Glanzmann> I only booted in on m1 air.

11:19 <mps> ok. now we know that it also boot on m1 mbp

11:31 <Sobek[m]> <mps> "Glanzmann: yes, 6.0-rc1 boot..." <- What happens on m1pro / why does it fail to boot ? Still missing some patches in upstream ?

11:32 <Glanzmann> Sobek[m]: In upstream are a lot of patches missing, unless you maz and you run mac mini headless.

11:33 <mps> Sobek[m]: have no idea. last text I see on screen is grub telling loading vmlinuz and nothing after that

11:33 <Glanzmann> Sobek[m]: But we were talking about 6.0-rc1 asahi branch that m a r c a n recently rebased. So that is asahi rebased on top of 6.0-rc1.

11:34 <Glanzmann> mps: My bets are on device tree, but might also be that the console does not initialize. Does the system ping afterwards?

11:37 <mps> no, nothing works, even caps lock key don't activate led when pressed

11:38 <Glanzmann> I see.

11:39 <Glanzmann> mps: Than just wait a bit once m a r c a n has recovered from yesterdays gpu session.

11:39 <mps> though lets try

11:40 <_jannau_> I would recommend running it under the HV. doesn't appear to work is not that informative

11:43 <mps> _jannau_: I agree, but now don't have option to run with HV, maybe on weekend

11:44 <_jannau_> I would just stop trying then and wait

11:45 <mps> that is what I'm doing for now

12:06 <isoriano> @Glanzmann, https://pbot.rmdir.de/C4zkt-2bLBEvs9x5YloczA network setup

12:06 <leif> Glanzman: marca n never rebased 60-rc1. Where are you seeing that?

12:07 <leif> *6.0-rc1

12:07 <isoriano> https://pbot.rmdir.de/oaWJOMEc6rVcqu2U07UdPg qemu start

12:08 <isoriano> thx @j`ey

12:09 <leif> https://github.com/AsahiLinux/linux/releases/tag/v6.0-rc1 is a Linus Torvalds tagged release

12:15 <Glanzmann> leig: Look a the current 'asahi' branch in above repository.

12:15 <Glanzmann> leif*

12:16 <Glanzmann> When you follow the commits you can see that the asahi stuff is rebased on top of Linux 6.0 rc1 (git log -p asahi) and than search for 6.0-rc1.

12:16 <Sobek[m]> <Glanzmann> "mps: Than just wait a bit once m..." <- Li.na is the one doing these, pretty sure m a r c a n is not involved :)

12:31 <leif> Glanzmann: cool, I see that. But if there's no asahi tagged version here: https://github.com/AsahiLinux/linux/tags and the kernel package doesn't show up here: https://de.mirror.asahilinux.org/aarch64/asahi-dev/ then it's probably a bit early. Just my 2 cents...please let me know if you get that working though.

12:32 <Glanzmann> leif: I got it working on m1 air with my config, but I'm not using it until it is released.

12:34 <_jannau_> yes, it is too early for build distro packages. there will changes for audio since the upstreamed audio code conflicts with what was in asahi before

18:56 <bluetail> Is there something fundamentally different with scheduling / if you compare debian vs arch? One specific game made in Java seems to be unplayable on arch but playable on debian, using the same kernel and video driver. Both systems are fully updated. I don't plan to find the cause deeper cause comparing two OS is a pain and the same behavior can be

18:56 <bluetail> found with different hardware configs for me.

18:57 <bluetail> This isnt about asahi ^

18:59 <bluetail> Oh, and both were using i3 with a minimal config