SliTaz Forum
You are not logged in.
Pages: 1
Thanks to the help of gibor, on the Toshiba Satellite Pro 4600, we found a bug, at least we think about reading the floppy disk.
initially after installing the operating system, I was not able to read any floppy.
After reinstalling the Slitaz operating system several times, the suspicion that came to mind gibor is of an error in the udev or udisks manager.
From the Terminal a mount point was created
mkdir /media/floppy
mount -t vfat /dev/fd0 /media/floppy
ls /media/floppy/*
The files contained in the floppy were displayed, and with pcmanfm, navigating to that folder, I could see all the contents of the floppy without problems.
After that I unmounted the floppy
umount /media/floppy
extracted the floppy
removed the mount point with
rm -r /media/floppy.
Now I can read the contents of every inserted floppy, however before reading the contents of the floppy an annoying message always appears first: An operatioin is already pending. Pressing enter the message disappears and the contents of the floppy appear.
Is there a way to solve this?
Offline
Hello NarakuITA,
I cannot reproduce the problem you described on my old computer.
Is the [c]gvfs-udisks2[/c] installed?
[c]tazpkg info gvfs-udisks2[/c]
If the package is mirrored then install it and try again.
Concerning the message An operation is already pending I reproduce it if I double-click on the floppy in the left panel in PCManFM; but no problem with a single clic.
Offline
The package is installed. If I insert the floppy with one click it does not read the content. I have to do two Clicks. The error message appears, I press OK, and then it reads the content.
From now on I can read the content without errors with one click.
Offline
Hello,
I don't know if this can bring interesting information but please
boot your SliTaz
open the Sakura terminal and type
[c]tail -f /var/log/messages[/c] (this will print the last 10 lines of the file on the screen and then all new lines; no need to be root)
hit [Enter] a few times to create a space between the existing messages and the new ones
insert a floppy disk and wait for new messages
hit [Enter] a few times again
open PCManFM and click on Floppy Disk in the left panel of the file manager; wait a few seconds for new messages
hit [Enter] a few times again
eject the floppy disk and wait for messages
copy and post the three groups of messages.
Offline
Hi Ceel, I repost the messages you were asking because I also experience problems with floppies.
It comes in two steps: I insert the floppy - from pcmanfm I click on floppy - the floppy spins for a few seconds and pcmanfm shows an empty folder
I click on eject from pcmanfm - I click on floppy again - the floppy spins a little and this time the folder with the contents appears.
/var/log/messages
Jul 17 00:09:18 (none) daemon.info : process '/sbin/getty 115200,38400,9600,4800,2400 ttyS0' (pid 2254) exited. Scheduling for restart.
Jul 17 00:09:18 (none) daemon.info : starting pid 2255, tty '/dev/ttyS0': '/sbin/getty 115200,38400,9600,4800,2400 ttyS0'
Jul 17 00:09:19 (none) daemon.info : process '/sbin/getty 115200,38400,9600,4800,2400 ttyS0' (pid 2255) exited. Scheduling for restart.
Jul 17 00:09:19 (none) daemon.info : starting pid 2256, tty '/dev/ttyS0': '/sbin/getty 115200,38400,9600,4800,2400 ttyS0'
/var/log/dmesg
FAT-fs (fd0): Directory bread(block 19) failed
FAT-fs (fd0): Directory bread(block 20) failed
FAT-fs (fd0): Directory bread(block 21) failed
FAT-fs (fd0): Directory bread(block 22) failed
FAT-fs (fd0): Directory bread(block 23) failed
FAT-fs (fd0): Directory bread(block 24) failed
FAT-fs (fd0): Directory bread(block 25) failed
FAT-fs (fd0): Directory bread(block 26) failed
FAT-fs (fd0): Directory bread(block 27) failed
FAT-fs (fd0): Directory bread(block 28) failed
FAT-fs (fd0): FAT read failed (blocknr 8)
FAT-fs (fd0): FAT read failed (blocknr 8)
FAT-fs (fd0): FAT read failed (blocknr 8)
FAT-fs (fd0): FAT read failed (blocknr 8)
On the second mount where the content appears in pcmanfm dmesg remains unchanged (no errors) and messages continues as above
messages
Jul 17 00:09:22 (none) daemon.info : starting pid 2259, tty '/dev/ttyS0': '/sbin/getty 115200,38400,9600,4800,2400 ttyS0'
Jul 17 00:09:23 (none) daemon.info : process '/sbin/getty 115200,38400,9600,4800,2400 ttyS0' (pid 2259) exited. Scheduling for restart.
Jul 17 00:09:23 (none) daemon.info : starting pid 2261, tty '/dev/ttyS0': '/sbin/getty 115200,38400,9600,4800,2400 ttyS0'
Jul 17 00:09:24 (none) daemon.info : process '/sbin/getty 115200,38400,9600,4800,2400 ttyS0' (pid 2261) exited. Scheduling for restart.
Jul 17 00:09:24 (none) daemon.info : starting pid 2262, tty '/dev/ttyS0': '/sbin/getty 115200,38400,9600,4800,2400 ttyS0'
dmesg
FAT-fs (fd0): Directory bread(block 19) failed
FAT-fs (fd0): Directory bread(block 20) failed
FAT-fs (fd0): Directory bread(block 21) failed
FAT-fs (fd0): Directory bread(block 22) failed
FAT-fs (fd0): Directory bread(block 23) failed
FAT-fs (fd0): Directory bread(block 24) failed
FAT-fs (fd0): Directory bread(block 25) failed
FAT-fs (fd0): Directory bread(block 26) failed
FAT-fs (fd0): Directory bread(block 27) failed
FAT-fs (fd0): Directory bread(block 28) failed
FAT-fs (fd0): FAT read failed (blocknr 8)
FAT-fs (fd0): FAT read failed (blocknr 8)
FAT-fs (fd0): FAT read failed (blocknr 8)
FAT-fs (fd0): FAT read failed (blocknr 8)
I forgot: floppy insertion and ejection are not detected by the system
Offline
Sorry for the delay. I've been very busy.
Anyway, I don't post the errors that appear because I have the same errors as gibor.
Offline
Ciao gibor e NarakuITA,
Quite strange.
On my side, no messages in[c]dmesg.log[/c] after the boot, only in messages:
[*]inserting a floppy disk
[c]Aug 26 15:15:52 (none) user.notice kernel: sd 2:0:0:0: [sdb] 2880 512-byte logical blocks: (1.47 MB/1.40 MiB)
Aug 26 15:15:52 (none) user.notice kernel: sd 2:0:0:0: [sdb] Write Protect is off
Aug 26 15:15:52 (none) user.debug kernel: sd 2:0:0:0: [sdb] Mode Sense: 00 46 94 00
Aug 26 15:15:52 (none) user.info kernel: sdb:[/c]
[*]mounting the volume
[c]Aug 26 15:18:05 (none) user.warn kernel: FAT-fs (sdb): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Aug 26 13:18:06 (none) daemon.notice udisksd[1795]: Mounted /dev/sdb at /media/disk on behalf of uid 1000[/c]
[*]unmounting the volume
[c]Aug 26 13:19:32 (none) daemon.notice udisksd[1795]: Cleaning up mount point /media/disk (device 8:16 is not mounted)
Aug 26 13:19:33 (none) daemon.notice udisksd[1795]: Unmounted /dev/sdb on behalf of uid 1000[/c]
or ejecting the floppy disk
[c]Aug 26 15:14:50 (none) user.warn kernel: VFS: busy inodes on changed media or resized disk sdb
Aug 26 13:14:50 (none) daemon.notice udisksd[1795]: Cleaning up mount point /media/SliTaz (device 8:16 no longer exist)
Aug 26 15:14:50 (none) user.info kernel: sdb: detected capacity change from 1474560 to 0[/c]
Messages in [c]dmesg.log[/c] just after the boot:
...
usb 1-1: new full-speed USB device number 2 using ohci-pci
usb-storage 1-1:1.0: USB Mass Storage device detected
scsi2 : usb-storage 1-1:1.0
...
scsi 2:0:0:0: Direct-Access Y-E DATA USB-FDU 4.01 PQ: 0 ANSI: 0 CCS
sd 2:0:0:0: Attached scsi generic sg1 type 0
sd 2:0:0:0: [sdb] Attached SCSI removable disk
udevd[930]: starting version 182
...
Offline
Hi Ceel
scsi 2:0:0:0: Direct-Access Y-E DATA USB-FDU 4.01 PQ: 0 ANSI: 0 CCS
it sounds like you have a usb floppy, and maybe that's not quite the same thing, since we detect the defect with a 34pin ide type interface. I don't know exactly what it's called, but it's the classic internal floppy mounted on old motherboards.
http://www.nullmodem.com/Floppy.htm
Offline
Hi gibor,
Right, its an external usb floppy. Hard to find a computer with an integrated floppy these days.
I have still one but it's in a box for 5 years. As soon as I'll have a little more courage, I'll do a test with it.
Offline
Pages: 1
[ Generated in 0.020 seconds, 7 queries executed - Memory usage: 1.56 MiB (Peak: 1.77 MiB) ]