public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Ivan T. Ivanov" <iivanov@mm-sol.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Wifi, problem, problem, problem
Date: Thu, 19 Dec 2013 13:05:43 +0200	[thread overview]
Message-ID: <1387451143.2920.21.camel@iivanov-dev.int.mm-sol.com> (raw)
In-Reply-To: <4569bf91942577663878b1e0e91f27a4@iiiha.com>



Hi, 

On Thu, 2013-12-19 at 09:54 +0100, Florian HEGRON wrote: 
> 
> On 2013-12-19 09:47, Ivan T. Ivanov wrote:
> > Hi Florian,
> > 
> Hi
> > On Thu, 2013-12-19 at 09:08 +0100, Florian HEGRON wrote:
> > 
> > 
> > 
> > I found the line !!
> > 
> > I had to enable wireless extension option on Network Support -> 
> > Wireless
> > 
> > So I enable my card support, and I reboot (I already emerge
> > ipw2200-firmware).
> > 
> > #dmesg | grep 2200
> > [    1.180583] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver,
> > 1.2.2k
> > [    1.180643] ipw2200: Copyright(c) 2003-2006 Intel Corporation
> > [    1.182617] ipw2200: Detected Intel PRO/Wireless 2200BG Network
> > Connection
> > [   61.408070] ipw2200: ipw2200-bss.fw request_firmware failed: Reason
> > -2
> > 
> > This means that driver can not find ipw2200-bss.fw file (probably
> > part  of sys-firmware/ipw2200-firmware) to load it to wireless card
> > RAM chip. Ensure that you have that file, usually it is localed
> > in /lib/firmware.
> > 
> This file is present, I checked.
> 

How did you build this driver? I mean as module or it is
build in ([M] or [*]). If it is build in it is possible
that root file system is not mounted when driver loads.
Try to build it as module.


Regards,
Ivan




  reply	other threads:[~2013-12-19 11:07 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 [this message]
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
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=1387451143.2920.21.camel@iivanov-dev.int.mm-sol.com \
    --to=iivanov@mm-sol.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