ORBIT-USER: Error setting bit-rate?

[Sachin]

When the nodes are powered on, the driver is not loaded...so it may
help if you explicitly "modprobe ath_pci" prior to configuring the
interfaces.

That way you can be sure the driver is loaded

On 1/19/07, Andrea G Forte <andreaf at cs.columbia.edu> wrote:
> Thanks, but what I mean is how can I check this in an automated way on
> 100 nodes? Do I have to check this before every experiment?
>
> -Andrea
>
>
> Sachin wrote:
> > lsmod should show "ath_pci"
> >
> > On 1/19/07, Andrea G Forte <andreaf at cs.columbia.edu> wrote:
> >> How do I check if the driver is loaded?
> >>
> >> -Andrea
> >>
> >>
> >> Sachin wrote:
> >> > Hi Andrea,
> >> >
> >> > Some basic checks:
> >> >
> >> > - How are you setting the frequencies and bitrates? which commands are
> >> > you using?
> >> > - Have made sure that the driver is loaded prior to access the device
> >> >
> >> >
> >> > On 1/19/07, Andrea G Forte <andreaf at cs.columbia.edu> wrote:
> >> >> Hi all,
> >> >>
> >> >> I am using the orbit handler and after I turn on the nodes and try to
> >> >> set channel and bit-rate, I get the following:
> >> >> Error for wireless request "Set Frequency" (8B04) :
> >> >>     SET failed on device ath0 ; Invalid argument.
> >> >> Error for wireless request "Set Frequency" (8B04) :
> >> >>     SET failed on device ath0 ; Invalid argument.
> >> >
> >> >> Error for wireless request "Set Bit Rate" (8B20) :
> >> >>     SET failed on device ath0 ; Invalid argument.
> >> >> Error for wireless request "Set Bit Rate" (8B20) :
> >> >>     SET failed on device ath0 ; Invalid argument.
> >> >>
> >> >> Any idea why this is happening?
> >> >> Thanks a lot,
> >> >> -Andrea
> >> >>
> >> >>
> >>
> >>
>
>