RH = Rebecca Hepper RH> Thanks for correcting my process, Christopher. If I follow your revised RH> instructions my module compiles successfully. But I still get unresolved RH> symbols (see output below) when the module attempts to get loaded during RH> kickstart. These are different unresolved symbols from when I wasn't RH> following the correct process for compiling the module under the BOOT RH> kernel. So, how do I tell whether the problem is with the compilation of RH> my module or whether it lies with my process of adding the module to the RH> initrd.img? RH> OUTPUT FROM ALTF3 SCREEN: RH> going to insmod e100.o (path is NULL) RH> /tmp/e100.o: unresolved symbols __io_virt_debug RH> /tmp/e100.o: unresolved symbols __netdev_watchdog_up RH> /tmp/e100.o: unresolved symbols eth_type_trans RH> /tmp/e100.o: unresolved symbols __kfree_skb RH> /tmp/e100.o: unresolved symbols alloc skb RH> . . . followed by about 10 more unresolved symbols Someone correct me if I'm wrong: I think if you get unresolved symbols which look like this: going to insmod e100.o (path is NULL) /tmp/e100.o: unresolved symbol __kfree_skb_R047ef26a /tmp/e100.o: unresolved symbol __netdev_watchdog_up_R1bbf5ccf /tmp/e100.o: unresolved symbol skb_over_panic_R11ebe673 then you didn't configure your kernel source correctly for the running kernel. But, if you get errors like the ones you mention above, e100.o depends on another module which is not included in the initrd. You need to figure out what that other module (or modules) is and include it in the initrd. Or maybe there's something which needs to be turned on in the kernel. Chris -- cmalek@xxxxxxxxxxx Nosce Teipsum Office: (626) 395-2593 Fax: (626) 792-4257 Mail Stop: 014-81
