On Tue, 1 May 2007, Paul de Weerd wrote:

quoted text
> On Tue, May 01, 2007 at 01:27:38PM -0500, Aaron Hsu wrote:
> | On Tue, 01 May 2007 13:15:04 -0500, Otto Moerbeek <otto@drijf.net> wrote:
> |
> | >On Tue, 1 May 2007, Aaron Hsu wrote:
> | >
> | >>On Tue, 01 May 2007 03:35:33 -0500, Otto Moerbeek <otto@drijf.net>
> | >>wrote:
> |
> | [...]
> |
> | >>> The UKC prompt is still not working, you'll need an ACPI enabled >
> | >>bsd.rd.
> | >>
> | >>I do not haveb&unfortunately, a current installation of OpenBSD on
> | >>which I can
> | >>compile a new BSD.RD kernel. Is there a way I can work around this?
> |
> | [...]
> |
> | >One quite involved method I can think of: if you have parallels, you
> | >could use that to build a ACPI enabled release (see release(8), remove
> | >"disable" from the acpi line for GENERIC and RAMDISK_CD).
> |
> | Well wait a second, that makes sense! Hah, I think I can do that. All I
> | would have to do is build two new kernels, right? A BSD.RD and a BSD? And
> | then I could just make a bootable iso straight from the rest of 4.1, no?
> 
> I think you can just run config(8) against a bsd.rd from some
> snapshot. After installation, you can chroot into your installed OS
> and config(8) /bsd and/or /bsd.mp (the Core Duo has two cores, you can
> run bsd.mp to get SMP support).
> 
> $ config -ef bsd.rd
> OpenBSD 4.1-current (RAMDISK_CD) #298: Sun Apr 29 14:18:55 MDT 2007
>     deraadt@i386.openbsd.org:/usr/src/sys/arch/i386/compile/RAMDISK_CD
> Enter 'help' for information
> ukc> find acpi
> 216 acpi0 at mainbus0 disable bus -1 flags 0x0
> ukc> enable acpi
> 216 acpi0 enabled
> ukc> quit
> Saving modified kernel.
> 
> No need to build kernels.

Huh? How is the OP supposed to get an install if the cd41.iso isn't working?

	-Otto