[QUOTE=IBall]What distro are you using?
Debian/woody/3.0
Yes sorry, I knew I should have put that.
>The Kernel Image is the binary
version of the kernel >that has been compiled from the Kernel Source.
>I think that that kernel image (2.4.18-686) is correct for
>a P4.
I looked and all the images for P4 end in -686 so I guess this is the optimzed P4.
> *Gzip is similar to Zip as used on Windows.
Thanks for that. Just not used to seeing 2 extentions on a file. :O
Obviosly the Kernels I have installed have not been compiled with my hardware in mind. What approach is best here?
Do I try to compile a kernel with drivers? Or are module drivers as good?
I have run Modconf which 'Installs' the modules, what does it install them into? It can't install them too the Kernel image, so the driver mods. get registerd somewhere and loaded at startup? How does it do this? (roughly)
I believe modules are just as good because the kernel is more efficient this way. But, I think a new kernel with Nividia/AGP drivers will give me native acceleration? the PCI/AGP bus is failing here, Bad. Only have Vesa video in X.
Also. To compile a kernel, first i need to type 'make xmenuconfig' or 'make menuconfig' ?
I have 'make' but no make files for menuconfig or making a new kernel. Is something missing here? Should I be looking for a package that will make new kernels? Or is 'make menuconfig' a Redhat thing?
I guess I ultimatly want this OS to run like windowz, With as much of my hardware supported in one kernel as possible.
I have 90% of the hardware detecting one way or another, but hardly any of it is useable. ALSA wont load a driver but other apps (ALSActl) have produced audio from the soundcard.
Im finding this incredibly complex.
Lots more questions.
Thanks for your help.
~Snaffta~
running
Debian/woody 3.0 Kernel 2.4.18-686