#
…

2022-02-13

00:12mtjzh has quit [Ping timeout: 480 seconds]
00:18user982492 has joined #asahi
00:21eroux has joined #asahi
00:29eroux has quit [Ping timeout: 480 seconds]
00:37mtjzh has joined #asahi
00:53chadmed has quit [Quit: Konversation terminated!]
00:56chadmed has joined #asahi
01:04ElvishJerricco[m] has joined #asahi
01:41eroux has joined #asahi
01:49eroux has quit [Ping timeout: 480 seconds]
02:54eroux has joined #asahi
03:02user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
03:02eroux has quit [Ping timeout: 480 seconds]
03:32coolshaurya#flameshot-org:matrix.org
03:33PhilippvK has joined #asahi
03:37phiologe has quit [Ping timeout: 480 seconds]
03:46kov has quit [Quit: Coyote finally caught me]
03:46kov has joined #asahi
04:10eroux has joined #asahi
04:18eroux has quit [Ping timeout: 480 seconds]
04:25user982492 has joined #asahi
04:48eroux has joined #asahi
04:56maman has joined #asahi
04:56marvin24 has joined #asahi
04:57maman has quit []
05:00marvin24_ has quit [Ping timeout: 480 seconds]
05:11Glanzmannkov: I also recall that once bullseye had a working trackpad. But it might be that with the new spi code, it requires a newer libinput. But good that it works for you.
05:43the_lanetly_052 has joined #asahi
05:54eroux has quit [Ping timeout: 480 seconds]
06:39eroux has joined #asahi
06:58eroux has quit [Ping timeout: 480 seconds]
06:58AstaraOS has joined #asahi
07:01* AstaraOShi all skraito here how are ya all ?
07:02* AstaraOSwhat you guys up to ?
07:04* AstaraOShey mind to do some coding advise at channel #0dev , let me know if anyone interested , lets code together
07:15i509VCBmight be a bot? saw the same message on #_oftc_#wayland:matrix.org
07:19eroux has joined #asahi
07:25AstaraOS<AstaraOS> yeah actually i am trying to break tor
07:25AstaraOS<arma> ah ha, i see that you have spammed every channel. definitely the wrong place.
07:25AstaraOS<AstaraOS> anyway if i know all node
07:25AstaraOS<AstaraOS> whwat is it that this tor is super bitcha anyway ?
07:25AstaraOS<AstaraOS> i just need to block all node
07:25AstaraOS<AstaraOS> if you go with server less
07:25AstaraOS<AstaraOS> people can block too
07:25AstaraOS<AstaraOS> client -- > server ?
07:25AstaraOS<AstaraOS> that's why in my opinion tor is stupid
07:25AstaraOS<AstaraOS> i don't even need the node
07:25AstaraOS<AstaraOS> just first node
07:25AstaraOS<AstaraOS> and last node
07:25AstaraOS<AstaraOS> if you encrypt it between middle
07:25AstaraOS<AstaraOS> i would rather
07:25AstaraOS<AstaraOS> use proxy
07:25AstaraOS<arma> ok. off you go then. please do not clutter up #tor.
07:25AstaraOS<AstaraOS> proxy1 -> proxy2 -< proxy3 -> proxy4 -> vpn --> target
07:25AstaraOS<AstaraOS> all traffic encrypted
07:26AstaraOS<AstaraOS> well i am skraito anyway
07:26AstaraOS<AstaraOS> that's why they call tor is stupid
07:26AstaraOS<AstaraOS> We are already breaking
07:27qeeg has quit [Read error: Connection reset by peer]
07:27* AstaraOSlet's go code at channel #0dev if you guys want ... .
07:28eroux has quit [Ping timeout: 480 seconds]
07:28* AstaraOSi am bot ? i am skraito the earthquake guy ... .just Repent https://tjc.org , before it's too late
07:32* AstaraOSif you want support from AstaraOS i am here or on another network #0dev or https://worldhacker.org
07:33* AstaraOShow to boot kernel from old to new one with out installation ?
07:34* AstaraOS[ Astara ] Team 0day request ... . https://worldhacker.org ... . https://worldhacker.org/index.php/irc-server/ ... . let's go code together :) and make some buck , i will wait ... .
07:35* AstaraOShandling case
07:37AstaraOS was banned on #asahi by marcan [*!*@180.241.255.245]
07:37AstaraOS was kicked from #asahi by marcan [AstaraOS]
07:39eroux has joined #asahi
07:46Tramtristthat was lovely
08:01Glanzmannj`ey: Do you remeber the guy who wrote the 64kb patch for chromium?
08:02GlanzmannI'm asking because I want to file a bug report with Debian and include as much information as possible.
08:02user982492 has quit [Remote host closed the connection]
08:02user982492 has joined #asahi
08:08the_lanetly_052 has quit [Ping timeout: 480 seconds]
08:13Glanzmannjannau / kettenis: Do you have fix for this? https://pbot.rmdir.de/PhY6D_v509BsFcLCJiNmEg
08:25user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
08:43the_lanetly_052 has joined #asahi
08:51j`eyGlanzmann: if you mean 16k, it was tpw_rules
08:54j`eyIm not sure if Debian can do much here
08:54Glanzmannj`ey: I see, thanks. Do you happen to have the url for the patch?
08:55Glanzmannj`ey: I can file a bug report and attach a patch, than it is at least documented. They can also address it upstream and other users have at least workaround.
08:55Glanzmanntpw_rules: Do you still have the chromium 16k patch?
08:58the_lanetly_052 has quit [Ping timeout: 480 seconds]
08:59user982492 has joined #asahi
09:00user982492 has quit []
09:05j`eyGlanzmann: the one I posted is just some random patch from 2018!
09:06GlanzmannYeah, but failing a bugreport against this is probably really useless.
09:06GlanzmannI mean if they wanted to fix that, they need to ship two binaries, one for each pagesize.
09:07jannauno, I think the binary compiled for 16k page size should work for page size 4k
09:07j`eybut waste memory?
09:07linearcannon has quit [Quit: Textual IRC Client: www.textualapp.com]
09:08GlanzmannOh, I see.
09:09Glanzmannjannau / j`ey: What will our way forward be? Will we stay on 16 KB page size for perfromance reason or do we end up using 4 KB page size at some point?
09:12j`eyGlanzmann: moving to 4K cos thats what distros ship
09:12jannauI will use 16k for 10% faster compile time (kernel compile time measured wit kcbench onthe macbook pro 14" p-cores running at 2GHz)
09:13jannaubut I'm not the typical user
09:13j`eyI may stay at 16K too, but getting distros to ship it is unlikely
09:14jannauwe should not give up before even trying
09:16jannaubut I would suggest to wait with filing bugs for distrobutions. I suepect the majority of issues require some interaction with the upstream project
09:17GlanzmannI think I'll also stay ok 16k.
09:18GlanzmannI don't care about chromium, but I prefer to file the bugs now, so that they can be addressed before the next Debian release.
09:19jannaueither fixing issues there or add build config options
09:20j`eyjannau: are you going to continue using arch?
09:20jannauI would wait filing issues until we have a convenient way for distro maintainers to fix the issue
09:20GlanzmannAnd even if they dismiss the bugs at wontfix the workaround is at least documented.
09:21jannauit does not make sense to file the same bug for X distros while it's still hard for them to fix it
09:22Glanzmannjannau: The only thing from Debian missing besides the kernel is the ability to tell grub during installation to use removable media path and not update the nvram. Two options that the normal package already has.
09:22j`eybetter to file upstream and keep a list of bugs on the asahi wiki?
09:22Glanzmannj`ey: Yes, probably.
09:23jannauand in the case of a fix which can go into the upstream project, there might not even a need to bother distros with
09:23Glanzmannyep, that's true.
09:24Glanzmannjannau: So you also run at 2GHZ pcores? You don't have the m1n1 crank up patch? :-)
09:25jannauj`ey: I will probably stay on arch in the beginning to help with the asahi linux reference distro testing
09:25GlanzmannI thought about writing a guide to setup arch.
09:25GlanzmannAnd one to setup OpenBSD.
09:26j`eyjannau: very helpful of you!
09:27Glanzmannjannau: What is your distribution of choice?
09:27jannauGlanzmann: I know what I have to change but I don't wnat that on the macbook. since yesterday thanks to the push by axboe I have a cpufreq driver if I would use the macbook productively
09:28GlanzmannI see. Btw. Does the interrupt firing bug also affect the m1 (not max/pro) models?
09:31jannauI think it affects only systems with magsafe, on the air and 13" macbook pro none of the ports will probe a tps6598x driver so the interrupt never gets enabled
09:34svenif usb hotplug works the interrupts are fine fwiw
09:39equiomax[m] has joined #asahi
09:59mpsI built kernel for mediatek mt8173 (arm64) with 16K pages to test how it works, but it doesn't boot even, so I think distros will 'stick' to 4K
09:59mpsI'll test next week also 16K kernel on rk3399 to see will it work
10:00j`eymt8173 is cortex-a72, doesnt support 16K
10:01j`eyrk3399 too, it wont work
10:01j`eyif distro ship, it'd be separate 4k, 16k kernels
10:02mpsj`ey: distros like one kernel per arch
10:03mpsj`ey: yes I know but anyway wanted to test 16K on them because I'm too much curious
10:03j`eyright, which is why they would take some persuading to do 16k :)
10:04mpssometimes things known to not work with some options if time pass start to work
10:05j`eythe cortex-a72/cortex-a53 CPUs don't support 16K, it's a hw thing, not a software thing!
10:06mpsfor example yesterday I got u-boot to load compressed kernel on rk3399 though known fact was it doesn't work ;)
10:06jannaupersuading them to fix packages to run under a 16k kernel is hopefully much easier than shipping a 16k kernel and is anyway needed as first step
10:07j`eyand hopefully theres not too many packages to fix anyway
10:07jannaugood luck persuading them to ship a 16k kernel if 2% (but high profile) packages are broken
10:09jannauyes, I think my random 2% number is probably way to high
10:26qeeg has joined #asahi
10:46gabuscus_ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
10:47gabuscus has joined #asahi
11:22kovjannau, where do I find this cpufreq you speak of?
11:58Glanzmannsven: I see, hotplut works.
12:00sventhen there’s also no irq storm issue
12:08Glanzmannkov: Probably look at the backlog of dev from yesterday. IIRC the cpufreq driver is from marcan (old one) and some small device tree updates from axboe. But I have no idea if it works for m1 (not pro/max) machines.
12:12jannaukov: merge https://github.com/AsahiLinux/linux/tree/cpufreq/v1 on M1 you're done, on M1 Pro/Max you need https://pastebin.com/dHEMCCY5 the memory controller changes seem to cause nvme stability issues so I removed them from the dts
12:13svennvme stability issues? Weird
12:13svenwhat happens?
12:15jannausven: "nvme-apple 393cc0000.nvme: I/O 32(aq:0) timeout: completion polled"
12:15svenhuh, so it’s missing interrupts
12:15mtjzh has quit [Remote host closed the connection]
12:16mtjzh has joined #asahi
12:23kovjannau, Glanzmann thank you =) I was under the impression that cpufreq/v1 had bitrot somehow
12:23mtjzh has quit [Remote host closed the connection]
12:23mtjzh has joined #asahi
12:24jannauit has conflicts in MAINTAINER and the common clk Kconfig (compared to asahi) but is otherwise fine
12:26svenat least I’m not the only one who abandons patches for weeks ;)
12:29jannauI fear that's a common theme. Let's hope I revived the stalled reserved/pre-mapped mem regions series
12:29svenyeah, would be nice to get upstream :)
12:30svenand then locked darts as a follow up ;)
12:30mtjzh has quit [Remote host closed the connection]
12:32tertu has quit [Quit: so long...]
12:35kovjannau, got a conflict on the dtsi as well (doing it on top of smc/work), looks like it's mostly a matter of removing the markers though
12:36mtjzh has joined #asahi
12:37mtjzh has quit [Remote host closed the connection]
12:38jannaukov: I'm ignoring conflicts git mergetool --tool=kdiff3 can resolve automatically
12:38kovjannau, ah, nice, will add it to my config thanks
13:14mtjzh has joined #asahi
13:28mtjzh has quit [Remote host closed the connection]
13:31mtjzh has joined #asahi
13:36mtjzh has quit [Remote host closed the connection]
14:07mtjzh has joined #asahi
14:09Glanzmannjannau: Thank you for the instructions on the cpufreq driver, I rebased it on top of smc/work. And it works. mps. If you want to pick that up. Do not forget to update the device tree in u-boot. https://git.zerfleddert.de/cgi-bin/gitweb.cgi/m1-debian
14:10GlanzmannI did it by doing 'git format-patch -9' in the cpufreq/v1 branch, than using git am -3 /path/to/patch and resolving the issues manually and reexporting them with git format-patch -9.
14:13Glanzmannjannau: I also get missed interrupts on the nvme when I build my stuff: https://pbot.rmdir.de/PJeZmiC15lJFnTiAyFVlrA
14:13GlanzmannI'll lookup your fix for that.
14:14GlanzmannNow my system hangs (browser, sudo su -, etc)
14:15j`eyI would just revert the cpufreq stuff, thats going to be rewritten anyway, so if its making things unstable.
14:16Misthios has quit [Quit: Misthios]
14:16Glanzmannj`ey: I see.
14:16Misthios has joined #asahi
14:17Misthios has quit []
14:17GlanzmannBtw. what I noticed it is device tree, not the cpufreq driver.
14:18GlanzmannWith the dtb from cpufreq even with a kernel that has no cpufreq the issue happens.
14:18j`eyah then it's the mcc nodes that jannau mentioned
14:19GlanzmannYep, probably, Trying now.
14:19Glanzmannj`ey: For me it happens fast after boot. ANd I notice immediately because I can't do anything locally anymore.
14:20Misthios has joined #asahi
14:26tpw_ruleslast i checked the built chromium only worked with the flags --in-process-gpu --no-sandbox --no-zygote but that may have been a kernel config problem
14:31Glanzmanntpw_rules: Thank you. I'm a firefox user after the apis for u-block origin were removed. But I'll write it down.
14:35Glanzmannj`ey: Okay I'm over cpufreq patch. So removing the power-domains = mmc did not do the trick for me, hangs again.
14:36* kovalso decided to wait
14:36mtjzh has quit [Remote host closed the connection]
14:36Glanzmannkov: Have you tried it?
14:37GlanzmannI mean m a r c a n wants to rewrite it anyway. Than I'll pick it up again.
14:38kovGlanzmann, I did, same problem as you I'm afraid, I thought it could be something I was doing wrong, but since you hit the exact same problem...
14:38jannauremoving the power-domains fixes a crash on t600x, to avoid the missed nvme interrupts all mcc related bits from the cpufreq dts change needs to be removed
14:38kovmaybe some bad interaction between smc and cpufreq?
14:39kovI can try that
14:40jannauI haven't looked into it assuming it will be rewritten soonish. I need to work on keyboard/trackpad
14:41kovyeah, probably not worth it if it doesn't work out of the box tbh
14:41Glanzmannjannau: Never mind, I'll wait for the rewrite.
14:45tpw_rulesfor some reason this was introduced in 1.6 a couple months ago so most distros aren't affected yet
15:50kovwebkit also has that issue, so anything that uses web views in gnome or other gtk-based desktops will crash
15:50kovwell, "that issue" = same issue as chrome
15:55jannauqtwebengine will probably have the same issue
15:57tpw_rulesyeah, i haven't figured out how to fix that yet but i noticed it wouldn't build when trying to fix libunwind
15:57tpw_rulesdoes it use that same page alloc thing?
15:59jannauit's based on chromium
16:10the_lanetly_052 has joined #asahi
16:57kovhmm no impact whatsoever in the binary size for a release build of libjavascriptcore with 16k pages
17:00the_lanetly_052__ has joined #asahi
17:01eroux has quit [Ping timeout: 480 seconds]
17:06the_lanetly_052 has quit [Ping timeout: 480 seconds]
17:13eroux has joined #asahi
17:14refi64 has quit [Quit: The Lounge - https://thelounge.chat]
17:16refi64 has joined #asahi
17:21eroux has quit [Ping timeout: 480 seconds]
17:31eroux has joined #asahi
17:31eroux has quit []
17:36sheepgoose has joined #asahi
17:38qeeg has quit [Ping timeout: 480 seconds]
17:42gooseduckoftc has joined #asahi
17:46the_lanetly_052__ has quit [Ping timeout: 480 seconds]
17:48sheepgoose has quit [Ping timeout: 480 seconds]
17:53as400[m]jannau: I tried today and this 5s sleep in u-boot does the job. It boots correctly unless it stops on another error with reserving memory address.
18:01jannauas400[m]: did you try sven's patch? still strange that you're the only one seing this
18:02as400[m]Yes, strange this is the error I get from time to time ---> https://paste.debian.net/1230780/
18:03kovthere we go, let's see what people say https://bugs.webkit.org/show_bug.cgi?id=236564
18:03as400[m]jannau: I can try sven's patch
18:04as400[m]jannau: but the error I pasted is from u-boot
18:04j`eykov: thats confusing because webkit is from apple..?
18:05kovj`ey, yeah, but it has linux and windows ports and has different ceilings for those
18:05j`eyah yeah, just looking at the patch now
18:05kovif you look at the comment, all apple ports are now using 16k for their ceiling
18:07j`eyI wonder if centos/RHEL patched this? since they had 64K kernels
18:09kovI also wonder, I'll try to find out, the first mention I've seen of chromium failing was actually on a bug that mentioned RH kernels
18:11kovI was trying to get an electron build going here for vscode, but I think it'll be easier to cross compile on x86 =/ the whole thing assumes x86-64
18:11j`eyrun qemu-x86_64 on the m1 :p
18:12kovhaha I think even the xps 13 will be faster than that ;D
18:12kovwhen linux and qemu with rosetta support
18:13kovbut in the end, if there's no big impact on binary size (which seems to be their only motivation?) I think chromium will accept a change to 16k?
18:21kovtpw_rules, this is yours I think? https://pastebin.com/NzJEQJDW
18:21kovtpw_rules, will you submit it upstream? =)
18:28tpw_rulesi am not a chromium user and the submission process looked somewhat onerous, so i did not plan to
18:28tpw_rulesit should probably be changed to 64k for RHEL
18:28j`eyRHEL switched to 4k
18:29tpw_rulesi will try and test your patch to webkitgtk later
18:30kovtpw_rules, thanks! it worked with jsc and a couple apps that use webviews
18:31kovin my testing
18:31kovis there any other concern btw other than binary size?
18:31tpw_ruleswhat distro do you use?
18:32kovI guess potential memory bloat, though that would be minimal I guess?
18:32tpw_rulesi mean for chromium there is that comment about breakpad relying on segment size
18:32kovtpw_rules, I have debian on the m1 atm
18:32tpw_rulesi don't really know what that means. i think breakpad is related to the crash dump infrastructure
18:32kovtpw_rules, but my daily driver has been fedora for a while, I'll try and install that later on
18:32tpw_rulesok. i think debian is still on like libunwind 1.3
18:33kovdebian testing, let me check libunwind
18:33kovtpw_rules, yep, 1.3.2
18:35qeeg has joined #asahi
19:17chengsun_ has joined #asahi
19:24chengsun has quit [Ping timeout: 480 seconds]
19:34landscape15[m]marcan: Why don’t you make the asahi installer showing the free space disk identifier? For those like me who have three free space instances.
19:58user982492 has joined #asahi
20:24grgy has quit [Quit: ZNC 1.8.2 - https://znc.in]
20:26grgy has joined #asahi
20:27grgy has quit []
20:35grgy has joined #asahi
21:33AstaraOS has joined #asahi
21:34* AstaraOSmorning afternoon evening all
21:35* AstaraOSanyone want openbsd source code ? releasing it now
21:35AstaraOS has quit [autokilled: This host violated network policy. Contact support@oftc.net for further information and assistance. (2022-02-13 21:35:21)]
21:37Tramtristops pls...
21:37Tramtristit's back..
21:37Tramtristdont have joins/quits on so didnt realize
21:43AstaraOS-- has joined #asahi
21:46user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
21:49AstaraOS-- has quit []
22:01auwooo has joined #asahi
22:06* auwooogreeting all , how are you all ? night morning afernoon all , i have setup base here for United Nations , incase you need me just go to channel #astara and leave me a message , i will see your president from there , tell me which country are you from ... .
22:12auwooo has quit [Remote host closed the connection]
22:25GlanzmannI updated https://tg.st/u/m1-d-i.mp4 and made the process more userfriendly.
22:28Glanzmannkit_ty_kate: I sent you an email.
22:31auwooo has joined #asahi
22:36auwooo has quit []
22:36Glanzmannbauen1: The hooks from your website did not work. So I solved the issue by executing two scripts manually, one during start, and one when finished. See: https://tg.st/u/m1-d-i.mp4
22:37GlanzmannHere is the script that I used to update the daily testing initrd in order to boot be able to use the debian installer for a m1 machine: https://git.zerfleddert.de/cgi-bin/gitweb.cgi/m1-debian
22:37GlanzmannIf someone has some hints how to improve, please let me know.
22:38GlanzmannThe arm64 d-i can't create a 512MB or 1GB ESP partition because something is wrong with the fat32 cluster size. So autmatic partitioning fails.
22:38GlanzmannWrong channel.
23:00yrlf has quit [Quit: The Lounge - https://thelounge.chat]
23:28kovGlanzmann, hmm I've seen a parameter to mkfs to overcome that limit
23:31tpw_rulesyes, i think you need to say -s 1. it's in my nixos guide
23:43yrlf has joined #asahi
…