[gentoo-user] ipw2200 chipset mini wireless card

2006-05-05 Thread William Kenworthy
I have a new sony lappy with a ipw2200 chipset mini wireless card. Should I be using the in kernel (2.6.16-r3) drivers or the builds in portage? Is the a configuration guide for this setup on gentoo? BillK -- William Kenworthy [EMAIL PROTECTED] Home! -- gentoo-user@gentoo.org mailing list

Re: [gentoo-user] ipw2200 chipset mini wireless card

2006-05-05 Thread Raymond Lewis Rebbeck
On Friday, May 5 2006 22:14, William Kenworthy wrote: I have a new sony lappy with a ipw2200 chipset mini wireless card. Should I be using the in kernel (2.6.16-r3) drivers or the builds in portage? Is the a configuration guide for this setup on gentoo? BillK -- William Kenworthy [EMAIL

Re: [gentoo-user] ipw2200 chipset mini wireless card

2006-05-05 Thread Mike Markowski
Bill, William Kenworthy wrote: I have a new sony lappy with a ipw2200 chipset mini wireless card. Should I be using the in kernel (2.6.16-r3) drivers or the builds in portage? Is the a configuration guide for this setup on gentoo? You want the portage builds. I'm going by memory (laptop is

Re: [gentoo-user] ipw2200 chipset mini wireless card

2006-05-05 Thread fire-eyes
On Friday 05 May 2006 08:44, William Kenworthy wrote: I have a new sony lappy with a ipw2200 chipset mini wireless card. Should I be using the in kernel (2.6.16-r3) drivers or the builds in portage?  Is the a configuration guide for this setup on gentoo? Some will say in kernel, some will say

Re: [gentoo-user] ipw2200 chipset mini wireless card

2006-05-05 Thread William Kenworthy
Thanks, as the in-kernel ones didnt work, I'll try the external. BillK On Fri, 2006-05-05 at 09:07 -0400, Mike Markowski wrote: Bill, William Kenworthy wrote: I have a new sony lappy with a ipw2200 chipset mini wireless card. Should I be using the in kernel (2.6.16-r3) drivers or the

Re: [gentoo-user] ipw2200 chipset mini wireless card

2006-05-05 Thread Jeremy Olexa
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 fire-eyes wrote: On Friday 05 May 2006 08:44, William Kenworthy wrote: I have a new sony lappy with a ipw2200 chipset mini wireless card. Should I be using the in kernel (2.6.16-r3) drivers or the builds in portage? Is the a configuration guide

Re: [gentoo-user] ipw2200 chipset mini wireless card

2006-05-05 Thread Raymond Lewis Rebbeck
On Friday, May 5 2006 23:22, Jeremy Olexa wrote: Does anyone really know what the difference is? I originally used the ebuilds because I could only assume that they will be more up to date. But now I realize that new kernels come out pretty quick so I don't think this is the case. Anyone have

Re: [gentoo-user] ipw2200 chipset mini wireless card

2006-05-05 Thread Christian Limberg
William Kenworthy schrieb: Thanks, as the in-kernel ones didnt work, I'll try the external. BillK Hm, did you compile the in-kernel ipw2200-driver as a kernel module? If the driver is built-in, it will not work, because the driver cannot load its firmware before the kernel has booted. As

Re: [gentoo-user] ipw2200 chipset mini wireless card

2006-05-05 Thread Jure Varlec
On Friday 05 May 2006 15:52, Jeremy Olexa wrote: Does anyone really know what the difference is? I originally used the ebuilds because I could only assume that they will be more up to date. But now I realize that new kernels come out pretty quick so I don't think this is the case. Anyone have

Re: [gentoo-user] ipw2200 chipset mini wireless card

2006-05-05 Thread Boyd Stephen Smith Jr.
On Friday 05 May 2006 08:23, fire-eyes [EMAIL PROTECTED] wrote about 'Re: [gentoo-user] ipw2200 chipset mini wireless card': On Friday 05 May 2006 08:44, William Kenworthy wrote: I have a new sony lappy with a ipw2200 chipset mini wireless card. Should I be using the in kernel (2.6.16-r3

Re: [gentoo-user] ipw2200 chipset mini wireless card

2006-05-05 Thread Raymond Lewis Rebbeck
On Saturday, May 6 2006 5:41, Jure Varlec wrote: For me, both worked well for normal usage. However, the in-kernel drivers didn't support monitor mode too well (or at all), i.e. kismet didn't work. I think firmware was the real culprit, but I'm not sure. Anyways, ebuild drivers and firmware