marcan changed the topic of #asahi to: Asahi Linux: porting Linux to Apple Silicon macs | Not ready for end users / self contained install yet. Soon. | General project discussion | GitHub: https://alx.sh/g | Wiki: https://alx.sh/w | Topics: #asahi-dev #asahi-re #asahi-gpu #asahi-stream #asahi-offtopic | Keep things on topic | Logs: https://alx.sh/l/asahi
yuyichao has quit [Ping timeout: 480 seconds]
PaterTemporalis has quit [Ping timeout: 480 seconds]
yuyichao has joined #asahi
mrkajetanp has quit [Ping timeout: 480 seconds]
hizon has joined #asahi
<zv> I'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 ?
<zv> reboots always fix it.
chadmed has quit [Quit: Konversation terminated!]
chadmed has joined #asahi
creechy has quit [Ping timeout: 480 seconds]
creechy has joined #asahi
phiologe has quit [Ping timeout: 480 seconds]
creechy has quit [Ping timeout: 480 seconds]
kov has quit [Quit: Coyote finally caught me]
kov has joined #asahi
mrkajetanp has joined #asahi
creechy has joined #asahi
apg has joined #asahi
kreechy has joined #asahi
creechy has quit [Ping timeout: 480 seconds]
marvin24_ has joined #asahi
marvin24 has quit [Ping timeout: 480 seconds]
tweets_so_fresh_ has joined #asahi
Collin has joined #asahi
Collin has quit [Remote host closed the connection]
ihaveamac has quit [Quit: fail]
ihaveamac has joined #asahi
balrog_ has quit [Ping timeout: 480 seconds]
balrog has joined #asahi
kreechy has quit [Ping timeout: 480 seconds]
<Glanzmann> zv: 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?
kreechy has joined #asahi
CarlosCamacho[m]1 has joined #asahi
on^ has joined #asahi
kreechy has quit [Ping timeout: 480 seconds]
kreechy has joined #asahi
kreechy has quit [Remote host closed the connection]
eroux has joined #asahi
<Glanzmann> marcan: I updated all my devices to 12.3, ping me when there is something to test.
sheepgoose has joined #asahi
the_lanetly_052 has joined #asahi
<sven> could also be that the usb2 phy isn't brought up correctly fwiw
<sven> there's a register that has a bit for device vs host mode which we just don't change after m1n1
<sven> and two more registers or so we just don't set\
<sven> who knows what that does
sheepgoose has quit [Quit: Konversation terminated!]
the_lanetly_052 has quit [Ping timeout: 480 seconds]
oi_wtf has quit [Remote host closed the connection]
oi_wtf has joined #asahi
<Glanzmann> sven: Is that also the case for the usb-a ports on the mini?
<sven> no
<Glanzmann> zv: 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.
<Glanzmann> sven: 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.
<sven> no idea
the_lanetly_052 has joined #asahi
<Glanzmann> marcan / povik: With the lastest asahi branch, I no longer have boot hangs and power management failures with the debian kernel distro kernel config.
<Glanzmann> sven: I let you know once I have found out what I did wrong.
ciggi has quit [Read error: Connection reset by peer]
ciggi has joined #asahi
MajorBiscuit has joined #asahi
MajorBiscuit has quit []
MajorBiscuit has joined #asahi
pa_ has joined #asahi
zopieux has quit [Ping timeout: 480 seconds]
zopieux has joined #asahi
apg has quit [Quit: Leaving]
pa_ has quit [Quit: Page closed]
ciggi has quit [Ping timeout: 480 seconds]
chadmed has quit [Ping timeout: 480 seconds]
Sobek[m] has joined #asahi
ciggi has joined #asahi
chengsun_ has quit [Quit: Quit]
chengsun has joined #asahi
<zv> Glanzmann: 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.
<sven> usb-a will also give you usb 3 support already fwiw
<Glanzmann> zv / sven: So might be more stable and better speed. zv: Let us know how it turns out to be.
kameks has joined #asahi
ChaosPrincess has joined #asahi
Erus_Iluvatar has quit []
Erus_Iluvatar has joined #asahi
phiologe has joined #asahi
eroux has quit [Ping timeout: 480 seconds]
eroux has joined #asahi
XeR has quit [Remote host closed the connection]
XeR has joined #asahi
amarioguy has joined #asahi
rikkaa has joined #asahi
PaterTemporalis has joined #asahi
amarioguy has quit [Ping timeout: 480 seconds]
giskard has joined #asahi
choco has joined #asahi
choco has quit []
hizon has quit [Read error: Connection reset by peer]
<marcan> new installer is up: curl -L https://alx.sh/dev | sh
<marcan> lots of changes, resizing, OS sizing, colors, fixes, more logging, yada yada
<marcan> the OS package has not been updated, please consider this a test of the installer only
<marcan> it requires 12.3 on paper but in expert mode it'll let you run on 12.1 still
<j`ey> so 12.3 is required for the base macOS install no...
<marcan> but I really want people to try the new 12.3 mechanism
<j`ey> but the stub it installs is still 12.1
<marcan> right now the stub is still installed as 12.1
<marcan> yeah, that's just an installer_data thing
<marcan> let me fix that
<kloenk> what's new there in 12.3? missed that
<j`ey> kloenk: `bless` support for apple silicon
<_jannau_> command line startup disk selection without automatic restart
<kloenk> oh nice
<marcan> j`ey: fixed, 12.3 now
<marcan> (well, in expert mode it lets you choose)
<marcan> I'm *really* glad we can finally get rid of that boot picker nonsense, that was going to cause us endless headaches
rikkaa has quit [Remote host closed the connection]
rikkaa has joined #asahi
rikkaa has quit [Remote host closed the connection]
<_jannau_> marcan: the 12.3 ipsw is still missing
<marcan> how so?
<j`ey> in src/main.py
<_jannau_> I missed it in the all in one commit
<j`ey> oh, not it isn't
<j`ey> me too :)
<marcan> yeah, sorry, I gave up on that
<marcan> wasn't going to happen cleanly
<j`ey> just as long as it doesn't happen in linux.git, it's fine :P
<marcan> :p
<_jannau_> my mac studio is apparently already in the Netherlands, apple claims it will arrive at april 1st - 5th (pushed 2 week back)
<marcan> yeah, I got a delay email too, 30th at the latest...
<Glanzmann> More time for the release.
<maz> not got anything yet, but I'm not scheduled before mid-May anyway...
<marcan> Glanzmann: the release is not waiting for that
<Glanzmann> I 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. :-)
<_jannau_> no updates from Apple so far but got message from DHL that they received the shipment information with pickup in Eindhoven
<j`ey> no bring it upstream, it'll Just Work ;)
<Glanzmann> jannau: When I orded my macbook air, it was the same. And than it took 2 weeks or so until it was shipped.
<_jannau_> I've checked Apple's order status and that said april 1st - 5th
<Glanzmann> jannau: 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.
<kloenk> Slightly 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?
<marcan> no BootPolicy
<marcan> therefore no running your own anything
<kloenk> what I guessed :)
MajorBiscuit has quit [Ping timeout: 480 seconds]
<Glanzmann> marcan: In the installer, id I leave out the volume_id it will randomize it?
<marcan> yes
<_jannau_> I assumed apple would only order the pickup after the package is already there
<Glanzmann> jannau: For me it was either a very large chipment and they took 2 weeks to unload or they submitted it before.
<sven> i got my m1 pretty soon after DHL sent me the that initial shipment mail
<sven> and that was at least one week before the date claimed on Apple's website
<Glanzmann> sven: For me it was the opposite.
<sven> yeah, you just said that
<kettenis> the way apple ships things is pretty bizarre
<kettenis> my mini was shipped from Ireland, whereas the 14" macbook pro was handed off to UPS in china
<Sobek[m]> Could it be simply bizarre because of the insane amount of things they are shipping on launch / in the initial launch period ?
<Sobek[m]> Also could BTO vs rather stock configs explain some of it ?
<kettenis> almost certainly
<Sobek[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)
<Sobek[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 ?
<brentr123[m]> Over voltage?
<Sobek[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).
<Sobek[m]> It's not really bricking and more failure to boot / boot loop.
chadmed has joined #asahi
<marcan> that's not really a brick, since DFU works
<marcan> looks like just a dumb bug
hizon has joined #asahi
<marcan> and if you're wondering why nobody noticed: I bet it's because Mac Studio
<marcan> before hardware launches, Apple release a new release with new support *on the RC*
<marcan> that means all the other prior betas are incomplete and useless as far as catching these regressions go
<marcan> so all they have is their internal testing
<marcan> Apple's secrecy/surprise announcement stuff is directly at odds with quality, by definition
<marcan> several 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.
<marcan> (that was when they broke Mac Mini HDMI output in iBoot)
<marcan> (though apparently that one was intentional?)
<Sobek[m]> Apparently the bug occured also with the dev beta.
<marcan> unclear if it's really the same bug
<kov> yeah 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?
<marcan> kov: still not working and I think it's intentional
<marcan> DCP works fine so it's iBoot just not turning it on
<Sobek[m]> Is this iBoot 1 or 2 ?
<Sobek[m]> (Are they both updatable ?)
<marcan> both changed a lot
<marcan> unclear
<marcan> yes
yuyichao has quit [Ping timeout: 480 seconds]
<kov> marcan, why would they want that? working around issues with some screens?
<marcan> no idea
kameks has quit [Ping timeout: 480 seconds]
<mps_> if I enable speakers in dts they work but then jack (headphone output) doesn't work. is that expected (for now)?
yuyichao has joined #asahi
<Glanzmann> mps_: It is expected. Workaround: https://pbot.rmdir.de/zH-6y89iGSviq1PojRX_iA
<mps_> Glanzmann: I see, thanks (though looks line not proper 'fix')
<Glanzmann> mps_: povik wants to put jack detection and switch depending on if there is jack plugged in or not in the future.
<Glanzmann> mps_: Did you get your text console back?
<mps_> Glanzmann: not yet, didn't had time to further test needed drivers/options
hizon has quit [Ping timeout: 480 seconds]
kreechy has joined #asahi
kgarrington has joined #asahi
kgarrington has quit [Remote host closed the connection]
kgarrington has joined #asahi
kgarrington has quit [Remote host closed the connection]
kgarrington has joined #asahi
<mps_> 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`
kgarrington has quit [Remote host closed the connection]
<Glanzmann> mps_: That is normal. See my dmesg: https://pbot.rmdir.de/ZfLPWI5Wq9MB8JcdZXcDVA
<mps_> Glanzmann: ah
<mps_> but next line in my log is `simple-framebuffer: probe of be206c000.framebuffer failed with error -16`
<mps_> and in your log I see it later find it and set /dev/fb
<Glanzmann> new asahi branch debian kernel tested on the air: curl -sL tg.st/u/ksh
kreechy has quit [Ping timeout: 480 seconds]
kreechy has joined #asahi
<Glanzmann> povik: With the latest asahi branch I have the problem that I can only mute the jack or totally overblow it volume wise.
<Glanzmann> povik: Might it be possible that this because I once executed 'pacmd load-module module-alsa-sink device=hw:0,1'?
MajorBiscuit has joined #asahi
<Glanzmann> povik: However when I start pacmd and issue pacmd list-module, I can't see it: https://pbot.rmdir.de/IGFY96yh-oY1tpkKTsrnqQ
<povik> no, that's because of something i did in one of the drivers
<povik> i thought it might be a good idea but it's not it
<povik> the "Mixer Volume" knob is fixed at its maximum
<povik> and hidden from userspace...
<Glanzmann> povik: I already tried to play with alsamixer and pavucontrol but I only get blow my brain out or mute.
<Glanzmann> povik: Maybe put that know to 25% or 50% than it will be fine.
<povik> ah, so if you disable the speakers in DT you can turn down the volume at pulseaudio level
<povik> but if you enable speakers and do the load-module thing, you can't?
<Glanzmann> povik: This is with disabled spakers.
<povik> hm
<povik> the other day you posted you could turn it down
<povik> maybe it is because you ran load-module after all
<Glanzmann> povik: Do you know how I get rid of it?
<povik> try rebooting
<povik> don't know what could be different from when you could turn it down
<Glanzmann> Since i tried the speakers, I rebooted about 20 times.
<povik> ah so you are sure you haven't run load-module since last reboot
<Glanzmann> povik: This solved it for me: rm -rf .config/pulse/
<povik> ha
<Glanzmann> And reboot (don't know if the reboot was necessary).
<povik> anyway you can just remove the line i linked to have the alsamixer knob back
<tohatsu[m]> Debian installed on internal NVME is not persistent? It boots the same initrd.gz as it boots if installed on USB?
<Glanzmann> tohatsu[m]: It is persistent.
<tohatsu[m]> can i make it not persistent
<tohatsu[m]> ?
<Glanzmann> tohatsu[m]: Yes, you use the live cd.
<tohatsu[m]> and sync it with initrd.gz on usb
<Sobek[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)
<Glanzmann> tohatsu[m]: ALso that is possible with: https://pbot.rmdir.de/1c0vwV4diKo3Vna0JvX0Lg see also 'tail -15 /root/quickstart.txt' in the live system itself.
<tohatsu[m]> so i curl debian-live.tar to internal partition? and uboot will choose nvme if no usb connected?
<Glanzmann> tohatsu[m]: Almost. If you want that it boots automatically you need to replace msdos1 with gpt4 or whatever your esp partition is.
<Glanzmann> In the grub.cfg
<tohatsu[m]> linux (hd0,gpt4)/vmlinuz expert # like this?
<Glanzmann> tohatsu[m]: Yes, and don't forget the initrd as well.
<tohatsu[m]> how do i make fat volume out of Free space? diskutil doesn't show IDENTIFIER
<Glanzmann> tohatsu[m]: You need to run the asahi installer, it will create the esp partition.
<Glanzmann> tohatsu[m]: Can you paste the output of diskutil list to tg.st/p ?
<Glanzmann> tohatsu[m]: You already have an esp partition.
<tohatsu[m]> 512mb is not enough, i need 1GB+
<Glanzmann> So if you really want to do what you just said than you run the following commands: https://pbot.rmdir.de/RwW72h9onAMYiqdY7cwegQ
<Glanzmann> tohatsu[m]: Nope, it is enough. You need 217M.
<Glanzmann> of free space.
<tohatsu[m]> efi for booting purposes? initrd.gz is going to be on another volume?
<Glanzmann> tohatsu[m]: You can also leave it on the volume, of course at some point you will run out of space.
<Glanzmann> tohatsu[m]: Just to be clear, you want a live system and don't install Debian on the nvme?
<tohatsu[m]> Live not persistent debian on both NVME and USB, which i will sync sometime by copying initrd.gz
tomtastic has quit [Ping timeout: 480 seconds]
<marcan> asahi-base OS image has been updated, along with the installer (just bumps m1n1 to 1.0) and Arch packages
<marcan> hopefully this is actually usable now, the PCIe explosions should be gone
<Glanzmann> marcan: Will test it and report back.
<Dcow[m]1> marcan: great news. looks like you made pcie always on? how this affects the battery life?
<Dcow[m]1> are you still going to prepare plasma image today?
<marcan> pcie was already always on
<marcan> it was just getting momentarily turned off during boot
<marcan> and that was breaking things
<marcan> and yes, hopefully
<Dcow[m]1> gotcha, gonna wait plasma image to try again
<Dcow[m]1> thank you for the efforts!
on^ has quit [Remote host closed the connection]
<marcan> also, the CDN is the default mirror now, and I just set up the caching rules to be quite conservative
<_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
the_lanetly_052 has quit [Ping timeout: 480 seconds]
ciggi_ has joined #asahi
ciggi has quit [Ping timeout: 480 seconds]
<Glanzmann> marcan: 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?
<Glanzmann> I tested on my wifes air and it works. I like the new colors and sane defaults.
<firefox317> Glanzmann, 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
MajorBiscuit has quit [Ping timeout: 480 seconds]
<Glanzmann>  I see
<Glanzmann> So I configured wifi, is there a dhcp client installed?
<Glanzmann> dhcpcd
<firefox317> Glanzmann, probably better to use systemd-networkd instead of manaully starting the dhcpcd deamon yourself. You can configure systemd-networkd using: networkctl
<firefox317> not 100% sure tho
<milek7> I think you can do systemctl start dhcpcd
<Glanzmann> I already deleted it again. Just wanted to see what it looks like. root password is 'root'.
tomtastic has joined #asahi
amarioguy has joined #asahi
ChaosPrincess has quit [Quit: Page closed]
ChaosPrincess has joined #asahi
amarioguy has quit [Ping timeout: 480 seconds]
<mps_> with iwd you don't need dhcp client
<mps_> it has one inside it
<mps_> you just need some of external 'helpers' (openresolv or systemd-something) to set params
<firefox317> marcan, base image works great on j313!
<Glanzmann> mps_: I see.
<mps_> Glanzmann: man iwd.config and look for NameResolvingService option
<marcan> firefox317: yay!
<marcan> _jannau_: I was going to ask about that, I'll merge it via releng
<marcan> that ticks off another TODO :)
<kettenis> good I just fixed the OpenBSD installer to not nuke the ESP ;)
<Sobek[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 ?)
<Sobek[m]> (Or point me at the right documentatin page)
<j`ey> Sobek[m]: U-boot provides UEFI
<Sobek[m]> Thanks !!! Makes more sense
m6wiq has joined #asahi
<Sobek[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 !!!!
<marcan> _jannau_: u-boot updated in the repo, pacman -Syu should pull it in and do All The Magic
<marcan> Sobek[m]: no secure boot yet but that's the plan (hence the rust for that bit)
<Sobek[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) ?)
<j`ey> nothing 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
<marcan> we've been trying to catch all the ones that will cause us pain down the line early :-)
<marcan> chainloading actually got bumped to something to get done for the first release rather recently, and I'm glad it did
<marcan> j`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
<j`ey> neat!
<marcan> also, 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
<j`ey> marcan: that change you made to use the kernel DTBs.. looks like it assumes only one kernel has been installed?
<marcan> that is how things normally work on arch, yes
<marcan> I'm not saying all distros will want to do it this way :-)
<j`ey> oh ok, been a while since I used arch
<marcan> it looks for DTBS=/lib/modules/*-ARCH/dtbs/*
<marcan> if you have non-arch kernels they will be ignored
<marcan> if you somehow manage to install multiple arch kernels, then yeah, you get to keep the pieces
<marcan> but I don't think that's normally a thing
<Sobek[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 😅)
<marcan> yeah, the arch approach is "just keep the latest kernel only!"
<marcan> which is... sub-optimal when regressions happen
<marcan> but hey, this is why I run gentoo on my servers, not arch :-)
<j`ey> yes :)
<jannau> marcan: 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
<marcan> jannau: of course
<marcan> I just haven't updated the images yet
<marcan> will happen when the plasma image is pushed :)
<marcan> the images are already pulling from the repo, nothing is left outdated there
<marcan> it just needs to be regenerated
<marcan> uboot-asahi and m1n1 updated (removed the hook, that's now taken care of by asahi-scripts)
zamadatix has joined #asahi
zamadatix has quit []
<tohatsu[m]> any way to increase EFI 512mb to 1+GB without recreating it?
<tohatsu[m]> my initrd.gz does not fit
<marcan> not sure if diskutil can resize FAT32, maybe?
<mps_> does asahi kernel for Arch use initram
<marcan> yes
<marcan> but not in the ESP
<marcan> tohatsu[m]: ESPs are usually 100-500MB or so, so you might want to consider whether whatever you're doing is sane
<mps_> marcan: in /boot dir?
<marcan> sounds like you'd run into this on many other systems
<marcan> mps_: yes
<mps_> is there binary pkg somewhere or to pull complete installer and extract
<marcan> binary pkg for what, the initramfs?
<mps_> no, complete kernel + initramfs
<marcan> the initramfs is generated by mkinitcpio
<kettenis> mps_: look at the script
<marcan> the kernel is a package like any other
<mps_> and on install it creates initramfs?
<marcan> yes
<mps_> ok, thanks
bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<mps_> want to see will I got text console with it
bisko has joined #asahi
<Dcow[m]1> what is the proper way to uninstall asahi linux?)
<marcan> delete the partitions
<j`ey> Dcow[m]1: it's impossible, you can never leave!
<sven> :D
<marcan> there is a tools/wipe-linux.sh which will indiscriminately wipe everything, don't run it unless you know what you're doing
<marcan> in the installer repo
<sven> j`ey: you’re not supposed to tell anyone that!
<j`ey> sven: ;-)
<Dcow[m]1> Yeah, I saw that. My question was more like "is it enough to delete partitions or not?"
<marcan> it is enough
<marcan> well, you can also resize macos back to full size of course
<Dcow[m]1> not need
<marcan> garbage boot policies will also be left behind, that script also removes them
<ChaosPrincess> maybe also clean up boot policies, no?
<marcan> those don't break anything but they will slow down boot policy actions as they pile up
<marcan> so you don't want too many
<Dcow[m]1> >garbage boot policies will also be left behind, that script also removes them
<Dcow[m]1> that the answer I wanted
<Dcow[m]1> * > garbage boot
<Dcow[m]1> thanks!
<Glanzmann> marcan: Can the installer already update the stub partition, or do I have to delete it and recreate it?
<marcan> there is no update functionality yet
<Glanzmann> I see, I'm testing currently with Debian and doing a recording.
<marcan> hopefully people won't have to do that for a while
<Glanzmann> marcan: I thought about the early adopters.
<j`ey> but just erasing the stub partition with diskutil, and then re-running the installer works right? was planning on updating to 12.3 that way
<mps_> hmm, no text console even with Arch kernel, strange
<kettenis> j`ey: you'll end up with another ESP that way
<j`ey> kettenis: I can pick the 'tethered' boot option, to not get the ESP
<j`ey> and then re-kmutil
<j`ey> or just stop step2 from doin that
<Glanzmann> marcan: I installed arch on my wifes air and I had console output.
<Glanzmann> j`ey: Yes, that what you have to do and recapture the firmware.
<Glanzmann> j`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.
<j`ey> theere's no rush for 12.3, so Ill just do it Later(tm)
<bluetail[m]> I talked with some colleagues
<kettenis> j'ey: not sure if you end up with a 1st stage m1n1 that loads the right 2nd stage m1n1+u-boot+dtbs that way
<bluetail[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
<bluetail[m]> There was even a test-case, where some colors where always mismatched... This is in regards to color measured with a pixel grabber
<tpw_rules> wuh? apple makes a big deal about color and HDR and stuff
<j`ey> kettenis: oh hm, yeah, I can fudge it, but it probably does need more work for a proper updater
<tpw_rules> i mean the macbook pros have 4x the colors
<j`ey> tpw_rules: yeah I find that pretty unlikely
<tpw_rules> or well 64x across all the channels
<bluetail[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.
<bluetail[m]> You can even use the same monitor and the same color profile
<bluetail[m]> You can measure the pixel itsel
<bluetail[m]> s/itsel/itself/
<tpw_rules> apple has slightly different interpretations
<bluetail[m]> it will be different on mac
<tpw_rules> iirc
<tpw_rules> yeah, cause apple applies color profiles
<j`ey> you can do that experiment the other way around ;)
<bluetail[m]> You cant get that sorted with a colorimeter
<j`ey> start from macOS and say it looks different on windows
<bluetail[m]> :D
<bluetail[m]> but thats not where the color measuring software is used....
<tpw_rules> i 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
<Glanzmann> I updated https://alx.sh/w/Debian and https://tg.st/u/debian_asahi_installer.mp4 for the new Debian. marcan did a great job.
<bluetail[m]> When you measure with anything like that on macos
<bluetail[m]> for instance the color picker
<bluetail[m]> you will be off
<bluetail[m]> if you measure on windows, it will find a different value
<bluetail[m]> but thats only for some colors
<bluetail[m]> not for all
<kettenis> this is waaay offtopic
<bluetail[m]> (sorry)
<bluetail[m]> but this shouldnt be the case on linux :D
<bluetail[m]> ... right?
<kettenis> I don't think anybody in their right mind expects linux output to be properly color calibrated ;)
<Glanzmann> kettenis: I'm happy that we have display output again.
<bluetail[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?
<j`ey> bluetail[m]: there was a while where mini didnt have output on linux
<bluetail[m]> oh :|
<Glanzmann> j`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.
<Glanzmann> I deleted the old stub and esp partition from Linux.
<Glanzmann> marcan / sven: I just updated my stub on the macbook air to 12.3 and lost usb.
<Glanzmann> Wait maybe it is just the outdated dtb on the '2' installer.
<Glanzmann> marcan / sven: Yes, that was it.
<Glanzmann> USB is back.
<Glanzmann> j`ey: So also evacuate and put back the 'm1n1/boot.bin' if that is a thing for you.
bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
bisko has joined #asahi
<Glanzmann> sven / marcan: Maybe I have problem anyway.
<Glanzmann> But I don't see the video grabber or the Jabra Headset that I have connected.
<sven> dwc3 still doesn’t probe for you
<Glanzmann> Both were there before I updated the stub version to 12.3
<Glanzmann> sven: On the distro kernel, no.
<sven> it’s not the stub
<Glanzmann> sven: On the striped down asahi config tha I used forever it does.
<sven> its definitely a wrong config
<Glanzmann> sven: The same kernel worked before. The installer video was recorded with this.
<sven> I’m willing to bet money it’s a missing config option
<sven> I don’t think so
<Glanzmann> using a jabra headset and a video grabber.
jelly has quit []
<sven> show me your config
<sven> and if this a config problem *again* maybe it’s time to stop messing with it
<bluetail[m]> offtopic: Killed 3 jabra headsets within 10 months. Always: Control unit broke, headset still intact - could be used with a USB soundcard.
<Glanzmann> sven: 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
bisko has quit []
<sven> 🤨
<sven> can I have that as a plaintext file please?
bisko has joined #asahi
<tohatsu[m]> which commands remove 2.5G stub and EFI partitions ?
<Glanzmann> That is /proc/config.gz
<Glanzmann> tohatsu[m]: From macos: https://pbot.rmdir.de/c4JQgEKHEwu2tWZlP5ASTw From Linux parted /dev/nvme0n1<RETURN>print<RETURN>rm n<RETURN>
<sven> okay, I’m confused now. Is this problem different from the one yesterday where dwc didn’t probe at all?
<tohatsu[m]> Glanzmann: thanx, worked like a charm
<Glanzmann> sven: Yes, that is a different config. But I'm happy to send it to you, too.
bisko has quit []
<Glanzmann> sven: Yes, it is different.
<sven> :/
<sven> let’s start with the one from yesterday
<Glanzmann> sven: With the other kernel config (where it is probably a config problem or race) lsusb does not show any devices.
<sven> can I have the config you used there?
<Glanzmann> One 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)
<sven> please fix your Webserver, it sends the wrong content type and I can’t open this on my mobile phone
<Glanzmann> sven: Okay, I fix that.
<Glanzmann> sven: This should open on your phone: https://pbot.rmdir.de/5V8L2dpC6jAqO75-1CVhLg
<sven> # CONFIG_TYPEC_TPS6598X is not set
<sven> that’s your issue there
bisko has joined #asahi
<jannau> and it's a module in the current config
<Glanzmann> jannau / j`ey: I fix that and try it.
<jannau> not sure if that's the problem but it's something to start testing
<Glanzmann> Compiling.
jelly has joined #asahi
<sven> tps6598x: probe of 0-003f failed with error -61
axenntio has joined #asahi
<sven> that’s also not good, but I can’t check what -61 is here
<jannau> ENODATA
axenntio has quit []
kreechy has quit [Ping timeout: 480 seconds]
<Glanzmann> sven / 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.)
<Glanzmann> here is the dmesg from the mini: https://pbot.rmdir.de/_Ftzjzde_SXyDYgT2Vn2XQ
<sven> now that sounds like an actual issue now
<sven> it looks like there’s something wrong with i2c on that air
bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
bisko has joined #asahi
<Glanzmann> sven: 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.
<sven> uh, and that actually fixes the issue?
<Glanzmann> sven: 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.
<Glanzmann> sven: usb-c did not give me trouble on the air and I used the air a lot on Linux.
bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
bisko has joined #asahi
<Glanzmann> sven: 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
<Glanzmann> I'll reboot a few more times.
<j`ey> thats a confusing sentence, but I think it means you were using an older dtb
kreechy has joined #asahi
<Glanzmann> j`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.
<marcan> heh, I installed wayland and xorg, and this defaulted to wayland... and I'm already running into problems with scaling
<marcan> looks like good old xorg it is for now
<Glanzmann> usb 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.
<j`ey> Glanzmann: weird
<Glanzmann> sven / 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.
<Glanzmann> marcan: Great job on the new installer.
<marcan> btw, I just built a plasma image and everything is working on the first try :-) (modulo the wayland default)
<marcan> just need to add a few tweaks and Calamares and that's about it
<Glanzmann> j`ey: I tried 'reboot' and 'halt -p' about 10 times and I can't reproduce the issue.
<Glanzmann> marcan: Btw. your new installer also worked on first try (that was the recording) with Debian.
<marcan> well, it doesn't really care about what distro you install, it's just a different image
<marcan> it'd be weird if it worked for one and not the other
<j`ey> marcan: nice, hopefully not too long left until its done!
<marcan> audio jack worked out of the box with pipewire, although it had a hiccup and I had to poke the output mode in pavucontrol
<marcan> (this is on an MBA)
<j`ey> I tried wayland+sway, worked well with 1x and 2x scaling
<marcan> j`ey: 3 more hours left in UTC to call it today so... :)
<marcan> yeah, but 1.5x scaling is ~ideal for these machines
<povik> output mode?
<marcan> the profile
<j`ey> marcan: yeah 2x was a little big :P
<marcan> USB ports work on this MBA
<marcan> looks like pretty much everything works, so I guess just the firstrun wizard now
<marcan> which is already mostly there
<j`ey> marcan: why dont you try get a GPU driver done too, after all you do have 3 hours still
<j`ey> :P
<tpw_rules> did usb-a in u-boot get fixed?
<kettenis> not yet
bisko has quit [Read error: Connection reset by peer]
<Glanzmann> tpw_rules: I fixed it: https://tg.st/u/IMG_20220317_220136185.jpg you want the high speed ports for usb sticks anyway.
<tpw_rules> fixed what?
<tpw_rules> i mean yeah i've used a usb a to c adapter too
<tpw_rules> but i wanted to know if i could remove that note from the guide
<Glanzmann> tpw_rules: Just a silly joke, I shut up for today.
<marcan> povik: weird, I rebooted and got only left channel
<marcan> maybe it's flaky?
bisko has joined #asahi
<marcan> and now nothing, yeah
<marcan> another reboot and stereo works
<Glanzmann> sven / 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.
* povik thinking
<povik> well there was the i2c breakage i didn't get to the bottom of
<povik> just haven't seen that in a while
m6wiq has quit []
<marcan> lol, the apple jis keyboard layout has the eisu and kana keys swapped
<marcan> *patches the xkb stuff again*
<marcan> really, nobody has been taking care of these layouts have they :/
<ar> well, between 2008-ish and recently, their laptops were just generic x86 machines if you didn't want to put up with macos :/
<sven> iirc some of iMacs were decent-ish even for running Linux
<marcan> ar: the keyboards were still like these
<mofux[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?
<opticron> marcan, it was just as bad 5 years ago when I was running Linux bare metal on the chromebook pixel
<marcan> which means these keys have been backwards for all japanese keyboard users in alu keyboards since forever
<marcan> unless apple swapped them, which I highly doubt
<opticron> it was a pain in the ass to manage keyboard configs
<opticron> so yeah, sounds like no one has even looked at it in forever
<Glanzmann> Debian 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
<marcan> alright, time to put in a quick hack for keyboard layouts in m1n1...
<opticron> Glanzmann, comes up on a m1m 14" mbp
<Glanzmann> opticron: Thanks for testing.
<opticron> and I just realized that the usb-c/usb-a adapters that google provides with pixels are usb2-only
eroux has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<sven> good thing our usb-c ports are usb2-only right now as well ;)
<j`ey> marcan: huh, keyboard layouts in m1n1?
<j`ey> oh, just saw the commit, more ADT->FDT forwarding
Telvana has quit []
gladiac has quit [Quit: Ping timeout (120 seconds)]
gladiac has joined #asahi
<M1bn3mar[m]> Hi is it possible to install gentoo using this or is it a rabbit hole; btw i don't mind a learning curve.
giskard has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
<j`ey> M1bn3mar[m]: it's possible yes, chadmed put sme stuff here https://github.com/chadmed/asahi-gentoosupport
<j`ey> I have no idea how usuable that is, or what it actually contains
<M1bn3mar[m]> j`ey: well it looks way too easy which usually means too good to be true, thanks though
Telvana has joined #asahi
<M1bn3mar[m]> install.sh: move scripts/post-install.sh
<M1bn3mar[m]> post-install.sh into being the One True Install.
<M1bn3mar[m]> the scope of this project has changed, so we move
<M1bn3mar[m]> * chadmed/gentoo-support install.sh:
<M1bn3mar[m]> * chadmed/gentoo-support... (full message at https://matrix.org/_matrix/media/r0/download/matrix.org/naEGQmTfLFIYLQsPHhKeUYoo)
<M1bn3mar[m]> * chadmed/gentoo-support... (full message at https://matrix.org/_matrix/media/r0/download/matrix.org/oJZTdAvztwPVkeLJHmOjEfsZ)
<M1bn3mar[m]> * chadmed/gentoo-support... (full message at https://matrix.org/_matrix/media/r0/download/matrix.org/DNJzXfdHwkvKxHNSxYzhvIMv)
<j`ey> M1bn3mar[m]: dont edit stuff on matrix.. it kinda spams irc
m6wiq has joined #asahi
<M1bn3mar[m]> ok, what now
m6wiq has quit [Remote host closed the connection]
<M1bn3mar[m]> what is One True Install
<j`ey> M1bn3mar[m]: I think thats just chadmed being silly
hizon has joined #asahi
<M1bn3mar[m]> j`ey: u mean like he didn't even make a script in the first place?
<j`ey> I guess they were planning to have a bunch of scripts and then just decided to have one
<marcan> building plasma image...
<marcan> will this work?
<marcan> (with the setup wizard)
<M1bn3mar[m]> ok, could i just be the installer is it is it that hard?
<tpw_rules> so can the asahi installer be the first install of 12.3 on my computer or will there be signatures or sth missing?
<tpw_rules> (also where is the new official installer link)
Telvana has quit []
<tpw_rules> M1bn3mar[m]: i mean the one under the alx.sh domain
<M1bn3mar[m]> tpw_rules: ah, well idk about that
<Dcow[m]1> just wait for it
<M1bn3mar[m]> it's under development -_-
<tpw_rules> yes i know lol
<tpw_rules> i thought it moved to a new link now that release is imminent
<tpw_rules> and wanted to update my docs with it
<M1bn3mar[m]> oh sorry
<tpw_rules> maybe it wouldn't be dumb to mark those as (GUI) and (CLI)
Telvana has joined #asahi
<Dcow[m]1> Plasma/Core
<Dcow[m]1> good enough
<marcan> tpw_rules: what do you mean by first install?
<M1bn3mar[m]> so is arch now installable
<tpw_rules> marcan: 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?
<marcan> no, that won't work
<marcan> you need macOS 12.3
zamadatix has joined #asahi
<tpw_rules> so apple's process does do some additional signaturey things
<marcan> it'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
<marcan> *those
<Dcow[m]1> and it take about 30 mins to upgrade, you're out of time!
<marcan> no, it's not about signatures
<tpw_rules> oh. well then what about when 12.4 comes?
<marcan> we do not have a process for upgrading system firmware
<marcan> you cannot run newer OSes than your system firmware
<tpw_rules> but you can run older ones?
<marcan> yes
<tpw_rules> okay, that makes sense. thanks
<marcan> if 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
<tpw_rules> yes, i saw that. makes sense
<brentr123[m]> Plasma like kde?
* tpw_rules goes to kick off the 12.3 upgrade
<zamadatix> How do you go about swapping Fn so the behavior is Fn unpressed = Fn1-10, Fn pressed = media/control functions?
<LuigyLeon[m]> same
<LuigyLeon[m]> time to upgrade
<marcan> options hid-apple swap_fn_leftctrl=1
<Dcow[m]1> what is default nvme flush now?
<Dcow[m]1> I meant workaround to delay flushes
<j`ey> 1000 msec
<Dcow[m]1> so it enabled by default?
<j`ey> yeah
<Dcow[m]1> cool
<tpw_rules> but only on your images right
<j`ey> zamadatix: isnt that the default?
<kov> j`ey, unless it changed in the last few days, default is media keys
<tpw_rules> j`ey: bah, i thought it would default to zero and you or your distro would have to enable it
<tpw_rules> i don't like it being on by default
<marcan> here we go: curl -L https://alx.sh/dev | sh
<marcan> tpw_rules: it is on so people test this codepath
<marcan> in the future once we have proper panic handling it will remain on on laptops, and be off on desktops
<tpw_rules> marcan: okay. not sure how it interacts with panics? you mean a hook into the driver to flush the disk on panic?
<marcan> yes
<marcan> haven't actually tested the first setup wizard yet, finishing the install now :)
<marcan> well, I did, but not on a fresh install
<marcan> okay, didn't work
<Dcow[m]1> lol, how to stop installation?)))
<j`ey> so hid_apple.fnmode=2
hizon has quit [Ping timeout: 480 seconds]
<marcan> argh I'm dumb
<psykose> smort :3
<j`ey> woops
<marcan> I think it works...
<zamadatix> Have I lost it or did the Asahi default install used to have DHCP enabled by default for Wi-Fi?
<marcan> building one more image...
<marcan> zamadatix: nothing has changed on that front
<marcan> the plasma image comes with full networkmanager/everything, the wifi networks show up on the desktop
<zamadatix> Alright I've just lost it then :). Works fine after I add the networkd file I just must have forgotten doing so before