Report probable bug « SliTaz Forum

SliTaz Forum » English Support » Hardware

Report probable bug

(5 posts) (3 voices)

Started 2 weeks ago by NarakuITA
Latest reply from gibor
This topic is not resolved

Tags:

No tags yet.

NarakuITA

offline
Member

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?

Posted 2 weeks ago #
Ceel

offline
Administrator

Hello NarakuITA,

I cannot reproduce the problem you described on my old computer.
Is the gvfs-udisks2 installed?
tazpkg info gvfs-udisks2
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.

Posted 2 weeks ago #
NarakuITA

offline
Member

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.

Posted 2 weeks ago #
Ceel

offline
Administrator
Hello,

I don't know if this can bring interesting information but please
boot your SliTaz
open the Sakura terminal and type
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.
Posted 1 week ago #
gibor

offline
Moderator

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

Posted 6 days ago #

RSS feed for this topic

Reply

You must log in to post.