colinux-users — coLinux users mailing list

[coLinux-users] colinux-net-daemon keeps crashing

[Mark G. W. <mar...@ya...>]

I'm not sure why, but I keep getting intermittent crashes of colinux-net-daemon whenever I start
an X session after booting colinux. This is on a 0.6.4 system running on a Pentium M laptop
(Thinkpad T42p) via the local ethernet connection, which is bridged to a tap connection.
Colinux.xml contains:
    <network index="0" name="Local Area Connection 2" type="tap" />
with fixed IP addresses for both the connection and for the Colinux machine. /NOPAE and
/NoExecute=AlwaysOff are set in boot.ini.

The htmp dump file contains:

This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(bc8.244): Access violation - code c0000005 (first/second chance not available)
eax=00002000 ebx=80070000 ecx=00002000 edx=00000000 esi=000000b4 edi=00000000
eip=7c90eb94 esp=00229d30 ebp=00229d94 iopl=0         nv up ei ng nz ac pe cy
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000297
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntdll.dll - 
ntdll!KiFastSystemCallRet:
7c90eb94 c3              ret
0:000> .ecxr
eax=86a17001 ebx=2a01007b ecx=7c810e16 edx=86a17001 esi=d640c2b3 edi=0042c184
eip=004013b0 esp=0022fd80 ebp=0022fd98 iopl=0         nv up ei pl nz na pe nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00010206
*** ERROR: Module load completed but symbols could not be loaded for colinux-net-daemon.exe
colinux_net_daemon+0x13b0:
004013b0 8b4610          mov     eax,dword ptr [esi+10h] ds:0023:d640c2c3=????????
0:000> .reload
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
0:000> .reload
...................
*** ERROR: Module load completed but symbols could not be loaded for colinux-net-daemon.exe
0:000> .ecxr
eax=86a17001 ebx=2a01007b ecx=7c810e16 edx=86a17001 esi=d640c2b3 edi=0042c184
eip=004013b0 esp=0022fd80 ebp=0022fd98 iopl=0         nv up ei pl nz na pe nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00010206
colinux_net_daemon+0x13b0:
004013b0 8b4610          mov     eax,dword ptr [esi+10h] ds:0023:d640c2c3=????????




 
____________________________________________________________________________________
Sponsored Link

Mortgage rates near 39yr lows. 
$310k for $999/mo. Calculate new payment! 
www.LowerMyBills.com/lre

Re: [coLinux-users] Running coLinux as a service.

[Mark Z. <mza...@gm...>]

Hi,

Thanks for the reply.

I'm running coLinux 0.7.1-hn16 on Windows XP. Here is the output from
colinux-daemon.exe --status-driver:

C:\coPlanet\coPlanet>colinux-daemon.exe --status-driver
Cooperative Linux Daemon, 0.7.1-hn16
Compiled on Sun Jul  9 16:35:25 2006

checking if the driver is installed
current state: 4 (fully initialized)
current number of monitors: 0
current linux api version: 10
current periphery api version: 20

so it looks like the CoLinuxDriver driver is installed properly.

To install a coLinux service I run the following:

colinux-daemon.exe "@C:\coPlanet\coPlanet\pl.conf" ro root=/dev/sda1
--install-service "coPlanet"

I tried running with the debugger but I only got the same information that
is dumped to stdout when I try and start the service from the console with:

colinux-daemon.exe --run-service "coPlanet"

Cheers,
Mark.

On 11/16/06, Henry Nestler <Hen...@ar...> wrote:
>
> Mark Zaloumis wrote:
> > Hello,
> >
> > I'm wondering what the coLinux installer does in the install process
> > that lets coLinux daemons be run as services. If I copy the files from a
> > coLinux install on one computer onto a computer that coLinux has never
> > been installed on, coLinux will run fine but if I try and run it as a
> > service I get the error:
> >
> > The service process could not connect to the service controller
> >
> > However, if I then go install coLinux somewhere else on the computer I
> > copied the coLinux install onto I can then start the copied version as a
> > service. This leads me to think that the coLinux installer is setting up
> > something to do with the service controller? I was wondering if anyone
> > could shed some light on this.
>
> The installer does a "colinux-daemon.exe --install-driver" and setthe
> path for the uninstaller, but does nothing with the system services.
>
> What version of coLinux you are running?
> What Windows (XP or W2K)?
>
> Is the coLinux right installed and unused?
> Check this, if service is not running:
>    colinux-daemon.exe --status-driver
>
> Try to start the debugger:
>    colinux-debug-daemon.exe -d -p -s prints=31,misc=31 > file.log
> Than run the service from a second prompt, stop debugger with CTRL-C
> after the error passed.  Than grep into the output, search the error
> line and read detailed error messages some lines before.
>
> What steps do you runs to "install the service"?
> Please list your inputs on windows command line.
>
> --
> Henry Nestler
>

Re: [coLinux-users] Running coLinux as a service.

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

Mark Zaloumis schrieb:
> Hello,
> 
> I'm wondering what the coLinux installer does in the install process
> that lets coLinux daemons be run as services. If I copy the files from a
> coLinux install on one computer onto a computer that coLinux has never
> been installed on, coLinux will run fine but if I try and run it as a
> service I get the error:
> 
> The service process could not connect to the service controller
> 
> However, if I then go install coLinux somewhere else on the computer I
> copied the coLinux install onto I can then start the copied version as a
> service. This leads me to think that the coLinux installer is setting up
> something to do with the service controller? I was wondering if anyone
> could shed some light on this.

If you didn't install colinux and just copied the files how do you install it as a service?

Maybe the service is missing the colinux driver. A service that is installed as a device. 

Re: [coLinux-users] Running coLinux as a service.

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

Mark Zaloumis wrote:
> Hello,
> 
> I'm wondering what the coLinux installer does in the install process 
> that lets coLinux daemons be run as services. If I copy the files from a 
> coLinux install on one computer onto a computer that coLinux has never 
> been installed on, coLinux will run fine but if I try and run it as a 
> service I get the error:
> 
> The service process could not connect to the service controller
> 
> However, if I then go install coLinux somewhere else on the computer I 
> copied the coLinux install onto I can then start the copied version as a 
> service. This leads me to think that the coLinux installer is setting up 
> something to do with the service controller? I was wondering if anyone 
> could shed some light on this.

The installer does a "colinux-daemon.exe --install-driver" and setthe 
path for the uninstaller, but does nothing with the system services.

What version of coLinux you are running?
What Windows (XP or W2K)?

Is the coLinux right installed and unused?
Check this, if service is not running:
   colinux-daemon.exe --status-driver

Try to start the debugger:
   colinux-debug-daemon.exe -d -p -s prints=31,misc=31 > file.log
Than run the service from a second prompt, stop debugger with CTRL-C 
after the error passed.  Than grep into the output, search the error 
line and read detailed error messages some lines before.

What steps do you runs to "install the service"?
Please list your inputs on windows command line.

-- 
Henry Nestler

[coLinux-users] Running coLinux as a service.

[Mark Z. <mza...@gm...>]

Hello,

I'm wondering what the coLinux installer does in the install process that
lets coLinux daemons be run as services. If I copy the files from a coLinux
install on one computer onto a computer that coLinux has never been
installed on, coLinux will run fine but if I try and run it as a service I
get the error:

The service process could not connect to the service controller

However, if I then go install coLinux somewhere else on the computer I
copied the coLinux install onto I can then start the copied version as a
service. This leads me to think that the coLinux installer is setting up
something to do with the service controller? I was wondering if anyone could
shed some light on this.

Cheers,
Mark.

Re: [coLinux-users] DRIVER_IRQL_NOT_LESS_OR_EQUAL blue screen

[Andrea M. <mar...@ac...>]

Henry Nestler wrote:
> Holger Krull wrote:
>   
> The /nopae would not help.
> Please add or change the C:\boot.ini and set
>    /noexecute=AlwaysOff
> See in wiki http://wiki.colinux.org/wiki/NoExecuteDEP
>
> An other workarrount is to remove the "initrd" from colinux config.
>   
Thanks to all, it works.

Andrea

Re: [coLinux-users] DRIVER_IRQL_NOT_LESS_OR_EQUAL blue screen

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

Henry Nestler schrieb:
> Holger Krull wrote:
>> Andrea Marchini wrote:
>>> Holger Krull wrote:
>>>> Andrea Marchini wrote:
>>  
>>>> Did you try to add /nopae to the entry in boot.ini?
>>> Yes, I've tried this. Last few times I tried, coLinux directly
>>> rebooted Windows without blue screen.
>>
>> What type of processor does this computer have, amount of ram?
> 
> The /nopae would not help.
> Please add or change the C:\boot.ini and set
>   /noexecute=AlwaysOff
> See in wiki http://wiki.colinux.org/wiki/NoExecuteDEP

Oh, sorry.
I assumed /nopae would override any /noexecute setting as you need the pae tables to set the no execute bit.
 

Re: [coLinux-users] DRIVER_IRQL_NOT_LESS_OR_EQUAL blue screen

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

Holger Krull wrote:
> Andrea Marchini wrote:
>> Holger Krull wrote:
>>> Andrea Marchini wrote:
>   
>>> Did you try to add /nopae to the entry in boot.ini?
>> Yes, I've tried this. Last few times I tried, coLinux directly rebooted 
>> Windows without blue screen.
> 
> What type of processor does this computer have, amount of ram?

