colinux-users — coLinux users mailing list

Re: [coLinux-users] Vista SP1 - complete failure

[Josep M. A. S. <ja...@pa...>]

commandline:
colinux-daemon.exe -t nt @D:\Colinux\debian\ramdisk-mode.txt

ramdisk-mode.txt:
kernel=vmlinux
initrd=initrd.gz
root=/dev/ram0

colinux version:
Linux (none) 2.6.22.18-co-0.7.3 #1 PREEMPT Sat May 24 22:27:30 UTC 2008 i686 unk
nown


I don't know if it may be related to being Vista Business, or the AMD chip. I
believe you'll have to work that out with the developers via debug builds.

-- 
 _ _  /~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-\
 o o  | Josep Ma [JAZ]                 |
  *   | ----------------               |
 `-´  | Messenger: ja...@ho... |
      \-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~/

Re: [coLinux-users] Vista SP1 - complete failure

[Jonathan D. <tz...@sp...>]

System is an AMD "turion x 2" cpu, on a laptop, running vista business.

As noted, I've been testing directly in ramdisk mode, where the only two 
options given are initrd.gz and root=dev/ram0 (I think) ...

Failure mode is reproduced with that simple setup for all 0.7.3 and 
newer versions I've tried.

Same exact setup is solid as a rock on XP on a P4 2.4.

- Jonathan

Josep Maria Antolín Segura wrote:
> May I ask some more information about the System?
>
> Here i am running Vista Home Premium SP1 (Spanish) with colinux 0.7.3, on a core
> 2 duo laptop (centrino duo) with 2GB of RAM.
> The amount of RAM for colinux is 256MB.
>
> The only problem i had with it was with some random reboots, which in my case,
> were due to the problems with ext2 and ext3 fixed recently.
>
> my config file is as follows:
> kernel=vmlinux
>
> #reenable each time colinux daemon is updated, so that modules can be updated
> aswell.
> initrd=initrd.gz
>
> cobd0=D:\Colinux\debian\Debian-etch.ext3.3gb
> cobd3=D:\Colinux\debian\swap_128Mb
>
> cofs0=C:\
> cofs1=D:\
>
>
> mem=256
> eth0=tuntap
> #eth1=pcap-bridge,ethernet
> root=/dev/cobd0
>
>
> Note that I run it as a service, but i've tried running it manually with the
> following script with no problems:
> c:
> cd "c:\Program Files\colinux\"
> start colinux-daemon.exe -t nt  @D:\Colinux\debian\debian.colinux.conf.txt
> start colinux-console-nt.exe
>
>
>
>
>   

Re: [coLinux-users] Vista SP1 - complete failure

[Josep M. A. S. <ja...@pa...>]

May I ask some more information about the System?

Here i am running Vista Home Premium SP1 (Spanish) with colinux 0.7.3, on a core
2 duo laptop (centrino duo) with 2GB of RAM.
The amount of RAM for colinux is 256MB.

The only problem i had with it was with some random reboots, which in my case,
were due to the problems with ext2 and ext3 fixed recently.

my config file is as follows:
kernel=vmlinux

#reenable each time colinux daemon is updated, so that modules can be updated
aswell.
initrd=initrd.gz

cobd0=D:\Colinux\debian\Debian-etch.ext3.3gb
cobd3=D:\Colinux\debian\swap_128Mb

cofs0=C:\
cofs1=D:\


mem=256
eth0=tuntap
#eth1=pcap-bridge,ethernet
root=/dev/cobd0


Note that I run it as a service, but i've tried running it manually with the
following script with no problems:
c:
cd "c:\Program Files\colinux\"
start colinux-daemon.exe -t nt  @D:\Colinux\debian\debian.colinux.conf.txt
start colinux-console-nt.exe




-- 
 _ _  /~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-\
 o o  | Josep Ma [JAZ]                 |
  *   | ICQ UIN: 7014661               |
 `-´  | Messenger: ja...@ho... |
      \-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~/

Re: [coLinux-users] Vista SP1 - complete failure

[Jonathan D. <tz...@sp...>]

I have the problem with the simple ramdisk (so no images) no matter what 
version I try.

The only difference is, with the "ntflood" 0.8.0 version, the onset of 
the slow response is delayed several minutes.

When the 'slow response' problem occurs, it affects BOTH colinux and 
windows, and continues to affect windows even after colinux is shut 
down.  The only way to recover is to reboot.

- Jonathan

