onboard ICH4 seen as ICH3 (ultra100 controller onboard) (2.4.20/2.4.21-pre7)

onboard ICH4 seen as ICH3 (ultra100 controller onboard) (2.4.20/2.4.21-pre7)

Post by ker.. » Sun, 06 Apr 2003 12:00:08



mainbord is an intel se7500cw2 (dual xeon)
same problem with 2.4.20 and 2.4.21-pre7

ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
ICH3: IDE controller at PCI slot 00:1f.1
ICH3: chipset revision 2
ICH3: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0x7040-0x7047, BIOS settings: hda:pio, hdb:pio
    ide1: BM-DMA at 0x7048-0x704f, BIOS settings: hdc:pio, hdd:pio

but this isn't an ICH3, but an ICH4 :

]$ cat /proc/ide/piix

Controller: 0

                                Intel PIIX4 Ultra 100 Chipset.
--------------- Primary Channel ---------------- Secondary Channel
-------------
                 enabled                          enabled
--------------- drive0 --------- drive1 -------- drive0 ---------- drive1
------
DMA enabled:    yes              no              yes               no
UDMA enabled:   yes              no              yes               no
UDMA enabled:   2                X               2                 X
UDMA
DMA
PIO

speed detection is also wrong :

hda: 351651888 sectors (180046 MB) w/2048KiB Cache, CHS=21889/255/63,
UDMA(33)
hdc: attached ide-disk driver.
hdc: host protected area => 1
hdc: 351651888 sectors (180046 MB) w/2048KiB Cache, CHS=21889/255/63,
UDMA(33)

while same harddrives (and same cables) on promise Ultra100 controller :

hde: attached ide-disk driver.
hde: host protected area => 1
hde: 351651888 sectors (180046 MB) w/2048KiB Cache, CHS=21889/255/63,
UDMA(100)

]$ cat /proc/pci
PCI devices found:
  Bus  0, device   0, function  0:
    Host bridge: Intel Corp. e7500 [Plumas] DRAM Controller (rev 3).
  Bus  0, device   0, function  1:
    Class ff00: Intel Corp. e7500 [Plumas] DRAM Controller Error Reporting
(rev 3).
  Bus  0, device   2, function  0:
    PCI bridge: Intel Corp. e7500 [Plumas] HI_B Virtual PCI Bridge (F0)
(rev 3).
      Master Capable.  Latency=64.  Min Gnt=6.
  Bus  0, device  29, function  0:
    USB Controller: Intel Corp. 82801CA/CAM USB (Hub #1) (rev 2).
      IRQ 10.
      I/O at 0x7000 [0x701f].
  Bus  0, device  29, function  1:
    USB Controller: Intel Corp. 82801CA/CAM USB (Hub #2) (rev 2).
      IRQ 5.
      I/O at 0x7020 [0x703f].
  Bus  0, device  30, function  0:
    PCI bridge: Intel Corp. 82801BA/CA/DB PCI Bridge (rev 66).
      Master Capable.  No bursts.  Min Gnt=14.
  Bus  0, device  31, function  0:
    ISA bridge: Intel Corp. 82801CA ISA Bridge (LPC) (rev 2).
  Bus  0, device  31, function  1:
    IDE interface: Intel Corp. 82801CA IDE U100 (rev 2).
      I/O at 0x7040 [0x704f].
      Non-prefetchable 32 bit memory at 0x20000000 [0x200003ff].
  Bus  0, device  31, function  3:
    SMBus: Intel Corp. 82801CA/CAM SMBus (rev 2).
      IRQ 11.
      I/O at 0x7060 [0x707f].
  Bus  1, device  28, function  0:
    PIC: Intel Corp. 82870P2 P64H2 I/OxAPIC (rev 3).
      Non-prefetchable 32 bit memory at 0xfb100000 [0xfb100fff].
  Bus  1, device  30, function  0:
    PIC: Intel Corp. 82870P2 P64H2 I/OxAPIC (#2) (rev 3).
      Non-prefetchable 32 bit memory at 0xfb101000 [0xfb101fff].
  Bus  1, device  29, function  0:
    PCI bridge: Intel Corp. 82870P2 P64H2 Hub PCI Bridge (rev 3).
      Master Capable.  Latency=64.  Min Gnt=38.
  Bus  1, device  31, function  0:
    PCI bridge: Intel Corp. 82870P2 P64H2 Hub PCI Bridge (#2) (rev 3).
      Master Capable.  Latency=64.  Min Gnt=38.
  Bus  2, device   1, function  0:
    RAID bus controller: 3ware Inc 3ware 7000-series ATA-RAID (rev 1).
      IRQ 10.
      Master Capable.  Latency=72.  Min Gnt=9.
      I/O at 0x8000 [0x800f].
      Non-prefetchable 32 bit memory at 0xfb200000 [0xfb20000f].
      Non-prefetchable 32 bit memory at 0xfb800000 [0xfbffffff].
  Bus  2, device   2, function  0:
    PCI bridge: Digital Equipment Corporation DECchip 21150 (rev 6).
      Master Capable.  Latency=64.  Min Gnt=4.
  Bus  3, device   1, function  0:
    RAID bus controller: Promise Technology, Inc. 20268R (rev 2).
      IRQ 10.
      Master Capable.  Latency=64.  Min Gnt=4.Max Lat=18.
      I/O at 0x9000 [0x9007].
      I/O at 0x9010 [0x9013].
      I/O at 0x9020 [0x9027].
      I/O at 0x9030 [0x9033].
      I/O at 0x9040 [0x904f].
      Non-prefetchable 32 bit memory at 0xfc000000 [0xfc00ffff].
  Bus  3, device   2, function  0:
    RAID bus controller: Promise Technology, Inc. 20268R (#2) (rev 2).
      IRQ 10.
      Master Capable.  Latency=64.  Min Gnt=4.Max Lat=18.
      I/O at 0x9080 [0x9087].
      I/O at 0x9090 [0x9093].
      I/O at 0x90a0 [0x90a7].
      I/O at 0x90b0 [0x90b3].
      I/O at 0x90c0 [0x90cf].
      Non-prefetchable 32 bit memory at 0xfc010000 [0xfc01ffff].
  Bus  4, device   1, function  0:
    Ethernet controller: Intel Corp. 82545EM Gigabit Ethernet Controller
(rev 1).
      IRQ 10.
      Master Capable.  Latency=64.  Min Gnt=255.
      Non-prefetchable 64 bit memory at 0xfc100000 [0xfc11ffff].
      I/O at 0xa000 [0xa03f].
  Bus  5, device   2, function  0:
    SCSI storage controller: Adaptec AHA-2940U/UW/D / AIC-7881U (rev 0).
      IRQ 5.
      Master Capable.  Latency=64.  Min Gnt=8.Max Lat=8.
      I/O at 0xb000 [0xb0ff].
      Non-prefetchable 32 bit memory at 0xfc220000 [0xfc220fff].
  Bus  5, device   3, function  0:
    VGA compatible controller: ATI Technologies Inc Rage XL (rev 39).
      IRQ 11.
      Master Capable.  Latency=66.  Min Gnt=8.
      Non-prefetchable 32 bit memory at 0xfd000000 [0xfdffffff].
      I/O at 0xb400 [0xb4ff].
      Non-prefetchable 32 bit memory at 0xfc221000 [0xfc221fff].
  Bus  5, device   6, function  0:
    RAID bus controller: Promise Technology, Inc. 20267 (rev 2).
      IRQ 11.
      Master Capable.  Latency=64.
      I/O at 0xb850 [0xb857].
      I/O at 0xb844 [0xb847].
      I/O at 0xb848 [0xb84f].
      I/O at 0xb840 [0xb843].
      I/O at 0xb800 [0xb83f].
      Non-prefetchable 32 bit memory at 0xfc200000 [0xfc21ffff].

]$ cat /proc/ide/ide0/config
pci bus 00 device f9 vendor 8086 device 248b channel 0
86 80 8b 24 07 00 80 02 02 8a 01 01 00 00 00 00
01 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00
41 70 00 00 00 00 00 20 00 00 00 00 86 80 19 34
00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00
07 a3 07 a3 00 00 00 00 05 00 02 02 00 00 00 00
00 00 00 00 00 04 00 00 00 00 00 00 00 00 00 00
08 00 00 00 00 00 00 00 08 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 47 0f 00 00 00 00 00 00

]$ cat /proc/ide/ide1/config
pci bus 00 device f9 vendor 8086 device 248b channel 1
86 80 8b 24 07 00 80 02 02 8a 01 01 00 00 00 00
01 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00
41 70 00 00 00 00 00 20 00 00 00 00 86 80 19 34
00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00
07 a3 07 a3 00 00 00 00 05 00 02 02 00 00 00 00
00 00 00 00 00 04 00 00 00 00 00 00 00 00 00 00
08 00 00 00 00 00 00 00 08 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 47 0f 00 00 00 00 00 00

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

onboard ICH4 seen as ICH3 (ultra100 controller onboard) (2.4.20/2.4.21-pre7)

Post by Alan Co » Sun, 06 Apr 2003 19:40:11



Quote:> mainbord is an intel se7500cw2 (dual xeon)
> same problem with 2.4.20 and 2.4.21-pre7

I'll take a look. Its probably just a typo in the list of names.
Its doing UDMA100 so it got the rest of it right 8)

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

onboard ICH4 seen as ICH3 (ultra100 controller onboard) (2.4.20/2.4.21-pre7)

Post by Stephan van Hiene » Sun, 06 Apr 2003 21:10:17




> > mainbord is an intel se7500cw2 (dual xeon)
> > same problem with 2.4.20 and 2.4.21-pre7

> I'll take a look. Its probably just a typo in the list of names.
> Its doing UDMA100 so it got the rest of it right 8)

I don't think it is doing U100 :

]# hdparm -Tt /dev/hda

/dev/hda:
 Timing buffer-cache reads:   128 MB in  0.27 seconds =474.07 MB/sec
 Timing buffered disk reads:  64 MB in  2.54 seconds = 25.20 MB/sec

]# hdparm -Tt /dev/hdc

/dev/hdc:
 Timing buffer-cache reads:   128 MB in  0.27 seconds =474.07 MB/sec
 Timing buffered disk reads:  64 MB in  2.58 seconds = 24.81 MB/sec

]# hdparm -Tt /dev/hde

/dev/hde:
 Timing buffer-cache reads:   128 MB in  0.27 seconds =474.07 MB/sec
 Timing buffered disk reads:  64 MB in  1.37 seconds = 46.72 MB/sec

(hde= promise U100)

]# hdparm -X69 /dev/hda

/dev/hda:
 setting xfermode to 69 (UltraDMA mode5)

dmesg gives me :

ide0: Speed warnings UDMA 3/4/5 is not functional.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

onboard ICH4 seen as ICH3 (ultra100 controller onboard) (2.4.20/2.4.21-pre7)

Post by Stephan van Hiene » Sun, 06 Apr 2003 23:20:12



> > I don't think it is doing U100 :

> why?  25 MB/s is exactly what you should expect from a disk
> which has around 15 GB/platter density.  the transfer mode
> doesn't matter, as long as it's 10-20% faster than the transfer
> rate of the disk's outer tracks.

because it is the same disk (WD1800BB (180GB)) only difference is the
controller...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
 
 
 

onboard ICH4 seen as ICH3 (ultra100 controller onboard) (2.4.20/2.4.21-pre7)

Post by Stephan van Hiene » Sun, 06 Apr 2003 23:30:16



> > > > I don't think it is doing U100 :

> > > why?  25 MB/s is exactly what you should expect from a disk
> > > which has around 15 GB/platter density.  the transfer mode
> > > doesn't matter, as long as it's 10-20% faster than the transfer
> > > rate of the disk's outer tracks.

> > because it is the same disk (WD1800BB (180GB)) only difference is the
> > controller...

> is the 80-pin cable validly configured and properly detected?
> or did you cover this already?

all disks and cables are the same
(i have 15 of these disks in this server)
only difference are the controllers

and since the kernel is giving me incorrect info at boottime
(ICH3 (instead of what is really there (ICH4))
i really think this is an kernel problem
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

onboard ICH4 seen as ICH3 (ultra100 controller onboard) (2.4.20/2.4.21-pre7)

Post by Andre Hedric » Sun, 06 Apr 2003 23:50:10


NO, since they all use the same timings there is no problem.
Intel never made an Ultra 133, and all the timings from PIIX forward build
on each other.

There is no bug, except in your BIOS maybe.

Cheers,



> > > > > I don't think it is doing U100 :

> > > > why?  25 MB/s is exactly what you should expect from a disk
> > > > which has around 15 GB/platter density.  the transfer mode
> > > > doesn't matter, as long as it's 10-20% faster than the transfer
> > > > rate of the disk's outer tracks.

> > > because it is the same disk (WD1800BB (180GB)) only difference is the
> > > controller...

> > is the 80-pin cable validly configured and properly detected?
> > or did you cover this already?

> all disks and cables are the same
> (i have 15 of these disks in this server)
> only difference are the controllers

> and since the kernel is giving me incorrect info at boottime
> (ICH3 (instead of what is really there (ICH4))
> i really think this is an kernel problem
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

> 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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

onboard ICH4 seen as ICH3 (ultra100 controller onboard) (2.4.20/2.4.21-pre7)

Post by Stephan van Hiene » Mon, 07 Apr 2003 00:30:13



> NO, since they all use the same timings there is no problem.
> Intel never made an Ultra 133, and all the timings from PIIX forward build
> on each other.

i didn't say anything about u133 ?
(hdparm -x69 = udma5/u100 ?)

Quote:

> There is no bug, except in your BIOS maybe.

in my bios i didn't select any drives (i thought linux was just bypassing
bios for disk access ?)
so why can't i use u100 with the onboard controller ? (which is an u100
controller)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
 
 
 

onboard ICH4 seen as ICH3 (ultra100 controller onboard) (2.4.20/2.4.21-pre7)

Post by Stephan van Hiene » Mon, 07 Apr 2003 12:30:10



> Looking back over the thread, you have a failed cable detect.
> I do not know why, but pat ide0=ata66 and ide1=ata66 to see if that is a
> temp work-around.

ok this works (but ide0=ata100/ide1=at100 doesn't work)

hda: 351651888 sectors (180046 MB) w/2048KiB Cache, CHS=21889/255/63,
UDMA(100)
blk: queue c03ddf68, I/O limit 4095Mb (mask 0xffffffff)
hdc: 351651888 sectors (180046 MB) w/2048KiB Cache, CHS=21889/255/63,
UDMA(100)
blk: queue c03de2cc, I/O limit 4095Mb (mask 0xffffffff)

]$ cat /proc/ide/piix

                                Intel PIIX4 Ultra 100 Chipset.
--------------- Primary Channel ---------------- Secondary Channel
-------------
                 enabled                          enabled
--------------- drive0 --------- drive1 -------- drive0 ---------- drive1
------
DMA enabled:    yes              no              yes               no
UDMA enabled:   yes              no              yes               no
UDMA enabled:   3                X               3                 X
UDMA
DMA
PIO

]# hdparm -X69 /dev/hda

/dev/hda:
 setting xfermode to 69 (UltraDMA mode5)

]# hdparm -X69 /dev/hdc

/dev/hdc:
 setting xfermode to 69 (UltraDMA mode5)

]# cat /proc/ide/piix

                                Intel PIIX4 Ultra 100 Chipset.
--------------- Primary Channel ---------------- Secondary Channel
-------------
                 enabled                          enabled
--------------- drive0 --------- drive1 -------- drive0 ---------- drive1
------
DMA enabled:    yes              no              yes               no
UDMA enabled:   yes              no              yes               no
UDMA enabled:   5                X               5                 X
UDMA
DMA
PIO

Quote:

> You said nothing selected?

> Does that mean your bios is set to [none] for all devices?
> If so change it to [auto], [none] tends to do strange things.

then i get get the 'lba48 problem', my bios doesn't support lba48
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
 
 
 

onboard ICH4 seen as ICH3 (ultra100 controller onboard) (2.4.20/2.4.21-pre7)

Post by Andre Hedric » Mon, 07 Apr 2003 12:40:19


Looking back over the thread, you have a failed cable detect.
I do not know why, but pat ide0=ata66 and ide1=ata66 to see if that is a
temp work-around.

You said nothing selected?

Does that mean your bios is set to [none] for all devices?
If so change it to [auto], [none] tends to do strange things.

Cheers,

Andre Hedrick
LAD Storage Consulting Group

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

1. Probleme mit 3DLabs Permedia 2v (onboard) / Problems with 3DLabs Permedia 2v (onboard)

Hallo!

Auf Arbeit nutze ich eine DIGITAL Workstation mit onboard 3DLabs
Permedia 2v Grafikchip. Leider bekomme ich unter X11 Version 4 (KDE
2.xx, SuSE 7.2 bzw. 7.3)  bei Verwendung des glint-Treibers mie 16bit
und 1280x1024 Streifen und falsche Farbmuster an den Titel- und
Menleisten sowie an den Scrollbalken. Gibt es generelle Probleme mit
onboard Grafikcontrollern dieses Typs? Was kann ich tun?

Mit freundlichen Gr?en
J?rg Emmelmann

Hello!

At work I use a DIGITAL workstation with onboard 3DLabs Permedia 2v
Video controller. Unfortunately I get in X11 Version 4 (KDE 2.xx, SuSE
7.2 respective 7.3) when I use the glint driver with 16 bit and
1280x1024 stripes and false colour patterns at the titlebars menubards
and scrollbars. Are there general problems with onboard Video
controllers of this type? What can I do?

With kind reards
Joerg Emmelmann

2. DNS knocking on my Shorewall

3. Need patch NetMos 9835 for 2S PCI card

4. I Broke It

5. Need rc.serial for a QuickPath Flexport 4S

6. 256 or 512 of PB cache?

7. X server with prodesigner 2s (Hicolor)

8. rubini's snull on red hat 6.1

9. GCC 2.7.2s cpp - what the..?

10. HP ScanJet 4s (and not 4p)

11. Clocks for an Orchid Prodesigner 2s

12. SIIG 4S setup

13. RH6 Xconfig, S3 Trio64V2/DX and SAMSUNG SyncMaster 4S Monitor..