2022-02-20
00:24Gaspare has quit [Quit: Gaspare]
01:24willemml has joined #asahi
01:36willemml has quit [Quit: willemml]
02:35jx0 has joined #asahi
03:12sri has joined #asahi
03:13sri_ has quit [Ping timeout: 480 seconds]
03:17marcantpw_rules: re the display stuff, can you poke around the sequences a bit? I can't really test it without a monitor that repros :(
03:25kov has quit [Quit: Coyote finally caught me]
03:25phiologe has joined #asahi
03:26kov has joined #asahi
03:29PhilippvK has quit [Ping timeout: 480 seconds]
03:31tpw_rulesmarcan: the patch seems like a poor man's way of implementing hotplug support. is there a way to do that for real?
03:38tpw_rulesi'm not sure that is because you would have to have code in the background monitoring the hdmi connection i would think. and in u-boot and its efi services. but i think the sequence of operations as documented in the issue is accurate. i don't know how you would predict how long it would take a slow monitor to disconnect so you know it's connected for good before you leave the init function
03:49tpw_ruleskov: finally sat through the webkitgtk build and it seems to work properly now with your patch, thank you!
04:20djsrv has quit [Quit: ZNC 1.8.2 - https://znc.in]
04:33tpw_rulesupdated my nixos stuff to the shiny new asahi branches. hoping to revise the guide soon
04:47gladiac is now known as Guest340
04:47gladiac has joined #asahi
04:53Guest340 has quit [Ping timeout: 480 seconds]
04:53axboe has quit [Quit: leaving]
05:25psykose has quit [Remote host closed the connection]
05:26psykose has joined #asahi
05:27marcantpw_rules: hotplug isn't really practical here, we don't do interrupts or timers or anything and we definitely don't want u-boot doing the same and nothing in the boot stack expects hotplug framebuffers
05:28marcanthe screen gets initialized once, and better stay there; that's also how iboot did it anyway
05:28marcanone workaround we *could* add is a second hotplug pass after loading payloads and such, just to parallelize the delay a bit
05:29marcanbut really what I want to know is can we do this in a way that does not introduce a 5 second delay for everyone
05:29marcanif there's no workaround for this it's going to have to be some kind of payload option people with problematic screens can enable at install time
05:30marcanwhat I want to know is whether invoking DCP ops in e.g. a different order, or doing something different, can mitigate the issue
05:30marcansince the current sequence is basically guesswork based on static RE, since we don't know what iBoot ddi
05:35tpw_rulesmarcan: ah, ok. well i can tell you that whatever iBoot did didn't work on my monitors
05:48sri has quit [Read error: No route to host]
05:48sri has joined #asahi
05:57willemml has joined #asahi
06:34willemml has quit [Quit: willemml]
06:36linearcannon has quit [Quit: Textual IRC Client: www.textualapp.com]
06:37benzmac16v[m] has joined #asahi
06:59VinDuvtpw_rules: did you test your monitor with <12.0 iBoot? (i.e. before a 12.0 macOS ever got installed)
07:19willemml has joined #asahi
07:25sri has quit [Read error: No route to host]
07:25sri has joined #asahi
07:31willemml has quit [Quit: willemml]
08:03willemml has joined #asahi
08:15willemml has quit [Quit: willemml]
09:34le0n_ has joined #asahi
09:41le0n has quit [Ping timeout: 480 seconds]
10:00linearcannon has joined #asahi
10:04chadmed has joined #asahi
10:28ThomasGlanzmann has joined #asahi
10:32ThomasGlanzmann has quit [Remote host closed the connection]
10:46gabuscus has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
10:46gabuscus has joined #asahi
10:52a_fellow_human[m] has joined #asahi
11:01tomtastic_ has quit [Read error: Connection reset by peer]
11:01tomtastic has joined #asahi
11:08as400[m]drivers/regulator/pfuze100-regulator.c: In function ‘pfuze_power_off_prepare_init’:... (full message at https://matrix.org/_matrix/media/r0/download/matrix.org/CCWdrHFrBDYiYbunzwKlCFas)
11:13sri has quit [Remote host closed the connection]
11:14sri_ has joined #asahi
11:25sri has joined #asahi
11:31sri_ has quit [Ping timeout: 480 seconds]
11:33Glanzmannjmr2: Maybe it was the issue in m1n1, because I thought I update m1n1 on my webserver when I run bootstrap.sh from the m1-debian repository, but I don't so maybe my m1n1 was a few days old. But I corrected that and will see if I see the issue later on.
11:41bps has joined #asahi
12:03mpsI don't understand why REGULATOR_PFUZE100=y is problem? if it doesn't exist it will not be detected by kernel, or it exists in M1?
12:14marcanj`ey: I dropped the patch for that because I thought it was an example, didn't realize it actually broke with the shutdown notifier patch
13:08off^ has joined #asahi
13:32bps has quit [Ping timeout: 480 seconds]
13:34mpsmaybe I should add event handler for power plug to switch policy automatically from performance to conservative when unplug power cable
13:35ciggi has joined #asahi
13:48mpsbut I don't see any event when I plug/unplug power, so maybe with small 'sleeping' daemon for now or cron job
13:49eroux has joined #asahi
13:51bps has joined #asahi
13:52Glanzmannmps: https://pbot.rmdir.de/KUir-Mu6hwO2GoqFeWgE1g First event on lid close, second on open.
13:52svennot sure if the current smc driver does it but you can also activate those events and will get a rtkit message on those
13:57Glanzmannas400[m]: Nope. When you're in a dark room, you can see that the backlight is on when the lid is closed.
13:57GlanzmannI thought about playing with it by copying the driver and see if I get to the point where I can turn it off and on.
14:00Glanzmannj`ey: I thought about this in the wiki smc documentation: * `gP12`: on at least one system, the LCD backlight. Can be turned off, which reduces apparent power consumption, and turned back on.
14:03svenif it’s a smc gpio it might just need a device tree node to hook up that gpio backlight driver to the smc
14:16svenbut I’m willing to bet it just needs the right compatible and a gpio = <…> reference to the smc if it’s indeed just a smc gpio
14:21GlanzmannOkay, I'll try that. But first I try that thing with m1n1 if really does what I think it does.
14:25sri has left #asahi [Leaving]
14:40bps has quit [Ping timeout: 480 seconds]
14:42bps has joined #asahi
14:56bps has quit [Ping timeout: 480 seconds]
15:06VinDuvtpw_rules: I see. I guess whatever delays iBoot uses are not sufficient with your monitors. I’m still wondering if iBoot somehow manages to avoid the disconnect/reconnect wait period in my case, or if it waits for it asynchronously while booting the rest of the system
15:13___nick___ has joined #asahi
15:13___nick___ has quit []
15:15___nick___ has joined #asahi
15:16Glanzmannj`ey / sven: https://pbot.rmdir.de/7d4Nh6T4zpjjr1k4FWAmbA So this appears to be the syntax.
15:17GlanzmannSo, now that i found that, does someone know how I can resolve gP12 into the corresponding number?
15:18GlanzmannSo this is what I have: https://pbot.rmdir.de/VQmGue1Sqq4hriFS7WwNFw but I need to resolve gP12 so that i can put it in FIXME.
15:34tpw_rulesi wonder what happens if you set the mode while the monitor is disconnected. presumably the problem is that dcp forgets the mode when the monitor disconencts
15:34tpw_rulesi read the HMDI spec and it seems well within the monitor's rights to cycle like this. like i said before i don't think anything is going wrong aside from hotplug not being supported
15:37svenwe could always hack it by having a second core polling the whole time but that’s quite ugly :D
15:39tpw_ruleswell the problem is you have to wait a while for it. and the time it takes for m1n1 to init the hardware and load u-boot is pretty negligible
15:39tpw_rulesso waiting in the main thread while a second core polls isn't any better than just polling in the main thread i don't think
15:40VinDuvtpw_rules: one of them yes, the other one still occasionally fails (power-up then “no signal”) with 11.x
15:43VinDuvI’m also pretty sure that it only starts waking up on dcp_ib_swap_begin, not dcp_ib_set_mode
15:48VinDuv(I think I tried doing the wait/set_mode after swap_end; it worked and the monitor stayed up, but it was blank, probably because the framebuffer address changed)
15:54kovone thing I have come to like on macos is the trackpad behaviour where a drag will have a small timeout before it drops (so you can quickly take the fingers off and resume the drag), is that a thing that can be configured in X/libinput does anyone know?
15:58tomtastic_ has joined #asahi
15:58tomtastic has quit [Ping timeout: 480 seconds]
16:02kovmps, just found about that here https://askubuntu.com/questions/1238551/drag-lock-not-working-on-fresh-20-04-install
16:07kovand gnome seems to even have a gsettings key for it(!) but it's not in Tweaks(!?), let me verify that
16:09kovso you probably want small swipes rather than crossing the trackpad and resetting when doing long drags, but it makes it possible anyway
16:10kovnow to get this added to gnome settings or Tweaks and get libinput people to add the timeout settings, I guess
16:14mpsI would like shorter timeout and thought to look at libinput source if it can be tweaked at build time
16:17bps has joined #asahi
16:44David[m]123456789I have this error when trying to untar the debian installer, anyone know why (```$ sudo curl -sL https://tg.st/u/m1-d-i.tar | tar -xf -... (full message at https://matrix.org/_matrix/media/r0/download/matrix.org/jyTitDhlDWddEeaMzZONyRPk)
16:45David[m]123456789 * I have this error when trying to untar the debian installer, anyone know why?... (full message at https://matrix.org/_matrix/media/r0/download/matrix.org/pJPtKUIyECycOTYlJRNeoTXv)
16:45David[m]123456789 * I have this error when trying to untar the debian installer, anyone know why?... (full message at https://matrix.org/_matrix/media/r0/download/matrix.org/MjxZzdKRAnwSjypYDkOXiRZg)
16:46David[m]123456789my mistake your message displayed weirdly in konqueror
16:49David[m]123456789Tar doesn't seems to like being run as root:... (full message at https://matrix.org/_matrix/media/r0/download/matrix.org/CFBocaYvnQJOZxWSdfFOeRDa)
16:49tpw_rulesthe EFI partition doesn't have the concept of users and groups so those operations will fail
16:51mpstpw_rules: yes, this annoys me currently because I install vmlinuz-$ver-$var-$min to ESP (vfat) now
17:27David[m]123456789The script for downloading the wifi firmware in the debian wiki page did not finished (nothing displayed), the python3 (wich is installed) call did not worked it seems but I cped the wifi folder in `/usr/share/firmware/wifi` to my USB key
17:27David[m]123456789s/but/so/
17:28David[m]123456789no output
17:29David[m]123456789s/but/so/, s/the wifi folder in//
17:29David[m]123456789 * no output/echo
17:31David[m]123456789there was really nothing
17:31David[m]123456789will rewatch it
17:32GlanzmannDavid[m]123456789: So when I run this command under macos or 1tr I get the output, you see in the video.
17:32GlanzmannBut in order to help you, you must paste the complete output (including the command you issued).
17:34David[m]123456789curl -sL tg.st/u/fwx.sh | sh
17:34David[m]123456789* `curl -sL, * | sh`
17:35David[m]123456789I remeber runing it by mistake before so maybe this folder was created at this time
17:39David[m]123456789seems to works now, thanks
17:39GlanzmannPerfect. Do not forget to copy the firmware to the usb stick, if you plan on installing debian over wifi.
18:02David[m]123456789Yes, i'm connected
18:06David[m]123456789The debian installer displays nonsense characters in french. Will upload pics once done
18:07off^ has quit [Ping timeout: 480 seconds]
18:08mlq has quit [Quit: WeeChat 3.0]
18:18off^ has joined #asahi
18:19j`eyi'm looking at https://support.apple.com/en-gb/HT212749 because I pretty much want to wipe my m1 now that Im going to upgrade to 12.x, does this actually erase all the paritions? or should I delete them with diskutil first
18:20tpw_rulesi think if you try to delete them with diskutil it will let you, but force you to reboot into recovery mode to install the os again
18:21tpw_rulesoh. i would just delete them all with diskutil and not bother with whatever that utility is
18:24Glanzmannj`ey: Easiest way is to delete them using linux (rember to keep the first two and the last parition)
18:24Glanzmannj`ey: Under macos you can use diskutil apfs deleteContainer to delete the stub partition.
18:25Glanzmannj`ey: If you find a way to delete the esp and linux parition let me know, than I document it.
18:31mlq has joined #asahi
18:33Glanzmannanyway I'm sure it works on the cli diskutil, but don't know how. If someone finds out, let me know I would like to document it.
18:46GlanzmannYes, but I'm not sure anymroe. Because I search for an example and could not find one.
19:11jmr2 has joined #asahi
19:13jmr2j`ey: my experience with "erase all content and settings" is that it won't resize the macos partition to use the whole disk in some cases. Not clear which. But it will properly reinitialize macos.
19:13axboe has joined #asahi
19:15jmr2I personnally chose to have the Linux partitions before the macos ones, because macos's diskutil renumber partitions when you create new ones, which force you to update anything that refers to nvme0n1pX.
19:17jmr2For info, I also got a corrupted m1n1 stub in the process, requiring marcan's "double-click and hold after 3s" trick. The installer was reporting it as a "broken stub", but I ignored that - to my expense.
19:18jmr2David[m]123456789: by curiosity, what ended up being the solution to your "unknown user David" issue?
19:20David[m]123456789it was david
19:21j`eyjmr2: I erased all my linux stuff, and then I did resizeContainer diskX 0, to get the freesoace used by macOS
19:24jmr2OK. What I did was 1) install m1n1 2) set that partition as startup disk 3) boot from it in recovery mode 4) delete the macos partition
19:25jmr25) create a temporary 30GB "placeholder" partition, to be used for the m1n1 + EFI + /boot ones later 6) create an apfs one of the size I want for MacOS
19:25jmr27) install macos in that one 8) create multiple smallish partitions at the end of the disk, to be used for /root over lvm
19:26jmr2My goal is to be able to have more linux or more macos space as needed, without needing to reinstall again.
19:34David[m]123456789followed the debian installer video but when I rebooted, there were a simili 2 flashes of the Apple logo then I entederred recovery which says tha amy custom kernel was not able to boot and then proposed to change my startup disk with only Machintosh HD available (which I did), there is still no more available asahi available as startup disk
19:34David[m]123456789s/followed the debian installer video but when I rebooted, there were a simili 2 flashes of the Apple logo then I entederred recovery which says tha amy custom kernel was not able to boot and then proposed to change my startup disk with only Machintosh HD available (which I did), there is still no more available asahi available as startup disk/followed the debian installer video but when I rebooted, there were 2 flashes of the Apple
19:34David[m]123456789logo followed by recovery which says that my custom kernel was not able to boot and then proposed to change my startup disk with only Machintosh HD available (which I did), there is still no more available asahi available as startup disk/
19:40jmr2David[m]123456789: just FYI the edits you're doing through Matrix are fairly hard to read on IRC. See https://oftc.irclog.whitequark.org/asahi/2022-02-20
19:42David[m]123456789Oups, will think more before posting
19:44GlanzmannIf you have not installed u-boot, you need to do that first: https://tg.st/u/asahi-installer-u-boot.mp4
19:46j`eyGlanzmann: I didnt figure it out at the diskutil cli, but I managed to do it from the GUI, I think you have to erase/reformat as APFS before you can delete the volumes
19:49j`eyso maybe trying with eraseVolume (I think that was a diskutil apfs command) first will help
19:53jmr2 has quit [Remote host closed the connection]
20:07David[m]123456789Glanzmann I installed U-Boot and booted the installer through it
20:11j`eyI need to understand it a bit more, I thouht that my efi/data volumes were part of my container stub
20:13j`eywell I never explicitly created volumes or containers, only partitions with diskutil addPartition
20:14tpw_ruleswhen you formatted the first one as apfs in order to make the stub, it turned into an apfs container
20:17svenapfs containers are more like volume groups. we’d need a pretty good apfs driver to use them from linux
20:22j`eyit's funny, even with needing 70GB or so for the macOS space, Im still going to have more storage than I do on my current computer :D
20:26jannautpw_rules: I think it can have 2 physical partitions as it supports apple's SSD+HDD Fusion drives
20:27svenbut I guess it would just use one of those two as a cache instead of increasing the totale space
20:28svenOr did it actually combine the space and just distribute stuff depending on how often it was used
21:05bps has quit [Ping timeout: 480 seconds]
21:08___nick___ has quit [Ping timeout: 480 seconds]
21:13skoobasteeve has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
21:18skoobasteeve has joined #asahi
21:21jeffmiw has quit [Ping timeout: 480 seconds]
21:43skoobasteeve has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
21:47skoobasteeve has joined #asahi
22:07mixiGlanzmann: https://tg.st/u/backlight_notes.txt looks right to me, and should make a /sys/class/backlight/backlight appear (the "backlight:" is only necessary if you want to refer to it from another node though)
22:07mixiit should also have created /sys/firmware/devicetree/base/backlight entry from the device tree node alone though, so my first guess would be that you are loading the wrong device tree again
22:10bps has joined #asahi
22:22zv has joined #asahi
22:22da_n has joined #asahi
22:23zvhello, anyone experience mac mini going to a black screen immediately after flashing "Options" (after the reboot in step 2) ?
22:24zvfrom fully powered off, I hold the power button for ~12 seconds, I see "Options" then the display goes black.
22:31axboe has quit [Quit: leaving]
22:32jannauzv: after executing step2.sh and reboot? do you see the asahilinux logo if power the mac mini on normally?
22:34zvjannau: this is the reboot right before step2.sh, after the step 2 heading in the developer quickstart guide
22:36da_n has quit [Quit: Igloo IRC: https://iglooirc.com]
22:40zvif I don't hold the power button, it boots to "This version of macOS on the selected disk needs to be reinstalled." and the display works, but of course it's not in the right mode.
22:42jannauwhich macos version did you chose for the stub install? 12.0.1 or 12.1? which version is your main macos?
22:43bps has quit [Remote host closed the connection]
22:50jannaucan you easily try a different display or display cable? it sounds like recovery doesn't like your display. not sure what could be broken
22:50zvI tried a dock with displayport, same thing, but unfortunately I don't have a different monitor available.
22:51zvbefore (out of the box) I was able to get to the Options menu, which was necessary due to an unrelated macos installer bug
22:57jannaudoes macos 12.2.1 still work with the display? you should be able to change the startup disk in the "This version of macOS on the selected disk needs to be reinstalled." recovery
23:00zvso this is *really* strange. I have a broken HDMI 7-inch display, connected it, and held the power button until it started glitching (meaning, picture). unplugged that, put back the normal monitor, and I see 3 items: macOS, Asahi, and Options. Good, right? then the display fades to black quickly, immediately after I see the picture.
23:00yrlf has quit [Quit: The Lounge - https://thelounge.chat]
23:05eroux has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
23:07zvI think the problem is my display; I can't even source-select on it without disconnecting HDMI first (meaning the display seems to have locked up). is the mac sending non-conforming HDMI data? I need to find another display; don't think it's an Asahi problem.
23:19babilen has quit [Ping timeout: 480 seconds]
23:53yrlf has joined #asahi