Paolo Minazzi wrote:
> At home I have Vista.
> I have used a little colinux on Vista, only to see if it works.
> I had found the bug of "flooding", that Henry have solved.
> The other things seem work for me .... I don't have important problem.
> But I use it a little. I use a lot colinux on XP at work.
> It is interesting understand what exactly works and what has problems....
> Have you problem with a very simple ramdisk ?
> I could try your images ....
> Bye,
> Paolo
>
> On Wed, Jun 18, 2008 at 2:58 AM, Jonathan Deitch <tz...@sp...> wrote:
>   
>> I saw a definite difference in behavior between the 0.7.3 and the
>> "ntflood" 0.8.0 ...
>>
>> 0.7.3 would cause the system to lockup within a minute ... 0.8.0 ntflood
>> would run OK for 4-5 minutes and then lock up (same exact symptoms).
>>
>> The pictures, unfortunately, do not help.
>>
>> As I memtioned, this problem occurs with minimal settings (initrd and
>> root) booting the initrd ram boot.
>>
>> No image, no network, no nothing.
>>
>> If I can't get the RAM boot to work, then there's no point going any
>> farther with anything else.
>>
>> Any ideas?  I really need help on this ... if there isn't a solution
>> soon, I will probably be forced to abandon using colinux altogether, and
>> rethinking my whole way of working.  :-(
>>
>> - Jonathan
>> Henry Nestler wrote:
>>     
>>> I have no Vista running. But from an example of install I have lots of
>>> screenshots. Perhaps you will find suggestions from there:
>>> http://www.henrynestler.com/colinux/screenshoots/Vista-Album
>>>
>>> The "ntconsoleflood" is also fixed in coLinux version 0.7.3 final release.
>>>
>>> Henry
>>>
>>> Jonathan Deitch wrote:
>>>
>>>       
>>>>  Whoops ... I spoke too soon.
>>>>
>>>> The "ntconsoleflood" 0.8.0 version allows the system to boot, and run
>>>> for a bit.
>>>>
>>>> After about 5 minutes, however, the same exact circumstances as before
>>>> occur.
>>>>
>>>> Reproduced with all the same settings (including the barebones /dev/RAM
>>>> boot).
>>>>
>>>> Same symptoms with vista before after colinux shutdown - everything runs
>>>> very slow, entire PC is unusable.
>>>>
>>>> So still no solution.
>>>>
>>>> - Jonathan
>>>>
>>>> Jonathan Deitch wrote:
>>>>
>>>>         
>>>>> OK ... update ...
>>>>>
>>>>> After diving into the colinux-users archive, I saw a note about the
>>>>> 0.8.0 test version for ntconsoleflood ... that actually seems to have
>>>>> fixed this issue.
>>>>>
>>>>> As noted in the email string that led to that test version, the Vista
>>>>> Business I'm running it on is a multi-core cpu; this may be another
>>>>> example where a SMP setup is breaking the 'older' versions of colinux.
>>>>>
>>>>> My previous system, is a WinXP P4 2.4 .. which is a single cpu system.
>>>>>
>>>>> - Jonathan
>>>>>
>>>>> Jonathan Deitch wrote:
>>>>>
>>>>>           
>>>>>> I've tried every trick I can find on the web, and I can't get /any/
>>>>>> version of colinux running on Vista SP1.
>>>>>>
>>>>>> Tried 0.7.3 (release version) and the latest 0.8.x development
>>>>>> version.  Same exact symptom.
>>>>>>
>>>>>> What happens is the system boots up, and seems to be just fine.
>>>>>>
>>>>>> After about 60 seconds, /both /the linux /and/ Vista slow to a crawl
>>>>>> and neither is usable.
>>>>>>
>>>>>> Even if you get Colinux shut down, Vista is /still/ slow as molasses
>>>>>> and the only recovery is to reboot (and that's if Vista doesn't
>>>>>> freeze on shutdown).
>>>>>>
>>>>>> Tried with multiple system images (various flavors of Linux), same thing.
>>>>>>
>>>>>> Tried with the bare Ramdisk boot (just initrd.gz) - same thing.
>>>>>>
>>>>>> Tried to run a debug on the bare ramdisk boot ... the instant the
>>>>>> system started, the entire machine rebooted.  No bluescreen, just
>>>>>> black screen then POST.
>>>>>>
>>>>>> So no way to capture debug info, either.
>>>>>>
>>>>>> So I'm completely stuck ... and this is a huge issue for me ... I do
>>>>>> major development work under colinux, and they want to retire my XP
>>>>>> box, since the entire company is migrating to Vista.
>>>>>>
>>>>>> Soon I won't be given a choice; I need this working before that
>>>>>> happens ...
>>>>>>
>>>>>> Anyone got any ideas?
>>>>>>
>>>>>> Remember ... the image in this case is irrelevant - the problem
>>>>>> occurs w/the initrd.gz RAM boot. so it's something endemic to within
>>>>>> colinux and its kernel itself.
>>>>>>
>>>>>> - Jonathan
>>>>>>
>>>>>> -------------------------------------------------------------------------
>>>>>> Check out the new SourceForge.net Marketplace.
>>>>>> It's the best place to buy or sell services for
>>>>>> just about anything Open Source.
>>>>>> http://sourceforge.net/services/buy/index.php
>>>>>>
>>>>>> _______________________________________________
>>>>>> coLinux-users mailing list
>>>>>> coL...@li... <mailto:coL...@li...>
>>>>>> https://lists.sourceforge.net/lists/listinfo/colinux-users
>>>>>>
>>>>>>
>>>>>>             
>>>> ------------------------------------------------------------------------
>>>>
>>>> -------------------------------------------------------------------------
>>>> Check out the new SourceForge.net Marketplace.
>>>> It's the best place to buy or sell services for
>>>> just about anything Open Source.
>>>> http://sourceforge.net/services/buy/index.php
>>>>
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>>         
>> -------------------------------------------------------------------------
>> Check out the new SourceForge.net Marketplace.
>> It's the best place to buy or sell services for
>> just about anything Open Source.
>> http://sourceforge.net/services/buy/index.php
>> _______________________________________________
>> coLinux-users mailing list
>> coL...@li...
>> https://lists.sourceforge.net/lists/listinfo/colinux-users
>>
>>     
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>   

Re: [coLinux-users] Vista SP1 - complete failure

[Steve W. <li...@la...>]

Ive know upgraded to lastest stable "Linux colinux 2.6.22.18-co-0.7.3 
#1" coLinux-stable-20080524 and it also works fine.

Steve

Steve Wagner schrieb:
> No i used a development snapshot downloaded from colinux.org.
> 
> Steve
> 
> Henry Nestler schrieb:
>> Hello Steve,
>>
>> thank you for your post.
>>
>> You have self compiled the kernel? Please let us see your used gcc and
>> type inside: "dmesg | head -n1"
>>
>> Please send me your kernel config.
>>
>> Henry
>>
>> Steve Wagner wrote:
>>> I cant help you, but i can say that "Linux colinux 2.6.17-co-0.8.0 #2" 
>>> works with Vista SP1 on an Core Duo without any problem for me.
>>>
>>> Steve
>>>
>>> Jonathan Deitch schrieb:
>>>> I saw a definite difference in behavior between the 0.7.3 and the 
>>>> "ntflood" 0.8.0 ...
>>>>
>>>> 0.7.3 would cause the system to lockup within a minute ... 0.8.0 ntflood 
>>>> would run OK for 4-5 minutes and then lock up (same exact symptoms).
>>>>
>>>> The pictures, unfortunately, do not help.
>>>>
>>>> As I memtioned, this problem occurs with minimal settings (initrd and 
>>>> root) booting the initrd ram boot.
>>>>
>>>> No image, no network, no nothing.
>>>>
>>>> If I can't get the RAM boot to work, then there's no point going any 
>>>> farther with anything else.
>>>>
>>>> Any ideas?  I really need help on this ... if there isn't a solution 
>>>> soon, I will probably be forced to abandon using colinux altogether, and 
>>>> rethinking my whole way of working.  :-(
>>>>
>>>> - Jonathan
>>>> Henry Nestler wrote:
>>>>> I have no Vista running. But from an example of install I have lots of
>>>>> screenshots. Perhaps you will find suggestions from there:
>>>>> http://www.henrynestler.com/colinux/screenshoots/Vista-Album
>>>>>
>>>>> The "ntconsoleflood" is also fixed in coLinux version 0.7.3 final release.
>>>>>
>>>>> Henry
>>>>>
>>>>> Jonathan Deitch wrote:
>>>>>   
>>>>>>  Whoops ... I spoke too soon.
>>>>>>
>>>>>> The "ntconsoleflood" 0.8.0 version allows the system to boot, and run
>>>>>> for a bit.
>>>>>>
>>>>>> After about 5 minutes, however, the same exact circumstances as before
>>>>>> occur.
>>>>>>
>>>>>> Reproduced with all the same settings (including the barebones /dev/RAM
>>>>>> boot).
>>>>>>
>>>>>> Same symptoms with vista before after colinux shutdown - everything runs
>>>>>> very slow, entire PC is unusable.
>>>>>>
>>>>>> So still no solution.
>>>>>>
>>>>>> - Jonathan
>>>>>>
>>>>>> Jonathan Deitch wrote:
>>>>>>     
>>>>>>> OK ... update ...
>>>>>>>
>>>>>>> After diving into the colinux-users archive, I saw a note about the
>>>>>>> 0.8.0 test version for ntconsoleflood ... that actually seems to have
>>>>>>> fixed this issue.
>>>>>>>
>>>>>>> As noted in the email string that led to that test version, the Vista
>>>>>>> Business I'm running it on is a multi-core cpu; this may be another
>>>>>>> example where a SMP setup is breaking the 'older' versions of colinux.
>>>>>>>
>>>>>>> My previous system, is a WinXP P4 2.4 .. which is a single cpu system.
>>>>>>>
>>>>>>> - Jonathan
>>>>>>>
>>>>>>> Jonathan Deitch wrote:
>>>>>>>       
>>>>>>>> I've tried every trick I can find on the web, and I can't get /any/
>>>>>>>> version of colinux running on Vista SP1.
>>>>>>>>
>>>>>>>> Tried 0.7.3 (release version) and the latest 0.8.x development
>>>>>>>> version.  Same exact symptom.
>>>>>>>>
>>>>>>>> What happens is the system boots up, and seems to be just fine.
>>>>>>>>
>>>>>>>> After about 60 seconds, /both /the linux /and/ Vista slow to a crawl
>>>>>>>> and neither is usable.
>>>>>>>>
>>>>>>>> Even if you get Colinux shut down, Vista is /still/ slow as molasses
>>>>>>>> and the only recovery is to reboot (and that's if Vista doesn't
>>>>>>>> freeze on shutdown).
>>>>>>>>
>>>>>>>> Tried with multiple system images (various flavors of Linux), same thing.
>>>>>>>>
>>>>>>>> Tried with the bare Ramdisk boot (just initrd.gz) - same thing.
>>>>>>>>
>>>>>>>> Tried to run a debug on the bare ramdisk boot ... the instant the
>>>>>>>> system started, the entire machine rebooted.  No bluescreen, just
>>>>>>>> black screen then POST.
>>>>>>>>
>>>>>>>> So no way to capture debug info, either.
>>>>>>>>
>>>>>>>> So I'm completely stuck ... and this is a huge issue for me ... I do
>>>>>>>> major development work under colinux, and they want to retire my XP
>>>>>>>> box, since the entire company is migrating to Vista.
>>>>>>>>
>>>>>>>> Soon I won't be given a choice; I need this working before that
>>>>>>>> happens ...
>>>>>>>>
>>>>>>>> Anyone got any ideas?
>>>>>>>>
>>>>>>>> Remember ... the image in this case is irrelevant - the problem
>>>>>>>> occurs w/the initrd.gz RAM boot. so it's something endemic to within
>>>>>>>> colinux and its kernel itself.
>>>>>>>>
>>>>>>>> - Jonathan
>>>>>>>>  
>>>>>>>> -------------------------------------------------------------------------
> 
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
> 

Re: [coLinux-users] Vista SP1 - complete failure

[Steve W. <li...@la...>]

No i used a development snapshot downloaded from colinux.org.

Steve

Henry Nestler schrieb:
> Hello Steve,
> 
> thank you for your post.
> 
> You have self compiled the kernel? Please let us see your used gcc and
> type inside: "dmesg | head -n1"
> 
> Please send me your kernel config.
> 
> Henry
> 
> Steve Wagner wrote:
>> I cant help you, but i can say that "Linux colinux 2.6.17-co-0.8.0 #2" 
>> works with Vista SP1 on an Core Duo without any problem for me.
>>
>> Steve
>>
>> Jonathan Deitch schrieb:
>>> I saw a definite difference in behavior between the 0.7.3 and the 
>>> "ntflood" 0.8.0 ...
>>>
>>> 0.7.3 would cause the system to lockup within a minute ... 0.8.0 ntflood 
>>> would run OK for 4-5 minutes and then lock up (same exact symptoms).
>>>
>>> The pictures, unfortunately, do not help.
>>>
>>> As I memtioned, this problem occurs with minimal settings (initrd and 
>>> root) booting the initrd ram boot.
>>>
>>> No image, no network, no nothing.
>>>
>>> If I can't get the RAM boot to work, then there's no point going any 
>>> farther with anything else.
>>>
>>> Any ideas?  I really need help on this ... if there isn't a solution 
>>> soon, I will probably be forced to abandon using colinux altogether, and 
>>> rethinking my whole way of working.  :-(
>>>
>>> - Jonathan
>>> Henry Nestler wrote:
>>>> I have no Vista running. But from an example of install I have lots of
>>>> screenshots. Perhaps you will find suggestions from there:
>>>> http://www.henrynestler.com/colinux/screenshoots/Vista-Album
>>>>
>>>> The "ntconsoleflood" is also fixed in coLinux version 0.7.3 final release.
>>>>
>>>> Henry
>>>>
>>>> Jonathan Deitch wrote:
>>>>   
>>>>>  Whoops ... I spoke too soon.
>>>>>
>>>>> The "ntconsoleflood" 0.8.0 version allows the system to boot, and run
>>>>> for a bit.
>>>>>
>>>>> After about 5 minutes, however, the same exact circumstances as before
>>>>> occur.
>>>>>
>>>>> Reproduced with all the same settings (including the barebones /dev/RAM
>>>>> boot).
>>>>>
>>>>> Same symptoms with vista before after colinux shutdown - everything runs
>>>>> very slow, entire PC is unusable.
>>>>>
>>>>> So still no solution.
>>>>>
>>>>> - Jonathan
>>>>>
>>>>> Jonathan Deitch wrote:
>>>>>     
>>>>>> OK ... update ...
>>>>>>
>>>>>> After diving into the colinux-users archive, I saw a note about the
>>>>>> 0.8.0 test version for ntconsoleflood ... that actually seems to have
>>>>>> fixed this issue.
>>>>>>
>>>>>> As noted in the email string that led to that test version, the Vista
>>>>>> Business I'm running it on is a multi-core cpu; this may be another
>>>>>> example where a SMP setup is breaking the 'older' versions of colinux.
>>>>>>
>>>>>> My previous system, is a WinXP P4 2.4 .. which is a single cpu system.
>>>>>>
>>>>>> - Jonathan
>>>>>>
>>>>>> Jonathan Deitch wrote:
>>>>>>       
>>>>>>> I've tried every trick I can find on the web, and I can't get /any/
>>>>>>> version of colinux running on Vista SP1.
>>>>>>>
>>>>>>> Tried 0.7.3 (release version) and the latest 0.8.x development
>>>>>>> version.  Same exact symptom.
>>>>>>>
>>>>>>> What happens is the system boots up, and seems to be just fine.
>>>>>>>
>>>>>>> After about 60 seconds, /both /the linux /and/ Vista slow to a crawl
>>>>>>> and neither is usable.
>>>>>>>
>>>>>>> Even if you get Colinux shut down, Vista is /still/ slow as molasses
>>>>>>> and the only recovery is to reboot (and that's if Vista doesn't
>>>>>>> freeze on shutdown).
>>>>>>>
>>>>>>> Tried with multiple system images (various flavors of Linux), same thing.
>>>>>>>
>>>>>>> Tried with the bare Ramdisk boot (just initrd.gz) - same thing.
>>>>>>>
>>>>>>> Tried to run a debug on the bare ramdisk boot ... the instant the
>>>>>>> system started, the entire machine rebooted.  No bluescreen, just
>>>>>>> black screen then POST.
>>>>>>>
>>>>>>> So no way to capture debug info, either.
>>>>>>>
>>>>>>> So I'm completely stuck ... and this is a huge issue for me ... I do
>>>>>>> major development work under colinux, and they want to retire my XP
>>>>>>> box, since the entire company is migrating to Vista.
>>>>>>>
>>>>>>> Soon I won't be given a choice; I need this working before that
>>>>>>> happens ...
>>>>>>>
>>>>>>> Anyone got any ideas?
>>>>>>>
>>>>>>> Remember ... the image in this case is irrelevant - the problem
>>>>>>> occurs w/the initrd.gz RAM boot. so it's something endemic to within
>>>>>>> colinux and its kernel itself.
>>>>>>>
>>>>>>> - Jonathan
>>>>>>>  
>>>>>>> -------------------------------------------------------------------------
> 

Re: [coLinux-users] Vista SP1 - complete failure

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

Hello Steve,

thank you for your post.

You have self compiled the kernel? Please let us see your used gcc and
type inside: "dmesg | head -n1"

Please send me your kernel config.

Henry

Steve Wagner wrote:
> I cant help you, but i can say that "Linux colinux 2.6.17-co-0.8.0 #2" 
> works with Vista SP1 on an Core Duo without any problem for me.
> 
> Steve
> 
> Jonathan Deitch schrieb:
>> I saw a definite difference in behavior between the 0.7.3 and the 
>> "ntflood" 0.8.0 ...
>>
>> 0.7.3 would cause the system to lockup within a minute ... 0.8.0 ntflood 
>> would run OK for 4-5 minutes and then lock up (same exact symptoms).
>>
>> The pictures, unfortunately, do not help.
>>
>> As I memtioned, this problem occurs with minimal settings (initrd and 
>> root) booting the initrd ram boot.
>>
>> No image, no network, no nothing.
>>
>> If I can't get the RAM boot to work, then there's no point going any 
>> farther with anything else.
>>
>> Any ideas?  I really need help on this ... if there isn't a solution 
>> soon, I will probably be forced to abandon using colinux altogether, and 
>> rethinking my whole way of working.  :-(
>>
>> - Jonathan
>> Henry Nestler wrote:
>>> I have no Vista running. But from an example of install I have lots of
>>> screenshots. Perhaps you will find suggestions from there:
>>> http://www.henrynestler.com/colinux/screenshoots/Vista-Album
>>>
>>> The "ntconsoleflood" is also fixed in coLinux version 0.7.3 final release.
>>>
>>> Henry
>>>
>>> Jonathan Deitch wrote:
>>>   
>>>>  Whoops ... I spoke too soon.
>>>>
>>>> The "ntconsoleflood" 0.8.0 version allows the system to boot, and run
>>>> for a bit.
>>>>
>>>> After about 5 minutes, however, the same exact circumstances as before
>>>> occur.
>>>>
>>>> Reproduced with all the same settings (including the barebones /dev/RAM
>>>> boot).
>>>>
>>>> Same symptoms with vista before after colinux shutdown - everything runs
>>>> very slow, entire PC is unusable.
>>>>
>>>> So still no solution.
>>>>
>>>> - Jonathan
>>>>
>>>> Jonathan Deitch wrote:
>>>>     
>>>>> OK ... update ...
>>>>>
>>>>> After diving into the colinux-users archive, I saw a note about the
>>>>> 0.8.0 test version for ntconsoleflood ... that actually seems to have
>>>>> fixed this issue.
>>>>>
>>>>> As noted in the email string that led to that test version, the Vista
>>>>> Business I'm running it on is a multi-core cpu; this may be another
>>>>> example where a SMP setup is breaking the 'older' versions of colinux.
>>>>>
>>>>> My previous system, is a WinXP P4 2.4 .. which is a single cpu system.
>>>>>
>>>>> - Jonathan
>>>>>
>>>>> Jonathan Deitch wrote:
>>>>>       
>>>>>> I've tried every trick I can find on the web, and I can't get /any/
>>>>>> version of colinux running on Vista SP1.
>>>>>>
>>>>>> Tried 0.7.3 (release version) and the latest 0.8.x development
>>>>>> version.  Same exact symptom.
>>>>>>
>>>>>> What happens is the system boots up, and seems to be just fine.
>>>>>>
>>>>>> After about 60 seconds, /both /the linux /and/ Vista slow to a crawl
>>>>>> and neither is usable.
>>>>>>
>>>>>> Even if you get Colinux shut down, Vista is /still/ slow as molasses
>>>>>> and the only recovery is to reboot (and that's if Vista doesn't
>>>>>> freeze on shutdown).
>>>>>>
>>>>>> Tried with multiple system images (various flavors of Linux), same thing.
>>>>>>
>>>>>> Tried with the bare Ramdisk boot (just initrd.gz) - same thing.
>>>>>>
>>>>>> Tried to run a debug on the bare ramdisk boot ... the instant the
>>>>>> system started, the entire machine rebooted.  No bluescreen, just
>>>>>> black screen then POST.
>>>>>>
>>>>>> So no way to capture debug info, either.
>>>>>>
>>>>>> So I'm completely stuck ... and this is a huge issue for me ... I do
>>>>>> major development work under colinux, and they want to retire my XP
>>>>>> box, since the entire company is migrating to Vista.
>>>>>>
>>>>>> Soon I won't be given a choice; I need this working before that
>>>>>> happens ...
>>>>>>
>>>>>> Anyone got any ideas?
>>>>>>
>>>>>> Remember ... the image in this case is irrelevant - the problem
>>>>>> occurs w/the initrd.gz RAM boot. so it's something endemic to within
>>>>>> colinux and its kernel itself.
>>>>>>
>>>>>> - Jonathan
>>>>>>  
>>>>>> -------------------------------------------------------------------------

Re: [coLinux-users] Vista SP1 - complete failure

[Steve W. <li...@la...>]

I cant help you, but i can say that "Linux colinux 2.6.17-co-0.8.0 #2" 
works with Vista SP1 on an Core Duo without any problem for me.

Steve

Jonathan Deitch schrieb:
> I saw a definite difference in behavior between the 0.7.3 and the 
> "ntflood" 0.8.0 ...
> 
> 0.7.3 would cause the system to lockup within a minute ... 0.8.0 ntflood 
> would run OK for 4-5 minutes and then lock up (same exact symptoms).
> 
> The pictures, unfortunately, do not help.
> 
> As I memtioned, this problem occurs with minimal settings (initrd and 
> root) booting the initrd ram boot.
> 
> No image, no network, no nothing.
> 
> If I can't get the RAM boot to work, then there's no point going any 
> farther with anything else.
> 
> Any ideas?  I really need help on this ... if there isn't a solution 
> soon, I will probably be forced to abandon using colinux altogether, and 
> rethinking my whole way of working.  :-(
> 
> - Jonathan
> Henry Nestler wrote:
>> I have no Vista running. But from an example of install I have lots of
>> screenshots. Perhaps you will find suggestions from there:
>> http://www.henrynestler.com/colinux/screenshoots/Vista-Album
>>
>> The "ntconsoleflood" is also fixed in coLinux version 0.7.3 final release.
>>
>> Henry
>>
>> Jonathan Deitch wrote:
>>   
>>>  Whoops ... I spoke too soon.
>>>
>>> The "ntconsoleflood" 0.8.0 version allows the system to boot, and run
>>> for a bit.
>>>
>>> After about 5 minutes, however, the same exact circumstances as before
>>> occur.
>>>
>>> Reproduced with all the same settings (including the barebones /dev/RAM
>>> boot).
>>>
>>> Same symptoms with vista before after colinux shutdown - everything runs
>>> very slow, entire PC is unusable.
>>>
>>> So still no solution.
>>>
>>> - Jonathan
>>>
>>> Jonathan Deitch wrote:
>>>     
>>>> OK ... update ...
>>>>
>>>> After diving into the colinux-users archive, I saw a note about the
>>>> 0.8.0 test version for ntconsoleflood ... that actually seems to have
>>>> fixed this issue.
>>>>
>>>> As noted in the email string that led to that test version, the Vista
>>>> Business I'm running it on is a multi-core cpu; this may be another
>>>> example where a SMP setup is breaking the 'older' versions of colinux.
>>>>
>>>> My previous system, is a WinXP P4 2.4 .. which is a single cpu system.
>>>>
>>>> - Jonathan
>>>>
>>>> Jonathan Deitch wrote:
>>>>       
>>>>> I've tried every trick I can find on the web, and I can't get /any/
>>>>> version of colinux running on Vista SP1.
>>>>>
>>>>> Tried 0.7.3 (release version) and the latest 0.8.x development
>>>>> version.  Same exact symptom.
>>>>>
>>>>> What happens is the system boots up, and seems to be just fine.
>>>>>
>>>>> After about 60 seconds, /both /the linux /and/ Vista slow to a crawl
>>>>> and neither is usable.
>>>>>
>>>>> Even if you get Colinux shut down, Vista is /still/ slow as molasses
>>>>> and the only recovery is to reboot (and that's if Vista doesn't
>>>>> freeze on shutdown).
>>>>>
>>>>> Tried with multiple system images (various flavors of Linux), same thing.
>>>>>
>>>>> Tried with the bare Ramdisk boot (just initrd.gz) - same thing.
>>>>>
>>>>> Tried to run a debug on the bare ramdisk boot ... the instant the
>>>>> system started, the entire machine rebooted.  No bluescreen, just
>>>>> black screen then POST.
>>>>>
>>>>> So no way to capture debug info, either.
>>>>>
>>>>> So I'm completely stuck ... and this is a huge issue for me ... I do
>>>>> major development work under colinux, and they want to retire my XP
>>>>> box, since the entire company is migrating to Vista.
>>>>>
>>>>> Soon I won't be given a choice; I need this working before that
>>>>> happens ...
>>>>>
>>>>> Anyone got any ideas?
>>>>>
>>>>> Remember ... the image in this case is irrelevant - the problem
>>>>> occurs w/the initrd.gz RAM boot. so it's something endemic to within
>>>>> colinux and its kernel itself.
>>>>>
>>>>> - Jonathan
>>>>>  
>>>>> -------------------------------------------------------------------------
>>>>> Check out the new SourceForge.net Marketplace.
>>>>> It's the best place to buy or sell services for
>>>>> just about anything Open Source.
>>>>> http://sourceforge.net/services/buy/index.php
>>>>>  
>>>>> _______________________________________________
>>>>> coLinux-users mailing list
>>>>> coL...@li... <mailto:coL...@li...>
>>>>> https://lists.sourceforge.net/lists/listinfo/colinux-users
>>>>>   
>>>>>         
>>> ------------------------------------------------------------------------
>>>
>>> -------------------------------------------------------------------------
>>> Check out the new SourceForge.net Marketplace.
>>> It's the best place to buy or sell services for
>>> just about anything Open Source.
>>> http://sourceforge.net/services/buy/index.php
>>>
>>>
>>> ------------------------------------------------------------------------
>>>     
> 
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
> 

Re: [coLinux-users] Vista SP1 - complete failure

[Paolo M. <pao...@gm...>]

At home I have Vista.
I have used a little colinux on Vista, only to see if it works.
I had found the bug of "flooding", that Henry have solved.
The other things seem work for me .... I don't have important problem.
But I use it a little. I use a lot colinux on XP at work.
It is interesting understand what exactly works and what has problems....
Have you problem with a very simple ramdisk ?
I could try your images ....
Bye,
Paolo

On Wed, Jun 18, 2008 at 2:58 AM, Jonathan Deitch <tz...@sp...> wrote:
> I saw a definite difference in behavior between the 0.7.3 and the
> "ntflood" 0.8.0 ...
>
> 0.7.3 would cause the system to lockup within a minute ... 0.8.0 ntflood
> would run OK for 4-5 minutes and then lock up (same exact symptoms).
>
> The pictures, unfortunately, do not help.
>
> As I memtioned, this problem occurs with minimal settings (initrd and
> root) booting the initrd ram boot.
>
> No image, no network, no nothing.
>
> If I can't get the RAM boot to work, then there's no point going any
> farther with anything else.
>
> Any ideas?  I really need help on this ... if there isn't a solution
> soon, I will probably be forced to abandon using colinux altogether, and
> rethinking my whole way of working.  :-(
>
> - Jonathan
> Henry Nestler wrote:
>> I have no Vista running. But from an example of install I have lots of
>> screenshots. Perhaps you will find suggestions from there:
>> http://www.henrynestler.com/colinux/screenshoots/Vista-Album
>>
>> The "ntconsoleflood" is also fixed in coLinux version 0.7.3 final release.
>>
>> Henry
>>
>> Jonathan Deitch wrote:
>>
>>>  Whoops ... I spoke too soon.
>>>
>>> The "ntconsoleflood" 0.8.0 version allows the system to boot, and run
>>> for a bit.
>>>
>>> After about 5 minutes, however, the same exact circumstances as before
>>> occur.
>>>
>>> Reproduced with all the same settings (including the barebones /dev/RAM
>>> boot).
>>>
>>> Same symptoms with vista before after colinux shutdown - everything runs
>>> very slow, entire PC is unusable.
>>>
>>> So still no solution.
>>>
>>> - Jonathan
>>>
>>> Jonathan Deitch wrote:
>>>
>>>> OK ... update ...
>>>>
>>>> After diving into the colinux-users archive, I saw a note about the
>>>> 0.8.0 test version for ntconsoleflood ... that actually seems to have
>>>> fixed this issue.
>>>>
>>>> As noted in the email string that led to that test version, the Vista
>>>> Business I'm running it on is a multi-core cpu; this may be another
>>>> example where a SMP setup is breaking the 'older' versions of colinux.
>>>>
>>>> My previous system, is a WinXP P4 2.4 .. which is a single cpu system.
>>>>
>>>> - Jonathan
>>>>
>>>> Jonathan Deitch wrote:
>>>>
>>>>> I've tried every trick I can find on the web, and I can't get /any/
>>>>> version of colinux running on Vista SP1.
>>>>>
>>>>> Tried 0.7.3 (release version) and the latest 0.8.x development
>>>>> version.  Same exact symptom.
>>>>>
>>>>> What happens is the system boots up, and seems to be just fine.
>>>>>
>>>>> After about 60 seconds, /both /the linux /and/ Vista slow to a crawl
>>>>> and neither is usable.
>>>>>
>>>>> Even if you get Colinux shut down, Vista is /still/ slow as molasses
>>>>> and the only recovery is to reboot (and that's if Vista doesn't
>>>>> freeze on shutdown).
>>>>>
>>>>> Tried with multiple system images (various flavors of Linux), same thing.
>>>>>
>>>>> Tried with the bare Ramdisk boot (just initrd.gz) - same thing.
>>>>>
>>>>> Tried to run a debug on the bare ramdisk boot ... the instant the
>>>>> system started, the entire machine rebooted.  No bluescreen, just
>>>>> black screen then POST.
>>>>>
>>>>> So no way to capture debug info, either.
>>>>>
>>>>> So I'm completely stuck ... and this is a huge issue for me ... I do
>>>>> major development work under colinux, and they want to retire my XP
>>>>> box, since the entire company is migrating to Vista.
>>>>>
>>>>> Soon I won't be given a choice; I need this working before that
>>>>> happens ...
>>>>>
>>>>> Anyone got any ideas?
>>>>>
>>>>> Remember ... the image in this case is irrelevant - the problem
>>>>> occurs w/the initrd.gz RAM boot. so it's something endemic to within
>>>>> colinux and its kernel itself.
>>>>>
>>>>> - Jonathan
>>>>>
>>>>> -------------------------------------------------------------------------
>>>>> Check out the new SourceForge.net Marketplace.
>>>>> It's the best place to buy or sell services for
>>>>> just about anything Open Source.
>>>>> http://sourceforge.net/services/buy/index.php
>>>>>
>>>>> _______________________________________________
>>>>> coLinux-users mailing list
>>>>> coL...@li... <mailto:coL...@li...>
>>>>> https://lists.sourceforge.net/lists/listinfo/colinux-users
>>>>>
>>>>>
>>> ------------------------------------------------------------------------
>>>
>>> -------------------------------------------------------------------------
>>> Check out the new SourceForge.net Marketplace.
>>> It's the best place to buy or sell services for
>>> just about anything Open Source.
>>> http://sourceforge.net/services/buy/index.php
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>

Re: [coLinux-users] Vista SP1 - complete failure

[Jonathan D. <tz...@sp...>]

I saw a definite difference in behavior between the 0.7.3 and the 
"ntflood" 0.8.0 ...

0.7.3 would cause the system to lockup within a minute ... 0.8.0 ntflood 
would run OK for 4-5 minutes and then lock up (same exact symptoms).

The pictures, unfortunately, do not help.

As I memtioned, this problem occurs with minimal settings (initrd and 
root) booting the initrd ram boot.

No image, no network, no nothing.

If I can't get the RAM boot to work, then there's no point going any 
farther with anything else.

Any ideas?  I really need help on this ... if there isn't a solution 
soon, I will probably be forced to abandon using colinux altogether, and 
rethinking my whole way of working.  :-(

- Jonathan
Henry Nestler wrote:
> I have no Vista running. But from an example of install I have lots of
> screenshots. Perhaps you will find suggestions from there:
> http://www.henrynestler.com/colinux/screenshoots/Vista-Album
>
> The "ntconsoleflood" is also fixed in coLinux version 0.7.3 final release.
>
> Henry
>
> Jonathan Deitch wrote:
>   
>>  Whoops ... I spoke too soon.
>>
>> The "ntconsoleflood" 0.8.0 version allows the system to boot, and run
>> for a bit.
>>
>> After about 5 minutes, however, the same exact circumstances as before
>> occur.
>>
>> Reproduced with all the same settings (including the barebones /dev/RAM
>> boot).
>>
>> Same symptoms with vista before after colinux shutdown - everything runs
>> very slow, entire PC is unusable.
>>
>> So still no solution.
>>
>> - Jonathan
>>
>> Jonathan Deitch wrote:
>>     
>>> OK ... update ...
>>>
>>> After diving into the colinux-users archive, I saw a note about the
>>> 0.8.0 test version for ntconsoleflood ... that actually seems to have
>>> fixed this issue.
>>>
>>> As noted in the email string that led to that test version, the Vista
>>> Business I'm running it on is a multi-core cpu; this may be another
>>> example where a SMP setup is breaking the 'older' versions of colinux.
>>>
>>> My previous system, is a WinXP P4 2.4 .. which is a single cpu system.
>>>
>>> - Jonathan
>>>
>>> Jonathan Deitch wrote:
>>>       
>>>> I've tried every trick I can find on the web, and I can't get /any/
>>>> version of colinux running on Vista SP1.
>>>>
>>>> Tried 0.7.3 (release version) and the latest 0.8.x development
>>>> version.  Same exact symptom.
>>>>
>>>> What happens is the system boots up, and seems to be just fine.
>>>>
>>>> After about 60 seconds, /both /the linux /and/ Vista slow to a crawl
>>>> and neither is usable.
>>>>
>>>> Even if you get Colinux shut down, Vista is /still/ slow as molasses
>>>> and the only recovery is to reboot (and that's if Vista doesn't
>>>> freeze on shutdown).
>>>>
>>>> Tried with multiple system images (various flavors of Linux), same thing.
>>>>
>>>> Tried with the bare Ramdisk boot (just initrd.gz) - same thing.
>>>>
>>>> Tried to run a debug on the bare ramdisk boot ... the instant the
>>>> system started, the entire machine rebooted.  No bluescreen, just
>>>> black screen then POST.
>>>>
>>>> So no way to capture debug info, either.
>>>>
>>>> So I'm completely stuck ... and this is a huge issue for me ... I do
>>>> major development work under colinux, and they want to retire my XP
>>>> box, since the entire company is migrating to Vista.
>>>>
>>>> Soon I won't be given a choice; I need this working before that
>>>> happens ...
>>>>
>>>> Anyone got any ideas?
>>>>
>>>> Remember ... the image in this case is irrelevant - the problem
>>>> occurs w/the initrd.gz RAM boot. so it's something endemic to within
>>>> colinux and its kernel itself.
>>>>
>>>> - Jonathan
>>>>  
>>>> -------------------------------------------------------------------------
>>>> Check out the new SourceForge.net Marketplace.
>>>> It's the best place to buy or sell services for
>>>> just about anything Open Source.
>>>> http://sourceforge.net/services/buy/index.php
>>>>  
>>>> _______________________________________________
>>>> coLinux-users mailing list
>>>> coL...@li... <mailto:coL...@li...>
>>>> https://lists.sourceforge.net/lists/listinfo/colinux-users
>>>>   
>>>>         
>> ------------------------------------------------------------------------
>>
>> -------------------------------------------------------------------------
>> Check out the new SourceForge.net Marketplace.
>> It's the best place to buy or sell services for
>> just about anything Open Source.
>> http://sourceforge.net/services/buy/index.php
>>
>>
>> ------------------------------------------------------------------------
>>     

Re: [coLinux-users] Vista SP1 - complete failure

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

I have no Vista running. But from an example of install I have lots of
screenshots. Perhaps you will find suggestions from there:
http://www.henrynestler.com/colinux/screenshoots/Vista-Album

The "ntconsoleflood" is also fixed in coLinux version 0.7.3 final release.

Henry

Jonathan Deitch wrote:
>  Whoops ... I spoke too soon.
> 
> The "ntconsoleflood" 0.8.0 version allows the system to boot, and run
> for a bit.
> 
> After about 5 minutes, however, the same exact circumstances as before
> occur.
> 
> Reproduced with all the same settings (including the barebones /dev/RAM
> boot).
> 
> Same symptoms with vista before after colinux shutdown - everything runs
> very slow, entire PC is unusable.
> 
> So still no solution.
> 
> - Jonathan
> 
> Jonathan Deitch wrote:
>> OK ... update ...
>>
>> After diving into the colinux-users archive, I saw a note about the
>> 0.8.0 test version for ntconsoleflood ... that actually seems to have
>> fixed this issue.
>>
>> As noted in the email string that led to that test version, the Vista
>> Business I'm running it on is a multi-core cpu; this may be another
>> example where a SMP setup is breaking the 'older' versions of colinux.
>>
>> My previous system, is a WinXP P4 2.4 .. which is a single cpu system.
>>
>> - Jonathan
>>
>> Jonathan Deitch wrote:
>>> I've tried every trick I can find on the web, and I can't get /any/
>>> version of colinux running on Vista SP1.
>>>
>>> Tried 0.7.3 (release version) and the latest 0.8.x development
>>> version.  Same exact symptom.
>>>
>>> What happens is the system boots up, and seems to be just fine.
>>>
>>> After about 60 seconds, /both /the linux /and/ Vista slow to a crawl
>>> and neither is usable.
>>>
>>> Even if you get Colinux shut down, Vista is /still/ slow as molasses
>>> and the only recovery is to reboot (and that's if Vista doesn't
>>> freeze on shutdown).
>>>
>>> Tried with multiple system images (various flavors of Linux), same thing.
>>>
>>> Tried with the bare Ramdisk boot (just initrd.gz) - same thing.
>>>
>>> Tried to run a debug on the bare ramdisk boot ... the instant the
>>> system started, the entire machine rebooted.  No bluescreen, just
>>> black screen then POST.
>>>
>>> So no way to capture debug info, either.
>>>
>>> So I'm completely stuck ... and this is a huge issue for me ... I do
>>> major development work under colinux, and they want to retire my XP
>>> box, since the entire company is migrating to Vista.
>>>
>>> Soon I won't be given a choice; I need this working before that
>>> happens ...
>>>
>>> Anyone got any ideas?
>>>
>>> Remember ... the image in this case is irrelevant - the problem
>>> occurs w/the initrd.gz RAM boot. so it's something endemic to within
>>> colinux and its kernel itself.
>>>
>>> - Jonathan
>>>  
>>> -------------------------------------------------------------------------
>>> Check out the new SourceForge.net Marketplace.
>>> It's the best place to buy or sell services for
>>> just about anything Open Source.
>>> http://sourceforge.net/services/buy/index.php
>>>  
>>> _______________________________________________
>>> coLinux-users mailing list
>>> coL...@li... <mailto:coL...@li...>
>>> https://lists.sourceforge.net/lists/listinfo/colinux-users
>>>   
> 
> ------------------------------------------------------------------------
> 
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> 
> 
> ------------------------------------------------------------------------

Re: [coLinux-users] Vista SP1 - complete failure

[Jonathan D. <tz...@sp...>]

OK ... update ...

After diving into the colinux-users archive, I saw a note about the 
0.8.0 test version for ntconsoleflood ... that actually seems to have 
fixed this issue.

As noted in the email string that led to that test version, the Vista 
Business I'm running it on is a multi-core cpu; this may be another 
example where a SMP setup is breaking the 'older' versions of colinux.

My previous system, is a WinXP P4 2.4 .. which is a single cpu system.

- Jonathan

Jonathan Deitch wrote:
> I've tried every trick I can find on the web, and I can't get /any/ 
> version of colinux running on Vista SP1.
>
> Tried 0.7.3 (release version) and the latest 0.8.x development 
> version.  Same exact symptom.
>
> What happens is the system boots up, and seems to be just fine.
>
> After about 60 seconds, /both /the linux /and/ Vista slow to a crawl 
> and neither is usable.
>
> Even if you get Colinux shut down, Vista is /still/ slow as molasses 
> and the only recovery is to reboot (and that's if Vista doesn't freeze 
> on shutdown).
>
> Tried with multiple system images (various flavors of Linux), same thing.
>
> Tried with the bare Ramdisk boot (just initrd.gz) - same thing.
>
> Tried to run a debug on the bare ramdisk boot ... the instant the 
> system started, the entire machine rebooted.  No bluescreen, just 
> black screen then POST.
>
> So no way to capture debug info, either.
>
> So I'm completely stuck ... and this is a huge issue for me ... I do 
> major development work under colinux, and they want to retire my XP 
> box, since the entire company is migrating to Vista.
>
> Soon I won't be given a choice; I need this working before that 
> happens ...
>
> Anyone got any ideas?
>
> Remember ... the image in this case is irrelevant - the problem occurs 
> w/the initrd.gz RAM boot. so it's something endemic to within colinux 
> and its kernel itself.
>
> - Jonathan
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> ------------------------------------------------------------------------
>
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>   

Re: [coLinux-users] Vista SP1 - complete failure

[Jonathan D. <tz...@sp...>]

Whoops ... I spoke too soon.

The "ntconsoleflood" 0.8.0 version allows the system to boot, and run 
for a bit.

After about 5 minutes, however, the same exact circumstances as before 
occur.

Reproduced with all the same settings (including the barebones /dev/RAM 
boot).

Same symptoms with vista before after colinux shutdown - everything runs 
very slow, entire PC is unusable.

So still no solution.

- Jonathan

Jonathan Deitch wrote:
> OK ... update ...
>
> After diving into the colinux-users archive, I saw a note about the 
> 0.8.0 test version for ntconsoleflood ... that actually seems to have 
> fixed this issue.
>
> As noted in the email string that led to that test version, the Vista 
> Business I'm running it on is a multi-core cpu; this may be another 
> example where a SMP setup is breaking the 'older' versions of colinux.
>
> My previous system, is a WinXP P4 2.4 .. which is a single cpu system.
>
> - Jonathan
>
> Jonathan Deitch wrote:
>> I've tried every trick I can find on the web, and I can't get /any/ 
>> version of colinux running on Vista SP1.
>>
>> Tried 0.7.3 (release version) and the latest 0.8.x development 
>> version.  Same exact symptom.
>>
>> What happens is the system boots up, and seems to be just fine.
>>
>> After about 60 seconds, /both /the linux /and/ Vista slow to a crawl 
>> and neither is usable.
>>
>> Even if you get Colinux shut down, Vista is /still/ slow as molasses 
>> and the only recovery is to reboot (and that's if Vista doesn't 
>> freeze on shutdown).
>>
>> Tried with multiple system images (various flavors of Linux), same thing.
>>
>> Tried with the bare Ramdisk boot (just initrd.gz) - same thing.
>>
>> Tried to run a debug on the bare ramdisk boot ... the instant the 
>> system started, the entire machine rebooted.  No bluescreen, just 
>> black screen then POST.
>>
>> So no way to capture debug info, either.
>>
>> So I'm completely stuck ... and this is a huge issue for me ... I do 
>> major development work under colinux, and they want to retire my XP 
>> box, since the entire company is migrating to Vista.
>>
>> Soon I won't be given a choice; I need this working before that 
>> happens ...
>>
>> Anyone got any ideas?
>>
>> Remember ... the image in this case is irrelevant - the problem 
>> occurs w/the initrd.gz RAM boot. so it's something endemic to within 
>> colinux and its kernel itself.
>>
>> - Jonathan
>> ------------------------------------------------------------------------
>>
>> -------------------------------------------------------------------------
>> Check out the new SourceForge.net Marketplace.
>> It's the best place to buy or sell services for
>> just about anything Open Source.
>> http://sourceforge.net/services/buy/index.php
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> coLinux-users mailing list
>> coL...@li...
>> https://lists.sourceforge.net/lists/listinfo/colinux-users
>>   

[coLinux-users] Vista SP1 - complete failure

[Jonathan D. <tz...@sp...>]

I've tried every trick I can find on the web, and I can't get /any/ 
version of colinux running on Vista SP1.

Tried 0.7.3 (release version) and the latest 0.8.x development version.  
Same exact symptom.

What happens is the system boots up, and seems to be just fine.

After about 60 seconds, /both /the linux /and/ Vista slow to a crawl and 
neither is usable.

Even if you get Colinux shut down, Vista is /still/ slow as molasses and 
the only recovery is to reboot (and that's if Vista doesn't freeze on 
shutdown).

Tried with multiple system images (various flavors of Linux), same thing.

Tried with the bare Ramdisk boot (just initrd.gz) - same thing.

Tried to run a debug on the bare ramdisk boot ... the instant the system 
started, the entire machine rebooted.  No bluescreen, just black screen 
then POST.

So no way to capture debug info, either.

So I'm completely stuck ... and this is a huge issue for me ... I do 
major development work under colinux, and they want to retire my XP box, 
since the entire company is migrating to Vista.

Soon I won't be given a choice; I need this working before that happens ...

Anyone got any ideas?

Remember ... the image in this case is irrelevant - the problem occurs 
w/the initrd.gz RAM boot. so it's something endemic to within colinux 
and its kernel itself.

- Jonathan

Re: [coLinux-users] change in slirp behavior from 0.7.1 to 0.7.3 with udp forwarded ports

[Mike F. <vap...@gm...>]

On Sun, Jun 15, 2008 at 2:16 AM, Mike Frysinger wrote:
> for some reason, the incoming packets from the tftp client as seen by
> colinux have the gateway's ip (10.0.2.2) instead of the real ip
> (192.168.0.17) ... any hints as to what's going wrong here ?
>
> taking a step back and just hitting colinux with netcat shows the same
> behavior.  connecting to a tcp forwarded port and things look good
> (the source ip is the real client, not the gateway).  connecting to a
> udp forwarded port and things look bad (the source ip is the gateway
> instead of the real client).

i noticed that there's a standalone exe called
'colinux-slirp-net-daemon.exe', so on a hunch i copied the one from
0.7.1 to 0.7.3 and when i rebooted, the network communication for UDP
forwarded ports started working again ... guess it's a bug in the
slirp daemon ?
-mike

[coLinux-users] change in slirp behavior from 0.7.1 to 0.7.3 with udp forwarded ports

[Mike F. <vap...@gm...>]

i took a working system that is running on 0.7.1 and looked at
updating to 0.7.3, but my slirp networking seems to break (sort of).
i'm using dhcp on the slirp network device.  same rootfs, so same
userspace configs between the two setups ...

here's my network settings given to colinux:
eth0=slirp,,tcp:22:22/tcp:333:22/tcp:10000:10000/udp:69:69
eth1=tuntap

and here's my network settings in userspace (/etc/network/interfaces):
auto eth0 eth1
iface eth0 inet dhcp
iface eth1 inet static
  address 10.12.12.2
  netmask 255.255.255.0

i use colinux as a tftp server.  so the setup is:
 - colinux side of slirp is 10.0.2.15
 - windows side of slirp is 10.0.2.{2,3} (i guess dns/gateway have diff IPs?)
 - windows public ip is 192.168.0.35
 - running tftp client on 192.168.0.17 ("G5")

on the working system (0.7.1), i can see this communication when
running tcpdump from inside colinux:
01:34:47.410000 IP G5.60808 > 10.0.2.15.tftp:  15 RRQ "moo" netascii
01:34:47.413067 IP 10.0.2.15.32797 > 10.0.2.3.domain:  59766+ PTR?
15.2.0.10.in-addr.arpa. (40)
01:34:47.447703 IP 10.0.2.15.32798 > G5.60808: UDP, length 9

on the failing system (0.7.3), i see this:
01:44:45.645802 IP 10.0.2.2.33431 > 10.0.2.15.tftp:  15 RRQ "moo" netascii
01:44:46.105809 IP 10.0.2.15.32769 > 10.0.2.2.33431: UDP, length 9
01:44:45.675802 IP 10.0.2.2 > 10.0.2.15: ICMP 10.0.2.2 udp port 33431
unreachable, length 45

for some reason, the incoming packets from the tftp client as seen by
colinux have the gateway's ip (10.0.2.2) instead of the real ip
(192.168.0.17) ... any hints as to what's going wrong here ?

taking a step back and just hitting colinux with netcat shows the same
behavior.  connecting to a tcp forwarded port and things look good
(the source ip is the real client, not the gateway).  connecting to a
udp forwarded port and things look bad (the source ip is the gateway
instead of the real client).
-mike

Re: [coLinux-users] Strange SLIRP behaviour

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

Marek Jawurek wrote:
> I had coLinux successfully set up at home using SLIRP but at a different
> site I am having problems:
> 
> I can DNS out but my TCP SYN packets are reseted and do not leave my
> machiene.

Remember: Slirp only supports TCP connections and UDP packets. No other
protocols, no IMCP packets.

> In my coLinux configuration file I have set up eth0=slirp
> In my Linux system I obtained network settings via dhcp and verified
> them against the static configuration in the manual. Then I try to wget
> a website via: wget http://heise.de
> 
> With wireshark I analysed the packets going out on eth0:
> There I first have the DNS request and reply going from my 10.0.2.15
> address to 10.0.2.3 and back.
> Then the TCP SYN packets go out to the PROXY set up for HTTP ( 10.0.2.15
> to the PROXY address) but an RST comes back ( PROXY -> 10.0.2.15).

Proxy setup? Perhaps Slirp does handle proxy wrong? Works it without proxy?

> On the windows side I have wireshark running on my Physical Ethernet
> Adapter. There the DNS request goes out and comes back ( WindowsIP ->
> DNS) and ( DNS -> WindowsIP).
> But then there is no TCP Syn Packet leaving my Windows Host.
> 
> The Windows Firewall is disabled globally. I tried to run the colinux debugger but it does not show the actual packets
> sent/received just memory addresses. Is there a way to see what colinux receives and resends in the debugger ?

Run TCPdump or process-Explorer from http://www.sysinternals.com
(forwarded to MS) to see what packets the slirp daemon on windows send
and received.

-- 
Henry N.

[coLinux-users] Strange SLIRP behaviour

[Marek J. <Mar...@ie...>]

Hi everyone,

I had coLinux successfully set up at home using SLIRP but at a different
site I am having problems:

I can DNS out but my TCP SYN packets are reseted and do not leave my
machiene.


In my coLinux configuration file I have set up eth0=slirp
In my Linux system I obtained network settings via dhcp and verified
them against the static configuration in the manual. Then I try to wget
a website via: wget http://heise.de

With wireshark I analysed the packets going out on eth0:
There I first have the DNS request and reply going from my 10.0.2.15
address to 10.0.2.3 and back.
Then the TCP SYN packets go out to the PROXY set up for HTTP ( 10.0.2.15
to the PROXY address) but an RST comes back ( PROXY -> 10.0.2.15).

On the windows side I have wireshark running on my Physical Ethernet
Adapter. There the DNS request goes out and comes back ( WindowsIP ->
DNS) and ( DNS -> WindowsIP).
But then there is no TCP Syn Packet leaving my Windows Host.

The Windows Firewall is disabled globally. I tried to run the colinux debugger but it does not show the actual packets
sent/received just memory addresses. Is there a way to see what colinux receives and resends in the debugger ?


Any ideas ?

Marek



-- 
Marek Jawurek,
Fraunhofer IESE, Security and Safety
Fraunhofer-Platz 1, 67663 Kaiserslautern, Germany
Phone/Fax: +49 631 6800-2132/-92132
mailto:mar...@ie...
http://www.iese.fraunhofer.de 

Re: [coLinux-users] Colinux on a closed network

[Josep M. A. S. <ja...@pa...>]

Ok. here it goes.
First, i'm taking of this networking method:
http://colinux.wikia.com/wiki/Network#TAP
(Scroll down until you see "TAP with Windows Software Bridge")

colinux installer should have already installed the tap driver, and a network
inteface named "TAP Win32" or something like that should appear.

Usually, this would give a closed network between colinux and XP, on a defined
subnet. The trick here is to bridge this adapter with the physical one, a
feature that windows XP (Pro?) has.

So, if you are on the window where you see all the network adapters, you can
select both network cards (the physical one, and the TAP one), rightclick, and
a "Make bridge" option should appear.

Once bridged, Windows will show a third adapter, which from now on, is the only
one that Windows (software) see. In this third adapter, you have to configure
the IP of the windows machine, on the physical subnet. In your case,
192.168.10.100.

Then, colinux should be configured with an IP on that subnet too. 192.168.10.200
looks ok.

The key point here is that bridging is like putting a software hub between the
physical adapter and the tap driver.



-- 
 _ _  /~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-\
 o o  | Josep Ma [JAZ]                 |
  *   | ICQ UIN: 7014661               |
 `-´  | Messenger: ja...@ho... |
      \-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~/


Missatge citat per Dave Coventry <dc...@da...>:

> Hi Josep Maria,
>
> I have installed Colinux on the box, but am unable to get Tuntap working.
>
> How is the bridge configured?
>
> Remember I an on a static IP. The Windows box has 192.168.10.100, the
> colinux ifconfig is on 192.168.10.200. How do I configure the tuntap
> adaptor? And the Bridge?
>
> Any advice?

Re: [coLinux-users] Colinux on a closed network

[Josep M. A. S. <ja...@pa...>]

Yes, it is possible (That was my main use of colinux, until i changed my job).

This is how i did it:

Installed colinux, (in that case, with a debian image with samba and controlled
via webmin), set it with TunTAP with an IP on the same subnet, made a bridge
with windows between the hardware ethernet and the TunTAP device, and
everything worked perfectly (well, i had a problem writing to windows
partitions, but that was solved in the 7.x versions)


That is one option. The other is using the pcap-bridge. Supposedly, the TunTAP
way should be better, but i didn't do any measurements on that.

Don't try to do it with slirp, except if you're adventurous. You would have to
disable the service in windows, without closing the ports themselves, and open
the appropiate ports in the slirp configuration.

-- 
 _ _  /~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-\
 o o  | Josep Ma [JAZ]                 |
  *   | ICQ UIN: 7014661               |
 `-´  | Messenger: ja...@ho... |
      \-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~/

[coLinux-users] Colinux on a closed network

[Dave C. <dc...@da...>]

Hi,

We have a number of XP machines on a closed network without DHCP (all
machines have a static IP).

All of the machines should connect to a 'Control' computer, but,
because of artificial limitations imposed by Microsoft, the control
computer is unable to handle all of the connections.

(The setup is a ship simulation lab with some 24 computers connecting
to the Control machine and simulating 8 ships).

The 24 computers would update the Control regarding their position and
course, etc.

However, because this is not possible in XP, we have added a linux box
to the network which is purely there to store files to be read and
written to by all 24 computers and also the Control.

I want to remove the Linux box and place a colinux instance on the
Control machine.

To do this, I need Colinux to offer a Samba share to the network to be
read and written to as if it were a seperate machine.

Is this possible?

How would it be done? With slirp, nat or bridged?

The network has static IPs 192.168.10.1-25, so the Colinux machine
would need to be 192.168.10.26

[coLinux-users] [ANNOUNCE] Cooperative Linux version 0.7.3 released

[Henry N. <Hen...@Ar...>]

Cooperative Linux version 0.7.3 released now.

This is an upgrade with new kernel 2.6.22.18 and lots of fixed bugs.

There are no changes between 0.7.3-rc5 and this release version. We
released the binary from builddate 24-May-2008. Users of this snapshot
don't need an update.

Download:  http://sourceforge.net/projects/colinux/files
Notes:
http://sourceforge.net/project/shownotes.php?release_id=385643&group_id=98788
Changelog: http://www.colinux.org/snapshots/stable-ChangeLog
Wiki:      http://colinux.wikia.com/

NEWS of Version 0.7.3
Bugfixes:
* Check ELF header before accessing kernel vmlinux (fix exception).
* Fix problems with memory hole from shared video cards and the
  error message "PFN to high".
* Bugfix host freeze after "Using IPI Shortcut mode" and other randomly
  crashes at mounting the root file system with types ext2 or ext3.

Daemon:
* Add build date to exe file properties.
* View build timestamp of ntkernel driver with --status-driver.
* Bug #1861876: Random created MAC stored in Registry to have same on
  every start. [HKCU\Software\coLinux]
* Bugfix: Image files >=4GB fails with size error on parameter "-v 3".
* Workarround for unresponsive key inputs on Vista flooded nt-console.
  Linux driver will sleep now, if message queues have to many entries
  and user task is busy. Network daemons drivers changed also into
  this mode.
* Incrase NT console screen to most as can without scrollbars at
  startup.

Kernel:
* Kernel has been updated to 2.6.22.18
* Kernel config added: More Netfilters (NF_NAT and more), Network
  Security Marking, RAID and LVM as module (MD), extended attributes for
  ext2/ext3/reiser/jfs/xfs, Quota, Kernel automounter support, eCrypt
  filesystem, and more...
* Removed: KALLSYMS_ALL (Debugging symbols)
* SELINUX support. To enable, set selinux=1 in colinux.conf
* Fix for splice local root exploit is included, details on
  http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.22.18
* Feature Requests #1421120: Fixup "vim fsync" error on cofs.
* Bugfix get_size for double opened block devices.
* Fix BSOD on "stty rows N" where n>25. Disable resize. (Paolo Minazzi)
* Bugfix: CR3 wrong converted for register dumps inside page fault
  handler.

Installer:
* Update image ArchLinux-2007.08-2
* Text '* Notes' sometimes was only shown as '*', adjust field sizes
* Feature Requests #1898468: expose install folder as variable %COLINUX%

Buildsystem:
* New option --errfile use different file for stdout and stderr.

-- 
Henry N.

Re: [coLinux-users] INIT: Id "C0" respawning too fast: disabled for 5 minutes

[Asif I. <a....@ie...>]

Thank you Paolo. It was the following line in /etc/inittab that was
being respawned continuously:

C0::respawn:/usr/bin/X11/startwindowsterminalsession

This in turn was calling /etc/sbin/launcher.pl.
Commented it and hope that the problem is solved. This X stuff is not
so simple to get rid of completely.

Asif

On Thu, Jun 5, 2008 at 5:31 PM, Paolo Minazzi <pao...@gm...> wrote:
> This happens because the init script continues to run a program in
> respawing mode, that is run it continuosly (see /etc/inittab). For
> some reason, this program terminates too quickly, so the init process
> warns about this.
> This is not related to colinux, you should have the same problem under
> native linux.
>
> Bye,
> Paolo
>
> On Thu, Jun 5, 2008 at 5:24 PM, Asif Iqbal <a....@ie...> wrote:
>> Hello everybody
>>
>> After I switched to a console only usage of colinux using putty, I am
>> facing this problem. The above-mentioned message appears sporadically
>> on the colinux console and putty remains locked for 5 minutes or so.
>> How can I solve it.
>>
>> It also complains something about /usr/sbin/launcher.pl. Is there a
>> way I can disable this launcher stuff altogether? I cannot find where
>> it is referred to in the startup scripts.
>>
>> Asif
>>
>> -------------------------------------------------------------------------
>> Check out the new SourceForge.net Marketplace.
>> It's the best place to buy or sell services for
>> just about anything Open Source.
>> http://sourceforge.net/services/buy/index.php
>> _______________________________________________
>> coLinux-users mailing list
>> coL...@li...
>> https://lists.sourceforge.net/lists/listinfo/colinux-users
>>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>

Re: [coLinux-users] INIT: Id "C0" respawning too fast: disabled for 5 minutes

[Paolo M. <pao...@gm...>]

This happens because the init script continues to run a program in
respawing mode, that is run it continuosly (see /etc/inittab). For
some reason, this program terminates too quickly, so the init process
warns about this.
This is not related to colinux, you should have the same problem under
native linux.

Bye,
Paolo

On Thu, Jun 5, 2008 at 5:24 PM, Asif Iqbal <a....@ie...> wrote:
> Hello everybody
>
> After I switched to a console only usage of colinux using putty, I am
> facing this problem. The above-mentioned message appears sporadically
> on the colinux console and putty remains locked for 5 minutes or so.
> How can I solve it.
>
> It also complains something about /usr/sbin/launcher.pl. Is there a
> way I can disable this launcher stuff altogether? I cannot find where
> it is referred to in the startup scripts.
>
> Asif
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>

[coLinux-users] INIT: Id "C0" respawning too fast: disabled for 5 minutes

[Asif I. <a....@ie...>]

Hello everybody

After I switched to a console only usage of colinux using putty, I am
facing this problem. The above-mentioned message appears sporadically
on the colinux console and putty remains locked for 5 minutes or so.
How can I solve it.

It also complains something about /usr/sbin/launcher.pl. Is there a
way I can disable this launcher stuff altogether? I cannot find where
it is referred to in the startup scripts.

Asif