#
#asahi · 2024-02-11 21:00
taniyamayes
#asahi · 2024-02-11 20:59
j`eywell it's /boot not /boot/efi thats the problem ^
#asahi · 2024-02-11 20:55
taniyama/dev/nvme0n1p4 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
#asahi · 2024-02-11 20:55
taniyamamount is showing an error mounting the disk with read/write privileges
#asahi · 2024-02-11 20:51
PaulFertserOr read-only? strace -f is usually good at shedding light in cases like that.
#asahi · 2024-02-11 20:51
taniyamano, still has 354 mb out of the 500
#asahi · 2024-02-11 20:50
j`eyis it full?
#asahi · 2024-02-11 20:50
taniyamaefi partition
#asahi · 2024-02-11 20:50
taniyamadoesn't make sens, since boot is mounted
#asahi · 2024-02-11 20:50
taniyamathis is the error that mkinitcpio is throwing ERROR: Unable to write to '/boot/initramfs-linux-asahi.img'
#asahi · 2024-02-11 20:45
j`ey*help
#asahi · 2024-02-11 20:45
j`eyok, I don't know about alarm much, maybe someone that's running it can jelp
#asahi · 2024-02-11 20:43
taniyamaoccurs when installing both the scripts, and the kernel
#asahi · 2024-02-11 20:43
taniyamait's not fedora, it's alarm, the error occurs with mkinitcpio, WARNING: errors were encountered during the build. The image may not be complete.
#asahi · 2024-02-11 20:42
j`eyis this fedora? can you pastebin the actual command/error (paste.rs)
#asahi · 2024-02-11 20:39
taniyamai had to reinstall and now when trying to install the newest kernel (compiled) or asahi scripts, I am getting a warning that errors were encountered during the build. That the image may not be complete, how can I debug this?
#asahi · 2024-02-11 19:44
TramtristGlad hes taking care of himself
#asahi · 2024-02-11 19:18
j`eyreposting for those not on masto: https://hachyderm.io/@marcan@treehouse.systems/111914251486933841
#asahi · 2024-02-11 14:09
chrisThanks, I'll migrate to -alt
#asahi · 2024-02-11 14:08
leiomost appropriate places would be #asahi-alt here on OFTC or #gentoo-arm on Libera
#asahi · 2024-02-11 14:06
chrisBecause if I reboot during the Gentoo well I've obviously wiped the Asahi volume group for Gentoo so can't reboot from that image through GRUB
#asahi · 2024-02-11 14:06
chrisProblem is that I have no idea where to access this live USB that the chadmed script has supposedly created. Can I not literally make a USB so I can resume my Gentoo as and when I want to rather than doing it all in one?
#asahi · 2024-02-11 14:06
chrisHi all, just wondering if this is the most appropriate channel to ask this or whether there's a more appropriate place. Basically using EXPERT mode to use ALARM to install Gentoo with Asahi. Simple enough, PITA with a lot of steps and takes a long time but simple enough. Only problem is when doing a Gentoo install I'm the sort of guy who just says do this, comes back to it like half an hour or hours later, resumes, maybe turns it off if going to sleep, etc.
#asahi · 2024-02-11 05:59
draco1017got it
#asahi · 2024-02-11 05:55
chadmedjoin #asahi-dev too
#asahi · 2024-02-11 05:55
chadmeddraco1017: https://github.com/AsahiLinux/docs/wiki/Yaks-in-need-of-shaving
#asahi · 2024-02-11 04:19
draco1017I am a unverisity student taking a introductory course in Operating Systems this semester, thought a good way to learn outside the classroom would be to contribute to this project. Read the website and it says that there's a few general options, but I wanted to ask on here a good task to tip my toes into.
#asahi · 2024-02-11 03:57
draco1017hello
#asahi · 2024-02-11 00:40
cy8aer(by update-m1n1 or - if you have a Glanzmann-Kernel/Debian by recovering it from /usr/lib/m1n1/boot.bin)
#asahi · 2024-02-11 00:39
cy8aerIt would be useful to rebuild m1n1 after this because the m1n1 is more generic than the distribution's one.
#asahi · 2024-02-11 00:23
cy8aerRight, I did it twice the way of the description from "upgrade_stub.txt".
#asahi · 2024-02-10 18:07
milkyby mounting the EFI partition inside mac os?
#asahi · 2024-02-10 18:07
milkyi would just need to copy the backup of the EFI folder?
#asahi · 2024-02-10 18:07
milkyso the installer would take care of m1n1 and asahi inside of the EFI partition?
#asahi · 2024-02-10 17:23
cy8aeror better the EFI directory...
#asahi · 2024-02-10 17:22
cy8aernever ever loose the EFI partition!
#asahi · 2024-02-10 17:21
cy8aerhttps://tg.st/u/upgrade_stub.txt is a good help
#asahi · 2024-02-10 17:20
cy8aermilky: rescue "/boot/efi/EFI", remove the ESP and the macOS stub. Then start the installer and install the EFI stuff, recover the EFI partition, boot
#asahi · 2024-02-10 15:50
milkydeleting the macOS stub and ESP and then chrooting into the system from mac os?
#asahi · 2024-02-10 15:49
milkyhow would i go about recreating the ESP in order to update the firmware to 13.5 (for HDMI)?
#asahi · 2024-02-10 14:38
leiofor me it's JetBrains stuff, which are looking good in 200% "scale" in GNOME, but fuzzy with 275%
#asahi · 2024-02-10 14:17
PaulFertserWhat legacy apps are you talking about anyway. Like Xfig?
#asahi · 2024-02-10 14:17
j`eybinary patch them to use wayland :P
#asahi · 2024-02-10 14:17
jannegsure, good luck with the biinary patching
#asahi · 2024-02-10 14:16
PaulFertserMake them not need external scaling.
#asahi · 2024-02-10 14:16
PaulFertserYou can fix legacy apps to behave.
#asahi · 2024-02-10 14:16
jannegI don't get the point. you can write applications that way but that has nothing to do with the high DPI scaling of legacy apps
#asahi · 2024-02-10 14:14
PaulFertserSame as how proper semantic markup lets web pages be displayed according to your needs and not just have a fixed "design" like a paper booklet.
#asahi · 2024-02-10 14:11
PaulFertserBut you do want that flexibility inside every app. Compare old dialog windows with all fixed pixel sizes with modern "layouts" where window elements are scaled automatically based on the app logic and your own preferences and size and shape of displays etc.
#asahi · 2024-02-10 14:11
jannegmaking the application dpi-aware is leaving the "scaling" to the application

plus ›