I'm running R5A15.1, Nvidia driver 7174, "Automatic" install...hardware is an Athlon 1.2GHz, Hauppauge PVR150 (silver remote), Nvidia FX5200.

Everything works great now, except I'm having trouble getting the nvidia-settings to load a good configuration on startup. I need this, as the saturation settings are too high using SVIDEO out to my TV set.

I can run nvidia-settings as mythtv, but if I try to use the -l or --load-config-only switches, I get errors about connecting to the display, and the settings don't load. I've noticed if I launch it from an xterm console (without the switch) I see the errors, but then the applet window appears, and I can adjust things.

I've tried running it in both console, and from the GUI menu. I've also noticed that if I run it in console as mythtv, change settings, close the program, then reset X windows and load nvidia-settings again, the settings are not loaded in, as if my .nvidia-settings-rc file is not there (it's there though).

Running with the -l switch works as root, but I'm trying to get this to auto run when I boot, and it's mythtv that's initiating the x session, and everyone else that writes a HOWTO seems to be able to load the configuration settings as user mythtv.

Any ideas would be appreciated.

- The exact error messages might help...

- Check the ownership and permissions on nvidia-settings to make sure it's kosher...

- Also check the dot file...

- Also your X authority file...

- You didn't create an extra mythtv user (a common sophmore install error) did you?

My settings were all as you described, and I had not created an extra mythtv user.

The answer lies with GDM setup. I unchecked "Disallow TCP connections to the X server", retarted X and now it loads the configuration fine.

I'm running this on the myth box, not remotely, but I'm just happy it's working.

The question becomes why was it checked in the first place? Is this something you changed, or is it a problem with the install?

BTW - Even on a local box lots of client server applications use TCP connections for the sake of uniformity.

Hmm... I just double checked on my box and is set there (it's actually the equivalent of xhost - preventing remote access).

I suspect that your box has some confusion about what it's IP address really is. Are you using DHCP and has the address changed for some reason?

My IP is set by my broadband router (it's running DHCP, but it gives the same IP to the Myth box everytime based on it's MAC)

Eth0 is down however, I use a wireless connection. Bootup does show that eth0 is trying to get a DHCP response. It fails after so many tries, but then my startup script to bring up wlan0 gives me connectivity. Perhaps this is the reason?

Is it advisable to map eth0 to wlan0? (if so, how do I do this?)

<best Viennese accent>Ah... Multiple IP personality disorder...</best Viennese accent> This is actually a fairly common problem on systems with multiple ethernet interfaces which get different IP addresses.

Fixing it is ... tedious ... and often fiddley. The secret is to declare one of them cannonical and make sure everything references it. This is harder with DHCP because the addresses may be assigned dynamically.

look in your /etc/network/interfaces file and see if you have a line like

auto eth0

if so comment it out and eth0 should stop trying to come up on boot.

if it is more like

auto eth0 wlan0

then just remove eth0 from it. I always put each one on it's own line, but I believe you can have multiple arguments to auto and some scripts use that ability.

_________________
Have a question search the forum and have a look at the KnoppMythWiki.

Xsecrets

I modified my /etc/network/interfaces to be the following:

auto lo wlan0
#auto lo eth0
iface lo inet loopback
#iface eth0 inet dhcp
iface wlan0 inet dhcp

This fixed the "eth0 trying for a DHCP response" thing. wlan0 gets set and all is well. Still, I have to leave that box unchecked in GDM settings regarding "disallow any TCP connections to the X server" otherwise nvidia-settings -l won't work when run under the mythtv account. (I referenced a startup script in the fluxbox apps area)

This might be an interesting exercise to see why everyone else's works with it checked, but I'm not looking further, it works fine for me now.

Thanks for everyone's input btw....this is a great resource.

I had this same problem.

I notice it {.nvidia-settings-rc} was using mythtv:0.0 as the DISPLAY
But while in fluxbox as mythtv the DISPLAY=:0.0 not mythtv:0.0

I removed the mythtv from the file and it worked without errors..

However my problem is it does NOT actually set the settings at all.

Any ideas why?

I have to launch nvidia-settings again select something then I can see
the changes occur. { I am utilizing the tvoverscan and tvflicker features }

BTW: I am using the 7174 drivers. and I assume the same version for
nvidia-settings.

Just to verify, open an xterm window and issue the command (while logged in as mythtv)

nvidia-settings --load-config-only

Does this load your settings in that you created the last time you used the applet? If not, do you get any error messages back?

I may have interpreted your problem wrong, but just in case, know that these settings are not persistent upon reboot. You need to issue this command in a boot script of some sort. Since fluxbox is the default window manager for KnoppMyth, my file ~/.fluxbox/apps has the following entry:

[startup] {~/startup.sh}


and my startup script (~/startup.sh)
-----------------------------------------------------------
#!/bin/bash
nvidia-settings --load-config-only
xvattr -a XV_COLORKEY -v 0 #removes blue lines

HTH

Thanks for the info..

I could run nvidia-settings -load-config-only and nothing would happen.

But, once I enabled TCP connections it works now...

Thanks for the startup I have now entered this on mine as well...
Thanks also for that xvattr line.. I was surfing for how to get rid of
those as well...

Hey linuxgeek:

Let me get this straight-you did an auto install on a box using a retail PVR-150? And your card
worked out of the box, without having to fiddle with ivtv issues and etc? Could you please verify this,
because I've had to go to a lot of trouble to get my PVR-150 working in R5A12. I understood that
R5A15 would not support a PVR-150 out of the box. It would save me
a lot of hassles to do an auto install in future builds.

Thanks

Shplad

_________________
KnoppMyth R5C7
Abit NF7-S
Athlon XP Mobile 2500+
Hauppauge PVR-150 + PVR-150MCE
nVidia Geforce 6600GT
Samsung Spinpoint SATA 120GB
NEC ND-3520A DVD
Seasonic Super Tornado 350
BTC 9019URF Wireless Kbd. w. Joystick

Well I hope I didn't imply that is what I did...

R5A15.1 or below does not support the PVR-150 or PVR-500.
There is no out-of-the box for these yet.

One must use beta release drivers 0.3.2? or higher for this support.

I had to do various changes to get my pvr-500's to work.
pvr-500 = (2) pvr-150's

However, it is rather simple once you know what to do.

I am currently using 0.3.4L of the ivtv drivers.

Be sure that you are using the tveeprom.ko and tuner.ko from ivtv
modules dir. Use modinfo KERNEL MODULE i.e. modinfo tuner.ko

This is where the biggest trouble starts.

On my pvr-500's I had to actually power down once the firmware was
loaded. From then on it has worked.

I hope that helps...

In here I was referring to the nvidia-settings and why it was broke
and what I found to fix it.

Actually I got my PVR150 working "almost" out of the box from R5A15.1 (without installing the newer ivtv). I did an 'automatic' installation, but then modified the ivtv config file. I did have to install a patched lirc to get the remote working. Let me know if you need a link for that howto.

My /etc/mythtv/modules/ivtv file is as follows: