From: Ali Bahar <ali@internetdog.org>
To: Fred Plissonneau <cohomewp4@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Makefile deletes previous driver install when two WiFi interfaces are from the same chip vendor
Date: Wed, 22 Jun 2011 00:23:26 +0800 [thread overview]
Message-ID: <20110621162326.GA9922@internetdog.org> (raw)
In-Reply-To: <BANLkTi=EygUbm5VB+H-mm+ofpbuaK8xafA@mail.gmail.com>
Hi Fred,
On Tue, Jun 21, 2011 at 05:02:57PM +0200, Fred Plissonneau wrote:
> On Tue, Jun 21, 2011 at 3:07 PM, Ali Bahar <ali@internetdog.org> wrote:
> > On Tue, Jun 21, 2011 at 11:59:17AM +0200, Fred Plissonneau wrote:
> >> From: Fred Plissonneau <cohomewp4@gmail.com>
> >> > But when I switch-off and back on my PC, only the latest installed
> In fact only the last installed driver remains in the system
> directories (/lib/modules/...)
> The last-but-one installed driver has been removed during the "make
> install" of the second one.
I think I understand: you built a new driver, ran a 'make install' to
install it, and you suspect that the makefile removed another device's
driver. However, since the latter driver is already loaded into RAM,
you don't notice its loss until the next time you reboot.
> ./scripts/driver-select carl9170
> make
> sudo make install
> sudo modprode carl9170
> If I delete lines #318 to #326 in the Makefile (right after the "make"
> command and before "make install") it works fine now.
I don't know the makefile, nor anything specific to Ubuntu. But if the
procedure selects a specific driver, then its installation step should
not delete other drivers!
All's well that ends well! ;-)
ali
prev parent reply other threads:[~2011-06-21 16:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 9:59 Makefile deletes previous driver install when two WiFi interfaces are from the same chip vendor Fred Plissonneau
2011-06-21 13:07 ` Ali Bahar
2011-06-21 15:02 ` Fred Plissonneau
2011-06-21 16:21 ` Larry Finger
2011-06-21 16:23 ` Ali Bahar [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110621162326.GA9922@internetdog.org \
--to=ali@internetdog.org \
--cc=cohomewp4@gmail.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).