Re: modprobe errors after apt-get upgrade
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 to >> /lib/modules/2.2.12.old and install the modules again... >> > There are no old modules in there. Only the new ones created and > installed by using make-kpkg and dpkg. These errors started a couple of > days ago after a dselect upgrade. > > I have not touched the kernel and the modules since I kernel 2.2.9 came > out a while back until I did the recompile today. > > I suppose I just have to wait and keep upgrading my potato box and hope > these errors disappear just as mysteriously as they appeared? That is what I am going to do :) -- Andrew
Re: modprobe errors after apt-get upgrade
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 the modules again... > There are no old modules in there. Only the new ones created and installed by using make-kpkg and dpkg. These errors started a couple of days ago after a dselect upgrade. I have not touched the kernel and the modules since I kernel 2.2.9 came out a while back until I did the recompile today. I suppose I just have to wait and keep upgrading my potato box and hope these errors disappear just as mysteriously as they appeared? -- Regards, Christian Dysthe E-mail: [EMAIL PROTECTED] Web: http://oddbird.dyndns.org/cdysthe/ ICQ 3945810 Powered by Debian GNU/Linux "Clones are people two"
Re: modprobe errors after apt-get upgrade
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 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 the modules again... Martin -- If the box says 'Windows 95 or better', it should run on Linux, right? - anonymous For public PGP-key: finger [EMAIL PROTECTED]
Re: modprobe errors after apt-get upgrade
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 "Clones are people two"
Re: modprobe errors after apt-get upgrade
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 /lib/modules/2.2.9/misc/comm.o > ... Then recompile the kernel ... that should work. Martin -- If the box says 'Windows 95 or better', it should run on Linux, right? - anonymous For public PGP-key: finger [EMAIL PROTECTED]
Re: modprobe errors after apt-get upgrade
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
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
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 symbols in /lib/modules/2.2.9/misc/dstr.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/epat.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/epia.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/fit2.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/fit3.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/friq.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/frpw.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/kbic.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/ktti.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/on20.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/on26.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/pcd.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/pd.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/pf.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/pg.o depmod: *** Unresolved symbols in /lib/modules/2.2.9/misc/pt.o This looks like what I am getting while booting also. This started yesterday after an upgrade of my potato box. -- Regards, Christian Dysthe E-mail: [EMAIL PROTECTED] Web: http://oddbird.dyndns.org/cdysthe/ ICQ 3945810 Powered by Debian GNU/Linux "Clones are people two"
Re: modprobe errors after apt-get upgrade
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 > /lib/modules/2.2.12/modules.dep > > Any ideas on how to fix this? > > > -- > Andrew > > > > - > GnuPG Public KeyID: 0x48109681 > *we all live downstream* > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > I am gettting som /usr/lib/modules.something..errors when I boot after yesterdays upgrade. I am not able to read it, cause it races by so fast, and I can not see them it when I do a "dmesg".It looks like it says something about "/lib/modules/2.2.9/modules.dep" and /etc/modules.conf. I have some messages like this in my daemon.log also now that are new. There's at least 10 of these module related messages during boot that I have never seen before. No idea what this is either. -- Regards, Christian Dysthe E-mail: [EMAIL PROTECTED] Web: http://oddbird.dyndns.org/cdysthe/ ICQ 3945810 Powered by Debian GNU/Linux "Clones are people two"
Re: modprobe errors after apt-get upgrade
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 > /lib/modules/2.2.12/modules.dep > > Any ideas on how to fix this? depmod -a Martin -- If the box says 'Windows 95 or better', it should run on Linux, right? - anonymous For public PGP-key: finger [EMAIL PROTECTED]
Re: modprobe errors after apt-get upgrade
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: /etc/modules.conf is more recent than > /lib/modules/2.2.12/modules.dep > > Any ideas on how to fix this? > > -- > Andrew > > - > GnuPG Public KeyID: 0x48109681 > *we all live downstream* > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null -- David Natkins Email to: [EMAIL PROTECTED] Fax to: (718) 488-1780 Phone: (718) 403-2474
modprobe errors after apt-get upgrade
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 /lib/modules/2.2.12/modules.dep Any ideas on how to fix this? -- Andrew - GnuPG Public KeyID: 0x48109681 *we all live downstream*
