The following reply was made to PR kern/155498; it has been noted by GNATS.

From: Julian Stecklina <[email protected]>
To: [email protected], [email protected]
Cc:  
Subject: Re: kern/155498: [ral] ral(4) needs to be resynced with OpenBSD&#39;s
 to gain RT2860/2870 support.
Date: Tue, 23 Oct 2012 23:02:18 +0200

 Hello,
 
 I've seen that RT2860 support has been MFC'd to 9-STABLE (great!) and
 gave it a shot. My ral device is:
 
 ral0@pci0:2:0:0:       class=0x028000 card=0x130f1043 chip=0x07811814
 rev=0x00 hdr=0x00
     vendor     = 'Ralink corp.'
     device     = 'RT2860'
     class      = network
 
 uname:
 FreeBSD block.xn--pl-wia.net 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #1
 r241898+9dad7f0: Tue Oct 23 21:58:07 CEST 2012
 
 The driver attaches and I get a ral0 interface, but it seems not to
 function. Kernel logs say:
 
 ral0: <Ralink Technology RT2790> mem 0xfe8f0000-0xfe8fffff irq 16 at
 device 0.0 on pci2
 ral0: discard raw packet
 ral0: discard raw packet
 ral0: discard raw packet
 ral0: discard raw packet
 
 julian@block:~/ > sudo ifconfig ral0 up
 julian@block:~/ > sudo ifconfig ral0 scan
 ifconfig: unable to get scan results
 
 julian@block:/tmp/ > sudo wpa_supplicant -c wpa.conf -d -i ral0
 Initializing interface 'ral0' conf 'wpa.conf' driver 'default'
 ctrl_interface 'N/A' bridge 'N/A'
 Configuration file 'wpa.conf' -> '/tmp/wpa.conf'
 Reading configuration file '/tmp/wpa.conf'
 Priority group 0
    id=0 ssid='AndroidAP'
 ioctl[SIOCG80211, op 98, len 32]: Invalid argument
 wpa_driver_bsd_init: failed to get device capabilities: Invalid argument
 Failed to initialize driver interface
 Failed to add interface ral0
 Cancelling scan request
 Cancelling authentication timeout
 ELOOP: remaining socket: sock=4 eloop_data=0x80140f300
 user_data=0x801460080 handler=0x427fb0
 
 If I can test something else, please tell me.
 
 Julian
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "[email protected]"

Reply via email to