Help setting up EIRI

[rhawk204]

I entered all of the commands that a previous post suggested. After rebooting the wdtv live i tried to telnet to port 14247 so that i can get the codes for one of my other remotes.
I keep getting the following error: telnet: cannot connect to remote host (0.0.55.167): Invalid argument

Can anybody tell me what i need to do to fix this?

Thanks

[KAD]

I suspect your running the normal full version 4.2 fw, I had the same problem until I switched to ext3 boot version

KAD

[rhawk204]

Thanks Kad... i am using 4.2 fw.
Can you explain to me what exactly the ext3 fw is? I am new to all of this and still learning. Do you install it the same way you do the 4.2 fw?

Thanks
Rick

[KAD]

rhawk204,

ext3 boot is a different file system for the firmware,
to boot into ext3 boot system you must first have the full or minimal version flashed (sounds like you've successfuly done this already)
preferably using a fat 32 pendrive place the root.bin file from the following link at the root of the drive
http://forum.wdlxtv.com/viewtopic.php?f=10&t=104
make sure there are no other app.bin files or osd.bin files on the root of the drive
power cycle the live (unplug the power cord and plug it back in)
give it a few minutes to boot, and you will be running on ext3 boot,

KEY- this gives you both read and WRITE access to all system files

my initial problem trying to set up EIRI was that when I create the eiri.conf file via ssh to was not actually saving because I did not have write access since I was not running ext3 boot

once you created the file and saved, only possible on ext3 boot
then run the config_tool

and you should be set to follow the instructions on the other post

KAD

[b-rad.cc]

i use eiri by having /conf/eiri.conf, everything works just fine with flashed fw...although i've never had to use the telnet bit, so can't say about that.

[KAD]

that's interesting, I wonder why I couldn't get it to work without running ext3 boot
I did try flashed fw with a eiri.conf on root at boot, but didn't work, I wonder if something else then was preventing proper execution
the telnet bit was essential though, as that's how I got the proper IR codes to enter in eiri.conf
well, like I said it works great running ext3 boot, but maybe I need to take a closer look

KAD

[rhawk204]

i guess that i am doing something wrong even though your instructions look pretty simple.
I downloaded that file and unzipped everything to my pen drive. I plugged in the pendrive and the wdtv said that it had a new fw and i allowed it to install.
When i rebooted it said that the box was using ext3. after complete boot was finished it said that i had new firmware do i want to update it. the control would not let me select cancel or ok so i just let it sit. I then went to my pc and tried to telnet again but got the same error.
after i got the error i still tried one of my remotes and no codes showed up on the telnet screen.

[b-rad.cc]

if you are have already flashed to wdlxtv-live then there is no reason to keep the wdtvlive.* files around, delete them and it will stop asking you if you want to upgrade. If it says you're running ext3-boot-live then you're running it

[rhawk204]

i check and it does say that i am running ext3-boot-live. I still cannot telnet to 14247 but i tried pushing a button on a remote but did not get a code. The remote i using is a Bose model. Could that be the problem. Maybe the box does not "see" the bose remote.

[KAD]

you shouldn't need to flash using the ext3 but it sounds like you confirmed it did boot into ext3, when I did this I had to re-do the first steps of creating eiri.conf via telnet,
and entering everything in nano, to make sure it was actually saving correctly, it's when eiri.conf is correctly saved and then you run eiri that the port was opened up for access,
basically, now that you're running ext3 you need to follow all of the instructions in the other post

although based on b-rad's reply, there may be something else going on, I had exactly the same error you have, not able to telnet to port 14247 and I solved it by running ext3.

I may play with this some more to see what's going on, but of coarse my daughters watching a movie now. at least I was smart enough to keep my ir codes I got from port 14247 so I don't have to start completely over to test things out

KAD

edit: a couple of other notes
jamiroo mentioned once that he could not get this to work using putty, don't know why and I didn't try in putty
to telnet to port telnet <wdtvlive-IP-address> 14247
and config to is config_tool -c eiri=ON
and apartently there are some remotes this does not work with, but regardless you should still be able to access the port, not all button work on my remote with this, but enough that it's very useful