WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Athereos Wireless Domain 0

To: Deepak Manohar <mjdeepak@xxxxxxxxx>
Subject: Re: [Xen-users] Athereos Wireless Domain 0
From: shyam sundar <shyamx@xxxxxxxxx>
Date: Mon, 13 Jun 2005 22:54:50 +0530
Cc: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, ian.pratt@xxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 13 Jun 2005 17:23:59 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=hTI7eblOcffUsL6mP4Eqb1tqpEsloxHG/0bg2mW4irJu8V5j1jyDE3dNBO+NgqBIqa5DZZmEXjWjxWX4QuwZczfAaGeColwLoYPAocTxbyfQq8PkkH+cBse3o604LVQu4TT+jrWTsSuAN/UZ3stiOo5p6s1LrINhggwJY8KGm48=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <fdef3c240506130847170bd84d@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D2821D4@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <fdef3c240506130847170bd84d@xxxxxxxxxxxxxx>
Reply-to: shyam sundar <shyamx@xxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Ian - 

The interrupt counter is increasing for the IRQ 10 (used by
ndiswrapper). The ndiswrapper entry in /proc/interrupts for XEN looks
like
=======
 10:       9122        Phys-irq  ndiswrapper, uhci_hcd
=======
On Fedora Core 3 
=======
 10:     314564          XT-PIC  ndiswrapper, uhci_hcd
=======
and yes the IP configuration and routes are fine. Please do let me
know if I can provide more information that can help you with....



Deepak -
I will write to the address you have specified.

- - Syam
On 6/13/05, Deepak Manohar <mjdeepak@xxxxxxxxx> wrote:
> Hi Shyam,
> 
>  We have wireless working in both dom0 and domU.
> 
>  For further information email shaocheng.wang@xxxxxxxxxx
> 
> 
> 
> 
> On 6/13/05, Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx> wrote:
> >
> > > I am trying to get my wireless network card work under dom0
> > > of XEN. I could successfully install the ndiswrapper drivers
> > > and could see it being associated to AP.
> > >
> > > However I amn't able to transmit any packets outbound. I
> > > could'nt even ping the AP.
> > > Interestingly when I run a tcpdump I can see few broadcast
> > > packets on the interface. There no rules in iptables for nat
> > > or filter or mangle.
> > > Neither did I start /setup any bridge setup.
> >
> > Does /proc/interrupts look like its going up? (I presume you've checked
> > the interface has an IP address and routes OK?)
> >
> > Ian
> >
> > > strace on ping gives me "EAGAIN Resource temporarily
> > > unavialable" errors.
> > >
> > > Even with madwifi drivers and it is the same story.  The
> > > drivers work perfectly on Fedora core 3 kernel.
> > >
> > > Am I missing something obvious ?
> > >
> > > Any help would be appreciated.
> > >
> > >
> > > Regards
> > > Syam
> > >
> > > _______________________________________________
> > > Xen-users mailing list
> > > Xen-users@xxxxxxxxxxxxxxxxxxx
> > > http://lists.xensource.com/xen-users
> > >
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-users
> >
>

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>