colinux-users — coLinux users mailing list

Re: [coLinux-users] System.map for colinux kernel?

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

Frederick Akalin wrote:
> Gentoo is complaining about not finding System.map.  I know the warning 
> is harmless, although I would like to shut it up.  Would anyone know 
> where to get a copy for the colinux kernel?  Neither the base gentoo nor 
> the initrd images contain them.

kernel file vmlinux is not stripped.  Try to use the output from nm:
   nm vmlinux > System.map

-- 
Henry Nestler

[coLinux-users] System.map for colinux kernel?

[Frederick A. <ak...@ak...>]

Gentoo is complaining about not finding System.map.  I know the warning 
is harmless, although I would like to shut it up.  Would anyone know 
where to get a copy for the colinux kernel?  Neither the base gentoo nor 
the initrd images contain them.

Frederick Akalin

Re: [coLinux-users] Colinux Start

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

tj...@we... wrote:
> Hi,
>
> I have installed Colinux but I cannot run it, what do I need to do?
> Please help.
>   

A great place to start is the docs in the wiki :)

http://wiki.colinux.org/wiki/Main_Page

The two few entries in "getting started" should prove particularly helpful.

Jason

[coLinux-users] Colinux Start

[<tj...@we...>]

Hi,

I have installed Colinux but I cannot run it, what do I need to do?
Please help.

Thanks.


-------------------------------------------
For super low premiums, click here http://www.webmail.co.za/dd.pwm

Re: [coLinux-users] boot from seperate physical drive

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

On 9/19/06, Michelangelo <mic...@gm...> wrote:

