ChanServ 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
pb17 has quit [Ping timeout: 480 seconds]
zumi has quit [Remote host closed the connection]
zumi has joined #asahi
pb17 has joined #asahi
chrisl has joined #asahi
chrisl has quit [Ping timeout: 480 seconds]
malte_ has joined #asahi
malte has quit [Ping timeout: 480 seconds]
chrisl has joined #asahi
chrisl has quit [Ping timeout: 480 seconds]
ddxtanx has joined #asahi
pb17 has quit [Ping timeout: 480 seconds]
pb17 has joined #asahi
ddxtanx has quit [Remote host closed the connection]
tobhe_ has joined #asahi
ddxtanx has joined #asahi
tobhe has quit [Ping timeout: 480 seconds]
Brainium has quit [Quit: Konversation terminated!]
deflax has quit [Quit: Ping timeout (120 seconds)]
zumi_ has joined #asahi
zumi has quit [Remote host closed the connection]
pb17 has quit [Ping timeout: 480 seconds]
zumi_ is now known as zumi
deflax has joined #asahi
ciara has quit [Remote host closed the connection]
ciara has joined #asahi
pb17 has joined #asahi
MichaelLong has quit []
<quaff>
Hm. I just did an upgrade and I am noticing that my touchbar service (tiny-dfr.service) is failing to run. I'm not seeing any errors in any logs. but when I run `tiny-dfr` manually, I see this error:
<quaff>
thread 'main' panicked at src/display.rs:31:33:called `Result::unwrap()` on an `Err` value: Os { code: 22, kind: InvalidInput, message: "Invalid argument" }
<quaff>
is anyone else having this issue? (macbook pro 13" m1)
<quaff>
ah! okay. so it was a regression. all good! thanks LarstiQ! I'll stop picking at it for now 🙏
MichaelLong has joined #asahi
chrisl has joined #asahi
chrisl has quit [Ping timeout: 480 seconds]
<jannau>
quaff: I don't think that was causing rust panics just non-working touch input. Which device and which kernel version is this?
<quaff>
jannau: macbook pro 13" m1 2020, 6.12.1-404.asahi.fc41.aarch64+16k
Sebastian2 has joined #asahi
WindowPain has quit [Quit: Ping timeout (120 seconds)]
WindowPain has joined #asahi
WindowPain0 has joined #asahi
WindowPain has quit [Remote host closed the connection]
WindowPain0 is now known as WindowPain
pb17 has quit [Ping timeout: 480 seconds]
<quaff>
jannau: I don't know if this makes a difference... but full disclosure, I installed displaylink drivers earlier today (bought a dock from a cybermonday sale), not sure if me mucking with dkms modules affects this or not.
<jannau>
quaff: the regression is supposed to fixed with 6.12.1-404.asahi (and confirmed elsewhere)
<quaff>
okay so it's probably the displaylink drivers. I'll see if I can uninstall them and try again
<jannau>
rust panic is probably expected if you run tiny-dfr as user
<quaff>
ah
<quaff>
my tiny-dfr.service is in a failed state. are there logs I can check to see a more detailed error?
<jannau>
what does `systemctl status tiny-dfr.service` output directly after the startup?
<quaff>
Dec 03 00:14:11 Pluto systemd[1]: tiny-dfr.service: Scheduled restart job, restart counter is at 5.
<quaff>
tiny-dfr.service: Start request repeated too quickly.
<quaff>
tiny-dfr.service: Failed with result 'exit-code'.
<quaff>
I see that
<jannau>
`journalctl -k -g display-pipe` and `journalctl -k -g 'Touch Bar'` should output 2 or 1 line which don't look like errors
pb17 has joined #asahi
<quaff>
Nov 13 16:00:00 Pluto kernel: adp 228200000.display-pipe: Adding to iommu group
<quaff>
Nov 13 16:00:00 Pluto kernel: [drm] Initialized adp 0.1.0 for 228200000.display-pipe on minor 5
<quaff>
Dec 03 00:16:47 Pluto kernel: input: MacBookPro17,1 Touch Bar as /devices/platform/soc/235100000.spi/spi_master/spi0/spi0.0/input/input2
<quaff>
first two is from the first command, third is from the last one
<jannau>
does /proc/device-tree/soc/spi@235100000/cs-gpios" exists?
<quaff>
nope
<quaff>
but I see "/proc/device-tree/soc/spi@235100000/touchbar@0/cs-gpios"
<chaos_princess>
run `ls -la /dev/dri/` please
u154ss has joined #asahi
<jannau>
quaff: is you're boot partition full? that looks like the device tree wasn't propagated to /boots/efi/m1n1/boot.bin
<u154ss>
@all yes, I know the question is premature, but I will ask anyway. Currently running an M2 mini, will be taking delivery of an M4 Mini Pro (64GB) this week. Any ideas on an installer timeline? Can I pull any data off the machine to help?
<jannau>
chaos_princess: there are two issues. touch input won't work after fixing the panic
<chaos_princess>
u154ss: installer specifically - thats like a 10 line change, but it will not help as there are a lot more things to be done. On actual support - no timeline, but from my baseless speculation - more than 3 months
<chaos_princess>
jannau: yep, but that one is an issue too
<quaff>
chaos_princess: ah.. okay. seems the displaylink uninstall script didn't clean everything out, so I'll dig a bit more there.
<jannau>
so display-link just creates dummy drm devices which fail to open. I really need to get dp-altmode shipped
<u154ss>
@chaos_princess thanks for the information. Again, it it helps, I can extract data from the hardware.
<chaos_princess>
quaff: would you mind sending me the guide you followed to install displaylink drivers, i will add "make tiny-dfr tolerant of those" to my task pile
<quaff>
I'm guessing the displaylink script installed the wrong kernel packages
<quaff>
dp-altmode would be dope, but I think there's space for displaylink, given that everything I read says we can only have 1 external monitor with some of these macs. I am sure some people will keep using them after the release of dp-altmode (whenever it's ready!!).
ariejan47 has quit [Quit: Ping timeout (120 seconds)]
ariejan47 has joined #asahi
ariejan47 has quit [Ping timeout: 480 seconds]
sand4rt has joined #asahi
<janrinze>
quaff: is displaylink stable on your system? I have tried it for a few weeks but decided that it is too unstable for me.
Moprius has joined #asahi
<quaff>
janrinze: I’ll update you on it tomorrow! I am just waiting for the delivery 🫡
<janrinze>
quaff: Okay, hope you have a beter experience than I had.
chrisl has joined #asahi
chrisl has quit [Ping timeout: 480 seconds]
Sebastian2 has joined #asahi
verlio has quit [Ping timeout: 480 seconds]
Sebastian2 has quit []
<LarstiQ>
janrinze, quaff: what compositor are you using? Iirc wlroots based ones seems to have become slower with displaylink
Calandracas has quit [Remote host closed the connection]
Calandracas has joined #asahi
<janrinze>
LarstiQ: Regarding speed, the display link is sort-of a framebuffer device. I suspect that there is accelerated graphics to fill the framebuffer but generally speaking this is a very slow update solution..
<janrinze>
LarstiQ: actually it makes the entire desktop pretty slow, even the HDMI connected monitor shows slow screen updates.
phire has quit [Read error: Connection reset by peer]
phire has joined #asahi
chrisl has joined #asahi
Gue___________________________ has joined #asahi
chrisl has quit [Ping timeout: 480 seconds]
verlio has quit [Ping timeout: 480 seconds]
verlio has joined #asahi
pb17 has quit [Ping timeout: 480 seconds]
sprokkel has joined #asahi
pb17 has joined #asahi
gi0 has joined #asahi
verlio has quit [Remote host closed the connection]
verlio has joined #asahi
bitcl has joined #asahi
<bitcl>
hi
Sebastian2 has joined #asahi
Sebastian2 has quit [Quit: Sebastian2]
Sebastian2 has joined #asahi
Sebastian2 has quit []
kaazoo has joined #asahi
chrisl has joined #asahi
chrisl has quit [Ping timeout: 480 seconds]
Sebastian2 has joined #asahi
Sebastian2 has quit []
sand4rt has quit [Ping timeout: 480 seconds]
pb17 has quit [Ping timeout: 480 seconds]
sand4rt has joined #asahi
pb17 has joined #asahi
ddxtanx has quit [Remote host closed the connection]
bitcl has quit [Quit: Leaving]
nicolas17 has joined #asahi
<nicolas17>
hi
<nicolas17>
I just booted my asahi volume after several months, there's a system upgrade with 504 packages, and it says it will uninstall kernel-16k... does the standard kernel support 16k now or what?
<j`ey>
is it also installing a kernel-16k?
<nicolas17>
ah I see, I already upgraded to fc40 but I still had kernel-16k from fc39 installed, so now it's removing *that*
<nicolas17>
one minor annoyance I noticed on my last update is that I have the default boot volume set to macOS
<nicolas17>
after downloading updates, it reboots into macOS, I have to hold power to get to the boot menu and select fedora
chrisl has joined #asahi
<nicolas17>
it boots into the offline-upgrade environment, installs updates, reboots again... into macOS
<nicolas17>
does nvram have any way to *temporarily* change the default boot volume? it would be useful if "install updates and restart" GUI button would reboot into fedora just once...
<j`ey>
asahi-bless has a next-boot
<nicolas17>
hm nice so iBoot does have that feature
chrisl has quit [Ping timeout: 480 seconds]
mkurz has quit [Quit: Konversation terminated!]
mkurz has joined #asahi
<nicolas17>
does the Riven 2023 remake work on Asahi? the answer is unfortunately not