From owner-freebsd-hardware Mon Jan 14 12:18:27 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from uky.edu (smtp.uky.edu [128.163.2.127]) by hub.freebsd.org (Postfix) with ESMTP id CCB2837B41C for ; Mon, 14 Jan 2002 12:18:25 -0800 (PST) Received: from uky.edu abmurr0@uky.edu [65.7.71.21] by uky.edu with Novell NIMS $Revision: 2.88 $ on Novell NetWare; Mon, 14 Jan 2002 15:16:09 -0500 Message-ID: <3C433D0E.C662DACB@uky.edu> Date: Mon, 14 Jan 2002 15:18:22 -0500 From: Alek B Murray Reply-To: abmurr0@uky.edu X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.5-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Subject: Logitech Quickcam Express USB Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I have a Logitech Quickcam Express USB that i've noticed now has a driver in usbdevs...but I'm unsure how to get it working with any h323 programs. Does anyone have a play by play to get it to work? I'm currently running 4.5-RC if that helps. I'm quite sure i'll have to do some work in /dev and that's mainly what i need help with. Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jan 15 6:15:22 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mpehp1.mpe-garching.mpg.de (mpehp1.mpe-garching.mpg.de [130.183.70.10]) by hub.freebsd.org (Postfix) with ESMTP id 812C237B405; Tue, 15 Jan 2002 06:15:16 -0800 (PST) Received: from robert2.mpe-garching.mpg.de (robert2.mpe-garching.mpg.de [130.183.136.59]) by mpehp1.mpe-garching.mpg.de (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id PAA19509; Tue, 15 Jan 2002 15:15:15 +0100 (MET) Received: (from sutter@localhost) by robert2.mpe-garching.mpg.de (8.11.6/8.11.6) id g0FEFnh03295; Tue, 15 Jan 2002 15:15:49 +0100 (CET) (envelope-from sutter) Date: Tue, 15 Jan 2002 15:15:49 +0100 From: Robert Suetterlin To: freebsd-questions@FreeBSD.ORG Cc: freebsd-hardware@FreeBSD.ORG Subject: CPQ ML350. Boot Hangs during Installation. Updated Problem Report. Message-ID: <20020115141549.GA3257@robert2.mpe-garching.mpg.de> References: <20020111150745.GE159@robert2.mpe-garching.mpg.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020111150745.GE159@robert2.mpe-garching.mpg.de> User-Agent: Mutt/1.3.24i Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello Again! Found some time to do more testing... So. I have the Promise Ultra100 TX2 (bios 2.12) connected to a PCI Slot which allows it to work at least under some conditions. Connected to Promise Controller are four IBM ATA 100 harddisks. The System it is plugged in is a COMPAQ Proliant ML350. The Bios of the Server states no IRQ conficts. I start the inital boot of the FreeBSD installation (FBSD4.4REL) with no special parameters, during visual configuration of the kernel I remove everything from Network, everything but fdc from Storage and PC-Card from Misc. The boot process ends with 'plip0: on ppbus0' while still in bright text mode. Then the machine hangs. I can boot ok if I remove either the drives connected to ata-interface 1 or 2 of the promise controller (these are ata-2 and ata-3 for my freebsd kernel). If I have anything connected to both ata-interfaces of the controller the boot hangs. If I have only stuff on one interface (no matter which of the two, but only one) the the system boots ok. BTW the harddrives I use are IBM IC35L040AVER07-0 (40Gig). The Chipset of the COMPAQ is a ServerWorks (don't know more specific). When the system boots ok (using only one channel of the promise controller) the next message in dmesg after plip0: is 'ad4 39266MB ... at ata2-master UDMA100'. Then there is one more for the second harddrive, then acd0 at ata0-slave, and finally 'Mounting root from ufs:/dev/md0c'. If anyone knows how I can get my second ata-channel working _please_ tell me. Or if there is any additional diagnostic I can apply. Regards, Robert S. -- Robert Suetterlin (robert@mpe.mpg.de) phone: (+49)89 / 30000-3546 fax: (+49)89 / 30000-3950 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jan 15 12:23:13 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mpehp1.mpe-garching.mpg.de (mpehp1.mpe-garching.mpg.de [130.183.70.10]) by hub.freebsd.org (Postfix) with ESMTP id 7535F37B416; Tue, 15 Jan 2002 12:23:07 -0800 (PST) Received: from robert2.mpe-garching.mpg.de (robert2.mpe-garching.mpg.de [130.183.136.59]) by mpehp1.mpe-garching.mpg.de (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id VAA20345; Tue, 15 Jan 2002 21:23:06 +0100 (MET) Received: (from sutter@localhost) by robert2.mpe-garching.mpg.de (8.11.6/8.11.6) id g0FKNfn04258; Tue, 15 Jan 2002 21:23:41 +0100 (CET) (envelope-from sutter) Date: Tue, 15 Jan 2002 21:23:41 +0100 From: Robert Suetterlin To: freebsd-questions@FreeBSD.ORG Cc: freebsd-hardware@FreeBSD.ORG Subject: Solved ?!? (was: CPQ ML350. Boot Hangs during Installation. Updated Problem Report.) Message-ID: <20020115202341.GK3257@robert2.mpe-garching.mpg.de> References: <20020111150745.GE159@robert2.mpe-garching.mpg.de> <20020115141549.GA3257@robert2.mpe-garching.mpg.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020115141549.GA3257@robert2.mpe-garching.mpg.de> User-Agent: Mutt/1.3.24i Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I 'solved' the Problem (?). I followed a hint in one replies (above) to install FreeBSD 4.4-Release on a single Hardrive and the upgrade to 4.4-Stable (in my case 4.5-RC) because there have been some patches to the ata driver inbetween these releases. I did it and when I reboot with a custom 4.5-RC kernel I can attach all four drives to the promise controller without hanging the system any longer. Unfortunately I do not know what caused the problem in the first place (i.e. a buggy driver that got patched, or a bad system setup that got repaired by the improved ata driver ...) and feel a little alarmed. BTW the driver works great. It delivers some 37MByte per second to a single Hardrive --- writing to a ufs filesystem --- which is close to the limit of what the IBMs can support. I was almost convinced that I should shun IDE for the rest of my life, unfortunately the ata drivers of FBSD developed a little to quickly. Sincerely, Robert S. -- Robert Suetterlin (robert@mpe.mpg.de) phone: (+49)89 / 30000-3546 fax: (+49)89 / 30000-3950 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jan 15 16: 8:46 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from prohosters.com (calcium.4ph.com [66.197.0.121]) by hub.freebsd.org (Postfix) with SMTP id 9EDC137B41A for ; Tue, 15 Jan 2002 16:08:37 -0800 (PST) Received: (qmail 41666 invoked from network); 15 Jan 2002 19:08:31 -0500 Received: from unknown (HELO laptop) (128.121.6.5) by 66.197.0.9 with SMTP; 15 Jan 2002 19:08:31 -0500 Message-ID: <04fc01c19e22$2974c640$6401a8c0@laptop> From: "Theodore D. Hickman Jr." To: Subject: Intel Ethernet Express Pro problem Date: Tue, 15 Jan 2002 19:10:10 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_04F9_01C19DF8.40834700" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_04F9_01C19DF8.40834700 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi,=20 My name is Ted Hickman and I run a company called ProHosters. I use = FreeBSD on all my machines. Just recently when i cvsuped to 4.4-STABLE = and now 4.5-RC fxp0 drivers have started at different intervals producing this error = message: fxp0: SCB timeout: 0x80 0x0 0x50 0x400 fxp0: SCB timeout: 0x80 0x0 0x50 0x400 fxp0: SCB timeout: 0x80 0x0 0x50 0x400 fxp0: SCB timeout: 0x80 0x0 0x50 0x400 fxp0: SCB timeout: 0x80 0x0 0x50 0x400 fxp0: SCB timeout: 0x80 0x0 0x50 0x400 fxp0: SCB timeout: 0x80 0x0 0x50 0x400 fxp0: SCB timeout: 0x80 0x0 0x50 0x400 fxp0: SCB timeout: 0x80 0x0 0x50 0x400 fxp0: SCB timeout: 0x80 0x0 0x50 0x400 fxp0: SCB timeout: 0x80 0x0 0x50 0x400 fxp0: SCB timeout: 0x80 0x0 0x50 0x400 fxp0: device timeout The box will issue these errors for about 20 seconds and then go back to = normal. The box for those 20 seconds is down. I greatly appreciate all = the work you do on the FreeBSD hardware side and would like to know as soon as possible = whether I should downgrade to 4.4-REL or there is some other answer. = This is happening on multiple machines on my network. Thank you for your attention to my = letter and please respond at your convience. Theodore D. Hickman Jr. President/CEO Pro Hosters L.L.C. ------=_NextPart_000_04F9_01C19DF8.40834700 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
    My name is Ted = Hickman and I run=20 a company called ProHosters.  I use FreeBSD on all my = machines.  Just=20 recently when i cvsuped to 4.4-STABLE and now 4.5-RC
fxp0 drivers have started at different = intervals=20 producing this error message:
 
fxp0: SCB timeout: 0x80 0x0 0x50 = 0x400
fxp0: SCB=20 timeout: 0x80 0x0 0x50 0x400
fxp0: SCB timeout: 0x80 0x0 0x50 = 0x400
fxp0:=20 SCB timeout: 0x80 0x0 0x50 0x400
fxp0: SCB timeout: 0x80 0x0 0x50=20 0x400
fxp0: SCB timeout: 0x80 0x0 0x50 0x400
fxp0: SCB timeout: = 0x80 0x0=20 0x50 0x400
fxp0: SCB timeout: 0x80 0x0 0x50 0x400
fxp0: SCB = timeout: 0x80=20 0x0 0x50 0x400
fxp0: SCB timeout: 0x80 0x0 0x50 0x400
fxp0: SCB = timeout:=20 0x80 0x0 0x50 0x400
fxp0: SCB timeout: 0x80 0x0 0x50 0x400
fxp0: = device=20 timeout
The box will issue these errors for = about 20=20 seconds and then go back to normal.  The box for those 20 seconds = is=20 down.  I greatly appreciate all the work you do
on the FreeBSD hardware side and would = like to know=20 as soon as possible whether I should downgrade to 4.4-REL or there is = some other=20 answer.  This is happening
on multiple machines on my = network.  Thank you=20 for your attention to my letter and please respond at your=20 convience.
 
 
Theodore D. Hickman Jr.
President/CEO
Pro Hosters = L.L.C.
 
------=_NextPart_000_04F9_01C19DF8.40834700-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jan 15 18:46:11 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from walter.dfmm.org (walter.dfmm.org [209.151.233.240]) by hub.freebsd.org (Postfix) with ESMTP id C8BE937B404 for ; Tue, 15 Jan 2002 18:45:54 -0800 (PST) Received: (qmail 36824 invoked by uid 1008); 16 Jan 2002 02:45:47 -0000 Date: Tue, 15 Jan 2002 18:45:47 -0800 From: Ryan Clancey To: freebsd-hardware@FreeBSD.ORG Subject: Re: cd/dvd drive problems Message-ID: <20020115184547.A36568@dfmm.org> 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: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org alright, so i made some progress. it was suggested to me that the problem might be not enough power getting to the device (which seemed like a good possibility, given that i already have 5 other drives sucking power). so i unplugged four drives, leaving only my boot drive and the dvd. no difference. i played around some with the configuration, and found that if i plugged the dvd drive into one of my promise ide cards, it got further before it failed. that got me to thinking that the problem might be in hardware. sure enough, i found some posts indicating that the ide chipset on my motherboard (via 686) has bugs. so, that solves the first problem i had (READ_DVD_STRUCTURE command timeout). this was showing up while ogle was trying to authenticate the disc. now that part appears to work, but then it fails while trying to send the video to the screen. ogle says: using MMX for yuv2rgb conversion Debug[ogle_vout]: resize: 836, 480 #!##!#!!!!!#!#!#!!demux: *** Lost Sync demux: *** at offset: 153612 bytes demux: Lost sync, resyncing Note[ogle_a52]: resetting offset Debug[ogle_a52]: a52_block() error Debug[ogle_a52]: A/52 error while decoding, restarting and sometime later, the kernel says: acd0: READ_BIG command timeout - resetting acd0: read data overrun 12288/0 acd0: read data overrun 32768/0 acd0: read data overrun 6144/0 so, i'm getting the feeling this is all due to bad hardware. especially, since the drive works fine on another machine with the same kernel and software. i'd really rather not have to replace the motherboard, but i could tolerate replacing/adding an ide card, if i thought that would do the trick. anyone have advice on this? thanks -ryan > -----Original Message----- > From: owner-freebsd-hardware@FreeBSD.ORG > [mailto:owner-freebsd-hardware@FreeBSD.ORG] On Behalf Of Ryan Clancey > Sent: 07 January 2002 10:02 > To: freebsd-hardware@FreeBSD.ORG > Subject: cd/dvd drive problems > > > i have a freebsd-4.4 box that refuses to play nice with atapi > devices. two > cdroms have failed to rip audio tracks, a cdr/rw failed to > rip audio and > failed to write write a disc (fixate failed in burncd) and > now i can't get > a dvd drive to do css key exchange. in each case, the kernel > reports the > following error: > > acd0: [COMMAND] command timeout - resetting > ata1: resetting devices .. done > > this message gets repeated over and over, until the program > trying to access > the device gives up. (if i kill the offending program, the > system keeps > trying on it's own, blocking all other processes, effectively > hanging the > machine.) > > each of these devices works on a different freebsd-4.4 > machine, and the hard > disks all seem to work fine. the only major difference > between the two > machines, is the problem machine has four drives attached to > two promise ide > cards. (the boot disk and the atapi drives are connected to > the on board > ide controllers.) however, i've tried diconnecting the > promise-controlled > drives to no avail. > > so, does anyone out there have any suggestions on fixing > this? is it a > hardware problem, a kernel configuration problem, or a bug? > sorry if this has > already been addressed on the mailing lists, but i couldn't > find anything > that seemed relevant and helpful. > > -ryan clancey > > -------------------------------------------------------------- > ----------------- > dmesg from boot -v follows: > > 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-STABLE #0: Mon Oct 29 22:02:15 PST 2001 > root@fattire.craplab.home:/usr/obj/usr/src/sys/FILESERV > Calibrating clock(s) ... TSC clock: 866643123 Hz, i8254 > clock: 1193106 Hz > CLK_USE_I8254_CALIBRATION not specified - using default frequency > Timecounter "i8254" frequency 1193182 Hz > CLK_USE_TSC_CALIBRATION not specified - using old calibration method > Timecounter "TSC" frequency 866703972 Hz > CPU: Pentium III/Pentium III Xeon/Celeron (866.70-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x686 Stepping = 6 > > Features=0x387f9ff ,PGE,MCA,CMOV,PAT,PSE36,PN,MMX,FXSR,SSE> > real memory = 268369920 (262080K bytes) > Physical memory chunk(s): > 0x00001000 - 0x0009efff, 647168 bytes (158 pages) > 0x003d4000 - 0x0ffe7fff, 264323072 bytes (64532 pages) > avail memory = 257171456 (251144K bytes) > bios32: Found BIOS32 Service Directory header at 0xc00fafd0 > bios32: Entry = 0xfb440 (c00fb440) Rev = 0 Len = 1 > pcibios: PCI BIOS entry at 0xb470 > pnpbios: Found PnP BIOS data at 0xc00fbe60 > pnpbios: Entry = f0000:be90 Rev = 1.0 > Other BIOS signatures found: > ACPI: 000f6fa0 > Preloaded elf kernel "kernel" at 0xc03ad000. > netsmb_dev: loaded > Pentium Pro MTRR support enabled > md0: Malloc disk > Creating DISK md0 > Math emulator present > pci_open(1): mode 1 addr port (0x0cf8) is 0x80000060 > pci_open(1a): mode1res=0x80000000 (0x80000000) > pci_cfgcheck: device 0 [class=060000] [hdr=00] is there > (id=06911106) > Using $PIR table, 7 entries at 0xc00fdce0 > pcib-: pcib0 exists, using next available unit number > npx0: on motherboard > npx0: INT 16 interface > pcib0: on motherboard > found-> vendor=0x1106, dev=0x0691, revid=0xc4 > class=06-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > map[10]: type 1, range 32, base d8000000, size 26 > found-> vendor=0x1106, dev=0x8598, revid=0x00 > class=06-04-00, hdrtype=0x01, mfdev=0 > subordinatebus=1 secondarybus=1 > found-> vendor=0x1106, dev=0x0686, revid=0x40 > class=06-01-00, hdrtype=0x00, mfdev=1 > subordinatebus=0 secondarybus=0 > found-> vendor=0x1106, dev=0x0571, revid=0x06 > class=01-01-8a, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > map[20]: type 1, range 32, base 0000a000, size 4 > found-> vendor=0x1106, dev=0x3038, revid=0x16 > class=0c-03-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=d, irq=11 > map[20]: type 1, range 32, base 0000a400, size 5 > found-> vendor=0x1106, dev=0x3038, revid=0x16 > class=0c-03-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=d, irq=11 > map[20]: type 1, range 32, base 0000a800, size 5 > found-> vendor=0x1106, dev=0x3057, revid=0x40 > class=06-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > found-> vendor=0x1106, dev=0x3058, revid=0x50 > class=04-01-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=c, irq=10 > map[10]: type 1, range 32, base 0000ac00, size 8 > map[14]: type 1, range 32, base 0000b000, size 2 > map[18]: type 1, range 32, base 0000b400, size 2 > found-> vendor=0x105a, dev=0x4d30, revid=0x02 > class=01-80-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=a, irq=11 > map[10]: type 1, range 32, base 0000b800, size 3 > map[14]: type 1, range 32, base 0000bc00, size 2 > map[18]: type 1, range 32, base 0000c000, size 3 > map[1c]: type 1, range 32, base 0000c400, size 2 > map[20]: type 1, range 32, base 0000c800, size 6 > map[24]: type 1, range 32, base dd000000, size 17 > found-> vendor=0x100b, dev=0x0020, revid=0x00 > class=02-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=a, irq=10 > map[10]: type 1, range 32, base 0000cc00, size 8 > map[14]: type 1, range 32, base dd040000, size 12 > found-> vendor=0x1274, dev=0x5880, revid=0x02 > class=04-01-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=a, irq=5 > map[10]: type 1, range 32, base 0000d000, size 6 > found-> vendor=0x105a, dev=0x4d38, revid=0x01 > class=01-80-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=a, irq=11 > map[10]: type 1, range 32, base 0000d400, size 3 > map[14]: type 1, range 32, base 0000d800, size 2 > map[18]: type 1, range 32, base 0000dc00, size 3 > map[1c]: type 1, range 32, base 0000e000, size 2 > map[20]: type 1, range 32, base 0000e400, size 6 > map[24]: type 1, range 32, base dd020000, size 17 > pci0: on pcib0 > pcib2: at > device 1.0 on pci0 > found-> vendor=0x5333, dev=0x8a13, revid=0x02 > class=03-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > map[10]: type 1, range 32, base d0000000, size 26 > pci1: on pcib2 > pci1: (vendor=0x5333, > dev=0x8a13) at 0.0 > isab0: at device 7.0 on pci0 > isa0: on isab0 > atapci0: port 0xa000-0xa00f at > device 7.1 on pci0 > ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xa000 > ata0: mask=03 status0=50 status1=00 > ata0: mask=03 ostat0=50 ostat2=00 > ata0-master: ATAPI probe a=00 b=00 > ata0-slave: ATAPI probe a=00 b=00 > ata0: mask=03 status0=50 status1=00 > ata0-master: ATA probe a=01 b=a5 > ata0: devices=01 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xa008 > ata1: mask=01 status0=51 status1=ff > ata1: mask=01 ostat0=51 ostat2=ff > ata1-master: ATAPI probe a=14 b=eb > ata1: mask=01 status0=00 status1=ff > ata1: devices=04 > ata1: at 0x170 irq 15 on atapci0 > uhci0: port 0xa400-0xa41f irq 11 > at device 7.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 0xa800-0xa81f irq 11 > at device 7.3 on pci0 > using shared irq11. > 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 > pcm0: port > 0xb400-0xb403,0xb000-0xb003,0xac00-0xacff irq 10 at device 7.5 on pci0 > pcm0: ac97 codec id 0x414c4326 > pcm0: ac97 codec features 5 bit master volume, Realtek 3D > Stereo Enhancement > pcm0: ac97 primary codec extended features AMAP > pcm: setmap f85a000, 1000; 0xc17e6000 -> f85a000 > pcm: setmap f87c000, 1000; 0xc17e8000 -> f87c000 > atapci1: port > 0xc800-0xc83f,0xc400-0xc403,0xc000-0xc007,0xbc00-0xbc03,0xb800 > -0xb807 mem 0xdd000000-0xdd01ffff irq 11 at device 9.0 on pci0 > ata-: ata2 exists, using next available unit number > ata2: iobase=0xb800 altiobase=0xbc02 bmaddr=0xc800 > ata2: mask=03 status0=50 status1=00 > ata2: mask=03 ostat0=50 ostat2=00 > ata2-master: ATAPI probe a=00 b=00 > ata2-slave: ATAPI probe a=00 b=00 > ata2: mask=03 status0=50 status1=00 > ata2-master: ATA probe a=01 b=a5 > ata2: devices=01 > ata2: at 0xb800 on atapci1 > ata3: iobase=0xc000 altiobase=0xc402 bmaddr=0xc808 > ata3: mask=03 status0=50 status1=00 > ata3: mask=03 ostat0=50 ostat2=00 > ata3-master: ATAPI probe a=00 b=00 > ata3-slave: ATAPI probe a=00 b=00 > ata3: mask=03 status0=50 status1=00 > ata3-master: ATA probe a=01 b=a5 > ata3: devices=01 > ata3: at 0xc000 on atapci1 > sis0: port 0xcc00-0xccff mem > 0xdd040000-0xdd040fff irq 10 at device 11.0 on pci0 > using shared irq10. > sis0: Ethernet address: 00:02:e3:15:32:3a > miibus0: on sis0 > ukphy0: on miibus0 > ukphy0: OUI 0x080017, model 0x0002, rev. 1 > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > bpf: sis0 attached > pcm1: port 0xd000-0xd03f irq 5 at device > 13.0 on pci0 > pcm1: ac97 codec id 0x83847609 (SigmaTel STAC9721/9723) > pcm1: ac97 codec features 18 bit DAC, 18 bit ADC, 5 bit > master volume, SigmaTel 3D Enhancement > pcm1: ac97 primary codec extended features AMAP > pcm: setmap f864000, 1000; 0xc17f0000 -> f864000 > pcm: setmap f846000, 1000; 0xc17f2000 -> f846000 > atapci2: port > 0xe400-0xe43f,0xe000-0xe003,0xdc00-0xdc07,0xd800-0xd803,0xd400 > -0xd407 mem 0xdd020000-0xdd03ffff irq 11 at device 17.0 on pci0 > ata-: ata2 exists, using next available unit number > ata-: ata2 exists, using next available unit number > ata4: iobase=0xd400 altiobase=0xd802 bmaddr=0xe400 > ata4: mask=03 status0=50 status1=00 > ata4: mask=03 ostat0=50 ostat2=00 > ata4-master: ATAPI probe a=00 b=00 > ata4-slave: ATAPI probe a=00 b=00 > ata4: mask=03 status0=50 status1=00 > ata4-master: ATA probe a=01 b=a5 > ata4: devices=01 > ata4: at 0xd400 on atapci2 > ata5: iobase=0xdc00 altiobase=0xe002 bmaddr=0xe408 > ata5: mask=03 status0=50 status1=00 > ata5: mask=03 ostat0=50 ostat2=00 > ata5-master: ATAPI probe a=00 b=00 > ata5-slave: ATAPI probe a=00 b=00 > ata5: mask=03 status0=50 status1=00 > ata5-master: ATA probe a=01 b=a5 > ata5: devices=01 > ata5: at 0xdc00 on atapci2 > pci-: pci1 exists, using next available unit number > pcib1: on motherboard > pci2: on pcib1 > ata-: ata0 exists, using next available unit number > ata-: ata1 exists, using next available unit number > Trying Read_Port at 203 > Trying Read_Port at 243 > Trying Read_Port at 283 > Trying Read_Port at 2c3 > Trying Read_Port at 303 > Trying Read_Port at 343 > Trying Read_Port at 383 > Trying Read_Port at 3c3 > isa_probe_children: disabling PnP devices > isa_probe_children: probing non-PnP devices > orm0: