Re: Modprobe errors after second kernel compile.

2003-06-04 Thread Kevin McKinley
On Tue, 3 Jun 2003 09:57:39 +0100 Patrick Beard [EMAIL PROTECTED] wrote: Hi, I upgraded to kernel 2.4.19 to allow me to add the i810 framebuffer patch. everything went fine except I had missed the generic-scsi support and so my cdrw didn't work. I turned this option on and recompiled. This

Re: modprobe errors I cannot fix

2000-10-05 Thread Eric G . Miller
On Fri, Oct 06, 2000 at 02:04:17AM +, Pollywog wrote: I just upgraded to 2.4.0 test9 kernel and got this error: lilypad modprobe: modprobe: Can't locate module char-major-14 I then made sure that /etc/modutils/aliases contained this: alias char-major-14 off I ran

Re: modprobe errors I cannot fix

2000-10-05 Thread Pollywog
On 06-Oct-2000 Eric G . Miller wrote: I ran update-modules, but still I get the modprobe error. Have I done something incorrect? I dunno, but I have: alias char-major-14 soundcore You got a sound card? If you don't have sound support, maybe just comment it out. I have a sound card,

RE: modprobe errors I cannot fix

2000-10-05 Thread Pollywog
On 06-Oct-2000 Pollywog wrote: I just upgraded to 2.4.0 test9 kernel and got this error: lilypad modprobe: modprobe: Can't locate module char-major-14 I then made sure that /etc/modutils/aliases contained this: alias char-major-14 off I ran update-modules, but still I get the

Re: modprobe errors again

1999-10-21 Thread Jean Pierre LeJacq
On Thu, 21 Oct 1999, Pollywog wrote: There has to be a bug in some package, because I upgraded my potato system and again I get the modprobe errors below: Oct 21 19:21:08 lilypad modprobe: Note: /etc/modules.conf is more recent than /lib/modules/2.2.12/modules.dep This is a know bug in the

Re: modprobe errors again

1999-10-21 Thread Pollywog
On 21-Oct-99 Jean Pierre LeJacq wrote: On Thu, 21 Oct 1999, Pollywog wrote: There has to be a bug in some package, because I upgraded my potato system and again I get the modprobe errors below: Oct 21 19:21:08 lilypad modprobe: Note: /etc/modules.conf is more recent than

Re: modprobe errors return

1999-10-19 Thread Pollywog
On 18-Oct-99 Martin Fluch wrote: By the way, at every boottime a depmod is executet (perhaps you have seen the 'Updating modules...' message at boottime. If you get ever again such an message (and want to get rid of it) just run a depmod -a I had done that, to no avail. I have not

Re: modprobe errors return

1999-10-19 Thread Christian Dysthe
On 18 Oct, Pollywog wrote: Those odd modprobe errors have returned after I did an apt upgrade today. Oct 18 21:43:46 lilypad modprobe: Note: /etc/modules.conf is more recent than /lib/modules/2.2.12/modules.dep Oct 18 21:43:53 lilypad insmod: Note: /etc/modules.conf is more recent than

Re: modprobe errors return

1999-10-19 Thread Pollywog
On 19-Oct-99 Christian Dysthe wrote: - GnuPG Public KeyID: 0x48109681 *we all live downstream* -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null I still get this when I do depmod -a. I have recompiled my kernel depmod: *** Unresolved

RE: modprobe errors return

1999-10-18 Thread Pollywog
On 18-Oct-99 Pollywog wrote: Those odd modprobe errors have returned after I did an apt upgrade today. Oct 18 21:43:46 lilypad modprobe: Note: /etc/modules.conf is more recent than /lib/modules/2.2.12/modules.dep Oct 18 21:43:53 lilypad insmod: Note: /etc/modules.conf is more recent than

Re: modprobe errors return

1999-10-18 Thread Martin Fluch
On Mon, 18 Oct 1999, Pollywog wrote: Those odd modprobe errors have returned after I did an apt upgrade today. Oct 18 21:43:46 lilypad modprobe: Note: /etc/modules.conf is more recent than /lib/modules/2.2.12/modules.dep Oct 18 21:43:53 lilypad insmod: Note: /etc/modules.conf is more recent

Re: modprobe errors after apt-get upgrade

1999-10-16 Thread Christian Dysthe
On 16 Oct, Martin Fluch wrote: Then recompile the kernel ... that should work. Nope, did that. Same errors. -- Regards, Christian Dysthe E-mail: [EMAIL PROTECTED] Web: http://oddbird.dyndns.org/cdysthe/ ICQ 3945810 Powered by Debian GNU/Linux

Re: modprobe errors after apt-get upgrade

1999-10-16 Thread Martin Fluch
On Fri, 15 Oct 1999, Christian Dysthe wrote: On 16 Oct, Martin Fluch wrote: Then recompile the kernel ... that should work. Nope, did that. Same errors. Then there seems to be some modules in the directory, wich are not needed, e.g. they are left from the previous kernel... (have a

Re: modprobe errors after apt-get upgrade

1999-10-16 Thread Christian Dysthe
On 16 Oct, Martin Fluch wrote: Then there seems to be some modules in the directory, wich are not needed, e.g. they are left from the previous kernel... (have a look at their date) ... I guess you can savely remove them ... or move /lib/modules/2.2.12 to /lib/modules/2.2.12.old and install

Re: modprobe errors after apt-get upgrade

1999-10-16 Thread Pollywog
On 16-Oct-99 Christian Dysthe wrote: On 16 Oct, Martin Fluch wrote: Then there seems to be some modules in the directory, wich are not needed, e.g. they are left from the previous kernel... (have a look at their date) ... I guess you can savely remove them ... or move /lib/modules/2.2.12

Re: modprobe errors after apt-get upgrade

1999-10-15 Thread David Natkins
You upgrade to a new version of modutils. Do an update-modules. Pollywog wrote: I did an upgrade of my potato system yesterday, and now I am getting this error even though I went back to the /etc/modules.conf I was using before the upgrade. Oct 15 16:56:47 lilypad modprobe: Note:

Re: modprobe errors after apt-get upgrade

1999-10-15 Thread Martin Fluch
On Fri, 15 Oct 1999, Pollywog wrote: I did an upgrade of my potato system yesterday, and now I am getting this error even though I went back to the /etc/modules.conf I was using before the upgrade. Oct 15 16:56:47 lilypad modprobe: Note: /etc/modules.conf is more recent than

Re: modprobe errors after apt-get upgrade

1999-10-15 Thread Christian Dysthe
On 15 Oct, Pollywog wrote: I did an upgrade of my potato system yesterday, and now I am getting this error even though I went back to the /etc/modules.conf I was using before the upgrade. Oct 15 16:56:47 lilypad modprobe: Note: /etc/modules.conf is more recent than

Re: modprobe errors after apt-get upgrade

1999-10-15 Thread Christian Dysthe
On 15 Oct, Martin Fluch wrote: depmod -a Did depmod -a This is what I got: depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/aten.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/bpck.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/comm.o depmod: *** Unresolved

Re: modprobe errors after apt-get upgrade

1999-10-15 Thread Pollywog
On 15-Oct-99 Christian Dysthe wrote: On 15 Oct, Martin Fluch wrote: depmod -a Did depmod -a This is what I got: I got: depmod: *** Unresolved symbols in /lib/modules/2.2.12/misc/snd.o -- Andrew

Re: modprobe errors after apt-get upgrade

1999-10-15 Thread Pollywog
On 15-Oct-99 David Natkins wrote: You upgrade to a new version of modutils. Do an update-modules. That was the first thing I did. It did not stop the messages. thanks -- Andrew

Re: modprobe errors after apt-get upgrade

1999-10-15 Thread Martin Fluch
On Fri, 15 Oct 1999, Christian Dysthe wrote: On 15 Oct, Martin Fluch wrote: depmod -a Did depmod -a This is what I got: depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/aten.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/bpck.o depmod: *** Unresolved symbols in

Re: modprobe errors

1999-03-09 Thread Pedro Guerreiro
On Mon, Mar 08, 1999 at 07:39:12PM -, Pollywog wrote: Here are some errors I am getting. Below I include my /etc/modules. I compiled the modules into the kernel, so do I need /etc/modules at all? You have compiled the modules for _use_ with the kernel. If you wanted them to be build

Re: modprobe errors

1999-03-09 Thread Pollywog
On 09-Mar-99 Pedro Guerreiro wrote: OTOH, why don't you try 2.2.x? It's great with the modules, installing and removing them from memory and you don't even notice. I am staying away from the newer kernels because I don't know anything about them, and I don't know how to use ipchains. I