Prev: news server
Next: cp slows machine
From: Luis Gomes on 13 Dec 2009 17:50
On 22 oct, 17:48, Mussemouse <Mussemo...(a)somewhere.els> wrote:
> Liberato Esposito wrote:
> > have you moved the old rc.bluetoot to rc.bluetooth.new ???
>
> > you have to do this:
>
> > mv /etc/rc.d/rc.bluetooth /etc/rc.d/rc.bluetooth.old
> > chmod -x /etc/rc.d/rc.bluetooth.old
> > mv /etc/rc.d/rc.bluetooth.new /etc/rc.d/rc.bluetooth
> > /etc/rc.d/rc.bluetooth restart
>
> > in the .new one there aren't any reference to hcid but to bluetoothd
>
> > let me know...
>
> Tried both ways.
> No success. But got a new angel to the problem from the guys at GSB.
> Remove the Slack packages for blues and install their.
> I didn't do exactly that. But I removed the slakc pkgs and installed my
> own newer version. Voila!! It works!
> Only one row in my rc.bluetooth and that one loads the bluetotthd and
> thats all.
> Will continue with it in the weekend to see if everything is as it
> should be.
>
> //Micke

Hello,

I've solved this doing this :
- remove all slacwkare official bluez packages (bluez-*)
- remove directory /etc/bluetooth and files /etc/rc.d/rc.bluetooth*
- use slapt-get --upgrade on Gnome Slack Build (it will found 2
packages : bluez and gnome-bluetooth)
- chmod +x /etc/rc.d/rc.bluetooth
- . /etc/rc.d/rc.bluetooth

After that, all process will be launched (without segfault) and all my
bluetooth periphericals are recognized

--
Luis
http://www.lightning-generator.org

 | 
Pages: 1
Prev: news server
Next: cp slows machine