| Author |
Message |
|
JoJa15
|
 Posted: Fri Dec 31, 2004 3:15 pm |
|
|
Joined: Tue Jun 15, 2004 12:57 pm
Posts: 31
|
I am trying to use a MediaMVP to watch my KnoppMyth recorded TV shows. I am trying to follow the instructions on the KnoppMyth wiki here:
http://knoppmythwiki.homelinux.org/index.php?page=MediaMVP_LinuxHOWTO
The first problem I encountered was in step #2 where it said:
Code: cd /opt Since I logged in as mythtv as instructed in the instructions and then did su in step 2 I was in the following directory: Code: root@mythtv:/home/mythtv# ls -l
total 1840
drwxr-xr-x 6 500 users 4096 Oct 25 19:52 mvpmc
-rw-r--r-- 1 mythtv mythtv 1860600 Oct 25 22:49 mvpmc_src.tar.gz
drwxr-xr-x 2 mythtv mythtv 4096 Oct 29 2003 tmp
As you can see there is no opt directory. Is it somewhere else? I did not know how to go looking for it if it was somewhere else so I just did mkdir opt to create it. In step 3 it asks me to do the following: Code: mkdir /tftpboot I assumed that it wanted me to do it in the mythtv home directory. If that is wrong someone let me know. Here is what my mythtv home directory looks like now: Code: root@mythtv:/home/mythtv# ls -l
total 1840
drwxr-xr-x 6 500 users 4096 Oct 25 19:52 mvpmc
-rw-r--r-- 1 mythtv mythtv 1860600 Oct 25 22:49 mvpmc_src.tar.gz
drwxr-xr-x 3 root root 4096 Dec 29 10:47 opt
drwxr-xr-x 2 root root 4096 Dec 29 12:08 tftpboot
drwxr-xr-x 2 mythtv mythtv 4096 Oct 29 2003 tmp
My next problem is that the instructions on the KnoppMyth WIKI site do not have anything for step 4 and step 5. It just goes from step 3 to step 6. Is there a step 4 and 5? Step 6 tells me to do the following: Code: 6. Now that the cross compiler softwware is present in /opt, and the dongle.bin kernel is in /tftpboot, you can change directories to the source folder and build the new kernel.
cd /home/mythtv/mvpmc_src
./build.sh
There is no mvpmc_src directory that I can find. When you extract mvpmc_src.tar.gz it creates a mvpmc directory. So I assumed that is what it is referring to and I do cd /home/mythtv/mvpmc.
I then try to do ./build.sh but there is no build.sh script in the /home/mythtv/mvpmc directory.
If I poke around I can find the build.sh script in /home/mythtv/mvpmc/scripts. If I do cd /home/mythtv/mvpmc/scripts and then try ./build.sh I get the following response "workarea not specified!". This is the point where I am stuck. Can anyone help me out with this problem and the other ones mentioned above? Is there a way someone could just send me the compiled program or for it to work do I have to compile it myself on my system?
Thanks for any help in advance.
|
|
| Top |
|
 |
