Making Linux no longer old-Bluetooth Installation notes

Making Linux no longer old-Bluetooth Installation notes

1. I read the latest news from www.bluez.org and found that bluez is supported by the latest Linux core, so I am ready to upgrade the core first. 2. The latest core is 2.6.5, so it took some time to study how to upgrade. For more information, see A. Grub man page B .linuxforum.net excellent article on how to upgrade to 2.6.5 3. It took some effort to upgrade the core. At the end of the day, it was impossible to eliminate all the errors during startup. However, this is not the key to the problem. Let's wait for a while. 4. I downloaded all the software packages from www.bluez.org, but I found that I didn't need to compile and install them all. So we compiled bluez-lib and bluez-tools. 5. Start debugging. During the debugging process, refer to the following documents: A. bluez-howto B. Tom's attempts to get GPRS working over Bluetooth with his laptop 6. commands used in debugging: -- Note: Before debugging, check that the bluetooth module has been compiled in the core. A. modprobe hci_usb -- This step is to activate your USB device B. hciconfig hci0 up -- This step is to activate your USB Bluetooth Dongle (USB Bluetooth adapter) C. hcitool Dev -- Check whether your adapter is correctly identified and working properly D. Adjust your mobile phone to the identifiable status. Sdptool search dun -- Search for services on a mobile phone, such as the dial-up connection service E. modprobe RFCOMM -- Activate the RFCOMM protocol of the system. This protocol can simulate a Bluetooth connection as a serial connection. F. Match the mobile phone with the desktop and search for the desktop with the mobile phone. After checking the desktop, enter the matching code. 　 -- Note: If the matching fails, first check whether the file bluepin exists. If not, go to the script in bluez-tools. Yes Scripts written in Python. It uses the/etc/Bluetooth/pin file to match with other devices. Therefore, the matching code sent by the mobile phone must be consistent with the pin file. -- Check the pinhelper item in the/etc/Bluetooth/hcid. conf file. The script called during matching is written here. Check whether the files under the path exist. Otherwise, modify the path and direct it to the real bluepin script. F. RFCOMM bind 0 Bluetooth Add 1 -- Bind your mobile phone to your computer and establish a virtual serial port connection G. minicom-S -- Modify the configuration file of minicom so that it is connected to/dev/ttyub0 by default. (/Dev/ttyub0 is a virtual serial port device connected to your mobile phone)

Original article address Http://www.linuxdiyf.com/bbs/viewthread.php? Tid = 1824 & fpage = 3