Thank you.

The first reference shows:

Product: 	Fedora
Component(s): 	kernel (Show other bugs)
Version(s): 	14
Platform: 	x86_64 Linux

I could not find a similar item in the second reference.

If I correctly understand the first reference, the issue is restricted 
to X86-64, and thus must be an issue either with the way the 64 bit 
kernel handles the 64 bit instruction set architecture extensions to the 
32 bit architecture, the 64 bit compiler, or a specification error in 
the driver when used in 64 bit mode (e.g., a long unsigned int that must 
be 32 bits but is mapped to a 64 bit value in error in the device driver 
source code or the linkage between the driver and the rest of the kernel).

Does anyone know the correct syntax and file entry to make the kernel 
automatically load the driver during boot?

Thanks,

Yasha Karant

On 06/19/2011 11:25 AM, Garrett Holmstrom wrote:
> On 2011-06-19 10:27, Yasha Karant wrote:
>> I fully understand that the /dev entries are created at boot time if the
>> driver actually is present (generally, in kernel space, but there are
>> exceptions where a driver crosses between kernel and user space). As it
>> is clear that the driver is present, why is the driver not autoloaded
>> during boot if the hardware is present?
>
> The kernel team chose to stop loading the floppy driver automatically
> due to problems with certain floppy disk controllers. [0] [1]
>
>> In which file(s) in SL6 does one make the modification to force the
>> existence of /dev/fd0 at each boot? As far as I can tell, SL6 is loading
>> drivers for all of the other physical hardware on the unit.
>
> You should be able to create a file in /etc/modprobe.d that makes the
> floppy driver load automatically when a floppy drive is around, though I
> have no idea what the syntax for that is.
>
> [0] https://bugzilla.redhat.com/show_bug.cgi?id=599127
> [1]
> http://pkgs.fedoraproject.org/gitweb/?p=kernel.git;a=blob;f=die-floppy-die.patch
>
>