Re: [Ltib] kdrive problem

[Stuart Hughes]

Hi Haitham,

Does your kernel have frame-buffer support enabled?  by default the 
startx script is going to run:


Xfbdev -ac -mouse mouse -keybd keyboard &
sleep 3
DISPLAY=:0 twm

So this means you need a working framebuffer.

Regards, Stuart


haitham akah wrote:
> Hi again
>
> I managed to stop the FBIOPUT_VSCREENINFO: Invalid argument
>
> by diselecting the "use graphical console" in the kernel configration
>
> the segmentation error disapred also
>
> what I get now is 
> Fatal server error:
> no screens found
> twm:  unable to open display ":0"
> killall: Xfbdev: no process killed
>
> so any help?
> how should I till the xserver that there is a screen?
>
> yours
> Haitham
>  
> --- On Mon, 10/5/09, Stuart Hughes <address@hidden> wrote:
>
> > From: Stuart Hughes <address@hidden>
> > Subject: Re: [Ltib] kdrive problem
> > To: "haitham akah" <address@hidden>
> > Date: Monday, October 5, 2009, 12:40 AM
> > Hi Haitham,
> >
> > I'm not sure what the problem is here.  You may be
> > able to get more help 
> > on the list.  If you do manage to fix this, please
> > send the solution to 
> > the list.
> >
> > The first problem to solve is to stop the X server from
> > causing a SEGV. 
> >   Also check that you have /dev populated as
> > expected.
> >
> > Regards, Stuart
> >
> > haitham akah wrote:
> > > I tried adding mode to kmode.c but no change.
> > >
> > > I recompiled the kernel with IPv6 enabled. this solve
> > the first three errors, so now I get the following errors:
> > > FBIOPUT_VSCREENINFO: Invalid argument
> > >
> > > Fatal server error:
> > > no screens found
> > >
> > > Backtrace (1 deep):
> > > 0: Xfbdev [0x43fc4]
> > >   
> > > FatalError re-entered, aborting
> > > Segmentation fault caught
> > >   
> > > twm:  unable to open display ":0"
> > > killall: Xfbdev: no process killed
> > >
> > > I'll try to solve them one by one asy suggestions? how
> > can I fix the FBIOPUT_VSCREENINFO: Invalid argument (is it
> > because a change in the device deriver interface in the
> > 2.6.27 kernel)
> > > please tell me what would you do and I'll do it in my
> > kit and post the results.
> > > and why doesn't kdrive find a screen (the kernel found
> > it and draw the TUX logo on startup) and even helloworld
> > program could accese it.
> > > --- On Thu, 10/1/09, Stuart Hughes <address@hidden>
> > wrote:
> > > > From: Stuart Hughes <address@hidden>
> > > > Subject: Re: [Ltib] kdrive problem
> > > > To: "haitham akah" <address@hidden>
> > > > Cc: address@hidden
> > > > Date: Thursday, October 1, 2009, 1:39 AM
> > > > Hi Haitham,
> > > >
> > > > Unfortunately I don't have one of those boards to
> > > > investigate.  However the 'startx' script in
> > LTIB only
> > > > has this:
> > > >
> > > >
> > > > Xfbdev -ac -mouse mouse -keybd keyboard &
> > > > sleep 3
> > > > DISPLAY=:0 twm
> > > > killall Xfbdev
> > > >
> > > >
> > > > It might be worth trying 'Xfbdev' from the command
> > line
> > > > with no command line args.  It looks like the
> > X server
> > > > may be crashing.  There's some comments here:
> > http://www.libertatia.org/blog/?p=66
> > > > Regards, Stuart
> > > >
> > > > haitham akah wrote:
> > > > > Hi there,
> > > > >
> > > > > I have the Arm9diim kit (LPC3250) I'm trying
> > to build
> > > > an xserver for it.
> > > > > I used LTIB for bulding the rootfs and kernel.
> > they
> > > > build ok.
> > > > > but when I try startx i get this massege :
> > > > >
> > > > > address@hidden /root]# startx
> > > > > _XSERVTransSocketOpenCOTSServer: Unable to
> > open socket
> > > > for inet6
> > > > > _XSERVTransOpen: transport open failed for
> > > > inet6/nxp:0
> > > > > _XSERVTransMakeAllCOTSServerListeners: failed
> > to open
> > > > listener for inet6
> > > > > FBIOPUT_VSCREENINFO: Invalid argument
> > > > >
> > > > > Fatal server error:
> > > > > no screens found
> > > > >
> > > > > Backtrace (1 deep):
> > > > > 0: Xfbdev [0x43fc4]
> > > > >
> > > > > FatalError re-entered, aborting
> > > > > Segmentation fault caught
> > > > >
> > > > > twm:  unable to open display ":0"
> > > > > killall: Xfbdev: no process killed
> > > > >
> > > > >
> > > > > so what is the problem?? or where can I change
> > the
> > > > kdrive configration to try other options??
> > > > > please help
> > > > >
> > > > > yours
> > > > > haitham
> > > > >
> > > > >
> > > > >         
> > _______________________________________________
> > > > > LTIB home page: http://ltib.org
> > > > >
> > > > > Ltib mailing list
> > > > > address@hidden
> > > > > http://lists.nongnu.org/mailman/listinfo/ltib
> > >
> > >        
>
>
>