From nobody Sat May 27 12:03:22 2023 X-Original-To: wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QT0mp5Mnwz4Cdtg for ; Sat, 27 May 2023 12:03:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QT0mp2WD2z43nc for ; Sat, 27 May 2023 12:03:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1685189002; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=57GG0troafsRTQvACJjD/smENWJ4CA1BfotFaG/2LC8=; b=YGv4Wz4QoM+5kcf0F4/0S5CDDaeUbkCkGNfIzYMAFfTGTGeP3dCWKgKBU8fXBfJARFbT0F i6tm3s0AdEzgz7xPoekEi1nAqh+eyLhaD67XMMQ8oc+AW/Nr/YNr1lvsiFHrysAVL0GsSX wdS4B7HbZcODIaIjnmn1dLDUCVfjQzJnffDg+hN/RraxVu4/TrjEoNuRgjmK3Xa/mCjMPQ /Vfcwa5uT1A/cEVVgYaXBFgrazyPq12AtMeTBzN6NPWSAvhP+KRDOZRvYGTeObIBY0hq6y iGH3UhOPsE6YKCYeBBxyiXAGQf3R/u6TZLdPDK2dkJqNA/FDk/n7ed2lwD2+Eg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1685189002; a=rsa-sha256; cv=none; b=KgdEeV8gIktd0z/LpR9oweI/gZ5s4wXDr27qoudsxmf22OP15TxboyFC/24NjodkhImeqL rbuDPn/a/ILedby4/JYBZNllqVBptaGANrBz8fdEtjS0fpyo7eGnCTysMFiBR69bGOgZ+g OtPM+1wxoNZzcJ5/l+kXqHgK3SjoczT2O7u5seYztEbtX5s8QrNvZEPZlPDajY7YJ3LH7m V+S35z5ZnMZPtRw8FSQwSZikJe3YOyjWJyzhv3ftR3n/PF1zpUEXmMWW56CzFBgOxIkSxO 7CtObdIL+tZXta+/nviwS/X9jFRjXfLEX0kGV17k4qKfRbcXBrgalUhNgZpJxg== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4QT0mp1bvvznTh for ; Sat, 27 May 2023 12:03:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 34RC3M08053962 for ; Sat, 27 May 2023 12:03:22 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 34RC3MMd053959 for wireless@FreeBSD.org; Sat, 27 May 2023 12:03:22 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 211866] iwm 7260 driver crash message on Thinkpad T440s Date: Sat, 27 May 2023 12:03:22 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: crash, needs-qa X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: grahamperrin@freebsd.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status bug_severity keywords Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org MIME-Version: 1.0 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211866 Graham Perrin changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Open Severity|Affects Only Me |Affects Some People Keywords| |crash, needs-qa --- Comment #6 from Graham Perrin --- >From comment 0: > device =3D 'Wireless 7260' >From comment 4:=20 > =E2=80=A6 7265 =E2=80=A6 Might the same type of crash occur with iwm(4) in FreeBSD 13.2-RELEASE with Intel(R) Dual Band Wireless AC 8265? --=20 You are receiving this mail because: You are the assignee for the bug.= From nobody Sun May 28 21:01:00 2023 X-Original-To: wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QTrfj0fDJz4XtN7 for ; Sun, 28 May 2023 21:01:01 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QTrfh5pngz471R for ; Sun, 28 May 2023 21:01:00 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1685307660; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=juL8ZW9KFBYYtVB2U3io6arcIDwNYKFMq7qdd5+d8ak=; b=MJk7X9bQtS+Zkz7I0SzExIgUp3iwFmql3oCb3M2WAQ5nMtu4yu04hmzlnQRU4r+8F0YyZ1 cW4NCzz2wS8fUq3INWAeOD8lqR+W6uV5TT6f/9JdhOoTz88m3APkelwrgijDBnZSqTkACy teNXEQl6ximjIoJ92qUov6VO0CW0C3NMEsJuxW7OPSYSj5Rqhne+ORKt/3gVEknjXn12VA hAcaJlhGTgq9y75zOWS3zKUxMAOcOx0lo4NuTFM8nF6Wntowmg3PZzVwjg+I4FZQ5juMox 7Bj5Alu5mAy8TOnBxiFu2aBylg5D2nFkYQSKp60CuYmCvlzr7RDL7O4xO6PqUQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1685307660; a=rsa-sha256; cv=none; b=N8nlu+iDJ7v6PUneoTZ5IBqZejYI+Gp2ruTqAyaeKJacLpG9NdZgigpISLtXCITw9cNtx6 c58yz4iEONlJ5NA5F4JbLDb+RNEBVWbL70aRI5gQBGDuYubOPKHGWHdbBUut3bhmyEWZTV ZbPmEXwqfGjqIhnUrk8xgse0X+Dn8pbzY+2c/M3v+fpqkELy84dSNNVHGxcIu7XZ54AkWs oljO2JobuqkhyafbFGVu1XegBFdg7ARsNLh8tXiCUyVWq/kkgypjvWgkBpgP3DyN8HbG0E 4HxCMvwBAhmMWgJePHLhE7jvp3BmqJwkgLUP9rWy3ck4IyEZvuvFu9S2mBUg3w== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4QTrfh4tBtzl3B for ; Sun, 28 May 2023 21:01:00 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 34SL10a6019338 for ; Sun, 28 May 2023 21:01:00 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 34SL10gR019337 for wireless@FreeBSD.org; Sun, 28 May 2023 21:01:00 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <202305282101.34SL10gR019337@kenobi.freebsd.org> X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@FreeBSD.org using -f From: bugzilla-noreply@FreeBSD.org To: wireless@FreeBSD.org Subject: Problem reports for wireless@FreeBSD.org that need special attention Date: Sun, 28 May 2023 21:01:00 +0000 List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="16853076605.Fbed4f89e.13752" Content-Transfer-Encoding: 7bit X-ThisMailContainsUnwantedMimeParts: N --16853076605.Fbed4f89e.13752 Date: Sun, 28 May 2023 21:01:00 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- Open | 236918 | Crash: in iwn_ampdu_tx_stop (or ieee80211_ht_node Open | 238636 | ath: Fix kernel addresses printed in if_ath_sysct 2 problems total for which you should take action. --16853076605.Fbed4f89e.13752 Date: Sun, 28 May 2023 21:01:00 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" 
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status      |    Bug Id | Description
------------+-----------+---------------------------------------------------
Open        |    236918 | Crash: in iwn_ampdu_tx_stop (or ieee80211_ht_node
Open        |    238636 | ath: Fix kernel addresses printed in if_ath_sysct

2 problems total for which you should take action.
--16853076605.Fbed4f89e.13752-- From nobody Sun May 28 21:08:28 2023 X-Original-To: wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QTrqX2cL3z4Xtmy for ; Sun, 28 May 2023 21:08:40 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (cross.sbone.de [195.201.62.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE Root Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QTrqW2tLLz49cq for ; Sun, 28 May 2023 21:08:39 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of bzeeb-lists@lists.zabbadoz.net designates 195.201.62.131 as permitted sender) smtp.mailfrom=bzeeb-lists@lists.zabbadoz.net; dmarc=none Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 3B5518D4A15D; Sun, 28 May 2023 21:08:32 +0000 (UTC) Received: from content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id DBE4F5C3A831; Sun, 28 May 2023 21:08:31 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) by content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (amavisd-new, port 10024) with ESMTP id tUxDYH0ahvj8; Sun, 28 May 2023 21:08:30 +0000 (UTC) Received: from strong-iwl0.sbone.de (strong-iwl0.sbone.de [IPv6:fde9:577b:c1a9:4902:b66b:fcff:fef3:e3d2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 4DEFE5C3A82F; Sun, 28 May 2023 21:08:30 +0000 (UTC) Date: Sun, 28 May 2023 21:08:28 +0000 (UTC) From: "Bjoern A. Zeeb" To: "Julian H. Stacey" cc: FreeBSD wireless mailing list Subject: Re: regression failure of wpa_supplicant from 12.3-RELEASE to 12.4-RELEASE In-Reply-To: <202305250908.34P98uXs062551@dell.no.berklix.net> Message-ID: <8rrrnq54-53rn-or4p-750s-0516605557rn@yvfgf.mnoonqbm.arg> References: <202305250908.34P98uXs062551@dell.no.berklix.net> X-OpenPGP-Key-Id: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Spamd-Result: default: False [-3.18 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-0.98)[-0.977]; NEURAL_HAM_SHORT(-0.90)[-0.903]; R_SPF_ALLOW(-0.20)[+ip4:195.201.62.131]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[wireless@freebsd.org]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; MIME_TRACE(0.00)[0:+]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; ASN(0.00)[asn:24940, ipnet:195.201.0.0/16, country:DE]; ARC_NA(0.00)[]; TO_DN_ALL(0.00)[]; RCVD_COUNT_FIVE(0.00)[5]; DMARC_NA(0.00)[zabbadoz.net]; FROM_HAS_DN(0.00)[]; RCVD_TLS_LAST(0.00)[] X-Rspamd-Queue-Id: 4QTrqW2tLLz49cq X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N On Thu, 25 May 2023, Julian H. Stacey wrote: > "Julian H. Stacey" wrote: >> Hi wireless@freebsd.org, >> I suffered regression failure of wpa_supplicant from 12.3-RELEASE to >> 12.4-RELEASE, ifconfig wlan0 | grep status >> was not showing status: associated I don't know the state in 12.x but can you see if bfb202c4554a72383202a1a401d80721935b8c95 and/or 052211e08c0e227277d0c4dc603bba2253eb3d73 apply and/or help? -- Bjoern A. Zeeb r15:7 From nobody Mon May 29 00:18:57 2023 X-Original-To: wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QTx3N4shDz4Y58X for ; Mon, 29 May 2023 00:19:12 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "land.berklix.org", Issuer "land.berklix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QTx3M0HwKz4Qh1 for ; Mon, 29 May 2023 00:19:10 +0000 (UTC) (envelope-from jhs@berklix.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of jhs@berklix.com has no SPF policy when checking 144.76.10.75) smtp.mailfrom=jhs@berklix.com; dmarc=none Received: from dell.no.berklix.net (p4fe6de81.dip0.t-ipconnect.de [79.230.222.129]) (authenticated bits=128) by land.berklix.org (8.16.1/8.16.1) with ESMTPSA id 34T0J2IX075826 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=FAIL); Mon, 29 May 2023 00:19:02 GMT (envelope-from jhs@berklix.com) Received: from dell.no.berklix.net (localhost [127.0.0.1]) by dell.no.berklix.net (8.16.1/8.16.1) with ESMTPS id 34T0IvEc089060 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 29 May 2023 02:18:57 +0200 (CEST) (envelope-from jhs@dell.no.berklix.net) Received: (from jhs@localhost) by dell.no.berklix.net (8.16.1/8.16.1/Submit) id 34T0IvHx089059; Mon, 29 May 2023 00:18:57 GMT (envelope-from jhs) Message-Id: <202305290018.34T0IvHx089059@dell.no.berklix.net> To: "Bjoern A. Zeeb" cc: FreeBSD wireless mailing list Subject: Re: regression failure of wpa_supplicant from 12.3-RELEASE to 12.4-RELEASE From: "Julian H. Stacey" Organization: http://berklix.com/jhs/ User-agent: EXMH on FreeBSD http://berklix.com/free/ X-From: http://www.berklix.org/~jhs/ In-reply-to: Your message "Sun, 28 May 2023 21:08:28 +0000." <8rrrnq54-53rn-or4p-750s-0516605557rn@yvfgf.mnoonqbm.arg> List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <89057.1685319537.1@dell.no.berklix.net> Content-Transfer-Encoding: quoted-printable Date: Mon, 29 May 2023 00:18:57 +0000 X-Spamd-Result: default: False [-0.71 / 15.00]; AUTH_NA(1.00)[]; URI_HIDDEN_PATH(1.00)[http://www.berklix.com/~jhs/bin/.sh/git-pull.sh]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-0.98)[-0.977]; NEURAL_HAM_SHORT(-0.64)[-0.638]; MIME_GOOD(-0.10)[text/plain]; RCPT_COUNT_TWO(0.00)[2]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[wireless@freebsd.org]; R_SPF_NA(0.00)[no SPF record]; R_DKIM_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; ASN(0.00)[asn:24940, ipnet:144.76.0.0/16, country:DE]; FREEFALL_USER(0.00)[jhs]; ARC_NA(0.00)[]; TO_DN_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; HAS_ORG_HEADER(0.00)[]; DMARC_NA(0.00)[berklix.com]; RCVD_COUNT_THREE(0.00)[4]; RCVD_TLS_LAST(0.00)[] X-Rspamd-Queue-Id: 4QTx3M0HwKz4Qh1 X-Spamd-Bar: / X-ThisMailContainsUnwantedMimeParts: N "Bjoern A. Zeeb" wrote: > On Thu, 25 May 2023, Julian H. Stacey wrote: > > > "Julian H. Stacey" wrote: > >> Hi wireless@freebsd.org, > >> I suffered regression failure of wpa_supplicant from 12.3-RELEASE to > >> 12.4-RELEASE, ifconfig wlan0 | grep status > >> was not showing status: associated > > I don't know the state in 12.x but can you see if > > bfb202c4554a72383202a1a401d80721935b8c95 and/or > 052211e08c0e227277d0c4dc603bba2253eb3d73 > > apply and/or help? Thanks, I'll read how to extract src/ with those. I'll read https://docs.freebsd.org/en/books/handbook/mirrors/#git man git-checkout or syntax example welcome ( I have a src-cur from http://www.berklix.com/~jhs/bin/.sh/git-pull.sh which calls git pull --ff-only ) Meantime per my > I'll compare typescripts from 12.3 & 12.4 wpa_supplicant -d Ive uploaded transcript of diff -c of good 12.3 & bad 12.4 to http://www.berklix.com/~jhs/src/bsd/fixes/freebsd/src/gen/usr.sbin/wpa/wla= n.diff Cheers, -- = Julian Stacey www.StolenVotes.UK/jhs/ Arm Ukraine, Zap Putin. Brexit infl= ates http://berklix.org/ferries/#dover_solution From nobody Tue May 30 17:30:20 2023 X-Original-To: wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QVzvJ4RRcz4XsBf for ; Tue, 30 May 2023 17:30:52 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from webmail5.jnielsen.net (webmail5.jnielsen.net [IPv6:2607:f170:34:11::b0]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.freebsdsolutions.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QVzvH3cHWz3lB2 for ; Tue, 30 May 2023 17:30:51 +0000 (UTC) (envelope-from lists@jnielsen.net) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of lists@jnielsen.net designates 2607:f170:34:11::b0 as permitted sender) smtp.mailfrom=lists@jnielsen.net; dmarc=none Received: from smtpclient.apple (166-70-14-17.xmission.com [166.70.14.17] (may be forged)) (authenticated bits=0) by webmail5.jnielsen.net (8.17.1/8.17.1) with ESMTPSA id 34UHUVbU003079 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Tue, 30 May 2023 11:30:33 -0600 (MDT) (envelope-from lists@jnielsen.net) X-Authentication-Warning: webmail5.jnielsen.net: Host 166-70-14-17.xmission.com [166.70.14.17] (may be forged) claimed to be smtpclient.apple From: John Nielsen Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\)) Subject: Help me grok the ath(4) device attach code Message-Id: <49AEA1CB-FA85-432F-89D7-8C49B5F3A344@jnielsen.net> Date: Tue, 30 May 2023 11:30:20 -0600 To: "wireless@freebsd.org" X-Mailer: Apple Mail (2.3731.600.7) X-Spamd-Result: default: False [-2.76 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.96)[-0.958]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:6364, ipnet:2607:f170:30::/44, country:US]; FROM_EQ_ENVFROM(0.00)[]; TO_DN_EQ_ADDR_ALL(0.00)[]; MIME_TRACE(0.00)[0:+]; MLMMJ_DEST(0.00)[wireless@FreeBSD.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; DMARC_NA(0.00)[jnielsen.net]; RCPT_COUNT_ONE(0.00)[1]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[wireless@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; HAS_XAW(0.00)[]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4QVzvH3cHWz3lB2 X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N I=E2=80=99m trying to wrap my head around the code in = sys/dev/ath/ath_hal , partly for my own edification but mostly due to = wanting to fix this bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D255337 The card in question is an AR9462, branded (I think) as a Dell Wireless = 1901 with this ID: vendor=3D0x168c device=3D0x0034 subvendor=3D0x1028 subdevice=3D0x020d The card is identified and appears to initialize correctly but it has a = default/bogus MAC address of 00:02:03:04:05:06 and is never able to scan = any networks. It does work fine under Linux, so I=E2=80=99m attempting = to compare the two codebases. But since I=E2=80=99m not a device = developer and haven=E2=80=99t done much C since my undergraduate work, = I=E2=80=99m having a bit of trouble. I=E2=80=99m open to any pointers but I=E2=80=99d specifically like to = work out the following (unless I=E2=80=99m way off base, in which case = I=E2=80=99d like to know that too): 1) Where does the default MAC address come from? In the Linux driver it = looks like it=E2=80=99s here: = https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/tree/drivers= /net/wireless/ath/ath9k/ar9003_eeprom.c#n49 I don=E2=80=99t see any such definition in the FreeBSD code. 2) When ath_hal_attach() calls chip->attach(), which code is actually = called (and how/where is that determined)? 3) Is there any equivalent in the FreeBSD code for this Linux process of = trying to read the EEPROM from multiple different addresses? (Is it = necessary?) = https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/tree/drivers= /net/wireless/ath/ath9k/ar9003_eeprom.c#n3299 See also: = https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/commit/drive= rs/net/wireless/ath/ath9k?id=3D528782ecf59f7bab2f1368628a479f49be59b512 and the definitions here: = https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/tree/drivers= /net/wireless/ath/ath9k/ar9003_eeprom.h#n78 (I don=E2=80=99t see any of those BASE_ADDR values referenced or defined = anywhere in FreeBSD) 4) In general, what code should I be looking at to see how the EEPROM is = read and interpreted for a specific card? Any help appreciated! Thanks, JN From nobody Tue May 30 23:34:59 2023 X-Original-To: wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QW7zg2vDkz4YLxk for ; Tue, 30 May 2023 23:35:11 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (cross.sbone.de [195.201.62.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE Root Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QW7zf49C6z3hk2 for ; Tue, 30 May 2023 23:35:10 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of bzeeb-lists@lists.zabbadoz.net designates 195.201.62.131 as permitted sender) smtp.mailfrom=bzeeb-lists@lists.zabbadoz.net; dmarc=none Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id D1D0F8D4A17C; Tue, 30 May 2023 23:35:02 +0000 (UTC) Received: from content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 843785C3A831; Tue, 30 May 2023 23:35:02 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) by content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (amavisd-new, port 10024) with ESMTP id b03Q0cTIzn0Y; Tue, 30 May 2023 23:35:01 +0000 (UTC) Received: from strong-iwl0.sbone.de (strong-iwl0.sbone.de [IPv6:fde9:577b:c1a9:4902:b66b:fcff:fef3:e3d2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 20B185C3A82F; Tue, 30 May 2023 23:35:00 +0000 (UTC) Date: Tue, 30 May 2023 23:34:59 +0000 (UTC) From: "Bjoern A. Zeeb" To: "Julian H. Stacey" cc: FreeBSD wireless mailing list Subject: Re: regression failure of wpa_supplicant from 12.3-RELEASE to 12.4-RELEASE In-Reply-To: <202305290018.34T0IvHx089059@dell.no.berklix.net> Message-ID: <2q06nn8n-27p2-o573-q508-or24579p92nn@yvfgf.mnoonqbm.arg> References: <202305290018.34T0IvHx089059@dell.no.berklix.net> X-OpenPGP-Key-Id: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Spamd-Result: default: False [-1.60 / 15.00]; URI_HIDDEN_PATH(1.00)[http://www.berklix.com/~jhs/bin/.sh/git-pull.sh]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.997]; NEURAL_HAM_LONG(-0.30)[-0.300]; R_SPF_ALLOW(-0.20)[+ip4:195.201.62.131]; MIME_GOOD(-0.10)[text/plain]; R_DKIM_NA(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[wireless@freebsd.org]; MIME_TRACE(0.00)[0:+]; TO_DN_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:24940, ipnet:195.201.0.0/16, country:DE]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_FIVE(0.00)[5]; DMARC_NA(0.00)[zabbadoz.net]; FROM_HAS_DN(0.00)[]; RCVD_TLS_LAST(0.00)[] X-Rspamd-Queue-Id: 4QW7zf49C6z3hk2 X-Spamd-Bar: - X-ThisMailContainsUnwantedMimeParts: N On Mon, 29 May 2023, Julian H. Stacey wrote: > "Bjoern A. Zeeb" wrote: >> On Thu, 25 May 2023, Julian H. Stacey wrote: >> >>> "Julian H. Stacey" wrote: >>>> Hi wireless@freebsd.org, >>>> I suffered regression failure of wpa_supplicant from 12.3-RELEASE to >>>> 12.4-RELEASE, ifconfig wlan0 | grep status >>>> was not showing status: associated >> >> I don't know the state in 12.x but can you see if >> >> bfb202c4554a72383202a1a401d80721935b8c95 and/or >> 052211e08c0e227277d0c4dc603bba2253eb3d73 >> >> apply and/or help? > > Thanks, I'll read how to extract src/ with those. > I'll read https://docs.freebsd.org/en/books/handbook/mirrors/#git > man git-checkout > or syntax example welcome > > ( I have a src-cur from http://www.berklix.com/~jhs/bin/.sh/git-pull.sh > which calls git pull --ff-only ) git show will give you something you can feed to patch -p1 normally; you can also try git cherry-pick in your local release branch branch. Or if you prefer the web, try https://cgit.freebsd.org/src/commit/?id= (always with replaced with each of the two above); there should be a download link on cgit for these. > Meantime per my >> I'll compare typescripts from 12.3 & 12.4 wpa_supplicant -d > > Ive uploaded transcript of diff -c of good 12.3 & bad 12.4 to > > http://www.berklix.com/~jhs/src/bsd/fixes/freebsd/src/gen/usr.sbin/wpa/wlan.diff > > Cheers, > -- Bjoern A. Zeeb r15:7 From nobody Tue May 30 23:40:43 2023 X-Original-To: wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QW86H1vPnz4YMQY for ; Tue, 30 May 2023 23:40:55 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:13b:39f::9f:25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE Root Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QW86G5dMBz3kcj for ; Tue, 30 May 2023 23:40:54 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Authentication-Results: mx1.freebsd.org; none Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 63CA88D4A17C; Tue, 30 May 2023 23:40:47 +0000 (UTC) Received: from content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 18D805C3A831; Tue, 30 May 2023 23:40:47 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) by content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (amavisd-new, port 10024) with ESMTP id AzVBx9JI5GNE; Tue, 30 May 2023 23:40:45 +0000 (UTC) Received: from strong-iwl0.sbone.de (strong-iwl0.sbone.de [IPv6:fde9:577b:c1a9:4902:b66b:fcff:fef3:e3d2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 16C625C3A82F; Tue, 30 May 2023 23:40:44 +0000 (UTC) Date: Tue, 30 May 2023 23:40:43 +0000 (UTC) From: "Bjoern A. Zeeb" To: John Nielsen cc: "wireless@freebsd.org" Subject: Re: Help me grok the ath(4) device attach code In-Reply-To: <49AEA1CB-FA85-432F-89D7-8C49B5F3A344@jnielsen.net> Message-ID: References: <49AEA1CB-FA85-432F-89D7-8C49B5F3A344@jnielsen.net> X-OpenPGP-Key-Id: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="1098556516-1091208796-1685490045=:48381" X-Rspamd-Queue-Id: 4QW86G5dMBz3kcj X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/32, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --1098556516-1091208796-1685490045=:48381 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8BIT On Tue, 30 May 2023, John Nielsen wrote: > I’m trying to wrap my head around the code in sys/dev/ath/ath_hal , partly for my own edification but mostly due to wanting to fix this bug: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255337 > > The card in question is an AR9462, branded (I think) as a Dell Wireless 1901 with this ID: > vendor=0x168c device=0x0034 subvendor=0x1028 subdevice=0x020d > > The card is identified and appears to initialize correctly but it has a default/bogus MAC address of 00:02:03:04:05:06 and is never able to scan any networks. It does work fine under Linux, so I’m attempting to compare the two codebases. But since I’m not a device developer and haven’t done much C since my undergraduate work, I’m having a bit of trouble. > > I’m open to any pointers but I’d specifically like to work out the following (unless I’m way off base, in which case I’d like to know that too): > > 1) Where does the default MAC address come from? In the Linux driver it looks like it’s here: > https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/tree/drivers/net/wireless/ath/ath9k/ar9003_eeprom.c#n49 > I don’t see any such definition in the FreeBSD code. No idea, but you should end up in a call to ar9300_get_mac_address() from sys/contrib/dev/ath/ath_hal/ar9300/ar9300_misc.c if my guess is right. The call comes from sys/dev/ath/if_ath.c ath_hal_getmac(). Hope that helps you to trace this. > 2) When ath_hal_attach() calls chip->attach(), which code is actually called (and how/where is that determined)? > > 3) Is there any equivalent in the FreeBSD code for this Linux process of trying to read the EEPROM from multiple different addresses? (Is it necessary?) > https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/tree/drivers/net/wireless/ath/ath9k/ar9003_eeprom.c#n3299 > See also: > https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/commit/drivers/net/wireless/ath/ath9k?id=528782ecf59f7bab2f1368628a479f49be59b512 > and the definitions here: > https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/tree/drivers/net/wireless/ath/ath9k/ar9003_eeprom.h#n78 > > (I don’t see any of those BASE_ADDR values referenced or defined anywhere in FreeBSD) > > 4) In general, what code should I be looking at to see how the EEPROM is read and interpreted for a specific card? > > Any help appreciated! > > Thanks, > > JN > > > -- Bjoern A. Zeeb r15:7 --1098556516-1091208796-1685490045=:48381-- From nobody Wed May 31 00:23:34 2023 X-Original-To: wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QW9401S3Cz4YQFL for ; Wed, 31 May 2023 00:24:00 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from webmail5.jnielsen.net (webmail5.jnielsen.net [IPv6:2607:f170:34:11::b0]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.freebsdsolutions.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QW93z5mDqz3pyp for ; Wed, 31 May 2023 00:23:59 +0000 (UTC) (envelope-from lists@jnielsen.net) Authentication-Results: mx1.freebsd.org; none Received: from smtpclient.apple (166-70-14-17.xmission.com [166.70.14.17] (may be forged)) (authenticated bits=0) by webmail5.jnielsen.net (8.17.1/8.17.1) with ESMTPSA id 34V0Nm1N010751 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 30 May 2023 18:23:51 -0600 (MDT) (envelope-from lists@jnielsen.net) X-Authentication-Warning: webmail5.jnielsen.net: Host 166-70-14-17.xmission.com [166.70.14.17] (may be forged) claimed to be smtpclient.apple From: John Nielsen Message-Id: Content-Type: multipart/alternative; boundary="Apple-Mail=_F3F041DD-38E8-4056-8EC4-14FDB0CE9F0B" List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\)) Subject: Re: Help me grok the ath(4) device attach code Date: Tue, 30 May 2023 18:23:34 -0600 In-Reply-To: Cc: "wireless@freebsd.org" To: "Bjoern A. Zeeb" References: <49AEA1CB-FA85-432F-89D7-8C49B5F3A344@jnielsen.net> X-Mailer: Apple Mail (2.3731.600.7) X-Rspamd-Queue-Id: 4QW93z5mDqz3pyp X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:6364, ipnet:2607:f170:30::/44, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --Apple-Mail=_F3F041DD-38E8-4056-8EC4-14FDB0CE9F0B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On May 30, 2023, at 5:40 PM, Bjoern A. Zeeb = wrote: >=20 > On Tue, 30 May 2023, John Nielsen wrote: >=20 >> I=E2=80=99m trying to wrap my head around the code in = sys/dev/ath/ath_hal , partly for my own edification but mostly due to = wanting to fix this bug: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D255337 >>=20 >> The card in question is an AR9462, branded (I think) as a Dell = Wireless 1901 with this ID: >> vendor=3D0x168c device=3D0x0034 subvendor=3D0x1028 subdevice=3D0x020d >>=20 >> The card is identified and appears to initialize correctly but it has = a default/bogus MAC address of 00:02:03:04:05:06 and is never able to = scan any networks. It does work fine under Linux, so I=E2=80=99m = attempting to compare the two codebases. But since I=E2=80=99m not a = device developer and haven=E2=80=99t done much C since my undergraduate = work, I=E2=80=99m having a bit of trouble. >>=20 >> I=E2=80=99m open to any pointers but I=E2=80=99d specifically like to = work out the following (unless I=E2=80=99m way off base, in which case = I=E2=80=99d like to know that too): >>=20 >> 1) Where does the default MAC address come from? In the Linux driver = it looks like it=E2=80=99s here: >> = https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/tree/drivers= /net/wireless/ath/ath9k/ar9003_eeprom.c#n49 >> I don=E2=80=99t see any such definition in the FreeBSD code. >=20 > No idea, but you should end up in a call to ar9300_get_mac_address() > from sys/contrib/dev/ath/ath_hal/ar9300/ar9300_misc.c if my guess is = right. >=20 > The call comes from sys/dev/ath/if_ath.c ath_hal_getmac(). >=20 > Hope that helps you to trace this. Thanks! I had no idea that directory was even there. More source to dive = through... >> 2) When ath_hal_attach() calls chip->attach(), which code is actually = called (and how/where is that determined)? >>=20 >> 3) Is there any equivalent in the FreeBSD code for this Linux process = of trying to read the EEPROM from multiple different addresses? (Is it = necessary?) >> = https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/tree/drivers= /net/wireless/ath/ath9k/ar9003_eeprom.c#n3299 >> See also: >> = https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/commit/drive= rs/net/wireless/ath/ath9k?id=3D528782ecf59f7bab2f1368628a479f49be59b512 >> and the definitions here: >> = https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/tree/drivers= /net/wireless/ath/ath9k/ar9003_eeprom.h#n78 >>=20 >> (I don=E2=80=99t see any of those BASE_ADDR values referenced or = defined anywhere in FreeBSD) >>=20 >> 4) In general, what code should I be looking at to see how the EEPROM = is read and interpreted for a specific card? >>=20 >> Any help appreciated! --Apple-Mail=_F3F041DD-38E8-4056-8EC4-14FDB0CE9F0B Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
On May 30, 2023, = at 5:40 PM, Bjoern A. Zeeb <bzeeb-lists@lists.zabbadoz.net> = wrote:

On Tue, 30 May 2023, = John Nielsen wrote:

I=E2=80=99m trying to wrap my head around the = code in sys/dev/ath/ath_hal , partly for my own edification but mostly = due to wanting to fix this = bug:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D255337

= The card in question is an AR9462, branded (I think) as a Dell Wireless = 1901 with this ID:
vendor=3D0x168c device=3D0x0034 subvendor=3D0x1028 = subdevice=3D0x020d

The card is identified and appears to = initialize correctly but it has a default/bogus MAC address of = 00:02:03:04:05:06 and is never able to scan any networks. It does work = fine under Linux, so I=E2=80=99m attempting to compare the two = codebases. But since I=E2=80=99m not a device developer and haven=E2=80=99= t done much C since my undergraduate work, I=E2=80=99m having a bit of = trouble.

I=E2=80=99m open to any pointers but I=E2=80=99d = specifically like to work out the following (unless I=E2=80=99m way off = base, in which case I=E2=80=99d like to know that too):

1) Where = does the default MAC address come from? In the Linux driver it looks = like it=E2=80=99s = here:
https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/tre= e/drivers/net/wireless/ath/ath9k/ar9003_eeprom.c#n49
I don=E2=80=99t = see any such definition in the FreeBSD code.

No idea, but you should end up in a call to = ar9300_get_mac_address()
from = sys/contrib/dev/ath/ath_hal/ar9300/ar9300_misc.c if my guess is = right.

The call comes from = sys/dev/ath/if_ath.c ath_hal_getmac().

Hope = that helps you to trace this.

Thanks! I = had no idea that directory was even there. More source to dive = through...

2) When ath_hal_attach() calls chip->attach(), which code is = actually called (and how/where is that determined)?

3) Is there = any equivalent in the FreeBSD code for this Linux process of trying to = read the EEPROM from multiple different addresses? (Is it = necessary?)
https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.g= it/tree/drivers/net/wireless/ath/ath9k/ar9003_eeprom.c#n3299
See = also:
https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/com= mit/drivers/net/wireless/ath/ath9k?id=3D528782ecf59f7bab2f1368628a479f49be= 59b512
and the definitions = here:
https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/tre= e/drivers/net/wireless/ath/ath9k/ar9003_eeprom.h#n78

(I don=E2=80=99= t see any of those BASE_ADDR values referenced or defined anywhere in = FreeBSD)

4) In general, what code should I be looking at to see = how the EEPROM is read and interpreted for a specific card?

Any = help = appreciated!

= --Apple-Mail=_F3F041DD-38E8-4056-8EC4-14FDB0CE9F0B-- From nobody Wed May 31 02:02:47 2023 X-Original-To: wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QWCGH2NgHz4XYjJ for ; Wed, 31 May 2023 02:03:03 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-lf1-f46.google.com (mail-lf1-f46.google.com [209.85.167.46]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QWCGH06STz3wCR for ; Wed, 31 May 2023 02:03:03 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-lf1-f46.google.com with SMTP id 2adb3069b0e04-4f4f89f71b8so3911561e87.3 for ; Tue, 30 May 2023 19:03:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685498580; x=1688090580; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=7xJq89d5CIVhfT0M3AqVwbPhKlx3ER1UCe4Pgwb9G1Y=; b=egdhWNuBdMHgmVWLMO+NZ3jGeJZVGuipHRjEQ8nyZ6OSMeu4rIM77Q7aKjCoxaIEZF FQuwYo6yWGDvFDYp5jD1l9UAt+U5OYceP2751vIYim1u7nvqa6C1ecCUeSLZWpjp6TX3 EgsHZ11zLnbXjFpAsEqVBleYkEoWwrArZFYK3LHAtk6NCkwQsRpgctN4gNOY2mM/fTek LTnmpbWTDK6nJ9PkG7iZWyiZlbLvGtQSxAYrEtrdecwFINt8O4CKoLAdX43LE0ws/yk5 CWgH67jTmzEgEW4mu0RuVo3k+nDw/vDvHT6lMjBj4ai40kkcKsj/tKtw5/5net1b2CJZ gXBQ== X-Gm-Message-State: AC+VfDwmEiUSgDRvqMpb0NdjMGgPaJScPIK7a55zKYMZKUVqaSLpjuAw 2GuypcBAD6pJkN3wCGz+RXJr+mGGKMbemqWMo7I= X-Google-Smtp-Source: ACHHUZ56j0wC7+3DB7TLK6MjopvwoJSt5GkTMEDsyVq+kfB/QPhXuoyG7XUQAAsMSsddkwJMrua4MgBmUqljUX3kxd8= X-Received: by 2002:a19:ac45:0:b0:4f3:b1e6:4b46 with SMTP id r5-20020a19ac45000000b004f3b1e64b46mr1704003lfc.12.1685498579751; Tue, 30 May 2023 19:02:59 -0700 (PDT) List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org MIME-Version: 1.0 References: <49AEA1CB-FA85-432F-89D7-8C49B5F3A344@jnielsen.net> In-Reply-To: From: Adrian Chadd Date: Tue, 30 May 2023 19:02:47 -0700 Message-ID: Subject: Re: Help me grok the ath(4) device attach code To: John Nielsen Cc: "Bjoern A. Zeeb" , "wireless@freebsd.org" Content-Type: multipart/alternative; boundary="0000000000001d982a05fcf3b80f" X-Rspamd-Queue-Id: 4QWCGH06STz3wCR X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --0000000000001d982a05fcf3b80f Content-Type: text/plain; charset="UTF-8" Err, if it's coming up w/ that MAC then it's not finding and attaching right to the OTP/EEPROM calibration information. That's the big red flag that it in general won't work correctly. Can you provide the rest of the ath_hal messages? I'd like to see what it's saying during boot around it checking the EEPROM/OTP contents. It's possible there's some work around required for this NIC. --0000000000001d982a05fcf3b80f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Err, if it's coming up w/ that MAC= then it's not finding and attaching right to the OTP/EEPROM calibratio= n information. That's the big red flag that it in general won't wor= k correctly.

Can you provide the rest of the ath_h= al messages? I'd like to see what it's saying during boot around it= checking=C2=A0the EEPROM/OTP contents. It's possible there's some = work around required for this NIC.


=
--0000000000001d982a05fcf3b80f-- From nobody Wed May 31 03:55:40 2023 X-Original-To: wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QWFml1vXlz4Xy6D for ; Wed, 31 May 2023 03:56:07 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from webmail5.jnielsen.net (webmail5.jnielsen.net [IPv6:2607:f170:34:11::b0]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.freebsdsolutions.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QWFmk5bTwz46JC; Wed, 31 May 2023 03:56:06 +0000 (UTC) (envelope-from lists@jnielsen.net) Authentication-Results: mx1.freebsd.org; none Received: from smtpclient.apple (166-70-14-17.xmission.com [166.70.14.17] (may be forged)) (authenticated bits=0) by webmail5.jnielsen.net (8.17.1/8.17.1) with ESMTPSA id 34V3tpbk013727 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 30 May 2023 21:55:53 -0600 (MDT) (envelope-from lists@jnielsen.net) X-Authentication-Warning: webmail5.jnielsen.net: Host 166-70-14-17.xmission.com [166.70.14.17] (may be forged) claimed to be smtpclient.apple Content-Type: text/plain; charset=utf-8 List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\)) Subject: Re: Help me grok the ath(4) device attach code From: John Nielsen In-Reply-To: Date: Tue, 30 May 2023 21:55:40 -0600 Cc: "Bjoern A. Zeeb" , "wireless@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: <85BF3AB2-2EBF-4398-A507-ABA35505A56C@jnielsen.net> References: <49AEA1CB-FA85-432F-89D7-8C49B5F3A344@jnielsen.net> To: Adrian Chadd X-Mailer: Apple Mail (2.3731.600.7) X-Rspamd-Queue-Id: 4QWFmk5bTwz46JC X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:6364, ipnet:2607:f170:30::/44, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N > On May 30, 2023, at 8:02 PM, Adrian Chadd wrote: >=20 > Err, if it's coming up w/ that MAC then it's not finding and attaching = right to the OTP/EEPROM calibration information. That's the big red flag = that it in general won't work correctly. >=20 > Can you provide the rest of the ath_hal messages? I'd like to see what = it's saying during boot around it checking the EEPROM/OTP contents. It's = possible there's some work around required for this NIC. He speaks! Thanks for taking the time. I just realized that = ath_hal_printf doesn=E2=80=99t prepend =E2=80=9Cath%d=E2=80=9D so I=E2=80=99= ve been missing those messages when grep-ing. Here=E2=80=99s the whole = snippet: ath0: mem 0xf7a00000-0xf7a7ffff at device 0.0 on = pci4 ar9300_flash_map: unimplemented for now Restoring Cal data from DRAM Restoring Cal data from EEPROM Restoring Cal data from Flash Restoring Cal data from Flash Restoring Cal data from OTP ar9300_eeprom_restore_internal[4338] No vaid CAL, calling default = template ar9300_hw_attach: ar9300_eeprom_attach returned 0 ath0: [HT] enabling HT modes ath0: [HT] enabling short-GI in 20MHz mode ath0: [HT] 1 stream STBC receive enabled ath0: [HT] 1 stream STBC transmit enabled ath0: [HT] LDPC transmit/receive enabled ath0: [HT] 3 RX streams; 3 TX streams ath0: AR9460 mac 640.2 RF5110 phy 0.0 ath0: 2GHz radio: 0x0000; 5GHz radio: 0x0000 And the comments in ar9300_eeprom_restore_something() are less = faith-inspiring the farther down you read.. I was about to add some = printfs there to see when it finally returns, I=E2=80=99ll post what I = learn. I=E2=80=99m happy to do any other code modifications or testing = you=E2=80=99d suggest as well. -JN From nobody Wed May 31 04:56:04 2023 X-Original-To: wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QWH6F2yNgz4Y2g0 for ; Wed, 31 May 2023 04:56:21 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-lj1-f179.google.com (mail-lj1-f179.google.com [209.85.208.179]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QWH6C2K5hz4DN3 for ; Wed, 31 May 2023 04:56:19 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-lj1-f179.google.com with SMTP id 38308e7fff4ca-2af1c884b08so6722311fa.1 for ; Tue, 30 May 2023 21:56:19 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685508977; x=1688100977; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=+nq3iW37VCsm/+xCv6gepKcYPk0k2xdAB4LiWZLehHE=; b=NhTn6T8TTCu8TGkC52dFpoBJMJVsKU5qwO4Ct6NGGNRtu9P5CKg2OeMXy+Maju5bVH tjSDJ0s3hlIN3on+EwfQQOfhjQ17R35w3DVbyLKDsff4V27h5D0dVtNZPk9Z56YJuiGb MbTZ7vlRHbfFCRCEgI/tu2I9cxgrIKVaSXyI3ZoRB1t9/E7GWgSDu8DTbH8TTepXpNM3 a5vCYVyeJh3n2T5GBNcYQRc2W+oPZkWomwhWV/wgUgnmJ2+GIbmwzac8kcBtb1ssvWpr 8RgwPppRcmsjJetylDBRXstN+rUONUTwSFHzVLQdQiobD9mIncVwGSOeAjjSfrftIKtK ksSg== X-Gm-Message-State: AC+VfDwiI/A2d2v+U/Ckw4AqLnnTDMrnzJflZ95TFb+413oG1i+ilybe Uw1KXYI1OcFNmWTrjhfGCSK7tuavPqaHLVAnA+9bqhsk X-Google-Smtp-Source: ACHHUZ7AJgblAAYlLxw/YqNla8/lSqdndzWBToOGEqEpGGb8JikG9EBRqeprz13cmuRh0/H3pCVagGFcUXil7BqbDYk= X-Received: by 2002:a05:651c:11cd:b0:2ad:d8e2:3948 with SMTP id z13-20020a05651c11cd00b002add8e23948mr4729097ljo.24.1685508976812; Tue, 30 May 2023 21:56:16 -0700 (PDT) List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org MIME-Version: 1.0 References: <49AEA1CB-FA85-432F-89D7-8C49B5F3A344@jnielsen.net> <85BF3AB2-2EBF-4398-A507-ABA35505A56C@jnielsen.net> In-Reply-To: <85BF3AB2-2EBF-4398-A507-ABA35505A56C@jnielsen.net> From: Adrian Chadd Date: Tue, 30 May 2023 21:56:04 -0700 Message-ID: Subject: Re: Help me grok the ath(4) device attach code To: John Nielsen Cc: "Bjoern A. Zeeb" , "wireless@freebsd.org" Content-Type: multipart/alternative; boundary="000000000000d4282205fcf623c2" X-Rspamd-Queue-Id: 4QWH6C2K5hz4DN3 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; TAGGED_FROM(0.00)[] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000d4282205fcf623c2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, 30 May 2023 at 20:56, John Nielsen wrote: > > On May 30, 2023, at 8:02 PM, Adrian Chadd wrote: > > > > Err, if it's coming up w/ that MAC then it's not finding and attaching > right to the OTP/EEPROM calibration information. That's the big red flag > that it in general won't work correctly. > > > > Can you provide the rest of the ath_hal messages? I'd like to see what > it's saying during boot around it checking the EEPROM/OTP contents. It's > possible there's some work around required for this NIC. > > He speaks! Thanks for taking the time. I just realized that ath_hal_print= f > doesn=E2=80=99t prepend =E2=80=9Cath%d=E2=80=9D so I=E2=80=99ve been miss= ing those messages when grep-ing. > Here=E2=80=99s the whole snippet: > > ath0: mem 0xf7a00000-0xf7a7ffff at device 0.0 on > pci4 > ar9300_flash_map: unimplemented for now > Restoring Cal data from DRAM > Restoring Cal data from EEPROM > Restoring Cal data from Flash > Restoring Cal data from Flash > Restoring Cal data from OTP > ar9300_eeprom_restore_internal[4338] No vaid CAL, calling default templat= e > ar9300_hw_attach: ar9300_eeprom_attach returned 0 > Yeah, this bit right here is the problem. It's not finding a valid calibration. I wonder what ath9k is doing here? Is there some weird pci based workaround/flag for the given NIC PCI id? -a --000000000000d4282205fcf623c2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Tue, 30 May 2023 at 20:56, John Ni= elsen <lists@jnielsen.net> = wrote:
> On M= ay 30, 2023, at 8:02 PM, Adrian Chadd <adrian@freebsd.org> wrote:
>
> Err, if it's coming up w/ that MAC then it's not finding and a= ttaching right to the OTP/EEPROM calibration information. That's the bi= g red flag that it in general won't work correctly.
>
> Can you provide the rest of the ath_hal messages? I'd like to see = what it's saying during boot around it checking the EEPROM/OTP contents= . It's possible there's some work around required for this NIC.

