nanogui: Thread: nano-X return code 1 with no error information

I've compiled the microwindows 0.89pre8 tarbal on my machine
and everything seemed to compile fine.  I then tried to execute
some of the demos in the demo dir and I can not get nano-X to
run.  I'm just starting it at the command line by typing 'nano-X'
and the screen will blink but a ps -ef shows that nano-X is NOT
running.  The $? after running nano-X is 1 but there is no error
information printed to stderr or stdout when I execute it.

Is this what is supposed to happen?  If so how do I run the demos?


Anthony

On Tue, 30 Apr 2002 17:29:43 -0400
Anthony Rassin ####@####.#### wrote:

> 
> I've compiled the microwindows 0.89pre8 tarbal on my machine
> and everything seemed to compile fine.  I then tried to execute
> some of the demos in the demo dir and I can not get nano-X to
> run.  I'm just starting it at the command line by typing 'nano-X'
> and the screen will blink but a ps -ef shows that nano-X is NOT
> running.  The $? after running nano-X is 1 but there is no error
> information printed to stderr or stdout when I execute it.
you should run the demo by running demo##.sh
or, for ex:
bin/nano-X & bin/nanowm & bin/launcher bin/launcher.cnf 
run the core    window manager    and the demo

Pierre
-- 
c'est quoi ce quatre et ce huit, dans mon adresse email ???

I tried this and still no luck.  To go a bit further, I've recompiled 
microwindows
to run under X11 and I can run all of the demos without problem.  Unfortunatly
when I compile microwindows with framebuffer support, nano-X won't start.

If I run the demo.sh script my output is
nxclient: bad readblock -1
nxclient 7046: Corrupted packet
nxclient: bad readblock -1
nxclient 7047: Corrupted packet
./demo.sh: line 1:   7046 Broken pipe            bin/nanowm
./demo.sh: line 1:   7047 Broken pipe            bin/world

and if I just run nano-X I still get the 1 errorcode ($?) and no error 
information
and it won't run.
Also, if I run nano-X & it immediatly goes into a stopped state.
  ([1]+  Stopped              bin/nano-X)

Any other ideas?

Thanks,
Anthony

BTW: framebuffer support is compiled into my kernel, and I do see the 
penduin when
I boot, and I'm in vesa fb mode 0301 if that helps.

At 12:03 AM 5/1/2002 +0200, Pierre Tardy wrote:
>On Tue, 30 Apr 2002 17:29:43 -0400
>Anthony Rassin ####@####.#### wrote:
>
> >
> > I've compiled the microwindows 0.89pre8 tarbal on my machine
> > and everything seemed to compile fine.  I then tried to execute
> > some of the demos in the demo dir and I can not get nano-X to
> > run.  I'm just starting it at the command line by typing 'nano-X'
> > and the screen will blink but a ps -ef shows that nano-X is NOT
> > running.  The $? after running nano-X is 1 but there is no error
> > information printed to stderr or stdout when I execute it.
>you should run the demo by running demo##.sh
>or, for ex:
>bin/nano-X & bin/nanowm & bin/launcher bin/launcher.cnf
>run the core    window manager    and the demo
>
>Pierre
>--
>c'est quoi ce quatre et ce huit, dans mon adresse email ???

> to run under X11 and I can run all of the demos without problem.
Unfortunatly
> when I compile microwindows with framebuffer support, nano-X won't start.

Undoubtably your kernel isn't setup for framebuffer support
correctly.  Can you change resolutions using the fbset
utility?  run "dmesg | more" to check that the framebuffer
driver initialized correctly.

Regards,

Greg


>
> If I run the demo.sh script my output is
> nxclient: bad readblock -1
> nxclient 7046: Corrupted packet
> nxclient: bad readblock -1
> nxclient 7047: Corrupted packet
> ./demo.sh: line 1:   7046 Broken pipe            bin/nanowm
> ./demo.sh: line 1:   7047 Broken pipe            bin/world
>
> and if I just run nano-X I still get the 1 errorcode ($?) and no error
> information
> and it won't run.
> Also, if I run nano-X & it immediatly goes into a stopped state.
>   ([1]+  Stopped              bin/nano-X)
>
> Any other ideas?
>
> Thanks,
> Anthony
>
> BTW: framebuffer support is compiled into my kernel, and I do see the
> penduin when
> I boot, and I'm in vesa fb mode 0301 if that helps.
>
> At 12:03 AM 5/1/2002 +0200, Pierre Tardy wrote:
> >On Tue, 30 Apr 2002 17:29:43 -0400
> >Anthony Rassin ####@####.#### wrote:
> >
> > >
> > > I've compiled the microwindows 0.89pre8 tarbal on my machine
> > > and everything seemed to compile fine.  I then tried to execute
> > > some of the demos in the demo dir and I can not get nano-X to
> > > run.  I'm just starting it at the command line by typing 'nano-X'
> > > and the screen will blink but a ps -ef shows that nano-X is NOT
> > > running.  The $? after running nano-X is 1 but there is no error
> > > information printed to stderr or stdout when I execute it.
> >you should run the demo by running demo##.sh
> >or, for ex:
> >bin/nano-X & bin/nanowm & bin/launcher bin/launcher.cnf
> >run the core    window manager    and the demo
> >
> >Pierre
> >--
> >c'est quoi ce quatre et ce huit, dans mon adresse email ???
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
>

Here's an update incase anyone is interested (might be helpful in the logs)
It's a mouse problem and not a framebuffer issue.  I recompiled
microwindows without mouse support (NOMOUSE Y) and I can now
start the nano-X core and run the demos, albeit without a mouse.

I don't know the relationship between gpm and nano, but gpm works
on my machine......so I guess I'll start looking there.

Thanks for all of the replies.
Anthony

At 01:12 PM 5/1/2002 -0700, Greg Haerr wrote:
> > to run under X11 and I can run all of the demos without problem.
>Unfortunatly
> > when I compile microwindows with framebuffer support, nano-X won't start.
>
>Undoubtably your kernel isn't setup for framebuffer support
>correctly.  Can you change resolutions using the fbset
>utility?  run "dmesg | more" to check that the framebuffer
>driver initialized correctly.
>
>Regards,
>
>Greg