At 03:05:20 on Monday Monday 01 June 2009, "Carlos E. R." <robin.listas@telefonica.net> wrote:
On Monday, 2009-06-01 at 00:01 +0300, Stan Goodman wrote:
Ok, then try to umount, then mount - manually.
stan@poblano:~> umount /media/floppy stan@poblano:~> ls /media/floppy stan@poblano:~> mount /media/floppy mount: /dev/fd0 is not a valid block device stan@poblano:~> mount /media/floppy
Above, is the umount, which was effective, since ls returned nothing. It is unexpected (at least to me) that the mount command then gets the error message.
And that's the real error: your system thinks it does not have a floppy.
You could look at the end of the /var/log/messages file right after the mount command, to see if the kernel says anything. Also, eject and put the floppy and look up the log again. Another place is to look in /var/log/boot.msg anything relative to the floppy.
-- Cheers, Carlos E. R.
I now see what it is that has to be done in order to get the floppy drive to be properly mounted; the WHY of it is still beyond me. Here is the sequence of actions: Before the diskette is inserted into the floppy drive, the Drive information list shows the floppy icon, but with no details. Inserting the diskette into the drive changes nothing, although <fstab> contains the line: /dev/fd0 /media/floppy auto noauto,user,sync 0 0 so apparently the drive is not mounted. I then did <mount /media/floppy>. This returns an error message saying that the apparently unmounted drive is already mounted. I did <umount/media/floppy>, to remove the evidently improperly mounted drive, followed by <mount/media/floppy. At no point have I removed the diskette from the drive. Now the Drive information list shows details of the floppy drive, and clicking on the floppy icon shows the files contained in the drive. The only conclusion that I can reach is that there is something wrong with the automatic mounting of the drive, per the above-quoted line in <fstab>. But to me, that line looks like what it should be. Viewing <var/log/messages> shows only the following lines relative to the sequence above: Jun 2 12:02:24 poblano su: (to root) stan on /dev/pts/3 Jun 2 12:10:24 poblano kernel: [drm:i915_getparam] *ERROR* Unknown parameter 5 Jun 2 12:12:33 poblano su: (to root) stan on /dev/pts/4 The two lines about /dev/pts are only about the console I was using, and so are irrelevant, as far as I understand. I have no clue what "parameter 5" has been found, nor how it got to wherever it is. It seems that this is the root of the problem of why the drive IS mounted, but isn't MOUNTED. Help! -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org