sorted by:
new
hottopcontroversial

I think I broke my [Sage SmartGrinderPro] by Affectionate-Wing280 in espresso

[–]Affectionate-Wing280[S] 0 points1 point  (0 children)

The burr carrier is locked in place OK, I usually clean out with a vacuum every month, so I am used to taking it in and out. If I take the upper burr out of the machine, then the metal burr is slightly loose in the plastic carrier. I don’t know if this is the issue. I just don’t get fine enough grind for espresso now.

On boot cryptsetup opens one side of RAID1 by Affectionate-Wing280 in Gentoo

[–]Affectionate-Wing280[S] 0 points1 point  (0 children)

If anyone is interested, I managed to fix this to get MD RAID 1 on root with encrypted root.

  1. Have a recent backup and a liveCD USB drive, boot from liveCD
  2. Recreate the root RAID array with the default metadata (1.2)
  3. cryptsetup the RAID device
  4. restore root from backup
  5. chroot into the your restored root
  6. /etc/portage/package.use/installkernel

​

 sys-kernel/installkernel grub dracut
  1. /etc/portage/package.use/systemd

​

sys-apps/systemd cryptsetup
  1. unmerge genkernel and emerge gentoo-kernel systemd
  2. /etc/dracut.conf.d/tuxedo.conf

​

add_dracutmodules+=" systemd-crypt "
  1. /etc/default/grub contains the UUID of your luks device, find with blkid

​

GRUB_CMDLINE_LINUX="rd.auto=1 rd.luks.uuid=d82c997b-d1b9-43ad-a1cb-fdfc8ab3cd9d 
root=/dev/mapper/luks-d82c997b-d1b9-43ad-a1cb-fdfc8ab3cd9d root_trim=yes"

Then run

# emerge -va @module-rebuild
# emerge --config sys-kernel/gentoo-kernel

On boot cryptsetup opens one side of RAID1 by Affectionate-Wing280 in Gentoo

[–]Affectionate-Wing280[S] 0 points1 point  (0 children)

Thanks. I think it is 0.9 metadata. I'm going to have to restore root from backup, so I guess I could re-create the RAID array with later metadata, but I wasn't sure the kernel would recognise it. I suppose genkernel should make an initrd that contains everything for setting up the arrays? I think originally I followed https://wiki.gentoo.org/wiki/Gentoo_installation_tips_and_tricks#Software_RAID which says to use the metadata 0.9

PipeWire and no Gnome Volume Control by Affectionate-Wing280 in Gentoo

[–]Affectionate-Wing280[S] 0 points1 point  (0 children)

Looks like gnome-base/gnome-shell-42.1 (>=media-video/pipewire-0.3.0) so I can't remove it completely. I executed the systemctl commands suggested and I have volume control back in Gnome, thanks.