#
…

2022-03-17

00:08yuyichao has quit [Ping timeout: 480 seconds]
00:28PaterTemporalis has quit [Ping timeout: 480 seconds]
00:44yuyichao has joined #asahi
00:59mrkajetanp has quit [Ping timeout: 480 seconds]
01:35hizon has joined #asahi
02:30zvI've adjusted the USB-C cable (to an NVMe drive) to ensure it's fastened securely; so far there have been 4 cases in 3 days of the device disconnecting for one reason or another. I don't think it is a hardware problem. things like [293872.480622] usb 5-1: reset high-speed USB device number 2 using xhci-hcd ?
02:30zvreboots always fix it.
03:14chadmed has quit [Quit: Konversation terminated!]
03:18chadmed has joined #asahi
03:18creechy has quit [Ping timeout: 480 seconds]
03:29creechy has joined #asahi
03:33phiologe has quit [Ping timeout: 480 seconds]
03:37creechy has quit [Ping timeout: 480 seconds]
03:50kov has quit [Quit: Coyote finally caught me]
03:50kov has joined #asahi
03:52mrkajetanp has joined #asahi
03:58creechy has joined #asahi
04:08apg has joined #asahi
04:10kreechy has joined #asahi
04:16creechy has quit [Ping timeout: 480 seconds]
04:18marvin24_ has joined #asahi
04:21marvin24 has quit [Ping timeout: 480 seconds]
04:34tweets_so_fresh_ has joined #asahi
04:46Collin has joined #asahi
04:48Collin has quit [Remote host closed the connection]
04:57ihaveamac has quit [Quit: fail]
04:59ihaveamac has joined #asahi
05:12balrog_ has quit [Ping timeout: 480 seconds]
05:16balrog has joined #asahi
05:20kreechy has quit [Ping timeout: 480 seconds]
05:25Glanzmannzv: I consider usb drives always unrealiable for long term use. Have you considered getting the storage via NFS for the time being and wait until we have thunderbolt support?
05:33kreechy has joined #asahi
05:44CarlosCamacho[m]1 has joined #asahi
05:52on^ has joined #asahi
05:55kreechy has quit [Ping timeout: 480 seconds]
06:00kreechy has joined #asahi
06:11kreechy has quit [Remote host closed the connection]
06:20eroux has joined #asahi
06:44Glanzmannmarcan: I updated all my devices to 12.3, ping me when there is something to test.
06:44sheepgoose has joined #asahi
07:08the_lanetly_052 has joined #asahi
07:13svencould also be that the usb2 phy isn't brought up correctly fwiw
07:13sventhere's a register that has a bit for device vs host mode which we just don't change after m1n1
07:13svenand two more registers or so we just don't set\
07:13svenwho knows what that does
07:20sheepgoose has quit [Quit: Konversation terminated!]
07:28the_lanetly_052 has quit [Ping timeout: 480 seconds]
07:30oi_wtf has quit [Remote host closed the connection]
07:31oi_wtf has joined #asahi
07:35Glanzmannsven: Is that also the case for the usb-a ports on the mini?
07:36Glanzmannzv: Are you connected to the usb-c ports or the usb-a ports, if you're connected to the usb-c ports, try the usb-a ports.
07:37Glanzmannsven: I took the Debian/arm64 kernel config and modified it for asahi. Everything works, but I'm to stupid to get usb working, do you have any hints for me? Otherwise I'll try until I find what I'm doing wrong.
07:37svenno idea
07:37the_lanetly_052 has joined #asahi
07:38Glanzmannmarcan / povik: With the lastest asahi branch, I no longer have boot hangs and power management failures with the debian kernel distro kernel config.
07:38Glanzmannsven: I let you know once I have found out what I did wrong.
07:51ciggi has quit [Read error: Connection reset by peer]
07:54ciggi has joined #asahi
08:28MajorBiscuit has joined #asahi
08:31MajorBiscuit has quit []
08:35MajorBiscuit has joined #asahi
08:42pa_ has joined #asahi
08:46zopieux has quit [Ping timeout: 480 seconds]
08:49zopieux has joined #asahi
08:59apg has quit [Quit: Leaving]
09:01pa_ has quit [Quit: Page closed]
09:03ciggi has quit [Ping timeout: 480 seconds]
09:08chadmed has quit [Ping timeout: 480 seconds]
09:22Sobek[m] has joined #asahi
09:29ciggi has joined #asahi
09:30chengsun_ has quit [Quit: Quit]
09:30chengsun has joined #asahi
09:47zvGlanzmann: connected via USB-C cable; I could try USB-A and let you know. network storage is possible of course, if it continues to be an issue.
09:48svenusb-a will also give you usb 3 support already fwiw
09:57Glanzmannzv / sven: So might be more stable and better speed. zv: Let us know how it turns out to be.
10:08kameks has joined #asahi
10:16ChaosPrincess has joined #asahi
10:16Erus_Iluvatar has quit []
10:18Erus_Iluvatar has joined #asahi
10:27phiologe has joined #asahi
10:32eroux has quit [Ping timeout: 480 seconds]
10:36eroux has joined #asahi
10:44XeR has quit [Remote host closed the connection]
11:10XeR has joined #asahi
11:22amarioguy has joined #asahi
11:24rikkaa has joined #asahi
11:29PaterTemporalis has joined #asahi
11:32amarioguy has quit [Ping timeout: 480 seconds]
11:33giskard has joined #asahi
11:35choco has joined #asahi
11:36choco has quit []
11:36hizon has quit [Read error: Connection reset by peer]
11:38marcannew installer is up: curl -L https://alx.sh/dev | sh
11:39marcanlots of changes, resizing, OS sizing, colors, fixes, more logging, yada yada
11:39marcanthe OS package has not been updated, please consider this a test of the installer only
11:41marcanit requires 12.3 on paper but in expert mode it'll let you run on 12.1 still
11:41j`eyso 12.3 is required for the base macOS install no...
11:42marcanbut I really want people to try the new 12.3 mechanism
11:42j`eybut the stub it installs is still 12.1
11:42marcanright now the stub is still installed as 12.1
11:42marcanyeah, that's just an installer_data thing
11:42marcanlet me fix that
11:42kloenkwhat's new there in 12.3? missed that
11:43j`eykloenk: `bless` support for apple silicon
11:43_jannau_command line startup disk selection without automatic restart
11:44marcanj`ey: fixed, 12.3 now
11:44marcan(well, in expert mode it lets you choose)
11:44marcanI'm *really* glad we can finally get rid of that boot picker nonsense, that was going to cause us endless headaches
11:46rikkaa has quit [Remote host closed the connection]
11:49rikkaa has joined #asahi
11:49rikkaa has quit [Remote host closed the connection]
11:50_jannau_marcan: the 12.3 ipsw is still missing
11:50j`eyin src/main.py
11:51_jannau_I missed it in the all in one commit
11:51j`eyoh, not it isn't
11:51j`eyme too :)
11:52marcanyeah, sorry, I gave up on that
11:52marcanwasn't going to happen cleanly
11:53j`eyjust as long as it doesn't happen in linux.git, it's fine :P
11:58_jannau_my mac studio is apparently already in the Netherlands, apple claims it will arrive at april 1st - 5th (pushed 2 week back)
12:00marcanyeah, I got a delay email too, 30th at the latest...
12:01GlanzmannMore time for the release.
12:01maznot got anything yet, but I'm not scheduled before mid-May anyway...
12:03marcanGlanzmann: the release is not waiting for that
12:06GlanzmannI know, I was just thinking about your studios this morning and wanted to ask when the bring up stream will be, but now I know. :-)
12:06_jannau_no updates from Apple so far but got message from DHL that they received the shipment information with pickup in Eindhoven
12:06j`eyno bring it upstream, it'll Just Work ;)
12:06Glanzmannjannau: When I orded my macbook air, it was the same. And than it took 2 weeks or so until it was shipped.
12:07_jannau_I've checked Apple's order status and that said april 1st - 5th
12:08Glanzmannjannau: I think Apple has the right date. At least in my three cases it was always a day or two before the announced date. I ordered seperately two airs and one mini.
12:08kloenkSlightly offtopic, is there any plan to look at/someone already did to bring linux to ipad? they have an m1 as well, but I guess no 1TR?
12:09marcanno BootPolicy
12:09marcantherefore no running your own anything
12:09kloenkwhat I guessed :)
12:10MajorBiscuit has quit [Ping timeout: 480 seconds]
12:11Glanzmannmarcan: In the installer, id I leave out the volume_id it will randomize it?
12:11_jannau_I assumed apple would only order the pickup after the package is already there
12:12Glanzmannjannau: For me it was either a very large chipment and they took 2 weeks to unload or they submitted it before.
12:13sveni got my m1 pretty soon after DHL sent me the that initial shipment mail
12:13svenand that was at least one week before the date claimed on Apple's website
12:13Glanzmannsven: For me it was the opposite.
12:13svenyeah, you just said that
12:14kettenisthe way apple ships things is pretty bizarre
12:15kettenismy mini was shipped from Ireland, whereas the 14" macbook pro was handed off to UPS in china
12:15Sobek[m]Could it be simply bizarre because of the insane amount of things they are shipping on launch / in the initial launch period ?
12:16Sobek[m]Also could BTO vs rather stock configs explain some of it ?
12:16kettenisalmost certainly
12:17Sobek[m](Like stock configs don't need to get out of the factory and so get sent as a big package to various platforms, in huge batch, and then they open the big box and spread the small box for the various people, vs BTO get tracked out of the factory)
12:42Sobek[m]Unrelated, I just read that some M1 mac that had had their logic board replaced got bricking issue when updating to 12.3 (or iBoot panic messages). I wonder if the experts in AS boot process might have a clue about what exactly could cause the boot system to be unhappy after such a replacement ?
12:44brentr123[m]Over voltage?
12:49Sobek[m]https://www.macrumors.com/2022/03/17/macos-monterey-bricking-macs-logic-boards/ for the source. I wonder how the OS detects the motherboard is not the right one (especially given many things or on the motherboard).
12:49Sobek[m]It's not really bricking and more failure to boot / boot loop.
13:02chadmed has joined #asahi
13:06marcanthat's not really a brick, since DFU works
13:06marcanlooks like just a dumb bug
13:08hizon has joined #asahi
13:08marcanand if you're wondering why nobody noticed: I bet it's because Mac Studio
13:08marcanbefore hardware launches, Apple release a new release with new support *on the RC*
13:08marcanthat means all the other prior betas are incomplete and useless as far as catching these regressions go
13:08marcanso all they have is their internal testing
13:09marcanApple's secrecy/surprise announcement stuff is directly at odds with quality, by definition
13:10marcanseveral times now there have been major changes between the last beta and the -rc, for this reason. last time it was with 12.0-rc.
13:10marcan(that was when they broke Mac Mini HDMI output in iBoot)
13:10marcan(though apparently that one was intentional?)
13:15Sobek[m]Apparently the bug occured also with the dev beta.
13:31marcanunclear if it's really the same bug
13:31kovyeah I've been wondering about that, the HDMI output is still not working on the Mini right? for early boot, I can't imagine that's intentional as it disabled the 'keep holding power to go into options' screen?
13:31marcankov: still not working and I think it's intentional
13:31marcanDCP works fine so it's iBoot just not turning it on
13:34Sobek[m]Is this iBoot 1 or 2 ?
13:35Sobek[m](Are they both updatable ?)
13:35marcanboth changed a lot
13:39yuyichao has quit [Ping timeout: 480 seconds]
13:39kovmarcan, why would they want that? working around issues with some screens?
13:41kameks has quit [Ping timeout: 480 seconds]
13:58mps_if I enable speakers in dts they work but then jack (headphone output) doesn't work. is that expected (for now)?
13:58yuyichao has joined #asahi
14:03mps_Glanzmann: I see, thanks (though looks line not proper 'fix')
14:04Glanzmannmps_: povik wants to put jack detection and switch depending on if there is jack plugged in or not in the future.
14:04Glanzmannmps_: Did you get your text console back?
14:05mps_Glanzmann: not yet, didn't had time to further test needed drivers/options
14:07hizon has quit [Ping timeout: 480 seconds]
14:22kreechy has joined #asahi
14:36kgarrington has joined #asahi
14:39kgarrington has quit [Remote host closed the connection]
14:41kgarrington has joined #asahi
14:42kgarrington has quit [Remote host closed the connection]
14:42kgarrington has joined #asahi
14:43mps_after blindly typing 'dmesg > dms.2' I've found this in file after reboot with working kernel `simple-framebuffer be206c000.framebuffer: [drm] *ERROR* could not acquire memory range [mem 0xbe206c000-0xbe300bfff flags 0x200]: error -16`
14:44kgarrington has quit [Remote host closed the connection]
14:54mps_Glanzmann: ah
14:54mps_but next line in my log is `simple-framebuffer: probe of be206c000.framebuffer failed with error -16`
14:55mps_and in your log I see it later find it and set /dev/fb
15:04Glanzmannnew asahi branch debian kernel tested on the air: curl -sL tg.st/u/ksh
15:05kreechy has quit [Ping timeout: 480 seconds]
15:07kreechy has joined #asahi
15:24Glanzmannpovik: With the latest asahi branch I have the problem that I can only mute the jack or totally overblow it volume wise.
15:25Glanzmannpovik: Might it be possible that this because I once executed 'pacmd load-module module-alsa-sink device=hw:0,1'?
15:25MajorBiscuit has joined #asahi
15:26Glanzmannpovik: However when I start pacmd and issue pacmd list-module, I can't see it: https://pbot.rmdir.de/IGFY96yh-oY1tpkKTsrnqQ
15:26povikno, that's because of something i did in one of the drivers
15:27poviki thought it might be a good idea but it's not it
15:27povikthe "Mixer Volume" knob is fixed at its maximum
15:27povikand hidden from userspace...
15:27Glanzmannpovik: I already tried to play with alsamixer and pavucontrol but I only get blow my brain out or mute.
15:27Glanzmannpovik: Maybe put that know to 25% or 50% than it will be fine.
15:28povikah, so if you disable the speakers in DT you can turn down the volume at pulseaudio level
15:29povikbut if you enable speakers and do the load-module thing, you can't?
15:29Glanzmannpovik: This is with disabled spakers.
15:30povikthe other day you posted you could turn it down
15:30povikmaybe it is because you ran load-module after all
15:30Glanzmannpovik: Do you know how I get rid of it?
15:31poviktry rebooting
15:31povikdon't know what could be different from when you could turn it down
15:32GlanzmannSince i tried the speakers, I rebooted about 20 times.
15:32povikah so you are sure you haven't run load-module since last reboot
15:34Glanzmannpovik: This solved it for me: rm -rf .config/pulse/
15:35GlanzmannAnd reboot (don't know if the reboot was necessary).
15:35povikanyway you can just remove the line i linked to have the alsamixer knob back
15:35tohatsu[m]Debian installed on internal NVME is not persistent? It boots the same initrd.gz as it boots if installed on USB?
15:35Glanzmanntohatsu[m]: It is persistent.
15:36tohatsu[m]can i make it not persistent
15:36Glanzmanntohatsu[m]: Yes, you use the live cd.
15:36tohatsu[m]and sync it with initrd.gz on usb
15:38Sobek[m]The talk about iPad earlier today made me wonder, is the lockdown of those device in hardware or is it bootloader software that could be by apple if they decided to change their mind ? (Very unlikely barring intervention of some deity however, I'd recon)
15:38Glanzmanntohatsu[m]: ALso that is possible with: https://pbot.rmdir.de/1c0vwV4diKo3Vna0JvX0Lg see also 'tail -15 /root/quickstart.txt' in the live system itself.
15:39tohatsu[m]so i curl debian-live.tar to internal partition? and uboot will choose nvme if no usb connected?
15:42Glanzmanntohatsu[m]: Almost. If you want that it boots automatically you need to replace msdos1 with gpt4 or whatever your esp partition is.
15:42GlanzmannIn the grub.cfg
15:44tohatsu[m]linux (hd0,gpt4)/vmlinuz expert # like this?
15:45Glanzmanntohatsu[m]: Yes, and don't forget the initrd as well.
15:47tohatsu[m]how do i make fat volume out of Free space? diskutil doesn't show IDENTIFIER
15:48Glanzmanntohatsu[m]: You need to run the asahi installer, it will create the esp partition.
15:48Glanzmanntohatsu[m]: Can you paste the output of diskutil list to tg.st/p ?
15:50Glanzmanntohatsu[m]: You already have an esp partition.
15:50tohatsu[m]512mb is not enough, i need 1GB+
15:51GlanzmannSo if you really want to do what you just said than you run the following commands: https://pbot.rmdir.de/RwW72h9onAMYiqdY7cwegQ
15:52Glanzmanntohatsu[m]: Nope, it is enough. You need 217M.
15:52Glanzmannof free space.
15:53tohatsu[m]efi for booting purposes? initrd.gz is going to be on another volume?
15:54Glanzmanntohatsu[m]: You can also leave it on the volume, of course at some point you will run out of space.
15:54Glanzmanntohatsu[m]: Just to be clear, you want a live system and don't install Debian on the nvme?
15:56tohatsu[m]Live not persistent debian on both NVME and USB, which i will sync sometime by copying initrd.gz
15:59tomtastic has quit [Ping timeout: 480 seconds]
16:07marcanasahi-base OS image has been updated, along with the installer (just bumps m1n1 to 1.0) and Arch packages
16:07marcanhopefully this is actually usable now, the PCIe explosions should be gone
16:09Glanzmannmarcan: Will test it and report back.
16:14Dcow[m]1marcan: great news. looks like you made pcie always on? how this affects the battery life?
16:14Dcow[m]1are you still going to prepare plasma image today?
16:15marcanpcie was already always on
16:15marcanit was just getting momentarily turned off during boot
16:15marcanand that was breaking things
16:15marcanand yes, hopefully
16:17Dcow[m]1gotcha, gonna wait plasma image to try again
16:17Dcow[m]1thank you for the efforts!
16:29on^ has quit [Remote host closed the connection]
16:42marcanalso, the CDN is the default mirror now, and I just set up the caching rules to be quite conservative
16:58_jannau_u-boot ESP selection would be nice to have in case people try to install the base and plasma os image at the same time
17:05the_lanetly_052 has quit [Ping timeout: 480 seconds]
17:05ciggi_ has joined #asahi
17:08ciggi has quit [Ping timeout: 480 seconds]
17:14Glanzmannmarcan: I like the new installer, but maybe you can provide some help for the alarm: How to get wifi working, how to install a desktop environment?
17:14GlanzmannI tested on my wifes air and it works. I like the new colors and sane defaults.
17:15firefox317Glanzmann, for the desktop env there will be a plasma image. Otherwise from the base image the process is the same as with normal ArchLinuxOnARM. You can use iwctl to configure wifi, see: https://wiki.archlinux.org/title/Iwd
17:16MajorBiscuit has quit [Ping timeout: 480 seconds]
17:20GlanzmannSo I configured wifi, is there a dhcp client installed?
17:22firefox317Glanzmann, probably better to use systemd-networkd instead of manaully starting the dhcpcd deamon yourself. You can configure systemd-networkd using: networkctl
17:23firefox317not 100% sure tho
17:27milek7I think you can do systemctl start dhcpcd
17:27GlanzmannI already deleted it again. Just wanted to see what it looks like. root password is 'root'.
17:28tomtastic has joined #asahi
17:31amarioguy has joined #asahi
17:36ChaosPrincess has quit [Quit: Page closed]
17:36ChaosPrincess has joined #asahi
17:39amarioguy has quit [Ping timeout: 480 seconds]
17:52mps_with iwd you don't need dhcp client
17:53mps_it has one inside it
17:54mps_you just need some of external 'helpers' (openresolv or systemd-something) to set params
17:58firefox317marcan, base image works great on j313!
18:04Glanzmannmps_: I see.
18:07mps_Glanzmann: man iwd.config and look for NameResolvingService option
18:14marcanfirefox317: yay!
18:15marcan_jannau_: I was going to ask about that, I'll merge it via releng
18:17marcanthat ticks off another TODO :)
18:18kettenisgood I just fixed the OpenBSD installer to not nuke the ESP ;)
18:20Sobek[m](I'm a bit confused about what's going on with Efi System Partitions when Apple Silicon is supposed not to have EFI, would someone explain what's going on here ?)
18:20Sobek[m](Or point me at the right documentatin page)
18:20j`eySobek[m]: U-boot provides UEFI
18:21Sobek[m]Thanks !!! Makes more sense
18:22m6wiq has joined #asahi
18:27Sobek[m]Reading this new doc, I was wondering why was m1n1 split in 2 phases (with chainloading, and using rust from what I've seen in tweets), but I found the explanation. (update ability without using 1TR + secure boot). Great job !!!!
18:34marcan_jannau_: u-boot updated in the repo, pacman -Syu should pull it in and do All The Magic
18:35marcanSobek[m]: no secure boot yet but that's the plan (hence the rust for that bit)
18:37Sobek[m]The simple fact that you are setting up all the parts so that it will work is pretty impressive ! The amount of foresight in the design is impressive. (Has there been any design decision you had to change afterwards with a serious cost (or know that they'll need to change at some point in the future at such a cost) ?)
18:43j`eynothing major. device tree compatability is the main one. that was broken with the power management update, and seems it will also be broken with usb3 support
18:43marcanwe've been trying to catch all the ones that will cause us pain down the line early :-)
18:44marcanchainloading actually got bumped to something to get done for the first release rather recently, and I'm glad it did
18:45marcanj`ey: the good thing is as of, er, the asahi-scripts release I just tagged, kernel updates automatically update the m1n1+u-boot image in the ESP with the new kernel's DTBs
18:45marcanalso, for the record: until now I've played fast and loose with re-making package versions, but starting ~now I'm committing to properly managing versions, so pacman should pull in all updates automatically
18:47j`eymarcan: that change you made to use the kernel DTBs.. looks like it assumes only one kernel has been installed?
18:48marcanthat is how things normally work on arch, yes
18:48marcanI'm not saying all distros will want to do it this way :-)
18:48j`eyoh ok, been a while since I used arch
18:48marcanit looks for DTBS=/lib/modules/*-ARCH/dtbs/*
18:48marcanif you have non-arch kernels they will be ignored
18:49marcanif you somehow manage to install multiple arch kernels, then yeah, you get to keep the pieces
18:49marcanbut I don't think that's normally a thing
18:49Sobek[m](As a gentoo user I just recently caught myself with a large number of old kernel source trees needing to be cleaned up, GB worth of it 😅)
18:49marcanyeah, the arch approach is "just keep the latest kernel only!"
18:49marcanwhich is... sub-optimal when regressions happen
18:49marcanbut hey, this is why I run gentoo on my servers, not arch :-)
18:49j`eyyes :)
18:50jannaumarcan: for the second install it has to be in the install binary. if it is missing u-boot will always boot from the 1st ESP
18:56marcanjannau: of course
18:56marcanI just haven't updated the images yet
18:56marcanwill happen when the plasma image is pushed :)
18:56marcanthe images are already pulling from the repo, nothing is left outdated there
18:56marcanit just needs to be regenerated
18:57marcanuboot-asahi and m1n1 updated (removed the hook, that's now taken care of by asahi-scripts)
19:01zamadatix has joined #asahi
19:01zamadatix has quit []
19:01tohatsu[m]any way to increase EFI 512mb to 1+GB without recreating it?
19:02tohatsu[m]my initrd.gz does not fit
19:03marcannot sure if diskutil can resize FAT32, maybe?
19:03mps_does asahi kernel for Arch use initram
19:03marcanbut not in the ESP
19:03marcantohatsu[m]: ESPs are usually 100-500MB or so, so you might want to consider whether whatever you're doing is sane
19:03mps_marcan: in /boot dir?
19:03marcansounds like you'd run into this on many other systems
19:03marcanmps_: yes
19:04mps_is there binary pkg somewhere or to pull complete installer and extract
19:04marcanbinary pkg for what, the initramfs?
19:04mps_no, complete kernel + initramfs
19:04marcanthe initramfs is generated by mkinitcpio
19:04kettenismps_: look at the script
19:05marcanthe kernel is a package like any other
19:05mps_and on install it creates initramfs?
19:05mps_ok, thanks
19:05bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
19:05mps_want to see will I got text console with it
19:06bisko has joined #asahi
19:07Dcow[m]1what is the proper way to uninstall asahi linux?)
19:07marcandelete the partitions
19:07j`eyDcow[m]1: it's impossible, you can never leave!
19:07marcanthere is a tools/wipe-linux.sh which will indiscriminately wipe everything, don't run it unless you know what you're doing
19:07marcanin the installer repo
19:08svenj`ey: you’re not supposed to tell anyone that!
19:08j`eysven: ;-)
19:09Dcow[m]1Yeah, I saw that. My question was more like "is it enough to delete partitions or not?"
19:09marcanit is enough
19:09marcanwell, you can also resize macos back to full size of course
19:09marcangarbage boot policies will also be left behind, that script also removes them
19:09ChaosPrincessmaybe also clean up boot policies, no?
19:09marcanthose don't break anything but they will slow down boot policy actions as they pile up
19:09marcanso you don't want too many
19:09Dcow[m]1>garbage boot policies will also be left behind, that script also removes them
19:09Dcow[m]1that the answer I wanted
19:10Dcow[m]1* > garbage boot
19:11Glanzmannmarcan: Can the installer already update the stub partition, or do I have to delete it and recreate it?
19:12marcanthere is no update functionality yet
19:12GlanzmannI see, I'm testing currently with Debian and doing a recording.
19:12marcanhopefully people won't have to do that for a while
19:12Glanzmannmarcan: I thought about the early adopters.
19:15j`eybut just erasing the stub partition with diskutil, and then re-running the installer works right? was planning on updating to 12.3 that way
19:15mps_hmm, no text console even with Arch kernel, strange
19:15kettenisj`ey: you'll end up with another ESP that way
19:17j`eykettenis: I can pick the 'tethered' boot option, to not get the ESP
19:17j`eyand then re-kmutil
19:17j`eyor just stop step2 from doin that
19:17Glanzmannmarcan: I installed arch on my wifes air and I had console output.
19:18Glanzmannj`ey: Yes, that what you have to do and recapture the firmware.
19:18Glanzmannj`ey: Or you take a backup copy of your esp, wipe it, too and recreate with the esp and extract grub to the new esp. That is what I'm going to try on my air.
19:20j`eytheere's no rush for 12.3, so Ill just do it Later(tm)
19:20bluetail[m]I talked with some colleagues
19:21kettenisj'ey: not sure if you end up with a 1st stage m1n1 that loads the right 2nd stage m1n1+u-boot+dtbs that way
19:21bluetail[m]They essentially told me that macs for the cheaper-end consumer market using cheaper material so that the color output is limited compared to Windows machines
19:22bluetail[m]There was even a test-case, where some colors where always mismatched... This is in regards to color measured with a pixel grabber
19:23tpw_ruleswuh? apple makes a big deal about color and HDR and stuff
19:23j`eykettenis: oh hm, yeah, I can fudge it, but it probably does need more work for a proper updater
19:24tpw_rulesi mean the macbook pros have 4x the colors
19:24j`eytpw_rules: yeah I find that pretty unlikely
19:24tpw_rulesor well 64x across all the channels
19:25bluetail[m]tpw_rules: colors produced and matched on macOS are often invalid. Make a prototype in figma, find a color that you like, look at it on a microsoft machine and then realize it's off... It's as simple as that.
19:25bluetail[m]You can even use the same monitor and the same color profile
19:25bluetail[m]You can measure the pixel itsel
19:26bluetail[m]s/itsel/itself/
19:26tpw_rulesapple has slightly different interpretations
19:26bluetail[m]it will be different on mac
19:26tpw_rulesyeah, cause apple applies color profiles
19:26j`eyyou can do that experiment the other way around ;)
19:26bluetail[m]You cant get that sorted with a colorimeter
19:26j`eystart from macOS and say it looks different on windows
19:27bluetail[m]but thats not where the color measuring software is used....
19:27tpw_rulesi mean it is true that the pixel value you paint your rectangle with and what gets sent over the monitor cable will be different, but that's because a color profile is applied to the whole system
19:27GlanzmannI updated https://alx.sh/w/Debian and https://tg.st/u/debian_asahi_installer.mp4 for the new Debian. marcan did a great job.
19:27bluetail[m]When you measure with anything like that on macos
19:27bluetail[m]for instance the color picker
19:28bluetail[m]you will be off
19:28bluetail[m]if you measure on windows, it will find a different value
19:28bluetail[m]but thats only for some colors
19:28bluetail[m]not for all
19:28kettenisthis is waaay offtopic
19:29bluetail[m]but this shouldnt be the case on linux :D
19:30kettenisI don't think anybody in their right mind expects linux output to be properly color calibrated ;)
19:32Glanzmannkettenis: I'm happy that we have display output again.
19:35bluetail[m]wdym with display output? It's not that we can share the mac display with foreign devices now, for instance a windows laptop, right?
19:35j`eybluetail[m]: there was a while where mini didnt have output on linux
19:53Glanzmannj`ey: I just updated by stub by evacuating 'EFI/BOOT' run asahi installer 2 option and extracted it (of course I forgot to modify the /etc/fstab) But that went smooth.
19:53GlanzmannI deleted the old stub and esp partition from Linux.
19:58Glanzmannmarcan / sven: I just updated my stub on the macbook air to 12.3 and lost usb.
19:59GlanzmannWait maybe it is just the outdated dtb on the '2' installer.
20:00Glanzmannmarcan / sven: Yes, that was it.
20:00GlanzmannUSB is back.
20:01Glanzmannj`ey: So also evacuate and put back the 'm1n1/boot.bin' if that is a thing for you.
20:01bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
20:02bisko has joined #asahi
20:02Glanzmannsven / marcan: Maybe I have problem anyway.
20:03GlanzmannBut I don't see the video grabber or the Jabra Headset that I have connected.
20:04svendwc3 still doesn’t probe for you
20:04GlanzmannBoth were there before I updated the stub version to 12.3
20:04Glanzmannsven: On the distro kernel, no.
20:04svenit’s not the stub
20:04Glanzmannsven: On the striped down asahi config tha I used forever it does.
20:04svenits definitely a wrong config
20:04Glanzmannsven: The same kernel worked before. The installer video was recorded with this.
20:04svenI’m willing to bet money it’s a missing config option
20:04svenI don’t think so
20:05Glanzmannusing a jabra headset and a video grabber.
20:05jelly has quit []
20:05svenshow me your config
20:06svenand if this a config problem *again* maybe it’s time to stop messing with it
20:06bluetail[m]offtopic: Killed 3 jabra headsets within 10 months. Always: Control unit broke, headset still intact - could be used with a USB soundcard.
20:06Glanzmannsven: Here is my kern.log same kernel multiple reboots (you can see the jabra headset and than its gone): https://pbot.rmdir.de/43zzHbfzdvxHmRqn_zcPgA
20:07bisko has quit []
20:07svencan I have that as a plaintext file please?
20:07bisko has joined #asahi
20:08tohatsu[m]which commands remove 2.5G stub and EFI partitions ?
20:08GlanzmannThat is /proc/config.gz
20:09Glanzmanntohatsu[m]: From macos: https://pbot.rmdir.de/c4JQgEKHEwu2tWZlP5ASTw From Linux parted /dev/nvme0n1<RETURN>print<RETURN>rm n<RETURN>
20:10svenokay, I’m confused now. Is this problem different from the one yesterday where dwc didn’t probe at all?
20:11tohatsu[m]Glanzmann: thanx, worked like a charm
20:11Glanzmannsven: Yes, that is a different config. But I'm happy to send it to you, too.
20:11bisko has quit []
20:11Glanzmannsven: Yes, it is different.
20:11svenlet’s start with the one from yesterday
20:12Glanzmannsven: With the other kernel config (where it is probably a config problem or race) lsusb does not show any devices.
20:12svencan I have the config you used there?
20:13GlanzmannOne time I tried to load it as module, than compiled in and than I tried to deselect one option (which is the try2 the try2 should have todays date)
20:13svenplease fix your Webserver, it sends the wrong content type and I can’t open this on my mobile phone
20:14Glanzmannsven: Okay, I fix that.
20:15sven# CONFIG_TYPEC_TPS6598X is not set
20:15sventhat’s your issue there
20:16bisko has joined #asahi
20:16jannauand it's a module in the current config
20:16Glanzmannjannau / j`ey: I fix that and try it.
20:17jannaunot sure if that's the problem but it's something to start testing
20:18GlanzmannCompiling.
20:19jelly has joined #asahi
20:19sventps6598x: probe of 0-003f failed with error -61
20:20axenntio has joined #asahi
20:20sventhat’s also not good, but I can’t check what -61 is here
20:22axenntio has quit []
20:23kreechy has quit [Ping timeout: 480 seconds]
20:27Glanzmannsven / jannau: Same kernel / stub (12.3) was used on the mini and there it appears to work (I can hotplug a usb keyboard which I can't on the air.)
20:32svennow that sounds like an actual issue now
20:32svenit looks like there’s something wrong with i2c on that air
20:34bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
20:35bisko has joined #asahi
20:38Glanzmannsven: I see. :-( USB curse strikes again. I fixed the stub version in the debian installer to 12.1 for the time being and downgrade my stub on the air.
20:38svenuh, and that actually fixes the issue?
20:39Glanzmannsven: I assume so, because that is - to my knowledge - the only thing I changed. But I'll leave the kernel for the time being as it is and downgrade the stub.
20:40Glanzmannsven: usb-c did not give me trouble on the air and I used the air a lot on Linux.
20:42bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
20:42bisko has joined #asahi
20:43Glanzmannsven: You'll probably kill me, but ... I once booted the air with the right kernel with the wrong dtb and the right kernel and than rebooted (without turning it completly off). Now I did a 'halt -p' and tuned it on again, and guess what, usb is back: https://pbot.rmdir.de/NaxC4a28g2wRK5XcR99VEg
20:43GlanzmannI'll reboot a few more times.
20:44j`eythats a confusing sentence, but I think it means you were using an older dtb
20:45kreechy has joined #asahi
20:46Glanzmannj`ey: I upgraded my stub to 12.3. The asahi installer put me some outdated stage2 m1n1 with an outdated dtb on my esp. I booted with the most recent kernel.
20:46marcanheh, I installed wayland and xorg, and this defaulted to wayland... and I'm already running into problems with scaling
20:46marcanlooks like good old xorg it is for now
20:46Glanzmannusb broke. I rebooted a few times, still broken usb. Than I did a halt -p and booted again now I can no longer reproduce the issue.
20:46j`eyGlanzmann: weird
20:47Glanzmannsven / jannau / j`ey: Anyway the next time, before I report a bug, I'll turn it off and on again and see if that fixes it.
20:48Glanzmannmarcan: Great job on the new installer.
20:48marcanbtw, I just built a plasma image and everything is working on the first try :-) (modulo the wayland default)
20:48marcanjust need to add a few tweaks and Calamares and that's about it
20:49Glanzmannj`ey: I tried 'reboot' and 'halt -p' about 10 times and I can't reproduce the issue.
20:49Glanzmannmarcan: Btw. your new installer also worked on first try (that was the recording) with Debian.
20:49marcanwell, it doesn't really care about what distro you install, it's just a different image
20:50marcanit'd be weird if it worked for one and not the other
20:52j`eymarcan: nice, hopefully not too long left until its done!
20:53marcanaudio jack worked out of the box with pipewire, although it had a hiccup and I had to poke the output mode in pavucontrol
20:53marcan(this is on an MBA)
20:53j`eyI tried wayland+sway, worked well with 1x and 2x scaling
20:53marcanj`ey: 3 more hours left in UTC to call it today so... :)
20:53marcanyeah, but 1.5x scaling is ~ideal for these machines
20:53povikoutput mode?
20:53marcanthe profile
20:54j`eymarcan: yeah 2x was a little big :P
20:54marcanUSB ports work on this MBA
20:55marcanlooks like pretty much everything works, so I guess just the firstrun wizard now
20:55marcanwhich is already mostly there
20:56j`eymarcan: why dont you try get a GPU driver done too, after all you do have 3 hours still
20:57tpw_rulesdid usb-a in u-boot get fixed?
21:01bisko has quit [Read error: Connection reset by peer]
21:02Glanzmanntpw_rules: I fixed it: https://tg.st/u/IMG_20220317_220136185.jpg you want the high speed ports for usb sticks anyway.
21:02tpw_rulesfixed what?
21:03tpw_rulesi mean yeah i've used a usb a to c adapter too
21:03tpw_rulesbut i wanted to know if i could remove that note from the guide
21:03Glanzmanntpw_rules: Just a silly joke, I shut up for today.
21:03marcanpovik: weird, I rebooted and got only left channel
21:03marcanmaybe it's flaky?
21:04bisko has joined #asahi
21:05marcanand now nothing, yeah
21:05marcananother reboot and stereo works
21:10Glanzmannsven / jannau Thank you for your help with the debian distro kernel. It works with usb-3. dmesg: https://pbot.rmdir.de/i7DSaMfQ39h-fdEWtOvouA config: https://tg.st/u/config-2022-03-17-distro-sven-jannau.txt But I build dwc3 as module, but it works anyway.
21:11* povikthinking
21:12povikwell there was the i2c breakage i didn't get to the bottom of
21:12povikjust haven't seen that in a while
21:17m6wiq has quit []
21:31marcanlol, the apple jis keyboard layout has the eisu and kana keys swapped
21:31marcan*patches the xkb stuff again*
21:31marcanreally, nobody has been taking care of these layouts have they :/
21:33arwell, between 2008-ish and recently, their laptops were just generic x86 machines if you didn't want to put up with macos :/
21:37sveniirc some of iMacs were decent-ish even for running Linux
21:40marcanar: the keyboards were still like these
21:40mofux[m]i have an earlier install (created by an older alashi installer). what is the correct way to update? e.g. should i just wipe the partitions and run fresh again?
21:40opticronmarcan, it was just as bad 5 years ago when I was running Linux bare metal on the chromebook pixel
21:41marcanwhich means these keys have been backwards for all japanese keyboard users in alu keyboards since forever
21:41marcanunless apple swapped them, which I highly doubt
21:41opticronit was a pain in the ass to manage keyboard configs
21:41opticronso yeah, sounds like no one has even looked at it in forever
21:44GlanzmannDebian users: Here is a debian distro kernel (taken from testing) with the asahi options turned on. Bit thanks to sven and jannau. Tested with the air and mini: curl -sL tg.st/u/ksh
21:44marcanalright, time to put in a quick hack for keyboard layouts in m1n1...
21:49opticronGlanzmann, comes up on a m1m 14" mbp
21:52Glanzmannopticron: Thanks for testing.
21:56opticronand I just realized that the usb-c/usb-a adapters that google provides with pixels are usb2-only
21:59eroux has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
22:01svengood thing our usb-c ports are usb2-only right now as well ;)
22:18j`eymarcan: huh, keyboard layouts in m1n1?
22:19j`eyoh, just saw the commit, more ADT->FDT forwarding
22:31Telvana has quit []
22:32gladiac has quit [Quit: Ping timeout (120 seconds)]
22:32gladiac has joined #asahi
22:33M1bn3mar[m]Hi is it possible to install gentoo using this or is it a rabbit hole; btw i don't mind a learning curve.
22:34giskard has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
22:35j`eyM1bn3mar[m]: it's possible yes, chadmed put sme stuff here https://github.com/chadmed/asahi-gentoosupport
22:35j`eyI have no idea how usuable that is, or what it actually contains
22:39M1bn3mar[m]j`ey: well it looks way too easy which usually means too good to be true, thanks though
22:40Telvana has joined #asahi
22:47M1bn3mar[m] install.sh: move scripts/post-install.sh
22:47M1bn3mar[m]post-install.sh into being the One True Install.
22:47M1bn3mar[m]the scope of this project has changed, so we move
22:48M1bn3mar[m]* chadmed/gentoo-support install.sh:
22:51j`eyM1bn3mar[m]: dont edit stuff on matrix.. it kinda spams irc
22:51m6wiq has joined #asahi
22:51M1bn3mar[m]ok, what now
22:51m6wiq has quit [Remote host closed the connection]
22:53M1bn3mar[m]what is One True Install
22:57j`eyM1bn3mar[m]: I think thats just chadmed being silly
22:58hizon has joined #asahi
22:59M1bn3mar[m]j`ey: u mean like he didn't even make a script in the first place?
23:00j`eyI guess they were planning to have a bunch of scripts and then just decided to have one
23:01marcanbuilding plasma image...
23:01marcanwill this work?
23:01marcan(with the setup wizard)
23:02M1bn3mar[m]ok, could i just be the installer is it is it that hard?
23:04tpw_rulesso can the asahi installer be the first install of 12.3 on my computer or will there be signatures or sth missing?
23:05tpw_rules(also where is the new official installer link)
23:06Telvana has quit []
23:06tpw_rulesM1bn3mar[m]: i mean the one under the alx.sh domain
23:07M1bn3mar[m]tpw_rules: ah, well idk about that
23:07Dcow[m]1just wait for it
23:08M1bn3mar[m]it's under development -_-
23:08tpw_rulesyes i know lol
23:09tpw_rulesi thought it moved to a new link now that release is imminent
23:09tpw_rulesand wanted to update my docs with it
23:10tpw_rulesmaybe it wouldn't be dumb to mark those as (GUI) and (CLI)
23:10Telvana has joined #asahi
23:10Dcow[m]1Plasma/Core
23:10Dcow[m]1good enough
23:11marcantpw_rules: what do you mean by first install?
23:11M1bn3mar[m]so is arch now installable
23:11tpw_rulesmarcan: like my main macOS is 12.2. if i install a stub partition with 12.3 will it boot? or do i have to do apple's upgrade process to 12.3 first?
23:11marcanno, that won't work
23:11marcanyou need macOS 12.3
23:11zamadatix has joined #asahi
23:12tpw_rulesso apple's process does do some additional signaturey things
23:12marcanit'll refuse to run on 12.2 in non-expert mode, and I removed 12.1 from the compats from the Asahi Linux releases anyway so expert mode won't let you install thiose
23:12Dcow[m]1and it take about 30 mins to upgrade, you're out of time!
23:12marcanno, it's not about signatures
23:12tpw_rulesoh. well then what about when 12.4 comes?
23:12marcanwe do not have a process for upgrading system firmware
23:12marcanyou cannot run newer OSes than your system firmware
23:12tpw_rulesbut you can run older ones?
23:12tpw_rulesokay, that makes sense. thanks
23:13marcanif you had 12.3 system firmware already it would work installed from 12.2, except I deliberately gated that out because 12.3 gave us a working `bless` and I want people to go through that path
23:13tpw_rulesyes, i saw that. makes sense
23:13brentr123[m]Plasma like kde?
23:13* tpw_rulesgoes to kick off the 12.3 upgrade
23:13zamadatixHow do you go about swapping Fn so the behavior is Fn unpressed = Fn1-10, Fn pressed = media/control functions?
23:13LuigyLeon[m]time to upgrade
23:14marcanoptions hid-apple swap_fn_leftctrl=1
23:14Dcow[m]1what is default nvme flush now?
23:14Dcow[m]1I meant workaround to delay flushes
23:15j`ey1000 msec
23:15Dcow[m]1so it enabled by default?
23:17tpw_rulesbut only on your images right
23:17j`eyzamadatix: isnt that the default?
23:18kovj`ey, unless it changed in the last few days, default is media keys
23:18tpw_rulesj`ey: bah, i thought it would default to zero and you or your distro would have to enable it
23:19tpw_rulesi don't like it being on by default
23:19marcanhere we go: curl -L https://alx.sh/dev | sh
23:20marcantpw_rules: it is on so people test this codepath
23:20marcanin the future once we have proper panic handling it will remain on on laptops, and be off on desktops
23:20tpw_rulesmarcan: okay. not sure how it interacts with panics? you mean a hook into the driver to flush the disk on panic?
23:21marcanhaven't actually tested the first setup wizard yet, finishing the install now :)
23:21marcanwell, I did, but not on a fresh install
23:23marcanokay, didn't work
23:23Dcow[m]1lol, how to stop installation?)))
23:23j`eyso hid_apple.fnmode=2
23:29hizon has quit [Ping timeout: 480 seconds]
23:47marcanargh I'm dumb
23:48psykosesmort :3
23:54marcanI think it works...
23:57zamadatixHave I lost it or did the Asahi default install used to have DHCP enabled by default for Wi-Fi?
23:57marcanbuilding one more image...
23:58marcanzamadatix: nothing has changed on that front
23:58marcanthe plasma image comes with full networkmanager/everything, the wifi networks show up on the desktop
23:58zamadatixAlright I've just lost it then :). Works fine after I add the networkd file I just must have forgotten doing so before
…