From neiga at mail.com Tue May 12 03:59:00 2015 From: neiga at mail.com (Joe) Date: Tue, 12 May 2015 06:00:52 +0200 Subject: photos retouching Message-ID: <0cb561b44dc12eff26c5ad6dd0630020@tripadvisor.com> Hope you are doing well! We provide photo editing: Such as ecommerce photos editing, jewelry photos retouching, beauty and skin image retouching, and wedding photo editing, image cut out and clipping path, masking. Our advantages: Quality is good Turnaround time fast 7/24/365 available Our service is best and price is affordable. You may send us a test photo to judge our quality. Have a good day! Best regards, Joe Email: songedit at tom.com From amijaresp at gmail.com Mon May 25 01:06:18 2015 From: amijaresp at gmail.com (Alberto Mijares) Date: Sun, 24 May 2015 20:36:17 -0430 Subject: Bluetooth USB Host Controller Atheros Communications Message-ID: Hi guys, I've been looking for a while how to enable my bluetooth adapter with no success. Hardware info is attached, I hope you can help me or I can help you to find a solution. Best regards, Alberto Mijares -------------- next part -------------- ugen1.4: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x00b1 bNumInterfaces = 0x0002 bConfigurationValue = 0x0001 iConfiguration = 0x0004 bmAttributes = 0x00e0 bMaxPower = 0x0032 Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0000 bAlternateSetting = 0x0000 bNumEndpoints = 0x0003 bInterfaceClass = 0x00e0 bInterfaceSubClass = 0x0001 bInterfaceProtocol = 0x0001 iInterface = 0x0000 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0081 bmAttributes = 0x0003 wMaxPacketSize = 0x0010 bInterval = 0x0001 bRefresh = 0x0000 bSynchAddress = 0x0000 Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0082 bmAttributes = 0x0002 wMaxPacketSize = 0x0040 bInterval = 0x0001 bRefresh = 0x0000 bSynchAddress = 0x0000 Endpoint 2 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0002 bmAttributes = 0x0002 wMaxPacketSize = 0x0040 bInterval = 0x0001 bRefresh = 0x0000 bSynchAddress = 0x0000 Interface 1 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0001 bAlternateSetting = 0x0000 bNumEndpoints = 0x0002 bInterfaceClass = 0x00e0 bInterfaceSubClass = 0x0001 bInterfaceProtocol = 0x0001 iInterface = 0x0000 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0083 bmAttributes = 0x0001 wMaxPacketSize = 0x0000 bInterval = 0x0001 bRefresh = 0x0000 bSynchAddress = 0x0000 Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0003 bmAttributes = 0x0001 wMaxPacketSize = 0x0000 bInterval = 0x0001 bRefresh = 0x0000 bSynchAddress = 0x0000 Interface 1 Alt 1 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0001 bAlternateSetting = 0x0001 bNumEndpoints = 0x0002 bInterfaceClass = 0x00e0 bInterfaceSubClass = 0x0001 bInterfaceProtocol = 0x0001 iInterface = 0x0000 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0083 bmAttributes = 0x0001 wMaxPacketSize = 0x0009 bInterval = 0x0001 bRefresh = 0x0000 bSynchAddress = 0x0000 Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0003 bmAttributes = 0x0001 wMaxPacketSize = 0x0009 bInterval = 0x0001 bRefresh = 0x0000 bSynchAddress = 0x0000 Interface 1 Alt 2 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0001 bAlternateSetting = 0x0002 bNumEndpoints = 0x0002 bInterfaceClass = 0x00e0 bInterfaceSubClass = 0x0001 bInterfaceProtocol = 0x0001 iInterface = 0x0000 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0083 bmAttributes = 0x0001 wMaxPacketSize = 0x0011 bInterval = 0x0001 bRefresh = 0x0000 bSynchAddress = 0x0000 Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0003 bmAttributes = 0x0001 wMaxPacketSize = 0x0011 bInterval = 0x0001 bRefresh = 0x0000 bSynchAddress = 0x0000 Interface 1 Alt 3 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0001 bAlternateSetting = 0x0003 bNumEndpoints = 0x0002 bInterfaceClass = 0x00e0 bInterfaceSubClass = 0x0001 bInterfaceProtocol = 0x0001 iInterface = 0x0000 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0083 bmAttributes = 0x0001 wMaxPacketSize = 0x0019 bInterval = 0x0001 bRefresh = 0x0000 bSynchAddress = 0x0000 Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0003 bmAttributes = 0x0001 wMaxPacketSize = 0x0019 bInterval = 0x0001 bRefresh = 0x0000 bSynchAddress = 0x0000 Interface 1 Alt 4 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0001 bAlternateSetting = 0x0004 bNumEndpoints = 0x0002 bInterfaceClass = 0x00e0 bInterfaceSubClass = 0x0001 bInterfaceProtocol = 0x0001 iInterface = 0x0000 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0083 bmAttributes = 0x0001 wMaxPacketSize = 0x0021 bInterval = 0x0001 bRefresh = 0x0000 bSynchAddress = 0x0000 Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0003 bmAttributes = 0x0001 wMaxPacketSize = 0x0021 bInterval = 0x0001 bRefresh = 0x0000 bSynchAddress = 0x0000 Interface 1 Alt 5 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0001 bAlternateSetting = 0x0005 bNumEndpoints = 0x0002 bInterfaceClass = 0x00e0 bInterfaceSubClass = 0x0001 bInterfaceProtocol = 0x0001 iInterface = 0x0000 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0083 bmAttributes = 0x0001 wMaxPacketSize = 0x0031 bInterval = 0x0001 bRefresh = 0x0000 bSynchAddress = 0x0000 Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0003 bmAttributes = 0x0001 wMaxPacketSize = 0x0031 bInterval = 0x0001 bRefresh = 0x0000 bSynchAddress = 0x0000 From hps at selasky.org Mon May 25 11:39:16 2015 From: hps at selasky.org (Hans Petter Selasky) Date: Mon, 25 May 2015 13:39:56 +0200 Subject: Bluetooth USB Host Controller Atheros Communications In-Reply-To: References: Message-ID: <55630A0C.50604@selasky.org> On 05/25/15 03:06, Alberto Mijares wrote: > Hi guys, > > I've been looking for a while how to enable my bluetooth adapter with > no success. Hardware info is attached, I hope you can help me or I can > help you to find a solution. > Hi, Have you tried : kldload ubt ? --HPS From amijaresp at gmail.com Mon May 25 14:42:29 2015 From: amijaresp at gmail.com (Alberto Mijares) Date: Mon, 25 May 2015 10:12:28 -0430 Subject: Bluetooth USB Host Controller Atheros Communications In-Reply-To: <55630A0C.50604@selasky.org> References: <55630A0C.50604@selasky.org> Message-ID: On Mon, May 25, 2015 at 7:09 AM, Hans Petter Selasky wrote: > On 05/25/15 03:06, Alberto Mijares wrote: >> >> Hi guys, >> >> I've been looking for a while how to enable my bluetooth adapter with >> no success. Hardware info is attached, I hope you can help me or I can >> help you to find a solution. >> > > Hi, > > Have you tried : > > kldload ubt > Hello Hans, I had not tried. First of all, I read the Bluetooth section of the handbook and tried what it says; then google, and nothing. However # kldload ubt kldload: can't load ubt: No such file or directory # uname -a FreeBSD mcs 10.1-RELEASE-p10 FreeBSD 10.1-RELEASE-p10 #0: Wed May 13 06:54:13 UTC 2015 root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 Any other suggestion? Thank you. Best regards, Alberto Mijares From hps at selasky.org Mon May 25 22:10:01 2015 From: hps at selasky.org (Hans Petter Selasky) Date: Tue, 26 May 2015 00:10:49 +0200 Subject: Bluetooth USB Host Controller Atheros Communications In-Reply-To: References: <55630A0C.50604@selasky.org> Message-ID: <55639DE9.4070904@selasky.org> On 05/25/15 16:42, Alberto Mijares wrote: > On Mon, May 25, 2015 at 7:09 AM, Hans Petter Selasky wrote: >> On 05/25/15 03:06, Alberto Mijares wrote: >>> >>> Hi guys, >>> >>> I've been looking for a while how to enable my bluetooth adapter with >>> no success. Hardware info is attached, I hope you can help me or I can >>> help you to find a solution. >>> >> >> Hi, >> >> Have you tried : >> >> kldload ubt >> Should be: kldload ng_ubt Any difference? --HPS From amijaresp at gmail.com Mon May 25 22:24:35 2015 From: amijaresp at gmail.com (Alberto Mijares) Date: Mon, 25 May 2015 17:54:34 -0430 Subject: Bluetooth USB Host Controller Atheros Communications In-Reply-To: <55639DE9.4070904@selasky.org> References: <55630A0C.50604@selasky.org> <55639DE9.4070904@selasky.org> Message-ID: > > Should be: > > kldload ng_ubt > > Any difference? > Since this is the first instruction in section 31.5.1 from the handbook, this was the first command I typed. The module is already loaded. However # ls /dev/ubt* ls: No match. Should the device be recognized? What else should I try? Thank you Alberto Mijares From hps at selasky.org Tue May 26 06:43:55 2015 From: hps at selasky.org (Hans Petter Selasky) Date: Tue, 26 May 2015 08:44:43 +0200 Subject: Bluetooth USB Host Controller Atheros Communications In-Reply-To: References: <55630A0C.50604@selasky.org> <55639DE9.4070904@selasky.org> Message-ID: <5564165B.30109@selasky.org> On 05/26/15 00:24, Alberto Mijares wrote: >> >> Should be: >> >> kldload ng_ubt >> >> Any difference? >> > > Since this is the first instruction in section 31.5.1 from the > handbook, this was the first command I typed. The module is already > loaded. > > However > > # ls /dev/ubt* > ls: No match. > > Should the device be recognized? What else should I try? > usbconfig show_ifdrv --HPS From hps at selasky.org Tue May 26 06:48:46 2015 From: hps at selasky.org (Hans Petter Selasky) Date: Tue, 26 May 2015 08:49:36 +0200 Subject: Bluetooth USB Host Controller Atheros Communications In-Reply-To: <5564165B.30109@selasky.org> References: <55630A0C.50604@selasky.org> <55639DE9.4070904@selasky.org> <5564165B.30109@selasky.org> Message-ID: <55641780.1060107@selasky.org> On 05/26/15 08:44, Hans Petter Selasky wrote: > On 05/26/15 00:24, Alberto Mijares wrote: >>> >>> Should be: >>> >>> kldload ng_ubt >>> >>> Any difference? >>> >> >> Since this is the first instruction in section 31.5.1 from the >> handbook, this was the first command I typed. The module is already >> loaded. >> >> However >> >> # ls /dev/ubt* >> ls: No match. >> >> Should the device be recognized? What else should I try? >> > > usbconfig show_ifdrv > Hi, If you dump the device descriptor, usbconfig -d X.Y dump_device_desc, and google the idVendor and idProduct pair in hex, maybe some other OS has quirks for your device to make it attach. --HPS From amijaresp at gmail.com Wed May 27 07:29:47 2015 From: amijaresp at gmail.com (Alberto Mijares) Date: Wed, 27 May 2015 02:59:46 -0430 Subject: Bluetooth USB Host Controller Atheros Communications In-Reply-To: <5564165B.30109@selasky.org> References: <55630A0C.50604@selasky.org> <55639DE9.4070904@selasky.org> <5564165B.30109@selasky.org> Message-ID: >> Since this is the first instruction in section 31.5.1 from the >> handbook, this was the first command I typed. The module is already >> loaded. >> >> However >> >> # ls /dev/ubt* >> ls: No match. >> >> Should the device be recognized? What else should I try? >> > > usbconfig show_ifdrv > % usbconfig show_ifdrv ugen0.1: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) ugen0.1.0: uhub0: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> ugen1.1: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen1.1.0: uhub1: ugen2.1: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen2.1.0: uhub2: ugen1.2: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen1.2.0: uhub3: ugen2.2: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen2.2.0: uhub4: ugen1.3: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA) ugen1.4: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=O