Mageia forum

Hi everybody, I have no more bluetooth features since I have upgraded to Mageia 2. I use a Hama Dongle that works still fine on my laptop with Mageia 1. So it seems to be ok.
The blueman-manager does not recognise this dongle on my two towers with Mageia 2 (64bit) though it is shown in harddrake as SiW.
If there could anybody help me I would be very happy and thankful.
WilHil

Some devices are similar to software modems, in that they are hybrid devices that have hardware, but to save money, some of their functionality is done using software. If that is the case, trying to get a 32bit device to run in 64bits may be much more difficult to get working if no 64bit 'driver' software exists.

To begin with, you'll need to know more about the bluetooth device at a hardware level.

As root su, run
lsusb

this should show some hexidecimal device ID values identifying your bluetooth device when you plug in your bluetooth.
This will be a likely starting point to seek further information on your particular bluetooth device.

The output of lsusb:

Code: Select all

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 010 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 011 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 002: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
Bus 008 Device 003: ID 413c:3012 Dell Computer Corp. Optical Wheel Mouse
Bus 011 Device 002: ID 0c10:0000

~please use code-tags for terminal-output, thanks

Okay, thought this was going to be easy, but it isn't - I didn't see your Hama in the list you show

The interesting point you mention is that it "does" show-up on your hardware list, so it is recognized at some point as SiW.

Right now, Mageia is going through Alpha testing for the next Mageia 3 release, and it makes good sense to see if you can get this problem fix built into the next release if you can, and if you have the patience to follow through with trying some Alpha releases along the way to report progress.

My suggestion is to get the latest Alpha, or Beta, and try it on the 64bit computer(s) having problems. It doesn't hurt to try on your 586 laptop too just to make sure it didn't regress, just remember to backup your computer before trying so that you can revert back to normal after trying it out. If the alpha or Beta appears to have your Hama as bluetooth, then, consider the problem already solved for the next release, on the other hand, if it isn't there, then it's best if you start a bug report to get this fixed hopefully.

although this isn't the same, it has some similarity, and you can use this as a template https://bugs.mageia.org/show_bug.cgi?id=2753 to help you create your own bug report, and see more-or-less what could possibly be involved along the process of fixing it.
As a note: Make sure to mark your bug report as Mageia3 Alpha N so that it is recognized immediately as something that is of interest for the next release.

I'm also going to attach these URLs just in case there may be something useful within these:

seeing if the Hama appears (as something else):
http://ubuntuforums.org/archive/index.php/t-1080161.html

some possible Hama tar and build info:
http://hometheatersalsa.com/hama-mce-event-client/

some additional Hama info:
http://ptspts.blogspot.ca/2009/10/using-hama-mce-remote-on-linux-with.html

another udev link:
http://wiki.xbmc.org/index.php?title=HOW-TO:Configure_VRC-1100_remote_for_Ubuntu

Best to have this bug report started, and hopefully it gets fixed for Mageia3.
In your bug report, have a link to this thread, since the more info you can pass along, it may help a bit more, and if you don't mind, perhaps listing the bug report here for anyone willing to track it too (in case there are other users with a similar issue searching for help).

I hope this gets you going in the right direction.