#
…

2021-12-22

00:32Redecorating[m]marcan: on bcm4364b3 otp data doesn't seem to be in the first 0x800 words with base 0: https://gist.github.com/Redecorating/d65eef7286babe63d08334f2d82c6ce9
00:32Redecorating[m]could the otp data be stored on a different core?
00:38crabbedhaloablut has joined #asahi
00:40kit_ty_kate has quit [Quit: WeeChat 2.9]
00:41kit_ty_kate has joined #asahi
00:41loki_val has quit [Ping timeout: 480 seconds]
00:51chadmed has joined #asahi
01:03amwGlanzmann: I'm using X11 + fluxbox - touch pad not working on my asahi linux build
01:05yuyichao_ has joined #asahi
01:06chadmed has quit [Quit: Konversation terminated!]
01:07chadmed has joined #asahi
01:12amwGlanzmann: I'm using Debian bullseye (stable) so many of your packages are not found for me e.g. gcc-11 (only have gcc-9 and -10)
01:18chadmed has quit [Quit: Konversation terminated!]
01:25chadmed has joined #asahi
01:37boardwalk has quit [Quit: The Lounge - https://thelounge.chat]
01:47boardwalk has joined #asahi
02:22amwMy trackpad is found by the driver and appears in the X11 log but it isn't used as input - see Xlog here https://paste.debian.net/1224365/
02:23amwMy system is debian bullseye - I believe I have every xorg libinput driver?
02:36darkapex4 has joined #asahi
02:41darkapex3 has quit [Ping timeout: 480 seconds]
02:50amwOk - found the answer for debian have to remove xserver-xorg-input-synaptics - it silently doesn't work
02:51amwYou need the newer xserver-xorg-input-libinput package as per https://unix.stackexchange.com/questions/337008/activate-tap-to-click-on-touchpad
03:20chadmeddoes debian not have xorg-libinput as a dependency for xorg yet?
03:20chadmedehh makes sense i guess, their whole schtick is stability uber alles
03:47marcanRedecorating[m]: weird, thanks for checking
03:47marcanlet's wait until I try the T2 machine and see if I run into the same issue
03:52phiologe has joined #asahi
03:55jmr2 has joined #asahi
03:58jmr2chadmed: why don't you check before making such an assumption? https://packages.debian.org/stable/xserver-xorg That SO discussion is 5 years old.
03:58jmr2 has quit []
04:02chadmedi didnt make an assumption, i asked a question. a question by which i meant no offence. interesting that amw needed to manually remove the synaptics package and install libinput instead if its a dependency in the debian xorg input metapackage
04:24marvin24_ has joined #asahi
04:28marvin24 has quit [Ping timeout: 480 seconds]
06:04off^ has quit [Ping timeout: 480 seconds]
06:04Glanzmann has joined #asahi
06:05Glanzmannamw: Glad that you found that, I add it under tripwires in my text document.
06:08Glanzmannmarcan[m]: Wifi is stable on the mini. I ran https://tg.st/u/wifitest.sh for approx 8 hours. No dmesg output, transfer logs are consistent: https://tg.st/u/wifi.log.gz (this was with 2 GHz). As soon as I find out how to use 5 GHZ, I will try that as well.
06:11Glanzmannamw: I'll rewrite the guide to use stable, since there is probably no reason to use testing and you can always ugprade if you need it easily.
06:13Glanzmannamw: I always run echo 'APT::Install-Recommends "false";' > /etc/apt/apt.conf.d/06norecommends # first. This is probably why I did not had the synaptics tocuh pad driver to beginn with.
07:34zimsneexh has quit [Quit: Leaving.]
07:46Major_Biscuit has joined #asahi
07:47Major_Biscuit has quit []
07:47MajorBiscuit has joined #asahi
07:51rkjnsn[m]marcan, are you still looking for folks to test the brcmfmac-do-not-release-d11-resets.patch on other hardware?
07:52rkjnsn[m]Assuming I applied the patch properly (relatively new to NixOS, but it did build a new kernel when I added the patch to my config), I see no change in behavior versus without that patch.
07:54rkjnsn[m]I do see "AXI timeout; APB Bridge 0" coming out of hibernate, but it looks like that happens without the patch, too, so not a regression.
07:56rkjnsn[m]This is a 2015 MBP (Firmware: BCM43602/1 wl0: Nov 10 2015 06:38:10 version 7.35.177.61 (r598657) FWID 01-ea662a8)
08:13sailorek1234 has joined #asahi
08:44mpsxorg synaptics driver works for me on alpine, I used it some time because touchpad is too sensitive and can't set touch high/low threshold with libinput driver
08:48GlanzmannI'll test it myself later.
09:41rkjnsn[m]FWIW, adding the "Pass PMK in binary" patch also works for me.
09:43joske has joined #asahi
09:47joskehello, been following for a while now and today decided to take the plunge and install asahi
09:47joskeI've followed the steps by glanzmann, was able to resize the macOS partition and run the installer
09:47joskehowever, when in 1TR, when running step2.sh it fails
09:48joskeBoot objects update failed
09:48joskecan provide screenshot
09:48j`eymacOS 12.1?
09:49j`eyyou need to edit the step2.sh script
09:49j`eyhttps://github.com/AsahiLinux/m1n1#usage and actually you have to build m1n1 yourself
09:50j`eyto get the raw m1n1 image
09:50joskeI've built m1n1 already
09:51j`eyok, if you have the m1n1.bin, you need to run the kmutil command shown there ^
09:52joskeok thx, trying
09:54joskethe step2.sh is read only, so I guess I only need to run the kmutil command manually?
09:56joskeand m1m1.bin from m1m1/build folder?
09:58joskenow kmutil says you must move to medium security (using startup disk)
10:09joskeI've set the startup disk to Linux and then got back into 1TR, and now step2.sh works
10:10joskeand m1n1 has booted
10:10j`eyjoske: step2.sh.. un changed worked or?
10:12j`eyjoske: in the installer, what macOS stub version did you pick?
10:12joskethe default one 12.01 IIRC
10:13FireFox317j`ey, there is no 12.1 IPSW in the asahi-installer yet
10:13j`eyfirefox317: ok
10:15j`eyjoske: next step is kernel + rootfs or initramfs (or both!)
10:15FireFox317I guess it kinda makes sense it works then, because you will go into the 1TR of the OS stub you just installed, instead of using the systemwide one
10:18josketrying to run m1n1 shell but python says No module named 'serial.tools'
10:18joskeI'm on manjaro, installed serial via pip3 install serial
10:20chengsunpip3 install serial.tools
10:20FireFox317joske, https://github.com/AsahiLinux/docs/wiki/Developer-Quickstart#debian-build-dependencies tells you to install ´pip install pyserial construct serial.tool´
10:21joskeI installed all those, but it still says serial.tools not found
10:22joske[jos@silence ~]$ pip3 install pyserial serial serial.tool construct
10:22joskeDefaulting to user installation because normal site-packages is not writeable
10:22joskeRequirement already satisfied: serial.tool in /usr/lib/python3.9/site-packages (0.0.1)
10:22joskeRequirement already satisfied: serial in ./.local/lib/python3.9/site-packages (0.0.97)
10:22joskeRequirement already satisfied: pyserial in /usr/lib/python3.9/site-packages (3.5)
10:22Dcow has quit [Read error: Connection reset by peer]
10:22joskeRequirement already satisfied: construct in ./.local/lib/python3.9/site-packages (2.10.67)
10:22joskeRequirement already satisfied: pyyaml>=3.13 in ./.local/lib/python3.9/site-packages (from serial) (6.0)
10:22Dcow__ has joined #asahi
10:22joskeRequirement already satisfied: iso8601>=0.1.12 in ./.local/lib/python3.9/site-packages (from serial) (1.0.2)
10:22joskeRequirement already satisfied: future>=0.17.1 in ./.local/lib/python3.9/site-packages (from serial) (0.18.2)
10:23FireFox317joske, well maybe chengsun suggestions is true and you need serial.tools instead
10:23joskethat one doesn't exist
10:23joske[jos@silence ~]$ pip3 install serial.tools
10:23joskeERROR: Could not find a version that satisfies the requirement serial.tools
10:23joskeERROR: No matching distribution found for serial.tools
10:23joskeDefaulting to user installation because normal site-packages is not writeable
10:24FireFox317joske, please use some pastebin next time to show these messages. Im not sure what you are missing here
10:25joskesorry not very used to IRC
10:25chengsunno, serial.tools only provides a binary iirc
10:25chengsunthe "serial" package is not what you want, that's completely unrelated
10:25chengsunpyserial provides the "serial" library that you want, and i'm going to guess there's some naming conflict caused by you also installing serial
10:25FireFox317joske, also make sure you are actually using the correct python version, maybe you have to call python3 or whatever
10:26chengsunthe wiki instructions don't ask you to pip install serial
10:27chengsunso try uninstalling that
10:27joskeyes I saw on stackoverflow
10:28joskeYEs! m1n1 prompt :-D
10:28j`eyjoske: ^_^
10:32joskenow trying to follow the asahi.txt again, trying to chainload m1n1.macho that I built
10:33joskebut it gives uart timeout
10:36joskeah I think the notes are wrong
10:36joskeshould be M1N1DEVICE=/dev/ttyACM0
10:39FireFox317joske, sometimes it gets assigned to ttyACM0 and sometimes to ttyACM1, there is a way in udev to make it consistent tho
10:41joskeI've got penguins on my screen!!!1!!
10:42joskebut it fails to mount root as I forgot to create the linux partition :-S
11:10Major_Biscuit has joined #asahi
11:11MajorBiscuit has quit [Ping timeout: 480 seconds]
11:12caef^ has joined #asahi
11:16Glanzmannsven: Should I try your NVMe branch or is it not ready for junior developers? :-)
11:16svenYeah, that branch should be fine to test
11:16svenit’ll
11:17svenit will still have that sync/flush issue
11:41Glanzmannsven: No issue, I'll give it a try. Marcan also mentioned on -dev that he will merge it soon.
11:41Glanzmannjoske: If you managed to boot from the usb stick, you can also create the linux partition with parted. That is what I did the last time.
11:42GlanzmannI really have to write a howto and record a video how to install Debian Linux in 10 minutes on a m1 machine.
11:43rose_ has joined #asahi
11:49joskeGlanzmann, boot from USB stick?
11:49joskeI did not read/understand that from your notes
11:52amwGlanzmann: Thanks for updating your notes. Does the firmware grabging step work on 11.x MacOS ?
11:52amwThanks my next step - for tomorrow though
11:52Glanzmannamw: I only tried on 12.1 but I send you a message
11:53amwI guess I can tested it for others.... - thanks again.
11:54marcanRedecorating[m]: I have a 4364b3 too on this T2 I'm borrowing, so let's see what I can find
11:55marcanbuilding linux now...
11:55marcan(holy shit these intel machines really are terribad at power consumption... even just idle with an external screen the fans are already annoyingly loud, since I guess that clocks up the GPU?)
11:57marcanamw: it should work on any version
11:57Glanzmannjoske: It says in the notes that you should extract the rootfs to a usb stick. Than on your first boot you have to say root=/dev/sda1 or something.
11:57GlanzmannBut I'll write a better howto and do a recording
11:58amwmarcan: Excellent!
12:01Glanzmannjoske: Once you boot from the usb stick you can than use debootstrap. But I'll modify the howto to be simpler and also build a rootfs that you can just dd on your partition. Than you need only one machine and it will be easy to install Linux in 10 minutes or so.
12:02joskeGlanzmann, maybe I'm too stupid, but it was not clear to me, I only see root=/dev/nvme... in the notes
12:05rose_hey, i've just been handed this m1 mini which apparently has u-boot and m1n1 on it and been asked to get macos back. i booted into 1tr and clicked the big "install macos big sur" button but once it finished and rebooted it told me "custom kernel failed to boot". apparently u-boot was installed with this guide:
12:05rose_https://wiki.netbsd.org/ports/evbarm/apple/ which seems to use kmutil to configure u-boot instead of the macos kernel - does anyone know how i can fix this and boot macos again?
12:06Glanzmannjoske: I did not mention it explicitly.
12:07Glanzmannjoske: So the idea in the howto is to get a usb stick, partition it, create an ext4, put the rootfs on it.
12:07dottedmagrose_: Another option to consider: connect to another Mac and use Apple Configurator 2 to wipe it.
12:08GlanzmannBoot once from the usb stick, create an ext4 on the nvme partition and copy rootfs over or run debootstrap.
12:08GlanzmannI'll do this evening a 10 minute quickstart guide for Debian.
12:08GlanzmannAnd do a video recording of it how to do it.
12:09rose_thanks for the suggestions. i tried bputil -n  just now and it "failed to create local policy" which might be something to do with me cancelling the second attempt at reinstalling macos :P
12:10rose_so i'll let it run all the way through this time and try again, and if that doesn't work i'll get the other mac and try the configurator thing
12:16Redecorating[m]marcan: on t2macs you need patches to applesmc + a patched version of mbpfan to get fan control. It makes it quieter, but I doubt it'll be as quiet as m1 macs. There's no harm in not getting fan control, but if you want it, see patches 3001-3006 here https://github.com/aunali1/linux-mbp-arch and https://wiki.t2linux.org/guides/fan/
12:16FireFox317rose_, there is also idevicerestore which let you restore it from linux instead
12:16joskeGlanzmann, OMG booted manjaro ARM!! touchpad doesn't seem to work though
12:18joskeneither does keyboard
12:20Glanzmannjoske: It might be the kernel.
12:21GlanzmannMaybe try the asahi branch instead of the wifi branch.
12:21Glanzmannjoske: Which m1 machine do you have?
12:23marcanRedecorating[m]: the fans are automatically scaling properly, and it does this on macOS too
12:23marcanthe machines are just bad
12:23GlanzmannSame as me. So I can test.
12:23joskeGlanzmann, Ok, first trying to install on NVMe
12:23marcanI disabled applesmc since upstream fails horribly on T2
12:23Glanzmannjoske: Btw, I just prepared an ext4 image, that you can disk dump on the partition
12:24_jannau_there's no difference in keyboard/trackpad support between asahi and wifi-take1. Make sure CONFIG_SPI_HID_APPLE and CONFIG_PINCTRL_APPLE_GPIO are set in the kernel config
12:24Glanzmannjannau: I thought so, thank you for the clarification.
12:25GlanzmannIt my config CONFIG_SPI_HID_APPLE=m and CONFIG_PINCTRL_APPLE_GPIO=y.
12:27_jannau_that means the keyboard/trackpad will only work once the module is loaded
12:33Glanzmannjannau: I see, so I'll enable it. Thank you for the tip.
12:44josketouchpad/keyboard now work with new kernel config
12:46GlanzmannPerfect. Here we go. :-)
12:46Glanzmannjoske: Btw. I finished the rootfs for dd, still working on the instructions: https://tg.st/u/m1-rootfs-stable-2021-12-22-wifi.gz
12:47aleasto has joined #asahi
12:48rose_for those following the macos installation saga the 3rd attempt at reinstalling using 1tr failed after nearly an hour. now onto idevicerestore
12:50Glanzmannrose_: I was able to do it without idevicerestore, but it took 3 - 5 tries until it worked.
12:50rose_using 1tr?
12:51Glanzmannrose_: I lost 1tr and had to recover my macbook air from another m1 machine.
12:51GlanzmannBy loosing I mean, I had now idea that the 1tr partition was 1tr and deleted it ... afterwards everything was fine except that I could no longer update macos.
12:52rose_also im quickly realising i dont know what im doing with idevicerestore lol like how do i even plug it in to my laptop
12:52rose_do i use the usb c ports?
12:54rose_okie i plugged in a usb c cable and my laptop sees it on lsusb so im gonna try like this
12:55Glanzmannrose_: I always use the usb ports that are closest to the power on the mini and farer away from me on the macbook air.
13:00rose_nice, that's the one i guessed :D
13:01rose_(from idevicerestore -ln)
13:01rose_ERROR: Unable to discover device mode. Please make sure a device is attached.
13:01rose_i am starting to see this computer as an enemy
13:03FireFox317rose_, you might have to put it in this dfu/recovery mode first?
13:03rose_if i use kmutil to point the bootloader at m1n1, surely i can use kmutil to point the bootloader at macos' kernel? only problem is i don't know where on the disk macos' kernel is
13:03FireFox317im not sure how to do that, since i never did that xd
13:04rose_thanks i'll look into that
13:04FireFox317rose_, well using bputil -n that should work, but that doesnt work right?
13:05rose_oh, right. yeah, bputil -n fails
13:06FireFox317but im just guessing too haha
13:10rose_cool im trying that
13:11rose_after csrutil clear and reboot, csrutil disable gives "failed to create local policy" :(
13:13FireFox317rose_, i guess you dont have the credentials of the machine owner right? in that case i think the only way to restore such a machine would be with with idevicerestore or another mac device
13:14rose_i have the credentials
13:14rose_well, i have the password that it asks for when i run these things, i don't know if there's any other credentials
13:16rose_honestly i'd like to just do it with idevicerestore but even that doesn't want to work
13:16FireFox317oh okay, well im kinda out of ideas xd
13:17rose_oh wait i forgot to try the dfu thing
13:22chadmed has quit [Quit: Konversation terminated!]
13:25rose_ok now the led is amber and idevicerestore sees it (if i run it as root) but it is "unable to discover device type"
13:27rose_fixed by upgrading to idevicerestore master
13:27FireFox317rose_, make sure you have the latest idevice
13:27FireFox317yeah exactly
13:33zimsneexh has joined #asahi
13:45Gaspare has joined #asahi
13:48Glanzmannmarcan: Using the asahi installer I created a 11.5.2 boot environment. Than it told me the m1n1.macho with the following command line: kmutil configure-boot -c m1.bin --raw --entry-point 2048 --lowest-virtual-address 0 -v /Volumes/Linux
13:48GlanzmannNow it tells me 'custom kernel failed to boot'. Any ideas what I'm doing wrong.
13:53j`eyGlanzmann: https://github.com/AsahiLinux/m1n1#usage --raw is for use with 12.1
13:54Glanzmannj`ey: I see, thanks. I'll try with the oldest one.
14:01j`eyhm, actually now im unsure, when you have a paired recoveryOS, is it the same version as the stub, or is it the latest version?
14:03Glanzmannj`ey: I think it is the latest version.
14:04GlanzmannBut I was able to install a few days asahi. in my macbook air but I used the oldest available version. So now I'm trying and let you know how it went.
14:04GlanzmannI don't want to use the newest due to hdmi not initalizing on the mini.
14:10Glanzmannj`ey: It seems I'm screwed. I'm unable to install m1n1.macho any longer on 11.x: https://tg.st/u/IMG_20211222_150925727_HDR.jpg
14:10GlanzmannI'll now try the latest and greatest and see if m1n1.bin comes up (even without video).
14:13j`eyGlanzmann: yeah so, since recoveryOS is 12.1, you have to use the raw option. sorry, I thought the recoveryOS was the same as the macOS version
14:14Glanzmannj`ey: No issue. Got it.
14:15FireFox317j`ey, interesting how for the other person this morning it did work
14:16joskefirefox317, I also used the command without the --raw (after booting into the stub recovery if that makes sense)
14:17joskeI could just run step2.sh
14:18joskeI have now manjaro ARM64 installed on the nvme, and can boot it from m1n1
14:19josketouchpad works, but no gestures and no 2finger or 3finger tap
14:19joskealso no wifi (I did extract the firmware in /lib/firmware)
14:20Glanzmannj'ey: aarch64-linux-gnu-ld: _start must be first!
14:20GlanzmannSo it does not build. That means my build chain does not work.
14:20GlanzmannI'm using debian stable, what do you use?
14:22j`eythat's pretty weird, Im not really sure how that's being messed up
14:22mpsjoske: wifi works only if you boot machine with hypervisor for now, and build kernel from wifi/take1
14:22Glanzmannj`ey: Can you build me one and upload it?
14:22Glanzmannwith your patch, and I try it again.
14:23j`eyGlanzmann: the patch is just a compile time assertion that things have built correctly, and it looks like they havent here
14:23Glanzmannmps: For me wifi works without the hypervisor, but I need a proxyclient to apply the pci enable experiment.
14:23j`eyGlanzmann: im using ubuntu
14:23mpsjoske: do you run xorg or wayland? touchpad works fine with xorg in my box
14:23Glanzmannj`ey: When you build it, does it give you the assert?
14:23joskemps, xorg
14:24joskerunning mate desktop (it does not support wayland yet)
14:24mpsGlanzmann: how do you run proxyclient without hypervisor
14:24j`eyGlanzmann: no
14:24Glanzmannmps: From a second PC.
14:24Glanzmannj`ey: So my build chain on Debian stable is broken.
14:24mpsGlanzmann: so this is posible, didn't know
14:25Glanzmannmps: I tested on macbook air and on mini.
14:25j`eyGlanzmann: either that, or m1n1 is expecting something to be built in a specific way that isnt guaranteed
14:25mpsjoske: you can set parameters with xinput utility or create /etc/X11/xorg.conf file to set libinput params
14:25Glanzmannj`ey: Your patch should be submitted upstream. Will do it or should i send it?
14:26joskeGlanzmann, I could not find this pci enable script
14:26FireFox317mps, you can just chainload instead of running it under the hypervisor, but for all cases you need a second pc
14:26j`eyGlanzmann: I'll talk to marcan about it
14:26Glanzmannjoske: 'git pull' in 'm1n1' and you need to make it executable (chmod +x ...)
14:26Glanzmannj`ey: Thank you.
14:26mpsfirefox317: yes, I run it chainloded
14:27j`eyGlanzmann: in the meantime, can you revert it, and build, and then upload that .bin somewhere
14:28mpsfirefox317: but iirc marcan told me that I have to boot with hypervisor if I want to run any of proxy commands
14:28j`eymps: no, you need to just have a plain m1n1, that doesnt have uboot appended
14:28mpswill try later when finish with some alpine packages upgrades
14:29mpsj`ey: that is what marcan told me
14:29mpsand I trust asahi devs :)
14:30j`eymps: you misunderstood, you just need to get to the proxy, to be able to run that script, then you can run with or without the hypervisor, but anyway, an smc driver will appear at some point and make all this not needed :P
14:31joskeGlanzmann, I now ran the pcie script but still no wifi
14:32mpsj`ey: so that means it is not make difference if I boot target with hypervisor or 'bare metal' boot?
14:33j`eymps: for wifi, no. but you have to currently have a bare m1n1 (aka not m1n1+uboot), to be able to run the python script
14:33Glanzmannjoske: Can you post the output of lspci; ip l s; dmesg; find /usr/lib/firmware/brcm somewhere?
14:33yuyichao_ has quit [Ping timeout: 480 seconds]
14:34j`eyGlanzmann: just noticed that you applied the patch to the wrong file, it was for m1n1-raw.ld not m1n1.ld
14:34mpsj`ey: aha, thanks. will try to check all this to see do I understand all these
14:34sailorek1234 has quit [Quit: sailorek1234]
14:36Glanzmannj`ey: Fixed, now I get no build errors.
14:37GlanzmannUploaded +ASSERT(_base + 2048 == _start, "_start must be first!")
14:37GlanzmannThan I'll go with the newest one for now.
14:38joskeas soon as I powered my USB C dock, the wifi appeared???
14:39joskeso wifi is working if powered?
14:39FireFox317joske, probably be coincidence, shouldnt matter
14:40joskeanyway good progress :-)
14:40joskegotta go now, will probably be back later tonight
14:41Glanzmannj`ey: Sorry about the wrong patch apply. Good catch the paste bot stripped the last \n so it was not applying. So I edited manually and did a mistake. This pbot does not strip newlines: https://tg.st/p
14:42j`eyGlanzmann: no worries, I was confused when I downloaded your m1n1 and verified the offsets were right!
14:42Glanzmannjoske: For debian it loads the module very early. But you can also manuall load it.
14:42Glanzmannj`ey: :-) I'll now try the latest version.
14:48joske has quit [Ping timeout: 480 seconds]
14:49Gaspare has quit [Quit: Gaspare]
14:51Glanzmannj`ey: I ran the asahi installer again with the newest version and it worked. I have no longer video on the mini, but it worked.
14:52rose_ has quit [Quit: Connection closed]
14:53rose_ has joined #asahi
14:58rose_alright, now idevicerestore makes decent progress, but when the mini reboots, idevice waits for it to enter restore mode so it can continue talking over usb, but this doesn't happen and both sides eventually time out. im getting an apple logo and an empty progress bar on the screen, and after a while the mac falls off lsusb and displays a link to
14:58rose_apple support. idevice tells me to make sure usbmuxd is running, and i have done. why do the gods hate me
15:00rose_hmm, dmesg is showing the mini *dis*connecting twice as "Apple Mobile Device (Recovery Mode)" and once as "Mac mini"
15:02yuyichao_ has joined #asahi
15:05bgb has joined #asahi
15:07Gaspare has joined #asahi
15:17Dcow has joined #asahi
15:19rusty-nail[m] has joined #asahi
15:20joske has joined #asahi
15:20Dcow__ has quit [Ping timeout: 480 seconds]
15:28joske has quit [Ping timeout: 480 seconds]
15:31bgb has quit [Ping timeout: 480 seconds]
15:56leo60228- has joined #asahi
15:58leo60228 has quit [Ping timeout: 480 seconds]
16:17mpshow to 'enter' target machine to mode to accept m1n1.macho over usb cable? poweroff it?
16:17Glanzmannmps: You need to kmutil an unmodified m1n1.macho or m1n1.bin
16:17tpw_rulesif it's ready it will have the asahi linux logo in the middle and say "Running proxy..." at the bottom
16:18tpw_rulesbut yes, if m1n1 has u-boot or a kernel appended to it, it will launch that automatically instead of starting the proxy
16:18GlanzmannThan power off, power on. It loads m1n1 and waits, than you can do all the commands using a second linux system conencted via usb cable.
16:18Gaspare has quit [Quit: Gaspare]
16:19mpsGlanzmann: ah, so m1n1.macho must be on Linux macos partition (not sure about macos terminology)
16:19mpsnot possible with currently chailoded m1n1+kernel+dtb
16:20Glanzmannmps: No you boot in 1tr.
16:20GlanzmannThan you use curl to download it.
16:20mpsGlanzmann: I know these
16:20GlanzmannThan you run the command from the wiki. It will it copy it somewhere.
16:20Glanzmannmps: But it is not possible with the chainloaded.
16:21GlanzmannBecause the chainloaded starts immediately
16:21mpsjust wanted to check I have to add bare m1n1 there, not full chainload
16:22mpsI tested all this about two months ago but that vanished from the head and I don't take notes
16:23Glanzmannmps: This always happened to me. Btw. I'm no longer able to install m1n1.macho on 11.x on the mini
16:23GlanzmannIt worked a week ago and I have no idea why. So I can't use my mini at the moment with a screen.
16:24GlanzmannMaybe I'm doing something wrong, maybe there was a macos update, don't know.
16:24mpsGlanzmann: iirc I had to upgrade to 12.0 to install m1n1 on MBP
16:25Glanzmannmps: On the air I don't have a problem with latest because the monitor works.
16:25mpsI prepared cables and other things, just have to upgrade kernel on machine from which I will control target
16:26mpsI don't have experience with macos so I don't dare to upgrade to 12.1
16:28rose_ has quit [Quit: Connection closed]
16:34tpw_rulesGlanzmann: did you try using the raw command but with the macho file?
16:40GlanzmannNo, I did not try.
16:40GlanzmannShould that work?
16:40GlanzmannI only tried the installer for the macho file.
16:41GlanzmannOh I tried once with a chainloaded kernel which also did not work.
16:41tpw_rulesi don't know what that means
16:41Glanzmanntpw_rules: So I'm on the lates macos, I run asahi installer, I choose number 1 (the oldest) I also tried 2 (second oldest). Than I boot in 1tr. Than I get the error that I can't kmutil the m1n1.macho.
16:43tpw_rulesmaybe you can ignore the error and use kmutil yourself
16:43Glanzmanntpw_rules: I tried that. Did not work.
16:43tpw_ruleshow did you try it
16:44GlanzmannI thought the command from the wiki, but I will try one more time and report back. Takes a while because I have to do the delete partition free up space dance.
16:45Glanzmanntpw_rules: Because once it did not work I isntalled the latest and greatest.
16:45GlanzmannThe one with the hdmi
16:45Glanzmannsorry, without the hdmi.
16:46GlanzmannBut, I'll try and report back.
16:48Glanzmanntpw_rules: Btw. I'm working on a guide using your tar trick to dd a debian rootfs. Almost finished, but I'm unable to install m1n1 on the mini (at least not with hdmi)
16:49tpw_rulesdid you ever see the updated version of it?
16:49tpw_rulesi redid it to use uefi and grub
16:50Glanzmanntpw_rules: No, I did not.
16:50tpw_rulestheoretically it should be able to boot the debian installer off usb if you know how to build one with the right kernel
16:50GlanzmannI searched for it today but was unable to find it, can you send me the link please.
16:51tpw_rulesi removed the old one
16:51Glanzmanntpw_rules: I see, this is why could not find it. I wrote down the url now. And took a backup just to be sure.
16:54tpw_rulesthe old ones are still in the git history. but i'm not sure a backup is great because this all changes pretty quickly.
16:54tpw_rulesi mean the trick is basically that if you have a .tar.gz with one file which is your rootfs image, you can use tar -xO to extract it in recoveryOS
16:56Glanzmanntpw_rules: Correctly.
16:57Glanzmannmarcan: https://pbot.rmdir.de/51FNpzGbOXqxqsUyQqUAdQ This is what I get when I try to do 'ifup wlan0' with wpa_supplicant.
16:57GlanzmannThis is on the macbook air.
17:10Glanzmannchromium on Debian stable on m1 just segfaults, interesting.
17:11mpsGlanzmann: also on alpine
17:11zimsneexhThe segfault has to do with pagesize, afaik
17:12Glanzmannjannau: On Debian stable the touchpad and keyboard works. But the middle and right click does no longer work: 2 finger click (right) and 3 finger click (middle) if multitouch is working - any idea what I need to do to enable multitouch?
17:12Glanzmannzimsneexh: I see.
17:13Glanzmanntpw_rules: About the mini and m1n1. Which version did you choose in the asahi installer?
17:14tpw_rulescurrently i'm using 11.4. but i never installed 12.1
17:15zimsneexhWith 12.1 you need the --raw flag, you are using the .bin file instead of the .macho right?
17:15tpw_ruleslike i said i think if you are using 12.1 with an 11.4 stub, you might be able to use --raw and the macho
17:16zimsneexhDoesn't that depend on the version of 1tr instead of the stub version?
17:21mpsgot wifi in lspci out and module loaded but dmesg says it can't find firmware though I installed firmware but kernel tries to load some other files
17:22mpsdo anyone have firmware tar for MBP
17:27jannauGlanzmann: that might depend on the libinput configuration. does right click by clicking in lower right part of the touchpad work?
17:39mpscreated symlinks for missed firmware and now 'modprobe brcmfmac' loads them but I see this in dmesg: [ 952.204243] brcmfmac 0000:01:00.0: brcmf_pcie_download_fw_nvram: FW failed to initialize
17:39SamAdams[m]On Ubuntu 22.04 Daily Build, the touchpad is working great! I can even swipe through the gnome workspaces with the 3 finger swipe, scrolling works great, and tap to click is even supported! It's actually very responsive. Pinching to zoom is more responsive than Mac OS!
17:43thasti has joined #asahi
17:49kettenismps: does it do that on every boot?
17:52mpskettenis: tried just two times
17:57mpsmarcan: you asked me about week ago to send dump from tools/dump_pmgr.py, here it is in case you still need it https://tpaste.us/8Ea8
18:01mpskettenis: tried boot once more but same result
18:03Gaspare has joined #asahi
18:09Major_Biscuit has quit []
18:16Glanzmannjannau: I see. It seems to always do the same no matter where I click. I'm on debian stable maybe I update to testing.
18:16GlanzmannSamAdams[m]: For me scrolling, left, middle and right click was working on Debian Testing out of the box as well in fvwm2
18:17MajorBiscuit has joined #asahi
18:22GlanzmannCan someone talk me through how I downgrade my mac mini to 11.x?
18:25zimsneexhGlanzmann: I assume you could do that with idevicerestore?
19:03Glanzmannzimsneexh: I have all the usb cables and devices, but never used idevicerestore before.
19:29Gaspare has quit [Quit: Gaspare]
19:48nobodynada has joined #asahi
19:56nobodynada has quit [Quit: Lost terminal]
20:25Glanzmannzimsneexh: What m1 device do you have? Wifi is working for you with 5 Ghz, correct?
20:27marcanzimsneexh: it depends on both
20:27marcankmutil in 12.1 will let you use --raw and then 11.4 iBoot will load it as a macho
20:28marcanmps: you shouldn't need to symlink any firmwares, if you do something is wrong
20:29Glanzmannmarcan: regading kmutil, does that mean I can kmutil --raw the macho file and than it will boot in 11.4 partition?
20:29marcanI think so
20:29marcanI'm not sure if anyone has tried it yet
20:29GlanzmannI'll try it and report back.
20:30marcananyway, I don't know why people keep using 11.4 stubs? just use 12.0 beta8, that one should work on the mac mini with HDMI and won't have problems with kmutil
20:31Glanzmannmarcan: I'll try that.
20:31marcanI really want people to stop using 11.x, it's going to be deprecated soon enough and the only reason I haven't nuked it from the installer is that 12.0.1 has the stupid HDMI problem left to solve
20:31marcanthe system recovery mismatch stuff is just one of many problems with 11.x
20:31marcanit was a rushed release and Apple fixed a ton of stuff for 12.x
20:32mpsmarcan: I followed your guide only. Also Glanzmann told me that on his machine have same problem
20:32joske has joined #asahi
20:32Glanzmannmarcan: I also send mps my firmware dump, same content. But to be honest on my air I only tried once, and I copied the firmware after the boot and unloaded and loadded the module.
20:33marcanso do you know what firmware is supposedly missing? that's more useful to know than "I symlinked something" :p
20:33GlanzmannI also have not figured out how to use 5 Ghz on the mini. But the 2 GHZ is rock stable. 9 hour endless loop burst transfers in both directions.
20:34mpsmarcan: I will look tomorrow again and post list of symlinks I made
20:34mps(because I forgot to save history)
20:35Glanzmannmarcan: Here is the ioreg -l otuptu from the air: https://tg.st/u/macbook_air_m1_ioreg_l.txt
20:38marcanGlanzmann: I literally used the same exact IDs for the example in the commit message in e2b4b1ea44
20:38marcan(since I was using my Air for that)
20:39marcanlrwxrwxrwx 1 marcan marcan 39 Jan 1 1970 brcmfmac4378b1-pcie.apple,shikoku.bin -> brcmfmac4378b1-pcie.apple,atlantisb.bin
20:39marcan-rw-r--r-- 1 marcan marcan 35373 Jan 1 1970 brcmfmac4378b1-pcie.apple,shikoku.clm_blob
20:39marcan-rw-r--r-- 1 marcan marcan 7597 Jan 1 1970 brcmfmac4378b1-pcie.apple,shikoku-RASP-m.txt
20:39marcan-rw-r--r-- 1 marcan marcan 7536 Jan 1 1970 brcmfmac4378b1-pcie.apple,shikoku-RASP-u.txt
20:39marcanall the necessary files should be there
20:45marcaneither way, I did get an ALARM install on an external HDD today so I can easily test on all the machines later
20:45marcan(once I work out the T2 business... sigh)
20:45marcanbut I need to get some sleep now
20:47mpsyes, also I have to go to bed
20:49Glanzmannmarcan: Have a good night sleep, mps, you too.
20:50marcanso what was missing?
20:52GlanzmannNo idea. But I'll try some more and report back. Sleep well.
20:57suricato_ has joined #asahi
20:58suricato has quit [Ping timeout: 480 seconds]
21:26lockejan[m] has left #asahi [#asahi]
21:27RianSouzaSantos[m] has joined #asahi
21:48GlanzmannMarcan, I tried the asahi installer to boot 12.0 beta8, I got that: https://tg.st/u/Screenshot_2021-12-22_at_22.18.05.png Than I tried to boot in 1tr and use the boot picker, it ends up in an endless progress bar: https://tg.st/u/IMG_20211222_224132138.jpg So I gave up and go without hdmi for now.
22:11x56whoops :)
22:25joske has quit [Ping timeout: 480 seconds]
22:45nobodynada has joined #asahi
22:46Glanzmannmarcan: About the wifi on macbook air. I have an interface, I can associate to the access point, but I can't do any traffic over the wlan interface (dhcp, ipv6 route advertisement; ping when I manually set an IP address) https://pbot.rmdir.de/HehUvWMel8NJGl_VdINrhg https://pbot.rmdir.de/c8wTQiOeknO7uC_jOsdrGQ
23:08nobodynada has quit [Ping timeout: 480 seconds]
23:17MajorBiscuit has quit [Quit: WeeChat 3.3]
23:57aleasto has quit [Quit: Konversation terminated!]
23:59aleasto has joined #asahi
…