colinux-users — coLinux users mailing list

RE: [coLinux-users] linux kernel port

[peter g. <plu...@bi...>]

i think it just uses vmlinux-x86 when building the kernel i don't think it
bothers with its own architecture name

i belive it may in the end be possible to have a kernel that supports
running both native and cooperative
  -----Original Message-----
  From: col...@li...
[mailto:col...@li...]On Behalf Of shruti pandey
  Sent: 11 September 2004 14:49
  To: col...@li...
  Subject: [coLinux-users] linux kernel port



  hi there ,

  like uml is a a port of linux kernel to  a linux kernel , and it uses the
architectural port  --ARCH=um--
  which one does coLinux use?

  thanks
  shruti
  col...@li... wrote:
    Send coLinux-users mailing list submissions to
    col...@li...

    To subscribe or unsubscribe via the World Wide Web, visit
    https://lists.sourceforge.net/lists/listinfo/colinux-users
    or, via email, send a message with subject or body 'help' to
    col...@li...

    You can reach the person managing the list at
    col...@li...

    When replying, please edit your Subject line so it is more specific
    than "Re: Contents of coLinux-users digest..."


    Today's Topics:

    1. Re: Random signal 11 problems? (Jules)
    2. Re: Random signal 11 problems? (Chuck Adams)
    3. Does colinux work on NT4 (Shi, Jue)
    4. Re: Does colinux work on NT4 (Nuno Lucas)
    5. A fix for the SIGFPE problem (>20040622) (Dan Aloni)

    --__--__--

    Message: 1
    Date: Thu, 09 Sep 2004 09:40:24 +0100
    From: Jules
    To: col...@li...
    Subject: [coLinux-users] Re: Random signal 11 problems?

    >
    >
    >It may be outdated and may not apply to your
    >problem, but it is probably worth looking at
    >the sig 11 FAQ:
    >http://www.bitwizard.nl/sig11/
    >

    Thanks. I'm pretty sure this isn't hardware related, as the same system
    runs the kernel supplied with the binary package just fine, plus kernels
    compiled by myself work OK without colinux.

    I've compiled a copy of the kernel with the config file supplied in the
    colinux source distribution, and that seems to be working, I'm going
    through a second compile of it now, with it running, and it seems to be
    pretty stable. It's got a lot farther than the last one did, at least.

    So I guess it was one of the config options that did it. Are there any
    that are known to be dangerous with colinux? The main changes I made
    were optimising for my processor environment (changed from CONFIG_M586
    to CONFIG_MK7, disabled CONFIG_X86_GENERIC, all consequential changes
    from this). I also killed support for a.out binaries, moved binfmt_misc
    to a module, switched off the kernel debugging options, and added
    support for unloading modules.

    There were other changes too, but mostly relating to filesystems, which
    I don't think are likely candidates.

    Any suggestions on what may have caused the problem?


    --__--__--

    Message: 2
    Date: Thu, 09 Sep 2004 09:51:36 -0700
    From: Chuck Adams
    To: Sandy Harris
    Cc: col...@li...
    Subject: Re: [coLinux-users] Random signal 11 problems?

    Sandy Harris wrote:

    > It may be outdated and may not apply to your
    > problem, but it is probably worth looking at
    > the sig 11 FAQ:
    > http://www.bitwizard.nl/sig11/


    Actually it's almost never worth looking at that FAQ. It's pure
    baloney. I remember this FAQ getting thrown at me before ... Yes,
    memory glitches may cause segfaults and if random apps are failing at
    random times, it's worth running memtest. But there are claims in that
    FAQ that are just absurd. I always found it odd how it was *just* gcc
    that somehow "stressed the memory" and therefore just gcc that would
    segfault. Occam's razor was right all along of course -- it was a bug
    in gcc. Either that or the next upgrade magically fixed my hardware.

    chuck



    --__--__--

    Message: 3
    From: "Shi, Jue"
    To: "'col...@li...'"

    Date: Thu, 9 Sep 2004 10:15:18 -0700
    Subject: [coLinux-users] Does colinux work on NT4


    Hi,

    I tried to install Colinux on Windows NT4, and get an error message "An
    error occured installing the tap-win32 device driver". Does Colinux work
on
    NT4 at all, or it's just my PC setup problem?

    BTW, I have colinux running on my XP box working fine.

    Thanks,
    JueS


    --__--__--

    Message: 4
    Date: Thu, 09 Sep 2004 18:38:35 +0100
    From: Nuno Lucas
    To: col...@li...
    Cc: "Shi, Jue"
    Subject: Re: [coLinux-users] Does colinux work on NT4

    Shi, Jue, dando pulos de alegria, escreveu :
    > Hi,
    >
    > I tried to install Colinux on Windows NT4, and get an error message
"An
    > error occured installing the tap-win32 device driver". Does Colinux
