On Tue, Jul 15, 2008 at 11:51:27AM +1000, Sarton O'Brien wrote:
> On Tue, 15 Jul 2008 07:55:17 am Jonathan A. Kollasch wrote:
> > On Thu, Jul 10, 2008 at 10:41:10AM +1000, Sarton O'Brien wrote:
> > > On Sun, 15 Jun 2008 01:33:06 am Sarton O'Brien wrote:
> > > > I'm seeing this on domu boot but not dom0 boot:
> > > >
> > > > powerd[268]: open /dev/power: Device not configured
> > >
> > > I'm still seeing this ... is there a way to fix it? I've not seen it
> mention
> > > outside of myself so I'm wondering if it's just me.
> > >
> > > 4.99.69 NetBSD 4.99.69 (XEN3_DOMU) #1: Tue Jul 8 19:03:22 EST 2008
> > >
> > > Recreating the device does nothing.
> >
> > ...
> >
> > src/sys/arch/i386/conf/majors.i386:
> > device-major sysmon char 67 sysmon_envsys | sysmon_wdog | sysmon_power
> >
> > src/sys/arch/amd64/conf/majors.amd64:
> > device-major sysmon char 67 sysmon_envsys | sysmon_wdog
> >
> > this results in config(1) not being aware that we actually want a working
> > /dev/power ...
>
> I won't attempt to display any understanding :) ... I'm guessing the
> difference is sysmon_power ... but what I find curious is that an amd64 dom0
> does not exhibit this problem despite running from the same sources.
Presumably because there are things that trigger the sysmon_envsys and
sysmon_wdog
whatevers in the dom0 kernel config.
Jonathan Kollasch
Attachment:
pgpdoUq5xWziV.pgp
Description: PGP signature