From: Jared Egolf <jegolf@yahoo.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] kernel panic on root mount / EFI =?unknown-8bit?q?can=E2=80=99t?= see /boot/efi partition!
Date: Fri, 16 Nov 2001 00:33:54 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805521@msgid-missing> (raw)
Using Redhat 7.2 and in the past 7.1, I cannot configure
the /boot/efi partition with such a type definition that
EFI will recognize the file-system and thus use it for
booting purposes. Our boot procedure has been to boot into
Whistler and copy over the data to a LS120 and then setup
to boot from there. This is occurring on our BigSur, Lion,
and Azusa machines.
Unfortunately, whenever I rebuild a kernel, (currently
attempting with 2.4.14, but also tried 2.4.10 and have only
tested on the BigSur), the kernel panics without being
capable of mounting the root partition. This occurs even
with the default configuration of the kernel and I suspect
the two problems may be linked. It is troubling however
that while the default Redhat kernel will mount the (/)
root system after loading the qla1260 driver from the
initrd file, when I have my new kernel configured to
compile and include qla1260 it still results in a kernel
panic. Is building an initrd file for each kernel rebuild
truly going to help the situation? Has anybody else seen a
situation where EFI refuses to recognize a FAT16 defined
partition? Perhaps Whistler is mangling the partition
tables on all the accessible disks? Could these problems
be linked?
Thank-you for your help,
Jared Egolf
__________________________________________________
Do You Yahoo!?
Find the one for you at Yahoo! Personals
http://personals.yahoo.com
next reply other threads:[~2001-11-16 0:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-16 0:33 Jared Egolf [this message]
2001-11-16 0:47 ` [Linux-ia64] kernel panic on root mount / EFI cant see Bdale Garbee
2001-11-16 21:42 ` Jared Egolf
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-105590698805521@msgid-missing \
--to=jegolf@yahoo.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