colinux-users — coLinux users mailing list

Re: [coLinux-users] Modern Linux kernel as coLinux host

[yin s. <sun...@gm...>]

I believe it is possible, at least I can see there are code/configure in svn
that handles that.

/Yin

On Wed, Sep 22, 2010 at 7:53 AM, Борис Морозов <um...@ya...> wrote:

> Hello. It is posible to run coLinux on modern Linux distros with kernel
> version >= 2.6.26 ?
>
> Best Regards
>
> Boris Morozov
>
>
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>

[coLinux-users] Modern Linux kernel as coLinux host

[Борис М. <um...@ya...>]

Hello. It is posible to run coLinux on modern Linux distros with kernel version >= 2.6.26 ? 

Best Regards

Boris Morozov

Re: [coLinux-users] colinux-console-nt.exe 8bit support

[Henry N. <hen...@ar...>]

  qnx4ever wrote:
> is there any way to make colinux-console-nt.exe operate with
> international 8bit chars ?

Currently no. We have no translation for charsets.
You can give the cofb a try, there the fonts comes from Linux kernel, 
and you would have all charsets:

http://www.henrynestler.com/colinux/testing/cofb-2.6.26.8/

-- 
Henry N.

Re: [coLinux-users] Very large time offset in coLinux

[Henry N. <hen...@ar...>]

  Hello Ron,

On 20.09.2010 08:29, Ron Avriel wrote:
> Hello Henry,
>
> Thanks a lot for debug version. I installed it, and I'm waiting for 
> the leap again.
>
> It's amazing that the exact same time offset was also seen by another 
> user. What's so special about this 30945 value?
> Too bad it doesn't happen here every five seconds. It would have been 
> solved by now.

If we would know. what it is, we would change it. But, currently it is a 
ghost on some computers only. ;-)

>
> Re the SF bug - our servers run latest Windows 2003, no virtual 
> machines. Our processor is Intel Pentium 4 1.4 GHz.
> However  cat /etc/adjtime
> 0.000000 1162000000 0.000000
> 1162000000
> UTC
>
> I got the same output is from other machines as well. Is that 
> 1162000000 OK?

Yes. The middle field says, when you have last set adjustment.
It's the count of seconds since 1/1/1970:

     TZ= LANG= date --date="1970-01-01 +1162000000sec"
     Sat Oct 28 01:46:40 UTC 2006

>
> BTW, from the output in the debug readme I saw that your server has 
> the same clock frequency as our leaping servers: freq=3579545.
> I hope it will help solving this problem.
>

Have tested co_div64 against the div64_32 by simulate timediffs between 
5 to 10*3579545, and have compaired the jiffies result and remainder for 
every timediff. Results are all exactly the same.

See attched file.
The output under Windows is the same as under Linux 32 bit:
     co_div64: 15 f
     co_div64: 983055 f000f
     div64_32: 16 10, rem:0 0
     div64_32: 1048576 100000, rem:0 0
     done

-- 
Henry N.

Re: [coLinux-users] Very large time offset in coLinux

[Ron A. <ra...@ho...>]

Hello Henry,

Thanks a lot for debug version. I installed it, and I'm waiting for the leap again.

It's amazing that the exact same time offset was also seen by another user. What's so special about this 30945 value?
Too bad it doesn't happen here every five seconds. It would have been solved by now.

Re the SF bug - our servers run latest Windows 2003, no virtual machines. Our processor is Intel Pentium 4 1.4 GHz.
However  cat /etc/adjtime
0.000000 1162000000 0.000000
1162000000
UTC

I got the same output is from other machines as well. Is that 1162000000 OK?

BTW, from the output in the debug readme I saw that your server has the same clock frequency as our leaping servers: freq=3579545.
I hope it will help solving this problem.

Thanks,
Ron

 		 	   		  

Re: [coLinux-users] Very large time offset in coLinux

[Henry N. <hen...@ar...>]

  Hello Ron,

please see the bug #1780633 on sf.net
https://sourceforge.net/tracker/?func=detail&aid=1780633&group_id=98788&atid=622063

The reporter sad: "Every 5 seconds, the system clock is increased by 8 
hours, 35 minutes and 45 seconds."

(8*60+35)*60+45 = 30 945 seconds. The time you also have seen!

Henry

On 17.09.2010 02:47, Henry Nestler wrote:
> Hello Ron,
>
> thank for tracing all this, and many thanks for pointing to the div64 
> bug. It would be nice, if you would open a bug report on sf.net, so we 
> don't forget to change the co_div64 some times. Currently I have no 
> idea for better function.
>
> I don't assume that is the problem. Because the rounding error will 
> later adjust by multily and storing the rest in the variable 
> timestamp_reminder. I mean this line:
> cmon->timestamp_reminder = timestamp_diff - (jiffies * 
> cmon->timestamp_freq.quad);
>
> A debug version is available from here:
> http://www.henrynestler.com/colinux/testing/devel-0.7.8/20100916-jiffies
>
> I have changed the casts from "long long" to "unsigned long long" and 
> remove the casts where we don't need. So we would have one bit more 
> and no negative values.
>
> Old:
> long long timestamp_diff;
> timestamp_diff += 100 * (((long long)timestamp.quad) - ((long 
> long)cmon->timestamp.quad));
>
> New:
> unsigned long long timestamp_diff;
> timestamp_diff += 100 * (timestamp.quad - cmon->timestamp.quad)
>
> Henry
>
> On 16.09.2010 19:06, Ron Avriel wrote:
>> Hi,
>>
>> Any update on this issue? The server leaped again with almost an 
>> identical value (30949 seconds).
>> Is it possible to at least have a debug version with log prints in 
>> case of large leap?
>> I also suggest replacing co_div64() - see below.
>>
>> Thanks,
>> Ron
>>
>>
>> From: ra...@ho... <mailto:ra...@ho...>
>> To: col...@li... 
>> <mailto:col...@li...>
>> Date: Sun, 12 Sep 2010 14:29:25 +0000
>> Subject: Re: [coLinux-users] Very large time offset in coLinux
>>
>> Hi Henry,
>>
>> One of our servers leaped forward again. The interesting part is that 
>> the leap is almost identical to a previous leap.
>> Last time it leaped forward by 30944 seconds, and this time by 30961 
>> seconds.
>> Performance frequency is 3579545.
>>
>> Since these two leaps are very close, I have a feeling it's not some 
>> a random error, but rather a calculation error.
>> It's possible that Windows/Linux were loaded at time of leap.
>>
>> I went over some of the code and found that co_div64() isn't accurate 
>> (!), although I couldn't explain the leap by this bug.
>>
>> For example,
>> co_div64(0x100000000,0x10000000) returns 15 instead of 16.
>> co_div64(0x1000000000000,0x10000000) returns 983055 instead of 1048576.
>>
>> I'm sure you'll find more accurate algorithms.
>>
>> Could you also go over relevant code and see if you notice any 
>> overflow, signed/unsigned error that can explain the leap with the 
>> above data?
>> Would it be possible to to get a debug version to get more 
>> information next time the problem occurs?
>>
>> Thanks in advance,
>> Ron

