From owner-freebsd-hardware  Sun Sep 23 12:21: 0 2001
Delivered-To: freebsd-hardware@freebsd.org
Received: from globalrelay.com (h216-18-71-77.gtcust.grouptelecom.net [216.18.71.77])
	by hub.freebsd.org (Postfix) with ESMTP id 2326537B401
	for <freebsd-hardware@freebsd.org>; Sun, 23 Sep 2001 12:20:55 -0700 (PDT)
Received: from [24.76.149.87] (HELO cns)
  by globalrelay.com (CommuniGate Pro SMTP 3.4.7)
  with SMTP id 698199 for freebsd-hardware@freebsd.org; Sun, 23 Sep 2001 12:20:52 -0700
Message-ID: <007d01c14464$a8b38440$57954c18@cns>
From: "Eric Parusel" <lists@globalrelay.net>
To: <freebsd-hardware@freebsd.org>
Subject: SIS Onboard Ethernet problem.... (sis0)
Date: Sun, 23 Sep 2001 12:18:56 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hardware.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hardware>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hardware>
X-Loop: FreeBSD.org

Hi,

I've just purchased a computer, installed RELENG_4_4, and I'm having a
problem with getting my onboard ethernet to work.

I'd like to get my sis0 device working if possible :)
For some reason it's not detecting the mac address properly, any
ideas?

I've tried turning PNP OS to On and Off, no luck.


Here's my dmesg:

Copyright (c) 1992-2001 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.4-RELEASE #0: Sun Sep 23 00:15:22 PDT 2001
    root@dusty.creativens.com:/usr/obj/usr/src/sys/GENERIC
Timecounter "i8254"  frequency 1193182 Hz
CPU: AMD Athlon(tm) Processor (1394.07-MHz 686-class CPU)
  Origin = "AuthenticAMD"  Id = 0x644  Stepping = 4

Features=0x183f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA
,CMOV,PAT,PSE36,MMX,FXSR>
  AMD Features=0xc0440000<<b18>,AMIE,DSP,3DNow!>
real memory  = 268435456 (262144K bytes)
avail memory = 256774144 (250756K bytes)
Preloaded elf kernel "kernel" at 0xc0480000.
Pentium Pro MTRR support enabled
md0: Malloc disk
Using $PIR table, 8 entries at 0xc00f77f0
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <Host to PCI bridge> on motherboard
pci0: <PCI bus> on pcib0
pcib2: <PCI to PCI bridge (vendor=1039 device=0001)> at device 1.0 on
pci0
pci1: <PCI bus> on pcib2
pci1: <ATI Mach64-GB graphics accelerator> at 0.0
isab0: <SiS 85c503 PCI-ISA bridge> at device 2.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <SiS 5591 ATA33 controller> port 0xff00-0xff0f at device 2.5
on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
sis0: <SiS 900 10/100BaseTX> port 0xdc00-0xdcff mem
0xcffdd000-0xcffddfff irq 10 at device 3.0 on pci0
sis0: Ethernet address: 00:00:00:00:00:00
sis0: MII without any PHY!
device_probe_and_attach: sis0 attach returned 6
xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xd800-0xd87f mem
0xcfffff80-0xcfffffff irq 11 at device 13.0 on pci0
xl0: Ethernet address: 00:10:4b:6e:1b:73
miibus0: <MII bus> on xl0
xlphy0: <3Com internal media interface> on miibus0
xlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
pcib1: <SiS 5591 host to AGP bridge> on motherboard
pci2: <PCI bus> on pcib1
orm0: <Option ROMs> at iomem 0xc0000-0xc7fff,0xc8000-0xcffff on isa0
fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on
isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on
isa0
sc0: <System console> 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: <Parallel port> at port 0x378-0x37f irq 7 on isa0
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
plip0: <PLIP network interface> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
ad0: 19470MB <MAXTOR 4K020H1> [39560/16/63] at ata0-master UDMA33
acd0: CDROM <CD-ROM 32X/AKU> at ata1-master using PIO4
Mounting root from ufs:/dev/ad0s1a



Thanks,

Eric Parusel


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Mon Sep 24  7:12: 8 2001
Delivered-To: freebsd-hardware@freebsd.org
Received: from hal9000.net.au (cu764.adelaide.adsl.on.net [150.101.237.2])
	by hub.freebsd.org (Postfix) with ESMTP
	id 0697A37B40E; Mon, 24 Sep 2001 07:11:54 -0700 (PDT)
Received: (from bruins@localhost)
	by hal9000.net.au (8.11.1/8.11.1) id f8OEBnP05151;
	Mon, 24 Sep 2001 22:11:49 +0800 (WST)
	(envelope-from bruins)
Date: Mon, 24 Sep 2001 22:11:49 +0800
From: Mike Bruins <bruins@hal9000.net.au>
To: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org
Cc: Mike Bruins <bruins@hal9000.net.au>
Subject: health chip driver - vt82c686 - finishing off
Message-ID: <20010924221149.A4971@wall.hal9000.net.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hardware.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hardware>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hardware>
X-Loop: FreeBSD.org

Hello,

I have put together most of a device driver for the health
monitoring chip via technologies vt82c686 function 4 (PCI 3057:1106).
All the kernel loadable module, device probe/attach code,
temperature/fan/voltage conversion routines are there.
I can read the device registers for PCI Vendor/Device, chip enable,
class, subclass etc.

Basically what I am not able to do is read the values 
hardware offset registers.  The call to bus_alloc_resource
fails (returns null) and I can't work out why.

If anyone could please help with the following questions:

1. It looks like bus_alloc_resource() gets resources from it's parent
   device driver.
   Does the vt82c686 function 4, talk I2C to it's parent to get resources?  
   If so, do I need a device driver for this parent?
   Anyone know it's PCI vendor/device chip code?

2. Perhaps I am going down the wrong path.  Ideas, example code 
   references appreciated.  I have looked at many examples of 
   code, but can't work out what is relevent/required for the 686a/b,
   in terms of resources and how it communicates.

3.  The bit of my code that is actually failing is below.
  Like I said, I am pretty much sure the code to this point
  is correct and working as I can print any of the registers
  and they have sane values.

  I have tried every conbination I can think of for hwm_io_base_reg
  and the type of resource I am asking for.
  I have read the 686a.pdf file many times, tried all I can think of.
  According to the 686a.pdf the data size is 0x80 bytes.


        via->mem_rid = hwm_io_base_reg;
        via->res_mem = bus_alloc_resource(dev, SYS_RES_MEMORY, &(via->mem_rid),
                0ul, ~0ul, 0x80, RF_ACTIVE);
        if (!via->res_mem) {
                device_printf(dev, "could not map memory\n");
                goto bad;
        }
        via->memt = rman_get_bustag(via->res_mem);
        via->memh = rman_get_bushandle(via->res_mem);

  Ultimately I need the memt and memh values, so I can make calls like:

   val =  bus_space_read_1(via->memt, via->memh, regno);



My system:
Motherboard: Gigabyte 6vxd7 
CPU        : dual 866
OS         : 4.3-RELEASE free-bsd

I have altered chip_match() so no driver is loaded at boot time for 0x30571106.

chip0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x06911106 rev=0xc4 hdr=0x00
pcib1@pci0:1:0: class=0x060400 card=0x00000080 chip=0x85981106 rev=0x00 hdr=0x01
isab0@pci0:7:0: class=0x060100 card=0x06861106 chip=0x06861106 rev=0x22 hdr=0x00
uhci0@pci0:7:2: class=0x0c0300 card=0x12340925 chip=0x30381106 rev=0x10 hdr=0x00
uhci1@pci0:7:3: class=0x0c0300 card=0x12340925 chip=0x30381106 rev=0x10 hdr=0x00
none0@pci0:7:4: class=0x0c0500 card=0x00000000 chip=0x30571106 rev=0x30 hdr=0x00
sym0@pci0:9:0:  class=0x010000 card=0x00000000 chip=0x00201000 rev=0x01 hdr=0x00
sym1@pci0:9:1:  class=0x010000 card=0x00000000 chip=0x00201000 rev=0x01 hdr=0x00
rl0@pci0:10:0:  class=0x020000 card=0x0027a0a0 chip=0x813910ec rev=0x10 hdr=0x00
pcm0@pci0:13:0: class=0x040100 card=0x13711274 chip=0x13711274 rev=0x08 hdr=0x00
none1@pci0:14:0: class=0x040100 card=0x20601458 chip=0x13711274 rev=0x07 hdr=0x00
none2@pci1:0:0: class=0x030000 card=0x00000000 chip=0x002c10de rev=0x15 hdr=0x00



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Mon Sep 24  7:26:48 2001
Delivered-To: freebsd-hardware@freebsd.org
Received: from smtp.bmi.net (smtp.bmi.net [204.57.191.31])
	by hub.freebsd.org (Postfix) with ESMTP
	id B78C037B407; Mon, 24 Sep 2001 07:26:36 -0700 (PDT)
Received: from johncoop.MSHOME (drumheller-router.bmi.net [206.63.201.3] (may be forged))
	by smtp.bmi.net (Pro-8.9.3/Pro-8.9.3) with ESMTP id OAA26665;
	Mon, 24 Sep 2001 14:33:30 -0700
Date: Mon, 24 Sep 2001 07:26:18 -0700
From: John Merryweather Cooper <john_m_cooper@yahoo.com>
To: Mike Bruins <bruins@hal9000.net.au>
Cc: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org,
	Mike Bruins <bruins@hal9000.net.au>
Subject: Re: health chip driver - vt82c686 - finishing off
Message-ID: <20010924072618.C677@johncoop.MSHOME>
References: <20010924221149.A4971@wall.hal9000.net.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
In-Reply-To: <20010924221149.A4971@wall.hal9000.net.au>; from bruins@hal9000.net.au on Mon, Sep 24, 2001 at 07:11:49 -0700
X-Mailer: Balsa 1.2.0
Lines: 108
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hardware.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hardware>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hardware>
X-Loop: FreeBSD.org


