Project Home
Project Home
Source Code
Source Code
Documents
Documents
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - modular x-window: (10 Items)
   
modular x-window  
Hi!

I'm testing modular-x-window on QNX 6.4.1-i386.
First I have installed all binary packages according to X11 from the pkgsrc-repository
using the pkg_add command.

After a lot of trials and confirurations I'm now able to start the X.Org X Server 1.4.2
with fvwm window manager and some x-Apps like xcalc, xterm, xeyes etc.

In general it works fine, but there are some problems:

1. I have no support to the keyboard bekause the libkbd.so file is missing!
   It should be part of the xf86-input-keyboard package which isn't present
   on the repository.

2. Currently I'm using a serial mouse which is working very fine.
   I'm not able to connect a PS/2- or a USM-Mouse because it is recommended
   to specify a device file (/dev/*) in the xorg.conf file. 
   I don't know, which are the correct device files.

3. At this moment the X-Server can only run in vga mode.
   svga or vesa don't start.

4. It seems that the xorg-packages are outdated. Is it very complicated to distribute
   newer versions?

I hope someone can help me!
Thanks
Andi
Re: modular x-window  
Can you describe details and attach your configuration (xorg.conf, pkg_info output)?

I am trying to run Xorg server, but I got just "Unresolved symbols" from all the video drivers (vga/nv/vesa).
Re: modular x-window  
Hi,

I hope I can help you. I'm only able to run a serial mosue atatched and virtual keyboard only but it is working 
perfectly fine.

first you have to add a lot of libraries for LD_PRELOAD so you will avoid the unresolved symbols.
export LD_PRELOAD=libvgahw.so:libint10.so:libfb.so:libxf1bpp.so:libxf4bpp.so:libshadowfb.so

and attach here my xorg.conf configuration

I hope this helps.

I have compiled all packages here but there was no difference to the binaries.
So the versions are quite old but running

copy the xorg.conf file to /etc/X11 so you can simply start the X server. And then I start  the fvwm

Attachment: Text xorg.conf 4 KB
Re: modular x-window  
Does it help, if you add these section into your /usr/pkg/etc/X11/xorg.conf file?

Section "InputDevice"
        Identifier  "Keyboard0"
        Driver      "kbd"
        Option          "Protocol" "hid"
EndSection

Section "InputDevice"
        Identifier  "Mouse0"
        Driver      "mouse"
        Option          "Protocol" "hid"
        Option      "Device" "/dev/devi/mouse0"
        Option      "ZAxisMapping" "4 5 6 7"
EndSection
Re: modular x-window  
I tried the configuration for mosue and keyboard again but the result was as expected

Here the input sections:


Section "InputDevice"
        Identifier  "Keyboard0"
        Driver      "kbd"
        Option          "Protocol" "hid"
EndSection

Section "InputDevice"
        Identifier  "Mouse0"
        Driver      "mouse"
        Option          "Protocol" "hid"
        Option      "Device" "/dev/devi/mouse0"
        Option      "ZAxisMapping" "4 5 6 7"
EndSection


and here the RESULT :

...
...
(EE) Failed to load module "kbd" (module does not exist, 0)
(II) Module "ddc" already built-in
(EE) Mouse0: cannot open '/dev/devi/mouse0'
(EE) PreInit failed for input device "Mouse0"
(EE) No Input driver matching `kbd'
...
..

The problem is that simply the input drivers are not there 

Re: modular x-window  
After some trials and errors I have managed to run X windows with VESA video mode driver (on NVidia GPU) with 24bpp, USB
 mouse and PS/2 keyboard.

These are the necessary steps:

As you have reported - there is an issue with loading Xserver modules. I believe this is related to library loading path
, because this is handled automatically on Linux. Solution are:
1) preloading libraries as described
2) explicity list the required modules in xorg.conf (see attachments url below).

The next step is to compile xf86-input-keyboard driver from source (with some easy pkgsrc tricks) or download my build.

Then switch off Photon and enter text mode (using "Shutdown" button on login screen). The last command is:
/usr/photon/bin/devi-hid -Pr mouse kbd; startx

This is crucial to start these both as one command, becasue devi-hid overtakes keyboard from text console. You should 
also have xinit, xterm and some other base packages installed. 

My files are here:

http://home.elka.pw.edu.pl/~ptrojane/QNX641/

I have running xterm,xeyes,links in graphics mode. I have also compiled icewm with disabled i18n.

I believe, that we are in the point, where some work should be taken to make more packages from pkgsrc compile under QNX
.
Re: modular x-window  
Hi,

you are absolutely right with the library things.

I have one question. What do you mean with "easy tricks" in pkgsrc ? I have tried that before but the configure script 
was quitting wit (somethign like) "unsupported operating system" message.
Can you tell me the trick ?

For the command lines I'm using telnet sessions from my Windows computer so I can start and quit all the things 
separately.

A lot of programs are already running even the Qt/X11 is running fine here so I assume all Qt based things are no 
problem. Now I'm just trying to get the touchscreen running.

Things to do for example:
Support of newest X versions and window managers like KDE
The main problems with the port would be the lack of open/gl stuff and driver for graphic cards.
Re: modular x-window  
You are absolutely right. It's been a while I forgot all the details. :(

Yes, I end up setting LD_LIBRARY_PATH to make sure X server can find the shared objects. And also, the devi-hid is 
important (I think I put that line in startx script already ...)

X windows are heavily rely on MAP_LAZY, since currently QNX do not support MAP_LAZY, this is the reason why a lot of 
video driver would complain "Unknown Symbols". We are working on address this issue.

I think Sean just drop the latest X window in. I am trying to make sure the source will clean built this time.

-xtang

> After some trials and errors I have managed to run X windows with VESA video 
> mode driver (on NVidia GPU) with 24bpp, USB mouse and PS/2 keyboard.
> 
> These are the necessary steps:
> 
> As you have reported - there is an issue with loading Xserver modules. I 
> believe this is related to library loading path, because this is handled 
> automatically on Linux. Solution are:
> 1) preloading libraries as described
> 2) explicity list the required modules in xorg.conf (see attachments url below
> ).
> 
> The next step is to compile xf86-input-keyboard driver from source (with some 
> easy pkgsrc tricks) or download my build.
> 
> Then switch off Photon and enter text mode (using "Shutdown" button on login 
> screen). The last command is:
> /usr/photon/bin/devi-hid -Pr mouse kbd; startx
> 
> This is crucial to start these both as one command, becasue devi-hid overtakes
>  keyboard from text console. You should also have xinit, xterm and some other 
> base packages installed. 
> 
> My files are here:
> 
> http://home.elka.pw.edu.pl/~ptrojane/QNX641/
> 
> I have running xterm,xeyes,links in graphics mode. I have also compiled icewm 
> with disabled i18n.
> 
> I believe, that we are in the point, where some work should be taken to make 
> more packages from pkgsrc compile under QNX.


Re: modular x-window  
is there any road map to enable the graphics cards drivers regarding the LD_LAZY problem ?

Would it be a workaround to build a wrapper library that will simply load the graphic and has dummy functions to the 
unresolved symbols ?
Re: modular x-window  
> is there any road map to enable the graphics cards drivers regarding the 
> LD_LAZY problem ?

The tools guys are already onto this. We are not sure if it will make it to the next release, but certainly would keep 
people notified.

> Would it be a workaround to build a wrapper library that will simply load the 
> graphic and has dummy functions to the unresolved symbols ?

For simple one (like the vmware driver), you can choose to link all it's required library, this way, a DL_NEEDED would 
be insert into the .so, and all required drivers will be loaded at the same time.

However, I have encounted more complicated drivers, where this method may not work.