Re: [coLinux-users] Very large time offset in coLinux

[Henry N. <hen...@ar...>]

  Hello Ron,

thank for tracing all this, and many thanks for pointing to the div64 
bug. It would be nice, if you would open a bug report on sf.net, so we 
don't forget to change the co_div64 some times. Currently I have no idea 
for better function.

I don't assume that is the problem. Because the rounding error will 
later adjust by multily and storing the rest in the variable 
timestamp_reminder. I mean this line:
cmon->timestamp_reminder = timestamp_diff - (jiffies * 
cmon->timestamp_freq.quad);

A debug version is available from here:
http://www.henrynestler.com/colinux/testing/devel-0.7.8/20100916-jiffies

I have changed the casts from "long long" to "unsigned long long" and 
remove the casts where we don't need. So we would have one bit more and 
no negative values.

Old:
long long timestamp_diff;
timestamp_diff += 100 * (((long long)timestamp.quad) - ((long 
long)cmon->timestamp.quad));

New:
unsigned long long timestamp_diff;
timestamp_diff += 100 * (timestamp.quad - cmon->timestamp.quad)

Henry

On 16.09.2010 19:06, Ron Avriel wrote:
> Hi,
>
> Any update on this issue? The server leaped again with almost an 
> identical value (30949 seconds).
> Is it possible to at least have a debug version with log prints in 
> case of large leap?
> I also suggest replacing co_div64() - see below.
>
> Thanks,
> Ron
>
>
> From: ra...@ho...
> To: col...@li...
> Date: Sun, 12 Sep 2010 14:29:25 +0000
> Subject: Re: [coLinux-users] Very large time offset in coLinux
>
> Hi Henry,
>
> One of our servers leaped forward again. The interesting part is that 
> the leap is almost identical to a previous leap.
> Last time it leaped forward by 30944 seconds, and this time by 30961 
> seconds.
> Performance frequency is 3579545.
>
> Since these two leaps are very close, I have a feeling it's not some a 
> random error, but rather a calculation error.
> It's possible that Windows/Linux were loaded at time of leap.
>
> I went over some of the code and found that co_div64() isn't accurate 
> (!), although I couldn't explain the leap by this bug.
>
> For example,
> co_div64(0x100000000,0x10000000) returns 15 instead of 16.
> co_div64(0x1000000000000,0x10000000) returns 983055 instead of 1048576.
>
> I'm sure you'll find more accurate algorithms.
>
> Could you also go over relevant code and see if you notice any 
> overflow, signed/unsigned error that can explain the leap with the 
> above data?
> Would it be possible to to get a debug version to get more information 
> next time the problem occurs?
>
> Thanks in advance,
> Ron

Re: [coLinux-users] Very large time offset in coLinux

[Ron A. <ra...@ho...>]

Hi,

Any update on this issue? The server leaped again with almost an identical value (30949 seconds).
Is it possible to at least have a debug version with log prints in case of large leap? 
I also suggest replacing co_div64() - see below.

Thanks,
Ron


From: ra...@ho...
To: col...@li...
Date: Sun, 12 Sep 2010 14:29:25 +0000
Subject: Re: [coLinux-users] Very large time offset in coLinux








Hi Henry,

One of our servers leaped forward again. The interesting part is that the leap is almost identical to a previous leap.
Last time it leaped forward by 30944 seconds, and this time by 30961 seconds. 
Performance frequency is 3579545.

Since these two leaps are very close, I have a feeling it's not some a random error, but rather a calculation error.
It's possible that Windows/Linux were loaded at time of leap.

I went over some of the code and found that co_div64() isn't accurate (!), although I couldn't explain the leap by this bug.

For example, 
co_div64(0x100000000,0x10000000) returns 15 instead of 16.
co_div64(0x1000000000000,0x10000000) returns 983055 instead of 1048576.

I'm sure you'll find more accurate algorithms.

Could you also go over relevant code and see if you notice any overflow, signed/unsigned error that can explain the leap with the above data?
Would it be possible to to get a debug version to get more information next time the problem occurs?

Thanks in advance,
Ron

 		 	   		  

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
coLinux-users mailing list
coL...@li...
https://lists.sourceforge.net/lists/listinfo/colinux-users 		 	   		  

[coLinux-users] [ANNOUNCE] Cooperative Linux version 0.7.8 with kernel 2.6.33.5 released

[Henry N. <hen...@ar...>]

  Cooperative Linux version 0.7.8 with kernel 2.6.33.5 released

Release: 0.7.8
Kernel:  2.6.33.5
Build:   1-September-2010

This is mainly a new kernel update with some improvements on the FLTK 
console,
for example scroll back, menue for fonts.
Please check the project file release and wiki for information, updates 
and progress.

Downloads: http://sourceforge.net/projects/colinux/files/
ChangeLog: http://www.colinux.org/?section=status
Wiki: http://colinux.wikia.com
Snapshots: http://www.colinux.org/snapshots/

Here are latest news details:
* Version 0.7.8
   FLTK Console (Shai Vaingast):
   * New: Select font style and size with menu, store current font in 
registry.
   * New: Setect text with right or left mouse and copy&paste with key 
Win+C.
   * New: "cocon=COLSxROWSxSCROLLBACK" to use console scrollback with keys
     Win+PageUP, Win+PageDown or mouse weel.
   * Disabling console FLTK resize functionality.
   * Enabled blinking cursor support.
   * New menu option "exit on detach" (quit console after shutting down).
   * Redesigned menu to be more inline with today's standard menu layout.
   * Workaround for some Vista keyboard drivers bugs where WinKey+C and 
WinKey+V
     don't work properly.  Now WinKey+Home and WinKey+End is teh alternate.

   Daemons:
   * Different descriription for file properties, add original filename.

   Kernel:
   * Version 2.6.33.5 added.
   * Filesystems EXT4 enabled in kernel, GFS2 enabled as module.
   * comouse.c: Fix build error, with CONFIG_MOUSE_COOPERATIVE. (Yin Sun)
   * Version 2.6.22.18 removed from patches and config. Cleanup patches.
     Softlink arch/i386 --> arch/x86 for patches removed.

   Buildsystem:
   * Suppress warnings from Python 2.6. (Shai Vaingast)
   * Config variable changed from SOURCE_DIR to DOWNLOADS.

   Updated libraries and tools:
   * FLTK 1.1.10, fixes problems with Window border frame on Vista.