On 2001.09.24 07:11 Mike Bruins wrote:
> Hello,
> 
> I have put together most of a device driver for the health
> monitoring chip via technologies vt82c686 function 4 (PCI 3057:1106).
> All the kernel loadable module, device probe/attach code,
> temperature/fan/voltage conversion routines are there.
> I can read the device registers for PCI Vendor/Device, chip enable,
> class, subclass etc.
> 
> Basically what I am not able to do is read the values 
> hardware offset registers.  The call to bus_alloc_resource
> fails (returns null) and I can't work out why.
> 
> If anyone could please help with the following questions:
> 
> 1. It looks like bus_alloc_resource() gets resources from it's parent
>    device driver.
>    Does the vt82c686 function 4, talk I2C to it's parent to get
> resources?  
>    If so, do I need a device driver for this parent?
>    Anyone know it's PCI vendor/device chip code?
> 
> 2. Perhaps I am going down the wrong path.  Ideas, example code 
>    references appreciated.  I have looked at many examples of 
>    code, but can't work out what is relevent/required for the 686a/b,
>    in terms of resources and how it communicates.
> 
> 3.  The bit of my code that is actually failing is below.
>   Like I said, I am pretty much sure the code to this point
>   is correct and working as I can print any of the registers
>   and they have sane values.
> 
>   I have tried every conbination I can think of for hwm_io_base_reg
>   and the type of resource I am asking for.
>   I have read the 686a.pdf file many times, tried all I can think of.
>   According to the 686a.pdf the data size is 0x80 bytes.
> 
> 
>         via->mem_rid = hwm_io_base_reg;
>         via->res_mem = bus_alloc_resource(dev, SYS_RES_MEMORY,
> &(via->mem_rid),
>                 0ul, ~0ul, 0x80, RF_ACTIVE);
>         if (!via->res_mem) {
>                 device_printf(dev, "could not map memory\n");
>                 goto bad;
>         }
>         via->memt = rman_get_bustag(via->res_mem);
>         via->memh = rman_get_bushandle(via->res_mem);
> 
>   Ultimately I need the memt and memh values, so I can make calls
> like:
> 
>    val =  bus_space_read_1(via->memt, via->memh, regno);
> 
> 
> 
> My system:
> Motherboard: Gigabyte 6vxd7 
> CPU        : dual 866
> OS         : 4.3-RELEASE free-bsd
> 
> I have altered chip_match() so no driver is loaded at boot time for
> 0x30571106.
> 
> chip0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x06911106
> rev=0xc4 hdr=0x00
> pcib1@pci0:1:0: class=0x060400 card=0x00000080 chip=0x85981106
> rev=0x00 hdr=0x01
> isab0@pci0:7:0: class=0x060100 card=0x06861106 chip=0x06861106
> rev=0x22 hdr=0x00
> uhci0@pci0:7:2: class=0x0c0300 card=0x12340925 chip=0x30381106
> rev=0x10 hdr=0x00
> uhci1@pci0:7:3: class=0x0c0300 card=0x12340925 chip=0x30381106
> rev=0x10 hdr=0x00
> none0@pci0:7:4: class=0x0c0500 card=0x00000000 chip=0x30571106
> rev=0x30 hdr=0x00
> sym0@pci0:9:0:  class=0x010000 card=0x00000000 chip=0x00201000
> rev=0x01 hdr=0x00
> sym1@pci0:9:1:  class=0x010000 card=0x00000000 chip=0x00201000
> rev=0x01 hdr=0x00
> rl0@pci0:10:0:  class=0x020000 card=0x0027a0a0 chip=0x813910ec
> rev=0x10 hdr=0x00
> pcm0@pci0:13:0: class=0x040100 card=0x13711274 chip=0x13711274
> rev=0x08 hdr=0x00
> none1@pci0:14:0: class=0x040100 card=0x20601458 chip=0x13711274
> rev=0x07 hdr=0x00
> none2@pci1:0:0: class=0x030000 card=0x00000000 chip=0x002c10de
> rev=0x15 hdr=0x00
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hardware" in the body of the message
> 

xmbmon works great (for temperature sorts of things) on my VIA 686B. 
You
might want to take a look at that code (it's in ports).

-- 
jmc

MacroHard -- the perfection of form over
             substance, marketing over
             performance, and greed over
             design . . .

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Mon Sep 24  9:36:47 2001
Delivered-To: freebsd-hardware@freebsd.org
Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166])
	by hub.freebsd.org (Postfix) with ESMTP
	id 0338D37B414; Mon, 24 Sep 2001 09:36:37 -0700 (PDT)
Received: from sun09pg2.wam.umd.edu (IDENT:root@sun09pg2.wam.umd.edu [128.8.73.19])
	by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id MAA21622;
	Mon, 24 Sep 2001 12:36:08 -0400 (EDT)
Received: from sun09pg2.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1])
	by sun09pg2.wam.umd.edu (8.9.3/8.9.3) with SMTP id MAA01265;
	Mon, 24 Sep 2001 12:36:08 -0400 (EDT)
Received: from localhost (culverk@localhost)
	by sun09pg2.wam.umd.edu (8.9.3/8.9.3) with ESMTP id MAA01260;
	Mon, 24 Sep 2001 12:36:06 -0400 (EDT)
X-Authentication-Warning: sun09pg2.wam.umd.edu: culverk owned process doing -bs
Date: Mon, 24 Sep 2001 12:36:06 -0400 (EDT)
From: Kenneth Wayne Culver <culverk@wam.umd.edu>
To: Mike Bruins <bruins@hal9000.net.au>
Cc: freebsd-questions@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG
Subject: Re: health chip driver - vt82c686 - finishing off
In-Reply-To: <20010924221149.A4971@wall.hal9000.net.au>
Message-ID: <Pine.GSO.4.21.0109241235001.1253-100000@sun09pg2.wam.umd.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hardware.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hardware>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hardware>
X-Loop: FreeBSD.org

This is the same problem I was having when I tried to write the driver for
freebsd, I never came up with a solution but mainly b/c I didn't have time
to mess with it anymore.

Ken

On Mon, 24 Sep 2001, Mike Bruins wrote:

> Hello,
> 
> I have put together most of a device driver for the health
> monitoring chip via technologies vt82c686 function 4 (PCI 3057:1106).
> All the kernel loadable module, device probe/attach code,
> temperature/fan/voltage conversion routines are there.
> I can read the device registers for PCI Vendor/Device, chip enable,
> class, subclass etc.
> 
> Basically what I am not able to do is read the values 
> hardware offset registers.  The call to bus_alloc_resource
> fails (returns null) and I can't work out why.
> 
> If anyone could please help with the following questions:
> 
> 1. It looks like bus_alloc_resource() gets resources from it's parent
>    device driver.
>    Does the vt82c686 function 4, talk I2C to it's parent to get resources?  
>    If so, do I need a device driver for this parent?
>    Anyone know it's PCI vendor/device chip code?
> 
> 2. Perhaps I am going down the wrong path.  Ideas, example code 
>    references appreciated.  I have looked at many examples of 
>    code, but can't work out what is relevent/required for the 686a/b,
>    in terms of resources and how it communicates.
> 
> 3.  The bit of my code that is actually failing is below.
>   Like I said, I am pretty much sure the code to this point
>   is correct and working as I can print any of the registers
>   and they have sane values.
> 
>   I have tried every conbination I can think of for hwm_io_base_reg
>   and the type of resource I am asking for.
>   I have read the 686a.pdf file many times, tried all I can think of.
>   According to the 686a.pdf the data size is 0x80 bytes.
> 
> 
>         via->mem_rid = hwm_io_base_reg;
>         via->res_mem = bus_alloc_resource(dev, SYS_RES_MEMORY, &(via->mem_rid),
>                 0ul, ~0ul, 0x80, RF_ACTIVE);
>         if (!via->res_mem) {
>                 device_printf(dev, "could not map memory\n");
>                 goto bad;
>         }
>         via->memt = rman_get_bustag(via->res_mem);
>         via->memh = rman_get_bushandle(via->res_mem);
> 
>   Ultimately I need the memt and memh values, so I can make calls like:
> 
>    val =  bus_space_read_1(via->memt, via->memh, regno);
> 
> 
> 
> My system:
> Motherboard: Gigabyte 6vxd7 
> CPU        : dual 866
> OS         : 4.3-RELEASE free-bsd
> 
> I have altered chip_match() so no driver is loaded at boot time for 0x30571106.
> 
> chip0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x06911106 rev=0xc4 hdr=0x00
> pcib1@pci0:1:0: class=0x060400 card=0x00000080 chip=0x85981106 rev=0x00 hdr=0x01
> isab0@pci0:7:0: class=0x060100 card=0x06861106 chip=0x06861106 rev=0x22 hdr=0x00
> uhci0@pci0:7:2: class=0x0c0300 card=0x12340925 chip=0x30381106 rev=0x10 hdr=0x00
> uhci1@pci0:7:3: class=0x0c0300 card=0x12340925 chip=0x30381106 rev=0x10 hdr=0x00
> none0@pci0:7:4: class=0x0c0500 card=0x00000000 chip=0x30571106 rev=0x30 hdr=0x00
> sym0@pci0:9:0:  class=0x010000 card=0x00000000 chip=0x00201000 rev=0x01 hdr=0x00
> sym1@pci0:9:1:  class=0x010000 card=0x00000000 chip=0x00201000 rev=0x01 hdr=0x00
> rl0@pci0:10:0:  class=0x020000 card=0x0027a0a0 chip=0x813910ec rev=0x10 hdr=0x00
> pcm0@pci0:13:0: class=0x040100 card=0x13711274 chip=0x13711274 rev=0x08 hdr=0x00
> none1@pci0:14:0: class=0x040100 card=0x20601458 chip=0x13711274 rev=0x07 hdr=0x00
> none2@pci1:0:0: class=0x030000 card=0x00000000 chip=0x002c10de rev=0x15 hdr=0x00
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-questions" in the body of the message
> 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Mon Sep 24  9:42:40 2001
Delivered-To: freebsd-hardware@freebsd.org
Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166])
	by hub.freebsd.org (Postfix) with ESMTP
	id C145237B40E; Mon, 24 Sep 2001 09:42:29 -0700 (PDT)
Received: from sun09pg2.wam.umd.edu (IDENT:root@sun09pg2.wam.umd.edu [128.8.73.19])
	by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id MAA23173;
	Mon, 24 Sep 2001 12:42:13 -0400 (EDT)
Received: from sun09pg2.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1])
	by sun09pg2.wam.umd.edu (8.9.3/8.9.3) with SMTP id MAA01329;
	Mon, 24 Sep 2001 12:42:13 -0400 (EDT)
Received: from localhost (culverk@localhost)
	by sun09pg2.wam.umd.edu (8.9.3/8.9.3) with ESMTP id MAA01325;
	Mon, 24 Sep 2001 12:42:13 -0400 (EDT)
X-Authentication-Warning: sun09pg2.wam.umd.edu: culverk owned process doing -bs
Date: Mon, 24 Sep 2001 12:42:13 -0400 (EDT)
From: Kenneth Wayne Culver <culverk@wam.umd.edu>
To: John Merryweather Cooper <john_m_cooper@yahoo.com>
Cc: Mike Bruins <bruins@hal9000.net.au>,
	freebsd-questions@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG
Subject: Re: health chip driver - vt82c686 - finishing off
In-Reply-To: <20010924072618.C677@johncoop.MSHOME>
Message-ID: <Pine.GSO.4.21.0109241241550.1253-100000@sun09pg2.wam.umd.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hardware.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hardware>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hardware>
X-Loop: FreeBSD.org

