[Linux-ia64] Recommended compiler for compiling kernels test10 and upper?

[Linux-ia64] Recommended compiler for compiling kernels test10 and upper?

[Francis Galiegue]

Right now I'm using the ia64-final version of gcc, and from test10 on a check
is done on whether __GNUC_MINOR__ is greater than 91. ia64-final returns 9
which is obviously not what the kernel expects...

After commenting this out and fixing by hand quite a lot of places, I got it to
compile and boot though. But more recent snapshots of gcc are available. Are
they worth upgrading?

Also, will the current glibc-2.2 compile as is on ia64 and work?

-- 
Francis Galiegue, fg@mandrakesoft.com
"Programming is a race between programmers, who try and make more and more
idiot-proof software, and universe, which produces more and more remarkable
idiots. Until now, universe leads the race"  -- R. Cook

Re: [Linux-ia64] Recommended compiler for compiling kernels test10 and upper?

[Jes Sorensen]

>>>>> "Francis" = Francis Galiegue <fg@mandrakesoft.com> writes:

Francis> Right now I'm using the ia64-final version of gcc, and from
Francis> test10 on a check is done on whether __GNUC_MINOR__ is
Francis> greater than 91. ia64-final returns 9 which is obviously not
Francis> what the kernel expects...

Which compiler is this?

Francis> After commenting this out and fixing by hand quite a lot of
Francis> places, I got it to compile and boot though. But more recent
Francis> snapshots of gcc are available. Are they worth upgrading?

Yes, you need the latest to compile glibc anyway.

Francis> Also, will the current glibc-2.2 compile as is on ia64 and
Francis> work?

Yes

Jes

Re: [Linux-ia64] Recommended compiler for compiling kernels test10

[Francis Galiegue]

On 10 Nov 2000, Jes Sorensen wrote:

> Francis> Right now I'm using the ia64-final version of gcc, and from
> Francis> test10 on a check is done on whether __GNUC_MINOR__ is
> Francis> greater than 91. ia64-final returns 9 which is obviously not
> Francis> what the kernel expects...
> 
> Which compiler is this?
> 

2.9-ia64-000216-final

> Francis> After commenting this out and fixing by hand quite a lot of
> Francis> places, I got it to compile and boot though. But more recent
> Francis> snapshots of gcc are available. Are they worth upgrading?
> 
> Yes, you need the latest to compile glibc anyway.
> 

OK, thanks :)


-- 
Francis Galiegue, fg@mandrakesoft.com
"Programming is a race between programmers, who try and make more and more
idiot-proof software, and universe, which produces more and more remarkable
idiots. Until now, universe leads the race"  -- R. Cook

Re: [Linux-ia64] Recommended compiler for compiling kernels test10 and upper?

[Jim Wilson]

I am maintaining a stable compiler for the ia64-linux (formerly Trillian)
group.  You can get it via ftp from ftp.cygnus.com in pub/ia64-linux.
This compiler assumes that you are using glibc 2.2.  This is based on FSF
gcc snapshots from the July/August timeframe.  There are patches to make
uit mostly work with glibc 2.1.3.

You can try using FSF gcc snapshots, but they tend to be a bit chaotic.
Especially so for ia64, because we are still doing optimization work on the
ia64 port, and hence we are occasionally destabilizing the ia64 port with
new optimizations.

Jim

RE: [Linux-ia64] Recommended compiler for compiling kernels test1

[Pimenov, Sergei]

Jim,

Does this compiler support cross-compilation?

p.s.
 


-----Original Message-----
From: Jim Wilson [mailto:wilson@cygnus.com]
Sent: Saturday, November 11, 2000 1:47 AM
To: Francis Galiegue
Cc: linux-ia64@linuxia64.org
Subject: Re: [Linux-ia64] Recommended compiler for compiling kernels test10 and upper? 


I am maintaining a stable compiler for the ia64-linux (formerly Trillian)
group.  You can get it via ftp from ftp.cygnus.com in pub/ia64-linux.
This compiler assumes that you are using glibc 2.2.  This is based on FSF
gcc snapshots from the July/August timeframe.  There are patches to make
uit mostly work with glibc 2.1.3.

You can try using FSF gcc snapshots, but they tend to be a bit chaotic.
Especially so for ia64, because we are still doing optimization work on the
ia64 port, and hence we are occasionally destabilizing the ia64 port with
new optimizations.

Jim

_______________________________________________
Linux-IA64 mailing list
Linux-IA64@linuxia64.org
http://lists.linuxia64.org/lists/listinfo/linux-ia64

Re: [Linux-ia64] Recommended compiler for compiling kernels

[Scott Hankin]

Howdy -

At the risk of appearing dense, exactly which compiler should we be using?
Could you provide a URL?  Thanks.

- Scott

-----------------------------
Scott Hankin                  In the beginning, there was nothing, then
Rational Software             God said, "Let there be light."  And there
20 Maguire Road               was light.  There was still nothing, but
Lexington, MA 02421           you could see it a lot better.

Re: [Linux-ia64] Recommended compiler for compiling kernels test1 0 and upper?

[Jim Wilson]

>Does this compiler support cross-compilation?

Yes.  It has probably been a few months since I last built a cross-compiler
myself, but other people have been building them successfully.  There was a
comment from H.J. claiming that the Red Hat 7.0 ia32 OS release can't build a
cross-compiler because of bugs in the compiler shipped with that release.
Otherwise, I don't know of any specific problems.

Jim

RE: [Linux-ia64] Recommended compiler for compiling kernels test1

[Broadfoot, KenX]

Redhat 7.0 shipped with two compilers.
The new one is gcc 2.95 and it is terrible for compiling kernels. ( ia32 )

The old one is called "kgcc" and works well. ( it is egcs 2.91 ) ( again
ia32 )

I have had no trouble with gcc version 2.9-ia64 that was packaged with the
Redhat 7.0 ia64 beta.
Not sure if it is a cross-compiler though.

--ken