> partition. As for the kernel Aand the initrd, you have to specify the ones
> shipped with colinux (or recompile a new one with colinux patches, a feat
> which I'd like to have some feedback on), obviously using paths relative to
> yr windows install.

Yes, always use the colinux kernel, the initrd for coLinux is more or
less options, if you don't use it or if it fails to do what it's
designed to do, you can avoid it's use by manually unarchiving the
contents of vmlinux-modules.tar.gz from the colinux install directory
into the root partition on SuSe 10.1 (basically initrd just tries to
automagically install the colinux kernel modules for you)

What specifically about compiling your own kernel did you want/need
feedback on.  I do this regularly as do many users.  There are a few
'gotchas' you have to be aware of though.

-- 
George

Re: [coLinux-users] boot from seperate physical drive

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

Holger Krull wrote:
> Kristopher Yates schrieb:
> 
>> I would like to run this software but can't figure out how to config the XML 
>> properly.  Can anyone help?  Here is my configuration:
>>
>> I use Suse 10.1 w/ grub.  This is on my primary master drive.  WinXP is on 
>> my primary slave drive.
>>
>> /dev/hda1 = swap
>>
>> /dev/hda2 = root
>>
>> /boot/vmlinuz is my kernel location.
> 
> First: Do you want to boot your existing Suse 10.1 in colinux?
> Which colinux version do you use?
> 
> The kernel that gets started with colinux will always be the colinux kernel, not the suse kernel.
> The config for the raw device access most likely will be 
> <block_device index="0" path="\Device\Harddisk0\Partition1" enabled="true"/> 
> <block_device index="1" path="\Device\Harddisk0\Partition2" enabled="true"/>
> 
> But i don't know if the partition numbering starts at 0 or 1.
> 
> Look at http://wiki.colinux.org/wiki/WindowsDevicePaths

With your informatitions about your disk, it's better to set the index 
for your hdaX to the same index as your native installation, than the 
cobdX is the same as hdaX.  And better, you use alias to real hdaX, that 
makes the /etc/fstab more easy.

This should work for you (coLinux 0.6.4):

<?xml version="1.0" encoding="UTF-8"?>
<colinux>
     <!-- cobd1 is your SWAP partition -->
     <block_device index="1" path="\Device\Harddisk0\Partition1"
     alias="hda1" enabled="true" />

     <!-- cobd2 is your SuSE Root -->
     <block_device index="2" path="\Device\Harddisk0\Partition2"
     alias="hda2" enabled="true" />

     <!-- Define your Root partition (not the Boot) -->
     <!-- Lets start a runlevel without graphic -->
     <bootparams>root=/dev/hda2 ro init 3</bootparams>

     <!-- Initial RamDISK (initrd) and Kernel from coLinux -->
     <initrd path="initrd.gz" />
     <image path="vmlinux" />

     <!-- this line allows you to specify the amount of memory
          available to coLinux -->
     <memory size="128" />
</colinux>

This all is in assumtion, that you would run your native Linux under 
colinux.  Is this right?

Please remember, that you need some changes on boot scripts in your 
SuSE, before it would be run properly.  Follow the title in wiki:

http://wiki.colinux.org/wiki/Converting_Distributions
http://wiki.colinux.org/wiki/Dual_boot_system#Skipping_some_scripts_under_coLinux_boot

-- 
Henry Nestler

Re: [coLinux-users] boot from seperate physical drive

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

Please ignore previous mail, some mistakes there. follows correct command
line


 kernel=c:\colinux\vmlinux initrd=c:\colinux\initrd.gz root=/dev/cobd/0
> cobd0=\Device\HardDisk0\Partition1
>
> Syntax to use when starting colinux via commandline parameters. Just adapt
> it for yr XML. It starts colinux using first partition of first hard disk as
> root partition. As for the kernel and the initrd, you have to specify the
> ones shipped with colinux (or recompile a new one with colinux patches, a
> feat which I'd like to have some feedback on), obviously using paths
> relative to yr windows install.
> If I'm not horribly mistaken, disk numbering starts at 0, partition
> numbering starts at 1 (it is windows naming schema).
>
> Ciao
> Michelangelo
>
>
>
> On 9/19/06, Kristopher Yates <kri...@ho...> wrote:
> >
> > Hi
> >
> > I would like to run this software but can't figure out how to config the
> > XML
> > properly.  Can anyone help?  Here is my configuration:
> >
> > I use Suse 10.1 w/ grub.  This is on my primary master drive.  WinXP is
> > on
> > my primary slave drive.
> >
> > /dev/hda1 = swap
> >
> > /dev/hda2 = root
> >
> > /boot/vmlinuz is my kernel location.
> >
> >
> > Normally, I boot up to the grub boot-loader screen.  I can select linux
> > or
> > XP.  Each OS is on its own seperate physical hard drive.
> >
> > Thank you,
> >
> > Kris
> >
> > _________________________________________________________________
> > Be seen and heard with Windows Live Messenger and Microsoft LifeCams
> >
> > http://clk.atdmt.com/MSN/go/msnnkwme0020000001msn/direct/01/?href=http://www.microsoft.com/hardware/digitalcommunication/default.mspx?locale=en-us&source=hmtagline
> >
> >
> > -------------------------------------------------------------------------
> >
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to share
> > your
> > opinions on IT & business topics through brief surveys -- and earn cash
> >
> > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> > _______________________________________________
> > coLinux-users mailing list
> > coL...@li...
> > https://lists.sourceforge.net/lists/listinfo/colinux-users
> >
>
>

Re: [coLinux-users] boot from seperate physical drive

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

 kernel=c:\colinux\vmlinux initrd=c:\colinux\initrd.gz
kernel=c:\colinux\vmlinux root=/dev/cobd/0
cobd0=\Device\HardDisk0\Partition1

Syntax using  when using commandline parameters. Just adapt it for yr XML.
It starts colinux using first partition of first hard disk as root
partition. As for the kernel Aand the initrd, you have to specify the ones
shipped with colinux (or recompile a new one with colinux patches, a feat
which I'd like to have some feedback on), obviously using paths relative to
yr windows install.
If I'm not horribly mistaken, Disk numbering starts at 0, partition
numbering starts at 1 (it is windows naming schema).

Ciao
Michelangelo


On 9/19/06, Kristopher Yates <kri...@ho...> wrote:
>
> Hi
>
> I would like to run this software but can't figure out how to config the
> XML
> properly.  Can anyone help?  Here is my configuration:
>
> I use Suse 10.1 w/ grub.  This is on my primary master drive.  WinXP is on
> my primary slave drive.
>
> /dev/hda1 = swap
>
> /dev/hda2 = root
>
> /boot/vmlinuz is my kernel location.
>
>
> Normally, I boot up to the grub boot-loader screen.  I can select linux or
> XP.  Each OS is on its own seperate physical hard drive.
>
> Thank you,
>
> Kris
>
> _________________________________________________________________
> Be seen and heard with Windows Live Messenger and Microsoft LifeCams
>
> http://clk.atdmt.com/MSN/go/msnnkwme0020000001msn/direct/01/?href=http://www.microsoft.com/hardware/digitalcommunication/default.mspx?locale=en-us&source=hmtagline
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>

Re: [coLinux-users] boot from seperate physical drive

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

Kristopher Yates schrieb:

> I would like to run this software but can't figure out how to config the XML 
> properly.  Can anyone help?  Here is my configuration:
> 
> I use Suse 10.1 w/ grub.  This is on my primary master drive.  WinXP is on 
> my primary slave drive.
> 
> /dev/hda1 = swap
> 
> /dev/hda2 = root
> 
> /boot/vmlinuz is my kernel location.

First: Do you want to boot your existing Suse 10.1 in colinux?
Which colinux version do you use?

The kernel that gets started with colinux will always be the colinux kernel, not the suse kernel.
The config for the raw device access most likely will be 
<block_device index="0" path="\Device\Harddisk0\Partition1" enabled="true"/> 
<block_device index="1" path="\Device\Harddisk0\Partition2" enabled="true"/>

But i don't know if the partition numbering starts at 0 or 1.

Look at http://wiki.colinux.org/wiki/WindowsDevicePaths

[coLinux-users] boot from seperate physical drive

[Kristopher Y. <kri...@ho...>]

Hi

I would like to run this software but can't figure out how to config the XML 
properly.  Can anyone help?  Here is my configuration:

I use Suse 10.1 w/ grub.  This is on my primary master drive.  WinXP is on 
my primary slave drive.

/dev/hda1 = swap

/dev/hda2 = root

/boot/vmlinuz is my kernel location.


Normally, I boot up to the grub boot-loader screen.  I can select linux or 
XP.  Each OS is on its own seperate physical hard drive.

Thank you,

Kris

_________________________________________________________________
Be seen and heard with Windows Live Messenger and Microsoft LifeCams 
http://clk.atdmt.com/MSN/go/msnnkwme0020000001msn/direct/01/?href=http://www.microsoft.com/hardware/digitalcommunication/default.mspx?locale=en-us&source=hmtagline

Re: [coLinux-users] Support of other devices with coLinux

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

Jonathan Malton wrote:
> I would like to use coLinux for development that includes a USB device.
> Is there any support for generic access to devices other than NICs yet?
> I saw some indication that this was in the roadmap, but I think it was
> fairly old, and I'm hopeful that some support is now available.
> 
> Specifically, I'm using WinXP Pro, and want to talk to a BlueTooth USB
> module from Linux.

This would not work.  There exist no drivers currently and not planed.

-- 
Henry Nestler

Re: [coLinux-users] Howto - Installing Gentoo in coLinux (was Re: Does colinux work with gentoo 2006.1?)

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

Jason:
Thank you for the long and complete guide. People like me would get lost without these helps. You really should put it into the colinux wiki. I don't think there is one that is as good.

I actually did a fresh installation pretty much as your description, and installed the necessory software again. It seems that the problem is my old 2006.0 cannot be update into 2006.1. I remmember when I updated it from 2005 to 2006 I did nothingg special at all. but this time I was forced to do a fresh installation. I think some how it is related to gcc 3.4 to 4.1 upgrade.

Bing

Re: [coLinux-users] Enable config_hotplug in kernel .config

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

=20

>=20
> On 9/9/06, Ron Helzer <he...@gm...> wrote:
> > I enabled config_hotplug and the kernel compiled and worked=20
> fine, but it
> > didn't solve my problem of no /dev/net/tun device file upon=20
> modprobing the
> > tun module.  I am not a hotplug or udev guru, I'm a devfs=20
> kind of guy, so I
> > may be doing something else wrong.  I decided once I was=20
> able to customize
> > the coLinux kernel, instead of modular tun and hotplug=20
> nonsence I would just
> > make tun part of the kernel and that fixed it for good.
>=20
> I'm no good with udev either. Sorry!  I wasn't even ever good at
> devfs...  I tend to manually create and maintain my /dev
> directories...  I know... I know...  For me it works and it's a big
> deal.
>=20

I can attest that hotplug is needed (in my experience) with >2.6.15
kernels to get any signals from the kernel to the udev daemon
on startup. Otherwise your udev managed /dev ends up with only a
handfull of entries.=20

/Anders

Re: [coLinux-users] Enable config_hotplug in kernel .config

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

On 9/9/06, Ron Helzer <he...@gm...> wrote:
> I enabled config_hotplug and the kernel compiled and worked fine, but it
> didn't solve my problem of no /dev/net/tun device file upon modprobing the
> tun module.  I am not a hotplug or udev guru, I'm a devfs kind of guy, so I
> may be doing something else wrong.  I decided once I was able to customize
> the coLinux kernel, instead of modular tun and hotplug nonsence I would just
> make tun part of the kernel and that fixed it for good.

I'm no good with udev either. Sorry!  I wasn't even ever good at
devfs...  I tend to manually create and maintain my /dev
directories...  I know... I know...  For me it works and it's a big
deal.

> I would like to know if what I was attempting with hotplug is possible in
> coLinux and where I went wrong.  If I find the time, I'll boot a test
> instance and look into it more fully.

I'm not 100%, but I believe we disabled it is because with it enabled,
some distros (Fedora?, Ubuntu? mabye) would crash/die on boot-up
because they where trying to access hardware directly with hotplug,
which is always a bad thing in coLinux.  I'll play with hotplug
enabled a default and a few distros and see what comes of it.

-- 
George

Re: [coLinux-users] Enable config_hotplug in kernel .config

[Ron H. <he...@gm...>]

I enabled config_hotplug and the kernel compiled and worked fine, but it
didn't solve my problem of no /dev/net/tun device file upon modprobing the
tun module.  I am not a hotplug or udev guru, I'm a devfs kind of guy, so I
may be doing something else wrong.  I decided once I was able to customize
the coLinux kernel, instead of modular tun and hotplug nonsence I would just
make tun part of the kernel and that fixed it for good.

I am running Gentoo in my coLinux, and they provide an option in
/etc/conf.d/rc to tar the contents of the /dev tempfs to be restored at next
boot which would also solve the problem if you makedev the /dev/net/tun
device yourself.

I would like to know if what I was attempting with hotplug is possible in
coLinux and where I went wrong.  If I find the time, I'll boot a test
instance and look into it more fully.

Ron Helzer
he...@gm...

On 9/9/06, George P Boutwell <geo...@gm...> wrote:
>
> Let us know how your custom kernel goes...  If you don't experience
> too many problems with it enabled, then we can test it and see how it
> makes out.
>
> On 9/9/06, Ron Helzer <he...@gm...> wrote:
> > I am in the process of building a custom kernel for use with coLinux to
> > enable hotplug support.  I am assuming  that since coLinux prevents
> > interaction directly with the hosts hardware, hotplug support was deemed
> > unnecessary.
> >
> > However, devices such as /dev/net/tun need hotplug support to work
> properly
> > with udev.  May I suggest that future coLinux default kernel
> configurations
> > have config_hotplug enabled?
>
> --
> George
>

Re: [coLinux-users] Enable config_hotplug in kernel .config

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

Let us know how your custom kernel goes...  If you don't experience
too many problems with it enabled, then we can test it and see how it
makes out.

On 9/9/06, Ron Helzer <he...@gm...> wrote:
> I am in the process of building a custom kernel for use with coLinux to
> enable hotplug support.  I am assuming  that since coLinux prevents
> interaction directly with the hosts hardware, hotplug support was deemed
> unnecessary.
>
> However, devices such as /dev/net/tun need hotplug support to work properly
> with udev.  May I suggest that future coLinux default kernel configurations
> have config_hotplug enabled?

-- 
George

[coLinux-users] Enable config_hotplug in kernel .config

[Ron H. <he...@gm...>]

I am in the process of building a custom kernel for use with coLinux to
enable hotplug support.  I am assuming  that since coLinux prevents
interaction directly with the hosts hardware, hotplug support was deemed
unnecessary.

However, devices such as /dev/net/tun need hotplug support to work properly
with udev.  May I suggest that future coLinux default kernel configurations
have config_hotplug enabled?

Ron Helzer
he...@gm...

[coLinux-users] JP Fortin is out of the office.

[<JP...@op...>]

I will be out of the office starting  09/08/2006 and will not return until
09/11/2006.

I will respond to your message when I return.

[coLinux-users] Support of other devices with coLinux

[Jonathan M. <jm...@in...>]

Hello

I would like to use coLinux for development that includes a USB device.
Is there any support for generic access to devices other than NICs yet?
I saw some indication that this was in the roadmap, but I think it was
fairly old, and I'm hopeful that some support is now available.

Specifically, I'm using WinXP Pro, and want to talk to a BlueTooth USB
module from Linux.

[ from http://www.gentoo.org/doc/en/colinux-howto.xml ::

coLinux emulates each type of hardware needed. You have emulated disk
access, networking, etc. What isn't available yet are USB, direct
graphics, or soundcard access. The good news is that coLinux is
currently working on getting USB working (excluding USB keyboards and
mice).=20
]


Jonathan Malton

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

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

I thought I'd give an update on this. IT seems that, occasionally, the
TAP drive seems to take a long time to "connect" between the coLinux
module/driver and the Windows driver. Every time this has happened,
within about 5 minutes at most, things are actually working correctly.

I do not know what causes the delay, and further, only seems to be, so
far, observed shortly after installation. After a few days, this went
away and has not resurfaced for about a week.

Just bit of oddness for your day.

Jason

Jason Ahrens wrote:
> 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.
>   

[coLinux-users] Howto - Installing Gentoo in coLinux (was Re: Does colinux work with gentoo 2006.1?)

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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
It was actually fairly easy. Note that these instructions will
reference chapter/section numbers from the 2006.1 installation
handboot, however I will try to provide enough context by including
the section name that this should be usable in the future with very
little modification.

Note that these instructions assume you know what you're doing with a
Gentoo install, and that you have enough knowledge of how coLinux
works that you won't need help modifying or creating the configuration
file.

1) Install coLinux with the gentoo image download it provides. This
may work with the debian image, but I didn't try it.

2) On your Windows file system, in the directory you want to store
your coLinux image, create your root and swap files. I made a 10G root
and 256M swap. There is a (mis-named) wiki on how to create files
suitable for coLinux block devices. see
http://wiki.colinux.org/wiki/HowtoCreateSwapFile
   a) Be aware that fsutil (XP and later) makes spares files. This
means the first time you write data to a block it takes longer than
subsequent times. ie: your mkfs is going to take longer than you think
;) Ditto for the first time you start writing out files and using
swap. To avoid this, don't use sparse files. Personally, I didn't mind
as sparse files are instant-create and let me continue with setting up
coLinux without waiting for large files to be initialize and written
to and performance hit for 'first use' isn't terrible.

3) Edit your coLinux config files to recognize your "new" root and
swap as if they were /dev/cobd2 and and /dev/cobd3

4) Boot coLinux using the Linux image you downloaded.

5) Start following the installation guide at
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml. There are only
a few minor differences that need to be made:
   a) In section 4.c (Using fdisk to Partition your Disk), You don't
partition your "virtual" disk. If you want separate "partitions" use
multiple files on the Windows side.
   b) In section 4.d (Creating Filesystems), I use reiserfs on my
virtual disk. I had to download and compile the reiserfstools (for v3)
into my non-chroot environment as they were not part of the initial
image. This is trivial. They are available from
http://www.namesys.com/ and you don't even have to do the full
install, just get to the point where you have mkreiserfs available.
   c) In sections 5.b/5.c (installting the initial stage tarball)
Getting the stage tarball has multiple options:
      i) If your network is set up to access the internet, section 5.b
(Using a Stage from the Internet) works perfectly.
      ii) If you are instead using section 5.c (Using a Stage from the
Installation CD), you can use scp to transfer the stage tarball to the
coLinux installation if you have networking enabled, but not set up
for Internet use.
      iii) Another option if using 5.c is to mount your CD drive in
