#
…

2022-08-18

06:46Glanzmannisoriano: Do you have a one liner to reproduce the issue, what does 'iptables -L -n' say?
06:59Glanzmannisoriano: All ipv4/ipv6 netfilter options are enabeld as built-in or module.
07:52_Votes78 has joined #asahi-alt
07:55Votes78 has quit [Ping timeout: 480 seconds]
07:58isoriano has joined #asahi-alt
08:03isorianoGood morning. @Glanzmann output is: iptables: Failed to initialize nft: Protocol not supported
08:08isoriano has quit [Quit: Leaving]
08:11isoriano has joined #asahi-alt
08:21isoriano has quit [Quit: Leaving]
08:24Votes78 has joined #asahi-alt
08:29_Votes78 has quit [Ping timeout: 480 seconds]
08:33isoriano has joined #asahi-alt
09:37isorianoAnd while testing ... i thought I give my oldskool demo a run on this nice architecture .. hoep you like some oldskool demos.
09:45mpsGlanzmann: on which machine you tested kernel 6.0-rc1? mb air?
10:49Glanzmannmps: mb air m1.
10:52Glanzmannisoriano: Can you send me the qemu command that you're trying to run?
10:53Glanzmannisoriano: For me iptables -L -n and iptables -L -n -t nat work without an error message.
10:53mpsGlanzmann: ah, I'm trying on m1pro
10:54mpswill take m1 mbp and try on it
10:59j`eyisoriano: hey cool demo! 43FPS without GPU support! :P
11:00chadmed has joined #asahi-alt
11:10mpsGlanzmann: yes, 6.0-rc1 boot fine on m1 mbp, but not on m1pro macbook
11:12Glanzmannmps: I see.
11:12GlanzmannI only booted in on m1 air.
11:19mpsok. now we know that it also boot on m1 mbp
11:31Sobek[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:32GlanzmannSobek[m]: In upstream are a lot of patches missing, unless you maz and you run mac mini headless.
11:33mpsSobek[m]: have no idea. last text I see on screen is grub telling loading vmlinuz and nothing after that
11:33GlanzmannSobek[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:34Glanzmannmps: My bets are on device tree, but might also be that the console does not initialize. Does the system ping afterwards?
11:37mpsno, nothing works, even caps lock key don't activate led when pressed
11:39Glanzmannmps: Than just wait a bit once m a r c a n has recovered from yesterdays gpu session.
11:39mpsthough lets try
11:40_jannau_I would recommend running it under the HV. doesn't appear to work is not that informative
11:43mps_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:45mpsthat is what I'm doing for now
12:06leif has joined #asahi-alt
12:06leifGlanzman: marca n never rebased 60-rc1. Where are you seeing that?
12:07leif*6.0-rc1
12:08isorianothx @j`ey
12:10leif has quit []
12:15Glanzmannleig: Look a the current 'asahi' branch in above repository.
12:16GlanzmannWhen 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:16Sobek[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:26leif has joined #asahi-alt
12:26leif has quit [Remote host closed the connection]
12:28leif has joined #asahi-alt
12:31leifGlanzmann: 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:32leif has quit []
12:32Glanzmannleif: 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
14:42_Votes78 has joined #asahi-alt
14:46Votes78 has quit [Ping timeout: 480 seconds]
14:49Votes78 has joined #asahi-alt
14:52_Votes78 has quit [Ping timeout: 480 seconds]
15:06_Votes78 has joined #asahi-alt
15:09Votes78 has quit [Ping timeout: 480 seconds]
15:24Votes78 has joined #asahi-alt
15:28_Votes78 has quit [Ping timeout: 480 seconds]
15:33_Votes78 has joined #asahi-alt
15:38Votes78 has quit [Ping timeout: 480 seconds]
15:42Votes78 has joined #asahi-alt
15:47_Votes78 has quit [Ping timeout: 480 seconds]
15:59_Votes78 has joined #asahi-alt
16:00Votes78 has quit [Ping timeout: 480 seconds]
16:26Votes78 has joined #asahi-alt
16:28_Votes78 has quit [Ping timeout: 480 seconds]
16:40_Votes78 has joined #asahi-alt
16:44Votes78 has quit [Ping timeout: 480 seconds]
17:00Votes78 has joined #asahi-alt
17:05_Votes78 has quit [Ping timeout: 480 seconds]
18:56bluetailIs 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:56bluetailfound with different hardware configs for me.
18:57bluetailThis isnt about asahi ^
18:59bluetailOh, and both were using i3 with a minimal config
19:22Votes78 has quit [Ping timeout: 480 seconds]
19:26Votes78 has joined #asahi-alt
19:45_Votes78 has joined #asahi-alt
19:48Votes78 has quit [Ping timeout: 480 seconds]
19:54Votes78 has joined #asahi-alt
19:58_Votes78 has quit [Ping timeout: 480 seconds]
20:57Votes78 has quit [autokilled: This host violated network policy and has been banned. Mail support@oftc.net if you think this is in error. (2022-08-18 20:57:18)]
20:58Votes78 has joined #asahi-alt
20:58Votes78 has quit [autokilled: This host violated network policy and has been banned. Mail support@oftc.net if you think this is in error. (2022-08-18 20:58:35)]
21:28isoriano has quit [Remote host closed the connection]
23:20bluetail has quit [Quit: Ping timeout (120 seconds)]
23:20bluetail has joined #asahi-alt
…