leon30: Well the problem was
only during the install phase, after which everything was fine (I run a few steam games, and some videos without worries), yes the NVidia card was old - 7300GT if I remember correctly, and the cpu was slow 1 core, but I persisted and at the end KDE 4 was handling pretty well, just beware of the liveDVD version which seems heavier than the real deal :). As per AdBlock, it's gotten worse even on windows - some ads are not disabled by default, it's memory hungry and prone to hangs/crashes with not Mozilla/Chrome browsers. Btw do some of you guys use AV software on Linux? In the recent years they got quite common, every major AV company have a Linux edition.
7300 is pretty old. I dont think Nvidia supports it, thats the catch. Even if it supports it, I dont think they patch it.
As of nouveau driver, have donated nvidia 6800gt to the team, so its realistic to assume that anything before 9800GT was reverse-engineered. Its a hit-or-miss minefield. Nvidia does not officially fund or support nouveau. UNlike AMD with its radeon driver.
That means, if you are on Nvidia hardware, make sure to have at least current card (current lowest nominator is Fermi) afaik; or supported by nouveau card. On AMD there are rough edges too, very ancient cards - basically anything before HD4000-era may not be supported fully as they have difficulty to find the documentation pieces themselves and not much interest to fix it.
Intel is rock solid in terms of support (usually), I have Pentium 4 as server with IGP from 2000, that is connected to my TV(1380x1000something). And it works.
What there can else be, is make sure you have "libtxc-dxtn" installed, the famous patented obligatory S3 texture compression. You may also ditch via patent-free "libtxc-dxtn-s2" if you want it all proper. But it must be there.
Where do you get that old hardware from? =) Or is it just for testing?
Regarding adblock, please do check the link in my post. There is some internal things, that cause such older - tech plugins consume huge amounts of RAM.
No, Linux does not need AV. All AV manufacturers I know, have either rewritten their AV-engines or ported/run them via wine/winelib, for only one reason - to check windows binaries and windows itself. For their own solutions, that usually check file traffic of windows binaries, or for their own products for desktop Windows.
There is an AV for Linux, but it is again, used to check windows binaries. There is a combination of factors, that causes Linux to not need any AV. They all come together. Let me sum up few of them:
1) software is pulled via encrypted or checksummed channels from secured central spot. Those locations are kept secure.
2) software itself is "Free Software" per license (not free software), the source is available and binaries are compiled from it; not just provided as convenience.
3) Linux binary file format is pretty fragile. while its possible to inject code into it, it breaks easily.
4) Linux filesystem and unix rights are both made with security in mind and easy to manage. That does not mean that they can't be improved further with application isolation, ACL and so on; but by default system is secure.
5) System allows you to manage it. You can break it, damage it, repair it. It will fully submits itself to root user, unlike windows where "administrator" account is not the top authority (but "system" is).
I think that sums it up. Linux machine can be defeated by selective hacking if you use weak passwords, does not update from insecure versions of packages, you download files from decentralized place or against closed-source software, including drivers and firmware. Of course, it won't protect against hardware sniffers and protocol weak spots (using Wifi without password on your router and main machine, and sending your sensitive data unencrypted via network).
The brightest example in contrast is Android.. while Android is mostly opensource - its "mostly" opensource. Also, userspace (interface is proprietary). It connects into proprietary sniffing network (Google+). There are a lot of applications on that network - and whilst Google smartly followed the same way of isolating application sources - it allows them to be proprietary and closed source. That means, malware can be easily uploaded. To compensate, Google secured the "root" password to itself in order to "pull out the malware already installed on devices". What gives? Not only has google full control of your device (root!), but also they can only pull back after the damage is done. This is why you don't install everything from Google Market; but you CAN install anything from official Debian repository and expect it to contain no malware.