Hi, I havn't been able to compile or install a 2.4.x kernel at all for my system would just reset itself when trying to boot.
I have posted several messages regarding this to this list, but havn't got any answers. So I'm wondering whether I'm the only one with such problems. Maybe you have an idea where I can start to look. Here's what happens: Lilo statrs booting then after putting some dots on the screen it the computer just resets itself. No matter what I've tried it's always the same. Here's what I have: a Shuttle FV24 Mainboard with a VIA C3 processor. The motherboard chipset has an integrated Savage4 video chip, some VIA audio chip, ATA100 IDE controllers, realtek 100Mbps ethernet, and a Lucent FireWire chip. I was running Potato then dist-upgraded to Testing (woody). Here's a list of things I've tried. - installing the shrink wrapped 2.4.10-I686 kernel package from testing did the initrd=/boot/initrd stuff - compiled about a dozen kernel versions on my own using make-kpkg - first from the debian kernel-source package for 2.4.10 with or without the ext3 patch - then downloaded 2.4.12 + ac6 patch from kernel.org - tried compiling with the least possible options (kernel size ca. 560k) - disablind ram disk, initrd support - disabling loadable modules alltogether - then explicitly compiling with make-kpkg --initrd - at lilo prompt adding boot parameters: noinitrd, then initrd=/boot/initrd ... - downgrading modutils Also this may be not realated but somebody mentioned a kernel panic 21.05 or 21.95 in some other post. (sorry I don't remember). I've also vaguely recall having seen some 21.something before the dots started after LILO a couple of times... Sorry again, but my Linux box is currently in pieces, so I can't check the exact message. Does any of this make sense? If you have any ideas, I'd be very, very greatfull, as I don't really know what to try next! Many thanks for your help in advance! best regards, Balazs ----- Original Message ----- From: "Eduard Bloch" <[EMAIL PROTECTED]> To: <debian-user@lists.debian.org> Sent: Wednesday, October 31, 2001 10:35 Subject: Re: Patches applied to stock kernel to make deb kernel image > #include <hallo.h> > Adam Warner wrote on Wed Oct 31, 2001 um 07:28:19AM: > > > I'm not an expert on this but I understand that Debian stays as close to > > the offical Linus kernel as possible. So if you want to compile your own > > kernel you should be fine just using a Linus one from kernel.org (or > > No. mkcramfs on initrd is broken in Linus's tree, so please don't build > initrd-aware kernel-image packages without using the debianised source > package. > > > mirrors). In my experience you will only need to patch it if you have > > non-standard hardware requirements (e.g. for one of my computers I > > require the Parallel Port SCSI patch). > > BTW, ppscsi patch is available in the patch-package in Sid. And in > kernel-image-2.4.13-586-ext3 image. > > > make menuconfig (and select the options I want) > > Yes, which _you_ want. If someone uses the config file from the Debian > packages (with initrd), you will see the breakage when you try to boot > with it. > > > make dep > > make bzImage > > make modules > > make modules_install > > make install > > We have "make-kpkg" for such tasks. Makes your life easier. > > > This isn't the standard Debian way of installing a kernel. However I > > have non-standard requirements like ReiserFS compiled into the kernel > > image which means I have to compile my own kernels. > > Errrr, this is not the reason for not using make-kpkg. > > Gruss/Regards, > Eduard. > -- > That's easy: If it ain't the prompt, it's shit. > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > >
