From: Bill Roberts <billbalt@eyeofthequark.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Is Gentoo still on the right path?
Date: Thu, 17 Nov 2005 09:03:35 -0500 [thread overview]
Message-ID: <20051117140335.GA16057@antec.eyeofthequark.com> (raw)
In-Reply-To: <9999810b0511160820h648eb1a5o4f62300507c2b8a9@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3493 bytes --]
On 11:20 Wed 16 Nov , Derek Tracy wrote:
> After restarting I noticed that ipw2200 did not load properly was posted
> in my boot mesg WTF. I distinctly remembered during the install that I
> waited until after I installed the kernel, then I went ahead and installed
> the external modules. (NOTE: I did not use the built in kernel modules
> for ipw2200 or ieee80211 I had read too many horror stories about
> incompatible versions of ipw2200-firmware and I have always had good luck
> with the external drivers) One other thing, instead of going for pure on
> the edge goodness of using a Nitro-esque kernel (one optimized for speed
> over stability) I decided to use Gentoo-sources again trusting the
> developers judgement. After searching through tons of articles regarding
> ipw2200 drivers not working with the latest "Stable" Gentoo-Sources I
> decided to go with the kernel drivers and give them a shot. I recompiled
> rebooted and low and behold the drivers still weren't working. After
> trying all sorts of different combinations Unstable versions of this
> stable versions of that. Nothing worked, so I proceeded to reboot back
> into the livecd and re-chroot into my system so I could get a network
> connection and install the Madwifi Drivers, for a pcmcia card that I have
> laying around. Also note that the Madwifi drivers are considered
> Unstable. I rebooted the computer and the drivers actually worked (Yea
> Unstable). So I got the network connection up, then I decided to go ahead
> and install X (I thought that it would be easier to troubleshoot the ipw
> drivers from a graphical environment copy, paste, multiple xterms.). Well
Maybe this will help a little. I am using the ipw2200 drivers, and they
work fine. I am using the gentoo-sources kernel, 2.6.13-r4, with
ipw2200-1.0.6-r3. My eix shows ipw2200-firmware 2.3 and 2.4 installed (I
guess they are slotted), I'm not sure which one is being loaded. I tried
upgrading to 2.6.14, wireless broke (I think that's when I tried loading
the 2.4 firmware), so I went back to my current kernel. I'll hang out here
for a while, 'til they get the bugs worked out of 2.6.14.
I have an ati video, so no help there.
My intial approach to my new laptop was a bit different than yours. Though
I've been doing Gentoo three years, I've never done it on a laptop, never
done Linux or wireless on a laptop. I've had good luck with Ubuntu, wanted
to try their newest, so I loaded it up first, to get info on hardware, get
a working xorg.conf, etc. Had a fully functional laptop in less than an
hour.
I then set up a dual boot gentoo, used the xorg.conf from Ubuntu,
cherry-picked a few ideas from the nicely done Ubuntu. I've added
additional functionality to my Gentoo build as I've needed it. So now,
every time I fire up, I always have a choice. I can use the fully loaded
Ubuntu, which I love for its ease of installation and administration, or I
can use Gentoo, my stripped down hot rod, which on occasion gives me fits.
Gentoo gets the nod every time, unless I'm looking for a bit of freecell.
Why?, I ask myself. I think it's the same reason I liked to take watches
apart when I was a kid. I want to know how things work. I love the Zen-like
aesthetic, starting with a blank slate, and adding only what is absolutely
essential. No cruft.
It's not for everyone, and it's not the "only true way". But it works for
me.
Good Luck
Bill Roberts
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-11-17 14:15 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 16:20 [gentoo-user] Is Gentoo still on the right path? Derek Tracy
2005-11-16 18:23 ` Mark Knecht
2005-11-19 15:07 ` A. Khattri
2005-11-16 19:53 ` Daniel da Veiga
2005-11-16 20:50 ` Derek Tracy
2005-11-16 21:50 ` Jeff Smelser
2005-11-16 22:32 ` Derek Tracy
2005-11-17 0:26 ` Richard Fish
2005-11-16 22:46 ` Neil Bothwick
2005-11-17 11:24 ` Derek Tracy
2005-11-17 11:59 ` Nagatoro
2005-11-17 7:44 ` jarmstrong
2005-11-16 22:51 ` Neil Bothwick
2005-11-17 3:03 ` Mark Knecht
2005-11-17 9:23 ` Neil Bothwick
2005-11-17 13:52 ` Allan Gottlieb
2005-11-17 14:35 ` Neil Bothwick
2005-11-17 17:44 ` Allan Gottlieb
2005-11-17 15:21 ` Mark Knecht
2005-11-17 0:17 ` Ciaran McCreesh
2005-11-17 0:34 ` Richard Fish
2005-11-16 20:12 ` Nick Rout
2005-11-16 20:30 ` kashani
2005-11-16 21:04 ` Nick Rout
2005-11-16 20:30 ` Benjamin Martin
2005-11-16 20:47 ` Mark Knecht
2005-11-16 20:55 ` Benjamin Martin
2005-11-16 20:59 ` Derek Tracy
2005-11-16 21:10 ` Mark Knecht
2005-11-16 21:20 ` Derek Tracy
2005-11-16 22:31 ` Richard Fish
2005-11-16 23:24 ` kashani
2005-11-16 21:33 ` Manuel McLure
2005-11-16 21:53 ` Jeff Smelser
2005-11-16 20:54 ` Zac Medico
2005-11-16 22:22 ` Richard Fish
2005-11-16 22:37 ` Derek Tracy
2005-11-17 0:21 ` Richard Fish
2005-11-17 14:03 ` Bill Roberts [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-16 20:27 Budd, Tracy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051117140335.GA16057@antec.eyeofthequark.com \
--to=billbalt@eyeofthequark.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox