colinux-users — coLinux users mailing list

[coLinux-users] coLinux Fedora builds/64 bit Windows

[Bill C R. <do...@gm...>]

Hi,

It looks like most of the image builds for coLinux desperately need updating.   For example, the last Fedora image I built was Fedora 10.   Since Fedora 10 has been end-of-life for more than a year now, the scripts for installing gnome no-longer work.

The problem of course is that coLinux does not support 64 bit operating systems.   I retired my last 32 bit Windows machine 2 years ago.  As such I am unable to run coLinux to build a newer image.

So I have two requests:

    1. Can we depreciate the links to the Fedora builds.   I added a readme file to the image directory that tells users they are end of life, but since you have scroll down to see the readme, many users will probably waste time downloading the images before noticing the readme.

    2. Can we maybe get a list of what we need volunteers to do to generate a version of coLinux that runs under a 64 bit OS?   I've seen the 64 bit development page referenced by the FAQ.   It looks like at least some of the issues are what is required for coLinux to run a 64 bit OS.   For now, I would be happy to run a 32 bit version of Fedora under Windows 7 - 64 bit.   It sounds like the main problem right may just be the drivers?   I would be happy to volunteer my own time, but I don't know a thing about windows drivers, and I would also not want to step on someone else's toes.

Regards,

Bill

[coLinux-users] How to debug: "INIT: PANIC: segmentation violation at 0xb776c417! sleeping for 30 seconds."

[Arturo R. <ja...@gm...>]

I hope it's OK that I'm cross-posting this. I sent the message to
debian-users, but I think I might have better luck here.

Per the title, I'd love to get your input on how to debug/fix this
particular issue. A description of my setup:

Asus UL30A-X5 Laptop
1.3GHz Intel SU7300 Core 2 Duo
4GB of DDR3 RAM
500GB SATA
Intel GMA 4500MHD

