public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* My /dev/hda became /dev/hde after upgrading
@ 2002-08-29  5:26 brian
  2002-08-29  6:23 ` Andre Hedrick
  0 siblings, 1 reply; 3+ messages in thread
From: brian @ 2002-08-29  5:26 UTC (permalink / raw)
  To: linux-kernel

While running 2.4.19-pre7-ac2 my system was happily buzzing away.

I upgraded to 2.4.19 and my /dev/hda became /dev/hde which caused
various boot problems, which I worked around.

It seems clear that upon booting 2.4.19, the newer kernel recognized
the "other" IDE controller on the MB, which 2.4.19-pre7-ac2 had not.

The manual that came with the MB said to use the IDE slots marked
IDE0 / IDE1 if I wasn't going to use RAID.

If I wanted to use RAID use the slots marked RAID0/RAID1.

I was just wondering how linux decides which controller is first
(hda-hdd) and which is second (hde-hdh).

Here is what I see from dmesg:

Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PDC20265: IDE controller on PCI bus 00 dev 70
PDC20265: chipset revision 2
PDC20265: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xb400-0xb407, BIOS settings: hda:pio, hdb:DMA
    ide1: BM-DMA at 0xb408-0xb40f, BIOS settings: hdc:pio, hdd:pio
VP_IDE: IDE controller on PCI bus 00 dev 89
PCI: No IRQ known for interrupt pin A of device 00:11.1. Please try using pci=bi
osirq.
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt8233 (rev 00) IDE UDMA100 controller on pci00:11.1
    ide2: BM-DMA at 0xb800-0xb807, BIOS settings: hde:DMA, hdf:pio
    ide3: BM-DMA at 0xb808-0xb80f, BIOS settings: hdg:DMA, hdh:pio
hde: ST380021A, ATA DISK drive
hdg: RW-241040, ATAPI CD/DVD-ROM drive
ide2 at 0x1f0-0x1f7,0x3f6 on irq 14
ide3 at 0x170-0x177,0x376 on irq 15
hde: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=9729/255/63, UDMA(100)
Partition check:
 hde: hde1 hde2 < hde5 hde6 >

-- 
Brian Litzinger

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: My /dev/hda became /dev/hde after upgrading
  2002-08-29  5:26 My /dev/hda became /dev/hde after upgrading brian
@ 2002-08-29  6:23 ` Andre Hedrick
  2002-08-30 20:27   ` brian
  0 siblings, 1 reply; 3+ messages in thread
From: Andre Hedrick @ 2002-08-29  6:23 UTC (permalink / raw)
  To: brian; +Cc: linux-kernel


For now issue in your append line "ide=reverse".
This will get you by until it can be fixed.

On Wed, 28 Aug 2002 brian@worldcontrol.com wrote:

> While running 2.4.19-pre7-ac2 my system was happily buzzing away.
> 
> I upgraded to 2.4.19 and my /dev/hda became /dev/hde which caused
> various boot problems, which I worked around.
> 
> It seems clear that upon booting 2.4.19, the newer kernel recognized
> the "other" IDE controller on the MB, which 2.4.19-pre7-ac2 had not.
> 
> The manual that came with the MB said to use the IDE slots marked
> IDE0 / IDE1 if I wasn't going to use RAID.
> 
> If I wanted to use RAID use the slots marked RAID0/RAID1.
> 
> I was just wondering how linux decides which controller is first
> (hda-hdd) and which is second (hde-hdh).
> 
> Here is what I see from dmesg:
> 
> Uniform Multi-Platform E-IDE driver Revision: 6.31
> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
> PDC20265: IDE controller on PCI bus 00 dev 70
> PDC20265: chipset revision 2
> PDC20265: not 100% native mode: will probe irqs later
>     ide0: BM-DMA at 0xb400-0xb407, BIOS settings: hda:pio, hdb:DMA
>     ide1: BM-DMA at 0xb408-0xb40f, BIOS settings: hdc:pio, hdd:pio
> VP_IDE: IDE controller on PCI bus 00 dev 89
> PCI: No IRQ known for interrupt pin A of device 00:11.1. Please try using pci=bi
> osirq.
> VP_IDE: chipset revision 6
> VP_IDE: not 100% native mode: will probe irqs later
> VP_IDE: VIA vt8233 (rev 00) IDE UDMA100 controller on pci00:11.1
>     ide2: BM-DMA at 0xb800-0xb807, BIOS settings: hde:DMA, hdf:pio
>     ide3: BM-DMA at 0xb808-0xb80f, BIOS settings: hdg:DMA, hdh:pio
> hde: ST380021A, ATA DISK drive
> hdg: RW-241040, ATAPI CD/DVD-ROM drive
> ide2 at 0x1f0-0x1f7,0x3f6 on irq 14
> ide3 at 0x170-0x177,0x376 on irq 15
> hde: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=9729/255/63, UDMA(100)
> Partition check:
>  hde: hde1 hde2 < hde5 hde6 >
> 
> -- 
> Brian Litzinger
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

Andre Hedrick
LAD Storage Consulting Group


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: My /dev/hda became /dev/hde after upgrading
  2002-08-29  6:23 ` Andre Hedrick
@ 2002-08-30 20:27   ` brian
  0 siblings, 0 replies; 3+ messages in thread
From: brian @ 2002-08-30 20:27 UTC (permalink / raw)
  To: Andre Hedrick; +Cc: linux-kernel

On Wed, Aug 28, 2002 at 11:23:36PM -0700, Andre Hedrick wrote:
> 
> For now issue in your append line "ide=reverse".
> This will get you by until it can be fixed.

Thanks, that worked.

An interesting note.  While things were running backwards, that
is on /dev/hde the filesystem was very slow.  An operation
that generally ran in about 5 seconds took about a minute.
A large filesystem backup, generally taking about 5 minutes,
took about 45 minutes.

As of reversing things back (/dev/hda) speed is back to normal.

The system only seemed slowed on disk access.



> On Wed, 28 Aug 2002 brian@worldcontrol.com wrote:
> 
> > While running 2.4.19-pre7-ac2 my system was happily buzzing away.
> > 
> > I upgraded to 2.4.19 and my /dev/hda became /dev/hde which caused
> > various boot problems, which I worked around.
> > 
> > It seems clear that upon booting 2.4.19, the newer kernel recognized
> > the "other" IDE controller on the MB, which 2.4.19-pre7-ac2 had not.
> > 
> > The manual that came with the MB said to use the IDE slots marked
> > IDE0 / IDE1 if I wasn't going to use RAID.
> > 
> > If I wanted to use RAID use the slots marked RAID0/RAID1.
> > 
> > I was just wondering how linux decides which controller is first
> > (hda-hdd) and which is second (hde-hdh).
> > 
> > Here is what I see from dmesg:
> > 
> > Uniform Multi-Platform E-IDE driver Revision: 6.31
> > ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
> > PDC20265: IDE controller on PCI bus 00 dev 70
> > PDC20265: chipset revision 2
> > PDC20265: not 100% native mode: will probe irqs later
> >     ide0: BM-DMA at 0xb400-0xb407, BIOS settings: hda:pio, hdb:DMA
> >     ide1: BM-DMA at 0xb408-0xb40f, BIOS settings: hdc:pio, hdd:pio
> > VP_IDE: IDE controller on PCI bus 00 dev 89
> > PCI: No IRQ known for interrupt pin A of device 00:11.1. Please try using pci=bi
> > osirq.
> > VP_IDE: chipset revision 6
> > VP_IDE: not 100% native mode: will probe irqs later
> > VP_IDE: VIA vt8233 (rev 00) IDE UDMA100 controller on pci00:11.1
> >     ide2: BM-DMA at 0xb800-0xb807, BIOS settings: hde:DMA, hdf:pio
> >     ide3: BM-DMA at 0xb808-0xb80f, BIOS settings: hdg:DMA, hdh:pio
> > hde: ST380021A, ATA DISK drive
> > hdg: RW-241040, ATAPI CD/DVD-ROM drive
> > ide2 at 0x1f0-0x1f7,0x3f6 on irq 14
> > ide3 at 0x170-0x177,0x376 on irq 15
> > hde: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=9729/255/63, UDMA(100)
> > Partition check:
> >  hde: hde1 hde2 < hde5 hde6 >
> > 
> > -- 
> > Brian Litzinger
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
> > 
> 
> Andre Hedrick
> LAD Storage Consulting Group

-- 
Brian Litzinger

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2002-08-30 20:23 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-08-29  5:26 My /dev/hda became /dev/hde after upgrading brian
2002-08-29  6:23 ` Andre Hedrick
2002-08-30 20:27   ` brian

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox