colinux-users — coLinux users mailing list

Re: [coLinux-users] [coLinux-devel] Google Summer of Code 2008 - and the future of coLinux

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

David H. Lynch Jr. wrote:
> I lurk on this list.
>        When I work with windows desktops, I make heavy use of coLinux.
>        Mostly I work under Linux anymore so I use it less.
>        However one of my projects is a hosted embeded linux system on a
> PC Card.
>        I have been very intrigued at borrowing colinux ideas to provide
> my linux target,
>        with access to resources on the host - much the way colinux
> scarfs resources from windows.
> 
>        I have not been foloowing the lguest and paravirt_ops work within
> the kernel
>        is there a good reference or howto for further information ?

Yes. The kernel driver (similar to linux.sys):
http://lxr.linux.no/linux/drivers/lguest/
and the user land application, like coLinux exe-Daemons:
http://lxr.linux.no/linux/Documentation/lguest/

(Links are from Kernel 2.6.23, more recent exist in current Kernel)

-- 
Henry N.

[coLinux-users] Google Summer of Code 2008 - and the future of coLinux

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

Hallo,

have registered coLinux as Google Summer of Code™.
http://code.google.com/soc/2008/

The idea behind this, is to join into the official Linux kernel
mainline. "lguest" inside the Linux kernel use a "paravirt_ops" as entry
point and a hypercall as connection from guest to the host. All this
code is similar as we have in coLinux as "co_switch".

Official Linux kernel would never accept our current hacking. But we can
use the exist kernel entry points and port coLinux into. This would
better to following recent kernels in future and distribution with
kernels with paravirtualization enabled would be work out of the DVD/CD
installation.

-- 
Henry N.

[coLinux-users] Tenemos 90% vacancias libres en su regi&#243; n. ofrecerle entrar en este c&#237; rculo de elegidos.

[asjajjhahhsda9 <asj...@ya...>]

poamgora?"|"UFQVFOYMVOCUEonvyc

Re: [coLinux-users] help with networking

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

Richard D. Morey wrote:
> I've read several guides to getting this working, but to no avail. I 
> installed CoLinux 0.7.2 with the Ubuntu 6.06 image, and the OS boots 
> fine. I also installed WinPcap, and am trying to get coLinux configured 
> so that I can use the network. So far, nothing works. I've used 
> Wireshark to confirm that the net packets are being sent from Colimux, 
> but it looks like Colinux is not recognizing any responses.
> 
> So far, my configuration is eth0 - winPcap, and eth1 - taptun. I can't 
> get either working. Here are more details:
> 
> My wireless card is an Intel(R) PRO/Wireless 3945ABG, running on Vista 
> Home Premium.

Some wireless cards dosn't work with promiscous mode. Try to disable it:
ethX=pcap-bridge,<network connection name>,<MAC>,nopromisc
-------------------------------------------------^^^^^^^^^

Some cards dosn't send/receive packedt with badly checksum. Try to find
a parameter setting in the wireless adapter to disable checksum.

Vista has some more protections on receiving pings and packet injections
that don't match regulary ipaddress. Disable the firewall, and ask
google about "Vista ping".

-- 
Henry N.

Re: [coLinux-users] Fedora 7 and the display

[<Dav...@cs...>]

Hi Henry

If you start fedora under CoLinux and go to Administration -> Display

You should get display options.  But nothing happens.

D

-----Original Message-----
From: Henry Nestler [mailto:Hen...@Ar...] 
Sent: Tuesday, 11 March 2008 6:57 AM
To: Miron, David (LI, Armidale)
Cc: col...@li...
Subject: Re: [coLinux-users] Fedora 7 and the display

Dav...@cs... wrote:
> When I first installed colinux I think it was 0.7.1 I was able to set
> the display inside the fedora 7 colinux environment.  I could change
the
> background and resolution with no problem.  However, at some point it
> broke - not sure why and upgrading to colinux 0.7.2 has not fixed the
> problem.  Is tehr anyone out there that has a patch to fix the
problem?

I not know what you means. Never hear about such. Can you please give
more details? What should I do to force the bug?

-- 
Henry N.

Re: [coLinux-users] Re : iptables nat modules

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

Network exist, but it can be eth2, eth3, or highter.

Configure a unique MAC for all network interfaces, example:
eth0=tuntap,"Connexion coLinux interne",02:00:00:00:00:01
eth1=tuntap,"Connexion coLinux externe",02:00:00:00:00:02