It seems that xmbmon is only in the ports if you're running -CURRENT...

Ken

On Mon, 24 Sep 2001, John Merryweather Cooper wrote:

> 
> On 2001.09.24 07:11 Mike Bruins wrote:
> > Hello,
> > 
> > I have put together most of a device driver for the health
> > monitoring chip via technologies vt82c686 function 4 (PCI 3057:1106).
> > All the kernel loadable module, device probe/attach code,
> > temperature/fan/voltage conversion routines are there.
> > I can read the device registers for PCI Vendor/Device, chip enable,
> > class, subclass etc.
> > 
> > Basically what I am not able to do is read the values 
> > hardware offset registers.  The call to bus_alloc_resource
> > fails (returns null) and I can't work out why.
> > 
> > If anyone could please help with the following questions:
> > 
> > 1. It looks like bus_alloc_resource() gets resources from it's parent
> >    device driver.
> >    Does the vt82c686 function 4, talk I2C to it's parent to get
> > resources?  
> >    If so, do I need a device driver for this parent?
> >    Anyone know it's PCI vendor/device chip code?
> > 
> > 2. Perhaps I am going down the wrong path.  Ideas, example code 
> >    references appreciated.  I have looked at many examples of 
> >    code, but can't work out what is relevent/required for the 686a/b,
> >    in terms of resources and how it communicates.
> > 
> > 3.  The bit of my code that is actually failing is below.
> >   Like I said, I am pretty much sure the code to this point
> >   is correct and working as I can print any of the registers
> >   and they have sane values.
> > 
> >   I have tried every conbination I can think of for hwm_io_base_reg
> >   and the type of resource I am asking for.
> >   I have read the 686a.pdf file many times, tried all I can think of.
> >   According to the 686a.pdf the data size is 0x80 bytes.
> > 
> > 
> >         via->mem_rid = hwm_io_base_reg;
> >         via->res_mem = bus_alloc_resource(dev, SYS_RES_MEMORY,
> > &(via->mem_rid),
> >                 0ul, ~0ul, 0x80, RF_ACTIVE);
> >         if (!via->res_mem) {
> >                 device_printf(dev, "could not map memory\n");
> >                 goto bad;
> >         }
> >         via->memt = rman_get_bustag(via->res_mem);
> >         via->memh = rman_get_bushandle(via->res_mem);
> > 
> >   Ultimately I need the memt and memh values, so I can make calls
> > like:
> > 
> >    val =  bus_space_read_1(via->memt, via->memh, regno);
> > 
> > 
> > 
> > My system:
> > Motherboard: Gigabyte 6vxd7 
> > CPU        : dual 866
> > OS         : 4.3-RELEASE free-bsd
> > 
> > I have altered chip_match() so no driver is loaded at boot time for
> > 0x30571106.
> > 
> > chip0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x06911106
> > rev=0xc4 hdr=0x00
> > pcib1@pci0:1:0: class=0x060400 card=0x00000080 chip=0x85981106
> > rev=0x00 hdr=0x01
> > isab0@pci0:7:0: class=0x060100 card=0x06861106 chip=0x06861106
> > rev=0x22 hdr=0x00
> > uhci0@pci0:7:2: class=0x0c0300 card=0x12340925 chip=0x30381106
> > rev=0x10 hdr=0x00
> > uhci1@pci0:7:3: class=0x0c0300 card=0x12340925 chip=0x30381106
> > rev=0x10 hdr=0x00
> > none0@pci0:7:4: class=0x0c0500 card=0x00000000 chip=0x30571106
> > rev=0x30 hdr=0x00
> > sym0@pci0:9:0:  class=0x010000 card=0x00000000 chip=0x00201000
> > rev=0x01 hdr=0x00
> > sym1@pci0:9:1:  class=0x010000 card=0x00000000 chip=0x00201000
> > rev=0x01 hdr=0x00
> > rl0@pci0:10:0:  class=0x020000 card=0x0027a0a0 chip=0x813910ec
> > rev=0x10 hdr=0x00
> > pcm0@pci0:13:0: class=0x040100 card=0x13711274 chip=0x13711274
> > rev=0x08 hdr=0x00
> > none1@pci0:14:0: class=0x040100 card=0x20601458 chip=0x13711274
> > rev=0x07 hdr=0x00
> > none2@pci1:0:0: class=0x030000 card=0x00000000 chip=0x002c10de
> > rev=0x15 hdr=0x00
> > 
> > 
> > 
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-hardware" in the body of the message
> > 
> 
> xmbmon works great (for temperature sorts of things) on my VIA 686B. 
> You
> might want to take a look at that code (it's in ports).
> 
> -- 
> jmc
> 
> MacroHard -- the perfection of form over
>              substance, marketing over
>              performance, and greed over
>              design . . .
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-questions" in the body of the message
> 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Mon Sep 24 10:54:33 2001
Delivered-To: freebsd-hardware@freebsd.org
Received: from mail.urx.com (2811.dynacom.net [206.107.213.4])
	by hub.freebsd.org (Postfix) with ESMTP
	id D98ED37B41F; Mon, 24 Sep 2001 10:54:20 -0700 (PDT)
Received: from owt.com [206.159.132.160] by mail.urx.com with ESMTP
  (SMTPD32-7.03) id A34233302EA; Mon, 24 Sep 2001 10:54:10 -0700
Message-ID: <3BAF733A.D243C6@owt.com>
Date: Mon, 24 Sep 2001 10:54:02 -0700
From: Kent Stewart <kstewart@owt.com>
X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Kenneth Wayne Culver <culverk@wam.umd.edu>
Cc: John Merryweather Cooper <john_m_cooper@yahoo.com>,
	Mike Bruins <bruins@hal9000.net.au>, freebsd-questions@FreeBSD.ORG,
	freebsd-hardware@FreeBSD.ORG
Subject: Re: health chip driver - vt82c686 - finishing off
References: <Pine.GSO.4.21.0109241241550.1253-100000@sun09pg2.wam.umd.edu>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hardware.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hardware>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hardware>
X-Loop: FreeBSD.org



Kenneth Wayne Culver wrote:
> 
> It seems that xmbmon is only in the ports if you're running -CURRENT...

You aren't using a current ports-all. I just installed it in 4.4-stable.

Kent

> 
> Ken
> 
> On Mon, 24 Sep 2001, John Merryweather Cooper wrote:
> 
> >
> > On 2001.09.24 07:11 Mike Bruins wrote:
> > > Hello,
> > >
> > > I have put together most of a device driver for the health
> > > monitoring chip via technologies vt82c686 function 4 (PCI 3057:1106).
> > > All the kernel loadable module, device probe/attach code,
> > > temperature/fan/voltage conversion routines are there.
> > > I can read the device registers for PCI Vendor/Device, chip enable,
> > > class, subclass etc.
> > >
> > > Basically what I am not able to do is read the values
> > > hardware offset registers.  The call to bus_alloc_resource
> > > fails (returns null) and I can't work out why.
> > >
> > > If anyone could please help with the following questions:
> > >
> > > 1. It looks like bus_alloc_resource() gets resources from it's parent
> > >    device driver.
> > >    Does the vt82c686 function 4, talk I2C to it's parent to get
> > > resources?
> > >    If so, do I need a device driver for this parent?
> > >    Anyone know it's PCI vendor/device chip code?
> > >
> > > 2. Perhaps I am going down the wrong path.  Ideas, example code
> > >    references appreciated.  I have looked at many examples of
> > >    code, but can't work out what is relevent/required for the 686a/b,
> > >    in terms of resources and how it communicates.
> > >
> > > 3.  The bit of my code that is actually failing is below.
> > >   Like I said, I am pretty much sure the code to this point
> > >   is correct and working as I can print any of the registers
> > >   and they have sane values.
> > >
> > >   I have tried every conbination I can think of for hwm_io_base_reg
> > >   and the type of resource I am asking for.
> > >   I have read the 686a.pdf file many times, tried all I can think of.
> > >   According to the 686a.pdf the data size is 0x80 bytes.
> > >
> > >
> > >         via->mem_rid = hwm_io_base_reg;
> > >         via->res_mem = bus_alloc_resource(dev, SYS_RES_MEMORY,
> > > &(via->mem_rid),
> > >                 0ul, ~0ul, 0x80, RF_ACTIVE);
> > >         if (!via->res_mem) {
> > >                 device_printf(dev, "could not map memory\n");
> > >                 goto bad;
> > >         }
> > >         via->memt = rman_get_bustag(via->res_mem);
> > >         via->memh = rman_get_bushandle(via->res_mem);
> > >
> > >   Ultimately I need the memt and memh values, so I can make calls
> > > like:
> > >
> > >    val =  bus_space_read_1(via->memt, via->memh, regno);
> > >
> > >
> > >
> > > My system:
> > > Motherboard: Gigabyte 6vxd7
> > > CPU        : dual 866
> > > OS         : 4.3-RELEASE free-bsd
> > >
> > > I have altered chip_match() so no driver is loaded at boot time for
> > > 0x30571106.
> > >
> > > chip0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x06911106
> > > rev=0xc4 hdr=0x00
> > > pcib1@pci0:1:0: class=0x060400 card=0x00000080 chip=0x85981106
> > > rev=0x00 hdr=0x01
> > > isab0@pci0:7:0: class=0x060100 card=0x06861106 chip=0x06861106
> > > rev=0x22 hdr=0x00
> > > uhci0@pci0:7:2: class=0x0c0300 card=0x12340925 chip=0x30381106
> > > rev=0x10 hdr=0x00
> > > uhci1@pci0:7:3: class=0x0c0300 card=0x12340925 chip=0x30381106
> > > rev=0x10 hdr=0x00
> > > none0@pci0:7:4: class=0x0c0500 card=0x00000000 chip=0x30571106
> > > rev=0x30 hdr=0x00
> > > sym0@pci0:9:0:  class=0x010000 card=0x00000000 chip=0x00201000
> > > rev=0x01 hdr=0x00
> > > sym1@pci0:9:1:  class=0x010000 card=0x00000000 chip=0x00201000
> > > rev=0x01 hdr=0x00
> > > rl0@pci0:10:0:  class=0x020000 card=0x0027a0a0 chip=0x813910ec
> > > rev=0x10 hdr=0x00
> > > pcm0@pci0:13:0: class=0x040100 card=0x13711274 chip=0x13711274
> > > rev=0x08 hdr=0x00
> > > none1@pci0:14:0: class=0x040100 card=0x20601458 chip=0x13711274
> > > rev=0x07 hdr=0x00
> > > none2@pci1:0:0: class=0x030000 card=0x00000000 chip=0x002c10de
> > > rev=0x15 hdr=0x00
> > >
> > >
> > >
> > > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > > with "unsubscribe freebsd-hardware" in the body of the message
> > >
> >
> > xmbmon works great (for temperature sorts of things) on my VIA 686B.
> > You
> > might want to take a look at that code (it's in ports).
> >
> > --
> > jmc
> >
> > MacroHard -- the perfection of form over
> >              substance, marketing over
> >              performance, and greed over
> >              design . . .
> >
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-questions" in the body of the message
> >
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-questions" in the body of the message

-- 
Kent Stewart
Richland, WA

It is hard to believe you are soaring with Eagles (las águilas) 
when you accept SPAM like a mouse (el ratón).

mailto:kbstew99@hotmail.com
http://kstewart.urx.com/kstewart/index.html
FreeBSD News http://daily.daemonnews.org/

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Mon Sep 24 11:34:30 2001
Delivered-To: freebsd-hardware@freebsd.org
Received: from mail.chronolabs.de (mail.chronolabs.de [62.154.158.51])
	by hub.freebsd.org (Postfix) with SMTP id 0EAA837B41B
	for <freebsd-hardware@freebsd.org>; Mon, 24 Sep 2001 11:34:07 -0700 (PDT)
Received: (qmail 9749 invoked by uid 0); 24 Sep 2001 19:57:56 -0000
Received: from andi.chronolabs.de (HELO chronolabs.de) (192.168.66.20)
  by mail.chronolabs.de with SMTP; 24 Sep 2001 19:57:56 -0000
Message-ID: <3BAF7CBB.37114A29@chronolabs.de>
Date: Mon, 24 Sep 2001 20:34:35 +0200
From: Andreas Krebs <hard_akrebs@chronolabs.de>
X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 5.0-CURRENT i386)
X-Accept-Language: en
MIME-Version: 1.0
To: msmith@freebsd.org, freebsd-hardware@freebsd.org
Subject: Problems with 3ware 6400
Content-Type: multipart/mixed;
 boundary="------------D2343404C13686638EC73301"
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hardware.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hardware>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hardware>
X-Loop: FreeBSD.org

This is a multi-part message in MIME format.
--------------D2343404C13686638EC73301
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi Mike,

i have a new 3ware 6400 running in a tyan thunderbolt board w/ freebsd
4.3 release. the 3ware controller has the newest firmware. But every
data transfer results in error messages. Doesn't matter if using raid 5,
1, 10 or stand alone drives. My guess is that the controller has either
problems with the board (coz of dual pci busses and stuff or it's simply
broken somehow. i wanna try the controller in a different machine w/ a
different mobo, but maybe you have seen this before and can give me some
hints. i have some error messages, the dmesg output and a page from the
3dmd utility.

tia

andy aka wintamute

error messages:

Sep 23 15:22:36  /kernel: twe0: FATAL STATUS BIT(S) 200000<MCERR>
Sep 23 15:22:36  /kernel: twe0: status  
57247380<CQEMPTY,UCREADY,RQEMPTY,AINTR,MCERR,>
Sep 23 15:22:36  /kernel: twe0:           current  max
Sep 23 15:22:36  /kernel: twe0: free      0229     0255
Sep 23 15:22:36  /kernel: twe0: ready     0000     0028
Sep 23 15:22:36  /kernel: twe0: busy      0026     0196
Sep 23 15:22:36  /kernel: twe0: complete  0000     0008
Sep 23 15:22:36  /kernel: twe0: bioq      0000     0001
Sep 23 15:22:36  /kernel: twe0: AEN queue head 7  tail 0
Sep 23 15:22:36  /kernel: twe0: controller reset in progress...
Sep 23 15:22:36  /kernel: twe0: controller reset done, 26 commands
restarted
Sep 23 15:22:36  /kernel: twe0: unexpected status bit(s) 200000<MCERR>
Sep 23 15:22:36  /kernel: twe0: FATAL STATUS BIT(S) 200000<MCERR>
Sep 23 15:22:36  /kernel: twe0: status  
572473e0<CQEMPTY,UCREADY,RQEMPTY,AINTR,MCERR,>
Sep 23 15:22:36  /kernel: twe0:           current  max
Sep 23 15:22:36  /kernel: twe0: free      0000     0255
Sep 23 15:22:36  /kernel: twe0: ready     0000     0028
Sep 23 15:22:36  /kernel: twe0: busy      0255     0255
Sep 23 15:22:36  /kernel: twe0: complete  0000     0008
Sep 23 15:22:36  /kernel: twe0: bioq      0051     0051
Sep 23 15:22:36  /kernel: twe0: AEN queue head 9  tail 0
Sep 23 15:22:36  /kernel: twe0: controller reset in progress...
Sep 23 15:22:36  /kernel: twe0: can't drain AEN queue
Sep 23 15:22:36  /kernel: twe0: reset 1 failed, trying again
Sep 23 15:22:36  /kernel: twe0: can't drain AEN queue
Sep 23 15:22:36  /kernel: twe0: reset 2 failed, trying again
Sep 23 15:22:36  /kernel: twe0: can't drain AEN queue
Sep 23 15:22:36  /kernel: twe0: can't reset controller, giving up
Sep 23 15:22:36  /kernel: twe0: unexpected status bit(s) 200000<MCERR>
Sep 23 15:22:36  /kernel: twe0: error polling for signalled AEN

dmesg:

Copyright (c) 1992-2001 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.3-RELEASE #0: Sat Apr 21 10:54:49 GMT 2001
    jkh@narf.osd.bsdi.com:/usr/src/sys/compile/GENERIC
Timecounter "i8254"  frequency 1193182 Hz
CPU: Pentium II/Pentium II Xeon/Celeron (400.91-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x665  Stepping = 5
 
Features=0x183fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR>
real memory  = 402522112 (393088K bytes)
config> di sn0
config> di lnc0
config> di ie0
config> di fe0
config> di ed0
config> di cs0
config> q
avail memory = 387289088 (378212K bytes)
Preloaded elf kernel "kernel" at 0xc044d000.
Preloaded userconfig_script "/boot/kernel.conf" at 0xc044d09c.
Pentium Pro MTRR support enabled
md0: Malloc disk
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <Intel 82443GX host to PCI bridge> on motherboard
pci0: <PCI bus> on pcib0
pcib2: <Intel 82443GX (440 GX) PCI-PCI (AGP) bridge> at device 1.0 on
pci0
pci1: <PCI bus> on pcib2
pci1: <ATI Mach64-GZ graphics accelerator> at 0.0 irq 10
isab0: <Intel 82371AB PCI to ISA bridge> at device 7.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel PIIX4 ATA33 controller> port 0xffa0-0xffaf at device 7.1
on pci0
ata0: at 0x1f0 irq 14 on atapci0
uhci0: <Intel 82371AB/EB (PIIX4) USB controller> port 0xef80-0xef9f irq
11 at device 7.2 on pci0
usb0: <Intel 82371AB/EB (PIIX4) USB controller> on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
chip1: <Intel 82371AB Power management controller> port 0x440-0x44f at
device 7.3 on pci0
ahc0: <Adaptec aic7896/97 Ultra2 SCSI adapter> port 0xe400-0xe4ff mem
0xffafe000-0xffafefff irq 10 at device 11.0 on pci0
aic7896/97: Wide Channel A, SCSI Id=7, 32/255 SCBs
ahc1: <Adaptec aic7896/97 Ultra2 SCSI adapter> port 0xe800-0xe8ff mem
0xffaff000-0xffafffff irq 10 at device 11.1 on pci0
aic7896/97: Wide Channel B, SCSI Id=7, 32/255 SCBs
pci0: <unknown card> (vendor=0x1274, dev=0x1371) at 12.0 irq 9
fxp0: <Intel Pro 10/100B/100+ Ethernet> port 0xee80-0xeebf mem
0xff900000-0xff9fffff,0xffafd000-0xffafdfff irq 11 at device 13.0 on
pci0
fxp0: Ethernet address 00:e0:81:10:38:6c
twe0: <3ware Storage Controller> port 0xefa0-0xefaf irq 10 at device
14.0 on pci0
twe0: 4 ports, Firmware FE6X 1.02.03.053, BIOS BE6X 1.07.01.015
pcib1: <Intel 82443GX host to AGP bridge> on motherboard
pci2: <PCI bus> on pcib1
fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on
isa0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on
isa0
sc0: <System console> 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: <Parallel port> at port 0x378-0x37f irq 7 on isa0
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
plip0: <PLIP network interface> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
acd0: CDROM <LTN382> at ata0-master using PIO4
Waiting 15 seconds for SCSI devices to settle
twed0: <JBOD, Normal> on twe0
twed0: 57259MB (117266688 sectors)
twed1: <JBOD, Normal> on twe0
twed1: 57259MB (117266688 sectors)
twed2: <JBOD, Normal> on twe0
twed2: 57259MB (117266688 sectors)
twed3: <JBOD, Normal> on twe0
twed3: 57259MB (117266688 sectors)
Mounting root from ufs:/dev/da0s2a
da0 at ahc1 bus 0 target 0 lun 0
da0: <IBM DDRS-39130 S97B> Fixed Direct Access SCSI-2 device
da0: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing
Enabled
da0: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C)
--------------D2343404C13686638EC73301
Content-Type: text/html; charset=us-ascii;
 name="technical.html"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="technical.html"

<html><head><title>3DM - mail.chronolabs.de - Technical - Error</title><STYLE TYPE="text/css">
TD.part
{
    COLOR: black;
    FONT-FAMILY: arial, helvetica;
    FONT-SIZE: 10pt;
    TEXT-ALIGN: left;
    TEXT-DECORATION: none
}
TH.part
{
    COLOR: navy;
    FONT-FAMILY: Arial, Helvetica;
    FONT-SIZE: 10pt;
    FONT-WEIGHT: bold;
    TEXT-ALIGN: left;
    TEXT-DECORATION: none
}
#navy
{
    COLOR: #000066
}
#nav1
{
    COLOR: #ffffff;
    FONT-FAMILY: Arial, Helvetica;
    FONT-SIZE: 10pt;
    FONT-WEIGHT: bold;
    TEXT-DECORATION: none
}
#nav2
{
    COLOR: #f9bb00;
    FONT-FAMILY: Arial, Helvetica;
    FONT-SIZE: 10pt;
    FONT-WEIGHT: bold;
    TEXT-DECORATION: none
}
#nav3
{
    COLOR: #dddddd;
    FONT-FAMILY: Arial, Helvetica;
    FONT-SIZE: 8pt;
    FONT-WEIGHT: normal;
    TEXT-DECORATION: none;
    VERTICAL-ALIGN: middle
}
TD.tech_control_header
{
    background-color: #000066;
    font-family: Arial, Helvetica;
    font-style: italic;
    font-weight: bold;
    font-size: large;
    color: white
}
TD.tech_drives_header
{
    background-color: #000066;
    font-family: Arial, Helvetica;
    font-style: italic;
    font-weight: bold;
    font-size: medium;
    color: white
}
TD.tech_drive_header
{
    background-color: #336699;
    font-family: Arial, Helvetica;
    font-weight: bold;
    font-size: x-small;
    color: white
}
TD.tech_unit_info
{
    font-family: Arial, Helvetica;
    font-weight: bold;
    font-size: small;
    color: white
}
TD.tech_unit_header
{
    background-color: #336699;
    font-family: Arial, Helvetica;
    font-weight: bold;
    font-size: x-small;
    color: white
}
TD.tech_control_field
{
    background-color: #ffffdd;
    width: 30%;
    font-family: Arial, Helvetica;
    font-weight: bold;
    font-size: x-small;
    color: black
}
TD.tech_control_value
{
    background-color: #ffffdd;
    width: 70%;
    font-family: Arial, Helvetica;
    font-size: x-small;
    color: black
}
TD.tech_unit_field
{
    background-color: #ffffdd;
    font-family: Arial, Helvetica;
    font-weight: bold;
    font-size: x-small;
    color: black
}
TD.tech_unit_value
{
    background-color: #ffffdd;
    font-family: Arial, Helvetica;
    font-size: x-small;
    color: black
}
</STYLE>
</head>
<body bgcolor="#FFFFFF" link="#FFFFFF" vlink="#FFFFFF" alink="#ff0000">
<table CELLSPACING=0 CELLPADDING=0 WIDTH="640" BGCOLOR="#FFFFFF" >
<tr><td><h1><font size=+2><A HREF="http://www.3ware.com"target="_blank"><IMG SRC="3ware.gif" BORDER=0 ALT="3ware 3DM"></A>&nbsp;</font></h1>
</td></tr></table>

<!-- NAVBAR 1 -->
<TABLE CELLSPACING="0" CELLPADDING="0" BORDER="0" WIDTH="100%" bgcolor="#000066">
<TR><TD>
  <TABLE border="0" width="780" cellspacing="0" cellpadding="3" bgcolor="#000066">
        <TR>
           <TD></TD>
           <TD><TABLE border="0" cellspacing="0" cellpadding="1" width="100%">
              <TR>
                 <TD bgcolor="#336699" width="100%"><TABLE width="100%" border="0" cellspacing="0" cellpadding="1">
                    <TR>
                       <TD align="center" bgcolor="#000066" width="100%" nowrap><A href="/index.html" id="nav1">&nbsp;Home&nbsp;</A></TD>
                    </TR>
                 </TABLE></TD>
              </TR>
           </TABLE></TD>
           <TD><TABLE border="0" cellspacing="0" cellpadding="1" width="100%">
              <TR>
                 <TD bgcolor="#336699" width="100%"><TABLE width="100%" border="0" cellspacing="0" cellpadding="1">
                    <TR>
                       <TD align="center" bgcolor="#336699" width="100%" nowrap><A href="/technical.html" id="nav1">&nbsp;Details&nbsp;</A></TD>
                    </TR>
                 </TABLE></TD>
              </TR>
           </TABLE></TD>
           <TD><TABLE border="0" cellspacing="0" cellpadding="1" width="100%">
              <TR>
                 <TD bgcolor="#336699" width="100%"><TABLE width="100%" border="0" cellspacing="0" cellpadding="1">
                    <TR>
                       <TD align="center" bgcolor="#000066" width="100%" nowrap><A href="/monitor.html" id="nav1">&nbsp;Monitor&nbsp;</A></TD>
                    </TR>
                 </TABLE></TD>
              </TR>
           </TABLE></TD>
           <TD><TABLE border="0" cellspacing="0" cellpadding="1" width="100%">
              <TR>
                 <TD bgcolor="#336699" width="100%"><TABLE width="100%" border="0" cellspacing="0" cellpadding="1">
                    <TR>
                       <TD align="center" bgcolor="#000066" width="100%" nowrap><A href="/alarms.html" id="nav1">&nbsp;Alarms&nbsp;</A></TD>
                    </TR>
                 </TABLE></TD>
              </TR>
           </TABLE></TD>
           <TD><TABLE border="0" cellspacing="0" cellpadding="1" width="100%">
              <TR>
                 <TD bgcolor="#336699" width="100%"><TABLE width="100%" border="0" cellspacing="0" cellpadding="1">
                    <TR>
                       <TD align="center" bgcolor="#000066" width="100%" nowrap><A href="/settings.html" id="nav1">&nbsp;Settings&nbsp;</A></TD>
                    </TR>
                 </TABLE></TD>
              </TR>
           </TABLE></TD>
           <TD><TABLE border="0" cellspacing="0" cellpadding="1" width="100%">
              <TR>
                 <TD bgcolor="#336699" width="100%"><TABLE width="100%" border="0" cellspacing="0" cellpadding="1">
                    <TR>
                       <TD align="center" bgcolor="#000066" width="100%" nowrap><A href="/config.html" id="nav1">&nbsp;Configure&nbsp;</A></TD>
                    </TR>
                 </TABLE></TD>
              </TR>
           </TABLE></TD>
           <TD><TABLE border="0" cellspacing="0" cellpadding="1" width="100%">
              <TR>
                 <TD bgcolor="#336699" width="100%"><TABLE width="100%" border="0" cellspacing="0" cellpadding="1">
                    <TR>
                       <TD align="center" bgcolor="#000066" width="100%" nowrap><A href="/help.html" id="nav1">&nbsp;&nbsp;Help&nbsp;&nbsp;</A></TD>
                    </TR>
                 </TABLE></TD>
              </TR>
           </TABLE></TD>
           <TD>.</TD>
        </TR>
     </TABLE>
</TD>
<TD NOWRAP BGCOLOR="#000066" WIDTH="100%">.</TD>
</TR>
</TABLE>
<!-- NAVBAR 2 -->
<TABLE CELLSPACING="0" CELLPADDING="0" BORDER="0" WIDTH="100%"bgcolor="#336699">
<TR><TD><TABLE HEIGHT="13" border="0" cellspacing="0" cellpadding="0"><TR><TD></TD><TD NOWRAP BGCOLOR="#336699" ALIGN="CENTER">&nbsp;</TD></TR></TABLE></TD><TD NOWRAP BGCOLOR="#336699" WIDTH="100%" ALIGN="RIGHT"><A HREF="/" TARGET="_top" id="nav3">mail.chronolabs.de&nbsp;&nbsp;</FONT></TD></TR></TABLE>
<!-- end NAVBAR 2 -->
<h1><b><font face="Arial,Helvetica" size=+2>Technical Detail View - <font color="#ff0000">Error</font></font></b></h1>
<p><font face=Arial,Helvetica>Hostname: mail.chronolabs.de</font><br><p><font face=Arial,Helvetica>1 controller detected</font></p>
<font face=Arial,Helvetica>FreeBSD</font><br><br>
<table class="tech_control" border="1" width="100%">
<tr><td class="tech_control_header">
Controller ID: 0
</td></tr>
<tr><td class="tech_control_info">
<table width="100%">
<tr><td class="tech_control_field">Monitor version:</td><td class="tech_control_value">ME6X 1.01.00.028</td></tr>
<tr><td class="tech_control_field">Firmware version:</td><td class="tech_control_value">FE6X 1.02.03.053</td></tr>
<tr><td class="tech_control_field">BIOS version:</td><td class="tech_control_value">BE6X 1.07.01.015</td></tr>
<tr><td class="tech_control_field">PCB version:</td><td class="tech_control_value">Rev2</td></tr>
<tr><td class="tech_control_field">Achip version:</td><td class="tech_control_value">V4.40</td></tr>
<tr><td class="tech_control_field">Pchip version:</td><td class="tech_control_value">V5.70</td></tr>
<tr><td class="tech_control_field">Model:</td><td class="tech_control_value">6400</td></tr>
<tr><td class="tech_control_field">Unit count:</td><td class="tech_control_value">1</td></tr>
</table>
</td></tr>
<tr><td>
<table><tr>
<td valign="top">
<table class="tech_unit">
<tr><td class="tech_unit_header">Unit 0</td></tr>
<tr><td class="tech_unit_info">
<table width="100%">
<tr><td class="tech_unit_field">Status:</td><td class="tech_unit_value"><font color="#ff0000">Degraded</font></td></tr>
<tr><td class="tech_unit_field">Capacity:</td><td class="tech_unit_value">111.83 GB (234529280 blocks)</td></tr>
<tr><td class="tech_unit_field">Write Cache:</td><td class="tech_unit_value">In Use</td></tr>
<tr><td class="tech_unit_field">Configuration:</td><td class="tech_unit_value">Striped with Parity 64K (RAID 5)</td></tr>
<tr><td class="tech_unit_field">Stripe size:</td><td class="tech_unit_value">64K (65536 bytes)</td></tr>
<tr><td class="tech_unit_field">Subunit count:</td><td class="tech_unit_value">3</td></tr>
</table>
</td></tr>
<tr><td>
<table><tr>
<td valign="top">
<table class="tech_unit">
<tr><td class="tech_unit_header">Subunit 0</td></tr>
<tr><td class="tech_unit_info">
<table width="100%">
<tr><td class="tech_unit_field">Logical drive status:</td><td class="tech_unit_value"><font color="#3333FF">OK</font></td></tr>
<tr><td class="tech_unit_field">Configuration:</td><td class="tech_unit_value">RAID Disk</td></tr>
<tr><td class="tech_unit_field">Physical drive number:</td><td class="tech_unit_value">0</td></tr>
<tr><td class="tech_unit_field">Logical drive number:</td><td class="tech_unit_value">0</td></tr>
</table>
</td></tr></table>
</td>
<td valign="top">
<table class="tech_unit">
<tr><td class="tech_unit_header">Subunit 1</td></tr>
<tr><td class="tech_unit_info">
<table width="100%">
<tr><td class="tech_unit_field">Logical drive status:</td><td class="tech_unit_value"><font color="#ff0000">Not in Service</font></td></tr>
<tr><td class="tech_unit_field">Configuration:</td><td class="tech_unit_value">RAID Disk</td></tr>
<tr><td class="tech_unit_field">Physical drive number:</td><td class="tech_unit_value">1</td></tr>
<tr><td class="tech_unit_field">Logical drive number:</td><td class="tech_unit_value">1</td></tr>
</table>
</td></tr></table>
</td>
<td valign="top">
<table class="tech_unit">
<tr><td class="tech_unit_header">Subunit 2</td></tr>
<tr><td class="tech_unit_info">
<table width="100%">
<tr><td class="tech_unit_field">Logical drive status:</td><td class="tech_unit_value"><font color="#3333FF">OK</font></td></tr>
<tr><td class="tech_unit_field">Configuration:</td><td class="tech_unit_value">RAID Disk</td></tr>
<tr><td class="tech_unit_field">Physical drive number:</td><td class="tech_unit_value">2</td></tr>
<tr><td class="tech_unit_field">Logical drive number:</td><td class="tech_unit_value">2</td></tr>
</table>
</td></tr></table>
</td>
</tr></table>
</td></tr>
</table>
</td>
</tr></table>
</td></tr>
<tr><td colspan=1>
<table width="100%">
<tr><td class="tech_drives_header">Drive count: 3</td></tr>
<tr>
<td><table><tr>
<td class="tech_drive_unit">
<table class="tech_drive">
<tr><td class="tech_drive_header">Port 0</td></tr>
<tr><td class="tech_drive_info">
<table>
<tr><td class="tech_unit_field">Status:</td><td class="tech_unit_value"><font color="#3333FF">OK</font></td></tr>
<tr><td class="tech_unit_field">Capacity:</td><td class="tech_unit_value">55.91 GB (117266688 blocks)</td></tr>
<tr><td class="tech_unit_field">Model:</td><td class="tech_unit_value">MAXTOR 4K060H3                          </td></tr>
<tr><td class="tech_unit_field">Serial number:</td><td class="tech_unit_value">673121028870        </td></tr>
<tr><td class="tech_unit_field">Unit number:</td><td class="tech_unit_value">0</td></tr>
</table></td></tr></table>
</td>
<td class="tech_drive_unit">
<table class="tech_drive">
<tr><td class="tech_drive_header">Port 1</td></tr>
<tr><td class="tech_drive_info">
<table>
<tr><td class="tech_unit_field">Status:</td><td class="tech_unit_value"><font color="#3333FF">OK</font></td></tr>
<tr><td class="tech_unit_field">Capacity:</td><td class="tech_unit_value">55.91 GB (117266688 blocks)</td></tr>
<tr><td class="tech_unit_field">Model:</td><td class="tech_unit_value">MAXTOR 4K060H3                          </td></tr>
<tr><td class="tech_unit_field">Serial number:</td><td class="tech_unit_value">673121028900        </td></tr>
<tr><td class="tech_unit_field">Unit number:</td><td class="tech_unit_value">0</td></tr>
</table></td></tr></table>
</td>
<td class="tech_drive_unit">
<table class="tech_drive">
<tr><td class="tech_drive_header">Port 2</td></tr>
<tr><td class="tech_drive_info">
<table>
<tr><td class="tech_unit_field">Status:</td><td class="tech_unit_value"><font color="#3333FF">OK</font></td></tr>
<tr><td class="tech_unit_field">Capacity:</td><td class="tech_unit_value">55.91 GB (117266688 blocks)</td></tr>
<tr><td class="tech_unit_field">Model:</td><td class="tech_unit_value">MAXTOR 4K060H3                          </td></tr>
<tr><td class="tech_unit_field">Serial number:</td><td class="tech_unit_value">673121028999        </td></tr>
<tr><td class="tech_unit_field">Unit number:</td><td class="tech_unit_value">0</td></tr>
</table></td></tr></table>
</td>
</tr></table></td></tr>
</table>
</td></tr>
</table>
<br><br>
<P><I><b>Note:</b>&nbsp;&nbsp;For better service when contacting 3ware customer support, please include a copy of this page.</I></P>
<hr><P><font face=Arial,Helvetica>Last Updated: 21:45:06 Thu 20-Sep-2001<br></P><P><I>3DM Version 1.10.00.011</I></P></body></html>
--------------D2343404C13686638EC73301--


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Mon Sep 24 16:37:32 2001
Delivered-To: freebsd-hardware@freebsd.org
Received: from hal9000.net.au (cu764.adelaide.adsl.on.net [150.101.237.2])
	by hub.freebsd.org (Postfix) with ESMTP
	id 692E637B425; Mon, 24 Sep 2001 16:37:22 -0700 (PDT)
Received: (from bruins@localhost)
	by hal9000.net.au (8.11.1/8.11.1) id f8ONbDo06846;
	Tue, 25 Sep 2001 07:37:13 +0800 (WST)
	(envelope-from bruins)
Date: Tue, 25 Sep 2001 07:37:13 +0800
From: Mike Bruins <bruins@hal9000.net.au>
To: John Merryweather Cooper <john_m_cooper@yahoo.com>
Cc: Mike Bruins <bruins@hal9000.net.au>,
	freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org
Subject: Re: health chip driver - vt82c686 - finishing off
Message-ID: <20010925073713.A6802@wall.hal9000.net.au>
References: <20010924221149.A4971@wall.hal9000.net.au> <20010924072618.C677@johncoop.MSHOME>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20010924072618.C677@johncoop.MSHOME>; from john_m_cooper@yahoo.com on Mon, Sep 24, 2001 at 07:26:18AM -0700
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hardware.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hardware>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hardware>
X-Loop: FreeBSD.org

On Mon, Sep 24, 2001 at 07:26:18AM -0700, John Merryweather Cooper wrote:
> 
> On 2001.09.24 07:11 Mike Bruins wrote:
> > Hello,
> > 
> > I have put together most of a device driver for the health
> > monitoring chip via technologies vt82c686 function 4 (PCI 3057:1106).
> > All the kernel loadable module, device probe/attach code,
> > temperature/fan/voltage conversion routines are there.
> > I can read the device registers for PCI Vendor/Device, chip enable,
> > class, subclass etc.
> > 
> > Basically what I am not able to do is read the values 
> > hardware offset registers.  The call to bus_alloc_resource
> > fails (returns null) and I can't work out why.
> > 
> > If anyone could please help with the following questions:
> > 
> > 1. It looks like bus_alloc_resource() gets resources from it's parent
> >    device driver.
> >    Does the vt82c686 function 4, talk I2C to it's parent to get
> > resources?  
> >    If so, do I need a device driver for this parent?
> >    Anyone know it's PCI vendor/device chip code?
> > 
> > 2. Perhaps I am going down the wrong path.  Ideas, example code 
> >    references appreciated.  I have looked at many examples of 
> >    code, but can't work out what is relevent/required for the 686a/b,
> >    in terms of resources and how it communicates.
> > 
> > 3.  The bit of my code that is actually failing is below.
> >   Like I said, I am pretty much sure the code to this point
> >   is correct and working as I can print any of the registers
> >   and they have sane values.
> > 
> >   I have tried every conbination I can think of for hwm_io_base_reg
> >   and the type of resource I am asking for.
> >   I have read the 686a.pdf file many times, tried all I can think of.
> >   According to the 686a.pdf the data size is 0x80 bytes.
> > 
> 
> xmbmon works great (for temperature sorts of things) on my VIA 686B. 
> You
> might want to take a look at that code (it's in ports).

Many thanks, I was not aware of this package.  I have had a quick
peek and it looks to be accessing te offset registers directly,
(which it warns about) but this should privide enough functionality
to get my code to work.

I will spend some time comparing the functionality of each.
If there is anything missing in the xmbmon for via functions
that I have, I will send patches to the author.  It's better to
have one package that can support multiple health chips.

 - mike

> 
> -- 
> jmc
> 
> MacroHard -- the perfection of form over
>              substance, marketing over
>              performance, and greed over
>              design . . .

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Mon Sep 24 18: 4:32 2001
Delivered-To: freebsd-hardware@freebsd.org
Received: from sasami.jurai.net (sasami.jurai.net [64.0.106.45])
	by hub.freebsd.org (Postfix) with ESMTP
	id 32B6C37B426; Mon, 24 Sep 2001 18:04:27 -0700 (PDT)
Received: from localhost (winter@localhost)
	by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id VAA17346;
	Mon, 24 Sep 2001 21:03:52 -0400 (EDT)
Date: Mon, 24 Sep 2001 21:03:52 -0400 (EDT)
From: "Matthew N. Dodd" <winter@jurai.net>
To: Mike Bruins <bruins@hal9000.net.au>
Cc: freebsd-questions@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG
Subject: Re: health chip driver - vt82c686 - finishing off
In-Reply-To: <20010924221149.A4971@wall.hal9000.net.au>
Message-ID: <Pine.BSF.4.21.0109242101270.3806-100000@sasami.jurai.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hardware.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hardware>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hardware>
X-Loop: FreeBSD.org

On Mon, 24 Sep 2001, Mike Bruins wrote:
>         via->mem_rid = hwm_io_base_reg;
>         via->res_mem = bus_alloc_resource(dev, SYS_RES_MEMORY, &(via->mem_rid),
>                 0ul, ~0ul, 0x80, RF_ACTIVE);

Change 0x80 to 1.  The parent has already specified the correct size of
this resource.

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| winter@jurai.net |       2 x '84 Volvo 245DL        | ix86,sparc,pmax |
| http://www.jurai.net/~winter |  For Great Justice!  | ISO8802.5 4ever |


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Tue Sep 25 19:16:33 2001
Delivered-To: freebsd-hardware@freebsd.org
Received: from EnContacto.Net (adsl-64-173-182-158.dsl.mtry01.pacbell.net [64.173.182.158])
	by hub.freebsd.org (Postfix) with ESMTP
	id 0A19837B408; Tue, 25 Sep 2001 19:16:27 -0700 (PDT)
Received: (from root@localhost)
	by EnContacto.Net (8.11.6/8.11.4) id f8Q2GN423768;
	Tue, 25 Sep 2001 19:16:23 -0700 (PDT)
	(envelope-from eculp@EnContacto.Net)
Received: from 24.20.19.75 ( [24.20.19.75])
	as user eculp@Mail.SavvyWorld.Net by Mail.SavvyWorld.Net with HTTP;
	Tue, 25 Sep 2001 19:16:23 -0700
Message-ID: <1001470583.3bb13a7799dd4@Mail.SavvyWorld.Net>
Date: Tue, 25 Sep 2001 19:16:23 -0700
From: Edwin Culp <eculp@EnContacto.Net>
To: hardware@FreeBSD.Org
Cc: ISP@FreeBSD.Org
Subject: Server recommendation for co-location.
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 2.3.7-cvs
X-Originating-IP: 24.20.19.75
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hardware.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hardware>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hardware>
X-Loop: FreeBSD.org

I need to co-locate a server in Singapore so reliability is
important:-).  I am thinking of something with a ServerWorks 
LE-based board, multiprocessor, but with one P-III Xeon to 
start, running at from 700 Mhz to 1,000 Mhz, 2Gb initial ram, 
an extremely well ventilated box with multiple, hot swap, 
power supplies 500-750 watts, each.  I would like to have a 
Raid 10 array with from .5 TB to 1 TB initially.  
I find the 3ware escalade 64 bit, switched, 7000 series to be a a 
very compelling solution but I remember seeing a thread not long
ago about it having pretty serious problems in one installation,
but I've also heard some very good things about it.  Does anyone
know of a solid raid 10 SCSI solution for FreeBSD? 

All suggestions appreciated especially about 3ware, motherboard, 
drives, etc.  If I remember the drives that were having problems 
in the 3ware thread were IBM, so they are out.  I was thinking 
about maxtor, I've used several (7500 rpm) for a couple 
of years with no problems.

Now for the hard part, our finance guy wants to lease the equipment
and would prefer to buy from a supplier rather than build it in house.:-(
He obviously suggested, IBM, Dell, HP, Compaq, etc. etc. all of which
have more trade-offs than I would like to make.  Does anyone know of a real
company that [could|would|does] build[s] something similar? 

Thanks,

ed

---

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Wed Sep 26  5:19:39 2001
Delivered-To: freebsd-hardware@freebsd.org
Received: from c001.snv.cp.net (c001-h011.c001.snv.cp.net [209.228.32.125])
	by hub.freebsd.org (Postfix) with SMTP id 4715D37B403
	for <freebsd-hardware@freebsd.org>; Wed, 26 Sep 2001 05:19:35 -0700 (PDT)
Received: (cpmta 2923 invoked from network); 26 Sep 2001 05:19:26 -0700
Date: 26 Sep 2001 05:19:26 -0700
Message-ID: <20010926121926.2922.cpmta@c001.snv.cp.net>
X-Sent: 26 Sep 2001 12:19:26 GMT
Received: from [24.48.64.135] by mail.sawilson.com with HTTP;
    26 Sep 2001 05:19:26 PDT
Content-Type: text/plain
Content-Disposition: inline
Mime-Version: 1.0
To: eculp@EnContacto.Net
From: sawilson@sawilson.com
Cc: freebsd-hardware@freebsd.org
X-Mailer: Web Mail 3.9.3.5
Subject: Re: Server recommendation for co-location.
X-Sent-From: sawilson@sawilson.com
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hardware.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hardware>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hardware>
X-Loop: FreeBSD.org

On Tue, 25 September 2001, Edwin Culp wrote:

> 
> I need to co-locate a server in Singapore so reliability is
> important:-).  I am thinking of something with a ServerWorks 
> LE-based board, multiprocessor, but with one P-III Xeon to 
> start, running at from 700 Mhz to 1,000 Mhz, 2Gb initial ram, 
> an extremely well ventilated box with multiple, hot swap, 
> power supplies 500-750 watts, each.  I would like to have a 
> Raid 10 array with from .5 TB to 1 TB initially.  
> I find the 3ware escalade 64 bit, switched, 7000 series to be a a 
> very compelling solution but I remember seeing a thread not long
> ago about it having pretty serious problems in one installation,
> but I've also heard some very good things about it.  Does anyone
> know of a solid raid 10 SCSI solution for FreeBSD? 
> Now for the hard part, our finance guy wants to lease the equipment
> and would prefer to buy from a supplier rather than build it in house.:-(
> He obviously suggested, IBM, Dell, HP, Compaq, etc. etc. all of which
> have more trade-offs than I would like to make.  Does anyone know of a real
> company that [could|would|does] build[s] something similar? 

Hello There,

	For SMP, I always use tyan stuff. They have serverworks based boards. For scsi raid 10 (1+0), I use AMI MegaRAID 428's or 434's. I usually go with IBM scsi drives. I don't know of anybody that's piecemealing systems together, then leasing them. If I'm not building it, I'm a big fan of either the Dell Poweredge series of SMP machines, or the Compaq equivalent. The raid solutions in both are supported. I've had great success with the PowerEdge machines running FreeBSD doing mission critical stuff. Even an old 2300/400 does a great job. I don't know very much about IDE raid. I don't have good feelings about using IDE for anything important. Are you sure this has to be a raid 10? I'm a big fan of the raid 10, but I'm a bigger fan of raid 50 at the moment. With an AMI 4xx card, you can have a hot spare already there waiting in case of drive failure, and it will automatically rebuild itself. 

	If you install sendmail on this machine, please consider doing everything you can to make sure it's not configured as an open relay. :) I get enough spam from singapore. I hope this helps.

--

Best Regards,
S.A.Wilson

"The box said 'Requires Windows 95, NT, or better' so I installed FreeBSD."

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Wed Sep 26  9:16:52 2001
Delivered-To: freebsd-hardware@freebsd.org
Received: from zeus.la.kdd.com (zeus.la.kdd.com [209.137.146.36])
	by hub.freebsd.org (Postfix) with ESMTP id D3B8C37B408
	for <freebsd-hardware@FreeBSD.ORG>; Wed, 26 Sep 2001 09:16:48 -0700 (PDT)
Received: from griffon (argos.la.kdd.com [209.137.146.34])
	by zeus.la.kdd.com (8.11.4+3.4W/8.11.4) with ESMTP id f8QGH0f12324
	for <freebsd-hardware@FreeBSD.ORG>; Wed, 26 Sep 2001 09:17:00 -0700 (PDT)
Date: Wed, 26 Sep 2001 09:14:29 -0700
From: Shinya Oda <shinya@la.kdd.com>
To: freebsd-hardware@FreeBSD.ORG
Subject: 
Message-Id: <20010926091418.1E2C.SHINYA@la.kdd.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.00.07
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hardware.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hardware>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hardware>
X-Loop: FreeBSD.org

auth d49a1da4 subscribe freebsd-hardware shinya@la.kdd.com

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Wed Sep 26 17: 3:49 2001
Delivered-To: freebsd-hardware@freebsd.org
Received: from hal9000.net.au (cu764.adelaide.adsl.on.net [150.101.237.2])
	by hub.freebsd.org (Postfix) with ESMTP id BF05237B406
	for <freebsd-hardware@freebsd.org>; Wed, 26 Sep 2001 17:03:39 -0700 (PDT)
Received: (from bruins@localhost)
	by hal9000.net.au (8.11.1/8.11.1) id f8R02uh14169;
	Thu, 27 Sep 2001 08:02:56 +0800 (WST)
	(envelope-from bruins)
Date: Thu, 27 Sep 2001 08:02:56 +0800
From: Mike Bruins <bruins@hal9000.net.au>
To: "Matthew N. Dodd" <winter@jurai.net>
Cc: Mike Bruins <bruins@hal9000.net.au>, freebsd-hardware@freebsd.org
Subject: Re: health chip driver - vt82c686 - finishing off
Message-ID: <20010927080256.A14035@wall.hal9000.net.au>
References: <20010925092517.A7092@wall.hal9000.net.au> <Pine.BSF.4.21.0109242143150.3806-100000@sasami.jurai.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <Pine.BSF.4.21.0109242143150.3806-100000@sasami.jurai.net>; from winter@jurai.net on Mon, Sep 24, 2001 at 09:47:38PM -0400
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hardware.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hardware>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hardware>
X-Loop: FreeBSD.org

On Mon, Sep 24, 2001 at 09:47:38PM -0400, Matthew N. Dodd wrote:
> On Tue, 25 Sep 2001, Mike Bruins wrote:
> > I will again try a value of 1.  Do you have any thoughts on
> > how to determine the value of the hwm_io_base_reg ?
> 
> The documentation should tell you which config space register contains
> your io/mem address mapping.
> 
> Typically this is 0x10 for IO and 0x14 for MEM.

I believe I need to read the value "loosely" pointed to by 0x70.
(by loosely I mean " &= 0xFFFE")

#define CONF_HWM_BASE        0x70
        a = CONF_HWM_BASE;
        v = pci_read_config(dev, a, 2);
        viahwm_base = 0xFFFE & v;
        device_printf(dev, "Base Address = 0x%04x\n",viahwm_base);

> 
> What does the probe line for your driver output?
> 

Output :
Sep 26 23:15:32 hal9000 /kernel: via0: via_attach via0
Sep 26 23:15:32 hal9000 /kernel: via0: register 0x00 = 0x1106
Sep 26 23:15:32 hal9000 /kernel: via0: register 0x02 = 0x3057
Sep 26 23:15:32 hal9000 /kernel: via0: register 0x74 = 0x0001
Sep 26 23:15:32 hal9000 /kernel: via0: register 0x74 = 0x0001
Sep 26 23:15:32 hal9000 /kernel: via0: register 0x70 = 0x0c01
Sep 26 23:15:32 hal9000 /kernel: via0: Base Address = 0x0c00
Sep 26 23:15:32 hal9000 /kernel: via0: via_attach: done
Sep 26 23:15:32 hal9000 /kernel: 
Sep 26 23:15:32 hal9000 /kernel: Loaded via character device driver


Typically the viahwm_base is 0x0c00.

I have seen code using /dev/io device to access that memory,
but wondering if that should only be done in userland.
(asside:I am planning to write a bit of perl on the weekend to 
test if it actually works.)

My questions is: What do I set the value of rid to?
 a) 0x70 
 b) 0x0c00
 c) Other?  Please specify.

        rid = ??;
        via->res_mem = bus_alloc_resource(dev, SYS_RES_MEMORY, &rid,
                0ul, ~0ul, 0x01, RF_ACTIVE);

Oh yes, I want to thank everyone who has been involved with this 
discussion.  I didn't expect such a good response.

  - mike

> | Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
> | winter@jurai.net |       2 x '84 Volvo 245DL        | ix86,sparc,pmax |
> | http://www.jurai.net/~winter |  For Great Justice!  | ISO8802.5 4ever |
> 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Wed Sep 26 19:48:59 2001
Delivered-To: freebsd-hardware@freebsd.org
Received: from sasami.jurai.net (sasami.jurai.net [64.0.106.45])
	by hub.freebsd.org (Postfix) with ESMTP id B03BD37B435
	for <freebsd-hardware@freebsd.org>; Wed, 26 Sep 2001 19:48:56 -0700 (PDT)
Received: from localhost (winter@localhost)
	by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id WAA54782;
	Wed, 26 Sep 2001 22:48:26 -0400 (EDT)
Date: Wed, 26 Sep 2001 22:48:26 -0400 (EDT)
From: "Matthew N. Dodd" <winter@jurai.net>
To: Mike Bruins <bruins@hal9000.net.au>
Cc: freebsd-hardware@freebsd.org
Subject: Re: health chip driver - vt82c686 - finishing off
In-Reply-To: <20010927080256.A14035@wall.hal9000.net.au>
Message-ID: <Pine.BSF.4.21.0109262248020.3806-100000@sasami.jurai.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hardware.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hardware>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hardware>
X-Loop: FreeBSD.org

On Thu, 27 Sep 2001, Mike Bruins wrote:
> My questions is: What do I set the value of rid to?
>  a) 0x70 
>  b) 0x0c00
>  c) Other?  Please specify.

Try 0x70.

>         rid = ??;
>         via->res_mem = bus_alloc_resource(dev, SYS_RES_MEMORY, &rid,
>                 0ul, ~0ul, 0x01, RF_ACTIVE);
> 
> Oh yes, I want to thank everyone who has been involved with this 
> discussion.  I didn't expect such a good response.

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| winter@jurai.net |       2 x '84 Volvo 245DL        | ix86,sparc,pmax |
| http://www.jurai.net/~winter |  For Great Justice!  | ISO8802.5 4ever |


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Thu Sep 27  9:49:31 2001
Delivered-To: freebsd-hardware@freebsd.org
Received: from mail.ots.utexas.edu (mail.ots.utexas.edu [128.83.223.128])
	by hub.freebsd.org (Postfix) with SMTP id 4D54F37B440
	for <FREEBSD-HARDWARE@freebsd.org>; Thu, 27 Sep 2001 09:49:26 -0700 (PDT)
Received: (qmail 71281 invoked by uid 0); 27 Sep 2001 16:49:25 -0000
Received: from bubba.ots.utexas.edu (128.83.223.16)
  by mail.ots.utexas.edu with SMTP; 27 Sep 2001 16:49:25 -0000
Date: Thu, 27 Sep 2001 11:49:25 -0500
From: Donald Nash <D.Nash@utexas.edu>
To: FREEBSD-HARDWARE@freebsd.org
Subject: FreeBSD and VIA chipsets
Message-ID: <114232891.1001591365@bubba.ots.utexas.edu>
X-Mailer: Mulberry/2.1.0 (Mac OS/PPC)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hardware.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hardware>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hardware>
X-Loop: FreeBSD.org

We are contemplating the purchase of some motherboards which use VIA 
chipsets rather than Intel.  Specifically, we're looking at a Micro Star 
694T PRO (MS-6309 v5.0), which uses the VIA 694X/694T (North-Bridge 510 
BGA) and VT82C686B (South-Bridge 352 BGA) chips.  According to VIA's 
website, that's called the Apollo Pro133A chipset.  One of the guys here is 
into Linux, and he saw something go across one of the Linux mailing lists 
to the effect that certain versions of the Linux kernel don't work with 
certain VIA chipsets.  Before we buy these systems, I need to know if 
FreeBSD will have any difficulty with this chipset.  I really don't expect 
it to be a problem since ASUS is a recommended motherboard manufacturer for 
FreeBSD systems and they use VIA chipsets, but I'd really like to have an 
informed opinion before we buy these things.

I attempted to sign on to this list yesterday, but my subscription had to 
go to the moderator (I used an address different from my normal return 
address), and he hasn't responded yet.  We're a little short on time, so I 
can't afford to sit on this question any longer.  So if you have an answer, 
please respond to me directly rather than just to the list.

Many thanks,

-- 
Donald L. Nash, <D.Nash@utexas.edu>, PGP Key ID: 0x689DA021
Telecommunication and Internet Services, The University of Texas at Austin


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Thu Sep 27 12:57: 0 2001
Delivered-To: freebsd-hardware@freebsd.org
Received: from msgbas1.cos.agilent.com (msgbas1x.cos.agilent.com [192.25.240.36])
	by hub.freebsd.org (Postfix) with ESMTP id 36DDD37B409
	for <FREEBSD-HARDWARE@FreeBSD.ORG>; Thu, 27 Sep 2001 12:56:57 -0700 (PDT)
Received: from msgrel1.cos.agilent.com (msgrel1.cos.agilent.com [130.29.152.77])
	by msgbas1.cos.agilent.com (Postfix) with ESMTP
	id A713B2F6F; Thu, 27 Sep 2001 13:56:56 -0600 (MDT)
Received: from mina.soco.agilent.com (mina.soco.agilent.com [141.121.54.157])
	by msgrel1.cos.agilent.com (Postfix) with ESMTP
	id DD581627; Thu, 27 Sep 2001 13:56:55 -0600 (MDT)