-- 
Henry N.

Re: [coLinux-users] CoLinux 0.7.7.1 + kernel 2.6.26.8 won't build

[Henry N. <hen...@ar...>]

  On 15.09.2010 19:16, Sergei Zhirikov wrote:
> On 2010-09-14 22:20, Henry Nestler wrote:
>>     On 14.09.2010 22:05, Sergei Zhirikov wrote:
>>> On 2010-09-14 20:19, Sergei Zhirikov wrote:
>>>> On 2010-09-14 01:35, Henry Nestler wrote:
>>>>>        On 12.09.2010 21:59, Sergei Zhirikov wrote:
>>>>>> make[1]: *** No rule to make target `arch/x86/pci/copci.o', needed by `arch/x86/pci/built-in.o'.  Stop.
>>>>>> make: *** [arch/x86/pci] Error 2
>>>>> [...]
>>>>
>>> I've managed to use coLinux build system without Python. It was actually quite easy, as Python is not really necessary. Shame that 'configure' treats it as a strict requirement.
>> Yes, kernel can build without Python. I hope you found doc/building, and
>> the bin/build-kernel.sh for simple kernel build.
>>
>> [...]
> Thanks for trying to help. I've figured out what the problem was. All I had to do is manually create a symbolic link 'arch/i386 ->  x86' in the kernel source directory *before* applying the coLinux patches.
>
> Apparently, some time between 2.6.22 and 2.6.26 the Linux code that used to be in arch/i386 moved to arch/x86. However coLinux patches continue using arch/i386, so if the symlink does not exist at the time of applying the patches a directory arch/i386 is created with only coLinux files in it. That causes subsequent build to fail.

Ah, yes. That is true. Sorry for trouble with that.
As long kernel 2.6.22 exist with more recent kernels, we had to merge 
both patches via softlink.

Since kernel 2.6.22 was removed inside coLinux 0.7.8, this softlink was 
removed from bin/build-kernel.sh, and no longer need.

By the while: The comouse.c was fixed in source of coLinux 0.7.8 now.

-- 
Henry N.

Re: [coLinux-users] CoLinux 0.7.7.1 + kernel 2.6.26.8 won't build

[Sergei Z. <sf...@ya...>]

