From: Tim Riker <TimR@CalderaSystems.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Problem with QLogic
Date: Tue, 29 Aug 2000 20:07:18 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205414@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205399@msgid-missing>
Uros,
I see your back at work after IDF. ;-) How dod your talk go?
What are you using to boot test7 with, lilo or eli? Just curious.
Uros Prestor wrote:
>
> Holger Berger wrote:
>
> > does the usage of BIOS 59 solve the SCSI timeout problems
> > or does it solve the problem that I can not access the QLogic BIOS?
>
> No, it doesn't. If you have a BugSur and you try entering Qlogic
> BIOS by pressing Alt-Q the system will hang.
>
> > I read that usage of older ELI or lilo should also solve some sort of
> > SCSI timeout problems. It does not for our boxes...
>
> If you get SCSI timeouts this usually means that IRQ routing setup is
> wrong. Neither lilo nor eli incorporated full ACPI support yet. The
> solution is to use 2.4.0-test7 kernel plus the latest IA-64 patch. This
> patch has support for ACPI parsing which means that it should be able to
> correctly set up IRQ routing from the ACPI tables. I have tested test7
> on a 2P BigSur with BIOS 60 and it works without problems.
PS: join #ia64Linux on irc.openprojects.net for live chat
--
Tim Riker - http://rikers.org/ - short SIGs! <g>
All I need to know I could have learned in Kindergarten
... if I'd just been paying attention.
next prev parent reply other threads:[~2000-08-29 20:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-29 11:43 [Linux-ia64] Problem with QLogic Holger Berger
2000-08-29 14:28 ` Bill Nottingham
2000-08-29 14:42 ` Holger Berger
2000-08-29 15:09 ` Bill Nottingham
2000-08-29 15:21 ` Christian Boissat
2000-08-29 17:06 ` Seth, Rohit
2000-08-29 18:18 ` Uros Prestor
2000-08-29 20:07 ` Tim Riker [this message]
2000-08-29 22:08 ` Uros Prestor
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=marc-linux-ia64-105590678205414@msgid-missing \
--to=timr@calderasystems.com \
--cc=linux-ia64@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