[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] madwifi and Xen


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Luke <secureboot@xxxxxxxxx>
  • Date: Sun, 12 Feb 2006 17:31:34 -0500
  • Delivery-date: Sun, 12 Feb 2006 22:44:11 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:mime-version:in-reply-to:references:content-type:message-id:content-transfer-encoding:from:subject:date:to:x-mailer; b=aHo+ME4qciV8TAGlnu/0nkARcwaG87Lg8DBDbdye1iXKJzcG79SCAdKpjNKhPr7M8sKNnbnOnCaEjmZQXXpi42UI1+P/3jxz/ciunE7AdrCJKEaq07a6DL1PkHvkKFnpX8YZhHSAlk+GEt2nDiF7pmHUl9VmuvIJQI8gERDQ0h8=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>


On Feb 12, 2006, at 5:19 PM, Ernst Bachmann wrote:

On Sunday 12 February 2006 22:58, Luke wrote:
Is it possible to get madwifi working in a dom0?  When I try, both
with and without the noacpi on the kernel line in menu.lst, the
machine crashes all the time, but in different ways (different parts
of the bootup segfault, and create different sorts of errors).

I built the old madwifi codebase, linked to the Xen kernel source via
make KERNELPATH=/path_to_xen_kernel

did you try

make ARCH=xen KERNELPATH=...  ?

/Ernst


Bah, that works.  Can't believe I forgot that one.

I'll post again if I'm having stability problems anymore, but it seems to be working alright now. Kinda neat that you can still compile external modules even with a Xen-modified kernel.

--
Luke

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.