From: Brian Jackson <brian@brianandsara.net>
To: Hans-Georg Esser <h.g.esser@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.20 and 2.4.21, Firewire, 160 GB Harddisk, 134 GB barrier
Date: Sat, 3 Apr 2004 10:53:40 -0600 [thread overview]
Message-ID: <200404031053.41975.brian@brianandsara.net> (raw)
In-Reply-To: <406EC833.4080909@gmx.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Saturday 03 April 2004 08:20, Hans-Georg Esser wrote:
> Hello list,
>
> I found an earlier thread ("KERNEL 2.6.3 and MAXTOR 160 GB", March 2004)
> dealing with a 137 GB barrier (that I guess meant: 137xxx MB) for a Maxtor
> 160 GB drive in Kernel 2.6.x. I'd like to add my personal observation to
> that (for Kernel 2.4.20/21):
>
> My drive (Western Digital WD1600BB-32DWA0) works well when directly
> connected to the IDE controller, but doesn't like using an external
> firewire connection ("Pyro 1394 Drive Kit" of Adstech.com). The firewire
> stuff worked well with an 80 GB disk, but with the 160 GB disk I'm only
> getting 134 GB (or 137439 MB).
The more likely scenario is that the bridge chip in said box doesn't support
the larger drive and is the limiting factor.
- --Brian Jackson
>
> This may be related to the other post I mentioned, cause of the same
> "barrier" number. I haven't tried a newer kernel yet, this was with the
> standard kernel that came with the distro:
>
<snip>
- --
http://www.brianandsara.net
For Sale : http://www.brianandsara.net/temp/forsale.php
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAbuwU+cPN+Z7qK9cRAhLGAKCBgz1xf3MdypI4lPZBl3N/PRPg6QCgqCfR
su8H1F2RwQVXKYPGXIhsiXk=
=0g7r
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-04-03 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-03 14:20 2.4.20 and 2.4.21, Firewire, 160 GB Harddisk, 134 GB barrier Hans-Georg Esser
2004-04-03 16:53 ` Brian Jackson [this message]
2004-04-03 19:58 ` Hans-Georg Esser
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=200404031053.41975.brian@brianandsara.net \
--to=brian@brianandsara.net \
--cc=h.g.esser@gmx.de \
--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