Suse/NovellThis Forum is for the discussion of Suse Linux.
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I'm trying to get my Yakumo USB Bluetooth Dongle to work (the same dongle works on Suse 9.3 but doesn't on 10.0 now ).
All bluez-packages are installed....
When I plug in the dongle /var/log/messages tells me
Nov 11 18:41:10 linux kernel: usb 3-1: new full speed USB device using uhci_hcd and address 3
Nov 11 18:41:10 linux hcid: HCI dev 0 registered
Nov 11 18:42:47 linux kernel: hci_cmd_task: hci0 command tx timeout
KBluetoothD in kicker is always gray and I can't right click the symbol for example when dongle is plugged in.
When I unplug the dongle I get a KBluetoothD message which says "Bluetooth adapter was unplugged".... hmm, why it recognize it when I unplug it !?
I've got a belkin f8t003 ver 2 usb dongle. I get these lines in the messages log
Nov 25 19:22:51 linux hcid: HCI dev 0 unregistered Nov 25 19:22:51 linux kernel: usb 1-1: USB disconnect, address 2 Nov 25 19:22:57 linux kernel: usb 1-1: new full speed USB device using uhci_hcd and address 3 Nov 25 19:22:57 linux hcid: HCI dev 0 registered Nov 25 19:23:03 linux kernel: hci_cmd_task: hci0 command tx timeout
and the "bluetooth unplugged" message when removed.
It seems as hough the kbluetooth program stalls untill I remove the dongle, if you click the grey icon while the dongle is inserted, nothing happens until you remove the dongle.
I also get three "Could not connect to sdp server" warnings that I used to get on Suse 9.3, but on that Suse the bluetooth got initialized right after the last warning.
SuSE made considerable changes in the are of auto-mounting. When I first installed 10.0 there were some quirks with USB memory sticks. It was possible for Linux to remember a stick was plugged in but get confused about permissions. Removing the stick and plugging it back in brought everything into sync. It would appear that updates via SuSE watcher have fixed that problem. So I have two suggestions 1st have you been updating? 2nd will re-inserting after removal get it to work?
Hmmm, played again and again with the pin file and also in yast - bluetooth with secrets disabled and enabled it again, restartet bluetooth service.... and so on...
Then obex push (send file from pc) worked and also after some testing the obex ftp from konqueror worked. Now I also can make my rfcomm0 .....
The only thing which doesn't work is when I try to send a file from my phone to the pc the phone says "send" but at my pc I don't get a dialog which ask me how to store this file. So it goes to nirvana I think...
As said from konqueror-obex-ftp I come to my phone folder structure and can copy files from handy to pc!
Bluetooth has protocols which are subject to the variability of software. Your phone may be the culprit or perhaps Linux needs to be a bit more forgiving of Bluetooth protocols. OpenSuSE may want to look into this. Why not report it as a potential bug. Excuse my curiosity, but are you a Brit? The UK is the only place I remember hearing a cell phone called a handy.