#
…

2022-12-18

00:16jacksonchen666 has quit [Remote host closed the connection]
00:16jacksonchen666 has joined #asahi
00:24c10l63 has joined #asahi
00:30jamespmorgan has joined #asahi
00:31c10l6 has quit [Ping timeout: 480 seconds]
00:36jamespm__ has quit [Ping timeout: 480 seconds]
00:54jacksonchen666 has quit [Ping timeout: 480 seconds]
00:55jacksonchen666 has joined #asahi
00:55swaggie has joined #asahi
01:36lea_ has joined #asahi
01:37lea_ has quit []
01:47leaneko has joined #asahi
01:52leaneko has quit [Quit: Textual IRC Client: www.textualapp.com]
01:55leaneko has joined #asahi
01:58leaneko has quit [Quit: Textual IRC Client: www.textualapp.com]
02:07chadmedjoske: 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
02:24austen has joined #asahi
02:25austenwhich browser can I use for DRM support in Asahi?
02:30nicolas17 has quit [Quit: Konversation terminated!]
02:31nicolas17 has joined #asahi
02:35kode54 has quit [Quit: Ping timeout (120 seconds)]
02:35kode54 has joined #asahi
02:43kode54 has quit [Quit: Ping timeout (120 seconds)]
02:43KDDLB has quit [Quit: Ping timeout (120 seconds)]
02:54austenI just want to watch videos from Udemy, can anyone help me, please?
02:55nicolas17Retr0id: did you get widevine to work on arm64 linux?
03:01riker77_ has joined #asahi
03:01riker77 has quit [Ping timeout: 480 seconds]
03:01riker77_ is now known as riker77
03:02chadmedgoogle dont publish an arm64 cdm afaik
03:04nicolas17they might for chromebooks, and Retr0id would be the kind of crazy person to try it
03:10chadmedchromeos userspace is 32 bit aiui
03:11c10l63 has quit []
03:11c10l has joined #asahi
03:12austenwidevine don't support for arm64 :D
03:13chadmedtheres no widevine blob at all for arm64 linux
03:13chadmedthe only one that exists is for macos which is very funny
03:13nicolas17not Android either?
03:13chadmedandroid does the same thing as chromeos i think
03:14austenIs there any way to enable for asahi? Nothing?
03:14chadmedausten: no, its a proprietary blob provided by google and they do not provide one for the linux abi
03:15austenhow can I watch Udemy videos, is there any ways?
03:16chadmednot if it relies on widevine
03:17nicolas17you should be glad that kind of DRM is available on x86 Linux nowadays :P
03:17nicolas17a decade ago a website like udemy would tell you to install a Windows-only browser plugin!
03:19nicolas17austen: reboot back into macOS
03:19chadmedwindows media player drm popups when trying to play CDs were always fun
03:20psykosei hope we never go back to that
03:35refi64you can definitely get the binaries from Chrome OS, it's just a PITA to extract & involves pulling it from the recovery issue
03:35refi64I've long debating automating this somehow for a widevine extension for the flatpak, but it's just...tricky
03:35nicolas17refi64: yes but if it's arm32 it's not useful here
03:36refi64I'm quite sure it was arm64
03:36refi64okay no I lied it was arm32, rip
03:39KDDLB has joined #asahi
03:44kode545 has joined #asahi
03:44kode545 is now known as kode54
04:00austen has quit [Ping timeout: 480 seconds]
04:27austen has joined #asahi
04:28austen has quit []
04:29marvin24 has joined #asahi
04:32marvin24_ has quit [Ping timeout: 480 seconds]
04:41mxz has quit [Quit: cya]
04:43mxz has joined #asahi
05:09jluthra has quit [Remote host closed the connection]
05:09jluthra has joined #asahi
05:13jamespmo_ has joined #asahi
05:18kode54 has quit [Quit: Ping timeout (120 seconds)]
05:18KDDLB has quit [Quit: Ping timeout (120 seconds)]
05:18KDDLB has joined #asahi
05:19kode54 has joined #asahi
05:19jamespmorgan has quit [Ping timeout: 480 seconds]
06:22aurelian has joined #asahi
06:22aurelianhey all, thanks for all the hard work on asahi.
06:22aurelianI was curious if anyone is running Gnome, I can't get the dark mode to work
07:00aurelian has quit [Remote host closed the connection]
07:09cdoltb^ has quit [Remote host closed the connection]
07:33marvin24_ has joined #asahi
07:36marvin24 has quit [Ping timeout: 480 seconds]
07:38corionIs 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.
07:39corionSpecifically the acceleration where you can scroll a page with high precision.
07:40corionI 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.
07:48kallisti has joined #asahi
07:49kallistihey does anyone know how I can easily reset my password as I don't want to have to reinstall
07:49nicolas17the Linux login password?
07:50kallistiI 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
07:50kallistinicolas17: yeah
07:51nicolas17were you able to modify the kernel parameters in grub?
07:51kallistiFor 2) I couldn't use the shell it booted to
07:51kallistiFor 3) I couldn't seem to find a key combo to bring me to tty9
07:52nicolas17hm did you get those numbers backwards?
07:52kallistiSo they were both fruitless unfortunatly
07:52kallistiYeah I got them backwards. My bad
07:52nicolas17(option 2 mentions tty9)
07:53nicolas17does your Mac have a touchbar?
07:53nicolas17(F9 gets more complicated in that case :P)
07:54nicolas17I suspect with the init=/bin/bash method you were hitting the "Some keyboards may not be loaded properly by the init system" issue
07:54kallistiSomeone mentioned chrooting from a container or vm. But I don't have a guide handy for that
07:54kallistiThat's probably it.
07:55mps_kallisti: fn+9
07:55nicolas17you 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...
07:56mps_also, it is possible with usb keyboard
07:56kallistimps_: I think I got to the ttys with more keys that that. But only able to get tty5 & 6
07:56kallistihmm I don't have a usb keyboard or a regular usb port
07:57kallistiseems like i'm up shits creek and reinstalling will be the easiest way :/
07:57mps_internal keyboard fn+NumberKeys are mapped to F keys
07:57nicolas17yeah but if they can get to tty5 and tty6 then they figured out the right key combo already
07:58kallistiyeah but I could only get to those ttys
07:58mps_then maybe nothing is running on tty5 and tty6
07:58kallistiSo I think tty9 might be disabled
07:58kallistiNo, I got login screens on tty5&6
07:59mps_aha, so nothing on tty9 is running?
08:00kallistiprobably got a blank screen when I tried entering that
08:00nclare you the kallisti i knew
08:00kallistii dunno what kallisti you knew
08:01kallistifrom where idk
08:01mps_I know that mappings works very fine, tested it extensively when I wrote that patch.
08:02kallistiThis 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.
08:02nclrizon 10y ago
08:02kallistiLook from the archlinux docs they mention ctrl+alt+f9
08:02nicolas17mps_: the key mapping works since they can get to tty5; but tty9 isn't working so something else is up
08:02kallistiso what keys are you suggesting?
08:02mps_but if no process runs on tty than pressing fn+alt+N keys is useless
08:02kallistiI was sort of mashing keys but able to get to tty5&6
08:03kallistino alt key on macOS keyboard
08:03mps_kallisti: alt is option or command
08:03nclcmd=win option=alt
08:04kallistiAnyhow don't think it will work. But I will have to leave the chat to test as I'm in macOS now.
08:04mps_ncl: keys could be remapped when keyboard driver is loaded
08:06kallistincl: idk rizon
08:06mps_boot from live usb stick, mount mvme root partition and reset password
08:07ncloh 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
08:07nicolas17mps_: how do you boot from live usb stick? need to tell uboot or grub to load OS from there?
08:07kallistimps_: yeah hmm unfortunately don't have a usb stick
08:07mps_nicolas17: yes, break u-boot and tell it to boot from usb
08:07kallistier, perhaps i do have a nvme flash drive with usb c
08:08kallistiso what can i use to create a bootable image on an external flash drive?
08:08kallistidoes the ashai install script work for that?
08:08ncli forget the exact invocation but it's something with SYSTEMD_SULOGIN_FORCE
08:09mps_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
08:13kallistincl: do we set environment like we do kernel parameters? I am really just an ignorant end user so idk these things
08:13nclyes but systemd can set envvar based on kernel cmdline if you eg. interrupt grub and append to it
08:15kallistiSo is the concensus I should try entering kernel parameter SYSTEMD_SULOGIN_FORCE=1 and hope that I can login like that from tty5 or 6?
08:15mps_does 'init=/bin/sh' works
08:16nclnot usually anymore with systemd, if it does it's still a bit of a pain but uh
08:16ncl'rescue systemd.setenv=SYSTEMD_SULOGIN_FORCE=1'
08:16kallistiOr 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)
08:16nicolas17mps_: if I understand correctly, that gets them a shell but the keyboard doesn't work
08:16nicolas17is there something in userspace loading keyboard firmware or something?
08:16mps_nicolas17: ah, driver is module and it is initramfs I guess
08:16nicolas17there you go
08:17ncli'll test
08:17kallistiyeah so should I just try appending rescue systemd.setenv==SYSTEMD_SULOGIN_FORCE=1 now?
08:18kallistiwith a single = ...
08:18mps_heh, that is why i built all basic drivers in-kernel and not as modules for alppine asahi kernel
08:18nclyeah it works
08:18kallistiok I will give it a shot. fingers crossed as I have already lost a couple hours tooling around :?
08:18nclwhen 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
08:18ncland you'll get a root shell
08:19kallistiyeah nice. I get the kernel params part. Thanks I will give it a shot!
08:19kallisti has quit [Quit: reboot]
08:20kode54 has quit [Quit: Ping timeout (120 seconds)]
08:21kode54 has joined #asahi
08:28kallisti has joined #asahi
08:28kallistihmm yeah it said root account is locked or similar... didn't work :?
08:29kallistitempting to just reinstall since it's burning all my time
08:31nclweird, that's also the advice for getting past a locked root account but shrug i'd give up by now too
08:32kallistiyeah i dunno. I could try to boot chroot. I would probably be better off cause I wouldn't lose my config that way.
08:33kallistiBut yeah, how should I build a bootable usb. And anyone have chroot instructions? I do these things once every 2-5 years ...
08:35Versus34 has left #asahi [Leaving]
08:38kallistiGoing 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
08:39nicolas17well 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
08:44mps_I tested with qemu on macos, and it is possible to mount linux partitions on it and do changes
08:44mps_generic arm kernel, not asahi is needed in VM
08:44nicolas17asahi kernel is not needed in VM, but does it *work* in VM?
08:45mps_nicolas17: asahi kernel could be compiled to run in VM ofc, but it is not needed
08:46nicolas17yeah I'm asking if the shipped .config supports running in a generic VM :P
08:47kallistiIt looks like there is a virtualbox beta for macOS. But I have no idea how I would boot ashai using it, or using qemu
08:48kode54 has quit [Quit: Ping timeout (120 seconds)]
08:48KDDLB has quit [Quit: Ping timeout (120 seconds)]
08:48kallistiHmm it looks like I'm going to have to reinstall unless I want to spend all weekend tooling around.
08:48nicolas17kallisti: 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
08:49SSJ_GZ has joined #asahi
08:49kallistinicolas17: Ahh ok. Yeah I thought about that. I have vbox running now. Guess I could get one of these prebuilt orcas linux builds
08:50nicolas17ah crap, sunrise >.>
08:56kallistilooks like I'll give UTM a shot then...
08:58kallistiahh, much easier. Now I just need to launch and chroot into the asahi install
08:58kallistiany hints on chrooting?
08:59nicolas17 has quit [Ping timeout: 480 seconds]
09:01kallistiAnyone know how to access the filesystem from UTM to chroot into ashai to fix my password problem?
09:04ChaosPrincessIf you have spare disk space, maybe install a second copy via installer, reset the password and then delete it?
09:07kallistiChaosPrincess: so not possible to chroot into it from UTM / qemu, since I have that running?
09:09ChaosPrincessProbably possible, i just have no idea how to passthrough the disk to the vm :P
09:10kallistiYeah, 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
09:10ChaosPrincessThe os does not matter
09:11ChaosPrincessAnd qemu defo can do it, you just put /dev/disk$something where you normally put the qcow file
09:12kallistiHave UTM installed, think it's a wrapper around qemu
09:13kallistiNot sure about what a qcow file is
09:15kallistinot sure what /dev/disk$something we're discussing here? The /dev/disk$something path to where asahi is installed?
09:16kallistiGuess I can try to play with qemu for a minute. Don't see /dev/disk* partitions via UTM
09:21ChaosPrincessPmuch that. Format=raw is the important bit
09:28kallistiI'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.
09:31kallistiSeems 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"
09:33kallisti``` 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```
09:33mps_something like '-drive if=virtio,id=hd1,format=raw,file=/dev/disk0s6`
09:33kallistimps_: have you tried that?
09:34mps_kallisti: here is my complete qemu start script https://tpaste.us/vyPY
09:34mps_ofc, you need to adapt it to your case
09:35mps_though, my advice is to use my usb image and boot it from usb-c
09:35kallistisudo qemu-system-aarch64 -drive if=virtio,id=hd1,format=raw,file=/dev/disk0s6 -machine virt-7.2
09:36kallistiseems like it's hanging so I assume I need to try a different /dev/disk0s* volume
09:36kallistiThink it would give me an error if it didn't exist however
09:36mps_I use plain qemu without any of these easy of use layers
09:37kallistimps_: the example looks handy. Any way to get the partition layout correct from macos so I[m not iterating?
09:38mps_kallisti: I have not much experience with macos, but I think diskutil can give you hints what is what
09:41kallistiyeah as above I mentioned i see 2s1 and 2s2 in du but I think these might not be right
09:41kallistiyour script returned qemu-system-aarch64: -soundhw: invalid option . guess my qemu don't have that option
09:42mps_yes, iirc in last qemu this option is changed/removed
09:42mps_for rescue I guess sound is not needed anyway ;)
09:43dgb has joined #asahi
09:45kallistii'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...
09:46dgbdiskutil list
09:51ChaosPrincessThe correct one is disk0
09:51ChaosPrincessbut mac os may complain
09:53javier_varez_ has quit [Quit: Connection closed for inactivity]
09:57kallistimps_: looks like it is having trouble with the `-device` parameter also ^^
09:58kallistiiterating throught he damn disks
10:00kallistihere's what my disks look like via diskutil -list: http://pastie.org/p/0P4EMxdow0p2WKYrRpKmqf
10:00mps_kallisti: I posted script just as example and not as recipe, you have to adapt it to your use case
10:01mps_kallisti: so looks like your asahi install is on the disk0s6
10:03kallistiwe must have iterated through that then
10:03kallistigotta fix the device error and whatever else
10:04mps_kallisti: in my script `-drive if=virtio,id=hd0,format=raw,file=m1` you have to replace with your VM disk
10:04mps_and you don't need ' -drive if=virtio,id=hd3,format=raw,file=m1hfs'
10:04dgbalso... disk0s3 and disk0s5 are both efi?
10:05mps_dgb: I think so
10:05dgbjust want to point it out in case it's not intentional
10:06kallistimps_: I think we're trying to load the ashai kernel in the vm, arent we
10:06mps_you should boot VM image and adding your asahi partition
10:07mps_then when VM boot you can mount manually your asahi root partition and fix it
10:08mps_I guess simply adding '-drive if=virtio,id=hd1,format=raw,file=/dev/disk0s6` to your UTM should be enough
10:09kallistiIf qemu can load utm images I could use ~/Library/Containers/com.utmapp.UTM/Data/Documents/
10:09mps_btw, this should be run as root on macos, or sudo
10:09kallisti~/Library/Containers/com.utmapp.UTM/Data/Documents/ArchLinux.utm
10:10mps_I have no experience with UTM, sorry can't help with it
10:11mps_I only tested with alpine iso and I know it works
10:12mps_but if it works with alpine iso I don't see any reason it will not work with other distros iso
10:16corionI 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?
10:17ChaosPrincessX or wayland?
10:18kallistiqemu-system-aarch64: Could not find ROM image 'QEMU_EFI.fd'
10:18corionChaosPrincess: wayland
10:18mps_hm, so UTM doesn't have EFI file
10:20ChaosPrincesskallisti: Just install a second copy and then delete it, would be way faster than fucking with utm
10:21kallistiChaosPrincess: here I will just download a qcow and not use the UTM file
10:21corionChaosPrincess: Like the marked item in the menu will lag behind the mouse pointer. There is also a delay when opening the menu at all.
10:22mps_kallisti: if you have usb-c stick just follow this https://arvanta.net/alpine/install-alpine-m1/ and you will have it in few minutes
10:23mps_and you will have ready usb rescue system in case you need it later
10:25kallistiSince 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.
10:26kallistiLike we're 95% there, and all I need is a working image now
10:26mps_yes, that will also helpful
10:26Tano70 has joined #asahi
10:27kallistiSo what's the fastest way to a non-utm image that I can use against qemu?
10:27mps_read few first lines
10:28mps_replace 'v3.12` with 'v3.17'
10:28kallistimps_: let me look. That url is broken for me but I see it here
10:30kallistisimple method: there is ready made bootable alpine image which can be used: download link https://dev.alpinelinux.org/~mps/m1/m1-usb-alpine-install.img.xz
10:30kallistiCan I just download that bootable image?
10:30mps_yes, it is now broken, I see
10:31mps_answer to wrong question
10:31mps_I talked about QEMU_EFI
10:33mps_about bootable usb image, yes it could be downloaded and decompressed and then dd-ed to usb stick
10:33kallistiCan I download an image to use as a qcow to boot via qemu?
10:33mps_no, it is intended for real machine
10:34kallistiSo I can't use qemu with an image?
10:35mps_right, this image is intended to boot apple silicon hardware, not VM
10:36kallistiOk, so you think I should write that image to an external source or partition somewhere?
10:37dgbyou can grab a qcow from your favourite distro
10:37dgbit's pretty much a standard cloud image
10:37kallistilook I'm ok with that m1 alpine image
10:37kallistilet's use that one
10:39kallistiso you think i should download that one, and write it to a disk and then use qemu to read from the written partition?
10:39mps_kallisti: you don't need to write this iso to disk, use it as file param for qemu
10:41kallistiso do we change the format line of the qemu parameter now? It was raw before, or is that correct for the iso?
10:42mps_yes, you have to use iso img
10:42kallisti-cdrom /path/to/alpine.iso
10:42mps_`-drive if=virtio,id=hd0,format=raw,file=alpine-virt-3.17.0-aarch64.iso'`
10:43mps_and -cdrom is also ok
10:44mps_but I think we should move to #asahi-alt if we speak about alpine
10:45kallistiI can move there if that's what you think
10:47mps_please do, this channel is for official asahi distro discussion
10:49dgb has quit [Quit: dgb]
10:59swaggie has quit [Remote host closed the connection]
10:59swaggie has joined #asahi
11:02KDDLB has joined #asahi
11:05kode54 has joined #asahi
11:08swaggie has quit [Ping timeout: 480 seconds]
11:10corionChaosPrincess: Nevermind. Seems to be a common problem in kde on wayland.
11:10corionChaosPrincess: So it's not asahi related.
11:15Zopolis4 has quit [Quit: Connection closed for inactivity]
11:30swaggie has joined #asahi
11:30kallisti has quit [Quit: brb]
11:38mps_ is now known as mps
11:41swaggie has quit [Ping timeout: 480 seconds]
11:49swaggie has joined #asahi
12:00cylm_ has joined #asahi
12:07swaggie has quit [Ping timeout: 480 seconds]
12:18swaggie has joined #asahi
12:28swaggie has quit [Ping timeout: 480 seconds]
12:45c10l has quit [Quit: Bye o/]
12:45rvalue has quit [Remote host closed the connection]
12:45rvalue has joined #asahi
13:01c10l has joined #asahi
13:02Dcow has joined #asahi
13:11riker77 has quit [Quit: Quitting IRC - gone for good...]
13:11Dcow has quit [Ping timeout: 480 seconds]
13:13Dcow has joined #asahi
13:18c10l has quit [Quit: Bye o/]
13:24Dcow has quit [Ping timeout: 480 seconds]
13:29c10l has joined #asahi
13:32panzone has joined #asahi
13:32panzone has quit []
13:42c10l has quit [Quit: Bye o/]
13:42Dcow has joined #asahi
13:43c10l has joined #asahi
13:57Dcow has quit [Ping timeout: 480 seconds]
14:03c10l has quit [Quit: Bye o/]
14:04c10l has joined #asahi
14:26Dcow has joined #asahi
14:34Dcow has quit [Ping timeout: 480 seconds]
14:40DexterHaxxor has joined #asahi
14:41DexterHaxxorhow is thunderbolt support? would a eGPU work?
14:44corionThere is no thunderbolt support.
14:44corionIt's a work in progress.
14:45ChaosPrincessthunderbolt support is coming eventually, but egpus are likely to never happen
14:46ChaosPrincessthere pci bus on this machines is a bit broken, in such a way that it will affect egpus but unlikely to a affect other devices
14:47DexterHaxxorwhat? why is that?
14:48delsol has joined #asahi
14:48DexterHaxxoris that on purpose somehow?
14:49ChaosPrincessgpu drivers map the gpu memory in a certain mode, and m1 does not support mapping pci bus in such a mode
14:49ChaosPrincessunlikely, most likely its just the engineers thought that people will not need this mode
14:50DexterHaxxorcould you work around that if you had like an arc where the driver is open
14:50ChaosPrincessand m1 is not the only device with pci-e broken in such a way to only affect gpus
14:50ChaosPrincessyes, you can, but it will require a lot of work in the drivers and unlikely to be upstreamable
14:50DexterHaxxorso it's not really worth it
14:51DexterHaxxorgot it, thanks
14:51DexterHaxxor has quit []
14:59eileen has joined #asahi
14:59eileenjust made a terrible terrible partitioning mistake
14:59eileenso i want to be extra careful now
14:59Dcow has joined #asahi
15:00eileeni'm trying to mount a rootfs from nvme
15:00eileensofar i've made the linux fs partition "/dev/disk0s4" with
15:00eileendiskutil addPartition disk0s3 %Linux% %noformat% 0
15:00eileenwould 'dd if=root.img of=/dev/disk0s4' be sufficient?
15:04z812 has quit [Quit: Bye!]
15:05z812 has joined #asahi
15:06eileeni feel like i'm missing to mkfs.ext4 but i'm not sure how/if diskutil supports that
15:08Dcow has quit [Ping timeout: 480 seconds]
15:10ChaosPrincessshould be sufficient, but add bs=1m and do rdisk0s4 instead
15:11eileenthank you :)
15:21swaggie has joined #asahi
15:26flying_sausages has quit [Ping timeout: 480 seconds]
15:27milesyucht has joined #asahi
15:29swaggie has quit [Ping timeout: 480 seconds]
15:29milesyucht has left #asahi [#asahi]
15:33Dcow has joined #asahi
15:39ptudor has quit [Read error: Connection reset by peer]
15:40ptudor has joined #asahi
15:42Dcow has quit [Ping timeout: 480 seconds]
15:46malte has quit [Remote host closed the connection]
15:47malte has joined #asahi
15:56eileen has quit [Quit: Page closed]
16:01malte has quit [Remote host closed the connection]
16:02malte has joined #asahi
16:35mambais fde something that is to be expected at some point?
16:39sveni think some people already set it up themselves
16:39sveneventually I'd really like to use the secure enclave for fde. that's still quite a long time away though
16:43marvin24_ has quit [Remote host closed the connection]
16:44marvin24 has joined #asahi
17:00swaggie has joined #asahi
17:07amarioguy has joined #asahi
17:08swaggie has quit [Ping timeout: 480 seconds]
17:12Tano70 has quit [Quit: Leaving]
17:16cylm has joined #asahi
17:16delsol has quit [Remote host closed the connection]
17:18swaggie has joined #asahi
17:18cylm_ has quit [Ping timeout: 480 seconds]
17:27swaggie has quit [Ping timeout: 480 seconds]
17:28marvin24 has quit [Ping timeout: 480 seconds]
17:30Dcow has joined #asahi
17:38Dcow has quit [Ping timeout: 480 seconds]
18:05Dcow has joined #asahi
18:13Dcow has quit [Ping timeout: 480 seconds]
19:01aurelian has joined #asahi
19:03Deewiant has quit [Remote host closed the connection]
19:04Deewiant has joined #asahi
19:15Raito_Bezarius has quit [Ping timeout: 481 seconds]
19:29aurelian has quit [Remote host closed the connection]
19:29ncl has quit [Quit: Bye]
19:47bcrumb has joined #asahi
19:51doggkruse has joined #asahi
19:51swaggie has joined #asahi
19:56cylm_ has joined #asahi
19:56Guest25 has quit [Quit: G-line: User has been permanently banned from this network.]
19:57vx has joined #asahi
19:58vx is now known as Guest120
20:02cylm has quit [Ping timeout: 480 seconds]
20:04doggkruse has quit [Remote host closed the connection]
20:07Dcow has joined #asahi
20:17roxfan has quit [Remote host closed the connection]
20:21dgb has joined #asahi
20:21roxfan has joined #asahi
20:22nicolas17 has joined #asahi
20:23bcrumb has quit [Quit: WeeChat 3.7.1]
20:31nicolas17 has quit [Quit: Konversation terminated!]
20:32nicolas17 has joined #asahi
20:32nicolas17 has quit []
20:32nicolas17 has joined #asahi
20:55Raito_Bezarius has joined #asahi
20:56swaggie has quit [Ping timeout: 480 seconds]
21:22lewurm has quit [Ping timeout: 480 seconds]
21:23dgb has quit [Quit: dgb]
21:34swaggie has joined #asahi
21:41lewurm has joined #asahi
21:42swaggie has quit [Ping timeout: 480 seconds]
21:47lewurm has quit [Quit: ZNC 1.8.2+deb2build5 - https://znc.in]
21:47lewurm has joined #asahi
22:03eileen has joined #asahi
22:04eileen_ has joined #asahi
22:05eileen_ChaosPrincess: sorry for the late reply, worked great! thank you :))
22:05eileen has quit [Remote host closed the connection]
22:05eileen_ has quit []
22:08lewurm has quit [Quit: ZNC 1.8.2+deb2build5 - https://znc.in]
22:08lewurm has joined #asahi
22:25rayanamukami3 has quit [Read error: Connection reset by peer]
22:29codingkoopa90 is now known as codingkoopa
22:55swaggie has joined #asahi
22:58SSJ_GZ has quit [Ping timeout: 480 seconds]
23:00yrlf has quit [Quit: The Lounge - https://thelounge.chat]
23:01yrlf has joined #asahi
23:03swaggie has quit [Ping timeout: 480 seconds]
23:09Dcow has quit [Remote host closed the connection]
23:13Zopolis4 has joined #asahi
23:24Dcow has joined #asahi
23:32Dcow has quit [Ping timeout: 480 seconds]
23:32flying_sausages has joined #asahi
23:43jamespmorgan has joined #asahi
23:50jamespmo_ has quit [Ping timeout: 480 seconds]
…