public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Uros Prestor <uros@turbolinux.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] issues of Linux 2.3.99 installed on BigSur EFI 1.00
Date: Wed, 12 Jul 2000 02:38:31 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205195@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205194@msgid-missing>

yiding_wang@agilent.com wrote:

> 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.

Could you send the dmesg output?  This will tell us the kernel version and the
devices kernel recognizes.

To get the dmesg output boot from CD and set root to your
CD-ROM (root=/dev/hda, /dev/hdb, ...).  Once you are in the installer press
Alt-F2 and you should see a bash prompt.  Now mount a LS-120 floppy on
/mnt/floppy (your LS-120 might be something other than /dev/hdb):

     # mount /dev/hdb /mnt/floppy
     # dmesg >/mnt/floppy/dmesg.out
     # umount /mnt/floppy

> Problem - System failed during the boot.  All scsi command timed out and
> aborted after
>                BIOS, EFI and eli sees the device.

SCSI timeouts usually happen when eli passes incorrect interrupt vectors to the
kernel.  I suggest that you update the eli on your system.  The latest eli RPM
is available at:

     ftp://ftp.turbolinux.com/pub/ia64/0505/updates/RPMS/ia64/eli-0.4.0-2.ia64.rpm

Uros

--
Uros Prestor
uros@turbolinux.com






  reply	other threads:[~2000-07-12  2:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-11 23:48 [Linux-ia64] issues of Linux 2.3.99 installed on BigSur EFI 1.00 [12.15] yiding_wang
2000-07-12  2:38 ` Uros Prestor [this message]
2000-07-14 23:39 ` 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-105590678205195@msgid-missing \
    --to=uros@turbolinux.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