Bug 114149

Description of problem:
kudzu doesn't recognize a new USB ADSL modem which installs itself as 
ethx, unless its driver is noted in modules.conf.

Version-Release number of selected component (if applicable):
1.1.40

How reproducible:
always (?)

Steps to Reproduce:
1. Install a new modem and driver which creates an ethernet device
2. Run system-config-network
3. Try to create a new xDSL connection.
  
Actual results:
See only the previously known Ethernet devices.

Expected results:
See the new device as well.

Additional info:
I'm using the German eagle-usb driver for the Allied Telesyn AT-AR215 
(Analog Devices chipset) ADSL modem, available from
http://eagle-usb.eisfront.de/ .
When this driver is loaded by hotplug, and the modem is correctly 
initialized, a new device pops up under "ifconfig -a". I used to have 
only eth0 (onboard Ethernet device), now there's also eth1 with the 
correct MAC address.
Nevertheless, kudzu doesn't detect a new device, therefore 
system-config-network doesn't allow me to use it for a new connection 
either.
I found a "workaround" by coincidence ("find /etc -type f | xargs 
grep eth" ;->): If I add "alias eth1 eagle-usb" in modules.conf, 
kudzu recognizes the device. (I need to fix the driver to eth1 now, 
though.) Nevertheless, the driver works fine manually 
(pppd/rp-pppoe/route) without this entry.
Is this perhaps necessary for kudzu/whatever to "query" eth1 in the 
kernel? I realize that kudzu needs to know what is there, but I 
really missed an instruction for this, because the actual driver 
worked fine.
-> Documentation update?
-> Detection algorith update (also query /proc/bus/usb/)?

Thanks,
Moritz