On Mon, 13 Jan 2025 21:41:54 -0700
Gregory Nowak <greg@???> wrote:

> On Mon, Jan 13, 2025 at 09:35:54PM -0700, Gregory Nowak via Dng wrote:
> > On Mon, Jan 13, 2025 at 07:21:12PM -0500, Curtis Maurand wrote:
> > > What's the chance of this thing booting without re-installing
> > > Daedalus? It's not the end of the world if I have to install a
> > > fresh copy and import the virtual machines. I'm curious if things
> > > are plug and play enough to be successful on the first try.  This
> > > is a project that will happen in the next few weeks to a month.
> > > AMD microcode is installed on all the machines including the
> > > kvm's.
> >
> > I'd say the chance of Daedalus coming up on first boot on the other
> > hardware is high. Unless you've compiled your own kernel, or highly
> > customized your initramfs, it shouldn't be a problem. GNU/Linux
> > isn't windows.
>
> If you have ethernet device names assigned by udev rules, you will
> need to adjust those once you boot up, but there shouldn't be major
> issues.
>
> Greg
>
It's a long story as to why it took this long to get this board
installed. This project has been the bane of my existence. I installed
the new motherboard, yesterday. I ran out of time and I couldn't
complete the set up of the m.2 nvme drive. Linux sees it, though and I
can access it. In order to boot from it, I'll need to repartition the
drive to a GPT partition table and set it up for UEFI boot and install
grub on it. (don't get me started on UEFI). Anyway, it's a XFS
filesystem so I'll be able to move all the files with xfsdump. It's not
the end of the world. All in all, we're in pretty good shape.

However, I set the proper existing SSD for booting and it booted
flawlessly.

Thank you, everyone, for your helpful suggestions all is well.

Thanks again,
Curtis
>