#
…

2022-02-23

00:12zvwhat more is needed than to have (a) built the kernel as mentioned earlier, (2) dd'd a rootfs image to e.g. /dev/disk0p6, (3) linux.py with root=PARTUUID=... ?
00:19tpw_rulesyes, the chromium folks semi-deliberately broke it on aarch64 with >4K pages
00:22chadmed has joined #asahi
00:23yuyichao has quit [Ping timeout: 480 seconds]
00:29rolodondo9378[m] is now known as rolodondo[m]
00:54yuyichao has joined #asahi
01:12vmeson has quit [Remote host closed the connection]
01:14vmeson has joined #asahi
01:25tanty has quit [Ping timeout: 480 seconds]
01:26tanty has joined #asahi
01:48kovblazra[m], kit_ty_kate it even made it into the 2.34.6 stable release already \o/ https://trac.webkit.org/log/webkit/releases/WebKitGTK/webkit-2.34
01:49kovI am trying to gather the energy to submit tpw_rules' patch to chromium, but haven't been able yet
01:49tpw_rulesi hope you are not doing it verbatim, i don't think it's a correct fix
01:50kovno, if I do end up doing it I'll figure out the proper fix
01:50tpw_rulesthank you for handling that; i'm not a chromium user
01:51tpw_rulesbut don't feel pressure, at least from me :)
01:51tpw_rules(or worry too much about credit etc)
01:58kovtpw_rules, tbh the main reason I would like that to go in is vscode lol
01:58kovI wish I could find a good replacement, but it's so good as a rust ide...
02:21riker77_ has joined #asahi
02:25riker77 has quit [Ping timeout: 480 seconds]
02:25riker77_ is now known as riker77
03:35PhilippvK has joined #asahi
03:39kov has quit [Quit: Coyote finally caught me]
03:39phiologe has quit [Ping timeout: 480 seconds]
03:39kov has joined #asahi
04:41marvin24_ has joined #asahi
04:47chadmed has quit [Quit: Konversation terminated!]
04:48marvin24 has quit [Ping timeout: 480 seconds]
04:51chadmed has joined #asahi
05:41chadmed has quit [Quit: Konversation terminated!]
05:46Glanzmannzv: For Debian, look at the wiki page. https://github.com/AsahiLinux/docs/wiki/Debian This automates the dding: https://tg.st/u/m1di.pl At the moment you have to boot the kernel the firs time manually: linux (hd0,gpt5)/boot/vmli<tab> root=/dev/nvme0n1p5 rw
05:47Glanzmannthan follow quickstart.txt inside /root to install grub properlly
05:47Glanzmannzv: Marcan currently works on the installer. As soon as he pushes, I'll prepare a Debian Image for the installer. Than all of that is completly automated.
05:48Glanzmannzv: I'm also working with Debian Guy on getting the official Debian installer in shape, but at the moment you can also use the official Debian installer. You just need to execute on script, when it fails to install grub from another console to install grub and the kernel.
05:48GlanzmannSee Asahi wiki Debian installer page.
05:49GlanzmannAnother option that does a friend of mine for 1,5 years: Just install Debian in a VM under macos. It runs with near native performance. Perfect for a build machine and easy to handle.
05:50Glanzmannzv: If you just want it as a build host and do not touch the kernel, in my experience Debian is very stable to run multiple weeks.
05:51Glanzmannzv: But if you want the latest and gratest features, you need to touch u-boot constantly which requires you to but into 1tr. than maybe you want pikvm with a opto coupler to the power button.
05:52GlanzmannAt some point we will have m1n1 chainload support, than you can update the device tree without fiddling in 1tr.
06:03zvGlanzmann: thanks. a VM is probably out of the question due to the extremely limited memory and wanting to minimize overhead. I'll look into the script above tomorrow.
06:09Glanzmannzv: If you have any problems, let me know. I made it a hobie to install Debian on these machines.
06:10Glanzmannzv: Oh and you can run Debian stable. The only thing you need 'testing' for at the moment is a newer libinput.
06:10GlanzmannWhich is necessary to make the touchpad run.
06:11Glanzmannzv: All the builds that are referenced in the Debian wiki, are 'testing' due to that.
06:13eroux has joined #asahi
06:13GlanzmannMy kernel builds are currently all 4k due to the webkit issue but of course in the long run I would like to run 16k pages. And I'm contact with a Debian developer which might help us to get to a 16k kernel on Debian with alle the dependencies.
06:15Glanzmannmarcan: Yesterday evening I was working on Linux and used 'halt -p' to shutdown Linux. This morning my macbook air did not turn on. Normally it turns on when I open the lid. But for sure when I press the power button. So the first thing I thought is that, I forgot to specify -p and it drained my battery. But that was _not_ the case.
06:16GlanzmannSo I plugged in the charger and tried to turn it on, no luck, than I waited 10 minutes, and tried the power button again, no luck, than I press and hold the power button. The charger was connected in the rear most usb-c port.
06:16GlanzmannThan I unplugged the charger and put it in the front most port. And it made the chime and I was able to power on the system.
06:16GlanzmannNow I checked the battery capacity and it is 76% not it was not power drained.
06:17GlanzmannDid that ever happen to you or someone else. For me. I think it was the second time that happened.
06:17Glanzmannmps: Did you had problems to turn the mbp '14 on with a charged battery?
06:33chadmed has joined #asahi
06:58the_lanetly_052 has joined #asahi
07:47MajorBiscuit has joined #asahi
08:14marcanGlanzmann: I've never seen that
08:17mpsGlanzmann: about week ago I had a 'glitch' similar like you but not same. I powered down machine with battery above 95% full. one hour later I opened lid but machine didn't started as always does. I pressed power button but again it didn't started. then I press and hold power button for about 5-10 seconds and it started
08:18mpsthat was only such 'problem' I had and only once
08:22GlanzmannI think, I had this once with the mini and again with the air. But this glitch this morning I never had before. But again replugging the power supply to the front most port, gave me the charging chime and than I could power on.
08:22Glanzmannmarcan: Once you finish the installer, we need to build a fedora installation to unboard Linus.
08:22as400[m]Glanzmann: I bet if you look at Apple forums you will find similar reports.
08:23Glanzmannas400[m]: I don't think so, because when you run macos, you never turn off your device.
08:23GlanzmannAt least, I never did, you just close the lid.
08:23as400[m]Glanzmann: ok, might be. I don't run macos :D
08:25as400[m]marcan: I noticed that upower does not properly read battery capacity on my mbp 14. Two questions: do you have the same on yours ? Would you like us to file issues like that on github ?
09:07maz has quit [Quit: ZNC 1.8.1+deb1 - https://znc.in]
09:08maz has joined #asahi
09:11marcanas400[m]: we do not have capacity values in Wh, we have them in Ah.
09:12marcanit seems upower converts that using the design min voltage, which we do provide, in the absence of a design max voltage, which I haven't found yet
09:12marcanthere is no correct way to calculate that anyway
09:13as400[m]marcan: ok. Strange it doesn't just read capacity
09:14as400[m]anyway thx
09:24gladiac has quit [Read error: No route to host]
09:24gladiac has joined #asahi
09:28gladiac has quit [Read error: No route to host]
09:28gladiac has joined #asahi
10:01marcanas400[m]: note that macOS does not report capacity in Wh either
10:01marcaneither way it's just a number, doesn't really matter if it doesn't match whatever apple uses in their marketing
10:02as400[m]marcan: yeah - just to make things "different" :D
10:04as400[m]although on their site they state that the battery is 69Wh
10:04as400[m]what a mess
10:09the_lanetly_052 has quit [Remote host closed the connection]
10:10the_lanetly_052 has joined #asahi
10:11marcanbattery capacites are a lie anyway
10:12as400[m]marcan: why ?
10:12marcanbecause it's just an estimate
10:12marcanit all depends on discharge rate and a ton of different things
10:12as400[m]ah yes - in that regard - sure
10:13as400[m]But anyway you need to have this estimate to estimate roughly how much time you have left on battery
10:20mpsas400[m]: battery calc are mostly (always) heuristic
10:40bisko has joined #asahi
10:42marcanas400[m]: no you do not
10:42marcanthe time left estimate is provided by the battery
10:42marcanthe Wh number is not needed nor used for anything useful to the user
10:44j`eyas400[m]: SMC gives a value 'TIME_TO_EMPTY' :)
10:45as400[m]I didn't know that. So this is where upower takes the value from to show you how much time is left ?
10:46as400[m]ok - I learned something new today :)
10:47the_lanetly_052 has quit [Remote host closed the connection]
10:48the_lanetly_052 has joined #asahi
10:54mpsas400[m]: https://tpaste.us/yped this is lua widget on my computers, and you can see how it calculates battery values
10:54as400[m]mps: thx - will take a look
11:03marcanmps: that code is wrong, it should be using time_to_empty
11:03marcanyou do not calculate that yourself, you let the battery do it for you if it will
11:06mpsmarcan: yes, after seeing you message above I thought to change this script
11:07mpss/you/your/
11:13eroux has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
11:14as400[m]It's probably the same with plasma battery widget. AFAIR it let's upower do this and its calculating this value instead of reading it from time_to_empty.
11:15mpsI think upower and similar things are made to be 'generic' solutions and not taking specifics of different battery models
11:15as400[m]very plausible
11:16as400[m]seems like tech went ahead again and they didn't change it
11:16mpsI'm following on #linux-rockchip loooong time discussion about this things
11:30Glanzmannmps: When you correct it, send it to me, I want to try it.
11:32mpsGlanzmann: does fvwm supports lua
11:51animus98[m] has joined #asahi
11:54akemin_dayo has quit [Ping timeout: 480 seconds]
12:00eroux has joined #asahi
12:00Glanzmannmps: yes, it does.
12:55chadmed has quit [Remote host closed the connection]
13:03mpsGlanzmann: through 'exec' or lua interpreter is integrated in fvwm
13:06GlanzmannI was mistaken. I thought i saw lua support for fvwm but must have it confused, because I just checked out the fvwm2 source code and there is no lua, but there is perl, not that I'm using it.
13:14mpsGlanzmann: aha
13:22m42uko_ has joined #asahi
13:27m42uko has quit [Ping timeout: 480 seconds]
13:46skepti has joined #asahi
14:23skepti has quit []
14:24GlanzmannDebian has a package that automatically resizes the root filesystem. I need to test this: cloud-initramfs-growroot
14:25Glanzmannmarcan: About having multiple Linux installations. So I assume the uuid of the rootfs will always be same, and the uuid of the esp will be different, correct?
14:26mpsmkfs.ext4 have '-U' option to set UUID
14:27Glanzmannmps: My question is actually, can I install three arch linux versions in parallel?
14:28GlanzmannAnd IIUC what marcan is currently doing, than the answer is no. Because grub identifies the root partition using the uuid which is hardcoded in dd of the ext4.
14:30tpw_ruleshe said he also wanted to add something that randomizes the UUID on first start after resizing the partition
14:31Glanzmannah thank you, that makes sense
14:31Glanzmannbecause having the same uuid on every system is asking for trouble.
14:32as400[m]Glanzmann: you can always use partname or dev
14:33Glanzmannas400[m]: But you probably don't want to.
14:34mpsGlanzmann: I prefer PARTUUID but marcan is free to use whatever it thinks is best
14:36mpsGlanzmann: bootaa64.efi uses gpt partition number to search for grub and then in grub.cfg 'everything is possible' to set
14:36as400[m]Glanzmann: what I'm saying is - lets not push marcan into users heads and anticipating "what would user want". The installer should be as simple as possible for the time being. That's my two cents.
14:36Glanzmannmps: I use whatever Debian uses which is uuid of the filesystem.
14:37Glanzmannmps: On Debian it is different: /boot/efi/EFI/boot/grub.cfg > https://pbot.rmdir.de/jyyewXwB6WF11X5NH48x4w
14:37GlanzmannSo they already use the uuid.
14:38GlanzmannSo if marcan change fs uuid on first boot, than I need to isntall grub again.
14:39GlanzmannBut that fits my mo anyway because it makes it much easier to build Debian automated. I can currently build the complete Debian artefacts in less than 5 minutes.
14:39Glanzmannkernel, u-boot, m1n1, root filesystem, usb stick and d-i.
14:40yuyichao has quit [Ping timeout: 480 seconds]
14:41mpsGlanzmann: I think debian use 'trick' to add something for grub on ESP to find grub files and conf and don't embed gpt part number in bootaa64.efi
14:41Glanzmannmps: On the m1 I prefer fsuuid over partuuid, because macos diskutil sometimes reassign partition numbers which change the partuuid IIUC.
14:42bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
14:42mpsGlanzmann: makes sense, I don't know how diskutil works on macos
14:42Glanzmannmps: I think, I pasted that before. Yes they have one or two patches: https://pbot.rmdir.de/VJCNncFWA2YCpQPW6Z0rrQ
14:43mpsyes, I remember
14:44mpsbut not sure how other distro do this. I only know that grub in alpine uses upstream default with `grub-install`
14:44mpsi.e. embed gpt number
14:52GlanzmannYeah, but this makes my life very easy packaging Debian, so I'm not complaining.
14:52eroux_ has joined #asahi
14:57eroux has quit [Ping timeout: 480 seconds]
14:58yuyichao has joined #asahi
14:58the_lanetly_052__ has joined #asahi
15:00GlanzmannSo applying a new uuid to the rootfs needs to be done in the initrd.
15:04the_lanetly_052 has quit [Ping timeout: 480 seconds]
15:05bisko has joined #asahi
15:52bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
16:04as400[m]Glanzmann: you need to think also about changing the ssh keys on first boot
16:13eroux has joined #asahi
16:18eroux_ has quit [Ping timeout: 480 seconds]
16:26Glanzmannas400[m]: I don't, because I don't install sshd. User can do that.
16:29bisko has joined #asahi
16:44zopieux has quit [Ping timeout: 480 seconds]
16:46zopieux has joined #asahi
17:05MajorBiscuit has quit [Ping timeout: 480 seconds]
17:17marcanyou don't change the SSH keys, it regenerates them
17:17marcanif you're installing SSH, deleting the SSH keys is one of the things you need to do before building a distributable image
17:18marcanthis is all standard fare
17:18marcanre bootaa64.efi, I'll have to figure out how it finds the part, but I'm sure we can come up with something
17:25mpsmarcan: I saw on stackoverflow something about binary patching bootaa64.efi but didn't wrote url, will try to find it
17:25marcanthat would obviously work
17:25marcanit's right there
17:25marcan00022330 28 2c 67 70 74 36 29 2f 62 6f 6f 74 2f 67 72 75 |(,gpt6)/boot/gru|
17:25marcan00022340 62 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |b...............|
17:26marcanbut there's almost certainly a better way
17:27Glanzmannmarcan: You can use the Debian grub.
17:27GlanzmannIt uses the grub.cfg in the same directory and you can specify the uuid.
17:28marcanGlanzmann: the solution to a simple problem is rarely "use another distro's package"
17:28mpsmarcan: yes, something like this
17:28marcanyou may have noticed that this project is all about doing things the right way, not about hacking together the first thing that works ;)
17:29Glanzmannmarcan: I agree, but I think Debian does it the right way, but whatever meets your standards.
17:29Glanzmannmarcan: And probably you want to use the method of the distribution, so that grub updates don't break the boot chain.
17:29marcanyes, I agree that that's a good approach, and I guarantee we can come up with a better solution than "use the debian grub package"
17:29tpw_rulesdoes debian's grub look for the grub files in another partition?
17:29Glanzmanntpw_rules: See above.
17:30marcantpw_rules: it configures `prefix` relative to the EFI boot volume, then loads a config file from there to find the real config file by UUID
17:30marcanwhich is a good idea
17:30Glanzmanntpw_rules: So Debian grub searches for grub.cfg in the same directory. In that grub.cfg it chainloads the real grub.cfg and uses that.
17:30Glanzmanntpw_rules: What marcan said.
17:30marcanGlanzmann: fwiw, you can already achieve this with grub-mkimage, which is what grub-install calls anyway
17:30marcanI'm trying to figure out if there's a way to get grub-install to call it like that
17:31mpson my machine `strings bootaa64.efi | grep ,gpt` gives `(,gpt5)/boot/grub` which is correct
17:32_jannau_mps: correct until the partition numbering changes
17:32mpsand that is done by `grub-install --target=x86_64-efi --efi-directory=/boot/efi`
17:33mps_jannau_: yes, but I don't change partition so often ;)
17:33_jannau_also not correct if the grub binary is just copied to ESP during the install from macos
17:33mpsI just told how it works with separate install media
17:34mpsand is it possible to run `grub-install` from macos
17:34mpsI think no, but who knows
17:34___nick___ has joined #asahi
17:35___nick___ has quit []
17:36Glanzmannmarcan: My plan for Debian after reading how you do things is: Don't use grub-install during image building, boot using a grub.cfg simliar to the one I posted above to boot the first time.
17:36GlanzmannDuring first boot in the initrd, grow the filesystem and exchange the uuid of the ext4
17:36GlanzmannThan with rc.local or systemd equivalent install grub the debian way.
17:36GlanzmannThat reduces complexity a lot.
17:37___nick___ has joined #asahi
17:37GlanzmannYou could do the same by patching the grub binary the same way the distro does it using python.
17:37GlanzmannIf noone else looks at it, I'll also look at Fedora. So that we can unboard Linus.
17:38j`eyhe wont run anything non mainline :p
17:39marcangood thing we're mainlining everything
17:40GlanzmannThat's why we need Linus.
17:45axboelinus was balking at the pricing of the laptops, but sounds like he wants to go get a mini
17:45axboeso he'll be receptive to get everything upstream
17:45axboeI too look forward to the day where I don't need a special branch :)
17:48marcanhey, you can boot mainline on t8103, if you don't mind a bunch of missing features
17:48marcanand if you want it on t6000, go shout at the IOMMU maintainer, that's not happening until that gets looked at ;)
17:48marcan(and then I need to submit AIC2 too)
17:48mazyup. I only use mainline on my mini, no extra patch whatsoever.
17:49marcanthere's actually not much missing there for a desktop, isn't there? other than wifi and cpufreq
17:49marcanand nvme of course
17:49* marcanpokes sven about rtkit ;)
17:50svenuh, do I need to do anything there?
17:50marcanjust figure out when and how we're submitting it :D
17:50akemin_dayo has joined #asahi
17:50svenphew. I was afraid I was supposed to do something there and forgot :D
17:51marcanbut we're getting there, right? what with having 3 consumers already
17:51marcanseems like it's slowly qualifying as decently tested
17:51svenalso doesn’t do anything stupid that only works for one iop
17:52Glanzmannaxboe: I mean the macbook air has a reasonable price, IMHO.
17:52svenand I guess nvme and possibly smc are in a shape we could submit
17:52mazmarcan: I'll probably close the door on the irqchip stuff one -rc7 is out, so if you aiming for 5.18, the time is now...
17:53marcanmaz: nod, let me take care of that tomorrow
17:53j`eysven: well bindings is the big thing missing I think?
17:53svenI’m still annoyed about that mystery lock that fixed the missed irqs but I’m out of ideas at this point :/
17:53marcanthough IOMMU is still kind of a blocker...
17:53marcansven: wanna poke that?
17:53sven(except for a scary “this doesn’t make sense but we don’t know wtf is going in either”)
17:53svenMarcan: already sent robin an email off list
17:55axboemarcan: where's the last posting of the IOMMU patches? I'm quite happy to help drive some of these forward...
17:55marcansven should be able to point you at that (the dart-t6000 stuff)
17:55svenit’s been a while, let me check
17:56marcanwith AIC2 and that, the kernel will boot on t6000, and I think there isn't even anything strictly missing, it'd be on par with t8103
17:57axboeomg november
17:57marcanIIRC the silly bug I found and fixed was already merged
17:57marcanso it's just that series
17:57axboeis he replying in general?
17:57marcanplus AIC2, which I'll send tomorrow
17:58axboeI kind of take the approach of ensuring Joerg provides a reviwed-by and then just send it in yourself for the merge window with Robin on CC
17:58svenJoerg mentioned that he wants to wait for robin to take a look at it
17:58axboesven: right, but if robin isn't replying...
17:59axboesven: then you just punt the decision higher up
17:59axboemeeting...
17:59* marcansleeps
18:00mazsven: Robin is on Libera Chat if you need to get hold of him (I saw him in #linux-rockchip).
18:19svenI’ll send another reminder to the list tomorrow
18:20svenlooks like the only other comment was jannau’s tested-by anyway
18:20svenoh, and Rob’s ack for the dt bindings
18:27the_lanetly_052__ has quit [Ping timeout: 480 seconds]
18:50jx0 has quit [Quit: poof!]
19:04the_lanetly_052__ has joined #asahi
19:09MajorBiscuit has joined #asahi
19:13the_lanetly_052__ has quit [Ping timeout: 480 seconds]
19:19mpshm, I didn't enabled CONFIG_NVMEM_RMEM in my kernel build. should it be enabled for asahi kernel
19:20mps`This driver maps reserved memory into an nvmem device. It might be useful to expose information left by firmware in memory`
19:20Glanzmannmps: I have it as a module, but it is not loaded.
19:21mpsGlanzmann: ok, I will also enable it as module
19:21mpsthanks
19:22svendon't think we use that anywhere
19:35kloenk has joined #asahi
19:46darkapex1 has joined #asahi
19:51darkapex has quit [Ping timeout: 480 seconds]
19:53MajorBiscuit has quit [Ping timeout: 480 seconds]
20:15eroux has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
20:17jannauso far no reserved memory in the devicetree, dcp will probably use reserved memory but things will blow up if another driver grabs it
20:22eroux has joined #asahi
20:42mpsheh, very nice, just plugged in something which have headphone jack and saw this with lsusb `Bus 001 Device 002: ID 4c4a:4155 Jieli Technology UACDemoV1.0`
20:42mpsand alsamixer see it
20:50mpsand found how use mpv with it
20:51mpsthis device is usb-c type
20:54mrkajetanp has quit [Read error: Connection reset by peer]
20:56mrkajetanp has joined #asahi
21:08___nick___ has quit [Ping timeout: 480 seconds]
21:43atka has quit [Quit: WeeChat 3.4]
22:30simplyemu[m] has joined #asahi
23:03GlanzmannI've modified https://git.zerfleddert.de/cgi-bin/gitweb.cgi/m1-debian/ so that it should work with the future Asahi installer. The only thing I need to modify is where the firmware tarball on the efi parition will end up. Tar archive for the efi parition is: https://tg.st/u/efi.tgz dd image: https://tg.st/u/m1.tgz '/etc/rc.local':
23:11sarah[m]It's been a while since the last blog. Can we expect any updates?
23:12Glanzmannsarah[m]: Sure. u-boot max/pro, nvme and spi support, wifi, wifi firmware extractor, smc (battery, reboot, poweroff, rtc), asahi installer (retry downloads, warn user about recovery OS, m1n1 nvme support, robustness), dcp, debian installer, OpenBSD, Asahi Installer for Arch, backlight for 2020 laptops, wip: Audio speakers on 2020 models, stable audio jack output 2020 models, stable audio input capture
23:12Glanzmannjack 2020 models, wip: usb-3
23:13GlanzmannThat is what happened since the last blog post.
23:13GlanzmannFeature-Support is also up2date.
23:13sarah[m]Glanzmann: Oh, that you
23:15GlanzmannYou're welcome, I'm sure m a r c a n will also write something up once he has upstreamed the kernel stuff and finished the asahi installer.
23:16sarah[m]Can we expect an alpha version or something once there is an installer?
23:17sarah[m]Or is the asahi project not interested in labels like "alpha"
23:17j`eyyeah, its gearing up for that
23:18sarah[m]From the feature support page, it seems linux is daily drivable.
23:18sarah[m]People would mostly be missing out on fast usb connections and audio I think
23:19sarah[m](and the gpu)
23:30GlanzmannHere is a recording of the Debian image with the fake asahi installer: https://tg.st/u/2022-02-24_00-16-19.mp4
23:31Glanzmannsarah[m]: Audio is coming at least for the 2020. Audio jack output and input already works. speakers are work in progress.
23:32GlanzmannI go to bed. n8.
23:53chadmed has joined #asahi
…