|
ceenvee703
|
Posted: Fri Dec 31, 2004 7:04 pm |
|
|
Joined: Fri Apr 02, 2004 10:08 am
Posts: 1637
Location:
Virginia, USA
|
I wrote that quite a while ago--can't say how complete it is any more or what's been changed. Since then, I think that getting it working under Linux has changed quite a bit. I'd recommend viewing this thread:
http://www.shspvr.com/forum/viewtopic.p ... mc&start=0
I pretty much gave up doing it via Linux and now drive my MediaMVP from a Windows machine (which connects to my MythTV backend's smb-shared /myth/ folder).
|
|
| Top |
|
|
|
Greg Frost
|
Posted: Fri Dec 31, 2004 8:27 pm |
|
|
Joined: Mon May 10, 2004 8:08 pm
Posts: 1891
Location:
Adelaide, Australia
|
|
JoJa15, I know nothing about MediaMPV, but when a directory is specified with a slash on the front (such as /opt and /tftpboot in your post) the directories are relative to the root directory, not your current directory. "cd /opt" will take you to the opt directory under the root directory and "mkdir /tftpboot" will make a directory tftpboot in the root directory. The contents of /home/myth are irrelevant.
|
|
| Top |
|
|
|
JoJa15
|
Posted: Sun Jan 02, 2005 7:16 am |
|
|
Joined: Tue Jun 15, 2004 12:57 pm
Posts: 31
|
|
ceenvee703 thank you for the link. It looks like they have binary versions now so I don't need to worry about compiling the app. Thank you for all the help. If I can get it to work I may go and update the WIKI if I can figure out how to do that.
Greg, thank you for the tip you are totally right. I have been away from Linux for a long time and forgot that.
Thanks,
JoJa15
|
|
| Top |
|
|
|
ceenvee703
|
Posted: Sun Jan 02, 2005 8:24 am |
|
|
Joined: Fri Apr 02, 2004 10:08 am
Posts: 1637
Location:
Virginia, USA
|
Quote: If I can get it to work I may go and update the WIKI if I can figure out how to do that.
Believe me, updating the wiki is waaaay easier than getting the MediaMVP up and running.  An update to that page would be great if you get it going: thanks.
|
|
| Top |
|
|
|
JoJa15
|
Posted: Sun Jan 02, 2005 2:22 pm |
|
|
Joined: Tue Jun 15, 2004 12:57 pm
Posts: 31
|
OK, I have made it a little farther but I am still having problems. I think I have my DHCP server running but I am not 100% sure. If I check my syslog I see the folllowing:
Code: Jan 2 13:08:13 mythtv dhcpd: DHCPDISCOVER from 00:0d:fe:00:10:33 via eth1
Jan 2 13:08:13 mythtv dhcpd: DHCPOFFER on 192.168.0.7 to 00:0d:fe:00:10:33 via
eth1
Jan 2 13:09:34 mythtv dhcpd: 3 bad IP checksums seen in 5 packets
Jan 2 13:10:02 mythtv /USR/SBIN/CRON[17654]: (root) CMD ([ -d /etc/shaper ] &&
/etc/init.d/shaper timecheck)
Jan 2 13:14:25 mythtv dhcpd: 5 bad IP checksums seen in 5 packets
It looks like it is discovering the MediaMVP box and assigning it an IP of 192.168.0.7 but it does not do anything else. On the MediaMVP screen it shows looking for DHCP server and then looking for MediaMVP server. It bounces between those two. Does anyone know what the "Jan 2 13:14:25 mythtv dhcpd: 5 bad IP checksums seen in 5 packets" line means? I also noticed that when I tried to do "ipconfig /renew" on my windows 2000 laptop I got the following message: Code: Windows 2000 IP Configuration
The following error occurred when renewing adapter Local Area Connection 3: DHCP
Server unreachable
I have made sure that my DSL router's DHCP functionality has been turned off and my MythTV Linux box should be the only DHCP server. Here is what my DHCPD.CONFIG file looks like: Code: #ddns-update-style ad-hoc;
allow booting; # This was originally commented out the first time I tried.
allow bootp; # This was originally commented out the first time I tried.
default-lease-time 600;
max-lease-time 7200;
subnet 192.168.0.0 netmask 255.255.255.0
{range 192.168.0.4 192.168.0.255; option routers 192.168.0.1; option domain-name-servers 4.2.2.1, 4.2.2.2;}
host MVP {hardware ethernet 00:0D:FE:00:10:33; filename "dongle.bin.new"; fixed-address 192.168.0.7;}
host mythtv {hardware ethernet 00:09:5B:BE:F3:D4; fixed-address 192.168.0.5;}
host JOHN-LAPTOP {hardware ethernet 00:06:25:AB:ED:D6; fixed-address 192.168.0.6;}
As you can see I have the filename dongle.bin.new specified. Here is what my tftpboot directory looks like: Code: root@mythtv:/tftpboot # ls -l
total 1828
-rw-r--r-- 1 root root 1861152 Jan 2 08:11 dongle.bin.new
-rw-r--r-- 1 root root 207 Jan 2 11:19 dongle.bin.new.config
I used to have dongle.bin in this directory also but I deleted it becuase I thought it was not needed. Here is what my dongle.bin.new.config file looks like: Code: rdate -s mythtv
mkdir /video
/etc/nfsmount.sh 192.168.0.5:/myth/tv/ /video
/bin/echo "Test Log" >/video/test/log
/bin/mvpmc -M -f /etc/helvR10.fnt -s 192.168.0.5 -a 4:3 -m ntsc -r /video >>/video/test.log &
Here is my TFTP boot line in my inetd.conf file: Code: tftp dgram udp wait nobody /usr/sbin/tcpd /usr/sbin/in.tftpd /tftpboot
Here is my hosts.allow file: Code: sshd: ALL
in.tftpd: 192.168.0.0/255.255.255.0
rpc.lockd: 192.168.0.0/255.255.255.0
rquotad: 192.168.0.0/255.255.255.0
rpc.mountd: 192.168.0.0/255.255.255.0
rpc.statd: 192.168.0.0/255.255.255.0
portmap: 192.168.0.0/255.255.255.0
exportfs: 192.168.0.0/255.255.255.0
rpc.nfsd: 192.168.0.0/255.255.255.0
So can anyone help me out here? What is going wrong? Is it my tftpboot server not working? If anyone can give me some pointers from here I would really appreciate it. Thanks, John [/code]
|
|
| Top |
|
|
|
ceenvee703
|
Posted: Sun Jan 02, 2005 4:56 pm |
|
|
Joined: Fri Apr 02, 2004 10:08 am
Posts: 1637
Location:
Virginia, USA
|
|
Not sure why but it doesn't appear that your MediaMVP is attempting the tftp of the dongle.bin file... you're not getting the BOOTREQUESTs.
Is the Windows MediaMVP software still running anywhere on your network?
Double-check your MAC codes? That's all I can suggest right now.
|
|
| Top |
|
|
|
aovermy
|
Posted: Thu Jan 13, 2005 12:27 pm |
|
|
Joined: Sat Apr 17, 2004 10:12 pm
Posts: 128
Location:
Chicago, IL
|
I got this far too, then couldn't get the tftp part to work. Finally decided to just use the mvploader available at
http://www.bluecherry.net/~other/mediamvp/files/
It gets the mediamvp loaded up with the image then I telnet to the mvp and tftp the /etc/dongle.config then execute the dongle.config and it works like a charm.
I've been enjoying using my mediamvp to watch my recordings on my living room TV.
|
|
| Top |
|
|
|
JoJa15
|
Posted: Thu Jan 13, 2005 3:16 pm |
|
|
Joined: Tue Jun 15, 2004 12:57 pm
Posts: 31
|
|
a0vermy, thanks for the info, I will try that out. I need to go back to the store and buy one because I returned it thinking I would not be able to get it work.
How do you like using the MediaMVP to watch recordings? Are there any issues like pauses, stuttering, etc? Are you able to still use the skip forward feature to go forward 30 seconds? Does that work well? Are you running it over a wired network or wireless? If wireless what speed network are you running? Any other issues or caveats that you have experienced.
Ceenvee703, I thought the same thing. I made sure I uninstalled the MediaMVP software on my Windows laptop. I am pretty sure it was not connecting to some windows software because when the windows software was installed the MediaMVP would boot up because it would get the dongle.bin. I am thinking it is related to my setting up of the TFTP server. I think I had all the right settings but how do you tell if your TFTP server is running or not? Is there a way to ping it or see it running in Webmin or some other utility?
Thanks for all the help everyone!
- John
|
|
| Top |
|
|
|
aovermy
|
Posted: Thu Jan 13, 2005 4:25 pm |
|
|
Joined: Sat Apr 17, 2004 10:12 pm
Posts: 128
Location:
Chicago, IL
|
|
I haven't figured the skip back/skip forward yet. I haven't noticed any pauses/stuttering. It's a wired network.
I've got it setup so the mythbox issues the dhcp. I still need the /tftpboot directory which is where I put the software <dongle.bin.mpvmc> and config file<dongle.config> then I call mvploader. After I get the status message that the tftp is done, I telnet to the mvp box and cat /etc/rcS which tells me which tftp instruction to use to get the dongle.config < I fill in the server and filename info because I'm not so sure it has this info available which is why it fails in the first place> then I issue . /etc/dongle.config and all's good. Since I only need to do this when changing the software, it's not so bad. The /etc/rcS can also be tftped over and changed so it will do the dongle.conf ig thing automatically.
After I can telnet into the mediamvp, I'll usually CTRL-C out of the mvploader program since it's just sitting in a spin loop at that point.
Amy
|
|
| Top |
|
|
|
JoJa15
|
Posted: Sun Apr 03, 2005 10:11 pm |
|
|
Joined: Tue Jun 15, 2004 12:57 pm
Posts: 31
|
I think the problem that I was having is with the TFTP server. When I look in webmin it does not show the TFTP server as running. That would explain why the DHCP requests and offer are working but the TFTP portion does not. When I try to run the TFTP server it says the following:
Code: root@mythtv2:/usr/sbin# /etc/init.d/tftpd-hpa restart
tftpd-hpa disabled
Here is what the startup script for TFTP server looks like: Code: #! /bin/sh
#
# skeleton Example initscript
# This file should be used to construct scripts to be
# placed in /etc/init.d.
#
# Author: Miquel van Smoorenburg <miquels@cistron.nl>.
# Ian Murdock <imurdock@gnu.ai.mit.edu>.
#
# Please remove the "Author" lines above and replace them
# with your own name if you copy and modify this script.
#
# Version: @(#)skeleton 2.85-23 28-Jul-2004 miquels@cistron.nl
#
set -e
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
DESC="HPA's tftpd"
NAME=in.tftpd
DAEMON=/usr/sbin/$NAME
PIDFILE=/var/run/$NAME.pid
SCRIPTNAME=/etc/init.d/tftpd-hpa
# Gracefully exit if the package has been removed.
test -x $DAEMON || exit 0
# Read config file if it is present.
if [ -r /etc/default/tftpd-hpa ]
then
. /etc/default/tftpd-hpa
fi
test "$RUN_DAEMON" = "yes" || echo "tftpd-hpa disabled" && exit 0
#
# Function that starts the daemon/service.
#
d_start() {
start-stop-daemon --start --quiet --pidfile $PIDFILE \
--exec $DAEMON -- $OPTIONS
}
#
# Function that stops the daemon/service.
#
d_stop() {
start-stop-daemon --stop --quiet --pidfile $PIDFILE \
--name $NAME
}
#
# Function that sends a SIGHUP to the daemon/service.
#
d_reload() {
start-stop-daemon --stop --quiet --pidfile $PIDFILE \
--name $NAME --signal 1
}
case "$1" in
start)
echo -n "Starting $DESC: $NAME"
d_start
echo "."
;;
stop)
echo -n "Stopping $DESC: $NAME"
d_stop
echo "."
;;
#reload)
#
# If the daemon can reload its configuration without
# restarting (for example, when it is sent a SIGHUP),
# then implement that here.
#
# If the daemon responds to changes in its config file
# directly anyway, make this an "exit 0".
#
# echo -n "Reloading $DESC configuration..."
# d_reload
# echo "done."
#;;
restart|force-reload)
#
# If the "reload" option is implemented, move the "force-reload"
# option to the "reload" entry above. If not, "force-reload" is
# just the same as "restart".
#
echo -n "Restarting $DESC: $NAME"
d_stop
sleep 1
d_start
echo "."
;;
*)
# echo "Usage: $SCRIPTNAME {start|stop|restart|reload|force-reload}" >&2
echo "Usage: $SCRIPTNAME {start|stop|restart|force-reload}" >&2
exit 1
;;
esac
exit 0
Can anyone see anything that is wrong with the above that would prevent the TFTP server from being able to run?
|
|
| Top |
|
|
|
JoJa15
|
Posted: Sat Apr 09, 2005 8:19 pm |
|
|
Joined: Tue Jun 15, 2004 12:57 pm
Posts: 31
|
OK, I got a little farther. First I figured out how to get the TFTP daemon running:
In /etc/default/tftpd-hpa is the following:
Code: #Defaults for tftpd-hpa
RUN_DAEMON="no"
I changed it to: Code: #Defaults for tftpd-hpa
RUN_DAEMON="yes"
I also found out one of my routers had it's DHCP running. As soon as I disabled the routers DHCP I got a little farther but not much farther. Here is my syslog output: Code: Apr 9 21:15:29 mythtv_server dhcpd: DHCPDISCOVER from 00:0d:fe:00:7c:76 via eth0
Apr 9 21:15:29 mythtv_server dhcpd: DHCPOFFER on 192.168.0.40 to 00:0d:fe:00:7c:76 via eth0
Apr 9 21:15:29 mythtv_server in.tftpd[9557]: cannot set groups for user nobody
00:0d:fe:00:7c:76 is the MAC of my MediaMVP. It looks like the DHCP server is offering an IP and the TFP server is trying to serve the dongle file but it is having the error "cannot set groups for user nobody".
I think I need to start the tftp-hpa daemon as root in order to solve this problem. When I look at the process it shows that owner is nobody.
Does anyone know what might be causing this and what I can do to fix it? Can someone help me with how I would start the TFTP-HPA daemon as root so the process would be owned by root?
Thanks,
John
|
|
| Top |
|
|
|
JoJa15
|
Posted: Sat Apr 09, 2005 9:02 pm |
|
|
Joined: Tue Jun 15, 2004 12:57 pm
Posts: 31
|
OK, I finally got it to work on my own! Hopefully this info helps someone else out. I had to use the shotgun approach to get it to work so I am unsure which change actually resulted in it working. Here are my config files though:
/etc/default/tftpd-hpa:
Code: #Defaults for tftpd-hpa
RUN_DAEMON="yes"
OPTIONS="-l -vv -p -u nobody -s /tftpboot"
My TFTP line in /etc/inetd.conf (all on one line): Code: tftp dgram udp wait nobody /usr/sbin/tcpd /usr/sbin/in.tftpd -l -vv -p -u nobody -s /tftpboot
Looking in the running process's I noticed that the tftp daemon is still running as nobody so it did not have to do with running it as root as I thought previously.
Hopefully the above info helps someone else out!
- John
|
|
| Top |
|
|
|
ceenvee703
|
Posted: Thu May 05, 2005 11:16 am |
|
|
Joined: Fri Apr 02, 2004 10:08 am
Posts: 1637
Location:
Virginia, USA
|
JoJa15: hope you see this so I can ask you some questions about your setup.
I'm trying to get the MediaMVP working again, but this time with R5A15. I've been changing the page on the wiki with some notes on differences between R4 and R5 setups. I've also followed your setup for tftpd-hpa script mods and your inetd.conf tftp line.
My DHCP server is now running on my master backend (after realizing that it's now dhcp3-server to start things, and that the config file location has changed as well). However, when I power up my MediaMVP, here's what I get in /var/log/syslog
Code: May 4 19:39:40 mbe inetd[7794]: /usr/sbin/tcpd: exit status 0x47
May 4 19:39:40 mbe in.tftpd[8047]: connect from 192.168.1.40 (192.168.1.40)
May 4 19:39:40 mbe in.tftpd[8047]: cannot bind to local socket: Permission denied
Any ideas? This is with the most recent dongle.bin on sourceforge and my original mvpmc config file in with the dongle in /tftpboot
|
|
| Top |
|
|
|
JoJa15
|
Posted: Thu May 05, 2005 4:04 pm |
|
|
Joined: Tue Jun 15, 2004 12:57 pm
Posts: 31
|
|
That is a hard one. I never encountered a permission denied on a socket bind. Since I am a linux newbie I have no clue where you set permissions for sockets.
If it is any help I am running R5A12. I would be more than willing to print out any config files you want me to as well as what permissions I have set if that will help. Just let me know what you need and how I can get/print them and I will provide the info.
- John
|
|
| Top |
|
|
View unanswered posts
View active topics
Print view
Previous topic Next topic 
LinHES Home
Board index
FAQ
Search
Login 
Register
