linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Walt H <waltabbyh@comcast.net>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	arjanv@redhat.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	davzaffiro@tasking.nl
Subject: Re: [PATCH] pdcraid and weird IDE geometry
Date: Fri, 18 Jul 2003 06:56:29 -0700	[thread overview]
Message-ID: <3F17FC8D.9080209@comcast.net> (raw)
In-Reply-To: <20030718105810.A2925@pclin040.win.tue.nl>

Andries Brouwer wrote:
 >
> I don't understand. Did you introduce some float? Remove it immediately.
> 
> You just replace
> 
>         lba = (ideinfo->capacity / (ideinfo->head*ideinfo->sect));
>         lba = lba * (ideinfo->head*ideinfo->sect);
>         lba = lba - ideinfo->sect;
> 
> by
> 
> 	lba = ideinfo->capacity - 63;
> 
> Then everything works for you, I suppose.
> Subsequently we wait for other people with the same hardware
> and see how the 63 varies as a function of their setup.
> (Or maybe you can go into the BIOS and specify different
> translations yourself?)
> 
> (By the way, didnt your boot parameters lead to ideinfo->head = 16
> and ideinfo->sect = 63?)
> 
> Andries
> 
> 

No, you're right. I was just trying to clarify the changes that I had
originally made. It seemed as there may have been some confusion that I
was doing more than the original. In my case, the simplified
ideinfo->capacity - ideinfo->sect should work just fine.
The boot parameters did take. The geometry was reported (correctly?) as
I had passed, but when trying to load the pdcraid module, access to the
disk failed with I/O errors. Seemed as if it was trying to read beyond
the end of the device. I used the identical geometry as reported by the
working drive.
Unfortunately, since this is the embedded FastTrak stuff, the BIOS
doesn't allow me to setup geometry for the drives.

I've just tried the simplified method and it works fine. I'll stick with
that on my end. Thanks for the help,

-Walt


  reply	other threads:[~2003-07-18 13:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-17  2:26 [PATCH] pdcraid and weird IDE geometry Walt H
2003-07-17  8:49 ` Arjan van de Ven
2003-07-17 14:37   ` Walt H
2003-07-17 14:58     ` Alan Cox
2003-07-17 15:34       ` Jeff Garzik
2003-07-17 16:03         ` Andries Brouwer
2003-07-17 15:34       ` Andries Brouwer
2003-07-18  2:33         ` Walt H
2003-07-18  8:58           ` Andries Brouwer
2003-07-18 13:56             ` Walt H [this message]
2003-07-17 12:19 ` David Zaffiro
2003-07-18 14:51 Walt H

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=3F17FC8D.9080209@comcast.net \
    --to=waltabbyh@comcast.net \
    --cc=aebr@win.tue.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arjanv@redhat.com \
    --cc=davzaffiro@tasking.nl \
    --cc=linux-kernel@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).