Re: Modules can't work after recompiling the kernel
On Sun, 24 Oct 2004 11:07:01 +0800, Lian Liming <[EMAIL PROTECTED]> wrote: > Hi all, > I am newbie to debian. I tried to recompile the kernel 2.6.8 following a > debian-kernel-how-to doc. > And now, i successfully install the new kernel and it can work. But the > problem now is that modules can't work on my new kernel system. > I get the error message when using the command "lsmod": > - > Module Size Used by Not tainted > lsmod: QM_MODULES: Function not implemented > - > Also got that error message "modprobe: QM_MODULES: Function not > implemented" when trying to use modprobe to enable modules. > I do select "Loadable module support" when compiling the kernel source. > > So what's wrong? > Do you have the module-init-tools package installed? Otherwise, check if you have enabled module support on your kernel config. Andrea P.S. what's wrong with the Debian binary kernel package? =) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Modules can't work after recompiling the kernel
Upgrade modutils to latest version. - Original Message - From: "Lian Liming" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, October 24, 2004 5:07 AM Subject: Modules can't work after recompiling the kernel > Hi all, > I am newbie to debian. I tried to recompile the kernel 2.6.8 following a > debian-kernel-how-to doc. > And now, i successfully install the new kernel and it can work. But the > problem now is that modules can't work on my new kernel system. > I get the error message when using the command "lsmod": > - > Module Size Used by Not tainted > lsmod: QM_MODULES: Function not implemented > - > Also got that error message "modprobe: QM_MODULES: Function not > implemented" when trying to use modprobe to enable modules. > I do select "Loadable module support" when compiling the kernel source. > > So what's wrong? > > Thank you for any suggestions! > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Modules can't work after recompiling the kernel
On Sun, 2004-10-24 at 11:07 +0800, Lian Liming wrote: > Hi all, > I am newbie to debian. I tried to recompile the kernel 2.6.8 following a > debian-kernel-how-to doc. > And now, i successfully install the new kernel and it can work. But the > problem now is that modules can't work on my new kernel system. > I get the error message when using the command "lsmod": > - > Module Size Used by Not tainted > lsmod: QM_MODULES: Function not implemented > - > Also got that error message "modprobe: QM_MODULES: Function not > implemented" when trying to use modprobe to enable modules. > I do select "Loadable module support" when compiling the kernel source. > > So what's wrong? > > Thank you for any suggestions! > > Update module-init-tools. -- Eric Gaumer <[EMAIL PROTECTED]> signature.asc Description: This is a digitally signed message part
Re: modules fail after apt-get upgrade
On Fri, Aug 06, 2004 at 09:33:45AM -0700, jeffd wrote: > Hi, > I'm wondering if the apt-get upgrade missed something, or if I am > missing something.. You fail to mention which kernel version you're using! If it is 2.6, make sure you update 'module-init-tools', and at the very least you run: depmod -a It appears that you're trying to load modules that are newer/older than the kernel version you're booting with. -- Thomas Adam -- "Frankly, Mr. Shankly, since you ask. You are a flatulent pain in the arse." -- Morrissey. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: modules not found after kernel recompile
On Mon, Jul 26, 2004 at 09:10:27PM +0200, [EMAIL PROTECTED] wrote: > > On Mon, 26 Jul 2004 10:42:37 -0600, "CW Harris" > <[EMAIL PROTECTED]> said: [...] > > > > Is this a typo? or are you using kernel 2.6.7 with an append-to-version > > of 1? I would recommend you use "-" (hyphen) before numeric > > append-to-version so the kernel version does not look wrong (i.e. there > > is no kernel 2.6.71). > > That would be correct. I put EXTRAVERSION=1 in the top-level Makefile. > So that 2.6.7 becomes 2.6.71. But, as you observed, it makes no > difference in this matter. Ah yes, I realized afterwards I was assuming you used the make-kpkg command from the kernel-package debian package (nice way to create a .deb of the kernel with all modules). > > > What are the first errors you get and the text above them? > > I don't get any errors, aside from the ones mentioned about > 'FATAL: module not found'. Not anymore, since I > renamed /etc/modules to /etc/modules.old and that one's empty. So it sounds like you had an old /etc/modules with modules corresponding to a different kernel and that was causing the error messages. > If I probe for nonexisting modules, the old FATAL msg. appears. > Nothing strange about that, though. > > UPDATE: > Tried running 'modprobe ', where 'module name' is one > of the module names in /lib/modules/2.6.71. Seems to work, but is this > a permanent solution? A reboot will of course tell me if it's not... No, modules loaded manually will not be loaded upon reboot. You can use /etc/modules to have them loaded at boot time. AFAIK /etc/modules is still a reasonable place to add modules you want that are not automatically loaded, although a lot of new capability is in the works in the 2.6 kernel and the udev project, which may make other methods preferred. Also, there may be cases where you simply need to add an appropriate "alias" line in /etc/modprobe.d/aliases to get a module to automatically load when needed. -- Chris Harris <[EMAIL PROTECTED]> --- GNU/Linux --- The best things in life are free. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: modules not found after kernel recompile
On Mon, 26 Jul 2004 10:42:37 -0600, "CW Harris" <[EMAIL PROTECTED]> said: > On Mon, Jul 26, 2004 at 12:15:29PM +0200, Inge Thorin Eidsæther wrote: > > > > Hi guys, and thanks for all your help so far! > > . > > - Modules are found in correct location,that is: > > /lib/modules/2.6.71, which corresponds to the output > > of 'uname -r' > > Is this a typo? or are you using kernel 2.6.7 with an append-to-version > of 1? I would recommend you use "-" (hyphen) before numeric > append-to-version so the kernel version does not look wrong (i.e. there > is no kernel 2.6.71). That would be correct. I put EXTRAVERSION=1 in the top-level Makefile. So that 2.6.7 becomes 2.6.71. But, as you observed, it makes no difference in this matter. > What are the first errors you get and the text above them? I don't get any errors, aside from the ones mentioned about 'FATAL: module not found'. Not anymore, since I renamed /etc/modules to /etc/modules.old and that one's empty. If I probe for nonexisting modules, the old FATAL msg. appears. Nothing strange about that, though. UPDATE: Tried running 'modprobe ', where 'module name' is one of the module names in /lib/modules/2.6.71. Seems to work, but is this a permanent solution? A reboot will of course tell me if it's not... > > Does things really have to be this convoluted? > > Maybe it helps to remember with W*nd*ws you wouldn't even have the > choice to compile your own kernel, or try the latest and greatest from > the developers. It could be argued that the process of adding a device driver to a W*nd*ws box and having it reboot in order to reconfigure the win32 kernel is not that unlike a recompilation from the non-technical user's point of view. Sure, that's an overly simplistic way of looking at it, since a kernel recompile is not just about adding support for new hardware, but... I dislike MS and W*nd*ws for a number of reasons, but installing a driver for a piece of hardware was *usually* not that troublesome in W*nd*ws. (Although I've had my share of problems as a technical consultant.) As for 'lates and greatest' software, well, if it's broken, it won't do much good. Seen that on more than one occasion with Linux. Then again, I've found much useful software under Linux, sometimes even in a pretty early state of development, so there you go. Still, I'm sticking to Linux (particularly Debian) because of the positive things: GPL licensed, open-source, non-proprietary, standards-compliant, et cetera. It' will require more from me as a user, but I'm a stubborn b*st*rd. > Sorry I'm not more help -- I'm not up-to-date with the latest versions > of things, and unfortunately I can't bring my play-around computer down > right now to see what has changed. Some help is better than none. Sometimes all that's needed is a push in the right direction. Thanks anyway! best regards, Inge Thorin Eidsæther blackwings NOSPAM at NOSPAM inbox dot com
Re: modules not found after kernel recompile
On Mon, Jul 26, 2004 at 12:15:29PM +0200, Inge Thorin Eidsæther wrote: > > Hi guys, and thanks for all your help so far! > > Observations: > > - I misspelled moudule-init-tools as modutils-init-tools. > Sorry! Did all file searches by correct name, though. > > - module-init-tools was installed BEFORE kernel recompile > > - A non-initrd kernel image was made > > - Documentation/post-halloween-2.6.txt > does not exist in my kernel source tree > (downloaded directly from www.kernel.org) > > - I upgraded module-init-tools to last available version > (now: 3.1-pre5) after kernel recompile (was 3.1-pre2) > > - I also did an 'apt-get update' and 'apt-get upgrade' > after recompile (could have been smart to do before?) > > - There is no modprobe.conf anywhere on my system, > just the manpage for it and a demo script called > generate-modprobe.conf.gz in doc/module-init-tools/ex.. Reading the info with the 3.1 module-init-tools this seems to be okay. Apparently modprobe.conf is *no longer* require (was with 3.0). > > - Modules are found in correct location,that is: > /lib/modules/2.6.71, which corresponds to the output > of 'uname -r' Is this a typo? or are you using kernel 2.6.7 with an append-to-version of 1? I would recommend you use "-" (hyphen) before numeric append-to-version so the kernel version does not look wrong (i.e. there is no kernel 2.6.71). That said, I don't think this is your problem (since you say it matches `uname -r`). What are the first errors you get and the text above them? > > - The file modules.dep in that directory looks OK. > > _ I have removed modutils as suggested, since I am > now running a 2.6 kernel anyway. > > - There's a modules.conf.old in /etc, but no modules.conf. > AFAIK I didn't rename it...so a script must have. > So moving entries from modules.conf (nonexisting) > into modprobe.conf (also nonexisting) or into the > modprobe.d directory (how? by copying them to the alias file, > which is already there, and contains - from what I can see - > about the same things?), confuses me a tad. > > - Getting a bit weary of this... :-\ > > Ideas, anyone? Do I have to go back to W*nd*ws? I hope not :-) > Does things really have to be this convoluted? Maybe it helps to remember with W*nd*ws you wouldn't even have the choice to compile your own kernel, or try the latest and greatest from the developers. > > Thanks for input! > > best regards, > > Inge Thorin Eidsæther > blackwings NOSPAM at NOSPAM inbox dot com Sorry I'm not more help -- I'm not up-to-date with the latest versions of things, and unfortunately I can't bring my play-around computer down right now to see what has changed. Hopefully others will have better input. -- Chris Harris <[EMAIL PROTECTED]> --- GNU/Linux --- The best things in life are free. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: modules not found after kernel recompile
Hi guys, and thanks for all your help so far! Observations: - I misspelled moudule-init-tools as modutils-init-tools. Sorry! Did all file searches by correct name, though. - module-init-tools was installed BEFORE kernel recompile - A non-initrd kernel image was made - Documentation/post-halloween-2.6.txt does not exist in my kernel source tree (downloaded directly from www.kernel.org) - I upgraded module-init-tools to last available version (now: 3.1-pre5) after kernel recompile (was 3.1-pre2) - I also did an 'apt-get update' and 'apt-get upgrade' after recompile (could have been smart to do before?) - There is no modprobe.conf anywhere on my system, just the manpage for it and a demo script called generate-modprobe.conf.gz in doc/module-init-tools/ex.. - Modules are found in correct location,that is: /lib/modules/2.6.71, which corresponds to the output of 'uname -r' - The file modules.dep in that directory looks OK. _ I have removed modutils as suggested, since I am now running a 2.6 kernel anyway. - There's a modules.conf.old in /etc, but no modules.conf. AFAIK I didn't rename it...so a script must have. So moving entries from modules.conf (nonexisting) into modprobe.conf (also nonexisting) or into the modprobe.d directory (how? by copying them to the alias file, which is already there, and contains - from what I can see - about the same things?), confuses me a tad. - Getting a bit weary of this... :-\ Ideas, anyone? Do I have to go back to W*nd*ws? Does things really have to be this convoluted? Thanks for input! best regards, Inge Thorin EidsÃther blackwings NOSPAM at NOSPAM inbox dot com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: modules not found after kernel recompile
On Wed, Jul 21, 2004 at 08:41:31PM +0200, Wim De Smet wrote: > On Wed, 21 Jul 2004 12:17:40 -0600, CW Harris <[EMAIL PROTECTED]> wrote: > > On Wed, Jul 21, 2004 at 07:55:27PM +0200, Wim De Smet wrote: > > > Hi, > > > > > [...] > > > > > > You normally don't need a modprobe.conf, everything should be in > > > /etc/modprobe.d. modprobe.conf is just an empty file on my system. I'm > > > > Is this true? Mine (a mostly Sarge with module-init-tools 3.0-pre2-1) has: > > > > # This line loads the part of the modprobe configuration managed with > > # update-modules(8) and built from the contents of /etc/modprobe.d/. > > include /lib/modules/modprobe.conf > > ^^ > > Which seems very important to me (not a GURU here). > > > > module-init-tools in sarge is 3.1-pre5. Maybe it has something to do > with the older version, or maybe you need this if you use udev or ^ Yes that was it. I see in the changelog that between 3.0 and 3.1 modprobe.conf is no longer used since /etc/modprobe.d/* files are parsed directly without the need for update-modules to process them. -- Chris Harris <[EMAIL PROTECTED]> --- GNU/Linux --- The best things in life are free. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: modules not found after kernel recompile
Wim De Smet([EMAIL PROTECTED]) is reported to have said: > On Wed, 21 Jul 2004 17:02:07 -0400, Wayne Topa <[EMAIL PROTECTED]> wrote: > > > > > > Wim De Smet([EMAIL PROTECTED]) is reported to have said: > > > On Wed, 21 Jul 2004 12:17:40 -0600, CW Harris <[EMAIL PROTECTED]> wrote: > > > > On Wed, Jul 21, 2004 at 07:55:27PM +0200, Wim De Smet wrote: > > > > > Hi, > > > > > > > > > [...] > > > > > > > > > > You normally don't need a modprobe.conf, everything should be in > > > > > /etc/modprobe.d. modprobe.conf is just an empty file on my system. I'm [ snipped the wrong info I sent ] I read " modprobe.conf is just an empty file " as modules.conf :-( Need new glasses, I guess. Sorry for the noise. > I don't know what you are trying to say. Yes, he needs > module-init-tools for a 2.6 kernel, that's what he is trying to > install. No he does not need a modprobe.conf (AFAIK). > > See: > $ cat modprobe.conf > $ > (eg nothing in there) > > You can safely remove the modutils if you run a 2.6.x kernel. > Wayne going to the corner and punting on the Dunce Cap. -- Real Users find the one combination of bizarre input values that shuts down the system for days. ___ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: modules not found after kernel recompile
Hi,
You can use either modprobe.conf or the modprobe.d directory-or both, both
of which are
replacements for the old modules.conf. When migrating to the newer
module-init-tools, you should move
required entries from modules.conf to the newer modprobe.conf or modprobe.d
directory.
I've picked this thread somewehere in the middle I rekon, but taking a guess
from the subject line I suggest the following --
1. Is there a /lib/modules/uname -r directory? Does it have the modules you
compiled in it? If not, maybe the make modules_install wasn't done?
2. Is there a modules.dep file in /lib/modules/uname -r directory? If not,
depmod possibly failed, try a depmod -a and then a modprobe again.
HTH
Awais
- Original Message -
From: "Wim De Smet" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, July 22, 2004 5:17 PM
Subject: Re: modules not found after kernel recompile
> On Wed, 21 Jul 2004 17:02:07 -0400, Wayne Topa <[EMAIL PROTECTED]>
wrote:
> >
> >
> > Wim De Smet([EMAIL PROTECTED]) is reported to have said:
> > > On Wed, 21 Jul 2004 12:17:40 -0600, CW Harris
<[EMAIL PROTECTED]> wrote:
> > > > On Wed, Jul 21, 2004 at 07:55:27PM +0200, Wim De Smet wrote:
> > > > > Hi,
> > > > >
> > > > [...]
> > > > >
> > > > > You normally don't need a modprobe.conf, everything should be in
> > > > > /etc/modprobe.d. modprobe.conf is just an empty file on my system.
I'm
> > > >
> > > > Is this true? Mine (a mostly Sarge with module-init-tools
3.0-pre2-1) has:
> > > >
> > > > # This line loads the part of the modprobe configuration managed
with
> > > > # update-modules(8) and built from the contents of /etc/modprobe.d/.
> > > > include /lib/modules/modprobe.conf
> > > > ^^
> > > > Which seems very important to me (not a GURU here).
> > > >
> > >
> > > module-init-tools in sarge is 3.1-pre5. Maybe it has something to do
> > > with the older version, or maybe you need this if you use udev or
> > > something else. I haven't really looked around for info on the subject
> > > but in any case I don't need it and that means with a somewhat typical
> > > setup it shouldn't be required (I never pull any fancy stuff and I
> > > have hardly ever messed with my modules config)
> > >
> > > cheers,
> > > Wim
> > >
> > > P.S.: I think we're all waiting here for somebody with a bit more
> > > knowledge to explain it to us after which we can say "h, like
> > > that" :-)
> >
> > aptitude show module-init-tools
> > Description: tools for managing Linux kernel modules
> > This package contains a set of programs for loading, inserting, and
> > removing kernel modules for Linux (versions 2.5.48 and above). It
> > serves the same function that the "modutils" package serves for Linux
2.4.
> >
> > NOTE: I am running testing with a bit of unstable with a 2.6.7
> > kernel.
> >
> > dpkg -l ii module-init-tools 3.1-pre5-1 tools for managing Linux
kernel modules
> >
> > less /etc/modules.conf
> > ### This file is automatically generated by update-modules"
> > #
> > # Please do not edit this file directly. If you want to change or add
> > # anything please take a look at the files in /etc/modutils and read
> > # the manpage for update-modules.
> > [ snip]
> >
###
> > # Generic section: do not change or copy
> > #
> > # All HDDs
> > probeall /dev/discsscsi_hostadapter sd_mod ide-probe-mod
ide-disk ide-floppy DAC960
> > alias /dev/discs/* /dev/discs
> >
> > # All CD-ROMs
> > probeall /dev/cdroms scsi_hostadapter sr_mod ide-probe-mod
ide-cd cdrom
> > alias /dev/cdroms/* /dev/cdroms
> > alias /dev/cdrom/dev/cdroms
> >
> > # All tapes
> > probeall /dev/tapesscsi_hostadapter st ide-probe-mod
ide-tape
> > alias /dev/tapes/* /dev/tapes
> >
> > {snip many pages }
> >
> > If you are trying to use the 2.6.s kernels you 'do' need to load
module-init-tools.
> >
> > :-) HTH, YMMV, HAND :-)
>
> I don't know what you are trying to say. Yes, he needs
> module-init-tools for a 2.6 kernel, that's what he is trying to
> install. No he does not need a modprobe
Re: modules not found after kernel recompile
On Wed, 21 Jul 2004 17:02:07 -0400, Wayne Topa <[EMAIL PROTECTED]> wrote:
>
>
> Wim De Smet([EMAIL PROTECTED]) is reported to have said:
> > On Wed, 21 Jul 2004 12:17:40 -0600, CW Harris <[EMAIL PROTECTED]> wrote:
> > > On Wed, Jul 21, 2004 at 07:55:27PM +0200, Wim De Smet wrote:
> > > > Hi,
> > > >
> > > [...]
> > > >
> > > > You normally don't need a modprobe.conf, everything should be in
> > > > /etc/modprobe.d. modprobe.conf is just an empty file on my system. I'm
> > >
> > > Is this true? Mine (a mostly Sarge with module-init-tools 3.0-pre2-1) has:
> > >
> > > # This line loads the part of the modprobe configuration managed with
> > > # update-modules(8) and built from the contents of /etc/modprobe.d/.
> > > include /lib/modules/modprobe.conf
> > > ^^
> > > Which seems very important to me (not a GURU here).
> > >
> >
> > module-init-tools in sarge is 3.1-pre5. Maybe it has something to do
> > with the older version, or maybe you need this if you use udev or
> > something else. I haven't really looked around for info on the subject
> > but in any case I don't need it and that means with a somewhat typical
> > setup it shouldn't be required (I never pull any fancy stuff and I
> > have hardly ever messed with my modules config)
> >
> > cheers,
> > Wim
> >
> > P.S.: I think we're all waiting here for somebody with a bit more
> > knowledge to explain it to us after which we can say "h, like
> > that" :-)
>
> aptitude show module-init-tools
> Description: tools for managing Linux kernel modules
> This package contains a set of programs for loading, inserting, and
> removing kernel modules for Linux (versions 2.5.48 and above). It
> serves the same function that the "modutils" package serves for Linux 2.4.
>
> NOTE: I am running testing with a bit of unstable with a 2.6.7
> kernel.
>
> dpkg -l ii module-init-tools 3.1-pre5-1 tools for managing Linux kernel modules
>
> less /etc/modules.conf
> ### This file is automatically generated by update-modules"
> #
> # Please do not edit this file directly. If you want to change or add
> # anything please take a look at the files in /etc/modutils and read
> # the manpage for update-modules.
> [ snip]
> ###
> # Generic section: do not change or copy
> #
> # All HDDs
> probeall /dev/discsscsi_hostadapter sd_mod ide-probe-mod ide-disk
> ide-floppy DAC960
> alias /dev/discs/* /dev/discs
>
> # All CD-ROMs
> probeall /dev/cdroms scsi_hostadapter sr_mod ide-probe-mod ide-cd cdrom
> alias /dev/cdroms/* /dev/cdroms
> alias /dev/cdrom/dev/cdroms
>
> # All tapes
> probeall /dev/tapesscsi_hostadapter st ide-probe-mod ide-tape
> alias /dev/tapes/* /dev/tapes
>
> {snip many pages }
>
> If you are trying to use the 2.6.s kernels you 'do' need to load module-init-tools.
>
> :-) HTH, YMMV, HAND :-)
I don't know what you are trying to say. Yes, he needs
module-init-tools for a 2.6 kernel, that's what he is trying to
install. No he does not need a modprobe.conf (AFAIK).
See:
$ cat modprobe.conf
$
(eg nothing in there)
You can safely remove the modutils if you run a 2.6.x kernel.
In any case I have some more ideas (to the OP):
- modprobe checks for your modules in /lib/modules/`uname -r`. So
check uname -r to see if it does indeed correspond to the directory
name, as something might have gone wrong when setting an extraversion
or whatever.
- check in that directory to see that there is a modules.dep file,
maybe something went wrong in this stage.
greets,
Wim
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: modules not found after kernel recompile
Wim De Smet([EMAIL PROTECTED]) is reported to have said:
> On Wed, 21 Jul 2004 12:17:40 -0600, CW Harris <[EMAIL PROTECTED]> wrote:
> > On Wed, Jul 21, 2004 at 07:55:27PM +0200, Wim De Smet wrote:
> > > Hi,
> > >
> > [...]
> > >
> > > You normally don't need a modprobe.conf, everything should be in
> > > /etc/modprobe.d. modprobe.conf is just an empty file on my system. I'm
> >
> > Is this true? Mine (a mostly Sarge with module-init-tools 3.0-pre2-1) has:
> >
> > # This line loads the part of the modprobe configuration managed with
> > # update-modules(8) and built from the contents of /etc/modprobe.d/.
> > include /lib/modules/modprobe.conf
> > ^^
> > Which seems very important to me (not a GURU here).
> >
>
> module-init-tools in sarge is 3.1-pre5. Maybe it has something to do
> with the older version, or maybe you need this if you use udev or
> something else. I haven't really looked around for info on the subject
> but in any case I don't need it and that means with a somewhat typical
> setup it shouldn't be required (I never pull any fancy stuff and I
> have hardly ever messed with my modules config)
>
> cheers,
> Wim
>
> P.S.: I think we're all waiting here for somebody with a bit more
> knowledge to explain it to us after which we can say "h, like
> that" :-)
aptitude show module-init-tools
Description: tools for managing Linux kernel modules
This package contains a set of programs for loading, inserting, and
removing kernel modules for Linux (versions 2.5.48 and above). It
serves the same function that the "modutils" package serves for Linux 2.4.
NOTE: I am running testing with a bit of unstable with a 2.6.7
kernel.
dpkg -l ii module-init-tools 3.1-pre5-1 tools for managing Linux kernel modules
less /etc/modules.conf
### This file is automatically generated by update-modules"
#
# Please do not edit this file directly. If you want to change or add
# anything please take a look at the files in /etc/modutils and read
# the manpage for update-modules.
[ snip]
###
# Generic section: do not change or copy
#
# All HDDs
probeall /dev/discsscsi_hostadapter sd_mod ide-probe-mod ide-disk
ide-floppy DAC960
alias /dev/discs/* /dev/discs
# All CD-ROMs
probeall /dev/cdroms scsi_hostadapter sr_mod ide-probe-mod ide-cd cdrom
alias /dev/cdroms/* /dev/cdroms
alias /dev/cdrom/dev/cdroms
# All tapes
probeall /dev/tapesscsi_hostadapter st ide-probe-mod ide-tape
alias /dev/tapes/* /dev/tapes
{snip many pages }
If you are trying to use the 2.6.s kernels you 'do' need to load module-init-tools.
:-) HTH, YMMV, HAND :-)
--
"... one of the main causes of the fall of the Roman Empire was that,
lacking zero, they had no way to indicate successful termination of
their C programs." -- Robert Firth
___
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: modules not found after kernel recompile
On Wed, 21 Jul 2004 12:17:40 -0600, CW Harris <[EMAIL PROTECTED]> wrote: > On Wed, Jul 21, 2004 at 07:55:27PM +0200, Wim De Smet wrote: > > Hi, > > > [...] > > > > You normally don't need a modprobe.conf, everything should be in > > /etc/modprobe.d. modprobe.conf is just an empty file on my system. I'm > > Is this true? Mine (a mostly Sarge with module-init-tools 3.0-pre2-1) has: > > # This line loads the part of the modprobe configuration managed with > # update-modules(8) and built from the contents of /etc/modprobe.d/. > include /lib/modules/modprobe.conf > ^^ > Which seems very important to me (not a GURU here). > module-init-tools in sarge is 3.1-pre5. Maybe it has something to do with the older version, or maybe you need this if you use udev or something else. I haven't really looked around for info on the subject but in any case I don't need it and that means with a somewhat typical setup it shouldn't be required (I never pull any fancy stuff and I have hardly ever messed with my modules config) cheers, Wim P.S.: I think we're all waiting here for somebody with a bit more knowledge to explain it to us after which we can say "h, like that" :-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: modules not found after kernel recompile
On Wed, Jul 21, 2004 at 07:55:27PM +0200, Wim De Smet wrote: > Hi, > [...] > > You normally don't need a modprobe.conf, everything should be in > /etc/modprobe.d. modprobe.conf is just an empty file on my system. I'm Is this true? Mine (a mostly Sarge with module-init-tools 3.0-pre2-1) has: # This line loads the part of the modprobe configuration managed with # update-modules(8) and built from the contents of /etc/modprobe.d/. include /lib/modules/modprobe.conf ^^ Which seems very important to me (not a GURU here). -- Chris Harris <[EMAIL PROTECTED]> --- GNU/Linux --- The best things in life are free. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: modules not found after kernel recompile
Hi, First of all sorry to the list that I replied directly to the poster. On Wed, 21 Jul 2004 19:27:21 +0200, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > On Wed, 21 Jul 2004 15:47:28 +0200, "Wim De Smet" <[EMAIL PROTECTED]> > said: > > > > Hi, > > > > On Wed, 21 Jul 2004 15:34:52 +0200, [EMAIL PROTECTED] > > The 2.6 kernels use upgraded modutils, they are in the package > > module-init-tools. You should've read the README before compiling, it > > usually contains stuff like that... > > > > greets, > > Wim > > Hi Wim > > I did read the kernel README file. It does NOT mention > modutils-init-tools at all. However the referenced kernel > compilation HOWTO at at above mentioned URL stated in > no unclear terms that modutils-init-tools was to be > installed prior to compilation, which is what I did. Oh yeah I didn't really check, but I knew there was some file saying what version was required (changes). It's kinda tedious to check these things whenever you upgrade a kernel but from 2.4 to 2.6 is obviously a big change. I actually read about it in Documentation/post-halloween-2.6.txt I think. > > Also, /usr/src/linux/Documentation/Changes says the following: > > "A new module loader is now in the kernel that requires > module-init-tools to use. It is backward compatible with > the 2.4.x series kernels." > > It goes on to say that the required minimum for module-init-tools > is 0.9.10. Installed on my system is 3.1-pre2. It does, I think the version number may simply be wrong. > > There's no man page installed for this package, but doing a > 'dpkg -L modutils-init-tools | grep doc' yields a pointer to > the file '/usr/share/doc/module-init-tools/FAQ', which basically > says that I should run generate-modutils.conf. > > No such binary is installed, but I found a file called > /usr/share/doc/module-init-tools/examples/generate-modprobe.conf.gz > that seems to be a script for doing this operation. > I could not avoid seeing that is says not to put much trust in it... You normally don't need a modprobe.conf, everything should be in /etc/modprobe.d. modprobe.conf is just an empty file on my system. I'm not sure what happened now. It seems you used the correct name and such, so I'm not really sure. I take it module-init-tools was installed before you configured and compiled your kernel? There is one hint in the post-halloween doc: - Some (older) versions of 'mkinitrd' don't search for modules that end with .ko, so update your mkinitrd if this is a problem. Did you make an initrd image? > > And after this comes ALSA config. > Tried that before, and it was a nightmare. > Will try again, but I have to have certain > modules in place first. Every guide I found > on that one wants you to install ALSA using > modules, anyway. Yes, pretty annoying that most guides assume that you don't have modules in kernel. Just configure the module in your kernel. Install those modules, install alsa-base and alsa-utils and then try running "alsaconf". With a bit of luck that should configure everything (as soon as you got the module problem from above sorted out, that is). greets, Wim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: modules not found after kernel recompile
On Wed, 21 Jul 2004 15:47:28 +0200, "Wim De Smet" <[EMAIL PROTECTED]> said: > Hi, > > On Wed, 21 Jul 2004 15:34:52 +0200, [EMAIL PROTECTED] > <[EMAIL PROTECTED]> wrote: > > Hi! > > > > I have recently upgraded my Debian system (running testing) > > from kernel 2.4.18-bf2.4 to 2.7.1 by following the standard > > method of kernel compilation detailed on the following site: > > > > www.digitalhermit.com/linux/Kernel-Build-HOWTO.html > > > > When I restart, boot messages fly by saying 'FATAL: module not > > found' > > I then edit /etc/modules, commenting out the lines, and restart again, > > this time not seeing any such messages. > > > > [snip further info] > > The 2.6 kernels use upgraded modutils, they are in the package > module-init-tools. You should've read the README before compiling, it > usually contains stuff like that... > > greets, > Wim Hi Wim I did read the kernel README file. It does NOT mention modutils-init-tools at all. However the referenced kernel compilation HOWTO at at above mentioned URL stated in no unclear terms that modutils-init-tools was to be installed prior to compilation, which is what I did. Also, /usr/src/linux/Documentation/Changes says the following: "A new module loader is now in the kernel that requires module-init-tools to use. It is backward compatible with the 2.4.x series kernels." It goes on to say that the required minimum for module-init-tools is 0.9.10. Installed on my system is 3.1-pre2. There's no man page installed for this package, but doing a 'dpkg -L modutils-init-tools | grep doc' yields a pointer to the file '/usr/share/doc/module-init-tools/FAQ', which basically says that I should run generate-modutils.conf. No such binary is installed, but I found a file called /usr/share/doc/module-init-tools/examples/generate-modprobe.conf.gz that seems to be a script for doing this operation. I could not avoid seeing that is says not to put much trust in it... And after this comes ALSA config. Tried that before, and it was a nightmare. Will try again, but I have to have certain modules in place first. Every guide I found on that one wants you to install ALSA using modules, anyway. I try to RTFM to the best of my ability, but I'm stumped on this one for now. -- greetings, Inge Thorin Eidsæther blackwings NOSPAM at NOSPAM inbox dot com
Re: Modules from other dist's ??
On Fri, Apr 02, 2004 at 05:16:27PM -0500, Phil wrote: > I couldn't get my NIC to work because the module didn't exist in except on > the internet. (can't logon). I found the module I need (e1000.o) when I > put SuSE the machine. Can I copy the e1000.o file into the /lib//net/ > directory when I put Debian back on and use it?? or are these things > complied differently for different distributions?? There is a very small chance this will work. However your best bet is to recompile the kernel with the relavent module. 'make-kpkg' is the Debian way(and quite handy) but you can always do this the traditional way: apt-get install kernel-source-2.4.whatever cd /usr/src tar -xjf something.tar.bz2 cd kernel-source* make menuconfig #you might prefer xconfig - choose your module here make dep clean modules bzImage modules_install install Ensure LILO(or grub) is set up properly and reboot. Brian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Modules for sata controler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Saturday 20 March 2004 05.13, Chris Lowe wrote: > Hi > I have been attempting to install Debian for the first time on my pc. > But I am having a problem getting the installer to recognise my Via > VT8237 sata raid controller. To install woody with a 2.6.x kernel may be a bit of work. Perhaps downloading the latest beta of the sarge installer would be an option to you? I'm not certain, but I believe there is some support for SATA controllers there. http://www.debian.org/devel/debian-installer/ I think the 30M image suffices to boot, the rest is downloaded as needed. Or take the 100MB image which does include the base system. It shouldn't be a problem to install most things from the woody CDs you have (or if you don't want to risk mixing woddy and sarge, just install sarge from the network). Good luck - -- vbi - -- Hallo ABS'ler! -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) Comment: get my key from http://fortytwo.ch/gpg/92082481 iKcEARECAGcFAkBcBTtgGmh0dHA6Ly9mb3J0eXR3by5jaC9sZWdhbC9ncGcvZW1h aWwuMjAwMjA4MjI/dmVyc2lvbj0xLjUmbWQ1c3VtPTVkZmY4NjhkMTE4NDMyNzYw NzFiMjVlYjcwMDZkYTNlAAoJEIukMYvlp/fWWdcAoI/gjdMX91D1zNSLWM5sIAIQ vd18AJ9aL+tkQOFhrxkGftwJ6XvIQMIRGQ== =MiC7 -END PGP SIGNATURE-
Re: modules after kernel make - can't get new kernel finding its modules
On Mon, Mar 01, 2004 at 09:37:22PM -, Chris Evans wrote: > On 1 Mar 2004 at 13:28, CW Harris wrote: > > > I thought you were using make-kpkg? It does all this for you when you > > "build" the .deb package. > So I thought: but it isn't! I think that's because it's picking up a > .config that isn't marking the module packages for inclusion > > > What are the diff's between the working 2.4.18 config > working 2.4.18-df2.4 > > > and the new one? > That lots of modules aren't marked for inclusion as loadable modules > or compiled in ... I assume ... but the bottom line is that I don't > know, exactly what they are as I have the basic source tree of 2.4.18 > from the distro and the working image from 2.4.18-bf2.4 but I don't > know (do I?) what the .config is that made the 2.4.18-bf2.4 and if I The kernel-image-2.4.18-1-386 package installs a file: -rw-r--r-- root/root 36944 2004-02-01 03:20:38 ./boot/config-2.4.18-1-386 (This is obviously from the "386" bf2.4 package, other bf2.4 packages will have a similar name.) This file contains the configuration that this kernel was compiled with. So if you already have a working kernel that you just want to add RAID to, start with it. I haven't really used the initrd stuff in my kernels, so I don't know if that is causing you any problems, but starting with that config file you should be able to build the same kernel since support for initrd is part of the configuration. > could start from that I think I'd be home and dry and could just add > RAID and take out quite a bit I don't need and probably add a bit of > IP tracking ... trouble is, I can't see how I get that starting > config for 2.4.18-bf2.4. Any idea how do I find out? > Should it only be the RAID built-in? I would start with the working kernel and add only 1 major change at a time (at least until you get more comfortable with this). As posted before in this thread, you can use the kernel flavours to help keep your kernel modules separate (and thus keep a working kernel as a stable rescue boot while you are playing around with kernel changes). If you are doing Software RAID, read the fine Software-RAID-HOWTO (it will be in /usr/share/doc/HOWTO/.. if you have installed the doc-linux-text package, otherwise check it out on the LDP, www.tldp.org - or a mirror near you). If you are doing hardware RAID, make sure you have everything to support your RAID hardware. > > Maybe start with the working config > but I don't think the kernel-image package gives me that, or, to be > more accurate, I'm sure it does but it's not in the /usr/src I don't recall where the Debian source package puts things, but the source can be installed anywhere and worked on by an ordinary user. Only the package install has to be by root. There is support for module building outside the kernel, that uses /usr/src/module or something like that. This is not the same as the normal modules used in the kernel source. The kernel-package docs also tell how to use make-kpkg to build these type modules. > directory tree obviously and I'm looking for someone on the list who > I'm sure does know, to tell me how I can get this ... > > > and do "make menuconfig" (or whatever method you like) to add the RAID > > stuff, then try the make-kpkg sequence again. > Yup > > > Note you should have a config in /boot corresponding to the > > kernel-compile options (but there may be a config option to not use > > it? I seem to recall there might be, but I have always had > > /boot/config-2.4.xx) > Don't understand this. Can you expand? See above. > > > Chris > > > PSYCTC: Psychotherapy, Psychology, Psychiatry, Counselling > > > > Take an anti-depressant PRN :> > Nah, I'm a group therapist and family/systems therapist by main > training so I guess I turn to the group/family PRN. Sorry if it's a > pain for those who really know what they're doing: I'd offer you a > free place in a group but I run them in a high secure hospital so > you'd have to kill someone first to get in... I'll keep that in mind. :> > > Thanks again! There are probably others who can help you better, but if /I/ can get through this, I'm sure you can. Just keep at it. Also, the fakeroot package is nice to let you do all the package work as non-root if you're not already. (Again, in the kernel-package docs.) HTH -- Chris Harris <[EMAIL PROTECTED]> --- GNU/Linux --- The best things in life are free. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: modules after kernel make - can't get new kernel finding its modules
On 1 Mar 2004 at 13:28, CW Harris wrote: > I thought you were using make-kpkg? It does all this for you when you > "build" the .deb package. So I thought: but it isn't! I think that's because it's picking up a .config that isn't marking the module packages for inclusion > What are the diff's between the working 2.4.18 config working 2.4.18-df2.4 > and the new one? That lots of modules aren't marked for inclusion as loadable modules or compiled in ... I assume ... but the bottom line is that I don't know, exactly what they are as I have the basic source tree of 2.4.18 from the distro and the working image from 2.4.18-bf2.4 but I don't know (do I?) what the .config is that made the 2.4.18-bf2.4 and if I could start from that I think I'd be home and dry and could just add RAID and take out quite a bit I don't need and probably add a bit of IP tracking ... trouble is, I can't see how I get that starting config for 2.4.18-bf2.4. Any idea how do I find out? Should it only be the RAID built-in? > Maybe start with the working config but I don't think the kernel-image package gives me that, or, to be more accurate, I'm sure it does but it's not in the /usr/src directory tree obviously and I'm looking for someone on the list who I'm sure does know, to tell me how I can get this ... > and do "make menuconfig" (or whatever method you like) to add the RAID > stuff, then try the make-kpkg sequence again. Yup > Note you should have a config in /boot corresponding to the > kernel-compile options (but there may be a config option to not use > it? I seem to recall there might be, but I have always had > /boot/config-2.4.xx) Don't understand this. Can you expand? > You can also read the kernel-package README.gz file if you haven't > already, to check you procedure using it, but your steps sound right > to me. I know I've looked through that several times and it's probably I've got to that point where I keep misreading the same bit ... > > TIA (and thanks again Martin: funny how down I get failing on these > > things, feeling stupid, _and_ getting no answers!) > > Don't despair. Hang in there. Thanks: appreciated! > > > > Chris > > PSYCTC: Psychotherapy, Psychology, Psychiatry, Counselling > > Take an anti-depressant PRN :> Nah, I'm a group therapist and family/systems therapist by main training so I guess I turn to the group/family PRN. Sorry if it's a pain for those who really know what they're doing: I'd offer you a free place in a group but I run them in a high secure hospital so you'd have to kill someone first to get in... Thanks again! C PSYCTC: Psychotherapy, Psychology, Psychiatry, Counselling and Therapeutic Communities; practice, research, teaching and consultancy. Chris Evans & Jo-anne Carlyle http://psyctc.org/ Email: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: modules after kernel make - can't get new kernel finding its modules
On Mon, Mar 01, 2004 at 06:38:07PM -, Chris Evans wrote: > On 1 Mar 2004 at 18:27, Martin Wood wrote: > > > I think this is exactly where i went wrong the other day. > > > > try adding : > > > > make modules > > make modules_install > > > > and hopefully your modules will show up > > Thanks Martin. I should have said that I've tried this sequence with > and without that, make modules and make modules_install both produce > a lot of moving in and out of subdirectories: I thought you were using make-kpkg? It does all this for you when you "build" the .deb package. > > make -C arch/i386/lib modules_install > make[1]: Entering directory `/usr/src/kernel-source- > 2.4.18/arch/i386/lib' > make[1]: Nothing to be done for `modules_install'. > > but that "Nothing to be done" message seems to be summarising the > situation! > > I think they aren't doing more than the make dep make-kpkg clean make- > kpkg --rev ... kernel_image sequence is doing. > > I think that all of them are simply assuming either I have the > necessary modules already or that there are far fewer modules I want > than I atually do want. > > Anyone any idea what's wrong and how I can perhaps restart the whole > sequence and insist that all the modules get compiled and installed? What are the diff's between the working 2.4.18 config and the new one? Should it only be the RAID built-in? Maybe start with the working config and do "make menuconfig" (or whatever method you like) to add the RAID stuff, then try the make-kpkg sequence again. Note you should have a config in /boot corresponding to the kernel-compile options (but there may be a config option to not use it? I seem to recall there might be, but I have always had /boot/config-2.4.xx) You can also read the kernel-package README.gz file if you haven't already, to check you procedure using it, but your steps sound right to me. > > TIA (and thanks again Martin: funny how down I get failing on these > things, feeling stupid, _and_ getting no answers!) Don't despair. Hang in there. > > Chris > PSYCTC: Psychotherapy, Psychology, Psychiatry, Counselling Take an anti-depressant PRN :> >and Therapeutic Communities; practice, research, >teaching and consultancy. > Chris Evans & Jo-anne Carlyle > http://psyctc.org/ Email: [EMAIL PROTECTED] > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- Chris Harris <[EMAIL PROTECTED]> --- GNU/Linux --- The best things in life are free. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: modules after kernel make - can't get new kernel finding its modules
On 1 Mar 2004 at 18:27, Martin Wood wrote: > I think this is exactly where i went wrong the other day. > > try adding : > > make modules > make modules_install > > and hopefully your modules will show up Thanks Martin. I should have said that I've tried this sequence with and without that, make modules and make modules_install both produce a lot of moving in and out of subdirectories: make -C arch/i386/lib modules_install make[1]: Entering directory `/usr/src/kernel-source- 2.4.18/arch/i386/lib' make[1]: Nothing to be done for `modules_install'. but that "Nothing to be done" message seems to be summarising the situation! I think they aren't doing more than the make dep make-kpkg clean make- kpkg --rev ... kernel_image sequence is doing. I think that all of them are simply assuming either I have the necessary modules already or that there are far fewer modules I want than I atually do want. Anyone any idea what's wrong and how I can perhaps restart the whole sequence and insist that all the modules get compiled and installed? TIA (and thanks again Martin: funny how down I get failing on these things, feeling stupid, _and_ getting no answers!) Chris PSYCTC: Psychotherapy, Psychology, Psychiatry, Counselling and Therapeutic Communities; practice, research, teaching and consultancy. Chris Evans & Jo-anne Carlyle http://psyctc.org/ Email: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: modules after kernel make - can't get new kernel finding its modules
Chris Evans wrote: More explicit version of earlier request. I installed 2.4.18-bf2.4 kernel from CDROM and then completed installation onto machine from net. I want to compile the RAID code into the kernel so I can boot from a mirrored disc array. I download kernel-source2.4.18. I do: make menuconfig make dep make-kpkg clean make-kpkg --version=custom.1.0 I think this is exactly where i went wrong the other day. try adding : make modules make modules_install and hopefully your modules will show up martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: modules
Thanks o lot. I see discover running. I'll try installation without discover and with discover. Since I'm running SCSI/IDE system I'll compile drivers form my controllers to kernel. No initrd needded Thanks Rob Weir wrote: On Sat, Feb 14, 2004 at 11:15:34AM -0500, cdummy said Hello. I'm new with testing. I have a few questions. Please answer or send me to proper list. I used daily built of Sarge installer without any big problems. Just trouble to get out of setting sources for apt, but I did them manuallly and hit cancel which took me to main menu. System works almost no problems just at the boot I'm getting message "couln't open /etc/mtab" but from what I see this is typical problem of this installer. I need advice.. I'd like to compile kernel. When I do lsmod I see all my modules loaded : snip usb-uhci 19696 0 (unused) usbcore52588 0 [usb-uhci] via82cxxx_audio17756 1 ac97_codec 11412 0 [via82cxxx_audio] uart401 6244 0 [via82cxxx_audio] sound 50568 0 [via82cxxx_audio uart401] soundcore 3268 4 [via82cxxx_audio sound] ide-scsi8464 0 3c59x 24016 1 snip but my /etc/modules looks like that: sd_mod ide-cd ide-detect If I go to /etc/modutils there are no my sound modules to load. When I take look on my stock kernel config file above sound modules are compiled as modules: snip # CONFIG_MSNDPIN_HAVE_BOOT is not set CONFIG_MSNDPIN_INIT_FILE="/etc/sound/pndspini.bin" CONFIG_MSNDPIN_PERM_FILE="/etc/sound/pndsperm.bin" CONFIG_SOUND_VIA82CXXX=m CONFIG_MIDI_VIA82CXXX=y CONFIG_SOUND_OSS=m snip And they are in /lib/modules. How do they load? Kernel loads modules automatically? Do you have something like "discover" or "kudzu" installed? They will load modules as they detect hardware. How come they are not in /etc/modutils/aliases Last kernel I compiled was 2.4.20 and I compiled modules and than added them to /etc/modules so they load. SCSI and IDE I always compile into kernel. And there comes my second question. I read 2 articles about compiling Debian specific kernel.: http://www.osnews.com/story.php?news_id=2949&page=1 http://www.tux.org/~tbr/debiankernelpkg/ But all new kernels are coming with initrd.img. Is this a must or can I compile old way? You can build kernels with make-kpkg without using initrd, Debian's kernels just use it so they can include everything as modules. If you're not using an initrd, don't forget to build all your essential stuff (IDE controller, filesystems) INTO the kernel, and not as modules. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: modules
On Sat, Feb 14, 2004 at 11:15:34AM -0500, cdummy said > Hello. I'm new with testing. I have a few questions. Please answer or > send me to proper list. I used daily built of Sarge installer without > any big problems. Just trouble to get out of setting sources for apt, > but I did them manuallly and hit cancel which took me to main menu. > System works almost no problems just at the boot I'm getting message > "couln't open /etc/mtab" but from what I see this is typical problem of > this installer. I need advice.. I'd like to compile kernel. When I do > lsmod I see all my modules loaded : > snip > usb-uhci 19696 0 (unused) > usbcore52588 0 [usb-uhci] > via82cxxx_audio17756 1 > ac97_codec 11412 0 [via82cxxx_audio] > uart401 6244 0 [via82cxxx_audio] > sound 50568 0 [via82cxxx_audio uart401] > soundcore 3268 4 [via82cxxx_audio sound] > ide-scsi8464 0 > 3c59x 24016 1 > snip > but my /etc/modules looks like that: > sd_mod > ide-cd > ide-detect > > If I go to /etc/modutils there are no my sound modules to load. When I > take look on my stock kernel config file above sound modules are > compiled as modules: > snip > # CONFIG_MSNDPIN_HAVE_BOOT is not set > CONFIG_MSNDPIN_INIT_FILE="/etc/sound/pndspini.bin" > CONFIG_MSNDPIN_PERM_FILE="/etc/sound/pndsperm.bin" > CONFIG_SOUND_VIA82CXXX=m > CONFIG_MIDI_VIA82CXXX=y > CONFIG_SOUND_OSS=m > snip > And they are in /lib/modules. How do they load? Kernel loads modules > automatically? Do you have something like "discover" or "kudzu" installed? They will load modules as they detect hardware. > How come they are not in /etc/modutils/aliases > Last kernel I compiled was 2.4.20 and I compiled modules and than added > them to /etc/modules so they load. SCSI and IDE I always compile into > kernel. And there comes my second question. I read 2 articles about > compiling Debian specific kernel.: > http://www.osnews.com/story.php?news_id=2949&page=1 > http://www.tux.org/~tbr/debiankernelpkg/ > But all new kernels are coming with initrd.img. Is this a must or can I > compile old way? You can build kernels with make-kpkg without using initrd, Debian's kernels just use it so they can include everything as modules. If you're not using an initrd, don't forget to build all your essential stuff (IDE controller, filesystems) INTO the kernel, and not as modules. -- Rob Weir <[EMAIL PROTECTED]> | [EMAIL PROTECTED] | Do I look like I want a CC? Words of the day: KGB PGP strategic Firefly Australia counter intelligence signature.asc Description: Digital signature
Re: modules
On 2004-02-14, cdummy penned: > > If I go to /etc/modutils there are no my sound modules to load. When I > take look on my stock kernel config file above sound modules are > compiled as modules: > snip > # CONFIG_MSNDPIN_HAVE_BOOT is not set > CONFIG_MSNDPIN_INIT_FILE="/etc/sound/pndspini.bin" > CONFIG_MSNDPIN_PERM_FILE="/etc/sound/pndsperm.bin" > CONFIG_SOUND_VIA82CXXX=m > CONFIG_MIDI_VIA82CXXX=y > CONFIG_SOUND_OSS=m > snip > And they are in /lib/modules. How do they load? Kernel loads modules > automatically? How come they are not in /etc/modutils/aliases Look at the file /etc/modules. This is a list of modules that the kernel will automatically load at boot, and I'm guessing that you will find your modules there. > Last kernel I compiled was 2.4.20 and I compiled modules and than added > them to /etc/modules so they load. SCSI and IDE I always compile into Now I'm confused. You didn't mention /etc/modules above. I am pretty sure /etc/modutils serves a different purpose, but I don't understand the system well enough to explain it. > kernel. And there comes my second question. I read 2 articles about > compiling Debian specific kernel.: > http://www.osnews.com/story.php?news_id=2949&page=1 > http://www.tux.org/~tbr/debiankernelpkg/ > But all new kernels are coming with initrd.img. Is this a must or can I > compile old way? I always pull down the Debian kernel-source package for the kernel version I want, then build in the standard way. No initrd for me, and it works fine. So, no: you don't have to use initrd with debian. -- monique -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: modules
Dennis Kaplan wrote: I just installed the new 2.6 K7 kernel but I can't use it because my serial mouse does not work. After doing some researching & reading I got totally confused about modules. Where I am at: I think there is a module missing maybe the serial module if there is such a thing and that is why my mouse will not work. If that is correct how do I get this module? Do I have to get a kernel source and recompile my own kernel or do I add some file in to a directory called module? How do I know what module I need at the first place? Can someone enlighten me about modules? Did you try modprobing busmouse or psmouse? -Roberto signature.asc Description: OpenPGP digital signature
Re: Modules/Ethernet setup
On Sun, 2003-11-30 at 15:32, Paul M Foster wrote: > When I was installing Deb 3.0r1 on a new machine, I couldn't find what I > thought was the right module/driver for the ethernet card, so I just > skipped it. Later I found the right driver. I can get the card up and > working. Manually, I can do it this way: > > modprobe natsemi > ifconfig eth0 inet 192.168.10.2 > route add default gw 192.168.10.20 > > However, I don't know how to integrate this with the Debian > /etc/modules/* and /etc/modules.conf. Can anyone tell me what files to > create and with what parameters? [EMAIL PROTECTED]:~$ cat /etc/network/interfaces auto lo eth0 iface lo inet loopback iface eth0 inet static address 192.168.1.4 netmask 255.255.255.0 broadcast 192.168.1.255 gateway 192.168.1.1 # For a dhcp eth0 commnet out above # and uncomment below #iface eth0 inet dhcp As you can see I have a good example for you here. -- greg, [EMAIL PROTECTED] REMEMBER ED CURRY! http://www.iwethey.org/ed_curry signature.asc Description: This is a digitally signed message part
Re: Modules/Ethernet setup
On Sun, 2003-11-30 at 21:32, Paul M Foster wrote: > When I was installing Deb 3.0r1 on a new machine, I couldn't find what I > thought was the right module/driver for the ethernet card, so I just > skipped it. Later I found the right driver. I can get the card up and > working. Manually, I can do it this way: > > modprobe natsemi > ifconfig eth0 inet 192.168.10.2 > route add default gw 192.168.10.20 > > However, I don't know how to integrate this with the Debian > /etc/modules/* and /etc/modules.conf. Can anyone tell me what files to > create and with what parameters? Two things to do: (1) Load the module. You can simply add it to /etc/modules. The module gets loaded at system boot time then. The other way is to add the line ---snip--- alias eth0 natsemi ---snap to /etc/modules.conf. Then, the module will get loaded, whenever eth0 is accessed. *But*, as a good debian admin you should *never* edit this file by hand. Look at update-modules(5) for information how to change you modules configuration database. (2) Configure the network device. You have to add the device configuration to the file /etc/network/interfaces. See interfaces(5) how to do that. Hope that helps. -alf -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Modules/Ethernet setup
Hello Paul M Foster (<[EMAIL PROTECTED]>) wrote: > When I was installing Deb 3.0r1 on a new machine, I couldn't find what > I thought was the right module/driver for the ethernet card, so I just > skipped it. Later I found the right driver. I can get the card up and > working. Manually, I can do it this way: > > modprobe natsemi > ifconfig eth0 inet 192.168.10.2 > route add default gw 192.168.10.20 > > However, I don't know how to integrate this with the Debian > /etc/modules/* and /etc/modules.conf. Can anyone tell me what files to > create and with what parameters? To load the driver module automatically, add natsemi to /etc/modules, manually or using modconf or alias eth0 natsemi to /etc/modutils/aliases or a new file in /etc/modutils and run update-modules. To configure the interface, edit /etc/network/interfaces (man interfaces) or install etherconf (you can run dpkg-reconfigure etherconf later to change the configuration). best regards Andreas Janssen -- Andreas Janssen [EMAIL PROTECTED] PGP-Key-ID: 0xDC801674 Registered Linux User #267976 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: modules of different kernels (same version)
Andreas Janssen <[EMAIL PROTECTED]> writes: > Robert Epprecht (<[EMAIL PROTECTED]>) wrote: > >> If I compile different kernels (of the same version) most documents >> say to rename the /lib/modules/x.x.x/ directory before doing the >> 'make modules_install' step. >> >> How can I boot the system after that with an older version? > You can use the "EXTRAVERSION" of the Kernel to have the Modules > installed in different directories. [ ... ] > This way the modules will not be installed in the same directory. Thanks a lot for explaining. > Maybe you also want to take a look at kernel-package and its make-kpkg > program. Yes, I know that and have been using it. >> Could somebody please give a pointer to a document describing how >> to do that? Roberto Sanchez gave me the following good advice > Save yourself some trouble and read this fine HOWTO on > compiling kernels the Debian way. > > http://newbiedoc.sourceforge.net/system/kernel-pkg.html Thank you Roberto. I *did* know this excellent tutorial. My problem was, that I had an outdated local copy, which did not treat this problem yet, but gave the advice to rename the module directory... The new version is much improved. Robert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: modules of different kernels (same version)
On Thu, Aug 28, 2003 at 11:44:47PM +0200, Andreas Janssen wrote: > Hello > > Robert Epprecht (<[EMAIL PROTECTED]>) wrote: > > > I have read different documents about kernel compiling, > > but something is still not clear to me: > > > > If I compile different kernels (of the same version) most documents > > say to rename the /lib/modules/x.x.x/ directory before doing the > > 'make modules_install' step. > > > > How can I boot the system after that with an older version? > > > > Could somebody please give a pointer to a document describing how > > to do that? > > You can use the "EXTRAVERSION" of the Kernel to have the Modules > installed in different directories. Take a look at the Makefile in your > Kernel source directory. It begins with something like: > > VERSION = 2 > PATCHLEVEL = 4 > SUBLEVEL = 22 > EXTRAVERSION = > > When you compile different Kernels from the same source and want to > install them on one system, set the extraversion to different values > (normally beginning with an "-"). This way the modules will not be > installed in the same directory. With the above configuration, modules > go to /lib/modules/2.4.22. If I set EXTRAVERSION to -custom, modules go > to /lib/modules/2.4.22-custom. The Kernel knows about its extraversion > and automatically looks for modules in the correct directory. > > Maybe you also want to take a look at kernel-package and its make-kpkg > program. It allows you to make deb packages containing kernel source, > doc, image/modules and headers from your source. > _Not_ maybe! For sure, you should look at kernel-package and make-kpkg! The naming of sets of modules is done automagically in Debian. Use it, and watch what it does. You will see the changes that others must do by hand. Paul Condon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: modules of different kernels (same version)
--- Robert Epprecht <[EMAIL PROTECTED]> escribió: > I have read different documents about kernel compiling, > but something is still not clear to me: > > If I compile different kernels (of the same version) most documents > say to rename the /lib/modules/x.x.x/ directory before doing the > 'make modules_install' step. > > How can I boot the system after that with an older version? > > Could somebody please give a pointer to a document describing how > to do that? > > Thank you, Robert Epprecht. Robert, Save yourself some trouble and read this fine HOWTO on compiling kernels the Debian way. http://newbiedoc.sourceforge.net/system/kernel-pkg.html By using kernel-package, you can do it all in a few steps and also easily differentiate your kernel versions. I always do something like this: cd /usr/src/kernel-source-2.4.xx/ make menuconfig make-kpkg clean fakeroot make-kpkg --revision=mmdd --append-to-version=-z cd .. sudo dpkg -i kernel-image-2.4.xx-z_mmdd_i386.deb It is very simple. -Roberto ___ Yahoo! Messenger - Nueva versión GRATIS Super Webcam, voz, caritas animadas, y más... http://messenger.yahoo.es -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: modules of different kernels (same version)
Hello Robert Epprecht (<[EMAIL PROTECTED]>) wrote: > I have read different documents about kernel compiling, > but something is still not clear to me: > > If I compile different kernels (of the same version) most documents > say to rename the /lib/modules/x.x.x/ directory before doing the > 'make modules_install' step. > > How can I boot the system after that with an older version? > > Could somebody please give a pointer to a document describing how > to do that? You can use the "EXTRAVERSION" of the Kernel to have the Modules installed in different directories. Take a look at the Makefile in your Kernel source directory. It begins with something like: VERSION = 2 PATCHLEVEL = 4 SUBLEVEL = 22 EXTRAVERSION = When you compile different Kernels from the same source and want to install them on one system, set the extraversion to different values (normally beginning with an "-"). This way the modules will not be installed in the same directory. With the above configuration, modules go to /lib/modules/2.4.22. If I set EXTRAVERSION to -custom, modules go to /lib/modules/2.4.22-custom. The Kernel knows about its extraversion and automatically looks for modules in the correct directory. Maybe you also want to take a look at kernel-package and its make-kpkg program. It allows you to make deb packages containing kernel source, doc, image/modules and headers from your source. best regards Andreas Janssen -- Andreas Janssen [EMAIL PROTECTED] PGP-Key-ID: 0xDC801674 Registered Linux User #267976 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: modules gone after kernel upgrade
On Sat, Jan 18, 2003 at 02:08:55AM -0500, Debian User wrote: > I just upgraded from potato 2.2.19 to woody and kernel 2.4.18-386. Now > my modules are gone in modconf? Where to put module path so it will > show in modconf? I can still insmod but was wondering why the path > didnt upgrade 2? > Also insmod ppp ->no module by that name? ppp_generic is there but not > just ppp. Sorry for my duh?s. > > Thanks for your help. Never used modconf, but the modules are in the directory tree under /lib/modules and I've always maninpulated them by editing /etc/modules and /etc/modules.conf. As for ppp, ppp_generic is correct for 2.4.x. I've got /lib/modules/2.4.20/kernel/drivers/net/ppp_async.o /lib/modules/2.4.20/kernel/drivers/net/ppp_deflate.o /lib/modules/2.4.20/kernel/drivers/net/ppp_generic.o ppp_generic is the beastie. The others depend on it. Pigeon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Modules Dont Load At Startup - THANKS
Le Sun, 17 Nov 2002 09:36:31 -0500 "Thomas H. George" <[EMAIL PROTECTED]> disait: > After this insmod NVdrivers worked > but I had to run it after each bootup and then restart xdm. If I > missed something in this sequence I would appreciate knowing what I > should have done. I don't know if we missed something but it was the same for me for 2 different machines (all running woody) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Modules Dont Load At Startup
Hello, Am 01:19 2002-11-17 +1100 hat Russell geschrieben: > >Thomas H. George,,, wrote: >> Would someone please point out what I have been too blind to see. > >I have an /etc/modules. It is meant to be hand-edited, and is loaded >at boot time. Type 'modconf' at the prompt... michelle -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Modules Dont Load At Startup - THANKS
Thanks for all the responses. I am begining to understand the roles of the various module files. For the moment I inserted the line alias char-major-195 NVdriver in the file /etc/modutils/aliases and then ran modconf so the line is now included in /etc/modules.conf. With this change xdm runs successfully at bootup. I dont know why my initial installation was incomplete. I created a directory /usr/local/nvidia and downloaded NVIDIA_GLX-1.0-3123.tar.gz and NVIDIA_kernel-1.0-3123.tar.gz into this directory. I unpacked each of these and ran make install in the subdirectories they created. Both compilations completed successfully. After this insmod NVdrivers worked but I had to run it after each bootup and then restart xdm. If I missed something in this sequence I would appreciate knowing what I should have done. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Modules Dont Load At Startup
"Thomas H. George,,," <[EMAIL PROTECTED]> writes: > It is certainly elementary but it baffles me. Although I have > compiled my kernel with module support set to load modules as needed > and run make modules and make modules_install, (Depending on what you're doing, you may find it easier/better to use kernel-package, which builds installable Debian packages from kernel source. It also makes it much more straightforward to build module packages that are distributed separately from the main kernel, including the ALSA sound driver, the lm-sensors hardware monitoring package, and the OpenAFS network file system.) > certain modules never loaded when needed. For example, the sound > card module never loaded at startup so I always ended up building it > into the kernel. For things where the kernel has an option for lots of things that provide the same interface (which network card, which sound card, etc.) it won't automatically load something without prodding. There might be hints in your system logs about which modules are attempting to be loaded; you can probably add aliases for these under /etc/modutils. > I know I have overlooked something basic, but what? My O'Reilly > Debian book discusses config.modules which has been replaced by > modules.config which starts with a warning I am not to edit it. You can create or edit a file under /etc/modutils and run update-modules to regenerate your modules.conf file. > Modules-HOWTO has a lot of interesting information but, unless I > missed it, no instructions regarding on requiring modules to load > during bootup. ...or, edit /etc/modules; it's a plain-text file that has a listing of modules to load at boot time, one to a line. -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ "Theoretical politics is interesting. Politicking should be illegal." -- Abra Mitchell -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Modules Dont Load At Startup
On Saturday 16 November 2002 04:40 am, Thomas H. George,,, wrote: > It is certainly elementary but it baffles me. Although I have > compiled my kernel with module support set to load modules as needed > and run make modules and make modules_install, certain modules never > loaded when needed. For example, the sound card module never loaded > at startup so I always ended up building it into the kernel. Now I > have a Geforce4 video card and must run insmod NVdriver each time > after I boot up as xdm fails until I have done this. Try using 'modconf' . This will build a list of modules that will load at boot time. -- Greg Madden Debian GNU/Linux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Modules Dont Load At Startup
Thomas H. George,,, wrote: It is certainly elementary but it baffles me. Although I have compiled my kernel with module support set to load modules as needed and run make modules and make modules_install, certain modules never loaded when needed. For example, the sound card module never loaded at startup so I always ended up building it into the kernel. Now I have a Geforce4 video card and must run insmod NVdriver each time after I boot up as xdm fails until I have done this. I know I have overlooked something basic, but what? My O'Reilly Debian book discusses config.modules which has been replaced by modules.config which starts with a warning I am not to edit it. Modules-HOWTO has a lot of interesting information but, unless I missed it, no instructions regarding on requiring modules to load during bootup. The Linux kernel is so compact there is no reason not to load everything I need at bootup so the real advantage of the module concept must be to allow third parties to add functions to the kernel - e.g. the NVdriver. Would someone please point out what I have been too blind to see. I have an /etc/modules. It is meant to be hand-edited, and is loaded at boot time. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: modules
Damn I hate it when people post with unreliable email addresses, makes it kinda hard to help them when they don't have accurate addresses... Dave -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, 24 September 2002 2:00 AM To: [EMAIL PROTECTED]; David Pastern Subject: modules Hi, Like a new user of Debian(Woody) I dont know how it works with modules. For example my box(celeron 500 with sound card isa?) doesnt play, it seem that the sound card wont work(kernel 2.2.20-idepci).How could Ifix this ? Thanks for any help! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: modules
Hi, Can you please provide further information, what does "lsmod" show when entered at the command line as root? What make/model of soundcard are you using? Are you getting any error messages (ie when trying to play an application that uses sound etc)?. Can you please provide details such as bootup information (type "dmesg > ~/filename.txt" and that will create a file that contains all the messages that you get at bootup, saved to your home directory). Dave -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, 24 September 2002 2:00 AM To: [EMAIL PROTECTED]; David Pastern Subject: modules Hi, Like a new user of Debian(Woody) I dont know how it works with modules. For example my box(celeron 500 with sound card isa?) doesnt play, it seem that the sound card wont work(kernel 2.2.20-idepci).How could Ifix this ? Thanks for any help! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: modules
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 24 September 2002 17:12, florin wrote: > Like a new user of Debian(Woody) I dont know how it work.For ex. my > box(celeron 500) with sound card isa? doesnt play under kernel > 2.2.20-idepci(it play with SuSE 7.1 and RH 7.3) > Is it any line command for sound configuration(like sndconfig-RedHat) > or another method.What about modules, how can I proceded for install > the new if it's necessary for sound? > Thanks for any help ! Normally all you have to do is to insert a line in /etc/modules to load the correct driver for your card. If you just told us what card you're using, it shouldn't be too hard to tell which one to use. - -- Embedded Linux -- True multitasking! TWO TOASTS AT THE SAME TIME! -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9kIUTeOF0+zcVdv8RAo+1AKCgZ73rLdM7QzvyeRNRru6UDam26gCfZjf+ 2sDjEpLWwKShz1sSjBRSLC4= =+s6c -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: modules
Unlike in RH, there is no autodetection of ISA cards in Debian Woody. The easiest and most straight forward way is to use modconf. There you find the necessary modules to make your card work. You'll need ISA working (pnp) and the sound card module itself. If you remember which modules were loaded under RH, just install them. I believe there is a package with sndconfig (the one from RH) that you can install. This might not be the optimal solution, though. florin wrote: > Like a new user of Debian(Woody) I dont know how it work.For ex. my > box(celeron 500) with sound card isa? doesnt play under kernel > 2.2.20-idepci(it play with SuSE 7.1 and RH 7.3) > Is it any line command for sound configuration(like sndconfig-RedHat) or > another method.What about modules, how can I proceded for install the > new if it's necessary for sound? > Thanks for any help ! > > -- Johan Ehnberg [EMAIL PROTECTED] "Windows? No... I don't think so." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
SOLVED - Re: Modules - unstable? -newbie
Stephen, Thank you! arts was the cause of the problem. both /dev/audio and /dev/dsp work well. Setyo Nugroho > > The second is usually a sound server if you're running X - GNOME uses > ESD, and KDE uses Arts. Try ps ax to see if either is running. > > The other is permissions - make sure your user is in group audio. Then, > either try to play a sound file from within an app, or cat > /usr/share/sounds/KDE_Window_UnSticky.wav > /dev/dsp . According to > devices.txt from the kernel source, /dev/dsp is digital audio, while > /dev/audio is Sun-compatible digital audio - don't know if both coexist > on a normal Debian install, but /dev/dsp has always worked for me. > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Modules - unstable? -newbie
On Fri, Sep 06, 2002 at 04:52:54PM +0200, Setyo Nugroho wrote: > I just configured sound modules, such as soundcore etc. The audio works > fine. The same audio modules were added into /etc/modules, so that > these modules wil be loaded every time the system is booted. > After rebooting, the modules in concern are there (checked using lsmod), > but audio does not work any longer. > > The message after > " $ cat /usr/share/sounds/KDE_Window_UnSticky.wav >dev/audio ", > is: > "bash: dev/audio: No such file or directory" Is that literally 'dev/audio'? If so, try '/dev/audio' instead. -- Colin Watson [[EMAIL PROTECTED]] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Modules - unstable? -newbie
This one time, at band camp, Setyo Nugroho said: > Am happy to have woody installed, after moving from suse. > One thing which makes me grabbling for quite sometime. It may take > sometime to understand the whole scene behind debian and its power. > Nevertheless I still trust this debian more than other popular distros. > > I just configured sound modules, such as soundcore etc. The audio works > fine. The same audio modules were added into /etc/modules, so that > these modules wil be loaded every time the system is booted. > After rebooting, the modules in concern are there (checked using lsmod), > but audio does not work any longer. > > The message after > " $ cat /usr/share/sounds/KDE_Window_UnSticky.wav >dev/audio ", > is: > "bash: dev/audio: No such file or directory" > > Flwg tools were used: insmod, modprobe, modconf, lsmod, rmmod. > > Could some help me, please. > > Setyo Nugroho There are several parts to getting audio to work, but it sounds like you're on the way. The first is hardware and module matching, which it sounds like you've done succesfully. The second is usually a sound server if you're running X - GNOME uses ESD, and KDE uses Arts. Try ps ax to see if either is running. The other is permissions - make sure your user is in group audio. Then, either try to play a sound file from within an app, or cat /usr/share/sounds/KDE_Window_UnSticky.wav > /dev/dsp . According to devices.txt from the kernel source, /dev/dsp is digital audio, while /dev/audio is Sun-compatible digital audio - don't know if both coexist on a normal Debian install, but /dev/dsp has always worked for me. HTH, Steve -- Age is a tyrant who forbids, at the penalty of life, all the pleasures of youth. msg01043/pgp0.pgp Description: PGP signature
Re: Modules?
On Fri, Jun 21, 2002 at 02:50:08PM -0700, curtis wrote: > I just compiled a new kernel (2.4.18) for a machine and installed it. > Well, when I run modconf, I find that the only available module is > dummy.o under kernel/drivers/net. > > And, in fact, this is the only module listed under > /lib/modules/2.4.18/kernel/drivers/net. > > How can I get a full listing of drivers in here? > > Curtis > I have just worked through this problem myself. Do this as root: cd /usr/src ln -s kernel-source-2.4.18 linux cd /usr/src/linux make-kpkg clean (to get rid of bad stuff from before) make-kpkg --revision xyz123 binary Also, if you want all the net drivers, you may want to crib a copy of config-2.4.18 from the kernel image that was built by the maintainer and use it as a starting point for your make config If this doesn't make sense email me directly for more detail. -- Paul E Condon [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Modules at boot time
I'M NOT MEMER OF YOUR MAILING LISTS. WHY THIS MAILS COME TO ME? EVERY DAY COME TO ME 200 MAILS FROM YOUR MAILING LISTS. CAN YOU DO SOMETHING WITH IT? THANK YOU. - Original Message - From: "Chris Kenrick" <[EMAIL PROTECTED]> To: "Kapil Khosla" <[EMAIL PROTECTED]> Cc: Sent: Tuesday, June 04, 2002 5:53 AM Subject: Re: Modules at boot time > On Mon, Jun 03, 2002 at 11:33:55PM -0400, Kapil Khosla wrote: > > Hi, > > I got my sound card to work by doing > > modprobe trident > > modprobe sound > > but I have to do this everytime at boot time. > > I also did update-modules expecting that it will modify the .conf file and I will be all set but that doesnt seem to be the case, > > How should I proceed from here, > > Thanks > > Kapil > > Please set your mailer/editor linewrap from 68-75 chars. 72 is a good default. > > You have a couple of options ... > > You could run modconf(same utility as runs during the Debian install), > which will then write the changes permanently for you. > > Or just manually edit /etc/modules and add those two lines (trident and > sound). > > More detailed info on how it all works can apparently be found in > /usr/share/doc/modutils > > - Chris > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Modules at boot time
I'M NOT MEMER OF YOUR MAILING LISTS. WHY THIS MAILS COME TO ME? EVERY DAY COME TO ME 200 MAILS FROM YOUR MAILING LISTS. CAN YOU DO SOMETHING WITH IT? THANK YOU. - Original Message - From: "Kapil Khosla" <[EMAIL PROTECTED]> To: Sent: Tuesday, June 04, 2002 5:33 AM Subject: Modules at boot time > Hi, > I got my sound card to work by doing > modprobe trident > modprobe sound > but I have to do this everytime at boot time. > I also did update-modules expecting that it will modify the .conf file and I will be all set but that doesnt seem to be the case, > How should I proceed from here, > Thanks > Kapil > > > > > > Outgrown your current e-mail service? > Get a 25MB Inbox, POP3 Access, No Ads and No Taglines with LYCOS MAIL PLUS. > http://login.mail.lycos.com/brandPage.shtml?pageId=plus > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Modules at boot time
On Mon, Jun 03, 2002 at 11:33:55PM -0400, Kapil Khosla wrote: > Hi, > I got my sound card to work by doing > modprobe trident > modprobe sound > but I have to do this everytime at boot time. > I also did update-modules expecting that it will modify the .conf file and I > will be all set but that doesnt seem to be the case, > How should I proceed from here, > Thanks > Kapil Please set your mailer/editor linewrap from 68-75 chars. 72 is a good default. You have a couple of options ... You could run modconf(same utility as runs during the Debian install), which will then write the changes permanently for you. Or just manually edit /etc/modules and add those two lines (trident and sound). More detailed info on how it all works can apparently be found in /usr/share/doc/modutils - Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Modules question
On Thu May 09, 2002 at 04:57:42PM -0400, Seneca wrote: > On Thu, May 09, 2002 at 10:10:05PM +0200, Joachim Fahnenmueller wrote: > > On Thu, May 09, 2002 at 05:21:22AM -0400, Seneca wrote: > > > (all my floppies are fat) > > > > Hope they still fit into the drive ;-) > > They all fit into the drive, but there's this one floppy... I don't know > how it does it, but it gets fatter in the drive and gets stuck. I have > to pull out the tweezers and screw-removers and pull it out (and the > floppy has the tweezer gouges to prove it). > LOL. If you had an old Mac (back when Macs had floppies) you would have to use a paper clip. -- -CraigW -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Modules question
On Thu, May 09, 2002 at 10:10:05PM +0200, Joachim Fahnenmueller wrote: > On Thu, May 09, 2002 at 05:21:22AM -0400, Seneca wrote: > > (all my floppies are fat) > > Hope they still fit into the drive ;-) They all fit into the drive, but there's this one floppy... I don't know how it does it, but it gets fatter in the drive and gets stuck. I have to pull out the tweezers and screw-removers and pull it out (and the floppy has the tweezer gouges to prove it). -- Seneca [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Modules question
On Thu, May 09, 2002 at 05:21:22AM -0400, Seneca wrote: > On Wed, May 08, 2002 at 09:46:27PM -0700, Paul 'Baloo' Johnson wrote: > > On 8 May 2002, Ron Johnson wrote: > > > > > possible, right? Create an hourly cron job that does "rmmod -a", > > > to eliminate any unused modules. > > > > If you do that, do modules get re-inserted as needed? > > I think it would depend upon the kernel. Early in the kernel config, > there is a question about autoloading modules when needed. I haven't > tried kernels without it, but whenever fat support is unloaded, if I use > my floppy (all my floppies are fat), it's loaded. It also depends on the entries in /etc/modules.conf . See: kerneld-mini-HOWTO (available at http://www.linuxdoc.org) (a little outdated, but still very useful) man modules.conf man update-modules . > (all my floppies are fat) Hope they still fit into the drive ;-) Regards, Joachim -- Joachim Fahnenmüller Lehrer für Mathematik und Physik Herder-Gymnasium Kattowitzer Straße 52 51065 Köln -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Modules question
On Thu, 9 May 2002, Seneca wrote: > I think it would depend upon the kernel. Early in the kernel config, > there is a question about autoloading modules when needed. I haven't > tried kernels without it, but whenever fat support is unloaded, if I use > my floppy (all my floppies are fat), it's loaded. Oh, cool. I'll give it a shot, then. -- Baloo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Modules question
On Wed, May 08, 2002 at 09:46:27PM -0700, Paul 'Baloo' Johnson wrote: > On 8 May 2002, Ron Johnson wrote: > > > possible, right? Create an hourly cron job that does "rmmod -a", > > to eliminate any unused modules. > > If you do that, do modules get re-inserted as needed? I think it would depend upon the kernel. Early in the kernel config, there is a question about autoloading modules when needed. I haven't tried kernels without it, but whenever fat support is unloaded, if I use my floppy (all my floppies are fat), it's loaded. -- Seneca [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Modules suddenly missing
On Fri, Mar 01, 2002 at 02:37:06PM +1100, Graham Williams wrote: > About a week ago I updated a Debian box, running a custom kernel > 2.4.16, with a dist-upgrade in unstable (it's been running unstable > for a long time, and this just brought it up to date). > > On the next reboot (a few days later) things started breaking! In > particular nfs, audio, and cdrom and cdrw access. I think I've > tracked the problems to the appropriate kernel modules not being > loaded? Why would a dist-upgrade cause this? I can add nfs, and nfsd > to /etc/modules and NFS is working again. I can add i810_audio and > audio is up agian. Also isofs, ide-cd, ide-probe-disk, and ide-disk > get CDROM going again. I've failed so far to get the CD-RW working > again: A couple of times this has happened to me. Both times the problem was between the keyboard and the seat. Both times I had manually loaded modules, didn't update /etc/modules or files in /etc/modutils, forgot about it and then rebooted. A few other possibilities: If you updated modutils, you may have inadvertently replaced configuration files in /etc/modutils. Since you are using ide-scsi, you may need to load sr-mod. Your cdrw may now be on /dev/sr0. If you have mounted devfs on /dev, you need to have sr-mod loaded, and your cdrw will now be found on /dev/cdrom. Hope this helps. > > # mount /cdrw > mount: /dev/scd0 is not a valid block device > > My questions: > >What could have changed to the modules stuff to cause these to no >longer be loaded on boot? > >Any ideas on why my ide-scsi CD-RW set up would be failing. A >scanbus does not find the ide-scsi CD-RW. > > Thanks > Graham -- Jerome pgpqmOlvuxvSH.pgp Description: PGP signature
Re: modules will taint the kernel?
On Sat, 20 Oct 2001, Paul 'Baloo' Johnson wrote: > On Sun, 21 Oct 2001, Pollywog wrote: > > > Warning, loading /lib/modules/2.4.12/pcmcia/i82365.o will taint the kernel: > > no license > > > Anyone know what this is about and how to fix it? > > It means a particular module is not GPL. Easiest fix: Don't use it. At this stage it actually means that the author hasn't bothered fixing the module to express its license. -jwb
Re: modules will taint the kernel?
On Sun, 21 Oct 2001, Pollywog wrote: > Warning, loading /lib/modules/2.4.12/pcmcia/i82365.o will taint the kernel: > no license > Anyone know what this is about and how to fix it? It means a particular module is not GPL. Easiest fix: Don't use it. -- Baloo
Re: modules will taint the kernel?
On Sun, Oct 21, 2001 at 02:46:36AM +, Pollywog wrote: > I just installed kernel 2.4.12 on my laptop, and when it boots, I get > the following messages: > Warning, loading /lib/modules/2.4.12/pcmcia/i82365.o will taint the > kernel: no license This is due to kernel/modutil incompatibility. There was report in debian-devel ML. In short, stable kernel changed it header file. So binutils compiled with older 2.4 kernel header file will not function properly. Your options are one of followings: 1) remove offending module by "rm" and use modutils 2) Wait for newer binutil in unstable and install it. You are using "testing" so expect some minor glich like this. Cheers. -- ~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ + Osamu Aoki <[EMAIL PROTECTED]>, GnuPG-key: 1024D/D5DE453D + + My debian quick-reference, http://www.aokiconsulting.com/quick/+
Re: modules will taint the kernel?
On Sun, Oct 21, 2001 at 02:46:36AM +, Pollywog wrote: > I just installed kernel 2.4.12 on my laptop, and when it boots, I get > the following messages: > > Warning, loading /lib/modules/2.4.12/pcmcia/i82365.o will taint the > kernel: no license > > I get a similar message for pcmcia/ds.o > > Anyone know what this is about and how to fix it? I just noticed this in 2.4.12; perhaps it's something new. I think it means that the module didn't tell the kernel what license it was published under, or has a license that's incompatible with the GPL. I don't know what you can do about it. >From oops-tracing.txt in the 2.4.12 kernel documentation: Tainted kernels: Some oops reports contain the string 'Tainted: ' after the program counter, this indicates that the kernel has been tainted by some mechanism. The string is followed by a series of position sensitive characters, each representing a particular tainted value. 1: 'G' if all modules loaded have a GPL or compatible license, 'P' if any proprietary module has been loaded. Modules without a MODULE_LICENSE or with a MODULE_LICENSE that is not recognised by insmod as GPL compatible are assumed to be proprietary. 2: 'F' if any module was force loaded by insmod -f, ' ' if all modules were loaded normally. The primary reason for the 'Tainted: ' string is to tell kernel debuggers if this is a clean kernel or if anything unusual has occurred. Tainting is permanent, even if an offending module is unloading the tainted value remains to indicate that the kernel is not trustworthy. -- Lance Simmons
Re: modules - can't get ip
[EMAIL PROTECTED] wrote: > when i boot up i get the message > modprobe: Note the file etc/modules.conf is more recent than the file > /lib/modules/2.4.9/modules.dep run depmod -a or update-modules, both as root. Regards, Joey -- In the beginning was the word, and the word was content-type: text/plain Please always Cc to me when replying to me on the lists.
Re: Modules gone after Kernel update to 2.4.7
On Tue, Jul 31, 2001 at 05:11:44PM -0600, Gary Hennigan wrote: > If you're running potato look at the debian-user list archive. I seem > to recall a post on how to run a 2.4.x kernel on potato. That post would be from Adrian Bunk who is maintaining package sets to allow 2.4.x kernels to work with potato. (Thank you Adrian). I think the URL you seek is http://people.debian.org/~bunk/debian/dists/potato/main/binary-i386/ I'm not sure what the apt line for that is :) I don't run potato anymore. Probably it's deb http://people.debian.org/~bunk/debian potato main Cheers, -- Nathan Norman - Staff Engineer | A good plan today is better Micromuse Ltd. | than a perfect plan tomorrow. mailto:[EMAIL PROTECTED] | -- Patton pgpPJrI7BfbY1.pgp Description: PGP signature
Re: Modules gone after Kernel update to 2.4.7
"Herbert Pirke" <[EMAIL PROTECTED]> writes: > I recently upgraded my Kernel from 2.2.19 to 2.4.7. > Everything worked fine at the first glance. But when I > try using functins that are available vie kernel > modules, I get a message saying "xxx not supported by > kernel" (or something similar). A modprobe ends with a > mesage saying "Cannot find module xxx". However an > insmod with the exact path works flawlessly... > > This looks like some missing paths to me. How and > where are these configurated? > > Or could it be that there is some kerneld > configuration missing? When I compiled my kernel, I > realised that the kerneld-option does not exist any > more. It only say "loadable module support" which I > checked of course. Modutils is installed of course... What debian distribution are you running? I hope it's "testing/woody" or "unstable/sid" because I don't think the modutils package in "stable/potato" can handle the new 2.4.x way of doing kernel modules. If you're running potato look at the debian-user list archive. I seem to recall a post on how to run a 2.4.x kernel on potato. Gary
Re: Modules gone after Kernel update to 2.4.7
* Herbert Pirke ([EMAIL PROTECTED]) [010731 19:08]: > Hi, > > I recently upgraded my Kernel from 2.2.19 to 2.4.7. > checked of course. Modutils is installed of course... But what version of modutils ?? The dir structure of modules changed with the 2.4 series of kernels and older modutils won't know or understand it. You need v2.4.2 or greater... I run "unstable" and it's up to 2.4.6. Regards Hall
Re: Modules gone after Kernel update to 2.4.7
on Tue, Jul 31, 2001 at 03:21:09PM -0700, Herbert Pirke ([EMAIL PROTECTED]) wrote: > Hi, > > I recently upgraded my Kernel from 2.2.19 to 2.4.7. Everything worked > fine at the first glance. But when I try using functins that are > available vie kernel modules, I get a message saying "xxx not > supported by kernel" (or something similar). A modprobe ends with a > mesage saying "Cannot find module xxx". However an insmod with the > exact path works flawlessly... > > This looks like some missing paths to me. How and where are these > configurated? > > Or could it be that there is some kerneld configuration missing? When > I compiled my kernel, I realised that the kerneld-option does not > exist any more. It only say "loadable module support" which I checked > of course. Modutils is installed of course... Have you run update-modules? -- Karsten M. Self http://kmself.home.netcom.com/ What part of "Gestalt" don't you understand? There is no K5 cabal http://gestalt-system.sourceforge.net/ http://www.kuro5hin.org Free Dmitry!! Boycott Adobe!! Repeal the DMCA!! http://www.freesklyarov.org pgphAC17oJj9Z.pgp Description: PGP signature
Re: Modules install
We're drifting towards questions that are more appropriate for debian-user. Thu, Jul 19, 2001 at 10:41:45AM -0400 wrote: > > The modules should be on your filesystem already. To install more you can > > 1 - use 'modconf' > > Cool! modconf is great, but how can I select all the modules en masse? The > reason I want to do this is because doing each module one at a time is really > time consuming. Actually, I don't have the first clue about what ISA ethernet > cards I've got installed, so I want to throw all the 'net' drivers I can at > the problem. ;-) For this you don't need/want modconf. If you want to do the brute-force method, which has some drawbacks: # cd /lib/modules/`uname -r`/ Depending on you kernel version you will have modules in net/ or kernel/net/ # mopdprobe * Or install the package libdetect0, which, depending on your hardware, will detect your card and tell you what module to use. -David
Re: Modules issues
On Tue, Jun 12, 2001 at 11:06:47AM -0700, Michael Dickey wrote: > After installing the kernel & modules I just compiled > I find that when booting there are all sorts of error > messages, most including something about modules.conf > being more recent than modules.dep. I can only glimpse > the messages before they are gone. Everything seems to > work fine, though. Is there something that I can do to > clean things up and eliminate the errors? You could try - "update-modules" or "depmode -a" but last time I got this I ended up just changing the timestamp on /etc/modules.conf with "touch" so the bitching would stop. hth, kent -- From seeing and seeing the seeing has become so exhausted First line of "The Panther" - R. M. Rilke
Re: modules
Thanks. If you look in the help it does say that it supports cs46xx chipsets. Do you know how I could file a bug report for this. (I think it's a bug. After all the option should say what chipsets it supports without looking in the Help right?) Thanks again, Andy "Keith G. Murphy" wrote: > I'm pretty sure it's the item "Crystal Sound Fusion" under "Sound card > support". > > Are you using the 2.2.18pre21 kernel source package or some other? > > "Andrew D Dixon,,," wrote: > > > > Hi All, > > I'm trying to compile support for my sound card into my kernel but I > > can't find an option for it in make config or make xconfig. I have, > > however, found the source for the right driver in sound/driver (it's > > cx46xx.c, I've got a Turtle Beach Santa Cruz based on the CS4630 chip). > > > > I was wondering how I could compile this as a module and install it in > > my system. > > > > Any hints, tips, pointers, advice . . . would be greatly appreciated. > > > > Thanks, > > Andy > > > > -- > > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- > I would rather spend 10 hours reading someone else's source code than > 10 minutes listening to Musak waiting for technical support which isn't. > -- Dr. Greg Wettstein, Roger Maris Cancer Center > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: modules
I'm pretty sure it's the item "Crystal Sound Fusion" under "Sound card support". Are you using the 2.2.18pre21 kernel source package or some other? "Andrew D Dixon,,," wrote: > > Hi All, > I'm trying to compile support for my sound card into my kernel but I > can't find an option for it in make config or make xconfig. I have, > however, found the source for the right driver in sound/driver (it's > cx46xx.c, I've got a Turtle Beach Santa Cruz based on the CS4630 chip). > > I was wondering how I could compile this as a module and install it in > my system. > > Any hints, tips, pointers, advice . . . would be greatly appreciated. > > Thanks, > Andy > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- I would rather spend 10 hours reading someone else's source code than 10 minutes listening to Musak waiting for technical support which isn't. -- Dr. Greg Wettstein, Roger Maris Cancer Center
Re: modules
I see it under 2.2.18pre21. It's actually cs46xx.c. ^ Wojciech Milek wrote: > > Which kernel do you have? I can't find this module in 2.2.18 > > W > > > Hi All, > > I'm trying to compile support for my sound card into my kernel but I > > can't find an option for it in make config or make xconfig. I have, > > however, found the source for the right driver in sound/driver (it's > > cx46xx.c, I've got a Turtle Beach Santa Cruz based on the CS4630 chip). > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- I would rather spend 10 hours reading someone else's source code than 10 minutes listening to Musak waiting for technical support which isn't. -- Dr. Greg Wettstein, Roger Maris Cancer Center
RE: modules
Which kernel do you have? I can't find this module in 2.2.18 W > Hi All, > I'm trying to compile support for my sound card into my kernel but I > can't find an option for it in make config or make xconfig. I have, > however, found the source for the right driver in sound/driver (it's > cx46xx.c, I've got a Turtle Beach Santa Cruz based on the CS4630 chip). >
Re: Modules, modprobe, and 2.4.1 kernel
On Sat, 17 Feb 2001, David B. Harris wrote: > To quote "Dean A. Roman" <[EMAIL PROTECTED]>, > # Hello all, > # > #I recently configured, compiled, and installed the 2.4.1 kernel. > So > # far things are going ok with it. > # > # However, modprobe has stopped working correctly, and can't find any > # modules. > > Chances are, you need a newer version of modutils. Here's a quick way to > get the appropriate version, made for your particular platform(Debian > Potato, I'm guessing). > > [explanation how to compile modutils yourself] >... I have already compiled the packages you may need when runnng kernel 2.4.1 on potato (including modutils). See [1] for more information. > David Barclay Harris, Clan Barclay cu, Adrian [1] http://www.fs.tum.de/~bunk/kernel-24.html -- Nicht weil die Dinge schwierig sind wagen wir sie nicht, sondern weil wir sie nicht wagen sind sie schwierig.
Re: Modules, modprobe, and 2.4.1 kernel
Have you installed the latest modutils? Greetz, Sebastiaan On Fri, 16 Feb 2001, Dean A. Roman wrote: > Hello all, > >I recently configured, compiled, and installed the 2.4.1 kernel. So > far things are going ok with it. > > However, modprobe has stopped working correctly, and can't find any > modules. > > I looked in /lib/modules/2.4.1/kernel/drivers/net and found drivers > (3c509.o) for the modules I am trying to load, however modprobe can't > find them. > If I go into the /lib/modules/2.4.1/kernel/drivers/net directory and > use "insmod 3c509.o", then insmod will load the module. > > Why can't modprobe find my modules any more? It worked fine on my older > 2.0.36 and 2.2.14 kernels? > What do I need to do to tell modprobe where to find the new modules? > > Thanks for any help you can give! > > ---Dean Roman (Email - [EMAIL PROTECTED]) > > > >
Re: Modules, modprobe, and 2.4.1 kernel
To quote "Dean A. Roman" <[EMAIL PROTECTED]>, # Hello all, # #I recently configured, compiled, and installed the 2.4.1 kernel. So # far things are going ok with it. # # However, modprobe has stopped working correctly, and can't find any # modules. Chances are, you need a newer version of modutils. Here's a quick way to get the appropriate version, made for your particular platform(Debian Potato, I'm guessing). 1) Add a deb-src line in /etc/apt/sources.list pointing to "testing", as opposed to "potato" or "stable". Remove this line when you're done. 2) As root, 'apt-get -b source modutils'. 3) As root, 'dpkg -i '. There you go :) If you read /path/to/kernel/sources/Documentation/Changes , you'll see the versions of all the programs you need to run a 2.4.x kernel. # Thanks for any help you can give! No probs. In return for this help, please refrain from posting your question multiple times to the mailing list. David Barclay Harris, Clan Barclay Aut agere, aut mori. (Either action, or death.)
Re: modules quit loading automatically all of the sudden
> From: Martin Albert <[EMAIL PROTECTED]> > On Thu, 01 Feb 2001, Daniel Barclay wrote: > > ... > > All of the sudden, various modules don't load when I boot (sound modules > > for a basic SoundBlaster and ftape). > > > > I haven't been messing with my configuration. Things worked last time > > I booted a couple of days ago. > > No apt-get, new kernel installed? Sure? Nope. (Well...yes, I'm sure; nope, no apt or kernel.) In fact, I just compared /etc/... and /lib/modules/... to the data from three or four backup tapes over the last couple of months. I see few changes, and none that seem relevant. Is there anything else I should check for changes? > > "modprobe" says: > > modprobe: Nothing to load ??? > > Specify at least a module or a wildcard like \* > > > > Any ideas about what I should look at? > > modprobe sb > > what happens? That seemed to load the sounds modules. Any idea why modules wouldln't be loading automatically? Daniel -- Daniel Barclay [EMAIL PROTECTED] (Hmm. A little worrisome: http://www.junkbusters.com/cgi-bin/privacy http://www.anonymizer.com/snoop.cgi )
Re: modules quit loading automatically all of the sudden
On Thu, 01 Feb 2001, Daniel Barclay wrote: > I have a strange problem. > > All of the sudden, various modules don't load when I boot (sound modules > for a basic SoundBlaster and ftape). > > I haven't been messing with my configuration. Things worked last time > I booted a couple of days ago. No apt-get, new kernel installed? Sure? > Any ideas what might have changed? What I might have changed accidentally? > > > "modprobe" says: > modprobe: Nothing to load ??? > Specify at least a module or a wildcard like \* > > Any ideas about what I should look at? modprobe sb what happens? greetings, martin
Re: modules
Please don't reply to an existing message when you are starting a new topic. Some of us use threading mail/news readers, so your message appears as a response to the message titled "Q: SB16 ok-Need load other modules?". I notice that most people who do this are running Micro$oft operating systems, so is there something about them that makes it difficult to start new topics? I am not picking on anybody in particular, since there have been several people doing this lately. -- Carl Johnson[EMAIL PROTECTED]
Re: modules
Hi, is that not something like depmod does, but then better? You have my support! Greetz, Sebastiaan On Wed, 17 Jan 2001, John Griffiths wrote: > over the last few days i've been wrestling with a lot of cryptic modules. and > so it would seem have others, judging by the list. > > how difficult would it be to make an apt-like module tool? > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > >
Re: Modules Not Loading
On Fri, Jan 12, 2001 at 12:55:41AM -0600, Benjamin Pharr wrote: > At 11:28 PM 1/11/01 , Kenward Vaughan wrote: ... > >Have you just upgraded to the 2.4.0 kernel? If so, you need to make sure > >you have the latest modutils package as well, as the older version doesn't > >recognize the 2.4.0 modules directory structure. > > > Is the most recent modutils Debian package up to date with 2.4.0? In unstable (and testing, I believe) it is. If you are using Potato, you have to upgrade. Kenward -- It is not so very important for a person to learn facts. For that he doesn't really need a college education, for he can learn them from books. The value of an education in a liberal arts college is not the learning of many facts but the training of the mind to thinking--something that cannot be learned from books. Albert Einstein
Re: Modules Not Loading
» Benjamin Pharr said this and I say that: > At 11:28 PM 1/11/01 , Kenward Vaughan wrote: > >Have you just upgraded to the 2.4.0 kernel? If so, you need to make sure > >you have the latest modutils package as well, as the older version doesn't > >recognize the 2.4.0 modules directory structure. > > > Is the most recent modutils Debian package up to date with 2.4.0? No. You must get the debs OR (and I recommend that) get the sources and build it yourself. To get the complete list of packages needes by kernel 2.4.0, see ./Documentation/Changes, assuming you're at the kernel source root. -- []'s, francisco m. neto (a.k.a ikari himura keiichi) Linux User #192809 ICQ #78493934 http://socrates.if.usp.br/~einstein "Toke au kokoro ga, watashi o kowasu" -- Ayanami Rei
Re: Modules Not Loading
At 11:28 PM 1/11/01 , Kenward Vaughan wrote: On Thu, Jan 11, 2001 at 11:01:13PM -0600, Benjamin Pharr wrote: > I have several modules in the /etc/modules file that are supposed to be > loaded upon boot. I receive an error message for each one saying that > can't be loaded. I know they were built and installed. I have checked and > they are in the right place. I have tried to load them manually with > insmod and depmod, but the modules still can't be found. It's very likely > I could be using the wrong syntax, but that doesn't solve the problem of > them not being loaded on boot. Can anyone help? ... Have you just upgraded to the 2.4.0 kernel? If so, you need to make sure you have the latest modutils package as well, as the older version doesn't recognize the 2.4.0 modules directory structure. Is the most recent modutils Debian package up to date with 2.4.0? Ben
Re: Modules Not Loading
On Thu, Jan 11, 2001 at 11:01:13PM -0600, Benjamin Pharr wrote: > I have several modules in the /etc/modules file that are supposed to be > loaded upon boot. I receive an error message for each one saying that > can't be loaded. I know they were built and installed. I have checked and > they are in the right place. I have tried to load them manually with > insmod and depmod, but the modules still can't be found. It's very likely > I could be using the wrong syntax, but that doesn't solve the problem of > them not being loaded on boot. Can anyone help? ... Have you just upgraded to the 2.4.0 kernel? If so, you need to make sure you have the latest modutils package as well, as the older version doesn't recognize the 2.4.0 modules directory structure. Kenward -- It is not so very important for a person to learn facts. For that he doesn't really need a college education, for he can learn them from books. The value of an education in a liberal arts college is not the learning of many facts but the training of the mind to thinking--something that cannot be learned from books. Albert Einstein
Re: Modules and kernel upgrades
thanks On Tue, 19 Dec 2000, Denzil Kelly wrote: > Date: Tue, 19 Dec 2000 20:16:36 -0800 (PST) > From: Denzil Kelly <[EMAIL PROTECTED]> > To: dude <[EMAIL PROTECTED]>, debian-user@lists.debian.org > Cc: [EMAIL PROTECTED] > Subject: Re: Modules and kernel upgrades > > Yes, I had this problem a few weeks back. I posted a > message here and here is the fix that worked for me. > > Ah! What you have there is a gotcha in the current > Debian > kernel-building > documentation. Most dists put a .config in the linux > directory that > reflects > the options used to build the distributed kernel. > Debian doesn't. > However, > you can get it from /boot/config-2.2.17 (if you are > running Potato). > Copy > that file to /usr/src/linux/.config before running > make menuconfig or > make > xconfig. > > In your situation, I think the make-kpkg routine puts > the new config in > the > /boot dir. The old one will be available as > /boot/config-2.2.17.bak. > > --- dude <[EMAIL PROTECTED]> wrote: > > > > Hi all. im not sure where to find this information > > > > ive read some of the documetntaion > > > > the problem is that when i install and compile a new > > kernel > > and then make modules > > and > > > > make modules install > > > > everything seems to work, > > > > but when i boot up > > > > i see a lot of messages about modules not found > > > > what is going on? > > > > thanks > > > > > > > > -- > > To UNSUBSCRIBE, email to > > [EMAIL PROTECTED] > > with a subject of "unsubscribe". Trouble? Contact > > [EMAIL PROTECTED] > > > > > __ > Do You Yahoo!? > Yahoo! Shopping - Thousands of Stores. Millions of Products. > http://shopping.yahoo.com/ >
Re: Modules and kernel upgrades
Yes, I had this problem a few weeks back. I posted a message here and here is the fix that worked for me. Ah! What you have there is a gotcha in the current Debian kernel-building documentation. Most dists put a .config in the linux directory that reflects the options used to build the distributed kernel. Debian doesn't. However, you can get it from /boot/config-2.2.17 (if you are running Potato). Copy that file to /usr/src/linux/.config before running make menuconfig or make xconfig. In your situation, I think the make-kpkg routine puts the new config in the /boot dir. The old one will be available as /boot/config-2.2.17.bak. --- dude <[EMAIL PROTECTED]> wrote: > > Hi all. im not sure where to find this information > > ive read some of the documetntaion > > the problem is that when i install and compile a new > kernel > and then make modules > and > > make modules install > > everything seems to work, > > but when i boot up > > i see a lot of messages about modules not found > > what is going on? > > thanks > > > > -- > To UNSUBSCRIBE, email to > [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > __ Do You Yahoo!? Yahoo! Shopping - Thousands of Stores. Millions of Products. http://shopping.yahoo.com/
Re: Modules not showing up after compile - why?
On Mon, Dec 04, 2000 at 03:04:53PM +, Anthony Campbell wrote: > On 04 Dec 2000, Harry Henry Gebel wrote: > > On Mon, Dec 04, 2000 at 12:16:35PM +, Anthony Campbell wrote: > > > However, lsmod and modprobe show nothing: there is no /proc/ksyms or > > > /proc/modules. > > > Questions: why don't these things show up, and how does the kernel work > > > if the modules aren't there? > > Did you run LILO after you installed the kernel? If you didn't you are > > probably still booting into your old kernel. If you run `dmesg` you will > > get a list off all the boot-up messages; the first one will include the > > data the kernel was compiles. If you enabled modules you should have > > /proc/modules even if it's empty (assuming you have /proc mounted). > You're right; I had the wrong kernel loaded! > Now that I've got the right one, I again can't use sound or access my > parallel port. I get: > The kernel does not recognize /dev/sda1 as a block device > (maybe insmod driver?) > Opening /dev/audio: no such device. > I don't know which drivers to install with insmod. Anyway, I thought the > kernel was supposed to call these things automatically? I don't know much about setting up module autoloading, but I'm sure somebody on the list can tell you more, make the subject "setting up module autoloading" or something similar to get their attention. Still, I get on pretty good without it using modprobe. Modprobe is a program loads a driver and any other drivers that driver depends on. The command for an older zip drive is `modprobe ppa`, or for a newer one `modprobe imm`. On some systems I can't get ppa to load while lp is loaded, if you have this problem run `rmmod lp` to unload the lp driver first. The configuration of the sound card must be setup before you can load the sound driver, if you use the ALSA modules they can be configured with a program called `alsaconf`, I don't know what the configuration program is for the OSS drivers, but I'm sure there is one. My usual policy is to compile anything I use 100% of the time into the kernel, so when I was using OSS I always compiled it into the kernel. I usually have the following compiled as modules. IDE CDROM drive Floppy drive Serial ports ppp Zip drive ALSA (only because I don't know how to compile them into the kernel) I don't compile lp support at all, but if you have a printer attached to the computer you will need that too, if you do you definitely want to compile it as a module so you can unload it if it decides not to get along with ppa (although if they were getting along when they were both compiled in they will probably get along with both as modules, but I have found this to vary from system to system.) I haven't done anything to set up module autoloading but everything loads automatically except ppa. (and ALSA, but alsaconf sets that up to get loaded during boot-up so it is functionally the same as being loaded automatically.) If you look in /proc/modules you will probaly see that some at least have already been loaded for you. The modules are in subdirectories of /lib/modules/kernel-version-number , if you need to know the name of a driver you can usually figure it out by digging around in there (the name of the module is the file name with the .o removed, so the ppa driver is ppa.o , etc.) -- Harry Henry Gebel, ICQ# 76308382 West Dover Hundred, Delaware
Re: Modules not showing up after compile - why?
On 04 Dec 2000, Harry Henry Gebel wrote: > On Mon, Dec 04, 2000 at 12:16:35PM +, Anthony Campbell wrote: > > However, lsmod and modprobe show nothing: there is no /proc/ksyms or > > /proc/modules. > > > > Questions: why don't these things show up, and how does the kernel work > > if the modules aren't there? > > Did you run LILO after you installed the kernel? If you didn't you are > probably still booting into your old kernel. If you run `dmesg` you will > get a list off all the boot-up messages; the first one will include the > data the kernel was compiles. If you enabled modules you should have > /proc/modules even if it's empty (assuming you have /proc mounted). > You're right; I had the wrong kernel loaded! Now that I've got the right one, I again can't use sound or access my parallel port. I get: The kernel does not recognize /dev/sda1 as a block device (maybe insmod driver?) Opening /dev/audio: no such device. I don't know which drivers to install with insmod. Anyway, I thought the kernel was supposed to call these things automatically? Anthony -- Anthony Campbell - running Linux Debian 2.2 (Windows-free zone) Over 100 book reviews: http://www.cix.co.uk/~acampbell/bookreviews/ Skeptical essays: http://www.cix.co.uk/~acampbell/freethinker/ "Palo y tente tieso." (Spanish proverb) Free translation: "Holdfast is your only dog."
Re: Modules not showing up after compile - why?
Hi, how did you compile the kernel? Basically, it works the following: make menuconfig (config or xconfig will also work) make clean make dep make bzImage make modules_install<-- have you done this? If you are not sure if your new kernel will work, make a copy of the modules: mv /lib/modules/2.2.17 /lib/modules/2.2.17.org before executing make modules_install. Greetings, Sebastiaan ps: you can still try running modules_install now and see if it works. On Mon, 4 Dec 2000, Anthony Campbell wrote: > Sorry for this basic query; I've always used monolithic kernels but > decided to build a modules version to try it out and I don't understand > what's happening.. > > I selected various modules and built the kernel. I included the kernel > module loader to enable automatic loading of modules. The kernel > compiled OK and I booted with it without problems. All the functions > seem to be implemented as I expected. > > > However, lsmod and modprobe show nothing: there is no /proc/ksyms or > /proc/modules. > > Questions: why don't these things show up, and how does the kernel work > if the modules aren't there? > > Anthony > > -- > Anthony Campbell - running Linux Debian 2.2 (Windows-free zone) > Over 100 book reviews: http://www.cix.co.uk/~acampbell/bookreviews/ > Skeptical essays: http://www.cix.co.uk/~acampbell/freethinker/ > > "Palo y tente tieso." (Spanish proverb) > Free translation: "Holdfast is your only dog." > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > >
Re: Modules not showing up after compile - why?
On Mon, Dec 04, 2000 at 12:16:35PM +, Anthony Campbell wrote: > However, lsmod and modprobe show nothing: there is no /proc/ksyms or > /proc/modules. > > Questions: why don't these things show up, and how does the kernel work > if the modules aren't there? Did you run LILO after you installed the kernel? If you didn't you are probably still booting into your old kernel. If you run `dmesg` you will get a list off all the boot-up messages; the first one will include the data the kernel was compiles. If you enabled modules you should have /proc/modules even if it's empty (assuming you have /proc mounted). -- Harry Henry Gebel, ICQ# 76308382 West Dover Hundred, Delaware
Re: Modules
T wrote: > > Hi, > i just got a cd drive for my computer and i was wondering what module i > should install to use it? It is a 40x Diamond Data. Could someone please > help me. I also got an internal modem. How do i get it to recognise this? > When i try to set up a ppp account, it will not detect it as a modem. > THanks > Scott > > ___ Probably one of those winmodems-not-modems-thingies. There's limited support for some of that stuff, but still a shitty modem... I believe Lucent has a binary-only driver for their winmodems. IIRC, you need to enable cd-rom support in your kernel. Hth Vitux -- "I'm not a crook" Richard Nixon Debian GNU/Linux Micro$loth-free Zone
Re: Modules
what kind of controller is the cdrom hooked up to? the onboard ide controller? if so you need no module, if it is hooked up to a sound card or something you must specify the soundcard or other controller for someone to assist you. as for the modem is it a hardware modem? what com port is it set to? what brand/model is the modem? nate On Sat, 3 Jun 2000, T wrote: icy4 >Hi, icy4 >i just got a cd drive for my computer and i was wondering what module i should install to use it? It is a 40x Diamond Data. Could someone please help me. I also got an internal modem. How do i get it to recognise this? When i try to set up a ppp account, it will not detect it as a modem. icy4 >THanks icy4 >Scott icy4 > icy4 >___ icy4 >GO Network Mail icy4 >Get Your Free, Private E-mail at http://mail.go.com icy4 > icy4 > icy4 > icy4 >-- icy4 >Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null icy4 > ::: http://www.aphroland.org/ http://www.linuxpowered.net/ [EMAIL PROTECTED] 10:35am up 6 days, 19:37, 1 user, load average: 0.02, 0.04, 0.00
Re: modules
Chris Gray <[EMAIL PROTECTED]> wrote: >On Mon, May 01, 2000 at 02:31:12PM +0100, Colin Watson wrote: >> jason <[EMAIL PROTECTED]> wrote: >> >is there a way to build a specific module from kernel source and install >> >it? without haveing to build a new kernel and do a make modules and such? >> >> Yes. Do a 'make modules' in the kernel tree, then just copy the sound >> module (something.o) from wherever it gets built into the right place in >> /lib/modules. Then do '/sbin/depmod -a' and modprobe the module. > >Even easier than "copying the module into the right place" is 'make >modules_install' which does it automagically. Indeed, if you don't mind it blatting your old ones. :) I wasn't sure if the original poster would mind that, or if he wanted to be more surgical about it. -- Colin Watson [EMAIL PROTECTED]
Re: modules
On Mon, May 01, 2000 at 02:31:12PM +0100, Colin Watson wrote: > jason <[EMAIL PROTECTED]> wrote: > >is there a way to build a specific module from kernel source and install > >it? without haveing to build a new kernel and do a make modules and such? > > Yes. Do a 'make modules' in the kernel tree, then just copy the sound > module (something.o) from wherever it gets built into the right place in > /lib/modules. Then do '/sbin/depmod -a' and modprobe the module. Even easier than "copying the module into the right place" is 'make modules_install' which does it automagically. Good luck, Chris -- pick, pack, pock, puck: like drops of water in a fountain falling softly in the brimming bowl.
Re: modules
jason <[EMAIL PROTECTED]> wrote: >is there a way to build a specific module from kernel source and install >it? without haveing to build a new kernel and do a make modules and such? Yes. Do a 'make modules' in the kernel tree, then just copy the sound module (something.o) from wherever it gets built into the right place in /lib/modules. Then do '/sbin/depmod -a' and modprobe the module. -- Colin Watson [EMAIL PROTECTED]
Re: Modules & name resolution
On Tue, Apr 25, 2000 at 10:56:04PM -0500, w trillich wrote > John Pearson wrote: > > > > On Mon, Apr 24, 2000 at 03:02:42PM +0200, Kovacs Istvan wrote > > > Hello! > > > > > > I've just installed potato, re-compiled the kernel, and now (some of) > > > my modules will not auto-load. I can load them with modprobe and/or > > > insmod. I have to load the driver for my Initio SCSI card, SB AWE32 > > > sound card and RTL8019-based NIC by hand. The question is: why? And of > > > course: how do I correct the situation? > > [snip] > > > After editing files in /etc/modutils always run update-modules, > > so that /etc/conf.modules gets updated. > > conf.modules? or modules.conf? > Well, that apparently depends on which release you're tracking, and when you last updated it. I'm a slink man myself. > my syslog was complaining of something quite similar, so maybe > you already helped my problem a bit. from syslog... > Apr 25 21:29:48 server modprobe: Note: /etc/modules.conf is more > recent than /lib/modules/2.0.36/modules.dep > Apr 25 21:29:48 server insmod: Note: /etc/modules.conf is more recent > than /lib/modules/2.0.36/modules.dep > > but i probably need more help yet... > Others have reported similar problems after upgrading to recent modutils, and have been told to run # depmod -a to update modules.dep. Maybe that will help. > i recently did the apt-get dist-upgrade and hadn't rebooted since... > until today. now we've got similar troubles to those Kovacs wrote > about, above... > > most important to us is getting connected to the 'net. what a pain! > need all kinds of handwaving before it gets past "SIOCADDRT" errors > and lets us ping out thru eth1 to the 'net. > > by handwaving, i mean stabbing in the dark with tries like > init 1 > ifup # SIOCADDRT: Network is unreachable > /etc/init.d/networking start # SIOCADDRT error > ipmasq > ping some.host.org # also breaks > init 2 > repeating and stabbing until a ping actually works. > then everything is fine even tho it seems sketchy... > > right now, i tried > # ifup > SIOCADDRT: Network is unreachable > eh?! > > yet i can ping anywhere, POP and SMTP email, DNS is working > like a champ. very odd... > Can't really comment on that, as it's a potato thing with which I'm not familiar. Did your apt-get dist-upgrade complete OK? Do you see any alarming messages if you run apt-get check? It could be you're only halfway through the upgrade. > in case of accidental relevancy here are some log slices-- > > from /var/log/messages: > Apr 25 22:03:05 server syslogd 1.3-3#33: restart. > Apr 25 22:03:05 server kernel: klogd 1.3-3#33, log source = /proc/kmsg > started. > Apr 25 22:03:05 server kernel: Cannot find map file. > Apr 25 22:03:05 server kernel: Loaded 28 symbols from 6 modules. > > from /var/log/syslog: > Apr 25 22:03:05 server named[1896]: listening on [127.0.0.1].53 (lo) > Apr 25 22:03:05 server named[1896]: listening on [192.168.1.1].53 (eth0) > Apr 25 22:03:05 server named[1896]: listening on [208.33.90.85].53 (eth1) > Apr 25 22:03:05 server named[1896]: Forwarding source address is > [0.0.0.0].1130 > Apr 25 22:03:05 server named[1897]: Ready to answer queries. > Apr 25 22:03:05 server /sbin/rpc.statd[1901]: unable to register > (SM_PROG, SM_VERS, udp). > Apr 25 22:03:05 server ypbind[1915]: Unable to register (YPBINDPROG, > YPBINDVERS, udp). > Apr 25 22:03:06 server /usr/sbin/gpm[1924]: Skipping a data packet (?) > Apr 25 22:03:08 server rwhod[2002]: sending on interface eth1 > Apr 25 22:03:08 server rwhod[2002]: sending on interface eth0 > Apr 25 22:03:09 server ntpdate[2005]: step time server 128.46.154.76 > offset -0.833622 sec > Apr 25 22:03:09 server afpd[2018]: main: atp_open: Invalid argument > Apr 25 22:03:09 server afpd[2018]: ASIP started on 208.33.90.85:548(0) > (1.4b2+asun2.1.3) > Apr 25 22:03:09 server papd[2020]: restart (1.4b2+asun2.1.3) > Apr 25 22:03:09 server proftpd[2026]: server - ProFTPD 1.2.0pre9 > standalone mode STARTUP > Apr 25 22:03:09 server /usr/sbin/cron[2033]: (CRON) INFO (pidfile fd = 3) > Apr 25 22:03:09 server /usr/sbin/cron[2034]: (CRON) STARTUP (fork ok) > Apr 25 22:07:12 server modprobe: modprobe: Can't locate module net-pf-18 > Apr 25 22:07:14 server last message repeated 3 times > > unable to register? invalid argument? missing module? > i'm guessing "net-pf-18" is significant... how do i get that? > The "net-pf-18" message is the kernel trying to load the module for network protocol family 18, which linux/include/net/socket.h lists as "Ash", with which I'm not familiar. If it represents a protocol family that you don't intend to support, or you just want to get rid of the messages, add alias net-pf-18 off to /etc/modutils/aliases and then run update-modules. I'd guess it's something to do with AppleTalk, and I'd avoid getting alarmed; the AppleTalk suite includes several protocols, only a few of which you are likely to need to talk to Macs on
Re: Modules & name resolution
John Pearson wrote: > > On Mon, Apr 24, 2000 at 03:02:42PM +0200, Kovacs Istvan wrote > > Hello! > > > > I've just installed potato, re-compiled the kernel, and now (some of) > > my modules will not auto-load. I can load them with modprobe and/or > > insmod. I have to load the driver for my Initio SCSI card, SB AWE32 > > sound card and RTL8019-based NIC by hand. The question is: why? And of > > course: how do I correct the situation? [snip] > After editing files in /etc/modutils always run update-modules, > so that /etc/conf.modules gets updated. conf.modules? or modules.conf? my syslog was complaining of something quite similar, so maybe you already helped my problem a bit. from syslog... Apr 25 21:29:48 server modprobe: Note: /etc/modules.conf is more recent than /lib/modules/2.0.36/modules.dep Apr 25 21:29:48 server insmod: Note: /etc/modules.conf is more recent than /lib/modules/2.0.36/modules.dep but i probably need more help yet... i recently did the apt-get dist-upgrade and hadn't rebooted since... until today. now we've got similar troubles to those Kovacs wrote about, above... most important to us is getting connected to the 'net. what a pain! need all kinds of handwaving before it gets past "SIOCADDRT" errors and lets us ping out thru eth1 to the 'net. by handwaving, i mean stabbing in the dark with tries like init 1 ifup # SIOCADDRT: Network is unreachable /etc/init.d/networking start # SIOCADDRT error ipmasq ping some.host.org # also breaks init 2 repeating and stabbing until a ping actually works. then everything is fine even tho it seems sketchy... right now, i tried # ifup SIOCADDRT: Network is unreachable eh?! yet i can ping anywhere, POP and SMTP email, DNS is working like a champ. very odd... in case of accidental relevancy here are some log slices-- from /var/log/messages: Apr 25 22:03:05 server syslogd 1.3-3#33: restart. Apr 25 22:03:05 server kernel: klogd 1.3-3#33, log source = /proc/kmsg started. Apr 25 22:03:05 server kernel: Cannot find map file. Apr 25 22:03:05 server kernel: Loaded 28 symbols from 6 modules. from /var/log/syslog: Apr 25 22:03:05 server named[1896]: listening on [127.0.0.1].53 (lo) Apr 25 22:03:05 server named[1896]: listening on [192.168.1.1].53 (eth0) Apr 25 22:03:05 server named[1896]: listening on [208.33.90.85].53 (eth1) Apr 25 22:03:05 server named[1896]: Forwarding source address is [0.0.0.0].1130 Apr 25 22:03:05 server named[1897]: Ready to answer queries. Apr 25 22:03:05 server /sbin/rpc.statd[1901]: unable to register (SM_PROG, SM_VERS, udp). Apr 25 22:03:05 server ypbind[1915]: Unable to register (YPBINDPROG, YPBINDVERS, udp). Apr 25 22:03:06 server /usr/sbin/gpm[1924]: Skipping a data packet (?) Apr 25 22:03:08 server rwhod[2002]: sending on interface eth1 Apr 25 22:03:08 server rwhod[2002]: sending on interface eth0 Apr 25 22:03:09 server ntpdate[2005]: step time server 128.46.154.76 offset -0.833622 sec Apr 25 22:03:09 server afpd[2018]: main: atp_open: Invalid argument Apr 25 22:03:09 server afpd[2018]: ASIP started on 208.33.90.85:548(0) (1.4b2+asun2.1.3) Apr 25 22:03:09 server papd[2020]: restart (1.4b2+asun2.1.3) Apr 25 22:03:09 server proftpd[2026]: server - ProFTPD 1.2.0pre9 standalone mode STARTUP Apr 25 22:03:09 server /usr/sbin/cron[2033]: (CRON) INFO (pidfile fd = 3) Apr 25 22:03:09 server /usr/sbin/cron[2034]: (CRON) STARTUP (fork ok) Apr 25 22:07:12 server modprobe: modprobe: Can't locate module net-pf-18 Apr 25 22:07:14 server last message repeated 3 times unable to register? invalid argument? missing module? i'm guessing "net-pf-18" is significant... how do i get that? any info would be helpful -- i'm glad linux is so crash-proof. the only snag would be if we lost power; then i'd hafta go thru all this voodoo again to get back online! help!
Re: Modules & name resolution
Looks like you have most of your bases covered. So, what's in /etc/host.conf? It probably should be like: order hosts,bind multi on It seems that the nameservers aren't being queried. Since, they are apparently set correctly, this is the last thing I can think of. I think if it just says "order hosts" then the resolver library never looks in /etc/resolv.conf for nameservers (only /etc/hosts). Worth a look. (The man pages aren't very clear about the relationship between /etc/host.conf and /etc/resolv.conf). -- ¶ One·should·only·use·the·ASCII·characterset·when·compos » ing·email·messages.
Re: Modules & name resolution
Hello! Thanks to John Pearson and Eric G. Miller for their replies. [modules not loading] On Tue, 25 Apr 2000 09:32:21 +0930, John Pearson wrote: >Or, run modconf which will allow you to do the same thing in a >more GUI way. Tried it, but it loaded the modules at boot time, and not in an on-demand fashion. :-( >After editing files in /etc/modutils always run update-modules, >so that /etc/conf.modules gets updated. I'll try reading all the docs on modules. [routes, name resolution] On Mon, 24 Apr 2000 18:29:27 -0700, Eric G . Miller wrote: >> Another question: I used pppconfig to set up my dialup Internet >> connection. I supplied the IP address of the ISP's name server, which >> was properly placed in /etc/resolv.conf. nslookup works okay, but >> nothing else: ping and browsers cannot resolve names. Everything works >> when IP addresses are given instead of names. > >Did you tell pppconfig to use the nameservers in /etc/resolv.conf or to >use the dynamically assigned ones by your ISP (if it does this). I set it manually to the value supplied to me by the ISP beforehand. No dynamic stuff. After dialling up the ISP, I found the address properly placed in /etc/resolv.conf. >Also, >did you tell it to set the default route? Look under the "Advanced" >option of pppconfig for some of these items. If memory serves me well, I let everything have default values. I checked the default route, and it was in my routing table. Please see below for an example session of what actually happens: --- eagle:~# ping lemma.math.bme.hu ping: unknown host lemma.math.bme.hu eagle:~# ping 152.66.83.11 PING 152.66.83.11 (152.66.83.11): 56 data bytes 64 bytes from 152.66.83.11: icmp_seq=0 ttl=59 time=2625.3 ms 64 bytes from 152.66.83.11: icmp_seq=1 ttl=59 time=1680.0 ms 64 bytes from 152.66.83.11: icmp_seq=2 ttl=59 time=690.5 ms 64 bytes from 152.66.83.11: icmp_seq=3 ttl=59 time=110.0 ms --- 152.66.83.11 ping statistics --- 4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max = 110.0/1276.4/2625.3 ms eagle:~# less /etc/resolv.conf nameserver 195.8.32.8 eagle:~# netstat -r Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 195.8.32.6 * 255.255.255.255 UH0 0 0 ppp0 default 195.8.32.6 0.0.0.0 UG0 0 0 ppp0 eagle:~# nslookup Default Server: ns.alarmix.net Address: 195.8.32.8 > lemma.math.bme.hu Server: ns.alarmix.net Address: 195.8.32.8 Non-authoritative answer: Name:lemma.math.bme.hu Address: 152.66.83.11 --- As you can see, /etc/resolv.conf is okay, nslookup works with that server, but ping (and other apps) don't. The routing table is ok, the default entry has been inserted and it's right, because ping reaches lemma when using the IP address, and nslookup works too. Editing text files is okay for me. Being an OS/2 user, ifconfig and nslookup are like good friends of mine. :-) Any more ideas? Kofa Homepage at http://www.math.bme.hu/~kofa - For PGP public key: send mail with the subject PGP Public Key Request or finger [EMAIL PROTECTED]
