public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jorge Nerin <comandante@zaralinux.com>
To: jlladono@pie.xtec.es
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.x kernels, big ide disks and old bios
Date: Fri, 28 Dec 2001 22:52:21 +0100	[thread overview]
Message-ID: <3C2CE995.6080503@zaralinux.com> (raw)
In-Reply-To: <3C285B40.91A83EC7@jep.dhis.org>

Josep Lladonosa i Capell wrote:

> Hello,
> 
> the problem is this:
> 
> bios only supports disks up to 32 Gb.


I have a 486, bios (as i remember) does not even see the disk.


> 
> hard disk is 60 Gb.


HD is 40Gb


> 
> kernel is 2.4.17
> 

2.4.15-pre9 + tux2 patches


> hard disk reports its correct size when reading parameters from the
> disk, not from the bios
> 
> verd:/proc/ide/hdc# cat geometry
> physical     65530/16/63
> logical      119150/16/63
> 


[root@head (22:45:56) ~]# cat /proc/ide/hda/geometry
physical     77545/16/63
logical      77545/16/63
[root@head (22:46:07) ~]#


> 
> when booting (dmesg):
> 
> hdc: IC35L060AVER07-0, ATA DISK drive
> hdc: 66055247 sectors (33820 MB) w/1916KiB Cache, CHS=119150/16/63,
> UDMA(33)
> 
> 


hda: 78165360 sectors (40021 MB) w/1024KiB Cache, CHS=77545/16/63


> Linux adopts the 'false' geometry (65530/16/63) ) to bypass the bios
> boot.
> 
> 


All I can say is that I have a /boot partition of about 64 Megs, because 
I have / formated as reiser so /boot is ext2 because it's from the time 
that you cannot boot from reiser without notail.


> 
> I know that there are patches for 2.2 kernels and 2.3 kernels, so as
> linux adopts the logical geometry (a kiddy trick with lba size). They
> are very simple (a line), but 2.4 ide implementation is (a little more)
> complicated. Any patch?
> 


Well, it works for me, and as I have said, I have a 486, I'm not sure if 
the bios supports this size, but I seem to remember that it even does 
not detect it at boot, or perhaps it detects it as a strange size such 
as 8Gb or 32Gb, just don't remember.

Linux boots and works for me with no problem in this system.


> Bon Nadal - Merry Christmas
> 


Feliz Navidad.


> --
> Salutacions...Josep
> http://www.geocities.com/SiliconValley/Horizon/1065/



-- 
Jorge Nerin
<comandante@zaralinux.com>


  parent reply	other threads:[~2001-12-30  1:09 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
2001-12-28 21:52 ` Jorge Nerin [this message]
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=3C2CE995.6080503@zaralinux.com \
    --to=comandante@zaralinux.com \
    --cc=jlladono@pie.xtec.es \
    --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