At 12:01 26/03/2004 -0500, you wrote:
On Fri, Mar 26, 2004 at 04:35:16PM +0000, stdPikachu wrote: > Hello there, long time lurker, first time poster. > > As you may have gathered, I'm having trouble getting a new kernel working > on my (pretty bog standard) Woody install, which after much trial and> tribulation got downgraded back to 2.4.18-bf2.4. I'd love to use one of the> stock kernel images, but can't for several reasons: > Most don't have support for my 3ware RAID card built in > None that I've used have support for my motherboard chipset(s) - it's a > (single K7 CPU) Tyan 2466 with an AMD 460 MPX nbridge and a 462 sbridge> IIRC, so I'm stuck with PIO for IDE access (argh!) - trying to activate DMA> with hdparm gives me an error > I'd like to disable loadable modules support in the interest of security; > this isn't a prerequisite, but would be nice. > > Obviously, the PIO-only is a major issue. Although the bulk of disk access > is done via the 3ware, the system disk is a bog-standard 30GB IDE drive, > and any access to it at all thrashes the CPU. So I took the plunge and > started downloading kernel sources - I've compiled million and one kernels > for Gentoo, and on the face of it the Debian method seemed much easier. >> Kernel sources I've tried include Debian 2.4.18, vanilla 2.4.22 and vanilla > 2.4.25 (kernels above 2.4.20 supposedly support both my mobo and 3ware card> better). Kernel configuration was always based on the 2.4.18-bf2.4 .config > so that I didn't fail to turn on something vital; most modules were > removed, the few I needed (SMBFS, 3com driver and Natsemi 83820 driver, > ext2&3) were compiled in statically. It sounds like you know what you are doing since you have done kernels with Gentoo. Why don't you try the 2.4.25 from kernel.org, take exact notes, and post back here again.
Compiling kernels on Gentoo is exactly the same as doing a standard kernel recompile, there's no magic to it really. The impressive bit is not mucking up the installation prior to that point (and then using the wrong sytntax in GRUB and having to reinstall ;^). The problem I have now is that the system is in use as an LDAP Samba-PDC, and I can't really afford to kill it again.
But yes, I might as well compile a vanilla kernel in my usual fashion, but should I use GRUB (which I know) or stick to LILO (which I don't)?
Recently, I have been installing Debian on brand new Dell Poweredge 400SC's with the gigabit ethernet which requires the e1000 module so I went straight to 2.4.25 and did not use the Debian kernel-package system.
I hope you're familiar with this page...? http://linux.dell.com/We used to use a stock RH install on the PowerEdges we shipped, and on my advice have switched the company over to Debian, and this site has been invaluable, as it contains links to plenty of Debian-related projects tailored to the Dell PE's including the RAID management utilities.
Something you might try is "make oldconfig" as I have been burned in the past by not doing this. By doing make oldconfig, you are made aware of anything new in 2.4.25. I bet you find something that you are missing.
I did consider it, but was under the impression that this was "make-kpkg clean" was for...?
The command I then use is:make dep && make clean && make bzImage && make modules && make modules_install && make install
Yup, sounds like Gentoo ;^)
Hope this helps you!
Yes it does, at least I know I won't irretrievably b0rk my Debian box by doing a bog-standard compile.
But again, if anyone has any additional pointers to doing it the Debian way, I'd be very interested, especially in shipping a standard kernel into our not-yet-online .deb repository (which contains a customised version of Samba with a ready-made smb.conf at present, but I'm still getting to grips with making debs at the moment), so it's easy to upgrade all of our hardware in a uniform fashion. We've still got a RH server out there somewhere running 2.4.2...!