public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2004@gmx.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: 2.6 kernels misdetect harddisk geometry, 2.4 kernels are fine
Date: Thu, 01 Apr 2004 16:45:15 +0200	[thread overview]
Message-ID: <406C2AFB.1030101@gmx.net> (raw)

Hi,

the harddisk geometry recognized by 2.6 kernels differs from the geometry
recognized by 2.4 kernels. The 2.4 kernel version agrees with the BIOS and
fdisk/parted. The 2.6 kernel version seems senseless to me. Here is a diff
between bootup messages: (more info available if you need it)

--- /var/log/boot.msg24 2004-04-01 10:33:23.000000000 +0200
+++ /var/log/boot.msg26 2004-04-01 10:34:48.751069936 +0200
 Floppy drive(s): fd0 is 1.44M
 FDC 0 is a post-1991 82077
 RAMDISK driver initialized: 16 RAM disks of 64000K size 1024 blocksize
 loop: loaded (max 16 devices)
-Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
+Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
-VP_IDE: IDE controller at PCI slot 00:07.1
+VP_IDE: IDE controller at PCI slot 0000:00:07.1
 VP_IDE: chipset revision 6
 VP_IDE: not 100%% native mode: will probe irqs later
-ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
-VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:07.1
+VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci0000:00:07.1
     ide0: BM-DMA at 0xa400-0xa407, BIOS settings: hda:DMA, hdb:pio
     ide1: BM-DMA at 0xa408-0xa40f, BIOS settings: hdc:DMA, hdd:pio
 hda: IBM-DTLA-307030, ATA DISK drive
-blk: queue c03e66c0, I/O limit 4095Mb (mask 0xffffffff)
-hdc: TOSHIBA DVD-ROM SD-M1402, ATAPI CD/DVD-ROM drive
 ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
+hdc: TOSHIBA DVD-ROM SD-M1402, ATAPI CD/DVD-ROM drive
 ide1 at 0x170-0x177,0x376 on irq 15
-hda: attached ide-disk driver.
-hda: host protected area => 1
-hda: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=3737/255/63, UDMA(100)
-ide-floppy driver 0.99.newide
-Partition check:
+hda: max request size: 128KiB
+hda: 60036480 sectors (30738 MB) w/1916KiB Cache, CHS=59560/16/63, UDMA(100)
  hda: hda1 hda2 hda3
 ide-floppy driver 0.99.newide


Especially interesting are the lines:
-hda: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=3737/255/63, UDMA(100)
+hda: 60036480 sectors (30738 MB) w/1916KiB Cache, CHS=59560/16/63, UDMA(100)

You can see that both share the same sector count, but differing Megabytes
and differing CHS. This breaks nearly every partitioning program I know
and it makes supporting old ATARAID configurations a nightmare. (Some of
the RAID superblock locations depend on the BIOS idea of CHS.)

Is this change intentional or a bug?


Regards,
Carl-Daniel
-- 
http://www.hailfinger.org/


             reply	other threads:[~2004-04-01 14:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-01 14:45 Carl-Daniel Hailfinger [this message]
2004-04-01 15:22 ` 2.6 kernels misdetect harddisk geometry, 2.4 kernels are fine Sergey Vlasov
2004-04-01 16:49   ` Jamie Lokier
2004-04-01 22:44 ` Patrick J. LoPresti

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=406C2AFB.1030101@gmx.net \
    --to=c-d.hailfinger.kernel.2004@gmx.net \
    --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