colinux-users — coLinux users mailing list

Re: [coLinux-users] Does colinux work with gentoo 2006.1?

[Anders E. C \(KI/EAB\) <and...@er...>]

Didn't know there was 2006.1 profile out yet. I'll check it out.
=20
What did you do exactly when you "tried to gcc 4.1.1 and glibc 2.4 "?
=20
Did you just switch to the other profile? emerge -e system? emerge -e
world?
=20
/Anders
=20



________________________________

	From: col...@li...
[mailto:col...@li...] On Behalf Of Bing
Wen
	Sent: den 4 september 2006 06:39
	To: col...@li...
	Subject: [coLinux-users] Does colinux work with gentoo 2006.1?
=09
=09
	I tried to gcc 4.1.1 and glibc 2.4 in the new profile. After
reboot, my network interface disappeared. "no interface module has been
loaded" is the message. Any one else experienced the same?
=09

[coLinux-users] Does colinux work with gentoo 2006.1?

[Bing W. <bx...@ya...>]

I tried to gcc 4.1.1 and glibc 2.4 in the new profile. After reboot, my network interface disappeared. "no interface module has been loaded" is the message. Any one else experienced the same?

Re: [coLinux-users] gentoo

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

I've done this numerous times. I download the latest Gentoo coLinux
image, do a Gentoo install using the downloaded coLinux gentoo image as
my 'initial boot' image to a new file, and when it comes time to
"install the kernel", just copy over /lib/modules/* to
/mnt/gentoo/lib/modules

Everything just works for me doing it this way. No muss, no fuss :)

Jason

George P Boutwell wrote:
> mattias,
>
>   I don't know.  I don't run gentoo or fedora.  I suggest you start
> with the images that coLinux provides in it's installer (same ones
> available for download at the same place that coLinux is downloaded),
> those are at least known to work with it at the time of release.  If
> you are having a specific problem with gentoo ask on
> forums.gentoo.org, ask a specific question about your problem on the
> colinux-users Mailing List and hopefully another Gentoo/coLinux user
> will respond, search the colinux-user Mailing List archives, perhaps
> your problem has been encountered and a solution already provided in
> the Mailing Lists.
>
>   

Re: [coLinux-users] gentoo

[George P B. <geo...@gm...>]

mattias,

  I don't know.  I don't run gentoo or fedora.  I suggest you start
with the images that coLinux provides in it's installer (same ones
available for download at the same place that coLinux is downloaded),
those are at least known to work with it at the time of release.  If
you are having a specific problem with gentoo ask on
forums.gentoo.org, ask a specific question about your problem on the
colinux-users Mailing List and hopefully another Gentoo/coLinux user
will respond, search the colinux-user Mailing List archives, perhaps
your problem has been encountered and a solution already provided in
the Mailing Lists.

-- 
George

Re: [coLinux-users] gentoo

[mattias j. <jo...@ma...>]

b2sNCndoYXQga2VybmVsIHZlcnNpb24gYXJlIHJlcXVpcmVkIHRvIHJ1biBnZW50b28/IG9yIGZl
ZG9yYT8NCnRoZSBrZXJuZWwgaSBoYXZlIGZyb20gdGhlIDAuNi40IGRvc2VuJ3Qgd29yaw0KDQot
LS0tDQptYXR0aWFzIGpvbnNzb24NCm1vYmlsOiAwNzA4MTc0NTE2DQpoZW1zaWRhOg0Kd3d3Lm1h
dHRpYXN3ZWIudGsNCmVtYWlsOg0Kam9uc3NvbkBtYXR0aWFzLnN5dGVzLm5ldA0KbXNuOiBtYXR0
aWFzX2pvbnNzb244NkBob3RtYWlsLmNvbSANCg0KaWNxIDIxMTc3Nzc4OA0KDQoNCg0KDQotLS0t
LVVyc3BydW5nbGlndCBtZWRkZWxhbmRlLS0tLS0NCkZy5W46IEdlb3JnZSBQIEJvdXR3ZWxsIFtt
YWlsdG86Z2VvcmdlLmJvdXR3ZWxsQGdtYWlsLmNvbV0NClNraWNrYXQ6IGRlbiAyIHNlcHRlbWJl
ciAyMDA2IDAyOjA3DQpUaWxsOiBtYXR0aWFzIGpvbnNzb24NCktvcGlhOiBjb2xpbnV4LXVzZXJz
QGxpc3RzLnNvdXJjZWZvcmdlLm5ldA0KxG1uZTogUmU6IFtjb0xpbnV4LXVzZXJzXSBnZW50b28N
Cg0KDQpPbiA4LzMwLzA2LCBtYXR0aWFzIGpvbnNzb24gPGpvbnNzb25AbWF0dGlhcy5zeXRlcy5u
ZXQ+IHdyb3RlOg0KPiB0aGUgbmV3ZXN0ZyBjb2xpbnV4IGFyZSAwLjYuND8NCj4gb3IgaGF2ZSBp
IHdyb25nPw0KDQpBdCB0aGlzIHRpbWUgMC42LjQgaXMgdGhlIG5ld2VzdCBTVEFCTEUgY29MaW51
eCB0aGF0IGhhcyBiZWVuIHJlbGVhc2VkLg0KDQotLSANCkdlb3JnZQ0K

Re: [coLinux-users] gentoo

[George P B. <geo...@gm...>]

On 8/30/06, mattias jonsson <jo...@ma...> wrote:
> the newestg colinux are 0.6.4?
> or have i wrong?

At this time 0.6.4 is the newest STABLE coLinux that has been released.

-- 
George

Re: [coLinux-users] Problems with TAP and/or WinPCap driver

[Jason A. <jta...@ac...>]

Thanks for the suggestions and advice.

Things just started working. Though I don't know why. I did find one 
problem with my config (the Name option in the NIC config in the xml was 
incorrect) but that would not explain why my host OS network went totally 
AWOL when bridging was set up, and why it suddenly fixed itself on my 
third or fourth attempt. Heh.

Either way, things are all working now.

Jason

Re: [coLinux-users] gentoo

[mattias j. <jo...@ma...>]

dGhlIG5ld2VzdGcgY29saW51eCBhcmUgMC42LjQ/DQpvciBoYXZlIGkgd3Jvbmc/DQoNCi0tLS0N
Cm1hdHRpYXMgam9uc3Nvbg0KbW9iaWw6IDA3MDgxNzQ1MTYNCmhlbXNpZGE6DQp3d3cubWF0dGlh
c3dlYi50aw0KZW1haWw6DQpqb25zc29uQG1hdHRpYXMuc3l0ZXMubmV0DQptc246IG1hdHRpYXNf
am9uc3Nvbjg2QGhvdG1haWwuY29tIA0KDQppY3EgMjExNzc3Nzg4DQoNCg0KDQoNCi0tLS0tVXJz
cHJ1bmdsaWd0IG1lZGRlbGFuZGUtLS0tLQ0KRnLlbjogR2VvcmdlIFAgQm91dHdlbGwgW21haWx0
bzpnZW9yZ2UuYm91dHdlbGxAZ21haWwuY29tXQ0KU2tpY2thdDogZGVuIDMwIGF1Z3VzdGkgMjAw
NiAxNzo0Nw0KVGlsbDogbWF0dGlhcyBqb25zc29uDQpLb3BpYTogY29saW51eC11c2Vyc0BsaXN0
cy5zb3VyY2Vmb3JnZS5uZXQNCsRtbmU6IFJlOiBbY29MaW51eC11c2Vyc10gZ2VudG9vDQoNCg0K
RG9uJ3Qga25vdyB0aGF0IGEgY2VydGFpbiB2ZXJzaW9uIGlzIG5lZWRlZC4gIFRoZXJlIG1pZ2h0
IGJlIHByb2JsZW1zDQp3aXRoIHRoZSBtb3N0IHJlY2VudCBnZW50b28gKHVkZXYgdG8gYmUgc3Bl
Y2lmaWMpICYgdGhlIGN1cnJlbnQNCnZlcnNpb25zIG9mIGNvTGludXggc2luY2UgY29MaW51eCdz
IGtlcm5lbCBpcyBsYWdnaW5nIGJlaGluZCBhIGxpdHRsZQ0KZnJvbSBsaW51eCBrZXJuZWwgcHJv
cGVyIGFuZCB3aGF0IGdlbnRvbyBwcm9iYWJseSBleHBlY3RzLiAgSSBjYW4gdGVsbA0KeW91IHRo
YXQgd2UgaGF2ZSBtYW55IGdlbnRvbyB1c2VycyB3aG8gaGF2ZSBiZWVuIHVzaW5nIGdlbnRvbyB3
aXRoDQpuZWFybHkgZXZlcnkgdmVyc2lvbiBvZiBjb2xpbnV4IGZvciBxdWl0ZSBzb21lIHRpbWUu
DQoNCk9uIDgvMjcvMDYsIG1hdHRpYXMgam9uc3NvbiA8am9uc3NvbkBtYXR0aWFzLnN5dGVzLm5l
dD4gd3JvdGU6DQo+IHdpY2ggdmVyc2lvbiBvZiBjb2xpbnV4IGFyZSByZXF1ZXJkIHRvIHJ1biBn
ZW50b28/DQoNCi0tIA0KR2VvcmdlDQo=

Re: [coLinux-users] gentoo

[George P B. <geo...@gm...>]

Don't know that a certain version is needed.  There might be problems
with the most recent gentoo (udev to be specific) & the current
versions of coLinux since coLinux's kernel is lagging behind a little
from linux kernel proper and what gentoo probably expects.  I can tell
you that we have many gentoo users who have been using gentoo with
nearly every version of colinux for quite some time.

On 8/27/06, mattias jonsson <jo...@ma...> wrote:
> wich version of colinux are requerd to run gentoo?

-- 
George

Re: [coLinux-users] Problem with mounting root partition after upgrade

[Holger K. <hol...@gm...>]

Marek Uher schrieb:
> I tried to boot coLinux directly (i.e. bypass config file) with options
> 
>      colinux-daemon kernel=... cobd0=root_fs ...
> 

with or without your additinal kernel parameters?

Re: [coLinux-users] Problem with mounting root partition after upgrade

[<xu...@se...>]

I tried to boot coLinux directly (i.e. bypass config file) with options

     colinux-daemon kernel=... cobd0=root_fs ...

But with the  same result - I am not still boot coLinux. coLinux is
unable to mount root partition ...

Re: [coLinux-users] Problem with mounting root partition after upgrade

[Holger K. <hol...@gm...>]

Marek Uher schrieb:

 >     <!-- bootparams allows you to pass kernel boot parameters -->
>     <bootparams>root=/dev/cobd0 nosmp maxcpus=0 mem=96m </bootparams>

I would try root=/dev/cobd0 without the additional parameters.
Maybe root=/dev/cobd/0.


> 
>     <!-- Initial RamDISK (initrd) support -->
>     <initrd path="boot\initrd-2.6.11-co-0.6.4.gz" />
>     
>     <!-- image allows you to specify the kernel to boot -->
>     <image path="boot\vmlinux-2.6.11-co-0.6.4" />
> 
>     <!-- this line allows you to specify the amount of memory available 
>          to coLinux -->
>     <memory size="96" />

Re: [coLinux-users] Problem with mounting root partition after upgrade

[<xu...@se...>]

Boot log and config file included ...

Re: [coLinux-users] Problems with TAP and/or WinPCap driver

[Michelangelo <mic...@gm...>]

Post your config for more help.

A simple working config:
Install colinux 0.6.4 with TAP driver.
Windows XP side: Activate internet connection sharing on i.e. your LAN
connection towards the TAP connection (make sure the connection you're
sharing does not belong already to a 192.168.0.x network).
Start colinux with something like
c:\colinux\colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/cobd/0
mem=256 eth0=tuntap cobd0=.gentoo4gb_notebook
COLINUX side: check that the colinux install is configured to obtain a DHCP
lease - check the colinux ip, should be in 192.168.0.1-254 range. Or, set
networking with a static IP in the abovementioned range.
hope this helps
Michelangelo

On 8/29/06, Jason Ahrens <ja...@co...> wrote:
>
> This may or may not be helpful, but when I start CoLinux with the TAP
> driver, the TAP interface in windows does not go 'active'. IE: Windows
> still things there is 'nothing listening' at the other end (red X over the
> connection in task bar and on Network Connections page)
>
> Jason
>
> On Tue, 29 Aug 2006, Jason Ahrens wrote:
>
>

Re: [coLinux-users] Problem with mounting root partition after upgrade

[Holger K. <hol...@gm...>]

Marek Uher schrieb:
>         Hi all,
> 
> I have a problem with my two coLinux installations after migrating to new
> versions. In the first case (MS Windows XP Home Edition SP1, notebook) I
> upgraded from coLinux version 0.6.3 to 0.6.4 a few days ago. In the second
> case (MS Windows XP Professional SP2, server) I upgraded another installation
> from coLinux version 0.6.4 to 0.6.4-2. In both cases a have a problem with
> mounting root file system. Error message follows:
> 
> ...
> VFS: Mounted root (ext2 filesystem).
> 

Send your config file please.

[coLinux-users] Problem with mounting root partition after upgrade

[<xu...@se...>]

        Hi all,

I have a problem with my two coLinux installations after migrating to new
versions. In the first case (MS Windows XP Home Edition SP1, notebook) I
upgraded from coLinux version 0.6.3 to 0.6.4 a few days ago. In the second
case (MS Windows XP Professional SP2, server) I upgraded another installation
from coLinux version 0.6.4 to 0.6.4-2. In both cases a have a problem with
mounting root file system. Error message follows:

...
VFS: Mounted root (ext2 filesystem).

===================================================
# This process will install (if necessary) the coLinux modules for the
# coLinux kernel.
===================================================

Determining /, Found.
Mounting /
mount: Mounting /dev/cobd0 on /mnt/linux failed: No such device
Closing /
umount: forced umount of (null) failed!
Failed. (trying again)
umount: forced umount of (null) failed!

initrd: umount failed on rootfs
Try to run coLinux without initrd. Comment out initrd from configuation.

Press <Enter> to continue.


I tried to comment out initrd section, but I got this another error message:

...
EXT2-fs warning: checktime reached, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
VFS: Cannot open root device "cobd0" or unknown-block(117,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(117,0)

I spend few days with searching for help or advice on Google. Unfortunately
I didn't find any useful info. I hadn't any problem with coLinux installations
many months - it was pretty stable. The reason for upgrade was periodical
system maintenance. I wanted to upgrade my installations and then keep it
them for next few months. These strange errors appear after upgrade. Now
I am not able to use none of my coLinux installations.

I tried to remove/reinstall or downgrade both installations to previous
versions, but without any success. So, I didn't change anything in
configuration file for longtime. Does anyone have some idea or advice for
me? Please, help. Thanks.

Marek

Re: [coLinux-users] Problems with TAP and/or WinPCap driver

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

This may or may not be helpful, but when I start CoLinux with the TAP 
driver, the TAP interface in windows does not go 'active'. IE: Windows 
still things there is 'nothing listening' at the other end (red X over the 
connection in task bar and on Network Connections page)

Jason

On Tue, 29 Aug 2006, Jason Ahrens wrote:

> I blew away my old XP install when I got a new hard disk and am setting 
> everything back up again.
>
> When I get to the coLinux install, everything looks ok. No errors during 
> install.
>
> However, when I set up  my TAP bridge in XP, my network goes away. XP says 
> everything is fine. The bridge is active, the real NIC is enabled and no 
> errors, but there's no trafic. I've checked the configuration and everything 
> looks OK to me. I've even gone and disabled all the offload options on my NIC 
> thinking I may be having a problem there. No dice.
>
> As soon as I remove the bridge, the real NIC starts working again and trafic 
> flows. No problem.
>
> So I decide to try the winPcap bridge as given in 
> http://wiki.colinux.org/wiki/Network
>
> With the option, the real NIC stays active, but I get no trafic out the 
> 'bridge'. Constantly getting the message "No route to host" for anything that 
> tries to use the network.
>
> What kind of troubleshooting do I have available to me for the TAP and/or 
> WinPCap drivers? I'm sure/hopefull that this is just a simple little thing 
> and I can get this all back up and going the way it was before my fresh 
> install!
> Thanks
>
> Jason
>

[coLinux-users] Problems with TAP and/or WinPCap driver

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

I blew away my old XP install when I got a new hard disk and am setting 
everything back up again.

When I get to the coLinux install, everything looks ok. No errors during 
install.

However, when I set up  my TAP bridge in XP, my network goes away. XP says 
everything is fine. The bridge is active, the real NIC is enabled and no 
errors, but there's no trafic. I've checked the configuration and 
everything looks OK to me. I've even gone and disabled all the offload 
options on my NIC thinking I may be having a problem there. No dice.

As soon as I remove the bridge, the real NIC starts working again and 
trafic flows. No problem.

So I decide to try the winPcap bridge as given in 
http://wiki.colinux.org/wiki/Network

With the option, the real NIC stays active, but I get no trafic out the 
'bridge'. Constantly getting the message "No route to host" for anything 
that tries to use the network.

What kind of troubleshooting do I have available to me for the TAP and/or 
WinPCap drivers? I'm sure/hopefull that this is just a simple little thing 
and I can get this all back up and going the way it was before my fresh 
install!
Thanks

Jason

Re: [coLinux-users] source unavailable?

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

Jay Mac wrote:
> I'm having trouble getting the source from sourceforge.
> I go to the download site & get a message saying the site is down.

Yes, SF is down or overloaded.  I got error "500 - Internal Server 
Error".  Browser refresh helps some times.

You can download lates coLinux from here:
http://www.henrynestler.com/colinux/testing/stable-0.6.4-2/

-- 
Henry Nestler

[coLinux-users] source unavailable?

[Jay M. <sig...@ya...>]

Hello.

I'm having trouble getting the source from sourceforge. 
I go to the download site & get a message saying the site is down.

anyone know what's happening? 

[coLinux-users] gentoo

[mattias j. <jo...@ma...>]

wich version of colinux are requerd to run gentoo?
----
mattias jonsson
mobil: 0708174516
hemsida:
www.mattiasweb.tk
email:
jo...@ma...
msn: mat...@ho... 

icq 211777788

Re: [coLinux-users] 0.7.1 and no more '-a #' switch...

[Simon D. <Sim...@ya...>]

>From Henry Nestler:

>> Now what would be be really sweet was if colinux-console-* could
>> simply accept the name of a running coLinux service to attach to.
>
> Ok, that is an solution for services.  What does command prompt starts?
>
> If you not give any params to colinux-console-*, then the first colinux
> will be attach.  Inside the source you will see  comment 'todo: add not
> only the first console here' (or so).
>
> Do not create a new tool.  Better you add a new param to the
> colinux-console-*,  for sample '-i N' where N is the number of colinux.

And that's pretty much how the old '-a' switch used to work.  The only
weakness with that old mechanism was the issue of ambiguity: if a later
instance started before an earlier instance (for whatever reason) then
those instance numbers would not be in the predicted order.  It wasn't
a problem in any way, shape or form.  But it caught me out a few times.
;-)

Anyway, to resolve the ambiguity of the earlier '-a' switch, coLinux-daemon
would need a complementary '-i N' parameter.

However, I feel that a '-n <name>' parameter for coLinux-daemon would work
better *if*: a) coLinux-console-* could attach to a *named* instance with
its own complementary '-n <name>' parameter, and b) the names of running
instances could be enumerated (this would be useful for future management
consoles because you could tell at a glance which instance you're dealing 
with).

I'd be tempted to patch 0.7.1, but I wouldn't know where to start.


		
___________________________________________________________ 
Yahoo! Messenger - with free PC-PC calling and photo sharing. http://uk.messenger.yahoo.com

Re: [coLinux-users] 0.7.1 and no more '-a #' switch...

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

Simon Dainty wrote:
> The 0.6.4 distro version of colinux-console-net supported the -d
> switch that allows us to specify which running instance of coLinux
> a console should attach to (I have two instances running as services),
> and worked fine.
> 
> The 0.7.1 distro has forsaken this in place of the -a switch that
> only accepts a PID.  This, too, is fine.  Except - well - I need to
> acquire the PID and manually specify it as a command-line arg.
> 
> Does anyone know of a simple command-line tool that will take
> a process name and return a PID?
> 
> Hmmm... Maybe I should just stop being bone idle, load Visual
> Studio and write my own.
> 
> Now what would be be really sweet was if colinux-console-* could
> simply accept the name of a running coLinux service to attach to.

Ok, that is an solution for services.  What does command prompt starts?

If you not give any params to colinux-console-*, then the first colinux 
will be attach.  Inside the source you will see  comment 'todo: add not 
only the first console here' (or so).

Do not create a new tool.  Better you add a new param to the 
colinux-console-*,  for sample '-i N' where N is the number of colinux.

-- 
Henry Nestler

[coLinux-users] 0.7.1 and no more '-a #' switch...

[Simon D. <Sim...@ya...>]

The 0.6.4 distro version of colinux-console-net supported the -d
switch that allows us to specify which running instance of coLinux
a console should attach to (I have two instances running as services),
and worked fine.

The 0.7.1 distro has forsaken this in place of the -a switch that
only accepts a PID.  This, too, is fine.  Except - well - I need to
acquire the PID and manually specify it as a command-line arg.

Does anyone know of a simple command-line tool that will take
a process name and return a PID?

Hmmm... Maybe I should just stop being bone idle, load Visual
Studio and write my own.

Now what would be be really sweet was if colinux-console-* could
simply accept the name of a running coLinux service to attach to.

Ps, anyone upgraded to Debian Etch from Sarge under coLinux yet?

		
___________________________________________________________ 
All New Yahoo! Mail – Tired of Vi@gr@! come-ons? Let our SpamGuard protect you. http://uk.docs.yahoo.com/nowyoucan.html

Re: [coLinux-users] help with gentoo

[Anders E. C \(KI/EAB\) <and...@er...>]

"QM_MODULES" is oftenly a sign that you have module-init-tools package
compiled towards a 2.4 kernel and you're running 2.6.
=20
I'm using module-init-tools-3.2.1 on kernel 2.6.15.
=20
-Anders
=20


________________________________

	From: col...@li...
[mailto:col...@li...] On Behalf Of
mattias jonsson
	Sent: den 19 augusti 2006 01:20
	To: col...@li...
	Subject: [coLinux-users] help with gentoo
=09
=09
	i can't start gentoo the folowing message comes up
	Console - Cooperative Linux - [To Exit, Press Window+Alt Keys]
	modprobe: Safe mode has more than one parameter
	modprobe: QM_MODULES: Function not implemented
	modprobe: Safe mode has more than one parameter

	modprobe: QM_MODULES: Function not implemented
	modprobe: Safe mode has more than one parameter
	modprobe: QM_MODULES: Function not implemented
	modprobe: Safe mode has more than one parameter

	fsck.ext3: No such file or directory while trying to open
/dev/cobd0
	/dev/cobd0:

	The superblock could not be read or does not describe a correct
ext2           =20
	filesystem.  If the device is valid and it really contains an
ext2
	filesystem (and not swap or ufs or something else), then the
superblock
	is corrupt, and you might try running e2fsck with an alternate
superblock:
	    e2fsck -b 8193 <device>

=09

	* Filesystem couldn't be fixed :( [ !! ]
	Give root password for maintenance
	(or type Control-D for normal startup): error copying:
"/dev/initctl" to "/lib/d
	ev-state/initctl"
	bash-2.05b#

	----
	mattias jonsson
	mobil: 0708174516
	hemsida:
	www.mattiasweb.tk
	email:
	jo...@ma...
	msn: mat...@ho...=20

	icq 211777788
=09

	=20