DragonFly users List (threaded) for 2007-02
DragonFly BSD
DragonFly users List (threaded) for 2007-02
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: ath(4) major update


From: "Sepherosa Ziehau" <sepherosa@xxxxxxxxx>
Date: Mon, 5 Feb 2007 11:54:12 +0800

On 2/5/07, Ja'far Railton <ibn.richard@gmail.com> wrote:
On Mon, Feb 05, 2007 at 11:13:25AM +0800, Sepherosa Ziehau wrote:
> On 2/5/07, Ja'far Railton <ibn.richard@gmail.com> wrote:
> >I am pleased to report an improvement with this patch. I used the
> >example from the DF handbook - there isn't any access point available yet.
>
> Do you mean ath(4) does not associate?

No, I mean that there is no access point existing to associate to. I am
only trying to get the device working before I try it out at Starbucks
(or somewhere). :-)

> >~ > sudo ifconfig ath0 inet 192.168.0.20 netmask 255.255.255.0 ssid \
> >my_net
>
> This configure means your AP is not using any protection (e.g. WEP, WPA ...)
>
> What's the output of:
> ifconfig ath0 up scan

That gives no output. And the LED's on the device don't toggle or
anything.

> Please refer to following link for an up-to-date wireless
> configuration guidance:
> http://leaf.dragonflybsd.org/~sephe/sam_wireless.html

Will do, thanks. Is this (should it be) linked to on the wiki?

> Note, the WPA rc script part in the above document does not apply to
> dfly.  I will be more than happy if someone can make it work :)
>
> >ath0: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> mtu 1500
>
> IFF_RUNNING was not turned on.  Have you seen any of following
> messages in your /var/log/messages or on you console when you
> configured your ath(4):
> "unable to reset hardware; hal status X"
> "unable to start recv logic"

Yes.

~ > tail -f /var/log/messages
Feb  5 06:22:13 think sudo:      jr0 : TTY=ttyp1 ; PWD=/home/jr0 ;
USER=root ; C
OMMAND=/sbin/ifconfig ath0 up scan
Feb  5 06:22:13 think kernel: ath0: unable to reset hardware; hal status
3399012
864
Feb  5 06:25:38 think sudo:      jr0 : TTY=ttyp1 ; PWD=/home/jr0 ;
USER=root ; C
OMMAND=/sbin/ifconfig ath0 up scan
Feb  5 06:25:38 think kernel: ath0: unable to reset hardware; hal status
3399012
864
Feb  5 06:26:09 think sudo:      jr0 : TTY=ttyp1 ; PWD=/home/jr0 ;
USER=root ; C
OMMAND=/sbin/ifconfig ath0 down
Feb  5 06:26:12 think sudo:      jr0 : TTY=ttyp1 ; PWD=/home/jr0 ;
USER=root ; C
OMMAND=/sbin/ifconfig ath0 up scan
Feb  5 06:26:12 think kernel: ath0: unable to reset hardware; hal status
0
Feb  5 06:30:51 think sudo:      jr0 : TTY=ttyp1 ; PWD=/home/jr0 ;
USER=root ; C
OMMAND=/sbin/ifconfig ath0 inet 192.168.0.20 netmask 255.255.255.0 ssid
my_net
Feb  5 06:31:11 think sudo:      jr0 : TTY=ttyp1 ; PWD=/home/jr0 ;
USER=root ; C
OMMAND=/sbin/ifconfig ath0 up scan
Feb  5 06:31:11 think kernel: ath0: unable to reset hardware; hal status
3399014

I don't think HAL can return such a large error code, there must be something out of sync. Can you post the full dmesg?

Best Regards,
sephe

--
Live Free or Die



[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]