Ones after upgrating from 0.7.2 to 0.8.x you needs to remove all entries
from /etc/udev/rules.d/z25_persistent-net.rules
Than reboot, and you have eth0 and eth1 again.

Read more about increasing networks in
"20071203-Snapshot -- ifconfig reports no networking"
http://sourceforge.net/tracker/index.php?func=detail&aid=1861876&group_id=98788&atid=622063


Jerome wrote:
> Ok I did a test. I upgraded from 7.3 so I uninstalled colinux, I installed the dev snapshot and installed the latest files as described.
> The good thing is the nat table is available now. The bad thing is my networking isn't working anymore.
> 
> I'm using 2 TAP virtual  network cards. The first one to build an internal private network and I bridge the second tap with my real ethernet adapter. colinux find the two adpters at startup but network configuration fails on eth0 (no such device) and eth1 doesn't seem to work (can't ping any host)
> 
> here is the statement I use for the network part :
> 
> eth0=tuntap,"Connexion coLinux interne"
> eth1=tuntap,"Connexion coLinux externe"
> 
> ----- Message d'origine ----
> De : Henry Nestler <Hen...@Ar...>
> À : Jerome <mar...@ya...>
> Cc : col...@li...
> Envoyé le : Lundi, 10 Mars 2008, 21h10mn 06s
> Objet : Re: [coLinux-users] iptables nat modules
> 
> Henry Nestler wrote:
>> Jerome wrote:
>>> I want to use colinux as an Internet firewall. I tried to configure iptables to do this but I can't define nat rules. (I got errors like "not existing nat table" error)
>>> So I'm thinking that there are missing iptables modules in the colinux kernel. Is it possible to include the nat module in the next build release please ?
> 
> Sorry, I was not viewing correctly your question.
> You are right, CONFIG_NF_NAT was not enabled.
> 
> Please try this build and give a feedback:
> 
> http://www.henrynestler.com/colinux/testing/devel-0.8.0/20080310-iptables-nat/
> 

-- 
Henry N.

Re: [coLinux-users] console-nt

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

Hello Paolo,

think, you have forgotten two lines with 79 and 24, the "values-1".
Have changed console size to 40x120. Hope, it is not to big now. ;-)

Here is the complete patch for coLinux 0.8.0:
http://www.henrynestler.com/colinux/patches/devel/console-size-40x120.patch
Should also be usable for 0.7.2/0.7.3, but not tested.

and a ready to use build with it:
http://www.henrynestler.com/colinux/testing/devel-0.8.0/20080310-con-40x120/

and a screenshot:
http://www.henrynestler.com/colinux/screenshoots/Console-size-40x120.png

Paolo Minazzi wrote:
> hi colinux developers and users.
> 
> I have two things to communicate (a post and a question)
> 
> 1)
> with the 0.7.1 if I use
> stty rows n , where n>25 , Windows crash
> This is not an important problem, but it is an error.
> I tried to understand where is the problem (into the source) but I wan
> unabile to do it. I'm sorry :=(
> 
> 2)
> I have tried to adjust the console-nt to have a larger console, for
> example 80x40.
> I have modified some lines in the code :
> 
> src/colinux/kernel/monitor.c:915:
>     rc = co_console_create(80, 40 /* 25 */ , 0, &cmon->console);  // BY PAOLO
> 
> src/colinux/os/linux/kernel/module/.module.kernel_build/monitor.c:915:
>     rc = co_console_create(80, 40 /* 25 */ , 0, &cmon->console);  // BY PAOLO
> 
> src/colinux/os/current/user/console-nt/widget.cpp:125
>     r.bottom = fs.Y * 40; // 25; BY PAOLO
> 
> src/colinux/os/current/user/console-nt/widget.cpp:141
>     size.Y = 40 ; // 25 ; PAOLO
> 
> ~/build/linux-2.6.22-source/drivers/video/console:63
>     c->vc_rows = 40; // 25; BY PAOLO
> 
> recompile all.
> Colinux on Win32 starts ok, but afterm some messages the system crash
> and my PC reboots.
> 
> I have searched something like "4000" (=80x25) or "8000" (=80*25*2,
> for char and attribute) but nothing.
> 
> I know that it is possbile use putty, but the console sometimes is more useful.
> If someone have ideas, please submit it.
> 
> Regards,
> Paolo Minazzi
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
> 

