I get the following error when booting up, and also when upgrading from
Can't open RFCOMM control socket: No such file or directory
It's coming from this part of the init script:
if [ -x /usr/bin/rfcomm -a -f /etc/bluetooth/rfcomm.conf ]; then
/usr/bin/rfcomm -f /etc/bluetooth/rfcomm.conf bind all
That appears to require a socket which isn't present on my system (probably b/c
I don't have bluetooth hardware)
I also see the following in dmesg once this error occurs:
request_module[bt-proto-3]: fork failed, errno 1
Well for cosmetic reasons I suppose the rfcomm tool could refrain from actually
opening its socket unless it needs to, but the modprobe shouldn't fail and there
shouldn't be any errors.
Bug #88859 seems to have recurred, but that isn't the problem in this case. It
looks like the kernel isn't even managing to run modprobe. Does it manage to
autoload any other modules?
Reassigning to kernel.
It autoloads other modules just fine....
I don't see this any more with kernel-2.4.22-1.2040.nptl from RHN