> -----Original Message-----
> From:	Jim Wilson [SMTP:wilson@cygnus.com]
> Sent:	Monday, November 13, 2000 12:35 PM
> To:	Pimenov, Sergei
> Cc:	linux-ia64@linuxia64.org
> Subject:	Re: [Linux-ia64] Recommended compiler for compiling kernels
> test1 0 and upper? 
> 
> >Does this compiler support cross-compilation?
> 
> Yes.  It has probably been a few months since I last built a
> cross-compiler
> myself, but other people have been building them successfully.  There was
> a
> comment from H.J. claiming that the Red Hat 7.0 ia32 OS release can't
> build a
> cross-compiler because of bugs in the compiler shipped with that release.
> Otherwise, I don't know of any specific problems.
> 
> Jim
> 
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64

Re: [Linux-ia64] Recommended compiler for compiling kernels test1 0 and upper?

[H . J . Lu]

On Mon, Nov 13, 2000 at 12:34:53PM -0800, Jim Wilson wrote:
> >Does this compiler support cross-compilation?
> 
> Yes.  It has probably been a few months since I last built a cross-compiler
> myself, but other people have been building them successfully.  There was a
> comment from H.J. claiming that the Red Hat 7.0 ia32 OS release can't build a
> cross-compiler because of bugs in the compiler shipped with that release.
> Otherwise, I don't know of any specific problems.
> 

FYI, last time when I checked it, this bug

http://gcc.gnu.org/ml/gcc-bugs/2000-08/msg00526.html

still is in CVS. BTW, there are some analysis and a kludge at

http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id\x16836


-- 
H.J. Lu (hjl@valinux.com)

Re: [Linux-ia64] Recommended compiler for compiling kernels test1 0 and upper?

[H . J . Lu]

On Mon, Nov 13, 2000 at 12:38:40PM -0800, Broadfoot, KenX wrote:
> Redhat 7.0 shipped with two compilers.
> The new one is gcc 2.95 and it is terrible for compiling kernels. ( ia32 )
> 

I have very few problems with gcc 2.96 in RedHat 7.0. You just need 2
small kernel patches. 

# cat /proc/version
Linux version 2.2.17-0.5smp (root@load137.var.com) (gcc version 2.96 20000731 (Red Hat Linux 7.0)) #1 SMP Mon Oct 16 14:35:44 PDT 2000


H.J.

Re: [Linux-ia64] Recommended compiler for compiling kernels test1 0 and upper?

[Jim Wilson]

>FYI, last time when I checked it, this bug
>http://gcc.gnu.org/ml/gcc-bugs/2000-08/msg00526.html
>still is in CVS. BTW, there are some analysis and a kludge at
>http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id\x16836

But that isn't an ia64 compiler bug, so it isn't really my problem.  
And since it only shows up in an unusual case, presumably from using the
--enable-shared configure option which few people use, and since there is
an easy workaround, I see no reason why I need to spend time trying to fix it.

Jim

Re: [Linux-ia64] Recommended compiler for compiling kernels test1 0 and upper?

[H . J . Lu]

On Mon, Nov 13, 2000 at 01:14:47PM -0800, Jim Wilson wrote:
> >FYI, last time when I checked it, this bug
> >http://gcc.gnu.org/ml/gcc-bugs/2000-08/msg00526.html
> >still is in CVS. BTW, there are some analysis and a kludge at
> >http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id\x16836
> 
> But that isn't an ia64 compiler bug, so it isn't really my problem.  

I doubt it should show up in ia64 unless we are talking 128bit type.

> And since it only shows up in an unusual case, presumably from using the
> --enable-shared configure option which few people use, and since there is
> an easy workaround, I see no reason why I need to spend time trying to fix it.
> 

That is one reason I never really pushed for it. I mentioned it just
in case someone wants to take a look at it :-).

-- 
H.J. Lu (hjl@valinux.com)

Re: [Linux-ia64] Recommended compiler for compiling kernels test10 and upper?

[Jim Wilson]

I am not a kernel expert.  I do not build my own kernels.  I can not tell you
which compiler versions are best for compiling which kernel versions.

However, in general, I recommend the most recent toolchain snapshot available
at  ftp://ftp.cygnus.com/pub/ia64-linux.  These toolchains assume glibc 2.2.
Unfortunately, sigh, there aren't any glibc 2.2 based OS releases yet, but
this shouldn't matter if you are just building kernels.

Jim

Re: [Linux-ia64] Recommended compiler for compiling kernels test1 0 and upper?

[Jim Wilson]

>The new one is gcc 2.95 and it is terrible for compiling kernels. ( ia32 )

To be more precise, it is terrible for compiling old (2.2 based) linux kernels,
because these old linux kernels don't have any of the bug fixes needed to work
with new gcc releases.  It should be fine for compiling 2.4 based kernels.
In fact, nearly everybody uses a gcc-2.95 based compiler for their ia64 kernel
compiles.

Jim

Re: [Linux-ia64] Recommended compiler for compiling kernels test10 and upper?

[Gerrit Huizenga]

I was able to build this toolchain (the lack of pre-existing g++ stuff
on my IA64 machine was a small problem but I ignored it for the time
being).  I installed it into a /usr/gcc1024 hierarchy so as not to
clobber my existing gcc (since I'm not yet moving to glibc 2.2 on
that machine).

Then I could build the kernel (on a Red Hat Linux release 6.93 (Zoot))
release, cut sometime in June, I believe.

Then, I built the kernel with:

HOSTCC=/usr/bin/gcc CC=/usr/gcc1024/bin/gcc make HOSTCC=/usr/bin/gcc CC=/usr/gcc1024/bin/gcc -j 20 > ERRS 2>&1 &

Which seems to work reasonably well.  This allows the cross tools to
build with the native CC (glibc 2.1 based) and the kernel to build
with a recent compiler, which does not care a whit about glibc
support.

The native toolchain on that Red Hat distro does not have unwind
support, impylying no stack tracebacks in panics, kdb, etc.  The newer
gcc works fine, compiles completely, and has wonderful stack
tracebacks.

All this on a 4-proc Lion, running A3 procs and an ancient BIOS/frame
(my B2/B3 upgrade has been deferred for a while).

YMMV.

gerrit

