Well, the fact that the error message reported by both mythbackend and the touch command is "No space left on device" I don't think that your problem is a permission error.

I have heard of reports of people running out of inodes causing problems. I thought that that only occurred because they had tuned the file system for the myth partion to be more efficient by limiting the number of inodes, and some people had tried to load 100000 mame roms. I also thought that the latest releases did not tune the filesystem anymore for this reason. search the forum to find out more about that.

You may also want to check the consistency of the drive. I may have become corrupted?? I dont really know about how to do that off the top of my head, byte search the forum for fsck*.

yeah.. i guess it is probably just a hardware issue.. ill grab a new hhd tomorrow.. and try a clean install on that.

i think we've put enough effort into this little problem.. my hardware was never really going to cut the mustard as a setup anyway.. i was just trying to convince myself that i could get it to work before i commited a grand to a new system...ill buy a new box tomorrow and let you know.. off to tier one i go in search of a mobo.. thnaks for your efforts .. appreciated muchly.

_________________
"enter witty comment here"

stevo, just so you know, the rwx thing specifies the access permissions on the files.
The d at the start says it is a directory.
the next three letters specify the access for user that owns the file.
the next three the access for all users in the same group as the file.
the last three the access for all others.
r represents read permission, w write permission, x execute permission.
A dash indicates no permission to access for the mode in that position.

there are some interesting errors that happen during my computer starting up.. but i cant seem to pause the screen by pressing pause.. is there any way i can scroll back through the dialog during startup.. cheers.

steve

_________________
"enter witty comment here"

I found this thread since my frontend was complaining that it couldn't detect the backend. I just downloaded the R5A15.1 last night and am trying to set it up on a P2.4, 250GB, Haupauge P350 with nvidia geforce 3 ti 200.

When I do the ps -ae | grep myth .....it typically is just stating that the frontend is running. So I try running mythbackend and it just spits me right back to the prompt.....no errors no nada.

On a healthy system...

To debug this try running:

Which should give you better diagnositics.

If you're sure the server isn't running you might try removing /var/run/mythtv/mythbackend.pid before you do that check the permissions on the directory which should look like this...

Also check the logfiles in /var/log for any driver issues...

OBTW - Try this too... If it returns more than one line you screwed up the install by creating an extra mythtv user. Cecil's directions are quite explicit about not doing this, but lots of people still make the mistake.

tjc:

here are the results....



next I did...



still came back without a single line of info.....just jumped right back to the prompt.

then...



Now that seems like an issue.....I've got a total of 8 vs your 12 and I'm missing the last line.

I continued and did...



and that just came back with a single line....so I suppose I did something right during the install.

The embarrassing thing is that I don't know how to look at the log file you specified. This is pretty pathetic I know, but I've just started down the linux path by installing Xandros a little bit ago so any help would be appreciated. Also....when I ran all of those commands I did it by hitting CTRL-ALT-F1 and just typed there....I'm assuming that isn't a problem....it leaves the desktop environment over at CTRL-ALT-F7.[/code]

No, that's actually fine... It just means it isn't running.

To see the contents of the directory is just another ls command:
Here (a)ll including dotfiles, (l)ong format, (t)ime order, and (r)eversed sort. The idea is to show you which log files have changed most recently so you can focus on those. You can then browse the files with the more command, or your favorite editor, or just look at the last 50 lines with something like tail -50 filename

OBTW - Here's a nice Unix tutorial I've been pointing folks at work to when they ask - http://www.ee.surrey.ac.uk/Teaching/Unix/

Oh! I almost forgot... Let's check your back end binary...
This is for R5A15.1 although Cecil may have rebuilt between the version I have installed and the public alpha version...

Ok.....here we go....first off I appreciate pointer to the UNIX tutorial, I'll definitely be reading up on that. Secondly I'm not exactly sure what to look for in the log files. I looked at the last 50 lines in each and nothing was exactly jumping out with a big yellow flag. Buuuut then I went back to CTRL-ALT-F7 (I need to know what that is called.....a terminal?) where my front end was and I exited out (not sure if I can minimize the full screen frontend without having to exit). Then I opened an XTerm window and typed mythfrontend. Obviously the front end opened but this time when I closed it I could see there were logging entries going to the console. In any case here's what it was yapping about:


I suppose I was hoping that the lirc_init failed message was important.

Not terribly meaningful since your backend isn't running.

What about checking the binary?

Oh, and look in /var/log/mythtv/mythbackend.log too

Dang, I knew I had forgotten something.

[code]ls -al /usr/bin/mythbackend
-rwxr-xr-x 1 root root 0 May 14 07:39 /usr/bin/mythbackend

md5sum /usr/bin/mythbackend
d41d8cd98f00b204e9800998ecf8427e /usr/bin/mythbackend[code]


And the /var/log/mythtv directory is empty[/code]

I can't say that I like that checksum much...

If you haven't done a lot of other work on this system I would consider downloading a fresh ISO image, verifying the md5sum of that, burning it at the slowest speed and doing an auto upgrade.

HOLY ****! I just noticed that your /usr/bin/mythbackend is zero length!!! OK, you DEFINITELY have an install problem. Time to upgrade or reinstall with a fresh ISO.

Heh, i had the same reaction.

Alrighty....so now that the laughing has subsided.....I've got a semi-working Myth box now. Gotta tell ya that is pretty sweet seeing some tv finally coming across.

I've gone into the tv program settings and attempted to enable the pvr-350's tv-out / MPEG decoder but that knocks out the ability to watch tv. Should I even bother with that or should I just use my geForce 3 TI200 card as the S-Vidteo output?

Also I was switching through some channels and then it seemed to lock and was just giving me a blank screen. I wound up rebooting and it started working again, but is that a common occurance with the PVR350?

By the way I certainly appreciate all the time you put into helping me there tjc.

I'm gonna search around and try and knock out these other probs, but I just noticed someone mentioning that the UI is very hard to get to display on the tv. I was under the assumption that once I got my tv out to work it would be displaying everything as I'm seeing it on the monitor right now.

I think the appropriate emoticons were more like:

Get it working the easiest way first, back that up, and then explore. Someobody has a script for setting up a PVR-350 as your display driver posted if you look.

No idea. There used to be a problem where if the tuner couldn't get a lock it'd go off to the land of lost bits but that was supposed to be fixed...

Pay it forward and help the next guy... It's all about community. (BTW - This is where I think the Harvard MBA types who think "altruism" is unnatural have gone very, very wrong. The "case system" apparently leaves their poor brains too narrow to grasp the concept of enlightened self intrest with a time horizon longer than next quarter.) I figure as soon as you get it working you'll know more about the PVR-350 than I do.

Getting TV output working takes me about 5 minutes on an upgrade or reinstall but that's because I've got an XF86Config-4 that I know works for my hardware. Usually all I do is run the install-nvidia-XXXX-debian.sh script and drop in my XF86Config-4 file. Occasionally I have to experiment with other stuff because there was a change.