From owner-freebsd-current@FreeBSD.ORG Thu Jan 15 07:30:45 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 78A7616A4CE for ; Thu, 15 Jan 2004 07:30:45 -0800 (PST) Received: from mx2.mail.ru (mx2.mail.ru [194.67.23.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id EBCEE43D2F for ; Thu, 15 Jan 2004 07:30:11 -0800 (PST) (envelope-from rihad@mail.ru) Received: from [212.47.129.6] (port=33779 helo=mail.ru) by mx2.mail.ru with esmtp id 1Ah9Rf-0000R2-00; Thu, 15 Jan 2004 18:30:08 +0300 Message-ID: <4006B229.8000501@mail.ru> Date: Thu, 15 Jan 2004 19:30:49 +0400 From: rihad User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031107 Debian/1.5-3 X-Accept-Language: en MIME-Version: 1.0 To: jason References: <4004E482.7030200@mail.ru> <20040114042707.K47506@alpha.siliconlandmark.com> <40056FC8.7020501@mail.ru> <20040115020730.I47506@alpha.siliconlandmark.com> <40067F22.8040209@ec.rr.com> In-Reply-To: <40067F22.8040209@ec.rr.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam: Not detected cc: freebsd-current@freebsd.org Subject: Re: ATA activity LED X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jan 2004 15:30:45 -0000 jason wrote: > Andre Guibert de Bruet wrote: > >> On Wed, 14 Jan 2004, rihad wrote: >> >> >> >>> Andre Guibert de Bruet wrote: >>> >>> >>> >>>> On Wed, 14 Jan 2004, rihad wrote: >>>> >>>> >>>> >>>>> Why is the disk activity LED always on in 5-C? Various Linuxes and XP >>>>> don't exhibit this behaviour. >>>>> >>>> >>>> Care to share what type of ATA controller(s) your system has? >>>> >>> >>> $ dmesg | grep -e ^ata -e ^ad -e ^acd >>> atapci0: port 0xfc00-0xfc0f at device >>> 31.1 on pci0 >>> ata0: at 0x1f0 irq 14 on atapci0 >>> ata0: [MPSAFE] >>> ata1: at 0x170 irq 15 on atapci0 >>> ata1: [MPSAFE] >>> ad0: 29325MB [59582/16/63] at ata0-master UDMA100 >>> acd0: DVDROM at ata0-slave PIO4 >>> >> >> >> > There is a problem here. 1st there should not be a pio4 and dma100 on > the same cable, the pio4 mode is on only there because it is not > working, the spec say no mode mixing like this. Try the cdrom on the > second ide able, it should be atleast UDMA33, I have a liteon so I > know it should be at least this fast. You may have the drive jumpers > set to 2 masters or something? Any way having the drives on there own > cables is much faster anyway. > > I added "hw.ata.atapi_dma=1" to /boot/loader.conf and rebooted. Now I got UDMA33 on primary slave, too. Other than that, the output of dmesg is basically the same, but the devices were probed (?) twice: $ dmesg | grep -e ^ata -e ^ad -e ^acd atapci0: port 0xfc00-0xfc0f at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] ad0: 29325MB [59582/16/63] at ata0-master UDMA100 acd0: DVDROM at ata0-slave PIO4 atapci0: port 0xfc00-0xfc0f at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] ata0-slave: DMA limited to UDMA33, non-ATA66 cable or device ad0: 29325MB [59582/16/63] at ata0-master UDMA100 acd0: DVDROM at ata0-slave UDMA33 $ The LED is still on. The devices are jumpered properly in master-slave terms. I'll try to get a hold of another cable and see if splitting them across cables helps. Thanks a lot.