When you get a problem like this, a good first place to check is the ``Kernel Newsflash" maintained by rgooch. URL available readily from Google.
The IEEE1284 module was broken in kernel 2.4.12. Kernel 2.4.13 was released early morning October 24. As of early evening, October 24 it had not yet propagated very far (not even to the US and CA kernel.org mirrors) but with any luck, it will soon be widely available. I was, in fact, never able to get a 2.4.12 kernel to boot, even after disabling the faulty IEEE1284 module. It was the first and so far only kernel release to have given me such problems. 2.4.13 worked perfectly first time <loud sigh of relief>. On 24 Oct 2001 at 23:41, parn wrote: Date forwarded: Thu, 25 Oct 2001 00:16:32 -0400 (EDT) Date sent: Wed, 24 Oct 2001 23:41:13 -0500 From: parn <[EMAIL PROTECTED]> To: Debian-user@lists.debian.org Subject: kernel-2.4.12 compile errors Forwarded by: debian-user@lists.debian.org I have been trying to compile this kernel using the information from The Kernel: Configuration and Compilation NHF V1.2 step by step. First by untarin in /usr/src/-> then make xconfig followed by the dep,bzimage. Here is where I get my errors. So I did a little more rtfm and saw about make-kpkg so tried make-kpkg buildpackage. Here is my results: make[5]: *** [ieee1284_ops.o] Error 1 make[5]: Leaving directory `/home/parn/linux/drivers/parport' make[4]: *** [first_rule] Error 2 make[4]: Leaving directory `/home/parn/linux/drivers/parport' make[3]: *** [_subdir_parport] Error 2 make[3]: Leaving directory `/home/parn/linux/drivers' make[2]: *** [_dir_drivers] Error 2 make[2]: Leaving directory `/home/parn/linux' make[1]: *** [stamp-build] Error 2 make[1]: Leaving directory `/home/parn/linux' make: *** [stamp-buildpackage] Error 2 I have compiled the 2.4.9 before w/no errors :) Works nicely, Could someone tell me what i am doing wrong? This is being compiled on a intel i810 700celeron w/gcc version 2.95.4 running testing/unstable. Thanks to any that reply! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
