Ok, here is what I tried...
But I still get the error. I am guessing there is some source or headers it needs that it can't find? LOL, but *I* don't know what its looking for!!!

Thanks for any ideas? I tried looking for anyone with debian or mepis with this that got it fixed, but didn't find any posted. Maybe I just wasn't searching correctly...


This page might have the cause/answer, but its beyond me to know what to do with it to implement because the directory structure appears different here and I don't know what I'm looking for


========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://weltall.heliohost.org/wordpress/2012/01/20/linux-kernel-3-3-rc1-and-nvidia-drivers/"
linktext was:"http://weltall.heliohost.org/wordpress/ ... a-drivers/"
====================================


I pasted in the most relevant looking stuff below

I think you missed the 2 scripts on offer on that page, they look like they will do the necessary for you.

Ok, I ran the sed to fix the conftest.sh and then tried the nvidia-installer, but got the same error.

So then I tried the sgfxi -! 6 again, but it reextracted the package, overwriting the conftest.sh again, and therefore also failing again.

If I run the script given, do I need to pass the nvidia-installer any parameters?

Is there a way to get sgfxi not to reextract so that the fixed conftest.sh gets left there to be used?

I wish I could be more helpful in identifying the problem, but I can't even read the scripts well enough to really know what they are trying to do, and have very little experience compiling C or C++ programs.

I'm hoping someone can suggest something. I did find a message from someone on that page that had debian that was successful using the sed method. I looked at the kernel versions available, and noticed that the ones with 3.5 or lower were not antiX, so would guess they wouldn't be a good idea.

I figured I was completely done for at this point anyway, so I tried loading an older, non-antix kernel Linux-3.2.0-4-486 and headers via synaptic, then went to term under root and did a update-grub, and rebooted, and ran sgfxi, and then started X, and it came up 1600x1200 and is working, thus far.

I'm not sure why the newer kernels don't work, but recall reading that they don't above 3.5, so that's why I tried the 3.2.0-4. I did lose SOME memory compared to the antiX I was running, now up to 32% with nothing running, but thats still a lot better than any of the other distros, and it seems to be running fine.

I still have to get my soundcard and wifi working, but getting the screen working right was top priority.

Thanks for all the help.

thriftee wrote:...I tried loading an older, non-antix kernel Linux-3.2.0-4-486...

Good to hear you got a working solution. I came to post the same method to find you had had also found it.

I managed to locate a system that uses a GeForce2 card. It's not exactly the same but close enough to illustrate the case. After creating a virgin installation of 13.2-Stable, then installing the alternative Debian kernel (linux-image-486), and subsequently installing the video driver via sgfxi, it works as shown below. I wonder if there might be any value in having an antiX kernel in the antiX repo specifically to handle cases such as this? It might be beneficial to have an in-house solution that fits with one of the prime antiX goals of extending the life of otherwise redundant kit.

Sam,

I do appreciate you and the others helping, as without the help, I might have given up. Sometimes ideas are close enough that eventually even someone like me if trying enough permutations, will find the right one, but with people like you guys around, I had much better odds.

I have to admit that I don't notice what's different other than I think its using more memory with the linux kernel vs the antiX, and as a result, when I get 1/2 dozen things going, it gets slow as it needs to swap out to disk.

The sound is working now, I just needed to install firmware. As for the wifi, the windows partition won't boot at all, now, so I can't identify what chip is in the wireless adapter, so I'm not sure what to install. I suppose I should start a new thread for that. Once I get that going, I want to find a"lite" panel program. I liked the panel that came with jessie xfce, and will look for something along those lines, or maybe try to figure out how antiX puts the cpu, ram and disk numbers on the screen, and find a way to add functions to that. I see on screenshots that others have, but don't understand how, etc. And once I have that going, I'll set it up on my bigger, faster laptops the same as on the Dell, and on those, with 12x memory and 4x cpus, they will fly, and then I might also try the desktops, which are even faster with 40x memory and 6x cpus. I will need to dual boot them all with windows for the apps that absolutely need it, but I just hope to get to where I am happy working with the linux and don't use the windows often.

Again, thanks to all for the help getting the screen working.

thriftee wrote:...its using more memory with the linux kernel vs the antiX, and as a result, when I get 1/2 dozen things going, it gets slow as it needs to swap out to disk.

This is the sort of thing I was meaning.

antiX is aimed at both newer powerful kit, and older less capable kit. The latter often has little RAM by today's standards, and one has to make a judgement about the economic cost v benefit of upgrading the hardware. antiX helps greatly with this as it strives to produce a usable, working system while at the same time reducing the demand for system resources.


Off Topic

thriftee wrote:...the windows partition won't boot at all, now, so I can't identify what chip is in the wireless adapter, so I'm not sure what to install. I suppose I should start a new thread for that.

A new thread is a good idea, probably two.

It is usually possible to acheive a dual boot with antiX and Windows. There are forum members that will be able to chip in with their experiences. If my memory can be trusted dolphin_oracle touches on this subject in one of the Youtube videos.

Identifying wireless chipsets and get them running can usually be done within antiX.

thriftee wrote:...I want to find a"lite" panel program. I liked the panel that came with jessie xfce, and will look for something along those lines...

Again think about a separate thread.

antiX-13.2 ships with two window managers that provide a panel (taskbar) as part of their default set up. Both IceWM (default WM for antiX-13.2) and JWM are lighter-weight than XFCE. They are highly configurable and have lots of themes (skins) - refer to the antiX FAQ as a starting point.

thriftee wrote:...antiX puts the cpu, ram and disk numbers on the screen, and find a way to add functions to that.

Again suitable for a separate thread.

You are probably referring to an app named Conky. There is lots of information about it in the forum and again the FAQ will help get you started.

Keep in mind it places a demand for resources. This demand increases as you add more monitors and bling to it. If you are intending to run it on low powered kit, these will eventually become increasingly noticeable.

Lots of users integrate Conky into the desktop which I find inconvenient due to it usually being covered by open windows. My preference is to run it only on demand, in a standard window. This also has the added benefit of using system resources only when neccessary i.e. when you want to see the window.

In the end it's your choice that matters and antiX provides lots of options.

Sam,

Thanks for all the thought and ideas that went into that post. You'd be surprised how close some of your comments there are to where I'm trying to get to. And yes, I did and do intend to put questions in separate threads. But it was real nice of you to help with the benefit of your experience in that reply, anyway.

Its just nice to see light at the end of the tunnel after the nvidia troubles.......