Received: from mina.soco.agilent.com (darrylo@localhost [127.0.0.1])
	by mina.soco.agilent.com (8.9.3 (PHNE_22672)/8.9.3 SMKit7.1.1_Agilent) with ESMTP id MAA19986;
	Thu, 27 Sep 2001 12:56:55 -0700 (PDT)
Message-Id: <200109271956.MAA19986@mina.soco.agilent.com>
To: Donald Nash <D.Nash@utexas.edu>
Cc: FREEBSD-HARDWARE@FreeBSD.ORG
Subject: Re: FreeBSD and VIA chipsets 
Reply-To: Darryl Okahata <darrylo@soco.agilent.com>
In-Reply-To: Your message of "Thu, 27 Sep 2001 11:49:25 CDT."
             <114232891.1001591365@bubba.ots.utexas.edu> 
Mime-Version: 1.0 (generated by tm-edit 1.6)
Content-Type: text/plain; charset=US-ASCII
Date: Thu, 27 Sep 2001 12:56:54 -0700
From: Darryl Okahata <darrylo@soco.agilent.com>
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hardware.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hardware>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hardware>
X-Loop: FreeBSD.org

Donald Nash <D.Nash@utexas.edu> wrote:

> I really don't expect 
> it to be a problem since ASUS is a recommended motherboard manufacturer for 
> FreeBSD systems and they use VIA chipsets, but I'd really like to have an 
> informed opinion before we buy these things.

     I don't know about the particular motherboard you're looking at,
but VIA KT133/KT133A w/686B chipset motherboards can supposedly have
issues with IDE data corruption (among other things), and, as far as I
know, FreeBSD has no fixes for this (unlike Linux, I think).

[ If anyone knows of FreeBSD fixes, I'd like to hear about them.  ]

     Supposedly, the problem can be fixed in the BIOS, but I've only
heard this as a rumor.  You might want to verify that whatever you buy
has the bug fixed.

     For some general (non-FreeBSD) information on the bug, check out:

	http://www.viahardware.com/686b_1.shtm
	http://www2.au-ja.de/review-kt133a-1-en.html

You can also do a google groups search for "via chipset ide corruption".

> I attempted to sign on to this list yesterday, but my subscription had to 
> go to the moderator (I used an address different from my normal return 
> address), and he hasn't responded yet.  We're a little short on time, so I 
> can't afford to sit on this question any longer.  So if you have an answer, 
> please respond to me directly rather than just to the list.

[ I normally do not reply by email, but this is definitely a good reason
  for doing so.  ]

-- 
	Darryl Okahata
	darrylo@soco.agilent.com

DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Agilent Technologies, or
of the little green men that have been following him all day.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Fri Sep 28 11:30:28 2001
Delivered-To: freebsd-hardware@freebsd.org
Received: from tandem.milestonerdl.com (tandem.milestonerdl.com [204.107.138.1])
	by hub.freebsd.org (Postfix) with ESMTP id E1F0537B40F
	for <freebsd-hardware@freebsd.org>; Fri, 28 Sep 2001 11:30:26 -0700 (PDT)
Received: (from marc@localhost)
	by tandem.milestonerdl.com (8.11.2/8.10.0) id f8SIXZE09070
	for freebsd-hardware@freebsd.org; Fri, 28 Sep 2001 13:33:35 -0500 (CDT)
Date: Fri, 28 Sep 2001 13:33:35 -0500 (CDT)
Message-Id: <200109281833.f8SIXZE09070@tandem.milestonerdl.com>
X-Authentication-Warning: tandem.milestonerdl.com: marc set sender to mtr+thinkpad@milestonerdl.com using -f
To: freebsd-hardware@freebsd.org
From: mtr+thinkpad@milestonerdl.com
Subject: Thinkpad I series 1300 ( 11715xu ) is it known to work with FreeBSD 4.X
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hardware.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hardware>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hardware>
X-Loop: FreeBSD.org

? 
I am looking to buy a IBM Thinkpad I 1300 series with the built in wireless    
option.   Does anyone know if the laptop works with FreeBSD stable (4.3/4.4)  
and does the wireless also work with this machine? 

Thanks for your reply. 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Sat Sep 29 20:52:46 2001
Delivered-To: freebsd-hardware@freebsd.org
Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80])
	by hub.freebsd.org (Postfix) with ESMTP id 2736137B406
	for <FREEBSD-HARDWARE@FreeBSD.ORG>; Sat, 29 Sep 2001 20:52:42 -0700 (PDT)
Received: by wantadilla.lemis.com (Postfix, from userid 1004)
	id 252716AB08; Sun, 30 Sep 2001 13:23:20 +0930 (CST)
Date: Sun, 30 Sep 2001 13:23:20 +0930
From: Greg Lehey <grog@FreeBSD.org>
To: Darryl Okahata <darrylo@soco.agilent.com>
Cc: Donald Nash <D.Nash@utexas.edu>, FREEBSD-HARDWARE@FreeBSD.ORG
Subject: Re: FreeBSD and VIA chipsets
Message-ID: <20010930132319.K25827@wantadilla.lemis.com>
References: <114232891.1001591365@bubba.ots.utexas.edu> <200109271956.MAA19986@mina.soco.agilent.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.2.5i
In-Reply-To: <200109271956.MAA19986@mina.soco.agilent.com>; from darrylo@soco.agilent.com on Thu, Sep 27, 2001 at 12:56:54PM -0700
Organization: The FreeBSD Project
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-418-838-708
WWW-Home-Page: http://www.FreeBSD.org/
X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF  13 24 52 F8 6D A4 95 EF
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hardware.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hardware>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hardware>
X-Loop: FreeBSD.org

On Thursday, 27 September 2001 at 12:56:54 -0700, Darryl Okahata wrote:
> Donald Nash <D.Nash@utexas.edu> wrote:
>
>> I really don't expect
>> it to be a problem since ASUS is a recommended motherboard manufacturer for
>> FreeBSD systems and they use VIA chipsets, but I'd really like to have an
>> informed opinion before we buy these things.
>
>      I don't know about the particular motherboard you're looking at,
> but VIA KT133/KT133A w/686B chipset motherboards can supposedly have
> issues with IDE data corruption (among other things), and, as far as I
> know, FreeBSD has no fixes for this (unlike Linux, I think).
>
> [ If anyone knows of FreeBSD fixes, I'd like to hear about them.  ]

Søren committed some fixes to -CURRENT the other day.  I expect it
will soon find its way to -STABLE.

>> I attempted to sign on to this list yesterday, but my subscription had to
>> go to the moderator (I used an address different from my normal return
>> address), and he hasn't responded yet.  We're a little short on time, so I
>> can't afford to sit on this question any longer.  So if you have an answer,
>> please respond to me directly rather than just to the list.
>
> [ I normally do not reply by email, but this is definitely a good reason
>   for doing so.  ]

There are plenty of others.  See http://www.lemis.com/questions.html
for more details.

Greg
--
See complete headers for address and phone numbers

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message