Limitations off regulatory domains on a controller

Hello,
are there any limitations off the amount off used regulatory domains on a controller?
Sven

Hello Saravanan,
very good information.
But one question is open for me:
The quantity.
How many regualatory domains can I use on one controller simultaneous?
Unlimited?
Regard Sven

Similar Messages

  • Regulatory domain on WiSM Controller

    Can we change the regulatory domain of the WISM controller. The region I am working in, the max EIRP allowed in on 14 dBm. Is it a right step if I change the regulatpry domain of the WISM controller so that the EIRP of 1524 can be increased?

    The EIRP is observed on AP. The Radio elements ( including Antennae ) are present in AP not controllers. So if AP has been regulated to emit maxm @14dBm , you cannot observe more power beyond that even if you configure it via controllers.

  • Version 6.0.182 Australia Regulatory Domain 5 Gig radios OFF

    Version 5 software all works OK
    Upgrade to 6.0.128
    5Gig radios all disabled with error
    AP on the 802.11a radio with Base Radio MAC xx:xx:xx:xx:xx:xx (APxxx.xxxx.xxxx) is unable to associate. The regulatory domain configured on it '-A' does not match the controller's regulatory domain: -N
    The controller is set to Australia
    Configured Country Code(s) AU
    Regulatory Domain
    802.11a: -N
    802.11bg: -A
    The access point is a AIR-LAP1131AG-A-K9 (the one for Australia)
    http://www.cisco.com/en/US/prod/collateral/wireless/ps5679/ps5861/product_data_sheet0900aecd80537b6a.html#wp9004368
    all looks OK.
    What has broken since version 5.0 I could and the country US to the county list and get around but I should not have to do this

    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Tabla normal";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-qformat:yes;
    mso-style-parent:"";
    mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
    mso-para-margin:0cm;
    mso-para-margin-bottom:.0001pt;
    mso-pagination:widow-orphan;
    font-size:11.0pt;
    font-family:"Calibri","sans-serif";
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-fareast-font-family:"Times New Roman";
    mso-fareast-theme-font:minor-fareast;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;
    mso-bidi-font-family:"Times New Roman";
    mso-bidi-theme-font:minor-bidi;}
    Hi Charles,
    I am also Cisco Network Engineer and found you on Cisco Support Community forum. I would like to ask you something in regards to one of your topics if you don’t mind. You mentioned that you would be doing the following “I would also be changing the polarization of the antenna to be 90 degrees off the existing one. IE rotate the antenna by 90 degrees“, have you done it already? What was the result of this and why would you do that? You see I have also a client with 2 Yagis pointing at each other with a distance around 2.5km and AIR-BR1310 bridges. What I am looking for it to get the signal strength better because it seems like now and then the non-root bridge disassociate itself from the root bridge due to weak signal. I heard that by turning both antennas by 90 degrees (changing polarization) clockwise or anticlockwise you can actually improve the signal strength, is that correct? How do you actually do that, by turning the tube in relation to the horizontal axis?
    I would greatly appreciate you experience on that and ony other tips you would like to share with me.
    Best regards,
    Remi

  • Two different regulatory domains on one access point

    Hi
    we use a Cisco wireless controller (2500 series) with four access points (LAP1142N).
    All of these access points have the regulatory domain E (in the product name). Even the lateset access point we added. But this one cannot activate the second internal radio (5GHz) because of a not supported regulatory domain. The controller shows the first radio as 802.11bg:-E and the second radio as 802.11a:-C.
    Changing the location settings didn't effect anything. The second radio is still offline.
    Is there a way to change the regulatory domain of the second radio? Or was there a wrong radio/antenna-module installed? Or is it even a bug in the software?
    Thanks a lot for your help

    RMA the AP.

  • AP is unable to associate. The Regulatory Domain '-E' configured on interface '802.11a' does not match the Controller Regulatory Domain '-C'

    Hi,
    There are three different types of APs associated with controller and working fine.
    1.       AIR-LAP1252AG-E-K9
    2.       AIR-LAP1522AG-E-K9
    3.       AIR-CAP1552E-C-K9
    WLC is AIR-CT5508-K9. Software version is 7.4.100.0. Field Recovery Image is 7.0.112.21. Firmware version is FPGA 1.7, Env 1.8, USB console 2.2. WCS is 7.0.240.0 for Windows.
    WCS is sending alarms for AIR-LAP1522AG-E-K9:
    Message: AP is unable to associate. The Regulatory Domain '-E' configured on interface '802.11a' does not match the Controller Regulatory Domain '-C'.
    Before Controller was 7.2.4 (not sure).
    Country configured on WLC is AE and shows -CE regulatory domain. Mesh APs are also associated.
    I believe this Critical alarm should not come.
    how much is this alarm important? What should be done to resolve this?

    Typically you still need to make sure that the country codes are indeed configured on the WLC. Thing can change when you upgrade code as standards might of changed and regulations also. If your AP's are functional, then you should be okay and I wouldn't worry too much about it, but if after the upgrade, the WLC complains about country code stuff, then you just need to verify that the AP's country code is defined on the WLC. May times the AP will not join and if it does join, the radios might be disabled or in a down status.
    Sent from Cisco Technical Support iPad App

  • Is an AP got problem with multiple regulatory domain?

    Hello,
    Our customer in China reported that they got poor 2.4GHz wireless quality(i.e.slow response, slow data transfer). But these not happened on 5GHz band. The main WLC installed in Bangkok, Thailand. This controller take controll all their APs over the country and oversea branchs. We checked into the AP configurations and saw this..
    Regulatory Domains: 802.11bg:-E    802.11a:-C
    Country Code: CN (China)
    AP Part:     AIR-CAP2602I-C-K9
    After we checked these tables
    (http://www.cisco.com/en/US/prod/collateral/wireless/ps5679/ps5861/product_data_sheet0900aecd80537b6a.html#wp9005671)
    All regulatory domains for this AP should be -C right?
    We followed this page for configuring China country code.
    (http://www.cisco.com/en/US/docs/wireless/controller/7.4/configuration/guides/lwap/config_lwap_chapter_010000.html)
    I got noticed in guidelines and limitations
    Although the controller supports different access points in different regulatory domains (countries), it requires all radios in a single access point to be configured for the same regulatory domain. For example, you should not configure a Cisco 1231 access point’s 802.11b/g radio for the US (-A) regulatory domain and its 802.11a radio for the Great Britain (-E) regulatory domain. Otherwise, the controller allows only one of the access point’s radios to turn on, depending on which regulatory domain you selected for the access point on the controller.
    So, this should be a problem? or I hit a bug?
    WLC information:
    Part:                                       AIR-CT5508-K9
    Version:                                  7.3.112
    Configured Country Code(s):     TH,US,CN
    Regulatory Domain:                 802.11a: -ACE, 802.11bg: -ACE
    Thank you.

    This is not a bug. Refer to Cisco TAC response.
    Its not a bug, from the WLC you can run the command:
    Show country supported tx-power
    (WLC-5508-RAC1) >show country supported tx-power       KEY: ## = Tx Power in dBm.
               ##*= Channel supports radar detection.
                . = Channel is not legal in this country.
              = Regulatory Domains allowed by this country.
              (-,-) = (indoor, outdoor) regulatory Domains allowed by this country.
    -----------------:+--+--+--+--+--+--+--+--+--+--+--+--+--+--
        802.11BG     :                                         
        Channels     :                             1  1  1  1  1
                     :  1  2  3  4  5  6  7  8  9  0  1  2  3  4
    -----------------:+--+--+--+--+--+--+--+--+--+--+--+--+--+--
    (-CE  ,-CE  ) AE : 20 20 20 20 20 20 20 20 20 20 20 20 20  .
    (-A   ,-AR  ) AR : 27 27 27 27 27 27 27 27 27 27 27  .  .  .
    (-E   ,-E   ) AT : 20 20 20 20 20 20 20 20 20 20 20 20 20  .
    (-A   ,-NA  ) AU : 27 27 27 27 27 27 27 27 27 27 27  .  .  .
    (-E   ,-    ) BA : 20 20 20 20 20 20 20 20 20 20 20 20 20  .
    (-A   ,-    ) BB : 27 27 27 27 27 27 27 27 27 27 27  .  .  .
    (-E   ,-E   ) BE : 20 20 20 20 20 20 20 20 20 20 20 20 20  .
    (-E   ,-E   ) BG : 20 20 20 20 20 20 20 20 20 20 20 20 20  .
    (-E   ,-    ) BH : 20 20 20 20 20 20 20 20 20 20 20 20 20  .
    (-E   ,-    ) BN : 20 20 20 20 20 20 20 20 20 20 20 20 20 20
    (-A   ,-A   ) BO : 27 27 27 27 27 27 27 27 27 27 27  .  .  .
    --More-- or (q)uit
    (-A   ,-AR  ) BR : 27 27 27 27 27 27 27 27 27 27 27  .  .  .
    (-E   ,-    ) BY : 20 20 20 20 20 20 20 20 20 20 20 20 20  .
    (-A   ,-ABN ) CA : 27 27 27 27 27 27 27 27 27 27 27  .  .  .
    (-A   ,-ABN ) CA2: 27 27 27 27 27 27 27 27 27 27 27  .  .  .
    (-E   ,-E   ) CH : 20 20 20 20 20 20 20 20 20 20 20 20 20  .
    (-AER ,-AR  ) CL : 20 20 20 20 20 20 20 20 20 20 20 20 20  .
    (-E   ,-E   ) CM : 20 20 20 20 20 20 20 20 20 20 20 20 20  .
    (-CE  ,-CE  ) CN : 20 20 20 20 20 20 20 20 20 20 20 20 20  .
    And for 802.11a:
    -----------------:+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--
       802.11A       :                                      1  1  1  1  1  1  1  1  1  1  1  1  1  1  1  1  1  1
       Channels      :  3  3  3  4  4  4  4  4  5  5  6  6  0  0  0  1  1  2  2  2  3  3  4  4  5  5  6  6  6  7
                     :  4  6  8  0  2  4  6  8  2  6  0  4  0  4  8  2  6  0  4  8  2  6  0  9  3  7  1  5  9  3
    -----------------:+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--
    (-CE  ,-C   ) AE :  . 23  . 23  . 23  . 23 23*23*23*23*30*30*30*30*30*30*30*30*30*30*30*23 23 23 23 23  .  .
    (-A   ,-A   ) AR :  . 23  . 23  . 23  . 23 23*23*23*23*23*23*23*23*23* .  .  . 23*23*23*30 30 30 30 30  .  .
    (-E   ,-E   ) AT :  . 20  . 20  . 20  . 20 20*20*20*20*27*27*27*27*27*27*27*27*27*27*27* .  .  .  .  .  .  .
    (-NZ  ,-NZ  ) AU :  . 23  . 23  . 23  . 23 23*23*23*23*30*30*30*30*30*30*30*30*30*30*30*30 30 30 30 30  .  .
    (-E   ,-    ) BA :  . 20  . 20  . 20  . 20 20*20*20*20*27*27*27*27*27*27*27*27*27*27*27* .  .  .  .  .  .  .
    (-N   ,-    ) BB :  . 23  . 23  . 23  . 23 23*23*23*23* .  .  .  .  .  .  .  .  .  .  . 30 30 30 30 30  .  .
    (-E   ,-E   ) BE :  . 20  . 20  . 20  . 20 20*20*20*20*27*27*27*27*27*27*27*27*27*27*27* .  .  .  .  .  .  .
    (-E   ,-E   ) BG :  . 20  . 20  . 20  . 20 20*20*20*20*27*27*27*27*27*27*27*27*27*27*27* .  .  .  .  .  .  .
    (-E   ,-    ) BH :  . 20  . 20  . 20  . 20 20*20*20*20*27*27*27*27*27*27*27*27*27*27*27* .  .  .  .  .  .  .
    (-S   ,-    ) BN :  . 20  . 20  . 20  . 20 20*20*20*20* .  .  .  .  .  .  .  .  .  .  . 30 30 30 30 30  .  .
    --More-- or (q)uit
    (-A   ,-A   ) BO :  . 23  . 23  . 23  . 23 23*23*23*23*23*23*23*23*23* .  .  . 23*23*23*30 30 30 30 30  .  .
    (-T   ,-AN  ) BR :  .  .  .  .  .  .  .  .  . 17*17*17*27*27*27*27*27*27*27*27*27*27*27*30 30 30 30 30  .  .
    (-I   ,-    ) BY :  . 20  . 20  . 20  . 20 20*20*20*20* .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .
    (-A   ,-ABN ) CA :  . 23  . 23  . 23  . 23 23*23*23*23*23*23*23*23*23* .  .  . 23*23*23*30 30 30 30 30  .  .
    (-A   ,-ABN ) CA2:  . 23  . 23  . 23  . 23 23*23*23*23*23*23*23*23*23* .  .  . 23*23*23*30 30 30 30 30  .  .
    (-E   ,-E   ) CH :  . 20  . 20  . 20  . 20 20*20*20*20*27*27*27*27*27*27*27*27*27*27*27* .  .  .  .  .  .  .
    (-SA  ,-A   ) CL :  . 20  . 20  . 20  . 20 20*20*20*20*27*27*27*27*27*27*27*27*27*27*27*30 30 30 30 30  .  .
    (-    ,-    ) CM :  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .
    (-C   ,-C   ) CN :  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  . 23 23 23 23 23  .  .
    So from that you can confirm that for 802.11bg you can use E and C regulatory domains.

  • WLC 4402 & AP 3502i Regulatory Domain Mismatch

    BACKGROUND: Access Point AP3502i successfully joins the WLC4402 (v 7.0.235.3) controller.
    PROBLEM: AP3502i after boot and joining the WLC, shuts down both the Radios due to "Regulartory Domain MISMATCH"
    ERROR:
    AP on the 802.11a radio with Base Radio MAC xx:xx:xx:xx:xx:xx (AP1xxx.xxxx.xxxx) is unable to associate. The regulatory domain configured on it '-N' does not match the controller's regulatory domain: -A
    AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:08:17:35:31:a9:d0 Cause=Radio reset due to Init. Status:NA
    AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:08:17:35:31:a9:d0 Cause=Radio reset due to Init. Status:NA
    To verify the Country & Regulatory Domains configured on WLC & AP, I check:
    Under: Wireless->All APs->Details for APxxxx.xxxx.xxxx->Advanced Tab:   Regulatory Domains:  802.11bg:-A   802.11a:-N
    Under Wireless->Country---> ONLY US is CHECKED
    It is clear that the WLC is setup for US Country; however, the AP is setup for US ONLY for 802.11bg AND MEXICO FOR 802.11a
    WLC & AP are both located in US. Therefore, I need to update the AP Regulatory domain for US (-A) instead of Mexico (-N)
    Question is, how do I update AP for US Regulatory Domain?
    Any information would be greatly appreciated.

    Even adding country code to WLC (i.e: WLC Country Code is set/checked to US & Mexico (-A and -N), even then I get the same error and the result is that the radio is powered off on access points. 
    To re-sum the current status:
    WLC Configured Country Codes: MX, US
    WLC Regulatory Domain: 802.11a: -AN
                                          802.11bg: -A
    3502i Access Points Country Code: US
    3502i Regulatory Domain:  802.11a:-N    <<<-- This is the access point config that is causing the mismatch eventhough
                                           802.11bg:-A            WLC Regulatory domain show both US & Mex (-AN).
    There's got to be way to change AP's Regulatory Domain.   

  • [SOLVED] WLAN ath5k: regulatory domain set but it is ignored?

    Original message below, adding solution to first post:
    1) if installed, remove the crda package, else our regulatory domain will keep resetting (in my case to GB)
    sudo pacman -R crda
    2) get and build ath_info
    svn co http://madwifi-project.org/svn/ath_info/trunk ath_info
    cd ath_info/
    make
    3) get your memory address (don't know if it's universal between the cards, better safe than sorry)
    athmem=`lspci -vd 168c: |sed -n 's/.*Memory at \([^ ]*\).*/0x\1/p'`
    3.1) backup EEPROM (optional)
    sudo ./ath_info -d $athmem
    4a) to get channels 12+13 (NO-IR) enabled, do
    sudo ./ath_info -w $athmem regdomain 68
    4b) to get channels 12+13+14 (NO-IR) enabled, do
    sudo ./ath_info -w $athmem regdomain 60
    5)  reload module (or just reboot)
    sudo modprobe -r ath5k
    sudo modprobe ath5k
    6) doing iw list should now show the desired channels
    Frequencies:
    * 2412 MHz [1] (20.0 dBm)
    * 2417 MHz [2] (20.0 dBm)
    * 2422 MHz [3] (20.0 dBm)
    * 2427 MHz [4] (20.0 dBm)
    * 2432 MHz [5] (20.0 dBm)
    * 2437 MHz [6] (20.0 dBm)
    * 2442 MHz [7] (20.0 dBm)
    * 2447 MHz [8] (20.0 dBm)
    * 2452 MHz [9] (20.0 dBm)
    * 2457 MHz [10] (20.0 dBm)
    * 2462 MHz [11] (20.0 dBm)
    * 2467 MHz [12] (20.0 dBm) (no IR)
    * 2472 MHz [13] (20.0 dBm) (no IR)
    * 2484 MHz [14] (disabled)
    or
    Frequencies:
    * 2412 MHz [1] (20.0 dBm)
    * 2417 MHz [2] (20.0 dBm)
    * 2422 MHz [3] (20.0 dBm)
    * 2427 MHz [4] (20.0 dBm)
    * 2432 MHz [5] (20.0 dBm)
    * 2437 MHz [6] (20.0 dBm)
    * 2442 MHz [7] (20.0 dBm)
    * 2447 MHz [8] (20.0 dBm)
    * 2452 MHz [9] (20.0 dBm)
    * 2457 MHz [10] (20.0 dBm)
    * 2462 MHz [11] (20.0 dBm)
    * 2467 MHz [12] (20.0 dBm)
    * 2472 MHz [13] (20.0 dBm) (no IR)
    * 2484 MHz [14] (20.0 dBm) (no IR)
    ================== original message ======================
    Hello,
    I'm quite new to linux so maybe it's somethin I'm overlooking.
    I have followed the steps  described here to set my regdom to EU to allow using channels 12 and 13 but I still only have 11 channels, and I don't see my WLAN which is working on channel 13.
    I have found different solutions, none of which helped.
    I tried adding options cfg80211 ieee80211_regdom=EU to /etc/modprobe.d/modprobe.conf and the modules load with that option when I load them with modprobe.
    I have also tried installing crda and editing /etc/conf.d/wireless-regdom uncommenting the DE entry (Germany)
    The solution also talked about adding wireless-regdom to /etc/rc.conf, but that was before arch moved to systemd (I guess) and there doesn't seem to be a wireless-regdom.service so I'm lost.
    The last thing I tried was to set the region with iw reg set, but it remains as 00:
    # iw reg set EU
    # iw reg get
    country 00: DFS-UNSET
    (2402 - 2472 @ 40), (N/A, 20)
    (2457 - 2482 @ 40), (N/A, 20), NO-IR
    (2474 - 2494 @ 20), (N/A, 20), NO-IR
    (5170 - 5250 @ 80), (N/A, 20), NO-IR
    (5735 - 5835 @ 80), (N/A, 20), NO-IR
    (57240 - 63720 @ 2160), (N/A, 0)
    It doesn't matter if I set the country code to EU, DE or JP for each of the methods listed above, I am still stuck with 11 channels only.
    The card in question is
    01:05.0 Ethernet controller: Qualcomm Atheros AR5212/AR5213 Wireless Network Adapter (rev 01)
    # iw list gives
    Wiphy phy0
    max # scan SSIDs: 4
    max scan IEs length: 2285 bytes
    Coverage class: 0 (up to 0m)
    Device supports RSN-IBSS.
    Supported Ciphers:
    * WEP40 (00-0f-ac:1)
    * WEP104 (00-0f-ac:5)
    * TKIP (00-0f-ac:2)
    * CCMP (00-0f-ac:4)
    * CMAC (00-0f-ac:6)
    Available Antennas: TX 0x3 RX 0x3
    Configured Antennas: TX 0x3 RX 0x3
    Supported interface modes:
    * IBSS
    * managed
    * AP
    * AP/VLAN
    * monitor
    * mesh point
    Band 1:
    Bitrates (non-HT):
    * 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
    Frequencies:
    * 2412 MHz [1] (20.0 dBm)
    * 2417 MHz [2] (20.0 dBm)
    * 2422 MHz [3] (20.0 dBm)
    * 2427 MHz [4] (20.0 dBm)
    * 2432 MHz [5] (20.0 dBm)
    * 2437 MHz [6] (20.0 dBm)
    * 2442 MHz [7] (20.0 dBm)
    * 2447 MHz [8] (20.0 dBm)
    * 2452 MHz [9] (20.0 dBm)
    * 2457 MHz [10] (20.0 dBm)
    * 2462 MHz [11] (20.0 dBm)
    * 2467 MHz [12] (disabled)
    * 2472 MHz [13] (disabled)
    * 2484 MHz [14] (disabled)
    Supported commands:
    * new_interface
    * set_interface
    * new_key
    * start_ap
    * new_station
    * new_mpath
    * set_mesh_config
    * set_bss
    * authenticate
    * associate
    * deauthenticate
    * disassociate
    * join_ibss
    * join_mesh
    * set_tx_bitrate_mask
    * frame
    * frame_wait_cancel
    * set_wiphy_netns
    * set_channel
    * set_wds_peer
    * probe_client
    * set_noack_map
    * register_beacons
    * start_p2p_device
    * set_mcast_rate
    * connect
    * disconnect
    Supported TX frame types:
    * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
    * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
    * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
    * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
    * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
    * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
    * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
    * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
    Supported RX frame types:
    * IBSS: 0x40 0xb0 0xc0 0xd0
    * managed: 0x40 0xd0
    * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
    * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
    * mesh point: 0xb0 0xc0 0xd0
    * P2P-client: 0x40 0xd0
    * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
    * P2P-device: 0x40 0xd0
    software interface modes (can always be added):
    * AP/VLAN
    * monitor
    valid interface combinations:
    * #{ managed } <= 2048, #{ AP, mesh point } <= 4,
    total <= 2048, #channels <= 1
    HT Capability overrides:
    * MCS: ff ff ff ff ff ff ff ff ff ff
    * maximum A-MSDU length
    * supported channel width
    * short GI for 40 MHz
    * max A-MPDU length exponent
    * min MPDU start spacing
    Device supports TX status socket option.
    Device supports HT-IBSS.
    Device supports low priority scan.
    Device supports scan flush.
    Device supports AP scan.
    I have seen someone say the regulatory domain may be fixed in the EEPROM of the card so changing it is not possible.
    I do not think it is the case, since it is actually a card from an old Japanese laptop, and from what I gathered, they even have 14 channels over there. So the ath5k module managed to change it from 14 to 11 somehow, which leads me to believe it should be possible to get it back to (at least) 13 channels. And windows doesn't seem to have a problem detecting my WLAN either...
    Any help appreciated.
    Last edited by Soukyuu (2014-04-12 18:46:09)

    The link helped, thanks!
    I managed to get channel 14 working as well now.
    For the record:
    - a value of 68 enables 1-11 + 12-13 (NO-IR)
    - a value of 60 enables 1-11 + 12-14 (NO-IR)
    Be careful experimenting with them though, I tried to write 392 (Japan) to the EEPROM and it did... after which the wlan interface has disappeared. In my opinion, the information regarding the 3 digit regdoms is rather unclear, it probably belongs into another register, not regdomain. You can still fix the card by rewriting a correct, two digit regdomain value.
    edit2: nevermind the part below, solved. Will add full instructions to the first post. Thanks for the help!
    edit: channel 14 seems to only hold for a few seconds, though. The EEPROM info keeps reverting regdom to GB for some reason. I then have to unload and reload the ath5k module to re-enable channel 14.
    Booting: correctly sets country to JP, then resets it to GB
    [ 6.285400] cfg80211: Calling CRDA to update world regulatory domain
    [ 7.054075] cfg80211: World regulatory domain updated:
    [ 7.054081] cfg80211: DFS Master region: unset
    [ 7.054081] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    [ 7.054085] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm)
    [ 7.054087] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
    [ 7.054089] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm)
    [ 7.054091] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    [ 7.054093] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    [ 7.054095] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm)
    [ 7.054119] cfg80211: Calling CRDA for country: JP
    [ 7.068527] cfg80211: Regulatory domain changed to country: JP
    [ 7.068555] cfg80211: DFS Master region: JP
    [ 7.068555] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    [ 7.068558] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
    [ 7.068560] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm)
    [ 7.068562] cfg80211: (4910000 KHz - 4990000 KHz @ 40000 KHz), (N/A, 2300 mBm)
    [ 7.068564] cfg80211: (5030000 KHz - 5090000 KHz @ 40000 KHz), (N/A, 2300 mBm)
    [ 7.068566] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    [ 7.068567] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    [ 7.068569] cfg80211: (5490000 KHz - 5710000 KHz @ 160000 KHz), (N/A, 2300 mBm)
    [ 35.219154] cfg80211: Calling CRDA for country: GB
    [ 35.224197] cfg80211: Regulatory domain changed to country: GB
    [ 35.224200] cfg80211: DFS Master region: ETSI
    [ 35.224204] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    [ 35.224208] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
    [ 35.224212] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    [ 35.224216] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    [ 35.224220] cfg80211: (5490000 KHz - 5710000 KHz @ 80000 KHz), (N/A, 2700 mBm)
    [ 35.224223] cfg80211: (57240000 KHz - 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm)
    me manually reloading modules
    [ 138.363438] cfg80211: Calling CRDA to update world regulatory domain
    [ 138.468156] cfg80211: World regulatory domain updated:
    [ 138.468167] cfg80211: DFS Master region: unset
    [ 138.468171] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    [ 138.468176] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm)
    [ 138.468180] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
    [ 138.468183] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm)
    [ 138.468187] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    [ 138.468191] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    [ 138.468195] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm)
    [ 138.468235] cfg80211: Calling CRDA for country: JP
    [ 138.473603] cfg80211: Regulatory domain changed to country: JP
    [ 138.473612] cfg80211: DFS Master region: JP
    [ 138.473615] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    [ 138.473620] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
    [ 138.473624] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm)
    [ 138.473628] cfg80211: (4910000 KHz - 4990000 KHz @ 40000 KHz), (N/A, 2300 mBm)
    [ 138.473632] cfg80211: (5030000 KHz - 5090000 KHz @ 40000 KHz), (N/A, 2300 mBm)
    [ 138.473635] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    [ 138.473639] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    [ 138.473643] cfg80211: (5490000 KHz - 5710000 KHz @ 160000 KHz), (N/A, 2300 mBm)
    and the thing overwriting the setting again without me doing anything a while later
    [ 147.725198] cfg80211: Calling CRDA to update world regulatory domain
    [ 147.731014] cfg80211: World regulatory domain updated:
    [ 147.731025] cfg80211: DFS Master region: unset
    [ 147.731028] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    [ 147.731033] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm)
    [ 147.731037] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
    [ 147.731041] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm)
    [ 147.731044] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    [ 147.731048] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    [ 147.731052] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm)
    [ 147.731079] cfg80211: Calling CRDA for country: JP
    [ 147.738678] cfg80211: Regulatory domain changed to country: JP
    [ 147.738689] cfg80211: DFS Master region: JP
    [ 147.738692] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    [ 147.738697] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
    [ 147.738701] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm)
    [ 147.738705] cfg80211: (4910000 KHz - 4990000 KHz @ 40000 KHz), (N/A, 2300 mBm)
    [ 147.738708] cfg80211: (5030000 KHz - 5090000 KHz @ 40000 KHz), (N/A, 2300 mBm)
    [ 147.738712] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    [ 147.738716] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    [ 147.738720] cfg80211: (5490000 KHz - 5710000 KHz @ 160000 KHz), (N/A, 2300 mBm)
    [ 158.396390] cfg80211: Calling CRDA for country: GB
    [ 158.403475] cfg80211: Regulatory domain changed to country: GB
    [ 158.403478] cfg80211: DFS Master region: ETSI
    [ 158.403481] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    [ 158.403486] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
    [ 158.403490] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    [ 158.403493] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    [ 158.403497] cfg80211: (5490000 KHz - 5710000 KHz @ 80000 KHz), (N/A, 2700 mBm)
    [ 158.403501] cfg80211: (57240000 KHz - 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm)
    I guess I really have to somehow change the three digit information saved in the EEPROM, maybe someone has a hint which register/address to edit? I don't see what could be causing this otherwise. An it is quite peculiar I have to do this in the first place, I guess Atheros didn't care about Japanese linux users.
    edit2: nevermind the part above, solved. Will add full instructions to the first post. Thanks for the help!
    Last edited by Soukyuu (2014-04-12 18:50:04)

  • How can i change regulatory domain C to A of access point

    Recently my office got an access point - (AIR-CAP2602E-C-K9)  which is not synchronizing with controller (AIR-CT2504-5-K9 )as it is in domain A , all other AP also in domain A. Now can i change the domain of access point or what is the possible solution to add new AP with controller ? is it possible to run both domain (A, C)  at the same time with one controller ?   

    Migrating Access Points from the -J Regulatory Domain to the -U Regulatory Domain
    The Japanese government has changed its 5-GHz radio spectrum regulations. These regulations allow a field upgrade of 802.11a 5-GHz radios. Japan allows three frequency sets:
    •J52 = 34 (5170 MHz), 38 (5190 MHz), 42 (5210 MHz), 46 (5230 MHz)
    •W52 = 36 (5180 MHz), 40 (5200 MHz), 44 (5220 MHz), 48 (5240 MHz)
    •W53 = 52 (5260 MHz), 56 (5280 MHz), 60 (5300 MHz), 64 (5320 MHz)
    Cisco has organized these frequency sets into the following regulatory domains:
    •-J regulatory domain = J52
    •-P regulatory domain = W52 + W53
    •-U regulatory domain = W52
    Regulatory domains are used by Cisco to organize the legal frequencies of the world into logical groups. For example, most of the European countries are included in the -E regulatory domain. Cisco access points are configured for a specific regulatory domain at the factory and, with the exception of this migration process, never change. The regulatory domain is assigned per radio, so an access point's 802.11a and 802.11b/g radios may be assigned to different domains.
    For more information please refer to the link-
    http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/321930RN.html#wp111182

  • WLC 802.11a/n Radio Regulatory Domain Issue

    Dear All
    We are facing an issue with a customer where a Cisco 4400 Series controller is blocking the 802.11a/n Radio Interface of a 1250 AP. The radio shows as down on the controller GUI. The error message on the GUI is that the 'Regulatory Domain' is not supported. This can be seen from the attached screenshot. Also relevant parts of the WLC configs are attached.
    WLC: Cisco 4402  Wireless
    WLC Country: SA
    Device: Cisco Lightweight Access Point 1250 (LAP) is controlled through the 4402 Cisco Wireless LAN Controller (WLC)
    The operating system version of the LAP: c1250-k9w8-mx.124-18a.JA version of the WLC: Software Version 5.2.178.0
    The problem is that the controller shows that the 802.11a/n Radio Interface in Radio Slot # 1 is always down ,  the customer tried to manually 'no shut' the AP interface from the console and it worked , but obviously this solution would not work as the configuration cannot be saved (LW AP).
    Any help or pointers would be greatly appreciated.
    Regards
    Farrukh

    Hello
    This is sort of like a testbed setup, so can you tell me which country/reg domain I can set on my controller in order to make our access point work. There is only one AP connected to this controller.
    LAP:  AIR-AP1252AG-N-K9
    Also as per the guide, we can configure the country on a per-AP basis, would this be a viable option?
    http://www.cisco.com/en/US/docs/wireless/controller/5.2/configuration/guide/c52lwap.html#wp1147805
    Regards
    Farrukh
    P.S I think South Africa is ZA

  • Question on Regulatory Domain

    HI
    We have purchased CISCO AIR-CAP2602I-S-K9 but want to use this access point in India.
    Can we use this AP in India with controller CISCO5508 .IOS version 7.4.100.0
    Please suggest.

    Customers are responsible for verifying approval for use in their individual countries. To verify approval and to identify the regulatory domain that corresponds to a particular country, not all regulatory domains have been approved. As they are approved, the part numbers will be available on the Global Price List.
    Please visit the below Link:http://www.cisco.com/go/aironet/compliance
    http://www.cisco.com/go/aironet/compliance.

  • LAP1142 with different regulatory domains on each wireless

    Hi, I wonder if anyone has come across this before:
    We've seen an AIR-LAP1142-E-K9 wireless access point - one of a batch on the pre-used market although I understand that they have been simply removed from the original user - where the regulatory domain on each of the radios is different.
    The 2.4GHz radio is 802.11bg:-E and the 5GHz radio is 802.11a:-A (as reported by the controller).
    This is really strange as the AP shows itself to be the Product/Model Number             : AIR-LAP1142N-E-K9
    And the radio circuit board contains the circuitry for both radios so it's not that the wrong board has been installed for the A radio.
    I don't know the software version that is running on the controller - and I've tried a bug search but that hasn't turned up anything useful (yet).
    Has anyone here seen anything like this or offer any explanation?
    Thanks in advance
    Robin

    That's what I thought, Scott, but I've had one of these to pieces and both radios are driven from the one circuit board...
    I did wonder if there was a bug in the firmware level on the WLC but I don't have access to it to check.  Especially since others from the same batch are reported to have worked without problems - we ourselves have had some - and they are reported to have worked fine in their original installation (these are pre-owned units).
    Oh well, I guess this will remain a mystery.  Thanks to everyone who replied.
    Robin

  • Is it possible to migrate an access point between regulatory domains?

    I see appendices full of channel usage and power maximums, but nothing that states clearly wether or not it is possible to simply reconfigure a lightweight access point deployed in one regulatory domain so that it can be used in another?
    Example - have an 1142 access point in Japan and would like to repurpose it for use in London.  Do I need to buy a new access point or can I reconfigure the Japan AP for use in London via software.
    Thanks!

    Hello,
    for the regulatory domain it is hardcoded in the AP itself.
    so for AP to be used in london , you need to purchase a -E AP.
    now you still can connect the -J in london , and join it to WLC  with Japan country code, but that would be breach for the eroupean regulations and allowed frequencies...
    the only migration you can perform in AP is between Japanese codes ( that allow different frequency ranges).
    http://www.cisco.com/en/US/docs/wireless/controller/6.0/configuration/guide/c60lwap.html#wp1147957
    Hope this answers your concerns.
    Best Regards
    Talal
    ==========
    please don't forget to rate answers that you find useful

  • Access points with differing regulatory domains?

    I have four new air-lap1142n-e-k9 that I'm attempting to connect to a wireless lan controller 4402.
    We have about 8 similar devices connected to it since earlier.
    Connecting them to the wlc isn't a problem, but only the 802.11b/g interface comes up when they're
    connected, the 802.11a is taken down. Looking at the configuration of the ap it seems that the
    802.11a interface has the wrong regulatory domain. Should be Sweden and '-E' (which all the other
    aps have), but the new ones all have -E on the 802.11b/g and -C on the 802.11a (see attached wlc
    webgui screenshots).
    Is there a way of changing the regulatory domain of the 802.11a interfaces to -E?
    And out of curiosity, is there a point in having different regulatory domains on different interfaces on
    the same access point..?
    Thanks in advance.
    /richard

    Please check if the regulatory domain should be on the same AP. Please check the PDF for referring codes of different countries-
    http://www.cisco.com/en/US/prod/collateral/wireless/ps5679/ps5861/product_data_sheet0900aecd80537b6a.pdf

  • Wireless regulatory domain set to GB, even tho BO have been selected

    Hello,
    for some reason something is setting my wireless regulatory domain to GB right after wicd associates my adapter with my access point. I have selected the correct domain in /etc/conf.d/wireless-regdom (everything but my domain has been commented out, I have installed crda) and added wireless-regdom to my DAEMONS line. Does anybody have an idea what is changing it to GB?
    Here's a paste of dmesg showing the problem
    [ 0.000000] Initializing cgroup subsys cpuset
    [ 0.000000] Initializing cgroup subsys cpu
    [ 0.000000] Linux version 3.1.6-1-ARCH (tobias@T-POWA-LX) (gcc version 4.6.2 20111125 (prerelease) (GCC) ) #1 SMP PREEMPT Thu Dec 22 09:11:48 CET 2011
    [ 0.000000] Command line: root=/dev/disk/by-label/archroot ro 5
    [ 0.000000] BIOS-provided physical RAM map:
    [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
    [ 0.000000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
    [ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
    [ 0.000000] BIOS-e820: 0000000000100000 - 00000000dfde0000 (usable)
    [ 0.000000] BIOS-e820: 00000000dfde0000 - 00000000dfee0000 (reserved)
    [ 0.000000] BIOS-e820: 00000000dfee0000 - 00000000dfee1000 (ACPI NVS)
    [ 0.000000] BIOS-e820: 00000000dfee1000 - 00000000dfef0000 (ACPI data)
    [ 0.000000] BIOS-e820: 00000000dfef0000 - 00000000dff00000 (reserved)
    [ 0.000000] BIOS-e820: 00000000f0000000 - 00000000f4000000 (reserved)
    [ 0.000000] BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
    [ 0.000000] BIOS-e820: 0000000100000000 - 00000001a0000000 (usable)
    [ 0.000000] NX (Execute Disable) protection: active
    [ 0.000000] DMI 2.4 present.
    [ 0.000000] DMI: Gigabyte Technology Co., Ltd. EX58-UD5/EX58-UD5, BIOS F13q 11/12/2010
    [ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
    [ 0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
    [ 0.000000] No AGP bridge found
    [ 0.000000] last_pfn = 0x1a0000 max_arch_pfn = 0x400000000
    [ 0.000000] MTRR default type: uncachable
    [ 0.000000] MTRR fixed ranges enabled:
    [ 0.000000] 00000-9FFFF write-back
    [ 0.000000] A0000-BFFFF uncachable
    [ 0.000000] C0000-CCFFF write-protect
    [ 0.000000] CD000-EFFFF uncachable
    [ 0.000000] F0000-FFFFF write-through
    [ 0.000000] MTRR variable ranges enabled:
    [ 0.000000] 0 base 000000000 mask F00000000 write-back
    [ 0.000000] 1 base 0E0000000 mask FE0000000 uncachable
    [ 0.000000] 2 base 100000000 mask F00000000 write-back
    [ 0.000000] 3 base 1C0000000 mask FC0000000 uncachable
    [ 0.000000] 4 base 1A0000000 mask FE0000000 uncachable
    [ 0.000000] 5 disabled
    [ 0.000000] 6 disabled
    [ 0.000000] 7 disabled
    [ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    [ 0.000000] e820 update range: 00000000e0000000 - 0000000100000000 (usable) ==> (reserved)
    [ 0.000000] last_pfn = 0xdfde0 max_arch_pfn = 0x400000000
    [ 0.000000] found SMP MP-table at [ffff8800000f5c40] f5c40
    [ 0.000000] initial memory mapped : 0 - 20000000
    [ 0.000000] Base memory trampoline at [ffff88000009a000] 9a000 size 20480
    [ 0.000000] init_memory_mapping: 0000000000000000-00000000dfde0000
    [ 0.000000] 0000000000 - 00dfc00000 page 2M
    [ 0.000000] 00dfc00000 - 00dfde0000 page 4k
    [ 0.000000] kernel direct mapping tables up to dfde0000 @ 1fffa000-20000000
    [ 0.000000] init_memory_mapping: 0000000100000000-00000001a0000000
    [ 0.000000] 0100000000 - 01a0000000 page 2M
    [ 0.000000] kernel direct mapping tables up to 1a0000000 @ dfdd8000-dfde0000
    [ 0.000000] RAMDISK: 37d89000 - 37ff0000
    [ 0.000000] ACPI: RSDP 00000000000f7600 00014 (v00 GBT )
    [ 0.000000] ACPI: RSDT 00000000dfee1040 00040 (v01 GBT GBTUACPI 42302E31 GBTU 01010101)
    [ 0.000000] ACPI: FACP 00000000dfee10c0 00074 (v01 GBT GBTUACPI 42302E31 GBTU 01010101)
    [ 0.000000] ACPI: DSDT 00000000dfee1180 04A7B (v01 GBT GBTUACPI 00001000 MSFT 0100000C)
    [ 0.000000] ACPI: FACS 00000000dfee0000 00040
    [ 0.000000] ACPI: HPET 00000000dfee5dc0 00038 (v01 GBT GBTUACPI 42302E31 GBTU 00000098)
    [ 0.000000] ACPI: MCFG 00000000dfee5e40 0003C (v01 GBT GBTUACPI 42302E31 GBTU 01010101)
    [ 0.000000] ACPI: EUDS 00000000dfee5e80 00470 (v01 GBT 00000000 00000000)
    [ 0.000000] ACPI: TAMG 00000000dfee62f0 00AF2 (v01 GBT GBT B0 5455312E BG?? 53450101)
    [ 0.000000] ACPI: APIC 00000000dfee5c40 0012C (v01 GBT GBTUACPI 42302E31 GBTU 01010101)
    [ 0.000000] ACPI: SSDT 00000000dfee6e00 00CCC (v01 INTEL PPM RCM 80000001 INTL 20061109)
    [ 0.000000] ACPI: Local APIC address 0xfee00000
    [ 0.000000] No NUMA configuration found
    [ 0.000000] Faking a node at 0000000000000000-00000001a0000000
    [ 0.000000] Initmem setup node 0 0000000000000000-00000001a0000000
    [ 0.000000] NODE_DATA [000000019fffb000 - 000000019fffffff]
    [ 0.000000] [ffffea0000000000-ffffea00067fffff] PMD -> [ffff880199600000-ffff88019f5fffff] on node 0
    [ 0.000000] Zone PFN ranges:
    [ 0.000000] DMA 0x00000010 -> 0x00001000
    [ 0.000000] DMA32 0x00001000 -> 0x00100000
    [ 0.000000] Normal 0x00100000 -> 0x001a0000
    [ 0.000000] Movable zone start PFN for each node
    [ 0.000000] early_node_map[3] active PFN ranges
    [ 0.000000] 0: 0x00000010 -> 0x0000009f
    [ 0.000000] 0: 0x00000100 -> 0x000dfde0
    [ 0.000000] 0: 0x00100000 -> 0x001a0000
    [ 0.000000] On node 0 totalpages: 1572207
    [ 0.000000] DMA zone: 64 pages used for memmap
    [ 0.000000] DMA zone: 5 pages reserved
    [ 0.000000] DMA zone: 3914 pages, LIFO batch:0
    [ 0.000000] DMA32 zone: 16320 pages used for memmap
    [ 0.000000] DMA32 zone: 896544 pages, LIFO batch:31
    [ 0.000000] Normal zone: 10240 pages used for memmap
    [ 0.000000] Normal zone: 645120 pages, LIFO batch:31
    [ 0.000000] ACPI: PM-Timer IO Port: 0x408
    [ 0.000000] ACPI: Local APIC address 0xfee00000
    [ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x02] enabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x04] enabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x06] enabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] disabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x05] disabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x06] disabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] disabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] disabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] disabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] disabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] disabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x0c] disabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x0d] disabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x0e] disabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x0f] disabled)
    [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
    [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
    [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
    [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1])
    [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x04] dfl dfl lint[0x1])
    [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x05] dfl dfl lint[0x1])
    [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x06] dfl dfl lint[0x1])
    [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x07] dfl dfl lint[0x1])
    [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] dfl dfl lint[0x1])
    [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] dfl dfl lint[0x1])
    [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] dfl dfl lint[0x1])
    [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] dfl dfl lint[0x1])
    [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x0c] dfl dfl lint[0x1])
    [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x0d] dfl dfl lint[0x1])
    [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x0e] dfl dfl lint[0x1])
    [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x0f] dfl dfl lint[0x1])
    [ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
    [ 0.000000] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
    [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    [ 0.000000] ACPI: IRQ0 used by override.
    [ 0.000000] ACPI: IRQ2 used by override.
    [ 0.000000] ACPI: IRQ9 used by override.
    [ 0.000000] Using ACPI (MADT) for SMP configuration information
    [ 0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000
    [ 0.000000] SMP: Allowing 16 CPUs, 12 hotplug CPUs
    [ 0.000000] nr_irqs_gsi: 40
    [ 0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
    [ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000f0000
    [ 0.000000] PM: Registered nosave memory: 00000000000f0000 - 0000000000100000
    [ 0.000000] PM: Registered nosave memory: 00000000dfde0000 - 00000000dfee0000
    [ 0.000000] PM: Registered nosave memory: 00000000dfee0000 - 00000000dfee1000
    [ 0.000000] PM: Registered nosave memory: 00000000dfee1000 - 00000000dfef0000
    [ 0.000000] PM: Registered nosave memory: 00000000dfef0000 - 00000000dff00000
    [ 0.000000] PM: Registered nosave memory: 00000000dff00000 - 00000000f0000000
    [ 0.000000] PM: Registered nosave memory: 00000000f0000000 - 00000000f4000000
    [ 0.000000] PM: Registered nosave memory: 00000000f4000000 - 00000000fec00000
    [ 0.000000] PM: Registered nosave memory: 00000000fec00000 - 0000000100000000
    [ 0.000000] Allocating PCI resources starting at dff00000 (gap: dff00000:10100000)
    [ 0.000000] Booting paravirtualized kernel on bare hardware
    [ 0.000000] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:16 nr_node_ids:1
    [ 0.000000] PERCPU: Embedded 27 pages/cpu @ffff88019fc00000 s80448 r8192 d21952 u131072
    [ 0.000000] pcpu-alloc: s80448 r8192 d21952 u131072 alloc=1*2097152
    [ 0.000000] pcpu-alloc: [0] 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15
    [ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 1545578
    [ 0.000000] Policy zone: Normal
    [ 0.000000] Kernel command line: root=/dev/disk/by-label/archroot ro 5
    [ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
    [ 0.000000] Checking aperture...
    [ 0.000000] No AGP bridge found
    [ 0.000000] Calgary: detecting Calgary via BIOS EBDA area
    [ 0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
    [ 0.000000] Memory: 6108484k/6815744k available (4158k kernel code, 526916k absent, 180344k reserved, 5286k data, 712k init)
    [ 0.000000] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=1
    [ 0.000000] Preemptible hierarchical RCU implementation.
    [ 0.000000] Verbose stalled-CPUs detection is disabled.
    [ 0.000000] NR_IRQS:2304
    [ 0.000000] Console: colour VGA+ 80x25
    [ 0.000000] console [tty0] enabled
    [ 0.000000] allocated 50331648 bytes of page_cgroup
    [ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
    [ 0.000000] hpet clockevent registered
    [ 0.000000] Fast TSC calibration using PIT
    [ 0.003333] Detected 3499.966 MHz processor.
    [ 0.000002] Calibrating delay loop (skipped), value calculated using timer frequency.. 7002.59 BogoMIPS (lpj=11666553)
    [ 0.000005] pid_max: default: 32768 minimum: 301
    [ 0.000071] Security Framework initialized
    [ 0.000074] AppArmor: AppArmor disabled by boot time parameter
    [ 0.000507] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
    [ 0.001636] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
    [ 0.002093] Mount-cache hash table entries: 256
    [ 0.002338] Initializing cgroup subsys cpuacct
    [ 0.002357] Initializing cgroup subsys memory
    [ 0.002367] Initializing cgroup subsys devices
    [ 0.002368] Initializing cgroup subsys freezer
    [ 0.002370] Initializing cgroup subsys net_cls
    [ 0.002371] Initializing cgroup subsys blkio
    [ 0.002400] CPU: Physical Processor ID: 0
    [ 0.002401] CPU: Processor Core ID: 0
    [ 0.002404] mce: CPU supports 9 MCE banks
    [ 0.002411] CPU0: Thermal monitoring enabled (TM1)
    [ 0.002416] using mwait in idle threads.
    [ 0.003061] ACPI: Core revision 20110623
    [ 0.004974] ftrace: allocating 16320 entries in 65 pages
    [ 0.008188] Switched APIC routing to physical flat.
    [ 0.008491] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    [ 0.041430] CPU0: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 04
    [ 0.146057] Performance Events: PEBS fmt1+, erratum AAJ80 worked around, Nehalem events, Intel PMU driver.
    [ 0.146061] ... version: 3
    [ 0.146061] ... bit width: 48
    [ 0.146062] ... generic registers: 4
    [ 0.146063] ... value mask: 0000ffffffffffff
    [ 0.146064] ... max period: 000000007fffffff
    [ 0.146065] ... fixed-purpose events: 3
    [ 0.146065] ... event mask: 000000070000000f
    [ 0.166297] NMI watchdog enabled, takes one hw-pmu counter.
    [ 0.192636] Booting Node 0, Processors #1
    [ 0.192638] smpboot cpu 1: start_ip = 9a000
    [ 0.305842] NMI watchdog enabled, takes one hw-pmu counter.
    [ 0.325715] #2
    [ 0.325716] smpboot cpu 2: start_ip = 9a000
    [ 0.438934] NMI watchdog enabled, takes one hw-pmu counter.
    [ 0.458778] #3
    [ 0.458779] smpboot cpu 3: start_ip = 9a000
    [ 0.571996] NMI watchdog enabled, takes one hw-pmu counter.
    [ 0.578530] Brought up 4 CPUs
    [ 0.578532] Total of 4 processors activated (28010.90 BogoMIPS).
    [ 0.580114] devtmpfs: initialized
    [ 0.580803] PM: Registering ACPI NVS region at dfee0000 (4096 bytes)
    [ 0.581343] print_constraints: dummy:
    [ 0.581392] NET: Registered protocol family 16
    [ 0.581455] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
    [ 0.581457] ACPI: bus type pci registered
    [ 0.581541] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf0000000-0xf3ffffff] (base 0xf0000000)
    [ 0.581543] PCI: MMCONFIG at [mem 0xf0000000-0xf3ffffff] reserved in E820
    [ 0.586719] PCI: Using configuration type 1 for base access
    [ 0.587041] bio: create slab <bio-0> at 0
    [ 0.587110] ACPI: Added _OSI(Module Device)
    [ 0.587111] ACPI: Added _OSI(Processor Device)
    [ 0.587112] ACPI: Added _OSI(3.0 _SCP Extensions)
    [ 0.587113] ACPI: Added _OSI(Processor Aggregator Device)
    [ 0.587538] ACPI: EC: Look up EC in DSDT
    [ 0.589316] ACPI Warning: Incorrect checksum in table [TAMG] - 0x50, should be 0x4F (20110623/tbutils-314)
    [ 0.589643] ACPI: Interpreter enabled
    [ 0.589645] ACPI: (supports S0 S3 S4 S5)
    [ 0.589654] ACPI: Using IOAPIC for interrupt routing
    [ 0.591717] ACPI: No dock devices found.
    [ 0.591718] HEST: Table not found.
    [ 0.591720] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
    [ 0.591751] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3f])
    [ 0.591811] pci_root PNP0A03:00: host bridge window [io 0x0000-0x0cf7]
    [ 0.591812] pci_root PNP0A03:00: host bridge window [io 0x0d00-0xffff]
    [ 0.591814] pci_root PNP0A03:00: host bridge window [mem 0x000a0000-0x000bffff]
    [ 0.591815] pci_root PNP0A03:00: host bridge window [mem 0x000c0000-0x000dffff]
    [ 0.591816] pci_root PNP0A03:00: host bridge window [mem 0xdff00000-0xfebfffff]
    [ 0.591826] pci 0000:00:00.0: [8086:3405] type 0 class 0x000600
    [ 0.591861] pci 0000:00:00.0: PME# supported from D0 D3hot D3cold
    [ 0.591864] pci 0000:00:00.0: PME# disabled
    [ 0.591882] pci 0000:00:03.0: [8086:340a] type 1 class 0x000604
    [ 0.591914] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
    [ 0.591916] pci 0000:00:03.0: PME# disabled
    [ 0.591935] pci 0000:00:10.0: [8086:3425] type 0 class 0x000800
    [ 0.591977] pci 0000:00:10.1: [8086:3426] type 0 class 0x000800
    [ 0.592017] pci 0000:00:11.0: [8086:3427] type 0 class 0x000800
    [ 0.592059] pci 0000:00:11.1: [8086:3428] type 0 class 0x000800
    [ 0.592099] pci 0000:00:13.0: [8086:342d] type 0 class 0x000800
    [ 0.592107] pci 0000:00:13.0: reg 10: [mem 0xfbfff000-0xfbffffff]
    [ 0.592137] pci 0000:00:13.0: PME# supported from D0 D3hot D3cold
    [ 0.592139] pci 0000:00:13.0: PME# disabled
    [ 0.592150] pci 0000:00:14.0: [8086:342e] type 0 class 0x000800
    [ 0.592193] pci 0000:00:14.1: [8086:3422] type 0 class 0x000800
    [ 0.592236] pci 0000:00:14.2: [8086:3423] type 0 class 0x000800
    [ 0.592279] pci 0000:00:15.0: [8086:342f] type 0 class 0x000800
    [ 0.592321] pci 0000:00:1a.0: [8086:3a37] type 0 class 0x000c03
    [ 0.592355] pci 0000:00:1a.0: reg 20: [io 0xff00-0xff1f]
    [ 0.592389] pci 0000:00:1a.1: [8086:3a38] type 0 class 0x000c03
    [ 0.592423] pci 0000:00:1a.1: reg 20: [io 0xfe00-0xfe1f]
    [ 0.592456] pci 0000:00:1a.2: [8086:3a39] type 0 class 0x000c03
    [ 0.592490] pci 0000:00:1a.2: reg 20: [io 0xfd00-0xfd1f]
    [ 0.592531] pci 0000:00:1a.7: [8086:3a3c] type 0 class 0x000c03
    [ 0.592548] pci 0000:00:1a.7: reg 10: [mem 0xfbffe000-0xfbffe3ff]
    [ 0.592607] pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
    [ 0.592610] pci 0000:00:1a.7: PME# disabled
    [ 0.592628] pci 0000:00:1b.0: [8086:3a3e] type 0 class 0x000403
    [ 0.592639] pci 0000:00:1b.0: reg 10: [mem 0xfbff8000-0xfbffbfff 64bit]
    [ 0.592682] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
    [ 0.592684] pci 0000:00:1b.0: PME# disabled
    [ 0.592699] pci 0000:00:1c.0: [8086:3a40] type 1 class 0x000604
    [ 0.592742] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
    [ 0.592744] pci 0000:00:1c.0: PME# disabled
    [ 0.592761] pci 0000:00:1c.1: [8086:3a42] type 1 class 0x000604
    [ 0.592803] pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
    [ 0.592806] pci 0000:00:1c.1: PME# disabled
    [ 0.592826] pci 0000:00:1d.0: [8086:3a34] type 0 class 0x000c03
    [ 0.592860] pci 0000:00:1d.0: reg 20: [io 0xfc00-0xfc1f]
    [ 0.592893] pci 0000:00:1d.1: [8086:3a35] type 0 class 0x000c03
    [ 0.592927] pci 0000:00:1d.1: reg 20: [io 0xfb00-0xfb1f]
    [ 0.592961] pci 0000:00:1d.2: [8086:3a36] type 0 class 0x000c03
    [ 0.592994] pci 0000:00:1d.2: reg 20: [io 0xfa00-0xfa1f]
    [ 0.593035] pci 0000:00:1d.7: [8086:3a3a] type 0 class 0x000c03
    [ 0.593052] pci 0000:00:1d.7: reg 10: [mem 0xfbffd000-0xfbffd3ff]
    [ 0.593111] pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
    [ 0.593114] pci 0000:00:1d.7: PME# disabled
    [ 0.593128] pci 0000:00:1e.0: [8086:244e] type 1 class 0x000604
    [ 0.593171] pci 0000:00:1f.0: [8086:3a16] type 0 class 0x000601
    [ 0.593239] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0800 (mask 000f)
    [ 0.593241] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 2 PIO at 0290 (mask 000f)
    [ 0.593270] pci 0000:00:1f.2: [8086:3a20] type 0 class 0x000101
    [ 0.593282] pci 0000:00:1f.2: reg 10: [io 0xf900-0xf907]
    [ 0.593287] pci 0000:00:1f.2: reg 14: [io 0xf800-0xf803]
    [ 0.593293] pci 0000:00:1f.2: reg 18: [io 0xf700-0xf707]
    [ 0.593299] pci 0000:00:1f.2: reg 1c: [io 0xf600-0xf603]
    [ 0.593305] pci 0000:00:1f.2: reg 20: [io 0xf500-0xf50f]
    [ 0.593310] pci 0000:00:1f.2: reg 24: [io 0xf400-0xf40f]
    [ 0.593338] pci 0000:00:1f.3: [8086:3a30] type 0 class 0x000c05
    [ 0.593350] pci 0000:00:1f.3: reg 10: [mem 0xfbffc000-0xfbffc0ff 64bit]
    [ 0.593366] pci 0000:00:1f.3: reg 20: [io 0x0500-0x051f]
    [ 0.593390] pci 0000:00:1f.5: [8086:3a26] type 0 class 0x000101
    [ 0.593401] pci 0000:00:1f.5: reg 10: [io 0xf200-0xf207]
    [ 0.593407] pci 0000:00:1f.5: reg 14: [io 0xf100-0xf103]
    [ 0.593413] pci 0000:00:1f.5: reg 18: [io 0xf000-0xf007]
    [ 0.593419] pci 0000:00:1f.5: reg 1c: [io 0xef00-0xef03]
    [ 0.593424] pci 0000:00:1f.5: reg 20: [io 0xee00-0xee0f]
    [ 0.593430] pci 0000:00:1f.5: reg 24: [io 0xed00-0xed0f]
    [ 0.593487] pci 0000:01:00.0: [10de:05e2] type 0 class 0x000300
    [ 0.593494] pci 0000:01:00.0: reg 10: [mem 0xf8000000-0xf8ffffff]
    [ 0.593502] pci 0000:01:00.0: reg 14: [mem 0xe0000000-0xefffffff 64bit pref]
    [ 0.593510] pci 0000:01:00.0: reg 1c: [mem 0xf6000000-0xf7ffffff 64bit]
    [ 0.593516] pci 0000:01:00.0: reg 24: [io 0xdf00-0xdf7f]
    [ 0.593521] pci 0000:01:00.0: reg 30: [mem 0x00000000-0x0007ffff pref]
    [ 0.593549] pci 0000:00:03.0: PCI bridge to [bus 01-01]
    [ 0.593551] pci 0000:00:03.0: bridge window [io 0xd000-0xdfff]
    [ 0.593553] pci 0000:00:03.0: bridge window [mem 0xf6000000-0xf9ffffff]
    [ 0.593557] pci 0000:00:03.0: bridge window [mem 0xe0000000-0xefffffff 64bit pref]
    [ 0.593587] pci 0000:00:1c.0: PCI bridge to [bus 02-02]
    [ 0.593638] pci 0000:03:00.0: [197b:2363] type 0 class 0x000106
    [ 0.593715] pci 0000:03:00.0: reg 24: [mem 0xfbdfe000-0xfbdfffff]
    [ 0.593752] pci 0000:03:00.0: PME# supported from D3hot
    [ 0.593756] pci 0000:03:00.0: PME# disabled
    [ 0.593780] pci 0000:03:00.1: [197b:2363] type 0 class 0x000101
    [ 0.593801] pci 0000:03:00.1: reg 10: [io 0xbf00-0xbf07]
    [ 0.593813] pci 0000:03:00.1: reg 14: [io 0xbe00-0xbe03]
    [ 0.593824] pci 0000:03:00.1: reg 18: [io 0xbd00-0xbd07]
    [ 0.593836] pci 0000:03:00.1: reg 1c: [io 0xbc00-0xbc03]
    [ 0.593847] pci 0000:03:00.1: reg 20: [io 0xbb00-0xbb0f]
    [ 0.593916] pci 0000:00:1c.1: PCI bridge to [bus 03-03]
    [ 0.593918] pci 0000:00:1c.1: bridge window [io 0xb000-0xbfff]
    [ 0.593921] pci 0000:00:1c.1: bridge window [mem 0xfbd00000-0xfbdfffff]
    [ 0.593948] pci 0000:04:01.0: [1102:0004] type 0 class 0x000401
    [ 0.593962] pci 0000:04:01.0: reg 10: [io 0xcf00-0xcf1f]
    [ 0.594015] pci 0000:04:01.0: supports D1 D2
    [ 0.594027] pci 0000:04:01.1: [1102:7003] type 0 class 0x000980
    [ 0.594040] pci 0000:04:01.1: reg 10: [io 0xce00-0xce07]
    [ 0.594093] pci 0000:04:01.1: supports D1 D2
    [ 0.594105] pci 0000:04:01.2: [1102:4001] type 0 class 0x000c00
    [ 0.594119] pci 0000:04:01.2: reg 10: [mem 0xfbeff000-0xfbeff7ff]
    [ 0.594127] pci 0000:04:01.2: reg 14: [mem 0xfbef8000-0xfbefbfff]
    [ 0.594177] pci 0000:04:01.2: supports D1 D2
    [ 0.594178] pci 0000:04:01.2: PME# supported from D0 D1 D2 D3hot
    [ 0.594181] pci 0000:04:01.2: PME# disabled
    [ 0.594221] pci 0000:00:1e.0: PCI bridge to [bus 04-04] (subtractive decode)
    [ 0.594224] pci 0000:00:1e.0: bridge window [io 0xc000-0xcfff]
    [ 0.594226] pci 0000:00:1e.0: bridge window [mem 0xfbe00000-0xfbefffff]
    [ 0.594230] pci 0000:00:1e.0: bridge window [io 0x0000-0x0cf7] (subtractive decode)
    [ 0.594232] pci 0000:00:1e.0: bridge window [io 0x0d00-0xffff] (subtractive decode)
    [ 0.594233] pci 0000:00:1e.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
    [ 0.594235] pci 0000:00:1e.0: bridge window [mem 0x000c0000-0x000dffff] (subtractive decode)
    [ 0.594236] pci 0000:00:1e.0: bridge window [mem 0xdff00000-0xfebfffff] (subtractive decode)
    [ 0.594250] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    [ 0.594335] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX0._PRT]
    [ 0.594351] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX1._PRT]
    [ 0.594375] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
    [ 0.594421] pci0000:00: Requesting ACPI _OSC control (0x1d)
    [ 0.594423] pci0000:00: ACPI _OSC request failed (AE_NOT_FOUND), returned control mask: 0x1d
    [ 0.594424] ACPI _OSC control for PCIe not granted, disabling ASPM
    [ 0.601329] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 11 *12 14 15)
    [ 0.601355] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
    [ 0.601380] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
    [ 0.601406] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 11 12 14 *15)
    [ 0.601431] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
    [ 0.601456] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 *7 9 10 11 12 14 15)
    [ 0.601481] ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 5 6 7 9 10 11 12 *14 15)
    [ 0.601506] ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
    [ 0.601562] vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
    [ 0.601565] vgaarb: loaded
    [ 0.601565] vgaarb: bridge control possible 0000:01:00.0
    [ 0.601611] PCI: Using ACPI for IRQ routing
    [ 0.602749] PCI: Discovered peer bus 3f
    [ 0.602767] pci 0000:3f:00.0: [8086:2c41] type 0 class 0x000600
    [ 0.602779] pci 0000:3f:00.1: [8086:2c01] type 0 class 0x000600
    [ 0.602792] pci 0000:3f:02.0: [8086:2c10] type 0 class 0x000600
    [ 0.602803] pci 0000:3f:02.1: [8086:2c11] type 0 class 0x000600
    [ 0.602815] pci 0000:3f:03.0: [8086:2c18] type 0 class 0x000600
    [ 0.602826] pci 0000:3f:03.1: [8086:2c19] type 0 class 0x000600
    [ 0.602837] pci 0000:3f:03.4: [8086:2c1c] type 0 class 0x000600
    [ 0.602848] pci 0000:3f:04.0: [8086:2c20] type 0 class 0x000600
    [ 0.602860] pci 0000:3f:04.1: [8086:2c21] type 0 class 0x000600
    [ 0.602871] pci 0000:3f:04.2: [8086:2c22] type 0 class 0x000600
    [ 0.602882] pci 0000:3f:04.3: [8086:2c23] type 0 class 0x000600
    [ 0.602894] pci 0000:3f:05.0: [8086:2c28] type 0 class 0x000600
    [ 0.602904] pci 0000:3f:05.1: [8086:2c29] type 0 class 0x000600
    [ 0.602915] pci 0000:3f:05.2: [8086:2c2a] type 0 class 0x000600
    [ 0.602926] pci 0000:3f:05.3: [8086:2c2b] type 0 class 0x000600
    [ 0.602938] pci 0000:3f:06.0: [8086:2c30] type 0 class 0x000600
    [ 0.602950] pci 0000:3f:06.1: [8086:2c31] type 0 class 0x000600
    [ 0.602961] pci 0000:3f:06.2: [8086:2c32] type 0 class 0x000600
    [ 0.602972] pci 0000:3f:06.3: [8086:2c33] type 0 class 0x000600
    [ 0.603233] PCI: pci_cache_line_size set to 64 bytes
    [ 0.603319] reserve RAM buffer: 000000000009f800 - 000000000009ffff
    [ 0.603320] reserve RAM buffer: 00000000dfde0000 - 00000000dfffffff
    [ 0.603384] NetLabel: Initializing
    [ 0.603385] NetLabel: domain hash size = 128
    [ 0.603386] NetLabel: protocols = UNLABELED CIPSOv4
    [ 0.603393] NetLabel: unlabeled traffic allowed by default
    [ 0.603400] HPET: 4 timers in total, 0 timers will be used for per-cpu timer
    [ 0.603403] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0
    [ 0.603406] hpet0: 4 comparators, 64-bit 14.318180 MHz counter
    [ 0.618592] Switching to clocksource hpet
    [ 0.621786] Switched to NOHz mode on CPU #0
    [ 0.621823] pnp: PnP ACPI init
    [ 0.621829] ACPI: bus type pnp registered
    [ 0.621868] pnp 00:00: [bus 00-3f]
    [ 0.621869] pnp 00:00: [io 0x0cf8-0x0cff]
    [ 0.621870] pnp 00:00: [io 0x0000-0x0cf7 window]
    [ 0.621873] pnp 00:00: [io 0x0d00-0xffff window]
    [ 0.621874] Switched to NOHz mode on CPU #1
    [ 0.621875] pnp 00:00: [mem 0x000a0000-0x000bffff window]
    [ 0.621877] pnp 00:00: [mem 0x000c0000-0x000dffff window]
    [ 0.621878] pnp 00:00: [mem 0xdff00000-0xfebfffff window]
    [ 0.621894] Switched to NOHz mode on CPU #3
    [ 0.621900] Switched to NOHz mode on CPU #2
    [ 0.621902] pnp 00:00: Plug and Play ACPI device, IDs PNP0a03 (active)
    [ 0.621940] pnp 00:01: [io 0x0010-0x001f]
    [ 0.621941] pnp 00:01: [io 0x0022-0x003f]
    [ 0.621942] pnp 00:01: [io 0x0044-0x005f]
    [ 0.621943] pnp 00:01: [io 0x0062-0x0063]
    [ 0.621944] pnp 00:01: [io 0x0065-0x006f]
    [ 0.621945] pnp 00:01: [io 0x0074-0x007f]
    [ 0.621946] pnp 00:01: [io 0x0091-0x0093]
    [ 0.621947] pnp 00:01: [io 0x00a2-0x00bf]
    [ 0.621948] pnp 00:01: [io 0x00e0-0x00ef]
    [ 0.621949] pnp 00:01: [io 0x04d0-0x04d1]
    [ 0.621950] pnp 00:01: [io 0x0290-0x029f]
    [ 0.621951] pnp 00:01: [io 0x0800-0x087f]
    [ 0.621952] pnp 00:01: [io 0x0290-0x0294]
    [ 0.621957] pnp 00:01: [io 0x0880-0x088f]
    [ 0.621996] system 00:01: [io 0x04d0-0x04d1] has been reserved
    [ 0.621998] system 00:01: [io 0x0290-0x029f] has been reserved
    [ 0.621999] system 00:01: [io 0x0800-0x087f] has been reserved
    [ 0.622001] system 00:01: [io 0x0290-0x0294] has been reserved
    [ 0.622002] system 00:01: [io 0x0880-0x088f] has been reserved
    [ 0.622004] system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
    [ 0.622010] pnp 00:02: [dma 4]
    [ 0.622011] pnp 00:02: [io 0x0000-0x000f]
    [ 0.622012] pnp 00:02: [io 0x0080-0x0090]
    [ 0.622013] pnp 00:02: [io 0x0094-0x009f]
    [ 0.622014] pnp 00:02: [io 0x00c0-0x00df]
    [ 0.622029] pnp 00:02: Plug and Play ACPI device, IDs PNP0200 (active)
    [ 0.622054] pnp 00:03: [irq 0 disabled]
    [ 0.622059] pnp 00:03: [irq 8]
    [ 0.622060] pnp 00:03: [mem 0xfed00000-0xfed003ff]
    [ 0.622078] pnp 00:03: Plug and Play ACPI device, IDs PNP0103 (active)
    [ 0.622092] pnp 00:04: [io 0x0070-0x0073]
    [ 0.622108] pnp 00:04: Plug and Play ACPI device, IDs PNP0b00 (active)
    [ 0.622112] pnp 00:05: [io 0x0061]
    [ 0.622127] pnp 00:05: Plug and Play ACPI device, IDs PNP0800 (active)
    [ 0.622132] pnp 00:06: [io 0x00f0-0x00ff]
    [ 0.622135] pnp 00:06: [irq 13]
    [ 0.622152] pnp 00:06: Plug and Play ACPI device, IDs PNP0c04 (active)
    [ 0.622220] pnp 00:07: [io 0x0400-0x04cf]
    [ 0.622221] pnp 00:07: [io 0x04d2-0x04ff]
    [ 0.622254] system 00:07: [io 0x0400-0x04cf] has been reserved
    [ 0.622255] system 00:07: [io 0x04d2-0x04ff] has been reserved
    [ 0.622257] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
    [ 0.622352] pnp 00:08: [mem 0xf0000000-0xf3ffffff]
    [ 0.622390] system 00:08: [mem 0xf0000000-0xf3ffffff] has been reserved
    [ 0.622392] system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
    [ 0.622472] pnp 00:09: [mem 0x000d3000-0x000d3fff]
    [ 0.622473] pnp 00:09: [mem 0x000f0000-0x000f7fff]
    [ 0.622474] pnp 00:09: [mem 0x000f8000-0x000fbfff]
    [ 0.622476] pnp 00:09: [mem 0x000fc000-0x000fffff]
    [ 0.622477] pnp 00:09: [mem 0xdfee0000-0xdfeeffff]
    [ 0.622478] pnp 00:09: [mem 0x00000000-0x0009ffff]
    [ 0.622479] pnp 00:09: [mem 0x00100000-0xdfedffff]
    [ 0.622480] pnp 00:09: [mem 0xdfef0000-0xdfefffff]

    After doing some troubleshooting I have discovered that the GB regdom is set when I connect to my wireless accesspoint with wicd. Wicd uses wpa_supplicant, I have set COUNTRY=BO in wpa_supplicant.conf, but it didnt help. If I dont connect I get to use my wireless adapter with the BO regulatory settings. Its a big mystery, especially considering the fact that I'm not in the GB, havent been there with this computer and I didnt find any config files where this locale was set either. Does anybody have an idea?
    Last edited by wims (2012-01-12 05:40:41)

Maybe you are looking for

  • Trigger a process when a record is inserted into database

    Hi, could someone tell me how to do the following (if it's possible): when a record is inserted into a table in a database, I want it to somehow trigger an action which will put an item into user's To-Do inBox of the WorkSpace, the user can then open

  • Save for web in CS5

    I bought a new computer that runs Windows 7 and this forced me to purchase a new version of Illustrator. I previously used CS4 and now I'm using CS5. In the old version I would do the following. 1. Open a new Illustrator document with the artboard 8.

  • Canon D1X Raw Files and IPhoto 6.0.6

    I'm unable to load Raw files into IPhoto 6.0.6 from my Canon G1X on a Macbook Pro using OS 10.7.4. I've resisted upgrading to a later version of IPhoto because of the negative comments about the later versions, and indeed never would as my existing v

  • Export to Portal via Broadcaster missing folders

    I am using the Broadcaster option 'Export to Portal'.  From the portal, I do the following: 1.  Select Business Intelligence > BEx Broadcaster 2.  I select my Web template 3.  I select Distribution Type = 'Broadcast to the Portal' 4.  For output form

  • How to implement Master-Detail Search in TopLink without using DataControl

    Hi, I am using TopLink and EJB in our requirement. But we are not creating any data controls. Without data controls how to implement master detail search using TopLink and EJB. I did search for a single table. It is working fine. The way i implented