> I am not a kernel expert.  I do not build my own kernels.  I can not tell you
> which compiler versions are best for compiling which kernel versions.
> 
> However, in general, I recommend the most recent toolchain snapshot available
> at  ftp://ftp.cygnus.com/pub/ia64-linux.  These toolchains assume glibc 2.2.
> Unfortunately, sigh, there aren't any glibc 2.2 based OS releases yet, but
> this shouldn't matter if you are just building kernels.
> 
> Jim
> 
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
> 

Re: [Linux-ia64] Recommended compiler for compiling kernels

[Scott Hankin]

>I was able to build this toolchain (the lack of pre-existing g++ stuff
>on my IA64 machine was a small problem but I ignored it for the time
>being).  I installed it into a /usr/gcc1024 hierarchy so as not to
>clobber my existing gcc (since I'm not yet moving to glibc 2.2 on
>that machine).

Which toolchain are you building?

>Then I could build the kernel (on a Red Hat Linux release 6.93 (Zoot))
>release, cut sometime in June, I believe.
>
>Then, I built the kernel with:
>
>HOSTCC=/usr/bin/gcc CC=/usr/gcc1024/bin/gcc make HOSTCC=/usr/bin/gcc 
>CC=/usr/gcc1024/bin/gcc -j 20 > ERRS 2>&1 &
>
>Which seems to work reasonably well.  This allows the cross tools to
>build with the native CC (glibc 2.1 based) and the kernel to build
>with a recent compiler, which does not care a whit about glibc
>support.
>
>The native toolchain on that Red Hat distro does not have unwind
>support, impylying no stack tracebacks in panics, kdb, etc.  The newer
>gcc works fine, compiles completely, and has wonderful stack
>tracebacks.
>
>All this on a 4-proc Lion, running A3 procs and an ancient BIOS/frame
>(my B2/B3 upgrade has been deferred for a while).

I'm trying to build the 2.4.0-test10 kernel with the ia64 patch.  We
recently upgaded the hardware on one of our boxes to B1 stepping, and
now it won't boot.  I'm hoping the newer kernel will work better.

So far, I'm running into problems with the old Red Hat toolchain, and
with the latest snapshot as well.  I haven't hit on the right compiler
yet, I guess.

Has anyone successfully built 2.4.0-test10 with the IA64 patch?  If so,
which toolchain did you use?

- Scott

-----------------------------
Scott Hankin                  In the beginning, there was nothing, then
Rational Software             God said, "Let there be light."  And there
20 Maguire Road               was light.  There was still nothing, but
Lexington, MA 02421           you could see it a lot better.

Re: [Linux-ia64] Recommended compiler for compiling kernels

[Scott Hankin]

>I am not a kernel expert.  I do not build my own kernels.  I can not tell you
>which compiler versions are best for compiling which kernel versions.
>
>However, in general, I recommend the most recent toolchain snapshot available
>at  ftp://ftp.cygnus.com/pub/ia64-linux.  These toolchains assume glibc 2.2.
>Unfortunately, sigh, there aren't any glibc 2.2 based OS releases yet, but
>this shouldn't matter if you are just building kernels.

I tried building glibc 2.2 (just released today on freshmeat.com) but
when building with the original compiler (Red Hat August release) I had
compile errors with sysdeps/ia64/fpu/s_isnanl.S - nat, qnan and snan
weren't defined.  The latest snapshot seems to define these, but crash
a lot.  Is there something in the middle you'd recommend?

- Scott

-----------------------------
Scott Hankin                  In the beginning, there was nothing, then
Rational Software             God said, "Let there be light."  And there
20 Maguire Road               was light.  There was still nothing, but
Lexington, MA 02421           you could see it a lot better.

Re: [Linux-ia64] Recommended compiler for compiling kernels test1 0 and

[Jun Nakajima]

Yes, I'm running 2.4 kernels (test10, for example) on IA-32 machines as
well, switching kernels on Redhat 7.0 based systems. They have been
compiled by the gcc 2.95.

Jim Wilson wrote:
> 
> >The new one is gcc 2.95 and it is terrible for compiling kernels. ( ia32 )
> 
> To be more precise, it is terrible for compiling old (2.2 based) linux kernels,
> because these old linux kernels don't have any of the bug fixes needed to work
> with new gcc releases.  It should be fine for compiling 2.4 based kernels.
> In fact, nearly everybody uses a gcc-2.95 based compiler for their ia64 kernel
> compiles.
> 
> Jim
> 
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64

-- 
Jun U Nakajima
Core OS Development
SCO/Murray Hill, NJ
Email: jun@sco.com, Phone: 908-790-2352 Fax: 908-790-2426

Re: [Linux-ia64] Recommended compiler for compiling kernels test10 and upper?

[Gerrit Huizenga]

I've built Jim's 1024 toolchain release this way.

I have not yet played with the test10 kernel - I'm still on test9 because
of the number of patches I'm using, not all of which are yet at test10
(actually, the last one or two was just announced, so I can probably move
up a notch soon).

You might want to look into just why it won't boot.  There are several
workarounds (e.g. qlc > 4GB memory addressing turned on in BIOS, EFI
workarounds, kernel config parameters such as VHPT and related workarounds
enabled/disabled, etc.).  Your problem may not be just the toolchain.

gerrit