coLinux itself for use. See http://wiki.colinux.org/wiki/CdDvdAccess
   d) Section 7.b (Installing the Sources), it's still safe to install
kernel sources (may even be required for some things you want to
install later) but don't compile your own kernel! See the next point.
   e) Section 7.c/7.d (Detailing two different methods of kernel
configuration), don't do this! Use the kernel and modules that came
with the initial image you downloaded. The kernel itself is kept on
the filesystem in your Windows boot. To  "install" the kernel modules,
do this from your non-chrooted installation image:
      # mkdir -p /mnt/gentoo/lib/modules
      # tar -cf - /lib/modules | (cd /mnt/gentoo/lib/modules;tar xvpf -)
   f) Section 8.a (Filesystem Information), make sure to set up your
fstab with the /dev/cobd devices that they *will be* in your final
image (ie: root as /dev/cobd1, swap as /dev/cobd2) not what they are
*now*.
   g) Chapter 10 (Configuring the Bootloader),. You don't need a boot
loader. I installed grub anyway just in case something in the future
insisted on having a bootloader around, but I did not configure it.

And that's really about it! The rest of the install is identical to
the installation guide. Once you get done, shutdown your coLinux
Gentoo install image, modify or create a new config file for coLinux
to point the block devices to your new root/swap, and start it up again!