Running Debian sid on a coLinux 0.7.8 (uname -a: "Linux colinux
2.6.33.5-co-0.7.8 #1 PREEMPT Wed Sep 1 22:49:51 UTC 2010 i686
GNU/Linux") inside of Windows XP Pro SP3. The error is reproducible
100% of the time. When the machine goes into standby, either
automatically or manually, init (or something else? see below),
crashes and takes the system down with it.

I've read that gdb can't attach to init by design, so I tried strace.
Output is attached as strace.log

Now, since I assumed the problem was with init, I switched to upstart,
but that's not working either. See upstart.log, attached.

I've also ruled out coLinux (and with it, its kernel) by trying one of
the filesystem images they provide. When using that, there is no
problem bringing the machine in and out of standby repeatedly.

Does anyone have any idea of how I could further narrow down where the
problem lies, or point me in the direction of the proper mailing list
to direct my question?

My apologies if I've left out any important detail. Please let me know
if you have any questions.

-- 
Arturo R.

Re: [coLinux-users] compile coLinux on Fedora 12 (x86_64)

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

Hello Bruce,

building coLinux with "Linux as host" is not full supported. The 32 bit 
part is broken for recent kernels, and the 64 bit host is not usable.

I suggest you to use an other virtualisation, for example VirtualBos. Or 
use UML. Or mount the coLinux Image as loop device an "chroot" into it.

Henry


On 16.01.2011 12:04, bruce bushby wrote:
> Hi
>
> I have an urgent requirement to compile/run coLinux on Fedora 12 and 
> mac OS 10.6 due to a vendor shipping an integrated development 
> environment based on a coLinux image.
>
>
> I started with the Fedora 12 compile.....but am running into a few 
> issues, would be very grateful for any pointers.
>
>
> [bruce@core colinux]$
> [bruce@core colinux]$ pwd
> /home/bruce/Downloads/colinux
> [bruce@core colinux]$ ls -l
> total 1036
> -rw-rw-r-- 1 bruce bruce 1060419 2011-01-16 10:53 coLinux-0.7.8-src.tar.gz
> [bruce@core colinux]$
> [bruce@core colinux]$ tar -zxf coLinux-0.7.8-src.tar.gz
> [bruce@core colinux]$
> [bruce@core colinux]$ cd coLinux-0.7.8
> [bruce@core coLinux-0.7.8]$
> [bruce@core coLinux-0.7.8]$ ./configure --target=i686-pc-linux
> Setting colinux_os=linux
> Setting prefix=/home/bruce/Downloads/colinux/linux
> Setting downloaddir=/home/bruce/Downloads/colinux/download
>  UNAME_RELEASE=2.6.32.26-175.fc12.x86_64
> Setting hostkerneldir=/lib/modules/2.6.32.26-175.fc12.x86_64/build
>  HOST_VERSION=2
>  HOST_PATCHLEVEL=6
>  HOST_SUBLEVEL=32
>  HOST_EXTRAVERSION=.26-175.fc12.x86_64
> Checking wget ... found
> Checking Python interpreter ... (2.6.2) found
> Checking patch ... found
> Checking make ... found
> Checking bunzip2 ... found
> Checking gcc for kernel ... (4.4.4) found
> Checking gcc g++ ... (4.4.4) found
> Checking FLTK devel (patched) ... (1.1.10) found
> nm: '/usr/lib64/libfltk.a': No such file
>   /usr/lib64/libfltk.a: label fl_x_global_event_hook not found
>   Please set right path to a patched FLTK
> Create bin/user-build.cfg
> Configure DONE
>
> Ready for "make download && make && make package && make installer"
> Run "make help" for more instructions, and read doc/building.
>
> [bruce@core coLinux-0.7.8]$
> [bruce@core coLinux-0.7.8]$ make download
> make: *** No rule to make target `download'.  Stop.
> [bruce@core coLinux-0.7.8]$
> [bruce@core coLinux-0.7.8]$ make
>
>
> I can't get the "make download" to work....is this because there is an 
> error on FLTK
>
> [bruce@core coLinux-0.7.8]$ rpm -qa | grep -i fltk
> fltk-devel-1.1.10-1.fc13.x86_64
> fltk-1.1.10-1.fc13.x86_64
> [bruce@core coLinux-0.7.8]$
>
>
> When I run the make....it fails with:
> /coLinux-0.7.8/src/colinux/common/common.h:28:31: error: 
> linux/cooperative.h: No such file or directory
>
>
> Thanks
> Bruce

[coLinux-users] compile coLinux on Fedora 12

[bruce b. <bru...@gm...>]

Hi

I have an urgent requirement to compile/run coLinux on Fedora 12 and mac OS
10.6 due to a vendor shipping an integrated development environment based on
a coLinux image.


I started with the Fedora 12 compile.....but am running into a few issues,
would be very grateful for any pointers.


[bruce@core colinux]$
[bruce@core colinux]$ pwd
/home/bruce/Downloads/colinux
[bruce@core colinux]$ ls -l
total 1036
-rw-rw-r-- 1 bruce bruce 1060419 2011-01-16 10:53 coLinux-0.7.8-src.tar.gz
[bruce@core colinux]$
[bruce@core colinux]$ tar -zxf coLinux-0.7.8-src.tar.gz
[bruce@core colinux]$
[bruce@core colinux]$ cd coLinux-0.7.8
[bruce@core coLinux-0.7.8]$
[bruce@core coLinux-0.7.8]$ ./configure --target=i686-pc-linux
Setting colinux_os=linux
Setting prefix=/home/bruce/Downloads/colinux/linux
Setting downloaddir=/home/bruce/Downloads/colinux/download
 UNAME_RELEASE=2.6.32.26-175.fc12.x86_64
Setting hostkerneldir=/lib/modules/2.6.32.26-175.fc12.x86_64/build
 HOST_VERSION=2
 HOST_PATCHLEVEL=6
 HOST_SUBLEVEL=32
 HOST_EXTRAVERSION=.26-175.fc12.x86_64
Checking wget ... found
Checking Python interpreter ... (2.6.2) found
Checking patch ... found
Checking make ... found
Checking bunzip2 ... found
Checking gcc for kernel ... (4.4.4) found
Checking gcc g++ ... (4.4.4) found
Checking FLTK devel (patched) ... (1.1.10) found
nm: '/usr/lib64/libfltk.a': No such file
  /usr/lib64/libfltk.a: label fl_x_global_event_hook not found
  Please set right path to a patched FLTK
Create bin/user-build.cfg
Configure DONE

Ready for "make download && make && make package && make installer"
Run "make help" for more instructions, and read doc/building.

[bruce@core coLinux-0.7.8]$
[bruce@core coLinux-0.7.8]$ make download
make: *** No rule to make target `download'.  Stop.
[bruce@core coLinux-0.7.8]$
[bruce@core coLinux-0.7.8]$ make


I can't get the "make download" to work....is this because there is an error
on FLTK

[bruce@core coLinux-0.7.8]$ rpm -qa | grep -i fltk
fltk-devel-1.1.10-1.fc13.x86_64
fltk-1.1.10-1.fc13.x86_64
[bruce@core coLinux-0.7.8]$


When I run the make....it fails with:
/coLinux-0.7.8/src/colinux/common/common.h:28:31: error:
linux/cooperative.h: No such file or directory


Thanks
Bruce

Re: [coLinux-users] Plans for version 0.7.9?

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

Hello Ron,

thanks for remembering.
Yes, think it's time for new release. I will start a snapshot build this 
weekend.

Henry

On 06.01.2011 15:13, Ron Avriel wrote:
> Hi,
>
> Are there any plans to release a new 0.79 version?
>
> I'm waiting for this version because it will fix my large time offset 
> bug Bug#1780633 
> http://colinux.svn.sourceforge.net/viewvc/colinux?view=revision&revision=1539 
> <http://colinux.svn.sourceforge.net/viewvc/colinux?view=revision&revision=1539> 
> .
>
> We are suffering from this problem in many installations.
>
> Thanks,
> Ron

[coLinux-users] Plans for version 0.79?

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

Hi,

Are there any plans to release a new 0.79 version?

I'm waiting for this version because it will fix my large time offset bug Bug#1780633 http://colinux.svn.sourceforge.net/viewvc/colinux?view=revision&revision=1539 .

We are suffering from this problem in many installations.

Thanks,
Ron

 		 	   		  

Re: [coLinux-users] Can we boot a 64-bit linux distro under WinXP 32-bit?

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

On 08.12.2010 18:41, Fuujuhi wrote:
> I have an existing Ubuntu Lucid 10.04 64-bit that I would like to boot
> natively or under Windows XP (32-bit).
>
> I tried coLinux 0.7.8, but it failed with the error messages:
>
> request_module: runaway loop modprobe binfmt-464c
> request_module: runaway loop modprobe binfmt-464c
> request_module: runaway loop modprobe binfmt-464c
> (5 times)
>
> A few googling (like [1]), and it seems that this is because a 32-bit
> kernel is trying to boot a 64-bit OS, which indeed is the case. From the
> comment, it seems that enabling IA-32 emulation, or enabling ELF support
> could solve this issue (not tried yet).

This is not true. You can't run a 64 bit program under 32 bit kernel.

IA-32 emulation is the other way. Here is the definition from kernel config.

IA32 Emulation:
"Include code to run 32-bit programs under a 64-bit kernel. You should 
likely turn this on, unless you're 100% sure that you don't have any 
32-bit programs left."

-- 
Henry N.

[coLinux-users] Can we boot a 64-bit linux distro under WinXP 32-bit?

[Fuujuhi <fu...@no...>]

Hello,

I have an existing Ubuntu Lucid 10.04 64-bit that I would like to boot
natively or under Windows XP (32-bit).

I tried coLinux 0.7.8, but it failed with the error messages:

request_module: runaway loop modprobe binfmt-464c
request_module: runaway loop modprobe binfmt-464c
request_module: runaway loop modprobe binfmt-464c
(5 times)

A few googling (like [1]), and it seems that this is because a 32-bit
kernel is trying to boot a 64-bit OS, which indeed is the case. From the
comment, it seems that enabling IA-32 emulation, or enabling ELF support
could solve this issue (not tried yet).

Before trying my first kernel compile ever, I would like to check if
someone went through similar problems or would have a suggestion to make.

Thanks,
Fuujuhi


[1]
http://saalwaechter-notes.blogspot.com/2008/10/requestmodule-runaway-loop-modprobe.html

Re: [coLinux-users] CoLinux not working with Ubuntu 10.04 (lucid) or Ubuntu 10.10 (maverick)

[Benjamin R. <kr...@kr...>]

so it seems the linode fixes do work it's just that 
the one I was following has a typo:
http://library.linode.com/troubleshooting/upgrade-to-ubuntu-10.10-maverick

should be:
dev  /dev  tmpfs  rw  0  0

NOT devtmpfs.  Everything else is correct.

Re: [coLinux-users] CoLinux not working with Ubuntu 10.04 (lucid) or Ubuntu 10.10 (maverick)

[Benjamin R. <kr...@kr...>]

I just tried the new 11.04 (natty) and it works. 

[coLinux-users] CoLinux not working with Ubuntu 10.04 (lucid) or Ubuntu 10.10 (maverick)

[Benjamin R. <kr...@kr...>]

Seems there are some custom kernel patches from Ubuntu that are now required for 
10.04 and newer to boot properly because of udev, plymouth, mountall, and 
ureadahead changes.

I have tried the latest development snapshot and the release version of colinux.

I'm having the same problems detailed here: 
http://www.linode.com/forums/viewtopic.php?t=5522

None of the Linode solutions resolve the problem.

There is a Ubuntu bug report here where lots of people with custom kernels are 
having the same issues:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/571258

It's easy to reproduce the issue using this guide to create a maverick image:
http://www.tekcited.net/colinux-create-an-ubuntu-image-from-scratch

I could also provide the image if needed.  It's around 70MB.

Re: [coLinux-users] KVM Support?

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

If you want to avoid an explosion of your windows my advice is to
avoid to do it :=)
You are right ... Windows owns the hardware.
Bye,
Paolo

