Re: [coLinux-users] CoLinux does not start

[Jurgis <ju...@em...>]

Henry,

Thank you for the provided information!

I have run following commands
 > colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/ram0 -v 1
 > colinux-debug-daemon.exe -d -p -s prints=31,misc=31 -f debug.xml
The results (2  screenshots and debug.xml file) can be found here:
http://jurgis.emails.lv/colinux/01/

I'm still using devel-coLinux-20090319.exe

When running colinux-daemon.exe it does not end normally, I have to click
on the cross at the right upper corner to close it.

Regards,
Jurgis

Henry Nestler wrote:
> Hello Jurgis,
>
> Jurgis wrote:
>> I can not start coLinux, I have tried all possible I could find:
>> - coLinux 0.7.3
>> - andLinux
>> - Ulteo Open Virtual Desktop
>> They all use coLinux and it does not start
>>
>> The last try was - I downloaded the latest snapshot and
>> run this command
>>   >  colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/ram0 -v 1
>>
>> The result is allways the same.
>> I have never gone past this line: PID hash table entries: 2048 (order:
>> 11, 8192 bytes)
>>
>> -------------------------------------------------------------------
>> Cooperative Linux Daemon, 0.8.0
>> Daemon compiled on Thu Mar 19 19:47:12 2009
>>
>> using 'vmlinux' as kernel image
>> using 'initrd.gz' as initrd image
>> mapping cofs31 to \??\D:\programs\coLinux
>> kernel boot parameters: 'root=/dev/ram0'
>> PID: 1820
>> colinux: launching console
>> colinux: booting
>> Linux version 2.6.22.18-co-0.8.0 (hn@hn-dt) (gcc version 4.2.1 (SUSE
>> Linux)) #1 PREEMPT Thu Mar 19 19:45:43 UTC 2009
>> 512MB LOWMEM available.
>> initrd enabled: start: 0xdff9a000  size: 0x00065881
>> [...]
>> Initializing CPU#0
>> Setting proxy interrupt vectors
>> PID hash table entries: 2048 (order: 11, 8192 bytes)
>
> The next line should be the init message from console:
> "Console: colour CoCON 80x25"
>
>> I have Windows XP SP3
>> Intel Core Duo T2250 @ 1.73Ghz
>> 2GB RAM
>>
>> Is there anything more I can do to help locating the problem?
>> I also run
>>   >  colinux-debug-daemon.exe -d -f trace.txt
>> and attached the trace file.
>
> With "colinux-debug-daemon.exe -d -p -f trace.xml" the output would 
> read better.
> You can convert it with "colinux-debug-daemon.exe -p <trace.txt 
> >trace.xml"
> But it contains non interestings as we can see from colinux-daemon 
> output:
>   using 'vmlinux' as kernel image
>   using 'initrd.gz' as initrd image
>   mapping cofs31 to \??\D:\programs\coLinux
>   kernel boot parameters: 'root=/dev/ram0'
>   colinux: launching console
>
> Please try a higher debug level:
>   colinux-debug-daemon.exe -d -p -s prints=31,misc=31 -f debug.xml
> More about debugging finds in file "debugging.txt" in your 
> installation, or online here:
> http://colinux.svn.sourceforge.net/svnroot/colinux/branches/devel/doc/debugging 
>
>
> For your problem I can not see a solution currently.
>
> How ends the colinux-daemon.exe? Is it back to prompt? Or hangs it?
>
> Exist the file "colinux-console-fltk.exe"?
> Is it launched? Can you see the "Cooperative Linux Console" Window, 
> like this:
> http://colinux.wikia.com/wiki/Image:CoLinux-fltk-console-0.7.3.png
> If not, can you execute colinux-console-fltk.exe manualy?
>