work on
    > NT4 at all, or it's just my PC setup problem?
    >
    > BTW, I have colinux running on my XP box working fine.

    At this phase of development it is only expected to run ok in Win2000
    and XP.

    I don't think it should be too difficult to make it work on NT4 (with a
    recent Service Pack, at least), but it may be premature to think about
    porting to old machines (for now at least).

    In relation to Win9x, it would need a big patch to work, but no one says
    it's impossible. But I don't know if there will be someone interested on
    doing that port....

    Regards,
    ~Nuno Lucas



    --__--__--

    Message: 5
    Date: Thu, 9 Sep 2004 22:52:00 +0300
    From: Dan Aloni
    To: col...@li...
    Cc: "Joe Wells (reverse mailbox letters for non-public replies)" ,
    gboutwel , Peng ,
    col...@li...,
    col...@li...
    Subject: [coLinux-users] A fix for the SIGFPE problem (>20040622)

    Hello,

    Thanks to Joe I was able to reproduce the problem locally and worked
    on a fix which makes the problem disappear.

    For the technical aspect: Since until now none of the code in
    arch/i386/kernel/head.S actually runs when coLinux starts I've suspected
    that there could be some initialization problem - if the kernel is not
    precisely aware of the CPU's capabilities and decides not to save the
    MMX registers between context switches it can indeed cause a problem. In
    a multi-process scenario (such as the one with gdb and Joe's program)
the
    problem was indeed triggered before.

    I've already commited the patch into the monotone server. If you can
    check that firefox / xdvi aren't crashing anymore I'd be glad.



    diff -u b/arch/i386/kernel/cooperative.c
b/arch/i386/kernel/cooperative.c
    --- b/arch/i386/kernel/cooperative.c
    +++ b/arch/i386/kernel/cooperative.c
    @@ -85,6 +85,15 @@
    __asm__ __volatile__("movl %%cr4, %0" : "=r" (mmu_cr4_features));
    }

    +asm(
    + ""
    + ".section .text\n"
    + ".globl co_arch_start_kernel\n"
    + "co_arch_start_kernel:\n"
    + " call co_startup_entry\n"
    + ".previous\n"
    + "");
    +
    void co_start_arch(void)
    {
    co_early_cpu_init();
    diff -u b/arch/i386/kernel/head.S b/arch/i386/kernel/head.S
    --- b/arch/i386/kernel/head.S
    +++ b/arch/i386/kernel/head.S
    @@ -238,6 +238,7 @@
    rep
    movsl
    1:
    +ENTRY(co_startup_entry)
    checkCPUtype:

    movl $-1,X86_CPUID # -1 for no CPUID initially
    diff -u b/include/linux/cooperative_internal.h
b/include/linux/cooperative_internal.h
    --- b/include/linux/cooperative_internal.h
    +++ b/include/linux/cooperative_internal.h
    @@ -28,6 +28,7 @@
    extern void co_idle_processor(void);
    extern void co_terminate(co_termination_reason_t reason);
    extern void co_start_kernel(void);
    +extern void co_arch_start_kernel(void);
    extern void co_handle_jiffies(long count);

    extern void co_send_message(co_module_t from,
    diff -u b/kernel/cooperative.c b/kernel/cooperative.c
    --- b/kernel/cooperative.c
    +++ b/kernel/cooperative.c
    @@ -48,8 +48,9 @@
    memcpy(co_boot_parameters, &co_passage_page->params[10],
    sizeof(co_boot_parameters));

    - start_kernel();
    + co_arch_start_kernel();

    + /* should never be reached */
    co_terminate(CO_TERMINATE_END);
    }




    --
    Dan Aloni
    da...@co...



    --__--__--

    _______________________________________________
    coLinux-users mailing list
    coL...@li...
    https://lists.sourceforge.net/lists/listinfo/colinux-users


    End of coLinux-users Digest

  Yahoo! India Matrimony: Find your life partner online.

[coLinux-users] linux kernel port

[<stu...@ya...>]

hi there ,
 
like uml is a a port of linux kernel to  a linux kernel , and it uses the architectural port  --ARCH=um--
which one does coLinux use?
 
thanks 
shruti 
col...@li... wrote:
Send coLinux-users mailing list submissions to
col...@li...

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/colinux-users
or, via email, send a message with subject or body 'help' to
col...@li...

You can reach the person managing the list at
col...@li...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of coLinux-users digest..."


Today's Topics:

1. Re: Random signal 11 problems? (Jules)
2. Re: Random signal 11 problems? (Chuck Adams)
3. Does colinux work on NT4 (Shi, Jue)
4. Re: Does colinux work on NT4 (Nuno Lucas)
5. A fix for the SIGFPE problem (>20040622) (Dan Aloni)

--__--__--

Message: 1
Date: Thu, 09 Sep 2004 09:40:24 +0100
From: Jules 
To: col...@li...
Subject: [coLinux-users] Re: Random signal 11 problems?

>
>
>It may be outdated and may not apply to your
>problem, but it is probably worth looking at
>the sig 11 FAQ:
>http://www.bitwizard.nl/sig11/
>

Thanks. I'm pretty sure this isn't hardware related, as the same system 
runs the kernel supplied with the binary package just fine, plus kernels 
compiled by myself work OK without colinux.

I've compiled a copy of the kernel with the config file supplied in the 
colinux source distribution, and that seems to be working, I'm going 
through a second compile of it now, with it running, and it seems to be 
pretty stable. It's got a lot farther than the last one did, at least.

So I guess it was one of the config options that did it. Are there any 
that are known to be dangerous with colinux? The main changes I made 
were optimising for my processor environment (changed from CONFIG_M586 
to CONFIG_MK7, disabled CONFIG_X86_GENERIC, all consequential changes 
from this). I also killed support for a.out binaries, moved binfmt_misc 
to a module, switched off the kernel debugging options, and added 
support for unloading modules.

There were other changes too, but mostly relating to filesystems, which 
I don't think are likely candidates.

Any suggestions on what may have caused the problem?


--__--__--

Message: 2
Date: Thu, 09 Sep 2004 09:51:36 -0700
From: Chuck Adams 
To: Sandy Harris 
Cc: col...@li...
Subject: Re: [coLinux-users] Random signal 11 problems?

Sandy Harris wrote:

> It may be outdated and may not apply to your
> problem, but it is probably worth looking at
> the sig 11 FAQ:
> http://www.bitwizard.nl/sig11/


Actually it's almost never worth looking at that FAQ. It's pure 
baloney. I remember this FAQ getting thrown at me before ... Yes, 
memory glitches may cause segfaults and if random apps are failing at 
random times, it's worth running memtest. But there are claims in that 
FAQ that are just absurd. I always found it odd how it was *just* gcc 
that somehow "stressed the memory" and therefore just gcc that would 
segfault. Occam's razor was right all along of course -- it was a bug 
in gcc. Either that or the next upgrade magically fixed my hardware.

chuck



--__--__--

Message: 3
From: "Shi, Jue" 
To: "'col...@li...'"

Date: Thu, 9 Sep 2004 10:15:18 -0700 
Subject: [coLinux-users] Does colinux work on NT4


Hi,

I tried to install Colinux on Windows NT4, and get an error message "An
error occured installing the tap-win32 device driver". Does Colinux work on
NT4 at all, or it's just my PC setup problem?

BTW, I have colinux running on my XP box working fine.

Thanks,
JueS


--__--__--

Message: 4
Date: Thu, 09 Sep 2004 18:38:35 +0100
From: Nuno Lucas 
To: col...@li...
Cc: "Shi, Jue" 
Subject: Re: [coLinux-users] Does colinux work on NT4

Shi, Jue, dando pulos de alegria, escreveu :
> Hi,
> 
> I tried to install Colinux on Windows NT4, and get an error message "An
> error occured installing the tap-win32 device driver". Does Colinux work on
> NT4 at all, or it's just my PC setup problem?
> 
> BTW, I have colinux running on my XP box working fine.

At this phase of development it is only expected to run ok in Win2000 
and XP.

I don't think it should be too difficult to make it work on NT4 (with a 
recent Service Pack, at least), but it may be premature to think about 
porting to old machines (for now at least).

In relation to Win9x, it would need a big patch to work, but no one says 
it's impossible. But I don't know if there will be someone interested on 
doing that port....

Regards,
~Nuno Lucas



--__--__--

Message: 5
Date: Thu, 9 Sep 2004 22:52:00 +0300
From: Dan Aloni 
To: col...@li...
Cc: "Joe Wells (reverse mailbox letters for non-public replies)" ,
gboutwel , Peng ,
col...@li...,
col...@li...
Subject: [coLinux-users] A fix for the SIGFPE problem (>20040622)

Hello,

Thanks to Joe I was able to reproduce the problem locally and worked
on a fix which makes the problem disappear.

For the technical aspect: Since until now none of the code in 
arch/i386/kernel/head.S actually runs when coLinux starts I've suspected
that there could be some initialization problem - if the kernel is not 
precisely aware of the CPU's capabilities and decides not to save the 
MMX registers between context switches it can indeed cause a problem. In 
a multi-process scenario (such as the one with gdb and Joe's program) the 
problem was indeed triggered before.

I've already commited the patch into the monotone server. If you can
check that firefox / xdvi aren't crashing anymore I'd be glad.



diff -u b/arch/i386/kernel/cooperative.c b/arch/i386/kernel/cooperative.c
--- b/arch/i386/kernel/cooperative.c
+++ b/arch/i386/kernel/cooperative.c
@@ -85,6 +85,15 @@
__asm__ __volatile__("movl %%cr4, %0" : "=r" (mmu_cr4_features));
}

+asm(
+ ""
+ ".section .text\n"
+ ".globl co_arch_start_kernel\n"
+ "co_arch_start_kernel:\n"
+ " call co_startup_entry\n"
+ ".previous\n"
+ "");
+
void co_start_arch(void)
{
co_early_cpu_init();
diff -u b/arch/i386/kernel/head.S b/arch/i386/kernel/head.S
--- b/arch/i386/kernel/head.S
+++ b/arch/i386/kernel/head.S
@@ -238,6 +238,7 @@
rep
movsl
1:
+ENTRY(co_startup_entry)
checkCPUtype:

movl $-1,X86_CPUID # -1 for no CPUID initially
diff -u b/include/linux/cooperative_internal.h b/include/linux/cooperative_internal.h
--- b/include/linux/cooperative_internal.h
+++ b/include/linux/cooperative_internal.h
@@ -28,6 +28,7 @@
extern void co_idle_processor(void);
extern void co_terminate(co_termination_reason_t reason);
extern void co_start_kernel(void);
+extern void co_arch_start_kernel(void);
extern void co_handle_jiffies(long count);

extern void co_send_message(co_module_t from, 
diff -u b/kernel/cooperative.c b/kernel/cooperative.c
--- b/kernel/cooperative.c
+++ b/kernel/cooperative.c
@@ -48,8 +48,9 @@
memcpy(co_boot_parameters, &co_passage_page->params[10], 
sizeof(co_boot_parameters));

- start_kernel();
+ co_arch_start_kernel();

+ /* should never be reached */
co_terminate(CO_TERMINATE_END);
}




-- 
Dan Aloni
da...@co...



--__--__--

_______________________________________________
coLinux-users mailing list
coL...@li...
https://lists.sourceforge.net/lists/listinfo/colinux-users


End of coLinux-users Digest

Yahoo! India Matrimony: Find your life partneronline.

Re: [coLinux-users] Re: snapshot 20040910 (0.6.2-pre1)

[Eric S. J. <es...@ha...>]

Nuno Lucas wrote:

> Eric S. Johansson, dando pulos de alegria, escreveu :
> 
>> Nuno Lucas wrote:
>>
>>> This has to do with devfs naming scheme and Gentoo uses and needs it 
>>> to run.
>>> But devfs is being deprecated in favor of udev. Don't know how the 
>>> udev naming scheme is.
>>
>>
>>
>> would it be too obnoxious to migrate straight to udev?
> 
> 
> No, there are many who are doing it already. It simply isn't the default 
> for gentoo yet (maybe because the devs were busy replacing XFree with 
> X.Org as the default package ;).
...

apologies.  I did not frame the question right.  Maybe a better question 
to ask would be since the world is moving towards udev, would it be 
appropriate for co-linux to require use of udev as its baseline?

no big deal either way I'm just wondering if it would simplify the 
installation process.

---eric

Re: [coLinux-users] Re: enabling sound support under colinux?

[Nuno L. <lu...@nl...>]

Greg Boehnlein, dando pulos de alegria, escreveu :
> Would it be possible, given the appropriate drivers, for CoLinux to be 
> able to access a PCI card on the PCI bus? Specifically, Asterisk uses 
> kernel modules (Zaptel) to communicate with Digium's hardware such as the 
> X100P card. This relies on a very strict 1,000 Hz interrupt timing to 
> ensure proper audio.

I think your biggest problem (at least at the current colinux state) 
would be the strict timing you require. Timer interrupts are more or 
less emulated now, and could not give the resolution you intend.

But you would have problems if you use DMA in same way, as that is 
controlled by windows.

A possible solution to your problem would be a sort of "linux proxy 
drivers", who would transfer messages between your application and a 
windows driver. That driver would then make the required low level work 
(using the appropriate windows mechanisms).

Hope I have helped you.

Regards,
~Nuno Lucas

Re: [coLinux-users] Re: enabling sound support under colinux?

[Greg B. <da...@na...>]

On Sat, 11 Sep 2004, Nuno Lucas wrote:

> >>hello I am trying to use yasr its a screen reader for the blind, I did 
> >>the following apt-get install yasr flite eflite
> >>yasr is the screen reader and flite and eflite is the tts engine stuff it needs how ever when I run 
> >>yasr at the command prompt I don't hear any speech.
> >>if sound support is not supported how easy would it be to put both in 
> >>colinux, and in astwind? whitch is the colinux with asterisk support.
> >>thanks
> >>hank
> > 
> > Hank,
> > 	I doubt that the CoLinux guys know about AstWind, but for those 
> > that are curious please check out: 
> > http://www.digium.com/index.php?menu=astwind
> > 
> > As for CoLinux sound support, I'm not sure how that would be accomplished, 
> > as I don't think that CoLinux supports Audio devices.
> 
> No, not yet ;)
> But there are some reports of geting sound to work using the network.
> I think there is something about it in the wiki. You should have a look 
> there.
> There were some posts about it in this mailing list or in the 
> colinux-devel list. Make a little search and you may have luck.

Would it be possible, given the appropriate drivers, for CoLinux to be 
able to access a PCI card on the PCI bus? Specifically, Asterisk uses 
kernel modules (Zaptel) to communicate with Digium's hardware such as the 
X100P card. This relies on a very strict 1,000 Hz interrupt timing to 
ensure proper audio.

-- 
    Vice President of N2Net, a New Age Consulting Service, Inc. Company
         http://www.n2net.net Where everything clicks into place!
                             KP-216-121-ST

[coLinux-users] Re: enabling sound support under colinux?

[Nuno L. <nt...@nl...>]

Greg Boehnlein, dando pulos de alegria, escreveu :
> On Fri, 10 Sep 2004, hank smith wrote:
>>hello I am trying to use yasr its a screen reader for the blind, I did 
>>the following apt-get install yasr flite eflite
>>yasr is the screen reader and flite and eflite is the tts engine stuff it needs how ever when I run 
>>yasr at the command prompt I don't hear any speech.
>>if sound support is not supported how easy would it be to put both in 
>>colinux, and in astwind? whitch is the colinux with asterisk support.
>>thanks
>>hank
> 
> Hank,
> 	I doubt that the CoLinux guys know about AstWind, but for those 
> that are curious please check out: 
> http://www.digium.com/index.php?menu=astwind
> 
> As for CoLinux sound support, I'm not sure how that would be accomplished, 
> as I don't think that CoLinux supports Audio devices.

No, not yet ;)
But there are some reports of geting sound to work using the network.
I think there is something about it in the wiki. You should have a look 
there.
There were some posts about it in this mailing list or in the 
colinux-devel list. Make a little search and you may have luck.

Regards,
~Nuno Lucas

[coLinux-users] Re: snapshot 20040910 (0.6.2-pre1)

[Nuno L. <nt...@nl...>]

Eric S. Johansson, dando pulos de alegria, escreveu :
> Nuno Lucas wrote:
> 
>> This has to do with devfs naming scheme and Gentoo uses and needs it 
>> to run.
>> But devfs is being deprecated in favor of udev. Don't know how the 
>> udev naming scheme is.
> 
> 
> would it be too obnoxious to migrate straight to udev?

No, there are many who are doing it already. It simply isn't the default 
for gentoo yet (maybe because the devs were busy replacing XFree with 
X.Org as the default package ;).

Another reason would be because the stable gentoo kernel is still 
2.4.26, and udev works better with the 2.6 (or is required?)

Look in the gentoo forums. I know there are good tutorials on doing the 
move, I simply didn't care about it enough.

Regards,
~Nuno Lucas

[coLinux-users] Re: Does colinux work on NT4

[Nuno L. <nt...@nl...>]

Shi, Jue, dando pulos de alegria, escreveu :
> My PC has the service patch 6a which I believ is the latest one. I also
> tried coLinux-20040910.exe. In addition to the error message mentioned
> before, I also get " The C:\colinux\linux.sys device driver could not locate
> the entry point ExFreePoolWithTag in driver ntoskrnl.exe", which didn't
> occur when I tried coLinux-0.6.1.exe.
 >
> I think there should be something needs to be done in the colinux to make it
> work. 

Yes, the driver model is not the same between NT 4 and NT 5 and 5.1 (2k 
and XP).

That function is only available in the 2000 DDK (not sure, but I think I 
got this right).

Also, even if the driver worked, the user space daemons use 2000 and 
higher specific functions (specially in the NT console).

 > I'd really like to have the climux on my NT work PC which I can't 
change OS.

Hehe, you need to have patient, as colinux is still young, and more work 
needs to be done before starting to think on porting to all different OS 
versions.

Maybe there is some undocumented function that does the some thing, I 
have no idea...

Regards,
~Nuno Lucas

RE: [coLinux-users] Does colinux work on NT4

[Shi, J. <Ju...@or...>]

My PC has the service patch 6a which I believ is the latest one. I also
tried coLinux-20040910.exe. In addition to the error message mentioned
before, I also get " The C:\colinux\linux.sys device driver could not locate
the entry point ExFreePoolWithTag in driver ntoskrnl.exe", which didn't
occur when I tried coLinux-0.6.1.exe.

I think there should be something needs to be done in the colinux to make it
work. 
I'd really like to have the climux on my NT work PC which I can't change OS.

Thanks,
JueS

-----Original Message-----
From: Nuno Lucas [mailto:lu...@nl...]
Sent: Thursday, September 09, 2004 10:39 AM
To: col...@li...
Cc: Shi, Jue
Subject: Re: [coLinux-users] Does colinux work on NT4


Shi, Jue, dando pulos de alegria, escreveu :
> Hi,
> 
> I tried to install Colinux on Windows NT4, and get an error message "An
> error occured installing the tap-win32 device driver". Does Colinux work
on
> NT4 at all, or it's just my PC setup problem?
> 
> BTW, I have colinux running on my XP box working fine.

At this phase of development it is only expected to run ok in Win2000 
and XP.

I don't think it should be too difficult to make it work on NT4 (with a 
recent Service Pack, at least), but it may be premature to think about 
porting to old machines (for now at least).

In relation to Win9x, it would need a big patch to work, but no one says 
it's impossible. But I don't know if there will be someone interested on 
doing that port....

Regards,
~Nuno Lucas

[coLinux-users] Re: snapshot 20040910 (0.6.2-pre1)

[Ian A. <ia...@ab...>]

On 10/09/2004 18:32, Nuno Lucas wrote:
> Ian Abbott, dando pulos de alegria, escreveu :
> 
>> I'm just wondering what the reason for this notation change is, 
>> particularly for aliases.  Sure, the /dev/cobd/X notation helps to 
>> keep the /dev directory tidy, but /dev/hda/X seems to be going a bit 
>> too far as /dev/hda is normally a block special file, not a directory!
> 
> This has to do with devfs naming scheme and Gentoo uses and needs it to 
> run.

But when I run Gentoo natively with a 2.6.x kernel with devfs 
enabled, I get the normal /dev/hda1 etc.

Re: [coLinux-users] enabling sound support under colinux?

[Greg B. <da...@na...>]

On Fri, 10 Sep 2004, hank smith wrote:

> hello I am trying to use yasr its a screen reader for the blind, I did 
> the following apt-get install yasr flite eflite
> yasr is the screen reader and flite and eflite is the tts engine stuff it needs how ever when I run 
> yasr at the command prompt I don't hear any speech.
> if sound support is not supported how easy would it be to put both in 
> colinux, and in astwind? whitch is the colinux with asterisk support.
> thanks
> hank

Hank,
	I doubt that the CoLinux guys know about AstWind, but for those 
that are curious please check out: 
http://www.digium.com/index.php?menu=astwind

As for CoLinux sound support, I'm not sure how that would be accomplished, 
as I don't think that CoLinux supports Audio devices.

-- 
    Vice President of N2Net, a New Age Consulting Service, Inc. Company
         http://www.n2net.net Where everything clicks into place!
                             KP-216-121-ST

Re: [coLinux-users] Re: snapshot 20040910 (0.6.2-pre1)

[Eric S. J. <es...@ha...>]

Nuno Lucas wrote:
> This has to do with devfs naming scheme and Gentoo uses and needs it to 
> run.
> But devfs is being deprecated in favor of udev. Don't know how the udev 
> naming scheme is.

would it be too obnoxious to migrate straight to udev?

Re: [coLinux-users] Re: snapshot 20040910 (0.6.2-pre1)

[Nuno L. <lu...@nl...>]

Ian Abbott, dando pulos de alegria, escreveu :
> I'm just wondering what the reason for this notation change is, 
> particularly for aliases.  Sure, the /dev/cobd/X notation helps to keep 
> the /dev directory tidy, but /dev/hda/X seems to be going a bit too far 
> as /dev/hda is normally a block special file, not a directory!

This has to do with devfs naming scheme and Gentoo uses and needs it to run.
But devfs is being deprecated in favor of udev. Don't know how the udev 
naming scheme is.

You can have the normal hda? names as symlinks to the others. They 
simply aren't created by default.

Note that this is Gentoo specific (more devfs specific, really). Is not 
related to coLinux in any way.

Regards,
~Nuno Lucas

[coLinux-users] Re: snapshot 20040910 (0.6.2-pre1)

[Ian A. <ia...@ab...>]

On 10/09/2004 15:39, Dan Aloni wrote:
> The problem with 0.6.2 is that people are expected to move from 2.4.x 
> based coLinux system to 2.6.x based system on upgrade from 0.6.1 and 
> prir. Many of the newbie users would wonder why their Gentoo stops 
> working on this move (technically a script breakage over the /dev/cobdX-
> to-/dev/cobd/X notation change caused by devfs). 

I'm just wondering what the reason for this notation change is, 
particularly for aliases.  Sure, the /dev/cobd/X notation helps to 
keep the /dev directory tidy, but /dev/hda/X seems to be going a bit 
too far as /dev/hda is normally a block special file, not a directory!

[coLinux-users] Re: [coLinux-devel] A fix for the SIGFPE problem (>20040622)

[<sl...@bl...>]

Dan Aloni <da...@co...> writes:

> Thanks to Joe I was able to reproduce the problem locally and worked
> on a fix which makes the problem disappear.

Yay!  Thank you, thank you, thank you.

> For the technical aspect: Since until now none of the code in 
> arch/i386/kernel/head.S actually runs when coLinux starts I've suspected
> that there could be some initialization problem - if the kernel is not 
> precisely aware of the CPU's capabilities and decides not to save the 
> MMX registers between context switches it can indeed cause a problem. In 
> a multi-process scenario (such as the one with gdb and Joe's program) the 
> problem was indeed triggered before.

Here's my big question:  How could things work at all?  Was it
sometimes saving MMX registers between context switches and sometimes
not?  I saw a lot of behavior under the debugger which left me puzzled
about this.

> I've already commited the patch into the monotone server. If you can
> check that firefox / xdvi aren't crashing anymore I'd be glad.

Okay, I am downloading the 20040910 snapshot.  (Am I correct in
assuming the fix is in this snapshot?)  I hope I will have time to try
it out next week.

-- 
Joe

[coLinux-users] enabling sound support under colinux?

[hank s. <ha...@ha...>]

hello I am trying to use yasr its a screen reader for the blind, I did =
the following
apt-get install yasr flite eflite
yasr is the screen reader and flite and eflite is the tts engine stuff =
it needs how ever when I run=20
yasr at the command prompt I don't hear any speech.
if sound support is not supported how easy would it be to put both in =
colinux, and in astwind? whitch is the colinux with asterisk support.
thanks
hank
----------------------------------------
My Inbox is protected by SPAMfighter
1063 spam mails have been blocked so far.
Download free www.spamfighter.com today!

[coLinux-users] snapshot 20040910 (0.6.2-pre1)

[Dan A. <da...@co...>]

Hello,

I've released a snapshot to bring us a step closer to 0.6.2-final.

    http://www.colinux.org/snapshots/coLinux-20040910.exe

The problem with 0.6.2 is that people are expected to move from 2.4.x 
based coLinux system to 2.6.x based system on upgrade from 0.6.1 and 
prir. Many of the newbie users would wonder why their Gentoo stops 
working on this move (technically a script breakage over the /dev/cobdX-
to-/dev/cobd/X notation change caused by devfs). 

Actually I think we should come with some sort of standard for a coLinux 
root file system, e.g a /etc/colinux file that could hint a fix-me-up 
initrd what's going on instead of auto-guessing.

Apropos initrd, this snapshot contains a beta version of an initrd 
image that installs the kernel modules for the supplied vmlinux unto 
the root filesystem (thanks George). You can test it simply by 
adding the element: <initrd path="initrd.gz" />.

Anyway, the list of changes from the last snapshot which was quite a 
while ago (20040710) includes:

  * If the MAC address is unspecified, a random MAC is choosed 
    using the familiar TAP prefix (00:FF:XX:XX:XX:XX).
  * Bug fix: Reception and delivery of network packets bigger than
    2kb.
  * Bug fix: Consoles and/or other daemons fail to connect to 
    colinux-daemon on startup (this is Windows only).
  * Bug fix: Stop reboots where different gcc compiler versions are 
    used to compile linux.sys & vmlinux, with an error/warning 
    (George Boutwell).
  * Enhanced coLinux keyboard handling support (sends raw scan codes
    from Windows to linux) (Nuno Lucas).
  * Bug fix: bad initialization caused unexpected SIGFPE for programs 
    compiled with -mpentium4 (me)

You might also want to take a look at the monotone ChangeLog (under
the snapshot directory for the monotone-declined users).

-- 
Dan Aloni
da...@co...

Re: [coLinux-users] Random signal 11 problems?

[Doctor B. <do...@gm...>]

Yes.  The general problem with the FAQ is it assumes the gcc and
kernel have been well tested under all possible configurations.  I
have seen sig 11 problems on many different hardware platforms in many
different cases.  In most cases I attributed it to an inadequately
tested configuration, and the fact most people do not report the sig
11 problem when it occurs.  Why?  Well if the location of the error
depends on the hardware configuration you are using, it is unlikely
someone else would be able to successfully debug the problem without
access to the same machine.  Sometimes it is repeatable on the same
file, regardless of current memory usage, sometimes not.  Most
commonly I've seen the problem under Solaris, where the bootstrapping
process is very particular about what set of bin utils you use, what
compiler you bootstrap from etc.  It seems after each major upgrade of
gcc, the bootstrapping order I need to follow to get a compiler that
does not sig 11 under Solaris is always slightly different.

Does that mean it isn't a hardware problem?  Not at all.  It could be
that the many different boxes I've seen the problem in the past all
share a similar design flaw, and finding a way of doing a majic build
of gcc that does not have the problem is just working around the
problem.  It is also possible that in the upgrade, someone added code
to workaround the hardware problem.  Possible, but not likely.

Under coLinux, I believe the most common culprit is corrupt or heavily
fragmented swap files.

                                  Bill


On Thu, 09 Sep 2004 09:51:36 -0700, Chuck Adams <ch...@da...> wrote:
> Sandy Harris wrote:
> 
> > It may be outdated and may not apply to your
> > problem, but it is probably worth looking at
> > the sig 11 FAQ:
> > http://www.bitwizard.nl/sig11/
> 
> 
> Actually it's almost never worth looking at that FAQ.  It's pure
> baloney.  I remember this FAQ getting thrown at me before ... Yes,
> memory glitches may cause segfaults and if random apps are failing at
> random times, it's worth running memtest.  But there are claims in that
> FAQ that are just absurd.  I always found it odd how it was *just* gcc
> that somehow "stressed the memory" and therefore just gcc that would
> segfault.  Occam's razor was right all along of course -- it was a bug
> in gcc.  Either that or the next upgrade magically fixed my hardware.
> 
> chuck
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
> Project Admins to receive an Apple iPod Mini FREE for your judgement on
> who ports your project to Linux PPC the best. Sponsored by IBM.
> Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
> 
> 
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>

Re: [coLinux-users] Random signal 11 problems?

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

Jules wrote:
> I've been using the colinux 2004-07-10 snapshot with some success for a 
> little while now (host system WinXP Pro), but recently I decided to 
> compile a new kernel as the one included with the snapshot lacks a few 
> features I wanted.
> 
> I downloaded the source to the 2.6.7 kernel and applied the patch 
> included in the colinux source to it, made a few changes to the config 
> and then compiled it.  The resulting kernel runs, but occasionally 
> processes die unexpectedly with a signal 11.  I've also seen corruption 
> on my root ext3 filesystem -- I'm not sure if this was related or not.
> 
> Has anyone encountered similar problems, or is it just me?
> 
> For reference, my distribution is SuSE 9.1 personal with a load of extra 
> development tools downloaded from the standard SuSE 9.1 drectory.

If you recompile kernel, you should also recompile colinux daemons.
It's strictly recommented, to use the same GCC version for kernel and 
daemons.

-- 
Henry Nestler

[coLinux-users] A fix for the SIGFPE problem (>20040622)

[Dan A. <da...@co...>]

Hello,

Thanks to Joe I was able to reproduce the problem locally and worked
on a fix which makes the problem disappear.

For the technical aspect: Since until now none of the code in 
arch/i386/kernel/head.S actually runs when coLinux starts I've suspected
that there could be some initialization problem - if the kernel is not 
precisely aware of the CPU's capabilities and decides not to save the 
MMX registers between context switches it can indeed cause a problem. In 
a multi-process scenario (such as the one with gdb and Joe's program) the 
problem was indeed triggered before.

I've already commited the patch into the monotone server. If you can
check that firefox / xdvi aren't crashing anymore I'd be glad.



diff -u b/arch/i386/kernel/cooperative.c b/arch/i386/kernel/cooperative.c
--- b/arch/i386/kernel/cooperative.c
+++ b/arch/i386/kernel/cooperative.c
@@ -85,6 +85,15 @@
 	__asm__ __volatile__("movl %%cr4, %0" : "=r" (mmu_cr4_features));
 }
 
+asm(
+	""
+	".section .text\n"
+	".globl co_arch_start_kernel\n"
+	"co_arch_start_kernel:\n"
+	"       call co_startup_entry\n"
+	".previous\n"
+	"");
+
 void co_start_arch(void)
 {
 	co_early_cpu_init();
diff -u b/arch/i386/kernel/head.S b/arch/i386/kernel/head.S
--- b/arch/i386/kernel/head.S
+++ b/arch/i386/kernel/head.S
@@ -238,6 +238,7 @@
 	rep
 	movsl
 1:
+ENTRY(co_startup_entry)
 checkCPUtype:
 
 	movl $-1,X86_CPUID		#  -1 for no CPUID initially
diff -u b/include/linux/cooperative_internal.h b/include/linux/cooperative_internal.h
--- b/include/linux/cooperative_internal.h
+++ b/include/linux/cooperative_internal.h
@@ -28,6 +28,7 @@
 extern void co_idle_processor(void);
 extern void co_terminate(co_termination_reason_t reason);
 extern void co_start_kernel(void);
+extern void co_arch_start_kernel(void);
 extern void co_handle_jiffies(long count);
 
 extern void co_send_message(co_module_t from, 
diff -u b/kernel/cooperative.c b/kernel/cooperative.c
--- b/kernel/cooperative.c
+++ b/kernel/cooperative.c
@@ -48,8 +48,9 @@
         memcpy(co_boot_parameters, &co_passage_page->params[10], 
                sizeof(co_boot_parameters));
 
-	start_kernel();
+	co_arch_start_kernel();
 
+	/* should never be reached */
 	co_terminate(CO_TERMINATE_END);
 }
 



-- 
Dan Aloni
da...@co...

Re: [coLinux-users] Does colinux work on NT4

[Nuno L. <lu...@nl...>]

Shi, Jue, dando pulos de alegria, escreveu :
> Hi,
> 
> I tried to install Colinux on Windows NT4, and get an error message "An
> error occured installing the tap-win32 device driver". Does Colinux work on
> NT4 at all, or it's just my PC setup problem?
> 
> BTW, I have colinux running on my XP box working fine.

At this phase of development it is only expected to run ok in Win2000 
and XP.

I don't think it should be too difficult to make it work on NT4 (with a 
recent Service Pack, at least), but it may be premature to think about 
porting to old machines (for now at least).

In relation to Win9x, it would need a big patch to work, but no one says 
it's impossible. But I don't know if there will be someone interested on 
doing that port....

Regards,
~Nuno Lucas

[coLinux-users] Does colinux work on NT4

[Shi, J. <Ju...@or...>]

Hi,

I tried to install Colinux on Windows NT4, and get an error message "An
error occured installing the tap-win32 device driver". Does Colinux work on
NT4 at all, or it's just my PC setup problem?

BTW, I have colinux running on my XP box working fine.

Thanks,
JueS

Re: [coLinux-users] Random signal 11 problems?

[Chuck A. <ch...@da...>]

Sandy Harris wrote:

> It may be outdated and may not apply to your
> problem, but it is probably worth looking at
> the sig 11 FAQ:
> http://www.bitwizard.nl/sig11/


Actually it's almost never worth looking at that FAQ.  It's pure 
baloney.  I remember this FAQ getting thrown at me before ... Yes, 
memory glitches may cause segfaults and if random apps are failing at 
random times, it's worth running memtest.  But there are claims in that 
FAQ that are just absurd.  I always found it odd how it was *just* gcc 
that somehow "stressed the memory" and therefore just gcc that would 
segfault.  Occam's razor was right all along of course -- it was a bug 
in gcc.  Either that or the next upgrade magically fixed my hardware.

chuck

[coLinux-users] Re: Random signal 11 problems?

[Jules <ju...@ds...>]

>
>
>It may be outdated and may not apply to your
>problem, but it is probably worth looking at
>the sig 11 FAQ:
>http://www.bitwizard.nl/sig11/
>

Thanks.  I'm pretty sure this isn't hardware related, as the same system 
runs the kernel supplied with the binary package just fine, plus kernels 
compiled by myself work OK without colinux.

I've compiled a copy of the kernel with the config file supplied in the 
colinux source distribution, and that seems to be working,  I'm going 
through a second compile of it now, with it running, and it seems to be 
pretty stable.  It's got a lot farther than the last one did, at least.

So I guess it was one of the config options that did it.  Are there any 
that are known to be dangerous with colinux?  The main changes I made 
were optimising for my processor environment (changed from CONFIG_M586 
to CONFIG_MK7, disabled CONFIG_X86_GENERIC, all consequential changes 
from this).  I also killed support for a.out binaries, moved binfmt_misc 
to a module, switched off the kernel debugging options, and added 
support for unloading modules.

There were other changes too, but mostly relating to filesystems, which 
I don't think are likely candidates.

Any suggestions on what may have caused the problem?

Re: [coLinux-users] Win XP Bridged Network Disconnecting

[overbored <ove...@ov...>]

That's right.

hank smith wrote:

> and your basicly running a  router hooked up to a nic card?
> ----- Original Message ----- From: "overbored" <ove...@ov...>
> To: "hank smith" <ha...@ha...>; 
> <col...@li...>
> Sent: Wednesday, September 08, 2004 5:49 PM
> Subject: Re: [coLinux-users] Win XP Bridged Network Disconnecting
> 
> 
>> Perhaps I got lucky, it didn't seem so complicated. I just followed 
>> the instructions under 
>> http://www.colinux.org/wiki/index.php/coLinuxNetworking ("Using native 
>> network bridge support in Windows XP"). I ran the CoLinux setup 
>> executable. That gave me a Local Area Connection 2 under Network 
>> Connections. I then selected the two Local Area Connections, 
>> right-clicked, and chose Bridge. In the default.colinux.xml file I have:
>>
>>     <network index="0" type="tap" />
>>
>> All this worked before, but not anymore; creating that bridge just 
>> disconnects me from everything.
>>
>> hank smith wrote:
>>
>>> what the heck did you do to get yours set up? I am using a netgear rp 
>>> 614 router and am having a heck of a time getting mine networked, I 
>>> even did what the wicki suggested with no success
>>> I was trying astwind whitch is a asterisk version of colinux asterisk 
>>> is a open source pbx and I even tried it on the regular colinux with 
>>> no luck.
>>> I am stuck  any help is greatly appreciated.
>>> you got farther then I did with getting yours online
>>> thanks
>>> hank
>>> ----- Original Message -----
>>>
>>>> Hi, I was able to get XP's native bridged networking going just fine 
>>>> before (I'm on a home LAN with one of those Linksys cable/DSL DHCP 
>>>> routers). However, I temporarily removed my Local Area Connection 
>>>> from the bridge (to appease my ISP's tech support guy who thought 
>>>> the bridged network was why my Internet connection was slow). But 
>>>> now when I try to add my Local Area Connection back to the bridge, I 
>>>> get disconnected; I can't reach my LAN or get on the net. I tried 
>>>> recreating the bridge from scratch, but no difference. I saw the 
>>>> following details under the Support tab (which I think is identical 
>>>> to ipconfig's stdout):
>>>>
>>>> For the bridge:
>>>> IP: 169.254.169.245
>>>> Subnet: 255.255.0.0
>>>> Gateway: [blank]
>>>>
>>>> For my ethernet (Local Area Connection):
>>>> [all blank]
>>>>
>>>> For CoLinux TAP (Local Area Connection 2):
>>>> [all blank]
>>>>
>>>> I tried hitting Repair for all three, to no avail (I think this just 
>>>> does the same as ipconfig /release followed by ipconfig /renew). For 
>>>> the bridge, there's a long pause before I see the error message.
>>>>
>>>> Anybody know what's going on? If it makes any difference, I have 
>>>> SP2, which has that application/port-based firewall, but I highly 
>>>> doubt it's the cause behind all this. Thanks in advance for any help.
>>>>
>>>>
>>>> -------------------------------------------------------
>>>> This SF.Net email is sponsored by BEA Weblogic Workshop
>>>> FREE Java Enterprise J2EE developer tools!
>>>> Get your free copy of BEA WebLogic Workshop 8.1 today.
>>>> http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
>>>> _______________________________________________
>>>> coLinux-users mailing list
>>>> coL...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/colinux-users
>>>
>>>
>>>
>>> ----------------------------------------
>>> My Inbox is protected by SPAMfighter
>>> 1009 spam mails have been blocked so far.
>>> Download free www.spamfighter.com today!
>>>
>>>
>>>
>>
> 
> ----------------------------------------
> My Inbox is protected by SPAMfighter
> 1011 spam mails have been blocked so far.
> Download free www.spamfighter.com today!
> 
> 
>