From: Bruce Hill <daddy@happypenguincomputers.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Wifi, problem, problem, problem
Date: Fri, 20 Dec 2013 09:32:37 -0600 [thread overview]
Message-ID: <20131220153237.GS13604@server> (raw)
In-Reply-To: <201312191918.11719.michaelkintzios@gmail.com>
On Thu, Dec 19, 2013 at 07:17:55PM +0000, Mick wrote:
> On Thursday 19 Dec 2013 15:18:15 the wrote:
> > On 12/19/13 17:50, Bruce Hill wrote:
> > > I *believe* if you have the driver built into your kernel:
> > > CONFIG_IPW2200=y then you need to have the firmware listed with
> > > these 2 lines: CONFIG_EXTRA_FIRMWARE="ipw2200-bss.fw"
> > > CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware/" (Something similar to
> > > the CONFIG_EXTRA_FIRMWARE line. I don't use ipw2200 and that might
> > > not be the proper way. You said the file is there, you checked, so
> > > you should know the proper path and syntax.)
> >
> > iirc I tried specifying extra firmware but it didn't load.
>
>
> Have a look at the section "Code Listing 2.10: Enabling external firmware"
> here:
>
> http://www.gentoo.org/doc/en/handbook/handbook-sparc.xml?part=1&chap=7
>
> Don't forget to recompile and *boot* the newly configured kernel after you do
> this.
Good post, Mick. It seems the amd64 Handbook is neutered concerning this.
Perhaps someone decided genkernel was a substitute for properly configuring a
custom kernel? If so, they should spend a day in #gentoo on IRC to help all
those poor blokes arriving with failure due to genkernel.
Cheers,
Bruce
--
List replies preferred.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting
next prev parent reply other threads:[~2013-12-20 15:32 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 14:36 [gentoo-user] Wifi, problem, problem, problem Florian HEGRON
2013-12-16 14:45 ` Mehdi Chemloul
2013-12-16 15:43 ` Florian HEGRON
2013-12-16 15:56 ` Rick "Zero_Chaos" Farina
2013-12-16 20:27 ` Mick
2013-12-17 9:44 ` Florian HEGRON
2013-12-17 10:31 ` Peter Humphrey
2013-12-17 10:48 ` Neil Bothwick
2013-12-17 15:23 ` Florian HEGRON
2013-12-18 8:25 ` Florian HEGRON
2013-12-18 8:59 ` Randolph Maaßen
2013-12-18 9:06 ` Florian HEGRON
2013-12-19 8:08 ` Florian HEGRON
2013-12-19 8:47 ` Ivan T. Ivanov
2013-12-19 8:54 ` Florian HEGRON
2013-12-19 11:05 ` Ivan T. Ivanov
2013-12-19 13:19 ` Florian HEGRON
2013-12-19 13:50 ` Bruce Hill
2013-12-19 15:18 ` the
2013-12-19 19:17 ` Mick
2013-12-20 11:03 ` Florian HEGRON
2013-12-20 15:32 ` Bruce Hill [this message]
2013-12-19 13:51 ` Ivan T. Ivanov
2013-12-19 14:09 ` Florian HEGRON
2013-12-19 14:19 ` Ivan T. Ivanov
2013-12-19 14:27 ` the
2013-12-19 14:39 ` Ivan T. Ivanov
2013-12-19 14:44 ` Florian HEGRON
2013-12-19 8:53 ` Neil Bothwick
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=20131220153237.GS13604@server \
--to=daddy@happypenguincomputers.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