From: Martin D. <li...@md...> - 2005-04-30 09:13:38
|
On Fri, 29 Apr 2005, Axel Dine wrote: > Some more data: > the problem is not related to a race condition on max_baud_rate file as I > previously said. Ok, as said, I really don't see how it might depend on the max_baud_rate value in your case. > Doing some more test evidenced that I have to launch irattach twice to get > it work!!! > I mean I load modules, irattach irda0 -s, irdaump -> nothing. > then killall -w irattach, then again irattach irda0 -s, irdadump -> > works!!!! Ok, either race between irattach and the module-init or nasty interaction with hotplug stuff or similar. Maybe the module-init isn't finished yet when irattach ifup's the irda0 interface. The second time the module is already there thus no need to go thru the init path. I'm just guessing of course. Please try something like --- #!/bin/bash modprobe ali-ircc sleep 1 ifconfig irda0 up echo 1 > /proc/sys/net/irda/discovery --- instead of irattach. If it works, try without the sleep. If not, try to increase the delay. And please make sure you have CONFIG_IRDA_DEBUG enabled so you can check the syslog for suspicous messages. Martin |