LinHES Forums
http://forums.linhes.org/

System broken by install-nvidia.sh
http://forums.linhes.org/viewtopic.php?f=1&t=1345		 Page 1 of 2
Author:  theslarty [ Sat May 01, 2004 1:17 pm ]
Post subject:  System broken by install-nvidia.sh
So here's my story...

I installed R4V3, did some twiddling and got it working perfectly on my CRT. To complete the installation I wanted to get it all working via TV-out (I've got a ChainTech Summit 7NIF2 w/ the built-in GeForce 4 MX, same as half the other people around here). I found a thread that said to install the nvidia graphics driver using install-nvidia.sh, so I gave that a shot.

First, X broke and won't come up anymore, but I think I can deal with that. The worst part is that the system seems to randomly hang now with blinking keyboard led's, and I'm at a loss to deal with that one.

Am I correct in assuming all this is a problem with the nvidia driver? Any way to uninstall that, or do I have to redo the entire Myth installation from scratch? Is the driver necessary for good performance and TV-out and overscan?

Thanks for any help...
Author:  cesman [ Sat May 01, 2004 1:49 pm ]
Post subject:  Re: System broken by install-nvidia.sh
theslarty wrote:
Am I correct in assuming all this is a problem with the nvidia driver? Any way to uninstall that, or do I have to redo the entire Myth installation from scratch? Is the driver necessary for good performance and TV-out and overscan?

Thanks for any help...
It is possible. You can try a newer version of the nVidia drivers but just don't have overscan.
Author:  Xsecrets [ Sat May 01, 2004 5:41 pm ]
Post subject: 
are you still trying to view on a crt, or have you switched to a tv? if you just have tv then you must edit the /etc/XF86Config-4 file with acceptable refresh rates. otherwise you can't see anything. I found this out the hard way you have to edit the file before running the install-nvidia.sh script or you are left in the dark, well me at least since I don't have crt in the living room.
Author:  khrusher [ Sat May 01, 2004 6:23 pm ]
Post subject: 
Hum....
Quote:
hang now with blinking keyboard led's

sounds familiar
Author:  Quigs [ Sun May 02, 2004 6:55 am ]
Post subject: 
theslarty:

I had the same issue when upgrading to to R4V3. There seems to be an issue with the nvidia drivers and this setup (my guess is the kernel). I tried just about everything to get it to work. I could get the system up without any nvidia settings in the XFConfig86-4 file. But once I set overscan or anything else, X would not start. In the end, overscan is important to me, so I reverted back to installing R4V2.

I also could not get R4V3 to accept my bttv settings (tuner type=2). If I set those, X would not start. That would require me to re-install the nvidia drivers to get the system to boot X. Strange stuff.

Funny you mentioned the keyboard lights flashing - I saw that while trying to figure things out and thought it was a fluke.

Good luck.
Author:  theslarty [ Mon May 03, 2004 4:10 pm ]
Post subject: 
Thanks, glad to know I'm not the only one who's had the problem. I switched to R4V3 mainly because the kernel doesn't have APIC (I'm one of the people bitten by the nForce2/APIC thing where the machine hard-locks every few minutes for no apparent reason). I guess I could switch back to R4V2 and try that new kernel that somebody posted a few weeks ago, but wouldn't that be basically the same thing in the end?

Anyway, yes, it was running perfectly on a CRT... it was only when I attempted to bring it into my living room and get it working on my TV-out that I tried to run install-nvidia.sh at all, which I think caused the problem.

So I guess, now the question is... is this worth it at all? If the nvidia drivers are going to be that much hassle, and the newer ones don't even have overscan, would I be better off just spending (even more) money and getting a scan converter or something? How does the quality on those things compare to TV-out?

(BTW... according to people who know more than me, the blinking keyboard LED's indicate a kernel panic or a kernel oops or some such thing. It's a Bad Thing, anyway.)

I'm gonna get this stupid box working yet, I swear! :-)
Author:  Xsecrets [ Mon May 03, 2004 4:30 pm ]
Post subject: 
well if you were having the problem that I did it has nothing to do with the kerenel, and just that the XF86XConfig-4 file has refresh rates your tv can't handle in it. You have to change those first or you won't be able to see anything. As for the scan converters I've never used one before, and the quality will depend on which one you are getting. If you are talking about an actual scan converter then the quality will depend on the device, if you are talking about a RGB to component converter then the quality should be much better than any tvout could produce.
Author:  Quigs [ Mon May 03, 2004 7:59 pm ]
Post subject: 
I don't have the APIC issues some have. I have the ASUS A7N8X Nforce2 board and it works flawless with R4V2. I wanted to go up to the new kernel to get the V4l2 drivers. I use a software encoder that has bright whites - I am told the V4l2 drivers will fix that.

