Date: Thu, 21 Nov 2002 17:13:47 -0500 (EST) From: John Baldwin <jhb@FreeBSD.org> To: Marcel Moolenaar <marcel@xcllnt.net> Cc: ia64@FreeBSD.org Subject: RE: Gotchas when trying 5.0-DP2 Message-ID: <XFMail.20021121171347.jhb@FreeBSD.org> In-Reply-To: <20021121220031.GB1191@dhcp01.pn.xcllnt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 21-Nov-2002 Marcel Moolenaar wrote: > Gang, > > I tried the DP2 install myself and with some corrective actions and > retries one can actually finish an install and end up with a usable > system. A quick rundown follows: > > 1. a CD boot (using miniinst.iso) doesn't give me any troubles on my > Itanium box. The mechanics work, so the problem here is the same > as on any other architecture: does the kernel boot at all? > > 2. When partitioning the disk, you have to create an EFI slice (type > 239). I used 110M as the size for it and that was enough to hold > 2 kernels of which one was a debug kernel. Note that the installer > still creates MBR partitions (=slices). Remember the EFI device > name (eg da0s1) at this point. You need it later. > > 3. When you create BSD partitions and define mount points, make sure > you give the EFI partition a mount point and also mark it as newfs. > In the description below I assume the mount point of the EFI > partition is called efi. > > 4. The actual install (after selecting ditribution, media and if you > want ports collection) starts off with an error. The error dissapears > too quickly, but it must be because the EFI partition couldn't be > mounted. This is nasty but not critical. The install continues > and finished successfully. We just have to patch things up. You > first finish the install in the normal way. Just fix things up > before you reboot (ie exit the installer). > > 5. After the install, go to vty4 (holographic shell) and fix the > link /boot->/mnt/efi/boot to be /boot->efi/boot (ie relative!). > Secondly, manually mount the EFI partition. This fixes the > currently known bugs in the installer and which ultimately causes > you to end up without a kernel to boot from (ouch). > > 6. Reinstall the base distribution. This will cause kernels to be > installed under /boot. Since we linked that to efi/boot, we end > up with kernels and modules on the EFI partition. That's where > we need them. > > 7. Reboot and create an EFI menu entry and you should be all set to > go. One question: is there any interest in just having the loader be in the EFI partition but leave the kernels in UFS / as well as the rest of /boot? I suppose one might would have to write a UFS driver for EFI to make that work. -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ia64" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.20021121171347.jhb>