He speaks! Thanks for taking the time. I just realized that ath_hal_printf = doesn=E2=80=99t prepend =E2=80=9Cath%d=E2=80=9D so I=E2=80=99ve been missin= g those messages when grep-ing. Here=E2=80=99s the whole snippet:

ath0: <Atheros AR946x/AR948x> mem 0xf7a00000-0xf7a7ffff at device 0.0= on pci4
ar9300_flash_map: unimplemented for now
Restoring Cal data from DRAM
Restoring Cal data from EEPROM
Restoring Cal data from Flash
Restoring Cal data from Flash
Restoring Cal data from OTP
ar9300_eeprom_restore_internal[4338] No vaid CAL, calling default template<= br> ar9300_hw_attach: ar9300_eeprom_attach returned 0

=
Yeah, this bit right here is the problem. It's not finding a= valid calibration.

=C2=A0I wonder what ath9k is d= oing here? Is there some weird pci based workaround/flag for the given NIC = PCI id?


-a

--000000000000d4282205fcf623c2-- From nobody Wed May 31 04:58:48 2023 X-Original-To: wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QWH9N1zzRz4Y3K7 for ; Wed, 31 May 2023 04:59:04 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-lj1-f176.google.com (mail-lj1-f176.google.com [209.85.208.176]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QWH9L68Ctz4D4V for ; Wed, 31 May 2023 04:59:02 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of adrian.chadd@gmail.com designates 209.85.208.176 as permitted sender) smtp.mailfrom=adrian.chadd@gmail.com; dmarc=none Received: by mail-lj1-f176.google.com with SMTP id 38308e7fff4ca-2af98eb6ef0so58238791fa.3 for ; Tue, 30 May 2023 21:59:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685509141; x=1688101141; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=LSqWX4h4773G9XgE1aWjAzWZI2IGOsSbwT5wLgqMixs=; b=XNxqN3pnPqio7MALc7ptoMk6JtB8Qxcq4aZRpR4eOduWYebp5hM4ajzYDqW7E4QEYB 7plAymrifUHsyqgduzJPXlLNhYaavqLqJmn3t4GRQ/T5WcOY3N/ODMHyzDMB64kb9lTE HZaPI051V5msylpBvapO/cfDluZWk1pEpwpwmhtYHHfZhjpprnktF58yKC9OAtBaQ3Z8 wfT2ZndIpyjLTDVPJtnB7cGC9rEmVBh7BY6YOvlykrSfIuE1N08Y3aBSB9JnOFRTawHw FVqSukexhDPWtmoU+ih1i5n3K8GQOOVfsdjibnSIx/o2GO2Tj6xN6JpvzZyuBus/qQMd Howg== X-Gm-Message-State: AC+VfDzHdChq0emmCxNepmppREv0kTbbzgJEFT69AQQvPMPjm6KQ/6g5 oNUN9ygFXnznsG3tZkeZqutQEJA2W71jIoYzPqU= X-Google-Smtp-Source: ACHHUZ7o1Q19aw7c2RtbmPRY41PtB7Qr7ljO/ltWo1AVruP+sxC4WnzIgQ8jgDV9my3Xg4bAufE7aOpxFGT9tuDW/rw= X-Received: by 2002:a2e:2e11:0:b0:2a8:d021:4121 with SMTP id u17-20020a2e2e11000000b002a8d0214121mr1926314lju.26.1685509140971; Tue, 30 May 2023 21:59:00 -0700 (PDT) List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org MIME-Version: 1.0 References: <49AEA1CB-FA85-432F-89D7-8C49B5F3A344@jnielsen.net> <85BF3AB2-2EBF-4398-A507-ABA35505A56C@jnielsen.net> In-Reply-To: From: Adrian Chadd Date: Tue, 30 May 2023 21:58:48 -0700 Message-ID: Subject: Re: Help me grok the ath(4) device attach code To: John Nielsen Cc: "Bjoern A. Zeeb" , "wireless@freebsd.org" Content-Type: multipart/alternative; boundary="0000000000009d054505fcf62dd6" X-Spamd-Result: default: False [-2.46 / 15.00]; NEURAL_HAM_LONG(-0.99)[-0.986]; NEURAL_HAM_SHORT(-0.74)[-0.743]; NEURAL_HAM_MEDIUM(-0.74)[-0.736]; FORGED_SENDER(0.30)[adrian@freebsd.org,adrianchadd@gmail.com]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.208.176:from]; MLMMJ_DEST(0.00)[wireless@freebsd.org]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_IN_DNSWL_NONE(0.00)[209.85.208.176:from]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FROM_NEQ_ENVFROM(0.00)[adrian@freebsd.org,adrianchadd@gmail.com]; RCPT_COUNT_THREE(0.00)[3]; FROM_HAS_DN(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[freebsd.org]; PREVIOUSLY_DELIVERED(0.00)[wireless@freebsd.org]; TO_DN_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4QWH9L68Ctz4D4V X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N --0000000000009d054505fcf62dd6 Content-Type: text/plain; charset="UTF-8" oh err, is there a wifi enable/disable switch or something? maybe it's asserted and somehow it's mucking up the NIC? -a --0000000000009d054505fcf62dd6 Content-Type: text/html; charset="UTF-8"
oh err, is there a wifi enable/disable switch or something? maybe it's asserted and somehow it's mucking up the NIC?


-a

--0000000000009d054505fcf62dd6-- From nobody Wed May 31 05:11:59 2023 X-Original-To: wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QWHSl2jjYz4Y3xD for ; Wed, 31 May 2023 05:12:23 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from webmail5.jnielsen.net (webmail5.jnielsen.net [IPv6:2607:f170:34:11::b0]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.freebsdsolutions.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QWHSl1YZRz4FlG; Wed, 31 May 2023 05:12:23 +0000 (UTC) (envelope-from lists@jnielsen.net) Authentication-Results: mx1.freebsd.org; none Received: from smtpclient.apple (166-70-14-17.xmission.com [166.70.14.17] (may be forged)) (authenticated bits=0) by webmail5.jnielsen.net (8.17.1/8.17.1) with ESMTPSA id 34V5CDoT015008 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 30 May 2023 23:12:15 -0600 (MDT) (envelope-from lists@jnielsen.net) X-Authentication-Warning: webmail5.jnielsen.net: Host 166-70-14-17.xmission.com [166.70.14.17] (may be forged) claimed to be smtpclient.apple From: John Nielsen Message-Id: Content-Type: multipart/alternative; boundary="Apple-Mail=_CC3AA7E8-0C74-4073-A6D6-F36E10D493C3" List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\)) Subject: Re: Help me grok the ath(4) device attach code Date: Tue, 30 May 2023 23:11:59 -0600 In-Reply-To: Cc: "Bjoern A. Zeeb" , "wireless@freebsd.org" To: Adrian Chadd References: <49AEA1CB-FA85-432F-89D7-8C49B5F3A344@jnielsen.net> <85BF3AB2-2EBF-4398-A507-ABA35505A56C@jnielsen.net> X-Mailer: Apple Mail (2.3731.600.7) X-Rspamd-Queue-Id: 4QWHSl1YZRz4FlG X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:6364, ipnet:2607:f170:30::/44, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --Apple-Mail=_CC3AA7E8-0C74-4073-A6D6-F36E10D493C3 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On May 30, 2023, at 10:56 PM, Adrian Chadd wrote: >=20 > On Tue, 30 May 2023 at 20:56, John Nielsen > wrote: >> > On May 30, 2023, at 8:02 PM, Adrian Chadd > wrote: >> >=20 >> > Err, if it's coming up w/ that MAC then it's not finding and = attaching right to the OTP/EEPROM calibration information. That's the = big red flag that it in general won't work correctly. >> >=20 >> > Can you provide the rest of the ath_hal messages? I'd like to see = what it's saying during boot around it checking the EEPROM/OTP contents. = It's possible there's some work around required for this NIC. >>=20 >> He speaks! Thanks for taking the time. I just realized that = ath_hal_printf doesn=E2=80=99t prepend =E2=80=9Cath%d=E2=80=9D so I=E2=80=99= ve been missing those messages when grep-ing. Here=E2=80=99s the whole = snippet: >>=20 >> ath0: mem 0xf7a00000-0xf7a7ffff at device 0.0 = on pci4 >> ar9300_flash_map: unimplemented for now >> Restoring Cal data from DRAM >> Restoring Cal data from EEPROM >> Restoring Cal data from Flash >> Restoring Cal data from Flash >> Restoring Cal data from OTP >> ar9300_eeprom_restore_internal[4338] No vaid CAL, calling default = template >> ar9300_hw_attach: ar9300_eeprom_attach returned 0 >=20 > Yeah, this bit right here is the problem. It's not finding a valid = calibration. > oh err, is there a wifi enable/disable switch or something? maybe it's = asserted and somehow it's mucking up the NIC? There is a physical switch and it=E2=80=99s in the =E2=80=9Cenable=E2=80=9D= position. > I wonder what ath9k is doing here? Is there some weird pci based = workaround/flag for the given NIC PCI id? That was the first breadcrumb BZ threw me but I can=E2=80=99t find = anything. There are some .driver_data hints for adjacent subdevice IDs = but none for this one (Dell 0x020d) in either FreeBSD or Linux that I = could find. The kernel on the Arch Linux USB I have handy doesn=E2=80=99t appear to = have been compiled with CONFIG_ATH_DEBUG but here=E2=80=99s what it has = in /sys/kernel/ieee80211/phy0/ath9k/base_eeprom: EEPROM Version : 2 RegDomain1 : 108 RegDomain2 : 31 TX Mask : 3 RX Mask : 3 Allow 5GHz : 1 Allow 2GHz : 1 Disable 2GHz HT20 : 0 Disable 2GHz HT40 : 0 Disable 5Ghz HT20 : 0 Disable 5Ghz HT40 : 0 Big Endian : 0 RF Silent : 45 BT option : 0 Device Cap : 0 Device Type : 5 Power Table Offset : 0 Tuning Caps1 : 0 Tuning Caps2 : 0 Enable Tx Temp Comp : 1 Enable Tx Volt Comp : 0 Enable fast clock : 1 Enable doubling : 1 Internal regulator : 0 Enable Paprd : 0 Driver Strength : 0 Quick Drop : 1 Chain mask Reduce : 0 Write enable Gpio : 6 WLAN Disable Gpio : 0 WLAN LED Gpio : 8 Rx Band Select Gpio : 255 Tx Gain : 1 Rx Gain : 3 SW Reg : 303972983 MacAddress : 44:39:c4:5b:44:4a It also has some calibration and other data in modal_eeprom.=20 There is this commit in ath9k which mentions an alternative EEPROM = address, but I=E2=80=99m not sure if that=E2=80=99s relevant. =46rom = what I can tell the probe should succeed at the normal base_address = 0x3ff instead of needing to try the =E2=80=9C4k=E2=80=9D one 0xfff. = https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/commit/drive= rs/net/wireless/ath/ath9k?id=3D528782ecf59f7bab2f1368628a479f49be59b512 --Apple-Mail=_CC3AA7E8-0C74-4073-A6D6-F36E10D493C3 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
On May 30, 2023, = at 10:56 PM, Adrian Chadd <adrian@freebsd.org> = wrote:

On Tue, 30 = May 2023 at 20:56, John Nielsen <lists@jnielsen.net> = wrote:
> On May = 30, 2023, at 8:02 PM, Adrian Chadd <adrian@freebsd.org> wrote:
> 
> Err, if it's = coming up w/ that MAC then it's not finding and attaching right to the = OTP/EEPROM calibration information. That's the big red flag that it in = general won't work correctly.
> 
> Can you provide = the rest of the ath_hal messages? I'd like to see what it's saying = during boot around it checking the EEPROM/OTP contents. It's possible = there's some work around required for this NIC.

He speaks! Thanks = for taking the time. I just realized that ath_hal_printf doesn=E2=80=99t = prepend =E2=80=9Cath%d=E2=80=9D so I=E2=80=99ve been missing those = messages when grep-ing. Here=E2=80=99s the whole snippet:

ath0: = <Atheros AR946x/AR948x> mem 0xf7a00000-0xf7a7ffff at device 0.0 on = pci4
ar9300_flash_map: unimplemented for now
Restoring Cal data = from DRAM
Restoring Cal data from EEPROM
Restoring Cal data from = Flash
Restoring Cal data from Flash
Restoring Cal data from = OTP
ar9300_eeprom_restore_internal[4338] No vaid CAL, calling default = template
ar9300_hw_attach: ar9300_eeprom_attach returned = 0

