All of lore.kernel.org
 help / color / mirror / Atom feed
* IWL5300, 2.6.29-rc4, CRDA 1.0.1: Missing out 802.11A frequency ranges
@ 2009-02-09 18:09 Tony Vroon
  2009-02-09 18:20 ` Luis R. Rodriguez
  0 siblings, 1 reply; 20+ messages in thread
From: Tony Vroon @ 2009-02-09 18:09 UTC (permalink / raw)
  To: linux-wireless; +Cc: reinette chatre, Luis R. Rodriguez

[-- Attachment #1: Type: text/plain, Size: 3457 bytes --]

I'm using:
[ebuild   R   ] net-wireless/wireless-regdb-20090130  0 kB
[ebuild   R   ] net-wireless/crda-1.0.1-r1  0 kB
[ebuild   R   ] net-wireless/iwl5000-ucode-5.4.0.11  0 kB

The regulatory information for Great Britain looks as follows:
country GB:
	(2402.000 - 2482.000 @ 40.000), (N/A, 20.00)
	(5170.000 - 5250.000 @ 40.000), (N/A, 20.00)
	(5250.000 - 5330.000 @ 40.000), (N/A, 20.00), DFS
	(5490.000 - 5710.000 @ 40.000), (N/A, 27.00), DFS

iw reports the card configuration like such:
Wiphy phy0
	Band 1:
		HT capabilities: 0x087e
			 * 20/40 MHz operation
			 * SM PS disabled
			 * HT-greenfield
			 * 20 MHz short GI
			 * 40 MHz short GI
			 * max A-MSDU len 7935
		HT A-MPDU factor: 0x0003 (65535 bytes)
		HT A-MPDU density: 0x0005 (4 usec)
		HT MCS set: ff ff ff 00 01 00 00 00 00 00 c2 01 01 00 00 00
		Frequencies:
			* 2412 MHz [1] (15.0 dBm)
			* 2417 MHz [2] (15.0 dBm)
			* 2422 MHz [3] (15.0 dBm)
			* 2427 MHz [4] (15.0 dBm)
			* 2432 MHz [5] (15.0 dBm)
			* 2437 MHz [6] (15.0 dBm)
			* 2442 MHz [7] (15.0 dBm)
			* 2447 MHz [8] (15.0 dBm)
			* 2452 MHz [9] (15.0 dBm)
			* 2457 MHz [10] (15.0 dBm)
			* 2462 MHz [11] (15.0 dBm)
			* 2467 MHz [12] (15.0 dBm) (passive scanning, no IBSS)
			* 2472 MHz [13] (15.0 dBm) (passive scanning, no IBSS)
		Bitrates:
			* 1.0 Mbps
			* 2.0 Mbps (short preamble supported)
			* 5.5 Mbps (short preamble supported)
			* 11.0 Mbps (short preamble supported)
			* 6.0 Mbps
			* 9.0 Mbps
			* 12.0 Mbps
			* 18.0 Mbps
			* 24.0 Mbps
			* 36.0 Mbps
			* 48.0 Mbps
			* 54.0 Mbps
			* 60.0 Mbps
	Band 2:
		HT capabilities: 0x087e
			 * 20/40 MHz operation
			 * SM PS disabled
			 * HT-greenfield
			 * 20 MHz short GI
			 * 40 MHz short GI
			 * max A-MSDU len 7935
		HT A-MPDU factor: 0x0003 (65535 bytes)
		HT A-MPDU density: 0x0005 (4 usec)
		HT MCS set: ff ff ff 00 01 00 00 00 00 00 c2 01 01 00 00 00
		Frequencies:
			* 5180 MHz [36] (disabled)
			* 5200 MHz [40] (disabled)
			* 5220 MHz [44] (disabled)
			* 5240 MHz [48] (disabled)
			* 5260 MHz [52] (disabled)
			* 5280 MHz [56] (disabled)
			* 5300 MHz [60] (disabled)
			* 5320 MHz [64] (disabled)
			* 5500 MHz [100] (disabled)
			* 5520 MHz [104] (disabled)
			* 5540 MHz [108] (disabled)
			* 5560 MHz [112] (disabled)
			* 5580 MHz [116] (disabled)
			* 5600 MHz [120] (disabled)
			* 5620 MHz [124] (disabled)
			* 5640 MHz [128] (disabled)
			* 5660 MHz [132] (disabled)
			* 5680 MHz [136] (disabled)
			* 5700 MHz [140] (disabled)
			* 5745 MHz [149] (disabled)
			* 5765 MHz [153] (disabled)
			* 5785 MHz [157] (disabled)
			* 5805 MHz [161] (disabled)
			* 5825 MHz [165] (disabled)
		Bitrates:
			* 6.0 Mbps
			* 9.0 Mbps
			* 12.0 Mbps
			* 18.0 Mbps
			* 24.0 Mbps
			* 36.0 Mbps
			* 48.0 Mbps
			* 54.0 Mbps
			* 60.0 Mbps
	Supported interface modes:
		 * IBSS
		 * Station
		 * Monitor

My Cisco AIR-AP1131AG-E-K9_v04 access point with C1130 Software
(C1130-K9W7-M), Version 12.4(10b)JA, RELEASE has Dot11Radio0 &
Dot11Radio1 configured like so:
world-mode dot11d country GB indoor

The kernel seems to do something else:
cfg80211: Calling CRDA for country: GB
cfg80211: Current regulatory domain updated by AP to: GB
	(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
	(2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)

Any idea how that could happen please?

Regards,
Tony V.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: IWL5300, 2.6.29-rc4, CRDA 1.0.1: Missing out 802.11A frequency ranges
  2009-02-09 18:09 IWL5300, 2.6.29-rc4, CRDA 1.0.1: Missing out 802.11A frequency ranges Tony Vroon
@ 2009-02-09 18:20 ` Luis R. Rodriguez
  2009-02-09 18:22   ` Luis R. Rodriguez
  2009-02-09 18:23   ` Tony Vroon
  0 siblings, 2 replies; 20+ messages in thread
From: Luis R. Rodriguez @ 2009-02-09 18:20 UTC (permalink / raw)
  To: tony; +Cc: linux-wireless, reinette chatre

