Bug 188385

Summary:	sys-kernel/genkernel-3.4.8 doesn't load rfcomm module
Product:	Gentoo Hosted Projects	Reporter:	Andrew Evans <gentoo>
Component:	genkernel	Assignee:	Gentoo Genkernel Maintainers <genkernel>
Status:	RESOLVED INVALID
Severity:	normal
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Andrew Evans 2007-08-10 18:15:01 UTC

With genkernel-3.4.8 and gentoo-sources-2.6.21-gentoo-r4, the Bluetooth rfcomm kernel module isn't loaded at startup. This causes `/etc/init.d/bluetooth start` to fail on starting rfcomm because the RFCOMM protocol isn't loaded in the kernel. This wasn't a problem before with genkernel-3.4.6 and gentoo-sources-2.6.20-gentoo-r8.

It seems to me the proper fix is to add rfcomm to MODULES_USB in /usr/share/genkernel/$ARCH/modules_load.

Comment 1 Andrew Gaffney (RETIRED) gentoo-dev

2007-08-10 18:21:30 UTC

This isn't genkernel's job. Genkernel's linux loads modules that are required to get your system booted (such as SCSI/IDE/SATA drivers).

If you want a module that is *not* required for boot loaded at startup, stick it in /etc/modules.autoload.d/kernel-2.x.

Comment 2 Andrew Evans 2007-08-10 19:47:19 UTC

My mistake. I thought genkernel used to load Bluetooth modules at startup, but I downgraded to genkernel-3.4.6 and didn't see any Bluetooth stuff in /usr/share/genkernel.

IMHO, putting stuff in /etc/modules.autoload.d is rather barbaric. The system should be smart enough to load the modules it needs automatically. /etc/init.d/bluetooth should probably do this. I'll file a bug for that.