From owner-freebsd-wireless@FreeBSD.ORG Wed May 1 15:04:28 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 423BF258; Wed, 1 May 2013 15:04:28 +0000 (UTC) (envelope-from sendtomatt@gmail.com) Received: from mail-pd0-f175.google.com (mail-pd0-f175.google.com [209.85.192.175]) by mx1.freebsd.org (Postfix) with ESMTP id 185211333; Wed, 1 May 2013 15:04:27 +0000 (UTC) Received: by mail-pd0-f175.google.com with SMTP id g10so851892pdj.6 for ; Wed, 01 May 2013 08:04:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=1SECz6P13rBslE6UDmYbtxS8KPrOBixtReUs4A5rdr4=; b=tr0mD2JSUNfZSOceijYuk4kw6flEny/OtNR4J0FjPuYx2KgPSiXcdJgTs01g8kaPWA 2Z60oBKUdIE9HXj1XkXjM9UqMSilxgdjrZwNkliC+juWjzZtqlZlO6tqG0FINqPYiy9c O6UHxle7jze0eIn7Z8sOza8Jr3oy3MEHkj6iDbvWmbNjaT45QQGrMGv+malBQXuLunS3 nfsn1BHcQd9c56KrkXMFO9pYCHRLSDn/HsQbkhQk9bIYQX8VQdtmfDxPC4gPMAqcfM9h MzAlBOv+pIWQQkwinzJc4ZtjN/OSKxPocePyMdWnr+FrlMFNPOrfF+o9E0l2WP2SUJrz fdTw== X-Received: by 10.68.7.70 with SMTP id h6mr4537925pba.77.1367420667444; Wed, 01 May 2013 08:04:27 -0700 (PDT) Received: from flatline.local (70-36-223-239.dsl.dynamic.sonic.net. [70.36.223.239]) by mx.google.com with ESMTPSA id pa2sm4000998pac.9.2013.05.01.08.04.25 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 01 May 2013 08:04:26 -0700 (PDT) Message-ID: <51812EEA.80806@gmail.com> Date: Wed, 01 May 2013 08:04:10 -0700 From: matt User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130405 Thunderbird/17.0.5 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: Problem with new laptop's ral0 (Ralink 5390) References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-wireless@freebsd.org, Goran Tepshic X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 May 2013 15:04:28 -0000 On 04/30/13 08:31, Adrian Chadd wrote: > Hi, > > I've no idea, unfortunately. You'd have to start adding kernel printfs > in the driver to see when the driver locks up. I can't be much more > help than that at the moment, sorry :( > > > > Adrian > > > I'm not sure that chip is supported, at least it's news to me...the forum link seems to refer to inserting the pci ids for that chip into the ral driver. I can definitely see how forcing ral to attach to an unsupported device might hang or crash. I think this chip may be similiar to rt2860/rt3060/rt3090, as it looks like it uses the rt2800 driver in Linux. It also looks like they have only recently added support on the Linux side...and it's not that stable. I would look at the sources for any driver that does support this and see if they are having to do special conditionals to handle something specific with this chip, especially with register addresses or chip setup. It might be a good starting point for figuring out why ours doesn't work. My guess would be that invalid data is coming back from the eeprom (since addresses may have changed) and causing havoc. Is the MAC address correct? For what it's worth, the FreeBSD ral seems to be picky about devices...there are a lot of ral variants, but I think only those listed in the manpage are known to work. Adding more is going to be with a lot of printfs and testing, unfortunately. Matt