Re: 5.8: uvideo has support for Logitech QuickCam Pro 5000 but ugen0 attaches instead

2016-01-15 Thread Martin Pieuchot
On 06/01/16(Wed) 10:17, Martin Pieuchot wrote:
> On 05/01/16(Tue) 13:19, Matt Adams wrote:
> > On 05/01/16 05:10 AM, Martin Pieuchot wrote:
> > >On 03/01/16(Sun) 23:18, Matt Adams wrote:
> > >>Hi,
> > >>
> > >>I noted that uvideo has support for the Logitech QuickCam Pro 5000 - a 
> > >>piece
> > >>of hardware that I have. However, ugen appears to attach to this device
> > >>instead of allowing the special firmware (installed via "# fw_install
> > >>uvideo") to configure /dev/video0 or /dev/video1, even though those two
> > >>device files are present in the system.
> > >>
> > >>For example:
> > >>
> > >>-bash-4.3$ luvcview
> > >>luvcview version 2.0
> > >>Video driver: x11
> > >>A window manager is available
> > >>video /dev/video0
> > >>ERROR opening V4L interface
> > >>: Device not configured
> > >>
> > >>Is there something that I am missing here or is my webcam not actually
> > >>supported?
> > >Could you paste the output of "lsusb -v" for your webcam?  lsusb(1) is
> > >part of the usbutils package.
> > 
> > lsusb -v as follows (webcam portion only):
> > 
> > Bus 001 Device 002: ID 046d:08c5 Logitech, Inc. QuickCam Pro 5000
> > Device Descriptor:
> >   bLength18
> >   bDescriptorType 1
> >   bcdUSB   2.00
> >   bDeviceClass0 (Defined at Interface level)
> >   bDeviceSubClass 0
> >   bDeviceProtocol 1
> >   bMaxPacketSize064
> >   idVendor   0x046d Logitech, Inc.
> >   idProduct  0x08c5 QuickCam Pro 5000
> 
> Thanks, does the diff below help?

Could you test the diff?  Does it work?

> Index: uvideo.c
> ===
> RCS file: /cvs/src/sys/dev/usb/uvideo.c,v
> retrieving revision 1.183
> diff -u -p -r1.183 uvideo.c
> --- uvideo.c  20 Dec 2015 10:08:05 -  1.183
> +++ uvideo.c  6 Jan 2016 09:14:05 -
> @@ -382,6 +382,12 @@ struct uvideo_devs {
>   NULL,
>   UVIDEO_FLAG_VENDOR_CLASS
>   },
> + {   /* Incorrectly reports as bInterfaceClass=UICLASS_VENDOR */
> + { USB_VENDOR_LOGITECH, USB_PRODUCT_LOGITECH_QUICKCAMPRO5K_1 },
> + NULL,
> + NULL,
> + UVIDEO_FLAG_VENDOR_CLASS
> + },
>  };
>  #define uvideo_lookup(v, p) \
>   ((struct uvideo_devs *)usb_lookup(uvideo_devs, v, p))



Re: 5.8: uvideo has support for Logitech QuickCam Pro 5000 but ugen0 attaches instead

2016-01-15 Thread Matt Adams

On 15/01/16 05:44 AM, Martin Pieuchot wrote:

Could you test the diff? Does it work?

I haven't had a chance but I will as soon as I can. Thanks!

Matt



Re: 5.8: uvideo has support for Logitech QuickCam Pro 5000 but ugen0 attaches instead

