From: rabbit@rabbit.us (Peter Rabbitson)
To: linux-ide@vger.kernel.org
Cc: jgarzik@pobox.com
Subject: SATAII150 TX4 Disk ordering (Was: Promise SATAII150 TX4: strange disk ordering)
Date: Fri, 22 Dec 2006 06:31:31 -0500 [thread overview]
Message-ID: <20061222113131.GA24610@rabbit.us> (raw)
Hello. I have stumbled upon the problem described more than a year ago
in http://www.mail-archive.com/linux-ide@vger.kernel.org/msg01743.html
It manifested itself in a very unpleasant way while trying to sort out a
damaged GRUB installation. As GRUB relies on BIOS device numbering
rather than linux kernel device numbering (there is no kernel at that
stage) writing a manual boot stanza took a number of trial and errors. I
just wanted to drop my 2 cents by pointing a use case when this mismatch
is a real pain. The above URL was the only info I was able to find on
google, so I assume no further work has been done on this.
This is a non-production system so I can help with any tests necessary
to get the ordering right, if anyone decides to work on the driver.
Thanks
Peter
reply other threads:[~2006-12-22 11:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20061222113131.GA24610@rabbit.us \
--to=rabbit@rabbit.us \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).