#492592 bluez-utils: load bluetooth kernel module on before starting hcid

Package:
src:bluez
Source:
bluez
Submitter:
Hendrik Sattler
Date:
2024-07-11 11:57:03 UTC
Severity:
important
#492592#5
Date:
2008-07-27 14:56:12 UTC
From:
To:
Hi,

hcid (and probably other bluetooth stuff) will not startup if bluetooth is only available
as kernel module. Thus, not loading it makes those pieces of software unusable.
Thus, the init script should make a call to "modprobe bluetooth" if e.g. /sys/class/bluetooth
does not exist (or whatever else is a clear indication that bluetooth is only available as
module and not built-in).

The effect of this bug is that hot-plugged devices are not up and thus not working until
"/etc/init.d/bluetooth restart" is called.

HS
#492592#10
Date:
2008-07-27 15:23:53 UTC
From:
To:
Hi,

in addition to the bluetooth kernel module, the rfcomm kernel module must also
be loaded or else the built-in SDP server will silently fail to work. And
bluetooth without SDP can be seen as non-functional.

HS
#492592#15
Date:
2008-07-27 18:02:31 UTC
From:
To:
filippo
--
Filippo Giunchedi - http://esaurito.net
PGP key: 0x6B79D401
random quote follows:

Gretchen: You're weird.
Donnie: Sorry.
Gretchen: No, that was a compliment.
-- from Donnie Darko (2001)
#492592#20
Date:
2008-07-27 18:21:03 UTC
From:
To:
Am Sonntag, 27. Juli 2008 20:02:31 schrieb Filippo Giunchedi:

udev is only used if CONFIG_KMOD is enabled for the current kernel. In that
case, starting hcid will load rfcomm, l2cap and bluetooth.

/etc/modules should just be used for cases that have no better solution.

An init script should at least try to meet the prerequisites for the program
that it is about to start and in no case silently fail.

HS
#492592#31
Date:
2024-07-11 11:52:38 UTC
From:
To:
auq dl