Thanks!
Going from uhci to usb-uhci solved it. The strange part is that I had a alias
in /etc/modules.conf to use usb-uhci, but uhci was getting loaded, as I found
when I did a lsmod. Forcing the loading of uhci in /etc/modules seems to have
solved the problem.
---
Jose Bernardo B R Silva | Source Mage GNU/Linux Section Guru
jbernardo@xxxxxxxxxxxxxx | http://www.sourcemage.org
http://counter.li.org #245602
http://cosmos.oninetspeed.pt/jose.bernardo
jbs@xxxxxxxxxxxxxxxxxxxx
---------- Original Message -----------
From: Max Krasnyansky <maxk@xxxxxxxxxxxx>
To: "Jose Bernardo Silva" <jbs@xxxxxxxxxxxxxxxxxxxx>,
bluez-users@xxxxxxxxxxxxxxxxxxxxx
Sent: Tue, 24 Jun 2003 11:09:06 -0700
Subject: Re: ACL tx timeout (was Re: [Bluez-users] Unable to connect panu to
pan)
> Jose,
>
> First try to switch from usb-uhci.o to uhci.o (or vice versa).
> If that doesn't help.
>
> Try to decrease number of outstanding bulk TX requests.
> In the file drivers/bluetooth/hci_usb.h
> Replace
> #define HCI_MAX_BULK_TX 4
> with
> #define HCI_MAX_BULK_TX 1
> Recompile and reload hci_usb module.
>
> Does that help ?
>
> Max
>
> At 03:11 AM 6/24/2003, Jose Bernardo Silva wrote:
> >More data:
> >I have a second machine at work, which is working as a NAP. That machine has
> >Mandrake 9.1, kernel 2.4.21-018 ("uname -sr" output: "Linux
> >2.4.21-0.18mdksecure"), and the following bluez packages installed:
> >
> ># rpm -qa | grep bluez
> >bluez-bluefw-0.9-2mdk
> >bluez-hciemu-1.0-1mdk
> >libbluez1-2.4-1mdk
> >bluez-pan-1.1-1mdk
> >libbluez1-devel-2.4-1mdk
> >bluez-hcidump-1.5-1mdk
> >libbluez-sdp2-1.1-1mdk
> >libbluez-sdp2-devel-1.1-1mdk
> >bluez-utils-2.3-2mdk
> >bluez-sdp-1.1-1mdk
> >
> >
> ># hciconfig -a
> >hci0: Type: USB
> > BD Address: 00:10:DC:71:DC:5E ACL MTU: 192:8 SCO MTU: 64:8
> > UP RUNNING PSCAN ISCAN AUTH ENCRYPT
> > RX bytes:136854 acl:760 sco:0 events:531 errors:0
> > TX bytes:91493 acl:664 sco:0 commands:15 errors:0
> > Features: 0xff 0xff 0x0f 0x00
> > Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
> > Link policy: HOLD SNIFF PARK
> > Link mode: SLAVE ACCEPT
> > Name: 'DeskRed (0)'
> > Class: 0x000100
> > Service Classes: Unspecified
> > Device Class: Computer, Uncategorized
> > HCI Ver: 1.1 (0x1) HCI Rev: 0x20d LMP Ver: 1.1 (0x1) LMP Subver:
> > 0x20d
> > Manufacturer: Cambridge Silicon Radio (10)
> >
> >As you can see, the MSI dongle has the same firmware as the one I have at
> >home. The command line parameters to PAND are also exactly the same
> >(/usr/bin/pand -E --listen --role NAP). Any ideas why this works, and I am
> >able to connect from my laptop (the machine described below as PANU), and the
> >other one gives the ACL tx timeout and then blocks, as I posted previously?
> >
> >Thanks!
> >
> >---
> >Jose Bernardo B R Silva | Source Mage GNU/Linux Section Guru
> >jbernardo@xxxxxxxxxxxxxx | http://www.sourcemage.org
> >http://counter.li.org #245602
> >http://cosmos.oninetspeed.pt/jose.bernardo
> >jbs@xxxxxxxxxxxxxxxxxxxx
> >
> >
> >---------- Original Message -----------
> >From: "Jose Bernardo Silva" <jbs@xxxxxxxxxxxxxxxxxxxx>
> >To: "Jose Bernardo Silva" <jbs@xxxxxxxxxxxxxxxxxxxx>,
> >bluez-users@xxxxxxxxxxxxxxxxxxxxx
> >Sent: Sat, 21 Jun 2003 12:09:03 +0000
> >Subject: ACL tx timeout (was Re: [Bluez-users] Unable to connect panu to pan)
> >
> >> Well, I spoke too soon. Now I get the dreaded "[kernel]
> >> hci_acl_tx_to: hci0 ACL tx timeout" error on the NAP pc, and from
> >> then on I can't connect again, getting only the "link key request"
> >> entries on the NAP and the following on the PANU:
> >>
> >> Jun 21 13:02:44 [pand] bnep0 disconnected : Connection reset by peer
> >> Jun 21 13:02:49 [pand] Inquiring
> >> Jun 21 13:03:02 [pand] Searching for NAP on 00:10:DC:AF:E1:13
> >> Jun 21 13:03:02 [hcid] link_key_request (sba=0E:96:32:57:60:00,
> >> dba=13:E1:AF:DC:10:00)
> >>
> >> Jun 21 13:03:42 [pand] Failed to connect to the SDP server.
> >> Connection timed out(110)
> >> Jun 21 13:03:47 [pand] Inquiring
> >> Jun 21 13:04:00 [pand] Searching for NAP on 00:10:DC:AF:E1:13
> >> Jun 21 13:04:00 [hcid] link_key_request (sba=0E:96:32:57:60:00,
> >> dba=13:E1:AF:DC:10:00)
> >>
> >> Any ideas, any new data needed?
> >>
> >> ---
> >> Jose Bernardo B R Silva | Source Mage GNU/Linux Section Guru
> >> jbernardo@xxxxxxxxxxxxxx | http://www.sourcemage.org
> >> http://counter.li.org #245602
> >> http://cosmos.oninetspeed.pt/jose.bernardo
> >> jbs@xxxxxxxxxxxxxxxxxxxx
> >>
> >> ---------- Original Message -----------
> >> From: "Jose Bernardo Silva" <jbs@xxxxxxxxxxxxxxxxxxxx>
> >> To: bluez-users@xxxxxxxxxxxxxxxxxxxxx
> >> Sent: Sat, 21 Jun 2003 11:39:00 +0000
> >> Subject: Re: [Bluez-users] Unable to connect panu to pan
> >>
> >> > Answering myself - the /etc/init.d/bluetooth file had been replaced
> >> > on the NAP computer, so pand wasn't being started. Sorry for all the
> >> > trouble - it seems that with 2.4.21-mh2 connections recover properly
> >> > after a timeout.
> >> >
> >> > Now all I have to fix are the "[kernel] usb_control/bulk_msg:
> >> > timeout" I get by the dozen when connecting the acer usb dongle to
> >> > the PANU pc...
> >> >
> >> > ---
> >> > Jose Bernardo B R Silva | Source Mage GNU/Linux Section Guru
> >> > jbernardo@xxxxxxxxxxxxxx | http://www.sourcemage.org
> >> > http://counter.li.org #245602
> >> > http://cosmos.oninetspeed.pt/jose.bernardo
> >> > jbs@xxxxxxxxxxxxxxxxxxxx
> >> >
> >> > ---------- Original Message -----------
> >> > From: "Jose Bernardo Silva" <jbs@xxxxxxxxxxxxxxxxxxxx>
> >> > To: bluez-users@xxxxxxxxxxxxxxxxxxxxx
> >> > Sent: Fri, 20 Jun 2003 19:10:57 +0000
> >> > Subject: [Bluez-users] Unable to connect panu to pan
> >> >
> >> > > Hi!
> >> > >
> >> > > I had some troubles since I updated the kernels on my two machines from
> >> > >
> >> > > 2.4.20-mh3 (I think) to 2.4.21-mh2. I was able to connect only after
> >> > > both usb bluetooth dongles had been connected, and for a short
> >> > > while. Then I would get a ACL TX timeout on the PANU machine, and
> >> > > would never be able to connect until I disconnected and reconnected
> >> > > the dongle on the PAN machine. So, I decided to update SDP from 1.1
> >> > > to 1.2, all other packages were already up to date (utils
> >> > > 2.3, libs 2.4, pan 1.1). Now I am always unable to connect, and no
> >> > > message is bening shown. I deleted both link_key files, restarted
> >> > > bluetooth on both machines, and got asked for the link key, but I am
> >> > > still unable to connect. Here are the relevant entries from syslog
> >> > > on the panu machine:
> >> > >
> >> > > [...]
> >> > > Jun 20 20:06:15 [pand] Inquiring
> >> > > Jun 20 20:06:15 [pand] Searching for NAP on 00:10:DC:AF:E1:13
> >> > >
> >> > > Jun 20 20:06:16 [hcid] link_key_request (sba=0E:96:32:57:60:00,
> >> dba=13:E1:AF:DC:
> >> > > 10:00)
> >> > > Jun 20 20:06:22 [pand] Inquiring
> >> > > Jun 20 20:06:35 [pand] Searching for NAP on 00:10:DC:AF:E1:13
> >> > >
> >> > > Jun 20 20:06:35 [hcid] link_key_request (sba=0E:96:32:57:60:00,
> >> dba=13:E1:AF:DC:
> >> > > 10:00)
> >> > > Jun 20 20:06:41 [pand] Inquiring
> >> > > Jun 20 20:06:41 [pand] Searching for NAP on 00:10:DC:AF:E1:13
> >> > >
> >> > > Jun 20 20:06:42 [hcid] link_key_request (sba=0E:96:32:57:60:00,
> >> dba=13:E1:AF:DC:
> >> > > 10:00)
> >> > > [...]
> >> > >
> >> > > And the PAN machine shows the corresponding "[hcid]
> >> > > link_key_request" entries.
> >> > >
> >> > > hciconfig -a (PANU machine, ACER dongle)
> >> > > hci0: Type: USB
> >> > > BD Address: 00:60:57:32:96:0E ACL MTU: 192:8 SCO MTU: 64:8
> >> > > UP RUNNING PSCAN ISCAN AUTH ENCRYPT
> >> > > RX bytes:13247 acl:325 sco:0 events:947 errors:0
> >> > > TX bytes:10516 acl:325 sco:0 commands:314 errors:0
> >> > > Features: 0xff 0xff 0x0b 0x00
> >> > > Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
> >> > > Link policy: RSWITCH HOLD SNIFF PARK
> >> > > Link mode: SLAVE ACCEPT
> >> > > Name: 'Port-Jbs (0)'
> >> > > Class: 0x000100
> >> > > Service Classes: Unspecified
> >> > > Device Class: Computer, Uncategorized
> >> > > HCI Ver: 1.1 (0x1) HCI Rev: 0x175 LMP Ver: 1.1 (0x1) LMP
> >> > > Subver: 0x175 Manufacturer: Cambridge Silicon Radio (10)
> >> > >
> >> > > hciconfig -a (PAN machine, MSI dongle)
> >> > > hci0: Type: USB
> >> > > BD Address: 00:10:DC:AF:E1:13 ACL MTU: 192:8 SCO MTU: 64:8
> >> > > UP RUNNING PSCAN ISCAN AUTH ENCRYPT
> >> > > RX bytes:11221 acl:260 sco:0 events:844 errors:0
> >> > > TX bytes:7416 acl:260 sco:0 commands:219 errors:0
> >> > > Features: 0xff 0xff 0x0f 0x00
> >> > > Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
> >> > > Link policy: RSWITCH HOLD SNIFF PARK
> >> > > Link mode: SLAVE ACCEPT
> >> > > Name: 'Jbs_Linux (0)'
> >> > > Class: 0x000100
> >> > > Service Classes: Unspecified
> >> > > Device Class: Computer, Uncategorized
> >> > > HCI Ver: 1.1 (0x1) HCI Rev: 0x20d LMP Ver: 1.1 (0x1) LMP
> >> > > Subver: 0x20d Manufacturer: Cambridge Silicon Radio (10)
> >> > >
> >> > > The ACER isn't able to update the firmware (always times out).
> >> > >
> >> > > Any ideas?
> >> > >
> >> > > Thanks!
> >> > >
> >
> >> ------- End of Original Message -------
> >------- End of Original Message -------
> >
> >
> >
> >-------------------------------------------------------
> >This SF.Net email is sponsored by: INetU
> >Attention Web Developers & Consultants: Become An INetU Hosting Partner.
> >Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
> >INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
> >_______________________________________________
> >Bluez-users mailing list
> >Bluez-users@xxxxxxxxxxxxxxxxxxxxx
> >https://lists.sourceforge.net/lists/listinfo/bluez-users
------- End of Original Message -------
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
|
