Hi Uplink,

Yes indeed the pvr150 exposes 3 devices, i thought Mythtv wasn't seeing this right (and already i have learned )
By digging in deeper what exactly do you mean, what steps can i make?
thanks a lot,

Br,
Raymond

Going down the udev route, you'll have to see if there are more parameters you can use to select the device for the symlink. Right now your rule matches all three devices, and it's the last one that gets the symlink. With a bit of luck, there's something that differentiates these three devices and udev use that information. I vaguely remember something called like "kernel parameters" (or something with "parameters" in its name) which would be different for each device and you can use it to narrow down the selection so the symlink points to the right device.

Hi,

Just curios but - what happens on the MD when you are trying to PXE boot?

Do you get a kernel panic, do you get we are announced to the router, at what point does the MD fail and what is the message?

Cheers.

He said it's not getting past the DHCPOFFER message in syslog, so I assume the MD says "Getting DHCP address" (or similar) with dots printed after it, possibly displaying a new dot once every 1-3 seconds. This is a PXE BIOS message. No Linux or boot loader has been loaded at this point.

Uplink this is what i get:

Code:

lrwxrwxrwx 1 root root 7 2011-07-21 15:04 /dev/pvr150 -> video25

br,
Raymond

So it points to the wrong device. The pvr150 driver exposes three devices. Myth can only use the first one. You probably need to dig some more to see how to tell udev to make the symlink to the first device. I have a non-udev scripted solution somewhere in a long forgotten place (translation: I may not be able to find it) that updates MythTV settings at boot time base on concepts similar to the USB serial ports in LinuxMCE. I can't promise I'll find it, let alone help integrate it - time constraints and all.

One thing that did come to mind is this:

The DHCPOFFER message doesn't contain the parameters for PXE boot, so the machine is ignoring it. Not exactly sure how this could happen though.

But if you look in /etc/dhcp3/dhcpd.conf you should see a section that looks like this:

Code:

subnet 192.168.80.0 netmask 255.255.255.0 {
        next-server 192.168.80.1;
        filename "/tftpboot/pxelinux.0";
        option pxelinux.reboottime = 30;

        default-lease-time 86400;
        max-lease-time 604800;
        pool {
                 allow unknown-clients;
                 range 192.168.80.129 192.168.80.254;
        }
}

The important bit here is this:

Code:

        next-server 192.168.80.1;
        filename "/tftpboot/pxelinux.0";

If these two lines are missing, the PXE BIOS doesn't even bother to continue the negotiation and starts from the beginning. If they're not there it means someone decided to break PXE booting for some unknown reason.

First, whoever said "eth0 is supposed to be external", forget that idea and beat whoever put it in your head to begin with

Next, I always hate it when the DHCPOFFER reply seems to get lost on the network. I still don't have a pattern about how to fix this when it happens. Last thing I wanted to throw into a wall because of this was a SoundBridge (their forums said it was a hardware issue, so no hope for a fix in a firmware update).

m3freak: I'm pretty sure your core is OK. The problem is when negotiating DHCP. Could be as "simple" as what purps said. Could be something else altogether. If I can run a LiveCD on a machine that exhibits DHCPOFFER-ignorance, I run a LiveCD just to make damn sure I can get DHCP with the out of the box distro. If not, I look in /var/log/syslog on both the Core and the machine in question to match them up. I even go as far as to run tcpdump on the machine that won't take DHCPOFFER as an answer to see if the message comes in (at this point I also get all kinds of ideas that there might be a "third party" on the network messing things up).

Not an easy thing debugging this. And it's annoying too.

I only skimmed over the thread, but I think the Realtek you mentioned is in your core. Try to leave the driver swap for last. See what you have in the machine you want to use as an MD.

Kubuntu goes fine, but when I run the LinuxMCE script I get a 'no resume image, doing normal boot' and then it boots to a prompt.
No worries, the forum or the wiki will have the answer, and I'll learn a little Linux on the way. Again no dice. Other people have had the same error, but there seems to be no answers.