XSecrets - Well, it is not the refresh rates. I know those are correct. The same XF86Config file works with R4V2 perfectly hooked to a TV. If you do a search on the nvidia board for "Screens found but none have a usable configuration" there are a TON of posts talking about the issue. Some people solve it by doing a modprobe then starting X. Some do a insmod nvidia. Some set BIOS settings - VGA assigned to an IRQ and disabled the Plug and Play bios. One of those might work - didn't for me.

As for the other kernel posted earlier - has the EXACT same issue. I have my system set up in dual boot mode to try the other kernel out. There is definitly something funky going on between the driver, the Kernel, and possibly the bttv settings. I have issues with them all with that kernel. Next attempt will be to compile a kernel and the nvidia driver locally. Maybe that will work.

Hopefully this is solveable - I would hate to be stuck on this kernel.
Author:  mgordon [ Tue May 04, 2004 6:53 am ]
Post subject: 
I just upgraded from R4V2 to R4V3 last night.

The uprgade went smoothly but I haven't installed the nvidia drivers yet.

Has anyone had success with the nvidia drivers and R4V3?

Thanks,
Mike G.
Author:  mgordon [ Tue May 04, 2004 7:08 am ]
Post subject: 
As part of the beta testing was the install of nvidia drivers tested?

I have been very satisifed with my R4V2 myth setup and upgraded to R4V3 to take advantage of the APIC disabled.

I am asking these questions to understand my options.

Thanks,
Mike G.
Author:  tjc [ Tue May 04, 2004 7:46 am ]
Post subject: 
I've had success installing the nvidia drivers and TV out under R4V3. I'm not entirely happy with the quality (over saturated colors) but it works as well as I ever saw it working under R4V2.

On the other hand I and several other people have reported dependency problems installing xine-ui to get DVD menus.

If you've got R4V2 working and stable, upgrading doesn't buy you much and may lose you some. Frankly I found an upgraded BIOS and some revised BIOS settings were what really made my system stable.
Author:  Xsecrets [ Tue May 04, 2004 9:16 am ]
Post subject: 
Yes I tested the nvidia install in the beta of R4V3 and it worked flawlessly. Then agian I have never had any problems with the nvidia drivers, but I haven't ever tried twinview either, and I always use the connectedmonitor tv and tvoutput svideo or whatever the exact options are, and I always use vert refresh 60 horz refresh 30-50. Since knoppmyth V3 I have been using these settings and I have never even pluged up a monitor to do my inatalls, maybe that's the difference.
Author:  Quigs [ Wed May 05, 2004 8:34 am ]
Post subject: 
Small update: I can now get X to load and MythTV to come up using the 2.4.25 kernel supplied by Chad. I am sure this is the same one that the new R4V3 is using except for some modules. To get this to work I had to compile the Nvidia drivers using the new kernel. There is an option in the nvidia install were you can add a command line path to the kernel source. After doing this, everything succesfully booted correctly.

The only issue I have now is the when I go to view TV I get a blank screen. I do know that my TV card is being set to the wrong tuner - tuner type=5. My settings are correct in the BTTV file - as R4V2 correctly sets the tuner and card type. For some reason this new kernel and possibly the new bttv drivers are not taking the setting. Maybe there are some other settings that have changed for the new bttv in this kernel that I do not have correct. My bttv settings are:

/etc/mythtv/modules/bttv

alias char-major-81 videodev
alias char-major-81-0 bttv
options bttv card=34 radio=1
options tuner debug=1 type=2

I also tried adding this to the modules.conf file with no luck.
Author:  mgordon [ Wed May 05, 2004 7:23 pm ]
Post subject: 
Quigs,

I sucessfully upgrade from R4V2 -> R4V3 as advertised but I am having a similiar problem with my tv tuner. My tuner type is setup incorrectly to 5. I have a Leadtek Winfast2000

In R4V2 I corrected the problem in the following manner:
echo "options bttv card=34 radio=1 gbuffers=8" > /etc/modutils/User
echo "options tuner type=2" >> /etc/modutils/User

This modification no longer works in R4V3.
Something must have changed with the V4L2.

Mike G.
Author:  mgordon [ Wed May 05, 2004 8:45 pm ]
Post subject: 
Quigs,

Make sure that your bttv options are as follows.

options bttv card=34 radio=1 gbuffers=8 tuner=2

The card is dependant on your TV tuner card.

The above line worked for me.
Good Luck,
Mike G.
Page 1 of 2 All times are UTC - 6 hours
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/