On Mon, Feb 9, 2009 at 10:09 AM, Tony Vroon <tony@linx.net> wrote:
> I'm using:
> [ebuild   R   ] net-wireless/wireless-regdb-20090130  0 kB
> [ebuild   R   ] net-wireless/crda-1.0.1-r1  0 kB
> [ebuild   R   ] net-wireless/iwl5000-ucode-5.4.0.11  0 kB
>
> The regulatory information for Great Britain looks as follows:
> country GB:
>        (2402.000 - 2482.000 @ 40.000), (N/A, 20.00)
>        (5170.000 - 5250.000 @ 40.000), (N/A, 20.00)
>        (5250.000 - 5330.000 @ 40.000), (N/A, 20.00), DFS
>        (5490.000 - 5710.000 @ 40.000), (N/A, 27.00), DFS
>
> iw reports the card configuration like such:
> Wiphy phy0
>        Band 1:
>                HT capabilities: 0x087e
>                         * 20/40 MHz operation
>                         * SM PS disabled
>                         * HT-greenfield
>                         * 20 MHz short GI
>                         * 40 MHz short GI
>                         * max A-MSDU len 7935
>                HT A-MPDU factor: 0x0003 (65535 bytes)
>                HT A-MPDU density: 0x0005 (4 usec)
>                HT MCS set: ff ff ff 00 01 00 00 00 00 00 c2 01 01 00 00 00
>                Frequencies:
>                        * 2412 MHz [1] (15.0 dBm)
>                        * 2417 MHz [2] (15.0 dBm)
>                        * 2422 MHz [3] (15.0 dBm)
>                        * 2427 MHz [4] (15.0 dBm)
>                        * 2432 MHz [5] (15.0 dBm)
>                        * 2437 MHz [6] (15.0 dBm)
>                        * 2442 MHz [7] (15.0 dBm)
>                        * 2447 MHz [8] (15.0 dBm)
>                        * 2452 MHz [9] (15.0 dBm)
>                        * 2457 MHz [10] (15.0 dBm)
>                        * 2462 MHz [11] (15.0 dBm)
>                        * 2467 MHz [12] (15.0 dBm) (passive scanning, no IBSS)
>                        * 2472 MHz [13] (15.0 dBm) (passive scanning, no IBSS)
>                Bitrates:
>                        * 1.0 Mbps
>                        * 2.0 Mbps (short preamble supported)
>                        * 5.5 Mbps (short preamble supported)
>                        * 11.0 Mbps (short preamble supported)
>                        * 6.0 Mbps
>                        * 9.0 Mbps
>                        * 12.0 Mbps
>                        * 18.0 Mbps
>                        * 24.0 Mbps
>                        * 36.0 Mbps
>                        * 48.0 Mbps
>                        * 54.0 Mbps
>                        * 60.0 Mbps
>        Band 2:
>                HT capabilities: 0x087e
>                         * 20/40 MHz operation
>                         * SM PS disabled
>                         * HT-greenfield
>                         * 20 MHz short GI
>                         * 40 MHz short GI
>                         * max A-MSDU len 7935
>                HT A-MPDU factor: 0x0003 (65535 bytes)
>                HT A-MPDU density: 0x0005 (4 usec)
>                HT MCS set: ff ff ff 00 01 00 00 00 00 00 c2 01 01 00 00 00
>                Frequencies:
>                        * 5180 MHz [36] (disabled)
>                        * 5200 MHz [40] (disabled)
>                        * 5220 MHz [44] (disabled)
>                        * 5240 MHz [48] (disabled)
>                        * 5260 MHz [52] (disabled)
>                        * 5280 MHz [56] (disabled)
>                        * 5300 MHz [60] (disabled)
>                        * 5320 MHz [64] (disabled)
>                        * 5500 MHz [100] (disabled)
>                        * 5520 MHz [104] (disabled)
>                        * 5540 MHz [108] (disabled)
>                        * 5560 MHz [112] (disabled)
>                        * 5580 MHz [116] (disabled)
>                        * 5600 MHz [120] (disabled)
>                        * 5620 MHz [124] (disabled)
>                        * 5640 MHz [128] (disabled)
>                        * 5660 MHz [132] (disabled)
>                        * 5680 MHz [136] (disabled)
>                        * 5700 MHz [140] (disabled)
>                        * 5745 MHz [149] (disabled)
>                        * 5765 MHz [153] (disabled)
>                        * 5785 MHz [157] (disabled)
>                        * 5805 MHz [161] (disabled)
>                        * 5825 MHz [165] (disabled)
>                Bitrates:
>                        * 6.0 Mbps
>                        * 9.0 Mbps
>                        * 12.0 Mbps
>                        * 18.0 Mbps
>                        * 24.0 Mbps
>                        * 36.0 Mbps
>                        * 48.0 Mbps
>                        * 54.0 Mbps
>                        * 60.0 Mbps
>        Supported interface modes:
>                 * IBSS
>                 * Station
>                 * Monitor
>
> My Cisco AIR-AP1131AG-E-K9_v04 access point with C1130 Software
> (C1130-K9W7-M), Version 12.4(10b)JA, RELEASE has Dot11Radio0 &
> Dot11Radio1 configured like so:
> world-mode dot11d country GB indoor
>
> The kernel seems to do something else:
> cfg80211: Calling CRDA for country: GB
> cfg80211: Current regulatory domain updated by AP to: GB
>        (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
>        (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
>
> Any idea how that could happen please?

Your AP did not provide 5 GHz frequencies in its country information
element. Because of this the intersection between what CRDA has for GB
and what your AP provides does not include any channels in 5 GHz. This
has been fixed in wireless-testing though, if your AP country IE does
not have information for a separate band we lave that band to trust
CRDA information instead.

This should have been propagated down to 29 already, maybe it'll be in rc5?

  Luis

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: IWL5300, 2.6.29-rc4, CRDA 1.0.1: Missing out 802.11A frequency ranges
  2009-02-09 18:20 ` Luis R. Rodriguez
@ 2009-02-09 18:22   ` Luis R. Rodriguez
  2009-02-09 18:23   ` Tony Vroon
  1 sibling, 0 replies; 20+ messages in thread
From: Luis R. Rodriguez @ 2009-02-09 18:22 UTC (permalink / raw)
  To: tony; +Cc: linux-wireless, reinette chatre

On Mon, Feb 9, 2009 at 10:20 AM, Luis R. Rodriguez
<lrodriguez@atheros.com> wrote:
> On Mon, Feb 9, 2009 at 10:09 AM, Tony Vroon <tony@linx.net> wrote:
>> I'm using:
>> [ebuild   R   ] net-wireless/wireless-regdb-20090130  0 kB
>> [ebuild   R   ] net-wireless/crda-1.0.1-r1  0 kB
>> [ebuild   R   ] net-wireless/iwl5000-ucode-5.4.0.11  0 kB
>>
>> The regulatory information for Great Britain looks as follows:
>> country GB:
>>        (2402.000 - 2482.000 @ 40.000), (N/A, 20.00)
>>        (5170.000 - 5250.000 @ 40.000), (N/A, 20.00)
>>        (5250.000 - 5330.000 @ 40.000), (N/A, 20.00), DFS
>>        (5490.000 - 5710.000 @ 40.000), (N/A, 27.00), DFS
>>
>> iw reports the card configuration like such:
>> Wiphy phy0
>>        Band 1:
>>                HT capabilities: 0x087e
>>                         * 20/40 MHz operation
>>                         * SM PS disabled
>>                         * HT-greenfield
>>                         * 20 MHz short GI
>>                         * 40 MHz short GI
>>                         * max A-MSDU len 7935
>>                HT A-MPDU factor: 0x0003 (65535 bytes)
>>                HT A-MPDU density: 0x0005 (4 usec)
>>                HT MCS set: ff ff ff 00 01 00 00 00 00 00 c2 01 01 00 00 00
>>                Frequencies:
>>                        * 2412 MHz [1] (15.0 dBm)
>>                        * 2417 MHz [2] (15.0 dBm)
>>                        * 2422 MHz [3] (15.0 dBm)
>>                        * 2427 MHz [4] (15.0 dBm)
>>                        * 2432 MHz [5] (15.0 dBm)
>>                        * 2437 MHz [6] (15.0 dBm)
>>                        * 2442 MHz [7] (15.0 dBm)
>>                        * 2447 MHz [8] (15.0 dBm)
>>                        * 2452 MHz [9] (15.0 dBm)
>>                        * 2457 MHz [10] (15.0 dBm)
>>                        * 2462 MHz [11] (15.0 dBm)
>>                        * 2467 MHz [12] (15.0 dBm) (passive scanning, no IBSS)
>>                        * 2472 MHz [13] (15.0 dBm) (passive scanning, no IBSS)
>>                Bitrates:
>>                        * 1.0 Mbps
>>                        * 2.0 Mbps (short preamble supported)
>>                        * 5.5 Mbps (short preamble supported)
>>                        * 11.0 Mbps (short preamble supported)
>>                        * 6.0 Mbps
>>                        * 9.0 Mbps
>>                        * 12.0 Mbps
>>                        * 18.0 Mbps
>>                        * 24.0 Mbps
>>                        * 36.0 Mbps
>>                        * 48.0 Mbps
>>                        * 54.0 Mbps
>>                        * 60.0 Mbps
>>        Band 2:
>>                HT capabilities: 0x087e
>>                         * 20/40 MHz operation
>>                         * SM PS disabled
>>                         * HT-greenfield
>>                         * 20 MHz short GI
>>                         * 40 MHz short GI
>>                         * max A-MSDU len 7935
>>                HT A-MPDU factor: 0x0003 (65535 bytes)
>>                HT A-MPDU density: 0x0005 (4 usec)
>>                HT MCS set: ff ff ff 00 01 00 00 00 00 00 c2 01 01 00 00 00
>>                Frequencies:
>>                        * 5180 MHz [36] (disabled)
>>                        * 5200 MHz [40] (disabled)
>>                        * 5220 MHz [44] (disabled)
>>                        * 5240 MHz [48] (disabled)
>>                        * 5260 MHz [52] (disabled)
>>                        * 5280 MHz [56] (disabled)
>>                        * 5300 MHz [60] (disabled)
>>                        * 5320 MHz [64] (disabled)
>>                        * 5500 MHz [100] (disabled)
>>                        * 5520 MHz [104] (disabled)
>>                        * 5540 MHz [108] (disabled)
>>                        * 5560 MHz [112] (disabled)
>>                        * 5580 MHz [116] (disabled)
>>                        * 5600 MHz [120] (disabled)
>>                        * 5620 MHz [124] (disabled)
>>                        * 5640 MHz [128] (disabled)
>>                        * 5660 MHz [132] (disabled)
>>                        * 5680 MHz [136] (disabled)
>>                        * 5700 MHz [140] (disabled)
>>                        * 5745 MHz [149] (disabled)
>>                        * 5765 MHz [153] (disabled)
>>                        * 5785 MHz [157] (disabled)
>>                        * 5805 MHz [161] (disabled)
>>                        * 5825 MHz [165] (disabled)
>>                Bitrates:
>>                        * 6.0 Mbps
>>                        * 9.0 Mbps
>>                        * 12.0 Mbps
>>                        * 18.0 Mbps
>>                        * 24.0 Mbps
>>                        * 36.0 Mbps
>>                        * 48.0 Mbps
>>                        * 54.0 Mbps
>>                        * 60.0 Mbps
>>        Supported interface modes:
>>                 * IBSS
>>                 * Station
>>                 * Monitor
>>
>> My Cisco AIR-AP1131AG-E-K9_v04 access point with C1130 Software
>> (C1130-K9W7-M), Version 12.4(10b)JA, RELEASE has Dot11Radio0 &
>> Dot11Radio1 configured like so:
>> world-mode dot11d country GB indoor
>>
>> The kernel seems to do something else:
>> cfg80211: Calling CRDA for country: GB
>> cfg80211: Current regulatory domain updated by AP to: GB
>>        (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
>>        (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
>>
>> Any idea how that could happen please?
>
> Your AP did not provide 5 GHz frequencies in its country information
> element. Because of this the intersection between what CRDA has for GB
> and what your AP provides does not include any channels in 5 GHz. This
> has been fixed in wireless-testing though, if your AP country IE does
> not have information for a separate band we lave that band to trust
> CRDA information instead.
>
> This should have been propagated down to 29 already, maybe it'll be in rc5?

BTW this is the patch commit info:

commit 0c7dc45d21de6ae212b5ccb7cdff5beff795ccf0
Author: Luis R. Rodriguez <lrodriguez@atheros.com>
Date:   Wed Jan 7 17:43:36 2009 -0800

    cfg80211: Fix regression with 11d on bands

    This fixes a regression on disallowing bands introduced with the new
    802.11d support. The issue is that IEEE-802.11 allows APs to send
    a subset of what a country regulatory domain defines. This was clarified
    in this document:

    http://tinyurl.com/11d-clarification

    As such it is possible, and this is what is done in practice, that a
    single band 2.4 GHz AP will only send 2.4 GHz band regulatory information
    through the 802.11 country information element and then the current
    intersection with what CRDA provided yields a regulatory domain with
    no 5 GHz information -- even though that country may actually allow
    5 GHz operation. We correct this by only applying the intersection rules
    on a channel if the the intersection yields a regulatory rule on the
    same band the channel is on.

    Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
    Acked-by: Johannes Berg <johannes@sipsolutions.net>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: IWL5300, 2.6.29-rc4, CRDA 1.0.1: Missing out 802.11A frequency ranges
  2009-02-09 18:20 ` Luis R. Rodriguez
  2009-02-09 18:22   ` Luis R. Rodriguez
@ 2009-02-09 18:23   ` Tony Vroon
  2009-02-09 18:39     ` John W. Linville
  1 sibling, 1 reply; 20+ messages in thread
From: Tony Vroon @ 2009-02-09 18:23 UTC (permalink / raw)
  To: John W. Linville; +Cc: linux-wireless, reinette chatre, Luis R. Rodriguez

[-- Attachment #1: Type: text/plain, Size: 616 bytes --]

On Mon, 2009-02-09 at 10:20 -0800, Luis R. Rodriguez wrote:
> Your AP did not provide 5 GHz frequencies in its country information
> element. Because of this the intersection between what CRDA has for GB
> and what your AP provides does not include any channels in 5 GHz. This
> has been fixed in wireless-testing though, if your AP country IE does
> not have information for a separate band we lave that band to trust
> CRDA information instead.
> 
> This should have been propagated down to 29 already, maybe it'll be in
> rc5?

John, will this make it into 2.6.29 final please?
> 
Regards,
Tony V.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: IWL5300, 2.6.29-rc4, CRDA 1.0.1: Missing out 802.11A frequency ranges
  2009-02-09 18:23   ` Tony Vroon
@ 2009-02-09 18:39     ` John W. Linville
  2009-02-09 19:21       ` Tony Vroon
  0 siblings, 1 reply; 20+ messages in thread
From: John W. Linville @ 2009-02-09 18:39 UTC (permalink / raw)
  To: Tony Vroon; +Cc: linux-wireless, reinette chatre, Luis R. Rodriguez

On Mon, Feb 09, 2009 at 06:23:31PM +0000, Tony Vroon wrote:
> On Mon, 2009-02-09 at 10:20 -0800, Luis R. Rodriguez wrote:
> > Your AP did not provide 5 GHz frequencies in its country information
> > element. Because of this the intersection between what CRDA has for GB
> > and what your AP provides does not include any channels in 5 GHz. This
> > has been fixed in wireless-testing though, if your AP country IE does
> > not have information for a separate band we lave that band to trust
> > CRDA information instead.
> > 
> > This should have been propagated down to 29 already, maybe it'll be in
> > rc5?
> 
> John, will this make it into 2.6.29 final please?

It is in 2.6.29-rc3 AFAICT.

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: IWL5300, 2.6.29-rc4, CRDA 1.0.1: Missing out 802.11A frequency ranges
  2009-02-09 18:39     ` John W. Linville
@ 2009-02-09 19:21       ` Tony Vroon
  2009-02-09 19:35         ` Tony Vroon
  0 siblings, 1 reply; 20+ messages in thread
From: Tony Vroon @ 2009-02-09 19:21 UTC (permalink / raw)
  To: John W. Linville; +Cc: linux-wireless, reinette chatre, Luis R. Rodriguez


[-- Attachment #1.1: Type: text/plain, Size: 421 bytes --]

Full dmesg of the faulty run with debugging attached for your reference.
Indeed, as John said this patch made it into mainline and is already
applied to my sources:

chainsaw@amalthea /cvs/linux-2.6 $ patch --dry-run -p1 -i ~/\[PATCH_5_6
\]_cfg80211\:_Fix_regression_with_11d_on_bands.diff 
patching file net/wireless/reg.c
Reversed (or previously applied) patch detected!  Assume -R? [n] ^C

Regards,
Tony V.

[-- Attachment #1.2: dmesg.txt --]
[-- Type: text/plain, Size: 44596 bytes --]

Linux version 2.6.29-rc4-00026-gf06da26 (root@amalthea) (gcc version 4.3.3 (Gentoo 4.3.3 p1.0, pie-10.1.5) ) #1 SMP Mon Feb 9 18:55:10 GMT 2009
Command line: auto BOOT_IMAGE=2.6.29-rc4-0002 rw root=0 video=vesafb:ywrap,pmipal,mtrr
KERNEL supported cpus:
  Intel GenuineIntel
  AMD AuthenticAMD
  Centaur CentaurHauls
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009d400 (usable)
 BIOS-e820: 000000000009d400 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 00000000bce51000 (usable)
 BIOS-e820: 00000000bce51000 - 00000000bce57000 (reserved)
 BIOS-e820: 00000000bce57000 - 00000000bd058000 (usable)
 BIOS-e820: 00000000bd058000 - 00000000bd0af000 (reserved)
 BIOS-e820: 00000000bd0af000 - 00000000bd1a8000 (usable)
 BIOS-e820: 00000000bd1a8000 - 00000000bd4af000 (reserved)
 BIOS-e820: 00000000bd4af000 - 00000000bd4d8000 (usable)
 BIOS-e820: 00000000bd4d8000 - 00000000bd4df000 (reserved)
 BIOS-e820: 00000000bd4df000 - 00000000bd535000 (usable)
 BIOS-e820: 00000000bd535000 - 00000000bd57f000 (ACPI NVS)
 BIOS-e820: 00000000bd57f000 - 00000000bd5e4000 (usable)
 BIOS-e820: 00000000bd5e4000 - 00000000bd5fd000 (ACPI data)
 BIOS-e820: 00000000bd5fd000 - 00000000bd600000 (usable)
 BIOS-e820: 00000000bd600000 - 00000000c0000000 (reserved)
 BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
 BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
 BIOS-e820: 00000000fed00000 - 00000000fed00400 (reserved)
 BIOS-e820: 00000000fed10000 - 00000000fed14000 (reserved)
 BIOS-e820: 00000000fed18000 - 00000000fed1a000 (reserved)
 BIOS-e820: 00000000fed1c000 - 00000000fed90000 (reserved)
 BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
 BIOS-e820: 00000000ff800000 - 0000000100000000 (reserved)
DMI 2.4 present.
last_pfn = 0xbd600 max_arch_pfn = 0x100000000
x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
init_memory_mapping: 0000000000000000-00000000bd600000
 0000000000 - 00bd600000 page 2M
kernel direct mapping tables up to bd600000 @ 8000-c000
last_map_addr: bd600000 end: bd600000
ACPI: RSDP 000F53D0, 0024 (r2 FUJ   )
ACPI: XSDT BD5F3434, 0074 (r1 FSC    PC        1160000 FUJ       100)
ACPI: FACP BD5E6000, 00F4 (r3 FSC    PC        1160000 FUJ       100)
FADT: X_PM1a_EVT_BLK.bit_width (16) does not match PM1_EVT_LEN (4)
ACPI: DSDT BD5E7000, 8CFF (r1 FUJ    FJNB1E6   1160000 FUJ       100)
ACPI: FACS BD56EFC0, 0040
ACPI: SSDT BD5FC1DF, 034F (r1 FUJ    FJNB1E6   1160000 FUJ       100)
ACPI: HPET BD5FC622, 0038 (r1 FUJ    FJNB1E6   1160000 FUJ       100)
ACPI: MCFG BD5FC65A, 003C (r1 FUJ    FJNB1E6   1160000 FUJ       100)
ACPI: SSDT BD5FC696, 042F (r1 FUJ    FJNB1E6   1160000 FUJ       100)
ACPI: SSDT BD5FCAC5, 02C1 (r1 FUJ    FJNB1E6   1160000 FUJ       100)
ACPI: APIC BD5FCD86, 0068 (r1 FUJ    FJNB1E6   1160000 FUJ       100)
ACPI: BOOT BD5FCDEE, 0028 (r1 FUJ    FJNB1E6   1160000 FUJ       100)
ACPI: SLIC BD5FCE16, 0176 (r1 FSC    PC        1160000 FUJ       100)
ACPI: SSDT BD5E5000, 04E6 (r1  PmRef    CpuPm     3000 INTL 20050624)
ACPI: Local APIC address 0xfee00000
(5 early reservations) ==> bootmem [0000000000 - 00bd600000]
  #0 [0000000000 - 0000001000]   BIOS data page ==> [0000000000 - 0000001000]
  #1 [0000006000 - 0000008000]       TRAMPOLINE ==> [0000006000 - 0000008000]
  #2 [0000200000 - 00009f3dec]    TEXT DATA BSS ==> [0000200000 - 00009f3dec]
  #3 [000009d400 - 0000100000]    BIOS reserved ==> [000009d400 - 0000100000]
  #4 [0000008000 - 000000a000]          PGTABLE ==> [0000008000 - 000000a000]
 [ffffe20000000000-ffffe200029fffff] PMD -> [ffff880001200000-ffff880003bfffff] on node 0
Zone PFN ranges:
  DMA      0x00000000 -> 0x00001000
  DMA32    0x00001000 -> 0x00100000
  Normal   0x00100000 -> 0x00100000
Movable zone start PFN for each node
early_node_map[8] active PFN ranges
    0: 0x00000000 -> 0x0000009d
    0: 0x00000100 -> 0x000bce51
    0: 0x000bce57 -> 0x000bd058
    0: 0x000bd0af -> 0x000bd1a8
    0: 0x000bd4af -> 0x000bd4d8
    0: 0x000bd4df -> 0x000bd535
    0: 0x000bd57f -> 0x000bd5e4
    0: 0x000bd5fd -> 0x000bd600
On node 0 totalpages: 774607
  DMA zone: 56 pages used for memmap
  DMA zone: 2138 pages reserved
  DMA zone: 1803 pages, LIFO batch:0
  DMA32 zone: 10549 pages used for memmap
  DMA32 zone: 760061 pages, LIFO batch:31
ACPI: PM-Timer IO Port: 0x408
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 0, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Using ACPI (MADT) for SMP configuration information
ACPI: HPET id: 0x8086a201 base: 0xfed00000
SMP: Allowing 2 CPUs, 0 hotplug CPUs
Allocating PCI resources starting at c2000000 (gap: c0000000:20000000)
NR_CPUS:2 nr_cpumask_bits:2 nr_cpu_ids:2 nr_node_ids:1
PERCPU: Allocating 49152 bytes of per cpu data
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 761864
Kernel command line: auto BOOT_IMAGE=2.6.29-rc4-0002 rw root=0 video=vesafb:ywrap,pmipal,mtrr
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
Extended CMOS year: 2000
Fast TSC calibration using PIT
Detected 2527.066 MHz processor.
Console: colour VGA+ 80x25
console [tty0] enabled
Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
Checking aperture...
No AGP bridge found
Memory: 3040120k/3102720k available (4161k kernel code, 4292k absent, 57580k reserved, 1977k data, 1428k init)
SLUB: Genslabs=12, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
hpet clockevent registered
HPET: 4 timers in total, 0 timers will be used for per-cpu timer
Calibrating delay loop (skipped), value calculated using timer frequency.. 5056.72 BogoMIPS (lpj=8423553)
Mount-cache hash table entries: 256
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 6144K
[ds] using Core 2/Atom configuration
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
CPU0: Thermal monitoring enabled (TM2)
using mwait in idle threads.
Freeing SMP alternatives: 37k freed
ACPI: Core revision 20081204
Setting APIC routing to flat
..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
CPU0: Intel(R) Core(TM)2 Duo CPU     T9400  @ 2.53GHz stepping 06
Booting processor 1 APIC 0x1 ip 0x6000
Initializing CPU#1
Calibrating delay using timer specific routine.. 5055.55 BogoMIPS (lpj=8423288)
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 6144K
[ds] using Core 2/Atom configuration
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 1
CPU1: Thermal monitoring enabled (TM2)
x86 PAT enabled: cpu 1, old 0x7040600070406, new 0x7010600070106
CPU1: Intel(R) Core(TM)2 Duo CPU     T9400  @ 2.53GHz stepping 06
checking TSC synchronization [CPU#0 -> CPU#1]: passed.
Brought up 2 CPUs
Total of 2 processors activated (10112.27 BogoMIPS).
net_namespace: 960 bytes
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
PCI: MCFG area at e0000000 reserved in E820
PCI: Using MMCONFIG at e0000000 - efffffff
PCI: Using configuration type 1 for base access
mtrr: your CPUs had inconsistent variable MTRR settings
mtrr: probably your BIOS does not setup all CPUs.
mtrr: corrected configuration.
bio: create slab <bio-0> at 0
ACPI: EC: Look up EC in DSDT
ACPI: SSDT BD56E965, 03F1 (r1 FUJ    FJNB1E6   1160000 FUJ       100)
ACPI: Interpreter enabled
ACPI: (supports S0 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI: EC: GPE = 0x17, I/O: command/status = 0x66, data = 0x62
ACPI: EC: driver started in poll mode
ACPI: ACPI Dock Station Driver: 2 docks/bays found
ACPI: PCI Root Bridge [PCI0] (0000:00)
pci 0000:00:02.0: reg 10 64bit mmio: [0xf0000000-0xf03fffff]
pci 0000:00:02.0: reg 18 64bit mmio: [0xd0000000-0xdfffffff]
pci 0000:00:02.0: reg 20 io port: [0x1800-0x1807]
pci 0000:00:02.1: reg 10 64bit mmio: [0xf0400000-0xf04fffff]
pci 0000:00:1a.0: reg 20 io port: [0x1820-0x183f]
pci 0000:00:1a.1: reg 20 io port: [0x1840-0x185f]
pci 0000:00:1a.2: reg 20 io port: [0x1860-0x187f]
pci 0000:00:1a.7: reg 10 32bit mmio: [0xf0a04800-0xf0a04bff]
pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
pci 0000:00:1a.7: PME# disabled
pci 0000:00:1b.0: reg 10 64bit mmio: [0xf0a00000-0xf0a03fff]
pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1b.0: PME# disabled
pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.0: PME# disabled
pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.2: PME# disabled
pci 0000:00:1d.0: reg 20 io port: [0x1880-0x189f]
pci 0000:00:1d.1: reg 20 io port: [0x18a0-0x18bf]
pci 0000:00:1d.2: reg 20 io port: [0x18c0-0x18df]
pci 0000:00:1d.7: reg 10 32bit mmio: [0xf0a04c00-0xf0a04fff]
pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
pci 0000:00:1d.7: PME# disabled
pci 0000:00:1f.2: reg 10 io port: [0x1818-0x181f]
pci 0000:00:1f.2: reg 14 io port: [0x180c-0x180f]
pci 0000:00:1f.2: reg 18 io port: [0x1810-0x1817]
pci 0000:00:1f.2: reg 1c io port: [0x1808-0x180b]
pci 0000:00:1f.2: reg 20 io port: [0x18e0-0x18ff]
pci 0000:00:1f.2: reg 24 32bit mmio: [0xf0a04000-0xf0a047ff]
pci 0000:00:1f.2: PME# supported from D3hot
pci 0000:00:1f.2: PME# disabled
pci 0000:00:1f.3: reg 10 64bit mmio: [0x000000-0x0000ff]
pci 0000:00:1f.3: reg 20 io port: [0x1c00-0x1c1f]
pci 0000:08:00.0: reg 10 64bit mmio: [0xf0500000-0xf0503fff]
pci 0000:08:00.0: reg 18 io port: [0x2000-0x20ff]
pci 0000:08:00.0: reg 30 32bit mmio: [0x000000-0x01ffff]
pci 0000:08:00.0: supports D1 D2
pci 0000:08:00.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:08:00.0: PME# disabled
pci 0000:00:1c.0: bridge io port: [0x2000-0x2fff]
pci 0000:00:1c.0: bridge 32bit mmio: [0xf0500000-0xf05fffff]
pci 0000:18:00.0: reg 10 64bit mmio: [0xf0600000-0xf0601fff]
pci 0000:18:00.0: PME# supported from D0 D3hot D3cold
pci 0000:18:00.0: PME# disabled
pci 0000:00:1c.2: bridge 32bit mmio: [0xf0600000-0xf06fffff]
pci 0000:38:03.0: reg 10 32bit mmio: [0x000000-0x000fff]
pci 0000:38:03.0: supports D1 D2
pci 0000:38:03.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:38:03.0: PME# disabled
pci 0000:38:03.2: reg 10 32bit mmio: [0xf0700000-0xf07000ff]
pci 0000:38:03.2: supports D1 D2
pci 0000:38:03.2: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:38:03.2: PME# disabled
pci 0000:38:03.3: reg 10 32bit mmio: [0xf0701000-0xf0701fff]
pci 0000:38:03.3: supports D1 D2
pci 0000:38:03.3: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:38:03.3: PME# disabled
pci 0000:38:03.4: reg 10 32bit mmio: [0xf0702000-0xf0702fff]
pci 0000:38:03.4: reg 14 32bit mmio: [0xf0700800-0xf0700fff]
pci 0000:38:03.4: supports D1 D2
pci 0000:38:03.4: PME# supported from D0 D1 D2 D3hot
pci 0000:38:03.4: PME# disabled
pci 0000:00:1e.0: transparent bridge
pci 0000:00:1e.0: bridge 32bit mmio: [0xf0700000-0xf07fffff]
pci_bus 0000:00: on NUMA node 0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP01._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP03._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIB._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 10 12 14 15) *11
ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 7 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 10 12 14 15) *11
ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 1 3 4 5 6 7 10 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 1 3 4 5 6 7 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKG] (IRQs 1 3 4 5 6 7 10 12 14 15) *11
ACPI: PCI Interrupt Link [LNKH] (IRQs 1 3 4 5 6 7 *11 12 14 15)
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Using ACPI for IRQ routing
Bluetooth: Core ver 2.14
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
cfg80211: Calling CRDA to update world regulatory domain
cfg80211: calling CRDA failed - unable to update world regulatory domain, using static definition
hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0
hpet0: 4 comparators, 64-bit 14.318180 MHz counter
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 14 devices
ACPI: ACPI bus type pnp unregistered
system 00:01: ioport range 0x400-0x47f has been reserved
system 00:01: ioport range 0x480-0x48f has been reserved
system 00:01: ioport range 0x4d0-0x4d1 has been reserved
system 00:01: ioport range 0x680-0x69f has been reserved
system 00:01: ioport range 0x800-0x80f has been reserved
system 00:01: ioport range 0xf40-0xf41 has been reserved
system 00:01: ioport range 0x1100-0x111f has been reserved
system 00:01: ioport range 0x1180-0x11ff has been reserved
system 00:01: ioport range 0x1640-0x164f has been reserved
system 00:01: ioport range 0xf800-0xf87f has been reserved
system 00:01: ioport range 0xf880-0xf8ff has been reserved
system 00:01: ioport range 0xfc00-0xfc7f has been reserved
system 00:01: ioport range 0xfc80-0xfcff has been reserved
system 00:01: ioport range 0xfd00-0xfd7f has been reserved
system 00:02: iomem range 0xfed1c000-0xfed1ffff has been reserved
system 00:02: iomem range 0xfed10000-0xfed13fff has been reserved
system 00:02: iomem range 0xfed18000-0xfed18fff has been reserved
system 00:02: iomem range 0xfed19000-0xfed19fff has been reserved
system 00:02: iomem range 0xe0000000-0xefffffff has been reserved
system 00:02: iomem range 0xfed20000-0xfed3ffff has been reserved
system 00:02: iomem range 0xfed45000-0xfed8ffff has been reserved
system 00:02: iomem range 0xfef00000-0xfeffffff has been reserved
system 00:0a: iomem range 0xfed00000-0xfed003ff has been reserved
pci 0000:00:1c.0: PCI bridge, secondary bus 0000:08
pci 0000:00:1c.0:   IO window: 0x2000-0x2fff
pci 0000:00:1c.0:   MEM window: 0xf0500000-0xf05fffff
pci 0000:00:1c.0:   PREFETCH window: 0x000000c2000000-0x000000c20fffff
pci 0000:00:1c.2: PCI bridge, secondary bus 0000:18
pci 0000:00:1c.2:   IO window: disabled
pci 0000:00:1c.2:   MEM window: 0xf0600000-0xf06fffff
pci 0000:00:1c.2:   PREFETCH window: disabled
pci 0000:38:03.0: CardBus bridge, secondary bus 0000:39
pci 0000:38:03.0:   IO window: 0x003000-0x0030ff
pci 0000:38:03.0:   IO window: 0x003400-0x0034ff
pci 0000:38:03.0:   PREFETCH window: 0xc4000000-0xc7ffffff
pci 0000:38:03.0:   MEM window: 0xc8000000-0xcbffffff
pci 0000:00:1e.0: PCI bridge, secondary bus 0000:38
pci 0000:00:1e.0:   IO window: 0x3000-0x3fff
pci 0000:00:1e.0:   MEM window: 0xf0700000-0xf07fffff
pci 0000:00:1e.0:   PREFETCH window: 0x000000c4000000-0x000000c7ffffff
pci 0000:00:1c.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
pci 0000:00:1c.0: setting latency timer to 64
pci 0000:00:1c.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
pci 0000:00:1c.2: setting latency timer to 64
pci 0000:00:1e.0: setting latency timer to 64
pci 0000:38:03.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
pci_bus 0000:00: resource 0 io:  [0x00-0xffff]
pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffffffffffff]
pci_bus 0000:08: resource 0 io:  [0x2000-0x2fff]
pci_bus 0000:08: resource 1 mem: [0xf0500000-0xf05fffff]
pci_bus 0000:08: resource 2 mem: [0xc2000000-0xc20fffff]
pci_bus 0000:08: resource 3 mem: [0x0-0x0]
pci_bus 0000:18: resource 0 mem: [0x0-0x0]
pci_bus 0000:18: resource 1 mem: [0xf0600000-0xf06fffff]
pci_bus 0000:18: resource 2 mem: [0x0-0x0]
pci_bus 0000:18: resource 3 mem: [0x0-0x0]
pci_bus 0000:38: resource 0 io:  [0x3000-0x3fff]
pci_bus 0000:38: resource 1 mem: [0xf0700000-0xf07fffff]
pci_bus 0000:38: resource 2 mem: [0xc4000000-0xc7ffffff]
pci_bus 0000:38: resource 3 io:  [0x00-0xffff]
pci_bus 0000:38: resource 4 mem: [0x000000-0xffffffffffffffff]
pci_bus 0000:39: resource 0 io:  [0x3000-0x30ff]
pci_bus 0000:39: resource 1 io:  [0x3400-0x34ff]
pci_bus 0000:39: resource 2 mem: [0xc4000000-0xc7ffffff]
pci_bus 0000:39: resource 3 mem: [0xc8000000-0xcbffffff]
NET: Registered protocol family 2
IP route cache hash table entries: 131072 (order: 8, 1048576 bytes)
TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
TCP reno registered
NET: Registered protocol family 1
Simple Boot Flag at 0x7b set to 0x1
Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
NTFS driver 2.1.29 [Flags: R/O].
fuse init (API version 7.11)
msgmni has been set to 5939
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci 0000:00:02.0: Boot video device
pcieport-driver 0000:00:1c.0: setting latency timer to 64
pcieport-driver 0000:00:1c.0: irq 24 for MSI/MSI-X
pcieport-driver 0000:00:1c.2: setting latency timer to 64
pcieport-driver 0000:00:1c.2: irq 25 for MSI/MSI-X
ACPI: AC Adapter [AC] (on-line)
ACPI: EC: non-query interrupt received, switching to interrupt mode
ACPI: Battery Slot [CMB1] (battery present)
ACPI: Battery Slot [CMB2] (battery absent)
input: Power Button (FF) as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
ACPI: Power Button (FF) [PWRF]
input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input1
ACPI: Lid Switch [LID]
input: Power Button (CM) as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input2
ACPI: Power Button (CM) [PWRB]
input: Sleep Button (CM) as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input3
ACPI: Sleep Button (CM) [SLPB]
acpi device:05: registered as cooling_device0
input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:03/input/input4
ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
ACPI: Invalid PBLK length [8]
ACPI: SSDT BD4DAC20, 0265 (r1  PmRef  Cpu0Ist     3000 INTL 20050624)
ACPI: SSDT BD4D86A0, 05CC (r1  PmRef  Cpu0Cst     3001 INTL 20050624)
Monitor-Mwait will be used to enter C-1 state
Monitor-Mwait will be used to enter C-2 state
ACPI: CPU0 (power states: C1[C1] C2[C2])
processor ACPI_CPU:00: registered as cooling_device1
ACPI: Invalid PBLK length [8]
ACPI: SSDT BD4D9DA0, 00FD (r1  PmRef    ApIst     3000 INTL 20050624)
ACPI: SSDT BD4DCF20, 0047 (r1  PmRef    ApCst     3000 INTL 20050624)
ACPI: CPU1 (power states: C1[C1] C2[C2])
processor ACPI_CPU:01: registered as cooling_device2
thermal LNXTHERM:01: registered as thermal_zone0
ACPI: Thermal Zone [TZ00] (27 C)
thermal LNXTHERM:02: registered as thermal_zone1
ACPI: Thermal Zone [TZ01] (27 C)
Real Time Clock Driver v1.12b
Non-volatile memory driver v1.3
Linux agpgart interface v0.103
agpgart-intel 0000:00:00.0: Intel Mobile Intel® GM45 Express Chipset
agpgart-intel 0000:00:00.0: detected 32764K stolen memory
agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xd0000000
tpm_tis 00:03: 1.2 TPM (device-id 0xB, rev-id 16)
Switched to high resolution mode on CPU 1
Switched to high resolution mode on CPU 0
tpm_tis 00:03: Operation Timed out
[drm] Initialized drm 1.1.0 20060810
pci 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
pci 0000:00:02.0: setting latency timer to 64
pci 0000:00:02.0: irq 26 for MSI/MSI-X
[drm] Initialized i915 1.6.0 20080730 on minor 0
intelfb: intelfb_init
intelfb: Framebuffer driver for Intel(R) 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/945GME/965G/965GM chipsets
intelfb: Version 0.9.6
intelfb: intelfb_setup
intelfb: no options
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:0b: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
loop: module loaded
sky2 driver version 1.22
sky2 0000:08:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
sky2 0000:08:00.0: setting latency timer to 64
sky2 0000:08:00.0: Yukon-2 EC Ultra chip revision 3
sky2 0000:08:00.0: Marvell Yukon 88E8055 Gigabit Ethernet Controller
 Part Number: 88E8055
 Engineering Level: Rev. 1.4
 Manufacturer: Marvell
sky2 0000:08:00.0: irq 27 for MSI/MSI-X
sky2 eth0: addr 00:17:42:c8:5a:90
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27kds
iwlagn: Copyright(c) 2003-2008 Intel Corporation
iwlagn 0000:18:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
iwlagn 0000:18:00.0: setting latency timer to 64
iwlagn: Detected Intel Wireless WiFi Link 5300AGN REV=0x24
iwlagn: Tunable channels: 13 802.11bg, 24 802.11a channels
iwlagn 0000:18:00.0: PCI INT A disabled
wmaster0 (iwlagn): not using net_device_ops yet
phy0: Selected rate control algorithm 'iwl-agn-rs'
wlan0 (iwlagn): not using net_device_ops yet
Linux video capture interface: v2.00
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v0.1.0)
Driver 'sd' needs updating - please use bus_type methods
Driver 'sr' needs updating - please use bus_type methods
ahci 0000:00:1f.2: version 3.0
ahci 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
ahci 0000:00:1f.2: irq 28 for MSI/MSI-X
ahci: SSS flag set, parallel bus scan disabled
ahci 0000:00:1f.2: AHCI 0001.0200 32 slots 4 ports 3 Gbps 0x3 impl SATA mode
ahci 0000:00:1f.2: flags: 64bit ncq sntf stag pm led clo pmp pio slum part 
ahci 0000:00:1f.2: setting latency timer to 64
scsi0 : ahci
scsi1 : ahci
scsi2 : ahci
scsi3 : ahci
ata1: SATA max UDMA/133 abar m2048@0xf0a04000 port 0xf0a04100 irq 28
ata2: SATA max UDMA/133 abar m2048@0xf0a04000 port 0xf0a04180 irq 28
ata3: DUMMY
ata4: DUMMY
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: ACPI cmd ef/10:03:00:00:00:a0 filtered out
ata1.00: ACPI cmd f5/00:00:00:00:00:a0 filtered out
ata1.00: ATA-8: Hitachi HTS543232L9A300, FB4OC40C, max UDMA/133
ata1.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata1.00: ACPI cmd ef/10:03:00:00:00:a0 filtered out
ata1.00: ACPI cmd f5/00:00:00:00:00:a0 filtered out
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access     ATA      Hitachi HTS54323 FB4O PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 625142448 512-byte hardware sectors: (320 GB/298 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] 625142448 512-byte hardware sectors: (320 GB/298 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1 sda2 sda3
sd 0:0:0:0: [sda] Attached SCSI disk
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.00: ACPI cmd ef/90:03:00:00:00:a0 rejected by device (Stat=0x51 Err=0x04)
ata2.00: ACPI cmd 00/00:00:00:00:00:a0 rejected by device (Stat=0x51 Err=0x04)
ata2.00: ATAPI: MATSHITADVD-RAM UJ862BJ, 1.00, max UDMA/33
ata2.00: ACPI cmd ef/90:03:00:00:00:a0 rejected by device (Stat=0x51 Err=0x04)
ata2.00: ACPI cmd 00/00:00:00:00:00:a0 rejected by device (Stat=0x51 Err=0x04)
ata2.00: configured for UDMA/33
scsi 1:0:0:0: CD-ROM            MATSHITA DVD-RAM UJ862BJ  1.00 PQ: 0 ANSI: 5
sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 1:0:0:0: Attached scsi CD-ROM sr0
firewire_ohci 0000:38:03.4: PCI INT A -> GSI 17 (level, low) -> IRQ 17
firewire_ohci: Added fw-ohci device 0000:38:03.4, OHCI version 1.10
yenta_cardbus 0000:38:03.0: CardBus bridge found [10cf:143d]
yenta_cardbus 0000:38:03.0: O2: res at 0x94/0xD4: 00/ea
yenta_cardbus 0000:38:03.0: O2: enabling read prefetch/write burst
yenta_cardbus 0000:38:03.0: ISA IRQ mask 0x0cb8, PCI irq 17
yenta_cardbus 0000:38:03.0: Socket status: 30000006
pci_bus 0000:38: Raising subordinate bus# of parent bus (#38) from #39 to #3c
yenta_cardbus 0000:38:03.0: pcmcia: parent PCI bridge I/O window: 0x3000 - 0x3fff
yenta_cardbus 0000:38:03.0: pcmcia: parent PCI bridge Memory window: 0xf0700000 - 0xf07fffff
yenta_cardbus 0000:38:03.0: pcmcia: parent PCI bridge Memory window: 0xc4000000 - 0xc7ffffff
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 18 (level, low) -> IRQ 18
ehci_hcd 0000:00:1a.7: setting latency timer to 64
ehci_hcd 0000:00:1a.7: EHCI Host Controller
ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1a.7: debug port 1
ehci_hcd 0000:00:1a.7: cache line size of 32 is not supported
ehci_hcd 0000:00:1a.7: irq 18, io mem 0xf0a04800
ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 6 ports detected
ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23
ehci_hcd 0000:00:1d.7: setting latency timer to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2
ehci_hcd 0000:00:1d.7: debug port 1
ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported
ehci_hcd 0000:00:1d.7: irq 23, io mem 0xf0a04c00
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 6 ports detected
uhci_hcd: USB Universal Host Controller Interface driver
uhci_hcd 0000:00:1a.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
uhci_hcd 0000:00:1a.0: setting latency timer to 64
uhci_hcd 0000:00:1a.0: UHCI Host Controller
uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1a.0: irq 16, io base 0x00001820
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
uhci_hcd 0000:00:1a.1: setting latency timer to 64
uhci_hcd 0000:00:1a.1: UHCI Host Controller
uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1a.1: irq 17, io base 0x00001840
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
uhci_hcd 0000:00:1a.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
uhci_hcd 0000:00:1a.2: setting latency timer to 64
uhci_hcd 0000:00:1a.2: UHCI Host Controller
uhci_hcd 0000:00:1a.2: new USB bus registered, assigned bus number 5
uhci_hcd 0000:00:1a.2: irq 18, io base 0x00001860
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
uhci_hcd 0000:00:1d.0: setting latency timer to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 6
uhci_hcd 0000:00:1d.0: irq 23, io base 0x00001880
usb usb6: configuration #1 chosen from 1 choice
hub 6-0:1.0: USB hub found
hub 6-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
uhci_hcd 0000:00:1d.1: setting latency timer to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 7
uhci_hcd 0000:00:1d.1: irq 19, io base 0x000018a0
usb usb7: configuration #1 chosen from 1 choice
hub 7-0:1.0: USB hub found
hub 7-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
uhci_hcd 0000:00:1d.2: setting latency timer to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 8
uhci_hcd 0000:00:1d.2: irq 18, io base 0x000018c0
usb usb8: configuration #1 chosen from 1 choice
hub 8-0:1.0: USB hub found
hub 8-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbserial
usbserial: USB Serial Driver core
USB Serial support registered for pl2303
usbcore: registered new interface driver pl2303
pl2303: Prolific PL2303 USB to serial adaptor driver
USB Serial support registered for Sierra USB modem
usbcore: registered new interface driver sierra
sierra: v.1.3.2:USB Driver for Sierra Wireless USB modems
PNP: PS/2 Controller [PNP0303:KBC,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
i8042.c: Detected active multiplexing controller, rev 1.1.
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX0 port at 0x60,0x64 irq 12
serio: i8042 AUX1 port at 0x60,0x64 irq 12
serio: i8042 AUX2 port at 0x60,0x64 irq 12
serio: i8042 AUX3 port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
input: PC Speaker as /devices/platform/pcspkr/input/input5
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.04
iTCO_wdt: Found a ICH9M TCO device (Version=2, TCOBASE=0x0460)
iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.14.0-ioctl (2008-04-23) initialised: dm-devel@redhat.com
Bluetooth: Generic Bluetooth USB driver ver 0.4
usbcore: registered new interface driver btusb
cpuidle: using governor ladder
cpuidle: using governor menu
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pci 0000:38:03.2: SDHCI controller found [1217:7120] (rev 2)
sdhci-pci 0000:38:03.2: PCI INT A -> GSI 17 (level, low) -> IRQ 17
mmc0: Unknown controller version (2). You may experience problems.
Marking TSC unstable due to TSC halts in idle
Registered led device: mmc0
mmc0: SDHCI controller on PCI [0000:38:03.2] using DMA
firewire_core: created device fw0: GUID 00000e1003fdee54, S400
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input6
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.18a.
HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
HDA Intel 0000:00:1b.0: setting latency timer to 64
usb 1-5: new high speed USB device using ehci_hcd and address 2
usb 1-5: configuration #1 chosen from 1 choice
hub 1-5:1.0: USB hub found
hub 1-5:1.0: 4 ports detected
usb 2-4: new high speed USB device using ehci_hcd and address 4
usb 2-4: configuration #1 chosen from 1 choice
uvcvideo: Found UVC 1.00 device OEM Camera (046d:09b2)
input: OEM Camera as /devices/pci0000:00/0000:00:1d.7/usb2/2-4/2-4:1.0/input/input7
Synaptics Touchpad, model: 1, fw: 7.2, id: 0x1c0b1, caps: 0xd04731/0xa42000
input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio4/input/input8
ALSA sound/pci/hda/hda_intel.c:633: hda_intel: azx_get_response timeout, switching to polling mode: last cmd=0x020c0000
hda-codec: No codec parser is available
ALSA device list:
  #0: HDA Intel at 0xf0a00000 irq 22
TCP cubic registered
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
Bluetooth: L2CAP ver 2.11
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO (Voice Link) ver 0.6
Bluetooth: SCO socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.10
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
BIOS EDD facility v0.16 2004-Jun-25, 1 devices found
Freeing unused kernel memory: 1428k freed
Write protecting the kernel read-only data: 5580k
usb 6-1: new full speed USB device using uhci_hcd and address 2
usb 6-1: configuration #1 chosen from 1 choice
usb 6-2: new full speed USB device using uhci_hcd and address 3
usb 6-2: configuration #1 chosen from 1 choice
usb 1-5.1: new full speed USB device using ehci_hcd and address 3
usb 1-5.1: configuration #1 chosen from 1 choice
hub 1-5.1:1.0: USB hub found
hub 1-5.1:1.0: 3 ports detected
usb 1-5.2: new low speed USB device using ehci_hcd and address 4
usb 1-5.2: configuration #1 chosen from 1 choice
generic-usb 0003:0A81:0701.0001: claimed by neither input, hiddev nor hidraw
usb 1-5.4: new full speed USB device using ehci_hcd and address 5
usb 1-5.4: configuration #1 chosen from 1 choice
usb 1-5.1.1: new full speed USB device using ehci_hcd and address 6
usb 1-5.1.1: configuration #1 chosen from 1 choice
hub 1-5.1.1:1.0: USB hub found
hub 1-5.1.1:1.0: 4 ports detected
usb 1-5.1.2: new low speed USB device using ehci_hcd and address 7
usb 1-5.1.2: configuration #1 chosen from 1 choice
input: Belkin Corporation Flip KVM as /devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.1/1-5.1.2/1-5.1.2:1.0/input/input9
belkin 0003:050D:3201.0002: input: USB HID v1.10 Device [Belkin Corporation Flip KVM] on usb-0000:00:1a.7-5.1.2/input0
usb 1-5.1.3: new full speed USB device using ehci_hcd and address 8
hub 1-5.1:1.0: unable to enumerate USB device on port 3
usb 1-5.1.1.1: new low speed USB device using ehci_hcd and address 9
usb 1-5.1.1.1: configuration #1 chosen from 1 choice
input: G15 Gaming Keyboard as /devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.1/1-5.1.1/1-5.1.1.1/1-5.1.1.1:1.0/input/input10
generic-usb 0003:046D:C226.0003: input: USB HID v1.10 Keyboard [G15 Gaming Keyboard] on usb-0000:00:1a.7-5.1.1.1/input0
input: G15 Gaming Keyboard as /devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.1/1-5.1.1/1-5.1.1.1/1-5.1.1.1:1.1/input/input11
generic-usb 0003:046D:C226.0004: input: USB HID v1.10 Device [G15 Gaming Keyboard] on usb-0000:00:1a.7-5.1.1.1/input1
usb 1-5.1.1.4: new full speed USB device using ehci_hcd and address 10
usb 1-5.1.1.4: configuration #1 chosen from 1 choice
input: G15 GamePanel LCD as /devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.1/1-5.1.1/1-5.1.1.4/1-5.1.1.4:1.0/input/input12
generic-usb 0003:046D:C227.0005: input: USB HID v1.11 Keypad [G15 GamePanel LCD] on usb-0000:00:1a.7-5.1.1.4/input0
usb 1-6: new high speed USB device using ehci_hcd and address 11
usb 1-6: configuration #1 chosen from 1 choice
sierra 1-6:1.0: Sierra USB modem converter detected
usb 1-6: Sierra USB modem converter now attached to ttyUSB0
sierra 1-6:1.1: Sierra USB modem converter detected
usb 1-6: Sierra USB modem converter now attached to ttyUSB1
sierra 1-6:1.2: Sierra USB modem converter detected
usb 1-6: Sierra USB modem converter now attached to ttyUSB2
sierra 1-6:1.3: Sierra USB modem converter detected
usb 1-6: Sierra USB modem converter now attached to ttyUSB3
sierra 1-6:1.4: Sierra USB modem converter detected
usb 1-6: Sierra USB modem converter now attached to ttyUSB4
sierra 1-6:1.5: Sierra USB modem converter detected
usb 1-6: Sierra USB modem converter now attached to ttyUSB5
sierra 1-6:1.6: Sierra USB modem converter detected
usb 1-6: Sierra USB modem converter now attached to ttyUSB6
usb 1-5.1.3: new full speed USB device using ehci_hcd and address 12
usb 1-5.1.3: configuration #1 chosen from 1 choice
input: Razer Razer Copperhead Laser Mouse as /devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.1/1-5.1.3/1-5.1.3:1.0/input/input13
generic-usb 0003:1532:0101.0006: input: USB HID v1.00 Mouse [Razer Razer Copperhead Laser Mouse] on usb-0000:00:1a.7-5.1.3/input0
input: Razer Razer Copperhead Laser Mouse as /devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.1/1-5.1.3/1-5.1.3:1.1/input/input14
generic-usb 0003:1532:0101.0007: input: USB HID v0.01 Keyboard [Razer Razer Copperhead Laser Mouse] on usb-0000:00:1a.7-5.1.3/input1
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
fujitsu-laptop: Identified laptop model 'Fujitsu Siemens S6420'.
input: Fujitsu FUJ02B1 as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:3f/FUJ02B1:00/input/input15
ACPI: Fujitsu FUJ02B1 [FJEX] (on)
input: Fujitsu FUJ02E3 as /devices/LNXSYSTM:00/device:00/FUJ02E3:00/input/input16
ACPI: Fujitsu FUJ02E3 [FEXT] (on)
fujitsu-laptop: BTNI: [0xff0101]
fujitsu-laptop: driver 0.5.0 successfully loaded.
gspca: main v2.4.0 registered
gspca: probing 0ac8:307b
zc3xx: probe 2wr ov vga 0x0000
zc3xx: probe 3wr vga 1 0x4001
zc3xx: probe 3wr vga 2 0x0000
zc3xx: Sensor UNKNOW_0 force Tas5130
gspca: probe ok
usbcore: registered new interface driver zc3xx
zc3xx: registered
EXT3 FS on dm-0, internal journal
input: G15 Extra Keys as /devices/virtual/input/input17
sky2 eth0: enabling interface
ADDRCONF(NETDEV_UP): eth0: link is not ready
iwlagn 0000:18:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
iwlagn 0000:18:00.0: restoring config space at offset 0x1 (was 0x100102, writing 0x100106)
iwlagn 0000:18:00.0: irq 29 for MSI/MSI-X
iwlagn 0000:18:00.0: firmware: requesting iwlwifi-5000-1.ucode
iwlagn loaded firmware version 5.4.1.16
ADDRCONF(NETDEV_UP): wlan0: link is not ready
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control rx
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
eth0: no IPv6 routers present
wlan0: direct probe to AP 00:1e:f7:ea:d1:60 try 1
wlan0 direct probe responded
wlan0: authenticate with AP 00:1e:f7:ea:d1:60
wlan0: authenticated
wlan0: associate with AP 00:1e:f7:ea:d1:60
wlan0: RX AssocResp from 00:1e:f7:ea:d1:60 (capab=0x431 status=0 aid=3)
wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
cfg80211: Calling CRDA for country: GB
cfg80211: Received country IE:
cfg80211: Regulatory domain: GB
	(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
	(2402000 KHz - 2494000 KHz @ 40000 KHz), (10000 mBi, 10000 mBm)
cfg80211: CRDA thinks this should applied:
cfg80211: Regulatory domain: GB
	(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
	(2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
	(5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm)
	(5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm)
	(5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm)
cfg80211: We intersect both of these and get:
cfg80211: Regulatory domain: 98
	(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
	(2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
cfg80211: Leaving channel 5180 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5200 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5220 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5240 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5260 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5280 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5300 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5320 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5500 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5520 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5540 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5560 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5580 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5600 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5620 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5640 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5660 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5680 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5700 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5745 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5765 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5785 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5805 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5825 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Current regulatory domain updated by AP to: GB
	(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
	(2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
wlan0: no IPv6 routers present
cfg80211: Calling CRDA for country: GB
cfg80211: Current regulatory intersected: 
	(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
	(2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
cfg80211: Calling CRDA for country: GB
cfg80211: Received country IE:
cfg80211: Regulatory domain: GB
	(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
	(2402000 KHz - 2494000 KHz @ 40000 KHz), (10000 mBi, 10000 mBm)
cfg80211: CRDA thinks this should applied:
cfg80211: Regulatory domain: GB
	(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
	(2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
	(5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm)
	(5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm)
	(5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm)
cfg80211: We intersect both of these and get:
cfg80211: Regulatory domain: 98
	(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
	(2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
cfg80211: Leaving channel 5180 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5200 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5220 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5240 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5260 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5280 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5300 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5320 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5500 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5520 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5540 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5560 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5580 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5600 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5620 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5640 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5660 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5680 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5700 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5745 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5765 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5785 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5805 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5825 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Current regulatory domain updated by AP to: GB
	(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
	(2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: IWL5300, 2.6.29-rc4, CRDA 1.0.1: Missing out 802.11A frequency ranges
  2009-02-09 19:21       ` Tony Vroon
@ 2009-02-09 19:35         ` Tony Vroon
  2009-02-10  1:39           ` Luis R. Rodriguez
  0 siblings, 1 reply; 20+ messages in thread
From: Tony Vroon @ 2009-02-09 19:35 UTC (permalink / raw)
  To: Luis R. Rodriguez; +Cc: linux-wireless, reinette chatre, John W. Linville

[-- Attachment #1: Type: text/plain, Size: 420 bytes --]

Do correct me if I'm missing something here, but:
cfg80211: Leaving channel 5180 MHz intact on phy0 - no rule found in
band on Country IE

How will leaving the channel intact help, if the static world domain
turned it off in the first place? (Note that the CRDA request for the
world domain is emitted by the kernel before /dev/sda is even attached,
so needless to say that goes unserviced)

Regards,
Tony V.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: IWL5300, 2.6.29-rc4, CRDA 1.0.1: Missing out 802.11A frequency ranges
  2009-02-09 19:35         ` Tony Vroon
@ 2009-02-10  1:39           ` Luis R. Rodriguez
  2009-02-10  1:51             ` Tony Vroon
  0 siblings, 1 reply; 20+ messages in thread
From: Luis R. Rodriguez @ 2009-02-10  1:39 UTC (permalink / raw)
  To: Tony Vroon
  Cc: Luis Rodriguez, linux-wireless, reinette chatre, John W. Linville

On Mon, Feb 09, 2009 at 11:35:52AM -0800, Tony Vroon wrote:
> Do correct me if I'm missing something here, but:
> cfg80211: Leaving channel 5180 MHz intact on phy0 - no rule found in
> band on Country IE

Looks good.

> How will leaving the channel intact help, if the static world domain
> turned it off in the first place?

In Intel's case the first regulatory domain is ignored (world). To see,
before associating to an AP try running 'iw list'.

> (Note that the CRDA request for the
> world domain is emitted by the kernel before /dev/sda is even attached,
> so needless to say that goes unserviced)

I noticed that, what ends up happening then is the static world regulatory
domain is used from the kernel. I take it you used an initramfs with the
sda driver in there? I've been using initramfs too but for some reason
on my system udev triggers the request eventually after the drive
is mounted. So this is the first time I hear of this.

I also noticed though:

cfg80211: Calling CRDA for country: GB
cfg80211: Current regulatory intersected:
        (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
        (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)

This seems to indicate to me you manually ran:

sudo iw reg set GB

Is that the case? If so then that would explain your 5 GHz channels
going missing. Technically we should not allow this though as the country
IE already had GB, I can send a patch for that but you could also not set
one up with iw manually and see the output if 'iw list'. Reason they would
have gone missing is that cfg80211 already has the intersected regulatory
domain present and if you issue a a user that you the country you are in
we will perform an intersection with what we have already and that of
the country you specificy and in that case the intersection yields no 5 GHz
channels. The band exception only occurs on country IEs. But regardless
trying to set the reg domain to manually if the country IE already had that
should result in a no-op. Will have to fix that.

  Luis

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: IWL5300, 2.6.29-rc4, CRDA 1.0.1: Missing out 802.11A frequency ranges
  2009-02-10  1:39           ` Luis R. Rodriguez
@ 2009-02-10  1:51             ` Tony Vroon
  2009-02-10  2:07               ` Luis R. Rodriguez
  0 siblings, 1 reply; 20+ messages in thread
From: Tony Vroon @ 2009-02-10  1:51 UTC (permalink / raw)
  To: Luis R. Rodriguez
  Cc: Luis Rodriguez, linux-wireless, reinette chatre, John W. Linville

[-- Attachment #1: Type: text/plain, Size: 1764 bytes --]

On Mon, 2009-02-09 at 17:39 -0800, Luis R. Rodriguez wrote: 
> In Intel's case the first regulatory domain is ignored (world). To see,
> before associating to an AP try running 'iw list'.

I will remove NetworkManager & gdm from the default runlevel and try
that, yes.

> I noticed that, what ends up happening then is the static world regulatory
> domain is used from the kernel. I take it you used an initramfs with the
> sda driver in there?

No. There's an initramfs, but it's only used to unlock the encrypted
root filesystem. The actual driver for sda (ata_piix) is in the kernel.

> I've been using initramfs too but for some reason
> on my system udev triggers the request eventually after the drive
> is mounted. So this is the first time I hear of this.

I have another user reporting it on PowerPC, without an encrypted root.

> I also noticed though:
> 
> cfg80211: Calling CRDA for country: GB
> cfg80211: Current regulatory intersected:
>         (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
>         (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
> 
> This seems to indicate to me you manually ran:
> 
> sudo iw reg set GB
> 
> Is that the case? 

Eventually, yes. To see if that would clear things up, but it didn't.
Even if I just leave the AP 802.11d info to fill in the regulatory
information (which you can see higher up, as it has the information
slightly wrong and includes channel 14 together with very high radio
power) the 5GHz channels are not included.

As said, will do an iw list with no other software having fiddled with
anything yet. The Cisco APs are in the vicinity so I may not be able to
stop them picking up the 80211d info though.

Regards,
Tony V.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: IWL5300, 2.6.29-rc4, CRDA 1.0.1: Missing out 802.11A frequency ranges
  2009-02-10  1:51             ` Tony Vroon
@ 2009-02-10  2:07               ` Luis R. Rodriguez
  2009-02-11 19:19                 ` Tony Vroon
  0 siblings, 1 reply; 20+ messages in thread
From: Luis R. Rodriguez @ 2009-02-10  2:07 UTC (permalink / raw)
  To: Tony Vroon
  Cc: Luis Rodriguez, linux-wireless, reinette chatre, John W. Linville

On Mon, Feb 09, 2009 at 05:51:29PM -0800, Tony Vroon wrote:
> On Mon, 2009-02-09 at 17:39 -0800, Luis R. Rodriguez wrote: 
> > In Intel's case the first regulatory domain is ignored (world). To see,
> > before associating to an AP try running 'iw list'.
> 
> I will remove NetworkManager & gdm from the default runlevel and try
> that, yes.
> 
> > I noticed that, what ends up happening then is the static world regulatory
> > domain is used from the kernel. I take it you used an initramfs with the
> > sda driver in there?
> 
> No. There's an initramfs, but it's only used to unlock the encrypted
> root filesystem. The actual driver for sda (ata_piix) is in the kernel.

Intersting -- this is the first case I hear about this.

> > I've been using initramfs too but for some reason
> > on my system udev triggers the request eventually after the drive
> > is mounted. So this is the first time I hear of this.
> 
> I have another user reporting it on PowerPC, without an encrypted root.

Are they also disabling OLD_REG? Note that the only routine I see
failing then in the initial:

err = __regulatory_hint(NULL, REGDOM_SET_BY_CORE, "00", 0, ENVIRON_ANY);

Is a kmalloc() (unlikely) or call_crda() failing, and call_crda() will
only fail if kobject_uevent_env() fails and last I checked that would
fail only if the kernel failed to build and emit the udev event (it doesn't mean
CRDA was not present, it should mean udev never got the udev event IIRC).

> > I also noticed though:
> > 
> > cfg80211: Calling CRDA for country: GB
> > cfg80211: Current regulatory intersected:
> >         (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
> >         (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
> > 
> > This seems to indicate to me you manually ran:
> > 
> > sudo iw reg set GB
> > 
> > Is that the case? 
> 
> Eventually, yes.

Oh? Hmm.. if we leave the channel intact before applying the intersected
regulatory domain and if 'iw list' shows the 5 GHz channels it should mean
they are left enabled, I'm a bit puzzled myself, unless I'm missing something.

> To see if that would clear things up, but it didn't.
> Even if I just leave the AP 802.11d info to fill in the regulatory
> information (which you can see higher up, as it has the information
> slightly wrong and includes channel 14 together with very high radio
> power) the 5GHz channels are not included.

Heh :)

> As said, will do an iw list with no other software having fiddled with
> anything yet. The Cisco APs are in the vicinity so I may not be able to
> stop them picking up the 80211d info though.

Actually we don't follow country IE hints in Linux until we associate
to an AP so you should be good.

  Luis

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: IWL5300, 2.6.29-rc4, CRDA 1.0.1: Missing out 802.11A frequency ranges
  2009-02-10  2:07               ` Luis R. Rodriguez
@ 2009-02-11 19:19                 ` Tony Vroon
  2009-02-11 21:46                   ` Luis R. Rodriguez
  2009-02-14  4:52                   ` Luis R. Rodriguez
  0 siblings, 2 replies; 20+ messages in thread
From: Tony Vroon @ 2009-02-11 19:19 UTC (permalink / raw)
  To: Luis R. Rodriguez; +Cc: linux-wireless, reinette chatre, John W. Linville


[-- Attachment #1.1: Type: text/plain, Size: 269 bytes --]

Clear run, haven't touched iw, still no 802.11A spectrum. dmesg
attached. Any suggestion for a workaround that will get me my networks
back please? (Besides enabling the old regulatory options, which is
scheduled to be taken away from me soon)

Regards,
Tony V.

[-- Attachment #1.2: dmesg --]
[-- Type: text/plain, Size: 40532 bytes --]

Linux version 2.6.29-rc4-00026-gf06da26 (root@amalthea) (gcc version 4.3.3 (Gentoo 4.3.3 p1.0, pie-10.1.5) ) #1 SMP Mon Feb 9 18:55:10 GMT 2009
Command line: auto BOOT_IMAGE=2.6.29-rc4-0002 rw root=0 video=vesafb:ywrap,pmipal,mtrr
KERNEL supported cpus:
  Intel GenuineIntel
  AMD AuthenticAMD
  Centaur CentaurHauls
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009d400 (usable)
 BIOS-e820: 000000000009d400 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 00000000bce51000 (usable)
 BIOS-e820: 00000000bce51000 - 00000000bce57000 (reserved)
 BIOS-e820: 00000000bce57000 - 00000000bd058000 (usable)
 BIOS-e820: 00000000bd058000 - 00000000bd0af000 (reserved)
 BIOS-e820: 00000000bd0af000 - 00000000bd1a8000 (usable)
 BIOS-e820: 00000000bd1a8000 - 00000000bd4af000 (reserved)
 BIOS-e820: 00000000bd4af000 - 00000000bd4d8000 (usable)
 BIOS-e820: 00000000bd4d8000 - 00000000bd4df000 (reserved)
 BIOS-e820: 00000000bd4df000 - 00000000bd535000 (usable)
 BIOS-e820: 00000000bd535000 - 00000000bd57f000 (ACPI NVS)
 BIOS-e820: 00000000bd57f000 - 00000000bd5e4000 (usable)
 BIOS-e820: 00000000bd5e4000 - 00000000bd5fd000 (ACPI data)
 BIOS-e820: 00000000bd5fd000 - 00000000bd600000 (usable)
 BIOS-e820: 00000000bd600000 - 00000000c0000000 (reserved)
 BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
 BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
 BIOS-e820: 00000000fed00000 - 00000000fed00400 (reserved)
 BIOS-e820: 00000000fed10000 - 00000000fed14000 (reserved)
 BIOS-e820: 00000000fed18000 - 00000000fed1a000 (reserved)
 BIOS-e820: 00000000fed1c000 - 00000000fed90000 (reserved)
 BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
 BIOS-e820: 00000000ff800000 - 0000000100000000 (reserved)
DMI 2.4 present.
last_pfn = 0xbd600 max_arch_pfn = 0x100000000
x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
init_memory_mapping: 0000000000000000-00000000bd600000
 0000000000 - 00bd600000 page 2M
kernel direct mapping tables up to bd600000 @ 8000-c000
last_map_addr: bd600000 end: bd600000
ACPI: RSDP 000F53D0, 0024 (r2 FUJ   )
ACPI: XSDT BD5F3434, 0074 (r1 FSC    PC        1160000 FUJ       100)
ACPI: FACP BD5E6000, 00F4 (r3 FSC    PC        1160000 FUJ       100)
FADT: X_PM1a_EVT_BLK.bit_width (16) does not match PM1_EVT_LEN (4)
ACPI: DSDT BD5E7000, 8CFF (r1 FUJ    FJNB1E6   1160000 FUJ       100)
ACPI: FACS BD56EFC0, 0040
ACPI: SSDT BD5FC1DF, 034F (r1 FUJ    FJNB1E6   1160000 FUJ       100)
ACPI: HPET BD5FC622, 0038 (r1 FUJ    FJNB1E6   1160000 FUJ       100)
ACPI: MCFG BD5FC65A, 003C (r1 FUJ    FJNB1E6   1160000 FUJ       100)
ACPI: SSDT BD5FC696, 042F (r1 FUJ    FJNB1E6   1160000 FUJ       100)
ACPI: SSDT BD5FCAC5, 02C1 (r1 FUJ    FJNB1E6   1160000 FUJ       100)
ACPI: APIC BD5FCD86, 0068 (r1 FUJ    FJNB1E6   1160000 FUJ       100)
ACPI: BOOT BD5FCDEE, 0028 (r1 FUJ    FJNB1E6   1160000 FUJ       100)
ACPI: SLIC BD5FCE16, 0176 (r1 FSC    PC        1160000 FUJ       100)
ACPI: SSDT BD5E5000, 04E6 (r1  PmRef    CpuPm     3000 INTL 20050624)
ACPI: Local APIC address 0xfee00000
(5 early reservations) ==> bootmem [0000000000 - 00bd600000]
  #0 [0000000000 - 0000001000]   BIOS data page ==> [0000000000 - 0000001000]
  #1 [0000006000 - 0000008000]       TRAMPOLINE ==> [0000006000 - 0000008000]
  #2 [0000200000 - 00009f3dec]    TEXT DATA BSS ==> [0000200000 - 00009f3dec]
  #3 [000009d400 - 0000100000]    BIOS reserved ==> [000009d400 - 0000100000]
  #4 [0000008000 - 000000a000]          PGTABLE ==> [0000008000 - 000000a000]
 [ffffe20000000000-ffffe200029fffff] PMD -> [ffff880001200000-ffff880003bfffff] on node 0
Zone PFN ranges:
  DMA      0x00000000 -> 0x00001000
  DMA32    0x00001000 -> 0x00100000
  Normal   0x00100000 -> 0x00100000
Movable zone start PFN for each node
early_node_map[8] active PFN ranges
    0: 0x00000000 -> 0x0000009d
    0: 0x00000100 -> 0x000bce51
    0: 0x000bce57 -> 0x000bd058
    0: 0x000bd0af -> 0x000bd1a8
    0: 0x000bd4af -> 0x000bd4d8
    0: 0x000bd4df -> 0x000bd535
    0: 0x000bd57f -> 0x000bd5e4
    0: 0x000bd5fd -> 0x000bd600
On node 0 totalpages: 774607
  DMA zone: 56 pages used for memmap
  DMA zone: 2138 pages reserved
  DMA zone: 1803 pages, LIFO batch:0
  DMA32 zone: 10549 pages used for memmap
  DMA32 zone: 760061 pages, LIFO batch:31
ACPI: PM-Timer IO Port: 0x408
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 0, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Using ACPI (MADT) for SMP configuration information
ACPI: HPET id: 0x8086a201 base: 0xfed00000
SMP: Allowing 2 CPUs, 0 hotplug CPUs
Allocating PCI resources starting at c2000000 (gap: c0000000:20000000)
NR_CPUS:2 nr_cpumask_bits:2 nr_cpu_ids:2 nr_node_ids:1
PERCPU: Allocating 49152 bytes of per cpu data
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 761864
Kernel command line: auto BOOT_IMAGE=2.6.29-rc4-0002 rw root=0 video=vesafb:ywrap,pmipal,mtrr
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
Extended CMOS year: 2000
Fast TSC calibration using PIT
Detected 2526.896 MHz processor.
Console: colour VGA+ 80x25
console [tty0] enabled
Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
Checking aperture...
No AGP bridge found
Memory: 3040120k/3102720k available (4161k kernel code, 4292k absent, 57580k reserved, 1977k data, 1428k init)
SLUB: Genslabs=12, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
hpet clockevent registered
HPET: 4 timers in total, 0 timers will be used for per-cpu timer
Calibrating delay loop (skipped), value calculated using timer frequency.. 5055.36 BogoMIPS (lpj=8422986)
Mount-cache hash table entries: 256
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 6144K
[ds] using Core 2/Atom configuration
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
CPU0: Thermal monitoring enabled (TM2)
using mwait in idle threads.
Freeing SMP alternatives: 37k freed
ACPI: Core revision 20081204
Setting APIC routing to flat
..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
CPU0: Intel(R) Core(TM)2 Duo CPU     T9400  @ 2.53GHz stepping 06
Booting processor 1 APIC 0x1 ip 0x6000
Initializing CPU#1
Calibrating delay using timer specific routine.. 5056.56 BogoMIPS (lpj=8423304)
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 6144K
[ds] using Core 2/Atom configuration
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 1
CPU1: Thermal monitoring enabled (TM2)
x86 PAT enabled: cpu 1, old 0x7040600070406, new 0x7010600070106
CPU1: Intel(R) Core(TM)2 Duo CPU     T9400  @ 2.53GHz stepping 06
checking TSC synchronization [CPU#0 -> CPU#1]: passed.
Brought up 2 CPUs
Total of 2 processors activated (10111.93 BogoMIPS).
net_namespace: 960 bytes
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
PCI: MCFG area at e0000000 reserved in E820
PCI: Using MMCONFIG at e0000000 - efffffff
PCI: Using configuration type 1 for base access
mtrr: your CPUs had inconsistent variable MTRR settings
mtrr: probably your BIOS does not setup all CPUs.
mtrr: corrected configuration.
bio: create slab <bio-0> at 0
ACPI: EC: Look up EC in DSDT
ACPI: SSDT BD56E965, 03F1 (r1 FUJ    FJNB1E6   1160000 FUJ       100)
ACPI: Interpreter enabled
ACPI: (supports S0 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI: EC: GPE = 0x17, I/O: command/status = 0x66, data = 0x62
ACPI: EC: driver started in poll mode
ACPI: ACPI Dock Station Driver: 2 docks/bays found
ACPI: PCI Root Bridge [PCI0] (0000:00)
pci 0000:00:02.0: reg 10 64bit mmio: [0xf0000000-0xf03fffff]
pci 0000:00:02.0: reg 18 64bit mmio: [0xd0000000-0xdfffffff]
pci 0000:00:02.0: reg 20 io port: [0x1800-0x1807]
pci 0000:00:02.1: reg 10 64bit mmio: [0xf0400000-0xf04fffff]
pci 0000:00:1a.0: reg 20 io port: [0x1820-0x183f]
pci 0000:00:1a.1: reg 20 io port: [0x1840-0x185f]
pci 0000:00:1a.2: reg 20 io port: [0x1860-0x187f]
pci 0000:00:1a.7: reg 10 32bit mmio: [0xf0a04800-0xf0a04bff]
pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
pci 0000:00:1a.7: PME# disabled
pci 0000:00:1b.0: reg 10 64bit mmio: [0xf0a00000-0xf0a03fff]
pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1b.0: PME# disabled
pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.0: PME# disabled
pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.2: PME# disabled
pci 0000:00:1d.0: reg 20 io port: [0x1880-0x189f]
pci 0000:00:1d.1: reg 20 io port: [0x18a0-0x18bf]
pci 0000:00:1d.2: reg 20 io port: [0x18c0-0x18df]
pci 0000:00:1d.7: reg 10 32bit mmio: [0xf0a04c00-0xf0a04fff]
pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
pci 0000:00:1d.7: PME# disabled
pci 0000:00:1f.2: reg 10 io port: [0x1818-0x181f]
pci 0000:00:1f.2: reg 14 io port: [0x180c-0x180f]
pci 0000:00:1f.2: reg 18 io port: [0x1810-0x1817]
pci 0000:00:1f.2: reg 1c io port: [0x1808-0x180b]
pci 0000:00:1f.2: reg 20 io port: [0x18e0-0x18ff]
pci 0000:00:1f.2: reg 24 32bit mmio: [0xf0a04000-0xf0a047ff]
pci 0000:00:1f.2: PME# supported from D3hot
pci 0000:00:1f.2: PME# disabled
pci 0000:00:1f.3: reg 10 64bit mmio: [0x000000-0x0000ff]
pci 0000:00:1f.3: reg 20 io port: [0x1c00-0x1c1f]
pci 0000:08:00.0: reg 10 64bit mmio: [0xf0500000-0xf0503fff]
pci 0000:08:00.0: reg 18 io port: [0x2000-0x20ff]
pci 0000:08:00.0: reg 30 32bit mmio: [0x000000-0x01ffff]
pci 0000:08:00.0: supports D1 D2
pci 0000:08:00.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:08:00.0: PME# disabled
pci 0000:00:1c.0: bridge io port: [0x2000-0x2fff]
pci 0000:00:1c.0: bridge 32bit mmio: [0xf0500000-0xf05fffff]
pci 0000:18:00.0: reg 10 64bit mmio: [0xf0600000-0xf0601fff]
pci 0000:18:00.0: PME# supported from D0 D3hot D3cold
pci 0000:18:00.0: PME# disabled
pci 0000:00:1c.2: bridge 32bit mmio: [0xf0600000-0xf06fffff]
pci 0000:38:03.0: reg 10 32bit mmio: [0x000000-0x000fff]
pci 0000:38:03.0: supports D1 D2
pci 0000:38:03.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:38:03.0: PME# disabled
pci 0000:38:03.2: reg 10 32bit mmio: [0xf0700000-0xf07000ff]
pci 0000:38:03.2: supports D1 D2
pci 0000:38:03.2: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:38:03.2: PME# disabled
pci 0000:38:03.3: reg 10 32bit mmio: [0xf0701000-0xf0701fff]
pci 0000:38:03.3: supports D1 D2
pci 0000:38:03.3: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:38:03.3: PME# disabled
pci 0000:38:03.4: reg 10 32bit mmio: [0xf0702000-0xf0702fff]
pci 0000:38:03.4: reg 14 32bit mmio: [0xf0700800-0xf0700fff]
pci 0000:38:03.4: supports D1 D2
pci 0000:38:03.4: PME# supported from D0 D1 D2 D3hot
pci 0000:38:03.4: PME# disabled
pci 0000:00:1e.0: transparent bridge
pci 0000:00:1e.0: bridge 32bit mmio: [0xf0700000-0xf07fffff]
pci_bus 0000:00: on NUMA node 0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP01._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP03._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIB._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 10 12 14 15) *11
ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 7 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 10 12 14 15) *11
ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 1 3 4 5 6 7 10 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 1 3 4 5 6 7 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKG] (IRQs 1 3 4 5 6 7 10 12 14 15) *11
ACPI: PCI Interrupt Link [LNKH] (IRQs 1 3 4 5 6 7 *11 12 14 15)
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Using ACPI for IRQ routing
Bluetooth: Core ver 2.14
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
cfg80211: Calling CRDA to update world regulatory domain
cfg80211: calling CRDA failed - unable to update world regulatory domain, using static definition
hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0
hpet0: 4 comparators, 64-bit 14.318180 MHz counter
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 14 devices
ACPI: ACPI bus type pnp unregistered
system 00:01: ioport range 0x400-0x47f has been reserved
system 00:01: ioport range 0x480-0x48f has been reserved
system 00:01: ioport range 0x4d0-0x4d1 has been reserved
system 00:01: ioport range 0x680-0x69f has been reserved
system 00:01: ioport range 0x800-0x80f has been reserved
system 00:01: ioport range 0xf40-0xf41 has been reserved
system 00:01: ioport range 0x1100-0x111f has been reserved
system 00:01: ioport range 0x1180-0x11ff has been reserved
system 00:01: ioport range 0x1640-0x164f has been reserved
system 00:01: ioport range 0xf800-0xf87f has been reserved
system 00:01: ioport range 0xf880-0xf8ff has been reserved
system 00:01: ioport range 0xfc00-0xfc7f has been reserved
system 00:01: ioport range 0xfc80-0xfcff has been reserved
system 00:01: ioport range 0xfd00-0xfd7f has been reserved
system 00:02: iomem range 0xfed1c000-0xfed1ffff has been reserved
system 00:02: iomem range 0xfed10000-0xfed13fff has been reserved
system 00:02: iomem range 0xfed18000-0xfed18fff has been reserved
system 00:02: iomem range 0xfed19000-0xfed19fff has been reserved
system 00:02: iomem range 0xe0000000-0xefffffff has been reserved
system 00:02: iomem range 0xfed20000-0xfed3ffff has been reserved
system 00:02: iomem range 0xfed45000-0xfed8ffff has been reserved
system 00:02: iomem range 0xfef00000-0xfeffffff has been reserved
system 00:0a: iomem range 0xfed00000-0xfed003ff has been reserved
pci 0000:00:1c.0: PCI bridge, secondary bus 0000:08
pci 0000:00:1c.0:   IO window: 0x2000-0x2fff
pci 0000:00:1c.0:   MEM window: 0xf0500000-0xf05fffff
pci 0000:00:1c.0:   PREFETCH window: 0x000000c2000000-0x000000c20fffff
pci 0000:00:1c.2: PCI bridge, secondary bus 0000:18
pci 0000:00:1c.2:   IO window: disabled
pci 0000:00:1c.2:   MEM window: 0xf0600000-0xf06fffff
pci 0000:00:1c.2:   PREFETCH window: disabled
pci 0000:38:03.0: CardBus bridge, secondary bus 0000:39
pci 0000:38:03.0:   IO window: 0x003000-0x0030ff
pci 0000:38:03.0:   IO window: 0x003400-0x0034ff
pci 0000:38:03.0:   PREFETCH window: 0xc4000000-0xc7ffffff
pci 0000:38:03.0:   MEM window: 0xc8000000-0xcbffffff
pci 0000:00:1e.0: PCI bridge, secondary bus 0000:38
pci 0000:00:1e.0:   IO window: 0x3000-0x3fff
pci 0000:00:1e.0:   MEM window: 0xf0700000-0xf07fffff
pci 0000:00:1e.0:   PREFETCH window: 0x000000c4000000-0x000000c7ffffff
pci 0000:00:1c.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
pci 0000:00:1c.0: setting latency timer to 64
pci 0000:00:1c.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
pci 0000:00:1c.2: setting latency timer to 64
pci 0000:00:1e.0: setting latency timer to 64
pci 0000:38:03.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
pci_bus 0000:00: resource 0 io:  [0x00-0xffff]
pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffffffffffff]
pci_bus 0000:08: resource 0 io:  [0x2000-0x2fff]
pci_bus 0000:08: resource 1 mem: [0xf0500000-0xf05fffff]
pci_bus 0000:08: resource 2 mem: [0xc2000000-0xc20fffff]
pci_bus 0000:08: resource 3 mem: [0x0-0x0]
pci_bus 0000:18: resource 0 mem: [0x0-0x0]
pci_bus 0000:18: resource 1 mem: [0xf0600000-0xf06fffff]
pci_bus 0000:18: resource 2 mem: [0x0-0x0]
pci_bus 0000:18: resource 3 mem: [0x0-0x0]
pci_bus 0000:38: resource 0 io:  [0x3000-0x3fff]
pci_bus 0000:38: resource 1 mem: [0xf0700000-0xf07fffff]
pci_bus 0000:38: resource 2 mem: [0xc4000000-0xc7ffffff]
pci_bus 0000:38: resource 3 io:  [0x00-0xffff]
pci_bus 0000:38: resource 4 mem: [0x000000-0xffffffffffffffff]
pci_bus 0000:39: resource 0 io:  [0x3000-0x30ff]
pci_bus 0000:39: resource 1 io:  [0x3400-0x34ff]
pci_bus 0000:39: resource 2 mem: [0xc4000000-0xc7ffffff]
pci_bus 0000:39: resource 3 mem: [0xc8000000-0xcbffffff]
NET: Registered protocol family 2
IP route cache hash table entries: 131072 (order: 8, 1048576 bytes)
TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
TCP reno registered
NET: Registered protocol family 1
Simple Boot Flag at 0x7b set to 0x1
Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
NTFS driver 2.1.29 [Flags: R/O].
fuse init (API version 7.11)
msgmni has been set to 5939
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci 0000:00:02.0: Boot video device
pcieport-driver 0000:00:1c.0: setting latency timer to 64
pcieport-driver 0000:00:1c.0: irq 24 for MSI/MSI-X
pcieport-driver 0000:00:1c.2: setting latency timer to 64
pcieport-driver 0000:00:1c.2: irq 25 for MSI/MSI-X
ACPI: AC Adapter [AC] (on-line)
ACPI: EC: non-query interrupt received, switching to interrupt mode
ACPI: Battery Slot [CMB1] (battery present)
ACPI: Battery Slot [CMB2] (battery absent)
input: Power Button (FF) as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
ACPI: Power Button (FF) [PWRF]
input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input1
ACPI: Lid Switch [LID]
input: Power Button (CM) as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input2
ACPI: Power Button (CM) [PWRB]
input: Sleep Button (CM) as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input3
ACPI: Sleep Button (CM) [SLPB]
acpi device:05: registered as cooling_device0
input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:03/input/input4
ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
ACPI: Invalid PBLK length [8]
ACPI: SSDT BD4DAC20, 0265 (r1  PmRef  Cpu0Ist     3000 INTL 20050624)
ACPI: SSDT BD4D86A0, 05CC (r1  PmRef  Cpu0Cst     3001 INTL 20050624)
Monitor-Mwait will be used to enter C-1 state
Monitor-Mwait will be used to enter C-2 state
ACPI: CPU0 (power states: C1[C1] C2[C2])
processor ACPI_CPU:00: registered as cooling_device1
ACPI: Invalid PBLK length [8]
ACPI: SSDT BD4D9DA0, 00FD (r1  PmRef    ApIst     3000 INTL 20050624)
ACPI: SSDT BD4DCF20, 0047 (r1  PmRef    ApCst     3000 INTL 20050624)
ACPI: CPU1 (power states: C1[C1] C2[C2])
processor ACPI_CPU:01: registered as cooling_device2
thermal LNXTHERM:01: registered as thermal_zone0
ACPI: Thermal Zone [TZ00] (27 C)
thermal LNXTHERM:02: registered as thermal_zone1
ACPI: Thermal Zone [TZ01] (27 C)
Real Time Clock Driver v1.12b
Non-volatile memory driver v1.3
Linux agpgart interface v0.103
agpgart-intel 0000:00:00.0: Intel Mobile Intel® GM45 Express Chipset
agpgart-intel 0000:00:00.0: detected 32764K stolen memory
agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xd0000000
tpm_tis 00:03: 1.2 TPM (device-id 0xB, rev-id 16)
Switched to high resolution mode on CPU 1
Switched to high resolution mode on CPU 0
tpm_tis 00:03: Operation Timed out
[drm] Initialized drm 1.1.0 20060810
pci 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
pci 0000:00:02.0: setting latency timer to 64
pci 0000:00:02.0: irq 26 for MSI/MSI-X
[drm] Initialized i915 1.6.0 20080730 on minor 0
intelfb: intelfb_init
intelfb: Framebuffer driver for Intel(R) 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/945GME/965G/965GM chipsets
intelfb: Version 0.9.6
intelfb: intelfb_setup
intelfb: no options
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:0b: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
loop: module loaded
sky2 driver version 1.22
sky2 0000:08:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
sky2 0000:08:00.0: setting latency timer to 64
sky2 0000:08:00.0: Yukon-2 EC Ultra chip revision 3
sky2 0000:08:00.0: Marvell Yukon 88E8055 Gigabit Ethernet Controller
 Part Number: 88E8055
 Engineering Level: Rev. 1.4
 Manufacturer: Marvell
sky2 0000:08:00.0: irq 27 for MSI/MSI-X
sky2 eth0: addr 00:17:42:c8:5a:90
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27kds
iwlagn: Copyright(c) 2003-2008 Intel Corporation
iwlagn 0000:18:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
iwlagn 0000:18:00.0: setting latency timer to 64
iwlagn: Detected Intel Wireless WiFi Link 5300AGN REV=0x24
iwlagn: Tunable channels: 13 802.11bg, 24 802.11a channels
iwlagn 0000:18:00.0: PCI INT A disabled
wmaster0 (iwlagn): not using net_device_ops yet
phy0: Selected rate control algorithm 'iwl-agn-rs'
wlan0 (iwlagn): not using net_device_ops yet
Linux video capture interface: v2.00
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v0.1.0)
Driver 'sd' needs updating - please use bus_type methods
Driver 'sr' needs updating - please use bus_type methods
ahci 0000:00:1f.2: version 3.0
ahci 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
ahci 0000:00:1f.2: irq 28 for MSI/MSI-X
ahci: SSS flag set, parallel bus scan disabled
ahci 0000:00:1f.2: AHCI 0001.0200 32 slots 4 ports 3 Gbps 0x3 impl SATA mode
ahci 0000:00:1f.2: flags: 64bit ncq sntf stag pm led clo pmp pio slum part 
ahci 0000:00:1f.2: setting latency timer to 64
scsi0 : ahci
scsi1 : ahci
scsi2 : ahci
scsi3 : ahci
ata1: SATA max UDMA/133 abar m2048@0xf0a04000 port 0xf0a04100 irq 28
ata2: SATA max UDMA/133 abar m2048@0xf0a04000 port 0xf0a04180 irq 28
ata3: DUMMY
ata4: DUMMY
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: ACPI cmd ef/10:03:00:00:00:a0 filtered out
ata1.00: ACPI cmd f5/00:00:00:00:00:a0 filtered out
ata1.00: ATA-8: Hitachi HTS543232L9A300, FB4OC40C, max UDMA/133
ata1.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata1.00: ACPI cmd ef/10:03:00:00:00:a0 filtered out
ata1.00: ACPI cmd f5/00:00:00:00:00:a0 filtered out
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access     ATA      Hitachi HTS54323 FB4O PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 625142448 512-byte hardware sectors: (320 GB/298 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] 625142448 512-byte hardware sectors: (320 GB/298 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1 sda2 sda3
sd 0:0:0:0: [sda] Attached SCSI disk
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.00: ACPI cmd ef/90:03:00:00:00:a0 rejected by device (Stat=0x51 Err=0x04)
ata2.00: ACPI cmd 00/00:00:00:00:00:a0 rejected by device (Stat=0x51 Err=0x04)
ata2.00: ATAPI: MATSHITADVD-RAM UJ862BJ, 1.00, max UDMA/33
ata2.00: ACPI cmd ef/90:03:00:00:00:a0 rejected by device (Stat=0x51 Err=0x04)
ata2.00: ACPI cmd 00/00:00:00:00:00:a0 rejected by device (Stat=0x51 Err=0x04)
ata2.00: configured for UDMA/33
scsi 1:0:0:0: CD-ROM            MATSHITA DVD-RAM UJ862BJ  1.00 PQ: 0 ANSI: 5
sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 1:0:0:0: Attached scsi CD-ROM sr0
firewire_ohci 0000:38:03.4: PCI INT A -> GSI 17 (level, low) -> IRQ 17
firewire_ohci: Added fw-ohci device 0000:38:03.4, OHCI version 1.10
yenta_cardbus 0000:38:03.0: CardBus bridge found [10cf:143d]
yenta_cardbus 0000:38:03.0: O2: res at 0x94/0xD4: 00/ea
yenta_cardbus 0000:38:03.0: O2: enabling read prefetch/write burst
yenta_cardbus 0000:38:03.0: ISA IRQ mask 0x0cb8, PCI irq 17
yenta_cardbus 0000:38:03.0: Socket status: 30000006
pci_bus 0000:38: Raising subordinate bus# of parent bus (#38) from #39 to #3c
yenta_cardbus 0000:38:03.0: pcmcia: parent PCI bridge I/O window: 0x3000 - 0x3fff
yenta_cardbus 0000:38:03.0: pcmcia: parent PCI bridge Memory window: 0xf0700000 - 0xf07fffff
yenta_cardbus 0000:38:03.0: pcmcia: parent PCI bridge Memory window: 0xc4000000 - 0xc7ffffff
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 18 (level, low) -> IRQ 18
ehci_hcd 0000:00:1a.7: setting latency timer to 64
ehci_hcd 0000:00:1a.7: EHCI Host Controller
ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1a.7: debug port 1
ehci_hcd 0000:00:1a.7: cache line size of 32 is not supported
ehci_hcd 0000:00:1a.7: irq 18, io mem 0xf0a04800
ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 6 ports detected
ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23
ehci_hcd 0000:00:1d.7: setting latency timer to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2
ehci_hcd 0000:00:1d.7: debug port 1
ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported
ehci_hcd 0000:00:1d.7: irq 23, io mem 0xf0a04c00
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 6 ports detected
uhci_hcd: USB Universal Host Controller Interface driver
uhci_hcd 0000:00:1a.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
uhci_hcd 0000:00:1a.0: setting latency timer to 64
uhci_hcd 0000:00:1a.0: UHCI Host Controller
uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1a.0: irq 16, io base 0x00001820
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
uhci_hcd 0000:00:1a.1: setting latency timer to 64
uhci_hcd 0000:00:1a.1: UHCI Host Controller
uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1a.1: irq 17, io base 0x00001840
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
uhci_hcd 0000:00:1a.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
uhci_hcd 0000:00:1a.2: setting latency timer to 64
uhci_hcd 0000:00:1a.2: UHCI Host Controller
uhci_hcd 0000:00:1a.2: new USB bus registered, assigned bus number 5
uhci_hcd 0000:00:1a.2: irq 18, io base 0x00001860
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
uhci_hcd 0000:00:1d.0: setting latency timer to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 6
uhci_hcd 0000:00:1d.0: irq 23, io base 0x00001880
usb usb6: configuration #1 chosen from 1 choice
hub 6-0:1.0: USB hub found
hub 6-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
uhci_hcd 0000:00:1d.1: setting latency timer to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 7
uhci_hcd 0000:00:1d.1: irq 19, io base 0x000018a0
usb usb7: configuration #1 chosen from 1 choice
hub 7-0:1.0: USB hub found
hub 7-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
uhci_hcd 0000:00:1d.2: setting latency timer to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 8
uhci_hcd 0000:00:1d.2: irq 18, io base 0x000018c0
usb usb8: configuration #1 chosen from 1 choice
hub 8-0:1.0: USB hub found
hub 8-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbserial
usbserial: USB Serial Driver core
USB Serial support registered for pl2303
usbcore: registered new interface driver pl2303
pl2303: Prolific PL2303 USB to serial adaptor driver
USB Serial support registered for Sierra USB modem
usbcore: registered new interface driver sierra
sierra: v.1.3.2:USB Driver for Sierra Wireless USB modems
PNP: PS/2 Controller [PNP0303:KBC,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
i8042.c: Detected active multiplexing controller, rev 1.1.
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX0 port at 0x60,0x64 irq 12
serio: i8042 AUX1 port at 0x60,0x64 irq 12
serio: i8042 AUX2 port at 0x60,0x64 irq 12
serio: i8042 AUX3 port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
input: PC Speaker as /devices/platform/pcspkr/input/input5
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.04
iTCO_wdt: Found a ICH9M TCO device (Version=2, TCOBASE=0x0460)
iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.14.0-ioctl (2008-04-23) initialised: dm-devel@redhat.com
Bluetooth: Generic Bluetooth USB driver ver 0.4
usbcore: registered new interface driver btusb
cpuidle: using governor ladder
cpuidle: using governor menu
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pci 0000:38:03.2: SDHCI controller found [1217:7120] (rev 2)
sdhci-pci 0000:38:03.2: PCI INT A -> GSI 17 (level, low) -> IRQ 17
mmc0: Unknown controller version (2). You may experience problems.
Registered led device: mmc0
mmc0: SDHCI controller on PCI [0000:38:03.2] using DMA
Marking TSC unstable due to TSC halts in idle
firewire_core: created device fw0: GUID 00000e1003fdee54, S400
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input6
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.18a.
HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
HDA Intel 0000:00:1b.0: setting latency timer to 64
usb 1-5: new high speed USB device using ehci_hcd and address 2
usb 1-5: configuration #1 chosen from 1 choice
hub 1-5:1.0: USB hub found
hub 1-5:1.0: 4 ports detected
usb 2-4: new high speed USB device using ehci_hcd and address 4
usb 2-4: configuration #1 chosen from 1 choice
uvcvideo: Found UVC 1.00 device OEM Camera (046d:09b2)
input: OEM Camera as /devices/pci0000:00/0000:00:1d.7/usb2/2-4/2-4:1.0/input/input7
Synaptics Touchpad, model: 1, fw: 7.2, id: 0x1c0b1, caps: 0xd04731/0xa42000
input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio4/input/input8
ALSA sound/pci/hda/hda_intel.c:633: hda_intel: azx_get_response timeout, switching to polling mode: last cmd=0x020c0000
hda-codec: No codec parser is available
ALSA device list:
  #0: HDA Intel at 0xf0a00000 irq 22
TCP cubic registered
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
Bluetooth: L2CAP ver 2.11
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO (Voice Link) ver 0.6
Bluetooth: SCO socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.10
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
BIOS EDD facility v0.16 2004-Jun-25, 1 devices found
Freeing unused kernel memory: 1428k freed
Write protecting the kernel read-only data: 5580k
usb 6-1: new full speed USB device using uhci_hcd and address 2
usb 6-1: configuration #1 chosen from 1 choice
usb 6-2: new full speed USB device using uhci_hcd and address 3
usb 6-2: configuration #1 chosen from 1 choice
usb 1-5.1: new full speed USB device using ehci_hcd and address 3
usb 1-5.1: configuration #1 chosen from 1 choice
hub 1-5.1:1.0: USB hub found
hub 1-5.1:1.0: 3 ports detected
usb 1-5.2: new low speed USB device using ehci_hcd and address 4
usb 1-5.2: configuration #1 chosen from 1 choice
generic-usb 0003:0A81:0701.0001: claimed by neither input, hiddev nor hidraw
usb 1-5.4: new full speed USB device using ehci_hcd and address 5
usb 1-5.4: configuration #1 chosen from 1 choice
usb 1-5.1.1: new full speed USB device using ehci_hcd and address 7
usb 1-5.1.1: configuration #1 chosen from 1 choice
hub 1-5.1.1:1.0: USB hub found
hub 1-5.1.1:1.0: 4 ports detected
usb 1-5.1.2: new low speed USB device using ehci_hcd and address 8
usb 1-5.1.2: configuration #1 chosen from 1 choice
input: Belkin Corporation Flip KVM as /devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.1/1-5.1.2/1-5.1.2:1.0/input/input9
belkin 0003:050D:3201.0002: input: USB HID v1.10 Device [Belkin Corporation Flip KVM] on usb-0000:00:1a.7-5.1.2/input0
usb 1-5.1.3: new full speed USB device using ehci_hcd and address 9
hub 1-5.1:1.0: unable to enumerate USB device on port 3
usb 5-2: new full speed USB device using uhci_hcd and address 2
usb 5-2: configuration #1 chosen from 1 choice
sierra 5-2:1.0: Sierra USB modem converter detected
usb 5-2: Sierra USB modem converter now attached to ttyUSB0
usb 5-2: Sierra USB modem converter now attached to ttyUSB1
usb 5-2: Sierra USB modem converter now attached to ttyUSB2
usb 1-5.1.1.1: new low speed USB device using ehci_hcd and address 10
usb 1-5.1.1.1: configuration #1 chosen from 1 choice
input: G15 Gaming Keyboard as /devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.1/1-5.1.1/1-5.1.1.1/1-5.1.1.1:1.0/input/input10
generic-usb 0003:046D:C226.0003: input: USB HID v1.10 Keyboard [G15 Gaming Keyboard] on usb-0000:00:1a.7-5.1.1.1/input0
input: G15 Gaming Keyboard as /devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.1/1-5.1.1/1-5.1.1.1/1-5.1.1.1:1.1/input/input11
generic-usb 0003:046D:C226.0004: input: USB HID v1.10 Device [G15 Gaming Keyboard] on usb-0000:00:1a.7-5.1.1.1/input1
usb 1-5.1.1.4: new full speed USB device using ehci_hcd and address 11
usb 1-5.1.1.4: configuration #1 chosen from 1 choice
input: G15 GamePanel LCD as /devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.1/1-5.1.1/1-5.1.1.4/1-5.1.1.4:1.0/input/input12
generic-usb 0003:046D:C227.0005: input: USB HID v1.11 Keypad [G15 GamePanel LCD] on usb-0000:00:1a.7-5.1.1.4/input0
usb 1-5.1.3: new full speed USB device using ehci_hcd and address 12
usb 1-5.1.3: configuration #1 chosen from 1 choice
input: Razer Razer Copperhead Laser Mouse as /devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.1/1-5.1.3/1-5.1.3:1.0/input/input13
generic-usb 0003:1532:0101.0006: input: USB HID v1.00 Mouse [Razer Razer Copperhead Laser Mouse] on usb-0000:00:1a.7-5.1.3/input0
input: Razer Razer Copperhead Laser Mouse as /devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.1/1-5.1.3/1-5.1.3:1.1/input/input14
generic-usb 0003:1532:0101.0007: input: USB HID v0.01 Keyboard [Razer Razer Copperhead Laser Mouse] on usb-0000:00:1a.7-5.1.3/input1
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
fujitsu-laptop: Identified laptop model 'Fujitsu Siemens S6420'.
input: Fujitsu FUJ02B1 as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:3f/FUJ02B1:00/input/input15
ACPI: Fujitsu FUJ02B1 [FJEX] (on)
input: Fujitsu FUJ02E3 as /devices/LNXSYSTM:00/device:00/FUJ02E3:00/input/input16
ACPI: Fujitsu FUJ02E3 [FEXT] (on)
fujitsu-laptop: BTNI: [0xff0101]
fujitsu-laptop: driver 0.5.0 successfully loaded.
gspca: main v2.4.0 registered
gspca: probing 0ac8:307b
zc3xx: probe 2wr ov vga 0x0000
zc3xx: probe 3wr vga 1 0x4001
zc3xx: probe 3wr vga 2 0x0000
zc3xx: Sensor UNKNOW_0 force Tas5130
gspca: probe ok
usbcore: registered new interface driver zc3xx
zc3xx: registered
EXT3 FS on dm-0, internal journal
input: G15 Extra Keys as /devices/virtual/input/input17
sky2 eth0: enabling interface
ADDRCONF(NETDEV_UP): eth0: link is not ready
iwlagn 0000:18:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
iwlagn 0000:18:00.0: restoring config space at offset 0x1 (was 0x100102, writing 0x100106)
iwlagn 0000:18:00.0: irq 29 for MSI/MSI-X
iwlagn 0000:18:00.0: firmware: requesting iwlwifi-5000-1.ucode
iwlagn loaded firmware version 5.4.1.16
ADDRCONF(NETDEV_UP): wlan0: link is not ready
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control rx
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
eth0: no IPv6 routers present
wlan0: direct probe to AP 00:1e:f7:ea:d1:60 try 1
wlan0 direct probe responded
wlan0: authenticate with AP 00:1e:f7:ea:d1:60
wlan0: authenticated
wlan0: associate with AP 00:1e:f7:ea:d1:60
wlan0: RX AssocResp from 00:1e:f7:ea:d1:60 (capab=0x431 status=0 aid=8)
wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
cfg80211: Calling CRDA for country: GB
cfg80211: Received country IE:
cfg80211: Regulatory domain: GB
	(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
	(2402000 KHz - 2494000 KHz @ 40000 KHz), (10000 mBi, 10000 mBm)
cfg80211: CRDA thinks this should applied:
cfg80211: Regulatory domain: GB
	(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
	(2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
	(5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm)
	(5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm)
	(5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm)
cfg80211: We intersect both of these and get:
cfg80211: Regulatory domain: 98
	(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
	(2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
cfg80211: Leaving channel 5180 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5200 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5220 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5240 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5260 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5280 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5300 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5320 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5500 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5520 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5540 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5560 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5580 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5600 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5620 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5640 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5660 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5680 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5700 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5745 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5765 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5785 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5805 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Leaving channel 5825 MHz intact on phy0 - no rule found in band on Country IE
cfg80211: Current regulatory domain updated by AP to: GB
	(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
	(2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
wlan0: no IPv6 routers present

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: IWL5300, 2.6.29-rc4, CRDA 1.0.1: Missing out 802.11A frequency ranges
  2009-02-11 19:19                 ` Tony Vroon
@ 2009-02-11 21:46                   ` Luis R. Rodriguez
  2009-02-13 10:55                     ` Tony Vroon
  2009-02-14  4:52                   ` Luis R. Rodriguez
  1 sibling, 1 reply; 20+ messages in thread
From: Luis R. Rodriguez @ 2009-02-11 21:46 UTC (permalink / raw)
  To: tony; +Cc: linux-wireless, reinette chatre, John W. Linville

On Wed, Feb 11, 2009 at 11:19 AM, Tony Vroon <tony@linx.net> wrote:
> Clear run, haven't touched iw, still no 802.11A spectrum. dmesg
> attached. Any suggestion for a workaround that will get me my networks
> back please? (Besides enabling the old regulatory options, which is
> scheduled to be taken away from me soon)

Looks good here -- can you please provide 'iw list' output prior to
trying to associate.

 Luis

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: IWL5300, 2.6.29-rc4, CRDA 1.0.1: Missing out 802.11A frequency ranges
  2009-02-11 21:46                   ` Luis R. Rodriguez
@ 2009-02-13 10:55                     ` Tony Vroon
  0 siblings, 0 replies; 20+ messages in thread
From: Tony Vroon @ 2009-02-13 10:55 UTC (permalink / raw)
  To: Luis R. Rodriguez; +Cc: linux-wireless, reinette chatre, John W. Linville


[-- Attachment #1.1: Type: text/plain, Size: 324 bytes --]

On Wed, 2009-02-11 at 13:46 -0800, Luis R. Rodriguez wrote:
> Looks good here -- can you please provide 'iw list' output prior to
> trying to associate.

As expected, the "world domain". Details attached.
Leaving the 802.11A spectrum alone won't help if your defaults don't
enable it.

>  Luis

Regards,
Tony V.

[-- Attachment #1.2: iwlist.earlyboot.txt --]
[-- Type: text/plain, Size: 2672 bytes --]

Wiphy phy0
	Band 1:
		HT capabilities: 0x087e
			 * 20/40 MHz operation
			 * SM PS disabled
			 * HT-greenfield
			 * 20 MHz short GI
			 * 40 MHz short GI
			 * max A-MSDU len 7935
		HT A-MPDU factor: 0x0003 (65535 bytes)
		HT A-MPDU density: 0x0005 (4 usec)
		HT MCS set: ff ff ff 00 01 00 00 00 00 00 c2 01 01 00 00 00
		Frequencies:
			* 2412 MHz [1] (15.0 dBm) (passive scanning, no IBSS)
			* 2417 MHz [2] (15.0 dBm) (passive scanning, no IBSS)
			* 2422 MHz [3] (15.0 dBm) (passive scanning, no IBSS)
			* 2427 MHz [4] (15.0 dBm) (passive scanning, no IBSS)
			* 2432 MHz [5] (15.0 dBm) (passive scanning, no IBSS)
			* 2437 MHz [6] (15.0 dBm) (passive scanning, no IBSS)
			* 2442 MHz [7] (15.0 dBm) (passive scanning, no IBSS)
			* 2447 MHz [8] (15.0 dBm) (passive scanning, no IBSS)
			* 2452 MHz [9] (15.0 dBm) (passive scanning, no IBSS)
			* 2457 MHz [10] (15.0 dBm) (passive scanning, no IBSS)
			* 2462 MHz [11] (15.0 dBm) (passive scanning, no IBSS)
			* 2467 MHz [12] (disabled)
			* 2472 MHz [13] (disabled)
		Bitrates:
			* 1.0 Mbps
			* 2.0 Mbps (short preamble supported)
			* 5.5 Mbps (short preamble supported)
			* 11.0 Mbps (short preamble supported)
			* 6.0 Mbps
			* 9.0 Mbps
			* 12.0 Mbps
			* 18.0 Mbps
			* 24.0 Mbps
			* 36.0 Mbps
			* 48.0 Mbps
			* 54.0 Mbps
			* 60.0 Mbps
	Band 2:
		HT capabilities: 0x087e
			 * 20/40 MHz operation
			 * SM PS disabled
			 * HT-greenfield
			 * 20 MHz short GI
			 * 40 MHz short GI
			 * max A-MSDU len 7935
		HT A-MPDU factor: 0x0003 (65535 bytes)
		HT A-MPDU density: 0x0005 (4 usec)
		HT MCS set: ff ff ff 00 01 00 00 00 00 00 c2 01 01 00 00 00
		Frequencies:
			* 5180 MHz [36] (disabled)
			* 5200 MHz [40] (disabled)
			* 5220 MHz [44] (disabled)
			* 5240 MHz [48] (disabled)
			* 5260 MHz [52] (disabled)
			* 5280 MHz [56] (disabled)
			* 5300 MHz [60] (disabled)
			* 5320 MHz [64] (disabled)
			* 5500 MHz [100] (disabled)
			* 5520 MHz [104] (disabled)
			* 5540 MHz [108] (disabled)
			* 5560 MHz [112] (disabled)
			* 5580 MHz [116] (disabled)
			* 5600 MHz [120] (disabled)
			* 5620 MHz [124] (disabled)
			* 5640 MHz [128] (disabled)
			* 5660 MHz [132] (disabled)
			* 5680 MHz [136] (disabled)
			* 5700 MHz [140] (disabled)
			* 5745 MHz [149] (disabled)
			* 5765 MHz [153] (disabled)
			* 5785 MHz [157] (disabled)
			* 5805 MHz [161] (disabled)
			* 5825 MHz [165] (disabled)
		Bitrates:
			* 6.0 Mbps
			* 9.0 Mbps
			* 12.0 Mbps
			* 18.0 Mbps
			* 24.0 Mbps
			* 36.0 Mbps
			* 48.0 Mbps
			* 54.0 Mbps
			* 60.0 Mbps
	Supported interface modes:
		 * IBSS
		 * Station
		 * Monitor

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: IWL5300, 2.6.29-rc4, CRDA 1.0.1: Missing out 802.11A frequency ranges
  2009-02-11 19:19                 ` Tony Vroon
  2009-02-11 21:46                   ` Luis R. Rodriguez
@ 2009-02-14  4:52                   ` Luis R. Rodriguez
  2009-02-14  5:02                     ` Luis R. Rodriguez
  2009-02-16 12:08                     ` Tony Vroon
  1 sibling, 2 replies; 20+ messages in thread
From: Luis R. Rodriguez @ 2009-02-14  4:52 UTC (permalink / raw)
  To: Tony Vroon
  Cc: Luis Rodriguez, linux-wireless, reinette chatre, John W. Linville

On Wed, Feb 11, 2009 at 11:19:41AM -0800, Tony Vroon wrote:
> Clear run, haven't touched iw, still no 802.11A spectrum. dmesg
> attached. Any suggestion for a workaround that will get me my networks
> back please? (Besides enabling the old regulatory options, which is
> scheduled to be taken away from me soon)
> 
> Regards,
> Tony V.

> Linux version 2.6.29-rc4-00026-gf06da26 (root@amalthea) (gcc version 4.3.3 (Gentoo 4.3.3 p1.0, pie-10.1.5) ) #1 SMP Mon Feb 9 18:55:10 GMT 2009
> Command line: auto BOOT_IMAGE=2.6.29-rc4-0002 rw root=0 video=vesafb:ywrap,pmipal,mtrr
> KERNEL supported cpus:
>   Intel GenuineIntel
>   AMD AuthenticAMD
>   Centaur CentaurHauls
> BIOS-provided physical RAM map:
>  BIOS-e820: 0000000000000000 - 000000000009d400 (usable)
>  BIOS-e820: 000000000009d400 - 00000000000a0000 (reserved)
>  BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
>  BIOS-e820: 0000000000100000 - 00000000bce51000 (usable)
>  BIOS-e820: 00000000bce51000 - 00000000bce57000 (reserved)
>  BIOS-e820: 00000000bce57000 - 00000000bd058000 (usable)
>  BIOS-e820: 00000000bd058000 - 00000000bd0af000 (reserved)
>  BIOS-e820: 00000000bd0af000 - 00000000bd1a8000 (usable)
>  BIOS-e820: 00000000bd1a8000 - 00000000bd4af000 (reserved)
>  BIOS-e820: 00000000bd4af000 - 00000000bd4d8000 (usable)
>  BIOS-e820: 00000000bd4d8000 - 00000000bd4df000 (reserved)
>  BIOS-e820: 00000000bd4df000 - 00000000bd535000 (usable)
>  BIOS-e820: 00000000bd535000 - 00000000bd57f000 (ACPI NVS)
>  BIOS-e820: 00000000bd57f000 - 00000000bd5e4000 (usable)
>  BIOS-e820: 00000000bd5e4000 - 00000000bd5fd000 (ACPI data)
>  BIOS-e820: 00000000bd5fd000 - 00000000bd600000 (usable)
>  BIOS-e820: 00000000bd600000 - 00000000c0000000 (reserved)
>  BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
>  BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
>  BIOS-e820: 00000000fed00000 - 00000000fed00400 (reserved)
>  BIOS-e820: 00000000fed10000 - 00000000fed14000 (reserved)
>  BIOS-e820: 00000000fed18000 - 00000000fed1a000 (reserved)
>  BIOS-e820: 00000000fed1c000 - 00000000fed90000 (reserved)
>  BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
>  BIOS-e820: 00000000ff800000 - 0000000100000000 (reserved)
> DMI 2.4 present.
> last_pfn = 0xbd600 max_arch_pfn = 0x100000000
> x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
> init_memory_mapping: 0000000000000000-00000000bd600000
>  0000000000 - 00bd600000 page 2M
> kernel direct mapping tables up to bd600000 @ 8000-c000
> last_map_addr: bd600000 end: bd600000
> ACPI: RSDP 000F53D0, 0024 (r2 FUJ   )
> ACPI: XSDT BD5F3434, 0074 (r1 FSC    PC        1160000 FUJ       100)
> ACPI: FACP BD5E6000, 00F4 (r3 FSC    PC        1160000 FUJ       100)
> FADT: X_PM1a_EVT_BLK.bit_width (16) does not match PM1_EVT_LEN (4)
> ACPI: DSDT BD5E7000, 8CFF (r1 FUJ    FJNB1E6   1160000 FUJ       100)
> ACPI: FACS BD56EFC0, 0040
> ACPI: SSDT BD5FC1DF, 034F (r1 FUJ    FJNB1E6   1160000 FUJ       100)
> ACPI: HPET BD5FC622, 0038 (r1 FUJ    FJNB1E6   1160000 FUJ       100)
> ACPI: MCFG BD5FC65A, 003C (r1 FUJ    FJNB1E6   1160000 FUJ       100)
> ACPI: SSDT BD5FC696, 042F (r1 FUJ    FJNB1E6   1160000 FUJ       100)
> ACPI: SSDT BD5FCAC5, 02C1 (r1 FUJ    FJNB1E6   1160000 FUJ       100)
> ACPI: APIC BD5FCD86, 0068 (r1 FUJ    FJNB1E6   1160000 FUJ       100)
> ACPI: BOOT BD5FCDEE, 0028 (r1 FUJ    FJNB1E6   1160000 FUJ       100)
> ACPI: SLIC BD5FCE16, 0176 (r1 FSC    PC        1160000 FUJ       100)
> ACPI: SSDT BD5E5000, 04E6 (r1  PmRef    CpuPm     3000 INTL 20050624)
> ACPI: Local APIC address 0xfee00000
> (5 early reservations) ==> bootmem [0000000000 - 00bd600000]
>   #0 [0000000000 - 0000001000]   BIOS data page ==> [0000000000 - 0000001000]
>   #1 [0000006000 - 0000008000]       TRAMPOLINE ==> [0000006000 - 0000008000]
>   #2 [0000200000 - 00009f3dec]    TEXT DATA BSS ==> [0000200000 - 00009f3dec]
>   #3 [000009d400 - 0000100000]    BIOS reserved ==> [000009d400 - 0000100000]
>   #4 [0000008000 - 000000a000]          PGTABLE ==> [0000008000 - 000000a000]
>  [ffffe20000000000-ffffe200029fffff] PMD -> [ffff880001200000-ffff880003bfffff] on node 0
> Zone PFN ranges:
>   DMA      0x00000000 -> 0x00001000
>   DMA32    0x00001000 -> 0x00100000
>   Normal   0x00100000 -> 0x00100000
> Movable zone start PFN for each node
> early_node_map[8] active PFN ranges
>     0: 0x00000000 -> 0x0000009d
>     0: 0x00000100 -> 0x000bce51
>     0: 0x000bce57 -> 0x000bd058
>     0: 0x000bd0af -> 0x000bd1a8
>     0: 0x000bd4af -> 0x000bd4d8
>     0: 0x000bd4df -> 0x000bd535
>     0: 0x000bd57f -> 0x000bd5e4
>     0: 0x000bd5fd -> 0x000bd600
> On node 0 totalpages: 774607
>   DMA zone: 56 pages used for memmap
>   DMA zone: 2138 pages reserved
>   DMA zone: 1803 pages, LIFO batch:0
>   DMA32 zone: 10549 pages used for memmap
>   DMA32 zone: 760061 pages, LIFO batch:31
> ACPI: PM-Timer IO Port: 0x408
> ACPI: Local APIC address 0xfee00000
> ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
> ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
> ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
> ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
> IOAPIC[0]: apic_id 2, version 0, address 0xfec00000, GSI 0-23
> ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
> ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
> ACPI: IRQ0 used by override.
> ACPI: IRQ2 used by override.
> ACPI: IRQ9 used by override.
> Using ACPI (MADT) for SMP configuration information
> ACPI: HPET id: 0x8086a201 base: 0xfed00000
> SMP: Allowing 2 CPUs, 0 hotplug CPUs
> Allocating PCI resources starting at c2000000 (gap: c0000000:20000000)
> NR_CPUS:2 nr_cpumask_bits:2 nr_cpu_ids:2 nr_node_ids:1
> PERCPU: Allocating 49152 bytes of per cpu data
> Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 761864
> Kernel command line: auto BOOT_IMAGE=2.6.29-rc4-0002 rw root=0 video=vesafb:ywrap,pmipal,mtrr
> Initializing CPU#0
> PID hash table entries: 4096 (order: 12, 32768 bytes)
> Extended CMOS year: 2000
> Fast TSC calibration using PIT
> Detected 2526.896 MHz processor.
> Console: colour VGA+ 80x25
> console [tty0] enabled
> Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
> Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
> Checking aperture...
> No AGP bridge found
> Memory: 3040120k/3102720k available (4161k kernel code, 4292k absent, 57580k reserved, 1977k data, 1428k init)
> SLUB: Genslabs=12, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
> hpet clockevent registered
> HPET: 4 timers in total, 0 timers will be used for per-cpu timer
> Calibrating delay loop (skipped), value calculated using timer frequency.. 5055.36 BogoMIPS (lpj=8422986)
> Mount-cache hash table entries: 256
> CPU: L1 I cache: 32K, L1 D cache: 32K
> CPU: L2 cache: 6144K
> [ds] using Core 2/Atom configuration
> CPU: Physical Processor ID: 0
> CPU: Processor Core ID: 0
> CPU0: Thermal monitoring enabled (TM2)
> using mwait in idle threads.
> Freeing SMP alternatives: 37k freed
> ACPI: Core revision 20081204
> Setting APIC routing to flat
> ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
> CPU0: Intel(R) Core(TM)2 Duo CPU     T9400  @ 2.53GHz stepping 06
> Booting processor 1 APIC 0x1 ip 0x6000
> Initializing CPU#1
> Calibrating delay using timer specific routine.. 5056.56 BogoMIPS (lpj=8423304)
> CPU: L1 I cache: 32K, L1 D cache: 32K
> CPU: L2 cache: 6144K
> [ds] using Core 2/Atom configuration
> CPU: Physical Processor ID: 0
> CPU: Processor Core ID: 1
> CPU1: Thermal monitoring enabled (TM2)
> x86 PAT enabled: cpu 1, old 0x7040600070406, new 0x7010600070106
> CPU1: Intel(R) Core(TM)2 Duo CPU     T9400  @ 2.53GHz stepping 06
> checking TSC synchronization [CPU#0 -> CPU#1]: passed.
> Brought up 2 CPUs
> Total of 2 processors activated (10111.93 BogoMIPS).
> net_namespace: 960 bytes
> NET: Registered protocol family 16
> ACPI: bus type pci registered
> PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
> PCI: MCFG area at e0000000 reserved in E820
> PCI: Using MMCONFIG at e0000000 - efffffff
> PCI: Using configuration type 1 for base access
> mtrr: your CPUs had inconsistent variable MTRR settings
> mtrr: probably your BIOS does not setup all CPUs.
> mtrr: corrected configuration.
> bio: create slab <bio-0> at 0
> ACPI: EC: Look up EC in DSDT
> ACPI: SSDT BD56E965, 03F1 (r1 FUJ    FJNB1E6   1160000 FUJ       100)
> ACPI: Interpreter enabled
> ACPI: (supports S0 S5)
> ACPI: Using IOAPIC for interrupt routing
> ACPI: EC: GPE = 0x17, I/O: command/status = 0x66, data = 0x62
> ACPI: EC: driver started in poll mode
> ACPI: ACPI Dock Station Driver: 2 docks/bays found
> ACPI: PCI Root Bridge [PCI0] (0000:00)
> pci 0000:00:02.0: reg 10 64bit mmio: [0xf0000000-0xf03fffff]
> pci 0000:00:02.0: reg 18 64bit mmio: [0xd0000000-0xdfffffff]
> pci 0000:00:02.0: reg 20 io port: [0x1800-0x1807]
> pci 0000:00:02.1: reg 10 64bit mmio: [0xf0400000-0xf04fffff]
> pci 0000:00:1a.0: reg 20 io port: [0x1820-0x183f]
> pci 0000:00:1a.1: reg 20 io port: [0x1840-0x185f]
> pci 0000:00:1a.2: reg 20 io port: [0x1860-0x187f]
> pci 0000:00:1a.7: reg 10 32bit mmio: [0xf0a04800-0xf0a04bff]
> pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
> pci 0000:00:1a.7: PME# disabled
> pci 0000:00:1b.0: reg 10 64bit mmio: [0xf0a00000-0xf0a03fff]
> pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
> pci 0000:00:1b.0: PME# disabled
> pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
> pci 0000:00:1c.0: PME# disabled
> pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
> pci 0000:00:1c.2: PME# disabled
> pci 0000:00:1d.0: reg 20 io port: [0x1880-0x189f]
> pci 0000:00:1d.1: reg 20 io port: [0x18a0-0x18bf]
> pci 0000:00:1d.2: reg 20 io port: [0x18c0-0x18df]
> pci 0000:00:1d.7: reg 10 32bit mmio: [0xf0a04c00-0xf0a04fff]
> pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
> pci 0000:00:1d.7: PME# disabled
> pci 0000:00:1f.2: reg 10 io port: [0x1818-0x181f]
> pci 0000:00:1f.2: reg 14 io port: [0x180c-0x180f]
> pci 0000:00:1f.2: reg 18 io port: [0x1810-0x1817]
> pci 0000:00:1f.2: reg 1c io port: [0x1808-0x180b]
> pci 0000:00:1f.2: reg 20 io port: [0x18e0-0x18ff]
> pci 0000:00:1f.2: reg 24 32bit mmio: [0xf0a04000-0xf0a047ff]
> pci 0000:00:1f.2: PME# supported from D3hot
> pci 0000:00:1f.2: PME# disabled
> pci 0000:00:1f.3: reg 10 64bit mmio: [0x000000-0x0000ff]
> pci 0000:00:1f.3: reg 20 io port: [0x1c00-0x1c1f]
> pci 0000:08:00.0: reg 10 64bit mmio: [0xf0500000-0xf0503fff]
> pci 0000:08:00.0: reg 18 io port: [0x2000-0x20ff]
> pci 0000:08:00.0: reg 30 32bit mmio: [0x000000-0x01ffff]
> pci 0000:08:00.0: supports D1 D2
> pci 0000:08:00.0: PME# supported from D0 D1 D2 D3hot D3cold
> pci 0000:08:00.0: PME# disabled
> pci 0000:00:1c.0: bridge io port: [0x2000-0x2fff]
> pci 0000:00:1c.0: bridge 32bit mmio: [0xf0500000-0xf05fffff]
> pci 0000:18:00.0: reg 10 64bit mmio: [0xf0600000-0xf0601fff]
> pci 0000:18:00.0: PME# supported from D0 D3hot D3cold
> pci 0000:18:00.0: PME# disabled
> pci 0000:00:1c.2: bridge 32bit mmio: [0xf0600000-0xf06fffff]
> pci 0000:38:03.0: reg 10 32bit mmio: [0x000000-0x000fff]
> pci 0000:38:03.0: supports D1 D2
> pci 0000:38:03.0: PME# supported from D0 D1 D2 D3hot D3cold
> pci 0000:38:03.0: PME# disabled
> pci 0000:38:03.2: reg 10 32bit mmio: [0xf0700000-0xf07000ff]
> pci 0000:38:03.2: supports D1 D2
> pci 0000:38:03.2: PME# supported from D0 D1 D2 D3hot D3cold
> pci 0000:38:03.2: PME# disabled
> pci 0000:38:03.3: reg 10 32bit mmio: [0xf0701000-0xf0701fff]
> pci 0000:38:03.3: supports D1 D2
> pci 0000:38:03.3: PME# supported from D0 D1 D2 D3hot D3cold
> pci 0000:38:03.3: PME# disabled
> pci 0000:38:03.4: reg 10 32bit mmio: [0xf0702000-0xf0702fff]
> pci 0000:38:03.4: reg 14 32bit mmio: [0xf0700800-0xf0700fff]
> pci 0000:38:03.4: supports D1 D2
> pci 0000:38:03.4: PME# supported from D0 D1 D2 D3hot
> pci 0000:38:03.4: PME# disabled
> pci 0000:00:1e.0: transparent bridge
> pci 0000:00:1e.0: bridge 32bit mmio: [0xf0700000-0xf07fffff]
> pci_bus 0000:00: on NUMA node 0
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP01._PRT]
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP03._PRT]
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIB._PRT]
> ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 10 12 14 15) *11
> ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 7 *11 12 14 15)
> ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 10 12 14 15) *11
> ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 *11 12 14 15)
> ACPI: PCI Interrupt Link [LNKE] (IRQs 1 3 4 5 6 7 10 12 14 15) *0, disabled.
> ACPI: PCI Interrupt Link [LNKF] (IRQs 1 3 4 5 6 7 11 12 14 15) *0, disabled.
> ACPI: PCI Interrupt Link [LNKG] (IRQs 1 3 4 5 6 7 10 12 14 15) *11
> ACPI: PCI Interrupt Link [LNKH] (IRQs 1 3 4 5 6 7 *11 12 14 15)
> SCSI subsystem initialized
> libata version 3.00 loaded.
> usbcore: registered new interface driver usbfs
> usbcore: registered new interface driver hub
> usbcore: registered new device driver usb
> PCI: Using ACPI for IRQ routing
> Bluetooth: Core ver 2.14
> NET: Registered protocol family 31
> Bluetooth: HCI device and connection manager initialized
> Bluetooth: HCI socket layer initialized
> cfg80211: Calling CRDA to update world regulatory domain
> cfg80211: calling CRDA failed - unable to update world regulatory domain, using static definition

OK please use the new patch series I am about to post to test why this is
happening. And I am perplexed as to why you have 5 GHz disabled because
wiphy->custom_regulatory is enabled for intel the iwlagn driver and upon
wiphy registration we have a check to see if this is set and if the last
regulatory hint came from the core, if this is true we don't update the
wiphy's channels based on the regulatory domain:

        if (!last_request)
                return true;
        if (setby == REGDOM_SET_BY_CORE &&
                  wiphy->custom_regulatory)
                return true

Please run with my latest patch series or wait until it gets merged,
we'll be able to do a trace of your udev even failing to call CRDA
and the core initialization will be much easier to read.

  Luis

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: IWL5300, 2.6.29-rc4, CRDA 1.0.1: Missing out 802.11A frequency ranges
  2009-02-14  4:52                   ` Luis R. Rodriguez
@ 2009-02-14  5:02                     ` Luis R. Rodriguez
  2009-02-16 12:08                     ` Tony Vroon
  1 sibling, 0 replies; 20+ messages in thread
From: Luis R. Rodriguez @ 2009-02-14  5:02 UTC (permalink / raw)
  To: Luis Rodriguez
  Cc: Tony Vroon, linux-wireless, reinette chatre, John W. Linville

On Fri, Feb 13, 2009 at 08:52:32PM -0800, Luis Rodriguez wrote:
> On Wed, Feb 11, 2009 at 11:19:41AM -0800, Tony Vroon wrote:
> > Clear run, haven't touched iw, still no 802.11A spectrum. dmesg
> > attached. Any suggestion for a workaround that will get me my networks
> > back please? (Besides enabling the old regulatory options, which is
> > scheduled to be taken away from me soon)
> >
> > Regards,
> > Tony V.
> 
> > Linux version 2.6.29-rc4-00026-gf06da26 (root@amalthea) (gcc version 4.3.3 (Gentoo 4.3.3 p1.0, pie-10.1.5) ) #1 SMP Mon Feb 9 18:55:10 GMT 2009
> > Command line: auto BOOT_IMAGE=2.6.29-rc4-0002 rw root=0 video=vesafb:ywrap,pmipal,mtrr
> > KERNEL supported cpus:
> >   Intel GenuineIntel
> >   AMD AuthenticAMD
> >   Centaur CentaurHauls
> > BIOS-provided physical RAM map:
> >  BIOS-e820: 0000000000000000 - 000000000009d400 (usable)
> >  BIOS-e820: 000000000009d400 - 00000000000a0000 (reserved)
> >  BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
> >  BIOS-e820: 0000000000100000 - 00000000bce51000 (usable)
> >  BIOS-e820: 00000000bce51000 - 00000000bce57000 (reserved)
> >  BIOS-e820: 00000000bce57000 - 00000000bd058000 (usable)
> >  BIOS-e820: 00000000bd058000 - 00000000bd0af000 (reserved)
> >  BIOS-e820: 00000000bd0af000 - 00000000bd1a8000 (usable)
> >  BIOS-e820: 00000000bd1a8000 - 00000000bd4af000 (reserved)
> >  BIOS-e820: 00000000bd4af000 - 00000000bd4d8000 (usable)
> >  BIOS-e820: 00000000bd4d8000 - 00000000bd4df000 (reserved)
> >  BIOS-e820: 00000000bd4df000 - 00000000bd535000 (usable)
> >  BIOS-e820: 00000000bd535000 - 00000000bd57f000 (ACPI NVS)
> >  BIOS-e820: 00000000bd57f000 - 00000000bd5e4000 (usable)
> >  BIOS-e820: 00000000bd5e4000 - 00000000bd5fd000 (ACPI data)
> >  BIOS-e820: 00000000bd5fd000 - 00000000bd600000 (usable)
> >  BIOS-e820: 00000000bd600000 - 00000000c0000000 (reserved)
> >  BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
> >  BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
> >  BIOS-e820: 00000000fed00000 - 00000000fed00400 (reserved)
> >  BIOS-e820: 00000000fed10000 - 00000000fed14000 (reserved)
> >  BIOS-e820: 00000000fed18000 - 00000000fed1a000 (reserved)
> >  BIOS-e820: 00000000fed1c000 - 00000000fed90000 (reserved)
> >  BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
> >  BIOS-e820: 00000000ff800000 - 0000000100000000 (reserved)
> > DMI 2.4 present.
> > last_pfn = 0xbd600 max_arch_pfn = 0x100000000
> > x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
> > init_memory_mapping: 0000000000000000-00000000bd600000
> >  0000000000 - 00bd600000 page 2M
> > kernel direct mapping tables up to bd600000 @ 8000-c000
> > last_map_addr: bd600000 end: bd600000
> > ACPI: RSDP 000F53D0, 0024 (r2 FUJ   )
> > ACPI: XSDT BD5F3434, 0074 (r1 FSC    PC        1160000 FUJ       100)
> > ACPI: FACP BD5E6000, 00F4 (r3 FSC    PC        1160000 FUJ       100)
> > FADT: X_PM1a_EVT_BLK.bit_width (16) does not match PM1_EVT_LEN (4)
> > ACPI: DSDT BD5E7000, 8CFF (r1 FUJ    FJNB1E6   1160000 FUJ       100)
> > ACPI: FACS BD56EFC0, 0040
> > ACPI: SSDT BD5FC1DF, 034F (r1 FUJ    FJNB1E6   1160000 FUJ       100)
> > ACPI: HPET BD5FC622, 0038 (r1 FUJ    FJNB1E6   1160000 FUJ       100)
> > ACPI: MCFG BD5FC65A, 003C (r1 FUJ    FJNB1E6   1160000 FUJ       100)
> > ACPI: SSDT BD5FC696, 042F (r1 FUJ    FJNB1E6   1160000 FUJ       100)
> > ACPI: SSDT BD5FCAC5, 02C1 (r1 FUJ    FJNB1E6   1160000 FUJ       100)
> > ACPI: APIC BD5FCD86, 0068 (r1 FUJ    FJNB1E6   1160000 FUJ       100)
> > ACPI: BOOT BD5FCDEE, 0028 (r1 FUJ    FJNB1E6   1160000 FUJ       100)
> > ACPI: SLIC BD5FCE16, 0176 (r1 FSC    PC        1160000 FUJ       100)
> > ACPI: SSDT BD5E5000, 04E6 (r1  PmRef    CpuPm     3000 INTL 20050624)
> > ACPI: Local APIC address 0xfee00000
> > (5 early reservations) ==> bootmem [0000000000 - 00bd600000]
> >   #0 [0000000000 - 0000001000]   BIOS data page ==> [0000000000 - 0000001000]
> >   #1 [0000006000 - 0000008000]       TRAMPOLINE ==> [0000006000 - 0000008000]
> >   #2 [0000200000 - 00009f3dec]    TEXT DATA BSS ==> [0000200000 - 00009f3dec]
> >   #3 [000009d400 - 0000100000]    BIOS reserved ==> [000009d400 - 0000100000]
> >   #4 [0000008000 - 000000a000]          PGTABLE ==> [0000008000 - 000000a000]
> >  [ffffe20000000000-ffffe200029fffff] PMD -> [ffff880001200000-ffff880003bfffff] on node 0
> > Zone PFN ranges:
> >   DMA      0x00000000 -> 0x00001000
> >   DMA32    0x00001000 -> 0x00100000
> >   Normal   0x00100000 -> 0x00100000
> > Movable zone start PFN for each node
> > early_node_map[8] active PFN ranges
> >     0: 0x00000000 -> 0x0000009d
> >     0: 0x00000100 -> 0x000bce51
> >     0: 0x000bce57 -> 0x000bd058
> >     0: 0x000bd0af -> 0x000bd1a8
> >     0: 0x000bd4af -> 0x000bd4d8
> >     0: 0x000bd4df -> 0x000bd535
> >     0: 0x000bd57f -> 0x000bd5e4
> >     0: 0x000bd5fd -> 0x000bd600
> > On node 0 totalpages: 774607
> >   DMA zone: 56 pages used for memmap
> >   DMA zone: 2138 pages reserved
> >   DMA zone: 1803 pages, LIFO batch:0
> >   DMA32 zone: 10549 pages used for memmap
> >   DMA32 zone: 760061 pages, LIFO batch:31
> > ACPI: PM-Timer IO Port: 0x408
> > ACPI: Local APIC address 0xfee00000
> > ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
> > ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
> > ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
> > ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
> > ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
> > IOAPIC[0]: apic_id 2, version 0, address 0xfec00000, GSI 0-23
> > ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
> > ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
> > ACPI: IRQ0 used by override.
> > ACPI: IRQ2 used by override.
> > ACPI: IRQ9 used by override.
> > Using ACPI (MADT) for SMP configuration information
> > ACPI: HPET id: 0x8086a201 base: 0xfed00000
> > SMP: Allowing 2 CPUs, 0 hotplug CPUs
> > Allocating PCI resources starting at c2000000 (gap: c0000000:20000000)
> > NR_CPUS:2 nr_cpumask_bits:2 nr_cpu_ids:2 nr_node_ids:1
> > PERCPU: Allocating 49152 bytes of per cpu data
> > Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 761864
> > Kernel command line: auto BOOT_IMAGE=2.6.29-rc4-0002 rw root=0 video=vesafb:ywrap,pmipal,mtrr
> > Initializing CPU#0
> > PID hash table entries: 4096 (order: 12, 32768 bytes)
> > Extended CMOS year: 2000
> > Fast TSC calibration using PIT
> > Detected 2526.896 MHz processor.
> > Console: colour VGA+ 80x25
> > console [tty0] enabled
> > Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
> > Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
> > Checking aperture...
> > No AGP bridge found
> > Memory: 3040120k/3102720k available (4161k kernel code, 4292k absent, 57580k reserved, 1977k data, 1428k init)
> > SLUB: Genslabs=12, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
> > hpet clockevent registered
> > HPET: 4 timers in total, 0 timers will be used for per-cpu timer
> > Calibrating delay loop (skipped), value calculated using timer frequency.. 5055.36 BogoMIPS (lpj=8422986)
> > Mount-cache hash table entries: 256
> > CPU: L1 I cache: 32K, L1 D cache: 32K
> > CPU: L2 cache: 6144K
> > [ds] using Core 2/Atom configuration
> > CPU: Physical Processor ID: 0
> > CPU: Processor Core ID: 0
> > CPU0: Thermal monitoring enabled (TM2)
> > using mwait in idle threads.
> > Freeing SMP alternatives: 37k freed
> > ACPI: Core revision 20081204
> > Setting APIC routing to flat
> > ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
> > CPU0: Intel(R) Core(TM)2 Duo CPU     T9400  @ 2.53GHz stepping 06
> > Booting processor 1 APIC 0x1 ip 0x6000
> > Initializing CPU#1
> > Calibrating delay using timer specific routine.. 5056.56 BogoMIPS (lpj=8423304)
> > CPU: L1 I cache: 32K, L1 D cache: 32K
> > CPU: L2 cache: 6144K
> > [ds] using Core 2/Atom configuration
> > CPU: Physical Processor ID: 0
> > CPU: Processor Core ID: 1
> > CPU1: Thermal monitoring enabled (TM2)
> > x86 PAT enabled: cpu 1, old 0x7040600070406, new 0x7010600070106
> > CPU1: Intel(R) Core(TM)2 Duo CPU     T9400  @ 2.53GHz stepping 06
> > checking TSC synchronization [CPU#0 -> CPU#1]: passed.
> > Brought up 2 CPUs
> > Total of 2 processors activated (10111.93 BogoMIPS).
> > net_namespace: 960 bytes
> > NET: Registered protocol family 16
> > ACPI: bus type pci registered
> > PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
> > PCI: MCFG area at e0000000 reserved in E820
> > PCI: Using MMCONFIG at e0000000 - efffffff
> > PCI: Using configuration type 1 for base access
> > mtrr: your CPUs had inconsistent variable MTRR settings
> > mtrr: probably your BIOS does not setup all CPUs.
> > mtrr: corrected configuration.
> > bio: create slab <bio-0> at 0
> > ACPI: EC: Look up EC in DSDT
> > ACPI: SSDT BD56E965, 03F1 (r1 FUJ    FJNB1E6   1160000 FUJ       100)
> > ACPI: Interpreter enabled
> > ACPI: (supports S0 S5)
> > ACPI: Using IOAPIC for interrupt routing
> > ACPI: EC: GPE = 0x17, I/O: command/status = 0x66, data = 0x62
> > ACPI: EC: driver started in poll mode
> > ACPI: ACPI Dock Station Driver: 2 docks/bays found
> > ACPI: PCI Root Bridge [PCI0] (0000:00)
> > pci 0000:00:02.0: reg 10 64bit mmio: [0xf0000000-0xf03fffff]
> > pci 0000:00:02.0: reg 18 64bit mmio: [0xd0000000-0xdfffffff]
> > pci 0000:00:02.0: reg 20 io port: [0x1800-0x1807]
> > pci 0000:00:02.1: reg 10 64bit mmio: [0xf0400000-0xf04fffff]
> > pci 0000:00:1a.0: reg 20 io port: [0x1820-0x183f]
> > pci 0000:00:1a.1: reg 20 io port: [0x1840-0x185f]
> > pci 0000:00:1a.2: reg 20 io port: [0x1860-0x187f]
> > pci 0000:00:1a.7: reg 10 32bit mmio: [0xf0a04800-0xf0a04bff]
> > pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
> > pci 0000:00:1a.7: PME# disabled
> > pci 0000:00:1b.0: reg 10 64bit mmio: [0xf0a00000-0xf0a03fff]
> > pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
> > pci 0000:00:1b.0: PME# disabled
> > pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
> > pci 0000:00:1c.0: PME# disabled
> > pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
> > pci 0000:00:1c.2: PME# disabled
> > pci 0000:00:1d.0: reg 20 io port: [0x1880-0x189f]
> > pci 0000:00:1d.1: reg 20 io port: [0x18a0-0x18bf]
> > pci 0000:00:1d.2: reg 20 io port: [0x18c0-0x18df]
> > pci 0000:00:1d.7: reg 10 32bit mmio: [0xf0a04c00-0xf0a04fff]
> > pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
> > pci 0000:00:1d.7: PME# disabled
> > pci 0000:00:1f.2: reg 10 io port: [0x1818-0x181f]
> > pci 0000:00:1f.2: reg 14 io port: [0x180c-0x180f]
> > pci 0000:00:1f.2: reg 18 io port: [0x1810-0x1817]
> > pci 0000:00:1f.2: reg 1c io port: [0x1808-0x180b]
> > pci 0000:00:1f.2: reg 20 io port: [0x18e0-0x18ff]
> > pci 0000:00:1f.2: reg 24 32bit mmio: [0xf0a04000-0xf0a047ff]
> > pci 0000:00:1f.2: PME# supported from D3hot
> > pci 0000:00:1f.2: PME# disabled
> > pci 0000:00:1f.3: reg 10 64bit mmio: [0x000000-0x0000ff]
> > pci 0000:00:1f.3: reg 20 io port: [0x1c00-0x1c1f]
> > pci 0000:08:00.0: reg 10 64bit mmio: [0xf0500000-0xf0503fff]
> > pci 0000:08:00.0: reg 18 io port: [0x2000-0x20ff]
> > pci 0000:08:00.0: reg 30 32bit mmio: [0x000000-0x01ffff]
> > pci 0000:08:00.0: supports D1 D2
> > pci 0000:08:00.0: PME# supported from D0 D1 D2 D3hot D3cold
> > pci 0000:08:00.0: PME# disabled
> > pci 0000:00:1c.0: bridge io port: [0x2000-0x2fff]
> > pci 0000:00:1c.0: bridge 32bit mmio: [0xf0500000-0xf05fffff]
> > pci 0000:18:00.0: reg 10 64bit mmio: [0xf0600000-0xf0601fff]
> > pci 0000:18:00.0: PME# supported from D0 D3hot D3cold
> > pci 0000:18:00.0: PME# disabled
> > pci 0000:00:1c.2: bridge 32bit mmio: [0xf0600000-0xf06fffff]
> > pci 0000:38:03.0: reg 10 32bit mmio: [0x000000-0x000fff]
> > pci 0000:38:03.0: supports D1 D2
> > pci 0000:38:03.0: PME# supported from D0 D1 D2 D3hot D3cold
> > pci 0000:38:03.0: PME# disabled
> > pci 0000:38:03.2: reg 10 32bit mmio: [0xf0700000-0xf07000ff]
> > pci 0000:38:03.2: supports D1 D2
> > pci 0000:38:03.2: PME# supported from D0 D1 D2 D3hot D3cold
> > pci 0000:38:03.2: PME# disabled
> > pci 0000:38:03.3: reg 10 32bit mmio: [0xf0701000-0xf0701fff]
> > pci 0000:38:03.3: supports D1 D2
> > pci 0000:38:03.3: PME# supported from D0 D1 D2 D3hot D3cold
> > pci 0000:38:03.3: PME# disabled
> > pci 0000:38:03.4: reg 10 32bit mmio: [0xf0702000-0xf0702fff]
> > pci 0000:38:03.4: reg 14 32bit mmio: [0xf0700800-0xf0700fff]
> > pci 0000:38:03.4: supports D1 D2
> > pci 0000:38:03.4: PME# supported from D0 D1 D2 D3hot
> > pci 0000:38:03.4: PME# disabled
> > pci 0000:00:1e.0: transparent bridge
> > pci 0000:00:1e.0: bridge 32bit mmio: [0xf0700000-0xf07fffff]
> > pci_bus 0000:00: on NUMA node 0
> > ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
> > ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP01._PRT]
> > ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP03._PRT]
> > ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIB._PRT]
> > ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 10 12 14 15) *11
> > ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 7 *11 12 14 15)
> > ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 10 12 14 15) *11
> > ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 *11 12 14 15)
> > ACPI: PCI Interrupt Link [LNKE] (IRQs 1 3 4 5 6 7 10 12 14 15) *0, disabled.
> > ACPI: PCI Interrupt Link [LNKF] (IRQs 1 3 4 5 6 7 11 12 14 15) *0, disabled.
> > ACPI: PCI Interrupt Link [LNKG] (IRQs 1 3 4 5 6 7 10 12 14 15) *11
> > ACPI: PCI Interrupt Link [LNKH] (IRQs 1 3 4 5 6 7 *11 12 14 15)
> > SCSI subsystem initialized
> > libata version 3.00 loaded.
> > usbcore: registered new interface driver usbfs
> > usbcore: registered new interface driver hub
> > usbcore: registered new device driver usb
> > PCI: Using ACPI for IRQ routing
> > Bluetooth: Core ver 2.14
> > NET: Registered protocol family 31
> > Bluetooth: HCI device and connection manager initialized
> > Bluetooth: HCI socket layer initialized
> > cfg80211: Calling CRDA to update world regulatory domain
> > cfg80211: calling CRDA failed - unable to update world regulatory domain, using static definition
> 
> OK please use the new patch series I am about to post to test why this is
> happening. And I am perplexed as to why you have 5 GHz disabled because
> wiphy->custom_regulatory is enabled for intel the iwlagn driver and upon
> wiphy registration we have a check to see if this is set and if the last
> regulatory hint came from the core, if this is true we don't update the
> wiphy's channels based on the regulatory domain:
> 
>         if (!last_request)
>                 return true;
>         if (setby == REGDOM_SET_BY_CORE &&
>                   wiphy->custom_regulatory)
>                 return true
> 
> Please run with my latest patch series or wait until it gets merged,
> we'll be able to do a trace of your udev even failing to call CRDA
> and the core initialization will be much easier to read.

Actually, upon further investigation it may just be that the iwlagn driver
is simply respecting your EEPROM settings. Enable IWL_DEBUG_INFO and recompile
and spit the log out here.
              
  Luis

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: IWL5300, 2.6.29-rc4, CRDA 1.0.1: Missing out 802.11A frequency ranges
  2009-02-14  4:52                   ` Luis R. Rodriguez
  2009-02-14  5:02                     ` Luis R. Rodriguez
@ 2009-02-16 12:08                     ` Tony Vroon
  2009-02-16 15:47                       ` John W. Linville
  1 sibling, 1 reply; 20+ messages in thread
From: Tony Vroon @ 2009-02-16 12:08 UTC (permalink / raw)
  To: Luis R. Rodriguez
  Cc: Luis Rodriguez, linux-wireless, reinette chatre, John W. Linville

[-- Attachment #1: Type: text/plain, Size: 444 bytes --]

Just to confirm, if I use my early-boot hook that I used for your iw
list to set the regulatory domain manually (iw reg set GB) all is well.
If I allow the driver stack to get to the association stage without
setting a regulatory domain, I can never get my 802.11A spectrum back
after the fact.
Would you still see this as a bug or rather a specific requirement of
the new interface that hasn't yet been documented?

Regards,
Tony V.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: IWL5300, 2.6.29-rc4, CRDA 1.0.1: Missing out 802.11A frequency ranges
  2009-02-16 12:08                     ` Tony Vroon
@ 2009-02-16 15:47                       ` John W. Linville
  2009-02-17 18:42                         ` Luis R. Rodriguez
  0 siblings, 1 reply; 20+ messages in thread
From: John W. Linville @ 2009-02-16 15:47 UTC (permalink / raw)
  To: Tony Vroon
  Cc: Luis R. Rodriguez, Luis Rodriguez, linux-wireless, reinette chatre

On Mon, Feb 16, 2009 at 12:08:44PM +0000, Tony Vroon wrote:
> Just to confirm, if I use my early-boot hook that I used for your iw
> list to set the regulatory domain manually (iw reg set GB) all is well.
> If I allow the driver stack to get to the association stage without
> setting a regulatory domain, I can never get my 802.11A spectrum back
> after the fact.
> Would you still see this as a bug or rather a specific requirement of
> the new interface that hasn't yet been documented?

Seems like a bug, or at least an unintended consequence of intersection...?

-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: IWL5300, 2.6.29-rc4, CRDA 1.0.1: Missing out 802.11A frequency ranges
  2009-02-16 15:47                       ` John W. Linville
@ 2009-02-17 18:42                         ` Luis R. Rodriguez
  2009-02-17 19:06                           ` Luis R. Rodriguez
  0 siblings, 1 reply; 20+ messages in thread
From: Luis R. Rodriguez @ 2009-02-17 18:42 UTC (permalink / raw)
  To: John W. Linville
  Cc: Tony Vroon, Luis Rodriguez, linux-wireless, reinette chatre

On Mon, Feb 16, 2009 at 07:47:33AM -0800, John W. Linville wrote:
> On Mon, Feb 16, 2009 at 12:08:44PM +0000, Tony Vroon wrote:
> > Just to confirm, if I use my early-boot hook that I used for your iw
> > list to set the regulatory domain manually (iw reg set GB) all is well.
> > If I allow the driver stack to get to the association stage without
> > setting a regulatory domain, I can never get my 802.11A spectrum back
> > after the fact.
> > Would you still see this as a bug or rather a specific requirement of
> > the new interface that hasn't yet been documented?
> 
> Seems like a bug, or at least an unintended consequence of intersection...?



^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: IWL5300, 2.6.29-rc4, CRDA 1.0.1: Missing out 802.11A frequency ranges
  2009-02-17 18:42                         ` Luis R. Rodriguez
@ 2009-02-17 19:06                           ` Luis R. Rodriguez
  2009-02-20  6:12                             ` Luis R. Rodriguez
  0 siblings, 1 reply; 20+ messages in thread
From: Luis R. Rodriguez @ 2009-02-17 19:06 UTC (permalink / raw)
  To: Luis Rodriguez
  Cc: John W. Linville, Tony Vroon, linux-wireless, reinette chatre

On Tue, Feb 17, 2009 at 10:42:30AM -0800, Luis Rodriguez wrote:
> On Mon, Feb 16, 2009 at 07:47:33AM -0800, John W. Linville wrote:
> > On Mon, Feb 16, 2009 at 12:08:44PM +0000, Tony Vroon wrote:
> > > Just to confirm, if I use my early-boot hook that I used for your iw
> > > list to set the regulatory domain manually (iw reg set GB) all is well.
> > > If I allow the driver stack to get to the association stage without
> > > setting a regulatory domain, I can never get my 802.11A spectrum back
> > > after the fact.
> > > Would you still see this as a bug or rather a specific requirement of
> > > the new interface that hasn't yet been documented?
> >
> > Seems like a bug, or at least an unintended consequence of intersection...?

Sorry for the blank e-mail.

You are reporting you are disabling OLD_REG and your 5 GHz on iwlagn is disabled
upon bootup. You also reported from your log:

cfg80211: Calling CRDA to update world regulatory domain
cfg80211: calling CRDA failed - unable to update world regulatory domain, using static definition

This indicates to me your regulatory domain was simply never updated by CRDA. So what
would have happened is that iwlagn registers its device to mac80211 via ieee80211_register_hw()
then mac80211 registers it with cfg80211 via wiphy_register(). Upon that call cfg80211 will update
the device's regulatory ifnromation by calling

wiphy_update_regulatory(wiphy, REGDOM_SET_BY_CORE);

This in turn will check to see if it should ignore the request, and in your case
the check is:

        if (!last_request)
                return true;
        if (setby == REGDOM_SET_BY_CORE &&
                  wiphy->custom_regulatory)
                return true

Since iwlagn sets wiphy->custom_regulatory to true and since upon registration setby is
REGDOM_SET_BY_CORE the device will be ignored to change the regulatory domain. I see I
currently see no reason why your 5 GHz channels will be disabled unless I'm missing
something or the card's EEPROM disables them.

To debug this further we need more information. So please provide the output of both
the kernel *and*, 'iw list' _prior_ to associating to your AP. Before you do so please
recompile wireless-testing with these options enabled:

# Intel debug
CONFIG_IWL_DEBUG_INFO=y

# Cfg80211 regulatory debug
CONFIG_CFG80211_REG_DEBUG=y

So to re-iterate: I want both your kernel log _and_ 'iw list' output prior to association.

  Luis

^ permalink raw reply	[flat|nested] 20+ messages in thread

* Re: IWL5300, 2.6.29-rc4, CRDA 1.0.1: Missing out 802.11A frequency ranges
  2009-02-17 19:06                           ` Luis R. Rodriguez
@ 2009-02-20  6:12                             ` Luis R. Rodriguez
  0 siblings, 0 replies; 20+ messages in thread
From: Luis R. Rodriguez @ 2009-02-20  6:12 UTC (permalink / raw)
  To: Luis Rodriguez
  Cc: John W. Linville, Tony Vroon, linux-wireless, reinette chatre

On Tue, Feb 17, 2009 at 11:06:46AM -0800, Luis Rodriguez wrote:
> On Tue, Feb 17, 2009 at 10:42:30AM -0800, Luis Rodriguez wrote:
> > On Mon, Feb 16, 2009 at 07:47:33AM -0800, John W. Linville wrote:
> > > On Mon, Feb 16, 2009 at 12:08:44PM +0000, Tony Vroon wrote:
> > > > Just to confirm, if I use my early-boot hook that I used for your iw
> > > > list to set the regulatory domain manually (iw reg set GB) all is well.
> > > > If I allow the driver stack to get to the association stage without
> > > > setting a regulatory domain, I can never get my 802.11A spectrum back
> > > > after the fact.
> > > > Would you still see this as a bug or rather a specific requirement of
> > > > the new interface that hasn't yet been documented?
> > >
> > > Seems like a bug, or at least an unintended consequence of intersection...?
> 
> Sorry for the blank e-mail.
> 
> You are reporting you are disabling OLD_REG and your 5 GHz on iwlagn is disabled
> upon bootup. You also reported from your log:
> 
> cfg80211: Calling CRDA to update world regulatory domain
> cfg80211: calling CRDA failed - unable to update world regulatory domain, using static definition
> 
> This indicates to me your regulatory domain was simply never updated by CRDA. So what
> would have happened is that iwlagn registers its device to mac80211 via ieee80211_register_hw()
> then mac80211 registers it with cfg80211 via wiphy_register(). Upon that call cfg80211 will update
> the device's regulatory ifnromation by calling
> 
> wiphy_update_regulatory(wiphy, REGDOM_SET_BY_CORE);
> 
> This in turn will check to see if it should ignore the request, and in your case
> the check is:
> 
>         if (!last_request)
>                 return true;
>         if (setby == REGDOM_SET_BY_CORE &&
>                   wiphy->custom_regulatory)
>                 return true
> 
> Since iwlagn sets wiphy->custom_regulatory to true and since upon registration setby is
> REGDOM_SET_BY_CORE the device will be ignored to change the regulatory domain. I see I
> currently see no reason why your 5 GHz channels will be disabled unless I'm missing
> something or the card's EEPROM disables them.
> 
> To debug this further we need more information. So please provide the output of both
> the kernel *and*, 'iw list' _prior_ to associating to your AP. Before you do so please
> recompile wireless-testing with these options enabled:
> 
> # Intel debug
> CONFIG_IWL_DEBUG_INFO=y
> 
> # Cfg80211 regulatory debug
> CONFIG_CFG80211_REG_DEBUG=y
> 
> So to re-iterate: I want both your kernel log _and_ 'iw list' output prior to association.

To help isolate that orthogonal issue about having the udev rule not being
created you can also test the new patch series I just posted and enable REG_DEBUG,
this will give us a trace and hopefully we can see if call_usermodehelper() was
the one that failed during early boot.

http://marc.info/?l=linux-wireless&m=123510990625914&w=2

  Luis

^ permalink raw reply	[flat|nested] 20+ messages in thread

end of thread, other threads:[~2009-02-20  6:12 UTC | newest]

Thread overview: 20+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-02-09 18:09 IWL5300, 2.6.29-rc4, CRDA 1.0.1: Missing out 802.11A frequency ranges Tony Vroon
2009-02-09 18:20 ` Luis R. Rodriguez
2009-02-09 18:22   ` Luis R. Rodriguez
2009-02-09 18:23   ` Tony Vroon
2009-02-09 18:39     ` John W. Linville
2009-02-09 19:21       ` Tony Vroon
2009-02-09 19:35         ` Tony Vroon
2009-02-10  1:39           ` Luis R. Rodriguez
2009-02-10  1:51             ` Tony Vroon
2009-02-10  2:07               ` Luis R. Rodriguez
2009-02-11 19:19                 ` Tony Vroon
2009-02-11 21:46                   ` Luis R. Rodriguez
2009-02-13 10:55                     ` Tony Vroon
2009-02-14  4:52                   ` Luis R. Rodriguez
2009-02-14  5:02                     ` Luis R. Rodriguez
2009-02-16 12:08                     ` Tony Vroon
2009-02-16 15:47                       ` John W. Linville
2009-02-17 18:42                         ` Luis R. Rodriguez
2009-02-17 19:06                           ` Luis R. Rodriguez
2009-02-20  6:12                             ` Luis R. Rodriguez

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.