DB <Freddog_de <at> yahoo.co.uk> writes: > ... > b) here's the tail output.... > > Dave <at> Fedora-Blue ~]$ sudo tail /var/log/messages > Apr 3 15:29:11 Fedora-Blue kernel: [83978.355678] sr 4:0:0:0: [sr0] > CDB: Read(10): 28 00 00 1f ff 6a 00 00 02 00 > Apr 3 15:29:11 Fedora-Blue kernel: [83978.355694] end_request: I/O > error, dev sr0, sector 8388008 > Apr 3 15:29:11 Fedora-Blue kernel: [83978.355703] Buffer I/O error on > device sr0, logical block 1048501 > ... > Basically, tells me SFA! & when I tried loading a workable DVD, there > is nothing in /var/log/messages to compare it with... > ... Well, at least I have learned something. I had to look it up ... SFA means "Sweet F**k All", slang for "nothing" :-) Keep in mind that I am not expert on this, just a user and an observer who tries to deduce causes of it all :-) Your inability to read your media (properly) may have at least two causes: - media settings (faulty code) in your KDE I am a GNOME user, but you should be able to find it in KDE as well. It is about: File Management Preferences - Media - Media Handling Choose what happens when inserting media ... etc. - kernel scsi interface and driver problem Also, you should test it (inserting and reading media) in both KDE and command line environment, while watching and documenting '# tail /var/log/messages' output after every event or entry: - KDE, under various media handling scenarios (see above) - in xterm only, using any combinations of entries e.g. a). do some basic scsi, drive, and driver checking (man wodim) # wodim -checkdrive # wodim -scanbus # wodim --devices etc b). then, insert your media # df pay attention to mount options ... # mount # umount /media/<whatever> # mount -t auto /dev/sr0 /media # ls /media/* It would be good if you test your drive by preparing small iso file and burn a CD-RW disk (or CD-R if you want to be wasteful). This should also show you potential errors, and confirm if your drive is healthy or not. Document action and faulty behavior/error output to be able to file a Bugzilla report, most probably to kernel scsi subsystem maintainers. Btw, yesterday I was in trouble with my notebook CD/DVD R/W drive when I wanted to burn a CD-RW disk. I tried it with Brasero disk burner app - failure. I tried it with 'wodim' on the command line, even 'wodim -scanbus' told me to f*k off due to something like "... inability to recognize scsi interface or finding a driver ...". After rebooting I was able to make it work with wodim. I do not remember anything like that happening ever ... That tells me perhaps there is a common problem for all of us, and not specific to GNOME, KDE, or any of their applications, but rather to wodim or kernel scsi interface and drivers. JB -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
