09:35 <cmalvi[m]> i have noticed that if i boot a live environment from usb, the usb itself is mounted as read only. For now i'm using the internal grub to boot it. How can i enable write permission?

09:58 <nico_32> cmalvi[m]: try mount -o remount,rw /

09:59 <cmalvi[m]> oh sorry, i haven't specified: in fstab is already set to be rw

09:59 <cmalvi[m]> maybe a misconfiguration in grub entry?

10:00 <nico_32> could you paste "findmnt" somewhere?

10:01 <nico_32> maybe your / is squashfs or something

10:01 <ChaosPrincess> actually, post fstab and output of `mount` (w/o any args)

10:01 <ChaosPrincess> they most likely disagree on what the root device is

10:02 <cmalvi[m]> i'm chrooted into it, i can post fstab

10:02 <cmalvi[m]> # /dev/sda1

10:02 <cmalvi[m]> UUID=46d06eaa-9e9f-4a37-9945-0bebf9288cc8/ ext4 rw,relatime,x-systemd.growfs0 1

10:03 <ChaosPrincess> cat /proc/cmdline ?

10:03 <cmalvi[m]> BOOT_IMAGE=/boot/vmlinuz-linux-asahi-4k root=UUID=e03650ff-c482-4694-be60-11d37f637791 rw loglevel=3 quiet

10:04 <ChaosPrincess> well, thats the problem i guess

10:05 <cmalvi[m]> i think i haven't understood

10:05 <ChaosPrincess> fstab and grub disagree on what the root device is supposed to be

10:05 <cmalvi[m]> oh

10:06 <ChaosPrincess> you should set both of them to have /dev/sda1 or whatever as root device

10:06 <cmalvi[m]> is the first time for me to set manually those things

10:06 <cmalvi[m]> ChaosPrincess: oh so i just need to change the uuid accordingly to the fstab

10:07 <ChaosPrincess> do blkid <path you your usb block device> first

10:07 <ChaosPrincess> to check who is correct

10:08 <cmalvi[m]> the fstab is the correct

10:23 <cmalvi[m]> but seems i can't modify cmdline from chroot or host system

10:24 <ChaosPrincess> yes, you should edit some file under /boot/grub or something like that

10:25 <ChaosPrincess> idk where exactly, do `grep -R root=UUID=e03650ff-c482-4694-be60-11d37f637791 /boot` and go from there

10:25 <cmalvi[m]> ok really thank you :)

10:44 <cmalvi[m]> seems the problem is also the alarm user which doesn't have write permission

11:08 <nico_32[m]> write permission where?

11:09 <FranciscoFernandes[m]> Chmod 777 path

11:11 <nico_32[m]> 777 is not often the right thing to do...

11:13 <cmalvi[m]> nico_32[m]: agree

11:13 <cmalvi[m]> just created a new live user

11:14 <cmalvi[m]> <nico_32[m]> "write permission where?" <- to all, alarm user seems to have only read permission

11:17 <FranciscoFernandes[m]> cmalvi[m]: Its a first aid kit lol

14:44 <mipi[m]> <marcan> "I was waiting for someone to..." <- I tested it on M1: Your fix works. Rust can be built, and rust packages can be built 😀

14:47 <mipi[m]> * Your fix (https://github.com/AsahiLinux/alarm-PKGBUILDs/commit/c2459a0ae6fc04b7fe98bb04f10795248eca949b) works. Rust

15:29 <pyropeter3> I used the installer to install 'Asahi Linux Minimal' on an macbook air, but now I can't get any outside connection because wpa_supplicant isn't installed, usb-c seems nonfunctional and this device does not have any other ports except for a headphone jack

15:29 <pyropeter3> I'm using an Anker USB-C dock with built-in ethernet and 2 usb-A 3-ports

15:30 <pyropeter3> I see the devices enumerate in dmesg, but they don't show up in linux, e.g. in `ip a` or the linux block device stuff (when trying an USB 2 mass storage device)

15:31 <pyropeter3> this is probably because my dock doesn't really do anything without USB 3, right?

15:32 <j`ey> pyropeter3: use iwd, not wpa_supplicant

15:32 <pyropeter3> great suggestion!

15:33 <pyropeter3> no wait, that is missing as well

15:33 <j`ey> hm, i thought that was installed..

15:34 <j`ey> https://github.com/AsahiLinux/asahi-alarm-builder/blob/main/scripts/base/10-base-packages.sh#L8

15:34 <pyropeter3> it is, I tried to execute the 'iwd' binary, which is not a thing with iwd

15:36 <psykose> it is, it's just in libexec

15:38 <pyropeter3> yes, quite right; I successfully connected to my wifi, thanks a lot

17:26 <cmalvi[m]> does the wifi need a specific package to work? because doesn't seem to work on a usb live environment

17:27 <cmalvi[m]> * live environment (arch base install from arm arch site with gnome)

17:27 <j`ey> cmalvi[m]: iwd is the package that asahi alarm comes with

17:28 <cmalvi[m]> isn't already installed on arch?

17:29 <j`ey> check if you have it

17:29 <j`ey> do you also have the wifi firmware?

17:30 <cmalvi[m]> j`ey: mmm i don't know really, i just use the armv8 generic image to create the usb and install the needed package from asahi repo

17:30 <cmalvi[m]> it's just an experiment to create live rescue environment

17:30 <pyropeter3> check if `ip link` or `ip address` shows a wlan0 device

17:31 <cmalvi[m]> i'll reboot and check

17:32 <j`ey> cmalvi[m]: you probably dont have iwd or the firware

17:34 <cmalvi[m]> I’m sure it’s the second but I’ll check both now

17:37 <cmalvi[m]> Iwd isn’t installed, so I need to chroot into. How can I check the Wi-Fi firmware?

17:38 <pyropeter3> look into /lib/firmware/brcm/

17:38 <pyropeter3> you need brcmfmac4378b...

17:39 <pyropeter3> those files do not belong to any package on my system so I guess the installer gets them from macos and just puts them there

17:39 <j`ey> yup

17:40 <pyropeter3> https://github.com/AsahiLinux/docs/wiki/Distro:Differences-from-Arch-Linux-ARM#asahi-scripts

17:40 <pyropeter3> > Fetches vendor firmware from the EFI system partition and installs it to /lib/firmware, or upgrades it if necessary, on each boot. This is required to make WiFi work out of the box, and more drivers in the future.

17:44 <cmalvi[m]> Oh thanks

17:45 <cmalvi[m]> So I just need to copy all the needed files into lib folder right?

17:46 <pyropeter3> you could do that, but I would just install asahi-scripts from repos and enable update-vendor-firmware.service

17:52 <cmalvi[m]> <pyropeter3> "you could do that, but I would..." <- A message suggest me that this service isn’t meant to be enabled using systemctl

17:52 <cmalvi[m]> However I’ve copied the files, now I try

18:28 <sanpen> hi, i'm having trouble with my machine after rebooting. i end up in a grub prompt and usb devices don't work so i can't remedy things using my keyboard. how do i get out of this state?

18:54 <ThomasGlanzmann> sanpen: which distro are you running?

18:54 <ThomasGlanzmann> if you wrote me an email earlier see my reply.

20:22 <joske> Hi guys/girls, just received my M1 max MBP for my next job

20:22 <joske> if you install asahi, is there any security that is downgraded that can not be reset before I start next week (planning to factory reset the thing before the first day)

20:22 <joske> ?

20:22 <j`ey> no

20:23 <joske> the machine will be managed by jamf, will it see the extra partitions as bad, or should I delete those before resetting?

20:24 <joske> so basically I can at least install asahi on it and play with it for a week before wiping?

20:25 <j`ey> yep

20:25 <joske> great! :-D

20:26 <tpw_rules> i'm not actually sure if the "erase all content and settings" gets those partitions

20:26 <tpw_rules> but erasing it with idevicerestore or apple configurator will completely zero it

20:26 <joske> can delete those partitions manually if needed

20:28 <tpw_rules> yeah it's easy. and the security of macos will not be affected by asahi in any way. so as long as jamf doesn't go out searching it won't notice

20:29 <joske> if that is true, I could just leave it on :-D

20:54 <Cy8aer[m]> hm, someone told here in the room some weeks ago that his mbp got hot when running linux and loading the battery. Seems to be the same for me. When I shut down the device got cold again but still loading the battery. It is especialy hot on the right hand side of the touch pad. So I wonder if it is save to load the battery when running linux? 5.18.0-asahi-00002-gc1c26949be91 - debian. When the battery is loaded the device keeps cool even if

20:54 <Cy8aer[m]> hooked on power.

20:54 <Cy8aer[m]> mbp14 running debian testing.

21:35 <Glanzmann> Cy8aer[m]: My macbook air also gets hotter on Linux while charging then under macos. Also I notice the heat coming from the right side of the touchpad.

21:37 <Glanzmann> No idea if it is safe or not, but I worked several weeks under Linux. And my macbook air still works fine. I use the system on a daily basis for multiple hours. It is my main machine when I'm traveling. But since I give a lot of online trainings and we don't have camera or microphone under Linux, I use macos to deliver trainings. I often reboot in the evening to Linux to do some work.

21:39 <Cy8aer[m]> Yes, my macbook is also daily basis for weeks now and the battery looks still ok.

21:39 <Cy8aer[m]> but heat is ageing...

21:39 <Glanzmann> Yes, I agree.

21:41 <Glanzmann> Cy8aer[m]: You can disable charging while under Linux, maybe that solves the heat issue. I never tried it.

21:41 <Glanzmann> But IIRC it is pretty easy.

21:41 <Cy8aer[m]> via some sys parameter I guess...

21:46 <Glanzmann> yep.