Tiny Core Linux

Tiny Core Base => TCB Q&A Forum => Topic started by: jqcore on April 10, 2013, 10:05:52 PM

Title: WYSE V50LE dual screen setup
Post by: jqcore on April 10, 2013, 10:05:52 PM: I have been trying to setup dual screen on this puppy and was not able to.

I know it works because the WYSE Linux OS works with dual screen.

I tried using xf86-video-openchrome, it loads and X starts but all I get is a black screen on the second screen.

Here is the output of lspci:

01:00.0 VGA compatible controller: VIA Technologies, Inc. CN700/P4M800 Pro/P4M800 CE/VN800 [S3 UniChrome Pro] (rev 01)

Here is the output of lsmod: (I cant see openchrome here)
tc@box:~$ lsmod
Module Size Used by Tainted: P
cpufreq_userspace 12288 0
cpufreq_powersave 12288 0
cpufreq_stats 12288 0
cpufreq_conservative 12288 0
squashfs 24576 37
ppdev 12288 0
scsi_wait_scan 12288 0
pcspkr 12288 0
parport_pc 24576 0
parport 24576 2 ppdev,parport_pc
via_rhine 20480 0
zcache 12288 0
zram 12288 1
loop 16384 74
tc@box:~$
Title: Re: WYSE V50LE dual screen setup
Post by: tinypoodle on April 10, 2013, 11:00:36 PM: Quote from: jqcore on April 10, 2013, 10:05:52 PM
Here is the output of lsmod: (I cant see openchrome here)

As expected, it's a userland driver and according to your Xorg.0.log gets loaded.

However:
Code: [Select]
[drm] failed to load kernel module "via"
Do you have graphics-3.0.21-tinycore.tcz loaded?
Title: Re: WYSE V50LE dual screen setup
Post by: jqcore on April 10, 2013, 11:37:37 PM: Yes, I just removed it and tried again with the same result.
Title: Re: WYSE V50LE dual screen setup
Post by: curaga on April 11, 2013, 05:17:05 AM: What happens if you try to set it up dynamically, with xrandr commands?
Title: Re: WYSE V50LE dual screen setup
Post by: jqcore on April 11, 2013, 09:34:53 AM: I get below when running xrandr -q

xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1280 x 1024, current 1280 x 1024, maximum 1280 x 1024
default connected 1280x1024+0+0 0mm x 0mm
1280x1024 75.0*
Title: Re: WYSE V50LE dual screen setup
Post by: jqcore on April 11, 2013, 10:46:13 PM: I read from openchrome and unichrome site that dual head is not supported. :(

I tried compiling the driver from VIA's site but getting Fatal error: xf86Resources.h No such file or directory,
Read it somewhere that this has been removed in version xorg 1.7.

I think using Xorg-7.4.tcz should work but I do'nt know how to proceed because i do not see Xorg-7.4-dev.tcz..

Can anyone share how to build (Xorg-7.4-dev / lib /bin)? so I can try compiling VIA's official driver...

Thanks
Title: Re: WYSE V50LE dual screen setup
Post by: Rich on April 11, 2013, 11:18:07 PM: Hi jqcore
Xorg-7.4-dev.tcz is available in the 3.x repository and is the same version as Xorg-7.4.tcz in the 4.x repository.
Title: Re: WYSE V50LE dual screen setup
Post by: Rich on April 11, 2013, 11:22:10 PM: Hi jqcore
By the way, Xorg-7.4-dev.tcz does contain xf86Resources.h.
Title: Re: WYSE V50LE dual screen setup
Post by: jqcore on April 11, 2013, 11:34:34 PM: where can I download Xorg-7.4-dev.tcz, cant seem to find it.

Thanks
Title: Re: WYSE V50LE dual screen setup
Post by: Rich on April 11, 2013, 11:40:47 PM: Hi jqcore
Try:
Code: [Select]
wget http://tinycorelinux.net/3.x/tcz/Xorg-7.4-dev.tczYou might also need the dependency file:
Code: [Select]
wget http://tinycorelinux.net/3.x/tcz/Xorg-7.4-dev.tcz.dep
Title: Re: WYSE V50LE dual screen setup
Post by: jqcore on April 12, 2013, 01:19:12 PM: Now I get panoramiXproto.h no such file or directory, the file is there when I search it..

I'm lost..

Thanks
Title: Re: WYSE V50LE dual screen setup
Post by: Rich on April 12, 2013, 01:29:46 PM: Hi jqcore
It might be helpful if you paste the error message and some of the lines preceding it in your next post. Use the mouse
with the left button held down to highlight the text in the terminal. Then paste it in the browser by middle clicking.
Please use code tags.
Title: Re: WYSE V50LE dual screen setup
Post by: jqcore on April 13, 2013, 12:39:55 PM: Code: [Select]
[tc@box:~/via-xserver-86a-50283_src/XServer$ make make all-recursive make[1]: Entering directory `/home/tc/via-xserver-86a-50283_src/XServer' Making all in src make[2]: Entering directory `/home/tc/via-xserver-86a-50283_src/XServer/src' /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -O2 -I/usr/local/include/xorg -I/usr/local/include/pixman-1 -I/usr/local/include -DXFree86LOADER -I/usr/local/include -I/usr/local/include/drm -I/usr/local/include/X11/dri -I/usr/include/X11 -I/usr/include/X11/extensions -I.. -I. -O2 -MT via_common.lo -MD -MP -MF .deps/via_common.Tpo -c -o via_common.lo via_common.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -O2 -I/usr/local/include/xorg -I/usr/local/include/pixman-1 -I/usr/local/include -DXFree86LOADER -I/usr/local/include -I/usr/local/include/drm -I/usr/local/include/X11/dri -I/usr/include/X11 -I/usr/include/X11/extensions -I.. -I. -O2 -MT via_common.lo -MD -MP -MF .deps/via_common.Tpo -c via_common.c -fPIC -DPIC -o .libs/via_common.o In file included from via_driver.h:66:0, from via_common.h:29, from via_common.c:32: via_bios.h:32:45: fatal error: panoramiXproto.h: No such file or directory compilation terminated. make[2]: *** [via_common.lo] Error 1 make[2]: Leaving directory `/home/tc/via-xserver-86a-50283_src/XServer/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/tc/via-xserver-86a-50283_src/XServer' make: *** [all] Error 2 tc@box:~/via-xserver-86a-50283_src/XServer$ /code] [code]tc@box:~/via-xserver-86a-50283_src/XServer$ sudo find / -name panoramiXproto.h /tmp/tcloop/Xorg-7.4-dev/usr/local/include/X11/extensions/panoramiXproto.h /usr/local/include/X11/extensions/panoramiXproto.h tc@box:~/via-xserver-86a-50283_src/XServer$
Title: Re: WYSE V50LE dual screen setup
Post by: jqcore on April 13, 2013, 12:42:36 PM: and here's the autogen.sh output.

Code: [Select]
tc@box:~/via-xserver-86a-50283_src/XServer$ ./autogen.sh autoreconf: Entering directory `.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal -I m4 autoreconf: configure.ac: tracing autoreconf: running: libtoolize --copy autoreconf: running: /usr/local/bin/autoconf autoreconf: running: /usr/local/bin/autoheader autoreconf: running: automake --add-missing --copy --no-force autoreconf: Leaving directory `.' checking for a BSD-compatible install... /usr/local/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /usr/local/bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... yes checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking how to print strings... printf checking for style of include used by make... GNU checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... gcc3 checking for a sed that does not truncate output... /usr/local/bin/sed checking for grep that handles long lines and -e... /usr/local/bin/grep checking for egrep... /usr/local/bin/grep -E checking for fgrep... /usr/local/bin/grep -F checking for ld used by gcc... /usr/local/bin/ld checking if the linker (/usr/local/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/local/bin/nm -B checking the name lister (/usr/local/bin/nm -B) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 32768 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... no checking how to convert i686-pc-linux-gnu file names to i686-pc-linux-gnu format... func_convert_file_noop checking how to convert i686-pc-linux-gnu file names to toolchain format... func_convert_file_noop checking for /usr/local/bin/ld option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for dlltool... no checking how to associate runtime and link libraries... printf %s\n checking for ar... ar checking for archiver @FILE support... @ checking for strip... strip checking for ranlib... ranlib checking command to parse /usr/local/bin/nm -B output from gcc object... ok checking for sysroot... no checking for mt... no checking if : is a manifest tool... no checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/local/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... no checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking dependency style of gcc... (cached) gcc3 checking if XINERAMA is defined... yes checking if RANDR is defined... yes checking if RENDER is defined... yes checking if XF86DRI is defined... yes checking if DPM.tension is defined... yes checking if XV is defined... yes checking for pkg-config... /usr/local/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for XORG... yes checking for ANSI C header files... (cached) yes checking for DRI... yes configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating config_via.h config.status: config_via.h is unchanged config.status: executing depfiles commands config.status: executing libtool commands tc@box:~/via-xserver-86a-50283_src/XServer$
Title: Re: WYSE V50LE dual screen setup
Post by: Rich on April 13, 2013, 01:16:14 PM: Hi jqcore
I don't see anything wrong, but I'm no expert. What does the include line for panoramiXproto.h look like in the
via_bios.h file on line 32?
Title: Re: WYSE V50LE dual screen setup
Post by: tinypoodle on April 13, 2013, 01:22:04 PM: Quote from: jqcore on April 13, 2013, 12:39:55 PM
[tc@box:~/via-xserver-86a-50283_src/XServer$ make
make all-recursive
make[1]: Entering directory `/home/tc/via-xserver-86a-50283_src/XServer'
Making all in src
make[2]: Entering directory `/home/tc/via-xserver-86a-50283_src/XServer/src'
/bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -O2 -I/usr/local/include/xorg -I/usr/local/include/pixman-1 -I/usr/local/include -DXFree86LOADER -I/usr/local/include -I/usr/local/include/drm -I/usr/local/include/X11/dri -I/usr/include/X11 -I/usr/include/X11/extensions -I.. -I. -O2 -MT via_common.lo -MD -MP -MF .deps/via_common.Tpo -c -o via_common.lo via_common.c
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -O2 -I/usr/local/include/xorg -I/usr/local/include/pixman-1 -I/usr/local/include -DXFree86LOADER -I/usr/local/include -I/usr/local/include/drm -I/usr/local/include/X11/dri -I/usr/include/X11 -I/usr/include/X11/extensions -I.. -I. -O2 -MT via_common.lo -MD -MP -MF .deps/via_common.Tpo -c via_common.c -fPIC -DPIC -o .libs/via_common.o

In file included from via_driver.h:66:0,
from via_common.h:29,
from via_common.c:32:
via_bios.h:32:45: fatal error: panoramiXproto.h: No such file or directory
compilation terminated.
make[2]: *** [via_common.lo] Error 1
make[2]: Leaving directory `/home/tc/via-xserver-86a-50283_src/XServer/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/tc/via-xserver-86a-50283_src/XServer'
make: *** [all] Error 2
tc@box:~/via-xserver-86a-50283_src/XServer$

tc@box:~/via-xserver-86a-50283_src/XServer$ sudo find / -name panoramiXproto.h
/tmp/tcloop/Xorg-7.4-dev/usr/local/include/X11/extensions/panoramiXproto.h
/usr/local/include/X11/extensions/panoramiXproto.h
tc@box:~/via-xserver-86a-50283_src/XServer$
Title: Re: WYSE V50LE dual screen setup
Post by: jqcore on April 13, 2013, 01:35:36 PM: Line 32 in via_bios.h

Code: [Select]
#include "panoramiXproto.h" /* required */
Title: Re: WYSE V50LE dual screen setup
Post by: Rich on April 13, 2013, 01:38:11 PM: Hi jqcore
Looks like tinypoodle found the problem.
Code: [Select]
-I/usr/include/X11/extensionsshould be:
Code: [Select]
-I/usr/local/include/X11/extensions
@tinypoodle: It took me a couple of minutes to spot what you were pointing out. Maybe use red instead of bold next time?
Title: Re: WYSE V50LE dual screen setup
Post by: tinypoodle on April 13, 2013, 01:59:55 PM: Believe it or not, red was what I tried first of all, somehow didn't want to work, so I ended up with bold which easily worked ;)
Title: Re: WYSE V50LE dual screen setup
Post by: jqcore on April 13, 2013, 02:02:47 PM: How should I proceed, newbie here! ;D
Title: Re: WYSE V50LE dual screen setup
Post by: Rich on April 13, 2013, 02:20:15 PM: Hi jqcore
This might work:
Code: [Select]
export CFLAGS="-I/usr/local/include/X11/extensions" export CXXFLAGS="-I/usr/local/include/X11/extensions" make all-recursivethough that's probably not the right way to solve it.
Title: Re: WYSE V50LE dual screen setup
Post by: tinypoodle on April 13, 2013, 02:29:18 PM: Symlinking might work, but depends on what - if any - is already there under /usr/include.
Title: Re: WYSE V50LE dual screen setup
Post by: Rich on April 13, 2013, 02:33:29 PM: Hi tinypoodle
/usr/include already has an extensions subdirectory as part of Xorg-7.4-dev.
Title: Re: WYSE V50LE dual screen setup
Post by: jqcore on April 13, 2013, 02:36:43 PM: I tried Rich suggestion and got the same output as last time..
Title: Re: WYSE V50LE dual screen setup
Post by: tinypoodle on April 13, 2013, 02:42:47 PM: Quote from: Rich on April 13, 2013, 02:33:29 PM
Hi tinypoodle
/usr/include already has an extensions subdirectory as part of Xorg-7.4-dev.

What I feared...
Then it would come down to symlinking single files not already there...
Title: Re: WYSE V50LE dual screen setup
Post by: Rich on April 13, 2013, 02:46:05 PM: Hi jqcore
Maybe the linker needs it too:
Code: [Select]
export CFLAGS="-I/usr/local/include/X11/extensions" export CXXFLAGS="-I/usr/local/include/X11/extensions" export LDFLAGS="-I/usr/local/include/X11/extensions" make all-recursiveIf that doesn't work, you could try a brute force approach:
Code: [Select]
sudo cp /usr/local/include/X11/extensions/* /usr/include/X11/extensionsor wait for someone more experienced to provide a proper answer.
Title: Re: WYSE V50LE dual screen setup
Post by: jqcore on April 13, 2013, 02:48:23 PM: I did a symlink and got pass that error.

here's a new one, does it look like its good to go?

Code: [Select]
tc@box:~/via-xserver-86a-50283_src/XServer$ make make all-recursive make[1]: Entering directory `/home/tc/via-xserver-86a-50283_src/XServer' Making all in src make[2]: Entering directory `/home/tc/via-xserver-86a-50283_src/XServer/src' /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -O2 -I/usr/local/include/xorg -I/usr/local/include/pixman-1 -I/usr/local/include -DXFree86LOADER -I/usr/local/include -I/usr/local/include/drm -I/usr/local/include/X11/dri -I/usr/include/X11 -I/usr/include/X11/extensions -I.. -I. -O2 -MT via_common.lo -MD -MP -MF .deps/via_common.Tpo -c -o via_common.lo via_common.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -O2 -I/usr/local/include/xorg -I/usr/local/include/pixman-1 -I/usr/local/include -DXFree86LOADER -I/usr/local/include -I/usr/local/include/drm -I/usr/local/include/X11/dri -I/usr/include/X11 -I/usr/include/X11/extensions -I.. -I. -O2 -MT via_common.lo -MD -MP -MF .deps/via_common.Tpo -c via_common.c -fPIC -DPIC -o .libs/via_common.o In file included from via_driver.h:90:0, from via_common.h:29, from via_common.c:32: via_3d.h:380:18: error: duplicate member 'bpp' In file included from via_driver.h:92:0, from via_common.h:29, from via_common.c:32: via_swov.h:346:23: error: duplicate member 'singleview' via_swov.h:349:23: error: duplicate member 'reserverd' make[2]: *** [via_common.lo] Error 1 make[2]: Leaving directory `/home/tc/via-xserver-86a-50283_src/XServer/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/tc/via-xserver-86a-50283_src/XServer' make: *** [all] Error 2 tc@box:~/via-xserver-86a-50283_src/XServer$
Title: Re: WYSE V50LE dual screen setup
Post by: Rich on April 13, 2013, 03:14:03 PM: Hi jqcore
No, you still have problems. Maybe someone like AmatCoder will see this thread and know what to do. You could
send him a PM with a link to this thread and ask if he can help.
Title: Re: WYSE V50LE dual screen setup
Post by: jqcore on April 13, 2013, 03:25:22 PM: I was able to get it going, now how do I load the driver, (insmod, modprobe)

I just had to symlynk 4 more files and edited the 3 below files, it is a duplicate entry.

via_3d.h:380:18: error: duplicate member 'bpp'
via_swov.h:346:23: error: duplicate member 'singleview'
via_swov.h:349:23: error: duplicate member 'reserverd

As you can see the make and make install finished.

Code: [Select]
tc@box:~/via-xserver-86a-50283_src/XServer$ make make all-recursive make[1]: Entering directory `/home/tc/via-xserver-86a-50283_src/XServer' Making all in src make[2]: Entering directory `/home/tc/via-xserver-86a-50283_src/XServer/src' /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -O2 -I/usr/local/include/xorg -I/usr/local/include/pixman-1 -I/usr/local/include -DXFree86LOADER -I/usr/local/include -I/usr/local/include/drm -I/usr/local/include/X11/dri -I/usr/include/X11 -I/usr/include/X11/extensions -I.. -I. -O2 -MT via_swov.lo -MD -MP -MF .deps/via_swov.Tpo -c -o via_swov.lo via_swov.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -O2 -I/usr/local/include/xorg -I/usr/local/include/pixman-1 -I/usr/local/include -DXFree86LOADER -I/usr/local/include -I/usr/local/include/drm -I/usr/local/include/X11/dri -I/usr/include/X11 -I/usr/include/X11/extensions -I.. -I. -O2 -MT via_swov.lo -MD -MP -MF .deps/via_swov.Tpo -c via_swov.c -fPIC -DPIC -o .libs/via_swov.o mv -f .deps/via_swov.Tpo .deps/via_swov.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -O2 -I/usr/local/include/xorg -I/usr/local/include/pixman-1 -I/usr/local/include -DXFree86LOADER -I/usr/local/include -I/usr/local/include/drm -I/usr/local/include/X11/dri -I/usr/include/X11 -I/usr/include/X11/extensions -I.. -I. -O2 -MT via_eng_fops.lo -MD -MP -MF .deps/via_eng_fops.Tpo -c -o via_eng_fops.lo via_eng_fops.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -O2 -I/usr/local/include/xorg -I/usr/local/include/pixman-1 -I/usr/local/include -DXFree86LOADER -I/usr/local/include -I/usr/local/include/drm -I/usr/local/include/X11/dri -I/usr/include/X11 -I/usr/include/X11/extensions -I.. -I. -O2 -MT via_eng_fops.lo -MD -MP -MF .deps/via_eng_fops.Tpo -c via_eng_fops.c -fPIC -DPIC -o .libs/via_eng_fops.o mv -f .deps/via_eng_fops.Tpo .deps/via_eng_fops.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -O2 -I/usr/local/include/xorg -I/usr/local/include/pixman-1 -I/usr/local/include -DXFree86LOADER -I/usr/local/include -I/usr/local/include/drm -I/usr/local/include/X11/dri -I/usr/include/X11 -I/usr/include/X11/extensions -I.. -I. -O2 -MT via_eng_fops_cme.lo -MD -MP -MF .deps/via_eng_fops_cme.Tpo -c -o via_eng_fops_cme.lo via_eng_fops_cme.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -O2 -I/usr/local/include/xorg -I/usr/local/include/pixman-1 -I/usr/local/include -DXFree86LOADER -I/usr/local/include -I/usr/local/include/drm -I/usr/local/include/X11/dri -I/usr/include/X11 -I/usr/include/X11/extensions -I.. -I. -O2 -MT via_eng_fops_cme.lo -MD -MP -MF .deps/via_eng_fops_cme.Tpo -c via_eng_fops_cme.c -fPIC -DPIC -o .libs/via_eng_fops_cme.o mv -f .deps/via_eng_fops_cme.Tpo .deps/via_eng_fops_cme.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -O2 -I/usr/local/include/xorg -I/usr/local/include/pixman-1 -I/usr/local/include -DXFree86LOADER -I/usr/local/include -I/usr/local/include/drm -I/usr/local/include/X11/dri -I/usr/include/X11 -I/usr/include/X11/extensions -I.. -I. -O2 -MT via_eng_fops_cle.lo -MD -MP -MF .deps/via_eng_fops_cle.Tpo -c -o via_eng_fops_cle.lo via_eng_fops_cle.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -O2 -I/usr/local/include/xorg -I/usr/local/include/pixman-1 -I/usr/local/include -DXFree86LOADER -I/usr/local/include -I/usr/local/include/drm -I/usr/local/include/X11/dri -I/usr/include/X11 -I/usr/include/X11/extensions -I.. -I. -O2 -MT via_eng_fops_cle.lo -MD -MP -MF .deps/via_eng_fops_cle.Tpo -c via_eng_fops_cle.c -fPIC -DPIC -o .libs/via_eng_fops_cle.o mv -f .deps/via_eng_fops_cle.Tpo .deps/via_eng_fops_cle.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -O2 -I/usr/local/include/xorg -I/usr/local/include/pixman-1 -I/usr/local/include -DXFree86LOADER -I/usr/local/include -I/usr/local/include/drm -I/usr/local/include/X11/dri -I/usr/include/X11 -I/usr/include/X11/extensions -I.. -I. -O2 -MT via_eng_reg_fops.lo -MD -MP -MF .deps/via_eng_reg_fops.Tpo -c -o via_eng_reg_fops.lo via_eng_reg_fops.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -O2 -I/usr/local/include/xorg -I/usr/local/include/pixman-1 -I/usr/local/include -DXFree86LOADER -I/usr/local/include -I/usr/local/include/drm -I/usr/local/include/X11/dri -I/usr/include/X11 -I/usr/include/X11/extensions -I.. -I. -O2 -MT via_eng_reg_fops.lo -MD -MP -MF .deps/via_eng_reg_fops.Tpo -c via_eng_reg_fops.c -fPIC -DPIC -o .libs/via_eng_reg_fops.o mv -f .deps/via_eng_reg_fops.Tpo .deps/via_eng_reg_fops.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -O2 -I/usr/local/include/xorg -I/usr/local/include/pixman-1 -I/usr/local/include -DXFree86LOADER -I/usr/local/include -I/usr/local/include/drm -I/usr/local/include/X11/dri -I/usr/include/X11 -I/usr/include/X11/extensions -I.. -I. -O2 -MT via_memmgr.lo -MD -MP -MF .deps/via_memmgr.Tpo -c -o via_memmgr.lo via_memmgr.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -O2 -I/usr/local/include/xorg -I/usr/local/include/pixman-1 -I/usr/local/include -DXFree86LOADER -I/usr/local/include -I/usr/local/include/drm -I/usr/local/include/X11/dri -I/usr/include/X11 -I/usr/include/X11/extensions -I.. -I. -O2 -MT via_memmgr.lo -MD -MP -MF .deps/via_memmgr.Tpo -c via_memmgr.c -fPIC -DPIC -o .libs/via_memmgr.o mv -f .deps/via_memmgr.Tpo .deps/via_memmgr.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -O2 -I/usr/local/include/xorg -I/usr/local/include/pixman-1 -I/usr/local/include -DXFree86LOADER -I/usr/local/include -I/usr/local/include/drm -I/usr/local/include/X11/dri -I/usr/include/X11 -I/usr/include/X11/extensions -I.. -I. -O2 -MT via_vt1636.lo -MD -MP -MF .deps/via_vt1636.Tpo -c -o via_vt1636.lo via_vt1636.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -O2 -I/usr/local/include/xorg -I/usr/local/include/pixman-1 -I/usr/local/include -DXFree86LOADER -I/usr/local/include -I/usr/local/include/drm -I/usr/local/include/X11/dri -I/usr/include/X11 -I/usr/include/X11/extensions -I.. -I. -O2 -MT via_vt1636.lo -MD -MP -MF .deps/via_vt1636.Tpo -c via_vt1636.c -fPIC -DPIC -o .libs/via_vt1636.o mv -f .deps/via_vt1636.Tpo .deps/via_vt1636.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -O2 -I/usr/local/include/xorg -I/usr/local/include/pixman-1 -I/usr/local/include -DXFree86LOADER -I/usr/local/include -I/usr/local/include/drm -I/usr/local/include/X11/dri -I/usr/include/X11 -I/usr/include/X11/extensions -I.. -I. -O2 -MT via_rotate.lo -MD -MP -MF .deps/via_rotate.Tpo -c -o via_rotate.lo via_rotate.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -O2 -I/usr/local/include/xorg -I/usr/local/include/pixman-1 -I/usr/local/include -DXFree86LOADER -I/usr/local/include -I/usr/local/include/drm -I/usr/local/include/X11/dri -I/usr/include/X11 -I/usr/include/X11/extensions -I.. -I. -O2 -MT via_rotate.lo -MD -MP -MF .deps/via_rotate.Tpo -c via_rotate.c -fPIC -DPIC -o .libs/via_rotate.o mv -f .deps/via_rotate.Tpo .deps/via_rotate.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -O2 -I/usr/local/include/xorg -I/usr/local/include/pixman-1 -I/usr/local/include -DXFree86LOADER -I/usr/local/include -I/usr/local/include/drm -I/usr/local/include/X11/dri -I/usr/include/X11 -I/usr/include/X11/extensions -I.. -I. -O2 -MT video_rotate.lo -MD -MP -MF .deps/video_rotate.Tpo -c -o video_rotate.lo video_rotate.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -O2 -I/usr/local/include/xorg -I/usr/local/include/pixman-1 -I/usr/local/include -DXFree86LOADER -I/usr/local/include -I/usr/local/include/drm -I/usr/local/include/X11/dri -I/usr/include/X11 -I/usr/include/X11/extensions -I.. -I. -O2 -MT video_rotate.lo -MD -MP -MF .deps/video_rotate.Tpo -c video_rotate.c -fPIC -DPIC -o .libs/video_rotate.o mv -f .deps/video_rotate.Tpo .deps/video_rotate.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -O2 -I/usr/local/include/xorg -I/usr/local/include/pixman-1 -I/usr/local/include -DXFree86LOADER -I/usr/local/include -I/usr/local/include/drm -I/usr/local/include/X11/dri -I/usr/include/X11 -I/usr/include/X11/extensions -I.. -I. -O2 -MT via_texvideo.lo -MD -MP -MF .deps/via_texvideo.Tpo -c -o via_texvideo.lo via_texvideo.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -O2 -I/usr/local/include/xorg -I/usr/local/include/pixman-1 -I/usr/local/include -DXFree86LOADER -I/usr/local/include -I/usr/local/include/drm -I/usr/local/include/X11/dri -I/usr/include/X11 -I/usr/include/X11/extensions -I.. -I. -O2 -MT via_texvideo.lo -MD -MP -MF .deps/via_texvideo.Tpo -c via_texvideo.c -fPIC -DPIC -o .libs/via_texvideo.o mv -f .deps/via_texvideo.Tpo .deps/via_texvideo.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -O2 -I/usr/local/include/xorg -I/usr/local/include/pixman-1 -I/usr/local/include -DXFree86LOADER -I/usr/local/include -I/usr/local/include/drm -I/usr/local/include/X11/dri -I/usr/include/X11 -I/usr/include/X11/extensions -I.. -I. -O2 -MT via_Hw3DScaling.lo -MD -MP -MF .deps/via_Hw3DScaling.Tpo -c -o via_Hw3DScaling.lo via_Hw3DScaling.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -O2 -I/usr/local/include/xorg -I/usr/local/include/pixman-1 -I/usr/local/include -DXFree86LOADER -I/usr/local/include -I/usr/local/include/drm -I/usr/local/include/X11/dri -I/usr/include/X11 -I/usr/include/X11/extensions -I.. -I. -O2 -MT via_Hw3DScaling.lo -MD -MP -MF .deps/via_Hw3DScaling.Tpo -c via_Hw3DScaling.c -fPIC -DPIC -o .libs/via_Hw3DScaling.o mv -f .deps/via_Hw3DScaling.Tpo .deps/via_Hw3DScaling.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -O2 -I/usr/local/include/xorg -I/usr/local/include/pixman-1 -I/usr/local/include -DXFree86LOADER -I/usr/local/include -I/usr/local/include/drm -I/usr/local/include/X11/dri -I/usr/include/X11 -I/usr/include/X11/extensions -I.. -I. -O2 -MT agpctl.lo -MD -MP -MF .deps/agpctl.Tpo -c -o agpctl.lo agpctl.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -O2 -I/usr/local/include/xorg -I/usr/local/include/pixman-1 -I/usr/local/include -DXFree86LOADER -I/usr/local/include -I/usr/local/include/drm -I/usr/local/include/X11/dri -I/usr/include/X11 -I/usr/include/X11/extensions -I.. -I. -O2 -MT agpctl.lo -MD -MP -MF .deps/agpctl.Tpo -c agpctl.c -fPIC -DPIC -o .libs/agpctl.o mv -f .deps/agpctl.Tpo .deps/agpctl.Plo /bin/sh ../libtool --tag=CC --mode=link gcc -O2 -I/usr/local/include/xorg -I/usr/local/include/pixman-1 -I/usr/local/include -DXFree86LOADER -I/usr/local/include -I/usr/local/include/drm -I/usr/local/include/X11/dri -I/usr/include/X11 -I/usr/include/X11/extensions -I.. -I. -O2 -module -avoid-version -o via_drv.la -rpath /usr/lib/xorg/modules/drivers via_common.lo via_serial.lo via_displcd.lo hw.lo via_accel.lo via_xaa.lo via_exa.lo via_exa_h5.lo via_exa_h6.lo via_3d.lo via_bandwidth.lo via_bios.lo via_cursor.lo via_output.lo via_display.lo via_dga.lo via_dri.lo via_driver.lo via_dvi.lo via_gpioi2c.lo via_i2c.lo via_lcd.lo via_mergedfb.lo via_shadow.lo via_utility.lo via_video.lo xf86drmVIA.lo via_dmabuffer.lo via_swov.lo via_eng_fops.lo via_eng_fops_cme.lo via_eng_fops_cle.lo via_eng_reg_fops.lo via_memmgr.lo via_vt1636.lo via_rotate.lo video_rotate.lo via_texvideo.lo via_Hw3DScaling.lo agpctl.lo libtool: link: gcc -shared -fPIC -DPIC .libs/via_common.o .libs/via_serial.o .libs/via_displcd.o .libs/hw.o .libs/via_accel.o .libs/via_xaa.o .libs/via_exa.o .libs/via_exa_h5.o .libs/via_exa_h6.o .libs/via_3d.o .libs/via_bandwidth.o .libs/via_bios.o .libs/via_cursor.o .libs/via_output.o .libs/via_display.o .libs/via_dga.o .libs/via_dri.o .libs/via_driver.o .libs/via_dvi.o .libs/via_gpioi2c.o .libs/via_i2c.o .libs/via_lcd.o .libs/via_mergedfb.o .libs/via_shadow.o .libs/via_utility.o .libs/via_video.o .libs/xf86drmVIA.o .libs/via_dmabuffer.o .libs/via_swov.o .libs/via_eng_fops.o .libs/via_eng_fops_cme.o .libs/via_eng_fops_cle.o .libs/via_eng_reg_fops.o .libs/via_memmgr.o .libs/via_vt1636.o .libs/via_rotate.o .libs/video_rotate.o .libs/via_texvideo.o .libs/via_Hw3DScaling.o .libs/agpctl.o -O2 -O2 -Wl,-soname -Wl,via_drv.so -o .libs/via_drv.so libtool: link: ( cd ".libs" && rm -f "via_drv.la" && ln -s "../via_drv.la" "via_drv.la" ) make[2]: Leaving directory `/home/tc/via-xserver-86a-50283_src/XServer/src' make[2]: Entering directory `/home/tc/via-xserver-86a-50283_src/XServer' make[2]: Nothing to be done for `all-am'. make[2]: Leaving directory `/home/tc/via-xserver-86a-50283_src/XServer' make[1]: Leaving directory `/home/tc/via-xserver-86a-50283_src/XServer' tc@box:~/via-xserver-86a-50283_src/XServer$ sudo make install Making install in src make[1]: Entering directory `/home/tc/via-xserver-86a-50283_src/XServer/src' make[2]: Entering directory `/home/tc/via-xserver-86a-50283_src/XServer/src' make[2]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/xorg/modules/drivers" || /usr/local/bin/mkdir -p "/usr/lib/xorg/modules/drivers" /bin/sh ../libtool --mode=install /usr/local/bin/install -c via_drv.la '/usr/lib/xorg/modules/drivers' libtool: install: /usr/local/bin/install -c .libs/via_drv.so /usr/lib/xorg/modules/drivers/via_drv.so libtool: install: /usr/local/bin/install -c .libs/via_drv.lai /usr/lib/xorg/modules/drivers/via_drv.la libtool: finish: PATH="/home/tc/.local/bin:/usr/local/sbin:/usr/local/bin:/apps/bin:/usr/sbin:/usr/bin:/sbin:/bin:/etc/sysconfig/tcedir/ondemand:/sbin" ldconfig -n /usr/lib/xorg/modules/drivers ---------------------------------------------------------------------- Libraries have been installed in: /usr/lib/xorg/modules/drivers If you ever happen to want to link against installed libraries in a given directory, LIBDIR, you must either use libtool, and specify the full pathname of the library, or use the `-LLIBDIR' flag during linking and do at least one of the following: - add LIBDIR to the `LD_LIBRARY_PATH' environment variable during execution - add LIBDIR to the `LD_RUN_PATH' environment variable during linking - use the `-Wl,-rpath -Wl,LIBDIR' linker flag - have your system administrator add LIBDIR to `/etc/ld.so.conf' See any operating system documentation about shared libraries for more information, such as the ld(1) and ld.so(8) manual pages. ---------------------------------------------------------------------- make[2]: Leaving directory `/home/tc/via-xserver-86a-50283_src/XServer/src' make[1]: Leaving directory `/home/tc/via-xserver-86a-50283_src/XServer/src' make[1]: Entering directory `/home/tc/via-xserver-86a-50283_src/XServer' make[2]: Entering directory `/home/tc/via-xserver-86a-50283_src/XServer' make[2]: Nothing to be done for `install-exec-am'. make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `/home/tc/via-xserver-86a-50283_src/XServer' make[1]: Leaving directory `/home/tc/via-xserver-86a-50283_src/XServer' tc@box:~/via-xserver-86a-50283_src/XServer$
Title: Re: WYSE V50LE dual screen setup
Post by: tinypoodle on April 13, 2013, 03:36:51 PM: Quote from: jqcore on April 13, 2013, 03:25:22 PM
I was able to get it going, now how do I load the driver, (insmod, modprobe)

See Reply #1

Specifying driver in your xorg.conf might work.
Title: Re: WYSE V50LE dual screen setup
Post by: jqcore on April 13, 2013, 03:48:39 PM: That's what I thought.

Thanks for all the help, I'll update the thread with the outcome later on.
Title: Re: WYSE V50LE dual screen setup
Post by: Rich on April 13, 2013, 03:58:36 PM: Hi jqcore
Quote
and edited the 3 below files, it is a duplicate entry.
I have my doubts that it's a duplicate entry. I suspect there is still something missing that modifies those entries to
make them hidden or private or something.
Title: Re: WYSE V50LE dual screen setup
Post by: jqcore on April 16, 2013, 12:17:49 PM: well this did not work, is it easy to downgrade the kernel?

I'm currently running TinyCore 4.7.6, can I downgrade the kernel to 2.6.28 easily?

Thanks,
jqcore
Title: Re: WYSE V50LE dual screen setup
Post by: Rich on April 16, 2013, 12:23:02 PM: Hi jqcore
If you install Tinycore 3.8.4 that will get you to 2.6.33. You can find the ISO here:
http://tinycorelinux.net/3.x/archive/3.8.4/
Title: Re: WYSE V50LE dual screen setup
Post by: jqcore on April 16, 2013, 12:37:31 PM: the source for via official legacy driver said its only for kernel version 2.6.28 and below..

I'll try tinycore 1.4 and see if i'm able to get it going...
Title: Re: WYSE V50LE dual screen setup
Post by: tinypoodle on April 16, 2013, 04:35:43 PM: Before you go into that, have you excluded that a more generic driver like vesa or fbdev could do what you want to achieve?
Title: Re: WYSE V50LE dual screen setup
Post by: jqcore on April 22, 2013, 04:22:42 PM: I read somewhere that vesa and fbdev does not support dual head... I tried but to no avail-
Title: Re: WYSE V50LE dual screen setup
Post by: jqcore on April 22, 2013, 04:24:09 PM: Can someone show how to downgrade Tinycore kernel to 2.6.28? I'm currently running 4.7.6..

Thanks,
jqcore
Title: Re: WYSE V50LE dual screen setup
Post by: Rich on April 22, 2013, 04:57:52 PM: Hi jqcore
I don't think you can simply downgrade the kernel since some extensions/modules are compiled against kernel versions.
You could try TC1.x, it runs kernel version 2.6.26:
http://distro.ibiblio.org/tinycorelinux/archive/
Title: Re: WYSE V50LE dual screen setup
Post by: jqcore on April 24, 2013, 05:16:12 PM: OK, I got TC 1.4 running and get this error:

./configure: line 20254: syntax error near unexpected token `XINERAMA,'
./configure: line 20254: `XORG_DRIVER_CHECK_EXT(XINERAMA, xineramaproto)'

I have below installed:

Xorg-7.4-dev.tce
Xorg-7.4-dev.tce.dep
Xorg-7.4-dev.tce.md5.txt
Xorg-7.4.tcel
Xorg-7.4.tcel.dep
Xorg-7.4.tcel.md5.txt

Code: [Select]
tc@box:~/via-xserver-86a-50283_src/XServer$ ./autogen.sh autoreconf: Entering directory `.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal -I m4 autoreconf: configure.ac: tracing autoreconf: running: libtoolize --copy libtoolize: `config.guess' exists: use `--force' to overwrite libtoolize: `config.sub' exists: use `--force' to overwrite libtoolize: `ltmain.sh' exists: use `--force' to overwrite autoreconf: running: /usr/bin/autoconf autoreconf: running: /usr/bin/autoheader autoreconf: running: automake --add-missing --copy --no-force autoreconf: Leaving directory `.' checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... yes checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for style of include used by make... GNU checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... gcc3 checking for a sed that does not truncate output... /bin/sed checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ld used by gcc... /usr/i686-pc-linux-gnu/bin/ld checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU ld... yes checking for /usr/i686-pc-linux-gnu/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes checking how to recognize dependent libraries... pass_all checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... gcc3 checking how to run the C++ preprocessor... g++ -E checking for g77... no checking for xlf... no checking for f77... no checking for frt... no checking for pgf77... no checking for cf77... no checking for fort77... no checking for fl32... no checking for af77... no checking for xlf90... no checking for f90... no checking for pgf90... no checking for pghpf... no checking for epcf90... no checking for gfortran... no checking for g95... no checking for xlf95... no checking for f95... no checking for fort... no checking for ifort... no checking for ifc... no checking for efc... no checking for pgf95... no checking for lf95... no checking for ftn... no checking whether we are using the GNU Fortran 77 compiler... no checking whether accepts -g... no checking the maximum length of command line arguments... 32768 checking command to parse /usr/bin/nm -B output from gcc object... ok checking for objdir... .libs checking for ar... ar checking for ranlib... ranlib checking for strip... strip checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking whether the gcc linker (/usr/i686-pc-linux-gnu/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... no configure: creating libtool appending configuration tag "CXX" to libtool checking for ld used by g++... /usr/i686-pc-linux-gnu/bin/ld checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU ld... yes checking whether the g++ linker (/usr/i686-pc-linux-gnu/bin/ld) supports shared libraries... yes checking for g++ option to produce PIC... -fPIC checking if g++ PIC flag -fPIC works... yes checking if g++ static flag -static works... no checking if g++ supports -c -o file.o... yes checking whether the g++ linker (/usr/i686-pc-linux-gnu/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate appending configuration tag "F77" to libtool checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking dependency style of gcc... (cached) gcc3 [color=red][b]./configure: line 20254: syntax error near unexpected token `XINERAMA,' ./configure: line 20254: `XORG_DRIVER_CHECK_EXT(XINERAMA, xineramaproto)'[/b][/color] tc@box:~/via-xserver-86a-50283_src/XServer$
Title: Re: WYSE V50LE dual screen setup
Post by: jqcore on April 27, 2013, 09:53:34 PM: I got this going by reinstalling TC 1.4, I got the dual head going.. :D

I have some packages I need but it is not available in 1.x repo so I downloaded it from the 2.x repo.

This is what I get when I tried to load it:

$tce-load package.tcz

mount: you must specify the filesystem type

Thanks,
jqcore
Title: Re: WYSE V50LE dual screen setup
Post by: tinypoodle on April 27, 2013, 11:26:36 PM: As expectable.
You shouldn't expect extension management of 1.x to work with extensions from 2.x repo.

Chance is that a part of binaries could work, once you extract them from .tcz or .tce, but that is in no way supported.
Title: Re: WYSE V50LE dual screen setup
Post by: jqcore on April 29, 2013, 02:55:31 PM: Ok, thanks... I was able to compile the package that I need..

One more and I can put this to bed...

I installled Citrix Receiver 12 on it, launching Citrix complains that this requires GLIBC 2.4. TC 1.4 is using GLIBC 2.3.

How do I proceed on this one...

Thanks,
jqcore
Title: Re: WYSE V50LE dual screen setup
Post by: tinypoodle on April 29, 2013, 10:25:44 PM: Quote from: jqcore on April 29, 2013, 02:55:31 PM
Ok, thanks... I was able to compile the package that I need..

One more and I can put this to bed...

I installled Citrix Receiver 12 on it, launching Citrix complains that this requires GLIBC 2.4. TC 1.4 is using GLIBC 2.3.

How do I proceed on this one...

Thanks,
jqcore

IMHO, at least since 3 posts ago, this thread has taken a totally different direction and started a separate subject, maybe not the best idea to go on with this.

Perhaps a moderator could split off to a new thread with an adequate subject.
Title: Re: WYSE V50LE dual screen setup
Post by: Rich on April 30, 2013, 12:05:08 AM: Hi jqcore
This may be of some use:
http://forums.citrix.com/thread.jspa?threadID=306567

Tinypoodle is correct, your original problem appears to be solved. You should start separate threads for any remaining
problems making certain to mention that you are referring to TC1.4.

@tinypoodle: Moderators can not split up threads.
Title: Re: WYSE V50LE dual screen setup
Post by: tinypoodle on April 30, 2013, 01:30:47 AM: Quote from: Rich on April 30, 2013, 12:05:08 AM
Tinypoodle is correct, your original problem appears to be solved. You should start separate threads for any remaining
problems making certain to mention that you are referring to TC1.4.

@tinypoodle: Moderators can not split up threads.

Confused now and not sure if I didn't express myself correctly, but I have observed that when posts would get off-topic in relation to thread, then they would be split out of the original thread and become start of a new thread (with a new subject).
Title: Re: WYSE V50LE dual screen setup
Post by: Rich on April 30, 2013, 01:37:41 AM: Hi tinypoodle
Threads can be split, but only by a higher power, such as an administrator. Moderators don't have that capability.
Title: Re: WYSE V50LE dual screen setup
Post by: tinypoodle on April 30, 2013, 01:47:00 AM: Quote from: Rich on April 30, 2013, 01:37:41 AM
Hi tinypoodle
Threads can be split, but only by a higher power, such as an administrator. Moderators don't have that capability.

Oh, semantics, now I get it, didn't even think about such a distinction, when I wrote "moderator".
Let's say the spirit of what I meant was "to whom it may concern" ;)
Title: Re: WYSE V50LE dual screen setup
Post by: Rich on April 30, 2013, 02:02:42 AM: Hi tinypoodle
I was only pointing out I was not ignoring your suggestion, I just can't act on it.
Title: Re: WYSE V50LE dual screen setup
Post by: tinypoodle on April 30, 2013, 02:36:08 AM: Oh, I guess I didn't get the spirit right then at first, thanks for clarifying that.