Bringing up interface eth0 error
 

Hi people i seem to be getting this error all the time

can any one tell me whats going on please ( OS is Trustix 2.1 )

On boot this error comes up when trying to load the eth0 from boot up screen

Bringing up interface eth0: modprode: Note /etc/modules.conf is more recent than
/ lib/modules/2.4.26-1trfirewall/modules.dep.

I tried do a touch / lib/modules/2.4.26-1trfirewall/modules.dep

and that didn't work, its say No such file or directory.

any one else had this program

TT

try "depmod -a"

Hi mate

whats a "depmod -a" do ?

I did try it and nothing happend, restarted and the error still shows

I aslo had the same problem on a Tiny Sofa OS, i also changed the network card..and the error comes up on both OS

TT

Strange, its suppose to update/generate the module dependencies file (ie modules.dep and the likes)
try running "depmod -v" and see what's happenning

I tried, but it didn't work, error still there.

I put the command in and it sits for a bit, then goes back to the promt.

then do a restart, error still there

TT

I got a USB card in there as well, would that cause any probs you reckon ?


My /etc/modules.conf

alias parport_lowlevel parport_pc
alias eth0 8139too
alias usb-controller usb-uhci
alias usb-controller1 usb-ohci

And in my /lib/modules folder i seem to have two folders one called ( 2.4.26-1tr ) and the other is ( 2.4.26-1trfirewall )


TT

that's not necessarily an error, just a notice.
I haven't used Trustix before but does it have some kind of init script that tries to automatically detect and configure hardware on boot?

Demonbane

I did that depmod -v thing you said
and the srceen scrolls with info, what am i looking for ?

TT

Nothing, just wanted to see if depmod is doing its job
The message should be harmless and safe to ignore, but if you're really annoyed try this cheap fix: add "depmod -a" to the script that brings up your eth0, before insmod/modprobe.

Its a big list, seem to be showing me things are starting up etc..

the file you are talking about is that here /etc/modules.conf

TT

this way be a dump question, would it have any thing to do with the date stamp ?

TT

Well people i dont know whats going on, I left the PC off over night, came back to it in the morning and it was still there, then i starter up the named server by doing a ( service named start ) and then a ( chckconfig named on ) to make sure it starts on boot and the eth0 error message is gone.

any one know why this happened ?

TT