On Mon, Nov 22, 2010 at 12:11 AM, Miller, Shao
<sha...@yr...> wrote:
> Hello Folks,
>
> Is it possible for coLinux to include KVM support for 'kvm-qemu'?  My
> guess would be that it cannot, since Windows owns the hardware.  But I
> have to ask.
>
> Thanks!
>
> - Shao Miller

[coLinux-users] KVM Support?

[Miller, S. <sha...@yr...>]

Hello Folks,

Is it possible for coLinux to include KVM support for 'kvm-qemu'?  My
guess would be that it cannot, since Windows owns the hardware.  But I
have to ask.

Thanks!

- Shao Miller

Re: [coLinux-users] CoLinux crashes display driver on Windows Vista

[Frédéric L. W. M. <lis...@pe...>]

On Wed, 17 Nov 2010, Anirudh Bagde wrote:

> Hi,
> I am quite sure that it is a problem with something related to the ATI card
> and my graphics driver, because my computer crashed differently before and
> after I upgraded my drivers, and both times Windows reported to me that the
> display driver had crashed (previously in a BSOD, after upgrading, as a
> system tray message). Both times my mouse would barely move, and both times
> my screen would go black for a long period of time.
> 
> I went to the link you specified. I opened up an admin CMD, and cd'ed to
> "C:\Program Files\andLinux". There I first ran "colinux-daemon" and
> "colinux-daemon --status-driver". Both commands reported the date of
> compilation (i.e. the former said "Daemon compiled on" and the latter said
> "Driver compiled on") as "Wed Apr 15 18:59:08 2009". I then ran the command
> "colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/ram0", which
> failed with the message "initrd.gz: The system cannot find the file
> specified". A "dir" showed that the file vmlinux exists but the file
> initrd.gz does not. Running startup.bat opens up another console window. The
> display driver crashes immediately after it finds the TAP-CoLinux driver.
> 
> Thanks for replying; andLinux was just an experiment for me, just to see if
> it worked, and how well it worked. It doesn't matter to me much; I can
> always use VirtualBox in Seamless Mode.

