From owner-freebsd-hardware Sun Jul 18 10:42:11 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from pinky.us.net (pinky.us.net [198.240.73.64]) by hub.freebsd.org (Postfix) with ESMTP id 4273314C38 for ; Sun, 18 Jul 1999 10:41:54 -0700 (PDT) (envelope-from sillybug@pinky.us.net) Received: (from sillybug@localhost) by pinky.us.net (8.8.8/8.8.8) id NAA03507 for freebsd-hardware@freebsd.org; Sun, 18 Jul 1999 13:30:19 -0400 (EDT) (envelope-from sillybug) From: Brian Skrab Message-Id: <199907181730.NAA03507@pinky.us.net> Subject: TurboCom Serial card + FBSD 3.2 ??? To: freebsd-hardware@freebsd.org Date: Sun, 18 Jul 1999 13:30:18 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I have just come across a 3com Impact IQ ISDN Terminal Adapter for my FreeBSD 3.2 box. Along with this device came a TurboCom 920 high speed serial card which has a 16750 UART on it to take full advantage of the high data rate delivered by the TA. Now, here's where the problem comes in. I have the TurboCom card setup to act as COM2 (/dev/cuaa1), but whenever I try to use the TA on that port, all communications with the modem come back as gibberish on the screen when viewed in the term utility of user ppp. I don't know if this has anything to do with it, but FBSD detects the serial port as a 16550 UART controlled port. Is there some sort of special support that must be compiled into the kernel for such a device? BTW, I know that the TA works when plugged into the standard serial port on the motherboard and with the speed ratcheted back to 115k -- I'm using it right now. If anyone can provide some information to help get this device working, or if you can recommend another serial card, I would very much appreciate it. Thanks, ~brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Jul 18 20:24:43 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from strike.velocet.ca (strike.velocet.ca [209.167.225.34]) by hub.freebsd.org (Postfix) with ESMTP id ED9C51507A for ; Sun, 18 Jul 1999 20:24:28 -0700 (PDT) (envelope-from dgilbert@strike.velocet.ca) Received: (from dgilbert@localhost) by strike.velocet.ca (8.9.3/8.9.2) id XAA08403; Sun, 18 Jul 1999 23:24:05 -0400 (EDT) (envelope-from dgilbert) Date: Sun, 18 Jul 1999 23:24:05 -0400 (EDT) Message-Id: <199907190324.XAA08403@strike.velocet.ca> To: freebsd-hardware@freebsd.org From: dgilbert@velocet.ca Subject: smbus not quite right? Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a machine with a P5A motherboard, which probes as follows: pcf0: iicbus0: on pcf0 addr 0xaa iicsmb0: on iicbus0 smbus0: on iicsmb0 smb0: on smbus0 iic0: on iicbus0 Now... If I run mbmon in ISA mode, which opens /dev/io, it works. If I run it in in smbus mode, which opens /dev/smb0, it fails. Having read the documentation on /dev/io, I'd rather not have that ability on a server... I would guess that it requires an insecure level. So... any ideas? Dave. -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Jul 18 22:39: 7 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 5461614D2A for ; Sun, 18 Jul 1999 22:38:55 -0700 (PDT) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id HAA22171 for freebsd-hardware@FreeBSD.ORG; Mon, 19 Jul 1999 07:38:54 +0200 (CEST) (envelope-from olli) Date: Mon, 19 Jul 1999 07:38:54 +0200 (CEST) From: Oliver Fromme Message-Id: <199907190538.HAA22171@dorifer.heim3.tu-clausthal.de> To: freebsd-hardware@FreeBSD.ORG Subject: USB support for Kodak DC240 (umass)? Organization: Administration Heim 3 Reply-To: freebsd-hardware@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I got a digital camera (Kodak DC240) which supports USB. It works very well under Windows98: As soon as it is plugged in, the camera is recognized as some kind of "disk drive", with a directory /dcim/100dc240 containing all the images in JPEG format. It's also nicely fast, downloading 8 Mbyte of images takes only a few seconds (would take 20 minutes through a standard serial cable!). Now, of course I'd like to use it under FreeBSD. Since it is accessed like a disk drive, I thought that it might work with the umass driver, but I didn't... The camera uses CompactFlash cards, which "emulate" ATA disks. So I guess the problem is that the camera is using the 8070i (ATA) subclass, which is not implemented in the umass driver yet. Is the 8070i support planned for the not-too-far future? Kodak freely provides programming docs for developers, but unfortunately I'm not an USB expert at all myself, so it's not of much use for me. I've attached the output of usbdevs and usb_dump below, in case it might be of any use. I cannot lend the camera to anybody, I'm afraid, but of course I'm willing to make any experiments and try everything that would help in this matter. Regards Oliver # usbdevs -v Controller /dev/usb0: addr 1: self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 port 1 addr 2: self powered, config 1, KODAK DC240 Zoom Digital Camera(0x0120), Eastman Kodak Company(0x040a), rev 1.03 port 2 powered # ./usb_dump -c 1 -i -f /dev/ugen0 Product: KODAK DC240 Zoom Digital Camera Vendor: Eastman Kodak Company address 2 # ./usb_dump -c 1 -d -f /dev/ugen0 DEVICE descriptor: bLength=18 bDescriptorType=1 bcdUSB=1.00 bDeviceClass=0 bDeviceSubClass=0 bDeviceProtocol=0 bMaxPacketSize=8 idVendor=0x040a idProduct=0x0120 bcdDevice=103 iManufacturer=1 iProduct=2 iSerialNumber=0 bNumConfigurations=1 CONFIGURATION descriptor: bLength=9 bDescriptorType=2 wTotalLength=32 bNumInterface=1 bConfigurationValue=1 iConfiguration=0 bmAttributes=40 bMaxPower=100 mA INTERFACE descriptor index 0: bLength=9 bDescriptorType=4 bInterfaceNumber=0 bAlternateSetting=0 bNumEndpoints=2 bInterfaceClass=0 bInterfaceSubClass=0 bInterfaceProtocol=0 iInterface=0 ENDPOINT descriptor index 0: bLength=7 bDescriptorType=5 bEndpointAddress=1-out bmAttributes=2 wMaxPacketSize=64 bInterval=0 ENDPOINT descriptor index 1: bLength=7 bDescriptorType=5 bEndpointAddress=2-in bmAttributes=2 wMaxPacketSize=64 bInterval=0 # ./usb_dump -c 1 -D -f /dev/ugen0 DEVICE descriptor: bLength=18 bDescriptorType=1 bcdUSB=1.00 bDeviceClass=0 bDeviceSubClass=0 bDeviceProtocol=0 bMaxPacketSize=8 idVendor=0x040a idProduct=0x0120 bcdDevice=103 iManufacturer=1 iProduct=2 iSerialNumber=0 bNumConfigurations=1 Current configuration is number 1 CONFIGURATION descriptor index 0: bLength=9 bDescriptorType=2 wTotalLength=32 bNumInterface=1 bConfigurationValue=1 iConfiguration=0 bmAttributes=40 bMaxPower=100 mA INTERFACE descriptor index 0, alt index 0: bLength=9 bDescriptorType=4 bInterfaceNumber=0 bAlternateSetting=0 bNumEndpoints=2 bInterfaceClass=0 bInterfaceSubClass=0 bInterfaceProtocol=0 iInterface=0 ENDPOINT descriptor index 0: bLength=7 bDescriptorType=5 bEndpointAddress=1-out bmAttributes=2 wMaxPacketSize=64 bInterval=0 ENDPOINT descriptor index 1: bLength=7 bDescriptorType=5 bEndpointAddress=2-in bmAttributes=2 wMaxPacketSize=64 bInterval=0 -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jul 19 0:19:49 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id E366014C4B for ; Mon, 19 Jul 1999 00:19:44 -0700 (PDT) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it (va-161.skylink.it [194.185.55.161]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id JAA32234; Mon, 19 Jul 1999 09:17:16 +0200 Received: from localhost (localhost.plazza.it [127.0.0.1]) by heidi.plazza.it (8.8.8/8.8.5) with SMTP id JAA00512; Mon, 19 Jul 1999 09:14:06 +0200 (CEST) Date: Mon, 19 Jul 1999 09:14:06 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: freebsd-hardware@FreeBSD.ORG Cc: USB BSD list Subject: Re: USB support for Kodak DC240 (umass)? In-Reply-To: <199907190538.HAA22171@dorifer.heim3.tu-clausthal.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Is the 8070i support planned for the not-too-far future? Yes, I have a SuperDrive here that I want to support. The problem is strapping the ATA layer on top. That layer is very much aimed at current AT-IDE interfaces and not yet able to be put on top of any host controller / transfer mechanism like SCSI. > Kodak freely provides programming docs for developers, but > unfortunately I'm not an USB expert at all myself, so it's not > of much use for me. Could you send me the URL? (saves me digging) > I've attached the output of usbdevs and usb_dump below, in case > it might be of any use. I cannot lend the camera to anybody, > I'm afraid, but of course I'm willing to make any experiments > and try everything that would help in this matter. Unfortunately the device does not speak about what it is (all zeroes int he deviceclass and subclass fields). Having 2 bulk endpipes it might be either a bulk mass storage device or Control/Bulk. Cheers, Nick > # usbdevs -v > Controller /dev/usb0: > addr 1: self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev= 1.00 > port 1 addr 2: self powered, config 1, KODAK DC240 Zoom Digital Camera(0= x0120), Eastman Kodak Company(0x040a), rev 1.03 > port 2 powered >=20 > # ./usb_dump -c 1 -i -f /dev/ugen0 > Product: KODAK DC240 Zoom Digital Camera > Vendor: Eastman Kodak Company > address 2 >=20 > # ./usb_dump -c 1 -d -f /dev/ugen0 > DEVICE descriptor: > bLength=3D18 bDescriptorType=3D1 bcdUSB=3D1.00 bDeviceClass=3D0 bDeviceSu= bClass=3D0 > bDeviceProtocol=3D0 bMaxPacketSize=3D8 > idVendor=3D0x040a idProduct=3D0x0120 bcdDevice=3D103 > iManufacturer=3D1 iProduct=3D2 iSerialNumber=3D0 bNumConfigurations=3D1 >=20 > CONFIGURATION descriptor: > bLength=3D9 bDescriptorType=3D2 wTotalLength=3D32 bNumInterface=3D1 > bConfigurationValue=3D1 iConfiguration=3D0 bmAttributes=3D40 bMaxPower=3D= 100 mA >=20 > INTERFACE descriptor index 0: > bLength=3D9 bDescriptorType=3D4 bInterfaceNumber=3D0 bAlternateSetting= =3D0 > bNumEndpoints=3D2 bInterfaceClass=3D0 bInterfaceSubClass=3D0 > bInterfaceProtocol=3D0 iInterface=3D0 >=20 > ENDPOINT descriptor index 0: > bLength=3D7 bDescriptorType=3D5 bEndpointAddress=3D1-out > bmAttributes=3D2 wMaxPacketSize=3D64 bInterval=3D0 >=20 > ENDPOINT descriptor index 1: > bLength=3D7 bDescriptorType=3D5 bEndpointAddress=3D2-in > bmAttributes=3D2 wMaxPacketSize=3D64 bInterval=3D0 >=20 > # ./usb_dump -c 1 -D -f /dev/ugen0 > DEVICE descriptor: > bLength=3D18 bDescriptorType=3D1 bcdUSB=3D1.00 bDeviceClass=3D0 bDeviceSu= bClass=3D0 > bDeviceProtocol=3D0 bMaxPacketSize=3D8 > idVendor=3D0x040a idProduct=3D0x0120 bcdDevice=3D103 > iManufacturer=3D1 iProduct=3D2 iSerialNumber=3D0 bNumConfigurations=3D1 >=20 > Current configuration is number 1 >=20 > CONFIGURATION descriptor index 0: > bLength=3D9 bDescriptorType=3D2 wTotalLength=3D32 bNumInterface=3D1 > bConfigurationValue=3D1 iConfiguration=3D0 bmAttributes=3D40 bMaxPower=3D= 100 mA >=20 > INTERFACE descriptor index 0, alt index 0: > bLength=3D9 bDescriptorType=3D4 bInterfaceNumber=3D0 bAlternateSetting= =3D0 > bNumEndpoints=3D2 bInterfaceClass=3D0 bInterfaceSubClass=3D0 > bInterfaceProtocol=3D0 iInterface=3D0 >=20 > ENDPOINT descriptor index 0: > bLength=3D7 bDescriptorType=3D5 bEndpointAddress=3D1-out > bmAttributes=3D2 wMaxPacketSize=3D64 bInterval=3D0 >=20 > ENDPOINT descriptor index 1: > bLength=3D7 bDescriptorType=3D5 bEndpointAddress=3D2-in > bmAttributes=3D2 wMaxPacketSize=3D64 bInterval=3D0 >=20 >=20 > --=20 > Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany > (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) >=20 > "In jedem St=FCck Kohle wartet ein Diamant auf seine Geburt" > (Terry Pratchett) >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message >=20 >=20 --=20 e-Mail: hibma@skylink.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jul 19 1:53:45 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from szorvor.mezon.net (www.mezon.net [194.143.248.55]) by hub.freebsd.org (Postfix) with ESMTP id 248201505C for ; Mon, 19 Jul 1999 01:53:36 -0700 (PDT) (envelope-from agdolla@mezon.net) Received: from localhost (agdolla@localhost) by szorvor.mezon.net (8.9.3/8.9.3) with ESMTP id KAA18661; Mon, 19 Jul 1999 10:53:08 +0200 (CEST) (envelope-from agdolla@mezon.net) X-Authentication-Warning: szorvor.mezon.net: agdolla owned process doing -bs Date: Mon, 19 Jul 1999 10:53:08 +0200 (CEST) From: Gabor Dolla To: Nick Hibma Cc: freebsd-hardware@FreeBSD.ORG, USB BSD list Subject: Re: [usb-bsd] Re: USB support for Kodak DC240 (umass)? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > Kodak freely provides programming docs for developers, but > > unfortunately I'm not an USB expert at all myself, so it's not > > of much use for me. > > Could you send me the URL? (saves me digging) me too, please. i have a kodak dvc323 usb kamera, so I'd like to play with it... Gabor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jul 19 9:10:24 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from pan.ch.intel.com (pan.ch.intel.com [143.182.246.24]) by hub.freebsd.org (Postfix) with ESMTP id 15DBB151D5 for ; Mon, 19 Jul 1999 09:10:17 -0700 (PDT) (envelope-from jreynold@sedona.ch.intel.com) Received: from sedona.intel.com (sedona.ch.intel.com [143.182.218.21]) by pan.ch.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.6 1998/11/24 22:10:56 iwep Exp iwep $) with ESMTP id JAA17930 for ; Mon, 19 Jul 1999 09:08:43 -0700 (MST) Received: from hip186.ch.intel.com (hip186.ch.intel.com [143.182.225.68]) by sedona.intel.com (8.9.1a/8.9.1/d: sendmail.cf,v 1.8 1999/04/16 15:25:49 steved Exp steved $) with ESMTP id JAA21418 for ; Mon, 19 Jul 1999 09:08:37 -0700 (MST) X-Envelope-To: X-Envelope-From: jreynold@sedona.ch.intel.com Received: (from jreynold@localhost) by hip186.ch.intel.com (8.9.1a/8.9.1/d: client.m4,v 1.3 1998/09/29 16:36:11 sedayao Exp sedayao $) id MAA24328; Mon, 19 Jul 1999 12:08:36 -0400 (EDT) From: John Reynolds~ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14227.19843.643417.275395@hip186.ch.intel.com> Date: Mon, 19 Jul 1999 09:08:35 -0700 (MST) To: freebsd-hardware@freebsd.org Subject: Recommendations of Seagate Hornet NS 8??? X-Mailer: VM 6.72 under Emacs 19.34.1 X-Euphoria: http://www.webnl.com/senff/leppard_start.html Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello all, I've tried searching the archives for this particular tape drive (seagate Hornet NS8) but didn't find anything but people complaining that Travan tape drives suck. Does anybody on this list have anything good to say about this model or Travan tapes in general? I *need* to have a tape backup of my home system (been burned on disks going bye-bye 1-too-many times) but simply cannot afford an Exabyte or "cheap" DAT tape drive :( ... these Hornet models look good on paper--have people used them with success? Thanks, -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds CEG, CCE, Next Generation Flows, HLA | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 868-6512 | | jreynold@sedona.ch.intel.com http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jul 19 15:35:52 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 23F0014DC0 for ; Mon, 19 Jul 1999 15:35:49 -0700 (PDT) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id AAA15773 for freebsd-hardware@freebsd.org; Tue, 20 Jul 1999 00:35:48 +0200 (CEST) (envelope-from olli) Date: Tue, 20 Jul 1999 00:35:48 +0200 (CEST) From: Oliver Fromme Message-Id: <199907192235.AAA15773@dorifer.heim3.tu-clausthal.de> To: freebsd-hardware@freebsd.org Subject: Re: USB support for Kodak DC240 (umass)? Organization: Administration Heim 3 Reply-To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Nick Hibma wrote in list.freebsd-hardware: > > Kodak freely provides programming docs for developers, but > > unfortunately I'm not an USB expert at all myself, so it's not > > of much use for me. > > Could you send me the URL? (saves me digging) http://www.kodak.com/US/en/developers/productsTechnologies/prodTechDC240.shtml You need to become a member of the "Kodak Developer Program", which is free, AFAIK. That's how the gPhoto folks got their information about the serial protocol of the Kodak cameras. As another alternative to download the pictures, it is possible to use an "IDE PCMCIA drive". You insert the camera's CompactFlash card, and then you can access it like a regular IDE drive. It's should work under FreeBSD, too. However, using USB would be much more convenient, and it would also be cheaper (such an IDE PCMCIA drive is 300 DM, =~ 150 $). Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jul 20 1:16:19 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id A3DC014D32 for ; Tue, 20 Jul 1999 01:16:06 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id KAA22166 for ; Tue, 20 Jul 1999 10:09:16 +0200 (MET DST) Date: Tue, 20 Jul 1999 10:09:14 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: freebsd-hardware@FreeBSD.ORG Subject: Re: USB support for Kodak DC240 (umass)? In-Reply-To: <199907192235.AAA15773@dorifer.heim3.tu-clausthal.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Could you send me the URL? (saves me digging) > > http://www.kodak.com/US/en/developers/productsTechnologies/prodTechDC240.shtml > > You need to become a member of the "Kodak Developer Program", > which is free, AFAIK. That's how the gPhoto folks got their > information about the serial protocol of the Kodak cameras. I haven't found any direct pointers at either Serial or USB protocols. but I'll do some more digging this evening. Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jul 20 5:24:10 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from mproxy.zedo.fuedo.de (mproxy.zedo.fuedo.de [193.99.167.226]) by hub.freebsd.org (Postfix) with ESMTP id E792614CEC; Tue, 20 Jul 1999 05:23:32 -0700 (PDT) (envelope-from hartung@zkom.de) Received: from master.zkom.de (master.zkom.de [193.99.166.6]) by mproxy.zedo.fuedo.de (8.9.3/8.9.3) with ESMTP id OAA06937; Tue, 20 Jul 1999 14:23:28 +0200 (CEST) Received: from zkom.de (jack.zkom.de [193.99.166.10]) by master.zkom.de (8.9.1a/8.8.8) with ESMTP id OAA09902; Tue, 20 Jul 1999 14:23:28 +0200 (CEST) (envelope-from hartung@zkom.de) Message-ID: <37946BAC.34DF01F3@zkom.de> Date: Tue, 20 Jul 1999 14:29:32 +0200 From: Michael Hartung Organization: ZKOM GmbH, Germany, Fax: +49 (0) 231 9700474 X-Mailer: Mozilla 4.06 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: RAID-controller Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Can anybody tell me which SCSI RAID-controller is the best ( and cheapest ) one to implement RAID-1 under FreeBSD 3.x. What about the storage management software? Thanks in advance -- Michael Hartung |~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| | ZKOM GmbH | | State Diagnostics Systems | | and Computer Networks | | | | WWW: www.zkom.de (WebCam) | | | | Joseph-von-Fraunhofer Str. 20 | | D-44227 Dortmund | | Germany | | E-mail: hartung@zkom.de | | Phone: +49 (0)231 / 9700 336 | | Fax: +49 (0)231 / 9700 474 | | Mobile: +49 (0)172 / 67 70 522 | | | | AG Dortmund HRB 12918 | | Managing Director: Dipl.-Ing. Michael Hartung | |_______________________________________________| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jul 20 11:37: 7 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from 001101.zer0.org (001101.zer0.org [206.24.105.163]) by hub.freebsd.org (Postfix) with ESMTP id A6BCF14C9E; Tue, 20 Jul 1999 11:37:03 -0700 (PDT) (envelope-from gsutter@001101.zer0.org) Received: (from gsutter@localhost) by 001101.zer0.org (8.9.2/8.9.2) id LAA76307; Tue, 20 Jul 1999 11:35:46 -0700 (PDT) (envelope-from gsutter) Date: Tue, 20 Jul 1999 11:35:46 -0700 From: Gregory Sutter To: Michael Hartung Cc: freebsd-scsi@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: RAID-controller Message-ID: <19990720113546.K45481@001101.zer0.org> References: <37946BAC.34DF01F3@zkom.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <37946BAC.34DF01F3@zkom.de>; from Michael Hartung on Tue, Jul 20, 1999 at 02:29:32PM +0200 Organization: Zer0 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Jul 20, 1999 at 02:29:32PM +0200, Michael Hartung wrote: > > Can anybody tell me which SCSI RAID-controller is the best ( and > cheapest ) one to implement RAID-1 under FreeBSD 3.x. What about the > storage management software? vinum(8) is the best software method, which would certainly be the cheapest. It's included in the base FreeBSD system. Any SCSI-SCSI RAID controller will work under FreeBSD. I personally have had good luck (and relatively cheap prices) with Infortrend, . It is likely that no vendor's storage management software will work under FreeBSD. Greg -- Gregory S. Sutter Cole's Law: Thinly sliced cabbage. mailto:gsutter@pobox.com http://www.pobox.com/~gsutter/ PGP DSS public key 0x40AE3052 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jul 20 21:24:51 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 32B88151C9; Tue, 20 Jul 1999 21:24:40 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id AAA29810; Wed, 21 Jul 1999 00:26:54 -0400 From: Bill Paul Message-Id: <199907210426.AAA29810@skynet.ctr.columbia.edu> Subject: Call for testers: Adaptec AIC-6915 fast ethernet driver To: hackers@freebsd.org, hardware@freebsd.org Date: Wed, 21 Jul 1999 00:26:53 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 4495 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org A driver for FreeBSD 3.x and 4.0-current is now available for testing for fast ethernet adapters based on the Adaptec AIC-6915 "Starfire" ethernet controller. This includes the following Adaptec "Duralink" models: - ANA-62011 single port 64-bit adapter - ANA-62022 dual port 64-bit adapter - ANA-62044 quad port 64-bit adapter - ANA-69011 single port 32-bit adapter - ANA-62020 single port 100baseFX These are Adaptec's replacements for its older DEC 21x4x-based multiport line of adapters. All cards support 10/100 speeds in full or half duplex. The multiport cards consist of multiple AIC-6915 chips linkec via a PCI to PCI bridge. Currently I have only tested the ANA-62022 dual port card, however all of them should work equally well. The 64-bit cards will work in a 32-bit slot on most newer machines. The Starfire supports a great many features including a 16-entry perfect RX filter, a 512-bit multicast hash table filter, a 512-bit high priority hash table, VLAN filtering, multiple RX and TX queues, and several different descriptor formats. There is also a programmable frame processor, however I haven't figured out how to use it. The FreeBSD driver uses a frame-based transmit descriptor (up to 14 packet fragments in one descriptor) and the producer/consumer queueing model with TX and RX completion descriptor queues. The perfect filter and hash filter are used for hardware multicast filtering. Support for BPF mode and promiscuous mode is also provided. The Starfire also supports TCP/IP checksum offload, however this is not yet implemented in this driver. The receive ring is programmed to have 256 descriptors. The transmit ring uses 128. This should be plenty for most server-based applications. Unfortunately, in spite of all the features in the Starfire, the chip requires receive buffers to be longword aligned, which means that received packets have to be copied in order to achieve proper payload alignemnt (which is handy on the x86 and required on the alpha). You'd think if they could go to the trouble of designing in special descriptor formats for MS-DOS and OS/2, they could handle DMAing to unaligned addresses. Oh well. This driver should work on both FreeBSD/i386 and FreeBSD/alpha. To add the driver to an existing FreeBSD 3.x system, do the following: - Download if_sf.c and if_sfreg.h from http://www.freebsd.org/~wpaul/Adaptec/3.0 and put them in /sys/pci. - Edit /sys/conf/files and add a line that says: pci/if_sf.c optional sf device-driver - Edit your kernel config file (e.g. /sys/i386/conf) and add a line that says: device sf0 - Config and compile a new kernel and boot it. To add the driver to an existing FreeBSD 4.0-current system, do one the following: - Download if_sf.c and if_sfreg.h from http://www.freebsd.org/~wpaul/Adaptec/4.0 and put them in /sys/pci. - Edit /sys/conf/files and add a line that says: pci/if_sf.c optional sf - Edit your kernel config file (e.g. /sys/i386/conf) and add a line that says: device sf0 - Config and compile a new kernel and boot it. Alternatively, if you have FreeBSD 4.0-current running on the x86 platform and don't want to recompile your kernel, you can try the following: - Download sf.ko from http://www.freebsd.org/~wpaul/Adaptec/4.0 and put it in /modules. - Edit /boot/defaults/loader.conf and add a line to the device driver modules section that says: sf_load="YES" # Adaptec PCI ethernet - Reboot The sf.ko module is compiled without BPF support. A Makefile is provided in the 4.0 directory which should allow you to recompile the module on both the x86 and alpha platforms. As usual, if you have any problems, please report them to wpaul@skynet.ctr.columbia.edu. Remember to provide lots of detailed information. Vote early and vote often. The sooner people bang on this a little, the sooner it will go into the tree. No user-servicable parts inside. Offer void where prohibited by law. Operators are standing by. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jul 21 13:19:31 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from orbital.eng.demon.net (orbital.eng.demon.net [193.195.224.208]) by hub.freebsd.org (Postfix) with ESMTP id A39761554F for ; Wed, 21 Jul 1999 13:19:18 -0700 (PDT) (envelope-from angel@orbital.eng.demon.net) Received: (from angel@localhost) by orbital.eng.demon.net (8.9.3/8.9.2) id VAA02615 for freebsd-hardware@freebsd.org; Wed, 21 Jul 1999 21:17:46 +0100 (BST) (envelope-from angel) Date: Wed, 21 Jul 1999 21:17:46 +0100 From: "angel@demon.net" To: freebsd-hardware@freebsd.org Subject: CDRW - HP CD Writer Plus 8100i - supported? Message-ID: <19990721211746.A2593@demon.net> Reply-To: angel@demon.net Mail-Followup-To: freebsd-hardware@freebsd.org References: <37946BAC.34DF01F3@zkom.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <37946BAC.34DF01F3@zkom.de>; from Michael Hartung on Tue, Jul 20, 1999 at 02:29:32PM +0200 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am thinking of purchasing a CD writer, but I don't have a SCSI card (and I don't think I can afford one, as well as a SCSI CD R). The most afforable CD writer I have found is the HP CD-Writer Plus 8100i; it is IDE. I was wondering if anyone has got this working under FreeBSD 3.2-RELEASE, and if any special kernel configs are required? Thanks in advance, angel -- angel@demon.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jul 21 17:56: 8 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from paprika.michvhf.com (paprika.michvhf.com [209.57.60.12]) by hub.freebsd.org (Postfix) with SMTP id 8136114C86 for ; Wed, 21 Jul 1999 17:55:58 -0700 (PDT) (envelope-from vev@michvhf.com) Received: (qmail 17560 invoked by uid 1001); 22 Jul 1999 00:54:53 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 21 Jul 1999 20:54:53 -0400 (EDT) X-Face: *0^4Iw) To: freebsd-hardware@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: 1373 sound chip Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I sent this to multimedia about a week ago and didn't get a response so I'm trying it here [hackers & hardware] (with minor mods): I'm setting up a new machine that has onboard sound in the form of an ES1373 Creative (Ensoniq, probably). Visual config shows an unknown device as ES0 and pcm0 doesn't find anything (tried various forms in the kernel config for that one, the last one was/is: device pcm0 Is there any driver for this chip? Under windows it uses the SoundBlaster AudioPCI 64V driver. So far I haven't found any specs on Creative's or Ensoniq's website. Can someone shed some light on possibly adapting the pcm driver to this chip (like how to ID, etc.) ? Vince. -- ========================================================================== Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null # include TEAM-OS2 Online Campground Directory http://www.camping-usa.com Online Giftshop Superstore http://www.cloudninegifts.com ========================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jul 22 5:45:56 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from sbridge.highvoltage.com (voltage.high-voltage.com [205.243.158.175]) by hub.freebsd.org (Postfix) with SMTP id 72AF914C0B; Thu, 22 Jul 1999 05:45:23 -0700 (PDT) (envelope-from BMCGROARTY@high-voltage.com) Date: Thu, 22 Jul 1999 7:07 -0600 From: "Brian McGroarty" To: "Vince Vielhaber" , "freebsd-hardware" , "hackers" Subject: RE: 1373 sound chip Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org There's a patch for the 1371 floating around that seems to work for the 1373 as well. Search the archive of FreeBSD-questions for "1371". Last I saw, the search page was still confused - you need to put "1371" in the web search field at the top, but still click the mailing list search button down below. -----Original Message----- From: Vince Vielhaber [mailto:vev@michvhf.com] Sent: Wednesday, July 21, 1999 6:54 PM To: Brian McGroarty; freebsd-hardware; hackers Subject: 1373 sound chip I sent this to multimedia about a week ago and didn't get a response so I'm trying it here [hackers & hardware] (with minor mods): I'm setting up a new machine that has onboard sound in the form of an ES1373 Creative (Ensoniq, probably). Visual config shows an unknown device as ES0 and pcm0 doesn't find anything (tried various forms in the kernel config for that one, the last one was/is: device pcm0 Is there any driver for this chip? Under windows it uses the SoundBlaster AudioPCI 64V driver. So far I haven't found any specs on Creative's or Ensoniq's website. Can someone shed some light on possibly adapting the pcm driver to this chip (like how to ID, etc.) ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jul 22 9:47: 1 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 7553C14C20; Thu, 22 Jul 1999 09:46:41 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id MAA02834; Thu, 22 Jul 1999 12:47:06 -0400 From: Bill Paul Message-Id: <199907221647.MAA02834@skynet.ctr.columbia.edu> Subject: Update on Adaptec AIC-6915 "starfire" driver To: hackers@freebsd.org, hardware@freebsd.org Date: Thu, 22 Jul 1999 12:47:04 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2873 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I haven't received any feedback yet on the Adaptec "Starfire" driver, however I made a few updates that people should know about: - I created a version of the driver for FreeBSD 2.2.x. You can find it at http://www.freebsd.org/~wpaul/Adaptec/2.2. Note: while I have verified that this code compiles, I have not been able to test it. There should not be any problems, but as always, Murphy's Law applies. - I found a bug today which is that sf_stats_update() required splimp() protection. I use the indirect register access method which is done in two stages: first you set the indirect address register to the register offset that you want to play with, then you access it via the indirect data register. However sf_stats_update() was interruptible which means that it was possible for the interrupt handler to run in between the first and second stages, which caused the stats updater to modify incorrect register locations. This bug would manifest itself in the form of watchdog timeouts and the 'collisions' counter sometimes reporting wildly incorrect values. I corrected this problem and updated the driver sources for each FreeBSD version (including 2.2.x) and recompiled the KLD module for FreeBSD 4.0-current. - The pre-compiled KLD module for FreeBSD 4.0-current now includes BPF support, since I have been told that there stubs that should allow BPF-enabled drivers to work even if BPF support isn't compiled into the kernel. - I added a README at http://www.freebsd.org/~wpaul/Adaptec which explains how to install the driver on FreeBSD 2.2.x, 3.x and 4.0. Also, a quick note about the Adaptec cards. I said previously that the Duralink adapters were Adaptec's replacement for their older DEC tulip-based cards. Adaptec still sells multiport adapters based on the 21x4x chip, however I believe they use the 21143 now since Intel discontinued production of the 21140 and supplies are drying up. It is possible that Adaptec may stop production on the older cards though now that they have their own high performance chipset. The Duralink cards may also be preferable in some cases since they are 64-bit PCI devices. Anyway: I would appreciate it if people could test the driver and get back to me with some feedback. I hope to merge this into the -current branch soon. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jul 22 10:36:48 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from paprika.michvhf.com (paprika.michvhf.com [209.57.60.12]) by hub.freebsd.org (Postfix) with SMTP id 1CAED14C02 for ; Thu, 22 Jul 1999 10:36:14 -0700 (PDT) (envelope-from vev@michvhf.com) Received: (qmail 19429 invoked by uid 1001); 22 Jul 1999 17:35:26 -0000 Date: Thu, 22 Jul 1999 13:35:26 -0400 (EDT) From: Vince Vielhaber To: Brian McGroarty Cc: freebsd-hardware , hackers Subject: RE: 1373 sound chip In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 22 Jul 1999, Brian McGroarty wrote: > There's a patch for the 1371 floating around that seems to work for the 1373 > as well. > > Search the archive of FreeBSD-questions for "1371". > > Last I saw, the search page was still confused - you need to put "1371" in > the web search field at the top, but still click the mailing list search > button down below. Found it and applied the patch. Still no go. The 1373 is IDing as a 1371 from BIOS, but FreeBSD doesn't see it at all. Looking at the other messages, I see some folks using 'device pcm0 at nexus?' but they're also running -current. I tried that under 3.2 and after it told me that pcm0 is only good with ISA it seg-faulted and blew core. There was also mention of another patch from Joachim Kuebart for PCI, but no mention where to find it. Vince. > > > > -----Original Message----- > From: Vince Vielhaber [mailto:vev@michvhf.com] > Sent: Wednesday, July 21, 1999 6:54 PM > To: Brian McGroarty; freebsd-hardware; hackers > Subject: 1373 sound chip > > I sent this to multimedia about a week ago and didn't get a response > so I'm trying it here [hackers & hardware] (with minor mods): > > > I'm setting up a new machine that has onboard sound in the form of an > ES1373 Creative (Ensoniq, probably). Visual config shows an unknown > device as ES0 and pcm0 doesn't find anything (tried various forms in > the kernel config for that one, the last one was/is: > > device pcm0 > > Is there any driver for this chip? Under windows it uses the SoundBlaster > AudioPCI 64V driver. So far I haven't found any specs on Creative's or > Ensoniq's website. Can someone shed some light on possibly adapting the > pcm driver to this chip (like how to ID, etc.) ? > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- ========================================================================== Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null # include TEAM-OS2 Online Campground Directory http://www.camping-usa.com Online Giftshop Superstore http://www.cloudninegifts.com ========================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jul 23 11:29:34 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from mc-qout4.whowhere.com (mc-qout4.whowhere.com [209.185.123.18]) by hub.freebsd.org (Postfix) with SMTP id AA230155FE for ; Fri, 23 Jul 1999 11:29:31 -0700 (PDT) (envelope-from virenshah@my-deja.com) Received: from Unknown/Local ([?.?.?.?]) by my-deja.com; Fri Jul 23 11:28:25 1999 To: hardware@freebsd.org Date: Fri, 23 Jul 1999 11:28:25 -0700 From: " " Message-ID: Mime-Version: 1.0 Cc: viren@viren.org X-Sent-Mail: on Reply-To: X-Mailer: MailCity Service Subject: 3.2-stable SCSI caching controller? X-Sender-Ip: 216.112.242.5 Organization: My Deja Email (http://www.my-deja.com:80) Content-Type: text/plain; charset=us-ascii Content-Length: 838 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We currently have a 2.2.6-BETA NFS server which we are planning to upgrade to 3.2-stable. We are looking for a caching SCSI controller (currently it uses the onboard 7880 wide controller). Having looked over the mailing list archives, it seems the FreeBSD only supports the DPT SmartCache IV controllers. Are the drivers for this stable? Am I missing any other controller that can be used with 3.2-stable? The other controller we are looking at is the Adaptec 3950U2 (even though it is not caching). Any advice would be much appreciated. Thanks Viren viren@rstcorp.com [Excuse the mail from my-deja.com, but we just changed IP addresses, and without reverse lookup, majordomo won't accept mail from my domain] --== Sent via Deja.com http://www.deja.com/ ==-- Share what you know. Learn what you don't. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Jul 24 0:37:20 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from serv05.slac.stanford.edu (SERV05.SLAC.Stanford.EDU [134.79.16.135]) by hub.freebsd.org (Postfix) with ESMTP id 84DB414F6C for ; Sat, 24 Jul 1999 00:37:19 -0700 (PDT) (envelope-from svarovsk@SLAC.Stanford.EDU) Received: from smtpserv1.SLAC.Stanford.EDU (SMTPSERV1.SLAC.Stanford.EDU [134.79.16.136]) by SERV05.SLAC.STANFORD.EDU (PMDF V5.2-27 #34067) with ESMTP id <01JDX99PBJ680022XH@SERV05.SLAC.STANFORD.EDU> for freebsd-hardware@freebsd.org; Sat, 24 Jul 1999 00:37:18 PDT Received: from vesta01.SLAC.Stanford.EDU ([134.79.17.11]) by smtpserv1.slac.stanford.edu (PMDF V5.2-29 #34068) with SMTP id <0FFD009NK6I6KE@smtpserv1.slac.stanford.edu> for freebsd-hardware@freebsd.org; Sat, 24 Jul 1999 00:37:18 -0700 (PDT) Date: Sat, 24 Jul 1999 00:37:17 -0700 (PDT) From: Gena Svarovski Subject: wormcontrolfixate error To: freebsd-hardware@freebsd.org Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Content-transfer-encoding: 7BIT Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I've recently bought Yamaha 4416E CD-RW drive and now trying to make write disks (reading works fine). I've managed to work out sequence of commands to prepare audio tracks and write them to CD. But I can't write data CDs. wormcontrol always reports an error when I'm trying to fixate disk: wormcontrol: ioctl(WORMIOFIXATION): Invalid argument It even reports same error when disk is not in drive. It seem that ioctl for fixation returns error but I have no idea for what reason. Here is a script I'm using: #!/bin/sh device=/dev/racd0c image=$1 wormcontrol -f $device prepdisk double wormcontrol -f $device track data dd if=$image of=$device bs=20k wormcontrol -f $device fixate 1 onp After dd completes everything is actually already written on disk. And I can read data I've just written on it without problems. But without closing session other CD-ROMs cannot access it. I'm sure I'm missing something simple but playing with this for couple days and searching mailing list archives didn't help. I'm running 3.2-STABLE. Regards, Gena To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Jul 24 11: 2:30 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (Postfix) with ESMTP id D835C14DD4 for ; Sat, 24 Jul 1999 11:02:26 -0700 (PDT) (envelope-from nsouch@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.3/8.9.3) with ESMTP id TAA01126; Sat, 24 Jul 1999 19:26:22 +0200 (MET DST) Received: (from nsouch@localhost) by teaser.fr (8.9.3/8.9.1) id SAA02314; Sat, 24 Jul 1999 18:08:24 +0200 (CEST) (envelope-from nsouch) Message-ID: <19990724180824.18086@breizh.teaser.fr> Date: Sat, 24 Jul 1999 18:08:24 +0200 From: Nicolas Souchu To: dgilbert@velocet.ca Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: smbus not quite right? References: <199907190324.XAA08403@strike.velocet.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199907190324.XAA08403@strike.velocet.ca>; from dgilbert@velocet.ca on Sun, Jul 18, 1999 at 11:24:05PM -0400 X-Operating-System: FreeBSD breizh 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Jul 18, 1999 at 11:24:05PM -0400, dgilbert@velocet.ca wrote: > >I have a machine with a P5A motherboard, which probes as follows: > >pcf0: >iicbus0: on pcf0 addr 0xaa >iicsmb0: on iicbus0 >smbus0: on iicsmb0 >smb0: on smbus0 >iic0: on iicbus0 > >Now... If I run mbmon in ISA mode, which opens /dev/io, it works. If >I run it in in smbus mode, which opens /dev/smb0, it fails. Having >read the documentation on /dev/io, I'd rather not have that ability on >a server... I would guess that it requires an insecure level. Whats mbmon? You have actually a Philips PCF8584 connected to your ISA bus? > >So... any ideas? > >Dave. > >-- > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hardware" in the body of the message > -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Jul 24 22:26:40 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from serv05.slac.stanford.edu (SERV05.SLAC.Stanford.EDU [134.79.16.135]) by hub.freebsd.org (Postfix) with ESMTP id B6E2214D2A for ; Sat, 24 Jul 1999 22:26:38 -0700 (PDT) (envelope-from svarovsk@SLAC.Stanford.EDU) Received: from smtpserv1.SLAC.Stanford.EDU (SMTPSERV1.SLAC.Stanford.EDU [134.79.16.136]) by SERV05.SLAC.STANFORD.EDU (PMDF V5.2-27 #34067) with ESMTP id <01JDYJ00L6RC0026CR@SERV05.SLAC.STANFORD.EDU> for freebsd-hardware@freebsd.org; Sat, 24 Jul 1999 22:26:37 PDT Received: from vesta01.SLAC.Stanford.EDU ([134.79.17.11]) by smtpserv1.slac.stanford.edu (PMDF V5.2-29 #34068) with SMTP id <0FFE001B1V4DQ7@smtpserv1.slac.stanford.edu> for freebsd-hardware@freebsd.org; Sat, 24 Jul 1999 22:26:37 -0700 (PDT) Date: Sat, 24 Jul 1999 22:26:34 -0700 (PDT) From: Gena Svarovski Subject: Re: wormcontrolfixate error In-reply-to: To: freebsd-hardware@freebsd.org Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Content-transfer-encoding: 7BIT Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I thought it is clear but it seems it's not so. I have EIDE version of CD-RW. I found one solution but I don't like it. Easy CD Creator 3.5 for Windows when sees my CD on which fixate command failed suggests to close session and does it successfully. After this I can use this CD anywhere. So, it seems the problem is not with hardware but with incorrect use of this hardware. Any clues? Gena On Sat, 24 Jul 1999, Gena Svarovski wrote: > Hello, > > I've recently bought Yamaha 4416E CD-RW drive and now trying to make write > disks (reading works fine). I've managed to work out sequence of commands > to prepare audio tracks and write them to CD. But I can't write data CDs. > wormcontrol always reports an error when I'm trying to fixate disk: > > wormcontrol: ioctl(WORMIOFIXATION): Invalid argument > > It even reports same error when disk is not in drive. > It seem that ioctl for fixation returns error but I have no idea for what > reason. Here is a script I'm using: > > #!/bin/sh > > device=/dev/racd0c > image=$1 > > wormcontrol -f $device prepdisk double > wormcontrol -f $device track data > dd if=$image of=$device bs=20k > wormcontrol -f $device fixate 1 onp > > After dd completes everything is actually already written on disk. And I > can read data I've just written on it without problems. But without > closing session other CD-ROMs cannot access it. > > I'm sure I'm missing something simple but playing with this for couple > days and searching mailing list archives didn't help. > > I'm running 3.2-STABLE. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message