Yeah, this bit right here is the = problem. It's not finding a valid = calibration.

oh err, is there a = wifi enable/disable switch or something? maybe it's asserted and somehow = it's mucking up the NIC?

There is a physical = switch and it=E2=80=99s in the =E2=80=9Cenable=E2=80=9D = position.

 I wonder what ath9k is doing here? Is there some weird = pci based workaround/flag for the given NIC PCI = id?

That was the first = breadcrumb BZ threw me but I can=E2=80=99t find anything. There are some = .driver_data hints for adjacent subdevice IDs but none for this one = (Dell 0x020d) in either FreeBSD or Linux that I could = find.

The kernel on the Arch Linux USB I have = handy doesn=E2=80=99t appear to have been compiled with CONFIG_ATH_DEBUG = but here=E2=80=99s what it has in = /sys/kernel/ieee80211/phy0/ath9k/base_eeprom:
  =     EEPROM Version :         =  2
          RegDomain1 :   =      108
          = RegDomain2 :         31
    =          TX Mask :         =  3
             RX = Mask :          3
    =       Allow 5GHz :         =  1
          Allow 2GHz :   =        1
   Disable 2GHz HT20 : =          0
   Disable 2GHz = HT40 :          0
  =  Disable 5Ghz HT20 :         =  0
   Disable 5Ghz HT40 :       =    0
          Big Endian : =          0
      =      RF Silent :         = 45
           BT option :   =        0
        =   Device Cap :          0
  =        Device Type :         =  5
  Power Table Offset :       =    0
        Tuning Caps1 : =          0
      =   Tuning Caps2 :         =  0
 Enable Tx Temp Comp :       =    1
 Enable Tx Volt Comp :     =      0
   Enable fast clock :   =        1
     Enable = doubling :          1
  Internal = regulator :          0
    =     Enable Paprd :         =  0
     Driver Strength :     =      0
          Quick = Drop :          1
   Chain = mask Reduce :          0
  =  Write enable Gpio :         =  6
   WLAN Disable Gpio :       =    0
       WLAN LED Gpio : =          8
 Rx Band Select Gpio = :        255
        =      Tx Gain :         =  1
             Rx = Gain :          3
    =           SW Reg : =  303972983
          MacAddress = : 44:39:c4:5b:44:4a

It also has some = calibration and other data in = modal_eeprom. 

There is this commit in = ath9k which mentions an alternative EEPROM address, but I=E2=80=99m not = sure if that=E2=80=99s relevant. =46rom what I can tell the probe should = succeed at the normal base_address 0x3ff instead of needing to try the = =E2=80=9C4k=E2=80=9D one = 0xfff.
https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.g= it/commit/drivers/net/wireless/ath/ath9k?id=3D528782ecf59f7bab2f1368628a47= 9f49be59b512