> >I was able to build this toolchain (the lack of pre-existing g++ stuff
> >on my IA64 machine was a small problem but I ignored it for the time
> >being).  I installed it into a /usr/gcc1024 hierarchy so as not to
> >clobber my existing gcc (since I'm not yet moving to glibc 2.2 on
> >that machine).
> 
> Which toolchain are you building?
> 
> >Then I could build the kernel (on a Red Hat Linux release 6.93 (Zoot))
> >release, cut sometime in June, I believe.
> >
> >Then, I built the kernel with:
> >
> >HOSTCC=/usr/bin/gcc CC=/usr/gcc1024/bin/gcc make HOSTCC=/usr/bin/gcc
> >CC=/usr/gcc1024/bin/gcc -j 20 > ERRS 2>&1 &
> >
> >Which seems to work reasonably well.  This allows the cross tools to
> >build with the native CC (glibc 2.1 based) and the kernel to build
> >with a recent compiler, which does not care a whit about glibc
> >support.
> >
> >The native toolchain on that Red Hat distro does not have unwind
> >support, impylying no stack tracebacks in panics, kdb, etc.  The newer
> >gcc works fine, compiles completely, and has wonderful stack
> >tracebacks.
> >
> >All this on a 4-proc Lion, running A3 procs and an ancient BIOS/frame
> >(my B2/B3 upgrade has been deferred for a while).
> 
> I'm trying to build the 2.4.0-test10 kernel with the ia64 patch.  We
> recently upgaded the hardware on one of our boxes to B1 stepping, and
> now it won't boot.  I'm hoping the newer kernel will work better.
> 
> So far, I'm running into problems with the old Red Hat toolchain, and
> with the latest snapshot as well.  I haven't hit on the right compiler
> yet, I guess.
> 
> Has anyone successfully built 2.4.0-test10 with the IA64 patch?  If so,
> which toolchain did you use?
> 
> - Scott
> 
> -----------------------------
> Scott Hankin                  In the beginning, there was nothing, then
> Rational Software             God said, "Let there be light."  And there
> 20 Maguire Road               was light.  There was still nothing, but
> Lexington, MA 02421           you could see it a lot better.
> 

Re: [Linux-ia64] Recommended compiler for compiling kernels

[Scott Hankin]

>I've built Jim's 1024 toolchain release this way.
>
>I have not yet played with the test10 kernel - I'm still on test9 because
>of the number of patches I'm using, not all of which are yet at test10
>(actually, the last one or two was just announced, so I can probably move
>up a notch soon).
>
>You might want to look into just why it won't boot.  There are several
>workarounds (e.g. qlc > 4GB memory addressing turned on in BIOS, EFI
>workarounds, kernel config parameters such as VHPT and related workarounds
>enabled/disabled, etc.).  Your problem may not be just the toolchain.

Actually, it does boot, but the Ethernet card reports that the 
receiver overflows, and I end up not connected to the net.  In the 
August Red Hat release, the log shows a message about detecting 
"Receiver lock-up bug"
and enables the workaround that exists in the code (even in test10) but
my kernel fails to detect the problem, so the workaround doesn't get
enabled, and my eth0 ends up non-functional as a result.  Have you seen
or heard of this?

- Scott

-----------------------------
Scott Hankin                  In the beginning, there was nothing, then
Rational Software             God said, "Let there be light."  And there
20 Maguire Road               was light.  There was still nothing, but
Lexington, MA 02421           you could see it a lot better.

Re: [Linux-ia64] Recommended compiler for compiling kernels test10 and upper?

[Jim Wilson]

>I tried building glibc 2.2 (just released today on freshmeat.com) but
>when building with the original compiler (Red Hat August release) I had

I assume you mean the Red Hat August Linux OS release.  Red Hat isn't just a
linux company anymore.  There were also compiler releases in August.  The
August OS release uses the February compiler, which is obsolete, and probably
won't compile any recent linux kernels.  Use the new compiler, which reports
itself as "2.96-ia64-000717 snap 001024".

>  The latest snapshot seems to define these, but crash
>a lot.  Is there something in the middle you'd recommend?

Unreproducible crashes are due to hardware, firmware, and/or kernel problems.
This is not a compiler problem.  If you have an A-step or B0-step machine,
then you need to use the -ma-step option to workaround around hardware
problems.  If you have a B2-step machine, then you need a firmware version
that Intel hasn't released yet, but will hopefully release soon.  There are
also other possible, though less common, explanations for this problem.

If you are seeing reproducible compiler problems, then I'd like to hear about
them.

Jim

Re: [Linux-ia64] Recommended compiler for compiling kernels

[Scott Hankin]

>  >I tried building glibc 2.2 (just released today on freshmeat.com) but
>>when building with the original compiler (Red Hat August release) I had
>
>I assume you mean the Red Hat August Linux OS release.  Red Hat isn't just a
>linux company anymore.  There were also compiler releases in August.  The
>August OS release uses the February compiler, which is obsolete, and probably
>won't compile any recent linux kernels.  Use the new compiler, which reports
>itself as "2.96-ia64-000717 snap 001024".

OK - that's what my latest build reports, so I'm fine there.

>  >  The latest snapshot seems to define these, but crash
>>a lot.  Is there something in the middle you'd recommend?
>
>Unreproducible crashes are due to hardware, firmware, and/or kernel problems.
>This is not a compiler problem.  If you have an A-step or B0-step machine,
>then you need to use the -ma-step option to workaround around hardware
>problems.  If you have a B2-step machine, then you need a firmware version
>that Intel hasn't released yet, but will hopefully release soon.  There are
>also other possible, though less common, explanations for this problem.
>
>If you are seeing reproducible compiler problems, then I'd like to hear about
>them.
>
>Jim

No, I suspect you are right, as the fix that usually works is to retry
the make, which usually goes much further before dying.  The crashes are
never reproducible.  While I've been told the upgrade is B1 stepping, I
have no idea what the existing hardware is.  I've scanned the logs - how
do you tell?

- Scott

-----------------------------
Scott Hankin                  In the beginning, there was nothing, then
Rational Software             God said, "Let there be light."  And there
20 Maguire Road               was light.  There was still nothing, but
Lexington, MA 02421           you could see it a lot better.

Re: [Linux-ia64] Recommended compiler for compiling kernels test10 and upper?

[Jim Wilson]

>I'm trying to build the 2.4.0-test10 kernel with the ia64 patch.  We
>recently upgaded the hardware on one of our boxes to B1 stepping, and
>now it won't boot.  I'm hoping the newer kernel will work better.

The Red Hat August Linux OS release won't boot on a B1.  This was due to a
misapplied kernel patch, and was fixed immediately after the problem was
discovered, which was unfortunately a couple of days after the OS release.

There is a kernel update available from Red Hat that fixes this, but it is
a little tricky to install the kernel update if the machine doesn't boot.
Since you presumably still have A step machines, you should be able to install
the kernel update on an Ax machine, and then move a hard disk over to the B1
machine, and then it should boot.
ftp://ftp.redhat.com/pub/redhat/ia64/updates/RPMS

