From owner-freebsd-mobile@FreeBSD.ORG Sun Nov 15 20:35:34 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A4621065757; Sun, 15 Nov 2009 20:35:34 +0000 (UTC) (envelope-from jwh@rewt.org.uk) Received: from smtp.as6911.net (smtp.as6911.net [62.84.177.6]) by mx1.freebsd.org (Postfix) with ESMTP id 932E98FC16; Sun, 15 Nov 2009 20:35:32 +0000 (UTC) Received: from jasmine.barbary (nat2.kaya.stf.rewt.org.uk [62.84.188.41]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.as6911.net (Postfix) with ESMTPS id A9283FEC0; Sun, 15 Nov 2009 20:35:31 +0000 (GMT) Received: from jasmine.barbary (jasmine.barbary [172.16.11.9]) by jasmine.barbary (Postfix) with ESMTP id 30162130DBB; Sun, 15 Nov 2009 20:35:35 +0000 (GMT) Date: Sun, 15 Nov 2009 20:35:35 +0000 (GMT) From: Joe Holden X-X-Sender: jwh@jasmine.barbary To: Rui Paulo In-Reply-To: <3B334B9B-54CE-4DB1-A010-9477A75D7BE1@freebsd.org> Message-ID: References: <5F4CC8D8-3FAB-405C-A94D-4950D13F7E98@freebsd.org> <3B334B9B-54CE-4DB1-A010-9477A75D7BE1@freebsd.org> User-Agent: Alpine 2.00 (LNX 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-mobile@freebsd.org Subject: Re: Atheros 9280 Issues X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Nov 2009 20:35:34 -0000 Hiya, This patch doesn't seem to apply to the tree (with original ah_regdomain.c checked out using csup): Patching file ah_regdomain.c using Plan A... Hunk #1 failed at 170. Hunk #2 failed at 433. Hunk #3 failed at 1683. Should I be using any special options? Thanks, On Sun, 15 Nov 2009, Rui Paulo wrote: > On 15 Nov 2009, at 02:52, Joe Holden wrote: > >> Hi thanks for the response. >> >> I have recompiled kernel and attached the dmesg, the errors it gives seem >> to relate to having no/invalid regdomain in the eeprom: >> >> ath0: mem 0xdc000000-0xdc00ffff irq 17 at device 0.0 on pci6 >> ath0: [ITHREAD] >> ar9280Attach: sc 0xc2d8d000 st 0x1 sh 0xc2be9000 >> ar5416SetPowerMode: AWAKE -> AWAKE (set chip ) >> ar9280Attach: ID 0x852ff VERSION 0x2 TYPE 0x5 REVISION 0x2 >> ath_hal_v14EepromAttach Eeprom Magic = 0xa55a >> ath_hal_v14EepromAttach Eeprom Version 14.16 >> v14EepromReadCTLInfo Numctls = 21 >> ar5416SetPowerMode: AWAKE -> AWAKE (set chip ) >> ar9280RfAttach: attach AR9280 radio >> enableAniMIBCounters: Enable mib counters: OfdmPhyErrBase 0x0 cckPhyErrBase >> 0x0 >> ar9280Attach: return >> getchannels: cc 0 regDmn 0xf0 mode 0xffffff ecm >> isEepromValid: invalid regulatory domain/country code 0x6b >> getregstate: invalid EEPROM contents >> ath0: ath_getchannels: unable to collect channel list from hal, status 12 >> ar5416Detach: >> Detaching Ani >> Disable MIB counters >> ar5212SetPowerMode: AWAKE -> AWAKE (set chip ) >> ar5416SetPowerMode: AWAKE -> FULL-SLEEP (set chip ) >> device_attach: ath0 attach returned 22 > > > Try the attached patch please. > > -- > Rui Paulo