Amount of RAM needed?
Posts: 110
I'm having a problem that might be a bug or it might be that I don't have enough ram. I have 256MB of RAM, GeForce FX5200 using the nvidia legacy driver. All apps run fast and smooth, including Tux Racer, exept the Mepis Assistant which causes the system to freeze. Mepis Assistant runs fine when using the nv driver.
Thought I'd get some opinions before I go off and make a bug report on something that might be a lack of RAM.
md5sums
Posts: 110
Md5sums checked out, and everything works when running from the cd and the hd with the nv driver. I only have the problem after switching to the nvidia glx driver.
I also considered that the video card might be going but it's running fine in SM6.0 with the glx driver.
try if you have the same
Posts: 2299
try if you have the same issues as root. Might be kdesu related.
Newbie or not Newbie, there's always a question
not a lack of ram
Posts: 162
Hi Carlops,
With regards to definitely no lack of ram although byco has a Geforce FX5200 he could have the 256mb graphics card model and not the 128mb model so if he only has 256mb memory on motherboard using a 256mb graphics card would be a problem.
Which one is he using !
John
Dunno, but since that memory
Posts: 2299
Dunno, but since that memory is on board of the graphics card, I don't think it will affect the system RAM.
Newbie or not Newbie, there's always a question
Video RAM
Posts: 110
That's a good question. I bought this card a couple of years ago. I don't have the box any more but I would guess it's 128mb. I'll scrounge around and see if I can find any info on it.
I haven't tried running as root/su to see if it still has problems, I'll try it and post the results.
If I am not too misinformed,
Posts: 2299
If I am not too misinformed, the FX 5200 has dedicated ram on board. It will therefore not impact the system memory.
I suspect an xorg.conf thing. Try adding the line:
"Option" "NvAGP" "0" to the device section of xorg.conf and see if that helps.
Newbie or not Newbie, there's always a question
Running as Root
Posts: 110
It still locks up as root when trying to launch any of the Mepis Assistants.
try the xorg.conf fix Newbie
Posts: 2299
try the xorg.conf fix
Newbie or not Newbie, there's always a question
Relative newbie, so give me
Posts: 110
Relative newbie, so give me the step by step for adding that line. 
- press alt-F2 - type: kdesu
Posts: 2299
- press alt-F2
- type: kdesu kwrite /etc/X11/xorg.conf
- find section "Device"
- paste in the line (there's more nvidia stuff)
- save and close
- logout, then restart X by Ctrl-Alt-Backspace
Newbie or not Newbie, there's always a question
xorg.conf
Posts: 110
There's nothing there, no device section or anything. Just a blank page.
While looking for xorg.conf in /root
Posts: 110
I ran across this in .xsession-errors. Judging from the time stamp this would have been about the time that I tried running as root with the glx driver.
Xsession: X session started for root at Fri Feb 2 15:33:23 EST 2007
startkde: Starting up...
/usr/bin/iceauth: creating new authority file /root/.ICEauthority
kbuildsycoca running...
kio (KSycoca): ERROR: No database available!
kio (KIOConnection): ERROR: Header read failed, errno=104
kio (KIOConnection): ERROR: Header has invalid size (-1)
kio (KIOConnection): ERROR: Header read failed, errno=104
kio (KIOConnection): ERROR: Header has invalid size (-1)
kio (KIOConnection): ERROR: Header read failed, errno=104
kio (KIOConnection): ERROR: Header has invalid size (-1)
kio (KIOConnection): ERROR: Header read failed, errno=104
kio (KIOConnection): ERROR: Header has invalid size (-1)
kio (KIOConnection): ERROR: Header read failed, errno=104
kio (KIOConnection): ERROR: Header has invalid size (-1)
kio (KIOConnection): ERROR: Header read failed, errno=104
kio (KIOConnection): ERROR: Header has invalid size (-1)
kio (KIOConnection): ERROR: Header read failed, errno=104
kio (KIOConnection): ERROR: Header has invalid size (-1)
kio (KIOConnection): ERROR: Header read failed, errno=104
kio (KIOConnection): ERROR: Header has invalid size (-1)
kio (KIOConnection): ERROR: Header read failed, errno=104
kio (KIOConnection): ERROR: Header has invalid size (-1)
kio (KIOConnection): ERROR: Header read failed, errno=104
kio (KIOConnection): ERROR: Header has invalid size (-1)
kcminit: ERROR: Access denied to driver shared memory
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/firefox/plugins/libunixprintplugin.so: undefined symbol: NP_GetValue
nspluginscan: WARNING: Plugin doesn't implement NP_GetValue
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/firefox/plugins/libunixprintplugin.so: undefined symbol: NP_GetMIMEDescription
kded: Launching previous backup analyse.
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/mozilla-firefox/plugins/libunixprintplugin.so: undefined symbol: NP_GetValue
nspluginscan: WARNING: Plugin doesn't implement NP_GetValue
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/mozilla-firefox/plugins/libunixprintplugin.so: undefined symbol: NP_GetMIMEDescription
kbuildsycoca running...
Reusing existing ksycoca
kio (KSycoca): ERROR: No database available!
DCOP Cleaning up dead connections.
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0xe00005
paste the line
Posts: 2299
There's nothing there, no device section or anything. Just a blank page.
The X in /etc/X11 is a capital. Paste the line to make sure you have it correct
Newbie or not Newbie, there's always a question
/etc/X11
Posts: 110
Right you are! LOL
Just did it, so far it seems to be working. Should I still make a bug report?
Thanx!
Nope, it is an issue with
Posts: 2299
Nope, it is an issue with the NVidia drivers that rears its head on some machines. Not a MEPIS specific bug I would say.
Glad it works.
Cheers
Newbie or not Newbie, there's always a question
Oops, problem not solved
Posts: 110
I must not have gotten X11 restarted before. I didn't play with it over the weekend and when I booted up today, no GUI.
I thought that maybe I mistyped something so I redid it and copied and pasted it in, rebooted and no GUI. Back on the nv driver, so now what? 
:puzzled
nvidia fx 5200
Posts: 123
I have an nvidia fx-5200 with 256mb ram. I have also seen this with 128mb ram. I use the regular nvidia driver not the legacy driver. You might try it.
Wrong Driver
Posts: 1109
I have 256MB of RAM, GeForce FX5200 using the nvidia legacy driver. All apps run fast and smooth, including Tux Racer, exept the Mepis Assistant which causes the system to freeze. Mepis Assistant runs fine when using the nv driver.
Wrong Driver.
For an Nvidia GeForce FX5200, you need to select the Nvidia *new* driver, *not* the Nvidia legacy driver.
To change it in the latest SimplyMEPIS 6.0-4 Beta 4, go to KMenu>System Settings>Peripherals>MEPIS X-Windows Assistant
Then, select the Nvidia Tab, check Nvidia (new), and click Apply.
When you reboot, you should see the Nvidia screen flash as it loads and everything should work fine.
I didn't even think the Nvidia legacy driver would work at all. It didn't the last time I tried it with an older version of SimplyMEPIS (I had to boot into a Live CD and reinstall X after I made the mistake of selecting the legacy driver).
I'm using an Nvidia GeForce FX5200 adapter (128MB on the card) with the Nvidia new driver (and I've been using the Nvidia new driver choice for a long time with this PC, through multiple releases of SimplyMEPIS).
Jim C.
Wrong Driver
Posts: 110
I've tried both drivers and get the same thing, no GUI at boot.
definitely not a lack of
Posts: 2299
definitely not a lack of ram. Please check md5sum of iso and cd, and try booting from CD and see if you can reproduce the error. If so, give a detailed report of your hardware and send it with specific error description to
Newbie or not Newbie, there's always a question