Or you could try one of the other OS releases.  I believe the latest Suse OS
release is OK.  I'm not sure about TurboLinux.  The next Red Hat Linux OS
release will be OK, but it isn't available yet, and I don't know exactly when
it will be available.

Jim

Re: [Linux-ia64] Recommended compiler for compiling kernels test10 and upper?

[Gerrit Huizenga]

> [...] The August OS release uses the February compiler, which is obsolete,
> and probably won't compile any recent linux kernels.

FWIW, gcc version 2.9-ia64-000216-final still compiles a working test9
ia64 kernel.  But gcc version 2.96-ia64-000717 snap 001024 is
definitely preferred (at least by me ;-).

gerrit

Re: [Linux-ia64] Recommended compiler for compiling kernels test10 and upper?

[H . J . Lu]

On Mon, Nov 13, 2000 at 03:01:56PM -0800, Jim Wilson wrote:
> >I'm trying to build the 2.4.0-test10 kernel with the ia64 patch.  We
> >recently upgaded the hardware on one of our boxes to B1 stepping, and
> >now it won't boot.  I'm hoping the newer kernel will work better.
> 
> The Red Hat August Linux OS release won't boot on a B1.  This was due to a
> misapplied kernel patch, and was fixed immediately after the problem was
> discovered, which was unfortunately a couple of days after the OS release.
> 
> There is a kernel update available from Red Hat that fixes this, but it is
> a little tricky to install the kernel update if the machine doesn't boot.
> Since you presumably still have A step machines, you should be able to install
> the kernel update on an Ax machine, and then move a hard disk over to the B1
> machine, and then it should boot.
> ftp://ftp.redhat.com/pub/redhat/ia64/updates/RPMS
> 

That is what happened to me when my machine was upgraded to B1. I
wound up putting a working kernel on the RedHat ia64 bootable LS120
floppy and booted it with root=.... It assumes you have RedHat already
installed on your machine befor upgrade.

-- 
H.J. Lu (hjl@valinux.com)

Re: [Linux-ia64] Recommended compiler for compiling kernels test10 and upper?

[Jim Wilson]

>Actually, it does boot, but the Ethernet card reports that the 
>receiver overflows, and I end up not connected to the net.

If you are seeing:
"eth0: card reports no RX buffers."
"eth0: card reports no resources."
then the same problem has been observed on ia32 machines, and is believed to be
a bug in the eepro100 driver.

Just do something like
	ifconfig eth0 down
	ifconfig eth0 up
and it will go away.  If it doesn't go away, repeat until it does.
Alternatively, you can go into /etc/rc.d/init.d and do
	./network stop
	./network start

I don't know anything about kernel workarounds for the problem.  A kernel
person would have to comment on that.  If there is a kernel problem, then
that might explain why this ethernet problem shows up more frequently on
some kernel versions than others.

Jim

Re: [Linux-ia64] Recommended compiler for compiling kernels test10 and upper?

[Don Dugger]

The actual problem here is that the EEpro driver gets confused
if it comes up on a `busy' network.  The reliable way to get
around this problem is to unplug the machine from the network
and then do:

	ifconfig eth0 down
	ifconfig eth0 up

Then re-attach the network and you should be OK.  This is
cumbersome but it should be effective.

Since this problem has been seen on IA32 we don't believe that
it's an IA64 problem and I don't know of anyone in the IA64
world working on it.

On Mon, Nov 13, 2000 at 03:14:54PM -0800, Jim Wilson wrote:
> >Actually, it does boot, but the Ethernet card reports that the 
> >receiver overflows, and I end up not connected to the net.
> 
> If you are seeing:
> "eth0: card reports no RX buffers."
> "eth0: card reports no resources."
> then the same problem has been observed on ia32 machines, and is believed to be
> a bug in the eepro100 driver.
> 
> Just do something like
> 	ifconfig eth0 down
> 	ifconfig eth0 up
> and it will go away.  If it doesn't go away, repeat until it does.
> Alternatively, you can go into /etc/rc.d/init.d and do
> 	./network stop
> 	./network start
> 
> I don't know anything about kernel workarounds for the problem.  A kernel
> person would have to comment on that.  If there is a kernel problem, then
> that might explain why this ethernet problem shows up more frequently on
> some kernel versions than others.
> 
> Jim
> 
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64

-- 
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
n0ano@valinux.com
Ph: 303/938-9838

Re: [Linux-ia64] Recommended compiler for compiling kernels test10 and upper?

[Jim Wilson]

There is an EFI utility available from Intel support (Quad) that will identify
processor stepping.  If you were told that it is a B1, then it probably is
a B1.

Jim

Re: [Linux-ia64] Recommended compiler for compiling kernels test10 and upper?

[Don Dugger]

[-- Attachment #1: Type: text/plain, Size: 2735 bytes --]

Scott-

I've been using the compiler from the TurboLinux 5/5 release,
`2.9-ia64-000216-final'.  I pretty sure I've also used the
compiler from Turbo's 8/28 release also, I don't know what
version it is offhand.  If it'll help I've attached the
`.config' file that I use.  You should change it to disable
B2 specific code and enable B1 specific code but other than
that it should work.

On Mon, Nov 13, 2000 at 05:00:44PM -0500, Scott Hankin wrote:
> >I was able to build this toolchain (the lack of pre-existing g++ stuff
> >on my IA64 machine was a small problem but I ignored it for the time
> >being).  I installed it into a /usr/gcc1024 hierarchy so as not to
> >clobber my existing gcc (since I'm not yet moving to glibc 2.2 on
> >that machine).
> 
> Which toolchain are you building?
> 
> >Then I could build the kernel (on a Red Hat Linux release 6.93 (Zoot))
> >release, cut sometime in June, I believe.
> >
> >Then, I built the kernel with:
> >
> >HOSTCC=/usr/bin/gcc CC=/usr/gcc1024/bin/gcc make HOSTCC=/usr/bin/gcc 
> >CC=/usr/gcc1024/bin/gcc -j 20 > ERRS 2>&1 &
> >
> >Which seems to work reasonably well.  This allows the cross tools to
> >build with the native CC (glibc 2.1 based) and the kernel to build
> >with a recent compiler, which does not care a whit about glibc
> >support.
> >
> >The native toolchain on that Red Hat distro does not have unwind
> >support, impylying no stack tracebacks in panics, kdb, etc.  The newer
> >gcc works fine, compiles completely, and has wonderful stack
> >tracebacks.
> >
> >All this on a 4-proc Lion, running A3 procs and an ancient BIOS/frame
> >(my B2/B3 upgrade has been deferred for a while).
> 
> I'm trying to build the 2.4.0-test10 kernel with the ia64 patch.  We
> recently upgaded the hardware on one of our boxes to B1 stepping, and
> now it won't boot.  I'm hoping the newer kernel will work better.
> 
> So far, I'm running into problems with the old Red Hat toolchain, and
> with the latest snapshot as well.  I haven't hit on the right compiler
> yet, I guess.
> 
> Has anyone successfully built 2.4.0-test10 with the IA64 patch?  If so,
> which toolchain did you use?
> 
> - Scott
> 
> -----------------------------
> Scott Hankin                  In the beginning, there was nothing, then
> Rational Software             God said, "Let there be light."  And there
> 20 Maguire Road               was light.  There was still nothing, but
> Lexington, MA 02421           you could see it a lot better.
> 
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64

-- 
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
n0ano@valinux.com
Ph: 303/938-9838

[-- Attachment #2: .config --]
[-- Type: text/plain, Size: 14660 bytes --]

#
# Automatically generated make config: don't edit
#

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y

#
# Loadable module support
#
CONFIG_MODULES=y
# CONFIG_MODVERSIONS is not set
# CONFIG_KMOD is not set

#
# General setup
#
CONFIG_IA64=y
CONFIG_SWIOTLB=y
# CONFIG_ISA is not set
# CONFIG_SBUS is not set
# CONFIG_IA64_GENERIC is not set
CONFIG_IA64_DIG=y
# CONFIG_IA64_HP_SIM is not set
# CONFIG_IA64_SGI_SN1 is not set
# CONFIG_IA64_PAGE_SIZE_4KB is not set
# CONFIG_IA64_PAGE_SIZE_8KB is not set
CONFIG_IA64_PAGE_SIZE_16KB=y
# CONFIG_IA64_PAGE_SIZE_64KB is not set
CONFIG_ITANIUM=y
CONFIG_IA64_BRL_EMU=y
# CONFIG_ITANIUM_ASTEP_SPECIFIC is not set
CONFIG_ITANIUM_BSTEP_SPECIFIC=y
# CONFIG_ITANIUM_B0_SPECIFIC is not set
# CONFIG_ITANIUM_B1_SPECIFIC is not set
CONFIG_ITANIUM_B2_SPECIFIC=y
# CONFIG_IA64_HAVE_IRQREDIR is not set
# CONFIG_ITANIUM_PTCG is not set
# CONFIG_IA64_SOFTSDV_HACKS is not set
# CONFIG_IA64_AZUSA_HACKS is not set
CONFIG_IA64_MCA=y
CONFIG_ACPI_KERNEL_CONFIG=y
CONFIG_PM=y
CONFIG_ACPI=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_KCORE_ELF=y
# CONFIG_SMP is not set
# CONFIG_PERFMON is not set
CONFIG_IA64_PALINFO=y
CONFIG_NET=y
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=y
CONFIG_PCI=y
# CONFIG_PCI_NAMES is not set
# CONFIG_HOTPLUG is not set
# CONFIG_PCMCIA is not set

#
# Parallel port support
#
# CONFIG_PARPORT is not set

#
# Networking options
#
# CONFIG_PACKET is not set
# CONFIG_NETLINK is not set
# CONFIG_NETFILTER is not set
# CONFIG_FILTER is not set
CONFIG_UNIX=y
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_INET_ECN is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_IPV6 is not set
# CONFIG_KHTTPD is not set
# CONFIG_ATM is not set

#
#  
#
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_LLC is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Plug and Play configuration
#
# CONFIG_PNP is not set
# CONFIG_ISAPNP is not set

#
# Block devices
#
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_LOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_BLK_DEV_INITRD is not set

#
# I2O device support
#
# CONFIG_I2O is not set
# CONFIG_I2O_PCI is not set
# CONFIG_I2O_BLOCK is not set
# CONFIG_I2O_LAN is not set
# CONFIG_I2O_SCSI is not set
# CONFIG_I2O_PROC is not set

#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set
# CONFIG_BLK_DEV_MD is not set
# CONFIG_MD_LINEAR is not set
# CONFIG_MD_RAID0 is not set
# CONFIG_MD_RAID1 is not set
# CONFIG_MD_RAID5 is not set
# CONFIG_BLK_DEV_LVM is not set
# CONFIG_LVM_PROC_FS is not set

#
# ATA/IDE/MFM/RLL support
#
CONFIG_IDE=y

#
# IDE, ATA and ATAPI Block devices
#
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_HD_IDE is not set
# CONFIG_BLK_DEV_HD is not set
CONFIG_BLK_DEV_IDEDISK=y
# CONFIG_IDEDISK_MULTI_MODE is not set
# CONFIG_BLK_DEV_IDEDISK_VENDOR is not set
# CONFIG_BLK_DEV_IDEDISK_FUJITSU is not set
# CONFIG_BLK_DEV_IDEDISK_IBM is not set
# CONFIG_BLK_DEV_IDEDISK_MAXTOR is not set
# CONFIG_BLK_DEV_IDEDISK_QUANTUM is not set
# CONFIG_BLK_DEV_IDEDISK_SEAGATE is not set
# CONFIG_BLK_DEV_IDEDISK_WD is not set
# CONFIG_BLK_DEV_COMMERIAL is not set
# CONFIG_BLK_DEV_TIVO is not set
# CONFIG_BLK_DEV_IDECS is not set
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set

#
# IDE chipset support/bugfixes
#
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
# CONFIG_BLK_DEV_ISAPNP is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_IDEDMA_PCI_AUTO=y
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_PCI_WIP is not set
# CONFIG_IDEDMA_NEW_DRIVE_LISTINGS is not set
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_AEC62XX_TUNING is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_WDC_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD7409 is not set
# CONFIG_AMD7409_OVERRIDE is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_HPT34X_AUTODMA is not set
# CONFIG_BLK_DEV_HPT366 is not set
CONFIG_BLK_DEV_PIIX=y
CONFIG_PIIX_TUNING=y
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_PDC202XX is not set
# CONFIG_PDC202XX_BURST is not set
# CONFIG_BLK_DEV_OSB4 is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_IDE_CHIPSETS is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_IDEDMA_IVB is not set
# CONFIG_DMA_NONPCI is not set
CONFIG_BLK_DEV_IDE_MODES=y

#
# SCSI support
#
CONFIG_SCSI=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
CONFIG_SD_EXTRA_DEVS=40
# CONFIG_CHR_DEV_ST is not set
CONFIG_BLK_DEV_SR=y
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_SR_EXTRA_DEVS=2
# CONFIG_CHR_DEV_SG is not set

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_DEBUG_QUEUES is not set
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set

#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_7000FASST is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AHA152X is not set
# CONFIG_SCSI_AHA1542 is not set
# CONFIG_SCSI_AHA1740 is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_IN2000 is not set
# CONFIG_SCSI_AM53C974 is not set
# CONFIG_SCSI_MEGARAID is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_CPQFCTS is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_DTC3280 is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_DMA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_GENERIC_NCR5380 is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_NCR53C406A is not set
# CONFIG_SCSI_NCR53C7xx is not set
# CONFIG_SCSI_NCR53C8XX is not set
# CONFIG_SCSI_SYM53C8XX is not set
# CONFIG_SCSI_PAS16 is not set
# CONFIG_SCSI_PCI2000 is not set
# CONFIG_SCSI_PCI2220I is not set
# CONFIG_SCSI_PSI240I is not set
# CONFIG_SCSI_QLOGIC_FAS is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
CONFIG_SCSI_QLOGIC_1280=y
# CONFIG_SCSI_SIM710 is not set
# CONFIG_SCSI_SYM53C416 is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_T128 is not set
# CONFIG_SCSI_U14_34F is not set
# CONFIG_SCSI_DEBUG is not set

#
# Network device support
#
CONFIG_NETDEVICES=y

#
# ARCnet devices
#
# CONFIG_ARCNET is not set
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_NET_SB1000 is not set

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_HP100 is not set
# CONFIG_NET_ISA is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_AC3200 is not set
# CONFIG_APRICOT is not set
# CONFIG_CS89x0 is not set
# CONFIG_DE4X5 is not set
# CONFIG_TULIP is not set
# CONFIG_DGRS is not set
# CONFIG_DM9102 is not set
CONFIG_EEPRO100=y
# CONFIG_EEPRO100_PM is not set
# CONFIG_LNE390 is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_NE3210 is not set
# CONFIG_ES3210 is not set
# CONFIG_RTL8129 is not set
# CONFIG_8139TOO is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_WINBOND_840 is not set
# CONFIG_NET_POCKET is not set

#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_SK98LIN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set

#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set

#
# Token Ring devices
#
# CONFIG_TR is not set
# CONFIG_NET_FC is not set
# CONFIG_RCPCI is not set
# CONFIG_SHAPER is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set

#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set

#
# ISDN subsystem
#
# CONFIG_ISDN is not set

#
# CD-ROM drivers (not for SCSI or IDE/ATAPI drives)
#
# CONFIG_CD_NO_IDESCSI is not set

#
# Input core support
#
# CONFIG_INPUT is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
# CONFIG_SERIAL is not set
# CONFIG_SERIAL_EXTENDED is not set
# CONFIG_SERIAL_NONSTANDARD is not set
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256

#
# I2C support
#
# CONFIG_I2C is not set

#
# Mice
#
# CONFIG_BUSMOUSE is not set
CONFIG_MOUSE=y
CONFIG_PSMOUSE=y
# CONFIG_82C710_MOUSE is not set
# CONFIG_PC110_PAD is not set

#
# Joysticks
#
# CONFIG_JOYSTICK is not set

#
# Input core support is needed for joysticks
#
# CONFIG_QIC02_TAPE is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_INTEL_RNG is not set
# CONFIG_NVRAM is not set
# CONFIG_RTC is not set
CONFIG_EFI_RTC=y
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
# CONFIG_AGP is not set
CONFIG_DRM=y
CONFIG_DRM_TDFX=y
# CONFIG_DRM_GAMMA is not set
# CONFIG_DRM_R128 is not set
# CONFIG_DRM_I810 is not set
# CONFIG_DRM_MGA is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

#
# File systems
#
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
# CONFIG_ADFS_FS is not set
# CONFIG_ADFS_FS_RW is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_BFS_FS is not set
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
# CONFIG_UMSDOS_FS is not set
CONFIG_VFAT_FS=y
# CONFIG_EFS_FS is not set
# CONFIG_JFFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_RAMFS is not set
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
# CONFIG_MINIX_FS is not set
# CONFIG_NTFS_FS is not set
# CONFIG_NTFS_RW is not set
# CONFIG_HPFS_FS is not set
CONFIG_PROC_FS=y
# CONFIG_DEVFS_FS is not set
# CONFIG_DEVFS_MOUNT is not set
# CONFIG_DEVFS_DEBUG is not set
# CONFIG_DEVPTS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_QNX4FS_RW is not set
# CONFIG_ROMFS_FS is not set
CONFIG_EXT2_FS=y
# CONFIG_SYSV_FS is not set
# CONFIG_SYSV_FS_WRITE is not set
# CONFIG_UDF_FS is not set
# CONFIG_UDF_RW is not set
# CONFIG_UFS_FS is not set
# CONFIG_UFS_FS_WRITE is not set

#
# Network File Systems
#
# CONFIG_CODA_FS is not set
CONFIG_NFS_FS=y
# CONFIG_NFS_V3 is not set
# CONFIG_ROOT_NFS is not set
# CONFIG_NFSD is not set
# CONFIG_NFSD_V3 is not set
CONFIG_SUNRPC=y
CONFIG_LOCKD=y
# CONFIG_SMB_FS is not set
# CONFIG_NCP_FS is not set
# CONFIG_NCPFS_PACKET_SIGNING is not set
# CONFIG_NCPFS_IOCTL_LOCKING is not set
# CONFIG_NCPFS_STRONG is not set
# CONFIG_NCPFS_NFS_NS is not set
# CONFIG_NCPFS_OS2_NS is not set
# CONFIG_NCPFS_SMALLDOS is not set
# CONFIG_NCPFS_MOUNT_SUBDIR is not set
# CONFIG_NCPFS_NDS_DOMAINS is not set
# CONFIG_NCPFS_NLS is not set
# CONFIG_NCPFS_EXTRAS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
CONFIG_NLS=y

#
# Native Language Support
#
CONFIG_NLS_DEFAULT="iso8859-1"
# CONFIG_NLS_CODEPAGE_437 is not set
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_ISO8859_1 is not set
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_UTF8 is not set

#
# Console drivers
#
CONFIG_VGA_CONSOLE=y

#
# Frame-buffer support
#
# CONFIG_FB is not set

#
# Sound
#
# CONFIG_SOUND is not set

#
# USB support
#
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_BANDWIDTH is not set

#
# USB Controllers
#
CONFIG_USB_UHCI_ALT=y
# CONFIG_USB_OHCI is not set

#
# USB Devices
#
# CONFIG_USB_PRINTER is not set
# CONFIG_USB_SCANNER is not set
# CONFIG_USB_MICROTEK is not set
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_ACM is not set
# CONFIG_USB_SERIAL is not set
# CONFIG_USB_IBMCAM is not set
# CONFIG_USB_OV511 is not set
# CONFIG_USB_DC2XX is not set
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_STORAGE is not set
# CONFIG_USB_USS720 is not set
# CONFIG_USB_DABUSB is not set
# CONFIG_USB_PLUSB is not set
# CONFIG_USB_PEGASUS is not set
CONFIG_USB_RIO500=y
# CONFIG_USB_DSBR is not set
# CONFIG_USB_BLUETOOTH is not set
# CONFIG_USB_NET1080 is not set

#
# USB Human Interface Devices (HID)
#

#
#   Input core support is needed for USB HID
#

#
# Kernel hacking
#
CONFIG_IA32_SUPPORT=y
CONFIG_MATHEMU=y
CONFIG_MAGIC_SYSRQ=y
# CONFIG_IA64_EARLY_PRINTK is not set
# CONFIG_IA64_DEBUG_CMPXCHG is not set
# CONFIG_IA64_DEBUG_IRQ is not set
# CONFIG_IA64_PRINT_HAZARDS is not set
# CONFIG_IA64_NEW_UNWIND is not set
CONFIG_DISABLE_VHPT=y

Re: [Linux-ia64] Recommended compiler for compiling kernels

[Scott Hankin]

>On Mon, Nov 13, 2000 at 03:01:56PM -0800, Jim Wilson wrote:
>>  >I'm trying to build the 2.4.0-test10 kernel with the ia64 patch.  We
>>  >recently upgaded the hardware on one of our boxes to B1 stepping, and
>>  >now it won't boot.  I'm hoping the newer kernel will work better.
>>
>>  The Red Hat August Linux OS release won't boot on a B1.  This was due to a
>>  misapplied kernel patch, and was fixed immediately after the problem was
>>  discovered, which was unfortunately a couple of days after the OS release.
>>
>>  There is a kernel update available from Red Hat that fixes this, but it is
>>  a little tricky to install the kernel update if the machine doesn't boot.
>>  Since you presumably still have A step machines, you should be 
>>able to install
>>  the kernel update on an Ax machine, and then move a hard disk over to the B1
>>  machine, and then it should boot.
>>  ftp://ftp.redhat.com/pub/redhat/ia64/updates/RPMS
>>
>
>That is what happened to me when my machine was upgraded to B1. I
>wound up putting a working kernel on the RedHat ia64 bootable LS120
>floppy and booted it with root=.... It assumes you have RedHat already
>installed on your machine befor upgrade.
>
>--
>H.J. Lu (hjl@valinux.com)

Howdy -

Precisely how did you do that?  I can currently boot from the LS120 disk
I made from the Red Hat CD, but when I mount it, the directory listing
is garbage, leading me to believe that the format is not that of a Linux
filesystem.  I have a new kernel - what do I do to get it on the LS120?

- Scott

-----------------------------
Scott Hankin                  In the beginning, there was nothing, then
Rational Software             God said, "Let there be light."  And there
20 Maguire Road               was light.  There was still nothing, but
Lexington, MA 02421           you could see it a lot better.

Re: [Linux-ia64] Recommended compiler for compiling kernels test10 and upper?

[Jim Wilson]

EFI uses the FAT (MSDOS) filesystem.  Use fdisk to check the partition table.
The floppy may have more than one partition, and there may be different
filesystem formats on different partitions.

Jim

Re: [Linux-ia64] Recommended compiler for compiling kernels test10 and upper?

[H . J . Lu]

On Wed, Nov 15, 2000 at 12:59:50PM -0500, Scott Hankin wrote:
> >>
> >
> >That is what happened to me when my machine was upgraded to B1. I
> >wound up putting a working kernel on the RedHat ia64 bootable LS120
> >floppy and booted it with root=.... It assumes you have RedHat already
> >installed on your machine befor upgrade.
> >
> >--
> >H.J. Lu (hjl@valinux.com)
> 
> Howdy -
> 
> Precisely how did you do that?  I can currently boot from the LS120 disk
> I made from the Red Hat CD, but when I mount it, the directory listing
> is garbage, leading me to believe that the format is not that of a Linux
> filesystem.  I have a new kernel - what do I do to get it on the LS120?
> 

As Jim said, it is an EFI partition. You can do

# mount -t vfat /dev/hdd1 /mnt/floppy/

Or you can use mtools.

-- 
H.J. Lu (hjl@valinux.com)