Alessandro Suardi wrote:
> 
> Trying to modprobe it yields
> 
> [root@dolphin root]# modprobe floppy
> /lib/modules/2.5.3/kernel/drivers/block/floppy.o: init_module: Device or resource busy
> Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
> /lib/modules/2.5.3/kernel/drivers/block/floppy.o: insmod /lib/modules/2.5.3/kernel/drivers/block/floppy.o failed
> /lib/modules/2.5.3/kernel/drivers/block/floppy.o: insmod floppy failed
> 
>  and dmesg says
> 
> inserting floppy driver for 2.5.3
> Floppy drive(s): fd0 is 1.44M
> floppy0: Floppy io-port 0x03f0 in use
> 

A simple but nice hint by Pierre Rousselet suggested the I/O port
 is in use - I plain assumed it broke because I have been loading
 modular floppy for the last 36 months or so without specifying
 any parameters...

It turns out this is due to the new PnPBIOS kernel config option:

[asuardi@dolphin asuardi]$ grep PnPBIOS /proc/ioports 
03f0-03f1 : PnPBIOS PNP0c01
0600-067f : PnPBIOS PNP0c01
0680-06ff : PnPBIOS PNP0c01
  0800-083f : PnPBIOS PNP0c01
  0840-084f : PnPBIOS PNP0c01
0880-088f : PnPBIOS PNP0c01
f400-f4fe : PnPBIOS PNP0c01

But since modular floppy was working before without setting any
 ioport parameter I'm not entirely sure this is a "feature".


Thanks,

--alessandro

 "this machine will, will not communicate
   these thoughts and the strain I am under
  be a world child, form a circle before we all go under"
                         (Radiohead, "Street Spirit [fade out]")
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/