Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature currently requires accessing the site using the built-in Safari browser.
yeah, i found that on net, it return this about my grfxthat should give you the info you need, but I can't remember if it works on AGP slots.Code:lspci
is my PCI ID: NV44A ?01:00.0 VGA compatible controller: nVidia Corporation NV44A [GeForce 6200] (rev a1)
sudo aptitude install nvidia-glx
sudo aptitude remove nvidia-glx && sudo aptitude install nvidia-glx-new
kdesu kate /etc/X11/xorg.conf
Section "Module"
Load "i2c"
Load "bitmap"
Load "ddc"
Load "dri"
Load "extmod"
Load "freetype"
Load "glx"
Load "int10"
Load "type1"
Load "vbe"
EndSection
Section "Device"
Identifier "NVIDIA GeForce FX 5200"
[COLOR="Red"]Driver "nvidia"[/COLOR]
Option "NoLogo"
[COLOR="#ff0000"]BusID "PCI:1:0:0"[/COLOR]
EndSection
Section "DRI"
Mode 0666
EndSection
since whether or not it works is pretty fragile and depends on many factors.
killall kdm
Don't be scared, it's not that difficult.guess i have no alternative, i'll try ATs way:eek: :eek: :eek: :scared: :(
Killall KDM stops the KDE display Manager, dropping you out of the X server (aka out of the graphical environment). To go to a different runlevel, it's actuallyEdit: tried "Current" drivers from here, trying the "Legacy" drivers next ... i presumedrops the system to to runlevel 3, correct ?Code:killall kdm
init #
yeah, for youAT said:Don't be scared, it's not that difficult.
so, why did my system recommend using runlevel 3 instead of runlevel 1AT said:Killall KDM stops the KDE display Manager, dropping you out of the GUI. To go to a different runlevel, it's actuallywhere # is equal to the runlevel, e.g. "init 3". You don't normally have to drop to a different runlevel in Debian and derivative systems, since they do things a little differently than most distros. Instead, usually just dropping out of X is enough.Code:init #
it already failed to install Legacy driversAT said:As far as installing the driver, don't install the legacy one unless you have a very old card which isn't supported by the new drivers.
that explains why, removing headers & installing "Latest" againAT said:Also, unless you have the kernel headers installed, the installation won't succeed.
i'm firing up Synaptic nowAT said:remove any packages with the word 'nvidia' in it before proceeding
:swear: i'll have to learn to live in konsole :swear:AT said:once you get the NVidia drivers working, keep in mind that they are mostly closed-source drivers. That means that if your system upgrades X.org, you will have to go through this process again. But don't worry, since the whole process only takes a few seconds when you're confident with it.
In most systems, runlevel 1 is too low-level to do what you need to do. In deb-like systems, you can do it from runlevel one. However, you shouldn't need to change the runlevel in deb systems to install the NVidia drivers anyway, as long as X.org/KDM isn't running. You just have to specify an argument on the command-line to tell the NVidia installer not to worry about the runlevel. I run my NVidia installer with the following options on a real Debian system:why did my system recommend using runlevel 3 instead of runlevel 1
sh NVIDIA-[I]someversion[/I].run --x-module-path=/usr/lib/xorg/modules/ -aqNX --no-runlevel-check
Yeah, that's to be expected. It's only for ancient GPUs, so anything since the turn of the century should use the newer driver. :)it already failed to install Legacy drivers
You need the kernel headers which match the installed kernel in order to install the driver. The NVidia installer needs to look at your kernel headers in order to build the driver for you.that explains why, removing headers & installing "Latest" again
Once you understand the basics of what's going on, everything else falls into place. For me, it makes no difference whether I have to do something in a CLI or in a GUI, it's just a matter of accomplishing a task in an efficient manner. In time, you might find that you feel the same way.i'll have to learn to live in konsole :swear:
That goes for any OS. The big difference is that in certain other OS'es, you don't have the option of running from CLI and getting all of the useful verbage back.BTW: luckily most things required have a GUI to generate commands (although the command are fed directly to konsole, and are invisible, unless you start it from konsole)
That's how I do maintenance on my wife's systems, my servers, etc. The servers don't even have a GUI installed, nor monitors, keyboards, etc. SSH is enough. :)BTW: this would be easier if i could browse net on one system and do things to another system, or if i had a printer to print the commands needed, can't wait to get my little LAN setup
i think i'd be better waiting until i can use one system online to get commands to type into the other system, will i be ok to use the vesa driver for about 3 months ?AT said:That's how I do maintenance on my wife's systems, my servers, etc. The servers don't even have a GUI installed, nor monitors, keyboards, etc. SSH is enough.
You can use the vesa driver as long as you want, of course! :) However, you won't have any hardware acceleration of any kind until you have proper drivers. Additionally, you won't be able to use any but basic resolutions and refresh rates either as long as you use vesa.i think i'd be better waiting until i can use one system online to get commands to type into the other system, will i be ok to use the vesa driver for about 3 months ?
Maybe you're thinking of SSL? SSH is Secure SHell, in other words, something similar to telnet but encrypted and secure. It's a great way to securely manage UNIX-like systems remotely, be it across the room or across the world.i thought SSH was a secure network protocol, what are you referring to ?
Donkey breath!BTW: major thankies to AT[ot]not asking this time, just ask your wife to look away, donkey give AT the biggest French kiss the world has ever seen[/ot]
:good: that'll be fine, i think i'll leave it for now, until i get my computer room setup[ot]computer room: a couple of crappy old systems i got off Freecycle[/ot]AT said:You can use the vesa driver as long as you want, of course! :) However, you won't have any hardware acceleration of any kind until you have proper drivers. Additionally, you won't be able to use any but basic resolutions and refresh rates either as long as you use vesa.
yeah :swear:AT said:Maybe you're thinking of SSL?
i dont think i'm ready to be doing that, yetAT said:It's a great way to securely manage UNIX-like systems remotely
how can i breath if our tounges are interlocked[/ot]AT said:Donkey breath!
cheers, ill check it outAddis said:Not sure if Kubuntu Feisty has this feature, but in Ubuntu feisty theres a restricted drivers manager which will install the driver for your kernel for you.
It's the same OS with the same repos. The only difference is the default window manager (KDE instead of Gnome).Not sure if Kubuntu Feisty has this feature, but in Ubuntu feisty theres a restricted drivers manager which will install the driver for your kernel for you.