kernel's PHP^Wpnp subsystem is broken

Upgraded to linux-image-2.6.15-16-386 (2.6.15-16.23) from a clean dapper flight 4 install. There is no /dev/fd0.

With the original kernel there is a /dev/fd0 and /sys/block/fd0/ entries. The floppy works (I have to mount it manually, because my test floppy needs "-t msdos", and does not work with "auto".)

With linux-image-2.6.15-16-386, I have to do "sudo modprobe floppy". Then the floppy works ok. Except for some other floppy bugs like bug #28783. And I have a "Floppy Drive" and a "Floppy 1" in my Nautilus "Computer" view.

seems like kernel upgrade 2.6.15-16-386 broke something.

I had to create /dev/fd0 manually using 'mknod' -command.
(tried MAKEDEV script too, but it didn't work)

uh, I just had to modprobe floppy.
Has floppy been on /etc/modules before?

Rejecting the task in util-linux, that's either an udev or kernel fault.

Scott, is the module 'floppy' supposed to be loaded automatically? Is that really a kernel bug, or something udevish?

(I do not have any floppy any more, I can't try)

Me neither.

It doesn't declare any aliases ... that in itsself could be considered a "kernel bug" I guess - but then I don't think floppy drives show up under any bus I'm aware of

It's probably a good example of "load it if you have one", with no way of finding out whether you have one except by loading the module.

It's not a udev bug anyway; nothing for udev to get involved with here. Either we stick "floppy" in /etc/modules, or we build it in.

I'm almost wondering why it's a module at all.. Ben?

I don't want to build it into the kernel, because then there's no real way to disable it on buggy hardware.

Let's just stick it in /etc/modules

Colin, can you add floppy to whatever writes /etc/modules for the appropriate platforms

hw-detect already adds floppy to /etc/modules for everything other than NewWorld PowerMacs, and has done so since Warty.

Is this happening on a live CD or something like that?

Are you sure?

floppy isn't in /etc/modules on my fresh Dapper install.

My bad; I misread the code. It was loading floppy during installation but wasn't registering it for addition to /etc/modules.

hw-detect (1.32ubuntu4) dapper; urgency=low

  * Add floppy to /etc/modules (closes: Malone #32599).

 -- Colin Watson <email address hidden> Tue, 28 Feb 2006 11:03:44 +0000

This won't take effect until the next rebuild of debian-installer.

I've reverted this hw-detect change in version 1.32ubuntu5; Scott says the kernel's PnP subsystem is in fact broken and that's where the fix should go.

Aye.

Ben, ls /sys/bus/pnp/devices ... there's supposed to be a dozen things in there, not nothing :)

Hi, what's the current status of this bug?
on flight5 floppy must be still modprobed separately.

Is this related?

[4294671.598000] pnp: PnP ACPI init
[4294671.598000] pnp: PnPACPI: unknown resource type 7
[4294671.598000] pnp: PnPACPI: METHOD_NAME__CRS failure for PNP0c01
[4294671.598000] pnp: PnPACPI: unknown resource type 7
[4294671.598000] pnp: PnPACPI: METHOD_NAME__CRS failure for PNP0c02
[4294671.598000] pnp: PnPACPI: unknown resource type 7
[4294671.598000] pnp: PnPACPI: METHOD_NAME__CRS failure for PNP0200
[4294671.598000] pnp: PnPACPI: unknown resource type 7
[4294671.598000] pnp: PnPACPI: METHOD_NAME__CRS failure for PNP0b00
[4294671.598000] pnp: PnPACPI: unknown resource type 7
[4294671.598000] pnp: PnPACPI: METHOD_NAME__CRS failure for PNP0800
[4294671.598000] pnp: PnPACPI: unknown resource type 7
[4294671.598000] pnp: PnPACPI: METHOD_NAME__CRS failure for PNP0c04
[4294671.598000] pnp: PnPACPI: unknown resource type 7
[4294671.598000] pnp: PnPACPI: METHOD_NAME__CRS failure for PNP0700
[4294671.599000] pnp: PnPACPI: unknown resource type 7
[4294671.599000] pnp: PnPACPI: METHOD_NAME__CRS failure for PNP0501
[4294671.600000] pnp: PnPACPI: unknown resource type 7
[4294671.600000] pnp: PnPACPI: METHOD_NAME__CRS failure for PNP0401
[4294671.600000] pnp: PnPACPI: unknown resource type 7
[4294671.600000] pnp: PnPACPI: METHOD_NAME__CRS failure for PNP0303
[4294671.600000] pnp: PnP ACPI: found 0 devices
[4294671.600000] PnPBIOS: Disabled by ACPI PNP

The "floppy" module still has to be loaded manually in Flight-6. A msdos floppy is also not recognised, because the "msdos" module is not loaded.

After recent updates, notably kernel 2.6.15-20, the "floppy" module is automatically loaded. However "msdos" is not.

msdos will be automatically loaded should you try and mount a filesystem of that type

chances are that "vfat" will be loaded instead, of course

Yes, if I manually do mount -t msdos /dev/fd0 /mnt it works. My point is that double clicking on the floppy icon in gnome won't work, neither would using mount without specifying fs (autodetection). After loading the module, autodetection works.

$ sudo mount /dev/fd0 /mnt
mount: you must specify the filesystem type
$ sudo modprobe msdos
$ sudo mount /dev/fd0 /mnt
$

This is a known bug, and there are ways to fix it; HAL has recently gained support for knowing the type of a filesystem before it's mounted so the right arguments can be passed to mount.

PNP stuff should be working again, for the kernel at least.

Just want to confirm that the msdos floppies now are recognized automatically. (dapper beta 2)

The msdos floppies are not recognised any longer, it's like in comment #20. Must be a regression from beta-2. Obviously, I don't use floppies that often :)