Why is udev trying to bring up my wireless card?

n0n · Guru Joined: 13 Jun 2002 Posts: 355

Hello. I've recently done a bunch of updates on my laptop, and now whenever I start, it loads up the ipw2200 module and tries to bring up eth1 (my wireless card), for some reason. It looks like it might be udev that's doing this.

I only have net.eth0 in my default runlevel (in fact, net.eth1 doesn't even exist). The ipw2200 module is *not* in my /etc/modules.autoload.d/kernel-2.6 file. My /etc/conf.d/net doesn't even mention eth1 (which should be a pretty good indication that I don't want it auto-configured), and it does include the following:

guduri · Posted: Mon Feb 26, 2007 12:13 am Post subject:

To the file /etc/conf.d/rc edit the line which says

n0n · Guru Joined: 13 Jun 2002 Posts: 355

Hm, okay, that makes sense. I notice a line in there for RC_COLDPLUG, as well. I just tried setting that to "no" and everything happens exactly as I'd like - no extra modules are loaded that I haven't explicitly loaded myself via modules.autoload.d or the like.

After some searching around, though, it sounds like when I set that to "no" then udev may not create /dev entries for some hardware. Is that the case, or is this option "safer" than that?

guduri · Posted: Mon Feb 26, 2007 1:18 am Post subject:

I was having this same problem on my laptop some time age. No matter what I had in my run level both net.eth0 and net.eth1 where being brought up. After some research I found out that there were changes made to baselayout to provide this magic to auto configure the network. At first it was very irritating since I know which network interface to bring up depending on where I was using the laptop. Then I stumbled across the RC_PLUG_SERVICES. Basically it tells the baselayout stuff to layoff net.eth1 if it sees "!net.eth1" on that line and not bring up and dependent stuff.

So, if you just want baselayout to not touch net.eth1 and let the run level stuff work as is, I would go for that addition. If I were you I wont touch the RC_COLDPLUG line and set it to "no" cause this can cause other side effects like you mentioned.
_________________
Power is about what you can control. Freedom is about what you can unleash.

n0n · Guru Joined: 13 Jun 2002 Posts: 355

Yeah, I understand. I realize this is getting away from "network & security" but ideally I'd really like something that just told hotplug/udev/whatever to not load any modules I haven't explicitly asked for. The RC_PLUG_SERVICES thing like you mentioned will certainly do the trick, but that doesn't address what I now realize is a bigger problem for me, which is that udev is also loading other stuff as well. I'd hate to have some hardware conflict and have my system crash on startup just because hotplug/coldplug/whatever decided that a module needed loading.

PaulBredbury · Watchman Joined: 14 Jul 2005 Posts: 7310

Then set:

n0n · Guru Joined: 13 Jun 2002 Posts: 355