Red Hat Bugzilla – Bug 138582
cyclades module does not autoload after compilation
Last modified: 2014-03-16 22:50:09 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7)
Description of problem:
I have installed the kernel src package and recompiled the kernel with
the addition of the cyclades multi-port serial card module. After
installing the kernel and rebooting with the new kernel, the cyclades
card isn't automatically detected and no device nodes are present in
/dev. If I modprobe the module manually ("modprobe cyclades"), the
module loads successfully and the device nodes appear (/dev/ttyC0,
ttyC1 etc). Kudzu is silent about the device's presence (removing it
or adding it doesn't prompt a hardware change dialog on bootup).
I have used the lines supplied in modprobe.conf.dist relating to the
cyclades device and added them to modprobe.conf as follows:
alias char-major-19-* cyclades
alias char-major-20-* cyclades
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install kernel source
2. Recompile kernel with selecting the cyclades module under Device
Drivers/Character Devices (I did a menuconfig on mine)
3. make modules ; make modules_install ; make install ; reboot
4. Select new kernel from grub menu (was 2.6.9-prep on my system)
5. boot system.
lsmod doesn't show the cyclades card in the system. No device nodes
appear in /dev.
Module should have loaded automatically (I would have expected kudzu
to pick up the device, too).
Would have liked the module to be included like our redhat machines.
This was filed as a bug report in June against FC2 at
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=125884 by another
This is a fresh install of FC3. This problem was also present in
FC3-test3 but not present in FC1.
How does one determine the presence of the cyclades card?
ALrighty. Had more of a play. Kudzu DOES seem to pick up the
cyclades just fine, but that's about it. modprobing manually works.
Can you attach your hwconf file?
Created attachment 106388 [details]
hwconf from machine in question
Interestingly enough, the same problem (chicken/egg) with the lucent winmodem
in this machine has also surfaced. Only solution is to load the module
manually, just like the cyclades.. is udev getting in the way perhaps?
Without the cyclades driver claiming the PCI id of the modem, there's
no way for it to autoload.