On 9/15/22 18:58, Chris Narkiewicz wrote:
On Mon, Jul 25, 2022 at 03:27:30PM -0400, Nick Holland wrote:
Somewhere between 7.1 release and -current, X quit working
on this machine. It is a really lousy machine, wireless
doesn't work, slow, etc., and it cost $80 new (and is
currently $60), so
On 8/10/22 00:42, Jonathan Gray wrote:
On Tue, Aug 09, 2022 at 10:29:41AM -0400, Nick Holland wrote:
On 8/9/22 09:36, Jonathan Gray wrote:
> On Sat, Aug 06, 2022 at 10:28:06AM -0400, Nick Holland wrote:
> > > When looking at top what does Xorg have for WAIT?
> >
> > PID USERNAME PRI NICE
On Tue, Aug 09, 2022 at 10:29:41AM -0400, Nick Holland wrote:
> On 8/9/22 09:36, Jonathan Gray wrote:
> > On Sat, Aug 06, 2022 at 10:28:06AM -0400, Nick Holland wrote:
> > > > When looking at top what does Xorg have for WAIT?
> > >
> > > PID USERNAME PRI NICE SIZE RES STATE WAIT
On Tue, Aug 09, 2022 at 10:29:41AM -0400, Nick Holland wrote:
> On 8/9/22 09:36, Jonathan Gray wrote:
> > On Sat, Aug 06, 2022 at 10:28:06AM -0400, Nick Holland wrote:
> > > > When looking at top what does Xorg have for WAIT?
> > >
> > > PID USERNAME PRI NICE SIZE RES STATE WAIT
On 8/9/22 09:36, Jonathan Gray wrote:
On Sat, Aug 06, 2022 at 10:28:06AM -0400, Nick Holland wrote:
> When looking at top what does Xorg have for WAIT?
PID USERNAME PRI NICE SIZE RES STATE WAIT TIMECPU COMMAND
41914 _x11 -22 -1 15M 26M idle schto 0:01
On Sat, Aug 06, 2022 at 10:28:06AM -0400, Nick Holland wrote:
> > When looking at top what does Xorg have for WAIT?
>
> PID USERNAME PRI NICE SIZE RES STATE WAIT TIMECPU COMMAND
> 41914 _x11 -22 -1 15M 26M idle schto 0:01 0.00% Xorg
>
> > this will run X
Back from vacation, sorry for the delay in responding...
On 7/28/22 10:04, Jonathan Gray wrote:
On Tue, Jul 26, 2022 at 09:56:21AM -0400, Nick Holland wrote:
On 7/26/22 8:43 AM, Jonathan Gray wrote:
> On Mon, Jul 25, 2022 at 09:34:14PM +0100, Chris Narkiewicz wrote:
> > On Mon, Jul 25, 2022 at
On Tue, Jul 26, 2022 at 09:56:21AM -0400, Nick Holland wrote:
> On 7/26/22 8:43 AM, Jonathan Gray wrote:
> > On Mon, Jul 25, 2022 at 09:34:14PM +0100, Chris Narkiewicz wrote:
> > > On Mon, Jul 25, 2022 at 03:48:19PM -0400, Nick Holland wrote:
> > > > Sigh. collect info, leave out most basic part:
On 7/26/22 8:43 AM, Jonathan Gray wrote:
On Mon, Jul 25, 2022 at 09:34:14PM +0100, Chris Narkiewicz wrote:
On Mon, Jul 25, 2022 at 03:48:19PM -0400, Nick Holland wrote:
> Sigh. collect info, leave out most basic part: what I mean
> by "X quit working"...
I checked your Xorg.0.log and it looks
On Mon, Jul 25, 2022 at 09:34:14PM +0100, Chris Narkiewicz wrote:
> On Mon, Jul 25, 2022 at 03:48:19PM -0400, Nick Holland wrote:
> > Sigh. collect info, leave out most basic part: what I mean
> > by "X quit working"...
>
> I checked your Xorg.0.log and it looks familiar. Please look for post
>
On Tue, Jul 26, 2022 at 04:17:18AM +0100, Chris Narkiewicz wrote:
> On Mon, Jul 25, 2022 at 11:02:25PM -0400, Nick Holland wrote:
> > here's what got added to dmesg after I built and installed a kernel with
> > that patch on my "problem" machine:
> >
> > ... snip ...
> >
On 7/25/22 4:34 PM, Chris Narkiewicz wrote:
On Mon, Jul 25, 2022 at 03:48:19PM -0400, Nick Holland wrote:
Sigh. collect info, leave out most basic part: what I mean
by "X quit working"...
I checked your Xorg.0.log and it looks familiar. Please look for post
"X11 hangs on StarLabs Mk IV -
On 7/25/22 3:27 PM, Nick Holland wrote:
Somewhere between 7.1 release and -current, X quit working
on this machine. It is a really lousy machine, wireless
doesn't work, slow, etc., and it cost $80 new (and is
currently $60), so "What do you expect?" is a valid response.
But in case someone
13 matches
Mail list logo