TV-out pentru placi Nvidia
     media: 4.00 din 4 voturi

postat de firefly in 2006-10-25 22:20
In /etc/X11/xorg.conf:

Section "Device"
Identifier "NVIDIA Corporation NV18 [GeForce4 MX 440 AGP 8x]"
Driver "nvidia"

VendorName "Videocard vendor"
BoardName "NVIDIA GeForce 4 (generic)"
Option "NvAGP" "1"
Option "RenderAccel" "1"
#TV Out Setup
Option "TwinView"
Option "SecondMonitorHorizSync" "30-50"
Option "SecondMonitorVertRefresh" "60"
Option "MetaModes" "1024x768, 1024x768; 800x600, 800x600; 640x480, 640x480;"
Option "TVStandard" "PAL-B"
#Option "TVOutFormat" "COMPOSITE"
Option "TVOutFormat" "SVIDEO"
Option "TwinViewOrientation" "Clone"
Option "ConnectedMonitor" "CRT, TV"


     media: 0.00 din 0 voturi

postat de firefly in 2006-10-20 11:44
#apt-get install tinyproxy
#mcedit /etc/tinyproxy/tinyproxy.conf

User nobody
Group nogroup
Port 8080
Timeout 600
Logfile "/var/log/tinyproxy.log"
LogLevel Connect
PidFile "/var/run/"
MaxClients 100
MinSpareServers 5
MaxSpareServers 10
StartServers 5
MaxRequestsPerChild 0
ViaProxyName "tinyproxy"

#ssh -L 8080: extproxy.domeniul.meu

ssh -qTfnN2 -D 8080 then set browsewr's proxy to port 8080

Looks like ssh can support forwarding traffic and act as a SOCKS proxy. This is fantastic for encrypted browsing over unsecured wifi connections. Just setup Firefox, AIM or any other SOCKS 4 or 5 compliant program to use the proxy. After executing the command below ssh will be listening on localhost ( and you would then point your SOCKS compliant program to this ip and the port you specify below. This can also be done with SSH client for windows Putty. Something like this possibly: putty -D 8080 -L 443 -ssh ssh_hostname.

ssh -qTfnN2 -D 8080

-q :- be very quite, we are acting only as a tunnel.

-T :- Do not allocate a pseudo tty, we are only acting a tunnel.

-f :- move the ssh process to background, as we don?t want to interact with this ssh session directly.

-N :- Do not execute remote command.

-n :- redirect standard input to /dev/null.

-2 :- Forces ssh to try protocol version 2 only.

-D :- Specifies a local ``dynamic'' application-level port forwarding. This works by allocating a socket to listen to port on the local side,and whenever a connection is made to this port, the connection is forwarded over the secure channel, and the application protocol is then used to determine where to connect to from the remote machine. Currently the SOCKS4 and SOCKS5 protocols are supported, and ssh will act as a SOCKS server. Only root can forward privileged ports.

If you want to change settings in firefox for example go to: edit -> preferences -> connection settings -> manual proxy configuration -> SOCKS Host Port 8080

If you have a browser like Opera or another program that is not SOCKS aware you can use a program called tsocks. It makes a little tunnel and takes all of the outbound network traffic from the program that can't talk SOCKS and turns it into a program that can use the SOCKS server.Open the config file (/etc/tsocks.conf) and set your local networks like "local = 192.168.0.*". Then tell tsocks where the local SOCKS server is running with the settings "server = localhost" and "server_port = 8080". Last set tsocks to SOCKS type 5 like "server_type = 5". Then save the file and fire up your non-socks aware program using tsocks like "tsocks opera".

If the network your on blocks ssh outbound but leaves open port 80 or 443 then just run your ssh server on the open 80 or 443 ports.

If the network your on blocks all ports outbound except one for a proxy server then you can use a program called corkscrew. It will tunnel SSH through HTTP proxies. All you need to know is what ports the proxy lets you connect to like https (443) or http (80). Follow the readme it will show you how to set it up with ssh. After that you just use the ssh line we discussed at the top of this article to use ssh as your SOCKS proxy. Possibly combine corkscrew with tsocks.

If you have a firewall or proxy that only allows http headers going out 80 then you could use httptunnel. You need to run httptunnel on both the machine you connecting from and the machine your connecting to. The machine your connecting to will be doing your tunneling (your home machine possibly) and will need to run the httptunnel server on port 80 so you could not have any program using that port. Just read the readme's and other instructions to get it going.

If your on a network that will only let you resolve dns queries then you can even tunnel your ssh traffic through dns. Wicked huh? You can do this with a program called iodine. To do this you have to have control over real domain like and a server with a static public IP number that does not yet run a DNS server. This is because you will be running a fake dns server on udp port 53 on your server. That is how the traffic is tunneled to your machine from the locked down network that only allows dns queries. Just read about it a the link above.

If your really desperate you can even tunnel icmp packets. This is know to most people through the program ping. A ping is just and icmp echo request. If you get onto a network that is really locked down but for some reason lets you ping hosts to the outside world then you can tunnel your traffic through icmp packets. It can be done with a program called ping tunnel.

Tunnels are really an endless game. The thing to remember is if your on a network and you can get any kind of machine on that network (proxy,dns,etc) to connect to a machine of your choosing outside of that network then you can tunnel to it. Like a dns query or a ping. You can tunnel almost any thing. Just becasue your on a locked down network doe not mean your situation is hopeless but if you have a host you control on the outside world (your home machine) and you control the host on the locked down network (root privs) you have a better chance of being able to use a tunnel.

CD-ROM & ISO image cookbook.
     media: 0.00 din 0 voturi

postat de firefly in 2006-10-09 19:35
Ripping a CD-ROM to an ISO image

Creating backups of CD-ROM images for storage, or to use as installation media for Qemu is a reasonably common task.

If your CD-ROM device is /dev/cdrom you can use the following command to create an ISO image from it:

dd if=/dev/cdrom of=myimage.iso
Mounting an existing ISO image

If you've made a previous backup of a CD-ROM, or downloaded the ISO image of a new Linux distribution you can mount it to see what is inside the image - before you burn it.

First make sure you have an existing, and empty, directory to mount the image upon:

mkdir -p /mnt/iso

Now mount the image with the loopback module:

modprobe loop
mount -t iso9660 -o loop myimage.iso /mnt/iso
Modifying an ISO Image

Whilst ISO images are readonly when mounted you can "fake" their writability using the unionfs filesystem driver. This cool module allows you to combine two, or more, directories and present their union in a new location.

Under Debian you can build and use this kernel module by running:

apt-get install module-assistant unionfs-source
module-assistant prepare
module-assistant build unionfs
module-assistant install unionfs
insmod unionfs

Once built and installed you can "merge" the mounted ISO image and another directory by running:

mkdir /mnt/tmp
mkdir /mnt/combined
mount -t unionfs -o dirs=/mnt/tmp:/mnt/iso none /mnt/combined

This will give you a directory /mnt/combined containing both the contents of the ISO image you previously mounted in /mnt/iso and the directory /mnt/tmp (which will be empty initially).

Now you can modify the read-only ISO image! Make any additions to the image by modifying the /mnt/combined directory. Instead of modifying the files upon the ISO image though the changes will be saved to the directory /mnt/tmp.


Creating an ISO image of a directory

If you have a directory containing files which you'd like to burn to CD-ROM you should first create an ISO image.

Install the appropriate software with:

apt-get install mkisofs

Then create the actual image with :

mkisofs -o /tmp/output.iso  -J -R /path/to/files
Burning an ISO image to CD-ROM

If you've created an ISO image you can burn it to your CD-writer using the cdrecord program. Install it with:

apt-get install cdrecord

Usage is really beyond the scope of this introduction, but in brief you'd first proceed by finding the CD-Writer device upon your system:

dan@PC13:~$ cdrecord -scanbus


0,0,0 0) '_NEC ' 'DVD_RW ND-3530A ' '1.80' Removable CD-ROM
0,1,0 1) *
0,2,0 2) *

Here we have a device labelled "0,0,0". To write an image to that writer we run:

cdrecord -dev 0,0,0 /tmp/output.iso
Creating Checksums of Images

When transferring large files such as ISO images you will almost certainly wish to make sure you've not downloaded/uploaded a corrupt file.

In this case you can list the MD5/SHA1 hashes alongside the file. This allows users to verify that their downloads were correct.

To create a checksum of a file run one of:

md5sum filename
sha1sum fileName

(These two commands are contained within the coreutils package - which should be installed upon all Debian GNU/Linux systems)

Video camera & FireWire (IEE1394)
     media: 0.00 din 0 voturi

postat de firefly in 2006-10-09 19:31

In an open terminal for root , edit the file /etc/modules to add the following lines:


That will load the FireWire modules at startup. To avoid restarting, you can:

modprobe raw1394
modprobe video1394

Then insure the device is present in /dev. To do that, several methods are applicable. The following one will always work. Create a script /etc/init.d/firewire with the following content:

#! /bin/sh

test -e /dev/raw1394 || mknod -m 666 /dev/raw1394 c 171 0

Make it executable:

chmod +x /etc/init.d/firewire

Establish the link to automatically startup the script at boot:

ln -s /etc/init.d/firewire /etc/rcS.d/S10firewire

Once again, it could be useful to restart to test it, but it is not absolutely necessary, you can do the same by executing the script yourself now like so:


And you're up! The DV camera will now be recognized by Kino. It's up to you now!

Video Camera used : DV Sony HC19

Howto to get openGL working on Debian (for Google Earth)
     media: 0.00 din 0 voturi

postat de firefly in 2006-10-09 19:26

3D drivers (openGL) have awlays been a source of problem on Linux. A lot of people just don't care, since they don't use there computer to play games. But yesterday, something change this fact: Google released a native version of Google Earth for Linux. Fine, except that I'm unable to get hardware openGL working and Google Earth is really slow, so I decided to fix that. (done on two computers..)

Configure your kernel

Be sure to have AGP (Device drivers->Character device) and DRM (Device drivers ->Graphic drivers) enabled for your card. Now rebuild it using the usual way.. and reboot.

After the boot look at dmesg, you should find something like this:

agpgart: Detected 892K stolen memory.
agpgart: AGP aperture is 128M @ 0xf0000000
[drm] Initialized drm 1.0.1 20051102
[drm] Initialized i915 1.4.0 20060119 on minor 0
[drm] Initialized i915 1.4.0 20060119 on minor 1
(If you have a Dell computer like D400 with Intel 855GM, you need to
choose the i915 driver for DRM, edit the linux/.config since it doesn't appear in common menuconfig)
Install latest xorg
#sudo apt-get install xserver-xorg

Let's go, for a long update... (I'm switching from 6.9 to Xorg 7.0).. I spent a little time to fix some errors here.. but nothing really important.

Install openGL libs:

  • xlibmesa-dri
  • xlibmesa-gl
  • xlibmesa-glu
  • mesa-utils
  • libgl1-mesa-dri
  • libgl1-mesa-glx

Start your Xserver, and look in /var/log/Xorg.0.log, you should fine stuff like this:

(II) I810(0): [drm] created "i915" driver at busid "pci:0000:00:02.0"
(II) I810(0): [drm] added 8192 byte SAREA at 0xe0b2f000

So we can test check with glxinfo

display: :0  screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.2

Be sure to have direct rendering ok.. if this is ok, .. you can start glxgears - printfps ... and Google Earth :) ..


Some users have some trouble w/ DRI not working with strange messages ( sizeof(I830DRIRec) does not match ...), or strange display updates (out of syncr windows .. ). This seems to be bugs in Mesa, you can try the latest experimental (which fix all issues for me). Simply install this packages:

  • libgl1-mesa-dri_6.5.0.cvs
  • libglu1-mesa_6.5.0.cvs
  • libgl1-mesa-glx_6.5.0.cvs

HOWTO: Solve flash problem on firefox
     media: 0.00 din 0 voturi

postat de firefly in 2006-10-09 19:24
Alright, lots of us have experienced firefox crashes on flash sites and got really frustrated. Now herez the fix for it:

#sudo apt-get install flashplayer-mozilla arts
#sudo gedit /etc/mozilla-firefox/mozilla-firefoxrc

and change


Even if u find an empty file or dont find any FIREFOX_DSP="auto" just type


and save and exit.
now close all firefox windows and restart firefox and check any flash site. This shd work!

Compilarea kernelului 2.6 mini-how-to - the Debian way
     media: 0.00 din 0 voturi

postat de firefly in 2006-10-09 19:21
Pentru a putea compila kernelul in stil Debian aveti nevoie de niste pachete suplimentare. Lansati un terminal si dati comanda:

#apt-get install make gcc bin86 libc6-dev kernel-package module-init-tools

Cele instalate ar trebui sa fie ok pentru o configurare in consola cu menuconfig (s-ar putea sa mai aveti nevoie si de ncurses-dev). De asemenea, daca doriti sa compilati kernelul cu initrd mai instalati si initrd-tools.

Daca doriti sa configurati kernelul in X aveti 2 optiuni: xconfig si gconfig.
In 2.6 xconfig foloseste interfata QT, deci daca folositi KDE ar trebui sa instalati:

#apt-get install libqt3-dev make gcc bin86 libc6-dev kernel-package module-init-tools

Sau daca folositi Gnome sau doriti interfata gtk:

#apt-get install libglade2-dev make gcc bin86 libc6-dev kernel-package module-init-tools

Instalati sursele kernelului:

#apt-get install kernel-source-2.6.11

Eu va recomand kernelele din distributie deoarece includ bugfixuri si patch-uri:

#firefly:~# apt-cache search kernel-source-2.6 --names-only
#kernel-source-2.6.11 - Linux kernel source for version 2.6.11 with Debian patches
#kernel-source-2.6.8 - Linux kernel source for version 2.6.8 with Debian patches

Dezarhivati sursele si creati un symlink la director:

#cd /usr/src
#tar jxf kernel-source-2.6.11.tar.bz2
#ln -s kernel-source-2.6.11 linux

Configurati kernelul (configurarea nu face obiectul acestui mini-how-to):

#cd /usr/src/linux

Folosind interfata ncurses, in terminal:
#make menuconfig

... sau folosind interfata QT:
#make xconfig

... sau folosind interfata GTK:
#make gconfig

Compilati kernelul:
#make-kpkg kernel_image

... sau creati kernelul cu initrd:
#make-kpkg --initrd kernel_image

... va aparea un warning message care il ignorati:
firefly:/usr/src/linux# make-kpkg --initrd kernel_image
Warning: You are using the initrd option, that may not
work, depending on your kernel version and architecture,
unless you have applied the initrd cramfs patch to
the kernel, or modified mkinitrd not to use cramfs by
default. The cramfs initrd patch, is included in the
Debian supplied kernel sources. New kernels on most
architectures do work fine.
By default, I assume you know what you are doing, and I
apologize for being so annoying. Should I abort[Ny]?

Aceasta va compila kernelul si va crea un pachet kernel-image-2.6.11_10.00.Custom_i386.deb pe care il instalati:

#cd /usr/src
#dpkg -i kernel-image-2.6.11_10.00.Custom_i386.deb

Daca folositi initrd nu uitati sa verificati daca /etc/lilo.conf are optiunea initrd=/initrd.img in sectiunea noului kernel ...

Installing nvidia driver
     media: 0.00 din 0 voturi

postat de firefly in 2006-10-09 19:13
Here are the instructions for building and installing your nVidia drivers, the Debian way.
The nVidia driver consists of two parts: a kernel module, and a collection of user-space libraries. The libraries (sometimes called the "binary driver" or GLX libraries) are distributed in binary form by nVidia, and packaged for Debian in the nvidia-glx package. The kernel module (aka the "kernel interface to the binary driver") is distributed in source form (though with one binary component), and packaged for Debian in the nvidia-kernel-source and nvidia-kernel-common packages. The user libraries and kernel module source only have to be installed once. Then the kernel module has to be rebuilt every time you rebuild or change your kernel. So, here's what you will do:
Build and install the kernel module.
Install the user-space libraries.
Update your configuration.

Step 2 has to be performed after step 1 because of some dependencies, as I explain below.

Steps 2 and 3 have to be performed only once. Step 1 you have to repeat every time you change your kernel, but with the help of module-assistant, apt-get, and make-kpkg, it's hardly any work at all.
Stock or Custom Kernel?
Some of the installation methods below depend on whether you're running a stock kernel, i.e. a prebuilt kernel from the Debian distribution. If you don't know what kind of kernel you're running, then it's probably a stock kernel. But to find out, run

apt-cache policy kernel-image-$(uname -r)
and look at the source lines for the version that's listed as installed. If the source lines include something at, then you're running a stock kernel. If no version is listed as installed, then you're running a custom kernel. If a version is installed, but the only source listed for the installed version is /var/lib/dpkg/status, then you may be running a custom kernel, or a stock kernel that's old enough to have dropped out of the Debian distribution. The easiest way to tell is just to look at the kernel version number (output of uname -r): if it looks like e.g. 2.4.x-1-k7 or 2.6.x-1-686, then it's probably an old stock kernel.
Choose a Distribution
Before you install the Debian nVidia packages, you should choose a distribution, either 'testing' or 'unstable', from which to install them. There is no 'stable' version of these packages at present. You can run 'apt-cache policy nvidia-kernel-source' to see which versions of the driver are available in each distribution.

Once you've chosen a distribution, put its value into a shell variable NVDIST, by executing one of the following lines:

I will use $NVDIST to represent this value in all of the commands below. Also, make sure that your /etc/apt/sources.list contains a line like 'deb $NVDIST main contrib non-free', for your $NVDIST. (Help yourself to a copy of my sources.list if you like.) And if you've just modified /etc/apt/sources.list, you need to run 'apt-get update' before continuing below.
Installation Instructions
Build and install the kernel module.

There are four different procedures that you can use to install the kernel module. If that sounds like a lot, don't worry—I've listed the easiest methods first. So start with the first one, and if it doesn't work for you, go on down the list. Click on the title of each method to see the instructions.
Use module-assistant. This method is very easy, and should work for most people, with either a stock or custom kernel.

Install module-assistant if you don't have it, and nvidia-kernel-common:

apt-get install module-assistant nvidia-kernel-common
Then run:

m-a prepare
m-a auto-install nvidia
And that's it. If all went well, your nVidia kernel module is now built and installed; you may proceed to step 2.

module-assistant automates the more detailed procedures described below: it downloads the nvidia kernel module source, builds a kernel module package compatible with your (stock or custom) kernel, and installs the package. (If you're interested, the package file is /usr/src/nvidia-kernel-*.deb, and you can see that it's installed by running apt-cache policy nvidia-kernel-$(uname -r).) Of course module-assistant has many other operations and options; see the module-assistant man page for details.

Note: you must use the same version of gcc to build your nvidia kernel module as was used to build your kernel. This might be a problem if you are running a stock kernel. If module-assistant fails, read its log output and look for messages suggesting that you need, for example, gcc-3.4 instead of gcc-3.3. (Thanks to Josep Ma Antolin for this tip.)
Install a pre-built module. This method is easy if you're running a recent stock kernel; will take a little more work and may fail if you're running an older stock kernel; and will not work at all if you're running a custom kernel.

Find out if there's a prebuilt module available for your kernel. The official Debian mirrors include prebuilt modules for just a few stock kernels, but Randall Donald maintains unofficial prebuilt modules for many other old and current stock kernels. To get access to Randall's repository, add

deb modules-unstable/i386/
into your /etc/apt/sources.list. Now run

apt-get update
apt-cache policy nvidia-kernel-$(uname -r)
and look for a source line somewhere at If there is one, then proceed to step (b). If you don't find one, then there's no prebuilt module for your kernel, so this installation method won't work for you; you should go ahead and try a different installation method.
Find out if there are nvidia-glx and nvidia-kernel-common packages compatible with your nvidia-kernel-* package: run

apt-cache policy nvidia-kernel-$(uname -r) nvidia-glx nvidia-kernel-common
and look for versions of all three packages with compatible version numbers (identical up to the first - or +). If you find them, you're in luck; proceed to step (c).

If you don't find compatible versions of all three nvidia-* packages, then you may still be able to find some on search there for nvidia, add the lines it tells you about to your /etc/apt/sources.list, run apt-get update, and repeat this step.

If after trying the above you still can't find compatible versions of the three nvidia-* packages, then sorry, but this installation method will not work for you. You should go another method. As a rule, nvidia-kernel-* packages are only available in the versions of the nvidia driver that were current at the same time as the kernels they were built for; while nvidia-glx is generally only available in the latest one or two versions. For example, at this writing nvidia-kernel-2.6.3-1-386 is only available in version 1.0.5336, while nvidia-glx is only available in version 1.0.7174. Those versions are incompatible, so if your kernel is a stock 2.6.3, then you have to either upgrade it or choose a different installation method for the nVidia drivers.
If you found compatible nvidia-* packages in steps (a) and (b), then install them now:

apt-get -t $NVDIST install nvidia-kernel-common nvidia-kernel-$(uname -r)
(you'll install nvidia-glx below). You may have to adjust $NVDIST here, depending on where you found compatible versions of the nVidia packages in step (b), above. Sorry, but the possible permutations are too numerous to list here. If this step succeeds, you may now proceed to step 2. If not, try a different installation method.
Build manually, with a stock kernel. Use this method if you're running a stock kernel, and want or need to build your own nVidia kernel module or other add-on kernel modules.

(The following procedure is adapted from the instructions in /usr/share/doc/nvidia-kernel-source/README.Debian.)
Save the release number of your kernel (e.g. 2.4.27-2-k7 or 2.6.8-1-686) in a couple of environment variables:

export KVERS=$(uname -r)
export KSRC=/usr/src/kernel-headers-$KVERS
Note that these variables are used by the build commands below, so you really do need to set and export them, as in the above commands.
Install the kernel module source: run

apt-get -t $NVDIST install nvidia-kernel-source nvidia-kernel-common
This will give you a source tarball /usr/src/nvidia-kernel-source.tar.gz. Unpack it with

cd /usr/src
tar -zxf nvidia-kernel-source.tar.gz
This will unpack the kernel module sources into /usr/src/modules/nvidia-kernel.
Install the header files for your kernel:

apt-get install kernel-headers-$KVERS
This will give you kernel header files in /usr/src/kernel-headers-$KVERS. Be sure to check that the installed kernel image and kernel header packages have the same version number: run

apt-cache policy kernel-image-$KVERS kernel-headers-$KVERS
and check that the version number listed as Installed is the same for both packages. If it isn't, find the distribution that has the version of kernel-headers that you need, e.g. testing, and rerun the above installation command, adding '-t testing' (or whichever).
Build the kernel module package:

cd /usr/src/modules/nvidia-kernel
debian/rules binary_modules
The result will be a package file /usr/src/nvidia-kernel-*.deb, which contains your kernel module.

Note: several users have told me recently that their nvidia package file ends up in /usr/src/modules, instead of /usr/src. I don't know yet why this happens. If this is your case, please adjust the next command appropriately.
Install the kernel module:

dpkg -i /usr/src/nvidia-kernel-*.deb
Use the fileglob as above if you want, but watch out that you don't have more than one nvidia-kernel package file lying around in /usr/src. If you do you'll get a blizzard of error messages. It's probably better to explicitly type all of the version information that I rendered as * above.
Now proceed to step 2, below.
Build manually, with a custom kernel. Use this method if you're configuring and building a custom kernel.
Install the kernel module source: run

apt-get -t $NVDIST install nvidia-kernel-source nvidia-kernel-common
This will give you a source tarball /usr/src/nvidia-kernel-source.tar.gz. Unpack it with

cd /usr/src
tar -zxf nvidia-kernel-source.tar.gz
This will unpack the kernel module sources into /usr/src/modules/nvidia-kernel.
Configure your kernel. I won't try to document this step here; if you need to learn how, see the Kernel HOWTO and "How to Upgrade to the 2.6 Kernel". But in summary, all you have to do is

cd /usr/src/linux
make xconfig
and then choose the options you want. Note, however, that each of the following kernel options has been reported to cause trouble with the nVidia drivers:
Graphics Support –> nVidia Riva support (FB_RIVA)
Kernel Hacking –> Use 4Kb for kernel stacks instead of 8Kb (4KSTACKS)
Processor Type and Features –> Local APIC support on uniprocessors (X86_UP_APIC) (not available if you have an SMP kernel, including hyperthreading)
I therefore recommend that you disable all of the above options in your kernel configuration. If for some reason you don't disable them, and then your X display doesn't work properly with the nVidia driver, you should suspect these options as the likely cause of the trouble. For more details, see the troubleshooting page.
Build the kernel and nvidia kernel module:

cd /usr/src/linux
make-kpkg clean
make-kpkg kernel_image modules_image
For an introduction to using make-kpkg to build kernel packages, see "Creating custom kernels with Debian's kernel-package system", or "Compiling Kernels the Debian Way". See also the make-kpkg man page, for a description of other options and targets that you can use in this command.

The result of the above command will be two Debian package files, kernel-image-*.deb and nvidia-kernel-*.deb, both in /usr/src. The first file contains your kernel, and the second contains your nVidia kernel module.

At the same time, if you have sources for any other add-on kernel modules in /usr/src/modules, then the "modules_image" target will cause make-kpkg to build Debian package files for them, too. For example, if you install the fuse-source package you'll get a source archive /usr/src/fuse.tar.gz, which you can unpack to get fuse module sources in /usr/src/modules/fuse. If you've done this, then this same invocation of make-kpkg will also build a fuse module package file, /usr/src/fuse-*.deb, that's specific to your new kernel.

Note: several users have told me recently that their nvidia package file ends up in /usr/src/modules, instead of /usr/src. I don't know yet why this happens. If this is your case, please adjust the following commands appropriately.
Install the new kernel and kernel module:

cd /usr/src
dpkg -i kernel-image-*.deb nvidia-kernel-*.deb
Use the fileglobs as above if you want, but watch out that you don't have more than one kernel-image or nvidia-kernel package file lying around in /usr/src. If you do you'll get a blizzard of error messages. It's probably better to explicitly type all of the version information that I rendered as * above.
Install the nVidia user-space libraries. Run

apt-get -t $NVDIST install nvidia-glx
If you're asked whether you want to install the thread-local storage libraries, say yes. Notes:
If the kernel you installed above is version 2.6.x, and the one you're running now is pre-2.6, then you should reboot with your new kernel before performing this step. The reason is that if you're not running a 2.6-series kernel when you perform this step, the thread-local storage part of the user-space libraries will not be installed. As a result your X server will crash when it tries to load the nVidia driver. If you already installed nvidia-glx earlier under a pre-2.6 kernel, then reboot to the new kernel, run dpkg-reconfigure nvidia-glx, and answer yes when asked if you want to install the TLS libraries.
The reason this step has to come after step 1 is that nvidia-glx depends on a virtual package called 'nvidia-kernel-$NVVERSION', where $NVVERSION is the version number of the nVidia driver you've installed. This virtual package is provided by the kernel module package that you installed in step 1; so you have to complete that step first.
Update your configuration.
Update /etc/X11/XF86Config-4. Naturally, there is both a Debian way and an old-fashioned way of doing this. Click on a method title to see the instructions.

The Debian way. This method avoids many common configuration errors, because you don't write an XF86Config-4 file yourself. Instead you answer a series of questions about your mouse, keyboard, and video hardware, and then the configuration script writes an XF86Config-4 file for you.

Save yourself some possible grief later, by backing up your current XF86Config-4:

cp -p /etc/X11/XF86Config-4 /etc/X11/XF86Config-4.bak
Tell Debian that XF86Config-4 has never been edited:

md5sum /etc/X11/XF86Config-4 >| /var/lib/xfree86/XF86Config-4.md5sum
If you don't perform this step, and you have ever edited XF86Config-4, then dpkg-reconfigure will lead you through its whole questionnaire below, and then silently fail to write a new XF86Config-4. This is Debian bug #223929.

dpkg-reconfigure xserver-xfree86
and answer all of the questions.
When asked to choose an X server driver, choose "nvidia". An open-source alternative is the "nv" driver, which has 2D but no 3D capabilities.
When asked to select X server modules, deselect (uncheck) GLCore and dri, and select (check) glx.

When you're done, ls -l /etc/X11/XF86Config-4 to be sure your new XF86Config-4 file has been written. Thanks to Dave Page for informing me about this method.
The manual way. This method is simpler, and it will preserve any customizations you've made to XF86Config-4. Just watch out for typos, and check /var/log/XFree86.0.log if you've recently edited XF86Config-4 and things go wrong.

Edit /etc/X11/XF86Config-4:
In the "Module" section, be sure that you have a line

Load "glx"
and remove or comment out (prepend with a #) any lines that refer to the "dri" or "GLCore" modules.
In the "Device" section for your video card, be sure you have a line

Driver "nvidia"
An open-source alternative is the "nv" driver, which has 2D but no 3D capabilities.
Create a "video" group, and add to it any users who you want to be able to use the display. You can do this manually by editing /etc/group, or the Debian way by

addgroup --system video
adduser $USER video
for each $USER you want to add to the group.
Ensure that the nvidia module gets inserted into your kernel automatically at boot, by adding it to /etc/modules if it's not already there:

grep -q ^nvidia /etc/modules || echo nvidia >> /etc/modules

That's it. Your binary driver and kernel interface module are now installed and configured, and should work when you reboot with the new kernel and/or restart your X server.
Of course the nvidia module will have to be loaded into your kernel to work. If you've just installed the driver and don't need to reboot, then load the driver manually with modprobe nvidia or modconf before restarting your X server.
For more information about the nVidia driver, see:
These files have loads of information about options and troubleshooting for the nVidia driver. Here's an enticement for you to read them: somewhere in one of them you can find an explanation of how to suppress the nVidia splash screen every time you start an X server (hint: search for "NoLogo").
You can adjust the clock rates of your GPU and video RAM by running nvclock, nvclock_gtk, or nvclock_qt, available respectively in the nvclock, nvclock-gtk, and nvclock-qt packages. Obligatory warning: you can destroy your video hardware with these tools if you're not careful.
You can adjust some other, relatively obscure settings of the driver by running nvidia-settings, available in the nvidia-settings package.
As I said above, you won't ever have to repeat steps 2 and 3 above, as long as you don't reverse them, of course.
On the other hand, the kernel module that you built in step 1 is specific to the kernel you built it with. If you install a new kernel that's different in any way from the old one, you'll have to install a new driver module to go with it. In that case just go back and repeat step 1.
Using this method, you don't need any of the following things:
The official nVidia installer from The Debian packages contain all of the parts of it that you need.
Any of the patch or installer files available at (But thanks to the folks at for providing those patches, during all of the time when the official nVidia drivers didn't work yet with kernel 2.6.)
The nvidia-kernel-src and nvidia-glx-src packages, which are deprecated. You can also ignore the nvidia-glx-dev package, unless you get complaints from some software (old games?) about missing (thanks to Randall Donald for this information).
You can ignore the warning at about carrying along the EXTRAVERSION information if you use --append-to-version with make-kpkg. Because you're using make-kpkg all the way through the build process, it takes care of this for you.

Install Microsoft TrueType core fonts
     media: 0.00 din 0 voturi

postat de firefly in 2006-10-09 15:44

How do I install Microsoft TrueType core fonts and FreeType fonts under Debian Linux?

# apt-get install msttcorefonts cabextract x-ttcidfont-conf

Reconfigure TrueType and CID fonts for X windows:
# dpkg-reconfigure x-ttcidfont-conf

Select FreeType from the drop down list.

Open /etc/X11/XF86Config-4 file and append following FontPath:
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID"

Save and close the file

Termeni si Conditii de Utilizare