Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 2 May 2005 10:24:17 +0200
From:      Stijn Hoop <stijn@win.tue.nl>
To:        Clement Twine <clem.twain@gmail.com>
Cc:        "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org>
Subject:   Re: 5.3 on latitude d600?
Message-ID:  <20050502082417.GA42487@pcwin002.win.tue.nl>
In-Reply-To: <42737CEF.8060304@gmail.com>
References:  <4273675C.1090400@gmail.com> <20050430122748.GC16298@pcwin002.win.tue.nl> <42737CEF.8060304@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--pf9I7BMVVzbSWLtt
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Apr 30, 2005 at 02:41:19PM +0200, Clement Twine wrote:
> Stijn Hoop wrote the following on 04/30/2005 02:27 PM:
> > On Sat, Apr 30, 2005 at 01:09:16PM +0200, Clement Twine wrote:
> > > has anyone installed freebsd 5.3 on a dell latitude d600? have
> > > the following worked "out-of-the-box"?
> > >
> > > WiFi:	Intel PRO/Wireless LAN 2100 3B Mini PCI Adapter
> >
> > Not out of the box but there's a driver in -CURRENT for it:
> > iwi(4). There is a version for 5.3 on Damien Bergamini's website
> > afaik (google for it).
>=20
> ok, but this laptop is like - 3 years old? anyway, i'll look there.

This is due to a lot of circumstance, most of it political:

- at first every wireless vendor refused to release programming
  information, except for a select few.
- now, although the programming information is out in the open, Intel
  refuses to release the needed firmware for the chipset under
  a license that is compatible for open source projects to include it

these two facts do not help regular driver development. In fact, the
original author of the BSD drivers for Intel wireless chips is also
the primary author of the cooperative Ralink Technology chipset driver;
given a choice it would be wise to choose a wireless adapter with that
chipset over the Intel ones.

Anyway you don't really have a choice, just explaining why things are
as they are.

> > > ACPI especially suspend to RAM?
> >
> > Haven't gotten that to work although apparently disabling USB
> > helps.
>=20
> hmm.. wouldnt disable usb on my laptop - and SuSE 9.2 currently
> installed does this well.

Maybe this has changed in recent -CURRENTs, I haven't tried it in
a while.

> My major concern is suspend to RAM. I use FreeBSD, but not on my
> laptop so far. Looks like i have to wait a while for the ACPI to
> fully 'mature' on freeBSD ;) I *hate* having to shutdown my laptoy :)

Just try it out. 5.4 has a lot of improvements and I haven't tried
suspend in a few releases so maybe you're in for a nice surprise.

--Stijn

--=20
"What if everything you see is more than what you see -- the person next to
you is a warrior and the space that appears empty is a secret door to anoth=
er
world? What if something appears that shouldn't? You either dismiss it, or =
you
accept that there is much more to the world than you think. Perhaps it real=
ly
is a doorway, and if you choose to go inside, you'll find many unexpected
things."
		-- Shigeru Miyamoto

--pf9I7BMVVzbSWLtt
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (FreeBSD)

iD8DBQFCdeOxY3r/tLQmfWcRAoHOAJ9cWDe/ZYOKYPVqLnNdRf4P7hGLAgCfRH0P
b6ZIyHUDDgztCZksOROljCQ=
=rDkd
-----END PGP SIGNATURE-----

--pf9I7BMVVzbSWLtt--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050502082417.GA42487>