The /nopae would not help.
Please add or change the C:\boot.ini and set
   /noexecute=AlwaysOff
See in wiki http://wiki.colinux.org/wiki/NoExecuteDEP

An other workarrount is to remove the "initrd" from colinux config.

-- 
Henry Nestler

Re: [coLinux-users] DRIVER_IRQL_NOT_LESS_OR_EQUAL blue screen

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

Andrea Marchini schrieb:
> Holger Krull wrote:
>> Andrea Marchini schrieb:
  
>> Did you try to add /nopae to the entry in boot.ini?
> Yes, I've tried this. Last few times I tried, coLinux directly rebooted 
> Windows without blue screen.

What type of processor does this computer have, amount of ram?

Re: [coLinux-users] DRIVER_IRQL_NOT_LESS_OR_EQUAL blue screen

[Andrea M. <mar...@ac...>]

Holger Krull wrote:
> Andrea Marchini schrieb:
>   
>> Hi all, I've installed different versions of coLinux (0.6.4, 0.6.3, 
>> 0.6.2), different root fs (Debian, Fedora),
>> but I got a DRIVER_IRQL_NOT_LESS_OR_EQUAL blue screen when I run the 
>> colinux-daemon.
>> I've tried to turn HT off, but doesn't work. I know the problem already 
>> occurred, but I've found no
>> solution on the web. Any suggestions appreciated, thanks in advance.
>>     
>
> Did you try to add /nopae to the entry in boot.ini?
Yes, I've tried this. Last few times I tried, coLinux directly rebooted 
Windows without blue screen.


Andrea

Re: [coLinux-users] DRIVER_IRQL_NOT_LESS_OR_EQUAL blue screen

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

Andrea Marchini schrieb:
> Hi all, I've installed different versions of coLinux (0.6.4, 0.6.3, 
> 0.6.2), different root fs (Debian, Fedora),
> but I got a DRIVER_IRQL_NOT_LESS_OR_EQUAL blue screen when I run the 
> colinux-daemon.
> I've tried to turn HT off, but doesn't work. I know the problem already 
> occurred, but I've found no
> solution on the web. Any suggestions appreciated, thanks in advance.

Did you try to add /nopae to the entry in boot.ini?

[coLinux-users] DRIVER_IRQL_NOT_LESS_OR_EQUAL blue screen

[Andrea M. <mar...@ac...>]

Hi all, I've installed different versions of coLinux (0.6.4, 0.6.3, 
0.6.2), different root fs (Debian, Fedora),
but I got a DRIVER_IRQL_NOT_LESS_OR_EQUAL blue screen when I run the 
colinux-daemon.
I've tried to turn HT off, but doesn't work. I know the problem already 
occurred, but I've found no
solution on the web. Any suggestions appreciated, thanks in advance.

Andrea

[coLinux-users] license

[Ken P. <ke...@gm...>]

what's the license of the coLinux?

-- 
perl -e 'print unpack(u,"62V5N\"FME;G\!E<FQ`9VUA:6PN8V]M\"\@``
")'

Re: [coLinux-users] Slackware with colinux

[<mki...@tl...>]

mattias jonsson wrote:
> How to use slackware with colinux?
> 
There's a HowTo on the Wiki: http://wiki.colinux.org/wiki/SlackwareHowTo
("hidden" under 'Linux Distributions' -> 'SlackwareHowTo')
There are also some generic instructions on how to build
images to be found on the wiki you might try.

I have never seen any slackware images ready for download anywhere.

Good luck,

Matthias Kievernagel
mkiever - at - web - dot - de

Re: [coLinux-users] mapped network drive ?

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

Hello,

lode leroy wrote:
> I have a physical drive "C:" and a network mount "N:"
> I tried to access both drives via COFS as follows:
> 
> colinux-daemon kernel=vmlinux mem=256 cobd0=rootdisk.img cofs0=C:\ cofs1=N:\ 
> root=/dev/cobd0 ro
> 
> "mount -t cofs /dev/cofs0 /mnt/c" works fine, but
> "mount -t cofs /dev/cofs1 /mnt/n" complains that the drive is already 
> mounted.

cofs is not a device, it is a file system and need special params, not 
the notation "/dev".  Change it into:
   mount -t cofs cofs0 /mnt/c
   mount -t cofs cofs1 /mnt/n
or
   mount -t cofs 0 /mnt/c
   mount -t cofs 1 /mnt/n

-- 
Henry Nestler

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

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

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

I will respond to your message when I return.

[coLinux-users] Slackware with colinux

[mattias j. <mj...@mj...>]

How to use slackware with colinux?

----
mattias jonsson
mobil: 0708174516
073-695 25 19 
det gamla nummret funkar med.
hemsida

http://mj.mydns.se
email:
mj...@mj...
msn: mat...@ho... 
icq 211777788

