#asahi · 2025-12-11 21:23
quaffI do see on the official support page that they have chromeOS and ubuntu support. so it could be workable. #asahi · 2025-12-11 21:22
quafffeoh: I have not. I'm not the one organizing the meetings so the device isn't mine to play with.#asahi · 2025-12-11 19:27
quaffbgtlover[mds]: if you're referring to the meeting owl: https://owllabs.com/, it's an audio&video conferencing device. I regularly use one for hybrid in-person + virtual meetings. pretty nifty but expensive. haven't tried it on linux, so I am not surprised if support for asahi is light as well.#asahi · 2025-12-04 00:17
quaffthx for your help!#asahi · 2025-12-04 00:17
quaffchaos_princess: just installed the gentoo asahi livecd on a usb, and booted into that. grub and u-boot is alien to me 🥲#asahi · 2025-12-03 23:05
quaffchaos_princess: I can't seem to get into grub. I've been running ls nvme 0:[1-7] / to try and figure out which is my root partition. looks like 4 & 5 are boot partitions. but everything else returns nothing can't change the bootargs without knowing which is root 😅#asahi · 2025-12-03 22:44
quaffoh.. with u-boot because the scroll happens so fast I can't really see what the initial options are. I'm having a hard time figuring out what to type#asahi · 2025-12-03 22:43
quaffchaos_princess: rd.shell? I'll try that one thank you!#asahi · 2025-12-03 22:40
quaffokay sweet. the documentation for how to use U-boot is on their website right? 🙏 no special asahi one?#asahi · 2025-12-03 22:39
quaffyes#asahi · 2025-12-03 22:38
quaffI need to delete /etc/ld.so.preload 🥲#asahi · 2025-12-03 22:38
quaffdoes asahi Linux have a bootable ISO i can put on a USB key? Or is there a bootable aarch64 ISO i can flash to a USB drive to boot from?#asahi · 2025-12-01 23:25
quaffjannau: way back on nov 3rd, you were helping me troubleshoot an issue that occurred after I upgraded my m1 to fedora 43. I figured it out haha I had "rye" installed and was referenced in ~/.profile which was breaking my login flow since rye is no longer available on the system (upgrade must have broke the install; which is fine, deprecated anyway). after removing the reference in my .profile, kde boots up fine from sddm again. not sure if you w#asahi · 2025-11-03 22:09
quaffjannau: shot in the dark, you think that might help my issue?#asahi · 2025-11-03 20:55
quaffjannau: ah, I don't see "Starting plasma-kwin_wayland.service - KDE Window Manager" at all after "Starting Wayland user session: ..."#asahi · 2025-11-03 20:53
quaffthen: pam_unix(sddm-greeter:session): session closed for user sddm#asahi · 2025-11-03 20:53
quaffsddm-helper-start-wayland[1317]: "kwin_scene_opengl: Could not delete render time query because no context is current\n"#asahi · 2025-11-03 20:53
quaffjannau: no, immediately after "Starting Wayland user session..." I see this:#asahi · 2025-11-03 20:49
quaffcomparing to this machine I'm using, I'm not seeing any big differences or glaring issues#asahi · 2025-11-03 20:44
quaffI uninstalled toshy, and rebooted, with ssh enabled, and tried logging in again, here's the log I get from journalctl: https://paste.sr.ht/~quaff/cf20bf1acc0090b7775a943c04a0d093f01dc4f7#asahi · 2025-11-03 20:37
quaffI'mm gonna uninstall toshy and see if that helps#asahi · 2025-11-03 20:37
quaffI think that kwin_wayland_drm is just a warning#asahi · 2025-11-03 20:37
quaffkwin_wayland_drm: Could not find edid for connector DrmConnector(id=41, gpu=\"/dev/dri/card3\", name=\"eDP-1\", connection=\"Connected\", countMode=1)\n"#asahi · 2025-11-03 20:37
quaffNov 03 12:31:32 Pluto sddm-helper-start-wayland[1326]: "kwin_wayland_drm: atomic commit failed: Permission denied\n"#asahi · 2025-11-03 20:35
quaffokay ssh enabled. I'll try and load plasma and check journalctl#asahi · 2025-11-03 20:33
quaffjannau: I don't lemme turn it on and try#asahi · 2025-11-03 20:33
quaffI see that error, not sure if it's related#asahi · 2025-11-03 20:33
quaff"gkr-pam: unable to locate daemon control file" in journald#asahi · 2025-11-03 20:30
quaffonly thing I see on my screen is what was on tty2 before I jumped to sddm that second time#asahi · 2025-11-03 20:29
quaffokay. just going from the top: I booted up to sddm, dropped to tty2, logged in and stopped sddm, ran startplasma-wayland (worked!), logged out and dropped back to tty2, started sddm up again, and tried to log into plasma via sddm, but the screen seems to be frozen. I can't jump between tty2-<*>. caps lock still works, so system isn't completely frozen#asahi · 2025-11-03 20:23
quaffI have! I'm up to date. I just tried running startplasma-wayland, and it worked... so something seems to be happening between sddm <-> plasma/cosmic/gnome (I tried all of these as well)#asahi · 2025-11-03 20:15
quaffafter booting up, and sddm loads.. if I drop to tty2/3, stop sddm, then run startplamsa-wayland manually, that should work, right?#asahi · 2025-11-03 20:14
quaffjannau: fair. I remember it did reboot (and logged in) properly once after upgrading. I was messing around with toshy afterwards (I dont' think it messages with anything?) and the second reboot was when I was getting issues. I'm testing now again and seeing it's stuck on a black screen after I attempt to login via sddm#asahi · 2025-11-03 19:56
quaffjannau: okay I'll dig around a bit more later to see if I can figure out if it's just a quaff issue, or if it's something else#asahi · 2025-11-03 19:48
quaffunless y'all are worried it's something that might be prevalent for everyone else. I'll spend a little time later digging to see if I can find the cause. it's probably something stupid I did tho#asahi · 2025-11-03 19:48
quaff🙏 no worries, I'll wait until 43 is officially out, then I'll try again. no rush!#asahi · 2025-11-03 19:45
quaffchaos_princess: hmmm I think I waited a longer than that and it stayed a black screen when I toggled through the ttys looking for plasma (tty1?)#asahi · 2025-11-03 19:44
quaffjannau: offline... yes! there was a little offline phase, I remember thinking "hm.. I don't remember doing this from 41->42" #asahi · 2025-11-03 19:40
quaffjannau: ah okay. just wanted to lend my voice to any issues related (seemingly) to f43. but everything else seems to work okay. booting, sddm, tty login, etc.#asahi · 2025-11-03 19:38
quaffcouldn't see anything in journalctl, so I dropped to tty3 and tried to run startplasma-wayland, and saw some error that looks like it might be drm related, not sure tho.#asahi · 2025-11-03 19:36
quaffI stupidly upgraded to f43. using sddm + plasma. upgraded f42->f43, rebooted, then rebooted again, when I login (after sddm), plasma doesn't start. I tried to troubleshoot, but the error seems to be related to a lack of a drm driver? I stopped there. I'm unsure if it was f43, or something I did, will wait for the official release and try again.#asahi · 2025-11-02 03:05
quaffchadmed_: huh. I'm getting some issue with wayland not loading. I'll leave my laptop and upgrade again when there's an official announcement #asahi · 2025-11-02 00:45
quaffI upgraded to fedora 43 on my m1 macbook.. that was a mistake, wasn't it? 😅#asahi · 2025-04-17 14:32
quaffyeah, was super straight forward. #asahi · 2025-04-14 06:03
quaffThanks Asahi team 😍#asahi · 2025-04-14 06:03
quaffInstalling the latest tiny-dfr package fixed the issue! https://koji.fedoraproject.org/koji/buildinfo?buildID=2697646#asahi · 2025-04-14 05:29
quaffnot yet at least 😂#asahi · 2025-04-14 05:29
quaffnicolas17: okay! I won't go nuts uninstalling things to figure out if I messed something up lol thank you#asahi · 2025-04-14 03:04
quaffwhen I try to run /usr/bin/tiny-dfr with sudo tiny-dfr I see a rust error: called Result::unwrap()on anErr value: No touchbar device found, attempted:#asahi · 2025-04-14 03:02
quaffI'm seeing this in the systemctl status tiny-dfr.service: Job tiny-dfr.service/start failed with result 'dependency'.