[mythtv-users] IP address

[R. G. Newbury]

Damian Surr wrote:
> I had a major breakthrough with MythTV this morning. Things started 
> actually working.
> 
> Being an over excited newbie fool who wants to get his system 'just 
> right', I thought. "I know, I'll change all of those settings that I was 
> frantically changing to try to get things working back to what they 
> should be". What happened? You guessed it, I broke it!
> 
> At one point of trying to fix old problems, I changed all of the 
> '127.0.0.1's that I could find to '192.168.0.2's. I've heard different 
> views on this though and being unsure as to if I did the right thing or 
> not, I tried to change them all back. Since then, I can't get into 
> anything :-)
> 
> Mythfrontend comes out with:
> 
> 2007-02-05 14:07:08.087 Connected to database 'mythconverg' at host:
> localhost
> SIP listening on IP Address 192.168.0.2:5060 NAT address 192.168.0.2
> SIP: Cannot register; proxy, username or password not set
> 
> 
> and mythtv-setup goes blue, but then crashes out with:
> X Error: BadDevice, invalid or uninitialized input device 169
>   Major opcode:  148
>   Minor opcode:  3
>   Resource id:  0x0
> Failed to open device
> X Error: BadDevice, invalid or uninitialized input device 169
>   Major opcode:  148
>   Minor opcode:  3
>   Resource id:  0x0
> Failed to open device
> 2007-02-05 14:12:31.618 Using runtime prefix = /usr
> 2007-02-05 14:12:31.659 Gnome-Screensaver support enabled
> 2007-02-05 14:12:31.660 DPMS is active.
> 2007-02-05 14:12:31.749 New DB connection, total: 1
> 2007-02-05 14:12:31.786 Connected to database 'mythconverg' at host:
> localhost
> 2007-02-05 14:12:31.791 Total desktop dim: 1024x768, with 1 screen[s].
> 2007-02-05 14:12:31.803 Using screen 0, 1024x768 at 0,0
> 2007-02-05 14:12:32.004 Current Schema Version: 1160
> 2007-02-05 14:12:32.047 Total desktop dim: 1024x768, with 1 screen[s].
> 2007-02-05 14:12:32.050 Using screen 0, 1024x768 at 0,0
> 2007-02-05 14:12:32.054 Switching to square mode (blue)
> 2007-02-05 14:12:32.119 Using the OpenGL painter
> mythtv: could not connect to socket
> mythtv: No such file or directory
> lirc_init failed for mythtv, see preceding messages
> 2007-02-05 14:12:34.248 Joystick disabled.
> 2007-02-05 14:12:34.463 Loading from:
> /usr/share/mythtv/themes/default/base.xml
> 2007-02-05 14:12:41.869 Using NV NPOT texture extension
> Aborted (core dumped)
> 
> 
> I also turned on OpenGL display somewhere in myth this morning, so I've 
> wondered if that may be part of the reason that I can't get into 
> mythtv-setup, but it was working fine earlier so I don't think that 
> should be causing a problem.
> 
> Any idea how to fix my over enthusiastic adjustments?
> Should the IP be 192.168.0.2 if I may want to use a different computer 
> as a front end in the future? I may or may not. That's a little way down 
> the line yet.

It appears that you now have mysql running correctly. It also appears 
that you have messed up your mythtv install. The frontend is talking to 
localhost (127.0.0.1) but your mythphone setup wants to talk to 192.168.0.2.

Actually the best thing you could do would be to drop the mythconverg 
database, and start again, running the mc,sql script, and then 
mythtv-setup, this time just leaving things as 127.0.01.

#mysql -u root -p < mc.sql:
 >quit
# mythtv-setup

It is not a trivial matter to change everything back once you have left 
the wrong entries in various places in the database. None of this 
affects the installed code base. You do not need to make any changes to it.

The Bad Device reports are fatal: you have to FIX THIS FIRST.

  X Error: BadDevice, invalid or uninitialized input device 169
 >   Major opcode:  148
 >   Minor opcode:  3
 >   Resource id:  0x0
 > Failed to open device
 > X Error: BadDevice, invalid or uninitialized input device 169
 >   Major opcode:  148
 >   Minor opcode:  3
 >   Resource id:  0x0
 > Failed to open device

I would guess that you are trying to initialize your tuner hardware 
without having loaded the proper firmware. You probably have a line in 
modprobe.conf to load a driver module, but that process is failing.

Try running   'dmesg | more' and reading what it reports as it tries to 
start the system.

Geoff