From: newsspam@weilbacher.org   
      
   On 13.11.2007 18:45, David W Noon wrote:   
      
   > On Tuesday 13 Nov 2007 14:17 in article   
   > <4739B201.2050009@gaston.Weilbacher.org> of alt.os.linux.gentoo, Peter   
   > Weilbacher(newsspam@weilbacher.org) wrote:   
   >   
   >> On 11.11.2007 15:45, David W Noon wrote:   
   >>   
   >>> It rebuilds /etc/modules.conf from the various Gentoo-specific lists   
   >>> of device drivers. It's the step everyone forgets when changing   
   >>> hardware configurations.   
   >>   
   >> Ah, OK. No hardware change involved here, though. And ipw2200 isn't   
   >> even listed in that file...   
   >   
   > Okay. That usually means that it is being insmod'ed as a dependency of   
   > another driver.   
      
   Actually, none of the four drivers I list below are in the generated   
   modules.conf.   
      
   > [snip]   
   >> ieee80211_crypt: registered algorithm 'NULL'   
   >> ieee80211: 802.11 data/management/control stack, git-1.1.13   
   >> ieee80211: Copyright (C) 2004-2005 Intel Corporation   
   >>  ipw2200: Intel(R) PRO/Wireless 2200/2915   
   >> Network Driver, 1.2.0k ipw2200: Copyright(c) 2003-2006 Intel   
   >> Corporation ACPI: PCI Interrupt 0000:01:02.0[A] -> GSI 17 (level, low)   
   >> -> IRQ 17 ipw2200: Detected Intel PRO/Wireless 2200BG Network   
   >   
   > It looks like the ieee80211 and/or ieee80211_crypt driver [probably the   
   > former] requires a physical transportation driver. You could try adding   
   > them to the blacklist as well.   
   >   
   > This looks similar to the situation I had with the new Firewire stack:   
   > the later drivers required firewire_core, so it was being loaded even   
   > though I had blacklisted it. I simply put all 3 in the blacklist, so:   
      
   Had already tried that. When I do modprobe -v ipw2200 I see   
      
   insmod /lib/modules/2.6.22-suspend2-r1/kernel/drivers/base/firmware_class.ko   
   insmod /lib/modules/2.6.22-suspend2-r1/kernel/net/ieee80211/ieee80211_crypt.ko   
   insmod /lib/modules/2.6.22-suspend2-r1/kernel/net/ieee80211/ieee80211.ko   
   insmod /lib/modules/2.6.22-suspend2-r1/kernel/drivers/net/wireless/ipw2200.ko   
      
   so I had added all four of them to the blacklist. But that didn't help. I   
   think it is actually not udev which is loading them. I see the output about   
   the ipw2200 driver much earlier in the boot process then I see anything   
   about udev...   
      
   Is there any way to actually capture the output I see on the screen during   
   boot? dmesg output and /var/log/messages only contain part of that stuff.   
      
      Peter.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)