On 2010-09-14 22:20, Henry Nestler wrote:
>    On 14.09.2010 22:05, Sergei Zhirikov wrote:
>> On 2010-09-14 20:19, Sergei Zhirikov wrote:
>>> On 2010-09-14 01:35, Henry Nestler wrote:
>>>>       On 12.09.2010 21:59, Sergei Zhirikov wrote:
>>>>> make[1]: *** No rule to make target `arch/x86/pci/copci.o', needed by `arch/x86/pci/built-in.o'.  Stop.
>>>>> make: *** [arch/x86/pci] Error 2
>>>> I don't know why you have this error. I can only say, that the patches
>>>> and config in source of coLinux version 0.7.7.1 can clean build kernel
>>>> 2.6.26.8, used gcc 4.4.1
>>>> Please try to remove or rename the both directories
>>>> linux-2.6.26.8-source and linux-2.6.26.8-build. Than start a fresh build
>>>> with default config.
>>>>
>>> I'm using gcc 4.4.3. I suppose I should have mentioned this in the beginning. I'm not using the coLinux configure/make. I'm applying the kernel patches by hand and running make in the kernel directory. This worked just fine for older coLinux/kernel. What else does coLinux make do besides applying the patches and default config?
>>>
>>> Unfortunately, I can't use the coLinux build system, because I don't have Python installed (and, to be honest, I'm not looking forward to installing it just to run a single script, as it would mean building it from source).
>>>
>> I've managed to use coLinux build system without Python. It was actually quite easy, as Python is not really necessary. Shame that 'configure' treats it as a strict requirement.
>
> Yes, kernel can build without Python. I hope you found doc/building, and
> the bin/build-kernel.sh for simple kernel build.
>
> CoLinux demons and Windows driver can't build without Python. But, this
> typcal user does not need to rebuild.
>
Thanks for trying to help. I've figured out what the problem was. All I had to do is manually create a symbolic link 'arch/i386 -> x86' in the kernel source directory *before* applying the coLinux patches.

Apparently, some time between 2.6.22 and 2.6.26 the Linux code that used to be in arch/i386 moved to arch/x86. However coLinux patches continue using arch/i386, so if the symlink does not exist at the time of applying the patches a directory arch/i386 is created with only coLinux files in it. That causes subsequent build to fail.

Re: [coLinux-users] CoLinux 0.7.7.1 + kernel 2.6.26.8 won't build

[Henry N. <hen...@ar...>]

  On 14.09.2010 22:05, Sergei Zhirikov wrote:
> On 2010-09-14 20:19, Sergei Zhirikov wrote:
>> On 2010-09-14 01:35, Henry Nestler wrote:
>>>      On 12.09.2010 21:59, Sergei Zhirikov wrote:
>>>> make[1]: *** No rule to make target `arch/x86/pci/copci.o', needed by `arch/x86/pci/built-in.o'.  Stop.
>>>> make: *** [arch/x86/pci] Error 2
>>> I don't know why you have this error. I can only say, that the patches
>>> and config in source of coLinux version 0.7.7.1 can clean build kernel
>>> 2.6.26.8, used gcc 4.4.1
>>> Please try to remove or rename the both directories
>>> linux-2.6.26.8-source and linux-2.6.26.8-build. Than start a fresh build
>>> with default config.
>>>
>> I'm using gcc 4.4.3. I suppose I should have mentioned this in the beginning. I'm not using the coLinux configure/make. I'm applying the kernel patches by hand and running make in the kernel directory. This worked just fine for older coLinux/kernel. What else does coLinux make do besides applying the patches and default config?
>>
>> Unfortunately, I can't use the coLinux build system, because I don't have Python installed (and, to be honest, I'm not looking forward to installing it just to run a single script, as it would mean building it from source).
>>
> I've managed to use coLinux build system without Python. It was actually quite easy, as Python is not really necessary. Shame that 'configure' treats it as a strict requirement.

Yes, kernel can build without Python. I hope you found doc/building, and 
the bin/build-kernel.sh for simple kernel build.

CoLinux demons and Windows driver can't build without Python. But, this 
typcal user does not need to rebuild.

-- 
Henry N.

Re: [coLinux-users] CoLinux 0.7.7.1 + kernel 2.6.26.8 won't build

[Sergei Z. <sf...@ya...>]

On 2010-09-14 20:19, Sergei Zhirikov wrote:
> On 2010-09-14 01:35, Henry Nestler wrote:
>>     On 12.09.2010 21:59, Sergei Zhirikov wrote:
>>> make[1]: *** No rule to make target `arch/x86/pci/copci.o', needed by `arch/x86/pci/built-in.o'.  Stop.
>>> make: *** [arch/x86/pci] Error 2
>>
>> I don't know why you have this error. I can only say, that the patches
>> and config in source of coLinux version 0.7.7.1 can clean build kernel
>> 2.6.26.8, used gcc 4.4.1
>> Please try to remove or rename the both directories
>> linux-2.6.26.8-source and linux-2.6.26.8-build. Than start a fresh build
>> with default config.
>>
> I'm using gcc 4.4.3. I suppose I should have mentioned this in the beginning. I'm not using the coLinux configure/make. I'm applying the kernel patches by hand and running make in the kernel directory. This worked just fine for older coLinux/kernel. What else does coLinux make do besides applying the patches and default config?
>
> Unfortunately, I can't use the coLinux build system, because I don't have Python installed (and, to be honest, I'm not looking forward to installing it just to run a single script, as it would mean building it from source).
>
I've managed to use coLinux build system without Python. It was actually quite easy, as Python is not really necessary. Shame that 'configure' treats it as a strict requirement.

Anyway, the build succeeded, so now I'm busy trying to figure out what made the difference.

Re: [coLinux-users] CoLinux 0.7.7.1 + kernel 2.6.26.8 won't build

[Sergei Z. <sf...@ya...>]

On 2010-09-14 01:35, Henry Nestler wrote:
>    On 12.09.2010 21:59, Sergei Zhirikov wrote:
>> make[1]: *** No rule to make target `arch/x86/pci/copci.o', needed by `arch/x86/pci/built-in.o'.  Stop.
>> make: *** [arch/x86/pci] Error 2
>
> I don't know why you have this error. I can only say, that the patches
> and config in source of coLinux version 0.7.7.1 can clean build kernel
> 2.6.26.8, used gcc 4.4.1
> Please try to remove or rename the both directories
> linux-2.6.26.8-source and linux-2.6.26.8-build. Than start a fresh build
> with default config.
>
I'm using gcc 4.4.3. I suppose I should have mentioned this in the beginning. I'm not using the coLinux configure/make. I'm applying the kernel patches by hand and running make in the kernel directory. This worked just fine for older coLinux/kernel. What else does coLinux make do besides applying the patches and default config?

Unfortunately, I can't use the coLinux build system, because I don't have Python installed (and, to be honest, I'm not looking forward to installing it just to run a single script, as it would mean building it from source).

Re: [coLinux-users] aufs2 for colinux 0.7.8rc1

[Henry N. <hen...@ar...>]

  On 11.09.2010 14:33, Wufu Chen wrote:
> Hello All
>         I successfully build the aufs2 module for colinux 0.7.8RC1 .
> (I'm try to run debian squeeze latest live cd(iso) with  colinux078 )
> (I had run successfully debian etch live cd(iso) with old colinux ,
> also announced in this list)
>
> it works with newly build vmlinux in same machine (ubuntu 10.04  for
> aufs2 build) ,
> but don't work with original vmlinux from colinux.org snapshot
> is it the gcc version mismatch?
>
> [...snip...]
>
>    MODPOST 1 modules
> WARNING: "deny_write_access"
> [/home/ccwufu/aufs2/aufs2-standalone.git/fs/aufs/aufs.ko] undefined!
> WARNING: "do_truncate"
> [/home/ccwufu/aufs2/aufs2-standalone.git/fs/aufs/aufs.ko] undefined!
> WARNING: "do_splice_from"
> [/home/ccwufu/aufs2/aufs2-standalone.git/fs/aufs/aufs.ko] undefined!
> WARNING: "cap_file_mmap"
> [/home/ccwufu/aufs2/aufs2-standalone.git/fs/aufs/aufs.ko] undefined!
> WARNING: "lookup_hash"
> [/home/ccwufu/aufs2/aufs2-standalone.git/fs/aufs/aufs.ko] undefined!
> WARNING: "do_splice_to"
> [/home/ccwufu/aufs2/aufs2-standalone.git/fs/aufs/aufs.ko] undefined!
> WARNING: "__lookup_one_len"

If you have such warnings, than the module can not load later.

The file "aufs2-base.patch" will change something directly in the kernel 
binary, for example the function "lookup_hash" will make no static. In 
the other file "aufs2-standalone.patch" the label "lookup_hash" will 
export for modules now. With such changes the coLinux default vmlinux is 
not more the same as you need for aufs module loading. There are some 
more functions, that aufs needs as exported (deny_write_access, 
__lookup_one_len, vfsmount_lock, ...). If you use default coLinux 
vmlinux, theses entries does not exist. So you must build the kernel 
file vmlinux self AND the module. No other way would work.

Thank you for your good step details.

-- 
Henry N.

Re: [coLinux-users] CoLinux 0.7.7.1 + kernel 2.6.26.8 won't build

[Henry N. <hen...@ar...>]

  On 12.09.2010 21:59, Sergei Zhirikov wrote:
> On 2010-09-10 20:55, H. Nestler wrote:
>> Sergei Zhirikov wrote:
>>> I have just tried to build kernel 2.6.26.8 with coLinux 0.7.7.1 and it
>>> fails:
>>>
>>>      CC      drivers/input/mouse/comouse.o
>>> drivers/input/mouse/comouse.c: In function 'comouse_init':
>>> drivers/input/mouse/comouse.c:107: error: implicit declaration of function
>>> 'LONG'
>>> drivers/input/mouse/comouse.c:108: warning: left shift count>= width of
>>> type
>>> drivers/input/mouse/comouse.c:109: warning: left shift count>= width of
>>> type
>>> drivers/input/mouse/comouse.c:109: warning: left shift count>= width of
>>> type
>>> drivers/input/mouse/comouse.c:109: warning: left shift count>= width of
>>> type
>>> make[3]: *** [drivers/input/mouse/comouse.o] Error 1
>>> make[2]: *** [drivers/input/mouse] Error 2
>>> make[1]: *** [drivers/input] Error 2
>>> make: *** [drivers] Error 2
>>>
>>> Previuosly I built kernel 2.6.22.18 with colinux 0.7.6 without any
>>> problems.
>>>
>>> I did some investigation and found the following.
>>> In kernel 2.6.22.18 the macro LONG is defined in include/linux/input.h, line
>>> 925.
>>> But in kernel 2.6.26.8 that header file is significantly different. The LONG
>>> macro is not defined any more.
>>> As far as I can tell, it is not defined anywhere in the Linux source (or
>>> coLinux for that matter).
>>>
>>> I'm wondering, how could anyone possibly have succeeded building the
>>> 2.6.26.8/0.7.7.1 combination?
>>> Are there any patches missing from the coLinux release tarball?
>> I hope not. The tar was created from SVN tree, so missing files are not doable.
>>
>> The devel version 0.7.8 can build with kernel 2.6.26.8 without errors. I have just tested.
>> I can currently not test the stable 0.7.7.1 from here.
>>
>> As long I remember, the mouse was disabled in kernel config. Maybe this is the condition, that I don't have the problem?
>> The line "CC ... comouse" does not exist in my build log! My devel config has "# CONFIG_MOUSE_COOPERATIVE is not set". So it is disabled.
>>
>> Mouse is always disabled in stable, see line 747:
>> http://colinux.svn.sourceforge.net/viewvc/colinux/branches/stable/conf/linux-2.6.26.8-config?revision=1407&view=markup
>>
>> Please test with default config from coLinux, or disable the mouse driver in your config.
>>
>> To compare patch files and config from 0.7.8 tree with yours, you will find all files on SVN http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/ or as tar under nightly builds on http://www.henrynestler.com/colinux/autobuild/
>>
> Thanks. Disabling mouse does solve the problem.

The mouse was fixed in devel by Yin Sun. I will copy his code next.

> However, now I'm facing another one:
>
> make[1]: *** No rule to make target `arch/x86/pci/copci.o', needed by `arch/x86/pci/built-in.o'.  Stop.
> make: *** [arch/x86/pci] Error 2

I don't know why you have this error. I can only say, that the patches 
and config in source of coLinux version 0.7.7.1 can clean build kernel 
2.6.26.8, used gcc 4.4.1
Please try to remove or rename the both directories 
linux-2.6.26.8-source and linux-2.6.26.8-build. Than start a fresh build 
with default config.

> This fails with the default configuration too. Am I doing something wrong?
> I don't suppose I can disable PCI, because it is needed for the virtual network adapter(s), right?

Yes, PCI is essential for networking.

-- 
Henry N.

Re: [coLinux-users] aufs2 for colinux 0.7.8rc1

[Sergei Z. <sf...@ya...>]

On 2010-09-11 14:33, Wufu Chen wrote:
> Hello All
>         I successfully build the aufs2 module for colinux 0.7.8RC1 .
> (I'm try to run debian squeeze latest live cd(iso) with  colinux078 )
> (I had run successfully debian etch live cd(iso) with old colinux ,
> also announced in this list)
>
> it works with newly build vmlinux in same machine (ubuntu 10.04  for
> aufs2 build) ,
> but don't work with original vmlinux from colinux.org snapshot
> is it the gcc version mismatch?
>
Just to clarify your question. You apply aufs2 patches to the kernel source,
and then you expect the built aufs2.ko to work with unpatched kernel?

Re: [coLinux-users] CoLinux 0.7.7.1 + kernel 2.6.26.8 won't build

[Sergei Z. <sf...@ya...>]

On 2010-09-10 20:55, H. Nestler wrote:
> Sergei Zhirikov wrote:
>> I have just tried to build kernel 2.6.26.8 with coLinux 0.7.7.1 and it
>> fails:
>>
>>     CC      drivers/input/mouse/comouse.o
>> drivers/input/mouse/comouse.c: In function 'comouse_init':
>> drivers/input/mouse/comouse.c:107: error: implicit declaration of function
>> 'LONG'
>> drivers/input/mouse/comouse.c:108: warning: left shift count>= width of
>> type
>> drivers/input/mouse/comouse.c:109: warning: left shift count>= width of
>> type
>> drivers/input/mouse/comouse.c:109: warning: left shift count>= width of
>> type
>> drivers/input/mouse/comouse.c:109: warning: left shift count>= width of
>> type
>> make[3]: *** [drivers/input/mouse/comouse.o] Error 1
>> make[2]: *** [drivers/input/mouse] Error 2
>> make[1]: *** [drivers/input] Error 2
>> make: *** [drivers] Error 2
>>
>> Previuosly I built kernel 2.6.22.18 with colinux 0.7.6 without any
>> problems.
>>
>> I did some investigation and found the following.
>> In kernel 2.6.22.18 the macro LONG is defined in include/linux/input.h, line
>> 925.
>> But in kernel 2.6.26.8 that header file is significantly different. The LONG
>> macro is not defined any more.
>> As far as I can tell, it is not defined anywhere in the Linux source (or
>> coLinux for that matter).
>>
>> I'm wondering, how could anyone possibly have succeeded building the
>> 2.6.26.8/0.7.7.1 combination?
>> Are there any patches missing from the coLinux release tarball?
>
> I hope not. The tar was created from SVN tree, so missing files are not doable.
>
> The devel version 0.7.8 can build with kernel 2.6.26.8 without errors. I have just tested.
> I can currently not test the stable 0.7.7.1 from here.
>
> As long I remember, the mouse was disabled in kernel config. Maybe this is the condition, that I don't have the problem?
> The line "CC ... comouse" does not exist in my build log! My devel config has "# CONFIG_MOUSE_COOPERATIVE is not set". So it is disabled.
>
> Mouse is always disabled in stable, see line 747:
> http://colinux.svn.sourceforge.net/viewvc/colinux/branches/stable/conf/linux-2.6.26.8-config?revision=1407&view=markup
>
> Please test with default config from coLinux, or disable the mouse driver in your config.
>
> To compare patch files and config from 0.7.8 tree with yours, you will find all files on SVN http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/ or as tar under nightly builds on http://www.henrynestler.com/colinux/autobuild/
>

Thanks. Disabling mouse does solve the problem.
However, now I'm facing another one:

make[1]: *** No rule to make target `arch/x86/pci/copci.o', needed by `arch/x86/pci/built-in.o'.  Stop.
make: *** [arch/x86/pci] Error 2

This fails with the default configuration too. Am I doing something wrong?
I don't suppose I can disable PCI, because it is needed for the virtual network adapter(s), right?

--
Sergei.

Re: [coLinux-users] Very large time offset in coLinux

[Ron A. <ra...@ho...>]

Hi Henry,

One of our servers leaped forward again. The interesting part is that the leap is almost identical to a previous leap.
Last time it leaped forward by 30944 seconds, and this time by 30961 seconds. 
Performance frequency is 3579545.

Since these two leaps are very close, I have a feeling it's not some a random error, but rather a calculation error.
It's possible that Windows/Linux were loaded at time of leap.

I went over some of the code and found that co_div64() isn't accurate (!), although I couldn't explain the leap by this bug.

For example, 
co_div64(0x100000000,0x10000000) returns 15 instead of 16.
co_div64(0x1000000000000,0x10000000) returns 983055 instead of 1048576.

I'm sure you'll find more accurate algorithms.

Could you also go over relevant code and see if you notice any overflow, signed/unsigned error that can explain the leap with the above data?
Would it be possible to to get a debug version to get more information next time the problem occurs?

Thanks in advance,
Ron

 		 	   		  

[coLinux-users] colinux-console-nt.exe 8bit support

[qnx4ever <qnx...@gm...>]

Dear coLinux developers,
is there any way to make colinux-console-nt.exe operate with
international 8bit chars ?

[coLinux-users] aufs2 for colinux 0.7.8rc1

[Wufu C. <cc...@gm...>]

Hello All
       I successfully build the aufs2 module for colinux 0.7.8RC1 .
(I'm try to run debian squeeze latest live cd(iso) with  colinux078 )
(I had run successfully debian etch live cd(iso) with old colinux ,
also announced in this list)

it works with newly build vmlinux in same machine (ubuntu 10.04  for
aufs2 build) ,
but don't work with original vmlinux from colinux.org snapshot
is it the gcc version mismatch?

a)work with newly build vmlinux
root@localhost:/tmp/aufs# dmesg | head -n1

Linux version 2.6.33.5-co-0.7.8 (ccwufu@desktop) (gcc version 4.4.3
(Ubuntu 4.4.3-4ubuntu5) ) #2 PREEMPT Sat Sep 11 17:33:35 CST 2010



root@localhost:/tmp/aufs#insmod ./aufs.kko



root@localhost:/tmp/aufs# dmesg | tail

fuse_read_super: connection already mounted

aufs 2-standalone.tree-33-20100823

 b) don't work with original vmlinux from colinux.org snapshot

root@localhost:~# dmesg | head -n1

Linux version 2.6.33.5-co-0.7.8 (hn@hn-dt) (gcc version 4.4.1
[gcc-4_4-branch revision 150839] (SUSE Linux) ) #1 PREEMPT Wed Sep 1
22:49:51 UTC 2010

root@localhost:~# insmod aufs.ko

insmod: error inserting 'aufs.ko': -1 Invalid module format


root@localhost:~# dmesg | tail

aufs: disagrees about version of symbol module_layout


Best Regards

ccwufu

below are building steps
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
prepare aufs2 standalone

mkdir ~/aufs2
cd ~/aufs2
git clone http://git.c3sl.ufpr.br/pub/scm/aufs/aufs2-standalone.git
aufs2-standalone.git
cd aufs2-standalone.git
git checkout origin/aufs2-33

vi config.mk
changed
CONFIG_AUFS_DEBUG = y
with
CONFIG_AUFS_DEBUG =


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compile colinux kernel

mkdir ~/colinux078
cd ~/colinux078
wget http://www.henrynestler.com/colinux/testing/stable-0.7.8/20100901-Snapshot/stable-colinux-20100901.tar.gz
tar -xvf stable-colinux-20100901.tar.gz
cd stable-colinux-20100901
cp ~/aufs2/aufs2-standalone.git/aufs2-base.patch ./patch/aufs2-base.diff
cp ~/aufs2/aufs2-standalone.git/aufs2-standalone.patch
./patch/aufs2-standalone.diff
gedit ./patch/series-2.6.33.5
(delete line : unionfs-2.5.4_for_2.6.33.diff
 add a line : aufs2-base.diff
 add another line : aufs2-standalone.diff)
./configure
make kernel

Tips : don't follow OLD tips in WIKI
"You can stop it with CTRL-C after the message "Making Kernel 2.6.22"
was showed (no needs to finish). "
...

(don't break it , let it go)

...........................
Configuring Kernel 2.6.33.5
Making Kernel 2.6.33.5
Making Modules 2.6.33.5
Create Modules archive
Create md5sum
local: 271: serial-core.diff: bad variable name
...........................

cd  ~/colinux078/build/linux-2.6.33.5-build

ccwufu@desktop:~/colinux078/build/linux-2.6.33.5-build$ ls -al
total 31084

-rw-r--r--  1 ccwufu ccwufu  219543 2010-09-11 17:33 Module.symvers

-rwxr-xr-x  1 ccwufu ccwufu 4323499 2010-09-11 17:33 vmlinux
-rw-r--r--  1 ccwufu ccwufu 3801394 2010-09-11 17:34 vmlinux-modules.tar.gz

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
make aufs

cd ~/aufs2/aufs2-standalone.git

ccwufu@desktop:~/aufs2/aufs2-standalone.git$ make
KDIR=/home/ccwufu/colinux078/build/linux-2.6.33.5-build

...
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /home/ccwufu/aufs2/aufs2-standalone.git/fs/aufs/aufs.mod.o
  LD [M]  /home/ccwufu/aufs2/aufs2-standalone.git/fs/aufs/aufs.ko
make[1]: Leaving directory `/home/ccwufu/colinux078/build/linux-2.6.33.5-build'
ln -f fs/aufs/aufs.ko aufs.ko
ccwufu@desktop:~/aufs2/aufs2-standalone.git$


&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
result :
ccwufu@desktop:~/colinux078/build/linux-2.6.33.5-build$ ls -al
-rwxr-xr-x  1 ccwufu ccwufu 4323499 2010-09-11 17:33 vmlinux
-rw-r--r--  1 ccwufu ccwufu 3801394 2010-09-11 17:34 vmlinux-modules.tar.gz
ccwufu@desktop:~/aufs2/aufs2-standalone.git/fs/aufs$ ls -al
-rw-r--r-- 2 ccwufu ccwufu 293595 2010-09-11 17:41 aufs.ko
&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
running in colinux
a)aufs2 insmod failure while original vmlinux from colinux.org

root@localhost:~# dmesg | head -n1

Linux version 2.6.33.5-co-0.7.8 (hn@hn-dt) (gcc version 4.4.1
[gcc-4_4-branch revision 150839] (SUSE Linux) ) #1 PREEMPT Wed Sep 1
22:49:51 UTC 2010

root@localhost:~# ls

Desktop  My GCompris  aufs.ko  vmlinux-modules.tar.gz

root@localhost:/tmp/aufs# modinfo ./aufs.ko

filename:       aufs.ko

version:        2-standalone.tree-33-20100823

description:    aufs -- Advanced multi layered unification filesystem

author:         Junjiro R. Okajima <auf...@li...>

license:        GPL

srcversion:     76B861C166EB214ECD5C416

depends:

vermagic:       2.6.33.5-co-0.7.8 preempt mod_unload modversions 586

parm:           debug:debug print (int)

parm:           brs:use <sysfs>/fs/aufs/si_*/brN (int)


root@localhost:~# insmod aufs.ko

insmod: error inserting 'aufs.ko': -1 Invalid module format


root@localhost:~# dmesg | tail

aufs: disagrees about version of symbol module_layout




a)aufs2 insmod works while newly build vmlinux from colinux.org



root@localhost:/tmp/aufs# dmesg | head -n1

Linux version 2.6.33.5-co-0.7.8 (ccwufu@desktop) (gcc version 4.4.3
(Ubuntu 4.4.3-4ubuntu5) ) #2 PREEMPT Sat Sep 11 17:33:35 CST 2010



root@localhost:/tmp/aufs# modinfo ./aufs.ko

filename:       aufs.ko

version:        2-standalone.tree-33-20100823

description:    aufs -- Advanced multi layered unification filesystem

author:         Junjiro R. Okajima <auf...@li...>

license:        GPL

srcversion:     76B861C166EB214ECD5C416

depends:

vermagic:       2.6.33.5-co-0.7.8 preempt mod_unload modversions 586

parm:           debug:debug print (int)

parm:           brs:use <sysfs>/fs/aufs/si_*/brN (int)



root@localhost:/tmp/aufs#insmod ./aufs.kko



root@localhost:/tmp/aufs# dmesg | tail

fuse_read_super: connection already mounted

aufs 2-standalone.tree-33-20100823



root@localhost:/tmp/aufs# lsmod

Module                  Size  Used by

aufs                  210765  1



root@localhost:/tmp# mount -t aufs -o br=/tmp/rw:${HOME}=ro none /tmp/aufs

root@localhost:~# mount

none on /tmp/aufs type aufs (rw,br=/tmp/rw:/root=ro)



&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&





~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
preblem :
a1)aufs2-base.patch :  2 out of 2 hunks FAILED -- saving rejects to
file fs/splice.c.rej
a2)aufs : make : WARNING: "do_splice_from"
[/home/ccwufu/aufs2/aufs2-standalone.git/fs/aufs/aufs.ko] undefined!
(delete the line : unionfs-2.5.4_for_2.6.33.diff  in
~/colinux078/stable-colinux-20100901/patch/series-2.6.33.5

b)aufs :make : /bin/sh: scripts/mod/modpost: not found
don't breake "make kernel" during make colinux kernel
"scripts/mod/modpost" will be created during "make kernel"

c)aufs : make :  WARNING: Module.symvers is missing; modules will have
no dependencies and modversions.
don't breake "make kernel" during make colinux kernel

-rw-r--r--  1 ccwufu ccwufu  219543 2010-09-11 17:33 Module.symvers
Module.symvers will be created during "make kernel"

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
log :
ccwufu@desktop:~/colinux078/build/linux-2.6.33.5-source$ patch -p1 <
aufs2-base.patch
patching file fs/namei.c
Hunk #1 succeeded at 1208 (offset 1 line).p
Hunk #2 succeeded at 1218 (offset 1 line).
patching file fs/splice.c
Hunk #1 FAILED at 1053.
Hunk #2 FAILED at 1081.
2 out of 2 hunks FAILED -- saving rejects to file fs/splice.c.rej
patching file include/linux/namei.h
Hunk #1 succeeded at 74 with fuzz 2 (offset 1 line).
patching file include/linux/splice.h
Hunk #1 succeeded at 87 with fuzz 2 (offset 5 lines).


ccwufu@desktop:~/colinux078/build/linux-2.6.33.5-source$ patch -p1
<aufs2-standalone.patch
patching file fs/namei.c
Hunk #2 succeeded at 1218 (offset 1 line).
Hunk #3 succeeded at 1241 (offset 1 line).
patching file fs/namespace.c
patching file fs/notify/group.c
patching file fs/notify/inode_mark.c
patching file fs/open.c
patching file fs/splice.c
Hunk #1 succeeded at 1047 with fuzz 2 (offset -30 lines).
Hunk #2 succeeded at 1236 with fuzz 2 (offset 132 lines).
patching file security/commoncap.c
patching file security/device_cgroup.c
patching file security/security.c
Hunk #11 succeeded at 560 with fuzz 2 (offset -7 lines).
Hunk #12 succeeded at 669 (offset 1 line).
Hunk #13 succeeded at 697 (offset 1 line).
ccwufu@desktop:~/colinux078/build/linux-2.6.33.5-source$

ccwufu@desktop:~/aufs2/aufs2-standalone.git$ make
KDIR=/home/ccwufu/colinux078/build/linux-2.6.33.5-build

  WARNING: Symbol version dump
/home/ccwufu/colinux078/build/linux-2.6.33.5-build/Module.symvers
           is missing; modules will have no dependencies and modversions.


Building modules, stage 2.
  MODPOST 1 modules
/bin/sh: scripts/mod/modpost: not found
make[4]: *** [__modpost] Error 127
make[3]: *** [modules] Error 2
make[2]: *** [sub-make] Error 2
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/ccwufu/colinux078/build/linux-2.6.33.5-build'
make: *** [fs/aufs/aufs.ko] Error 2
ccwufu@desktop:~/aufs2/aufs2-standalone.git$


  MODPOST 1 modules
WARNING: "deny_write_access"
[/home/ccwufu/aufs2/aufs2-standalone.git/fs/aufs/aufs.ko] undefined!
WARNING: "do_truncate"
[/home/ccwufu/aufs2/aufs2-standalone.git/fs/aufs/aufs.ko] undefined!
WARNING: "do_splice_from"
[/home/ccwufu/aufs2/aufs2-standalone.git/fs/aufs/aufs.ko] undefined!
WARNING: "cap_file_mmap"
[/home/ccwufu/aufs2/aufs2-standalone.git/fs/aufs/aufs.ko] undefined!
WARNING: "lookup_hash"
[/home/ccwufu/aufs2/aufs2-standalone.git/fs/aufs/aufs.ko] undefined!
WARNING: "do_splice_to"
[/home/ccwufu/aufs2/aufs2-standalone.git/fs/aufs/aufs.ko] undefined!
WARNING: "__lookup_one_len"
[/home/ccwufu/aufs2/aufs2-standalone.git/fs/aufs/aufs.ko] undefined!
  CC      /home/ccwufu/aufs2/aufs2-standalone.git/fs/aufs/aufs.mod.o
  LD [M]  /home/ccwufu/aufs2/aufs2-standalone.git/fs/aufs/aufs.ko
make[1]: Leaving directory `/home/ccwufu/colinux078/build/linux-2.6.33.5-build'
ln -f fs/aufs/aufs.ko aufs.ko
ccwufu@desktop:~/aufs2/aufs2-standalone.git$

[coLinux-users] New Linux image

[qnx4ever <qnx...@gm...>]

Hello coLinux users,
I've created a start mini image of the Alpine Linux 2.0 only 1.52Mb
compressed size;)
Uploaded here http://www.megaupload.com/?d=ABEVBG9C

To install, please unpack coAlpine-2.0.7z to wherever you'd like
coLinux to live.
You will find three files in archive:
_start.bat  coLinux launcher, has to be updated to reflect path to
where colinux-daemon.exe is located.
alp.hda1  512mb ext2 image of the basic Alpine 2.0 install
coLin.conf   coLinux config file

Please copy vmlinux from your coLinux installation into the same
directory and update _start.bat with proper path to colinux-daemon.exe

To boot Alpine in coLinux, simply run _start.bat
Note error on loading modules during boot, you need fill
/lib/modules/2.6.26.8-co-0.7.7.1 with contents of vmlinux-modules.tar
from your coLinux installation.

To switch filesystem to ext3 please run #apk add e2fsprogs && tune2fs
-j /dev/hda
And update fstab to reflect / being ext3, but not ext2

To install full blown sdk run #apk add alpine-sdk
This will install everything you might need to compile any linux
programs and even build your own alpine packages.

Re: [coLinux-users] CoLinux 0.7.7.1 + kernel 2.6.26.8 won't build

[H. N. <hen...@ar...>]

Sergei Zhirikov wrote:
> I have just tried to build kernel 2.6.26.8 with coLinux 0.7.7.1 and it
> fails:
> 
>    CC      drivers/input/mouse/comouse.o
> drivers/input/mouse/comouse.c: In function 'comouse_init':
> drivers/input/mouse/comouse.c:107: error: implicit declaration of function
> 'LONG'
> drivers/input/mouse/comouse.c:108: warning: left shift count >= width of
> type
> drivers/input/mouse/comouse.c:109: warning: left shift count >= width of
> type
> drivers/input/mouse/comouse.c:109: warning: left shift count >= width of
> type
> drivers/input/mouse/comouse.c:109: warning: left shift count >= width of
> type
> make[3]: *** [drivers/input/mouse/comouse.o] Error 1
> make[2]: *** [drivers/input/mouse] Error 2
> make[1]: *** [drivers/input] Error 2
> make: *** [drivers] Error 2
> 
> Previuosly I built kernel 2.6.22.18 with colinux 0.7.6 without any
> problems.
> 
> I did some investigation and found the following.
> In kernel 2.6.22.18 the macro LONG is defined in include/linux/input.h, line
> 925.
> But in kernel 2.6.26.8 that header file is significantly different. The LONG
> macro is not defined any more.
> As far as I can tell, it is not defined anywhere in the Linux source (or
> coLinux for that matter).
> 
> I'm wondering, how could anyone possibly have succeeded building the
> 2.6.26.8/0.7.7.1 combination?
> Are there any patches missing from the coLinux release tarball?

I hope not. The tar was created from SVN tree, so missing files are not doable.

The devel version 0.7.8 can build with kernel 2.6.26.8 without errors. I have just tested.
I can currently not test the stable 0.7.7.1 from here.

As long I remember, the mouse was disabled in kernel config. Maybe this is the condition, that I don't have the problem?
The line "CC ... comouse" does not exist in my build log! My devel config has "# CONFIG_MOUSE_COOPERATIVE is not set". So it is disabled.

Mouse is always disabled in stable, see line 747:
http://colinux.svn.sourceforge.net/viewvc/colinux/branches/stable/conf/linux-2.6.26.8-config?revision=1407&view=markup

Please test with default config from coLinux, or disable the mouse driver in your config.

To compare patch files and config from 0.7.8 tree with yours, you will find all files on SVN http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/ or as tar under nightly builds on http://www.henrynestler.com/colinux/autobuild/


-- 
Gruss Henry

---------------------------------------------------------
... Es folgt Arcor Werbung | Ads follows by Arcor ...


Heute erleben, was morgen Trend wird - das kann man auf der IFA in Berlin. Oder auf arcor.de: Wir stellen Ihnen die wichtigsten News, Trends und Gadgets der IFA vor. Natürlich mit dabei: das brandneue IPTV-Angebot von Vodafone! Alles rund um die Internationale Funkausstellung in Berlin finden Sie hier: http://www.arcor.de/rd/footer.ifa2010

[coLinux-users] CoLinux 0.7.7.1 + kernel 2.6.26.8 won't build

[Sergei Z. <sf...@ya...>]

Hi,

I have just tried to build kernel 2.6.26.8 with coLinux 0.7.7.1 and it fails:

   CC      drivers/input/mouse/comouse.o
drivers/input/mouse/comouse.c: In function 'comouse_init':
drivers/input/mouse/comouse.c:107: error: implicit declaration of function 'LONG'
drivers/input/mouse/comouse.c:108: warning: left shift count >= width of type
drivers/input/mouse/comouse.c:109: warning: left shift count >= width of type
drivers/input/mouse/comouse.c:109: warning: left shift count >= width of type
drivers/input/mouse/comouse.c:109: warning: left shift count >= width of type
make[3]: *** [drivers/input/mouse/comouse.o] Error 1
make[2]: *** [drivers/input/mouse] Error 2
make[1]: *** [drivers/input] Error 2
make: *** [drivers] Error 2

Previuosly I built kernel 2.6.22.18 with colinux 0.7.6 without any problems.

I did some investigation and found the following.
In kernel 2.6.22.18 the macro LONG is defined in include/linux/input.h, line 925.
But in kernel 2.6.26.8 that header file is significantly different. The LONG macro is not defined any more.
As far as I can tell, it is not defined anywhere in the Linux source (or coLinux for that matter).

I'm wondering, how could anyone possibly have succeeded building the 2.6.26.8/0.7.7.1 combination?
Are there any patches missing from the coLinux release tarball?

Thanks and regards,
Sergei.

Re: [coLinux-users] cramfs mount

[Henry N. <hen...@ar...>]

  On 07.09.2010 22:34, qnx4ever wrote:
> is there any way to mount cramfs images using the standard
> coLinux-7.7.1 kernel ?

zgrep CRAMFS /proc/config.gz
# CONFIG_CRAMFS is not set

So, it is not enabled in kernel.

You can enable it and build a kernel your self. Please read section 
"Private kernel config" in file doc/building inside coLinux source, or 
online here:
http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/doc/building

-- 
Henry N.