RE: [Discuss-gnuradio] help: cannot send after transport endpoint shutdown

[Joreen Tan]

I'm trying it on the benchmark_tx and benchmark_rx scripts as i need to make it at least a half duplex communication between the two devices, i need to free up the resources if not i will get error message that states that the resource is busy.
 
Another question that i observed is that, there seems to be no way to stop the receiver once it is activated unlike the transmitter. Any suggestions to that?

Regards,
Joreen




> Date: Tue, 27 Jan 2009 21:48:10 -0800
> From: address@hidden
> To: address@hidden
> CC: address@hidden
> Subject: Re: [Discuss-gnuradio] help: cannot send after transport endpoint shutdown
>
> On Wed, Jan 28, 2009 at 01:41:06PM +0800, Joreen Tan wrote:
> >
> > Hi,
> >
> > I have got this error message when i'm trying to use this two commands to free up the usb resource,
> >
> > modprobe -vr ehci_hcd
> > modprobe -v ehci_hcd
> >
> > the error message is:
> >
> > usb_control_msg failed: error sending control message: Cannot send after transport endpoint shutdown
>
> > Can anyone help me with this? i don't really quite understand this
> > error message.. It was initially working fine until i tried it for
> > the second time.. Regards,Joreen
>
>
> From the modprobe man page, note particularly the second paragraph:
>
> -r --remove
> This option causes modprobe to remove, rather than insert a mod-
> ule. If the modules it depends on are also unused, modprobe
> will try to remove them, too. Unlike insertion, more than one
> module can be specified on the command line (it does not make
> sense to specify module parameters when removing modules).
>
> There is usually no reason to remove modules, but some buggy
> modules require it. Your kernel may not support removal of mod-
> ules.
>
> Eric

---

See all the ways you can stay connected to friends and family