As soon as there exists an entry for the floppy drive in fstab, the mount command does not work anymore. To easy access the floppy drive from KDE, there has to be an entry in fstab. This happens on opensuse 12.1.
On 2012-02-18 22:56, amadrits wrote:
>
> As soon as there exists an entry for the floppy drive in fstab, the
> mount command does not work anymore. To easy access the floppy drive
> from KDE, there has to be an entry in fstab. This happens on opensuse
> 12.1.
Too little info. Please give examples. And the line you put in fstab.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
of coerce the floppy drive is NOT detected
they stopped making them( the drives) a few years back
Sony last year finally shut down the production line that made the 3.5 floppies
The Linux kernel no longer even LOOKS for a 3.5 floppy seeing as you can NOT buy a new computer WITH one installed
you ** MUST** run
su -
modprobe floppy
first
THEN if it is in the fstab it will be mounted
I know this works for the 2.6 kernel on RHEL6
but i have no idea if the 3.2 linux kernel still supports it
On 2012-02-19 02:36, JohnVV wrote:
> but i have no idea if the 3.2 linux kernel still supports it
The one in 12.1 does.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
The floppy module is loaded by default:
pcam1:/ # lsmod|grep floppy
floppy 64406 0
pcam1:/ #
If there is no entry for the floppy in fstab, mounting works:
pcam1:/ # mount -v /dev/fd0 /mnt
mount: you didn’t specify a filesystem type for /dev/fd0
I will try type vfat
/dev/fd0 on /mnt type vfat (rw)
pcam1:/ #
pcam1:/ # ls /mnt
testfile
pcam1:/ #
With the following entry in fstab mounting does not work anymore:
/dev/fd0 /mnt auto rw,noauto,user,sync 0 0
There is no error message, but ls does not show the content of the floppy disk.
pcam1:/ # ls /mnt
pcam1:/ #
And umount complains that there is no floppy disk mounted:
pcam1:/ # umount /dev/fd0
umount: /dev/fd0: not mounted
pcam1:/ #
I vaguely remember some broken behavior with some kernel versions where
automatic detection of the floppy format failed and you have to specify
the format in the fstab like /dev/fd0u1440 (if that is your format).
–
PC: oS 11.4 (dual boot 12.1) 64 bit | Intel Core i7-2600@3.40GHz | KDE
4.6.0 | GeForce GT 420 | 16GB Ram
Eee PC 1201n: oS 11.4 64 bit | Intel Atom 330@1.60GHz | KDE 4.8.0 |
nVidia ION | 3GB Ram
replace “auto” by “vfat” and the options by “defaults”. See what happens.
On 2012-02-19 13:26, amadrits wrote:
> With the following entry in fstab mounting does not work anymore:
>
> /dev/fd0 /mnt auto rw,noauto,user,sync 0 0
>
> There is no error message, but ls does not show the content of the
> floppy disk.
But I don’t see you trying to mount. From the command line, of course, same
as you did before: “mount /mnt”. Do so and paste the command and the output
- but using code tags, do not insert the code in the middle of the message.
Also of interest is the last few lines in the /var/log/messages file.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Here is the output when I try to mount the floppy disk with its entry in fstab:
pcam1:/ # mount -v /mnt
mount: you didn't specify a filesystem type for /dev/fd0
I will try type vfat
/dev/fd0 on /mnt type vfat (rw,noexec,nosuid,nodev,sync)
pcam1:/ # ls /mnt
pcam1:/ #
And here the last view lines in /var/log/messages:
Feb 19 19:06:41 pcam1 dbus-daemon[1094]: **** /proc/self/mountinfo changed
Feb 19 19:06:41 pcam1 dbus-daemon[1094]: **** MOUNTED /sys/devices/platform/floppy.0/block/fd0
Feb 19 19:06:41 pcam1 dbus-daemon[1094]: **** CHANGING /sys/devices/platform/floppy.0/block/fd0
Feb 19 19:06:41 pcam1 dbus-daemon[1094]: **** UPDATING /sys/devices/platform/floppy.0/block/fd0
Feb 19 19:06:41 pcam1 dbus-daemon[1094]: **** EMITTING CHANGED for /sys/devices/platform/floppy.0/block/fd0
Feb 19 19:06:41 pcam1 dbus-daemon[1094]: **** NOTE: Force unmounting device /dev/fd0
Feb 19 19:06:41 pcam1 dbus-daemon[1094]: **** EMITTING JOB-CHANGED for /sys/devices/platform/floppy.0/block/fd0
Feb 19 19:06:41 pcam1 dbus-daemon[1094]: helper(pid 7043): launched job umount on /dev/fd0
Feb 19 19:06:41 pcam1 dbus-daemon[1094]: **** CHANGED /sys/devices/platform/floppy.0/block/fd0
Feb 19 19:06:41 pcam1 dbus-daemon[1094]: **** /proc/self/mountinfo changed
Feb 19 19:06:41 pcam1 dbus-daemon[1094]: **** UNMOUNTED /sys/devices/platform/floppy.0/block/fd0
Feb 19 19:06:41 pcam1 dbus-daemon[1094]: **** CHANGING /sys/devices/platform/floppy.0/block/fd0
Feb 19 19:06:41 pcam1 dbus-daemon[1094]: **** UPDATING /sys/devices/platform/floppy.0/block/fd0
Feb 19 19:06:41 pcam1 dbus-daemon[1094]: **** EMITTING CHANGED for /sys/devices/platform/floppy.0/block/fd0
Feb 19 19:06:41 pcam1 dbus-daemon[1094]: **** CHANGED /sys/devices/platform/floppy.0/block/fd0
Feb 19 19:06:41 pcam1 dbus-daemon[1094]: helper(pid 7043): completed with exit code 0
Feb 19 19:06:41 pcam1 dbus-daemon[1094]: **** NOTE: Successfully force unmounted device /dev/fd0
Feb 19 19:06:41 pcam1 dbus-daemon[1094]: **** UPDATING /sys/devices/platform/floppy.0/block/fd0
Feb 19 19:06:41 pcam1 dbus-daemon[1094]: **** EMITTING JOB-CHANGED for /sys/devices/platform/floppy.0/block/fd0
On 2012-02-19 19:16, amadrits wrote:
>
> Here is the output when I try to mount the floppy disk with its entry in
> fstab:
>
>
> Code:
> --------------------
>
> pcam1:/ # mount -v /mnt
> mount: you didn’t specify a filesystem type for /dev/fd0
> I will try type vfat
> /dev/fd0 on /mnt type vfat (rw,noexec,nosuid,nodev,sync)
> pcam1:/ # ls /mnt
> pcam1:/ #
Apparently, the mount succeeded.
> And here the last view lines in /var/log/messages:
Not related, I think.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Here is the output when I try to mount the floppy disk without its entry in fstab and with the same floppy disk:
pcam1:/ # mount -v /dev/fd0 /mnt
mount: you didn't specify a filesystem type for /dev/fd0
I will try type vfat
/dev/fd0 on /mnt type vfat (rw)
pcam1:/ # ls /mnt
testfile
pcam1:/ #
And the last view lines in /var/log/messages:
Feb 20 03:48:40 pcam1 dbus-daemon[949]: **** /proc/self/mountinfo changed
Feb 20 03:48:40 pcam1 dbus-daemon[949]: **** MOUNTED /sys/devices/platform/floppy.0/block/fd0
Feb 20 03:48:40 pcam1 dbus-daemon[949]: **** CHANGING /sys/devices/platform/floppy.0/block/fd0
Feb 20 03:48:40 pcam1 dbus-daemon[949]: **** UPDATING /sys/devices/platform/floppy.0/block/fd0
Feb 20 03:48:40 pcam1 dbus-daemon[949]: **** EMITTING CHANGED for /sys/devices/platform/floppy.0/block/fd0
Feb 20 03:48:40 pcam1 dbus-daemon[949]: **** CHANGED /sys/devices/platform/floppy.0/block/fd0
That works as it should, but I use the fstab entry for easy accas to the floppy disk in KDE.
On 2012-02-20 04:06, amadrits wrote:
> That works as it should, but I use the fstab entry for easy accas in
> KDE.
Notice that if the device has an entry in fstab, the convention is that the
desktop should then not try to mount it, hands off. An fstab entry signals
that you intend to mount manually, not automatically.
From the code excerpts you posted it appears your floppy drive is mounting
perfectly, but kde does not mount it. With a line in fstab kde should not
even attempt to mount it, and if without the line kde does nothing, then it
is a bug in kde, or an expected feature because they think floppies obsolete.
As far as I remember, it is not simple to detect if there is a disk inside
and then mount it automatically.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Carlos E. R. wrote:
> Notice that if the device has an entry in fstab, the convention is that the
> desktop should then not try to mount it, hands off. An fstab entry signals
> that you intend to mount manually, not automatically.
Surely it is the noauto option in an fstab entry that decides that a
system should not try to mount a device? Otherwise, no disks at all
would be mounted.
On 2012-02-20 13:38, Dave Howorth wrote:
> Carlos E. R. wrote:
>> Notice that if the device has an entry in fstab, the convention is that the
>> desktop should then not try to mount it, hands off. An fstab entry signals
>> that you intend to mount manually, not automatically.
>
> Surely it is the noauto option in an fstab entry that decides that a
> system should not try to mount a device? Otherwise, no disks at all
> would be mounted.
No, no. Entry in fstab ==> desktop will not mount it automatically.
It may go a step further and offer to mount it on request, according to the
entry, but this is not guaranteed.
I know because I reported several bugs in gnome in this area, till it
worked right.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Carlos E. R. wrote:
> On 2012-02-20 13:38, Dave Howorth wrote:
>> Carlos E. R. wrote:
>>> Notice that if the device has an entry in fstab, the convention is that the
>>> desktop should then not try to mount it, hands off. An fstab entry signals
>>> that you intend to mount manually, not automatically.
>> Surely it is the noauto option in an fstab entry that decides that a
>> system should not try to mount a device? Otherwise, no disks at all
>> would be mounted.
>
> No, no. Entry in fstab ==> desktop will not mount it automatically.
Entry in fstab and the system mounts the disk on boot. Unless there is a
noauto option.
On 2012-02-20 15:23, Dave Howorth wrote:
> Carlos E. R. wrote:
>> No, no. Entry in fstab ==> desktop will not mount it automatically.
>
> Entry in fstab and the system mounts the disk on boot. Unless there is a
> noauto option.
Or the device is not present at boot, like an external disk. You plug it
in, but it is listed in fstab, then the desktop doesn’t mount it.
Try it.
At least in gnome it works, I have reported when it did not.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
I intend to mount the floppy disk with kfloppy.
In opensuse 11.3 mounting a floppy disk worked even if there was an entry in fstab.