Beam Device is Busy???

[RichS]

Now that my wifi card is dead, I\'ve tried to connect with my IR modem to get my updates. This normally works just fine. I have everything set up and working. But, if it doesn\'t hook up right with the modem, the Z seems to keep the \"Beam Device\" as \"Busy\" and I can\'t try to reconnect. Last time this happened I finally did a reboot to get back the beam device.

There must be a way to free the \'beam device\' without doing a reboot? Anyone know how? Anyone know if there\'s a fix that might prevent this from happening?

Thanks!

[RichS]

So absolutely noone knows what a \"beam device\" is and how to turn it off???

[skoorb]

check under settings, beam receive and make sure it is set to manual mode

[tumnus]

and if it still says that after checking beam receive, run the following command as root in the terminal:

/etc/rc.d/init.d/irda stop

[RichS]

Ahh, thank you for the responses!

The beam recieve is always set at manual as I never use it, but I did check...

Then I tried the ir modem connect without anything out there to connect to. \'Course it failed... Then I tried to reconnect and got the \"Beam device is busy\". Fine...

Then I entered in the above command. result:

Shutting down IrDa: killall: irattach: no process killed

Then I try the connect again, and \"Beam device is busy\"...

In case it wasn\'t clear. This connection is through the network \'Globe\" for an IR modem connection set up through the Network settings.

I don\'t see any new processes running in  WhatUponZ...

And I do have Lirc installed but I\'m pretty sure I had this problem long before I instaleld that... ANd I can run lirc programs like mode2 and they still work when the Z is giving this error for the net connection.

Any other ideas? I hope...

[zautrix]

Maybe you have to remove the irda lock-file?

I do not remember the name ... it should be some file in /var/lock/

z.

P.S.

It is /var/lock/subsys/irda

[RichS]

Ahhh, you were close enough that I found a temp solution...

It creates a file \"irattach.pid\" in /var/run/ ( which apparently is really \"/dev/shm/run\"). If I delete that file, I can hit the connect button again and it tries to connect without the Device Busy message box... That beats the heck out of a reboot!

Thanks!