On Wed, Feb 02, 2005 at 01:16:30PM -0800, john heasley wrote:
> sysctls might be the missing glue to get tw_cli working.  I had noticed
> them before.
> 
> You could try adding these or try
> 	http://shrubbery.net/~heas/twedm
> 	http://shrubbery.net/~heas/twedm.8
> no warranty, all warnings implied.

John,

Is the twedm 0.8a supposed to work on a -current amd64? From the other reports
on these lists, it sounds like it works on i386, but on amd64 with an 8000
series I get:

intrepid# ./twedm -d /dev/twe0
Warning: This code is of alpha quality, has had very little testing,
         may destroy arrays on a whim.  Use it at your own risk.  I can
         not be held accountable!

twedm> show
ERROR: ioctl() failed for controller compatibility code: Invalid argument
intrepid#

This is for:

twe0 at pci0 dev 14 function 0: 3ware Escalade
twe0: interrupting at ioapic0 pin 19 (irq 11)
twe0: 4 ports, Firmware FE8S 1.05.00.068, BIOS BE7X 1.08.00.048
twe0: Monitor ME7X 1.01.00.040, PCB Rev5    , Achip 3.20    , Pchip 1.30-66
twe0: port 0: Maxtor 6Y250P0                           239372 MB
twe0: port 1: Maxtor 6Y250P0                           239372 MB
twe0: port 3: Maxtor 6Y250P0                           239372 MB
ld0 at twe0 unit 0: 64K stripe RAID5, status: Normal

Do I need a native amd64 binary (the .tar.gz on your site isn't +r for the web),
or is there some other config bogon?

	ScottE