What I have done (thanks to Michael Blandford) is to get the SRPM for the kernel, called kernel-2.4.18-3.src.rpm as far as I can recall, edit the spec file to add the correct patch (in my case for the e1000) and compile it like rpm -bb --with BOOT kernel.spec Michael, would you like to post to the group the guidelines you gave me on this venture? -Torvald -----Opprinnelig melding----- Fra: Rebecca.R.Hepper@xxxxxxxxxxx [mailto:Rebecca.R.Hepper@xxxxxxxxxxx] Sendt: 11. oktober 2002 17:49 Til: kickstart-list@xxxxxxxxxx Emne: Re: Compiling modules for kickstart Thanks for correcting my process, Christopher. If I follow your revised instructions my module compiles successfully. But I still get unresolved symbols (see output below) when the module attempts to get loaded during kickstart. These are different unresolved symbols from when I wasn't following the correct process for compiling the module under the BOOT kernel. So, how do I tell whether the problem is with the compilation of my module or whether it lies with my process of adding the module to the initrd.img? OUTPUT FROM ALTF3 SCREEN: going to insmod e100.o (path is NULL) /tmp/e100.o: unresolved symbols __io_virt_debug /tmp/e100.o: unresolved symbols __netdev_watchdog_up /tmp/e100.o: unresolved symbols eth_type_trans /tmp/e100.o: unresolved symbols __kfree_skb /tmp/e100.o: unresolved symbols alloc skb . . . followed by about 10 more unresolved symbols Christopher Malek <cmalek@xxxxxxxxxxx> To: kickstart-list@xxxxxxxxxx Sent by: cc: kickstart-list-admin@ Subject: Re: Compiling modules for kickstart redhat.com No Phone Info Available 10/10/2002 11:33 AM Please respond to kickstart-list RH = Rebecca Hepper RH> 1. Install the BOOT kernel RPM (kernel-BOOT-2.4.2-2.i386.rpm) RH> 2. Install the kernel source RPM (kernel-source-2.4.2-2.i386.rpm) RH> 3. Boot into the BOOT kernel (uname -r shows 2.4.2-2BOOT) You don't need this step. RH> 4. cp /usr/src/linux-2.4.2/config/kernel-2.4.2-i386-BOOT.config RH> /usr/src/linux-2.4.2/.config At this point, you need to do "cd /usr/src/linux-2.4.2; make oldconfig". It's this, I think, that saves you from having to do step 3. RH> 5. then do a 'make clean' and a 'make dep' in the /usr/src/linux-2.4.2 RH> directory RH> 6. change directories to my e100 source code and change the KSP define in RH> the Makefile to the following: RH> KSP := /usr/src/linux-2.4.2 RH> 7. Compile the driver and install the resulting module into the RH> initrd.img. Chris -- cmalek@xxxxxxxxxxx Nosce Teipsum Office: (626) 395-2593 Fax: (626) 792-4257 Mail Stop: 014-81 _______________________________________________ Kickstart-list mailing list Kickstart-list@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/kickstart-list _______________________________________________ Kickstart-list mailing list Kickstart-list@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/kickstart-list
