From owner-freebsd-scsi Sun Feb 3 20: 3:51 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.visi.com (msp-65-30-224-230.mn.rr.com [65.30.224.230]) by hub.freebsd.org (Postfix) with ESMTP id D164237B419; Sun, 3 Feb 2002 20:03:42 -0800 (PST) Received: (from hrp@localhost) by mail.visi.com (8.11.3/8.11.3) id g1443a200921; Sun, 3 Feb 2002 22:03:36 -0600 (CST) (envelope-from hrp) From: Hal Peterson MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15454.2071.788157.885858@localhost.pinemarten.org.pri> Date: Sun, 3 Feb 2002 22:03:35 -0600 To: freebsd-questions@freebsd.org, freebsd-scsi@freebsd.org Subject: Microtech CameraMate has two LUNs. Now what? X-Mailer: VM 7.00 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hoping for help getting a USB interface to SmartMedia working. I get ENXIO when I try to mount the SmartMedia as a filesystem. Here are the gory details. I have a kernel built from fresh RELENG_4 sources: FreeBSD melchett.pinemarten.org.pri 4.5-STABLE FreeBSD 4.5-STABLE #1: Sun Feb 3 16:35:37 CST 2002 hrp@melchett.pinemarten.org.pri:/usr/src/sys/compile/MELCHETT i386 I made a cvsup copy of the source tree yesterday, so it's quite recent. The first problem was to recognize the CameraMate as a umass device. That took a patch to umass_match_proto (stolen from the freebsd-scsi archive), so: ================================================================ --- umass.c.bak Sun Feb 3 16:31:27 2002 +++ umass.c Sun Feb 3 16:35:26 2002 @@ -629,6 +629,15 @@ umass_match_proto(struct umass_softc *sc return(UMATCH_VENDOR_PRODUCT); } + if (UGETW(dd->idVendor) == USB_VENDOR_MICROTECH + && UGETW(dd->idProduct) == USB_PRODUCT_MICROTECH_DPCM) { + /* the cameramate does not provide valid + class/subclass information. fake it. */ + sc->proto = PROTO_SCSI | PROTO_CBI; + sc->quirks |= NO_TEST_UNIT_READY | NO_START_STOP; + return(UMATCH_VENDOR_PRODUCT); + } + id = usbd_get_interface_descriptor(iface); if (id == NULL || id->bInterfaceClass != UCLASS_MASS) return(UMATCH_NONE); ================================================================ When I boot with the CameraMate attached, the right things appear to happen: uhci0: port 0x1080-0x109f irq 9 at device 7.2 on pci0 usb0: 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 umass0: Microtech International, Inc DPCM-USB, rev 1.00/1.00, addr 2 uhid0: WACOM ET-0405-UV1.1-1, rev 1.00/1.11, addr 3, iclass 3/1 That agrees with usbdevs -v: Controller /dev/usb0: addr 1: self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 0x0100 port 1 addr 2: power 100 mA, config 1, DPCM-USB(0x0006), Microtech International, Inc(0x07af), rev 0x0100 port 2 addr 3: low speed, power 40 mA, config 1, ET-0405-UV1.1-1(0x0010), WACOM(0x056a), rev 0x0111 and camcontrol devlist agrees: at scbus0 target 0 lun 0 (pass0,da0) Trouble appears when I try "mount -t msdos /dev/da0 /mnt": msdos: /dev/da0: Device not configured the console bleats: (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): NOT READY asc:3a,0 (da0:umass-sim0:0:0:0): Medium not present That is not true; I have an 8MB SmartMedia card plugged in. ================================================================ Here's what I think is going on. When I plug the CameraMate into a box running W2K, it shows up as *two* drives: the first one for the CompactFlash slot on the CameraMate, the second for the SmartMedia slot. When I read the drive properties with W2K, it tells me that the CompactFlash is (ScsiPort 2 Target 0 Lun 0), and that the SmartMedia is (ScsiPort 2 Target 0 Lun 1). Can it be that the umass driver is only reporting the first LUN, so the SmartMedia slot is invisible? If so, what do I do to fix it? Do I need to hack umass_bbb_get_max_lun? -- Hal Peterson Bloomington, MN, USA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Feb 3 21:55:50 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 53C0A37B41D; Sun, 3 Feb 2002 21:55:45 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.11.4/8.11.4) id g145tff22191; Mon, 4 Feb 2002 00:55:41 -0500 (EST) (envelope-from wollman) Date: Mon, 4 Feb 2002 00:55:41 -0500 (EST) From: Garrett Wollman Message-Id: <200202040555.g145tff22191@khavrinen.lcs.mit.edu> To: jordan.breeding@attbi.com Cc: freebsd-current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Support for atapi cdrw as scsi in -current? In-Reply-To: <20020202201020.EWNX26243.rwcrmhc51.attbi.com@rwcrwbc57> References: <20020202201020.EWNX26243.rwcrmhc51.attbi.com@rwcrwbc57> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org < I noticed a patch on freebsd-scsi a while back that > added a not very complete form of atapi as scsi support > to the freebsd kernel. Are there plans to complete > this and add it to -current sometime before -current > turns into 5.0-RELEASE? Thanks for any information. I've been using it somewhat actively in the past week or so in -current. The patch as it exists needs a few changes to fit in current -current. $ camcontrol devlist at scbus0 target 0 lun 0 (cd0,pass0) at scbus0 target 1 lun 0 (cd1,pass1) I don't think that ATAPICAM works well enough to use it entirely in place of the atapi-cd driver; for example, I get the following errors: atapicam0: READ_DISK_INFO - ILLEGAL REQUEST asc=0x20 ascq=0x00 error=0x04 atapicam0: READ_TOC - ILLEGAL REQUEST asc=0x24 ascq=0x00 error=0x04 However, it works well-enough to run cdrdao, which is what mattered to me, for both reading and writing on both of the afore-mentioned ATAPI devices. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 5 10:49:48 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from ledzep.dyndns.org (12-237-133-3.client.attbi.com [12.237.133.3]) by hub.freebsd.org (Postfix) with ESMTP id A5ACF37B47D; Tue, 5 Feb 2002 10:49:11 -0800 (PST) Received: from attbi.com (root@localhost.dyndns.org [127.0.0.1]) by ledzep.dyndns.org (8.11.6/8.11.6) with ESMTP id g15In6r96946; Tue, 5 Feb 2002 12:49:07 -0600 (CST) (envelope-from jordan.breeding@attbi.com) Message-ID: <3C602922.2020400@attbi.com> Date: Tue, 05 Feb 2002 12:49:06 -0600 From: Jordan Breeding User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:0.9.7) Gecko/20011221 X-Accept-Language: en-us MIME-Version: 1.0 To: Garrett Wollman Cc: freebsd-current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Support for atapi cdrw as scsi in -current? References: <20020202201020.EWNX26243.rwcrmhc51.attbi.com@rwcrwbc57> <200202040555.g145tff22191@khavrinen.lcs.mit.edu> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Garrett Wollman wrote: > < > >>I noticed a patch on freebsd-scsi a while back that >>added a not very complete form of atapi as scsi support >>to the freebsd kernel. Are there plans to complete >>this and add it to -current sometime before -current >>turns into 5.0-RELEASE? Thanks for any information. >> > > I've been using it somewhat actively in the past week or so in > -current. The patch as it exists needs a few changes to fit in > current -current. > > $ camcontrol devlist > at scbus0 target 0 lun 0 (cd0,pass0) > at scbus0 target 1 lun 0 (cd1,pass1) > > I don't think that ATAPICAM works well enough to use it entirely in > place of the atapi-cd driver; for example, I get the following errors: > > atapicam0: READ_DISK_INFO - ILLEGAL REQUEST asc=0x20 ascq=0x00 error=0x04 > atapicam0: READ_TOC - ILLEGAL REQUEST asc=0x24 ascq=0x00 error=0x04 > > However, it works well-enough to run cdrdao, which is what mattered to > me, for both reading and writing on both of the afore-mentioned ATAPI > devices. > > -GAWollman > > > Is there a place where I can find this updated patch which will work for me in the current -current? Thanks. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 5 11:14:39 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from melchior.cuivre.fr.eu.org (melchior.enst.fr [137.194.161.6]) by hub.freebsd.org (Postfix) with ESMTP id DBB1837B419; Tue, 5 Feb 2002 11:14:33 -0800 (PST) Received: from melusine.cuivre.fr.eu.org (melusine.enst.fr [137.194.160.34]) by melchior.cuivre.fr.eu.org (Postfix) with ESMTP id A5FB282C4; Tue, 5 Feb 2002 20:14:26 +0100 (CET) Received: by melusine.cuivre.fr.eu.org (Postfix, from userid 1000) id 3E7502C3D1; Tue, 5 Feb 2002 20:14:22 +0100 (CET) Date: Tue, 5 Feb 2002 20:14:22 +0100 From: Thomas Quinot To: Garrett Wollman Cc: freebsd-current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG, sam@inf.enst.fr Subject: Re: Support for atapi cdrw as scsi in -current? Message-ID: <20020205201422.A24340@melusine.cuivre.fr.eu.org> Reply-To: thomas@cuivre.fr.eu.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > Is there a place where I can find this updated patch which will work for > me in the current -current? Thanks. I put up updated patches at http://www.cuivre.fr.eu.org/~thomas/atapicam/ For -CURRENT, you should be using the latest one (of today) which fixes a silly line inversion. I'd be very interested in success/failuire reports on this patch, especially with ATAPI tape or floppy drives. Thomas. -- Thomas.Quinot@Cuivre.FR.EU.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Feb 6 5: 2:12 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by hub.freebsd.org (Postfix) with ESMTP id 8AADD37B420; Wed, 6 Feb 2002 05:02:03 -0800 (PST) Received: from heho.snv.jussieu.fr (heho.snv.jussieu.fr [134.157.37.22]) by shiva.jussieu.fr (8.12.1/jtpda-5.4) with ESMTP id g16D22YD035579 ; Wed, 6 Feb 2002 14:02:02 +0100 (CET) Received: from (arno@localhost) by heho.snv.jussieu.fr (8.11.6/jtpda-5.2) id g16D22D13459 ; Wed, 6 Feb 2002 14:02:02 +0100 (MET) To: freebsd-stable@freebsd.org Cc: freebsd-scsi@freebsd.org Subject: Problem reading (and writing ...) Rewriteable CDs From: arno@heho.snv.jussieu.fr Date: 06 Feb 2002 14:02:02 +0100 Message-ID: Lines: 83 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, ehmm, am I the only one who sees this problem (since end November): I cannot mount, let alone burn, rewriteable CDs on -stable boxes (two) with adaptec SCSI-controller (one 1542, the other 2940) and SCSI-2 cd-writers. Recordable CDs read and write without any problem, changes settings in the Adaptec BIOS do not seem to make any difference. step 1, put (Windows created) CDRW in cd-writer: su-2.05a# mount_cd9660 -v /dev/cd1c /cdrom could not determine starting sector, using very first session mount_cd9660: /dev/cd1c: Device not configured step 2, put very same CDRW in cd-reader on very same machine: su-2.05a# mount_cd9660 -v /dev/cd0c /cdrom using starting sector 0 su-2.05a# ls /cdrom cd su-2.05a# step 3, put a CDR in cdwriter: su-2.05a# mount_cd9660 -v /dev/cd1c /cdw=20=20 using starting sector 0 su-2.05a# ls -l /cdw total 1 -r-xr-xr-x 1 root wheel 3728 May 1 1997 readme.txt If this helps, this is the output when trying to blank a CDRW: su-2.05a# cdrecord -v dev=3D6,0 speed=3D1 blank=3Dfast Cdrecord 1.10 (i386-unknown-freebsd4.5) Copyright (C) 1995-2001 J=F6rg Sc= hilling TOC Type: 1 =3D CD-ROM scsidev: '6,0' scsibus: 0 target: 6 lun: 0 Using libscg version 'schily-0.5' atapi: 0 Device type : Removable CD-ROM Version : 2 Response Format: 2 Capabilities : RELADR SYNC LINKED=20 Vendor_info : 'TEAC ' Identifikation : 'CD-R55S ' Revision : '1.0F' Device seems to be: Teac CD-R50S. Using driver for Teac CD-R50S, Teac CD-R55S, JVC XR-W2010, Pinnacle RCD-5= 020 (teac_cdr50). Driver flags : SWABAUDIO cdrecord: Input/output error. test unit ready: scsi sendcmd: retryable er= ror CDB: 00 00 00 00 00 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 3A 00 00 00 00 00 00 00 = 00 00 00 00 00 00 00 00 00 00 00 00 Sense Key: 0x2 Not Ready, Segment 0 Sense Code: 0x3A Qual 0x00 (medium not present) Fru 0x0 Sense flags: Blk 0 (not valid)=20 cmd finished after 0.005s timeout 40s cdrecord: No disk / Wrong disk! The other machine wich exhibits this behaviour, has a YAMAHA CRW4416S 1.0f = cdwriter (and both of them work correctly for CDRWs until end November). Any help, suggestions are appreciated. One of the machines is a production = box, but the other is halted almost every evening and I can easily test a patched ke= rnel. Thanx in advance, Arno Klaassen --=20 Arno J. Klaassen SCITO S.A. Le Grand Sablon 4, avenue de l'Obiou 38700 La Tronche arno@ccr.jussieu.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Feb 6 7:47:36 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by hub.freebsd.org (Postfix) with ESMTP id C708C37B421; Wed, 6 Feb 2002 07:47:31 -0800 (PST) Received: from heho.snv.jussieu.fr (heho.snv.jussieu.fr [134.157.37.22]) by shiva.jussieu.fr (8.12.1/jtpda-5.4) with ESMTP id g16FlUYD083366 ; Wed, 6 Feb 2002 16:47:30 +0100 (CET) Received: from (arno@localhost) by heho.snv.jussieu.fr (8.11.6/jtpda-5.2) id g16FlUJ14037 ; Wed, 6 Feb 2002 16:47:30 +0100 (MET) To: freebsd-stable@FreeBSD.ORG Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Problem reading (and writing ...) Rewriteable CDs References: From: arno@heho.snv.jussieu.fr Date: 06 Feb 2002 16:47:29 +0100 In-Reply-To: Message-ID: Lines: 6 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org sorry, I forgot: supplementary info: a *virgin* CDRW can perfectly well being burned. Arno To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Feb 6 11:50:10 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 3B34F37B41A for ; Wed, 6 Feb 2002 11:50:06 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id UAA04594 for freebsd-scsi@freebsd.org; Wed, 6 Feb 2002 20:50:05 +0100 (CET) Received: (from j@localhost) by uriah.heep.sax.de (8.11.6/8.11.6) id g16JhS424008; Wed, 6 Feb 2002 20:43:28 +0100 (MET) (envelope-from j) Date: Wed, 6 Feb 2002 20:43:28 +0100 (MET) Message-Id: <200202061943.g16JhS424008@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: From: j@uriah.heep.sax.de (Joerg Wunsch) Subject: Re: Problem reading (and writing ...) Rewriteable CDs X-Original-Newsgroups: local.freebsd.scsi To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org arno@heho.snv.jussieu.fr wrote: > su-2.05a# mount_cd9660 -v /dev/cd1c /cdrom > could not determine starting sector, using very first session > mount_cd9660: /dev/cd1c: Device not configured Hmm, are there any syslog messages about this? > cdrecord: Input/output error. test unit ready: scsi sendcmd: retryable error > CDB: 00 00 00 00 00 00 > status: 0x2 (CHECK CONDITION) > Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 3A 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > Sense Key: 0x2 Not Ready, Segment 0 > Sense Code: 0x3A Qual 0x00 (medium not present) Fru 0x0 The drive probably "went off for lunch" after some other command. You need a full traceback of the SCSI commands sent to the drive, plus a SCSI reference manual for it. I once had a similar problem with my old Plasmon writer, which then needed a patch (patch-ai in cdrtools) in order to prevent cdrecord from issuing something to the drive the drive didn't understand. The other option is that whatever already caused the above read error, has also caused the cdrecord "not ready" problem later. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 7 3:18:33 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.nsu.ru (mx.nsu.ru [193.124.215.71]) by hub.freebsd.org (Postfix) with ESMTP id 6D73D37B41D; Thu, 7 Feb 2002 03:18:05 -0800 (PST) Received: from iclub.nsu.ru ([193.124.215.97] ident=root) by mail.nsu.ru with esmtp (Exim 3.20 #1) id 16YmXn-0003pM-00; Thu, 07 Feb 2002 17:16:47 +0600 Received: (from fjoe@localhost) by iclub.nsu.ru (8.11.6/8.11.6) id g17BGes08115; Thu, 7 Feb 2002 17:16:40 +0600 (NS) (envelope-from fjoe) Date: Thu, 7 Feb 2002 17:16:39 +0600 From: Max Khon To: Thomas Quinot Cc: Garrett Wollman , freebsd-current@freebsd.org, freebsd-scsi@freebsd.org, sam@inf.enst.fr Subject: Re: Support for atapi cdrw as scsi in -current? Message-ID: <20020207171639.A7595@iclub.nsu.ru> References: <20020205201422.A24340@melusine.cuivre.fr.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020205201422.A24340@melusine.cuivre.fr.eu.org>; from thomas@cuivre.fr.eu.org on Tue, Feb 05, 2002 at 08:14:22PM +0100 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org hi, there! On Tue, Feb 05, 2002 at 08:14:22PM +0100, Thomas Quinot wrote: > > Is there a place where I can find this updated patch which will work for > > me in the current -current? Thanks. > > I put up updated patches at > http://www.cuivre.fr.eu.org/~thomas/atapicam/ > > For -CURRENT, you should be using the latest one (of today) > which fixes a silly line inversion. > > I'd be very interested in success/failuire reports on this patch, > especially with ATAPI tape or floppy drives. I successfully recorded data cd using cdrecord on NEC NR-7700A IDE CD-RW. dmesg follows Copyright (c) 1992-2002 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.5-STABLE #0: Thu Feb 7 04:49:06 NS 2002 fjoe@husky.fjoe.org:/usr/obj/usr/fbsd/RELENG_4/src/sys/husky Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K7(tm) Processor (503.53-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x612 Stepping = 2 Features=0x81f9ff AMD Features=0xc0400000 real memory = 268369920 (262080K bytes) config> enable apm0 config> quit avail memory = 256040960 (250040K bytes) Preloaded elf kernel "kernel" at 0xc04af000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc04af09c. Preloaded elf module "if_ppp.ko" at 0xc04af0ec. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 7 entries at 0xc00f82b0 apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 5.0 irq 11 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xcc00-0xcc1f irq 12 at device 4.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xd000-0xd01f irq 12 at device 4.3 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered chip1: at device 4.4 on pci0 pci0: (vendor=0x1274, dev=0x1371) at 13.0 irq 11 ed0: port 0xc400-0xc41f irq 5 at device 14.0 on pci0 ed0: address 00:00:01:00:fb:08, type NE2000 (16 bit) sym0: <810a> port 0xd800-0xd8ff mem 0xefffff00-0xefffffff irq 10 at device 15.0 on pci0 sym0: No NVRAM, ID 7, Fast-10, SE, parity checking orm0: