From: Jesse Barnes <jbarnes@engr.sgi.com>
To: Jan Kasprzak <kas@informatics.muni.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Stock IA64 kernel on SGI Altix 350
Date: Thu, 3 Jun 2004 10:30:36 -0700 [thread overview]
Message-ID: <200406031030.36181.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <20040603170147.GK10708@fi.muni.cz>
On Thursday, June 3, 2004 10:01 am, Jan Kasprzak wrote:
> I have a SGI Altix 350 IA64 machine (running SLES 8) for testing before
> it goes to the production use. I have succeeded recompiling and booting
> the SuSE distribution kernel (2.4.21+patches) from sources, but I have
> failed to compile/run any stock kernel from ftp.kernel.org (+ patches from
> kernel/ports/ia64/v2.[46]).
The 2.6 kernel, as of 2.6.0-test10 iirc, should work ok. Recent kernels
contain an 'sn2_defconfig' file that you can use to build a usable kernel:
# tar zxf linux-2.6.6.tar.gz
# cd linux-2.6.6
# make sn2_defconfig
# make -j<some high number> compressed
# boot your kernel
But don't forget that you need to pass 'console=ttyS0' on your kernel boot
line (it's easiest to add this to your elilo.conf file).
> Firstly, is there any Linux IA64-specific mailing list?
> The MAINTAINERS file points to www.linuxia64.org, which is probably
> expired (please update the MAINTAINERS file).
Yep, linux-ia64@vger.kernel.org
> Now the detailed description:
>
> ---------------------
> The 2.6.6 kernel + linux-2.6.6-ia64-040521.diff.bz2 patch compiled and
> linked correctly, but failed to boot (it did not print anything to the
> console):
>
> ELILO boot: 2.6.6 console=ttyS0
> Uncompressing Linux... done
>
> (and without "console=ttyS0" it was the same).
Is this with the sn2_defconfig file? What PROM are you running?
>
> ---------------------
> The 2.4.26 kernel + linux-2.4.26-ia64-040510.diff.bz2 patch failed to link
> on my box with <asm/sn/idle.h> missing:
Stock (i.e. non-SGI or non-SuSE) 2.4 kernels won't work on Altix. You need
2.6.
> My .configs are at http://www.fi.muni.cz/~kas/tmp/ia64/.
> So is it possible to use stock kernel on Altix 350? Is there a better
> list to report this than lkml?
It should work fine. And linux-ia64 is probably a better list (more chance of
me seeing your message).
Jesse
next prev parent reply other threads:[~2004-06-03 17:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 17:01 Jan Kasprzak
2004-06-03 17:30 ` Jesse Barnes [this message]
2004-06-03 20:09 ` Jan Kasprzak
2004-06-03 20:19 ` Jesse Barnes
2004-06-03 20:41 ` Jan Kasprzak
2004-06-04 12:09 ` Jan-Benedict Glaw
2004-06-04 15:03 ` Linus Torvalds
2004-06-03 17:34 ` Paul Jackson
[not found] <962201031@toto.iv>
2004-06-04 3:59 ` Peter Chubb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200406031030.36181.jbarnes@engr.sgi.com \
--to=jbarnes@engr.sgi.com \
--cc=kas@informatics.muni.cz \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®