From owner-freebsd-current@FreeBSD.ORG Fri May 21 14:00:08 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E7FBA16A4CE for ; Fri, 21 May 2004 14:00:08 -0700 (PDT) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id E88E043D31 for ; Fri, 21 May 2004 14:00:05 -0700 (PDT) (envelope-from adridg@cs.kun.nl) Received: from odin.cs.kun.nl [131.174.33.33] (helo=odin.cs.kun.nl) by pandora.cs.kun.nl (8.12.10/3.67) with ESMTP id i4LL03Nh007629 for ; Fri, 21 May 2004 23:00:03 +0200 (MEST) Date: Fri, 21 May 2004 23:00:03 +0200 (MEST) From: Adriaan de Groot To: freebsd-current@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Sat, 22 May 2004 05:15:46 -0700 Subject: SiI3112 not finding attached drives X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: adridg@cs.kun.nl List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 May 2004 21:00:09 -0000 My amd64 board blew up. Since it was new and funky, I had all my data on SATA drives. Then I realized that none of the available backup machines (x86es) had SATA ports at all, and that I really needed to read some stuff off of that SATA drive. Enter the SiI3112 SATA controller card - a piece of junk according to Soren, and perhaps he's right, but it's the only thing you can get when you walk into a store and say "I need a SATA controller _now_". Anyway, it doesn't work - in the classical sense of it kinda does and kinda doesn't. Right now I'm running: FreeBSD eggs.ebn.kun.nl 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Fri May 21 18:09:11 CEST 2004 root@eggs.ebn.kun.nl:/usr/obj/mnt/sys/CURRENT/src/sys/GENERIC i386 So that's -CURRENT from today. It was updated from a 5.1-R CD also freshly installed today. dmesg shows me atapci0: port 0xd000-0xd00f,0xcc00-0xcc03,0xc800-0xc807,0xc400-0xc403,0xc000-0xc007 mem 0xe8000000-0xe80001ff irq 10 at device 9.0 on pci0 ata2: at 0xe8000000 on atapci0 ata3: at 0xe8000000 on atapci0 So far, so good, but the single drive that is attached to the controller isn't recognized - atacontrol list turns up ATA channel 2: Master: no device present Slave: no device present ATA channel 3: Master: no device present Slave: no device present Alternatively, I tried an old 4.9 install I still had lying around. After applying patches from Matt Dillon (google for freebsd stable sil 3112) which he posted to one of the lists, 4.9 did recognize the controller and find the drive (much to my chagrin, though, 4.9 can't read the UFS2 filesystem on the drive, hence my dallying with -CURRENT again). Back to 5.1-R (yes, riding the ol' time machine) from CD, pciconf says: none0@pci0:9:0: class=0x018000 card=0x31121095 chip=0x31121095 rev=0x02 hdr=0x00 and clearly, the controller and drive isn't recognized. Rebuilding the kernel and world for an august 21st, 2003 snapshot gets me: ad4: 117246MB [238216/16/63] at ata2-master UDMA133 Hooray, etc. So that gives some data points: 5.1-R doesn't get is, 5.1 middle of august does, 5-CURRENT from today doesn't. What could the matter be? [ade] (not ade)