marcan changed the topic of #asahi to: Asahi Linux: porting Linux to Apple Silicon macs | "Does XXX work yet?": https://alx.sh/fs | GitHub: https://alx.sh/g | Wiki: https://alx.sh/w | Topics: #asahi-dev #asahi-re #asahi-gpu #asahi-alt #asahi-stream #asahi-offtopic | Keep things on topic | Logs: https://alx.sh/l/asahi
Nokurn has quit [Ping timeout: 480 seconds]
Tramtris1 is now known as Tramtrist
loading is now known as idk
<idk>
now a question about weechat
<idk>
how is it that this server is able to transmit our usernames?
<idk>
for instance: (~gi0@185.253.160.139)
<idk>
(marcan@marcansoft.com)
<idk>
I've always figured that the people on the other side of an irc couldn't see anything about my linux instance (other than my ip ofc_
<psykose>
that's just irc stuff
<ellyq>
host@ip? that's just how IRC works
<psykose>
nick!~username@ip (realname)
<psykose>
1,2,4 you can change to anything in client
<psykose>
well, @host is more accurate, and it can be cloaked
<idk>
@ellyq that can't be true. There is no reason a messaging protocol needs to know my actual login username
<psykose>
it's not your actual login username
<psykose>
it's what your client sends
<psykose>
and most of them send your current username
<idk>
that makes more sense
<idk>
I'll look into the clientside settings then
<idk>
ty
<idk>
@psykose do you know how to change this in weechat? before I go looking in all the wrong places
<psykose>
/set irc.server.<name of server>.username "someusername"
<psykose>
same for .realname and .nicks (which is "nick1,nick2,nick3" in preference order)
i509vcb has quit [Quit: Connection closed for inactivity]
<gill6151>
Hey anyone know if you can live boot asahi without installing
ptudor has quit [Ping timeout: 480 seconds]
<ChaosPrincess>
the short answer is no
<nsklaus_>
^ maybe this is indication that question belong to a faq somewhere
<nsklaus_>
after being asked so often
ptudor has joined #asahi
darkapex has quit [Remote host closed the connection]
<nsklaus_>
ChaosPrincess: after installing just the uboot and efi mode, from the installer, maybe then, livecd would boot ? (for the distro that have support merged in already)
<ChaosPrincess>
yes, but you are still installing apfs and esp at this point
<nsklaus_>
i was just confirming that possibility
<nsklaus_>
which ..
<nsklaus_>
make me think.. there are updated iso out there
<nsklaus_>
maybe a spin of fedora, or others too, if i installed just the uboot + efi mode from the installer and tried to boot from those iso,
<nsklaus_>
ChaosPrincess: that could maybe solve the broken keyboard and trackpad i had when i attempted to install plain asahi (due to an updated uboot being necessary)
<nsklaus_>
?
<nsklaus_>
do you think that have a chance to work ?
<ChaosPrincess>
its the same u-boot as asahi install
<nsklaus_>
ah so those spin off iso aren't updated yet then .. i see .. thank you for telling
<nsklaus_>
hum not even those iso, it's the uboot itself.. ok
ptudor has quit [Ping timeout: 480 seconds]
<TheDcoder>
j`ey: Hi
<j`ey>
hi
<TheDcoder>
Is it true that Asahi is switching distro?
<j`ey>
TheDcoder: markan has posted a bunch of times about ALARM on here and mastodon
<flatz>
hi. i'm experiencing some problem with DCP on M2 Mini, display is external connected via HDMI. that's logs from m1n1 (first is during cold boot, second is after chainloading of m1n1 itself): https://pastebin.com/2cMzdhUL
<flatz>
and when i try to boot stock/development macOS kernel (13.2.1) via run_guest.py, i'm getting panic: panic(cpu 1 caller 0xfffffe0016625038): "RTBuddy(DCP)::_setManagedStateGated " "No response received in 20s, DCP not started? (4)" "\nRTBuddy(AP): Debug info: _iopStatus = 0x4 _powerStateChangeLocked = true Mailbox Status: IDLE_STATUS: 0x00000008 INBOX0_CTRL: 0x00200201 OUTBOX0_CTRL: 0x00020001
<flatz>
any ideas?
<loading>
[
<jannau>
flatz: update m1n1, it should reject to initialize dcp on m2/m2 pro mac minis since v1.2.8
<flatz>
thanks, i'll try soon
<jannau>
ee
<jannau>
see commit 076217a8026188bf5fc3545c5f7ee763ad492a4d
loading_ has joined #asahi
karpouzi has joined #asahi
possiblemeatball has joined #asahi
loading has quit [Ping timeout: 480 seconds]
mkurz has joined #asahi
rootbeerdan1 has joined #asahi
rootbeerdan has quit [Ping timeout: 480 seconds]
rootbeerdan1 is now known as rootbeerdan
delsol has joined #asahi
rvalue has joined #asahi
rvalue- has quit [Read error: Connection reset by peer]
<flatz>
jannau: thank you a lot, it works now
rvalue has quit [Ping timeout: 480 seconds]
rvalue has joined #asahi
linuxgemini180248 has quit []
linuxgemini180248 has joined #asahi
ptudor has quit [Ping timeout: 480 seconds]
ptudor has joined #asahi
<karpouzi>
mps: continuing from #asahi-dev, even with the usize fix, the fp-armv8 warning trips an error
<ChaosPrincess>
delete -Werror ?
<mps>
hm, I thought -Werror is not in defaults
possiblemeatball has quit [Quit: Quit]
<mps>
CONFIG_WERROR is not set
<karpouzi>
hmm, well it didn't error out this time
<karpouzi>
7x instances of the unknown fp-armv8 feature warning
<mps>
it doesn't make kernel problematic, works fine even with this warning
giskard has quit [Quit: My iMac has gone to sleep. ZZZzzz…]