[opensuse-es] Bluetooth USB Adapter ES-388 no funciona en opensuse 11.
El adaptador http://www.linuxquestions.org/hcl/showproduct.php/product/3312/cat/all no he podido hacerlo funcionar con opensuse 11. Algunas lineas de dmesg: Linux version 2.6.25.18-0.2-default (geeko@buildhost) (gcc version 4.3.1 20080507 (prerelease) [gcc-4_3-branch revision 135036] (SUSE Linux) ) #1 SMP 2008-10-21 16:30:26 +0200 usb usb2: configuration #1 chosen from 1 choice hub 2-0:1.0: USB hub found hub 2-0:1.0: 2 ports detected usb usb2: New USB device found, idVendor=1d6b, idProduct=0001 usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb2: Product: UHCI Host Controller usb usb2: Manufacturer: Linux 2.6.25.18-0.2-default uhci_hcd usb usb2: SerialNumber: 0000:00:1f.4 usb 2-2: new full speed USB device using uhci_hcd and address 3 PM: Starting manual resume from disk usb 2-2: configuration #1 chosen from 1 choice usb 2-2: New USB device found, idVendor=1131, idProduct=1004 usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 2-2: Product: ISSCEDRBTA usb 2-2: Manufacturer: ISSC Bluetooth: Core ver 2.11 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized iTCO_vendor_support: vendor-support=0 pci_hotplug: PCI Hot Plug PCI Core version: 0.5 iTCO_wdt: Intel TCO WatchDog Timer Driver v1.02 (26-Jul-2007) iTCO_wdt: failed to reset NO_REBOOT flag, reboot disabled by hardware iTCO_wdt: No card detected shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 Bluetooth: Generic Bluetooth USB driver ver 0.1 usbcore: registered new interface driver btusb Initializing USB Mass Storage driver... scsi2 : SCSI emulation for USB Mass Storage devices Bluetooth: HCI USB driver ver 2.9 usbcore: registered new interface driver hci_usb usb 2-1: new full speed USB device using uhci_hcd and address 4 usb 2-1: configuration #1 chosen from 1 choice usb 2-1: New USB device found, idVendor=1131, idProduct=1004 usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 2-1: Product: ISSCEDRBTA usb 2-1: Manufacturer: ISSC :~ # lsusb Bus 002 Device 004: ID 1131:1004 Integrated System Solution Corp. Bus 002 Device 001: ID 1d6b:0001 Bus 001 Device 001: ID 1d6b:0001 :~ # /usr/sbin/hciconfig hci0: Type: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:0 acl:0 sco:0 commands:0 errors:0 :~ # hcitool scan Device is not available: No such device Otros usuarios con problemas encontrados con Google: ES-388 Bluetooth USB dongle not working [Log in to get rid of this advertisement] Hi all. I have an ES-388 bluetooth adapter which I can't get working properly. Kernel 2.6.20.1, with BlueZ stack. -- Other Thoughts: In Linux ------------------ modules bluetooth,rfcomm,l2cap,hci_usb lsusb Bus 001 Device 004: ID 1131:1004 Integrated System Solution Corp. lsusb -v Bus 001 Device 004: ID 1131:1004 Integrated System Solution Corp. Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 224 Wireless bDeviceSubClass 1 Radio Frequency bDeviceProtocol 1 Bluetooth bMaxPacketSize0 16 idVendor 0x1131 Integrated System Solution Corp. idProduct 0x1004 bcdDevice 3.73 iManufacturer 1 iProduct 2 iSerial 0 bNumConfigurations 1 Bottomline: It is good... bluez-libs/utils-3.11 Code: # lsusb Bus 5 Device 33: ID 0a5c:2035 Broadcom Corp. BCM2035 Bluetooth dmesg shows that: Code: Bluetooth: Core ver 2.11 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized Bluetooth: HCI USB driver ver 2.9 Device driver usbdev5.30_ep83 lacks bus and class support for being resumed. Device driver usbdev5.30_ep03 lacks bus and class support for being resumed. Device driver hci0 lacks bus and class support for being resumed. usbcore: registered new interface driver hci_usb hcid says it can't retrieve BD-address of new device. So it is detected and brought up: Code: twee@home:~# hciconfig hci0 -a hci0: Type: USB BD Address: 00:00:00:00:00:00 ACL MTU: 377:10 SCO MTU: 16:0 UP RUNNING PSCAN ISCAN RX bytes:496 acl:0 sco:0 events:24 errors:0 TX bytes:337 acl:0 sco:0 commands:24 errors:0 twee@home:~# hciconfig hci0 version hci0: Type: USB BD Address: 00:00:00:00:00:00 ACL MTU: 377:10 SCO MTU: 16:0 HCI Ver: 1.1 (0x1) HCI Rev: 0x3 LMP Ver: 1.1 (0x1) LMP Subver: 0x700 Manufacturer: Broadcom Corporation (15) twee@home:~# hciconfig hci0 features hci0: Type: USB BD Address: 00:00:00:00:00:00 ACL MTU: 377:10 SCO MTU: 16:0 Features: 0xff 0xff 0x0d 0x00 0x00 0x00 0x00 0x00 <3-slot packets> <5-slot packets> <encryption> <slot offset> <timing accuracy> <role switch> <hold mode> <sniff mode> <park state> <RSSI> <channel quality> <SCO link> <HV2 packets> <HV3 packets> <u-law log> <A-law log> <CVSD> <power control> <transparent SCO> but it's BD addr is zero and, not surprising, it's not working: Code: # hcitool scan Device is not available: No such device Going thru blueZ sources, I've found that 1sec timeout for reading version info & address from card isn't enough. I increased them to 60s. Now, version info is read (as you may see above), addr is read too, but remains zero Someone has an idea what this can mean?.. Thx in advance. Saludos. -- Para dar de baja la suscripción, mande un mensaje a: opensuse-es+unsubscribe@opensuse.org Para obtener el resto de direcciones-comando, mande un mensaje a: opensuse-es+help@opensuse.org
You posted this question in English... in the Spanish list.
On Fri, Nov 7, 2008 at 9:32 PM, Antonio
El adaptador http://www.linuxquestions.org/hcl/showproduct.php/product/3312/cat/all no he podido hacerlo funcionar con opensuse 11.
Algunas lineas de dmesg:
Linux version 2.6.25.18-0.2-default (geeko@buildhost) (gcc version 4.3.1 20080507 (prerelease) [gcc-4_3-branch revision 135036] (SUSE Linux) ) #1 SMP 2008-10-21 16:30:26 +0200
usb usb2: configuration #1 chosen from 1 choice hub 2-0:1.0: USB hub found hub 2-0:1.0: 2 ports detected usb usb2: New USB device found, idVendor=1d6b, idProduct=0001 usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb2: Product: UHCI Host Controller usb usb2: Manufacturer: Linux 2.6.25.18-0.2-default uhci_hcd usb usb2: SerialNumber: 0000:00:1f.4
usb 2-2: new full speed USB device using uhci_hcd and address 3 PM: Starting manual resume from disk usb 2-2: configuration #1 chosen from 1 choice usb 2-2: New USB device found, idVendor=1131, idProduct=1004 usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 2-2: Product: ISSCEDRBTA usb 2-2: Manufacturer: ISSC Bluetooth: Core ver 2.11 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized iTCO_vendor_support: vendor-support=0 pci_hotplug: PCI Hot Plug PCI Core version: 0.5 iTCO_wdt: Intel TCO WatchDog Timer Driver v1.02 (26-Jul-2007) iTCO_wdt: failed to reset NO_REBOOT flag, reboot disabled by hardware iTCO_wdt: No card detected shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Bluetooth: Generic Bluetooth USB driver ver 0.1 usbcore: registered new interface driver btusb Initializing USB Mass Storage driver... scsi2 : SCSI emulation for USB Mass Storage devices
Bluetooth: HCI USB driver ver 2.9 usbcore: registered new interface driver hci_usb
usb 2-1: new full speed USB device using uhci_hcd and address 4 usb 2-1: configuration #1 chosen from 1 choice usb 2-1: New USB device found, idVendor=1131, idProduct=1004 usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 2-1: Product: ISSCEDRBTA usb 2-1: Manufacturer: ISSC :~ # lsusb Bus 002 Device 004: ID 1131:1004 Integrated System Solution Corp. Bus 002 Device 001: ID 1d6b:0001 Bus 001 Device 001: ID 1d6b:0001
:~ # /usr/sbin/hciconfig hci0: Type: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:0 acl:0 sco:0 commands:0 errors:0 :~ # hcitool scan Device is not available: No such device
Otros usuarios con problemas encontrados con Google:
ES-388 Bluetooth USB dongle not working
[Log in to get rid of this advertisement] Hi all. I have an ES-388 bluetooth adapter which I can't get working properly.
Kernel 2.6.20.1, with BlueZ stack. -- Other Thoughts: In Linux ------------------ modules bluetooth,rfcomm,l2cap,hci_usb lsusb Bus 001 Device 004: ID 1131:1004 Integrated System Solution Corp. lsusb -v Bus 001 Device 004: ID 1131:1004 Integrated System Solution Corp. Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 224 Wireless bDeviceSubClass 1 Radio Frequency bDeviceProtocol 1 Bluetooth bMaxPacketSize0 16 idVendor 0x1131 Integrated System Solution Corp. idProduct 0x1004 bcdDevice 3.73 iManufacturer 1 iProduct 2 iSerial 0 bNumConfigurations 1
Bottomline: It is good... bluez-libs/utils-3.11
Code:
# lsusb Bus 5 Device 33: ID 0a5c:2035 Broadcom Corp. BCM2035 Bluetooth
dmesg shows that: Code:
Bluetooth: Core ver 2.11 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized Bluetooth: HCI USB driver ver 2.9 Device driver usbdev5.30_ep83 lacks bus and class support for being resumed. Device driver usbdev5.30_ep03 lacks bus and class support for being resumed. Device driver hci0 lacks bus and class support for being resumed. usbcore: registered new interface driver hci_usb
hcid says it can't retrieve BD-address of new device.
So it is detected and brought up: Code:
twee@home:~# hciconfig hci0 -a hci0: Type: USB BD Address: 00:00:00:00:00:00 ACL MTU: 377:10 SCO MTU: 16:0 UP RUNNING PSCAN ISCAN RX bytes:496 acl:0 sco:0 events:24 errors:0 TX bytes:337 acl:0 sco:0 commands:24 errors:0
twee@home:~# hciconfig hci0 version hci0: Type: USB BD Address: 00:00:00:00:00:00 ACL MTU: 377:10 SCO MTU: 16:0 HCI Ver: 1.1 (0x1) HCI Rev: 0x3 LMP Ver: 1.1 (0x1) LMP Subver: 0x700 Manufacturer: Broadcom Corporation (15) twee@home:~# hciconfig hci0 features hci0: Type: USB BD Address: 00:00:00:00:00:00 ACL MTU: 377:10 SCO MTU: 16:0 Features: 0xff 0xff 0x0d 0x00 0x00 0x00 0x00 0x00 <3-slot packets> <5-slot packets> <encryption> <slot offset> <timing accuracy> <role switch> <hold mode> <sniff mode> <park state> <RSSI> <channel quality> <SCO link> <HV2 packets> <HV3 packets> <u-law log> <A-law log> <CVSD> <power control> <transparent SCO>
but it's BD addr is zero and, not surprising, it's not working:
Code:
# hcitool scan Device is not available: No such device
Going thru blueZ sources, I've found that 1sec timeout for reading version info & address from card isn't enough. I increased them to 60s. Now, version info is read (as you may see above), addr is read too, but remains zero
Someone has an idea what this can mean?.. Thx in advance.
Saludos. -- Para dar de baja la suscripción, mande un mensaje a: opensuse-es+unsubscribe@opensuse.org Para obtener el resto de direcciones-comando, mande un mensaje a: opensuse-es+help@opensuse.org
-- Saludos, miguel Los agujeros negros son lugares donde dios dividió por cero. Black holes are places where god divided by zero. Steven Wright -- Para dar de baja la suscripción, mande un mensaje a: opensuse-es+unsubscribe@opensuse.org Para obtener el resto de direcciones-comando, mande un mensaje a: opensuse-es+help@opensuse.org
El Viernes, 7 de Noviembre de 2008, miguel gmail escribió:
You posted this question in English... in the Spanish list.
A medias ; ) Aun no se como sacar dmesg en español ;-) Bueno, pues en otro ordenador si me funciona en opensuse 11 32 y con opensuse 11 64, tambien en kubuntu 8.04. Linux version 2.6.25.16-0.1-default (geeko@buildhost) (gcc version 4.3.1 20080507 (prerelease) [gcc-4_3-branch revision 135036] (SUSE Linux) ) #1 SMP 2008-08-21 00:34:25 +0200 Linux version 2.6.25.11-0.1-default (geeko@buildhost) (gcc version 4.3.1 20080507 (prerelease) [gcc-4_3-branch revision 135036] (SUSE Linux) ) #1 SMP 2008-07-13 20:48:28 +0200 Estas lineas no me salen en el ordenador en que no funciona BT. Bluetooth: L2CAP ver 2.9 Bluetooth: L2CAP socket layer initialized Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM ver 1.8 Bluetooth: BNEP (Ethernet Emulation) ver 1.2 Bluetooth: BNEP filters: protocol multicast Saludos. -- Para dar de baja la suscripción, mande un mensaje a: opensuse-es+unsubscribe@opensuse.org Para obtener el resto de direcciones-comando, mande un mensaje a: opensuse-es+help@opensuse.org
2008/11/10, Antonio:
Aun no se como sacar dmesg en español ;-)
:-D
Bueno, pues en otro ordenador si me funciona en opensuse 11 32 y con opensuse 11 64, tambien en kubuntu 8.04.
Linux version 2.6.25.16-0.1-default (geeko@buildhost) (gcc version 4.3.1 20080507 (prerelease) [gcc-4_3-branch revision 135036] (SUSE Linux) ) #1 SMP 2008-08-21 00:34:25 +0200
Linux version 2.6.25.11-0.1-default (geeko@buildhost) (gcc version 4.3.1 20080507 (prerelease) [gcc-4_3-branch revision 135036] (SUSE Linux) ) #1 SMP 2008-07-13 20:48:28 +0200
Estas lineas no me salen en el ordenador en que no funciona BT.
Bluetooth: L2CAP ver 2.9 Bluetooth: L2CAP socket layer initialized Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM ver 1.8 Bluetooth: BNEP (Ethernet Emulation) ver 1.2 Bluetooth: BNEP filters: protocol multicast
Parecen todos protocolos :-? Comprueba los módulos que carga en ambos equipos de bluetooth y usb (en el que funciona y en el que no) para ver diferencias... Saludos, -- Camaleón -- Para dar de baja la suscripción, mande un mensaje a: opensuse-es+unsubscribe@opensuse.org Para obtener el resto de direcciones-comando, mande un mensaje a: opensuse-es+help@opensuse.org
El Lunes, 10 de Noviembre de 2008, Camaleón escribió:
2008/11/10, Antonio:
Aun no se como sacar dmesg en español ;-)
:-D :
Bueno, pues en otro ordenador si me funciona en opensuse 11 32 y con opensuse 11 64, tambien en kubuntu 8.04.
Linux version 2.6.25.16-0.1-default (geeko@buildhost) (gcc version 4.3.1 20080507 (prerelease) [gcc-4_3-branch revision 135036] (SUSE Linux) ) #1 SMP 2008-08-21 00:34:25 +0200
Linux version 2.6.25.11-0.1-default (geeko@buildhost) (gcc version 4.3.1 20080507 (prerelease) [gcc-4_3-branch revision 135036] (SUSE Linux) ) #1 SMP 2008-07-13 20:48:28 +0200
Estas lineas no me salen en el ordenador en que no funciona BT.
Bluetooth: L2CAP ver 2.9 Bluetooth: L2CAP socket layer initialized Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM ver 1.8 Bluetooth: BNEP (Ethernet Emulation) ver 1.2 Bluetooth: BNEP filters: protocol multicast
Parecen todos protocolos :-?
Comprueba los módulos que carga en ambos equipos de bluetooth y usb (en el que funciona y en el que no) para ver diferencias...
Hola CAmaleón. Aqui estan los modulos en el ordenador que funciona: Module Size Used by rfcomm 63392 8 l2cap 44160 12 bnep,rfcomm usb_storage 112928 1 fglrx 2062676 0 hci_usb 34716 0 btusb 25496 2 sg 56912 0 bluetooth 82340 9 bnep,rfcomm,l2cap,hci_usb,btusb ehci_hcd 56204 0 ohci_hcd 42628 0 usbcore 188376 6 usb_storage,hci_usb,btusb,ehci_hcd,ohci_hcd sd_mod 47280 6 edd 28176 0 ahci 51080 3 scsi_mod 195032 4 usb_storage,sg,sd_mod,libata Y aqui donde no funciona: Module Size Used by usb_storage 88584 1 hci_usb 19484 0 btusb 11668 0 bluetooth 61924 2 hci_usb,btusb sg 39732 0 uhci_hcd 28432 0 usbcore 152268 5 usb_storage,hci_usb,btusb,uhci_hcd sd_mod 33048 10 scsi_mod 156148 5 usb_storage,sr_mod,sg,sd_mod,libata Y aqui el lsusb: # lsusb Bus 002 Device 003: ID 13fe:1a00 Bus 002 Device 002: ID 1131:1004 Integrated System Solution Corp. Bus 002 Device 001: ID 1d6b:0001 Bus 001 Device 001: ID 1d6b:0001 # lspci 00:00.0 Host bridge: Intel Corporation 82845 845 [Brookdale] Chipset Host Bridge (rev 03) 00:01.0 PCI bridge: Intel Corporation 82845 845 [Brookdale] Chipset AGP Bridge (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 12) 00:1f.0 ISA bridge: Intel Corporation 82801BA ISA Bridge (LPC) (rev 12) 00:1f.1 IDE interface: Intel Corporation 82801BA IDE U100 Controller (rev 12) 00:1f.2 USB Controller: Intel Corporation 82801BA/BAM USB Controller #1 (rev 12) 00:1f.3 SMBus: Intel Corporation 82801BA/BAM SMBus Controller (rev 12) 00:1f.4 USB Controller: Intel Corporation 82801BA/BAM USB Controller #1 (rev 12) 00:1f.5 Multimedia audio controller: Intel Corporation 82801BA/BAM AC'97 Audio Controller (rev 12) 01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS 02:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) Yo no veo nada aqui. Voy a intentar compilar desde las fuentes. Saludos. -- Para dar de baja la suscripción, mande un mensaje a: opensuse-es+unsubscribe@opensuse.org Para obtener el resto de direcciones-comando, mande un mensaje a: opensuse-es+help@opensuse.org
participants (3)
-
Antonio -
Camaleón -
miguel gmail