2016-01-06 Thread Martin Pieuchot
On 05/01/16(Tue) 13:19, Matt Adams wrote:
> On 05/01/16 05:10 AM, Martin Pieuchot wrote:
> >On 03/01/16(Sun) 23:18, Matt Adams wrote:
> >>Hi,
> >>
> >>I noted that uvideo has support for the Logitech QuickCam Pro 5000 - a piece
> >>of hardware that I have. However, ugen appears to attach to this device
> >>instead of allowing the special firmware (installed via "# fw_install
> >>uvideo") to configure /dev/video0 or /dev/video1, even though those two
> >>device files are present in the system.
> >>
> >>For example:
> >>
> >>-bash-4.3$ luvcview
> >>luvcview version 2.0
> >>Video driver: x11
> >>A window manager is available
> >>video /dev/video0
> >>ERROR opening V4L interface
> >>: Device not configured
> >>
> >>Is there something that I am missing here or is my webcam not actually
> >>supported?
> >Could you paste the output of "lsusb -v" for your webcam?  lsusb(1) is
> >part of the usbutils package.
> 
> lsusb -v as follows (webcam portion only):
> 
> Bus 001 Device 002: ID 046d:08c5 Logitech, Inc. QuickCam Pro 5000
> Device Descriptor:
>   bLength18
>   bDescriptorType 1
>   bcdUSB   2.00
>   bDeviceClass0 (Defined at Interface level)
>   bDeviceSubClass 0
>   bDeviceProtocol 1
>   bMaxPacketSize064
>   idVendor   0x046d Logitech, Inc.
>   idProduct  0x08c5 QuickCam Pro 5000

Thanks, does the diff below help?

Index: uvideo.c
===
RCS file: /cvs/src/sys/dev/usb/uvideo.c,v
retrieving revision 1.183
diff -u -p -r1.183 uvideo.c
--- uvideo.c20 Dec 2015 10:08:05 -  1.183
+++ uvideo.c6 Jan 2016 09:14:05 -
@@ -382,6 +382,12 @@ struct uvideo_devs {
NULL,
UVIDEO_FLAG_VENDOR_CLASS
},
+   {   /* Incorrectly reports as bInterfaceClass=UICLASS_VENDOR */
+   { USB_VENDOR_LOGITECH, USB_PRODUCT_LOGITECH_QUICKCAMPRO5K_1 },
+   NULL,
+   NULL,
+   UVIDEO_FLAG_VENDOR_CLASS
+   },
 };
 #define uvideo_lookup(v, p) \
((struct uvideo_devs *)usb_lookup(uvideo_devs, v, p))



Re: 5.8: uvideo has support for Logitech QuickCam Pro 5000 but ugen0 attaches instead

2016-01-06 Thread Raf Czlonka
On Mon, Jan 04, 2016 at 06:18:30AM GMT, Matt Adams wrote:

> Hi,
>
> I noted that uvideo has support for the Logitech QuickCam Pro 5000 -
> a piece of hardware that I have. However, ugen appears to attach to
> this device instead of allowing the special firmware (installed via
> "# fw_install uvideo") to configure /dev/video0 or /dev/video1, even
> though those two device files are present in the system.

Hi Matt,

Logitech QuickCam Pro 5000 comes is two models: UVC and non-UVC[0].

Please verify that your camera is the V-UAX16[1], not the V-VAX16, model
(P/N 861306) - I can't verify it based only on its USB Product ID as I'm
not entirely sure whether it would differ between these two models.

Regards,

Raf

[0] http://support.logitech.com/en_gb/product/quickcam-pro-5000
[1] http://support.logitech.com/en_gb/article/6471



Re: 5.8: uvideo has support for Logitech QuickCam Pro 5000 but ugen0 attaches instead

2016-01-05 Thread Matt Adams

On 05/01/16 05:10 AM, Martin Pieuchot wrote:

On 03/01/16(Sun) 23:18, Matt Adams wrote:

Hi,

