From owner-freebsd-current Tue Mar 25 13:29:20 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E36EE37B401; Tue, 25 Mar 2003 13:29:14 -0800 (PST) Received: from scl8owa02.int.exodus.net (scl8out02.exodus.net [66.35.230.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 394D643F75; Tue, 25 Mar 2003 13:29:14 -0800 (PST) (envelope-from Maksim.Yevmenkin@cw.com) Received: from scl8owa01.int.exodus.net ([66.35.230.241]) by scl8owa02.int.exodus.net with Microsoft SMTPSVC(5.0.2195.5329); Tue, 25 Mar 2003 13:29:08 -0800 Received: from exodus.net ([165.193.27.35]) by scl8owa01.int.exodus.net over TLS secured channel with Microsoft SMTPSVC(5.0.2195.5329); Tue, 25 Mar 2003 13:29:08 -0800 Message-ID: <3E80C95B.7040806@exodus.net> Date: Tue, 25 Mar 2003 13:25:47 -0800 From: Maksim Yevmenkin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1) Gecko/20021126 X-Accept-Language: ru, en-us, en MIME-Version: 1.0 To: Tobias Roth , mobile@freebsd.org, current@freebsd.org Subject: Re: Bluetooth on IBM T30 (USB device problem) References: <20030323181910.GA9037@speedy.unibe.ch> <20030324090619.GC13336@speedy.unibe.ch> <3E7F4338.5040405@exodus.net> <3E7F4FE5.3080603@exodus.net> <20030325194710.GA13944@speedy.unibe.ch> <3E80BA67.4060301@exodus.net> <20030325210939.GA14960@speedy.unibe.ch> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 25 Mar 2003 21:29:08.0632 (UTC) FILETIME=[91D51980:01C2F315] X-Spam-Status: No, hits=-18.1 required=5.0 tests=AWL,QUOTED_EMAIL_TEXT,REFERENCES,USER_AGENT_MOZILLA_UA version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Tobias, >>yes it is a CSR chip based device. can you tell if its a USB device? > > yes, it is usb. windows clearly states it as usb. good. then you will most likely get it to work. if you get it to attach (see below). >>1) at loader prompt type (without quotes) "boot -v" >>2) do not press the Bluetooth button just yet >>3) wait until system is fully loaded >>4) kldload ugen (this is only required if you do not have >> "device ugen" the in the kernel config file) >>5) press the Bluetooth button > > did 1), then 5) > > ugen did not attach, instead I got an error. see the attached > files, the error is at the bottom of dmesg. Mar 25 21:59:36 angel5 kernel: uhub2: device problem, disabling port 1 well, this is a USB problem and has nothing to do with Bluetooth. you have a USB hub inside your laptop. for whatever reason USB stack does not like Bluetooth(?) USB devices when they plugged into hub. i have exactly the same problem with my laptop (Toshiba Tecra 8100). when i put it into the docking station (docking station has USB hub inside) my Bluetooth USB dongle stops working :( when i plug device directly into the laptop (without hub) evrything is working fine. i found out that if i unplug and re-plug the dongle quickly several times i can get it to attach. i guess you could try to press the Bluetooth button quickly few times :) i asked several times about this problem, but nobody answered :( you could try to do the same. i guess FreeBSD does not have USB guru anymore :( bottom line: ugen(4) must attach to the device, *if* USB stack attach the device. if you get the device to attach then you most likely will have working Bluetooth. thanks, max To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message