Messages in this thread | | | Subject | Re: 2.6.0 problems | From | Joshua Schmidlkofer <> | Date | Thu, 25 Dec 2003 21:09:48 -0800 |
| |
On Thu, 2003-12-25 at 17:07, dan@eglifamily.dnsalias.net wrote: > On Thu, 25 Dec 2003, Eric wrote: > > > On Thursday 25 December 2003 02:57 pm, dan@eglifamily.dnsalias.net wrote: > > > I grabbed the 2.6.0 code yesterday. But when I tried to compile a > > > modular kernel, I got a *LOT* of unresolved symbols in the modules. I'm > > > attaching the stderr output from depmod's run of make modules_install. > > I had this problem with a RH9 install. Instead of modutils, upgrade the the > > latest module-init-tools from ftp://kernel.org. > > The problem is that most of the module loading code has been moved from > > userspace to kernel code to make module loading more portable. Be sure to > > follow the upgrade instructions carefully. If done correctly it will keep > > your old modutils in case you load a 2.4.x kernel and will default to the new > > module-init-tools for 2.6.x kernels. > > I'll try that, thanks! > > Any ideas on the blank screen issue? > > --- Dan
I took module-init-tools out of Redhat Severn beta, and I upgraded init scripts, ethtool, and module-init-tools at the same time, it worked vary nicely.
-- VB programmers ask why no one takes them seriously, it's somewhat akin to a McDonalds manager asking employees why they don't take their 'career' seriously.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |