From: yiding_wang@agilent.com
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] issues of Linux 2.3.99 installed on BigSur EFI 1.00 [12.15]
Date: Tue, 11 Jul 2000 23:48:51 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205194@msgid-missing> (raw)
We have two BigSur system experiencing hard time on Linux 2.3.99 scsi
interface:
-------------------------
System #1:
Configuration - EFI 1.00 [12.15], upgrade by Intel from A-1 stepping to A-3
stepping
Qlogic BIOS 1.15
Qla1280 Firmware 8.13.08
1GB RAM, 9GB scsi hard drive
Problem - System booted fine and most IO test OK before the upgrade. After
upgrade,
BIOS can see the scsi device
EFI also see the files on the drive
"eli vmlinux root=/dev/sda3" will fail due to cannot found
/dev/sda3
Tried other possible device node but none of them works.
Re-install Linux 2.3.99 (TurboLinux) also failed on the same
problem.
Note: for system #1, windows2000 64 installation and running OK!
----------------------------------
System #2:
Configuration - EFI 0.99 [12.25], A-2 stepping
Qlogic BIOS 1.15
Qla1280 Firmware 8.13.08
1GB RAM, 9GB scsi hard drive
Problem - System failed during the boot. All scsi command timed out and
aborted after
BIOS, EFI and eli sees the device.
-----------------------------------
Is anyone can help on these issues?
Also could someone explain a little bit about the EFI and eil loading
process, what are they stand for and basic function among BIOS, EFI and eli?
Many thanks!
-eddie
next reply other threads:[~2000-07-11 23:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-11 23:48 yiding_wang [this message]
2000-07-12 2:38 ` [Linux-ia64] issues of Linux 2.3.99 installed on BigSur EFI 1.00 Uros Prestor
2000-07-14 23:39 ` [Linux-ia64] issues of Linux 2.3.99 installed on BigSur EFI 1.00 [12.15] Johannes Erdfelt
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-105590678205194@msgid-missing \
--to=yiding_wang@agilent.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.