Difference between revisions of "IBM Integrated Bluetooth IV with 56K Modem (BMDC-3)"

From ThinkWiki
Jump to: navigation, search
(Linux Bluetooth driver)
m (re-identified modem, changed chipset name for more accuracy)
 
(26 intermediate revisions by 12 users not shown)
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
 
{| width="100%"
 
{| width="100%"
|style="vertical-align:top" |[[Image:Logo_bluetooth.jpg|Bluetooth Logo]]
+
|style="vertical-align:top" |
 
|style="vertical-align:top" |
 
|style="vertical-align:top" |
 
<div style="margin:0px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
 
<div style="margin:0px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
 
=== IBM Integrated Bluetooth IV with 56K Modem (BMDC-3) ===
 
=== IBM Integrated Bluetooth IV with 56K Modem (BMDC-3) ===
This is a combination USB Bluetooth and AC97 Modem Adapter that is installed in a [[CDC slot]].
+
This is a combination AC'97 Bluetooth and Modem Adapter that is installed in a [[CDC slot]].
=== Bluetooth Features ===
+
 
* Chipset: Broadcom
+
=== Features ===
* USB VID/PID: 0A5C:201E
+
* Chipset: Broadcom BCM2035 Bluetooth Controller and Conexant SmartV.92 Softmodem Controller
=== Modem Features ===
+
* Speeds: 434/723 Kbps (Bluetooth 1.2) and 33.6/56.6 Kbps (V.34/V.90/V.92/K56flex)
* Chipset: Conexant
+
* PCI ID: Varies, depends on the AC'97 modem controller's PCI ID
* AC'97 Modem
+
* USB ID: 0A5C:201E
 +
* Headers: One 2-pin connector, one Hirose U.FL connector
 
</div>
 
</div>
 
|}
 
|}
=== IBM Partnumbers ===
+
=== Partnumbers ===
 
*IBM FRU PN: 39T0022 ($37.50 in July 2005) - ''no longer available at IBM''
 
*IBM FRU PN: 39T0022 ($37.50 in July 2005) - ''no longer available at IBM''
 
*IBM FRU PN: 39T0024 ($49.00 in September 2005) - ''no longer available at IBM''
 
*IBM FRU PN: 39T0024 ($49.00 in September 2005) - ''no longer available at IBM''
*IBM FRU PN: 39T0026 ($46.00 in October 2005)
+
*IBM FRU PN: 39T0026 ($56 in Dec 2006, $50.00 in July 2006)
  
 
This part takes the place of the 56K Modem board.
 
This part takes the place of the 56K Modem board.
It requires a Bluetooth antenna, and some ThinkPads built without Bluetooth already have the antenna installed -- the antenna wire may be found disconnected and taped under the Modem board.
+
It requires a Bluetooth antenna, and some ThinkPads built without Bluetooth already have the antenna installed -- the antenna wire may be found disconnected and taped under the Modem board.  
 +
{{HINT|To check if your T4x laptop has a BlueTooth antenna, check the parts list for the specific model. More directly, you can check whether there is a white antenna wire (in addition to the two WiFi antenna cables, which are gray and black) passing through the left LCD hinge: either peek through the small hole in front of the left hinge, or remove the keyboard and inspect the wires near the CDC (see [[:Image:T43-2686-DGU-CDC.jpg|here]] or [http://www.pbase.com/kenn/t42_bluetooth here]).}}
  
In addition to the Modem/BT module, a Bluetooth Thinkpad also uses an extra indicator LED below the LCD display, and another indicator LED on the top of the lid.  To see these two LEDs, two new clear plates are required.  The entire set of replacement sticker plates can be ordered as FRU 26R8409 ($12 as of July 2005). (formerly FRU: 13R2455)
+
In addition to the Modem/BT module, a Bluetooth Thinkpad also uses an extra indicator LED below the LCD display, and another indicator LED on the top of the lid.  To see these two LEDs, two new clear plates are required.  The entire set of replacement sticker plates can be ordered as FRU 26R8409 (unavailable as of Dec 2006; $16.50 as of March 2006; formerly FRU 13R2455)
 +
 
 +
As of January 2006, IBM charged $13.50 for airborne shipping.
 +
 
 +
See [[Buyers_Guide#Buying_FRUs|Buying FRUs]].
  
 
=== Linux Bluetooth driver ===
 
=== Linux Bluetooth driver ===
The Bluetooth device is implemented using USB. Enabling/disabling bluetooth leads to USB connect and disconnect events. It can be enabled or disabled by:
+
The Bluetooth device is implemented using USB. Enabling/disabling bluetooth (i.e. by use of {{key|Fn}}{{key|F5}}) leads to USB connect and disconnect events.
  
* pressing the {{key|Fn}}{{key|F5}} key combination;
+
As Bluetooth is implemented using USB, this will only work with USB drivers enabled:
* using [[ibm-acpi]].
+
:{{cmdroot|modprobe uhci-hcd ; modprobe ehci-hcd}}
  
The bcm203x kernel module, which is included in recent kernels, supports this chipset. Since the Bluetooth device is using USB, you have to make sure to '''compile it as a module'''. If it's built into the kernel, the kernel won't detect the chip at boottime (when Bluetooth is turned off).
+
The <tt>bcm203x</tt> kernel module, which is included in recent kernels, supports this chipset. You have to make sure to '''compile it as a module''' since the kernel won't detect the chip at boottime (when Bluetooth is turned off).
  
Use bluez-utils (http://www.bluez.org/) or fancier software like the GNOME Bluetooth subsystem (http://usefulinc.com/software/gnome-bluetooth) to use the device.
+
Use BlueZ-utils (http://www.bluez.org/) or fancier software like the GNOME Bluetooth subsystem (http://usefulinc.com/software/gnome-bluetooth) to use the device.
  
 
Some problems have been reported using bluetooth after a suspend/resume cycle on the T43. These problems can be mitigated by unloading the USB kernel modules (uhci_hcd, ehci_hcd, hci_usb, bcm203x) before the machine is put to sleep, and by re-loading these modules when the machine wakes up again.
 
Some problems have been reported using bluetooth after a suspend/resume cycle on the T43. These problems can be mitigated by unloading the USB kernel modules (uhci_hcd, ehci_hcd, hci_usb, bcm203x) before the machine is put to sleep, and by re-loading these modules when the machine wakes up again.
  
On a T43p you must ensure that you call hotplug (re)start upon resume or you will lose bluetooth functionality. See the ACPI area for sample suspend scripts, or if bluetooth flakes on a debian system at any time you can manually call
+
You could also try [http://www.kernel.org/git/?p=linux/kernel/git/holtmann/bluetooth-2.6.git;a=commitdiff_plain;h=dcdcf63ef12dc3fbaa17a6d04f16ada8e63bb4d0;hp=2b86ad21deec4c47a1f0089298f12e4038c2aa68 this patch] which adds suspend/resume support to the hci_usb module. This patch is already in kernel 2.6.18-rc1. Or you use the [http://www.holtmann.org/linux/kernel/patch-2.6.17-mh4.gz bluez mh4-patch for 2.6.17] which adds suspend/resume and also fixes an issue with the SCO buffer size.
  
:/etc/init.d/hotplug restart
+
On a T43p you must ensure that you call hotplug (re)start upon resume or you will lose bluetooth functionality. See the ACPI area for sample suspend scripts, or if bluetooth flakes on a debian system at any time you can manually call
 +
:{{cmdroot|/etc/init.d/hotplug restart}}
 +
and it will come back with another {{key|Fn}}{{key|F5}} press.
  
and then it will come back with another {{key|Fn}}{{key|F5}} press.
+
=== Linux modem driver ===
 +
See [[Conexant HSF modem drivers]].
  
=== Linux Modem driver ===
+
===See also===
Although, the [http://www.smlink.com/ Smartlink] driver for Agere modems is able to communicate with the modem via AT commands, it cannot dial out (contradicting reports welcome!).
+
* [[How to setup Bluetooth | Bluetooth HOWTO]]
 
+
If your favourite distribution does not include a hsfmodem driver (search for "hsfmodem" or "Conexant"), you can try the one from Linuxant: http://www.linuxant.com/drivers (14k free as in beer, 56k+Fax license 15$, they explain this policy under: http://www.linuxant.com/store/faq.php )
+
 
+
=== ThinkPads this card may be found in ===
+
* {{R52}}
+
* {{T43}}, {{T43p}}
+
* {{X32}}
+
* {{X41}}, {{X41T}}
+
* {{Z60m}}, {{Z60t}}
+
  
 
===External Sources===
 
===External Sources===
 
*[http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-51427 IBM's page about configuring Bluetooth under Linux]
 
*[http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-51427 IBM's page about configuring Bluetooth under Linux]
  
 +
== This card may be found in ==
 +
* {{T43}}, {{T43p}}
 +
* {{X32}}, {{X41}}, {{X41 Tablet}}
 +
* {{R52}}
  
 
[[Category:Components]]
 
[[Category:Components]]

Latest revision as of 12:32, 24 December 2019

IBM Integrated Bluetooth IV with 56K Modem (BMDC-3)

This is a combination AC'97 Bluetooth and Modem Adapter that is installed in a CDC slot.

Features

  • Chipset: Broadcom BCM2035 Bluetooth Controller and Conexant SmartV.92 Softmodem Controller
  • Speeds: 434/723 Kbps (Bluetooth 1.2) and 33.6/56.6 Kbps (V.34/V.90/V.92/K56flex)
  • PCI ID: Varies, depends on the AC'97 modem controller's PCI ID
  • USB ID: 0A5C:201E
  • Headers: One 2-pin connector, one Hirose U.FL connector

Partnumbers

  • IBM FRU PN: 39T0022 ($37.50 in July 2005) - no longer available at IBM
  • IBM FRU PN: 39T0024 ($49.00 in September 2005) - no longer available at IBM
  • IBM FRU PN: 39T0026 ($56 in Dec 2006, $50.00 in July 2006)

This part takes the place of the 56K Modem board. It requires a Bluetooth antenna, and some ThinkPads built without Bluetooth already have the antenna installed -- the antenna wire may be found disconnected and taped under the Modem board.

Hint:
To check if your T4x laptop has a BlueTooth antenna, check the parts list for the specific model. More directly, you can check whether there is a white antenna wire (in addition to the two WiFi antenna cables, which are gray and black) passing through the left LCD hinge: either peek through the small hole in front of the left hinge, or remove the keyboard and inspect the wires near the CDC (see here or here).

In addition to the Modem/BT module, a Bluetooth Thinkpad also uses an extra indicator LED below the LCD display, and another indicator LED on the top of the lid. To see these two LEDs, two new clear plates are required. The entire set of replacement sticker plates can be ordered as FRU 26R8409 (unavailable as of Dec 2006; $16.50 as of March 2006; formerly FRU 13R2455)

As of January 2006, IBM charged $13.50 for airborne shipping.

See Buying FRUs.

Linux Bluetooth driver

The Bluetooth device is implemented using USB. Enabling/disabling bluetooth (i.e. by use of FnF5) leads to USB connect and disconnect events.

As Bluetooth is implemented using USB, this will only work with USB drivers enabled:

# modprobe uhci-hcd ; modprobe ehci-hcd

The bcm203x kernel module, which is included in recent kernels, supports this chipset. You have to make sure to compile it as a module since the kernel won't detect the chip at boottime (when Bluetooth is turned off).

Use BlueZ-utils (http://www.bluez.org/) or fancier software like the GNOME Bluetooth subsystem (http://usefulinc.com/software/gnome-bluetooth) to use the device.

Some problems have been reported using bluetooth after a suspend/resume cycle on the T43. These problems can be mitigated by unloading the USB kernel modules (uhci_hcd, ehci_hcd, hci_usb, bcm203x) before the machine is put to sleep, and by re-loading these modules when the machine wakes up again.

You could also try this patch which adds suspend/resume support to the hci_usb module. This patch is already in kernel 2.6.18-rc1. Or you use the bluez mh4-patch for 2.6.17 which adds suspend/resume and also fixes an issue with the SCO buffer size.

On a T43p you must ensure that you call hotplug (re)start upon resume or you will lose bluetooth functionality. See the ACPI area for sample suspend scripts, or if bluetooth flakes on a debian system at any time you can manually call

# /etc/init.d/hotplug restart

and it will come back with another FnF5 press.

Linux modem driver

See Conexant HSF modem drivers.

See also

External Sources

This card may be found in