[gentoo-dev] MOSIX and kernel 2.4.6

[gentoo-dev] MOSIX and kernel 2.4.6

[jb3insf]

Hello,
I today I tried to upgarde to kernel 2.4.6 from portage/sys-kernel/linux-sources. It stops immediatly saying it cannot get MOSIX-1.0.5.I am doing a fresh install with build.10_rc5.Is there a way to fix this?.
Thanks
Jake

Re: [gentoo-dev] MOSIX and kernel 2.4.6

[Hendrik Visage]

On Sun, Jul 22, 2001 at 03:18:39PM -0700, jb3insf@chronic.unixabuse.org wrote:
> Hello,
> I today I tried to upgarde to kernel 2.4.6 from portage/sys-kernel/linux-sources. It stops immediatly saying it cannot get MOSIX-1.0.5.I am doing a fresh install with build.10_rc5.Is there a way to fix this?.

Fetch MOSIX-1.0.5 yourself.

But Caveat Emptor: -rc5's 2.4.6 is flaky as far as I can see.
Module support is broken based on some _mmx_* calls thats somehow
either not mangled, or mangled wrongly.

Advice:
 Install build-rc5 with a 2.4.4 kernel (I think I did a 2.4.4-r something),
and after that (Except if you need it the extra extentions) fetch
linux-2.4.6 yourself & do a manual installation.
(That's what I did, and yes, it's not "ebuild"/portage safe, but it works :)

Hendrik
a.k.a. hevisko
> Thanks
> Jake
> 
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@cvs.gentoo.org
> http://cvs.gentoo.org/mailman/listinfo/gentoo-dev

-- 
------------------------
Hendrik Visage
hvisage@envisage.co.za

Re: [gentoo-dev] MOSIX and kernel 2.4.6

[Daniel Robbins]

On Mon, Jul 23, 2001 at 02:00:31AM +0200, Hendrik Visage wrote:

> On Sun, Jul 22, 2001 at 03:18:39PM -0700, jb3insf@chronic.unixabuse.org wrote:
> > Hello,
> > I today I tried to upgarde to kernel 2.4.6 from portage/sys-kernel/linux-sources. It stops immediatly saying it cannot get MOSIX-1.0.5.I am doing a fresh install with build.10_rc5.Is there a way to fix this?.
> 
> Fetch MOSIX-1.0.5 yourself.
> 
> But Caveat Emptor: -rc5's 2.4.6 is flaky as far as I can see.
> Module support is broken based on some _mmx_* calls thats somehow
> either not mangled, or mangled wrongly.

Another caveat emptor: right now, the MOSIX support is in development and the "mosix"
USE variable will cause your linux-*-2.4.6 packages to be patched incorrectly.  I've
posted to the MOSIX list and have found a MOSIX user who may be interested in helping
test/improve MOSIX support in Gentoo Linux, but for now MOSIX support is still in
development.

-- 
Daniel Robbins					<drobbins@gentoo.org>
President/CEO					http://www.gentoo.org 
Gentoo Technologies, Inc.			

Re: [gentoo-dev] MOSIX and kernel 2.4.6

[Hendrik Visage]

Hmmm...
 Daniel, just were is the mosix USE flag DEactivated?

Stock standard build-rc5 installations all wants it into the kernel....
And yes, I'm using the stock standard make.conf with ONLY the i686 variables
uncommented in /etc/make.conf

Hendrik

On Sun, Jul 22, 2001 at 11:00:30PM -0600, Daniel Robbins wrote:
> 
> Another caveat emptor: right now, the MOSIX support is in development and the "mosix"
> USE variable will cause your linux-*-2.4.6 packages to be patched incorrectly.  I've
> posted to the MOSIX list and have found a MOSIX user who may be interested in helping
> test/improve MOSIX support in Gentoo Linux, but for now MOSIX support is still in
> development.
> 
> -- 
> Daniel Robbins					<drobbins@gentoo.org>
> President/CEO					http://www.gentoo.org 
> Gentoo Technologies, Inc.			
> 
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@cvs.gentoo.org
> http://cvs.gentoo.org/mailman/listinfo/gentoo-dev

-- 
------------------------
Hendrik Visage
hvisage@envisage.co.za

RE: [gentoo-dev] MOSIX and kernel 2.4.6

[Sean Mitchell]

> -----Original Message-----
> From: Hendrik Visage [mailto:hvisage@envisage.co.za]

> But Caveat Emptor: -rc5's 2.4.6 is flaky as far as I can see.
> Module support is broken based on some _mmx_* calls thats somehow
> either not mangled, or mangled wrongly.

I'm not sure about that, Hendrik. I had a lot of those problems with both
2.4.4ac9 and 2.4.6 and it seems to have something to do with broken
makefiles. There seem to be a lot of people with Durons (including
me)posting with unresolved _mmx_ symbol problems.

Cheers,

Sean

------------------------------------------------------------------------
 Sean Mitchell                                        Software Engineer
 smitchell@phoenix-interactive.com       Phoenix Interactive Design Inc
 tel. 519-679-2913 x237                        4th Floor, 137 Dundas St
 fax. 519 679 6773                          London, ON, Canada  N6A 1E9
                           ICQ# 104246806
------------------------------------------------------------------------ 

Re: [gentoo-dev] MOSIX and kernel 2.4.6

[Jerry A!]

