Bug 7023

Summary:	Device Notifier now always shows my Floppy drive as available but it can't be mounted.
Product:	Mageia	Reporter:	Steve <kin7500-fm>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	?	CVE:
Status comment:

Description Steve 2012-08-11 22:23:21 CEST

Description of problem:
After some recent (since July 28th) updates to my Cauldron/KDE desktop, the Device Notifier now always shows my Floppy drive available as Removable Media, (previously it never showed it) but it cannot be mounted and dmesg shows these two errors each time I try:

[ 2153.673025] end_request: I/O error, dev fd0, sector 0
[ 2153.697025] end_request: I/O error, dev fd0, sector 0

I do have a /dev/fd0 mount line in my fstab but removing this has no effect on the Device Notifier.

I believe the issue of not being able to mount the Floppy drive could be related to this bug report:
https://bugs.mageia.org/show_bug.cgi?id=4642

I found a Fedora reference to the dmesg errors here:
http://fedoraproject.org/wiki/Common_kernel_problems

and the suggestion was to add floppy.allowed_drive_mask=0 to the kernel boot options. This does stop the Device Notifier from showing the Floppy drive but I don't see this as a solution. If the Floppy drive is truly not available the Device Notifier should not show it. It should not be necessary to add kernel boot options manually.

Comment 1 Steve 2012-09-03 15:32:03 CEST

After updating 323 packages today the problem has gone away.

I will change this bug report to RESOLVED and FIXED.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 2 Steve 2012-12-13 20:03:30 CET

This issue has returned at some point earlier this week after regularly updating my PC.
I plan to do a new install when Beta1 is released so I will see what the situation is after the new installation and if necessary re-open this bug.

Comment 3 Steve 2012-12-21 11:10:46 CET

I have completed a clean install of M3B1 on a new partition and this issue is not present. I will now regularly update this install and see if the issue returns.