I noted that uvideo has support for the Logitech QuickCam Pro 5000 - a piece
of hardware that I have. However, ugen appears to attach to this device
instead of allowing the special firmware (installed via "# fw_install
uvideo") to configure /dev/video0 or /dev/video1, even though those two
device files are present in the system.

For example:

-bash-4.3$ luvcview
luvcview version 2.0
Video driver: x11
A window manager is available
video /dev/video0
ERROR opening V4L interface
: Device not configured

Is there something that I am missing here or is my webcam not actually
supported?

Could you paste the output of "lsusb -v" for your webcam?  lsusb(1) is
part of the usbutils package.


lsusb -v as follows (webcam portion only):

Bus 001 Device 002: ID 046d:08c5 Logitech, Inc. QuickCam Pro 5000
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   2.00
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 1
  bMaxPacketSize064
  idVendor   0x046d Logitech, Inc.
  idProduct  0x08c5 QuickCam Pro 5000
  bcdDevice0.05
  iManufacturer   0
  iProduct0
  iSerial 2 87C33093
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 1267
bNumInterfaces  4
bConfigurationValue 1
iConfiguration  0
bmAttributes 0x80
  (Bus Powered)
MaxPower  500mA
Interface Association:
  bLength 8
  bDescriptorType11
  bFirstInterface 0
  bInterfaceCount 2
  bFunctionClass255 Vendor Specific Class
  bFunctionSubClass   3
  bFunctionProtocol   0
  iFunction   0
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   1
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass  1
  bInterfaceProtocol  0
  iInterface  0
  ** UNRECOGNIZED:  0d 24 01 00 01 6a 00 00 6c dc 02 01 01
  ** UNRECOGNIZED:  12 24 02 01 01 02 00 00 00 00 00 00 00 00 03 0e 
00 00

  ** UNRECOGNIZED:  0b 24 05 02 01 00 40 02 7b 17 00
  ** UNRECOGNIZED:  1c 24 06 03 82 06 61 63 70 50 ab 49 b8 cc b3 85 
5e 8d 22 1d 00 01 02 03 ff ff 1f 00
  ** UNRECOGNIZED:  1b 24 06 04 82 06 61 63 70 50 ab 49 b8 cc b3 85 
5e 8d 22 1e 00 01 03 02 7f 01 00

  ** UNRECOGNIZED:  09 24 03 05 01 01 00 04 00
  ** UNRECOGNIZED:  20 41 01 08 82 06 61 63 70 50 ab 49 b8 cc b3 85 
5e 8d 22 51 03 01 04 03 19 00 00 00 00 00 00 00
  ** UNRECOGNIZED:  20 41 01 0a 82 06 61 63 70 50 ab 49 b8 cc b3 85 
5e 8d 22 52 01 01 04 03 00 40 00 00 00 00 00 00

  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x87  EP 7 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0010  1x 16 bytes
bInterval   8
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber1
  bAlternateSetting   0
  bNumEndpoints   0
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass  2
  bInterfaceProtocol  0
  iInterface  0
  ** UNRECOGNIZED:  10 24 01 03 a9 02 81 00 05 02 01 00 01 04 00 04
  ** UNRECOGNIZED:  0b 24 06 01 09 01 03 00 00 00 00
  ** UNRECOGNIZED:  32 24 07 01 00 a0 00 78 00 00 70 17 00 00 a0 8c 
00 00 96 00 00 15 16 05 00 06 15 16 05 00 80 1a 06 00 20 a1 07 00 2a 2c 
0a 00 40 42 0f 00 80 84 1e 00
  ** UNRECOGNIZED:  32 24 07 02 00 b0 00 90 00 00 f0 1e 00 00 a0 b9 
00 00 c6 00 00 15 16 05 00 06 15 16 05 00 80 1a 06 00 20 a1 07 00 2a 2c 
0a 00 40 42 0f 00 80 84 1e 00
  ** UNRECOGNIZED:  32 24 07 03 00 40 01 f0 00 00 c0 5d 00 00 80 32 
02 00 58 02 00 2a 2c 0a 00 06 15 16 05 00 80 1a 06 00 20 a1 07 00 2a 2c 
0a 00 40 42 0f 00 80 84 1e 00
  ** UNRECOGNIZED:  32 24 07 04 00 60 01 20 01 00 c0 7b 00 00 80 e6 
02 00 18 03 00 15 16 05 00 06 15 16 05 00 80 1a 06 00 20 a1 07 00 2a 2c 
0a 00 40 42 0f 00 80 84 1e 00
  ** UNRECOGNIZED:  32 24 07 05 00 b0 01 f0 00 00 90 7e 00 00 60 f7 
02 00 2a 03 00 15 16 05 00 06 15 16 05 00 80 1a 06 00 20 a1 07 00 2a 2c 
0a 00 40 42 0f 00 80 84 1e 00
  ** UNRECOGNIZED:  32 24 07 06 00 e0 01 68 01 00 f0 d2 00 00 a0 f1 
04 00 46 05 00 15 16 05 00 06 15 16 05 00 80 1a 06 00 20 a1 07 00 2a 2c 
0a 00 40 42 0f 00 80 84 1e 00
  ** UNRECOGNIZED:  32 24 07 07 00 00 02 20 01 00 00 b4 00 00 00 38 
04 00 

Re: 5.8: uvideo has support for Logitech QuickCam Pro 5000 but ugen0 attaches instead

2016-01-05 Thread Martin Pieuchot
On 03/01/16(Sun) 23:18, Matt Adams wrote:
> Hi,
> 
> I noted that uvideo has support for the Logitech QuickCam Pro 5000 - a piece
> of hardware that I have. However, ugen appears to attach to this device
> instead of allowing the special firmware (installed via "# fw_install
> uvideo") to configure /dev/video0 or /dev/video1, even though those two
> device files are present in the system.
> 
> For example:
> 
> -bash-4.3$ luvcview
> luvcview version 2.0
> Video driver: x11
> A window manager is available
> video /dev/video0
> ERROR opening V4L interface
> : Device not configured
> 
> Is there something that I am missing here or is my webcam not actually
> supported?

Could you paste the output of "lsusb -v" for your webcam?  lsusb(1) is
part of the usbutils package.

> 
> -bash-4.3$ ls -l /dev/video*
> lrwxr-xr-x  1 root  wheel 6 Dec 24 00:09 /dev/video -> video0
> crw-rw-rw-  1 root  wheel   44,   0 Dec 24 00:09 /dev/video0
> crw-rw-rw-  1 root  wheel   44,   1 Dec 24 00:09 /dev/video1
> 
> Thanks,
> 
> Matt
> 
> -- usbdevs -v below
> 
> Controller /dev/usb0:
> addr 1: high speed, self powered, config 1, EHCI root hub(0x),
> Intel(0x8086), rev 1.00
>  port 1 powered
>  port 2 powered
>  port 3 addr 2: high speed, self powered, config 1, product 0x2514(0x2514),
> Standard Microsystems(0x0424), rev 0.00
>   port 1 powered
>   port 2 powered
>  port 4 powered
> Controller /dev/usb1:
> addr 1: high speed, self powered, config 1, EHCI root hub(0x),
> Intel(0x8086), rev 1.00
>  port 1 powered
>  port 2 powered
>  port 3 powered
>  port 4 powered
>  port 5 addr 2: high speed, power 500 mA, config 1, QuickCam Pro
> 5000(0x08c5), Logitech(0x046d), rev 0.05, iSerialNumber 87C33093
>  port 6 powered
>  port 7 powered
>  port 8 powered
> Controller /dev/usb2:
> addr 1: full speed, self powered, config 1, UHCI root hub(0x),
> Intel(0x8086), rev 1.00
>  port 1 powered
>  port 2 addr 2: full speed, self powered, config 1, product 0x7000(0x7000),
> ATEN International(0x0557), rev 1.00
>   port 1 addr 3: low speed, power 100 mA, config 1, Type 6 Keyboard(0x0005),
> Fujitsu Component(0x0430), rev 1.02
>   port 2 powered
>   port 3 powered
>   port 4 powered
> Controller /dev/usb3:
> addr 1: full speed, self powered, config 1, UHCI root hub(0x),
> Intel(0x8086), rev 1.00
>  port 1 powered
>  port 2 powered
> Controller /dev/usb4:
> addr 1: full speed, self powered, config 1, UHCI root hub(0x),
> Intel(0x8086), rev 1.00
>  port 1 powered
>  port 2 powered
> Controller /dev/usb5:
> addr 1: full speed, self powered, config 1, UHCI root hub(0x),
> Intel(0x8086), rev 1.00
>  port 1 powered
>  port 2 powered
> Controller /dev/usb6:
> addr 1: full speed, self powered, config 1, UHCI root hub(0x),
> Intel(0x8086), rev 1.00
>  port 1 powered
>  port 2 addr 2: low speed, self powered, config 1, Back-UPS RS 1300 LCD
> FW:838.H5 .D USB FW:H5(0x0002), American Power Conversion(0x051d), rev 1.01,
> iSerialNumber JB0721002454
> Controller /dev/usb7:
> addr 1: full speed, self powered, config 1, UHCI root hub(0x),
> Intel(0x8086), rev 1.00
>  port 1 powered
>  port 2 powered
> 
> 
> -- dmesg below
> 
> OpenBSD 5.8 (GENERIC.MP) #1236: Sun Aug 16 02:31:04 MDT 2015
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> real mem = 25739890688 (24547MB)
> avail mem = 24955904000 (23799MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xcf49c000 (85 entries)
> bios0: vendor Dell Inc. version "6.4.0" date 07/23/2013
> bios0: Dell Inc. PowerEdge T710
> acpi0 at bios0: rev 2
> acpi0: sleep states S0 S4 S5
> acpi0: tables DSDT FACP APIC SPCR HPET DMAR MCFG WD__ SLIC ERST HEST BERT
> EINJ SRAT TCPA SSDT
> acpi0: wakeup devices PCI0(S5) PCI1(S5)
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel(R) Xeon(R) CPU X5680 @ 3.33GHz, 3458.46 MHz
> cpu0: 
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,AES,NXE,PAGE1GB,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
> cpu0: 256KB 64b/line 8-way L2 cache
> cpu0: smt 0, core 0, package 0
> mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
> cpu0: apic clock running at 132MHz
> cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE
> cpu1 at mainbus0: apid 2 (application processor)
> cpu1: Intel(R) Xeon(R) CPU X5680 @ 3.33GHz, 3458.00 MHz
> cpu1: 
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,AES,NXE,PAGE1GB,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
> cpu1: 256KB 64b/line 8-way L2 cache
> cpu1: smt 0, core 1, package 0
> cpu2 at mainbus0: apid 4 (application processor)

5.8: uvideo has support for Logitech QuickCam Pro 5000 but ugen0 attaches instead

2016-01-03 Thread Matt Adams

Hi,

I noted that uvideo has support for the Logitech QuickCam Pro 5000 - a 
piece of hardware that I have. However, ugen appears to attach to this 
device instead of allowing the special firmware (installed via "# 
fw_install uvideo") to configure /dev/video0 or /dev/video1, even though 
those two device files are present in the system.


For example:

-bash-4.3$ luvcview
luvcview version 2.0
Video driver: x11
A window manager is available
video /dev/video0
ERROR opening V4L interface
: Device not configured

Is there something that I am missing here or is my webcam not actually 
supported?


-bash-4.3$ ls -l /dev/video*
lrwxr-xr-x  1 root  wheel 6 Dec 24 00:09 /dev/video -> video0
crw-rw-rw-  1 root  wheel   44,   0 Dec 24 00:09 /dev/video0
crw-rw-rw-  1 root  wheel   44,   1 Dec 24 00:09 /dev/video1

Thanks,

Matt

-- usbdevs -v below

Controller /dev/usb0:
addr 1: high speed, self powered, config 1, EHCI root hub(0x), 
Intel(0x8086), rev 1.00

 port 1 powered
 port 2 powered
 port 3 addr 2: high speed, self powered, config 1, product 
0x2514(0x2514), Standard Microsystems(0x0424), rev 0.00

  port 1 powered
  port 2 powered
 port 4 powered
Controller /dev/usb1:
addr 1: high speed, self powered, config 1, EHCI root hub(0x), 
Intel(0x8086), rev 1.00

 port 1 powered
 port 2 powered
 port 3 powered
 port 4 powered
 port 5 addr 2: high speed, power 500 mA, config 1, QuickCam Pro 
5000(0x08c5), Logitech(0x046d), rev 0.05, iSerialNumber 87C33093

 port 6 powered
 port 7 powered
 port 8 powered
Controller /dev/usb2:
addr 1: full speed, self powered, config 1, UHCI root hub(0x), 
Intel(0x8086), rev 1.00

 port 1 powered
 port 2 addr 2: full speed, self powered, config 1, product 
0x7000(0x7000), ATEN International(0x0557), rev 1.00
  port 1 addr 3: low speed, power 100 mA, config 1, Type 6 
Keyboard(0x0005), Fujitsu Component(0x0430), rev 1.02

  port 2 powered
  port 3 powered
  port 4 powered
Controller /dev/usb3:
addr 1: full speed, self powered, config 1, UHCI root hub(0x), 
Intel(0x8086), rev 1.00

 port 1 powered
 port 2 powered
Controller /dev/usb4:
addr 1: full speed, self powered, config 1, UHCI root hub(0x), 
Intel(0x8086), rev 1.00

 port 1 powered
 port 2 powered
Controller /dev/usb5:
addr 1: full speed, self powered, config 1, UHCI root hub(0x), 
Intel(0x8086), rev 1.00

 port 1 powered
 port 2 powered
Controller /dev/usb6:
addr 1: full speed, self powered, config 1, UHCI root hub(0x), 
Intel(0x8086), rev 1.00

 port 1 powered
 port 2 addr 2: low speed, self powered, config 1, Back-UPS RS 1300 LCD 
FW:838.H5 .D USB FW:H5(0x0002), American Power Conversion(0x051d), rev 
1.01, iSerialNumber JB0721002454

Controller /dev/usb7:
addr 1: full speed, self powered, config 1, UHCI root hub(0x), 
Intel(0x8086), rev 1.00

 port 1 powered
 port 2 powered


-- dmesg below

OpenBSD 5.8 (GENERIC.MP) #1236: Sun Aug 16 02:31:04 MDT 2015
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 25739890688 (24547MB)
avail mem = 24955904000 (23799MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xcf49c000 (85 entries)
bios0: vendor Dell Inc. version "6.4.0" date 07/23/2013
bios0: Dell Inc. PowerEdge T710
acpi0 at bios0: rev 2
acpi0: sleep states S0 S4 S5
acpi0: tables DSDT FACP APIC SPCR HPET DMAR MCFG WD__ SLIC ERST HEST 
BERT EINJ SRAT TCPA SSDT

acpi0: wakeup devices PCI0(S5) PCI1(S5)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Xeon(R) CPU X5680 @ 3.33GHz, 3458.46 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,AES,NXE,PAGE1GB,LONG,LAHF,PERF,ITSC,SENSOR,ARAT

cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 132MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Xeon(R) CPU X5680 @ 3.33GHz, 3458.00 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,AES,NXE,PAGE1GB,LONG,LAHF,PERF,ITSC,SENSOR,ARAT

cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Xeon(R) CPU X5680 @ 3.33GHz, 3458.00 MHz
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,AES,NXE,PAGE1GB,LONG,LAHF,PERF,ITSC,SENSOR,ARAT

cpu2: 256KB 64b/line 8-way L2 cache