CD Player problems

[phil1349]

I cannot get CDs to play properly on my Lenovo laptop. When using kscd, after a CD is inserted, the disk/track information is displayed but it will not play. I tried kaffeine and it also displays the disk info and plays the first track perfectly at the end of which it just stops and refuses to do anything else untill the disk is ejected and reinserted. If I try the track forward function while playing the first track it stops and again will not respond to the control buttons untill after the disk is ejected.

Any ideas on how to fix this ? As far as I'm aware, all appropriate codecs/libraries are installed.

[Rog131]

Do you get any error messages if you start the player from the konsole ?

Konsole:

kscd --nofork

or/and

kaffeine --nofork

KDE options:

--nofork Do not run in the background.

[phil1349]

Tried running both players from commnd line as recommended by Rog131 which gave the following messages :-

"QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave."

and they both misbehaved as before. Interestingly, running the players from the command line without the --nofork option resulted in the error message being printed twice.

[Rog131]

Hmm - sadly the "QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave." is only a warnig: http://forum.kde.org/viewtopic.php?f=66&t=102251. So it is not helping to solve the problem.

Do you have another OS in your Lenovo ? That is - If the CD's are playing fine with the Windows then the problem is not with the hardware.

[phil1349]

I have Windoze 7 on the laptop & CDs/DVDs play perfectly on that so it is not a hardware problem. Using Kubuntu, DVD's play perfectly with Kaffeine. I cannot understand why CD will play the 1st track only then stop. Also when playing that track, the control buttons do not work, the just stop the player & nothing responds until either Kaffeine is shut down and restarted & the CD ejected & re-inserted.

I followed the links you indicated which indicate this may be a deep-seated problem in KDE itself.

[Rog131]

At here
(with Kubuntu 12.04.2/KDE 4.8.5/KSCD 1.5/Kaffeine 1.2.2)

There is the Qt warning but the CDs are playing fine.



KSCD & Kaffeine

The KSCD is using the KDE settings and the phonon. The Kaffeine is using the Xine.

Kaffeine/Xine setting file: ~/.xine/config


Check list

0 Is the problem with the hardware - It seems that it is not.
1 Are there error messages ? - It seems that there are none.
2 The KDE Audio/CD settings: KDE System Settings > Multimedia > Audio CDs. 'Is there Specify CD Device: /dev/cdrom' ?



If yes - Is the device file pointing to the real device ?

ls -l /dev/cd*

At here:

lrwxrwxrwx 1 root root 3 May 14 13:36 /dev/cdrom -> sr0
lrwxrwxrwx 1 root root 3 May 14 13:36 /dev/cdrw -> sr0

How about there ?

Is the hardware detected right ?

dmesg | grep sr0

At here:

[ 2.551620] sr0: scsi3-mmc drive: 48x/12x writer dvd-ram cd/rw xa/form2 cdda tray
[ 2.551839] sr 4:0:0:0: Attached scsi CD-ROM sr0

How about there ?

More:
Has the CD played well with the earlier Kubuntu (Linux)versions ?
Did the CD play earlier with the Kubuntu 12.04 ?

[phil1349]

We might be getting somewhere, ls -l /dev/cd* returns "ls: cannot access /dev/cd*: No such file or directory". Replacing cd* with sr* returns "brw-rw----+ 1 root cdrom 11, 0 May 14 18:13 /dev/sr0" which would indicate it is treating the cd/dvd player as a block device. No real surprises there but the permissions look strange so I tried running kscd as root but no change in behaviour."dmesg | grep" produced no output for either cdrom or sr0.

I checked out the system settings for audio & this pointed to /dev/cdrom, tried changing to sr0 but no change.

I have 12.04.2 installed on my desktop & kscd works normally on this. Also ls -l /dev/cd* on this produces much the same output as indicated in the last post from Rog131. Again, no great surprises there.

Could the problem be related to the way my Lenovo laptop connects to the optical drive ?

[Rog131]

Looking the hardware

The lshw command should list all detected hardware and information of them.

At here:

sudo lshw

is telling:

*-cdrom
description: DVD-RAM writer
product: DVDRAM GH22NS90
vendor: HL-DT-ST
physical id: 0.0.0
bus info: scsi@4:0.0.0
logical name: /dev/cdrom
logical name: /dev/cdrw
logical name: /dev/dvd
logical name: /dev/dvdrw
logical name: /dev/sr0
version: HN00
capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram
configuration: ansiversion=5 status=nodisc

There is an option to redirect the output to the html file and then view it in the browser:

sudo lshw -html > lshw.html

Could the problem be related to the way my Lenovo laptop connects to the optical drive ?

Is it a usb device ?



udev rules

The symlinks (/dev/cdrom/->sr0 etc) are made when the system is booting up.

The rules file is /etc/udev/rules.d/70-persistent-cd.rules

Sometimes, when there are more than one CD/DVD device, the symlinks have been pointing to the wrong device.

[phil1349]

lshw produced the following output:-

*-cdrom
description: DVD-RAM writer
product: DVD-RAM UJ8C1
vendor: MAT****A
physical id: 1
bus info: scsi@2:0.0.0
logical name: /dev/sr0
version: 8.20
capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram
configuration: ansiversion=5 status=nodisc

I was surprised that there were no other logical names declared. The "/etc/udev/rules.d/70-persistent-cd.rules" file was blank except for the comment lines.

It was the same on my desktop, only sr0 declared and a blank rules file but that works perfectly.

Maybe adding rules may cure the problem, it mentions udev(7) for syntax, where do I find this ?

[Rog131]

Automatic

If the "/etc/udev/rules.d/70-persistent-cd.rules" is missing then it should be created when booting (tested - renaming the 70-persistent-cd.rules, booting -> there is a new one).

Manual way

Manual creation: http://comments.gmane.org/gmane.linu...an.user/434723

Move "/etc/udev/rules.d/70-persistent-cd.rules" to another location
and run "echo add > /sys/block/sr0/uevent".

Tested with the command:

sudo bash -c 'echo add > /sys/block/sr0/uevent'

Seems to create a new 70-persistent-cd.rules file.

70-persistent-cd.rules @ here

# This file was automatically generated by the /lib/udev/write_cd_rules
# program, run by the cd-aliases-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and set the $GENERATED variable.

# HL-DT-ST_DVDRAM_GH22NS90 (pci-0000:00:14.1-scsi-0:0:0:0)
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:14.1-scsi-0:0:0:0", SYMLINK+="cdrom", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:14.1-scsi-0:0:0:0", SYMLINK+="cdrw", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:14.1-scsi-0:0:0:0", SYMLINK+="dvd", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:14.1-scsi-0:0:0:0", SYMLINK+="dvdrw", ENV{GENERATED}="1"

Documents

Debian udev wiki: http://wiki.debian.org/udev

or/and

man udev:

UDEV(7) udev UDEV(7)

NAME
udev - Linux dynamic device management

DESCRIPTION
udev supplies the system software with device events, manages permissions of device nodes and may
create additional symlinks in the /dev directory, or renames network interfaces. The kernel usually
just assigns unpredictable device names based on the order of discovery. Meaningful symlinks or
network device names provide a way to reliably identify devices based on their properties or current
configuration....

More of the docs/man pages:

- http://www.kubuntuforums.net/showthr...mentation-help
- http://www.kubuntuforums.net/showthr...an-page-viewer