<chadmed>
joske: i cant seem to reproduce the bad reg sync here with my patches. fwiw i also didnt have any problem applying them to the latest asahi branch whatsoever, so the fact that you did might suggest youve left some cruft in your branch and things have fallen out of sync
austen has joined #asahi
<austen>
which browser can I use for DRM support in Asahi?
nicolas17 has quit [Quit: Konversation terminated!]
nicolas17 has joined #asahi
kode54 has quit [Quit: Ping timeout (120 seconds)]
kode54 has joined #asahi
kode54 has quit [Quit: Ping timeout (120 seconds)]
KDDLB has quit [Quit: Ping timeout (120 seconds)]
<austen>
I just want to watch videos from Udemy, can anyone help me, please?
<nicolas17>
Retr0id: did you get widevine to work on arm64 linux?
riker77_ has joined #asahi
riker77 has quit [Ping timeout: 480 seconds]
riker77_ is now known as riker77
<chadmed>
google dont publish an arm64 cdm afaik
<nicolas17>
they might for chromebooks, and Retr0id would be the kind of crazy person to try it
<chadmed>
chromeos userspace is 32 bit aiui
c10l63 has quit []
<nicolas17>
ah crap
c10l has joined #asahi
<austen>
widevine don't support for arm64 :D
<chadmed>
yeah
<chadmed>
theres no widevine blob at all for arm64 linux
<chadmed>
the only one that exists is for macos which is very funny
<nicolas17>
not Android either?
<chadmed>
android does the same thing as chromeos i think
<austen>
Is there any way to enable for asahi? Nothing?
<chadmed>
austen: no, its a proprietary blob provided by google and they do not provide one for the linux abi
<austen>
how can I watch Udemy videos, is there any ways?
<chadmed>
not if it relies on widevine
<nicolas17>
you should be glad that kind of DRM is available on x86 Linux nowadays :P
<nicolas17>
a decade ago a website like udemy would tell you to install a Windows-only browser plugin!
<nicolas17>
austen: reboot back into macOS
<chadmed>
windows media player drm popups when trying to play CDs were always fun
<psykose>
i hope we never go back to that
<refi64>
you can definitely get the binaries from Chrome OS, it's just a PITA to extract & involves pulling it from the recovery issue
<refi64>
I've long debating automating this somehow for a widevine extension for the flatpak, but it's just...tricky
<nicolas17>
refi64: yes but if it's arm32 it's not useful here
<refi64>
I'm quite sure it was arm64
<refi64>
okay no I lied it was arm32, rip
KDDLB has joined #asahi
kode545 has joined #asahi
kode545 is now known as kode54
austen has quit [Ping timeout: 480 seconds]
austen has joined #asahi
austen has quit []
marvin24 has joined #asahi
marvin24_ has quit [Ping timeout: 480 seconds]
mxz has quit [Quit: cya]
mxz has joined #asahi
jluthra has quit [Remote host closed the connection]
jluthra has joined #asahi
jamespmo_ has joined #asahi
kode54 has quit [Quit: Ping timeout (120 seconds)]
KDDLB has quit [Quit: Ping timeout (120 seconds)]
KDDLB has joined #asahi
kode54 has joined #asahi
jamespmorgan has quit [Ping timeout: 480 seconds]
aurelian has joined #asahi
<aurelian>
hey all, thanks for all the hard work on asahi.
<aurelian>
I was curious if anyone is running Gnome, I can't get the dark mode to work
aurelian has quit [Remote host closed the connection]
cdoltb^ has quit [Remote host closed the connection]
marvin24_ has joined #asahi
marvin24 has quit [Ping timeout: 480 seconds]
<corion>
Is there any way to feasibly figure out just how apple manages to get the touchpad so smooth in macos? Linux feels like a decade or two behind.
<corion>
Specifically the acceleration where you can scroll a page with high precision.
<corion>
I know about the https://linuxtouchpad.org/docs/ project, but was mostly wondering if there is anything asahi can/will add to the field of research.
kallisti has joined #asahi
<kallisti>
hey does anyone know how I can easily reset my password as I don't want to have to reinstall
<nicolas17>
the Linux login password?
<kallisti>
I tried setting kernel parameters via archlinux instructions, but wasn't able to access tty9 and the shell setting method I couldn't use my keyboard
<nicolas17>
were you able to modify the kernel parameters in grub?
<kallisti>
yes
<kallisti>
For 2) I couldn't use the shell it booted to
<kallisti>
For 3) I couldn't seem to find a key combo to bring me to tty9
<nicolas17>
hm did you get those numbers backwards?
<kallisti>
So they were both fruitless unfortunatly
<kallisti>
Yeah I got them backwards. My bad
<nicolas17>
(option 2 mentions tty9)
<nicolas17>
okay
<nicolas17>
does your Mac have a touchbar?
<kallisti>
No
<nicolas17>
(F9 gets more complicated in that case :P)
<nicolas17>
I suspect with the init=/bin/bash method you were hitting the "Some keyboards may not be loaded properly by the init system" issue
<kallisti>
Someone mentioned chrooting from a container or vm. But I don't have a guide handy for that
<kallisti>
That's probably it.
<mps_>
kallisti: fn+9
<nicolas17>
you need someone with more of a clue than me :p about how the keyboard is initialized, and/or how to enter tty9, and/or how to boot via USB...
<mps_>
also, it is possible with usb keyboard
<kallisti>
mps_: I think I got to the ttys with more keys that that. But only able to get tty5 & 6
<kallisti>
hmm I don't have a usb keyboard or a regular usb port
<kallisti>
seems like i'm up shits creek and reinstalling will be the easiest way :/
<mps_>
internal keyboard fn+NumberKeys are mapped to F keys
<nicolas17>
yeah but if they can get to tty5 and tty6 then they figured out the right key combo already
<kallisti>
yeah but I could only get to those ttys
<mps_>
then maybe nothing is running on tty5 and tty6
<kallisti>
So I think tty9 might be disabled
<kallisti>
No, I got login screens on tty5&6
<mps_>
aha, so nothing on tty9 is running?
<kallisti>
iirc yes
<kallisti>
probably got a blank screen when I tried entering that
<ncl>
are you the kallisti i knew
<kallisti>
i dunno what kallisti you knew
<kallisti>
from where idk
<mps_>
I know that mappings works very fine, tested it extensively when I wrote that patch.
<kallisti>
This will do a normal boot but start debug-shell.service which runs a root shell (/bin/sh) on tty9. Press Ctrl+Alt+F9 to access it.
<ncl>
rizon 10y ago
<kallisti>
Look from the archlinux docs they mention ctrl+alt+f9
<nicolas17>
mps_: the key mapping works since they can get to tty5; but tty9 isn't working so something else is up
<kallisti>
so what keys are you suggesting?
<mps_>
but if no process runs on tty than pressing fn+alt+N keys is useless
<kallisti>
I was sort of mashing keys but able to get to tty5&6
<kallisti>
no alt key on macOS keyboard
<mps_>
kallisti: alt is option or command
<ncl>
cmd=win option=alt
<kallisti>
Anyhow don't think it will work. But I will have to leave the chat to test as I'm in macOS now.
<mps_>
ncl: keys could be remapped when keyboard driver is loaded
<mps_>
boot from live usb stick, mount mvme root partition and reset password
<ncl>
oh if this is all about resetting the pw i think there's a cmdline you can stick in to force systemd into a root shell with no login
<nicolas17>
mps_: how do you boot from live usb stick? need to tell uboot or grub to load OS from there?
<kallisti>
mps_: yeah hmm unfortunately don't have a usb stick
<mps_>
nicolas17: yes, break u-boot and tell it to boot from usb
<kallisti>
er, perhaps i do have a nvme flash drive with usb c
<kallisti>
so what can i use to create a bootable image on an external flash drive?
<kallisti>
does the ashai install script work for that?
<ncl>
i forget the exact invocation but it's something with SYSTEMD_SULOGIN_FORCE
<mps_>
nicolas17: here is short guide how to boot from usb I wrote for alpine https://arvanta.net/alpine/install-alpine-m1/ and there are somewhere for debian and iirc for nixos somewhere
<kallisti>
Or that I should try to install to my usb c flash drive and chroot into the system and reset the password that way? Finally chrooting from docker or a vm on mac os would be nice because I wouldn't have to reboot (until testing if it worked)
<nicolas17>
mps_: if I understand correctly, that gets them a shell but the keyboard doesn't work
<nicolas17>
is there something in userspace loading keyboard firmware or something?
<mps_>
nicolas17: ah, driver is module and it is initramfs I guess
<nicolas17>
there you go
<ncl>
i'll test
<kallisti>
yeah so should I just try appending rescue systemd.setenv==SYSTEMD_SULOGIN_FORCE=1 now?
<kallisti>
with a single = ...
<mps_>
heh, that is why i built all basic drivers in-kernel and not as modules for alppine asahi kernel
<ncl>
yeah it works
<kallisti>
ok I will give it a shot. fingers crossed as I have already lost a couple hours tooling around :?
<kallisti>
;?
<kallisti>
;/
<ncl>
when you see grub pop up just tap 'e', arrow down to the line beginning with "linux", add "rescue systemd.setenv=SYSTEMD_SULOGIN_FORCE=1" to the end, fn+f10 to boot, enter when you reach a prompt
<ncl>
and you'll get a root shell
<kallisti>
yeah nice. I get the kernel params part. Thanks I will give it a shot!
kallisti has quit [Quit: reboot]
kode54 has quit [Quit: Ping timeout (120 seconds)]
kode54 has joined #asahi
kallisti has joined #asahi
<kallisti>
hmm yeah it said root account is locked or similar... didn't work :?
<kallisti>
;/
<kallisti>
tempting to just reinstall since it's burning all my time
<ncl>
weird, that's also the advice for getting past a locked root account but shrug i'd give up by now too
<kallisti>
yeah i dunno. I could try to boot chroot. I would probably be better off cause I wouldn't lose my config that way.
<kallisti>
But yeah, how should I build a bootable usb. And anyone have chroot instructions? I do these things once every 2-5 years ...
Versus34 has left #asahi [Leaving]
<kallisti>
Going to try to see if I can launch asahi from virtualbox on the mac. That would be pretty awesome and make this easier. Or if I could chroot from a virtual environment
<nicolas17>
well virtualbox would emulate a standard ARM64 system without the Mac's peculiarities, I'm not sure if the asahi kernel is configured to run on generic ARM systems too, but maybe
<mps_>
I tested with qemu on macos, and it is possible to mount linux partitions on it and do changes
<mps_>
generic arm kernel, not asahi is needed in VM
<nicolas17>
asahi kernel is not needed in VM, but does it *work* in VM?
<mps_>
nicolas17: asahi kernel could be compiled to run in VM ofc, but it is not needed
<nicolas17>
yeah I'm asking if the shipped .config supports running in a generic VM :P
<kallisti>
It looks like there is a virtualbox beta for macOS. But I have no idea how I would boot ashai using it, or using qemu
kode54 has quit [Quit: Ping timeout (120 seconds)]
KDDLB has quit [Quit: Ping timeout (120 seconds)]
<kallisti>
Hmm it looks like I'm going to have to reinstall unless I want to spend all weekend tooling around.
<nicolas17>
kallisti: I'm not sure if the asahi kernel will work in the VM, but what you *can* do is boot a normal arm64 linux and then mount the asahi partition from there
SSJ_GZ has joined #asahi
<kallisti>
nicolas17: Ahh ok. Yeah I thought about that. I have vbox running now. Guess I could get one of these prebuilt orcas linux builds
<kallisti>
looks like I'll give UTM a shot then...
<kallisti>
ahh, much easier. Now I just need to launch and chroot into the asahi install
<kallisti>
any hints on chrooting?
nicolas17 has quit [Ping timeout: 480 seconds]
<kallisti>
Anyone know how to access the filesystem from UTM to chroot into ashai to fix my password problem?
<ChaosPrincess>
If you have spare disk space, maybe install a second copy via installer, reset the password and then delete it?
<kallisti>
ChaosPrincess: so not possible to chroot into it from UTM / qemu, since I have that running?
<ChaosPrincess>
Probably possible, i just have no idea how to passthrough the disk to the vm :P
<kallisti>
Yeah, that makes sense. Was going to say something like mac OS probably doesn't understand the filesystem, so not sure how the host would pass it on to the VM
<ChaosPrincess>
The os does not matter
<ChaosPrincess>
And qemu defo can do it, you just put /dev/disk$something where you normally put the qcow file
<kallisti>
Have UTM installed, think it's a wrapper around qemu
<kallisti>
Not sure about what a qcow file is
<kallisti>
not sure what /dev/disk$something we're discussing here? The /dev/disk$something path to where asahi is installed?
<kallisti>
Guess I can try to play with qemu for a minute. Don't see /dev/disk* partitions via UTM
<kallisti>
I'm not even sure which partition to specify. I take a look in disk utility and it looks like I'm missing some details there, but I do see some small partitions for Asahi there.
<kallisti>
Seems like I want to do something like `qemu-system-arm64 -kernel bzImage -hda rootdisk.img -append "root=/dev/disk2s1" or `qemu-system-arm64 -kernel bzImage -hda rootdisk.img -append "root=/dev/disk2s2"
<kallisti>
``` qemu-system-aarch64 -kernel bzImage -hda rootdisk.img -append "root=/dev/disk2s1" -machine virt-7.2 qemu-system-aarch64: -hda rootdisk.img: Could not open 'rootdisk.img': No such file or directory```
<mps_>
something like '-drive if=virtio,id=hd1,format=raw,file=/dev/disk0s6`
<kallisti>
seems like it's hanging so I assume I need to try a different /dev/disk0s* volume
<kallisti>
Think it would give me an error if it didn't exist however
<mps_>
I use plain qemu without any of these easy of use layers
<kallisti>
mps_: the example looks handy. Any way to get the partition layout correct from macos so I[m not iterating?
<mps_>
kallisti: I have not much experience with macos, but I think diskutil can give you hints what is what
<kallisti>
yeah as above I mentioned i see 2s1 and 2s2 in du but I think these might not be right
<kallisti>
your script returned qemu-system-aarch64: -soundhw: invalid option . guess my qemu don't have that option
<mps_>
yes, iirc in last qemu this option is changed/removed
<mps_>
for rescue I guess sound is not needed anyway ;)
dgb has joined #asahi
<kallisti>
i'm getting no such file m1 and after setting the values to 2s1 and 2s2. about to try to write a for loop to iterate over the damn values...
<dgb>
diskutil list
<ChaosPrincess>
The correct one is disk0
<ChaosPrincess>
but mac os may complain
javier_varez_ has quit [Quit: Connection closed for inactivity]
<mps_>
I have no experience with UTM, sorry can't help with it
<mps_>
I only tested with alpine iso and I know it works
<mps_>
but if it works with alpine iso I don't see any reason it will not work with other distros iso
<corion>
I have a question regarding the kde plasma menu. It seems there is a slight lag (with gpu drivers), but I get almost no lag in something like supertuxkart. How is that? Do I need to adjust something in kde?
<mps_>
and you will have ready usb rescue system in case you need it later
<kallisti>
Since I have spent this much time trying to get qemu working, it seems that would be ideal. It looks like you're chrooting asahi from qemu. That would help me to have a bridge between the two.
<kallisti>
Like we're 95% there, and all I need is a working image now
<mps_>
yes, that will also helpful
Tano70 has joined #asahi
<kallisti>
So what's the fastest way to a non-utm image that I can use against qemu?