HR10-250 no ip address assigned

[energy2spare]

I just upgraded my HR10-250 using InstantCake 6.3c and PTVnetHD which I just downloaded a couple of days ago. I have an HDVR2 using the Netgear FA120 that works with no issues. I've tried using that same Netgear FA120 on the HR10-250 but the HR10-250 will not grab an address. I see a link light on the FA120 as well as my switch but no address is registered to the tivo. I also tried scanning my entire network for open ports but couldn't find it.

During the PTVNet installation, it did not ask me any questions about networking such as drivers....it only asked if I wanted to enable FTP/TELNET, etc. I assume that's the way it's supposed to work? I've tried the installation 3 times and am getting the same results. Thoughts?

Is there any way to get console access to the Tivo?

[geordi]

I have the same setup, hardware and software, and haven't had any problems with getting network detection. If you have a link light, then the FA120 *should* be working on the Tivo side, you should log into the router directly and look at the dhcp logs. The Tivo won't have a computer name listed, just a very long number that IIRC is not the mac address. It might be the RID number, I don't know. But it will be in the "computer name" field, so you can find it. If there isn't anything there, you might want to pull the drives and try the upgrade again. There software is pretty seamless for installing, I didn't have to customize much of anything other than some personal touches in the rc.sysinit.author after it was all said and done. You might have just had a glitchy install.

[geordi]

Wait a second, I just noticed you said "saw a link light on my *SWITCH*"

You DO have a ROUTER with a dhcp server in it, right? This will show a link light just b/c there is tcp/ip data flowing and the cable is good, but if all you have is a SWITCH, then the tivo will NEVER get an IP b/c there isn't anything there to provide that address.

Go get yourself a cheap Linksys router and use that, if you don't have one already. Then log into it directly using your computer's web browser, and you can see the log to find the address for the tivo. You can also specify a static address to always give the tivo from the router, so the Tivo can stay as a dhcp device, and you can easily find it on the network.

[energy2spare]

I have a switch where my PC, laptop and Tivo connect to which has an uplink to my router which is also my DHCP server. My laptop and PC grab an ip just fine so it's not a switch/router issue. The DHCP log shows no entry other than my standard devices. It seems to me that the TIVO is not grabbing an address. During the install process, is there anyway to set a static ip address?

[Jamie]

I have a switch where my PC, laptop and Tivo connect to which has an uplink to my router which is also my DHCP server. My laptop and PC grab an ip just fine so it's not a switch/router issue. The DHCP log shows no entry other than my standard devices. It seems to me that the TIVO is not grabbing an address. During the install process, is there anyway to set a static ip address?As always, for support of DVRupgrade products, you should probably talk to them. They have their own support forums: link (http://www.dvrplayground.com/forum/topic/22/DVRupgrade-Official-Support-Area/).

There are known issues with the 3.1.5 kernel and dhcp on 6.3x. See link (http://www.dealdatabase.com/forum/showthread.php?t=51032).

[energy2spare]

Problem solved. Swapped out the Netgear FA120 for an Airlink 101 and it fired right up. Plugged the FA120 back in, no dice. Plugged the FA120 back into the HDVR2 and it worked fine.

BTW, picked up the Airlink for $15 at Fry's :)

[geordi]

Gee, it's so great to see people offering the ultimate in customer service replies: "We offer support, but you would be better off talking to another forum b/c we choose not to help you"

So caring. :(

Oh, and those "well known problems" have been fixed. IIRC, it was a command conflict, I think it involved trying to load specific drivers using insmod while the new 6.3x is loading general drivers that support most of the common adapters. The overlapping drivers didn't play nice.


Energy2Spare.. I covet your access to Frys. There aren't any of those toy stores here on the East Coast... /me sad about that. Good work on getting it to work. I don't know why it wouldn't work on yours, but my FA120 is just fine on my Tivo. *shrug* At least the problem is solved.

[Jamie]

Gee, it's so great to see people offering the ultimate in customer service replies: "We offer support, but you would be better off talking to another forum b/c we choose not to help you"

So caring. :(The issue is that PTVNet is a product most people here don't use and know little about. If the problem is specific to PTVNet, your best bet is to consult the seller of the product. If it is a generic issue, then there are probably people with greater expertice here (no offense intended to DVRPlayground).


Oh, and those "well known problems" have been fixed. IIRC, it was a command conflict, I think it involved trying to load specific drivers using insmod while the new 6.3x is loading general drivers that support most of the common adapters. The overlapping drivers didn't play nice.Nope. The 3.1.5 kernel does not include the af_packet code needed for dhcp. The solution is to either use the 7.2.2-oth.K1 kernel, or to find and load the af_packet.o module. 6.3 includes af_packet in the kernel, so you won't find a af_packet.o module there, but the older releases had it as a module. This is covered in Cheer's thread I linked to.

I'm guessing that PTVNetHD is using the 7.2.2-oth.K1 kernel now, but I don't know for sure, since I don't have or use PTVNet/PTVNetHD.

Energy2Spare.. I covet your access to Frys. There aren't any of those toy stores here on the East Coast... /me sad about that. Good work on getting it to work. I don't know why it wouldn't work on yours, but my FA120 is just fine on my Tivo. *shrug* At least the problem is solved.The tivo software stores separate net configuration data in MFS for each device, addressed by MAC. I'm not sure how PTVNet sets up the MFS data, but my guess is that the MFS data for the airlink 101 is setup for dhcp, but the MFS data for the FA120 is not for some reason. If you apply the HME patch so you can get access to the network configuration screens, you can probably fix this easily there.

[PlainBill]

The tivo software stores separate net configuration data in MFS for each device, addressed by MAC. I'm not sure how PTVNet sets up the MFS data, but my guess is that the MFS data for the airlink 101 is setup for dhcp, but the MFS data for the FA120 is not for some reason. If you apply the HME patch so you can get access to the network configuration screens, you can probably fix this easily there.
To continue repeating what should be obvious, this illustrates why PTVnet doesn't get much support here. The standard Tivo configuration works and is well understood. The PTVnet kludge has issues. Why spend time supporting an inferior product when an easier, cheaper, better way is available?

PlainBill

[geordi]

Ok, maybe they are using the new kernel on the instantcake, I don't know.

But my background is I killHD'd my original drive image when it was 3.1.5f, and had the network static with this FA120 and all was well.

Now, b/c my slice upgrade to 6.3 stopped at 6.3b... and there are all sorts of issues I was having, I upgraded to 6.3c using cake and ptvnet. I wiped the drive out, and then did some investigating on how they have stuff organized. The code is basically the same as what we do manually here, just in a different location. Also Cake doesn't apply some of the path and busybox stuff that I would like, so I had to change those. But their network connections were seamless, my FA120 fired right up with no changes.

The thing to remember is that while it is a "product" of sorts, what they are really "developing" are the install scripts. The on-tivo files and scripts are the same as what we are doing here. So unless the install is buggered, the info here usually will be helpful.

And yea, DVRplayground has a LOT less information for advanced work in the code than is available here .

[geordi]

Bill, sometimes you dont have a choice. While "easier, cheaper better" is usually the desirable way... Sometimes you don't have a choice. If you need the file image and can't get it any other way... PTV is available.

I was in that situation. I wasn't happy about it.

[PlainBill]

Bill, sometimes you dont have a choice. While "easier, cheaper better" is usually the desirable way... Sometimes you don't have a choice. If you need the file image and can't get it any other way... PTV is available.

I was in that situation. I wasn't happy about it.

You're half right. If you need an image, InstantCake is a quick (good) solution.

There is absolutely no excuse except laziness or low IQ to use PTVnet. For most adapters, simply adding iptables -F early in rc.sysinit.author will accomplish everything it does. For those adapters not supported by the stock drivers, Jamie's backported drivers work.

<EDIT> OK, I overstated the simplicity. You must also replace the stock kernel with a killhdinitrd one, install Series 2 utilities, and create /etc/rc.d/rc.sysinit.author. Cheer's roadmap (http://www.dealdatabase.com/forum/showthread.php?t=43599) has the details.</EDIT>

PlainBill

[geordi]

Count me usually in the lazy (or efficient, depending on your point of view) column, but in this instance, I didn't have much time to screw around with the rebuild. While I have multiple Tivos and a stand alone receiver... Only the Tivo is currently available for me to watch tv.