phire has quit [Remote host closed the connection]
phire has joined #asahi
tiagom has quit [Ping timeout: 480 seconds]
yamii has quit [Quit: WeeChat 3.5]
Moprius has quit [Quit: Konversation terminated!]
PhilippvK has joined #asahi
phiologe has quit [Ping timeout: 480 seconds]
Telvana has quit []
Telvana has joined #asahi
marvin24_ has joined #asahi
marvin24 has quit [Ping timeout: 480 seconds]
kov has quit [Quit: Coyote finally caught me]
yyyyyyyyyyyyyyyyyyyyyydrtdsea^ has joined #asahi
ptudor has joined #asahi
ptudor_ has quit [Read error: Connection reset by peer]
Ry_Darcy has joined #asahi
Ry_Darcy has quit []
ROCK-and-ROLL has joined #asahi
ROCK-and-ROLL has quit [Remote host closed the connection]
Koda[m] has joined #asahi
Bey0ndB1nary has joined #asahi
Bey0ndB1nary has quit []
guillaume_g has joined #asahi
ptudor_ has joined #asahi
ptudor has quit [Ping timeout: 480 seconds]
<life-the-user[m]>
Hello asahi nerds
<life-the-user[m]>
I have a question
<life-the-user[m]>
How likely my macbook will brick 🧱 when installing asahi?
<life-the-user[m]>
Uh also
<life-the-user[m]>
What functionality issues might be with MacBook Pro from 2017?
<ktz_[m]>
basically unbrickable.. imagine that even the developers haven't been able to brick one
<life-the-user[m]>
ktz_[m]: Lol
<ktz_[m]>
I mean you'll loose everything file wise but you can always dfu
<life-the-user[m]>
ktz_: alright I think at least I might nuke my drive huh?
<ktz_[m]>
just keep that in mind and back up your files
<life-the-user[m]>
ktz_[m]: Yeah sure
<life-the-user[m]>
life-the-user[m]: ^
<ktz_[m]>
if you mess up your partitions for some reason yes you might not be able to boot into recovery mode and you'll have to use dfu from another pc to reset it
<life-the-user[m]>
As I understood fingerprint scanner doesn’t work too
<life-the-user[m]>
It’s just not specified
<ktz_[m]>
well your laptop is x86 so you can't use asahi
<life-the-user[m]>
ktz_[m]: Oh man wait uh, so I’m planning to install arch linux on MacBook Pro 2017, can I just nuke my whole drive and freely install as usual?
<life-the-user[m]>
ktz_: just talking about possible issues with camera, microphone etc
<_jannau_>
life-the-user[m]: asahi supports only apple silicon based apple devices from end of 2020 and later
<life-the-user[m]>
life-the-user[m]: Actually I did already kind of nuked it
<life-the-user[m]>
_jannau_: Dude I understand I’m asking if you guys just know
<ktz_[m]>
well I asume you can install any regular x86 distro with a current kernel and you'll prolly be fine, haven't done it just guessing, check yt
<life-the-user[m]>
ktz_[m]: I don’t care about macos, I need to be sure that I will successfully boot to Linux when everything except Linux required stuff is erased
<life-the-user[m]>
Bios isn’t stored on the hard drive right?
eroux has joined #asahi
<ktz_[m]>
well I only got exprience with m1 macbooks sorry, I'm sure you could find relevant stuff about installing alternative distros on youtube
<life-the-user[m]>
Uh ok
<life-the-user[m]>
<life-the-user[m]> "As I understood fingerprint..." <- ^?
<ktz_[m]>
but to your question about bricking it in general I assume you'll have to look into specifics for your machine
<ktz_[m]>
sorry, is this a 2017 mbp or not?
<ktz_[m]>
I mean they didn't have a fingerprint back then did they
<ktz_[m]>
I think people try to keep the chat low volume so they can skim through it, you'd better read the wiki page
<life-the-user[m]>
Eh
<life-the-user[m]>
Ok
<mps>
and, linux works fine for years on x86_64 macbooks
giskard has joined #asahi
<life-the-user[m]>
mps: Yeah I know, I want to ask about camera, speakers, lid, brightness support
<nicolas17>
hm don't know about lid detection actually
<mps>
life-the-user[m]: you should ask more clearly, what machine you mean
<life-the-user[m]>
Can I be certain that MacBook Pro 2015 will work perfectly on Linux?
<life-the-user[m]>
I have several machines
<mps>
life-the-user[m]: I have it on 2009 macbook
<life-the-user[m]>
MacBook Pro 2017 with least specs
<nicolas17>
there's no warranty so no :P
<life-the-user[m]>
mps: Other is some macbook from 2014-2015 I guess
<mps>
I didn't tested camera, though I think it works. all rest works fine
<mps>
ktz_[m]: I'll answer you question here. on my mbp temperature doesn't go high
<mps>
ktz_[m]: no difference with macos or linux
<ktz_[m]>
I was speculating that it could be something on the graphics stack eg wayland since you're running xorg the only difference that made sense in mysetup out of the box making a difference
<mps>
that could be reason
<mps>
but it shouldn't depend on distro then
<mps>
though I noticed that mbp bought at the end of 2021 is somewhat different from one bought at end of 2020
<mps>
new term: year diffs :)
<ktz_[m]>
yes it shouldn't, I'm running sway on alarm as well, I guess it's not the same version tho. I'll install it again and maybe stay on the tty for some time and see how it does
<ktz_[m]>
mps: namely? on the outside?
<mps>
no, just they are different in firmware I think
<ktz_[m]>
yes makes sense
<ktz_[m]>
have you got temp showing up now maybe?
<mps>
on this old one in xorg top line is drawn outside of display, i.e. invisible
<mps>
ktz_[m]: I read battery temp
<ktz_[m]>
yes the battery one
<mps>
290
<ktz_[m]>
did you have it working before as well?
<mps>
?
<ktz_[m]>
#_oftc_#asahi-offtopic:matrix.org
yamii has joined #asahi
jluthra has quit [Remote host closed the connection]
jluthra has joined #asahi
nicolas17 has quit [Quit: Konversation terminated!]
MajorBiscuit has joined #asahi
MajorBiscuit has quit []
MajorBiscuit has joined #asahi
MajorBiscuit has quit []
ptudor_ is now known as ptudor
w12101111 has joined #asahi
MajorBiscuit has joined #asahi
<mps>
hm, even 'dead' macbook pro trying to connect apple network
<ktz_[m]>
sounds like a zombie to me hehe
<mps>
power button couldn't power of it
<ktz_[m]>
such innocent machines...
<mps>
caps look led works
<mps>
lock*
<ktz_[m]>
if you ever take it apart don't forget film it I got a friend whos really interested in finding how to physically kill the transmitter
<mps>
it trying to connect to 17.57.146.22.5223
<mps>
and 'this site has requested that you identify yourself with a certificate'
<Sobek[m]>
marcan: I saw some of your can rust be used to prevent people from writing code that may dedalock (especially around the interupt disabling logic). Rust isn't design to solve that problem, but I wonder if one could do some things using fancy type system stuff and using custom lock that use these. When you acquire a lock you have to give it the current locking context, and it returns a new context, and when you release the lock it gves you back
<Sobek[m]>
the context, where those context encode the interesting info in their types. The interrupt disabling / enabling routine would also use these and require a context type that's incompatible with the one returned by locks.
<Sobek[m]>
I'd have to spend time trying out writing these sort of stuff to see if it works out and how heavy the syntax may be.
<m1n1m4[m]>
<mps> "kode54: thanks. but as I reading..." <- I am using it, with zero problems for weeks...
<Sobek[m]>
Also, it might be worth looking at what the redow folks did btw.
<j`ey>
Sobek[m]: the problem is passing that context/token to every function
<Sobek[m]>
Yep, that's the drawback at that point, perhaps macros could help though >:) Rust macros are powerful
<Sobek[m]>
I don't know the state of the art in kernel development / system programming research but I feel like what marcan is looking for probably is kind of close to the research bleeding edge.
mizuhiki has joined #asahi
<mizuhiki>
hello
<Sobek[m]>
Another way one could try out something like auditing logs and friends could be using a compiler plugin implementing a lint https://doc.rust-lang.org/1.5.0/book/compiler-plugins.html (And add flags in your config to make the lint warnings into compile errors)
<Sobek[m]>
(Then you could annotate functions to indicate their locking expectations and let the compiler shout at you until your annotation and the code match)
<j`ey>
Sobek[m]: this is like "no_panic" and stuff that doesnt exist in rust yet
mizuhiki has quit [Ping timeout: 480 seconds]
<Sobek[m]>
j`ey: What's exactly the no_panic you are referring to ? I've seen a crate that exploits the linker to make the compilation fail if certain functions cannot be proven not to panic.
eroux has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<j`ey>
Sobek[m]: I mean a theoretical attribute that can be put on a function to make the compiler error out if it can panic in anyway
<Sobek[m]>
There isn't an rfc for that apparently. Rust compiler plugins are a thing on nightly though. The API isn't quite stable but it does exist.
<Sobek[m]>
Now developping a plugin to track all these things requires some R&D work, as would a type system solution, but it could probably fit within the rust language
<marcan>
Sobek[m]: the problem is that's not practical since you'd have to pass around the context to literally every function call
<j`ey>
percpu globals!
<j`ey>
nvm that's runtime
<Sobek[m]>
(Well, you could use macro black magic to write code naturally and have it re-written at compile time to add those parameters, however that would be pretty heavy black magic)
METALLICA- has joined #asahi
METALLICA- has quit [Remote host closed the connection]
METALLICA- has joined #asahi
METALLICA- has quit [Remote host closed the connection]
METALLICA- has joined #asahi
Moprius has joined #asahi
tiagom has joined #asahi
METALLICA- has quit [Remote host closed the connection]
METALLICA- has joined #asahi
kov has joined #asahi
Ry_Darcy has joined #asahi
eroux has joined #asahi
METALLICA- has quit [Remote host closed the connection]
___nick___ has joined #asahi
___nick___ has quit []
jn has joined #asahi
tiagom has quit [Quit: WeeChat 3.5]
ricekot has quit [Quit: Connection closed for inactivity]
___nick___ has joined #asahi
Bai-Chiang has joined #asahi
al3xtjames has quit [Remote host closed the connection]
al3xtjames has joined #asahi
<cmalvi[m]>
Just for compatibility info:
<cmalvi[m]>
The Proton Mail Bridge works if you build from source the no-gui version, the gui version doesn't
Ry_Darcy has quit [Remote host closed the connection]
yuyichao has quit [Ping timeout: 480 seconds]
<m1n1m4[m]>
<Sobek[m]> "(Well, you could use macro black..." <- Sorry for my ignorance, just an idea. Would the community from this project have had the same issues you're describing? ( userspace/kernel)?
<m1n1m4[m]>
ah you mentioned something about the arm limitation, not x86
<m1n1m4[m]>
j`ey: ok ok
eroux has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
eNV25[m] has joined #asahi
yyyyyyyyyyyyyyyyyyyyyydrtdsea^ has quit [Ping timeout: 480 seconds]
yyyyyyyyyyyyyyyyyyyyyydrtdsea^ has joined #asahi
w12101111 has quit [Remote host closed the connection]
linearcannon has quit [Ping timeout: 480 seconds]
vovanoxin[m] has joined #asahi
vovanoxin[m]1 has joined #asahi
Bai-Chiang has quit [Quit: Konversation terminated!]
Bai-Chiang has joined #asahi
memoryleak_ has joined #asahi
memoryleak has quit [Ping timeout: 480 seconds]
vovanoxin has joined #asahi
vovanoxin has quit [Remote host closed the connection]
yyyyyyyyyyyyyyyyyyyyyydrtdsea^ has quit [Remote host closed the connection]
guillaume_g has quit []
Bai-Chiang has quit [Ping timeout: 480 seconds]
eroux has joined #asahi
MajorBiscuit has quit [Ping timeout: 480 seconds]
toranosora[m] has joined #asahi
hellstabber has joined #asahi
joannepaixa1312[m] has joined #asahi
Gaspare has joined #asahi
ptudor_ has joined #asahi
ptudor has quit [Read error: Connection reset by peer]
<joannepaixa1312[m]>
hey
Bai-Chiang has joined #asahi
garret has quit [Quit: WeeChat 3.4.1]
eNV25[m] has left #asahi [#asahi]
memoryleak has joined #asahi
memoryleak_ has quit [Ping timeout: 480 seconds]
___nick___ has quit []
___nick___ has joined #asahi
___nick___ has quit []
___nick___ has joined #asahi
axboe has joined #asahi
nicolas17 has joined #asahi
* nicolas17
reads log
<nicolas17>
mps: port 5223 is push notifications
<mps>
nicolas17: yes, but it could be used for other things, I have no idea for what apple uses it especially on hidden connections
<nicolas17>
something on 17.x.x.x and port 5223 is definitely Apple Push Notification Service, but Apple does use *that* for other things beyond user-visible notifications :)
<mps>
thanks for info. I blocked it on firewall just in case
<nicolas17>
the port?
<nicolas17>
it will probably fallback to 443 lol
<mps>
no, I blocked IP address of machine
<vovanoxin[m]1>
Hi, are there some task which require contribution? I am starting linux kernel dev, I think I may be useful
<mps>
nicolas17: I expect there is more, so IP blocking looks more reasonable
<nicolas17>
no you have that backwards, there's more IP than ports and I don't think you can even get all IPs
<nicolas17>
(they're probably spread all over 17.x.x.x)
<nicolas17>
why do you even want to block it?
<mps>
nicolas17: no, I blocked machine IP not apple network
<nicolas17>
ah *your* IP
<nicolas17>
okay makes sense
<mps>
there are two other m1 machines which uses macos in local net so they probably need some of this spying services
Gaspare has quit [Quit: Gaspare]
<cmalvi[m]>
is possible to map "delete" key to the power button in linux? (for macbook air)
Gaspare has joined #asahi
eroux has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
___nick___ has quit [Ping timeout: 480 seconds]
<mps>
cmalvi[m]: I think only on kernel level
<cmalvi[m]>
Oh that’s why I didn’t find anything useful only, thank you :)
eroux has joined #asahi
<mps>
cmalvi[m]: Fn+backspace is 'delete' key
<cmalvi[m]>
Yes I know, when I bought this MacBook, because is my first apple product, it took me a lot to figure out 😂
<cmalvi[m]>
But I thing have a dedicated delete button is better
<mps>
it is possible to remap left 'option' (or actually any) in userspace
mizuhiki has joined #asahi
jakebot has joined #asahi
mizuhiki has quit [Ping timeout: 480 seconds]
Bai-Chiang has quit [Ping timeout: 480 seconds]
mizuhiki has joined #asahi
<hpux735[m]>
Does anyone know how to disable hardware acceleration in gnome terminal? It's the easiest terminal for me to get "right" with my keyboard shortcuts, but it seems to be pretty dependent on some kind of graphical support that Avahi doesn't have yet :)
<mizuhiki>
I'm pretty sure there was a way
<mizuhiki>
give me a sec to look it up real quick
<mizuhiki>
from my quick google search it seems to just cause the system to crash out when disabled, and unfortunutly it seems you will need the gui
mizuhiki has quit [Quit: Lost terminal]
Gaspare has quit [Quit: Gaspare]
<hpux735[m]>
Wow. Ok, thanks so much for looking!
<hello9999901[m]>
<mps> "cmalvi: Fn+backspace is 'delete'..." <- That’s actually insane didn’t know that lol
eroux has quit [Ping timeout: 480 seconds]
Gaspare has joined #asahi
<cmalvi[m]>
<mps> "it is possible to remap left '..." <- Yes sure, I’ve remapped the keyboard like a “windows” one, so shortcuts are the same between my computers
<cmalvi[m]>
<hpux735[m]> "Does anyone know how to disable..." <- My gnome terminal works perfectly, what’s your problem? Maybe I could help you
<hpux735[m]>
cmalvi[m]: That would be awesome. I'm uploading a video
<cmalvi[m]>
Disable transparency
<cmalvi[m]>
If I remember correctly this is the problem
<cmalvi[m]>
* Disable transparency for gnome terminal
Gaspare has quit [Quit: Gaspare]
<hpux735[m]>
cmalvi[m]: oooh! This was the ticket. It wasn't "transparency" per se, but I assume that "Use colors from system theme" included transparency. Either way, that works. Thanks!!
<cmalvi[m]>
Glad you solved :)
eroux has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]