-- 
Henry N.

Re: [coLinux-users] iptables nat modules

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

Henry Nestler wrote:
> Jerome wrote:
>> I want to use colinux as an Internet firewall. I tried to configure iptables to do this but I can't define nat rules. (I got errors like "not existing nat table" error)
>> So I'm thinking that there are missing iptables modules in the colinux kernel. Is it possible to include the nat module in the next build release please ?
> 

Sorry, I was not viewing correctly your question.
You are right, CONFIG_NF_NAT was not enabled.

Please try this build and give a feedback:

http://www.henrynestler.com/colinux/testing/devel-0.8.0/20080310-iptables-nat/

-- 
Henry N.

Re: [coLinux-users] Fedora 7 and the display

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

Dav...@cs... wrote:
> When I first installed colinux I think it was 0.7.1 I was able to set
> the display inside the fedora 7 colinux environment.  I could change the
> background and resolution with no problem.  However, at some point it
> broke – not sure why and upgrading to colinux 0.7.2 has not fixed the
> problem.  Is tehr anyone out there that has a patch to fix the problem?

I not know what you means. Never hear about such. Can you please give
more details? What should I do to force the bug?

-- 
Henry N.

Re: [coLinux-users] iptables nat modules

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

Jerome wrote:
> I want to use colinux as an Internet firewall. I tried to configure iptables to do this but I can't define nat rules. (I got errors like "not existing nat table" error)
> So I'm thinking that there are missing iptables modules in the colinux kernel. Is it possible to include the nat module in the next build release please ?

iptables are enabled for coLinux 0.7.2, 0.7.3 and 0.8.0
Check, that you have modules installed right. If not, do it manualy:

  tar -xzf modules-*.tgz -C /

The modules you will find in your Windows installation path as file
vmlinux-modules.tar.gz

I don't know what you are missing. I have modules for iptables.
Perhaps you need an "modprobe ip_tables" or such things?

Try this in your running coLinux:

# zgrep IPTABLES < /proc/config.gz
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP6_NF_IPTABLES=m

# modprobe ip_tables
# lsmod
Module                  Size  Used by
ip_tables              12488  0
x_tables               15748  1 ip_tables

-- 
Henry N.

[coLinux-users] Fedora 7 and the display

[<Dav...@cs...>]

Hi all

 

When I first installed colinux I think it was 0.7.1 I was able to set
the display inside the fedora 7 colinux environment.  I could change the
background and resolution with no problem.  However, at some point it
broke - not sure why and upgrading to colinux 0.7.2 has not fixed the
problem.  Is tehr anyone out there that has a patch to fix the problem?

 

Kind regards

 

David

 

Dr David Miron

CSIRO

02 6776 1375

 

[coLinux-users] console-nt

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

hi colinux developers and users.

I have two things to communicate (a post and a question)

1)
with the 0.7.1 if I use
stty rows n , where n>25 , Windows crash
This is not an important problem, but it is an error.
I tried to understand where is the problem (into the source) but I wan
unabile to do it. I'm sorry :=(

2)
I have tried to adjust the console-nt to have a larger console, for
example 80x40.
I have modified some lines in the code :

src/colinux/kernel/monitor.c:915:
    rc = co_console_create(80, 40 /* 25 */ , 0, &cmon->console);  // BY PAOLO

src/colinux/os/linux/kernel/module/.module.kernel_build/monitor.c:915:
    rc = co_console_create(80, 40 /* 25 */ , 0, &cmon->console);  // BY PAOLO

src/colinux/os/current/user/console-nt/widget.cpp:125
    r.bottom = fs.Y * 40; // 25; BY PAOLO

src/colinux/os/current/user/console-nt/widget.cpp:141
    size.Y = 40 ; // 25 ; PAOLO

~/build/linux-2.6.22-source/drivers/video/console:63
    c->vc_rows = 40; // 25; BY PAOLO

recompile all.
Colinux on Win32 starts ok, but afterm some messages the system crash
and my PC reboots.

I have searched something like "4000" (=80x25) or "8000" (=80*25*2,
for char and attribute) but nothing.

I know that it is possbile use putty, but the console sometimes is more useful.
If someone have ideas, please submit it.

Regards,
Paolo Minazzi

