[mythtv-users] IP address

[Damian Surr]

> 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.
>   
I think I've fixed it. Everything seems to be ok now. I've changed 
everything to the 192.168 ... address and temporarily turned off OpenGL 
in the Myth settings and things are working beautifully. I can watch TV, 
make scheduled recordings and everything. I'm so happy :-)
> 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
>   
That was part of what I did along the way. I did lots of thing along the 
way, but I'm now getting a better feel for the right and the wrong 
things to be doing and how to do them.
> 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.
>   
I think I've got things back to a fairly good place.
> 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
>   
Yes, these are the only comments still concerning me. I've been ignoring 
them since things started to work anyway, but you're comments have shown 
me that I need to take a second look.
> 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.
>   
Right, I'm out of my depth again here. I'll have a look at that file 
when I can and see if I can work out what's going on.
> Try running   'dmesg | more' and reading what it reports as it tries to 
> start the system.
>   
Will do, thanks Geoff

Damian