Did you remove the jumper from the disk to put it in "single drive =20
mode" and you're using an ATA/66 cable? That's the only simple thing =20
I can think of that you might have missed. It looks like the card is =20
working correctly.

On Apr 8, 2006, at 2:36 PM, Dmitry N. Vladimirov wrote:

> Hi guys.
> I'm not an not an expert on the NetBSD on macppc (rather newbie) and i
> wanted to get use out of the G3 was getting dusty.
> I unstalled the NetBSD 2.0.2 and it worked fine.
> After that I trying to get more out of it and insert the Promise
> Ultra66 i was using on my PC into it (I'm running samba on it and I
> want to make it faster).
>
> Per the dmesg.boot (I attached below) the card is being identified =20
> correctly
> (or am I wrong?).
> But despite of any tries the I cannot see drive attached to it (though
> when i connect it to the usual IDE connector on the motherboard, it
> worked fine - i also attached the output of the "atactl wd2 identify"
> command - "wd2" is the disk I'm trying to see attached to the Promise
> controller and "wd2" is its name when it's attached to the "USUAL" IDE
> on the motherboard).
>
> Could you give any advices or suggestions?
>
> It'd be greatly appreciated.
>
> Sincerely,
> Dmitry
>
> --------------------------------- dmesg.boot ----------------------
> NetBSD 2.0.2 (GENERIC) #0: Tue Mar 22 16:19:08 UTC 2005
>         jmc@faith.netbsd.org:/home/builds/ab/netbsd-2-0-2-RELEASE/=20
> macppc/200503220140Z-obj/home/builds/ab/netbsd-2-0-2-RELEASE/src/=20
> sys/arch/macppc/compile/GENERIC
> total memory =3D 192 MB
> avail memory =3D 178 MB
> mainbus0 (root)
> cpu0 at mainbus0: 750 (Revision 2.2), ID 0 (primary)
> cpu0: HID0 8290c0a4<EMCP,ECLK,DOZE,DPM,ICE,DCE,SGE,BTIC,BHT>
> cpu0: 237.29 MHz, no-parity 512KB WB L2 cache (PB SRAM) at 2:1 ratio
> grackle0 at mainbus0
> pci0 at grackle0 bus 0
> pci0: i/o space, memory space enabled
> pchb0 at pci0 dev 0 function 0
> pchb0: Motorola MPC106 "Grackle" Host Bridge (rev. 0x40)
> pdcide0 at pci0 dev 13 function 0
> pdcide0: Promise Ultra66/ATA Bus Master IDE Accelerator (rev. 0x01)
> pdcide0: bus-master DMA support present
> pdcide0: primary channel configured to native-PCI mode
> pdcide0: using irq 23 for native-PCI interrupt
> atabus0 at pdcide0 channel 0
> pdcide0: secondary channel configured to native-PCI mode
> atabus1 at pdcide0 channel 1
> ex0 at pci0 dev 15 function 0: 3Com 3c905C-TX 10/100 Ethernet with =20
> mngmt (rev. 0x74)
> ex0: interrupting at irq 25
> ex0: MAC address 00:04:79:66:79:44
> bmtphy0 at ex0 phy 24: Broadcom 3c905C internal PHY, rev. 6
> bmtphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> obio0 at pci0 dev 16 function 0: addr 0xf3000000
> mesh0 at obio0 offset 0x10000 irq 12: 50MHz, SCSI ID 7
> scsibus0 at mesh0: 8 targets, 8 luns per target
> bm0 at obio0 offset 0x11000 irq 42,33: address 00:05:02:b5:98:04
> zsc0 at obio0 offset 0x13000: irq 15,16
> zstty0 at zsc0 channel 0
> zstty1 at zsc0 channel 1
> davbus at obio0 offset 0x14000 not configured
> swim3 at obio0 offset 0x15000 not configured
> nvram0 at obio0 offset 0x60000
> wdc0 at obio0 offset 0x20000 irq 13: DMA transfer
> atabus2 at wdc0 channel 0
> wdc1 at obio0 offset 0x21000 irq 14: DMA transfer
> atabus3 at wdc1 channel 0
> adb0 at obio0 offset 0x16000 irq 18: 0 targets
> aed0 at adb0 addr 0: ADB Event device
> ofb0 at pci0 dev 18 function 0: ATI Technologies 3D Rage Pro
> ofb0: 1024 x 768, 8bpp
> wsdisplay0 at ofb0 kbdmux 1: console (std, vt100 emulation)
> wsmux1: connecting to wsdisplay0
> scsibus0: waiting 2 seconds for devices to settle...
> wd0 at atabus2 drive 0: <QUANTUM FIREBALL640A>
> wd0: drive supports 8-sector PIO transfers, LBA addressing
> wd0: 612 MB, 1244 cyl, 16 head, 63 sec, 512 bytes/sect x 1253952 =20
> sectors
> wd0: drive supports PIO mode 4, DMA mode 2
> wd1 at atabus2 drive 1: <SAMSUNG WINNER-3 WN31273A(1.27GB)>
> wd1: drive supports 16-sector PIO transfers, LBA addressing
> wd1: 1212 MB, 2464 cyl, 16 head, 63 sec, 512 bytes/sect x 2483712 =20
> sectors
> wd1: drive supports PIO mode 4, DMA mode 2
> wd0(wdc0:0:0): using PIO mode 4, DMA mode 2 (using DMA data transfers)
> wd1(wdc0:0:1): using PIO mode 4, DMA mode 2 (using DMA data transfers)
> atapibus0 at atabus3: 2 targets
> cd0 at atapibus0 drive 0: <HITACHI CDR-8130, , 0021> cdrom removable
> cd0: drive supports PIO mode 4, DMA mode 2
> cd0(wdc1:0:0): using PIO mode 4, DMA mode 2 (using DMA data transfers)
> boot device: wd0
> root on wd0a dumps on wd0b
> root file system type: ffs
> ----------- end of dmesg.boot --------------------
>
> ------------ output of the "atactl wd2 identify" command -------
> Model: WDC WD200BB-00CLB0, Rev: 05.04E05, Serial #: WD-WMAAR1227306
> Device type: ATA, fixed
> Device capabilities:
>         DMA
>         LBA
>         ATA standby timer values
>         IORDY operation
>         IORDY disabling
> Device supports following standards:
> ATA-1 ATA-2 ATA-3 ATA-4 ATA-5
> Command set support:
>         READ BUFFER command
>         WRITE BUFFER command
>         Host Protected Area feature set
>         look-ahead
>         write cache
>         Power Management feature set
>         Security Mode feature set
>         SMART feature set
>         Automatic Acoustic Management feature set
>         SET MAX security extension
>         DOWNLOAD MICROCODE command
> Command sets/features enabled:
>         look-ahead
>         write cache
> ------------ output of the "atactl wd2 identify" command -------
>
>
>
>
>
>
>
> --=20
> =D0=A1 =D1=83=D0=B2=D0=B0=D0=B6=D0=B5=D0=BD=D0=B8=D0=B5=D0=BC,
>  Dmitry                          mailto: press Reply button
>
>
>
> !DSPAM:443a332f170444209710833!
>
>
>