From owner-freebsd-questions Sat Sep 9 19:26:38 2000 Delivered-To: freebsd-questions@freebsd.org Received: from blueyonder.co.uk (pcow025o.blueyonder.co.uk [195.188.53.125]) by hub.freebsd.org (Postfix) with ESMTP id AFBF437B422 for ; Sat, 9 Sep 2000 19:26:30 -0700 (PDT) Received: from i-zone.demon.co.uk ([62.30.21.2]) by blueyonder.co.uk with Microsoft SMTPSVC(5.5.1877.197.19); Sun, 10 Sep 2000 03:27:24 +0100 Message-ID: Date: Sun, 10 Sep 2000 03:26:15 +0100 To: freebsd-questions@freebsd.org From: John Subject: (was) ATA66 troubles under 4.0R vs 3.4 References: <0ad401c0186b$ddaddc20$c991f280@mfn.org> In-Reply-To: <0ad401c0186b$ddaddc20$c991f280@mfn.org> MIME-Version: 1.0 Content-Type: text/plain;charset=us-ascii;format=flowed User-Agent: Turnpike/6.00-Alpha-20-U () Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, just another data point, hope it makes sense In message <0ad401c0186b$ddaddc20$c991f280@mfn.org>, graphics writes >Hello, > > After seeing uncountable sudden "drive deaths" >on *brand new* drives, we did a little digging (thank >god for the archives!) and have noted the many similar >tales of woe... Now, since 3.4 reportedly does not suffer >from these troubles, we are going to go back down to 3.4, >however, we would like the transition to be as painless as >humanly possible, so: Can we simply do an overlay of >3.4 onto a 4.0 system? doubt it very much, but then i'm not an expert :) > >Also, is it known whether 4.1 has fixed the 4.0 ATA66 >problems? How about 5-stable? > Well, I dunno if later versions 'fix' it but I'm unable to tell whether its the driver or the chipset thats broken [0]. I am seeing much the same as you except that the problem affects only one drive, and i use dma-33. I have two hard drives on ide channel 0 and a hard drive & a cdrom on ide channel 1, where the cdrom drive is on the master [1] and the hard drive is slave [2]. At bootup, the ata-slave times out. It is however fully functional under 3.4. The two hard drives and the cdrom are recognised by the 'atac' controller, but not the final drive, which is a Seagate Medallist Pro 4520 I think the answer will be to comment out the ata stuff from the kernel and put in the wd stuff but heres hoping getting all the entries ok in both kernel & fstab :) Here is my dmesg output: bash-2.04$ dmesg Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.1-RELEASE #0: Sun Sep 10 01:24:51 BST 2000 root@fw-router.clues.yi.org:/usr/src/sys/compile/CLUES Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 149921017 Hz CPU: Cyrix 6x86MX (149.92-MHz 686-class CPU) Origin = "CyrixInstead" Id = 0x600 Stepping = 0 DIR=0x0451 Features=0x80a135 real memory = 66060288 (64512K bytes) config> di pcic0 No such device: pcic0 Invalid command or syntax. Type `?' for help. config> di sn0 No such device: sn0 Invalid command or syntax. Type `?' for help. config> di lnc0 No such device: lnc0 Invalid command or syntax. Type `?' for help. config> di le0 No such device: le0 Invalid command or syntax. Type `?' for help. config> di ie0 No such device: ie0 Invalid command or syntax. Type `?' for help. config> di fe0 No such device: fe0 Invalid command or syntax. Type `?' for help. config> di cs0 No such device: cs0 Invalid command or syntax. Type `?' for help. config> di bt0 No such device: bt0 Invalid command or syntax. Type `?' for help. config> di aic0 No such device: aic0 Invalid command or syntax. Type `?' for help. config> di aha0 No such device: aha0 Invalid command or syntax. Type `?' for help. config> di adv0 No such device: adv0 Invalid command or syntax. Type `?' for help. config> en ed0 config> po ed0 0x300 config> ir ed0 10 config> iom ed0 0xd8000 config> f ed0 0 config> q avail memory = 61558784 (60116K bytes) Preloaded elf kernel "kernel" at 0xc02a3000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc02a309c. md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 atapci0: port 0x4000-0x400f,0x211d0240-0x211d0243,0x 59310498-0x5931049f,0x10e0a00-0x10e0a03,0xc7540a20-0xc7540a27 irq 0 at device 1. 1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: <3Dfx Voodoo graphics accelerator> at 9.0 pci0: (vendor=0x1274, dev=0x1371) at 13.0 irq 11 pci0: at 20.0 irq 0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 ed0 at port 0x300-0x31f iomem 0xd8000-0xdbfff irq 10 drq 0 on isa0 ed0: address 00:00:c0:75:70:a6, type SMC8216/SMC8216C (16 bit) ata1-slave: identify retries exceeded ad0: 1554MB [3158/16/63] at ata0-master using WDMA2 ad1: 3098MB [6296/16/63] at ata0-slave using UDMA33 acd0: CDROM at ata1-master using WDMA2 Mounting root from ufs:/dev/ad0s1a bash-2.04$ [0] i know, cheap hardware :) [1] on a completely seperate topic that I cant fathom, I can boot from both redhat 6.1 CD and latest SuSE CD with this drive but not with any FreeBSD CD ( i have tried since 2.2.5 - all Walnut Creek Cds ) - are some CD drives incompatible with Rockridge? [2] should it be an issue having the HD on secondary channel slave? cheers -- John - freebsd-lists@i-zone.demon.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message