I don't know how much help this will give: http://www.linuxquestions.org/questi...un-4175582468/ being that it's a Mint install but a .run is easily: http://askubuntu.com/questions/18747...tall-run-files

have fun at work...

1 members found this post helpful.

Ok, but this happens after I install sax or salix right? Or can I do this from the live cd? Right now the issue I'm stuck on with salix is I need a password to do anything, and I never made one and don't have one, nor does the website mention a default one or anything.

In Salix you probably need to run:or they have a preset "root" (to change) and maybe a "user?" Here's their startup guide: https://www.salixos.org/guide.html tho the Wiki or Forum may have more about running live?

Add: The average live system will wipe out all changes after a reboot.

1 members found this post helpful.

Ok I'm back at it, I tried an Ubuntu legacy driver that showed up in the list of found alternative drivers, it seems to at least keep the system stable until I run flash or resize windows, the resize windows is a known bug with future NVIDIA updates though. -One thing I did notice is NVIDIA website recommends a 2013 driver, not the newest which I was trying to use with the alternative driver finder in Ubuntu. Downloading that and i followed instructions to allow it to run as a program, I double clocked it and it opened in a text editor and has a loading bar at the top so I'm assuming its installing? Taking an awfully long time to install for a 50mb file, unless its downloading or something.-

Never mind, I somehow selected the 32 bit version instead of 64... back to square one here cause the recommended one from NVIDIA is the same offered on additional drivers of software and updates that results in all the issues =/

Yea, installed the newest NVIDIA driver, instead of rebooting I tested a flash video, was working flawlessly (after I installed hal) and went to reboot, clicked search and the system crashed QQ looked like display issue cause it went all blocky and garbled and then I'm sitting here looking at a grey screen.

Ok thanks, this is my next step i believe, just to confirm you're saying all I have to do is open a console and type passwd ? And yea I read the startup guide, doesn't say anything about a password or anything so idk. Is there like a universal password already installed? I mean like I tried "Su" in Ubuntu and my regular password (the only one I remember creating with Linux) didn't work. To reiterate, this is literally the first time I've worked with Linux, so anything Linux specific I have no idea about.

Sorry for not consolidating posts here but I just was looking at this;

Usually the procedure is straightforward:

1) download the driver according to your graphic card on the nvidia site:

http://www.nvidia.com/Download/index.aspx?lang=en-us

(You get the graphic card specification with the command lspci)

2) make the file executable

3) get out of the x environment using the command: init 3

* 4) login: root, password:toor, get in the directory of the nvidia_etc.run program. Issue the command: ./ *.run

5) agree with most questions, except the proposition to get the update from the net. Accept to function with another gcc compiler version. Accept the change of the nvidia-xconf file (I hope you will get the version of the program where you toggle between choices with the arrow keys, if you have to right down the answer letter by letter like in Accept, it looks bad usually)

6) Once out of the program installation use command: startx

7) the nvidia x server setting program should be under the settings or system categorie in the kde menu.

I do not know the if the problem as been fixed with the new version of slax 6.1.1.

If no one else answers, I will try 6.1.1 this coming weekend, and report back to you. If in a hurry download slax 6.0.7, just google download slax 6.0.7 or:

http://filespump.com/download_file.php?qq=slax%206&file=5288032&desc=slax-6.0.7.tar"

Now is #4 what I'm experiencing here? Should I be logging in as "root" with password "toor" when trying to install from the live cd? If so why in the world would that not be in the setup instructions? Is that just common knowledge everyone should know?

Looks like you're doing okay to me (nvidia can be a pain and may need some distro hopping*) but Salixos as you originally posted is different than Slax...

Yea I know they just seem related and salixos says its compatible or w.e, I'm still not able to actually install salixos, theres an executable file that says "salix-live installation" that when I open asks for a password for "one" I tried changing it but I need an old password to do that... maybe I downloaded the wrong version to install it? I'm gonna go try a different version of salix I guess.

Wait so am I right in assuming the live version can not be installed to a hard drive? I thought it could? What is the point of including a live install file on the desktop of the live cd if you can't install it? Also, is the "root user" something that's on a live cd or is it part of your Linux partition? In other words, if I go try another live cd, will the root user be different? Just trying to understand what exactly a root user is.

As long as you have good backups and don't mess with the factory repair partition (if one or delete m$ if you need them,) I suggest trying to install the drivers in a number of the top distros installed until one hits home...

Yea that's already gone I think, what happened was I installed windows 10 technical preview then dropped behind on the updates, and when I recently went to boot up, it updated then i got an error telling me my operating system had expired, right after the post, didn't even load windows or anything. So now I don't even have a win 10 key for it that I know of. I'd like windows 10 on it, but theres no way I'm going to spend the $100 and the alternatives are... shady.

Oh also, to be clear, this wasn't an OEM machine or anything, just a pc I built from stuff I ordered. I think I had xp on it before, might even go searching for my xp key again idk, for now gonna keep trying different distros as you suggest

Couldn't agree more!

If you have a boot CD somewhere that includes Memtest86, I'd boot into that and run the memory tests to see if shows anything that might be wrong with the memory.

I had a system that was of a similar vintage that began behaving weirdly and freezing at odd times. Memtest86 showed that memory test were failing but in different locations each time I ran the test.

What I eventually was able to determine was that I had a few bad capacitors on the motherboard. In the end I declared that it was a goner and -- after a brief, tasteful service -- it was pulled from the case and I bought and installed a replacement. Do a close visual inspection of the capacitors on the motherboard. If you see any whose metal tops aren't perfectly flat but seem to be bulging, you're liekly to be in the market for a new motherboard. And probably new memory as well. Anything you have plugged into PCI slots should be transferable onto the new M'board provided it has enough slots.

Hope this isn't the case but a system that old may be on it last legs. All because of a few poorly sourced components. If you find you need a new board, look for one that doesn't use the old-style, can-type electrolytic capacitors.

Good luck.

1 members found this post helpful.

Look around the bios on that mobo for potential incompatabilities.