On Mon, Jul 23, 2001 at 09:04:47AM -0400, Sean Mitchell wrote:
: > -----Original Message-----
: > From: Hendrik Visage [mailto:hvisage@envisage.co.za]
: 
: > But Caveat Emptor: -rc5's 2.4.6 is flaky as far as I can see.
: > Module support is broken based on some _mmx_* calls thats somehow
: > either not mangled, or mangled wrongly.
: 
: I'm not sure about that, Hendrik. I had a lot of those problems with both
: 2.4.4ac9 and 2.4.6 and it seems to have something to do with broken
: makefiles. There seem to be a lot of people with Durons (including
: me)posting with unresolved _mmx_ symbol problems.

I don't suppose, you changed your processor type w/out doing a "make
mrproper" first?  By default the kernel compiles with either i486 or
i586 and a make dep links all appropriate symbols.

If you want to change the type of processor you're compiling for, then
you need to start fresh (make mrproper), configure your kernel (make
mennuconfig), make dependencies (make dep) and then make your modules
(make modules && make modules_install).

        --Jerry

name:  Jerry Alexandratos         ||  Open-Source software isn't a
phone: 703.599.6023               ||  matter of life or death...
email: jerry@thehutt.org          ||  ...It's much more important
                                  ||  than that!

Re: [gentoo-dev] MOSIX and kernel 2.4.6

[Hendrik Visage]

On Mon, Jul 23, 2001 at 09:04:47AM -0400, Sean Mitchell wrote:
> > -----Original Message-----
> > From: Hendrik Visage [mailto:hvisage@envisage.co.za]
> 
> > But Caveat Emptor: -rc5's 2.4.6 is flaky as far as I can see.
> > Module support is broken based on some _mmx_* calls thats somehow
> > either not mangled, or mangled wrongly.
> 
> I'm not sure about that, Hendrik. I had a lot of those problems with both
> 2.4.4ac9 and 2.4.6 and it seems to have something to do with broken
> makefiles. There seem to be a lot of people with Durons (including
> me)posting with unresolved _mmx_ symbol problems.

Read TBird on this side having the trouble :(

Straigh linus linux for me :)

> 
> Cheers,
> 
> Sean
> 
> ------------------------------------------------------------------------
>  Sean Mitchell                                        Software Engineer
>  smitchell@phoenix-interactive.com       Phoenix Interactive Design Inc
>  tel. 519-679-2913 x237                        4th Floor, 137 Dundas St
>  fax. 519 679 6773                          London, ON, Canada  N6A 1E9
>                            ICQ# 104246806
> ------------------------------------------------------------------------ 
> 
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@cvs.gentoo.org
> http://cvs.gentoo.org/mailman/listinfo/gentoo-dev

-- 
------------------------
Hendrik Visage
hvisage@envisage.co.za

RE: [gentoo-dev] MOSIX and kernel 2.4.6

[Sean Mitchell]

> : I'm not sure about that, Hendrik. I had a lot of those 
> problems with both
> : 2.4.4ac9 and 2.4.6 and it seems to have something to do with broken
> : makefiles. There seem to be a lot of people with Durons (including
> : me)posting with unresolved _mmx_ symbol problems.
> 
> I don't suppose, you changed your processor type w/out doing a "make
> mrproper" first?  By default the kernel compiles with either i486 or
> i586 and a make dep links all appropriate symbols.
> 
> If you want to change the type of processor you're compiling for, then
> you need to start fresh (make mrproper), configure your kernel (make
> mennuconfig), make dependencies (make dep) and then make your modules
> (make modules && make modules_install).

Aha! Thanks Jerry... all the posts I saw on the subject (including one by
Alan Cox) suggested starting with a clean tree which did work me (no deps at
that point). I think your suggestion was in fact my problem. At any rate it
was suggested that the makefiles in recent kernels are somehow broken. Not
sure if this is actually the case, but....

Cheers,

Sean

------------------------------------------------------------------------
 Sean Mitchell                                        Software Engineer
 smitchell@phoenix-interactive.com       Phoenix Interactive Design Inc
 tel. 519-679-2913 x237                        4th Floor, 137 Dundas St
 fax. 519 679 6773                          London, ON, Canada  N6A 1E9
                           ICQ# 104246806
------------------------------------------------------------------------ 

Re: [gentoo-dev] MOSIX and kernel 2.4.6

[Jerry A!]

On Mon, Jul 23, 2001 at 09:32:34AM -0400, Sean Mitchell wrote:
: 
: Aha! Thanks Jerry... all the posts I saw on the subject (including one by
: Alan Cox) suggested starting with a clean tree which did work me (no deps at
: that point). I think your suggestion was in fact my problem. At any rate it
: was suggested that the makefiles in recent kernels are somehow broken. Not
: sure if this is actually the case, but....

The makefiles aren't broken, just the people that use them.  8)  Most of
the people that I've seen have this issue aren't used to constantly
changing kernels.  They're used to having 2.2.1x on their tree and never
needing to do a "make dep" after their initial configuration.

Alas, we're living in a world where we're getting a kernel rev per week,
so this stuff gonna happen more and more often.

        --Jerry

name:  Jerry Alexandratos         ||  Open-Source software isn't a
phone: 703.599.6023               ||  matter of life or death...
email: jerry@thehutt.org          ||  ...It's much more important
                                  ||  than that!