Enjoy your new coLinux setup! I've actually used this procedure
through many iterations of Gentoo releases whenever I did a windows
re-install for whatever reasons, so these are not specific to 2006.1
(however chapter/section numbers may change between releases)

Another useful note is you may want to comment-out or remove:
<initrd path="initrd.gz" />

from your config file. For some reason, some people report that using
the initrd causes coLinux to only boot properly every second time (I
was one of them, until I found this).

This may be useful to wiki-ize, but I found multiple Gentoo Howtos'
already on the Wiki. If people think it's worthwhile to create yet
another one I can.

Jason

Bing Wen wrote:
> Did you start from scratch or update from a running installation?
> Would you please describe the procedure you switched to 2006.1?
>
> Bing
>
> */Jason <ja...@co...>/* wrote:
>
>     I am using 2006.1 successfully. The only thing I did different
>     from a
>     'regular' gentoo install was copy the modules from the provided
>     Gentoo
>     coLinux image to my new system, so I am using the provided Linux
>     kernel
>     and modules, I did not try to compile my own.
>
>     Jason
>
>
>
> ----------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>
> ----------------------------------------------------------------------
>
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
 
iD8DBQFFAanLy+4gAFBGLZIRAgSEAJ4ijNMRNSaOtfs8oIyZgg5jPQQ3bACeL0c8
0N2U8q0EW/LsDK9VkisxeII=
=H0Av
-----END PGP SIGNATURE-----

[coLinux-users] changes from 2.6.15 to 2.6.16

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

Hello Anders,

last weeks I have read and grep into Linux kernels, and read all changes
between vanilla kernel 2.6.15 and 2.6.17, with my eyes on the file
arch/i386/kernel/cpu/common.c

I no found a running way behind yours 2.6.15

Please see this boot functions flow, I will comment now:

--- view this flow with fixed font ---
inside Kernel:
c010cde0 <co_start>:
     call co_start_arch (label for first switch from windows)
         call co_early_cpu_init (setup a GDT)
         call co_start_kernel (kernel/cooperative.c)
             loads Parameters from passage page
             call co_arch_start_kernel
                 call co_startup_entry (i386/kernel/head.S, skip behind
"setup_idt()", loads gdt,lgt,idt )
                     call start_kernel (init/main.c)
                         boot_cpu_init
                         page_address_init
                         printk(linux_banner)
                         call setup_arch (arch/i386/kernel/setup.c)
                             pre_setup_arch_hook
                             early_cpu_init
                                 cpu_init
                             setup_memory
                             paging_init
                             register_memory (!colinux)
                         setup_per_cpu_areas
             co_terminate(CO_TERMINATE_END)
--- end flow ---

1. The main problem is the function "co_early_cpu_init()"
(arch/i386/kernel/cooperative.c).  This function sets the GDT and some
more memory registers to exact the same GTD, that later will be used in
function "cpu_init()" (arch/i386/kernel/cpu/common.c).

2. Function "co_early_cpu_init()" has no support for memory alloc, you
can not use printk.  You can not use alloc_bootmem_pages, and not
get_zeroed_page, but kernel >= 2.6.16 needs this.

3. The GDT must be set on this place, because the function
"co_start_kernel()" use memory pointers to get the boot parameter values
from the passage memory.

4. The ugly thing: On "co_startup_entry" (arch/i386/kernel/head.S) the
GDT will be replace with a fixed GDT from unchangable code
"cpu_gdt_table" in the assmbler booting steps.

5. Some there, the memory mappings will be configured.

6. Then function "cpu_init()" (arch/i386/kernel/cpu/common.c) sets the
GDT to linux variable area and task structs.  Memory alloc and printk is
usable.


With the change on 2.6.16, the memory behind GDT is an allocatable page.
We can not alloc it in function "co_early_cpu_init()".  Can not give the
same GDT in fuction "co_early_cpu_init()" and "cpu_init()".


My ideas:

Remove the function "co_early_cpu_init()" from C source.
Starts colinux (first from boot) directly some there in the head.S, near
the label "co_startup_entry".

Remove the function "co_start_kernel()" (kernel/cooperative.c), modify
directly such values in head.S from dolinux-daemon.exe on loading the
kernel.

OR:
Code parameters directly in some registers.  All registers are free.
Only one register is used for the passage page number.

Variables they needs are co_core_end, co_memory_size, co_initrd,
co_initrd_size, and command line.  This should be a struct on one label
in head.S
colinux-daemon should set the values.  A sample for using, is the label
"cpu_gdt_table".

OR:
Call "co_start_kernel()" before call "start_kernel()" from head.S

OR:
Why not inside head.S use "co_passage_page->params[0] ... [10+256]" and
copy the value to struct with elements "co_core_end, co_memory_size, ...
co_boot_parameters"?  See near entry "startup_32" in head.S, it's coping
the string "saved_command_line" from a real memory page.
"co_passage_page" is a fixed virtual adress (inside kernel).

Best way would be, if we can enter "startup_32" as booting.  For this
all registers should be set as lilo/grub does it.  Perhaps, we need some
very small patches on this assembler code.  The "startup_32" will be
jumped from arch/i386/boot/setup.S, this shows some notes about booting.
In the end we would have also a more linux boot and perhaps more opened
to use more as 1GB memory.

-- 
Henry Nestler

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

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

Did you start from scratch or update from a running installation? Would you please describe the procedure you switched to 2006.1?

Bing

Jason <ja...@co...> wrote: I am using 2006.1 successfully. The only thing I did different from a
'regular' gentoo install was copy the modules from the provided Gentoo
coLinux image to my new system, so I am using the provided Linux kernel
and modules, I did not try to compile my own.

Jason

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

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

emerge --sync

link make.profile to 2006.1

emerge -u gcc. it trys to pull in glibc 2.4 but will fail

gcc-config switch to gcc 4.1

emerge -u gcc again, now glibc 2.4 is compiled

emerge -e system && emerge -e world

reboot, no network! I've tried this on 3 machines. Failed miserably.


"Anders Eriksson C (KI/EAB)" <and...@er...> wrote:     Didn't  know there was 2006.1 profile out yet. I'll check it out.
  
 What  did you do exactly when you "tried to gcc 4.1.1 and glibc 2.4 "?
  
 Did  you just switch to the other profile? emerge -e system? emerge -e  world?
  
 /Anders
  

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

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

I am using 2006.1 successfully. The only thing I did different from a
'regular' gentoo install was copy the modules from the provided Gentoo
coLinux image to my new system, so I am using the provided Linux kernel
and modules, I did not try to compile my own.

Jason

Bing Wen wrote:
> 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?