I also have an internal X1200 and it never crashed here with coLinux in 
2 and 1/2 years, using Windows Vista SP1, SP2 and Windows 7. But I only 
have 2Gb of RAM and never use TAP.

Re: [coLinux-users] CoLinux crashes display driver on Windows Vista

[Anirudh B. <ani...@gm...>]

Hi,

I am quite sure that it is a problem with something related to the ATI card
and my graphics driver, because my computer crashed differently before and
after I upgraded my drivers, and both times Windows reported to me that the
display driver had crashed (previously in a BSOD, after upgrading, as a
system tray message). Both times my mouse would barely move, and both times
my screen would go black for a long period of time.

I went to the link you specified. I opened up an admin CMD, and cd'ed to
"C:\Program Files\andLinux". There I first ran "colinux-daemon" and
"colinux-daemon --status-driver". Both commands reported the date of
compilation (i.e. the former said "Daemon compiled on" and the latter said
"Driver compiled on") as "Wed Apr 15 18:59:08 2009". I then ran the command
"colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/ram0", which
failed with the message "initrd.gz: The system cannot find the file
specified". A "dir" showed that the file vmlinux exists but the file
initrd.gz does not. Running startup.bat opens up another console window. The
display driver crashes immediately after it finds the TAP-CoLinux driver.

Thanks for replying; andLinux was just an experiment for me, just to see if
it worked, and how well it worked. It doesn't matter to me much; I can
always use VirtualBox in Seamless Mode.

On Wed, Nov 17, 2010 at 5:24 PM, Henry Nestler <hen...@ar...> wrote:

>  Hello Anirudh,
>
>
> On 17.11.2010 00:45, Anirudh Bagde wrote:
>
> Hi,
>
>  I don't know where to ask this or whether to file a bug report, so I
> decided to post it here. I recently installed andLinux Beta 2 (final)
> downloaded from the andLinux downloads page. I verified its MD5 and SHA1
> hashes using HashTab, and I successfully installed it. All the shortcuts and
> icons and explorer extensions are now working. However, the colinux daemon
> is not. The service is on manual startup. Every time I open up services.msc
> and start the service andLinux, the display goes black within a minute and
> then shoes a BSOD with a stop error 116. It says that the display driver
> stopped working and could not be restarted. My display driver is and ATI
> Radeon X1200. After upgrading the ATI driver to 10.02 and reinstalling the
> coLinux driver, all this still happens, except I do not get a BSOD. The
> screen goes blank and the cursor (which I cannot move) flashes on and off.
> Then the screen comes back, and there is a message coming from the system
> tray that says the ATI display driver crash and recovered. However, I still
> cannot move the mouse, and the screen goes black again. This process keeps
> repeating until I manually held the power button and turned off the
> computer.
>
>  My computer is a Windows Vista Home Premium 32-bit with Service Pack 2.
> The graphics card is an ATI Radeon X1200. There are lots of driver files
> loaded as reported by Device Manager. The driver version is 8.593.100.0, and
> the Catalyst Control Center version is 2010.0210.2339.42455. The computer is
> a Toshiba Satellite A215-S7411. The processor is AMD Athlon(tm) 64 X2
> Dual-Core Processor TK-53 running at 1.70 GHz. I have about 240 GB of hard
> drive and 4 GB of RAM.
>
>  Is there any more information I need to provide? And does anyone know if
> there is anything I can do to get andLinux and coLinux to work?
>
>
> I think, there exist no solution.
>
> I see you have 4GB RAM and a Windows 32 bit. Windows use some dirty tricks
> to access full 4GB, while hardware can only access ~3,5GB of RAM directly.
> If Windows now give coLinux this dirty memory, then it will crash.
> The dirty trick is named AWE, please read last articles from this Open
> Discussion "How to let coLinux run in large RAM (>4GB)":
> https://sourceforge.net/projects/colinux/forums/forum/342354/topic/3467832
>
> Other problem can be ATI card. If that card uses shared memory and not
> marked this memory correctly as "used by graphic card", then coLinux would
> attach this memory and will later crash.
>
> --
> Henry N.
>
>


-- 
I'm an FSF member -- Help us support software freedom!
<http://fsf.org/about>

Re: [coLinux-users] TCP Network Broken from Host to coLinux Broadcom WinPcap

[Miller, S. <sha...@yr...>]

From: Miller, Shao 
Sent: Thursday, November 11, 2010 12:29
To: 'col...@li...'
Subject: RE: TCP Network Broken from Host to coLinux Broadcom WinPcap

Hello all,

Just for the record, I have a Broadcom NetLink Gigabit Ethernet NIC with
PCI IDs V14E4 (Broadcom, obviously), D1693.  My Windows XP driver is
b57xp32.sys.

I had encountered an issue where I could ping and perform any sort of
UDP to my hosted coLinux, but TCP wasn't working.  My coLinux' service
had parameters something like:

... ... ... (Solution omitted from previous e-mail)



Just reporting that I can reproduce the problem (and solution) on a
Marvell Yukon 88E8053 PCI-E Gigabit Ethernet Controller (VENdor 11AB,
DEVice 4362), which is the wired NIC on some Apple MacBook computers.
For this NIC, the setting was called TCP/UDP Checksum Offload (IPv4) and
one can reproduce the issue with the On setting.

Have a nice day.

- Shao Miller

Re: [coLinux-users] CoLinux crashes display driver on Windows Vista

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

  Hello Anirudh,

On 17.11.2010 00:45, Anirudh Bagde wrote:
> Hi,
>
> I don't know where to ask this or whether to file a bug report, so I 
> decided to post it here. I recently installed andLinux Beta 2 (final) 
> downloaded from the andLinux downloads page. I verified its MD5 and 
> SHA1 hashes using HashTab, and I successfully installed it. All the 
> shortcuts and icons and explorer extensions are now working. However, 
> the colinux daemon is not. The service is on manual startup. Every 
> time I open up services.msc and start the service andLinux, the 
> display goes black within a minute and then shoes a BSOD with a stop 
> error 116. It says that the display driver stopped working and could 
> not be restarted. My display driver is and ATI Radeon X1200. After 
> upgrading the ATI driver to 10.02 and reinstalling the coLinux driver, 
> all this still happens, except I do not get a BSOD. The screen goes 
> blank and the cursor (which I cannot move) flashes on and off. Then 
> the screen comes back, and there is a message coming from the system 
> tray that says the ATI display driver crash and recovered. However, I 
> still cannot move the mouse, and the screen goes black again. This 
> process keeps repeating until I manually held the power button and 
> turned off the computer.
>
> My computer is a Windows Vista Home Premium 32-bit with Service Pack 
> 2. The graphics card is an ATI Radeon X1200. There are lots of driver 
> files loaded as reported by Device Manager. The driver version 
> is 8.593.100.0, and the Catalyst Control Center version is 
> 2010.0210.2339.42455. The computer is a Toshiba Satellite A215-S7411. 
> The processor is AMD Athlon(tm) 64 X2 Dual-Core Processor TK-53 
> running at 1.70 GHz. I have about 240 GB of hard drive and 4 GB of RAM.
>
> Is there any more information I need to provide? And does anyone know 
> if there is anything I can do to get andLinux and coLinux to work?

I think, there exist no solution.

I see you have 4GB RAM and a Windows 32 bit. Windows use some dirty 
tricks to access full 4GB, while hardware can only access ~3,5GB of RAM 
directly. If Windows now give coLinux this dirty memory, then it will crash.
The dirty trick is named AWE, please read last articles from this Open 
Discussion "How to let coLinux run in large RAM (>4GB)":
https://sourceforge.net/projects/colinux/forums/forum/342354/topic/3467832

Other problem can be ATI card. If that card uses shared memory and not 
marked this memory correctly as "used by graphic card", then coLinux 
would attach this memory and will later crash.

-- 
Henry N.

[coLinux-users] CoLinux crashes display driver on Windows Vista

[Anirudh B. <ani...@gm...>]

Hi,

I don't know where to ask this or whether to file a bug report, so I decided
to post it here. I recently installed andLinux Beta 2 (final) downloaded
from the andLinux downloads page. I verified its MD5 and SHA1 hashes using
HashTab, and I successfully installed it. All the shortcuts and icons and
explorer extensions are now working. However, the colinux daemon is not. The
service is on manual startup. Every time I open up services.msc and start
the service andLinux, the display goes black within a minute and then shoes
a BSOD with a stop error 116. It says that the display driver stopped
working and could not be restarted. My display driver is and ATI Radeon
X1200. After upgrading the ATI driver to 10.02 and reinstalling the coLinux
driver, all this still happens, except I do not get a BSOD. The screen goes
blank and the cursor (which I cannot move) flashes on and off. Then the
screen comes back, and there is a message coming from the system tray that
says the ATI display driver crash and recovered. However, I still cannot
move the mouse, and the screen goes black again. This process keeps
repeating until I manually held the power button and turned off the
computer.

My computer is a Windows Vista Home Premium 32-bit with Service Pack 2. The
graphics card is an ATI Radeon X1200. There are lots of driver files loaded
as reported by Device Manager. The driver version is 8.593.100.0, and the
Catalyst Control Center version is 2010.0210.2339.42455. The computer is a
Toshiba Satellite A215-S7411. The processor is AMD Athlon(tm) 64 X2
Dual-Core Processor TK-53 running at 1.70 GHz. I have about 240 GB of hard
drive and 4 GB of RAM.

Is there any more information I need to provide? And does anyone know if
there is anything I can do to get andLinux and coLinux to work?

Thanks

-- 
I'm an FSF member -- Help us support software freedom!
 <http://fsf.org/about>

Re: [coLinux-users] TCP Network Broken from Host to coLinux Broadcom WinPcap

[Miller, S. <sha...@yr...>]

Hello all,

 

Just for the record, I have a Broadcom NetLink Gigabit Ethernet NIC with
PCI IDs V14E4 (Broadcom, obviously), D1693.  My Windows XP driver is
b57xp32.sys.

 

I had encountered an issue where I could ping and perform any sort of
UDP to my hosted coLinux, but TCP wasn't working.  My coLinux' service
had parameters something like:

 

  --run-service coLinux kernel=vmlinux cobd0=c:\somepath\Ubuntu_2GB.ext3
root=/dev/cobd0 eth0=pcap-bridge,Wired,00:0c:29:ab:ad:7e,promisc

 

So I was obviously using WinPcap bridging.  I tried updating to the
latest WinPcap, but it didn't fix the problem.  Wireshark revealed a lot
of duplicate TCP ACKs and invalid checksums, so I checked the properties
for the Broadcom NIC.  In the Advanced tab of its properties, I had
Checksum Offload set to Tx/Rx TCP/IP Checksum.  I set it to None and the
problem disappeared and TCP communications now work as expected.  I had
not encountered this problem on some other hardware.

 

