Bug#765426: umount; floppy light and humming still present after "umount" and even after "shutdown"
On Mon, Nov 24, 2014 at 06:41:39PM +0000, Bjarni Ingi Gislason wrote:
> On Sat, Oct 25, 2014 at 03:30:01PM +0100, Ben Hutchings wrote:
> > On Fri, 2014-10-17 at 00:02 +0000, Bjarni Ingi Gislason wrote:
> > > On Wed, Oct 15, 2014 at 12:06:06AM +0000, Debian Bug Tracking System wrote:
> > > > Thank you for filing a new Bug report with Debian.
> > > >
> > > [...]
> > > >
> > > > --
> > > > 765426: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765426
> > > > Debian Bug Tracking System
> > > > Contact owner@bugs.debian.org with problems
> > >
> > > This bug report belongs most probably to the 'udev' package.
> > >
> > > Changing the group of '/dev/fd0' from 'disk' to 'floppy' causes 'eject'
> > > to shut off the floppy drive light after a few seconds, although some
> > > messages are shown.
> >
> > I believe that a floppy drive activity light is normally connected to
> > the spindle motor, i.e. it indicates whether the disk is spinning. It
> > is supposed to be turned off automatically by the driver when the drive
> > is idle, and cannot be directly controlled by userland, so this doesn't
> > make any sense to me.
> >
>
> "eject /dev/fd0" or "floppycontrol --eject /dev/fd0" is now necessary
> to stop the disk spinning and then the floppy can be ejected
> mechanically as it is not software-controlled.
>
> > > The bug is therefore caused by creating the device with the wrong
> > > group.
> > [...]
> >
> > I think that's a separate bug that exacerbates an underlying driver bug.
> >
>
> This report should be reassigned to package "udev" or if a subject
> change is necessary be closed(?). I will then issue a new report to
> "udev".
>
> The bug (regression) can be fixed in the file
> "/lib/udev/rules.d/50-udev-default.rules.
>
> The (block) devices "/dev/fd[0-9]" shall be (as before) in the group
> "floppy" as a write-permission is necessary to spin the drive down.
>
I reported the bug to the "udev"-package (#775 144). The behaviou
was decleared "as designed" and the bug report closed.
I added the missing line to
/etc/udev/rules.d/91-permissions.local.rules
to keep it permanent, and that should fix this bug permanently.
--
Bjarni I. Gislason
Reply to: