2021-12-23
00:51chadmed has joined #asahi-dev
01:05chadmed has quit [Quit: Konversation terminated!]
01:05chadmed has joined #asahi-dev
01:12chadmed has quit [Quit: Konversation terminated!]
01:18chadmed has joined #asahi-dev
01:23aleasto has quit [Quit: Konversation terminated!]
01:39yuyichao_ has quit [Ping timeout: 480 seconds]
01:43kit_ty_kate has quit [Quit: WeeChat 2.9]
02:44kit_ty_kate has joined #asahi-dev
02:46yuyichao_ has joined #asahi-dev
03:58phiologe has quit [Ping timeout: 480 seconds]
04:14marcanthe kernel needs a bunch of patches that aren't upstreamed yet to support mising 4K CPU and 16K IOMMU pages
04:16marcanas far as I'm concerned we're doing 4K only because distros default to it (so they don't have to ship a separate kernel once everything is upstream) and for FEX to work properly; I still expect 16K to work for everything else, and will be shipping 16K kernels for our ALARM remix until 4K is stable and FEX makes sense
04:16marcanany non-emulation software that doesn't work on 16K pages is broken and needs to be fixed
04:18marcanmy current plan for chrome is to just do our first dev release with a big "chrome doesn't work, please file upstream bugs for 16K page support" known issue :p
04:18tpw_ruleschrome deliberately chose to break it for "binary size reduction" so not sure how amenable they'll be to fixing it
04:22marcan(which is why RHEL will never run their default kernels on M1s... that and they also disable DT support because apparently they want the whole world to run on ACPI)
04:23tpw_ruleslike i said in the other channel i got it building by replacing a few cases of assuming 4k pages but it only works with flags that disable multiple processes. so idk if that's a deeper page related problem or some deficiency in another area of asahi
04:28tpw_ruleseh i'll try to build a bigger kernel tomorrow and see what happens. it would be nice to be able to say "make these changes and it will work"
04:32tpw_rulesrelatedly, the nvme stuff in linux-asahi is robust enough to handle a chromium build. maybe tomorrow i can try sven's branch and see if it's worse
05:45Dcow has quit [Ping timeout: 480 seconds]
05:45Dcow has joined #asahi-dev
07:08MajorBiscuit has joined #asahi-dev
07:09chengsun has quit [Quit: Quit]
07:12chengsun has joined #asahi-dev
07:13chengsun has quit []
07:14chengsun has joined #asahi-dev
08:19marcanso it turns out 1) the core was wrong, as I said, 2) you need to flip an OTP enable bit, which I'd found but did not understand went along with the shadow area, *and* the arm64 macOS driver does not do that but the x86 build does, 3) you have to read the OTP area using 16-bit accesses on these chips
08:20marcanso, now just the ACPI shenanigans for module-instance and antenna-sku left to make T2 macs work properly
08:21Redecorating[m]nice!
08:22Dcow_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
08:22Dcow_ has joined #asahi-dev
08:41adityagarg8[m] has joined #asahi-dev
08:45adityagarg8[m] has left #asahi-dev [#asahi-dev]
09:05Major_Biscuit has joined #asahi-dev
09:07MajorBiscuit has quit [Ping timeout: 480 seconds]
09:28marcan... but it's necessary on at least some T2 macs, without that entropy block the cards won't boot
09:34Redecorating[m]the random bytes stuff is needed when the firmware is taken from Catalina+ for 4364 and 4355 (not sure about 4377)
09:35Redecorating[m]but bcm4364b3 only has firmware from Catalina onwards
09:38sventpw_rules: there’s a 4K series somewhere on LKMl that works fine but needs some more adjustments to be accepted upstream
09:53Redecorating[m]if you have the name of the nvram variable, i can send what I have on bali u X3
10:01___nick___ has joined #asahi-dev
10:03aleasto has joined #asahi-dev
10:04mjg59marcan: I have sincere appreciation for you improving the state of affairs on last-gen x86 Macs as well
10:05mjg59A lot of what we did in that space was the bare minimum to make things work, and it's clear that in various fields (like wifi) that wasn't actually sufficient
10:37Major_Biscuit has quit []
10:41MajorBiscuit has joined #asahi-dev
10:43BastienSaidi[m] has joined #asahi-dev
10:50Major_Biscuit has joined #asahi-dev
10:51___nick___ has quit []
10:52MajorBiscuit has quit [Ping timeout: 480 seconds]
10:54___nick___ has joined #asahi-dev
10:57marcanmjg59: I had to blacklist two drivers since they were misbehaving badly, and there's still no VHCI driver so no keyboard/touchpad... so clearly there is a ways to go :(
10:58marcanI don't actually seem to be able to see any networks in NetworkManager, not sure if that's PEBKAC or something else (it does do scans and returns SSDIs, including some cached ones?)
10:59marcanso maybe there's something else to do, but at least it should get the right firmware/config and boot the card
11:24Dcow__ has joined #asahi-dev
11:26Redecorating[m]marcan: wifi/take2 works fine for me, I can scan and connect to networks (but i'm using iwctl)
11:27Dcow has quit [Ping timeout: 480 seconds]
11:28Dcow has joined #asahi-dev
11:32Dcow__ has quit [Ping timeout: 480 seconds]
11:43DragoonAethis has quit [Remote host closed the connection]
11:48DragoonAethis has joined #asahi-dev
13:00Gaspare has joined #asahi-dev
13:38svenRedecorating[m]: could you install fio (apt-get install fio on ubuntu should work) and run fio --ioengine=sync --direct=0 --fsync_on_close=1 --randrepeat=0 --nrfiles=1 --name=randwrite --rw=randwrite --bs=4K --size=1G --end_fsync=1 --fallocate=none --overwrite=0 --numjobs=1 --sync=1 --directory=[SOME DIRECTORY ON THE NVME DRIVE]? i'm curious how
13:39svenit'll benchmark nvme performance for random writes w/ flushes which are still very slow on the M1 with my driver
13:44Redecorating[m]it says eta 1h 28m so i'll probably be asleep when it finishes
13:44Redecorating[m]dunno if this is useful in the meantime`Jobs: 1 (f=1): [w(1)][1.1%][w=196KiB/s][w=49 IOPS][eta 01h:28m:30s]`
13:45Redecorating[m]it is btrfs btw
13:45Redecorating[m]if that changes anything
13:46Dcow_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
13:48chadmed has quit [Remote host closed the connection]
13:53Dcow_ has joined #asahi-dev
14:05Gaspare has quit [Quit: Gaspare]
14:40marcansven: fwiw, since I happen to be on a T2 too, changing size to 100M (I only have the EFI partition mountable here): Jobs: 1 (f=1): [w(1)][2.7%][w=108KiB/s][w=27 IOPS][eta 10m:45s]
14:42yuyichao_ has quit [Ping timeout: 480 seconds]
14:45marcanoriginally I thought it would be easier to just have a default and use the standard firmware set MAC call in a generic way, but I realized today that having a macaddr= unconditionally in nvram overrides the SROM MAC for cards which do have it
14:46kettenisadmittedly the OpenBSD code is a bit dumb and blindly appends a macaddr= line if a local-mac-address property is found in the device tree
14:46marcanso now I only add it (or replace it if it's already there) iff the platform has a MAC set
14:46Gaspare has joined #asahi-dev
14:46kettenisreplacing it would require more string parsing code in the kernel, which we don't really like
14:47marcan(which also had a potential buffer overflow which I just fixed as part of these changes... so yeah)
14:47marcan(it wasn't allocating extra space for additional appended props, so if there wasn't enough space saved from comment/junk removal... that would overflow heap)
14:47psykose has quit [Remote host closed the connection]
14:49marcanat least in cases where there is no boardrev so a default gets added, and nothing else removed
14:49psykose has joined #asahi-dev
15:03Gaspare has quit [Quit: Gaspare]
15:22yuyichao_ has joined #asahi-dev
15:30aleasto has quit [Quit: Konversation terminated!]
15:31aleasto has joined #asahi-dev
15:54aleasto has quit [Remote host closed the connection]
15:57aleasto has joined #asahi-dev
16:29Dcow_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
16:45aleasto has quit [Quit: Konversation terminated!]
16:46aleasto has joined #asahi-dev
16:46aleasto has quit []
16:46aleasto has joined #asahi-dev
17:59Gaspare has joined #asahi-dev
18:08skipwich has joined #asahi-dev
19:10Gaspare has quit [Quit: Gaspare]
20:28jannaumarcan: wpa3-personal seems to be broken: "ieee80211 phy0: brcmf_set_sae_password: failed to set SAE password in firmware (len=24)" with wifi/take3 on j274
21:07___nick___ has quit [Ping timeout: 480 seconds]
21:22MajorBiscuit has joined #asahi-dev
21:23Major_Biscuit has quit [Ping timeout: 480 seconds]
22:26jannaumarcan: on j314c "brcmfmac 0000:01:00.0: brcmf_pcie_read_otp: OTP unavailable, using default firmware"
22:33yuyichao has joined #asahi-dev
22:36yuyichao_ has quit [Ping timeout: 480 seconds]
22:42yuyichao_ has joined #asahi-dev
22:45MajorBiscuit has quit [Ping timeout: 480 seconds]
22:46yuyichao has quit [Ping timeout: 480 seconds]
22:52yuyichao_ has quit [Ping timeout: 480 seconds]
23:31manawyrm has quit [Quit: Read error: 2.99792458 x 10^8 meters/second (Excessive speed of light)]
23:31manawyrm has joined #asahi-dev
23:40tpw_rulessven: i'm not able to get your asahi-with-new-nvme branch working, but i didn't try all that hard. the nvme driver fails to identify the device, the rtkit driver tries to reset it, then rtkit crashes
23:41tpw_rulesbut that is also with u-boot in the mix. just wondered if you had seen that in any configuration before
23:41tpw_rulesbut the current nvme drivers in the asahi branch seem quite robust, been compiling junk all day
23:42tpw_rulesmaybe they are susceptible to problems under high sustained speed but certainly not random i/o