[lkml]   [2002]   [Sep]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 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
>[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.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:28    [W:0.053 / U:0.364 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site