This is one of those lightbulb moments: Can you verify that things have really stopped? There are cases when things are just slow before X is started and you are left watching a login prompt which can make you think that's as far as you'll go. A thing that comes to mind that could slow things down this way is the lack of a Internet connection. Please login and paste a list of running processes in here. Use this command:

Code:

ps -axf

to get the process tree. Ping google.com while you're there to confirm the Internet works too.

Why do I get the feeling I shouldn't assume you know how to redirect the output of a command to a file and paste it to a website?

Hi Uplink,
Thanks for helping,

Not entirely shure what you mean but this is what happens:
For the hauppage pvr150,
when i set mythtv to /dev/video1 i get a picture and everything seems to be ok but,
when i set mythtv to /dev/pvr150 it doesn't seem to work.

br,
Raymond

What I mean is: can you confirm /dev/pvr150 actually exists and is a symlink to /dev/video1?

Code:

ls -l /dev/pvr150

this should do it

Sorry for hijacking a bit (just trying to understand how things work and having trouble ripping some dvd's)
but what is the relation between setting a default region to your dvd-drive and libdvdcss2 ?

br,
Raymond

As Andrew said, we found most drives currently made (if not all of them) want a region to be set even to properly operate with region-free DVDs. These changes in behaviour always catch us by surprise. I have an old DVD drive that even supports being set to ALL the regions at once (a thing that newer drives don't accept) and it doesn't care what region is set to operate.

Most of the drives we encounter these days want the region to be set, but they don't actually enforce it. But we found at least a make that "kind of" enforces a match between the region you set and the region of the DVD and will make you go crazy trying to understand why discs that don't match the region behave the way they do (in one case we encountered "short" rips: there were no errors but the drive lied and said the size of the DVD is a lot smaller than it really is).

It's a minefield as far as I can tell.

Right now Dianemo doesn't have a easy install DVD either. The difference is that when you buy a system we do the installation for you, so it seems easy. We also help if you run into trouble. I'm making it easier every chance I get, but the idea is we have a person here who does all the installs and by doing so many installs he got around various gotchas as time went by. It also seems easy because we have a limited choice of hardware, and I tend to scream a lot when new hardware that I didn't get to test gets thrown in the mix and is expected to work.

If anything, the key word here is "persistence". Install, scream, format, start over. In a few weeks you'll figure out a few patterns and it will work. If possible, make some notes for the rest of us. Sometimes a little note about a little quirk can light a lightbulb in someone's head about something he's been thinking on when idle but is at the back of their head and need a little nudge to surface. And when it surfaces, it's such a simple thing that the person in question will have no peace unless they do it.

Do the symlinks point to the same devices you'd give MythTV? If yes, does MythTV work when you give it the device names directly but doesn't work when you give it the symlinks? If the second case is true, it is very odd behaviour of symlinks.

I'm on 8.10 all it's the only version I have found to work !!

I do hope you reported what you found not to work in 1004 when you tried it.

Could you please explain a bit more because this thread is only 1 post long
thanks upfront,
br,
Raymond

He probably meant to say "see the bottom of this post, in my signature".

You'll be "happy" to know that possy's debs don't create /usr/pluto/orbiter/bits That's why things still don't work out of the box. I'll chase him up for a fix.

Andrew or Uplink, i got into a bit of trouble could one of you help?

i installed
http://deb.linuxmce.org/pluto-proxy-orbiter_2.0.0.44.11071224175_i386.deb
http://deb.linuxmce.org/pluto-website-admin_2.0.0.44.11071224175_i386.deb
and the new Dianemo iOS Orbiter v1.2.

also created a dir: sudo mkdir -p /usr/pluto/orbiter/bits

but the Dianemo iOS Orbiter v1.2 and the existing RoamingOrb are not working anymore

i did: /usr/pluto/bin/Proxy_Orbiter -d 40 -r localhost which gave me:

Code:

Proxy_Orbiter, v.2.0.0.44.11071224175
Visit www.plutohome.com for source code and license information


     =======================|  DirectFB 1.0.1  |=======================
          (c) 2001-2007  The DirectFB Organization (directfb.org)
          (c) 2000-2004  Convergence (integrated media) GmbH
        ------------------------------------------------------------

(*) DirectFB/Core: Single Application Core. (2008-09-12 19:59)
(!) Direct/Util: opening '/dev/fb0' and '/dev/fb/0' failed
    --> No such file or directory
(!) DirectFB/FBDev: Error opening framebuffer device!
(!) DirectFB/FBDev: Use 'fbdev' option or set FRAMEBUFFER environment variable.
(!) DirectFB/Core: Could not initialize 'system' core!
    --> Initialization error!
Failed initializing SDL: DirectFBCreate: Initialization error!
01 07/14/11 11:34:55.485 X is not running! Starting X and the window manager: /usr/pluto/bin/Start_X.sh <0xb4ee96f0>
1 07/14/11 11:34:58 SetupAudioVideo (server) Starting
1 07/14/11 11:34:58 SetupAudioVideo (server) '
1 07/14/11 11:34:58 SetupAudioVideo (server) DBSetting: S Reboot:  Script Path: /usr/pluto/bin/
1 07/14/11 11:34:58 /usr/pluto/bin/Start_X.sh (server) Starting X server (client: /usr/bin/xfwm4; parms: --compositor=off)
1 07/14/11 11:34:59 /usr/pluto/bin/Start_X.sh (server) X server: backround; AlphaBlending: 0

any help would be much appreciated,
br,
Raymond

It looks like you ran this without a valid DISPLAY variable in the terminal. I think DirectFB is attempted when you do that. No idea why. I think SDL decides to try it out.

my genereic  web device  is  34  
and generic proxy orbiter is 35


from the apache log  i get

2.168.80.1 - - [12/Jul/2011:11:49:56 -0300] "GET /lmce-admin/weborbiter_image.php?device_id=34 HTTP/1.1" 404 262 "-" "Mozilla/5.0"
192.168.80.1 - - [12/Jul/2011:11:49:56 -0300] "GET /lmce-admin/weborbiter_command.php?device_id=34&cmd=SCREEN_XML HTTP/1.1" 404 262 "-" "Mozilla/5.0"
192.168.80.1 - - [12/Jul/2011:11:49:56 -0300] "GET /lmce-admin/weborbiter_image.php?device_id=34 HTTP/1.1" 404 262 "-" "Mozilla/5.0"
192.168.80.1 - - [12/Jul/2011:11:49:56 -0300] "GET /lmce-admin/weborbiter_command.php?device_id=34&cmd=SCREEN_XML HTTP/1.1" 404 262 "-" "Mozilla/5.0"
192.168.80.1 - - [12/Jul/2011:11:49:57 -0300] "GET /lmce-admin/weborbiter_image.php?device_id=34 HTTP/1.1" 404 262 "-" "Mozilla/5.0"
192.168.80.1 - - [12/Jul/2011:11:49:57 -0300] "GET /lmce-admin/weborbiter_command.php?device_id=34&cmd=SCREEN_XML HTTP/1.1" 404 262 "-" "Mozilla/5.0"

Can you access this orbiter using the Web Orbiter interface in a browser? Go to /lmce-admin/weborbiter.php

There are three points where weborbiter_command.php says 404:

- if the device_id is not given or empty
- if the device given doesn't exist or isn't a proxy orbiter
- if the Proxy_Orbiter DCE device can't be contacted (i.e. it's not running, it died, this kind of thing)

In addition to these, weborbiter_image.php says 404 if the image contents couldn't be retrieved.

I'd be looking to see if the Proxy_Orbiter device is running. It may have died 50 times. If a device dies 50 times, it will stay dead until you do one of these: 1. reboot or 2. delete the Generic Proxy Orbiter device number from /usr/pluto/locks/pluto_spawned_local_devices.txt and reload the router. Note how this is the child device's number. It's a bit confusing, but you get the hang if it.

Also, make sure you have the latest pluto-proxy-orbiter package. This package creates the /usr/pluto/orbiter/bits directory. Without this directory Proxy_Orbiter will die.