On Fri, Jun 17, 2022 at 12:46:49PM -0700, Mike Larkin wrote:
> Sorry, out of ideas.
No worries. Thanks for all of the back and forth :)
--
Best Regards
Edd Barrett
https://www.theunixzoo.co.uk
On Fri, Jun 17, 2022 at 08:32:29PM +0100, Edd Barrett wrote:
> Hi Mike,
>
> On Fri, Jun 17, 2022 at 11:55:51AM -0700, Mike Larkin wrote:
> > > - disabling xhci in ukc: the system fails to boot multi-user. The first
> > >oddness comes where cpus #1-3 fail to "become ready" (as reported by
> >
Hi Mike,
On Fri, Jun 17, 2022 at 11:55:51AM -0700, Mike Larkin wrote:
> > - disabling xhci in ukc: the system fails to boot multi-user. The first
> >oddness comes where cpus #1-3 fail to "become ready" (as reported by
> > dmesg).
> >It spends a while thinking about these cores not
On Fri, Jun 17, 2022 at 06:41:23PM +0100, Edd Barrett wrote:
> Hi Mike,
>
> On Fri, Jun 17, 2022 at 10:20:35AM -0700, Mike Larkin wrote:
> > Oh, didn't read this closely enough the first time. If ZZZ doesn't
> > instantly wake
> > the machine, then it's one of the two S3 devices described in your
Hi Mike,
On Fri, Jun 17, 2022 at 10:20:35AM -0700, Mike Larkin wrote:
> Oh, didn't read this closely enough the first time. If ZZZ doesn't instantly
> wake
> the machine, then it's one of the two S3 devices described in your next email.
> Since one is XHCI, I'd disable xhci in ukc and see if
On Fri, Jun 17, 2022 at 09:14:45AM +0100, Edd Barrett wrote:
> Hi Mike,
>
> On Thu, Jun 16, 2022 at 09:19:50PM -0700, Mike Larkin wrote:
> > From your original dmesg:
> >
> > > acpi0: wakeup devices PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4)
> > > PEGP(S4) SIO1(S3) RP09(S4) PXSX(S4) RP10(S4)
On Fri, Jun 17, 2022 at 09:14:45AM +0100, Edd Barrett wrote:
> Hi Mike,
>
> On Thu, Jun 16, 2022 at 09:19:50PM -0700, Mike Larkin wrote:
> > From your original dmesg:
> >
> > > acpi0: wakeup devices PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4)
> > > PEGP(S4) SIO1(S3) RP09(S4) PXSX(S4) RP10(S4)
On Fri, Jun 17, 2022 at 09:14:45AM +0100, Edd Barrett wrote:
> > 1. remove the code that truncates this list after 16, and note down all the
> > wake devices.
Here's the full list:
acpi0: wakeup devices PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) PEGP(S4)
SIO1(S3) RP09(S4) PXSX(S4) RP10(S4)
Hi Mike,
On Thu, Jun 16, 2022 at 09:19:50PM -0700, Mike Larkin wrote:
> From your original dmesg:
>
> > acpi0: wakeup devices PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) PEGP(S4)
> > SIO1(S3) RP09(S4) PXSX(S4) RP10(S4) PXSX(S4) RP11(S4) PXSX(S4) RP12(S4)
> > PXSX(S4) RP13(S4) [...]
>
>
On Thu, Jun 16, 2022 at 08:48:36PM +0100, Edd Barrett wrote:
> On Thu, Jun 16, 2022 at 10:22:16AM -0700, Mike Larkin wrote:
> > did it ever work in the past?
>
> I've only just received the machine, so it's difficult to say.
>
> I've spent the last hour changing various BIOS settings to see if
On Thu, Jun 16, 2022 at 10:22:16AM -0700, Mike Larkin wrote:
> did it ever work in the past?
I've only just received the machine, so it's difficult to say.
I've spent the last hour changing various BIOS settings to see if anything
changes, but alas no. I don't see any sleep-related power
On Thu, Jun 16, 2022 at 05:14:53PM +0100, Edd Barrett wrote:
> Hi,
>
> Has anyone managed to get a Lenovo ThinkCentre M910q (or similar) to suspend
> with OpenBSD?
>
> When invoking `zzz` the system prepares to go down, the screen goes blank, but
> then a short while later, the system comes back,
Hi,
Has anyone managed to get a Lenovo ThinkCentre M910q (or similar) to suspend
with OpenBSD?
When invoking `zzz` the system prepares to go down, the screen goes blank, but
then a short while later, the system comes back, as though it was awoken
straight away.
Here's the diff between the
13 matches
Mail list logo
