From owner-freebsd-wireless@FreeBSD.ORG Tue Dec 4 07:51:12 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E942DF90 for ; Tue, 4 Dec 2012 07:51:12 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 728538FC13 for ; Tue, 4 Dec 2012 07:51:12 +0000 (UTC) Received: by mail-we0-f182.google.com with SMTP id u54so1788570wey.13 for ; Mon, 03 Dec 2012 23:51:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=ty2TKVkz3zL7Lx/9tl9qvxR6iZfawgttesd/0Odcydc=; b=fwBTGJzgBC589fZvY6QP07byMsZSmiDmIEplZG4AkXIIFCtMWhUQbVGxkFuogDYgJc wn+kode5FvO1ILe3AV+OdQu5p90KaLLvMfUpodO+DCa7wCPyLBhVr4ccZov6byxqfkk/ 6v54iEYcPVcBoE0hEP+r5HwDNhxlAzkWwFNw3oF3RDpm3VLNEs2Z3KcrqU2VfJEGmUeN evmKbO/60nHArAKrD8nUeSncGEACarWwMmziYdbgSqiXZcmBp/XpI7BSs3MDiUQNc2tU TEUBnlXEgU/gZ7NGUieCTju1ii5O3CuPZ8+LgyZ6kzs1NM/RRpDFhXoKbLZvxvnsDSeO YFDw== MIME-Version: 1.0 Received: by 10.180.88.71 with SMTP id be7mr2559291wib.17.1354607471132; Mon, 03 Dec 2012 23:51:11 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Mon, 3 Dec 2012 23:51:10 -0800 (PST) In-Reply-To: <978297250.20121203222002@takeda.tk> References: <188790082.20121202234216@takeda.tk> <978297250.20121203222002@takeda.tk> Date: Mon, 3 Dec 2012 23:51:10 -0800 X-Google-Sender-Auth: Vx8gqU5kx56RJPgxl-OZuHvCfxU Message-ID: Subject: Re: Problem with Atheros card, regression? Layer 8 problem? From: Adrian Chadd To: Derek Kulinski Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Dec 2012 07:51:13 -0000 That's really good to know! Thanks! Adrian On 3 December 2012 22:20, Derek Kulinski wrote: > Hello Adrian, > > So I figured the problem out. > > This is how it went. I booted OpenSuSE and couldn't find the device as > well... > > At that point I was sure that the problem is with my PC. I decided to > install the card in a PC that is running Windows. After start it > recognized new hardware but I did not have drivers, looking at > hardware information it showed correct values. > > I then put back the card to the FreeBSD machine and started SuSE. The > card became correctly recognized by Linux, I booted FreeBSD and the > card was no longer visible (though this time devid value was correct), > switched to Linux and Linux did not see it as well. At that point I > took isopropyl alcohol and cleaned the connection, plugged it back and > FreeBSD is seeing it now. > > That card was in that old PC for many years, so probably the > connection oxidized (or maybe just dirt built up - I'm no chemist). > > In any case it looks like it was a layer 8 problem after all. I'm > sorry for bugging you. > > Thanks, > Derek > > Monday, December 3, 2012, 12:26:06 AM, you wrote: > >> Hi, > >> If it's not recognising the card then it's either a whacky PCI bus >> code problem, or the device is just plainly not being seen by the >> motherboard or BIOS. > >> Can you try booting Linux and see if it sees the PCI device? > > >> Adrian > > >> On 2 December 2012 23:42, Derek Kulinski wrote: >>> Hello Adrian, >>> >>> I'm having some issues with a NIC card that worked fine in another >>> FreeBSD box (very old hardware - Celeron 366MHz :) that was running >>> version 8. >>> >>> The box died, and I decided to just move the card to recent machine >>> (running FreeBSD 9.1 RC3). >>> >>> Unfortunately the machine does not recognize the card, I asked on the >>> forum, and person trying to help me thinks that perhaps it is a bug: >>> >>> http://forums.freebsd.org/showthread.php?t=36099 >>> >>> I thought initially that I couldn't see the card even in pciconf, but >>> seems like the card probably is: >>> >>> none3@pci0:4:0:0: class=0x020000 card=0x3a131186 chip=0x00130000 rev=0x01 hdr=0x00 >>> class = network >>> subclass = ethernet >>> cap 01[44] = powerspec 2 supports D0 D3 current D0 >>> >>> I tried to follow his advice and changed value of AR5212_DEVID to >>> 0x0000 but that did not seem to do anything (I recompiled if_ath and >>> if_ath_pci). >>> >>> So I went further and modified ar5212Probe() >>> and put a printf() statement there (as a first instruction). >>> Unfortunately it doesn't look that the statement was ever called, or >>> at least I did not see anything in the logs. >>> >>> I decided to not file PR because there is still a possibility I might >>> be doing something wrong. I configured that old machine a while ago >>> and I no longer have access to it's contents :/ >>> >>> The old machine was running i386 kernel, the new one is running amd64. >>> The new one has Gigabyte GA-H77-DS3H motherboard and the NIC in >>> question is D-Link, I belive DWL-G520. >>> -- >>> Best regards, >>> Derek mailto:takeda@takeda.tk >>> >>> -- I can see clearly now, the brain is gone... >>> > > > > -- > Best regards, > Derek mailto:takeda@takeda.tk > > What happens if you get scared half to death twice? >