On Sat, 2003-08-16 at 16:29, Pablo Manalastas wrote: > Under the 2.6.0 kernel, all modules have name *.ko, not the > old name *.o. Maybe you have to rename the module as a .ko > file. Also make sure that your modprobe (or insmod) is from the > new module-init-tools package and not the old modutils package. >
Sir, The .ko file is just a renamed .o, as you pointed out. However, this is only cosmetic-- the kernel loader will still load a .o file if it conforms to the new kernel module signature. As with the new module-init-tools, I have them. The problem really lies in the said binary-only module-- and I am out of my wits in trying to figure out how to kludge it. It'll be krufty, but as long as it works, it's fine with me. --- JM Ibanez [EMAIL PROTECTED] http://www.livejournal.com/~cyberlizard/ --- PL/1, "the fatal disease", belongs more to the problem set than to the solution set. -- E. W. Dijkstra ---
signature.asc
Description: This is a digitally signed message part
-- Philippine Linux Users' Group (PLUG) Mailing List [EMAIL PROTECTED] (#PLUG @ irc.free.net.ph) Official Website: http://plug.linux.org.ph Searchable Archives: http://marc.free.net.ph . To leave, go to http://lists.q-linux.com/mailman/listinfo/plug . Are you a Linux newbie? To join the newbie list, go to http://lists.q-linux.com/mailman/listinfo/ph-linux-newbie