[coLinux-users] iptables nat modules

[Jerome <mar...@ya...>]

Hello,

I want to use colinux as an Internet firewall. I tried to configure iptables to do this but I can't define nat rules. (I got errors like "not existing nat table" error)
So I'm thinking that there are missing iptables modules in the colinux kernel. Is it possible to include the nat module in the next build release please ?

Cheers,
Jerome




      _____________________________________________________________________________ 
Envoyez avec Yahoo! Mail. Une boite mail plus intelligente http://mail.yahoo.fr

Re: [coLinux-users] Networking

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

Krishna Murthy wrote:
> eth0=tuntap,LINLAN,80:16:76:C0:29:03
> eth1=pcap-bridge,WINLAN
> [...]
>  
> It works well and I am using “devel-coLinux-20071105”
>  
> “devel-coLinux-20071203” onwards, the eth1 gets renamed to something
> like eth16 and keeps incrementing.
> 
> Hoping that it is a bug kept waiting and tried now with
> “devel-coLinux-20080302”.  The problem remains same.

Hm? devel-coLinux-20080302 should stop the increasing. There the
automatic generated mac is stored in registry. Exist this key?

# Automatic generated MAC, monitor number 'M', network device index 'X'
[HKEY_CURRENT_USER\Software\coLinux\monitor\M\ethX]
"mac"="00:ff:XX:XX:XX:XX"

Plesae start "colinux-daemon -v 3 -k ..." and watch for messages about
MAC. Should say "read" from registry key.

> What modification is needed in the configuration?

Configure a unique MAC for eth1, example:
eth1=pcap-bridge,WINLAN,02:00:00:00:00:03

You needs to remove entries from z25_persistent-net.rules ones after
running older versions again.


Read more about increasing networks in
"20071203-Snapshot -- ifconfig reports no networking"
http://sourceforge.net/tracker/index.php?func=detail&aid=1861876&group_id=98788&atid=622063

> Workarround:
> 
> 1st step:
> Assign a fixed MAC address in the colinux config:
> 
> For example:
> eth0=pcap-bridge,,0A:C0:71:65:08:00,  (implicit ethernet device is not
> recommanded)
> eth0=pcap-bridge,"WindowsNameOfYourEthernet",0A:C0:71:65:08:00,
> eth0=tuntap,LAN-TAP Vqe8(colinux),0A:C0:71:65:08:00,
> 
> Attention:
> The "second" nibble (from left) should/must have only the values 2,6,A or
> E.
> The remainder does not matter as long as it is unique in your LAN.
> 
> 
> 2nd step:
> remove all entries in
> 
> "/etc/udev/rules.d/z25_persistent-net.rules"
> 
> like these:
> SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:ff:06:be:41:00",
> NAME="eth0"
> 
> # PCI device 0x1a55:0x0005 (conet)
> SUBSYSTEM=="net", DRIVERS=="?*",
> ATTRS{address}=="00:ff:25:e6:00:00",NAME="eth1"

-- 
Henry N.

[coLinux-users] (no subject)

[Krishna M. <glo...@da...>]

I have the following configuration

 

kernel=vmlinux

initrd=initrd.gz 

mem=256

cobd0=c:\coLinux\root_fs3

cobd1=c:\coLinux\swap_device

cobd2=\Device\HarddiskVolume6

eth0=tuntap,LINLAN,80:16:76:C0:29:03

eth1=pcap-bridge,WINLAN

root=/dev/cobd0 3

ro

cofs0=D:\

cofs1=E:\

cofs2=F:\

cofs3=G:\

 

It works well and I am using “devel-coLinux-20071105”

 

“devel-coLinux-20071203” onwards, the eth1 gets renamed to something like
eth16 and keeps incrementing.

Hoping that it is a bug kept waiting and tried now with
“devel-coLinux-20080302”.  The problem remains same.

What modification is needed in the configuration?

 

Krishna Murthy

 

 


No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.516 / Virus Database: 269.21.7/1319 - Release Date: 3/8/2008
10:14 AM
 

[coLinux-users] Networking

[Krishna M. <glo...@da...>]

I have the following configuration

 

kernel=vmlinux

initrd=initrd.gz 

mem=256

cobd0=c:\coLinux\root_fs3

cobd1=c:\coLinux\swap_device

cobd2=\Device\HarddiskVolume6

eth0=tuntap,LINLAN,80:16:76:C0:29:03

eth1=pcap-bridge,WINLAN

root=/dev/cobd0 3

ro

cofs0=D:\

cofs1=E:\

cofs2=F:\

cofs3=G:\

 

It works well and I am using “devel-coLinux-20071105”

 

“devel-coLinux-20071203” onwards, the eth1 gets renamed to something like
eth16 and keeps incrementing.

Hoping that it is a bug kept waiting and tried now with
“devel-coLinux-20080302”.  The problem remains same.

What modification is needed in the configuration?

 

Krishna Murthy

 


No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.516 / Virus Database: 269.21.7/1319 - Release Date: 3/8/2008
10:14 AM
 

Re: [coLinux-users] 0.7.2 less reliable on dual core?

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

Hello Baldyeti,

http://www.henrynestler.com/colinux/testing/pfn-check-0.7.3/daemons-0.7.3-20080306.zip
this is the final code. All debugs removed. Should run properly on your
machine.

-- 
Henry N.

Re: [coLinux-users] 0.7.2 less reliable on dual core?

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

baldyeti wrote:
> On 06/03/2008 09:18, Henry Nestler wrote:
>> DebugView is totaly ok. No errors, no "Bug: ...", very good.
>>
>> "big Range" can not see on coLinux starts.
>> You can only see it at driver load:
>>   colinux-daemon.exe --remove-driver
>>   colinux-daemon.exe --install-driver
>>
> Just for confirmation:
> 
> [m:colinux-driver f:0 l:10 
> src/colinux/os/winnt/kernel/manager.c:134:co_os_manager_init] big 
> Range[2] 0x0.01000000 0x0.77000000
> 
> and then later:
> 
> [m:colinux-driver f:0 l:10 
> src/colinux/os/winnt/kernel/alloc.c:65:co_winnt_new_mdl_bucket] FixRange 
> used 0x1000000 0x77000000
> 
> So Henry ... is this all pointing to a problem in the nvidia
> graphics driver, or a bug that might have bitten anyone with
> an IGP using shared memory?

I have tryed to allocating memory in the range of my shared graphic
adapter. Failed, and don't got memory from this area. So, my graphics
driver (ATI) works right and block coLinux from getting this memory area.

My laptop has 512MB total ram, from that are 32MB shared graphic. This
is coLinux driver debug from testing:
  Rage[0] 0x1000 0x9e000 (647168 0MB)
  Rage[1] 0x100000 0xeff000 (15724544 14MB)
  Rage[2] 0x1000000 0x1cff0000 (486473728 463MB)
  Try to get from 0x1e000000 to 0x20000000 size 262144
  MmAllocatePagesForMdl failed


It's a double fault on both drivers. It's a bug in your graphic card
driver and in coLinux driver. Would coLinux ask for specific range
instead "any" ram, then would no have problems. The last workarround
does exactly this.
If your card would mark the memory as "in use", then colinux driver
would not got it.

We know, that MmAllocatePagesForMdl is undocumented. But, I can not find
a simple way to get a big list of pages without having virtual memory
before. All the functions needs to have virtual memory as parameter.
With virtual bufer would have to create a MDL from that, than can fill
the MDL with pages...

Interesing links:
"Address Mappings and MDLs"
http://msdn2.microsoft.com/en-us/library/ms796200.aspx

"Long-Term Internal Driver Buffers"
http://msdn2.microsoft.com/en-us/library/ms796250.aspx

-- 
Henry N.

Re: [coLinux-users] 0.7.2 less reliable on dual core?

[baldyeti <e_...@ho...>]

On 06/03/2008 09:18, Henry Nestler wrote:
> DebugView is totaly ok. No errors, no "Bug: ...", very good.
> 
> "big Range" can not see on coLinux starts.
> You can only see it at driver load:
>   colinux-daemon.exe --remove-driver
>   colinux-daemon.exe --install-driver
> 
Just for confirmation:

[m:colinux-driver f:0 l:10 
src/colinux/os/winnt/kernel/manager.c:134:co_os_manager_init] big 
Range[2] 0x0.01000000 0x0.77000000

and then later:

[m:colinux-driver f:0 l:10 
src/colinux/os/winnt/kernel/alloc.c:65:co_winnt_new_mdl_bucket] FixRange 
used 0x1000000 0x77000000

So Henry ... is this all pointing to a problem in the nvidia
graphics driver, or a bug that might have bitten anyone with
an IGP using shared memory?

Re: [coLinux-users] 0.7.2 less reliable on dual core?

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

baldyeti wrote:
>> Debugs on startup are enabled for DebugView.
>> If my idea works, you should see exactly this line:
>> "... big Range[2] 0x0.01000000 0x0.77000000"
>>
>> and some lines later two or more of:
>> "... co_winnt_new_mdl_bucket] FixRange used 0x1000000 0x77000000"
> 
> I see the second one (FixRange) repeated numerous times in the
> rather verbose log, but not the 1st one (BigRange).

DebugView is totaly ok. No errors, no "Bug: ...", very good.

"big Range" can not see on coLinux starts.
You can only see it at driver load:
  colinux-daemon.exe --remove-driver
  colinux-daemon.exe --install-driver

"FixRange" is the usage of "big range" finder on startup. So it is no
problem, that you not have seen it in log. It is still working.

>> All other 'Range' should automaticly ignored.
>> No errors with 'pfn to big' or 'pfn out of range' should be have now (in
>> colinux-debug only, not in DebugView).
> 
> I am still seeing "Bug: PFN too high! 521536 >= 491520" but didn't
> you tell me that one was safe to ignore?

Yes, you can double ignore this. ;-)
1. This was an false/positive on co_os_map.
2. In the new code don't exist such text. There exist a new text "Bug:
PFN out of range", and this should not ignore.

The debug xml contains an old plus new debug (file was append).
Behind the text "Daemon compiled on Thu Mar  6 00:31:32 2008" all is ok,
no more errors.

Thanks. I will cleanup the code next weekend.

-- 
Henry N.

Re: [coLinux-users] 0.7.2 less reliable on dual core?

[baldyeti <e_...@ho...>]

> Debugs on startup are enabled for DebugView.
> If my idea works, you should see exactly this line:
> "... big Range[2] 0x0.01000000 0x0.77000000"
> 
> and some lines later two or more of:
> "... co_winnt_new_mdl_bucket] FixRange used 0x1000000 0x77000000"

I see the second one (FixRange) repeated numerous times in the
rather verbose log, but not the 1st one (BigRange).

> All other 'Range' should automaticly ignored.
> No errors with 'pfn to big' or 'pfn out of range' should be have now (in
> colinux-debug only, not in DebugView).

I am still seeing "Bug: PFN too high! 521536 >= 491520" but didn't
you tell me that one was safe to ignore?

Cheers,

--bald

Re: [coLinux-users] 0.7.2 less reliable on dual core?

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

baldyeti wrote:
> I my case there are 4 entries:
> Phys addre	Length
> 0x001000	0x9d000
> 0x100000	0xeff00
> 0x1000000	0x76000000
> 0x7f000000	0xdf0000
> 
> All blocks have R/W access.
> I think I copied those right, they're identical to the 4 dbgview
> output lines indeed.

Yes, was the same as automicly detect by coLinux driver.
Thanks. Graphic card is not in list. Very good.

That should be run:
http://www.henrynestler.com/colinux/testing/pfn-check-0.7.3/daemons-0.7.3-20080305.zip

Debugs on startup are enabled for DebugView.
If my idea works, you should see exactly this line:
"... big Range[2] 0x0.01000000 0x0.77000000"

and some lines later two or more of:
"... co_winnt_new_mdl_bucket] FixRange used 0x1000000 0x77000000"

All other 'Range' should automaticly ignored.
No errors with 'pfn to big' or 'pfn out of range' should be have now (in
colinux-debug only, not in DebugView).

If that works, I can remove some of the debuggings and made a clean
runable version.

-- 
Henry N.

[coLinux-users] Colinux for Windows embedded CE

[Gopinath R.A <gop...@gm...>]

Hello all

Colinux is OS Independent. I have seen it been mentioned in the
Download section.
So is there any possibility to implement or make colinux work in
Microsoft WIndows Embedded CE.

Thanks in advance

Re: [coLinux-users] 0.7.2 less reliable on dual core?

[baldyeti <e_...@ho...>]

On 04/03/2008 23:57, Henry Nestler wrote:
 > ...
 > Watch in the WebugView, save the output to log file.

Here's dbgview's output (maybe usenet will mess up the formatting,
let me know if you want the file sent to you)
Note that I haven't actually started colinux, only re-installed
the driver as requested if I understood you correctly.

