[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Ltib] Re: LPC3250 board, X server fault: Invalid argument
From: |
Dmitry Vinokurov |
Subject: |
[Ltib] Re: LPC3250 board, X server fault: Invalid argument |
Date: |
Thu, 06 Aug 2009 16:23:33 +0600 |
User-agent: |
Mozilla-Thunderbird 2.0.0.19 (X11/20090103) |
Some news again.
Executing 'Xfbdev -nolisten tcp -ac -mouse mouse -keybd keyboard'
results in:
===
Warning: mode not found, using default
error: Invalid argument
Fatal server error:
no screens found
===
If mode is set (as Daniel advised), 'Xfbdev -nolisten tcp -ac -mouse
mouse -keybd keyboard -screen 320x240x18' (where 18 (6 for each R,G,B)
is depth for my display, according to documentation) results in:
===
error: Invalid argument
Fatal server error:
no screens found
===
Settings resolution to 240x320 or something other lead to mode not found
warning.
I've digged a little in the source and found function throwing an error
-- it is fbdevScreenInitialize. Here is fragment of this function,
containing error (as I think):
===
if (k < 0 || (t->horizontal != var.xres || t->vertical != var.yres))
fbdevConvertMonitorTiming (t, &var);
var.activate = FB_ACTIVATE_NOW;
var.bits_per_pixel = screen->fb[0].depth;
var.nonstd = 0;
var.grayscale = 0;
k = ioctl (priv->fd, FBIOPUT_VSCREENINFO, &var);
if (k < 0)
{
fprintf (stderr, "error: %s\n", strerror (errno));
return FALSE;
}
===
I think error is here because before this code 'struct fb_var_screeninfo
var' was initialized using 'k = ioctl (priv->fd, FBIOGET_VSCREENINFO,
&var);' and all changes of 'var' structure is located exactly in this
code. By the way, 'fbdevConvertMonitorTiming' executes because var.xres
= 240 but t->horizontal = 320 and var.yres = 320 but t->vertical = 240
Adding 'fprintf(stderr, "%dx%dx%d\n", var.xres, var.yres,
var.bits_per_pixel);' before 'k = ioctl (priv->fd, FBIOPUT_VSCREENINFO,
&var);' give '320x240x18'.
Have anybody ideas about this error? I've completely stuck at this point.
--
Best Regards,
Dmitry Vinokurov
<address@hidden>
Dmitry Vinokurov wrote:
Hello,
I've compiled X server "tiny X (kdrive)" package and all packages in
"X11 libraries and packages section".
When I try to execute 'startx' on RDK LPC3250, I get:
/*
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/nxp:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6
*/
Then I try to manually execute first line of startx script with
'-nolisten tcp' parameter:
# Xfbdev -nolisten tcp -ac -mouse mouse -keybd keyboard
And get following output:
/*
Warning: mode not found, using default
error: Invalid argument
Fatal server error:
no screens found
*/
Executing
# Xfbdev -nolisten tcp
gave same output.
Can anybody explain, what exactly argument is invalid and what 'mode'
Xfbdev haven't found?
Thanks in advance.