From owner-freebsd-hardware Mon Jun 10 2:27:48 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from prophecy.dyndns.org (phil2191.dialup.dandy.net [66.28.137.191]) by hub.freebsd.org (Postfix) with ESMTP id 8D20337B400 for ; Mon, 10 Jun 2002 02:27:43 -0700 (PDT) Received: (from apeiron@localhost) by prophecy.dyndns.org (8.12.3/8.11.6) id g59Nvoad051063; Sun, 9 Jun 2002 19:57:50 -0400 (EDT) (envelope-from chris@zanphar.net) X-Authentication-Warning: prophecy.dyndns.org: apeiron set sender to chris@zanphar.net using -f Subject: PPP and PCM conflict From: Christopher Nehren To: freebsd-hardware@freebsd.org Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.5 Date: 09 Jun 2002 19:57:50 -0400 Message-Id: <1023667070.50854.15.camel@prophecy.dyndns.org> Mime-Version: 1.0 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I've tried this on 4.5-RELEASE and 4.6-STABLE. Whenever I place pcm and ppp in the same kernel, the system hard freezes whenever I try to access my modem (U.S. Robotics 56K Performance Pro). I can't do anything except turn on the various locks (num-lock, scroll-lock, caps-lock). This happens when I try to use the ppp program, or the KPPP program, or something like setppp (available via FreshMeat IIRC). My sound card is an SiS 7018 on-board. Sound works (somewhat). I would include log entries but there aren't any. Thanks in advance, and best regards, Chris Nehren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jun 10 2:27:51 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from prophecy.dyndns.org (phil2191.dialup.dandy.net [66.28.137.191]) by hub.freebsd.org (Postfix) with ESMTP id 0D62E37B408 for ; Mon, 10 Jun 2002 02:27:46 -0700 (PDT) Received: (from apeiron@localhost) by prophecy.dyndns.org (8.12.3/8.11.6) id g59NmW7O050994; Sun, 9 Jun 2002 19:48:32 -0400 (EDT) (envelope-from apeiron@prophecy.dyndns.org) Subject: PPP and PCM conflict From: Christopher Nehren To: freebsd-hardware@freebsd.org Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.5 Date: 09 Jun 2002 19:48:32 -0400 Message-Id: <1023666512.50854.13.camel@prophecy.dyndns.org> Mime-Version: 1.0 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I've tried this on 4.5-RELEASE and 4.6-STABLE. Whenever I place pcm and ppp in the same kernel, the system hard freezes whenever I try to access my modem (U.S. Robotics 56K Performance Pro). I can't do anything except turn on the various locks (num-lock, scroll-lock, caps-lock). This happens when I try to use the ppp program, or the KPPP program, or something like setppp (available via FreshMeat IIRC). My sound card is an SiS 7018 on-board. Sound works (somewhat). I would include log entries but there aren't any. Thanks in advance, and best regards, Chris Nehren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jun 10 13:40:25 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.speakeasy.net (mail15.speakeasy.net [216.254.0.215]) by hub.freebsd.org (Postfix) with ESMTP id D8BFA37B400 for ; Mon, 10 Jun 2002 13:40:08 -0700 (PDT) Received: (qmail 1176 invoked from network); 10 Jun 2002 20:40:07 -0000 Received: from unknown (HELO asus.tddhome) ([64.81.20.229]) (envelope-sender ) by mail15.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 10 Jun 2002 20:40:07 -0000 Received: from asus.tddhome (localhost [127.0.0.1]) by asus.tddhome (8.12.3/8.12.3) with ESMTP id g5AKe6HE036386 for ; Mon, 10 Jun 2002 13:40:07 -0700 (PDT) (envelope-from tomdean@speakeasy.org) Received: (from tomdean@localhost) by asus.tddhome (8.12.3/8.12.3/Submit) id g5AKe6b6036383; Mon, 10 Jun 2002 13:40:06 -0700 (PDT) Date: Mon, 10 Jun 2002 13:40:06 -0700 (PDT) Message-Id: <200206102040.g5AKe6b6036383@asus.tddhome> X-Authentication-Warning: asus.tddhome: tomdean set sender to tomdean@speakeasy.org using -f From: "Thomas D. Dean" To: freebsd-hardware@FreeBSD.ORG Subject: nVidia nForce IGP-128 Chipset (420-D?) Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I have an ASUS A7N266-E motherboard with the nVidia nForce IGP-128 Chipset. I want to expand support for the chipset. This chipset is rumored to be similar to the AMD 758 chipset. But, it is not. See the full output of pciconf -lv at the bottom. The AMD 758 has a config register at 0x41. But, the lword at 0x40 looks like a device:vendor Id, identical to the lword at 0x2c. Or, is this bogus? # pciconf -r pci0:1:1 0:0xff 0x01b410de 0x00b00001 0x0c0500c1 0x00800000 0x00005001 0x00005501 0x00005101 0x00000000 0x00000000 0x00000000 0x00000000 0x0c111043 0x00000000 0x00000044 0x00000000 0x01030105 0x0c111043 0xc0020001 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 Anyone have the register definitions for this chip? tomdean # pciconf -lv chip0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x01a410de rev=0xb2 hdr=0x00 vendor = 'Nvidia Corporation' device = 'nForce AGP Controller' class = bridge subclass = HOST-PCI none0@pci0:0:1: class=0x050000 card=0x0c111043 chip=0x01ac10de rev=0xb2 hdr=0x00 vendor = 'Nvidia Corporation' device = 'nForce 220/420 Memory Controller' class = memory subclass = RAM none1@pci0:0:2: class=0x050000 card=0x0c111043 chip=0x01ad10de rev=0xb2 hdr=0x00 vendor = 'Nvidia Corporation' device = 'nForce 220/420 Memory Controller' class = memory subclass = RAM none2@pci0:0:3: class=0x050000 card=0x0c111043 chip=0x01ab10de rev=0xb2 hdr=0x00 vendor = 'Nvidia Corporation' device = 'nForce 420 Memory Controller (DDR)' class = memory subclass = RAM isab0@pci0:1:0: class=0x060100 card=0x0c111043 chip=0x01b210de rev=0xc3 hdr=0x00 vendor = 'Nvidia Corporation' device = 'nForce HUB Interface' class = bridge subclass = PCI-ISA none3@pci0:1:1: class=0x0c0500 card=0x0c111043 chip=0x01b410de rev=0xc1 hdr=0x00 vendor = 'Nvidia Corporation' device = 'nForce SMBus Controller' class = serial bus subclass = SMBus ohci0@pci0:2:0: class=0x0c0310 card=0x0c111043 chip=0x01c210de rev=0xc3 hdr=0x00 vendor = 'Nvidia Corporation' device = 'nForce OHCI USB Controller' class = serial bus subclass = USB ohci1@pci0:3:0: class=0x0c0310 card=0x0c111043 chip=0x01c210de rev=0xc3 hdr=0x00 vendor = 'Nvidia Corporation' device = 'nForce OHCI USB Controller' class = serial bus subclass = USB pcib1@pci0:8:0: class=0x060400 card=0x00000044 chip=0x01b810de rev=0xc2 hdr=0x01 vendor = 'Nvidia Corporation' device = 'nForce PCI Bridge' class = bridge subclass = PCI-PCI atapci0@pci0:9:0: class=0x01018a card=0x0c111043 chip=0x01bc10de rev=0xc3 hdr=0x00 vendor = 'Nvidia Corporation' device = 'nForce ATA Controller' class = mass storage subclass = ATA pcib2@pci0:30:0: class=0x060400 card=0x00000000 chip=0x01b710de rev=0xb2 hdr=0x01 vendor = 'Nvidia Corporation' device = 'nForce AGP Host to PCI Bridge' class = bridge subclass = PCI-PCI rl0@pci1:2:0: class=0x020000 card=0x805b1043 chip=0x813910ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RT8139 (A/B/C/8130) Fast Ethernet Adapter' class = network subclass = ethernet none4@pci2:0:0: class=0x030000 card=0x003a1002 chip=0x51591002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies' device = 'Radeon VE QY' class = display subclass = VGA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jun 10 21: 2:22 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (Postfix) with ESMTP id F01FA37B401 for ; Mon, 10 Jun 2002 21:02:18 -0700 (PDT) Received: from dsto-ms2.dsto.defence.gov.au (dsto-ms2.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au (8.10.1/8.10.1) with ESMTP id g5B40tS18806 for ; Tue, 11 Jun 2002 13:30:55 +0930 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by dsto-ms2.dsto.defence.gov.au (Content Technologies SMTPRS 4.1.5) with ESMTP id for ; Tue, 11 Jun 2002 13:32:11 +0930 Received: from salex001.dsto.defence.gov.au (salex001.dsto.defence.gov.au [131.185.2.9]) by muttley.dsto.defence.gov.au (8.9.3/8.9.3/8.9.3.LMD.990513) with ESMTP id NAA05593 for ; Tue, 11 Jun 2002 13:29:36 +0930 (CST) Received: from squirm.dsto.defence.gov.au ([131.185.75.211]) by salex001.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id MLWBFZ33; Tue, 11 Jun 2002 13:29:50 +0930 Date: Tue, 11 Jun 2002 13:20:28 +0930 (CST) From: "Wilkinson,Alex" X-X-Sender: wilkinsa@squirm.dsto.defence.gov.au Reply-To: Alex.Wilkinson@dsto.defence.gov.au To: freebsd-hardware@freebsd.org Subject: Matrox Millennium && Alpha pws 500au Message-ID: <20020611131929.F387-100000@squirm.dsto.defence.gov.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi there, I have finally bought my Matrox Millennium G450 (PCI) Dual head Video card. I physically put the card in the Alpha 500au pws last night. I then proceeded to boot the OS. The SRM made 1 longish beep followed by 3 short beeps...AND a black screen with no SRM. Is there something else I need to do ? Thanks - aW To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jun 11 1:47:12 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from clientmail.ehsrealtime.com (eris.ehsrealtime.com [213.52.146.130]) by hub.freebsd.org (Postfix) with ESMTP id 1D70237B408 for ; Tue, 11 Jun 2002 01:47:07 -0700 (PDT) Received: from pan.ehsrealtime.com ([213.52.146.196]) by clientmail.ehsrealtime.com with esmtp (Exim 3.33 #2) id 17HhIq-0009sW-01 for freebsd-hardware@freebsd.org; Tue, 11 Jun 2002 09:47:00 +0100 Received: from byrons (helo=localhost) by pan.ehsrealtime.com with local-esmtp (Exim 3.35 #1) id 17HhIN-0000GF-00 for freebsd-hardware@freebsd.org; Tue, 11 Jun 2002 09:46:31 +0100 Date: Tue, 11 Jun 2002 09:46:31 +0100 (BST) From: Byron Schlemmer To: freebsd-hardware@freebsd.org Subject: AMI Megaraid + Reboot problems Message-ID: <20020611094541.H1005-100000@pan.ehsbrann.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi folks I have sent the following to freebsd-questions but maybe this is a better place to ask? I have a AMI MegaRaid controller : amr0: mem 0xffff0000-0xffffffff irq 11 at device 11.0 on pci0 amr0: Firmware E161, BIOS 3.13, 32MB RAM running on : $ uname -a FreeBSD machine 4.6-RC FreeBSD 4.6-RC #0: Tue May 28 15:35:17 BST 2002 root@machine:/usr/src/sys/compile/EHSB i386 Now the problem is whenever I reboot, or shutdown, the box seems to shutdown correctly, then I get a message saying : amr0 flushing cache ... done Rebooting... And the machine seems to hang there, never actually rebooting? Has anyone else experienced this? Any solutions to actually get the box to reboot? -byron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jun 11 7:53:13 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6]) by hub.freebsd.org (Postfix) with ESMTP id F32D837B406 for ; Tue, 11 Jun 2002 07:53:02 -0700 (PDT) Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12]) by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA08424 for ; Tue, 11 Jun 2002 10:53:00 -0400 (EDT) Received: from sol.eng.fore.com (sol.pit.comms.marconi.com [169.144.155.73]) by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA09286 for ; Tue, 11 Jun 2002 10:52:55 -0400 (EDT) Received: from gravel.fore.com (gravel [169.144.54.125]) by sol.eng.fore.com (8.8.8/8.8.8) with ESMTP id KAA27109 for ; Tue, 11 Jun 2002 10:52:54 -0400 (EDT) Received: from localhost (jritorto@localhost) by gravel.fore.com (8.10.2+Sun/8.10.2) with ESMTP id g5BEqsH15278 for ; Tue, 11 Jun 2002 10:52:54 -0400 (EDT) X-Authentication-Warning: gravel.fore.com: jritorto owned process doing -bs Date: Tue, 11 Jun 2002 10:52:53 -0400 (EDT) From: Jacob Ritorto X-X-Sender: jritorto@gravel To: freebsd-hardware@freebsd.org Subject: serial trouble on dell cpi 366 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, I'm frequently losing bits on my laptop's serial port using FreeBSD 4.5-RELEASE and 5.0-CURRENT. The kernel frequently reports one more silo overflow (xx total) on the serial port. Both installations are generic kernels, though I did try cutting out superfluous devices in 5.0, but to no effect. 5.0 Seems to drop many more bits than 4.5, and 5.0 seems not to care how fast the transfer happens -- it loses data even at 2400 bps, while the 4.5-RELEASE usually only loses data at rates above 38400. Do people already know about this? Is there a bug filed yet? Any resolution / workaround? I use the machine (and camediaplay or gphoto -- same behaviour with both programs) to grab digital photos from my Olympus. The scheme worked fine on previous FreeBSD versions with my now defunct Intel machine.. Please advise as it seems to me that the kernel is having trouble getting around to servicing the serial port's requests, which I'm assuming denotes the kernel's failure to fully grok the uart or something like that.. thanks. -jake To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jun 11 23:16: 4 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 2942937B40A for ; Tue, 11 Jun 2002 23:15:58 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id QAA06746; Wed, 12 Jun 2002 16:15:48 +1000 Date: Wed, 12 Jun 2002 16:20:10 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Jacob Ritorto Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: serial trouble on dell cpi 366 In-Reply-To: Message-ID: <20020612155759.W596-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, 11 Jun 2002, Jacob Ritorto wrote: > I'm frequently losing bits on my laptop's > serial port using FreeBSD 4.5-RELEASE and > 5.0-CURRENT. The kernel frequently reports one > more silo overflow (xx total) on the serial port. > Both installations are generic kernels, though I > did try cutting out superfluous devices in 5.0, > but to no effect. > 5.0 Seems to drop many more bits than 4.5, > and 5.0 seems not to care how fast the transfer > happens -- it loses data even at 2400 bps, while > the 4.5-RELEASE usually only loses data at rates > above 38400. > Do people already know about this? Is > there a bug filed yet? Any resolution / > workaround? I use the machine (and camediaplay or I think this is unknown, except that interrupt latency problems are worse in -current. > gphoto -- same behaviour with both programs) to > grab digital photos from my Olympus. The scheme > worked fine on previous FreeBSD versions with my > now defunct Intel machine.. It's interesting that it used to work. The only significant change in the driver between 4.4 and 4.5 was to reduce the input fifo (silo) trigger level. In theory, this should reduce silo overruns by up to a factor of 4, but since there should be none without this change, this change should make no difference except to reduce efficiency. Silo overruns at low speeds like 38400 point to deeper problems. Try running 4.4 to see if this is a software problem. > Please advise as it seems to me that the > kernel is having trouble getting around to > servicing the serial port's requests, which I'm > assuming denotes the kernel's failure to fully > grok the uart or something like that.. Silo overflows are more often caused by a software bug, or other hardware using so many bus cycles that the serial driver can't access its hardware in time. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jun 12 1:43:35 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from prometheus.vh.laserfence.net (prometheus.laserfence.net [196.44.73.116]) by hub.freebsd.org (Postfix) with ESMTP id 917F237B40D for ; Wed, 12 Jun 2002 01:43:27 -0700 (PDT) Received: from phoenix.vh.laserfence.net ([192.168.0.10]) by prometheus.vh.laserfence.net with esmtp (Exim 3.34 #1) id 17I3iu-0003It-00 for freebsd-hardware@freebsd.org; Wed, 12 Jun 2002 10:43:24 +0200 Date: Wed, 12 Jun 2002 10:43:24 +0200 (SAST) From: Willie Viljoen X-X-Sender: will@phoenix.vh.laserfence.net To: freebsd-hardware@freebsd.org Subject: Per-drive ATA configuration? (fwd) Message-ID: <20020612104259.H252-100000@phoenix.vh.laserfence.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, I've recently set my system up in a rather perculiar way, the mainboard (an Asus P3V133) has an onboard ATA-66 controller of some VIA flavour. I have a CMD-469 ATA-100 controller lying around, which was needed to run my 40GB drive on an older motherboard. I can boot directly off the 649, but the problem with this is that ATA_STATIC_ID option turned on, then lists the drive as ad4, which means at boot time, the system keeps probing for ad0, and my bootup is basically stalled for about 60 seconds while the ata driver tries to get around the fact that I have no ad0. For this reason, I've reenabled the ATA-66 controller, and connected an old drive (Conner Peripherals 425MB) to it. The conner now holds root partitions for all my OSs, and the rest is installed on the 40GB, controlled by the ATA-100. This is also a slow boot, due to the lack of speed on the conner's part, but is significantly faster than waiting for drivers looking for a drive which is just not there. I could just run the 40GB off the ATA-66, but I'm greedy in terms of speed, and don't see why I should run at ATA-66 if my drive is ATA-100 capable. The problem now is that under very heavy load, like installing a new world or kernel etc into the root partition, the little conner freeses up. I've tried with different drives, all give the same problem (A 210MB Seagate, a 1.7GB Seagate, and an 800MB Western Digital) The machine goes into a hard lock and simply refuses to budge after the lockup, no kernel panic output or even log messages to go by. Infact, it does not even respond to ctrl+alt+delete, the soft power off sequence, or even the ATX power switch on my case. The only way to get it out of this lock is switching off the wall socket and switching it back on again. After some testing, I noticed that the conner is running at WDMA2. I found this strange, since the conner is a very old drive, and I doubt it was built for DMA, even if it was, I doubt wether they had the specs completely right back in 1994. Upon disabling ATA DMA completely, I found that the conner loses no speed at all, and the problem seems to be gone. From this it is rather evident that these old drives should not be making an attempt at DMA. The problem now is that ATA is disabled accross my entire system, meaning I have to read the 40GB at PIO4, which, obviously, is less than desirable. This has me to the point of simply wanting to remove the ATA-100 controller and using the ATA-66, but I'm usually not keen on just giving up. I checked the ata(4) manpage, and they mentioned a sysctl called hw.atamodes. This sysctl (aparently) allows for individual tuning of ATA parameters. However, to my great dismay, I discovered that this sysctl does not exist on my system (FreeBSD 4.6-RC) I've tried having sysctl display all its opaque variables, and this sysctl still simply isn't there. I tried setting it from loader.conf asif it were a kernel tunable, again, to no avail. Has this controle been removed from the ata driver? Or has it simply not yet been implimented... Either of those cases being true, is there any way anyone can think of in which I could individually tune my ATA devices, short of downgrading or going to 5.0-CURRENT? Regards, Will -- Willie Viljoen Highveld Computing Solutions 214 Paul Kruger Avenue Universitas Bloemfontein 9321 South Africa +27 51 522 15 60, a/h +27 51 522 44 36 +27 82 404 03 27 will@highveldcs.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jun 12 11:34:52 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from skink.ru.ac.za (skink.ru.ac.za [146.231.128.4]) by hub.freebsd.org (Postfix) with ESMTP id 7DB5237B400 for ; Wed, 12 Jun 2002 11:34:45 -0700 (PDT) Received: from bashir.dsl.ru.ac.za ([146.231.113.19] helo=rucus.ru.ac.za) by skink.ru.ac.za with esmtp (Exim 3.36 #1) id 17I5P1-0001dM-00; Wed, 12 Jun 2002 12:30:59 +0200 Message-ID: <3D0722E1.4090601@rucus.ru.ac.za> Date: Wed, 12 Jun 2002 12:30:57 +0200 From: =?ISO-8859-1?Q?David_Sieb=F6rger?= User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.0rc1) Gecko/20020506 X-Accept-Language: en-za, en-gb, en-us, en MIME-Version: 1.0 To: will@highveldcs.com Cc: hardware@freebsd.org Subject: Re: Per-drive ATA configuration? (fwd) References: <20020612104259.H252-100000@phoenix.vh.laserfence.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-added-header: added by skink.ru.ac.za Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Willie Viljoen wrote: > I've recently set my system up in a rather perculiar way, the mainboard= > (an Asus P3V133) has an onboard ATA-66 controller of some VIA flavour. = I > have a CMD-469 ATA-100 controller lying around, which was needed to run= my > 40GB drive on an older motherboard. [snip] > I checked the ata(4) manpage, and they mentioned a sysctl called > hw.atamodes. This sysctl (aparently) allows for individual tuning of AT= A > parameters. However, to my great dismay, I discovered that this sysctl > does not exist on my system (FreeBSD 4.6-RC) It was removed when the new ATA RAID code was MFC'ed during 4.5-STABLE. > I've tried having sysctl display all its opaque variables, and this sys= ctl > still simply isn't there. I tried setting it from loader.conf asif it w= ere > a kernel tunable, again, to no avail. >=20 > Has this controle been removed from the ata driver? Or has it simply no= t > yet been implimented... On a recent system, you'll need to use atacontrol(8). I guess you'll=20 need to do something like 'atacontrol mode 0 pio4 pio4'. Though, personally, I would want to get rid of the old drive and I'd=20 run the newer drive on the UDMA66 controller. I doubt the performance=20 difference between UDMA66 and UDMA100 is significant, particularly=20 with a single drive on the channel. --=20 David Sieb=F6rger drs@rucus.ru.ac.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jun 12 13:31:38 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from prometheus.vh.laserfence.net (prometheus.laserfence.net [196.44.73.116]) by hub.freebsd.org (Postfix) with ESMTP id D25EC37B40C for ; Wed, 12 Jun 2002 13:30:28 -0700 (PDT) Received: from phoenix.vh.laserfence.net ([192.168.0.10]) by prometheus.vh.laserfence.net with esmtp (Exim 3.34 #1) id 17IEkw-0003Wq-00; Wed, 12 Jun 2002 22:30:14 +0200 Date: Wed, 12 Jun 2002 22:30:14 +0200 (SAST) From: Willie Viljoen X-X-Sender: will@phoenix.vh.laserfence.net To: =?ISO-8859-1?Q?David_Sieb=F6rger?= Cc: hardware@freebsd.org Subject: Re: Per-drive ATA configuration? (fwd) In-Reply-To: <3D0722E1.4090601@rucus.ru.ac.za> Message-ID: <20020612222735.Q252-100000@phoenix.vh.laserfence.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org David, I've tested it abit, in FreeBSD the performance hit from the ATA66 isn't that much, the main problem is that this one, being my home machine, is a multiboot system, because of M$'s lack of lateral thought (I suppose) Windows just simply breaks in half with the ATA66, may even be their driver for my VIA just doesn't cut it. Even with the VIA service pack (from VIA themselves) the VIA just isn't up to scratch. If it weren't for the occasional weekend need for some serious gaming, the old drive would be out and collecting dust in storage. Thanks for the advise though, I'll give atacontrol a try. Will On Wed, 12 Jun 2002, [ISO-8859-1] David Sieb=F6rger wrote: > Willie Viljoen wrote: > > I've recently set my system up in a rather perculiar way, the mainboard > > (an Asus P3V133) has an onboard ATA-66 controller of some VIA flavour. = I > > have a CMD-469 ATA-100 controller lying around, which was needed to run= my > > 40GB drive on an older motherboard. > [snip] > > I checked the ata(4) manpage, and they mentioned a sysctl called > > hw.atamodes. This sysctl (aparently) allows for individual tuning of AT= A > > parameters. However, to my great dismay, I discovered that this sysctl > > does not exist on my system (FreeBSD 4.6-RC) > > It was removed when the new ATA RAID code was MFC'ed during 4.5-STABLE. > > > I've tried having sysctl display all its opaque variables, and this sys= ctl > > still simply isn't there. I tried setting it from loader.conf asif it w= ere > > a kernel tunable, again, to no avail. > > > > Has this controle been removed from the ata driver? Or has it simply no= t > > yet been implimented... > > On a recent system, you'll need to use atacontrol(8). I guess you'll > need to do something like 'atacontrol mode 0 pio4 pio4'. > > Though, personally, I would want to get rid of the old drive and I'd > run the newer drive on the UDMA66 controller. I doubt the performance > difference between UDMA66 and UDMA100 is significant, particularly > with a single drive on the channel. > > > --=20 Willie Viljoen Highveld Computing Solutions 214 Paul Kruger Avenue Universitas Bloemfontein 9321 South Africa +27 51 522 15 60, a/h +27 51 522 44 36 +27 82 404 03 27 will@highveldcs.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jun 13 0:25: 2 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from smtp.noos.fr (lafontaine.noos.net [212.198.2.72]) by hub.freebsd.org (Postfix) with ESMTP id C990437B43B for ; Thu, 13 Jun 2002 00:24:56 -0700 (PDT) Received: (qmail 45421845 invoked by uid 0); 13 Jun 2002 07:24:55 -0000 Received: from unknown (HELO gits.gits.dyndns.org) ([212.198.230.194]) (envelope-sender ) by 212.198.2.72 (qmail-ldap-1.03) with SMTP for ; 13 Jun 2002 07:24:55 -0000 Received: from gits.gits.dyndns.org (hmd780d501ahdaco@localhost [127.0.0.1]) by gits.gits.dyndns.org (8.12.3/8.12.3) with ESMTP id g5D7Ota6039668; Thu, 13 Jun 2002 09:24:55 +0200 (CEST) (envelope-from root@gits.dyndns.org) Received: (from root@localhost) by gits.gits.dyndns.org (8.12.3/8.12.3/Submit) id g5D7OsV2039667; Thu, 13 Jun 2002 09:24:54 +0200 (CEST) (envelope-from root) Date: Thu, 13 Jun 2002 09:24:54 +0200 From: Cyrille Lefevre To: Willie Viljoen Cc: freebsd-hardware@freebsd.org Subject: Re: Per-drive ATA configuration? (fwd) Message-ID: <20020613072454.GB39353@gits.dyndns.org> Mail-Followup-To: Cyrille Lefevre , Willie Viljoen , freebsd-hardware@freebsd.org References: <20020612104259.H252-100000@phoenix.vh.laserfence.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020612104259.H252-100000@phoenix.vh.laserfence.net> User-Agent: Mutt/1.3.99i Organization: ACME X-Face: V|+c;4!|B?E%BE^{E6);aI.[< List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, Jun 12, 2002 at 10:43:24AM +0200, Willie Viljoen wrote: [snip] > I checked the ata(4) manpage, and they mentioned a sysctl called > hw.atamodes. This sysctl (aparently) allows for individual tuning of ATA > parameters. However, to my great dismay, I discovered that this sysctl > does not exist on my system (FreeBSD 4.6-RC) PR sent, see the following URL for details : http://www.FreeBSD.org/cgi/query-pr.cgi?pr=misc/39202 Cyrille. -- Cyrille Lefevre mailto:cyrille.lefevre@laposte.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Jun 15 4:15: 4 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id 1094A37B414 for ; Sat, 15 Jun 2002 04:14:55 -0700 (PDT) Received: from v-ger.we.lc.ehu.es (lxpx149.lx.ehu.es [158.227.26.49]) by polaris.we.lc.ehu.es (8.11.6/8.11.6) with ESMTP id g5FBEpn10713 for ; Sat, 15 Jun 2002 13:14:52 +0200 (MET DST) Received: from v-ger.we.lc.ehu.es (localhost [127.0.0.1]) by v-ger.we.lc.ehu.es (8.12.3/8.12.3) with ESMTP id g5FBEsWx000372 for ; Sat, 15 Jun 2002 13:14:54 +0200 (CEST) (envelope-from jose@v-ger.we.lc.ehu.es) Received: (from jose@localhost) by v-ger.we.lc.ehu.es (8.12.3/8.12.3/Submit) id g5FBEqm4000371 for hardware@FreeBSD.org; Sat, 15 Jun 2002 13:14:52 +0200 (CEST) Date: Sat, 15 Jun 2002 13:14:52 +0200 From: "Jose M. Alcaide" To: hardware@FreeBSD.org Subject: ATAPI CDROM does not work in DMA mode, but it works with NetBSD Message-ID: <20020615131452.A267@v-ger.we.lc.ehu.es> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i X-Operating-System: FreeBSD 4.6-RELEASE Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org [I am sorry for the long message.] The machine is a Dell Inspiron 3700. FreeBSD was *never* able to put its ATAPI CD-ROM in DMA mode, including 4.6-RELEASE and 5.0-CURRENT. However, the CD-ROM does work fine with DMA using NetBSD 1.5.2. Here are the most relevant boot messages: -------------------------------------------------------------------------- atapci0: port 0x860-0x86f at device 7.1 on pci0 [...] ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0x0868 ata1: mask=03 ostat0=50 ostat2=00 ata1-master: ATAPI 14 eb ata1-slave: ATAPI 7f 7f ata1: mask=03 stat0=00 stat1=00 ata1: devices=04 ata1: at 0x170 irq 15 on atapci0 [...] ata1-master: piomode=4 dmamode=2 udmamode=-1 dmaflag=1 ata1-master: success setting PIO4 on generic chip acd0: CDROM drive at ata1 as master -------------------------------------------------------------------------- Here is the atacontrol output: -------------------------------------------------------------------------- # atacontrol info 1 Master: acd0 ATA/ATAPI rev 0 Slave: no device present # atacontrol cap 1 0 ATA channel 1, Master, device acd0: ATA/ATAPI revision 0 device model TOSHIBA CD-ROM XM-1902B firmware revision 1A15 cylinders 0 heads 0 sectors/track 0 lba supported lba48 not supported dma supported overlap not supported Feature Support Enable Value Vendor write cache no no read ahead no no dma queued no no 0/00 SMART no no microcode download no no security no no power management no no advanced power management no no 0/00 automatic acoustic management no no 0/00 0/00 -------------------------------------------------------------------------- And I am not a fool ;-) : -------------------------------------------------------------------------- # sysctl hw.ata hw.ata.ata_dma: 1 hw.ata.wc: 1 hw.ata.tags: 0 hw.ata.atapi_dma: 1 -------------------------------------------------------------------------- I can force WDMA2 mode using atacontrol, but then the data transfers with the CD-ROM do not work, and after some resets of the ATA channel it falls back to PIO4. Given that the CD-ROM works in DMA mode with NetBSD (and I tested it, achieving a noticeably higher data throughput and slower CPU consumption compared with those obtained using FreeBSD), I guess that this CD-ROM is not one of those ATAPI devices with broken DMA support. After reading /sys/dev/ata/atapi-all.c and ata-dma.c, I deduced that the following condition (in atapi_attach()) is true: atadev->param->drq_type == ATAPI_DRQT_INTR which prevents setting the CD-ROM in DMA mode. Of course, I removed that test and then the CD-ROM was put in WDMA2 mode, but it did not worked anyway. I wonder why NetBSD does not bother about drq_type being ATAPI_DRQT_INTR. Cheers, JMA -- ****** Jose M. Alcaide // jose@we.lc.ehu.es // jmas@FreeBSD.org ****** ** "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein ** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message