On Sat, Dec 5, 2009 at 5:53 PM, MVallevand <[email protected]> wrote:

> The Hauppauge and Sage software does update flash with the IP address
> of the Hauppauge/Sage servers.  I wrote a small utility that is part
> of the mvpmc binary called vpdread that extracts this to help when
> DHCP isn't set up properly.  On the older D3A it will try to use bootp
> from them if DHCP is configured incorrectly and I think this is the
> problem, it is very unlikely that it is bricked.
>
> Martin
>

*Well, this sounds promising*. The device does request an IP address, so
that might indicate that it is not bricked.

Maybe I am being dense, but what is the next suggested step?

Here is the last dhcp config file I tried:

m...@mymythbe:/etc/dhcp3$ cat dhcpd.conf
#
# Sample configuration file for ISC dhcpd for Debian
#
# Attention: If /etc/ltsp/dhcpd.conf exists, that will be used as
# configuration file instead of this file.
#
# $Id: dhcpd.conf,v 1.1.1.1 2002/05/21 00:07:44 peloy Exp $
#

# The ddns-updates-style parameter controls whether or not the server will
# attempt to do a DNS update when a lease is confirmed. We default to the
# behavior of the version 2 packages ('none', since DHCP v2 didn't
# have support for DDNS.)
ddns-update-style none;

# option definitions common to all supported networks...
option domain-name "local";
option domain-name-servers xxx.xxx.74.12, xxx.xxx.14.23;

default-lease-time 600;
max-lease-time 600;

allow bootp;
allow booting;

# If this DHCP server is the official DHCP server for the
local
# network, the authoritative directive should be
uncommented.
authoritative;


# 2009.12.05 DS from
http://www.basicconfig.com/linuxnetwork/configure_dhcp_server_ubuntu

subnet 192.168.2.0 netmask 255.255.255.0
{
    #option broadcast-address 192.168.2.255;
    option routers 192.168.2.251; #my Netgear
router
    range 192.168.2.200 192.168.2.220; # No comma, just
whitespace
}


group {
  next-server 192.168.2.107; # IP address of your TFTP server
    host mvpmcRevD
    {
         # NOTE: Change the hardware ethernet to the MAC address of your
actual
MVP

        hardware ethernet
00:0d:fe:00:xx:xx;
        fixed-address
192.168.2.200;
        filename
"mvp.bin";
        option root-path
"/home/me,rsize=4096,wsize=4096,nolock";


}
}


# Use this to send dhcp log messages to a different log file (you also
# have to hack syslog.conf to complete the redirection).
log-facility local7;

m...@mymythbe:/etc/dhcp3$
------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing. 
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Mvpmc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mvpmc-users
mvpmc wiki: http://mvpmc.wikispaces.com/

Reply via email to