Doug Jolley wrote: > Tom -- > > At the risk of beating a dead horse, I have just one thought that I > would like to toss out. Based on the symptoms that we're seeing, it > seems to me that the source of the problem has to be that there is > something wrong with the alias assignment in /etc/modprobe.conf. By > way of review, here is what it is: > > alias wlan0 prism2_usb > > Can you think of any possible reason why that assignment would be > either defective or ineffective? I think that that has to be the crux > of the problem; but, I have no idea why it's causing me grief. > > Thanks. > > ... doug
Nah, that's not the problem - it's exactly the same as mine. However, there is one more thing you can try. Do the modprobe without prism2_doreset=1. I used to use it too, but at some stage when I was having problems with the thing, I read that it was no longer necessary. Actually, you should be able to lose the modprobe command entirely, as long as you're using the Arch udev setup and MOD_AUTOLOAD="yes" in /etc/rc.conf. The module autoloads for me. _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