--------> start of capture <--------
[m:colinux-driver f:0 l:10 
src/colinux/os/winnt/kernel/manager.c:51:co_os_manager_init] Rage[0] 
0x1000 0x9d000 (643072 MB)
colinux-debug: section created: sections: 1, total: 4096, filled: 0
[m:colinux-driver f:0 l:10 
src/colinux/os/winnt/kernel/manager.c:51:co_os_manager_init] Rage[1] 
0x100000 0xeff000 (15724544 MB)
[m:colinux-driver f:0 l:10 
src/colinux/os/winnt/kernel/manager.c:51:co_os_manager_init] Rage[2] 
0x1000000 0x76000000 (1979711488 MB)
[m:colinux-driver f:0 l:10 
src/colinux/os/winnt/kernel/manager.c:51:co_os_manager_init] Rage[3] 
0x7f000000 0xdf0000 (14614528 MB)
[m:colinux-driver f:0 l:10 
src/colinux/kernel/reversedpfns.c:30:co_manager_alloc_reversed_pfns] 
allocating reversed physical mapping for 491520 pages
[m:colinux-driver f:0 l:10 
src/colinux/kernel/reversedpfns.c:34:co_manager_alloc_reversed_pfns] 
allocating top level pages map (1920 bytes)
[m:colinux-driver f:0 l:10 
src/colinux/kernel/reversedpfns.c:41:co_manager_alloc_reversed_pfns] 
allocating 480 top level pages
[m:colinux-driver f:0 l:10 
src/colinux/os/winnt/kernel/alloc.c:49:co_winnt_new_mdl_bucket] Limit 
page request to 0x78000000
[m:colinux-driver f:0 l:10 
src/colinux/kernel/reversedpfns.c:56:co_manager_alloc_reversed_pfns] 
using 4 table entries for reversed physical mapping
--------> end of capture <--------

> Last please verify these ranges with the Registry. It should be the
> same: Run regedit.exe and open key
> "HKEY_LOCAL_MACHINE\HARDWARE\RESOURCEMAP\System Resources\Physical Memory"
> Double click on key ".Translated", select  "intern" and than the button
> "view". The output is not very nice, is scroll area with 2 lines only.

I my case there are 4 entries:
Phys addre	Length
0x001000	0x9d000
0x100000	0xeff00
0x1000000	0x76000000
0x7f000000	0xdf0000

All blocks have R/W access.
I think I copied those right, they're identical to the 4 dbgview
output lines indeed.

--bald

Re: [coLinux-users] 0.7.2 less reliable on dual core?

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

Hello Baldyeti,

would be nice to check the next step, before I use the values.

Download and extract this
http://www.henrynestler.com/colinux/testing/pfn-check-0.7.3/daemons-0.7.3-20080304.zip

Download DebugView.exe from http://www.sysinternals.com (redirected to
MS), exist under "Miscellaneous Utilities".
Direct link: http://download.sysinternals.com/Files/DebugView.zip

Unpack and start DebugView.exe, let this window opened

Open a new command prompt and reload coLinux driver with:
  colinux-daemon --remove-driver
  colinux-daemon --install-driver
Check driver state with
  colinux-daemon --status-driver
should give:
  Driver compiled on: Tue Mar  4 23:20:25 2008

Watch in the WebugView, save the output to log file.
You should see such lines:
... Rage[0] 0x1000 0x9e000 (647168 MB)	
... Rage[1] 0x100000 0xeff000 (15724544 MB)	
... Rage[2] 0x1000000 0x1eef0000 (518979584 MB)	
... Rage[3] 0x1ff00000 0x100000 (1048576 MB)	
... allocating reversed physical mapping for 131072 pages

This are the physicaly pages of my system (the "MB" are Bytes, please
ignore my typofix). Please send me this text file, or post your short
version here (see my shorts). Hope to see your graphic card hole there.

Last please verify these ranges with the Registry. It should be the
same: Run regedit.exe and open key
"HKEY_LOCAL_MACHINE\HARDWARE\RESOURCEMAP\System Resources\Physical Memory"
Double click on key ".Translated", select  "intern" and than the button
"view". The output is not very nice, is scroll area with 2 lines only.
There you should see the current memory. The same as from coLinux?

-- 
Henry N.