From mboxrd@z Thu Jan  1 00:00:00 1970
From: Dmitri Seletski <drjoms@gmail.com>
Subject: Re: wifi pci card issue in windows host.
Date: Mon, 21 Dec 2009 16:48:14 +0000
Message-ID: <4B2FA6CE.9050203@gmail.com>
References: <4B2A579E.3090704@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
To: kvm@vger.kernel.org
Return-path: <kvm-owner@vger.kernel.org>
Received: from ey-out-2122.google.com ([74.125.78.27]:25507 "EHLO
	ey-out-2122.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1750974AbZLUQsX (ORCPT <rfc822;kvm@vger.kernel.org>);
	Mon, 21 Dec 2009 11:48:23 -0500
Received: by ey-out-2122.google.com with SMTP id 4so289414eyf.5
        for <kvm@vger.kernel.org>; Mon, 21 Dec 2009 08:48:22 -0800 (PST)
In-Reply-To: <4B2A579E.3090704@gmail.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Dmitri Seletski wrote:
> Hello folks.
> My goal is to make my pci based network card work under windows
> guest.(obviously using windows drivers)
>
> this is device i am interested in:
> 01:07.0 Network controller: Atheros Communications Inc. AR5416
> 802.11abgn Wireless PCI Adapter (rev 01)
>     Subsystem: D-Link System Inc Device 3a6b
>     Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+
> Stepping- SERR+ FastB2B+ DisINTx-
>     Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
>     Latency: 168, Cache Line Size: 64 bytes
>     Interrupt: pin A routed to IRQ 16
>     Region 0: Memory at f9ff0000 (32-bit, non-prefetchable) [size=64K]
>     Capabilities: [40] #00 [0000]
>     Kernel driver in use: ath9k
>     Kernel modules: ath9k
>
> uname -a: Linux dimko 2.6.32 #4 SMP PREEMPT Thu Dec 17 02:45:45 GMT 2009
> x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ AuthenticAMD GNU/Linux
>
>
>
>
> below commands I have executed:
> #echo "1186 3a6b" > /sys/bus/pci/drivers/pci-stub/new_id
> #echo 0000:01:07.0 > /sys/bus/pci/devices/0000\:01\:07.0/driver/unbind
> #echo 0000:01:07.0 > /sys/bus/pci/drivers/pci-stub/bind
>
> last command gives:  "echo: write error: No such device"
> I have "pci_stub" module loaded.
>
> and part of dmesg:
> "[ 8471.257299] wlan0: deauthenticating from 00:1e:58:b4:f6:83 by local
> choice (reason=3)
> [ 8471.537053] ath9k 0000:01:07.0: PCI INT A disabled"
> Which i guess is ok.
>
> than i load my guest with smth like: qemu xp32.img -pcidevice
> host=01:07.0 -m 2048
>
> I can see device in linux, i can even install driver for it, and there
> are no other problems with that.
> But device is not usable. Basically wireless device sees no networks,
> even though my network has ESSID opened.
> I was wondering if that previous "echo 0000:01:07.0 >
> /sys/bus/pci/drivers/pci-stub/bind" failure can affect me?
>
> Windows driver is freshly downloaded off dlink site. Access Point is
> */definitely/*
> <http://www.google.ie/search?hl=en&safe=off&client=firefox-a&rls=org.gentoo:en-US:official&hs=h3d&ei=NVcqS5TnA8be4gbw3siBCQ&sa=X&oi=spell&resnum=0&ct=result&cd=1&ved=0CAYQBSgA&q=definitely&spell=1> 
> working, since i am connecting to it using native linux drivers.
>
> Thanks in advance.
> Dmitri
>
>   
Guys, anyone?