colinux-users — coLinux users mailing list

Re: [coLinux-users] Is it possible to install setup a Linux distribution from CD ROM?

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

Am 22.04.2009 21:33, schrieb Frank Church:
> Is it possible to install setup a Linux distribution from CD ROM?
>
> I have an Ubuntu 7.10 coLinux setup, and I want to create new Ubuntu
> 8.04 and 8.10 from ISO images.
>
> Is it possible to mount the CDROMs and install them, or use some kind
> of debootstrap system which
> can install from a local FTP created from loop mounted ISO?
>
> What I mean is if the coLinux cannot install an image from the CDROM,
> is it possible to extract
> debootstrap from the ISO image, and use it to install the rest of the
> files from the ISO image mounted
> as an FTP location?

Here is an interesing stepguide for CentOS bootstrapping:
http://blog.gbraad.nl/2009/03/manually-installing-centos-52-on.html

In wiki http://colinux.wikia.com/wiki/UbuntuBase exist a very old 
script. Perhaps it is very outdated?

Newer coLinux version 0.7.4-rc2 has an option for cdrom, like this:
    scsi1=cdrom,C:\image.iso
or
    scsi1=cdrom,\Device\Cdrom0

Please read also comments from Bill about Fedora here: 
http://tinyurl.com/cnovnz
And my answers: http://tinyurl.com/csw9nr, http://tinyurl.com/cr9ene

-- 
Henry N.

[coLinux-users] Is it possible to install setup a Linux distribution from CD ROM?

[Frank C. <vfc...@go...>]

Is it possible to install setup a Linux distribution from CD ROM?

I have an Ubuntu 7.10 coLinux setup, and I want to create new Ubuntu
8.04 and 8.10 from ISO images.

Is it possible to mount the CDROMs and install them, or use some kind
of debootstrap system which
can install from a local FTP created from loop mounted ISO?

What I mean is if the coLinux cannot install an image from the CDROM,
is it possible to extract
debootstrap from the ISO image, and use it to install the rest of the
files from the ISO image mounted
as an FTP location?

/vfclists

[coLinux-users] How do I start with coLinux.

[Javier O. C. <joc...@ho...>]

Hello:

        I'm trying to start with coLinux. What things I must count for start?

        How to setting coLinux? Any information is good.

        Thank.

Javier O. Chércoles
  ----- Original Message ----- 
  From: Henry Nestler 
  To: ColdShine 
  Cc: col...@li... 
  Sent: Monday, April 20, 2009 3:22 PM
  Subject: Re: [coLinux-users] Is there a way to set the tile of the console?


  ColdShine wrote:
  > Henry Nestler wrote:
  >> Frank Church wrote:
  >>> Is there a way to set the title of the console in the colinux.conf
  >>> file i the command options.
  >> no, you can't. The title line will be update from console depends on the
  >> current state (attached or detached).
  >
  > I'd like that to be implemented, too. I think it could be set using a
  > special sequence for PS1, like you do in Xterm. I think
  > colinux-console already has a parser for the escape sequences, right?

  coLinux use the kernel "struct consw" in same way all other video 
  drivers used it (frame less graphic cards). There is no option for 
  title, as I known. Xterm uses other ways and more subfunctions.

  To add a title to coLinux console, needs to change directly in the user 
  land console programs on host side.

  -- 
  Henry N.

  ------------------------------------------------------------------------------
  Stay on top of everything new and different, both inside and 
  around Java (TM) technology - register by April 22, and save
  $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
  300 plus technical and hands-on sessions. Register today. 
  Use priority code J9JMT32. http://p.sf.net/sfu/p
  _______________________________________________
  coLinux-users mailing list
  coL...@li...
  https://lists.sourceforge.net/lists/listinfo/colinux-users

Re: [coLinux-users] Is there a way to set the tile of the console?

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

ColdShine wrote:
> Henry Nestler wrote:
>> Frank Church wrote:
>>> Is there a way to set the title of the console in the colinux.conf
>>> file i the command options.
>> no, you can't. The title line will be update from console depends on the
>> current state (attached or detached).
>
> I'd like that to be implemented, too. I think it could be set using a
> special sequence for PS1, like you do in Xterm. I think
> colinux-console already has a parser for the escape sequences, right?

