Very Computer

I have ReadHat 6.0, and just recompiled my kernel.
It boots until it gets to the
'finding module dependencies'
and then it hangs.
Any ideas why?
I did all of the steps coorectly with no errors.
I looked for info in the LDP, but couldn't
find what I needed.

Also, Anybody have problems with Gnome/Enlightenment being quirky?
For the second time, the panel crashed.  Now whenever I log back in, it
take several minutes for the screen to come up (instead of seconds)
and there is no panel. Same happens if I start a new panel.
IS there good documentation?  The included stuff isn't enough.
I still can't get programs like wmmon, wmifs, etc to come back when I
log in.

Thanks,
Chuck

messages
for very long.

--
+-------------------------------------------------+
|                Charles A. Cusack                |
|                 Graduate Student                |
|  Department of Computer Science and Engineering |
|         University of Nebraska-Lincoln          |
|                                                 |

+-------------------------------------------------+

You may

1) have forgotten to compile some important modules. Look in
/lib/modules/old.version and see what modules you have there that you
don't have in /lib/modules/new.version
2) have not installed the modules at all. Look in /lib/modules and see
if you have a directory for your version.
3) need to do a depmod -a version     where version is the actual
version you compiled (e.g. 2.2.5 or 2.2.9)

Silviu Minut

    - Matt Goheen

You may
1) have forgotten to compile some important modules. Look in /lib/modules/old.version and see what
modules you have there that you don't have in /lib/modules/new.version
2) have not installed the modules at all. Look in /lib/modules and see if you have a directory for
your version.
3) need to do a depmod -a version     where version is the actual version you compiled (e.g. 2.2.5
or 2.2.9)

I have ReadHat 6.0, and just recompiled my kernel.
It boots until it gets to the
'finding module dependencies'
and then it hangs.
Any ideas why?
I did all of the steps coorectly with no errors.
I looked for info in the LDP, but couldn't
find what I needed.

Quote:> 2) have not installed the modules at all. Look in /lib/modules and see if

Quote:> your version.
> 3) need to do a depmod -a version     where version is the actual version
you compiled (e.g.
> 2.2.5 or 2.2.9)

I get the problem too (btw - you can still boot with this problem by
pressing ctrl-c when it hangs at Finding Module Dependencies....) but I
cannot install my new modules.

I have enabled loadable modules support in my kernel (2.2.5), done make
bzImage and make modules - works fine. When I do make modules_install I get
the error:

make modules_install
ls: *.o: No such file or directory

If I then do a depmod -a 2.2.5-15 (as suggested above to fix this problem) I
get loads and loads of

/lib/modules/2.2.5-15/xxxx.o: unresolved symbol(s)

errors.

One note is that this is an upgrade install from redhat 5.2 with kernel
2.0.36....

Any ideas?

Dave.
--
David McMullen
Systems Engineer, SIG (Europe)

If there has already been a constructive solution posted to this genre
of problem, I apologise - my news feed does not seem to have picked it
up.

In my case, I have reinstalled redhat 6.0 from scratch a couple of times
and I have tried what seems like dozens of different combinations of
make menuconfig options and each kernel build has failed in the same
place - at the "finding module dependencies" stage of booting. I can't
rule out that I've done something stupid in selecting various 2.2.5-22
kernel options but having built many different (older) versions of the
kernel in the past, I've hopefully not done something wildly dumb.

When my kernel builds reach the "finding module dependencies" stage, the
hard drive hammers away for about another 5 seconds and then everything
stops. With one particular kernel configuration combination I tried (and
can't remember the options any more), after about 30 seconds, the system
reported a number of parsing errors in the module.dep file. depmod -a to
create a new version of this file didn't change this behaviour and
neither did make clean and rebuilding the same options - also the
manually created modules.dep file didn't have errors in the lines which
were alleged to have errors in them. After changing the particular
configuration again, I could never reproduce this behaviour - only the
hang at "finding module dependencies" :-)

I have also noticed that after a make modules_install, the
/lib/modules/2.2.5-22 directory contains lots of subdirectories and .o
files but there is no modules.dep file. Is the modules.dep file supposed
to be created after the first successful boot of the new kernel?

Has anybody been able to find the reason for this problem and propose a
solution?

Thanks,
Stefan Keller-Tuberg