From: Johannes Berg <johannes@sipsolutions.net>
To: Dominik Feser <dominik.feser@googlemail.com>
Cc: Emmanuel Grumbach <egrumbach@gmail.com>,
Arend van Spriel <arend@broadcom.com>,
linux-wireless@vger.kernel.org,
Wey-Yi Guy <wey-yi.w.guy@intel.com>
Subject: Re: wlan0 not present
Date: Thu, 19 Apr 2012 07:20:06 -0700 [thread overview]
Message-ID: <4F901F16.6080007@sipsolutions.net> (raw)
In-Reply-To: <EA757D90-2CCE-48A1-AF35-7F65EB45F7EE@gmail.com> (sfid-20120419_161001_182682_E2B061CB)
On 4/19/2012 7:09 AM, Dominik Feser wrote:
> Finally, here is the output of dmesg after recompiling:
>
> iwlwifi 0000:02:00.0: edd19e18
> iwlwifi 0000:02:00.0: d55c1e18
> iwlwifi 0000:02:00.0: d55c1ddc
> iwlwifi 0000:02:00.0: PCI INT A disabled
> Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:d
> Copyright(c) 2003-2012 Intel Corporation
> iwlwifi 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
> iwlwifi 0000:02:00.0: setting latency timer to 64
> iwlwifi 0000:02:00.0: pci_resource_len = 0x00002000
> iwlwifi 0000:02:00.0: pci_resource_base = f447c000
> iwlwifi 0000:02:00.0: HW Revision ID = 0x34
> iwlwifi 0000:02:00.0: irq 1277 (277) for MSI/MSI-X
> iwlwifi 0000:02:00.0: U iwl_request_firmware d5b37d70
> iwlwifi 0000:02:00.0: U iwl_request_firmware e09ebdd4
> iwlwifi 0000:02:00.0: ee2afe18
> iwlwifi 0000:02:00.0: U iwl_request_firmware ee2afdd4
> iwlwifi 0000:02:00.0: cc93fe18
> iwlwifi 0000:02:00.0: cc93fddc
Still pretty useless since you get %pV printed as a pointer rather than
a message. Does anyone know how to fix that in compat? But the
iwl_request_firmware 3 times probably means it failed?
johannes
next prev parent reply other threads:[~2012-04-19 14:20 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 17:59 wlan0 not present Dominik Feser
2012-04-17 19:19 ` Arend van Spriel
2012-04-17 21:41 ` Dominik Feser
2012-04-18 0:37 ` Johannes Berg
2012-04-18 6:49 ` Dominik Feser
2012-04-18 8:36 ` Emmanuel Grumbach
2012-04-18 8:48 ` Dominik Feser
2012-04-18 9:30 ` Emmanuel Grumbach
2012-04-18 14:39 ` Dominik Feser
2012-04-18 16:37 ` Emmanuel Grumbach
2012-04-18 16:56 ` Dominik Feser
2012-04-18 19:25 ` Emmanuel Grumbach
2012-04-18 19:28 ` Dominik Feser
2012-04-18 19:33 ` Emmanuel Grumbach
2012-04-18 21:17 ` Dominik Feser
2012-04-19 5:03 ` Emmanuel Grumbach
2012-04-19 7:25 ` Dominik Feser
2012-04-19 7:45 ` Emmanuel Grumbach
2012-04-19 7:49 ` Dominik Feser
2012-04-19 7:54 ` Emmanuel Grumbach
2012-04-19 7:55 ` Emmanuel Grumbach
2012-04-19 10:08 ` Dominik Feser
2012-04-19 13:16 ` Emmanuel Grumbach
2012-04-19 13:20 ` Dominik Feser
2012-04-19 13:24 ` Johannes Berg
2012-04-19 14:09 ` Dominik Feser
2012-04-19 14:20 ` Johannes Berg [this message]
2012-04-19 15:08 ` Dominik Feser
2012-04-19 16:19 ` Emmanuel Grumbach
2012-04-19 17:26 ` Dominik Feser
2012-04-19 18:04 ` Emmanuel Grumbach
2012-04-20 6:42 ` Dominik Feser
2012-04-22 5:23 ` Emmanuel Grumbach
2012-04-22 13:00 ` Dominik Feser
2012-04-22 16:53 ` Emmanuel Grumbach
2012-04-23 21:26 ` Dominik Feser
2012-04-24 5:28 ` Emmanuel Grumbach
2012-04-24 11:50 ` Pat Erley
2012-04-24 12:07 ` Sedat Dilek
2012-04-24 12:29 ` Dominik Feser
2012-04-24 12:45 ` Sedat Dilek
2012-04-24 15:34 ` Emmanuel Grumbach
2012-04-25 6:23 ` Sedat Dilek
2012-04-25 7:26 ` Emmanuel Grumbach
2012-04-25 7:32 ` Emmanuel Grumbach
2012-04-25 7:34 ` Sedat Dilek
2012-04-25 10:44 ` Sedat Dilek
2012-05-02 5:08 ` Emmanuel Grumbach
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=4F901F16.6080007@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend@broadcom.com \
--cc=dominik.feser@googlemail.com \
--cc=egrumbach@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=wey-yi.w.guy@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.