DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Hey guys I have a problem with the bluetooth, it doesn't give me any error but doesn't want to connect, also when I turn off the bluetooth from the system tray the wireless card also get disconnected.
Are you on a laptop on which the wireless and the bluetooth turn on and off with the same key?
Do you use network manager (the app, the "opposite" of wicd :P)?
Are you on a laptop on which the wireless and the bluetooth turn on and off with the same key?
Do you use network manager (the app, the "opposite" of wicd :P)?
As for your first question I don't know how to tell LOL, but I remember I didn't had this problem before (maybe 8 months ago), and
yeah I'm using network manager, this is the laptop HP DV5
My assumption is that, if the bluetooth and the wifi functions are controlled by the same hardwara (the same switch I mentioned above), network manager uses it as both, thus it fails as bluetooth.
On the other hand, wicd will only take care of the wifi part and leave bluetooth intact.
I have seen it happening back in early days of "newcomer wicd vs ultrabuggy network manager", so I just mentioned it.
My assumption is that, if the bluetooth and the wifi functions are controlled by the same hardwara (the same switch I mentioned above), network manager uses it as both, thus it fails as bluetooth.
On the other hand, wicd will only take care of the wifi part and leave bluetooth intact.
I have seen it happening back in early days of "newcomer wicd vs ultrabuggy network manager", so I just mentioned it.
Ok so I installed wicd but I'm unable to uninstall network-manager as is a dependency of gnome-core, however I unmanaged the connections on netwrok-manager by editing NetworkManager.conf but still bluetooth doesn't work, also I tried using a bluetooth dongle and still not luck
Gnome-core is a metapackage, so it is safe to remove it.
You can not have 2 network-managing daemons running at the same time.
Plus, who had the great idea of making nm a dependency of the BASIC gnome enviroment? (thumbdown)
Yeah I stopped NM daemon, then starter wicd
This is what it wants to remove
aptitude remove --purge network-manager
Code:
The following packages will be REMOVED:
network-manager
0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 3,847 kB will be freed.
The following packages have unmet dependencies:
network-manager-gnome: Depends: network-manager (>= 0.9.2) but it is not going to be installed.
The following actions will resolve these dependencies:
Remove the following packages:
1) gnome-core
2) network-manager-gnome
Accept this solution? [Y/n/q/?] y
The following packages will be REMOVED:
baobab{pu} crda{pu} dconf-tools{pu} dnsmasq-base{pu} empathy{pu}
empathy-common{pu} fonts-cantarell{pu} freedesktop-sound-theme{pu}
gcalctool{pu} gnome-backgrounds{pu} gnome-core{a} gnome-dictionary{pu}
gnome-disk-utility{pu} gnome-font-viewer{pu} gnome-icon-theme-extras{pu}
gnome-packagekit{pu} gnome-packagekit-data{pu} gnome-search-tool{pu}
gnome-session-canberra{pu} gnome-system-log{pu} gucharmap{pu} iw{pu}
libavahi-ui-gtk3-0{pu} libchamplain-0.12-0{pu}
libchamplain-gtk-0.12-0{pu} libgdict-1.0-6{pu} libgdu-gtk0{pu}
libgeocode-glib0{pu} libjim0debian2{pu} libnetfilter-conntrack3{pu}
libnl-route-3-200{pu} libtelepathy-farsight0{pu}
mobile-broadband-provider-info{pu} modemmanager{pu}
nautilus-sendto-empathy{pu} network-manager network-manager-gnome{a}
telepathy-gabble{pu} telepathy-logger{pu} telepathy-salut{pu}
usb-modeswitch{pu} usb-modeswitch-data{pu} vino{pu} wireless-regdb{pu}
0 packages upgraded, 0 newly installed, 44 to remove and 0 not upgraded.
Updated: wait a minute, I installed blueman and run it, same thing with the laptop bluetooth, it doesn't detect or get detected, but I plugged in the dongle and is working (partially) now it can detect my phone and get detected and receive files but I cannot send files as it gives me an error
Quote:
Service search failed (Host is down)
Error occurred while sending file proxy
Last edited by devianpctek; 01-31-2012 at 08:46 PM.
Reason: Updated
With gnome-bluetooth I can get files from my phone but can not send files to my computer. I don't have any problem getting files from the phone or sending files to the phone.
Code:
chevy@debian:~$ aptitude search ~iblue
i A bluez - Bluetooth tools and daemons
i A gnome-bluetooth - GNOME Bluetooth tools
i A libbluetooth3 - Library to use the BlueZ Linux Bluetooth stack
i A libgnome-bluetooth7 - GNOME Bluetooth tools - support library
this is what is installed on my Squeeze, could be different on Wheezy.
this is what is installed on my Squeeze, could be different on Wheezy.
thanx 62chevy, I have those packages installed as well (but sid's version, I'm running Sid) however on my main pc everything is working fine with the same version, so I'm thinking it could be a hardware problem, because it doesn't get detected or detects any device with the integrated bluetooth,
chevy@sid:~$ aptitude search ~iblue
i A bluez - Bluetooth tools and daemons
i A gir1.2-gnomebluetooth-1.0 - Introspection data for GnomeBluetooth
i A gnome-bluetooth - GNOME Bluetooth tools
i A libbluetooth3 - Library to use the BlueZ Linux Bluetooth stack
i A libgnome-bluetooth8 - GNOME Bluetooth tools - support library
This is what I have installed on Sid and it works the same as Squeeze. I can not send files from the phone to the computer but my computer can see and copy files off/to my phone.
Hope this helps.
If you post an lspci or lsusb that may help find missing firmware you need or someone may know a workaround.
I bought a ASUS USB-BT21 but it shows up as a Broadcom.
Code:
chevy@sid:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 046d:c408 Logitech, Inc. Marble Mouse (4-button)
Bus 005 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 005 Device 003: ID 0a5c:4502 Broadcom Corp. Keyboard (Boot Interface Subclass)
Bus 005 Device 004: ID 0a5c:4503 Broadcom Corp. Mouse (Boot Interface Subclass)
Bus 005 Device 005: ID 0a5c:2148 Broadcom Corp. BCM92046DG-CL1ROM Bluetooth 2.1 Adapter
chevy@sid:~$
If you post an lspci or lsusb that may help find missing firmware you need or someone may know a workaround.
Ok here's lspci
Code:
00:00.0 Host bridge: Advanced Micro Devices [AMD] RS880 Host Bridge
00:01.0 PCI bridge: Advanced Micro Devices [AMD] RS780/RS880 PCI to PCI bridge (int gfx)
00:04.0 PCI bridge: Advanced Micro Devices [AMD] RS780/RS880 PCI to PCI bridge (PCIE port 0)
00:05.0 PCI bridge: Advanced Micro Devices [AMD] RS780/RS880 PCI to PCI bridge (PCIE port 1)
00:11.0 SATA controller: ATI Technologies Inc SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode]
00:12.0 USB controller: ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:12.2 USB controller: ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:13.0 USB controller: ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:13.2 USB controller: ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 42)
00:14.1 IDE interface: ATI Technologies Inc SB7x0/SB8x0/SB9x0 IDE Controller (rev 40)
00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) (rev 40)
00:14.3 ISA bridge: ATI Technologies Inc SB7x0/SB8x0/SB9x0 LPC host controller (rev 40)
00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge (rev 40)
00:14.5 USB controller: ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
00:16.0 USB controller: ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:16.2 USB controller: ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:18.0 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor HyperTransport Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor Link Control
01:05.0 VGA compatible controller: ATI Technologies Inc RS880M [Mobility Radeon HD 4200 Series]
01:05.1 Audio device: ATI Technologies Inc RS880 HDMI Audio [Radeon HD 4200 Series]
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
08:00.0 Network controller: Ralink corp. RT3090 Wireless 802.11n 1T/1R PCIe
lsusb (no bluetooth dongle)
Code:
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 10f1:1a16 Importek
Bus 007 Device 002: ID 148f:1000 Ralink Technology, Corp.
lsusb (with bluetooth dongle)
Code:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 10f1:1a16 Importek
Bus 007 Device 002: ID 148f:1000 Ralink Technology, Corp.
Bus 004 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
I'm out of ideas used google to find your bluetooth dongle and only found old post and bugreports that didn't give any answers. Even found one question on the Debian mailing list with your exact problem but no one answered his question so that was no help.
Hopefully someone with more insight than me can give you some help.
I'm out of ideas used google to find your bluetooth dongle and only found old post and bugreports that didn't give any answers. Even found one question on the Debian mailing list with your exact problem but no one answered his question so that was no help.
Hopefully someone with more insight than me can give you some help.
Thanx 62chevy, well actually my problem is more related with the integrated bluetooth not working at all, because this same dongle works great on my main pc, anyway I'm thinking is a hardware problem, I don't have a way to test it with a different system, oh wait I think I have a live cd laying around somewhere so I'm going to give it a try just to make sure is a hardware issue, because like I said before it was running fine, but I can't remember if it was before the 3.x kernel upgrade, so I'll try with the live cd and post back.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.