Hi everyone,
Just upgraded to R5B7. Liking it a lot. No problems with th upgrade, except when it comes to my DVD drive.
The drive works... I used it to upgrade. I when I try to play a DVD, it won't work.
As I don't want to upset anyone, I shall use choose my words carefully: I am well aware of needing to follow the 'examples' of others and install 'pineapple' to make things work.
But for some reason it doesn't...
I choose play DVD and it tries to start the player and then I get kicked out to the menu again. I can see something flicking up on the screen (a notification of some sort) but it is too quick to see.
Where would I find the log of this failure?
Any ideas what I need to do to fix this?
Thanks in advance.

ps... I'm kinda hoping I need a new dvd drive so I can justify a new DVD RW to the missus (my finances are being watched as I have a habit of buying 'computer stuff' and she wants a decent holiday this year!)

Permissions? Try the x sessions log (search the wiki for "logfile" the CheckingLogFiles pages should be at the top of the list). If that doesn't have anything useful, exit the front end, start an xterm and run it (mythfrontend) from that.

Do you have more than one optical drive in the box?

also look at your command for playing dvd's in the settings and run that from an xterm might give you some more info as well.

_________________
Have a question search the forum and have a look at the KnoppMythWiki.

Xsecrets

Thanks you for the quick responces. I'll look into them today.
tjc- no I only have one drive but I would like to replace it with a dvd rw to back stuff up: I only have a DVD rom in there atm

The multiple queston was because it can confuse the cd_link.sh script. Have you tried running that and checking the results?

Thanks to tjc and XSecrets for helping me this far....

Well, after an hour of rooting around the logs I have discovered several reports of reports of the DVD not being able to be opened. More specifically in in /usr/log/messages and /usr/log/syslog

and in /home/mythtv/.xsession-errors


I could add more to that but not wanting to cause trouble, I shan't, suffice to say the .xsession-errors seems to report version "1.2.5" is there and would be used if the cd rom or dvd rom could be opened.

I tried running the cd_link.sh script. It didn't appear to do anything, apart from producing an error in the logs about not being able to open cdrom.

So I think this is a permissions problem.

when I typed

The responce was


Fairly conclusive stuff, now I've had a quick search regarding permissions and the references I have seen seem rather confusing. I searched the forum and didn't find anything immidiately obvious, and I found a number of web pages through Google.

I see I can change permissions of a file with chmod, but I'm still a little unsure of how quite to go about this or even if this is the correct command as I'm dealing with a device not a file. Then of course there are the switches to include, which according to one web site seemed to suggest I can use letters but numbers also.

Though I suspect I'm on the right lines, I'm not yet convinced. Any chance of a few pointers please?

Thanks again (and for reading this far!)

Chris

by the way, what would the command be to run play a dvd from an xterm window?

do as root

ls -l /dev/dvd

you should see something like this.

lrwxrwxrwx 1 root cdrom 8 Mar 9 22:49 /dev/dvd -> /dev/hdc

then do

ls -l /dev/hdc

alter the /dev/hdc if yours is different in the end of the output above.

you should see something like this

brw-rw---- 1 root cdrom 22, 0 May 7 2004 /dev/hdc

make sure the letters at the start match up and that root and cdrom match up. If not post your results here.

_________________
Have a question search the forum and have a look at the KnoppMythWiki.

Xsecrets

Like this:

Notice that I checked the symlinks first to verify their destination. Then checked that. Finally I made sure that the mythtv user was in the group that owns the real device. Remember symlinks are like a magician's smoke and mirrors, just "look over there" redirection.

Well, it looks like a case of 'Check, double check'. I got what was expected from both it seems, bar one thing... Anyhow, this is what I've done.

Xsecrets wrote:

I did the same and got:

respectively.

tcj wrote:


My results were:


The only difference I can see is my user (tophee) is listed as well as mythtv. Is that the problem?

I am playing along with this thread as I have exactly the same symptoms as tophee:

* DVD won't play DVDs
* "pineapple" is installed
* xine-check checks fine
* don't have multiple optical drives
* /var/log/messages has same "cdrom:open failed" message
* "ls -al /dev/cdrom /dev/dvd" reports as it should
* so does "ls -al /dev/hdc"
* like tophee, "grep cdrom /etc/group" includes my username as well as mythtv, rather than just mythtv

The extra group members are harmless.

tophee: per the xine howto on the wiki, did you try "xine -pfhq dvd://" instead of "xine -pfhq --no-splash --auto-scan dvd" or vice versa? I have not but will try it when I get home.

Hey Ceenvee
Haven't, but as I'm at home (and if I can get to the TV) I will try it now-ish...
If I get it done before you, I'll post back.
Chris

I checked my playback string and it was somehow set to "xine -pfhw --no-splash --auto-scan dvd" instead of "-pfhq." So the good news is that xine now runs and seems to recognize the disc, bad news is now I'm getting some kind of "audio module missing or busy" error. But the "cdrom open failed" message is not in /var/log/messages so that's progress.

Well, finally got on my Mythenbox and... no luck with making the changes to the player command.
The dvd player command was as I'd exected. I then changed it to
This didn't do anything new (unfortunately - unlike for Ceenvee).
When I tried to to play a DVD nothing happened apart from the GUI locking up.

One restart later...

I ran from an xterm. No problems were reported.

I then ran the dvd commands from an xterm. [
code]xine -pfhq dvd:// [/code] gave me a load of errors. Here's the abridged version...


Then I tried
to see if there was anything different reported. Not much, except less detail. Here's what I got back


Is xine wrongly pointing at a partition that doesn't exist (hda1)?

Still stuck, any further help would be good.
Thanks