From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=5.0 tests=DMARC_MISSING, MAILING_LIST_MULTI,RDNS_DYNAMIC autolearn=unavailable autolearn_force=no version=4.0.0 Received: from coral.cfftechnologies.com (dsl081-147-127.chi1.dsl.speakeasy.net [64.81.147.127]) by chiba.3jane.net (Postfix) with ESMTP id 77E0620EDA1D for ; Tue, 2 Apr 2002 12:39:46 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by coral.cfftechnologies.com (Postfix on SuSE Linux 7.2 (i386)) with ESMTP id 460E212F96B for ; Tue, 2 Apr 2002 12:35:04 -0600 (CST) Received: from d225.sosmarketplace.com (garm-x.sosmarketplace.com [63.98.0.66]) by coral.cfftechnologies.com (Postfix on SuSE Linux 7.2 (i386)) with ESMTP id A41B912F96A for ; Tue, 2 Apr 2002 12:35:02 -0600 (CST) From: Avi Schwartz To: gentoo-dev@gentoo.org Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 Date: 02 Apr 2002 12:35:02 -0600 Message-Id: <1017772502.6035.60.camel@seahorse> Mime-Version: 1.0 X-Virus-Scanned: by AMaViS snapshot-20010714 Subject: [gentoo-dev] How do I keep multiple versions of modules? Sender: gentoo-dev-admin@gentoo.org Errors-To: gentoo-dev-admin@gentoo.org X-BeenThere: gentoo-dev@gentoo.org X-Mailman-Version: 2.0.6 Precedence: bulk Reply-To: gentoo-dev@gentoo.org List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux developer list List-Unsubscribe: , List-Archive: X-Archives-Salt: 570dd510-37f6-400d-9903-32505a24fdbf X-Archives-Hash: 586b845b2a7fd545aad0e50de35f4e56 Sounds strange, but not so. The problem happened when I built the 2.4.19 kernel. I had to rebuild the pcmcia and alsa modules as well. Guess what, I had some problems with 2.4.19 (actually the problem is vmware and not the kernel. vmware will not build the modules since it uses malloc.h which was depriciated in 2.4.19). So I decided to boot 2.4.18. Suddenly none of the alsa modules would load. What happens is that when I built the alsa modules for 2.4.19, the installation program removed the previous version and therefore the modules where gone from the /lib/modules/2.4.18 hierarchy. Kernel modules should be special and if you rebuild a module, it should remove the module only for the currently running kernel hierarchy and not from a different kernel version. Is this even possible with the poratge system? I wasn't sure where I should post this, so I crossposted to user and dev. Avi -- Avi Schwartz avi@CFFtechnologies.com