LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian
User Name
Password
Debian This forum is for the discussion of Debian Linux.

Notices

Reply
 
Search this Thread
Old 10-07-2003, 09:40 AM   #1
Gilion
Member
 
Registered: Sep 2003
Location: Netherlands
Distribution: Debian 3.0
Posts: 78

Rep: Reputation: 15
3 repeating boot time messages


After a fresh potato install I upgraded to woody with a 2.4.18 kernel. Everything works, but booting takes a while. During reboot the calculation of the module dependencies alone takes about 1 minute. Also the following 3 messages are repeated a couple of times:

insmod: NOTE: /etc/modules.conf is more recent than /lib/modules/2.4.18-1-386/modules.dep

Depmod: ** unresolved symbol in binfmt_aout.o

/etc/mtab: No such file or directory

I guess these messages indicate the cause for the slow boot. Now my question is, off course, how to get rid of these problems.

Gilion
 
Old 10-07-2003, 10:35 AM   #2
ToniT
Senior Member
 
Registered: Oct 2003
Location: Zurich, Switzerland
Distribution: Debian/unstable
Posts: 1,357

Rep: Reputation: 47
The time used to dependency resolving can be redused quite a lot by compiling a kernel that contains only support for your hardware.

To compile a kernel in debian, you need to
Code:
apt-get install kernel-source-2.4.XX kernel-package build-essential
(replace XX with your favorite version)

and read the /usr/share/doc/kernel-package/README.gz

For the unresolved symbols: get rid ot the aout-format support.

in case of /etc/mtab, updating of mount-package might help.
Or you can try to make /etc/mtab to be a symlink to /proc/mounts.
 
Old 10-08-2003, 03:48 AM   #3
pe2338
Member
 
Registered: Dec 2002
Location: Bucharest,RO
Distribution: debian etch, sarge and sid
Posts: 407

Rep: Reputation: 30
Re: 3 repeating boot time messages

Quote:
Originally posted by Gilion

[.....]
insmod: NOTE: /etc/modules.conf is more recent than /lib/modules/2.4.18-1-386/modules.dep
[.....]
Depmod: ** unresolved symbol in binfmt_aout.o
[.....]
/etc/mtab: No such file or directory
[.....]
there are 2 problems here....
1. the "etc/modules.conf is more recent than /lib/modules/2.4.18-1-386/modules.dep" section indicates you will have to do a
Code:
#update-modules
or 
#update-modules.modutils
first variant is to be used if you have manually modified the /etc/modules file.
second is if you didn't, or you made modifications through /etc/modutils/* files (the right way in debian)



2.maybe you have read-only permisions on your /etc/mtab file or you don't have it at all.
variant 1:
Code:
#chmod o+rw /etc/mtab
variant 2:
Code:
#touch /etc/mtab
#chmod o+rw /etc/mtab
good luck.

And tell us if you solved the problem.... or not
 
Old 10-08-2003, 06:30 AM   #4
Gilion
Member
 
Registered: Sep 2003
Location: Netherlands
Distribution: Debian 3.0
Posts: 78

Original Poster
Rep: Reputation: 15
I read somewhere that compiling kernels on i486 with 8Mb RAM can take hours, so I don't like that solution. Compiling kernels at each hardware change would cost a lot of time.

Can you be more specific about the aout format. What is it and where can I find info on how to remove it? Stuff like that.

For /etc/mtab reinstalling the mount package and chmod-ing the file didn't change anything. /etc/mtab seems to be generated over and over during reboot, changing permision again.

Also update-modules.modutils does not exist. Update-modules does exist, but doesn't change the booting error. When I change i.e. /etc/modutils/ne and run update-modules these changes appear in modules.conf like I intended.

Something which crossed my minds, should I worry about these messages?

Gilion
 
Old 10-08-2003, 10:53 AM   #5
ToniT
Senior Member
 
Registered: Oct 2003
Location: Zurich, Switzerland
Distribution: Debian/unstable
Posts: 1,357

Rep: Reputation: 47
Well,

I wouldn't stress too much about those messages.
There was a discussion at the debian-user list few years ago about the subject. Seems like nobody nows exactly what is wrong in the module handling.

The aout-stuff was somewhat fixing the sympons than the real probmem. Meaning that if you remove (move away, so you can return it back if you find you need it) the binfmt_aout.o module from /lib/modules/kernversion/ somewhere, then it can't complain about it having some strange symbols to be resolved.

The 1 minute dependency checkking is the price to be paid from the dynamic kernel.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Mulitple Problems at boot(processes repeating, alsa, usb) h1tman Slackware 0 11-03-2004 03:55 PM
Remotely viewing boot messages during boot? flysideways Linux - Networking 6 05-11-2004 02:35 PM
Error messages at boot time ICO Slackware 3 01-30-2004 04:37 AM
Burn syslog messages in real time? OlRoy Linux - Security 3 05-28-2003 08:06 PM
boot time messages adam171771 Programming 3 05-10-2001 07:14 PM


All times are GMT -5. The time now is 01:31 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration