WYSE V50LE dual screen setup

[jqcore]

That's what I thought.

Thanks for all the help, I'll update the thread with the outcome later on.

 

[Rich]

Hi jqcore

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.

[jqcore]

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

[Rich]

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/

[jqcore]

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...

[tinypoodle]

Before you go into that, have you excluded that a more generic driver like vesa or fbdev could do what you want to achieve?

[jqcore]

I read somewhere that vesa and fbdev does not support dual head... I tried but to no avail-

[jqcore]

Can someone show how to downgrade Tinycore kernel to 2.6.28? I'm currently running 4.7.6..

Thanks,
jqcore

[Rich]

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/

[jqcore]

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$


[jqcore]

I got this going by reinstalling TC 1.4, I got the dual head going.. 

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

[tinypoodle]

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.

[jqcore]

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

[tinypoodle]

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.

[Rich]

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.