[coLinux-users] mapped network drive ?

[lode l. <lod...@ho...>]

Hello,

I've been using coLinux for a while, and it's really cool!
Now I have a new laptop, I needed some changes, and ran into a problem:

I have a physical drive "C:" and a network mount "N:"
I tried to access both drives via COFS as follows:

colinux-daemon kernel=vmlinux mem=256 cobd0=rootdisk.img cofs0=C:\ cofs1=N:\ 
root=/dev/cobd0 ro

"mount -t cofs /dev/cofs0 /mnt/c" works fine, but
"mount -t cofs /dev/cofs1 /mnt/n" complains that the drive is already 
mounted.

when I skip mounting the "C:" the mount succeeds,
but "mount -t cofs /dev/cofs1 /mnt/n" actually mounts the "C:" drive in 
"/mnt/n".

does anyone know how to accomplish this?

ps: this is what I use:

colinux-0.6.4
host windows xp-sp2
kernel 2.6.11-co-0.6.4
distribution slackware-11.0
(also using tun/tap network driver)

-- lode

_________________________________________________________________
Alex came home an hour earlier today... It could happen to you too! 
http://toolbar.live.com

Re: [coLinux-users] 445 VeAGRA

[Aneirin B. <ga...@ho...>]

So thats what they look like. I never


Good VeAGRA http://www.putionkdetunjadesunha.com

=20
into this operation by telling me I had been poisoned and that I had

[coLinux-users] Trabajo. Espana

[Julia M. <Ar...@ni...>]

Hola,

Nuestra compania internacional ofrece el trabajo facil para los habitantes 
de la Espana.
Puedes ganar 200-600 Euros por dia.
Esto es legal y es seguro.

Respondan solamente este e-mail:
TRA...@IN...

--
Un Saludo,
Julia M.

Re: [coLinux-users] can't scroll the screen

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

João Esteves schrieb:
> Hello:
> 
> Sory for a very beginner issue, but I can't scroll up the console screen,
> which means that for long output I loose a lot of information. The "PageUp"
> key doesn't work, nor do ctrl + up arrow or alt + up arrow. Also the wheel
> mouse doesn't work.
> Is it possible to change this?

I recommend using putty to connect to colinux. Screen history will work then.

[coLinux-users] GDB cannot find new threads

[Ron P. <ron...@mo...>]

Hi,

I am using the 20061003 snapshot, with Fedora Core 5 (the FC4 images was
enlarged, upgraded, etc.)  When I start gdb and run a program I receive
the following:

There is absolutely no warranty for GDB.  Type "show warranty" for
details.
This GDB was configured as "i386-redhat-linux-gnu"...Using host
libthread_db library "/lib/libthread_db.so.1".

(gdb) r
Starting program: /some-path/some-program
Reading symbols from shared object read from target memory...done.
[Thread debugging using libthread_db enabled]
Cannot find new threads: generic error
Cannot find user-level thread for LWP 1864: generic error
(gdb)

Any ideas?
--=20
Ron Parker
Scientific Literature Indexing on Networked Computers (SciLINC)
Missouri Botanical Garden

[coLinux-users] can't scroll the screen

[<joa...@ne...>]

Hello:

Sory for a very beginner issue, but I can't scroll up the console screen,
which means that for long output I loose a lot of information. The "PageUp"
key doesn't work, nor do ctrl + up arrow or alt + up arrow. Also the wheel
mouse doesn't work.
Is it possible to change this?

I'm using debian in colinux 0.6.4

Regards.
Joao

[coLinux-users] SMB vs NFS performance on the virtual adapter

[Juaco <ka...@gm...>]

Hello ppl,
I'm using colinux at my work to share to mi local windows (via TAP) and  
the LAN (via PCAP) a 300G XFS partition fulled with mp3, videos, etc. All  
this is done with a SWAT-configured samba server. The performance is good,  
though i haven't made any test. It works reasonably well.
What i'm wondering is if it's possible to further improve the *LOCAL*  
(TAP) throughput to the maximum achievable, either by tuning SMB and every  
other network parameter that helps, or by using NFS and a good client (aka  
"not the microsoft one") on the windows side.
What option should work better? anybody has tried with nfs? I looked on  
several forums but the few people that compared the two systems have found  
contradictory results, apparently. Maybe NFS is better suited for this  
specific scenario, a pure local, virtual share.
Many thanks

Joaquin

[coLinux-users] Suspend colinux?

[w.goesgens <roo...@ou...>]

<html><body>

<p>Hy, as one tends to reboot his WinTendo more frequent than a usual Col=
inux installation, is there a way to do swsusp in the colinux, so it coul=
d be resumed on restarting the windows?</p><p>Tia, </p><p>&nbsp; Wilfried=
 Goesgens<br />&nbsp; </p>
</body></html>