Unable to read picture cds

I have the 64bit version of SuSe 11.2 installed on my PC.
For some reason it cannot read a Jessops photo cd which reads ok on a windows pc or any other cd with photos on it, it has no problem reading other cds with program files on them.
Any suggestions how I solve this problem?

Does k3b see the CD
If so, try copying it to a .iso then see if you can read the .iso with VLC or acetoneISO

Probably something to do with the way it was made…

I suspect that Jessops photo cd is some propritary format. Did you install some Windows App to use it in windows? If so that probably installed the needed drivers.

K3b is able to show media info as follows:
Medium Type: CD-R
Capacity: 79:57:74 min (702.8 MiB)
Used Capacity: 60:09:39 min (528.7 MiB)
Remaining: 00:00:00 min (0 B)
Rewritable: no
Appendable: no
Empty: no
Sessions: 1
Supported writing speeds:
8x (1411 KB/s)
16x (2822 KB/s)
24x (4234 KB/s)
32x (5645 KB/s)
40x (7056 KB/s)
48x (8467 KB/s)
ISO9660 Filesystem Info

System Id: -
Volume Id: Image CD 061310
Volume Set Id: -
Publisher Id: -
Preparer Id: -
Application Id: -
Volume Size: 528.4 MiB (2,048 B * 270,562 blocks = 554,110,976 B)
Tracks

Type Attributes First-Last Sector Length
1 (Data/Mode2 XA Form1) no copy/uninterrupted 0 - 270713 270714 (60:09:39)

It cannot show the individual files.
In Dolphin or My Computer the CD is not seen at all.
The Jessops cd does contain a program for showing a slideshow but windows is able to see and read all files without this.
Has anybody encountered a similar problem with 64 bit 11.2?
I did not have any problems with 32 bit 11.1 reading the same cds!

The Jessops cd does contain a program for showing a slideshow
Doh! Vendor locked after a fashion!
Can you open the cd in Win, extract the files and put them on the HD. Linux can read your win partition.

This is not confined to the Jessop cd it would appear to be problem with any photo file cd produced in microsoft windows.
I no longer have windows on my main pc, have to go to the wife’s laptop if I need to check something in windows.

It is something to do with the software used to make the CD. Understand this, microsoft and vendors that produce software for that OS, do not want you to use free software/OS’s like openSUSE/Linux.

“It is something to do with the software used to make the CD. Understand this, microsoft and vendors that produce software for that OS, do not want you to use free software/OS’s like openSUSE/Linux.”

I already knew this.

Please read what I posted again, this is definitely a problem with SuSe 11.2. How else can you explain why a CD which works perfectly in Suse 11.1 32 bit will not read in SuSe 11.2 64 bit and how do I draw it to the attention of those who need to know?

Its difficult to determine what is failing for you here. Try the following: Insert your photo CD, and click on the cd icon (that shows up in ‘Places’ menu in Dolphin, so that the file system is mounted. Then type ‘mount’ in a terminal.

If I do this with a photo cd I have available, I get

/dev/sr0 on /media/London Photos type iso9660 (ro,nosuid,nodev,uid=1000,utf8)

What does this command return?

dmesg |tail

For reference, I get

ISO 9660 Extensions Microsoft Joilet Level 3
ISOFS: changing to secondary root

I assume you have the libiso9660-7 package (or similar) installed? (Normally included by default at install time).

About all I can think of at the moment…

deano_ferrari,

This is part of the problem as I stated earlier Dolphin does not see the CD so that there is no CD icon in ‘Places’.
K3b, however, is able to see the CD and provide basic information(as I posted earlier) but cannot see individual files.
I opened a terminal and tried typing mount and this is what I get:
" /dev/sda2 on / type ext4 (rw,acl,user_xattr)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw)
udev on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
/dev/sda3 on /home type ext4 (rw,acl,user_xattr)
/dev/sdb1 on /windows/C type vfat (rw,noexec,nosuid,nodev,gid=100,umask=0002,utf8=true)
/dev/sdc1 on /windows/D type vfat (rw,noexec,nosuid,nodev,gid=100,umask=0002,utf8=true)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
securityfs on /sys/kernel/security type securityfs (rw)
gvfs-fuse-daemon on /home/john/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=john "

double dutch to me I am afraid! as my brain is incapable of coping with command line stuff any more.

I next tried typing “dmesg |tail” in termianal and this is the response:
" 2791.369150] sr 1:0:0:0: [sr0] Sense Key : Medium Error [current]
2791.369169] sr 1:0:0:0: [sr0] Add. Sense: Unrecovered read error
2791.369187] end_request: I/O error, dev sr0, sector 19192
2791.369203] Buffer I/O error on device sr0, logical block 2399
2798.371402] sr 1:0:0:0: [sr0] Unhandled sense code
2798.371430] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
2798.371450] sr 1:0:0:0: [sr0] Sense Key : Medium Error [current]
2798.371470] sr 1:0:0:0: [sr0] Add. Sense: Unrecovered read error
2798.371489] end_request: I/O error, dev sr0, sector 19192
2798.371506] Buffer I/O error on device sr0, logical block 2399 "

I have libiso9660-7 installed.

I hope the above allows you to throw some light on the matter
A further thought that occurs is could it be associated with tne actual software used to write the CD as I know that two of the CDs involved were produced with Roxio software. Although my heading suggested it it is not just photo CDs as the last CD I tried held two Word documents and one .pdf file.

I must admit I’m baffled by those particular errors reported by dmesg. There are numerous threads discussing these type of errors (if you google with any one of those errors), however not much I’ve dug up so far appears to be helpful or promising. For example, a typical similar thread:

CD burning problems

One openSUSE thread that may be worth reading:

CD/DVD player not recognized - openSUSE Forums

It might also be worth trying a Live CD distro to compare results with. I’ve read suggestions online about checking the BIOS DMA settings too (if relevant).