Messages in this thread |  | | Date | Wed, 11 Sep 2002 10:25:56 +0200 (MET DST) | From | Mikael Pettersson <> | Subject | Re: 2.5.34-bk floppy weirdness |
| |
On Tue, 10 Sep 2002 20:38:47 -0500 (CDT), Thomas Molina wrote: >The following appeared with the latest bk updated kernel. It was not >present with the 2.5.33 version, nor with a 2.4 kernel version. > >I cannot dd to the floppy until either it has been mounted, or until the >superuser has dd'd to the floppy. The following is from a fresh boot: > >[tmolina@dad testfloppystable]$ ls >floppy floppyimage >[tmolina@dad testfloppystable]$ ls -l /dev/fd0 >brw-rw---- 1 tmolina floppy 2, 0 Apr 11 09:25 /dev/fd0 >[tmolina@dad testfloppystable]$ ls -l >total 1448 >drwxr-xr-x 2 tmolina tmolina 4096 Dec 31 1969 floppy >-rw-rw-r-- 1 tmolina tmolina 1474560 Sep 1 09:49 floppyimage >[tmolina@dad testfloppystable]$ dd if=floppyimage of=/dev/fd0 >dd: opening `/dev/fd0': No such device or address >[tmolina@dad testfloppystable]$ su >Password: >[root@dad testfloppystable]# dd if=floppyimage of=/dev/fd0 >2880+0 records in >2880+0 records out
My 2.5.34 (proper, not bk) doesn't have this misbehaviour.
Are you building the floppy driver as a module and relying on kmod+modutils to insert it on demand? If so, you may be seeing the same problem I was when I upgraded my user-space to RedHat 7.3: dd of=/dev/fd0 as a user won't load floppy.o. See RedHat bug id 65685 for details.
/Mikael - 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/
|  |