Well, i havent tried yet to build own modules. If you try to, you must also have the apropriet/same kernel (vmlinuz) on the bootdisk if you take a another kernel. If you dont you get these version problems like you wrote. I think the best way is to get+unpack drvnet.img and maybe drvblock.img as described in my howto. you can do this also on any other linux distributions you maybe prefer(debian, gentoo, ...). if the module isnt on any of these images get kernel-BOOT-2.?.??-?.i386.rpm .. install it .. and you will find in /lib/modules/2.?.??-?BOOT/kernel/drivers your module. this should work also work on any linux distribution that uses rpm as package format (mandrake, suse, ...). Since i dont know (havent checked yet) whats further in that kernel-BOOT package, i cant give you any further tips. Maybe it unpacks also in /usr/src/linux-2.?.??-?BOOT where you can build your own kernel as you want. But well as i told .. i dont know it and i am to lazy to look now for it ;> OJ > Thanks for the writeup, it was informative. > > I have a (related) question: what is the best way to build modules for > a boot kernel when you DON'T have access to a machine running the same? > The module(s) that I've tried building invariably fail to load with version > conflicts. And the kernel that I built (to go with the module, in case that > works) failed to autodetect some hardware. :-( > > Thanks, > > Ajay > > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/kickstart-list >