= --Apple-Mail=_CC3AA7E8-0C74-4073-A6D6-F36E10D493C3-- From nobody Wed May 31 05:17:19 2023 X-Original-To: wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QWHZk0V8cz4Y4Qm for ; Wed, 31 May 2023 05:17:34 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-lf1-f45.google.com (mail-lf1-f45.google.com [209.85.167.45]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QWHZj4rHNz4FmG for ; Wed, 31 May 2023 05:17:33 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-lf1-f45.google.com with SMTP id 2adb3069b0e04-4f4b384c09fso6262459e87.3 for ; Tue, 30 May 2023 22:17:33 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685510252; x=1688102252; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=oRLON56D3Fr8Rd9wMKm7GR1sz5nBxYf1//qWyzeJzzY=; b=Xrnd8zilBI4sRgDJBrhPIO9y+pgRKBIhHiHOKaVv4AuuSD7Ot9SpGzbUyql2V7NDlK pK5inxmMvtZ+waU7d2jU42innAQhhipMgYz8uFwYYnO3LsVbv8kFKNzH1hBZMqW8vlAZ cNEbwqmoqgRBuDD72NTjIyT63urfjphEdUVxf2WjLzNay6cnGtspZAMb+j2JKVyiLVaJ vKnkkUmZYqPC74oyp/38/eCByrqqZV3MbhAAIdvWRVIKB/7KrBX674WrF6umUrv2wddN 33th9gAXJ2uUsZ77HYTaZEfOLvIYrvjRiCue8/q9smvwjr87PIe2pR4rC22c/90JWaaS UHYg== X-Gm-Message-State: AC+VfDyL3u7g7Q2mburl4Ke9ApPllEZHZ2Id4O9CREFPF4VSFXLz7NlD mEBgpj0JfS7dcDVbYLCF7zmeZ/COwfiMKhgwG8t7gAA9 X-Google-Smtp-Source: ACHHUZ7JwUWFtubJvGgxHQO3xJ7sH5+QB4Awr9blQ0EnH1mKFKdmbEvPuY6G8vlGHh4M6xvGOTTzfu8RS0j6NOOm+M4= X-Received: by 2002:a2e:828f:0:b0:2af:2466:1c18 with SMTP id y15-20020a2e828f000000b002af24661c18mr2109822ljg.18.1685510251746; Tue, 30 May 2023 22:17:31 -0700 (PDT) List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org MIME-Version: 1.0 References: <49AEA1CB-FA85-432F-89D7-8C49B5F3A344@jnielsen.net> <85BF3AB2-2EBF-4398-A507-ABA35505A56C@jnielsen.net> In-Reply-To: From: Adrian Chadd Date: Tue, 30 May 2023 22:17:19 -0700 Message-ID: Subject: Re: Help me grok the ath(4) device attach code To: John Nielsen Cc: "Bjoern A. Zeeb" , "wireless@freebsd.org" Content-Type: multipart/alternative; boundary="000000000000d21add05fcf66f78" X-Rspamd-Queue-Id: 4QWHZj4rHNz4FmG X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; TAGGED_FROM(0.00)[] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000d21add05fcf66f78 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, 30 May 2023 at 22:12, John Nielsen wrote: > On May 30, 2023, at 10:56 PM, Adrian Chadd wrote: > > On Tue, 30 May 2023 at 20:56, John Nielsen wrote: > >> > On May 30, 2023, at 8:02 PM, Adrian Chadd wrote: >> > >> > Err, if it's coming up w/ that MAC then it's not finding and attaching >> right to the OTP/EEPROM calibration information. That's the big red flag >> that it in general won't work correctly. >> > >> > Can you provide the rest of the ath_hal messages? I'd like to see what >> it's saying during boot around it checking the EEPROM/OTP contents. It's >> possible there's some work around required for this NIC. >> >> He speaks! Thanks for taking the time. I just realized that >> ath_hal_printf doesn=E2=80=99t prepend =E2=80=9Cath%d=E2=80=9D so I=E2= =80=99ve been missing those messages >> when grep-ing. Here=E2=80=99s the whole snippet: >> >> ath0: mem 0xf7a00000-0xf7a7ffff at device 0.0 on >> pci4 >> ar9300_flash_map: unimplemented for now >> Restoring Cal data from DRAM >> Restoring Cal data from EEPROM >> Restoring Cal data from Flash >> Restoring Cal data from Flash >> Restoring Cal data from OTP >> ar9300_eeprom_restore_internal[4338] No vaid CAL, calling default templa= te >> ar9300_hw_attach: ar9300_eeprom_attach returned 0 >> > > Yeah, this bit right here is the problem. It's not finding a valid > calibration. > > > oh err, is there a wifi enable/disable switch or something? maybe it's > asserted and somehow it's mucking up the NIC? > > > There is a physical switch and it=E2=80=99s in the =E2=80=9Cenable=E2=80= =9D position. > > I wonder what ath9k is doing here? Is there some weird pci based > workaround/flag for the given NIC PCI id? > > > That was the first breadcrumb BZ threw me but I can=E2=80=99t find anythi= ng. There > are some .driver_data hints for adjacent subdevice IDs but none for this > one (Dell 0x020d) in either FreeBSD or Linux that I could find. > > The kernel on the Arch Linux USB I have handy doesn=E2=80=99t appear to h= ave been > compiled with CONFIG_ATH_DEBUG but here=E2=80=99s what it has in > /sys/kernel/ieee80211/phy0/ath9k/base_eeprom: > EEPROM Version : 2 > RegDomain1 : 108 > RegDomain2 : 31 > TX Mask : 3 > RX Mask : 3 > Allow 5GHz : 1 > Allow 2GHz : 1 > Disable 2GHz HT20 : 0 > Disable 2GHz HT40 : 0 > Disable 5Ghz HT20 : 0 > Disable 5Ghz HT40 : 0 > Big Endian : 0 > RF Silent : 45 > BT option : 0 > Device Cap : 0 > Device Type : 5 > Power Table Offset : 0 > Tuning Caps1 : 0 > Tuning Caps2 : 0 > Enable Tx Temp Comp : 1 > Enable Tx Volt Comp : 0 > Enable fast clock : 1 > Enable doubling : 1 > Internal regulator : 0 > Enable Paprd : 0 > Driver Strength : 0 > Quick Drop : 1 > Chain mask Reduce : 0 > Write enable Gpio : 6 > WLAN Disable Gpio : 0 > WLAN LED Gpio : 8 > Rx Band Select Gpio : 255 > Tx Gain : 1 > Rx Gain : 3 > SW Reg : 303972983 > MacAddress : 44:39:c4:5b:44:4a > > It also has some calibration and other data in modal_eeprom. > > There is this commit in ath9k which mentions an alternative EEPROM > address, but I=E2=80=99m not sure if that=E2=80=99s relevant. From what I= can tell the > probe should succeed at the normal base_address 0x3ff instead of needing = to > try the =E2=80=9C4k=E2=80=9D one 0xfff. > > https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/commit/driv= ers/net/wireless/ath/ath9k?id=3D528782ecf59f7bab2f1368628a479f49be59b512 > Yeah i'd try that. It'd be nice if I knew that the NIC used OTP or EEPROM though. There's known issues with all the Atheros chips (sigh) with how the EEPROM and PCIe bus reset .. interact. (If the bus reset is too short then the EEPROM state machine gets stuck and nothing gets read.) It makes debugging this hard because the NIC itself will work in another device fine, because it's the BIOS/ACPI code. :( -adrian --000000000000d21add05fcf66f78 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Tue, 30 May 2023 at 22:12, John Ni= elsen <lists@jnielsen.net> = wrote:
On May 30, 2023, at 10:56 PM, Adrian Chadd = <adrian@freebsd.= org> wrote:

On Tue, 30 May 2023 at 20:= 56, John Nielsen <lists@jnielsen.net> wrote:
> On May 30, 2023, at 8:02 PM, Adrian Chadd <adrian@freebsd.org&= gt; wrote:
>=C2=A0
> Err, if it's coming up w/= that MAC then it's not finding and attaching right to the OTP/EEPROM c= alibration information. That's the big red flag that it in general won&= #39;t work correctly.
>=C2=A0
> Can you provide th= e rest of the ath_hal messages? I'd like to see what it's saying du= ring boot around it checking the EEPROM/OTP contents. It's possible the= re's some work around required for this NIC.

He speaks! Thanks f= or taking the time. I just realized that ath_hal_printf doesn=E2=80=99t pre= pend =E2=80=9Cath%d=E2=80=9D so I=E2=80=99ve been missing those messages wh= en grep-ing. Here=E2=80=99s the whole snippet:

ath0: <Atheros AR9= 46x/AR948x> mem 0xf7a00000-0xf7a7ffff at device 0.0 on pci4
ar9300_fl= ash_map: unimplemented for now
Restoring Cal data from DRAM
Restoring= Cal data from EEPROM
Restoring Cal data from Flash
Restoring Cal dat= a from Flash
Restoring Cal data from OTP
ar9300_eeprom_restore_intern= al[4338] No vaid CAL, calling default template
ar9300_hw_attach: ar9300_= eeprom_attach returned 0

Yeah, this bit= right here is the problem. It's not finding a valid calibration.
=

oh err, is there a wifi enable/disable switch o= r something? maybe it's asserted and somehow it's mucking up the NI= C?

There is a physical switch and it=E2=80= =99s in the =E2=80=9Cenable=E2=80=9D position.

=C2=A0I wonder wha= t ath9k is doing here? Is there some weird pci based workaround/flag for th= e given NIC PCI id?

That was t= he first breadcrumb BZ threw me but I can=E2=80=99t find anything. There ar= e some .driver_data hints for adjacent subdevice IDs but none for this one = (Dell 0x020d) in either FreeBSD or Linux that I could find.

<= /div>
The kernel on the Arch Linux USB I have handy doesn=E2=80=99t app= ear to have been compiled with CONFIG_ATH_DEBUG but here=E2=80=99s what it = has in /sys/kernel/ieee80211/phy0/ath9k/base_eeprom:
=C2=A0 = =C2=A0 =C2=A0 EEPROM Version : =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A02
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 RegDomain1 : =C2=A0 =C2=A0 =C2=A0 =C2= =A0108
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 RegDomain2 : =C2=A0 =C2= =A0 =C2=A0 =C2=A0 31
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0TX Mask : =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A03
=C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0RX Mask : =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A03
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Allow 5GHz : =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A01
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 A= llow 2GHz : =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A01
=C2=A0 =C2=A0Disa= ble 2GHz HT20 : =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A00
=C2=A0 =C2=A0= Disable 2GHz HT40 : =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A00
=C2=A0 = =C2=A0Disable 5Ghz HT20 : =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A00
=C2= =A0 =C2=A0Disable 5Ghz HT40 : =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A00
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Big Endian : =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A00
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0RF Silent : = =C2=A0 =C2=A0 =C2=A0 =C2=A0 45
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0BT option : =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A00
=C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 Device Cap : =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A00
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Device Type : =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A05
=C2=A0 Power Table Offset : =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A00
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Tuning Caps1 : =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A00
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Tuni= ng Caps2 : =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A00
=C2=A0Enable Tx Te= mp Comp : =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A01
=C2=A0Enable Tx Vol= t Comp : =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A00
=C2=A0 =C2=A0Enable = fast clock : =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A01
=C2=A0 =C2=A0 = =C2=A0Enable doubling : =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A01
=C2= =A0 Internal regulator : =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A00
=C2= =A0 =C2=A0 =C2=A0 =C2=A0 Enable Paprd : =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A00=
=C2=A0 =C2=A0 =C2=A0Driver Strength : =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A00
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Quick Drop : =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A01
=C2=A0 =C2=A0Chain mask Reduce := =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A00
=C2=A0 =C2=A0Write enable Gp= io : =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A06
=C2=A0 =C2=A0WLAN Disabl= e Gpio : =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A00
=C2=A0 =C2=A0 =C2=A0= =C2=A0WLAN LED Gpio : =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A08
=C2=A0= Rx Band Select Gpio : =C2=A0 =C2=A0 =C2=A0 =C2=A0255
=C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Tx Gain : =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A01
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Rx Gain = : =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A03
=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 SW Reg : =C2=A0303972983
=C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 MacAddress : 44:39:c4:5b:44:4a

I= t also has some calibration and other data in modal_eeprom.=C2=A0

There is this commit in ath9k which mentions an alternativ= e EEPROM address, but I=E2=80=99m not sure if that=E2=80=99s relevant. From= what I can tell the probe should succeed at the normal base_address 0x3ff = instead of needing to try the =E2=80=9C4k=E2=80=9D one 0xfff.

Yeah i'= ;d try that. It'd be nice if I knew that the NIC used OTP or EEPROM tho= ugh.

There's known issues with all the Atheros= chips (sigh) with how the EEPROM and PCIe bus reset .. interact.
(If the bus reset is too short then the EEPROM state machine gets stuck an= d nothing gets read.) It makes debugging this hard because the NIC itself w= ill work in another device fine, because it's the BIOS/ACPI code. :(


-adrian


=
--000000000000d21add05fcf66f78-- From nobody Wed May 31 05:31:02 2023 X-Original-To: freebsd-wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QWHtW2hJsz4Y5VF for ; Wed, 31 May 2023 05:31:15 +0000 (UTC) (envelope-from gshapiro@freebsd.org) Received: from z.gshapiro.net (z.gshapiro.net [IPv6:2600:1f18:408a:c610::100]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.gshapiro.net", Issuer "GoGetSSL RSA DV CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QWHtV4bhrz4HkF for ; Wed, 31 May 2023 05:31:14 +0000 (UTC) (envelope-from gshapiro@freebsd.org) Authentication-Results: mx1.freebsd.org; dkim=none; spf=softfail (mx1.freebsd.org: 2600:1f18:408a:c610::100 is neither permitted nor denied by domain of gshapiro@freebsd.org) smtp.mailfrom=gshapiro@freebsd.org; dmarc=none Received: from zim.gshapiro.net (zim.gshapiro.net [IPv6:2001:bc8:2e97:100:0:0:0:100]) by z.gshapiro.net (8.16.1/8.16.1) with ESMTPS id 34V5V7Rx069876 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=FAIL) for ; Wed, 31 May 2023 05:31:07 GMT (envelope-from gshapiro@freebsd.org) Received: from thornystick.local ([IPv6:2601:647:5d00:1ac0:e0ea:b362:685f:a728]) (authenticated bits=0) by zim.gshapiro.net (8.17.1.27/8.17.1.27) with ESMTPSA id 34V5V2XA032877 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Wed, 31 May 2023 05:31:05 GMT Date: Tue, 30 May 2023 22:31:02 -0700 From: Gregory Shapiro To: freebsd-wireless@freebsd.org Subject: Intel NUC iwm0 (Intel Dual Band Wireless AC 8260) supported? Message-ID: List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Spamd-Result: default: False [-1.35 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; NEURAL_HAM_LONG(-0.75)[-0.746]; MID_RHS_NOT_FQDN(0.50)[]; MIME_GOOD(-0.10)[text/plain]; ASN(0.00)[asn:14618, ipnet:2600:1f18:4000::/35, country:US]; DMARC_NA(0.00)[freebsd.org]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-wireless@freebsd.org]; ARC_NA(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; RCPT_COUNT_ONE(0.00)[1]; FROM_HAS_DN(0.00)[]; FREEFALL_USER(0.00)[gshapiro]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_TLS_ALL(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-wireless@freebsd.org]; R_SPF_SOFTFAIL(0.00)[~all:c]; TO_DOM_EQ_FROM_DOM(0.00)[] X-Rspamd-Queue-Id: 4QWHtV4bhrz4HkF X-Spamd-Bar: - X-ThisMailContainsUnwantedMimeParts: N I recently obtained an Intel NUC and, of course, installed FreeBSD on it. Everything that I need works except for the built-in wireless. Though it shows at boot (as iwm0), after booting, it doesn't show up as a network interface. I tried installing the iwmbt-firmware-20221109 port and using it, but it didn't help (successfully applied, but no change). Is there something I am missing or is this particular device not supported? # iwmbtfw -I -d ugen0.3 -f /usr/local/share/iwmbt-firmware iwmbt_is_8260: found 8260/8265 main: Firmware has already been downloaded main: Firmware download is successful! pciconf sees: # pciconf -l | grep iwm iwm0@pci0:1:0:0: class=0x028000 rev=0x3a hdr=0x00 vendor=0x8086 device=0x24f3 subvendor=0x8086 subdevice=0x9010 # pciconf -lv pci0:1:0:0 iwm0@pci0:1:0:0: class=0x028000 rev=0x3a hdr=0x00 vendor=0x8086 device=0x24f3 subvendor=0x8086 subdevice=0x9010 vendor = 'Intel Corporation' device = 'Wireless 8260' class = network Kernel modules are autoloaded for it: # kldstat Id Refs Address Size Name 1 75 0xffffffff80200000 1f3e2d0 kernel 2 1 0xffffffff8213f000 a4a0 cryptodev.ko 3 1 0xffffffff8214a000 59dfa8 zfs.ko 4 1 0xffffffff83010000 d9b0 geom_eli.ko 5 1 0xffffffff8301e000 3250 ichsmb.ko 6 1 0xffffffff83022000 2180 smbus.ko 7 1 0xffffffff83025000 880c8 if_iwlwifi.ko 8 1 0xffffffff830ae000 17310 if_iwm.ko 9 1 0xffffffff830c6000 2110 pchtherm.ko 10 1 0xffffffff83200000 207d78 iwm8000Cfw.ko 11 1 0xffffffff830c9000 3340 uhid.ko 12 1 0xffffffff830cd000 3380 usbhid.ko 13 1 0xffffffff830d1000 31f8 hidbus.ko 14 1 0xffffffff830d5000 3320 wmt.ko 15 1 0xffffffff830d9000 4d00 ng_ubt.ko 16 6 0xffffffff830de000 aac8 netgraph.ko 17 2 0xffffffff830e9000 a238 ng_hci.ko 18 4 0xffffffff830f4000 25a8 ng_bluetooth.ko 19 1 0xffffffff830f7000 e250 ng_l2cap.ko 20 1 0xffffffff83106000 1bee8 ng_btsocket.ko 21 1 0xffffffff83122000 39c0 ng_socket.ko 22 1 0xffffffff83126000 27190 ipfw.ko 23 1 0xffffffff8314e000 2a08 mac_ntpd.ko Boot messages: FreeBSD 13.2-RELEASE releng/13.2-n254617-525ecfdad597 GENERIC amd64 ... ACPI APIC Table: ... pci1: on pcib1 ... pci1: at device 0.0 (no driver attached) ... Intel(R) Wireless WiFi based driver for FreeBSD pchtherm0: mem 0xdf250000-0xdf250fff irq 18 at device 20.2 on pci0 ichsmb0: port 0xf040-0xf05f mem 0xdf24a000-0xdf24a0ff irq 16 at device 31.4 on pci0 smbus0: on ichsmb0 iwm0: mem 0xdf100000-0xdf101fff irq 16 at device 0.0 on pci1 iwm0: hw rev 0x200, fw ver 22.361476.0, address a0:c5:89:17:cc:f3 ... ubt0 on uhub0 ubt0: on usbus0 WARNING: attempt to domain_add(bluetooth) after domainfinalize() WARNING: attempt to domain_add(netgraph) after domainfinalize() ... From nobody Wed May 31 05:42:02 2023 X-Original-To: freebsd-wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QWJ7B1wvlz4Y6Dr for ; Wed, 31 May 2023 05:42:14 +0000 (UTC) (envelope-from lwhsu@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QWJ7B1Rrvz4Jl3; Wed, 31 May 2023 05:42:14 +0000 (UTC) (envelope-from lwhsu@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1685511734; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=wMMRXviePnGfZw3k1LJuqmwEJM1t93GEU3Z315TluvU=; b=Ie3U1xbEwIK7rrpy5f8u6A3WqWwffeLOxHcgqrNGV6H2pSYXxBCDkAxAIJVMruuA/abG1P 4I0NzsYV+0L309imoNVriHAqm2uTx5DBvqT97+vKvIZX7ev6ACDY2oh171aWsVD655m5zc bD6LvV4zLYt0sF37tcoV61Q5tV/fOboXfO+2LlTTHJek/rsMSnMMurY0ksKOLd0nnM4Xew 37xEWB7e6MYgMlh8EF3EDs8PBl2Hy3ifsijE+S2bxE8PnimDjbecOvY4nESIvO7zqRH7Ya 0ww7mz/zO2Dz5GVmTFvghQLuhftKAEY8f3yVlcFOjL2pkVaLI/78588GGHLB0A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1685511734; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=wMMRXviePnGfZw3k1LJuqmwEJM1t93GEU3Z315TluvU=; b=rD06ivw1cx5n+Qe2gHAfwFE6lm79uBMd8EdegUI0iu8lNoU4vuEeeyFqr2b9Do03Shc97Y 2VOZVRBjju9O92yw0tN0lFQ79cb+EmnLhE9HU01sjR2CIZboYzWwdABJ7TYbjL3frHftCJ ORwcQJ/doxLM7yMn8C9zFh223JVi9qNWPnXL+MUll4d7XxxwhTC81FSAdYoIXRqFE6VEl6 5HzFI+6cOsc0O9lxew1fxJYvCsmHZUDwo/9zA1w2OeDcQFRMo0QTTMenNIUel4FOfgqX9b MexLS1UI9vSXmFFc5RmkC/nFp4yGQAASmxE9uVIntUo2E1jd0RItjcDHBMmlhg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1685511734; a=rsa-sha256; cv=none; b=FauMrqYYKqJqyHWHS9uWVc2W3Ihn+UW8X5yI7npnjVAR7HzMqFPsFB7BxnC3VRJemhJMRZ Gi0BrhoX9Py7ARdUckoimoL2ne9+Q68yRDB3BWCEqiHnNP+EuVZA2kyBr5SV5f+tAc/OOP jYSPVekCuYRRwBIRNWq2BMYo0/GoYejWWBva/xFmnQZZbjItNxsFlqQ/NKNSth6w6weX/u cjsi8y61RZRww7pZr9kwNmcazj/++F/a8AMqBYZlMz0VwEnhmVZZ+9B2MTB84AdzSoQHwh mZI+8mL2kzZDGbZaEqC8QtKWQwyS4iAxzYYR/vsf9qZK67FHaBbANKPIlGwxdQ== Received: from mail-qv1-f46.google.com (mail-qv1-f46.google.com [209.85.219.46]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) (Authenticated sender: lwhsu/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4QWJ7B0W8dzxmX; Wed, 31 May 2023 05:42:14 +0000 (UTC) (envelope-from lwhsu@freebsd.org) Received: by mail-qv1-f46.google.com with SMTP id 6a1803df08f44-6260f03b76dso24630986d6.1; Tue, 30 May 2023 22:42:14 -0700 (PDT) X-Gm-Message-State: AC+VfDzl+zw2y6QgMlNRQb3jCqwjBYMOUZML4Oq/magIJy6s6ko54Hpn BXVxUfOq4SjWQka1hsFOSt0sOWfeWKd3hSQlP7I= X-Google-Smtp-Source: ACHHUZ4ArFMFFFkpg/IFmhTURuzLvKCJKkGxbxW6pVV8SYsuer32bnHLF4yDHylLCTJL0+p/ialbiGnHambIK5BuMfQ= X-Received: by 2002:a05:6214:2526:b0:61a:281b:9a4b with SMTP id gg6-20020a056214252600b0061a281b9a4bmr5089733qvb.0.1685511733633; Tue, 30 May 2023 22:42:13 -0700 (PDT) List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Li-Wen Hsu Date: Wed, 31 May 2023 13:42:02 +0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Intel NUC iwm0 (Intel Dual Band Wireless AC 8260) supported? To: Gregory Shapiro Cc: freebsd-wireless@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-ThisMailContainsUnwantedMimeParts: N On Wed, May 31, 2023 at 1:31=E2=80=AFPM Gregory Shapiro wrote: > > I recently obtained an Intel NUC and, of course, installed FreeBSD on it.= Everything that I need works except for the built-in wireless. Though it= shows at boot (as iwm0), after booting, it doesn't show up as a network in= terface. I tried installing the iwmbt-firmware-20221109 port and using it,= but it didn't help (successfully applied, but no change). Is there someth= ing I am missing or is this particular device not supported? > > # iwmbtfw -I -d ugen0.3 -f /usr/local/share/iwmbt-firmware > iwmbt_is_8260: found 8260/8265 > main: Firmware has already been downloaded > main: Firmware download is successful! > > pciconf sees: > > # pciconf -l | grep iwm > iwm0@pci0:1:0:0: class=3D0x028000 rev=3D0x3a hdr=3D0x00 vendor=3D0= x8086 device=3D0x24f3 subvendor=3D0x8086 subdevice=3D0x9010 > # pciconf -lv pci0:1:0:0 > iwm0@pci0:1:0:0: class=3D0x028000 rev=3D0x3a hdr=3D0x00 vendor=3D0= x8086 device=3D0x24f3 subvendor=3D0x8086 subdevice=3D0x9010 > vendor =3D 'Intel Corporation' > device =3D 'Wireless 8260' > class =3D network > > Kernel modules are autoloaded for it: > > # kldstat > Id Refs Address Size Name > 1 75 0xffffffff80200000 1f3e2d0 kernel > 2 1 0xffffffff8213f000 a4a0 cryptodev.ko > 3 1 0xffffffff8214a000 59dfa8 zfs.ko > 4 1 0xffffffff83010000 d9b0 geom_eli.ko > 5 1 0xffffffff8301e000 3250 ichsmb.ko > 6 1 0xffffffff83022000 2180 smbus.ko > 7 1 0xffffffff83025000 880c8 if_iwlwifi.ko > 8 1 0xffffffff830ae000 17310 if_iwm.ko > 9 1 0xffffffff830c6000 2110 pchtherm.ko > 10 1 0xffffffff83200000 207d78 iwm8000Cfw.ko > 11 1 0xffffffff830c9000 3340 uhid.ko > 12 1 0xffffffff830cd000 3380 usbhid.ko > 13 1 0xffffffff830d1000 31f8 hidbus.ko > 14 1 0xffffffff830d5000 3320 wmt.ko > 15 1 0xffffffff830d9000 4d00 ng_ubt.ko > 16 6 0xffffffff830de000 aac8 netgraph.ko > 17 2 0xffffffff830e9000 a238 ng_hci.ko > 18 4 0xffffffff830f4000 25a8 ng_bluetooth.ko > 19 1 0xffffffff830f7000 e250 ng_l2cap.ko > 20 1 0xffffffff83106000 1bee8 ng_btsocket.ko > 21 1 0xffffffff83122000 39c0 ng_socket.ko > 22 1 0xffffffff83126000 27190 ipfw.ko > 23 1 0xffffffff8314e000 2a08 mac_ntpd.ko > > > Boot messages: > > FreeBSD 13.2-RELEASE releng/13.2-n254617-525ecfdad597 GENERIC amd64 > ... > ACPI APIC Table: > ... > pci1: on pcib1 > ... > pci1: at device 0.0 (no driver attached) > ... > Intel(R) Wireless WiFi based driver for FreeBSD > pchtherm0: mem 0xdf250000-0xdf250fff irq = 18 at device 20.2 on pci0 > ichsmb0: port 0xf040-0xf05f mem= 0xdf24a000-0xdf24a0ff irq 16 at device 31.4 on pci0 > smbus0: on ichsmb0 > iwm0: mem 0xdf100000-0xdf101fff irq= 16 at device 0.0 on pci1 > iwm0: hw rev 0x200, fw ver 22.361476.0, address a0:c5:89:17:cc:f3 > ... > ubt0 on uhub0 > ubt0: = on usbus0 > WARNING: attempt to domain_add(bluetooth) after domainfinalize() > WARNING: attempt to domain_add(netgraph) after domainfinalize() > ... > > > iwmbt-firmware is for bluetooth. I guess what you want is 802.11 wireless. The firmware of iwm(4) is in the base. From your chip (8260) and the output of kldstate, It seems using iwm8000Cfw.ko and it's already loaded. For the interface, have you tried to create a vap (wlan) from the parent device (iwm)? Try: `ifconfig wlan create wlandev iwm0` BTW, You can also try the newer iwlwifi(4) Best, Li-Wen From nobody Wed May 31 06:17:56 2023 X-Original-To: freebsd-wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QWJwV5zrqz4Y89y for ; Wed, 31 May 2023 06:18:02 +0000 (UTC) (envelope-from gshapiro@freebsd.org) Received: from z.gshapiro.net (z.gshapiro.net [IPv6:2600:1f18:408a:c610::100]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.gshapiro.net", Issuer "GoGetSSL RSA DV CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QWJwV5GwWz4MSQ; Wed, 31 May 2023 06:18:02 +0000 (UTC) (envelope-from gshapiro@freebsd.org) Authentication-Results: mx1.freebsd.org; none Received: from zim.gshapiro.net (zim.gshapiro.net [IPv6:2001:bc8:2e97:100:0:0:0:100]) by z.gshapiro.net (8.16.1/8.16.1) with ESMTPS id 34V6I0XY069942 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=FAIL); Wed, 31 May 2023 06:18:01 GMT (envelope-from gshapiro@freebsd.org) Received: from thornystick.local ([98.51.131.164]) (authenticated bits=0) by zim.gshapiro.net (8.17.1.27/8.17.1.27) with ESMTPSA id 34V6HuWr033196 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 31 May 2023 06:17:59 GMT Date: Tue, 30 May 2023 23:17:56 -0700 From: Gregory Shapiro To: Li-Wen Hsu Cc: freebsd-wireless@freebsd.org Subject: Re: Intel NUC iwm0 (Intel Dual Band Wireless AC 8260) supported? Message-ID: References: List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4QWJwV5GwWz4MSQ X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:14618, ipnet:2600:1f18:4000::/35, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N > For the interface, have you tried to create a vap (wlan) from the > parent device (iwm)? > Try: `ifconfig wlan create wlandev iwm0` Thank you! That was the magic I was missing. From nobody Wed May 31 19:52:55 2023 X-Original-To: wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QWg1K2sxLz4XW2l for ; Wed, 31 May 2023 19:53:25 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from webmail5.jnielsen.net (webmail5.jnielsen.net [IPv6:2607:f170:34:11::b0]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.freebsdsolutions.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QWg1K01bjz3hGf; Wed, 31 May 2023 19:53:24 +0000 (UTC) (envelope-from lists@jnielsen.net) Authentication-Results: mx1.freebsd.org; none Received: from smtpclient.apple (166-70-14-17.xmission.com [166.70.14.17] (may be forged)) (authenticated bits=0) by webmail5.jnielsen.net (8.17.1/8.17.1) with ESMTPSA id 34VJrBcR032745 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 31 May 2023 13:53:14 -0600 (MDT) (envelope-from lists@jnielsen.net) X-Authentication-Warning: webmail5.jnielsen.net: Host 166-70-14-17.xmission.com [166.70.14.17] (may be forged) claimed to be smtpclient.apple From: John Nielsen Message-Id: <5264D290-EB82-4D24-A812-85E3E6B5C88E@jnielsen.net> Content-Type: multipart/alternative; boundary="Apple-Mail=_C8BA0CC5-1187-4926-8F88-FF63B1972285" List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\)) Subject: Re: Help me grok the ath(4) device attach code Date: Wed, 31 May 2023 13:52:55 -0600 In-Reply-To: Cc: "Bjoern A. Zeeb" , "wireless@freebsd.org" To: Adrian Chadd References: <49AEA1CB-FA85-432F-89D7-8C49B5F3A344@jnielsen.net> <85BF3AB2-2EBF-4398-A507-ABA35505A56C@jnielsen.net> X-Mailer: Apple Mail (2.3731.600.7) X-Rspamd-Queue-Id: 4QWg1K01bjz3hGf X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:6364, ipnet:2607:f170:30::/44, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --Apple-Mail=_C8BA0CC5-1187-4926-8F88-FF63B1972285 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On May 30, 2023, at 11:17 PM, Adrian Chadd wrote: >=20 > On Tue, 30 May 2023 at 22:12, John Nielsen > wrote: >>> On May 30, 2023, at 10:56 PM, Adrian Chadd > wrote: >>>=20 >>> On Tue, 30 May 2023 at 20:56, John Nielsen > wrote: >>>> > On May 30, 2023, at 8:02 PM, Adrian Chadd > wrote: >>>> >=20 >>>> > Err, if it's coming up w/ that MAC then it's not finding and = attaching right to the OTP/EEPROM calibration information. That's the = big red flag that it in general won't work correctly. >>>> >=20 >>>> > Can you provide the rest of the ath_hal messages? I'd like to see = what it's saying during boot around it checking the EEPROM/OTP contents. = It's possible there's some work around required for this NIC. >>>>=20 >>>> He speaks! Thanks for taking the time. I just realized that = ath_hal_printf doesn=E2=80=99t prepend =E2=80=9Cath%d=E2=80=9D so I=E2=80=99= ve been missing those messages when grep-ing. Here=E2=80=99s the whole = snippet: >>>>=20 >>>> ath0: mem 0xf7a00000-0xf7a7ffff at device = 0.0 on pci4 >>>> ar9300_flash_map: unimplemented for now >>>> Restoring Cal data from DRAM >>>> Restoring Cal data from EEPROM >>>> Restoring Cal data from Flash >>>> Restoring Cal data from Flash >>>> Restoring Cal data from OTP >>>> ar9300_eeprom_restore_internal[4338] No vaid CAL, calling default = template >>>> ar9300_hw_attach: ar9300_eeprom_attach returned 0 >>>=20 >>> Yeah, this bit right here is the problem. It's not finding a valid = calibration. >>=20 >>> oh err, is there a wifi enable/disable switch or something? maybe = it's asserted and somehow it's mucking up the NIC? >>=20 >> There is a physical switch and it=E2=80=99s in the =E2=80=9Cenable=E2=80= =9D position. >>=20 >>> I wonder what ath9k is doing here? Is there some weird pci based = workaround/flag for the given NIC PCI id? >>=20 >> That was the first breadcrumb BZ threw me but I can=E2=80=99t find = anything. There are some .driver_data hints for adjacent subdevice IDs = but none for this one (Dell 0x020d) in either FreeBSD or Linux that I = could find. >>=20 >> The kernel on the Arch Linux USB I have handy doesn=E2=80=99t appear = to have been compiled with CONFIG_ATH_DEBUG but here=E2=80=99s what it = has in /sys/kernel/ieee80211/phy0/ath9k/base_eeprom: >> EEPROM Version : 2 >> RegDomain1 : 108 >> RegDomain2 : 31 >> TX Mask : 3 >> RX Mask : 3 >> Allow 5GHz : 1 >> Allow 2GHz : 1 >> Disable 2GHz HT20 : 0 >> Disable 2GHz HT40 : 0 >> Disable 5Ghz HT20 : 0 >> Disable 5Ghz HT40 : 0 >> Big Endian : 0 >> RF Silent : 45 >> BT option : 0 >> Device Cap : 0 >> Device Type : 5 >> Power Table Offset : 0 >> Tuning Caps1 : 0 >> Tuning Caps2 : 0 >> Enable Tx Temp Comp : 1 >> Enable Tx Volt Comp : 0 >> Enable fast clock : 1 >> Enable doubling : 1 >> Internal regulator : 0 >> Enable Paprd : 0 >> Driver Strength : 0 >> Quick Drop : 1 >> Chain mask Reduce : 0 >> Write enable Gpio : 6 >> WLAN Disable Gpio : 0 >> WLAN LED Gpio : 8 >> Rx Band Select Gpio : 255 >> Tx Gain : 1 >> Rx Gain : 3 >> SW Reg : 303972983 >> MacAddress : 44:39:c4:5b:44:4a >>=20 >> It also has some calibration and other data in modal_eeprom.=20 >>=20 >> There is this commit in ath9k which mentions an alternative EEPROM = address, but I=E2=80=99m not sure if that=E2=80=99s relevant. =46rom = what I can tell the probe should succeed at the normal base_address = 0x3ff instead of needing to try the =E2=80=9C4k=E2=80=9D one 0xfff. >> = https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/commit/drive= rs/net/wireless/ath/ath9k?id=3D528782ecf59f7bab2f1368628a479f49be59b512 >=20 > Yeah i'd try that. It'd be nice if I knew that the NIC used OTP or = EEPROM though. >=20 > There's known issues with all the Atheros chips (sigh) with how the = EEPROM and PCIe bus reset .. interact. > (If the bus reset is too short then the EEPROM state machine gets = stuck and nothing gets read.) It makes debugging this hard because the = NIC itself will work in another device fine, because it's the BIOS/ACPI = code. :( The 4k EEPROM read didn=E2=80=99t work. But I did notice that where it = says it=E2=80=99s restoring Cal data from OTP it actually just does an = EEPROM read again. Shouldn=E2=80=99t this line be a call to = ar9300_otp_read() instead of ar9300_eeprom_restore_internal_address()? = https://cgit.freebsd.org/src/tree/sys/contrib/dev/ath/ath_hal/ar9300/ar930= 0_eeprom.c#n4292 Otherwise it doesn=E2=80=99t use the 0x14000 (0x30000 for some cards) = OTP offset as a starting point. -John --Apple-Mail=_C8BA0CC5-1187-4926-8F88-FF63B1972285 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
On May 30, 2023, = at 11:17 PM, Adrian Chadd <adrian@freebsd.org> = wrote:

On Tue, 30 May 2023 at 22:12, John = Nielsen <lists@jnielsen.net> = wrote:
On May 30, 2023, at 10:56 PM, Adrian Chadd <adrian@freebsd.org> wrote:

On Tue, 30 May = 2023 at 20:56, John Nielsen <lists@jnielsen.net> wrote:
> On May 30, 2023, at 8:02 = PM, Adrian Chadd <adrian@freebsd.org> = wrote:
> 
> Err, if it's coming up w/ that = MAC then it's not finding and attaching right to the OTP/EEPROM = calibration information. That's the big red flag that it in general = won't work correctly.
> 
> Can you provide = the rest of the ath_hal messages? I'd like to see what it's saying = during boot around it checking the EEPROM/OTP contents. It's possible = there's some work around required for this NIC.

He speaks! Thanks = for taking the time. I just realized that ath_hal_printf doesn=E2=80=99t = prepend =E2=80=9Cath%d=E2=80=9D so I=E2=80=99ve been missing those = messages when grep-ing. Here=E2=80=99s the whole snippet:

ath0: = <Atheros AR946x/AR948x> mem 0xf7a00000-0xf7a7ffff at device 0.0 on = pci4
ar9300_flash_map: unimplemented for now
Restoring Cal data = from DRAM
Restoring Cal data from EEPROM
Restoring Cal data from = Flash
Restoring Cal data from Flash
Restoring Cal data from = OTP
ar9300_eeprom_restore_internal[4338] No vaid CAL, calling default = template
ar9300_hw_attach: ar9300_eeprom_attach returned = 0

Yeah, this bit right here is the = problem. It's not finding a valid = calibration.

oh err, is there a wifi enable/disable = switch or something? maybe it's asserted and somehow it's mucking up the = NIC?

There is a physical switch and = it=E2=80=99s in the =E2=80=9Cenable=E2=80=9D = position.

 I wonder what ath9k is doing here? Is there = some weird pci based workaround/flag for the given NIC PCI = id?

That was the first = breadcrumb BZ threw me but I can=E2=80=99t find anything. There are some = .driver_data hints for adjacent subdevice IDs but none for this one = (Dell 0x020d) in either FreeBSD or Linux that I could = find.

The kernel on the Arch Linux USB I have = handy doesn=E2=80=99t appear to have been compiled with CONFIG_ATH_DEBUG = but here=E2=80=99s what it has in = /sys/kernel/ieee80211/phy0/ath9k/base_eeprom:
  =     EEPROM Version :         =  2
          RegDomain1 :   =      108
          = RegDomain2 :         31
    =          TX Mask :         =  3
             RX = Mask :          3
    =       Allow 5GHz :         =  1
          Allow 2GHz :   =        1
   Disable 2GHz HT20 : =          0
   Disable 2GHz = HT40 :          0
  =  Disable 5Ghz HT20 :         =  0
   Disable 5Ghz HT40 :       =    0
          Big Endian : =          0
      =      RF Silent :         = 45
           BT option :   =        0
        =   Device Cap :          0
  =        Device Type :         =  5
  Power Table Offset :       =    0
        Tuning Caps1 : =          0
      =   Tuning Caps2 :         =  0
 Enable Tx Temp Comp :       =    1
 Enable Tx Volt Comp :     =      0
   Enable fast clock :   =        1
     Enable = doubling :          1
  Internal = regulator :          0
    =     Enable Paprd :         =  0
     Driver Strength :     =      0
          Quick = Drop :          1
   Chain = mask Reduce :          0
  =  Write enable Gpio :         =  6
   WLAN Disable Gpio :       =    0
       WLAN LED Gpio : =          8
 Rx Band Select Gpio = :        255
        =      Tx Gain :         =  1
             Rx = Gain :          3
    =           SW Reg : =  303972983
          MacAddress = : 44:39:c4:5b:44:4a

It also has some = calibration and other data in = modal_eeprom. 

There is this commit in = ath9k which mentions an alternative EEPROM address, but I=E2=80=99m not = sure if that=E2=80=99s relevant. =46rom what I can tell the probe should = succeed at the normal base_address 0x3ff instead of needing to try the = =E2=80=9C4k=E2=80=9D one 0xfff.

Yeah i'd = try that. It'd be nice if I knew that the NIC used OTP or EEPROM = though.

There's known issues with all the = Atheros chips (sigh) with how the EEPROM and PCIe bus reset .. = interact.
(If the bus reset is too short then the EEPROM state = machine gets stuck and nothing gets read.) It makes debugging this hard = because the NIC itself will work in another device fine, because it's = the BIOS/ACPI code. = :(

The 4k EEPROM read = didn=E2=80=99t work. But I did notice that where it says it=E2=80=99s = restoring Cal data from OTP it actually just does an EEPROM read again. = Shouldn=E2=80=99t this line be a call to ar9300_otp_read() instead of = ar9300_eeprom_restore_internal_address()?

https:/= /cgit.freebsd.org/src/tree/sys/contrib/dev/ath/ath_hal/ar9300/ar9300_eepro= m.c#n4292

Otherwise it doesn=E2=80=99t use the = 0x14000 (0x30000 for some cards) OTP offset as a starting = point.

-John

= --Apple-Mail=_C8BA0CC5-1187-4926-8F88-FF63B1972285--