#
…

2022-01-07

00:18aleasto has quit [Remote host closed the connection]
00:24aleasto has joined #asahi
00:42chadmed has joined #asahi
00:45aleasto has quit [Quit: Konversation terminated!]
01:00qeeg has joined #asahi
01:06yuyichao has joined #asahi
03:26kov has quit [Quit: Coyote finally caught me]
03:26kov has joined #asahi
03:40PhilippvK has joined #asahi
03:43phiologe has quit [Ping timeout: 480 seconds]
03:45h_ has joined #asahi
04:03darkapex4 has joined #asahi
04:07marvin24 has joined #asahi
04:09darkapex3 has quit [Ping timeout: 480 seconds]
04:11marvin24_ has quit [Ping timeout: 480 seconds]
04:54Xesxen has quit [Remote host closed the connection]
05:02tertu has joined #asahi
05:03Xesxen has joined #asahi
05:08marcanlandscape15[m]: every change to machine software does not require 1TR
05:08marcanchanges to the custom boot object require 1TR
05:08marcannormal installs can happen from macOS if Apple still signs that version or from any rOS if they do not (reduced security)
05:09marcanbut that wouldn't work from linux anyway because we wouldn't want to implement or require the phone home stuff
05:09marcanso upgrades will require recovery mode (=1TR in the normal case anyway)
05:10marcanthe remaining question is whether they will *also* require two reboots, doing step2.sh again from upgraded rOS
05:10marcanI'm not sure yet, I suspect they will ever since 12.x but maybe we can find a way around that. unclear.
05:11marcansven: the auxKC stuff is more magic than we thought anyway
05:12marcanapparently there's a "kcOS" involved
05:12marcanit doesn't get updated from macOS; stuff gets staged and a reboot through recovery in a special mode happens
05:12marcanyou can tell because installing kexts ends up in a magic double reboot on macOS
05:12Plutoon has joined #asahi
05:12marcanand all that will only work with real kexts and there's magic authentication/credential passing and it's all a giant confusing thing
05:13marcanso even if it *did* work for fuOS, we wouldn't be able to use it without some serious craziness
05:17Plutoononce pluton becomes a thing you wont even be able to install linux on x84
05:19gabuscus_ has joined #asahi
05:22gabuscus has quit [Ping timeout: 480 seconds]
05:22marcanisn't pluton the xbox stuff? if so hey, maybe x86 actually has a chance at decent silicon security too, no thanks to intel
05:22marcanApple (iDevices) and Microsoft (Xbox) are, in my opinion, the only two companies that know how to do consumer product security properly
05:23chadmedyeah pluton is the xbox security chip ported to SIP block, the new AMD laptop chips have it integrated
05:23marcanthe xbox security stuff was always an IP block
05:24marcanso this is just MS telling AMD they have permission to ship it in non-xbox silicon :)
05:24Plutoonpermission?
05:24chadmedwell AMD cant just take Microsoft's IP and use it wherever they want
05:25chadmedthey need permission to integrate it onto their chips
05:25Plutoonactually they are mandating it
05:25chadmedyeah ok but its still not open source HDL so you need MS's permission to have it and integrate it into your own design
05:25chadmedmandating its presence for win11 certification is different to letting chipmakers put it in their chips
05:26Plutoonat least if they want to get windows XX working on their silicon
05:28marcanalso I see nothing about this locking down the platform to other OSes, that sounds like the same nonsense FUD we had with TPMs
05:28Plutoonim sure windows loves linux as long as its running under windows
05:28marcaneither way, this is offtopic
05:28chadmedthey wont stop you from installing linux because that would be extremely illegal and regulatory bodies the world over would come down on them like a metric tonne of bricks
05:29mjg59The firmware running on Pluton in the AMD chips just exposes TPM functionality
05:29mjg59It is literally unable to prevent you booting the OS of your choice
05:29Plutoonyes they are taking babe steps with this for sometime now
05:29chadmed#asahi-offtopic
05:29marcanI'm *not* having this kind of rhetoric here, sorry
05:29marcannot even in -offtopic
05:30marcanI've had more than enough "apple will lock down macs next year" arguments on HN and friends and this is the exact same thing but for PCs
05:30marcanplease take your conspiracy theories to another community
05:30Plutoonconspiracy theories?
05:31marcan< Plutoon> yes they are taking babe steps with this for sometime now
05:31Plutoonits plain to see
05:31marcangreat; please discuss this elsewhere
05:31marcanwe're busy improving free software here
05:33Plutoonif they had it their way linux would be illegal since its inception
05:33marcanthis is not the place.
05:34Plutoonokay i just dont get why are you so worked up about some triviall thing
05:35marcanit's not a "trivial thing", this is the 20th time someone tries to argue that $manufacturer is evil and going to lock everyone out with me and I am tired of it. It doesn't matter that it's always Apple and now it's Microsoft. Those arguments never go anywhere, no proof is ever shown of anything, we've had this kind of fearmongering since TPMs and I'm not going to waste my and everyone else's time ...
05:35marcan... further on this.
05:36Plutoonis it possible to install linux on chrome books natively?
05:36marcanfrom the very start, with a documented process. it always has been.
05:37marcanI have a chromebook running Arch sitting on my shelf
05:37Plutoonyou need some emulation thing croton
05:37marcanno you don't
05:37Plutoonokay then
05:37Plutoonthats good to know
05:38Plutoonso you didnt use that croton thing?
05:38marcanno I did not
05:39krbtgtremember back when all this rhetoric was called palladium?
05:39krbtgtfun times...
05:39marcanah yes...
05:39krbtgtguys vister will be the end of freedom!!!
05:41rkjnsn[m]Crouton is an unofficial way to install a separate distro in a chroot environment inside a reduced-security Chrome OS. It is distinct from installing a different Linux distro on the bare metal.
05:41krbtgtchromebooks come with w/ a boot time unlock for that
05:43rkjnsn[m]Yes, sorry. Just meaning to clarify that not only do you not need crouton to install Linux bare-metal on a Chromebook, that's not even what crouton seeks to accomplish.
05:48vnogueira has quit [Ping timeout: 480 seconds]
05:55eroux has joined #asahi
05:58vnogueira has joined #asahi
06:08Plutoon is there some easy way to disable l3 cache on linux?
06:10Plutoonim geting this  [Hardware Error]: cache level: L3/GEN, tx: GEN, mem-tx: RD
06:11eroux_ has joined #asahi
06:11marcanthis is on x86, right? that is also offtopic
06:11Plutoonthere doesnt seem to be anything on topic going on here
06:11eroux has quit [Ping timeout: 480 seconds]
06:12marcanthat's not an invitation to use this channel for other topics
06:12Plutoonbetter that not using it for anything at all
06:13marcanthat really isn't how IRC works
06:15PlutoonIRC works like divide and conquer
06:22rkjnsn[m]I haven't tested it, but it looks like the hostap / wpa_supplicant patches published by Cypress add support for SAE offload, among other things: https://community.infineon.com/t5/Resource-Library/Cypress-Linux-WiFi-Driver-Release-FMAC-2020-09-25/ta-p/251089
06:22marcanhah. yeah, they would, since they run on brcmfmac :)
06:22marcangood to know
06:22marcanwonder if anyone plans to upstream that?
06:35the_lanetly_052__ has joined #asahi
06:38rkjnsn[m]Hopefully, not too far off-topic, but do you know if any of the firmware extraction / loading stuff could be applied to pre-T2 Macbook Pros?
06:38rkjnsn[m]According to https://support.apple.com/guide/security/protocol-security-sec8a67fa93d/web, WPA3 is supported by macOS on late-2013 and newer Macs, but the firmware included in linux-firmware for my 2015 MBP doesn't appear to support it.
06:46marcanrkjnsn[m]: I actually haven't figured out where the firmware for older cards lives
06:46marcanit's not in /usr/share/firmware/wifi, at least not in Monterey
07:01marcanrkjnsn[m]: I poked around and it seems for those the firmware is embedded in the kexts
07:01marcanso not as easy to extract
07:01marcanand no idea how the OTP/platform selection stuff would work there
07:42MajorBiscuit has joined #asahi
07:43Plutoon has quit []
08:31ey3ball[m]<jannau> "has anyone a 16-inch macbook pro..." <- Sorry, a bit late to the party, just in case you didn't manage to get that info yet :... (full message at https://matrix.org/_matrix/media/r0/download/matrix.org/VdGqznlZtBqRkjxLHaFAZHlX)
08:37mpssorry if it is OT, but chromebooks have physical screw by which it is possible to flash boot firmware (say u-boot) and change some hardware configs to internal flash, and it is intended for 'brave' ones to do this
08:39mpsI run linux in 'bare metal mode' for years on some chromebooks
08:40_jannau_ey3ball[m]: thanks. I didn't have the information yet and it's not the same product ID as the 14-inch model
08:42ey3ball[m]It's a french keyboard though, don't know if this can have an impact too
08:48_jannau_I don't think so, product ids are continuous for the 13, 14 and 16-inch macbook pros. product id was constant for various Keyboard layouts on the other models
08:48darkapex has joined #asahi
08:52chadmed has quit [Ping timeout: 480 seconds]
08:53darkapex4 has quit [Ping timeout: 480 seconds]
08:53rkjnsn[m]marcan: Ah, slightly unfortunate. Which kext?
09:17darkapex1 has joined #asahi
09:21darkapex has quit [Ping timeout: 480 seconds]
09:26vnogueira has quit [Ping timeout: 480 seconds]
09:42darkapex2 has joined #asahi
09:46darkapex1 has quit [Ping timeout: 480 seconds]
10:03marcanrkjnsn[m]: there's plugins with the chip name in the filename, something under AirPort, you should be able to find them (not in front of that computer atm)
10:03marcansearch for e.g. 4360
10:04marcanmps: the screw thing is obsolete, it's now some kind of power button tap sequence, not unlike (but more extreme than) 1TR
10:04marcanbut mine is from the screw era
10:07mpsmarcan: also all of mine are more than 4 years old, didn't know they changed this, so now even opening them is not needed
10:08j`eymarcan: can you push a branch for your wifi v2 patchset?
10:09j`eymarcan: (to be able to diff against v3)
10:10marcanj`ey: pushed as wifi/v2, but you'll have to rebase one or the other since the v3 wip is against asahi
10:11marcan(ignore the last commit in wifi/v2, that was not part of the series obviously)
10:12marcanI think v3-wip-asahi should have all the review feedback so far
10:12marcanplus a couple extra fixes and the WPA3 thing
10:12j`eymarcan: ty
10:13mpsmarcan: would you add my keyboard patch
10:14marcanmps: the F key thing? I need to do the overall rebase to update the nvme and keyboard/touchpad stuff first but sure, we can carry that in lieu of working touch bar for now
10:15mpsmarcan: yes, temporary 'workaround' for Fkeys till someone made touchbar driver
10:15j`eymarcan: reckon you'll be back to streaming ""soon""?
10:17_jannau_mps: I've integrated it dependent on the 13-inch macbook pro product id. I haven't pushed my current input tree yet though
10:18marcanj`ey: yeah, I'd like to sneak in a day in the next week but if I can't, definitely the week after
10:18j`eymarcan: I think devm_kasprintf rather than the incremental buildup of 'buf' is easier to read
10:18marcanyeah, I think so too
10:18mps_jannau_: aha, ok.
10:19j`eymarcan: and cool, look forward to it
10:19mpsthis Fkeys hack is very useful for me
10:21rkjnsn[m]marcan: Hmm… I'm not seeing any files with 4360 in the name. I have a /System/Library/Extensions/IO80211FamilyLegacy.kext/Contents/PlugIns/AirPortBrcmNIC.kext/Contents/MacOS/AirPortBrcmNIC, which appears to contain a symbol named _dlarray_43602pci, among others.
10:22marcanhm, different version maybe? I think it was under that PlugIns path, I can check again a bit later
10:22marcanor just ioreg -l and see what it mentions, it should be in there, grep -i airport or bcm should find it
10:23rkjnsn[m]Thanks! I'm on 12.1.
11:09eroux_ has quit []
11:32Major_Biscuit has joined #asahi
11:39MajorBiscuit has quit [Ping timeout: 480 seconds]
12:48aleasto has joined #asahi
13:27rkjnsn[m]Well, I'm pretty sure the _dlarray_43602pci symbol points to at least part of the firmware, but not everything needed (possibly just for one core type). At the very least, it is lacking nvram settings. But I have already spent way too much time on this for tonight, and must sleep.
13:44neobrain has quit [Remote host closed the connection]
14:39yuyichao has quit [Ping timeout: 480 seconds]
16:23the_lanetly_052___ has joined #asahi
16:29the_lanetly_052__ has quit [Ping timeout: 480 seconds]
16:34yuyichao has joined #asahi
17:04vmeson has joined #asahi
17:29___nick___ has joined #asahi
17:29___nick___ has quit []
17:30___nick___ has joined #asahi
17:40Major_Biscuit has quit []
17:54artemist has quit [Remote host closed the connection]
17:58artemist has joined #asahi
18:14mps has quit [Ping timeout: 480 seconds]
19:07wCPO has quit [Remote host closed the connection]
19:08wCPO has joined #asahi
19:12mps has joined #asahi
19:21Latrina has quit [Quit: Powered by AlpineLinux under the supervision of Docker.]
19:22Latrina has joined #asahi
19:56Latrina has quit [Quit: Powered by AlpineLinux under the supervision of Docker.]
19:57Latrina has joined #asahi
20:27___nick___ has quit []
20:28___nick___ has joined #asahi
20:43darkapex2 has quit [Ping timeout: 480 seconds]
20:54darkapex3 has joined #asahi
21:07___nick___ has quit [Ping timeout: 480 seconds]
21:16jannaumy macbook seems much warmer with wifi/take5 and wifi enabled compared to my spi-hid branch based on linux-asahi. system is idling at sddm login screen
21:23qeeg has quit [Read error: Connection reset by peer]
21:36mpsjannau: I'm also running asahi wifi/take5 and machine is not warm, though I don't know how warm or cold it is with your branch
21:37darkapex3 has quit [Ping timeout: 480 seconds]
21:39mpswhere I can find your branch, maybe I could try to build it and test
21:43jannauit's work in progress but the only difference to linux-asahi is my work on the input devices
21:43jannauI think it was with apple_defconfig so it might be audio
21:57darkapex3 has joined #asahi
22:19Dcow_ has joined #asahi
22:20Dcow___ has joined #asahi
22:23Dcow has quit [Ping timeout: 480 seconds]
22:24Dcow__ has quit [Ping timeout: 480 seconds]
22:25Dcow has joined #asahi
22:26Dcow__ has joined #asahi
22:30Dcow____ has joined #asahi
22:30Dcow___ has quit [Ping timeout: 480 seconds]
22:30Dcow___ has joined #asahi
22:31Dcow_ has quit [Ping timeout: 480 seconds]
22:33Dcow has quit [Ping timeout: 480 seconds]
22:35Dcow__ has quit [Ping timeout: 480 seconds]
22:47Dcow has joined #asahi
22:47Dcow_ has joined #asahi
22:48Dcow____ has quit [Ping timeout: 480 seconds]
22:49Dcow___ has quit [Ping timeout: 480 seconds]
22:51Quinn[m] has joined #asahi
22:57yuyichao has quit [Ping timeout: 480 seconds]
…