2021-08-11
00:12yuyichao has quit [Quit: Konversation terminated!]
00:13yuyichao has joined #asahi
00:19jeffmiw has quit [Ping timeout: 480 seconds]
00:25quarkyalice has joined #asahi
00:35yuyichao has quit [Ping timeout: 480 seconds]
00:37quarkyalice has quit [Ping timeout: 480 seconds]
01:57riker77_ has joined #asahi
02:02riker77 has quit [Ping timeout: 480 seconds]
02:02riker77_ is now known as riker77
02:06yuyichao has joined #asahi
02:27PhilippvK has joined #asahi
02:30phiologe has quit [Ping timeout: 480 seconds]
03:20cth451_desktop has joined #asahi
03:37marvin24 has joined #asahi
03:41marvin24_ has quit [Ping timeout: 480 seconds]
03:53kov has quit [Quit: Coyote finally caught me]
03:53kov has joined #asahi
04:46marcanwill probably stream in a bit, once macOS finishes reinstalling :-) (I think I broke my "Linux" install)
04:52marcanfwiw, the (basic) installer is 70% of the way there; I just need to solve the ownership transfer problem (basically generate a macOS user database in the installer) and add the missing partitioning assistant type functionality (just wrapping diskutil to automate things)
04:53marcanso we should be able to deprecate that hideous quickstart wiki page for something much simpler today :)
04:54chadmedso that OD user database is where 1TR/bputil get the user information when it asks us for it?
04:54marcannot entirely sure, but regardless, the problem is it wants a user *in* that volume, not just any machine owner
04:55marcanI think the SEP backend lets you authenticate with any machine owner, but sadly the frontend tools don't (and we can't go directly to the SEP due to entitlements)
04:55marcanhowever, the boot picker has an ownership transfer feature that lets you set up ownership on a user in the volume, if it has one
04:56marcanthat said, if kmutil/bputil is really only looking for the user existence in the database, maybe we can cheat
04:57marcan(if it's just authing against the SEP, we could just create a fake user matching the *macOS* i.e. another partition's user, with no password even)
04:57marcanbut I think that won't quite work because I do have the same username everywhere and it did want the right password
04:58marcanregardless, this worked when I copied the database over manually, and I think I did the ownership transfer thing then
05:08al3xtjames has quit [Quit: The Lounge - https://thelounge.chat]
05:10al3xtjames has joined #asahi
06:01svenamw: and that didn't happen before? the code in nvme and devel is also essentially the same
06:02svenamw: and just to confirm: this specific usb drive works fine if you use it with another machine? (i'm asking because i have one broken usb drive that caused me headaches for a week or so until i realized it *also* failed in the same ways on macOS and another linux machine)
06:03chadmedwasnt there also someone else having data corruption issues with devel or dart/dev yesterday?
06:07svenit's also weird because even with 4k pagesize code that i know to be broken i haven't seen that severe corruption
06:10amwI use it through a hub, but that shouldn't make a difference but I can move things around and see if this misbehave on other machines.
06:12amwIt's probably something screwy on my hacky set of patches that I have made - if anyone else tries it shoukd just be-aware of it.
06:13amwAs I can re-image that partition in a minute, it's main impact is that if it happens, I have to re-start the Mac, then m1n1, then load linux et cetera.
06:15amwMy branch is https://github.com/amworsley/AsahiLinux/tree/asahi-keyboard if you wanted to see what is present
06:20svensure, i'm also working (read: waiting for something to finish and chatting in the meantime ;))
06:42bps has joined #asahi
07:21bps has quit [Ping timeout: 480 seconds]
07:49bps has joined #asahi
09:09phiologe has joined #asahi
09:12PhilippvK has quit [Ping timeout: 480 seconds]
10:23pinskia has quit [Remote host closed the connection]
10:51amwsven: I just built and booted the devel branch with out fault. I booted it twice - both were fine
10:52amwI mounted it on host linux in between and no faults or problems. I think it is my set of unstable patches that was causing problems
10:58svenhm... still very strange. please let me know if this happens again, could still be very subtle bug in the DART driver
11:37tomtastic has quit [Read error: No route to host]
11:39tomtastic has joined #asahi
13:10obr[m] has joined #asahi
13:12obr[m] has left #asahi [#asahi]
13:18robinp has quit [Read error: Connection reset by peer]
13:18Lockna[m] has joined #asahi
13:19yuyichao has quit [Ping timeout: 480 seconds]
13:36Lockna[m] is now known as lockna[m]
13:53alyssaI guess that's https://github.com/svenpeter42/linux/commit/88560e2ba97b3fac76c476a263a1642fdcedaf09
13:54yuyichao has joined #asahi
14:06alyssasven: AFAIU you have a branch of those patches rebased on top of the latest DART (used to test said DART)? i don't want to go duplicating effort and it looks like a nontrivial rebase
14:16yuyichao_ has joined #asahi
14:17lockna[m] is now known as Lockna
14:17Lockna is now known as lockna
14:20yuyichao has quit [Ping timeout: 480 seconds]
15:12alyssa kettenis_: building your u-boot, I'm getting a link error for print_cpu_info unless I unset CONFIG_DISPLAY_CPUINFO -- it looks like arch/arm/mach-apple/ needs to define tha
15:22svenalyssa: https://f.svpe.de/66488f63476f52f57d48cdc44d06c4aec86c62050ca00792bcba92c8f724d55c_0001-WIP.patch and https://f.svpe.de/88f8159ac9ff9972a17484e43d8bcdf984929fce54daae7d7b148e3afeb0a11f_0002-pcie-hacks.patch
15:24svenand then i use python3 proxyclient/tools/linux.py -u ../u-boot/u-boot-nodtb.bin -t /dev/cu.debug-console --bootargs="earlycon rw root=/dev/sda1 rootwait rootfstype=ext4" Image.gz ../u-boot/u-boot.dtb
15:24svenit's... not great. but now that DART is on its way to mainline we should be able to make this nicer
15:25TheJollyRoger has quit [Remote host closed the connection]
15:25TheJollyRoger has joined #asahi
15:27svenyou must be mistaken! all my code is immensely beautiful and never contains any hacks whatsoever :-P
15:28bps has quit [Ping timeout: 480 seconds]
15:29svenso the issue with that iommu-map is that apple's pcie controller allows you to essentially configure a pcie rid to sid map in some register
15:29sventhat pci code in linux probably need some support to take care of that. there's another pci driver that also needs that but only during init time
15:30svenso that dtb patch just changes "map these devices to SID 1" to "map these devcies to SID 0" which then works out
15:35sveni've only ever tested that with a hardware UART. it patches u-boot in memory to setup the correct baudrate for that
15:38svendunno how to go from here. i've never debugged u-boot. i just treated it as a black box that i needed to hack a little bit to get pcie up and running
15:53pipcet[m]speaking of insufficient voltages, my MBP just gave me the red battery just as I was about to test&push the fast-ipi thing. works now, code at https://github.com/pipcet/linux/tree/apple-fast-ipi, but I'm taking it as a sign that it's time to do something else prior to cleanup+checking it masks things at the vipi layer+serializing+PRing :-)
15:55svenalyssa: https://f.svpe.de/ef85f68951ed6a14ae83221c6d52dc3561c18132241e3b2e4f66f8672872fbb5_.config so that's my u-boot config
16:58yuyichao_ has quit [Ping timeout: 480 seconds]
17:03yuyichao_ has joined #asahi
17:46YTG123[m] has joined #asahi
17:54YTG123[m] is now known as ytg
17:54ytg has quit [Quit: Reconnecting]
17:54ytg has joined #asahi
18:01handlerug has joined #asahi
18:16hramrach has joined #asahi
21:00PhilippvK has joined #asahi
21:04phiologe has quit [Ping timeout: 480 seconds]
21:09bps has joined #asahi
21:14bps has quit [Read error: Connection reset by peer]
21:40phiologe has joined #asahi
21:40PhilippvK has quit [Ping timeout: 480 seconds]
22:49yuyichao_ has quit [Quit: Konversation terminated!]
22:50riker77 has quit [Ping timeout: 480 seconds]
22:51riker77 has joined #asahi
23:22riker77_ has joined #asahi
23:25riker77 has quit [Ping timeout: 480 seconds]
23:25riker77_ is now known as riker77