From: Josep Lladonosa i Capell <jep@jep.net.dhis.org>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Stephan von Krawczynski <skraw@ithnet.com>,
Guest section DW <dwguest@win.tue.nl>,
James Stevenson <mistral@stev.org>,
jlladono@pie.xtec.es, linux-kernel@vger.kernel.org
Subject: Re: 2.4.x kernels, big ide disks and old bios
Date: Sun, 30 Dec 2001 02:40:43 +0100 [thread overview]
Message-ID: <3C2E709A.1D12BEFB@jep.dhis.org> (raw)
In-Reply-To: <Pine.LNX.4.10.10112271926400.24491-100000@master.linux-ide.org>
Andre Hedrick wrote:
> You have it called "STROKE".
>
> Use a patch and execute a soft-clip operation to the device and you are
> fixed.
...depends. I want the big disk to be /dev/hda, and bootable (an unattended
boot).
Disk is 119150/16/63. I soft (un)clipped it to max capacity (60Gb) with setmax
.
Configured it in the bios (32Gb limit) as a smaller disk, bios complained,
telling an error, asking to press F1 to continue. The LBA mode (4111/255/63,
LBA, for example) told the error, and asking for F1, as well. With
(65530/16/63, NORM), it booted well.
Kernel (2.4.17, patched) corrected the geometry while booting, but mke2fs
generated many io-errors, I suspect beyond the 32Gb.
Finally, a bios upgrade (unfortunately not for sizes beyond 32Gb), let me to
configure the setup with
the LBA mode, and boot works well, and mke2fs doesn't complain.
I don't need to use setmax to clip-unclip when booting.
What's the meaning of the 65535 max limit in bios_cyl? *
*I don't think it is a kernel limit.
*Is it the max value accepted by the physical disk, and that's why lba is used?
*Was that the problem with the io-errors?
# cat /proc/ide/hdc/settings
name value min max mode
---- ----- --- --- ----
bios_cyl 119150 0 65535 rw
bios_head 16 0 255 rw
bios_sect 63 0 63 rw
--
Salutacions...Josep
http://www.geocities.com/SiliconValley/Horizon/1065/
--
next prev parent reply other threads:[~2001-12-30 1:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-25 10:56 2.4.x kernels, big ide disks and old bios Josep Lladonosa i Capell
2001-12-25 14:10 ` Santiago Garcia Mantinan
2001-12-25 19:09 ` James Stevenson
2001-12-26 16:33 ` Stephan von Krawczynski
2001-12-27 13:14 ` James Stevenson
2001-12-27 18:51 ` Stephan von Krawczynski
2001-12-27 19:53 ` Ido Diamant
2001-12-27 22:41 ` Guest section DW
2001-12-27 23:04 ` Stephan von Krawczynski
2001-12-28 0:06 ` [PATCH] " Eric Lammerts
2001-12-28 3:29 ` Andre Hedrick
2001-12-30 1:40 ` Josep Lladonosa i Capell [this message]
2001-12-28 21:52 ` Jorge Nerin
2001-12-30 9:33 ` Josep Lladonosa i Capell
-- strict thread matches above, loose matches on Subject: below --
2001-12-25 16:38 Andries.Brouwer
2001-12-25 22:52 ` Eric Lammerts
2001-12-26 9:28 ` Josep Lladonosa i Capell
2001-12-26 10:39 ` Santiago Garcia Mantinan
2001-12-26 2:12 Andries.Brouwer
2001-12-30 2:47 Andries.Brouwer
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=3C2E709A.1D12BEFB@jep.dhis.org \
--to=jep@jep.net.dhis.org \
--cc=andre@linux-ide.org \
--cc=dwguest@win.tue.nl \
--cc=jlladono@pie.xtec.es \
--cc=linux-kernel@vger.kernel.org \
--cc=mistral@stev.org \
--cc=skraw@ithnet.com \
/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