RE: Log Errors
Yea, you're probably right. Why would they put sound options under "Sound". Thats too obvious. Sheesh. Brian > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Mike Andrew > Sent: Friday, March 22, 2002 6:22 PM > To: [EMAIL PROTECTED] > Subject: Re: Log Errors > > > > From: "Brian Witowski" <[EMAIL PROTECTED]> > > > One more note, I'm using grub, not lilo. > > uname -r will determine if you've configured grub correctly in context to > the kernel you think you've booted. Bottom line is that you missed a few > non-obvious options on the kernel compile. > > > > > ___ Linux-users mailing list - http://linux-sxs.org/mailman/listinfo/linux-users Subscribe/Unsubscribe info, Archives,and Digests are located at the above URL.
Re: Log Errors
From: "Brian Witowski" <[EMAIL PROTECTED]> > One more note, I'm using grub, not lilo. uname -r will determine if you've configured grub correctly in context to the kernel you think you've booted. Bottom line is that you missed a few non-obvious options on the kernel compile. ___ Linux-users mailing list - http://linux-sxs.org/mailman/listinfo/linux-users Subscribe/Unsubscribe info, Archives,and Digests are located at the above URL.
RE: Log Errors
One more note, I'm using grub, not lilo. Brian > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Mike Andrew > Sent: Friday, March 22, 2002 12:13 AM > To: [EMAIL PROTECTED] > Subject: Re: Log Errors > > > > --- Brian Witowski <[EMAIL PROTECTED]> wrote: > > > Where is it determined that it would be looking in > > > /lib/modules/2.4.2... > > From: "Net Llama" <[EMAIL PROTECTED]> > > > Well, Caldera has an ass-backwards modutils, which i believe looks in > > /etc/modules/default > > I've been following this thread. It would seem to me that you are not > booting the kernel you think you are, OR, you never booted the > (new) kernel > that you previously thought you did. And the answer is really simple, you > did some minor thing to make things different just a few days > ago, only you > can't (obviously) see the connection between the events because you're > assuming, quite wrongly as it turns out, that the compile went > 'ok', it did > not, and ama hit the target first time because all messages > about unable > to find a heap of char major anythings are kernel miscompiles. More > correctly: it's symptomatic of not including some kernel options in an > otherwise good compile. > > first thing to do is > > uname -r > > this will tell you unreservedly THE kernel you have currently booted. > Chances are high that you have a misconfigured lilo.conf (not > having a shot > at you, am covering some non-obvious bases). > > To answer your above question, kernd (the kernel module daemon within the > kernel) passes requests to modprobe to find it's modules. It is modprobe > which determines which /lib/path to use. It is fixed in concrete that it > will be /lib/modules/, unless specifically over-ridden > (as likely > as hell freezing over). > > Caldera's /etc/modules is chalk and cheese, /etc/modules/ is > simply a (very > sensible) method of supplying a one-stop shop for ALL modules to be loaded > at boot time, it is a look-up list written against Caldera's > version of the > /etc/rc.d/sysinit scripts, not _the_ modules, and is agnostic to kernel > versions (again, unless hell freezes over, Col 2.2 is version > sensitive, the > others are not). > > Using poetic licence, the actual modules created are derived from > /usr/src/linux//modules. This directory is created on > the fly from > /usr/src/linux//drivers during compile time (and destroyed at > 'make modules" incantation). > > 'make modules_install' copies these binaries to the correct > /lib/modules/ path and then runs a fudged depmod -a to > correctly sync this stuff. That bit has never worked as advertised for > reasons no-one has ever been able to explain to me. As a result, > all distros > I am aware of run a hidden depmod -a at boot time. Each distro > hides this in > a different way, but the end result is identical, depmod (the modprobe > generator) _guarantees_ that the modules the booted kernel wants, are > indexed correctly. 'Correctly' means depmod is going to scream > blue murder, > at boot time, if it can't find THE location of _the_ kernel > version modules. > That doesn't mean all modules are 'ok' it means it can find them. So to > answer a question you were thinking, there is no way on the planet that > kernel-2.4.18 will use anything other than /lib/modules/2.4.18. > And contra, > no way on earth kernel 2.4.10 will use 2.4.18 compiled modules (There are > if's and but's to that statement, but you can take it at face value). > > As far as deleting /usr/src/anything, the answer is: irrelevant to the > problem. /usr/src/linux is not used at any time by the kernel or it's > friends. It is simply a convenient hole in the ground to compile, > well gee, > user / source. Anything required from /usr/src/ is, as stated > above, copied > out of there, in the expectation that you will indeed delete /usr/src at > some future date. > > To get back to Lama's original reply, he is spot on. You don't > in fact have an issue with any of the above, it will all work as > advertised > and you aint gone done broken it. The truth is, you've missed out a few > options on the compile. See the SxS which contains fairly bullet proof gif > images of each dialog box during 'make xconfig', or, use Keith's equally > good text based version. > > > > ___ Linux-users mailing list - http://linux-sxs.org/mailman/listinfo/linux-users Subscribe/Unsubscribe info, Archives,and Digests are located at the above URL.
RE: Log Errors
Mike, Thanks for that explanation! Most of the docs out there tell you what to do and when to do it but they don't tell you why! I need to know the 'nuts and bolts'. Once I know that, I can fix anything myself. I am indeed running 2.4.18. I recompiled my kernel last night and went through xconfig slowly and deliberately. And guess what? Even though I didn't compile in sound, I was getting a char-major-14 error in my logs. I read at another site on the web that even though sound isn't compiled in, it will generate those errors if an application attempts to use sound. It also advised putting 'alias char-major-14 off' in my modules.conf file to stop the error from appearing in my logs. Now that is something nobody else ever suggested. An app would try to use sound, which would in turn try to load a module that didn't exist and thus create an error. The end result being there is nothing wrong with my kernel or the way I compiled it. That of course doesn't explain all of the errors (the rtc thing was my fault) but it does suggest we shouldn't jump to 'compile errors' as a first resort. Thanks again for your detailed explanation. Brian > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Mike Andrew > Sent: Friday, March 22, 2002 12:13 AM > To: [EMAIL PROTECTED] > Subject: Re: Log Errors > > > > --- Brian Witowski <[EMAIL PROTECTED]> wrote: > > > Where is it determined that it would be looking in > > > /lib/modules/2.4.2... > > From: "Net Llama" <[EMAIL PROTECTED]> > > > Well, Caldera has an ass-backwards modutils, which i believe looks in > > /etc/modules/default > > I've been following this thread. It would seem to me that you are not > booting the kernel you think you are, OR, you never booted the > (new) kernel > that you previously thought you did. And the answer is really simple, you > did some minor thing to make things different just a few days > ago, only you > can't (obviously) see the connection between the events because you're > assuming, quite wrongly as it turns out, that the compile went > 'ok', it did > not, and ama hit the target first time because all messages > about unable > to find a heap of char major anythings are kernel miscompiles. More > correctly: it's symptomatic of not including some kernel options in an > otherwise good compile. > > first thing to do is > > uname -r > > this will tell you unreservedly THE kernel you have currently booted. > Chances are high that you have a misconfigured lilo.conf (not > having a shot > at you, am covering some non-obvious bases). > > To answer your above question, kernd (the kernel module daemon within the > kernel) passes requests to modprobe to find it's modules. It is modprobe > which determines which /lib/path to use. It is fixed in concrete that it > will be /lib/modules/, unless specifically over-ridden > (as likely > as hell freezing over). > > Caldera's /etc/modules is chalk and cheese, /etc/modules/ is > simply a (very > sensible) method of supplying a one-stop shop for ALL modules to be loaded > at boot time, it is a look-up list written against Caldera's > version of the > /etc/rc.d/sysinit scripts, not _the_ modules, and is agnostic to kernel > versions (again, unless hell freezes over, Col 2.2 is version > sensitive, the > others are not). > > Using poetic licence, the actual modules created are derived from > /usr/src/linux//modules. This directory is created on > the fly from > /usr/src/linux//drivers during compile time (and destroyed at > 'make modules" incantation). > > 'make modules_install' copies these binaries to the correct > /lib/modules/ path and then runs a fudged depmod -a to > correctly sync this stuff. That bit has never worked as advertised for > reasons no-one has ever been able to explain to me. As a result, > all distros > I am aware of run a hidden depmod -a at boot time. Each distro > hides this in > a different way, but the end result is identical, depmod (the modprobe > generator) _guarantees_ that the modules the booted kernel wants, are > indexed correctly. 'Correctly' means depmod is going to scream > blue murder, > at boot time, if it can't find THE location of _the_ kernel > version modules. > That doesn't mean all modules are 'ok' it means it can find them. So to > answer a question you were thinking, there is no way on the planet that > kernel-2.4.18 will use anything other than /lib/modules/2.4.18. > And contra, > no way on earth kernel 2.4.10 will use 2.4.18 compiled modules (There are > if's a
Re: Log Errors
> > --- Brian Witowski <[EMAIL PROTECTED]> wrote: > > > Where is it determined that it would be looking in > > > /lib/modules/2.4.2... > > From: "Net Llama" <[EMAIL PROTECTED]> > > > Well, Caldera has an ass-backwards modutils, which i believe looks in > > /etc/modules/default > I've been following this thread. It would seem to me that you are not booting the kernel you think you are, OR, you never booted the (new) kernel that you previously thought you did. And the answer is really simple, you did some minor thing to make things different just a few days ago, only you can't (obviously) see the connection between the events because you're assuming, quite wrongly as it turns out, that the compile went 'ok', it did not, and ama hit the target first time because all messages about unable to find a heap of char major anythings are kernel miscompiles. More correctly: it's symptomatic of not including some kernel options in an otherwise good compile. first thing to do is uname -r this will tell you unreservedly THE kernel you have currently booted. Chances are high that you have a misconfigured lilo.conf (not having a shot at you, am covering some non-obvious bases). To answer your above question, kernd (the kernel module daemon within the kernel) passes requests to modprobe to find it's modules. It is modprobe which determines which /lib/path to use. It is fixed in concrete that it will be /lib/modules/, unless specifically over-ridden (as likely as hell freezing over). Caldera's /etc/modules is chalk and cheese, /etc/modules/ is simply a (very sensible) method of supplying a one-stop shop for ALL modules to be loaded at boot time, it is a look-up list written against Caldera's version of the /etc/rc.d/sysinit scripts, not _the_ modules, and is agnostic to kernel versions (again, unless hell freezes over, Col 2.2 is version sensitive, the others are not). Using poetic licence, the actual modules created are derived from /usr/src/linux//modules. This directory is created on the fly from /usr/src/linux//drivers during compile time (and destroyed at 'make modules" incantation). 'make modules_install' copies these binaries to the correct /lib/modules/ path and then runs a fudged depmod -a to correctly sync this stuff. That bit has never worked as advertised for reasons no-one has ever been able to explain to me. As a result, all distros I am aware of run a hidden depmod -a at boot time. Each distro hides this in a different way, but the end result is identical, depmod (the modprobe generator) _guarantees_ that the modules the booted kernel wants, are indexed correctly. 'Correctly' means depmod is going to scream blue murder, at boot time, if it can't find THE location of _the_ kernel version modules. That doesn't mean all modules are 'ok' it means it can find them. So to answer a question you were thinking, there is no way on the planet that kernel-2.4.18 will use anything other than /lib/modules/2.4.18. And contra, no way on earth kernel 2.4.10 will use 2.4.18 compiled modules (There are if's and but's to that statement, but you can take it at face value). As far as deleting /usr/src/anything, the answer is: irrelevant to the problem. /usr/src/linux is not used at any time by the kernel or it's friends. It is simply a convenient hole in the ground to compile, well gee, user / source. Anything required from /usr/src/ is, as stated above, copied out of there, in the expectation that you will indeed delete /usr/src at some future date. To get back to Lama's original reply, he is spot on. You don't in fact have an issue with any of the above, it will all work as advertised and you aint gone done broken it. The truth is, you've missed out a few options on the compile. See the SxS which contains fairly bullet proof gif images of each dialog box during 'make xconfig', or, use Keith's equally good text based version. ___ Linux-users mailing list - http://linux-sxs.org/mailman/listinfo/linux-users Subscribe/Unsubscribe info, Archives,and Digests are located at the above URL.
Re: Log Errors
> --- Brian Witowski <[EMAIL PROTECTED]> wrote: > > Where is it determined that it would be looking in > > /lib/modules/2.4.2... From: "Net Llama" <[EMAIL PROTECTED]> > Well, Caldera has an ass-backwards modutils, which i believe looks in > /etc/modules/default I've been following this thread. It would seem to me that you are not booting the kernel you think you are, OR, you never booted the (new) kernel that you previously thought you did. And the answer is really simple, you did some minor thing to make things different just a few days ago, only you can't (obviously) see the connection between the events because you're assuming, quite wrongly as it turns out, that the compile went 'ok', it did not, and ama hit the target first time because all messages about unable to find a heap of char major anythings are kernel miscompiles. More correctly: it's symptomatic of not including some kernel options in an otherwise good compile. first thing to do is uname -r this will tell you unreservedly THE kernel you have currently booted. Chances are high that you have a misconfigured lilo.conf (not having a shot at you, am covering some non-obvious bases). To answer your above question, kernd (the kernel module daemon within the kernel) passes requests to modprobe to find it's modules. It is modprobe which determines which /lib/path to use. It is fixed in concrete that it will be /lib/modules/, unless specifically over-ridden (as likely as hell freezing over). Caldera's /etc/modules is chalk and cheese, /etc/modules/ is simply a (very sensible) method of supplying a one-stop shop for ALL modules to be loaded at boot time, it is a look-up list written against Caldera's version of the /etc/rc.d/sysinit scripts, not _the_ modules, and is agnostic to kernel versions (again, unless hell freezes over, Col 2.2 is version sensitive, the others are not). Using poetic licence, the actual modules created are derived from /usr/src/linux//modules. This directory is created on the fly from /usr/src/linux//drivers during compile time (and destroyed at 'make modules" incantation). 'make modules_install' copies these binaries to the correct /lib/modules/ path and then runs a fudged depmod -a to correctly sync this stuff. That bit has never worked as advertised for reasons no-one has ever been able to explain to me. As a result, all distros I am aware of run a hidden depmod -a at boot time. Each distro hides this in a different way, but the end result is identical, depmod (the modprobe generator) _guarantees_ that the modules the booted kernel wants, are indexed correctly. 'Correctly' means depmod is going to scream blue murder, at boot time, if it can't find THE location of _the_ kernel version modules. That doesn't mean all modules are 'ok' it means it can find them. So to answer a question you were thinking, there is no way on the planet that kernel-2.4.18 will use anything other than /lib/modules/2.4.18. And contra, no way on earth kernel 2.4.10 will use 2.4.18 compiled modules (There are if's and but's to that statement, but you can take it at face value). As far as deleting /usr/src/anything, the answer is: irrelevant to the problem. /usr/src/linux is not used at any time by the kernel or it's friends. It is simply a convenient hole in the ground to compile, well gee, user / source. Anything required from /usr/src/ is, as stated above, copied out of there, in the expectation that you will indeed delete /usr/src at some future date. To get back to Lama's original reply, he is spot on. You don't in fact have an issue with any of the above, it will all work as advertised and you aint gone done broken it. The truth is, you've missed out a few options on the compile. See the SxS which contains fairly bullet proof gif images of each dialog box during 'make xconfig', or, use Keith's equally good text based version. ___ Linux-users mailing list - http://linux-sxs.org/mailman/listinfo/linux-users Subscribe/Unsubscribe info, Archives,and Digests are located at the above URL.
RE: Log Errors
Ill try it... > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Tim Wunder > Sent: Tuesday, March 19, 2002 10:04 AM > To: [EMAIL PROTECTED] > Subject: Re: Log Errors > > > Could fixing this be as simple as executing > depmod -ae > ?? > > Tim > > Net Llama wrote: > > Well, Caldera has an ass-backwards modutils, which i believe looks in > > /etc/modules/default > > Did you grab a new copy of modutils? > > > > --- Brian Witowski <[EMAIL PROTECTED]> wrote: > > > >>Yes, I had rebooted. And the only thing I did that I can think of is > >>I > >>deleted my /usr/src/linux-2.4.2 directory because I had upgraded my > >>kernel > >>to 2.4.18. > >> > >>Where is it determined that it would be looking in > >>/lib/modules/2.4.2... > >>rather that /lib/modules/2.4.18? Are the modules placed in the > >>modules > >>directory at compile time? I checked my logs for yesterday and the > >>only > >>error was the rtc.o error. > >> > >>I'm still trying to get a handle on how the various directories are > >>created > >>and how the various files are called. Once I have a firm > >>understanding of > >>that, it will be easier to troubleshoot myself. > >> > >> > >>Thanks, > >>Brian > >> > >> > >>>What did you do as root on March 16? Had you rebooted between when > >> > >>you > >> > >>>built the kernel & March 16? > >>> > >> > >> > Mar 16 10:06:21 server insmod: > >> > /lib/modules//2.4.2/kernel/drivers/scsi/scsi_mod.o: insmod > >> > block-major-8 > >> > failed > >> > >> > Those are SCSI drives (sda etc). > >> > >> > >>>Mar 16 10:06:22 server last message repeated 15 times > >>>Mar 16 20:34:17 server insmod: > >> > >> > /lib/modules//2.4.2/kernel/drivers/sound/soundcore.o: insmod > >> > >>>char-major-14 > >>>failed > >> > >>>Sound devices (/dev/mixer etc) > >> > >>>Mar 18 09:41:02 server insmod: > >>>/lib/modules//2.4.2/kernel/drivers/char/rtc.o: insmod > >>>char-major-10-135 > >>>failed > >> > > > > = > > > > Lonni J. Friedman [EMAIL PROTECTED] > > > > Linux Step-by-step help: http://netllama.ipfox.com > > > > . > > > > __ > > Do You Yahoo!? > > Yahoo! Sports - live college hoops coverage > > http://sports.yahoo.com/ > > ___ > > Linux-users mailing list - > http://linux-sxs.org/mailman/listinfo/linux-users > > Subscribe/Unsubscribe info, Archives,and Digests are located at > the above URL. > > > > > > ___ Linux-users mailing list - http://linux-sxs.org/mailman/listinfo/linux-users Subscribe/Unsubscribe info, Archives,and Digests are located at the above URL.
RE: Log Errors
Yes, and it's installed. brian > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Net Llama > Sent: Tuesday, March 19, 2002 9:50 AM > To: [EMAIL PROTECTED] > Subject: RE: Log Errors > > > Well, Caldera has an ass-backwards modutils, which i believe looks in > /etc/modules/default > Did you grab a new copy of modutils? > > --- Brian Witowski <[EMAIL PROTECTED]> wrote: > > Yes, I had rebooted. And the only thing I did that I can think of is > > I > > deleted my /usr/src/linux-2.4.2 directory because I had upgraded my > > kernel > > to 2.4.18. > > > > Where is it determined that it would be looking in > > /lib/modules/2.4.2... > > rather that /lib/modules/2.4.18? Are the modules placed in the > > modules > > directory at compile time? I checked my logs for yesterday and the > > only > > error was the rtc.o error. > > > > I'm still trying to get a handle on how the various directories are > > created > > and how the various files are called. Once I have a firm > > understanding of > > that, it will be easier to troubleshoot myself. > > > > > > Thanks, > > Brian > > > > > > > > What did you do as root on March 16? Had you rebooted between when > > you > > > built the kernel & March 16? > > > > > > Mar 16 10:06:21 server insmod: > > > /lib/modules//2.4.2/kernel/drivers/scsi/scsi_mod.o: insmod > > > block-major-8 > > > failed > > > > > Those are SCSI drives (sda etc). > > > > > Mar 16 10:06:22 server last message repeated 15 times > > > Mar 16 20:34:17 server insmod: > > > /lib/modules//2.4.2/kernel/drivers/sound/soundcore.o: insmod > > > char-major-14 > > > failed > > > > > Sound devices (/dev/mixer etc) > > > > > Mar 18 09:41:02 server insmod: > > > /lib/modules//2.4.2/kernel/drivers/char/rtc.o: insmod > > > char-major-10-135 > > > failed > > = > > Lonni J. Friedman [EMAIL PROTECTED] > > Linux Step-by-step help: http://netllama.ipfox.com > > . > > __ > Do You Yahoo!? > Yahoo! Sports - live college hoops coverage > http://sports.yahoo.com/ > ___ Linux-users mailing list - http://linux-sxs.org/mailman/listinfo/linux-users Subscribe/Unsubscribe info, Archives,and Digests are located at the above URL.
Re: Log Errors
On Tue, 19 Mar 2002 06:50:07 -0800 (PST) begin Net Llama <[EMAIL PROTECTED]> spewed forth: > Well, Caldera has an ass-backwards modutils, which i believe looks in > /etc/modules/default > Did you grab a new copy of modutils? > /etc/modules/default has _nothing_ whatsoever to do with modutils (or vice versa). /etc/modules/default is called during boot from /etc/rc.d/rc.modules. Other distros do something else (Debian uses /etc/modules which contains the same info as /etc/modules/default), and RH does pure dynamic loading. modutils provides standard modules utilities which look at /etc/modules.conf. Now Caldera has managed to break /etc/modules.conf with idiotic directives that need to be removed, but they have nothing to do with /etc/modules/default. So there's nothing ass-backwards about Caldera's modutils. It's the same as everyone else's. Ciao, David A. Bandel -- Focus on the dream, not the competition. -- Nemesis Racing Team motto Internet (H323) phone: 206.28.187.30 ___ Linux-users mailing list - http://linux-sxs.org/mailman/listinfo/linux-users Subscribe/Unsubscribe info, Archives,and Digests are located at the above URL.
Re: Log Errors
Possibly, although my understanding was that command is run when you do 'make modules_install' during the kernel build. --- Tim Wunder <[EMAIL PROTECTED]> wrote: > Could fixing this be as simple as executing > depmod -ae > ?? > > Tim > > Net Llama wrote: > > Well, Caldera has an ass-backwards modutils, which i believe looks > in > > /etc/modules/default > > Did you grab a new copy of modutils? > > > > --- Brian Witowski <[EMAIL PROTECTED]> wrote: > > > >>Yes, I had rebooted. And the only thing I did that I can think of > is > >>I > >>deleted my /usr/src/linux-2.4.2 directory because I had upgraded my > >>kernel > >>to 2.4.18. > >> > >>Where is it determined that it would be looking in > >>/lib/modules/2.4.2... > >>rather that /lib/modules/2.4.18? Are the modules placed in the > >>modules > >>directory at compile time? I checked my logs for yesterday and the > >>only > >>error was the rtc.o error. > >> > >>I'm still trying to get a handle on how the various directories are > >>created > >>and how the various files are called. Once I have a firm > >>understanding of > >>that, it will be easier to troubleshoot myself. > >> > >> > >>Thanks, > >>Brian > >> > >> > >>>What did you do as root on March 16? Had you rebooted between when > >> > >>you > >> > >>>built the kernel & March 16? > >>> > >> > >> > Mar 16 10:06:21 server insmod: > >> > /lib/modules//2.4.2/kernel/drivers/scsi/scsi_mod.o: insmod > >> > block-major-8 > >> > failed > >> > >> > Those are SCSI drives (sda etc). > >> > >> > >>>Mar 16 10:06:22 server last message repeated 15 times > >>>Mar 16 20:34:17 server insmod: > >> > >> > /lib/modules//2.4.2/kernel/drivers/sound/soundcore.o: insmod > >> > >>>char-major-14 > >>>failed > >> > >>>Sound devices (/dev/mixer etc) > >> > >>>Mar 18 09:41:02 server insmod: > >>>/lib/modules//2.4.2/kernel/drivers/char/rtc.o: insmod > >>>char-major-10-135 > >>>failed = Lonni J. Friedman [EMAIL PROTECTED] Linux Step-by-step help: http://netllama.ipfox.com . __ Do You Yahoo!? Yahoo! Sports - live college hoops coverage http://sports.yahoo.com/ ___ Linux-users mailing list - http://linux-sxs.org/mailman/listinfo/linux-users Subscribe/Unsubscribe info, Archives,and Digests are located at the above URL.
Re: Log Errors
Could fixing this be as simple as executing depmod -ae ?? Tim Net Llama wrote: > Well, Caldera has an ass-backwards modutils, which i believe looks in > /etc/modules/default > Did you grab a new copy of modutils? > > --- Brian Witowski <[EMAIL PROTECTED]> wrote: > >>Yes, I had rebooted. And the only thing I did that I can think of is >>I >>deleted my /usr/src/linux-2.4.2 directory because I had upgraded my >>kernel >>to 2.4.18. >> >>Where is it determined that it would be looking in >>/lib/modules/2.4.2... >>rather that /lib/modules/2.4.18? Are the modules placed in the >>modules >>directory at compile time? I checked my logs for yesterday and the >>only >>error was the rtc.o error. >> >>I'm still trying to get a handle on how the various directories are >>created >>and how the various files are called. Once I have a firm >>understanding of >>that, it will be easier to troubleshoot myself. >> >> >>Thanks, >>Brian >> >> >>>What did you do as root on March 16? Had you rebooted between when >> >>you >> >>>built the kernel & March 16? >>> >> >> > Mar 16 10:06:21 server insmod: >> > /lib/modules//2.4.2/kernel/drivers/scsi/scsi_mod.o: insmod >> > block-major-8 >> > failed >> >> > Those are SCSI drives (sda etc). >> >> >>>Mar 16 10:06:22 server last message repeated 15 times >>>Mar 16 20:34:17 server insmod: >> >> > /lib/modules//2.4.2/kernel/drivers/sound/soundcore.o: insmod >> >>>char-major-14 >>>failed >> >>>Sound devices (/dev/mixer etc) >> >>>Mar 18 09:41:02 server insmod: >>>/lib/modules//2.4.2/kernel/drivers/char/rtc.o: insmod >>>char-major-10-135 >>>failed >> > > = > > Lonni J. Friedman [EMAIL PROTECTED] > > Linux Step-by-step help: http://netllama.ipfox.com > > . > > __ > Do You Yahoo!? > Yahoo! Sports - live college hoops coverage > http://sports.yahoo.com/ > ___ > Linux-users mailing list - http://linux-sxs.org/mailman/listinfo/linux-users > Subscribe/Unsubscribe info, Archives,and Digests are located at the above URL. > ___ Linux-users mailing list - http://linux-sxs.org/mailman/listinfo/linux-users Subscribe/Unsubscribe info, Archives,and Digests are located at the above URL.
RE: Log Errors
Well, Caldera has an ass-backwards modutils, which i believe looks in /etc/modules/default Did you grab a new copy of modutils? --- Brian Witowski <[EMAIL PROTECTED]> wrote: > Yes, I had rebooted. And the only thing I did that I can think of is > I > deleted my /usr/src/linux-2.4.2 directory because I had upgraded my > kernel > to 2.4.18. > > Where is it determined that it would be looking in > /lib/modules/2.4.2... > rather that /lib/modules/2.4.18? Are the modules placed in the > modules > directory at compile time? I checked my logs for yesterday and the > only > error was the rtc.o error. > > I'm still trying to get a handle on how the various directories are > created > and how the various files are called. Once I have a firm > understanding of > that, it will be easier to troubleshoot myself. > > > Thanks, > Brian > > > > > What did you do as root on March 16? Had you rebooted between when > you > > built the kernel & March 16? > > > > Mar 16 10:06:21 server insmod: > > /lib/modules//2.4.2/kernel/drivers/scsi/scsi_mod.o: insmod > > block-major-8 > > failed > > > Those are SCSI drives (sda etc). > > > Mar 16 10:06:22 server last message repeated 15 times > > Mar 16 20:34:17 server insmod: > > /lib/modules//2.4.2/kernel/drivers/sound/soundcore.o: insmod > > char-major-14 > > failed > > > Sound devices (/dev/mixer etc) > > > Mar 18 09:41:02 server insmod: > > /lib/modules//2.4.2/kernel/drivers/char/rtc.o: insmod > > char-major-10-135 > > failed = Lonni J. Friedman [EMAIL PROTECTED] Linux Step-by-step help: http://netllama.ipfox.com . __ Do You Yahoo!? Yahoo! Sports - live college hoops coverage http://sports.yahoo.com/ ___ Linux-users mailing list - http://linux-sxs.org/mailman/listinfo/linux-users Subscribe/Unsubscribe info, Archives,and Digests are located at the above URL.
RE: Log Errors
Yes, I had rebooted. And the only thing I did that I can think of is I deleted my /usr/src/linux-2.4.2 directory because I had upgraded my kernel to 2.4.18. Where is it determined that it would be looking in /lib/modules/2.4.2... rather that /lib/modules/2.4.18? Are the modules placed in the modules directory at compile time? I checked my logs for yesterday and the only error was the rtc.o error. I'm still trying to get a handle on how the various directories are created and how the various files are called. Once I have a firm understanding of that, it will be easier to troubleshoot myself. Thanks, Brian > > What did you do as root on March 16? Had you rebooted between when you > built the kernel & March 16? > > Mar 16 10:06:21 server insmod: > /lib/modules//2.4.2/kernel/drivers/scsi/scsi_mod.o: insmod > block-major-8 > failed > Those are SCSI drives (sda etc). > Mar 16 10:06:22 server last message repeated 15 times > Mar 16 20:34:17 server insmod: > /lib/modules//2.4.2/kernel/drivers/sound/soundcore.o: insmod > char-major-14 > failed > Sound devices (/dev/mixer etc) > Mar 18 09:41:02 server insmod: > /lib/modules//2.4.2/kernel/drivers/char/rtc.o: insmod > char-major-10-135 > failed ___ Linux-users mailing list - http://linux-sxs.org/mailman/listinfo/linux-users Subscribe/Unsubscribe info, Archives,and Digests are located at the above URL.
RE: Log Errors
What did you do as root on March 16? Had you rebooted between when you built the kernel & March 16? --- Brian Witowski <[EMAIL PROTECTED]> wrote: > What you're saying makes sense except I built the new kernel about a > week > ago or more and these errors only show up on March 16. In addition to > the > kernel itself and modules.conf, where eles could modules be called > from? > > Brian > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]On Behalf Of Net Llama > > Sent: Monday, March 18, 2002 12:09 PM > > To: [EMAIL PROTECTED] > > Subject: Re: Log Errors > > > > > > --- Brian Witowski <[EMAIL PROTECTED]> wrote: > > > Hello, > > > > > > I am getting the following errors in my logs. As near as I can > tell, > > > I > > > didn't have these until I upgraded to the latest modutils module: > > > > > > Mar 16 10:06:21 server modprobe: modprobe: Can't locate module > > > block-major-33 > > > Mar 16 10:06:21 server modprobe: modprobe: Can't locate module > > > block-major-33 > > > > That's the 3rd IDE channel (hde/hdf). Do you have 3 IDE channels? > > > > > Mar 16 10:06:21 server modprobe: modprobe: Can't locate module > > > block-major-34 > > > Mar 16 10:06:21 server modprobe: modprobe: Can't locate module > > > block-major-34 > > > > That's the 4th IDE channel. Sounds like you built something into > the > > kernel that you shouldn't have. > > > > > Mar 16 10:06:21 server insmod: > > > /lib/modules//2.4.2/kernel/drivers/scsi/scsi_mod.o: insmod > > > block-major-8 > > > failed > > > > Those are SCSI drives (sda etc). > > > > > Mar 16 10:06:22 server last message repeated 15 times > > > Mar 16 20:34:17 server insmod: > > > /lib/modules//2.4.2/kernel/drivers/sound/soundcore.o: insmod > > > char-major-14 > > > failed > > > > Sound devices (/dev/mixer etc) > > > > > Mar 18 09:41:02 server insmod: > > > /lib/modules//2.4.2/kernel/drivers/char/rtc.o: insmod > > > char-major-10-135 > > > failed > > > > /dev/rtc - Real time clock support, which you didn't built properly, > i'm > > guessing. > > > > > > > > These are not necessarily in sequence. Here is my modules.conf > file: > > > Note that I don't use sound nor SCSI. I would like to remedy > these > > > errors. > > > > Considering how about 50% of the lines are commented out, why don't > you > > remove them altogether? Also, just because you don't use sound or > SCSI, > > doesn't mean that you didn't say Y to stuff that requires them in > the > > kernel config. = Lonni J. Friedman [EMAIL PROTECTED] Linux Step-by-step help: http://netllama.ipfox.com . __ Do You Yahoo!? Yahoo! Sports - live college hoops coverage http://sports.yahoo.com/ ___ Linux-users mailing list - http://linux-sxs.org/mailman/listinfo/linux-users Subscribe/Unsubscribe info, Archives,and Digests are located at the above URL.
RE: Log Errors
What you're saying makes sense except I built the new kernel about a week ago or more and these errors only show up on March 16. In addition to the kernel itself and modules.conf, where eles could modules be called from? Brian > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Net Llama > Sent: Monday, March 18, 2002 12:09 PM > To: [EMAIL PROTECTED] > Subject: Re: Log Errors > > > --- Brian Witowski <[EMAIL PROTECTED]> wrote: > > Hello, > > > > I am getting the following errors in my logs. As near as I can tell, > > I > > didn't have these until I upgraded to the latest modutils module: > > > > Mar 16 10:06:21 server modprobe: modprobe: Can't locate module > > block-major-33 > > Mar 16 10:06:21 server modprobe: modprobe: Can't locate module > > block-major-33 > > That's the 3rd IDE channel (hde/hdf). Do you have 3 IDE channels? > > > Mar 16 10:06:21 server modprobe: modprobe: Can't locate module > > block-major-34 > > Mar 16 10:06:21 server modprobe: modprobe: Can't locate module > > block-major-34 > > That's the 4th IDE channel. Sounds like you built something into the > kernel that you shouldn't have. > > > Mar 16 10:06:21 server insmod: > > /lib/modules//2.4.2/kernel/drivers/scsi/scsi_mod.o: insmod > > block-major-8 > > failed > > Those are SCSI drives (sda etc). > > > Mar 16 10:06:22 server last message repeated 15 times > > Mar 16 20:34:17 server insmod: > > /lib/modules//2.4.2/kernel/drivers/sound/soundcore.o: insmod > > char-major-14 > > failed > > Sound devices (/dev/mixer etc) > > > Mar 18 09:41:02 server insmod: > > /lib/modules//2.4.2/kernel/drivers/char/rtc.o: insmod > > char-major-10-135 > > failed > > /dev/rtc - Real time clock support, which you didn't built properly, i'm > guessing. > > > > > These are not necessarily in sequence. Here is my modules.conf file: > > Note that I don't use sound nor SCSI. I would like to remedy these > > errors. > > Considering how about 50% of the lines are commented out, why don't you > remove them altogether? Also, just because you don't use sound or SCSI, > doesn't mean that you didn't say Y to stuff that requires them in the > kernel config. > > = > > Lonni J. Friedman [EMAIL PROTECTED] > > Linux Step-by-step help: http://netllama.ipfox.com > > . > > __ > Do You Yahoo!? > Yahoo! Sports - live college hoops coverage > http://sports.yahoo.com/ > ___ Linux-users mailing list - http://linux-sxs.org/mailman/listinfo/linux-users Subscribe/Unsubscribe info, Archives,and Digests are located at the above URL.
Re: Log Errors
--- Brian Witowski <[EMAIL PROTECTED]> wrote: > Hello, > > I am getting the following errors in my logs. As near as I can tell, > I > didn't have these until I upgraded to the latest modutils module: > > Mar 16 10:06:21 server modprobe: modprobe: Can't locate module > block-major-33 > Mar 16 10:06:21 server modprobe: modprobe: Can't locate module > block-major-33 That's the 3rd IDE channel (hde/hdf). Do you have 3 IDE channels? > Mar 16 10:06:21 server modprobe: modprobe: Can't locate module > block-major-34 > Mar 16 10:06:21 server modprobe: modprobe: Can't locate module > block-major-34 That's the 4th IDE channel. Sounds like you built something into the kernel that you shouldn't have. > Mar 16 10:06:21 server insmod: > /lib/modules//2.4.2/kernel/drivers/scsi/scsi_mod.o: insmod > block-major-8 > failed Those are SCSI drives (sda etc). > Mar 16 10:06:22 server last message repeated 15 times > Mar 16 20:34:17 server insmod: > /lib/modules//2.4.2/kernel/drivers/sound/soundcore.o: insmod > char-major-14 > failed Sound devices (/dev/mixer etc) > Mar 18 09:41:02 server insmod: > /lib/modules//2.4.2/kernel/drivers/char/rtc.o: insmod > char-major-10-135 > failed /dev/rtc - Real time clock support, which you didn't built properly, i'm guessing. > > These are not necessarily in sequence. Here is my modules.conf file: > Note that I don't use sound nor SCSI. I would like to remedy these > errors. Considering how about 50% of the lines are commented out, why don't you remove them altogether? Also, just because you don't use sound or SCSI, doesn't mean that you didn't say Y to stuff that requires them in the kernel config. = Lonni J. Friedman [EMAIL PROTECTED] Linux Step-by-step help: http://netllama.ipfox.com . __ Do You Yahoo!? Yahoo! Sports - live college hoops coverage http://sports.yahoo.com/ ___ Linux-users mailing list - http://linux-sxs.org/mailman/listinfo/linux-users Subscribe/Unsubscribe info, Archives,and Digests are located at the above URL.
