Quote:
Originally posted by ChemBot
Does anyone know how to fix this?
|
Sure, we could.
But why not trying a quick and dirty approach first? (my speciallity, lol):
If you are using a precompiled kernel, there is a high probabilyt that the module is already compiled. So first try would be loading the module. Debians have a nice interface for this so you don't need to figure out if the module is compiled or not and how its called. The app to load modules is
modconf, launch it from an xterm an look for the video4linux drivers. From my experience I would say it is there, as I do always find it enabled in debianized and even vanilla sources. I'm aware of this fact because I always have to deactivate it.
This is the first approach. Easier impossible. But if it happens that you like to tamper with your kernel... why not doing it debian style? Debian has a complete set of tools to build your own DEB packages and compile and install stuff in a wya which completly fits your system, avoiding problems like bootloader missconfiguration when installing a new kernel and a very easy building proces. What you need is to apt-get install an application called
make-kpkg which does many of the work for you, so you only have to care about properly configuring the kernel.
The syntax of mak-kpkg is easy. Read the man page as it is very comprehensive and short.
For a quick tyr you can build the kernel image, debianized sources, headers and docs in separate deb packages with this command:
Code:
make-kpkg buildpackage
You can configure the kernel before or after issuing it (don't run make clean nor make mrproper).
The packages are installed with:
Code:
dpkg -i package.deb
or clicking on the package in Konqueror, Nautilus or Mozilla
Some hints to avoid Kernel panics:
- check the architecture, it must be exactly the one which fits the CPU brand you are using, if in doubt use i386
- check the filesystem drivers, if in doubt enable them all and built them *into* your kernel
- check if you are using a initrd or ramfs, this is somewhat tricky in Debian, if in doubt disable the initrd option
OK; hope that helps.