User talk:Jared

From Gentoo Wiki
Jump to:navigation Jump to:search
Note
Before creating a discussion or leaving a comment, please read about using talk pages. To create a new discussion, click here. Comments on an existing discussion should be signed using ~~~~:
A comment [[User:Larry|Larry]] 13:52, 13 May 2024 (UTC)
: A reply [[User:Sally|Sally]] 22:24, 22 July 2024 (UTC)
:: Your reply ~~~~

techguru@20240613

Talk status
This discussion is still ongoing as of 2024-06-13.

following in your footsteps for an initial trial, noting the following changes needed for my MacBook Air M2

1) install Asahi June 12 ... with gnome desktop -- verified working 2) started gentoo install, following Jared @gentoo.wiki 3) the initial reboot after genstrap.sh does not show a grub menu for me -- briefly showed prompt for uboot --- tweak 3a) modified the grub2.conf file to make GenToo the default 3b) reboot 3c) joy -- now inside of the gentoo setup environment


4) when mounting /boot in the chroot, must use the /dev/mapper/luks # not the nvme [encrypted] device


5) "./install.sh" -- initial received message "We use ESP-as-boot. Please mount the Asahi ESP to /boot and before continuing. This is absolutely essential for the system to function correctly." 5a) removed the name check for "Asahi ESP" from install.sh, reran.


6) The following USE changes are necessary to proceed:

(see "package.use" in the portage(5) man page for more details)
  1. required by sys-kernel/asahi-kernel-6.8.9_p7::asahi[initramfs]
  2. required by sys-boot/m1n1-1.4.12::asahi
  3. required by sys-apps/asahi-meta-2-r7::asahi
  4. required by sys-apps/asahi-meta (argument)

>=sys-kernel/installkernel-38 dracut

  1. required by sys-kernel/asahi-kernel-6.8.9_p7::asahi
  2. required by sys-boot/m1n1-1.4.12::asahi
  3. required by sys-apps/asahi-meta-2-r7::asahi
  4. required by sys-apps/asahi-meta (argument)

>=dev-lang/rust-bin-1.77.1 rust-src rustfmt


6a) added two references above to "/etc/portage/package.use/extras_asahi

...


7a) no mention of /etc/crypttab or its contents -- it is needed to mount the encrypted partition in a decrypted state

Hello techguru ! Apologies for the delay.
4) For /boot it should be a /dev/nvme0n1p# partition that's NOT luks.
5/5a) I suspect this was due to mounting the wrong partition at /boot?
6) Yes, I also hit that, good to hear I wasn't the only one!
7) You shouldn't need to modify /etc/crypttab since {{{1}}} being added to the kernel cmdline will handle automatic mounting of the encrypted device. Perhaps that'd be needed if there's multiple encrypted drives or LVM in use, but that's outside of the scope.
--Jared (talk) 02:20, 23 June 2024 (UTC)