Re: attempting to disable acpi in kernel

["Michael Litchard" <michael%schmong.org@localhost>]

well, in the past I have had random inexplicable problems solved by
disabling acpi.
In this case it's vnc. On a prior amd64 machine (laptop), with an
older -current, vnc worked fine. Now, it doesn't.
I've tried my best (including trying to get some help from port-xen).
I just want it to be disabled as a way to rule out that it is, or is
not the problem.

On Mon, Aug 25, 2008 at 5:38 PM, Sarton O'Brien 
<bsd-xen%roguewrt.org@localhost> wrote:
> On Tuesday 26 August 2008 10:28:51 Michael Litchard wrote:
>> yes, I do. But doesn't the netbsd kernel also need to disable acpi?
>
> If it was a GENERIC kernel I'd say yes but with the hypervisor above dom0, I'd
> be inclined to believe that dom0 is smart enough to know if acpi is available
> or not.
>
>> Trying to do it via console (using the -c) hangs. It seems the only
>> way I can disable it is by
>> configuring a kernel with no acpi support.
>>
>> Here's my menu.lst file
>> title Xen 3.0 / NetBSD (hda0, vga)
>>   root(hd0,0)
>>   kernel (hd0,a)/xen.gz acpi=off dom0_mem=1048576
>>   module (hd0,a)/netbsd-XEN3_DOM0 bootdev=wd0a ro console=tty0
>
> What's the motivation behind manually disabling acpi in dom0?
>
> Sarton
>