headers
Daniel Meyer | 2 Nov 2009 10:57
Picon

Recompiling Xorg 6.9


Hi,

i just tried to rebuild xorg 6.9, without success. even though setup.sh
produces no visible error, not even an errorcode (!!), world2.log shows
the following error:

In file included from acecad.c:39:

/usr/include/linux/input.h:801: error: parse error before
"kernel_ulong_t"
/usr/include/linux/input.h:805: error: parse error before "evbit"
/usr/include/linux/input.h:805: error: `BITS_PER_LONG' undeclared here
(not in
a function)
/usr/include/linux/input.h:806: error: parse error before "keybit"
/usr/include/linux/input.h:807: error: parse error before "relbit"
/usr/include/linux/input.h:808: error: parse error before "absbit"
/usr/include/linux/input.h:809: error: parse error before "mscbit"
/usr/include/linux/input.h:810: error: parse error before "ledbit"
/usr/include/linux/input.h:811: error: parse error before "sndbit"
/usr/include/linux/input.h:812: error: parse error before "ffbit"
/usr/include/linux/input.h:813: error: parse error before "swbit"
/usr/include/linux/input.h:815: error: parse error before "driver_info"
/usr/include/linux/input.h:805: error: storage size of `evbit' isn't known
/usr/include/linux/input.h:806: error: storage size of `keybit' isn't known
/usr/include/linux/input.h:807: error: storage size of `relbit' isn't known
/usr/include/linux/input.h:808: error: storage size of `absbit' isn't known
/usr/include/linux/input.h:809: error: storage size of `mscbit' isn't known
/usr/include/linux/input.h:810: error: storage size of `ledbit' isn't known
(Continue reading)

Permalink | Reply | 0 comments |
headers
ElRode | 6 Nov 2009 18:43
Picon

Re: v2.2.2 adding USB-Server kernel module


I followed the steps said by Frank and it worked great.
I have to add that is necessary to copy the binaries of the usb-server tar
file to the packages/base/bin directory and the file rc.usbsrvd.sh to the
packages/base/etc/init.d
It's also good idea to edit the rc.usbsrv.sh file to add the flag
--autoshareon in the script, so all the usb devices can be shared.
I've tested it over rdp, using the trial Terminal server client software of
the same vendor and it was amazing how easy and fast everything worked. The
downside is that the Guindows version of the client is licensed but the
linux version is totally free.

Regards.
--

-- 
View this message in context: http://old.nabble.com/v2.2.2-adding-USB-Server-kernel-module-tp22720777p26230844.html
Sent from the thinstation-developer mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
Permalink | Reply | 4 comments |
headers
Gavin Hamill | 12 Nov 2009 15:11
Picon

TS with newer kernels

Hi all,

We've been using TS 2.2.2 with the Asus 'eeebox' VESA-mounted on the
back of monitors for a really clean term serv setup, but Asus have
recently changed the onboard ethernet to a device made by 'JMicron'
which is only supported in kernel 2.6.28 and onwards.

I've tried the guides on the wiki to compile the 2.6.16 kernel that TS
uses, and attempted to pop the driver [1] in place 

Unsurprisingly for such an elderly kernel, the compile fails:

  CC [M]  drivers/net/jme.o
In file included from drivers/net/jme.c:41:
drivers/net/jme.h:463: error: field `napi' has incomplete type
drivers/net/jme.h: In function `jme_napi_priv':
drivers/net/jme.h:488: warning: type defaults to `int' in declaration of
`__mptr'
drivers/net/jme.h:488: warning: initialization from incompatible pointer
type
drivers/net/jme.c: In function `jme_clear_pm':
drivers/net/jme.c:208: error: `false' undeclared (first use in this
function)

... and so on for hundreds of lines...

Has anyone got a working TS setup (i.e. with all the patches...) with a
recent (2.6.28 or newer) kernel as a base?

Cheers,
(Continue reading)

Permalink | Reply | 0 comments |
headers
Gavin Hamill | 13 Nov 2009 14:19
Picon

Re: TS with newer kernels

On Fri, 2009-11-13 at 10:42 +1100, TrevorB wrote:
> You could try this
> http://batley.com.au/thinstation/kernel-2.6.31.5_TS-2.x.tar.gz
> But it is experimental (It is working for me, but I haven't done too
> much testing yet).
> 
> Move (or delete if you are brave.. ) your current kernel directory first
> cd <path to build>/Thinstation-2.2.2
> mv kernel old_kernel
> tar zxf <path to downloads>/kernel-2.6.31.5_TS-2.x.tar.gz
> 

Thanks, Trevor :) I was getting myself into a terrible state with
binutils + make versions when trying to compile a new kernel in the
chroot compile environment...

Your kernel works for me, although an interesting side-effect is that a
link to /lib/modules/2.6.31.6 (rather than to .5) is made in the
squashfs, so all the kernel modules refuse to load.. I couldn't see
where that was being created, so I just did a 'mv' of the 2.6.31.6 to
2.6.31.5 before mksquashfs and that works OK :)

Module loading is very slow - 1 second pause between each module - so I
think I still need to tinker with making the modules.dep available.

Are there plans to make a 2.2.3 release using this newer kernel? There
must surely be many devices on the market which 2.6.16 is too old to
support (I mean other than our Eee boxes :)

gdh
(Continue reading)

Permalink | Reply | 1 comment |
headers
TrevorB | 14 Nov 2009 00:06
Picon
Gravatar

Re: TS with newer kernels

On Fri, 2009-11-13 at 13:19 +0000, Gavin Hamill wrote:
> On Fri, 2009-11-13 at 10:42 +1100, TrevorB wrote:
> > You could try this
> > http://batley.com.au/thinstation/kernel-2.6.31.5_TS-2.x.tar.gz
> > But it is experimental (It is working for me, but I haven't done too
> > much testing yet).
> > 
> > Move (or delete if you are brave.. ) your current kernel directory first
> > cd <path to build>/Thinstation-2.2.2
> > mv kernel old_kernel
> > tar zxf <path to downloads>/kernel-2.6.31.5_TS-2.x.tar.gz
> > 
> 
> Thanks, Trevor :) I was getting myself into a terrible state with
> binutils + make versions when trying to compile a new kernel in the
> chroot compile environment...
> 
> Your kernel works for me, although an interesting side-effect is that a
> link to /lib/modules/2.6.31.6 (rather than to .5) is made in the
> squashfs, so all the kernel modules refuse to load.. I couldn't see
> where that was being created, so I just did a 'mv' of the 2.6.31.6 to
> 2.6.31.5 before mksquashfs and that works OK :)

OK, I'll look at this. Thanks for the pointer...
> 
> Module loading is very slow - 1 second pause between each module - so I
> think I still need to tinker with making the modules.dep available.

Hmmm, I don't get that. In 2.4 I experimented with generating a
modules.dep as part of the build, but also had a few issues.... There is
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mike Eriksen | 16 Nov 2009 12:45
Picon

TSoM bug: GUI + background.jpg broken

Hi Trevor

TSoM is broken in GUI mode concerning applying an uploaded
background.jpg to the desktop. In text mode it is OK.

The trouble is that the line

param desktop ./background.jpg

fails to appear in build.conf when using GUI mode even though it is
ticked in Parameters/Basic.

Mike
--

-- 
Thinstation oldtimer
http://thinstation.org
- a light, full featured linux based thin client OS

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
Permalink | Reply | 1 comment |
headers
Mike Eriksen | 18 Nov 2009 00:25
Picon

Re: TSoM bug: GUI + background.jpg broken

On Mon, Nov 16, 2009 at 12:45 PM, Mike Eriksen
<thinstation.mike@...> wrote:
> Hi Trevor
>
> TSoM is broken in GUI mode concerning applying an uploaded
> background.jpg to the desktop. In text mode it is OK.
>
> The trouble is that the line
>
> param desktop ./background.jpg
>
> fails to appear in build.conf when using GUI mode even though it is
> ticked in Parameters/Basic.

Hmm. Did a bit more of experiments. As default in build.conf.example
the desktop parameter id disabled:

#param desktop ./background.jpg

and GUI mode fails consistently. However, if I change the default to active

param desktop ./background.jpg

apparently it works nicely even without an upload (you just get the
standard image).

Odd.

Mike
(Continue reading)

Permalink | Reply | 0 comments |
headers
bad_request | 18 Nov 2009 11:10
Picon
Favicon

ThinStation IP Problem on VLAN network


My thin station get ip on local DHCP server with udhcpc, but can't get ip on
WAN (univercity LAN). That WAN includes 90 VLANs and 90 DHCP scope. 

Ethernet cable is who input my thin station, only across VLAN 26, NOT trunc.

When i start dhcp server on thin stations local, thin stations get ip but,
can't get ip vlan net work. My switch's are Alcatel 6248 and my back-bone is
alcatel 9700.

I think udhcpc is can't get ip VLAN network.

By the way, there ara a lots of different OS running and get ip that area,
only thin station can't.....
--

-- 
View this message in context: http://old.nabble.com/ThinStation-IP-Problem-on-VLAN-network-tp26405216p26405216.html
Sent from the thinstation-developer mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
Permalink | Reply | 2 comments |
headers
TrevorB | 20 Nov 2009 10:52
Picon
Gravatar

Re: [Thinstation-general] Thinstation 946 display driver compile reg.

This is not a configuration/usage question. For developer stuff (eg.
compiling), please use the developer list...

configure: error: in `/source/946':
configure: error: C preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details.
Did you look in config.log to see what the error was...???

make: *** No rule to make target `install'.  Stop.

Means, that there is no such option as install specified for this
software. But it just indicates that the ./configure didn't finish and
create the Makefile that make uses.

I would suggest that the latest intel driver from freedesktop is
unlikely to compile against XOrg 6.9 (the version used in Thinstation
2.2.2).

Trevor B

On Thu, 2009-11-19 at 22:52 -0800, Jagcbe wrote:
> Dear all
> 
> I am trying to add driver for Intel 946 Display driver in
> Thinstation compliing. I am new to this thinstation compile environment. 
> 
> I have downloaded Intel driver from following location
> 
> http://xorg.freedesktop.org/archive/individual/driver/xf86-video-intel-2.9.1.tar.bz2
>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Mike Eriksen | 20 Nov 2009 11:24
Picon

Re: [Thinstation-general] Thinstation 946 display driver compile reg.

On Fri, Nov 20, 2009 at 10:52 AM, TrevorB
<trevorbatley@...> wrote:
> This is not a configuration/usage question. For developer stuff (eg.
> compiling), please use the developer list...
>
> configure: error: in `/source/946':
> configure: error: C preprocessor "/lib/cpp" fails sanity check
> See `config.log' for more details.
> Did you look in config.log to see what the error was...???
>
> make: *** No rule to make target `install'.  Stop.
>
> Means, that there is no such option as install specified for this
> software. But it just indicates that the ./configure didn't finish and
> create the Makefile that make uses.
>
> I would suggest that the latest intel driver from freedesktop is
> unlikely to compile against XOrg 6.9 (the version used in Thinstation
> 2.2.2).

Correct. The driver requires xserver 1.3.0, which means Xorg 7.2

Mike

>
> Trevor B
>
--

-- 
Thinstation oldtimer
http://thinstation.org
(Continue reading)

Permalink | Reply | 0 comments |

Gmane