| View previous topic :: View next topic |
| Author |
Message |
simone-27
Tux's lil' helper
Joined: 19 Feb 2007
Posts: 118
|
 Posted: Fri Mar 23, 2007 10:14 pm Post subject: problema configurazione bluetooth |
 |
|
Ho seguito questa guida http://www.gentoo.org/doc/en/bluetooth-guide.xml, sono arrivato ad avviare il bluetooth dando
| Code: | | /etc/init.d/bluetooth start |
mi da il seguente output
| Code: | * Starting Bluetooth ...
* Starting hcid ... [ ok ]
* Starting sdpd ... [ !! ]
* Starting rfcomm ...
Can't open RFCOMM control socket: Protocol not supported [ ok ] |
quale puo essere il problema? |
|
| Back to top |
|
 |
simone-27
Tux's lil' helper
Joined: 19 Feb 2007
Posts: 118
|
| Posted: Mon Mar 26, 2007 10:52 pm Post subject: |
|
|
nessuno che mi sa dare una mano??  |
|
| Back to top |
|
|
cloc3
Advocate
Joined: 13 Jan 2004
Posts: 4810
Location: http://www.gentoo-users.org/user/cloc3/
|
| Posted: Tue Mar 27, 2007 4:12 am Post subject: |
|
|
| simone-27 wrote: | | nessuno che mi sa dare una mano?? |
ad occhio è un problema di kernel. non ti so dire di più perché non possiedo un bluetooth.
trattandosi di un problema non strettamente inerente a gentoo, in questi casi, è meglio fare una ricerchina su google.
_________________
vu vu vu
gentù
mi piaci tu |
|
| Back to top |
|
|
IlGab
Guru
Joined: 26 Nov 2004
Posts: 486
|
| Posted: Tue Mar 27, 2007 9:10 am Post subject: |
|
|
Suggerirei un
| Code: | Networking --->
<M> Bluetooth subsystem support --->
<M> RFCOMM protocol support |
Nel kernel. |
|
| Back to top |
|
|
simone-27
Tux's lil' helper
Joined: 19 Feb 2007
Posts: 118
|
| Posted: Sun Apr 08, 2007 2:03 pm Post subject: |
|
|
Ho scoperto che dando
e poi
| Code: | | /etc/init.d/bluetooth start |
si avvia senza dare problemi, come fare perche si avvii dall accensione?
ho provato con
| Code: | | echo "rfcomm" >> /etc/modules.autoload.d/kernel |
ma comunque al riavvio bisogna ridare
Idee?Grazie. |
|
| Back to top |
|
|
skypjack
l33t
Joined: 05 Aug 2006
Posts: 884
Location: Italia - Firenze
|
| Posted: Sun Apr 08, 2007 2:17 pm Post subject: |
|
|
| Se ti serve sempre e comunque, hai pensato che potresti inglobarlo nel kernel?? |
|
| Back to top |
|
|
simone-27
Tux's lil' helper
Joined: 19 Feb 2007
Posts: 118
|
| Posted: Sun Apr 08, 2007 2:44 pm Post subject: |
|
|
si ok, ma io ho semplicemente seguito la guida e c' era scritto di configurare cosi
| Code: | Networking --->
<*> Bluetooth subsystem support --->
--- Bluetooth subsystem support
<M> L2CAP protocol support
<M> SCO links support
<M> RFCOMM protocol support
[*] RFCOMM TTY support
<M> BNEP protocol support
[*] Multicast filter support
[*] Protocol filter support
<M> HIDP protocol support
Bluetooth device drivers --->
<M> HCI USB driver
[*] SCO (voice) support
<M> HCI UART driver
[*] UART (H4) protocol support
[*] BCSP protocol support
[*] Transmit CRC with every BCSP packet
<M> HCI BCM203x USB driver
<M> HCI BPA10x USB driver
<M> HCI BlueFRITZ! USB driver
(The four drivers below are for PCMCIA Bluetooth devices and will only
show up if you have also selected PCMCIA support in your kernel.)
<M> HCI DTL1 (PC Card) driver
<M> HCI BT3C (PC Card) driver
<M> HCI BlueCard (PC Card) driver
<M> HCI UART (PC Card) device driver
(The driver below is intended for HCI Emulation software.)
<M> HCI VHCI (Virtual HCI device) driver
(Move back three levels to Device Drives and then check if USB is
enabled. This is required if you use a Bluetooth dongle, which are mostly USB
based.)
USB support --->
<*> Support for Host-side USB
--- USB Host Controller Drivers
<M> EHCI HCD (USB 2.0) support
[ ] Full speed ISO transactions (EXPERIMENTAL)
[ ] Root Hub Transaction Translators (EXPERIMENTAL)
<*> OHCI HCD support
<*> UHCI HCD (most Intel and VIA) support
< > SL811HS HCD support |
Secondo te integro nel kernel solo rfcomm oppure tutto cio che riguarda il bluetooth? |
|
| Back to top |
|
|
Ic3M4n
Advocate
Joined: 02 Nov 2004
Posts: 3489
Location: Bergamo.
|
| Posted: Sun Apr 08, 2007 5:22 pm Post subject: |
|
|
echo "rfcomm" >> /etc/modules.autoload.d/kernel-2.6  |
|
| Back to top |
|
|
MeMyselfAndI
l33t
Joined: 15 Nov 2005
Posts: 784
Location: Between the monitor and the chair
|
| Posted: Sun Apr 08, 2007 7:36 pm Post subject: |
|
|
| Strano comportamento, con udev i moduli per le periferiche dovrebbere essere caricati autonomamente senza necessita' di aggiungerli ad autoload.d/kernel-2.6 |
|
| Back to top |
|
|
simone-27
Tux's lil' helper
Joined: 19 Feb 2007
Posts: 118
|
| Posted: Sun Apr 08, 2007 11:03 pm Post subject: |
|
|
| infatti ad esempio il modulo nvidia lo carica automaticamente udev....non capisco perche questo bisogna metterlo in /etc/modules.autoload.d/kernel-2.6!! |
|
| Back to top |
|
|
IlGab
Guru
Joined: 26 Nov 2004
Posts: 486
|
| Posted: Tue Apr 10, 2007 12:08 pm Post subject: |
|
|
RFCOMM è un protocollo e non un driver di periferica
| Code: | RFCOMM provides connection oriented stream transport. RFCOMM
support is required for Dialup Networking, OBEX and other Bluetooth
applications. |
|
|
| Back to top |
|
|
skypjack
l33t
Joined: 05 Aug 2006
Posts: 884
Location: Italia - Firenze
|
| Posted: Wed Apr 11, 2007 11:00 am Post subject: |
|
|
| Infatti, non credo che udev tiri su il detto modulo perchè non riguarda una periferica in particolare e il suo funzionamento in senso stretto, ma un funzionamento più "di alto livello", direi (sbaglio?). Ergo, o lo carichi a mano o lo integri nel Kernel. Dipende che uso ne devi fare, se tutte le volte che accendi il pc ne hai bisogno, non vedo perchè no!! |
|
| Back to top |
|
|
|
Forum italiano (Italian)