Just putting this out there as a solution, in case anyone can benefit.
Dunno if it's FAQ-worthy; possibly not.

 

Please forgive some further detail: Only TCP communications between the
host and the hosted coLinux were affected.  TCP communications between
the hosted coLinux and any other computer were fine all along.  It was
quite irritating having to use another computer as a stepping-stone to
get back to the hosted coLinux. :-)

 

- Shao Miller

[coLinux-users] TCP Network Broken from Host to coLinux Broadcom WinPcap

[Miller, S. <sha...@yr...>]

Hello all,

 

Just for the record, I have a Broadcom NetLink Gigabit Ethernet NIC with
PCI IDs V14E4 (Broadcom, obviously), D1693.  My Windows XP driver is
b57xp32.sys.

 

I had encountered an issue where I could ping and perform any sort of
UDP to my hosted coLinux, but TCP wasn't working.  My coLinux' service
had parameters something like:

 

  --run-service coLinux kernel=vmlinux cobd0=c:\somepath\Ubuntu_2GB.ext3
root=/dev/cobd0 eth0=pcap-bridge,Wired,00:0c:29:ab:ad:7e,promisc

 

So I was obviously using WinPcap bridging.  I tried updating to the
latest WinPcap, but it didn't fix the problem.  Wireshark revealed a lot
of duplicate TCP ACKs and invalid checksums, so I checked the properties
for the Broadcom NIC.  In the Advanced tab of its properties, I had
Checksum Offload set to Tx/Rx TCP/IP Checksum.  I set it to None and the
problem disappeared and TCP communications now work as expected.  I had
not encountered this problem on some other hardware.

 

Just putting this out there as a solution, in case anyone can benefit.
Dunno if it's FAQ-worthy; possibly not.

 

- Shao Miller

Re: [coLinux-users] Native-Mode versus Win32

[Miller, S. <sha...@yr...>]

Good day Henry,

Thank you very much for your response.

You are right: I mean no Windows GUI and none of the user-land .DLLs you
listed.

You are right: Almost seems as good as running Linux natively, except:
The use of Windows drivers for, let's say, storage and network, which we
could bridge to the hosted Linux.

You are right: I'm thinking of a "native" application with similar
dependencies as drivers (.SYS) files: HAL.DLL, NTOSKRNL.EXE, NDIS.SYS,
probably NTDLL.DLL, etc.  For an example of a "native" application, see
Windows XP's \Windows\System32\AutoChk.exe.

I was very hopeful that most of coLinux resides in LINUX.SYS.  It seems
that you are confirming this.  If it's a simple matter of sending some
IRPs to \Device\CoLinuxDriver (I forget what it's called right now) in
order to get the driver to host the Linux, that is really what I'm
interested in, since we can send IRPs from "native" .EXEs.

I had already taken a quick look at the source directories you mentioned
before I sent the original e-mail, but wasn't 100% sure how feasible it
would be.  You seem to be suggesting that LINUX.SYS is the most critical
component, which is what I had hoped for.

I'll have to read more of the source and see if it would be difficult to
avoid the Win32 API and port to just use the native functions.

Thank you again,

- Shao Miller

-----Original Message-----
From: Henry Nestler [mailto:hen...@ar...] 
Sent: Monday, October 25, 2010 16:43
To: Miller, Shao
Cc: col...@li...
Subject: Re: [coLinux-users] Native-Mode versus Win32

  Hello Shao,

I don't know why you ask, this. First: Win32 is the complete Windows 
user land API. You means that? You means without GUI and so, than you 
would need to run coLinux without some basic DLLs, for example without 
user32.dll, gdi32.dll?

This is the list of all used DLL:
'user32', 'gdi32', 'ws2_32', 'ntdll', 'kernel32', 'ole32', 'uuid', 
'msvcrt', 'crtdll', 'shlwapi'.

You say, only kernel function can use? Then only kernel32.dll would be 
leave? I think, that is to little.
Without Session Manager you would have no other task, no winlogon, no 
other windows task. So, and way we should this run now? If you all of 
the windows GUI have removed, then I would say: Better start Linux
natively.

By the way the most things does the linux.sys, and this use only kernel 
DLLs ndis, ntoskrnl and hal. The colinux-daemon is only a loader to 
start Linux from inside the kernel driver, and later the monitor of 
running Linux task. colinux-daemon.exe send some ioctl to the kernel 
driver. The Win32 functions are for reading files and manage the task 
switch (WaitForMultipleObjects), and of curse for inter process 
communication base between the other colinux-*-daemon's (data pipe).

Please check files in src/colinux/os/winnt/user/*.c and 
src/colinux/os/winnt/user/daemon/*.c to see what API functions are used
http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/src/col
inux/os/winnt/user/

Henry

On 24.10.2010 04:35, wrote Miller, Shao:
> Thanks, Yin.
>
> Right now, the coLinux .EXEs have dependencies on the Win32
sub-system; they use the Win32 API, whether run as a service or not.
For example, the top of the process tree on Windows XP might look
something like:
>
> - System
>    - SMSS.EXE (Session Manager)
>      - CSRSS.EXE (Client Server Runtime)
>      - WinLogon.EXE (Windows NT Logon)<- Win32-dependent
>        - Services.EXE (Services and Controller)<- Win32-dependent
>        - LSASS.EXE (LSA Shell)<- Win32-dependent
>
> I believe that all [non-driver] services are Win32 applications
spawned by Services.EXE.  The minimal environment I'm interested in is:
>
> - System
>    - XXX.EXE
>
> where XXX.EXE is a "native" executable which does some of whatever
colinux-daemon.exe does...  Starts up a Linux and sits there.  It'd
possibly need to do some of whatever the other colinux-*-daemon.exe
programs do, in order to facilitate networking for the hosted Linux.
>
> I'm wondering now if the Win32 dependencies are huge or if it might be
relatively straight-forward to port the daemons to use the native API.
>
> - Shao Miller
>
> -----Original Message-----
> From: yin sun [mailto:sun...@gm...]
> Sent: Saturday, October 23, 2010 21:18
> To: Miller, Shao
> Cc: col...@li...
> Subject: Re: [coLinux-users] Native-Mode versus Win32
>
> don't know much about how windows separate the subsystem, looking at
> the code inside kernel to see what is part of win32.
> the user part can be removed completely in service mode.
>
> /Yin
>
> On Sat, Oct 23, 2010 at 12:28 PM, Miller, Shao
> <sha...@yr...>  wrote:
>> Good day to All,
>>
>>
>>
>> coLinux is very nice.
>>
>>
>>
>> I'm interested in the possibility of utilizing it in an environment
without
>> the Win32 subsystem.  This would be an environment with little more
than the
>> NT kernel, network, block and other NT drivers.
>>
>>
>>
>> Since the various coLinux daemons and network-controlling
applications are
>> Win32 executables, I'm wondering if there's any chance at all that
their
>> functions could run solely in a "native" environment without the
Win32
>> subsystem available.  There needn't be any user interface at all; the
idea
>> is for a "headless" Windows with coLinux facilitating a Linux and
making
>> that Linux available on the network.
>>
>>
>>
>> Does this seem remotely possible?
>>
>>
>>
>> Thank you for your time, and for coLinux!
>>
>>
>>
>> - Shao Miller

Re: [coLinux-users] Native-Mode versus Win32

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

  Hello Shao,

I don't know why you ask, this. First: Win32 is the complete Windows 
user land API. You means that? You means without GUI and so, than you 
would need to run coLinux without some basic DLLs, for example without 
user32.dll, gdi32.dll?

This is the list of all used DLL:
'user32', 'gdi32', 'ws2_32', 'ntdll', 'kernel32', 'ole32', 'uuid', 
'msvcrt', 'crtdll', 'shlwapi'.

You say, only kernel function can use? Then only kernel32.dll would be 
leave? I think, that is to little.
Without Session Manager you would have no other task, no winlogon, no 
other windows task. So, and way we should this run now? If you all of 
the windows GUI have removed, then I would say: Better start Linux natively.

By the way the most things does the linux.sys, and this use only kernel 
DLLs ndis, ntoskrnl and hal. The colinux-daemon is only a loader to 
start Linux from inside the kernel driver, and later the monitor of 
running Linux task. colinux-daemon.exe send some ioctl to the kernel 
driver. The Win32 functions are for reading files and manage the task 
switch (WaitForMultipleObjects), and of curse for inter process 
communication base between the other colinux-*-daemon's (data pipe).

Please check files in src/colinux/os/winnt/user/*.c and 
src/colinux/os/winnt/user/daemon/*.c to see what API functions are used
http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/src/colinux/os/winnt/user/

Henry

On 24.10.2010 04:35, wrote Miller, Shao:
> Thanks, Yin.
>
> Right now, the coLinux .EXEs have dependencies on the Win32 sub-system; they use the Win32 API, whether run as a service or not.  For example, the top of the process tree on Windows XP might look something like:
>
> - System
>    - SMSS.EXE (Session Manager)
>      - CSRSS.EXE (Client Server Runtime)
>      - WinLogon.EXE (Windows NT Logon)<- Win32-dependent
>        - Services.EXE (Services and Controller)<- Win32-dependent
>        - LSASS.EXE (LSA Shell)<- Win32-dependent
>
> I believe that all [non-driver] services are Win32 applications spawned by Services.EXE.  The minimal environment I'm interested in is:
>
> - System
>    - XXX.EXE
>
> where XXX.EXE is a "native" executable which does some of whatever colinux-daemon.exe does...  Starts up a Linux and sits there.  It'd possibly need to do some of whatever the other colinux-*-daemon.exe programs do, in order to facilitate networking for the hosted Linux.
>
> I'm wondering now if the Win32 dependencies are huge or if it might be relatively straight-forward to port the daemons to use the native API.
>
> - Shao Miller
>
> -----Original Message-----
> From: yin sun [mailto:sun...@gm...]
> Sent: Saturday, October 23, 2010 21:18
> To: Miller, Shao
> Cc: col...@li...
> Subject: Re: [coLinux-users] Native-Mode versus Win32
>
> don't know much about how windows separate the subsystem, looking at
> the code inside kernel to see what is part of win32.
> the user part can be removed completely in service mode.
>
> /Yin
>
> On Sat, Oct 23, 2010 at 12:28 PM, Miller, Shao
> <sha...@yr...>  wrote:
>> Good day to All,
>>
>>
>>
>> coLinux is very nice.
>>
>>
>>
>> I'm interested in the possibility of utilizing it in an environment without
>> the Win32 subsystem.  This would be an environment with little more than the
>> NT kernel, network, block and other NT drivers.
>>
>>
>>
>> Since the various coLinux daemons and network-controlling applications are
>> Win32 executables, I'm wondering if there's any chance at all that their
>> functions could run solely in a "native" environment without the Win32
>> subsystem available.  There needn't be any user interface at all; the idea
>> is for a "headless" Windows with coLinux facilitating a Linux and making
>> that Linux available on the network.
>>
>>
>>
>> Does this seem remotely possible?
>>
>>
>>
>> Thank you for your time, and for coLinux!
>>
>>
>>
>> - Shao Miller

Re: [coLinux-users] Native-Mode versus Win32

[Miller, S. <sha...@yr...>]

Thanks, Yin.

Right now, the coLinux .EXEs have dependencies on the Win32 sub-system; they use the Win32 API, whether run as a service or not.  For example, the top of the process tree on Windows XP might look something like:

- System
  - SMSS.EXE (Session Manager)
    - CSRSS.EXE (Client Server Runtime)
    - WinLogon.EXE (Windows NT Logon) <- Win32-dependent
      - Services.EXE (Services and Controller) <- Win32-dependent
      - LSASS.EXE (LSA Shell) <- Win32-dependent

I believe that all [non-driver] services are Win32 applications spawned by Services.EXE.  The minimal environment I'm interested in is:

- System
  - XXX.EXE

where XXX.EXE is a "native" executable which does some of whatever colinux-daemon.exe does...  Starts up a Linux and sits there.  It'd possibly need to do some of whatever the other colinux-*-daemon.exe programs do, in order to facilitate networking for the hosted Linux.

I'm wondering now if the Win32 dependencies are huge or if it might be relatively straight-forward to port the daemons to use the native API.

- Shao Miller

-----Original Message-----
From: yin sun [mailto:sun...@gm...] 
Sent: Saturday, October 23, 2010 21:18
To: Miller, Shao
Cc: col...@li...
Subject: Re: [coLinux-users] Native-Mode versus Win32

don't know much about how windows separate the subsystem, looking at
the code inside kernel to see what is part of win32.
the user part can be removed completely in service mode.

/Yin

On Sat, Oct 23, 2010 at 12:28 PM, Miller, Shao
<sha...@yr...> wrote:
> Good day to All,
>
>
>
> coLinux is very nice.
>
>
>
> I'm interested in the possibility of utilizing it in an environment without
> the Win32 subsystem.  This would be an environment with little more than the
> NT kernel, network, block and other NT drivers.
>
>
>
> Since the various coLinux daemons and network-controlling applications are
> Win32 executables, I'm wondering if there's any chance at all that their
> functions could run solely in a "native" environment without the Win32
> subsystem available.  There needn't be any user interface at all; the idea
> is for a "headless" Windows with coLinux facilitating a Linux and making
> that Linux available on the network.
>
>
>
> Does this seem remotely possible?
>
>
>
> Thank you for your time, and for coLinux!
>
>
>
> - Shao Miller
>
> ------------------------------------------------------------------------------
> Nokia and AT&T present the 2010 Calling All Innovators-North America contest
> Create new apps & games for the Nokia N8 for consumers in  U.S. and Canada
> $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
> Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store
> http://p.sf.net/sfu/nokia-dev2dev
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>
>

Re: [coLinux-users] Native-Mode versus Win32

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

don't know much about how windows separate the subsystem, looking at
the code inside kernel to see what is part of win32.
the user part can be removed completely in service mode.

/Yin

On Sat, Oct 23, 2010 at 12:28 PM, Miller, Shao
<sha...@yr...> wrote:
> Good day to All,
>
>
>
> coLinux is very nice.
>
>
>
> I’m interested in the possibility of utilizing it in an environment without
> the Win32 subsystem.  This would be an environment with little more than the
> NT kernel, network, block and other NT drivers.
>
>
>
> Since the various coLinux daemons and network-controlling applications are
> Win32 executables, I’m wondering if there’s any chance at all that their
> functions could run solely in a “native” environment without the Win32
> subsystem available.  There needn’t be any user interface at all; the idea
> is for a “headless” Windows with coLinux facilitating a Linux and making
> that Linux available on the network.
>
>
>
> Does this seem remotely possible?
>
>
>
> Thank you for your time, and for coLinux!
>
>
>
> - Shao Miller
>
> ------------------------------------------------------------------------------
> Nokia and AT&T present the 2010 Calling All Innovators-North America contest
> Create new apps & games for the Nokia N8 for consumers in  U.S. and Canada
> $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
> Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store
> http://p.sf.net/sfu/nokia-dev2dev
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>
>

Re: [coLinux-users] Where is coLinux-0.8.0?

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

  Hello Hiroki
On 23.10.2010 05:35, Hiroki Horiuchi wrote:
> Hello.
>
> I happened to find version 0.8.0.1370 of colinux-daemon.exe in
> Portable_Ubuntu_TRES.exe but I can only find version 0.7.8.1505 of
> colinux-daemon.exe in devel-coLinux-20100727.exe.
>
> Where is coLinux-0.8.0?

coLinux 0.8.0.1370 was a developer version, that is now released as 
version 0.7.8
Please get downloads from
https://sourceforge.net/projects/colinux/files/coLinux-stable/0.7.8-linux-2.6.33.5 
or
http://www.henrynestler.com/colinux/releases/0.7.8/

-- 
Henry N.