coLinux use the kernel "struct consw" in same way all other video 
drivers used it (frame less graphic cards). There is no option for 
title, as I known. Xterm uses other ways and more subfunctions.

To add a title to coLinux console, needs to change directly in the user 
land console programs on host side.

-- 
Henry N.

Re: [coLinux-users] Is there a way to set the tile of the console?

[ColdShine <col...@us...>]

2009/4/19 Henry Nestler <hen...@ar...>:
> Frank Church wrote:
>> Is there a way to set the title of the console in the colinux.conf
>> file i the command options.
>
> no, you can't. The title line will be update from console depends on the
> current state (attached or detached).

I'd like that to be implemented, too. I think it could be set using a
special sequence for PS1, like you do in Xterm. I think
colinux-console already has a parser for the escape sequences, right?
I'll see if I can figure how to implement that. And I also wish I had
time to help with the patches for a newer kernel :(

--
CS

Re: [coLinux-users] Is there a way to set the tile of the console?

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

Hello Frank,

Frank Church wrote:
> Is there a way to set the title of the console in the colinux.conf
> file i the command options.

no, you can't. The title line will be update from console depends on the 
current state (attached or detached).

-- 
Henry N.

[coLinux-users] Is there a way to set the tile of the console?

[Frank C. <vfc...@go...>]

Is there a way to set the title of the console in the colinux.conf
file i the command options.

I have looked and can't find any thing like that.

/vfclists

[coLinux-users] [ANNOUNCE] Cooperative Linux 0.7.4-rc2 pre-release

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

Hello,

Next release candidate 0.7.4-rc2 as build 20090415 is available from
snapshot page under "stable branch".
http://www.colinux.org/snapshots/

This is a pure copy from currently branch devel. Users of devel 0.8.0
will not find any differences as only the versions number.

Notes about all changes you can read from file NEWS and Changelog there.

In previous candidate was detected a FPU Floating Point error between 
tasks switches (Related Bugs #2748015, #2756909).
Please update modules manualy, because initrd can't do this automatically:
"tar xzf vmlinux-modules.tar.gz -C /"
This is necessary especialy for using Raid5 and Raid6.

-- 
Henry N.

Re: [coLinux-users] coLinux and APM events?

[Jason <ja...@co...>]

Paolo Minazzi wrote:
> Colinux does not have support for APM.
>   
That's what I've been coming to the conclusion of. It'd be great if
coLinux could somehow see the event (does Windows even send or have a
trappable event that processes can get notified that the system is
sleeping/hibernating?) and pass it on to the kernel as an APM or ACPI event.

So this answers my question, and the only way to deal with my dhcpcd not
getting an IP (either because of the way it keeps track of time while
'sleeping', or because the bridge doesn't come up fast enough during the
wake up) is going to be to do some clock skew monitoring.

Thanks!

Jason

Re: [coLinux-users] coLinux and APM events?

[Nambi J U <ju...@gm...>]

Hi,

I have been using Colinux and always put my laptop on stand-by and I have
not faced any issue with Colinux.

Regards,
Nambi


On Mon, Mar 30, 2009 at 11:42 AM, Paolo Minazzi <pao...@gm...>wrote:

> Colinux does not have support for APM.
> But windows (that is the host system) has support for it.
> Colinux is seen as a (more or less) a normal application by windows.
> So APM works OK. I repeat, colinux does not support APM.
> APM is managed from windows!
> I don't know an elegant solution for your problem.
> I don't think there is it.
> Bye,
> Paolo
>
> On Sun, Mar 29, 2009 at 10:30 PM, Jason <ja...@co...> wrote:
> > Jason wrote:
> >> Does coLinux pass along any kind of APM events during
> >> sleep/hibernates/wakups from Windows XP?
> >>
> >
> > I've had a few people write me direct to say they don't know the answer,
> > but actual sleep/recover works fine.
> >
> > So, I'll expound a bit on my use case. My system lives on a network that
> > uses DHCP. Sometimes it moves between networks actually between
> > hibernate/wake up.
> >
> > The dhcpcd does not seem keep track of it's lease time properly during
> > the sleep cycle (or maybe coLinux just comes up too fast before the
> > network is properly re-established, so dhcpcd never sees a reply from a
> > reachable dhcp server... either way, same effect).
> >
> > Either way, I want to be able to catch the 'wakeup' signal so I can work
> > on getting an event to occur that gets dhcpcd to re-negotiate it's lease
> > properly.
> >
> > I could brute force it by checking for large skews in the clock between
> > runs of a script, however if APM support exists, it would be a much more
> > elegant solution.
> >
> > Thanks
> >
> > Jason
> >
> >
> ------------------------------------------------------------------------------
> > _______________________________________________
> > coLinux-users mailing list
> > coL...@li...
> > https://lists.sourceforge.net/lists/listinfo/colinux-users
> >
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>

Re: [coLinux-users] coLinux and APM events?

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

Colinux does not have support for APM.
But windows (that is the host system) has support for it.
Colinux is seen as a (more or less) a normal application by windows.
So APM works OK. I repeat, colinux does not support APM.
APM is managed from windows!
I don't know an elegant solution for your problem.
I don't think there is it.
Bye,
Paolo

On Sun, Mar 29, 2009 at 10:30 PM, Jason <ja...@co...> wrote:
> Jason wrote:
>> Does coLinux pass along any kind of APM events during
>> sleep/hibernates/wakups from Windows XP?
>>
>
> I've had a few people write me direct to say they don't know the answer,
> but actual sleep/recover works fine.
>
> So, I'll expound a bit on my use case. My system lives on a network that
> uses DHCP. Sometimes it moves between networks actually between
> hibernate/wake up.
>
> The dhcpcd does not seem keep track of it's lease time properly during
> the sleep cycle (or maybe coLinux just comes up too fast before the
> network is properly re-established, so dhcpcd never sees a reply from a
> reachable dhcp server... either way, same effect).
>
> Either way, I want to be able to catch the 'wakeup' signal so I can work
> on getting an event to occur that gets dhcpcd to re-negotiate it's lease
> properly.
>
> I could brute force it by checking for large skews in the clock between
> runs of a script, however if APM support exists, it would be a much more
> elegant solution.
>
> Thanks
>
> Jason
>
> ------------------------------------------------------------------------------
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>

[coLinux-users] [ANNOUNCE] Cooperative Linux 0.7.4-rc1 pre-release

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

Hello,

Next release candidate 0.7.4-rc1 is available from
snapshot page under "stable branch".
http://www.colinux.org/snapshots/

This is a pure copy from currently branch devel. Users of devel 0.8.0 
will not find any differences as only the versions number.

Notes about all changes you can read from file NEWS and Changelog there.

-- 
Henry N.

Re: [coLinux-users] coLinux and APM events?

[Jason <ja...@co...>]

Jason wrote:
> Does coLinux pass along any kind of APM events during
> sleep/hibernates/wakups from Windows XP?
>   

I've had a few people write me direct to say they don't know the answer,
but actual sleep/recover works fine.

So, I'll expound a bit on my use case. My system lives on a network that
uses DHCP. Sometimes it moves between networks actually between
hibernate/wake up.

The dhcpcd does not seem keep track of it's lease time properly during
the sleep cycle (or maybe coLinux just comes up too fast before the
network is properly re-established, so dhcpcd never sees a reply from a
reachable dhcp server... either way, same effect).

Either way, I want to be able to catch the 'wakeup' signal so I can work
on getting an event to occur that gets dhcpcd to re-negotiate it's lease
properly.

I could brute force it by checking for large skews in the clock between
runs of a script, however if APM support exists, it would be a much more
elegant solution.

Thanks

Jason

[coLinux-users] coLinux and APM events?

[Jason <ja...@co...>]

I'm not holding out much hope now after my research bout, but thought
I'd ask the question...

Does coLinux pass along any kind of APM events during
sleep/hibernates/wakups from Windows XP?

I found a few threads from 2005 saying no, but it's 2009 now, so thought
I'd ask again. Searching in the Wiki didn't yield any results.

Thanks

Jason

Re: [coLinux-users] CoLinux does not start

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

Hi Paolo,

Here are DebugView results:
http://jurgis.emails.lv/colinux/03/DebugView.txt

Jurgis

Paolo Minazzi wrote:
> Hi Jurgis,
> I have a small win32 driver that counts interrupts.
> It does not change anything and it is removed cleanly after the end.
> If you run it, we can have some more information.
> Let me know if you are interested to try it.
> Bye,
> Paolo
>
>
>
> On Sun, Mar 22, 2009 at 11:15 PM, Henry Nestler <hen...@ar...> wrote:
>   
>> Am 22.03.2009 08:16, schrieb Jurgis:
>>     
>>> Henry,
>>>
>>> Thank you for the provided information!
>>>
>>> I have run following commands and attached screenshots and debug.xml file.
>>>   >  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
>>>
>>> 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.
>>>       
>> Sorry, the debug have not more helpfully informations.
>>
>> I think, it's a problem with timer. The next boot step after
>> "pidhash_init" (your last line) will setup the timer source for coLinux
>> kernel. That is very hard to debug. I feel this PC has one of the
>> special timer chip, that we don't handle right.
>>
>> Please view the older mail:
>> http://www.nabble.com/forum/ViewPost.jtp?post=18019511&framed=y
>>
>> Boot with a Live CD, for example Knoppix or Gparted and watch for such
>> kernel boot message: "MP-BIOS bug: 8254 timer not connected to IO-APIC"
>>
>> --
>> Henry N.
>>
>> ------------------------------------------------------------------------------
>> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
>> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
>> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
>> software that enables intelligent coding and step-through debugging.
>> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
>> _______________________________________________
>> coLinux-users mailing list
>> coL...@li...
>> https://lists.sourceforge.net/lists/listinfo/colinux-users
>>
>>     

Re: [coLinux-users] CoLinux does not start

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

Henry,

Thank you for such a thorough descriptions of all the steps!

Here are the results:
http://jurgis.emails.lv/colinux/02/

Jurgis

Henry Nestler wrote:
> Am 22.03.2009 23:15, schrieb Henry Nestler:
>> Am 22.03.2009 08:16, schrieb Jurgis:
>>> Henry,
>>>
>>> Thank you for the provided information!
>>>
>>> I have run following commands and attached screenshots and debug.xml 
>>> file.
>>>    >   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
>>>
>>> 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.
>>
>> Sorry, the debug have not more helpfully informations.
>>
>> I think, it's a problem with timer. The next boot step after
>> "pidhash_init" (your last line) will setup the timer source for coLinux
>> kernel. That is very hard to debug. I feel this PC has one of the
>> special timer chip, that we don't handle right.
>>
>> Please view the older mail:
>> http://www.nabble.com/forum/ViewPost.jtp?post=18019511&framed=y
>>
>> Boot with a Live CD, for example Knoppix or Gparted and watch for such
>> kernel boot message: "MP-BIOS bug: 8254 timer not connected to IO-APIC"
>>
>
> It would be nice, if you can send me kernel boot messages from such 
> live cd.
> Run "dmesg >/mesg.txt" to store the messages in file, and please the 
> list of interrupts under this native Linux ("cat /proc/interrupts 
> >interrupts.txt")
>
> And under Windows please send me the list of interrupts. You will find 
> this by running
> "C:\Program files\Shared files\Microsoft Shared\MsInfo\msinfo32.exe" 
> and selecting Hardwareresource IRQs. The Directory can be localized in 
> your language.
>
> To solve the problem we need to locatisate the stopping function 
> inside coLinux kernel. But this needs many more developing time and 
> special builds with more outputs between the steps to find the 
> stopper. I don't know how we can do this over a mail distance. That 
> would cost time for your testing and my coding.
>

Re: [coLinux-users] CoLinux does not start

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

Hi Jurgis,
I have a small win32 driver that counts interrupts.
It does not change anything and it is removed cleanly after the end.
If you run it, we can have some more information.
Let me know if you are interested to try it.
Bye,
Paolo



On Sun, Mar 22, 2009 at 11:15 PM, Henry Nestler <hen...@ar...> wrote:
> Am 22.03.2009 08:16, schrieb Jurgis:
>> Henry,
>>
>> Thank you for the provided information!
>>
>> I have run following commands and attached screenshots and debug.xml file.
>>   >  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
>>
>> 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.
>
> Sorry, the debug have not more helpfully informations.
>
> I think, it's a problem with timer. The next boot step after
> "pidhash_init" (your last line) will setup the timer source for coLinux
> kernel. That is very hard to debug. I feel this PC has one of the
> special timer chip, that we don't handle right.
>
> Please view the older mail:
> http://www.nabble.com/forum/ViewPost.jtp?post=18019511&framed=y
>
> Boot with a Live CD, for example Knoppix or Gparted and watch for such
> kernel boot message: "MP-BIOS bug: 8254 timer not connected to IO-APIC"
>
> --
> Henry N.
>
> ------------------------------------------------------------------------------
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>

Re: [coLinux-users] CoLinux does not start

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

Am 22.03.2009 08:16, schrieb Jurgis:
> Henry,
>
> Thank you for the provided information!
>
> I have run following commands and attached screenshots and debug.xml file.
>   >  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
>
> 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.

Sorry, the debug have not more helpfully informations.

I think, it's a problem with timer. The next boot step after 
"pidhash_init" (your last line) will setup the timer source for coLinux 
kernel. That is very hard to debug. I feel this PC has one of the 
special timer chip, that we don't handle right.

Please view the older mail:
http://www.nabble.com/forum/ViewPost.jtp?post=18019511&framed=y

Boot with a Live CD, for example Knoppix or Gparted and watch for such 
kernel boot message: "MP-BIOS bug: 8254 timer not connected to IO-APIC"

-- 
Henry N.

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

Re: [coLinux-users] CoLinux does not start

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

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?

-- 
Henry N.

[coLinux-users] CoLinux does not start

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

Hi!

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
Entering add_active_range(0, 0, 131072) 0 entries of 256 used
Zone PFN ranges:
  DMA             0 ->        0
  Normal          0 ->   131072
early_node_map[1] active PFN ranges
    0:        0 ->   131072
On node 0 totalpages: 131072
  DMA zone: 0 pages used for memmap
  Normal zone: 1024 pages used for memmap
  Normal zone: 130048 pages, LIFO batch:31
Built 1 zonelists.  Total pages: 130048
Kernel command line: root=/dev/ram0
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
Setting proxy interrupt vectors
PID hash table entries: 2048 (order: 11, 8192 bytes)
--------------------------------------------------------

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.

Any help would be appreciated.
Jurgis

[coLinux-users] Help with network

[Vlad S. <vla...@gm...>]

after installing and running coloinux i tried to setup the network.
I used the instructions on 
http://colinux.wikia.com/wiki/Network#TAP_-_Private_Connection_with_Hosting_OS
On the windows side i setup Local Area Connection 2 (TAP-Win32 Adapter 
V8 (coLinux))

Connection-specific DNS Suffix  . :
        IP Address. . . . . . . . . . . . : 192.168.37.10
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . :    .   .   .
in the colinux side i edited interfaces and added 

auto lo eth0

iface eth0 inet static
    address 192.168.37.20
    network 192.168.37.0
    netmask 255.255.255.0
    broadcast 192.168.37.255

auto eth1
iface eth1 inet dhcp

i restarted colinux and i can't even ping. I get network unreachable 
when  i ping 192.168.37.10 from colinux
and timeout when i ping 192.168.37.20 from windows

Re: [coLinux-users] Can't start colinux

[Shai V. <sva...@gm...>]

Hi Vlad,

I reinstalled coLinux version 0.7.3 with the same Ubuntu file system
you've been using but for me, it seems to be working fine.  After
close examination of the output from my machine with the output from
your machine I think that a plausible explanation is a corrupted image
file.  This first happens here in your log:

> VFS: Mounted root (ext2 filesystem).
> end_request: I/O error, dev cobd0, sector 16


My suggestion is that you download the Ubuntu image again and expand
it.  To expand the image file, I've used Cygwin with the command:
$ bunzip2.exe  Ubuntu-6.06.1.ext3.1gb.bz2

Good luck,

- Shai

On Tue, Mar 3, 2009 at 10:02 AM, Vlad Stanimir <vla...@gm...> wrote:
> Shai Vaingast wrote:
>
> In the file example.conf, typically in directory c:\Program
> Files\coLinux, the line:
> cobd0="c:\coLinux\root_fs"
> Should be edited to point to an actual Linux filesystem.
> Assuming you did modify this to point to the right file system, it
> could be that for some reason the file is missing, or already open by
> another application.
> - Shai
> On Tue, Mar 3, 2009 at 9:47 AM, Vlad Stanimir <vla...@gm...> wrote:
>
>
> i tried to start colinux using colinux-daemon.exe @example.conf but i
> get the this error:
> No filesystem could mount root, tried:  reiserfs ext3 ext2 iso9660
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(117,0)
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
> -Strategies to boost innovation and cut costs with open source participation
> -Receive a $600 discount off the registration fee with the source code: SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>
>
>
>
> i am using windows xp profesional sp3 and the image is
> Ubuntu-6.06.1.ext3.1gb and yes i did extract Ubuntu-6.06.1.ext3.1gb.bz2 to
> theUbuntu-6.06.1.ext3.1gb folder
> this is a copy of my example.config file:
> #
> # This is an example for a configuration file that can
> # be passed to colinux-daemon in this manner:
> #
> #    colinux-daemon @example.conf
> #
> # Note that you can still prepend or append configuration and
> # boot parameters before and after '@', or you can use more
> # that one '@ to load several settings one after another.
> #
> #    colinux-daemon @example.conf @overrider.conf mem=32
> #
> # Full list of config params is listed in colinux-daemon.txt.
>
> # The default kernel
> kernel=vmlinux
>
> # File contains the root file system.
> # Download and extract preconfigured file from SF "Images for 2.6".
> cobd0="C:\Program Files\coLinux\Ubuntu-6.06.1.ext3.1gb"
>
> # Swap device, should be an empty file with 128..512MB.
> #cobd1="C:\Program Files\coLinux\swap_device"
>
> # Tell kernel the name of root device (mostly /dev/cobd0,
> # /dev/cobd/0 on Gentoo)
> # This parameter will be forward to Linux kernel.
> root=/dev/cobd0
>
> # Additional kernel parameters (ro = rootfs mount read only)
> ro
>
> # Initrd installs modules into the root file system.
> # Need only on first boot.
> initrd=initrd.gz
>
> # Maximal memory for linux guest
> #mem=128
>
> # Slirp for internet connection (outgoing)
> # Inside running coLinux configure eth0 with this static settings:
> # ipaddress 10.0.2.15   broadcast  10.0.2.255   netmask 255.255.255.0
> # gateway   10.0.2.2    nameserver 10.0.2.3
> #eth0=slirp
>
> # Tuntap as private network between guest and host on second linux device
> #eth1=tuntap
>
> # Setup for serial device
> #ttys0=COM1,"BAUD=115200 PARITY=n DATA=8 STOP=1 dtr=on rts=on"
>
> # Run an application on colinux start (Sample Xming, a Xserver)
> #exec0=C:\Programs\Xming\Xming.exe,":0 -clipboard -multiwindow -ac"
>
> this is the message i get in cmd prompt:
> C:\Program Files\coLinux>colinux-daemon.exe @example.conf
> Cooperative Linux Daemon, 0.7.3
> Daemon compiled on Sat May 24 22:36:07 2008
>
> PID: 2344
> colinux: booting
> Linux version 2.6.22.18-co-0.7.3 (hn@coLinux) (gcc version 4.1.2) #1 PREEMPT
> Sat
>  May 24 22:27:30 UTC 2008
> 256MB LOWMEM available.
> initrd enabled: start: 0xcff9a000  size: 0x00065881
> Entering add_active_range(0, 0, 65536) 0 entries of 256 used
> Zone PFN ranges:
>   DMA             0 ->        0
>   Normal          0 ->    65536
> early_node_map[1] active PFN ranges
>     0:        0 ->    65536
> On node 0 totalpages: 65536
>   DMA zone: 0 pages used for memmap
>   Normal zone: 512 pages used for memmap
>   Normal zone: 65024 pages, LIFO batch:15
> Built 1 zonelists.  Total pages: 65024
> Kernel command line: root=/dev/cobd0 ro ro
> Enabling fast FPU save and restore... done.
> Enabling unmasked SIMD FPU exception support... done.
> Initializing CPU#0
> Setting proxy interrupt vectors
> PID hash table entries: 1024 (order: 10, 4096 bytes)
> Console: colour CoCON 80x25
> Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
> Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
> Memory: 255616k/262144k available (1705k kernel code, 0k reserved, 470k
> data, 12
> 8k init, 0k highmem)
> virtual kernel memory layout:
>     fixmap  : 0xffffc000 - 0xfffff000   (  12 kB)
>     vmalloc : 0xd0800000 - 0xffffa000   ( 759 MB)
>     lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)
>       .init : 0xc0322000 - 0xc0342000   ( 128 kB)
>       .data : 0xc02aa638 - 0xc031ffe4   ( 470 kB)
>       .text : 0xc0100000 - 0xc02aa638   (1705 kB)
> Calibrating delay loop... 4364.69 BogoMIPS (lpj=21823488)
> Mount-cache hash table entries: 512
> CPU: After generic identify, caps: bfebfbff 20100000 00000000 00000000
> 0000e49d
> 00000000 00000001
> monitor/mwait feature present.
> using mwait in idle threads.
> CPU: Trace cache: 12K uops, L1 D cache: 16K
> CPU: L2 cache: 2048K
> CPU: After all inits, caps: bfebf3ff 20100000 00000000 0000b180 0000e49d
> 0000000
> 0 00000001
> Compat vDSO mapped to ffffe000.
> CPU: Intel(R) Pentium(R) D CPU 3.20GHz stepping 05
> Checking 'hlt' instruction... OK.
> NET: Registered protocol family 16
> NET: Registered protocol family 2
> IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
> TCP established hash table entries: 8192 (order: 4, 65536 bytes)
> TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
> TCP: Hash tables configured (established 8192 bind 8192)
> TCP reno registered
> checking if image is initramfs...it isn't (no cpio magic); looks like an
> initrd
> Freeing initrd memory: 406k freed
> VFS: Disk quotas dquot_6.5.1
> Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> cofuse init 0.1 (API version 2.2)
> io scheduler noop registered
> io scheduler anticipatory registered (default)
> io scheduler deadline registered
> io scheduler cfq registered
> RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
> cobd: loaded (max 32 devices)
> loop: module loaded
> conet: loaded (max 16 devices)
> serio: cokbd at irq 1
> mice: PS/2 mouse device common for all mice
> input: AT Translated Set 2 keyboard as /class/input/input0
> TCP cubic registered
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> Using IPI Shortcut mode
> RAMDISK: Compressed image found at block 0
> VFS: Mounted root (ext2 filesystem).
> end_request: I/O error, dev cobd0, sector 16
> ReiserFS: cobd0: warning: sh-2006: read_super_block: bread failed (dev
> cobd0, bl
> ock 2, size 4096)
> end_request: I/O error, dev cobd0, sector 128
> ReiserFS: cobd0: warning: sh-2006: read_super_block: bread failed (dev
> cobd0, bl
> ock 16, size 4096)
> ReiserFS: cobd0: warning: sh-2021: reiserfs_fill_super: can not find
> reiserfs on
>  cobd0
> end_request: I/O error, dev cobd0, sector 2
> EXT3-fs: unable to read superblock
> end_request: I/O error, dev cobd0, sector 2
> EXT2-fs: unable to read superblock
> end_request: I/O error, dev cobd0, sector 64
> isofs_fill_super: bread failed, dev=cobd0, iso_blknum=16, block=32
>
>

Re: [coLinux-users] Can't start colinux

[Shai V. <sva...@gm...>]

In the file example.conf, typically in directory c:\Program
Files\coLinux, the line:
cobd0="c:\coLinux\root_fs"
Should be edited to point to an actual Linux filesystem.

Assuming you did modify this to point to the right file system, it
could be that for some reason the file is missing, or already open by
another application.

- Shai

On Tue, Mar 3, 2009 at 9:47 AM, Vlad Stanimir <vla...@gm...> wrote:
> i tried to start colinux using colinux-daemon.exe @example.conf but i
> get the this error:
>
> No filesystem could mount root, tried:  reiserfs ext3 ext2 iso9660
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(117,0)
>
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
> -Strategies to boost innovation and cut costs with open source participation
> -Receive a $600 discount off the registration fee with the source code: SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>

[coLinux-users] Can't start colinux

[Vlad S. <vla...@gm...>]

i tried to start colinux using colinux-daemon.exe @example.conf but i 
get the this error:
 
No filesystem could mount root, tried:  reiserfs ext3 ext2 iso9660
Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(117,0)