Unpacking a bios

I have dual Inno 6600GTs which wont work in SLI mode. Inno have provided me with a new bios which appears to be in a packed format. The file (called gf66gt128.46) shows as a size of 64,512, packed to 43,774 in winzip. Can anyone offer any assistance on how to unpack this to the correct format. Anything I attempt comes up unrecognised format/program etc etc. I am still awaiting advice from Inno but I thought that an expert on here would be able to help in the meanwhile.
Cheers
Bill

Hello,
So is gf66gt128.46 a file in the ZIP?
I think gf66gt128.46 is the BIOS image.
You will need this
http://downloads.guru3d.com/download.php?det=972
Use 1 card in the PC when you flash it.
Can you show me the actual file that inno3d sent you, attach it here.
Do not try this yet until you are sure, maybe post this to inno3d and ask if it is how to flash the bios.
HOW TO FLASH THE BIOS
==============
Download this run it to make a RMADRIVE boot disk.
http://www.nerdlabs.org/bootdisks/diskimages/wboot98se.exe
Then get a 2nd floppy disk, copy nvflash to it and the BIOS file.
Boot from the RAMDRIVE DISK, start computer without cdrom support.
once its all loaded, put in the 2nd disk.
type
copy a:\*.* c:
press enter
type
c:
press enter
type
nvflash -f gf66gt128.46
press enter
it should flash the BIOS.
==============

Similar Messages

  • Bios update Satellite 1730

    I want to update the BIOS and have already downloaded and dezipped the file. This file I have copied onto a floppy. In the desciption they say I have to restart the computer and press a certain key( F12 or the key left to the space bar). But this didnot work. Does anyone know how to proceed?
    Guenter.

    Hi
    on this model You don't need to press F12 or any other key. Just unpack the BIOS-packege to a blank floppy, reboot the machine and make sure it boots from the floppy. The BIOS upgrade will be done automatically.
    Make sure that You have the AC-Adaptor connected!!
    BR Tom

  • K9N2 Diamond + AMD Phenom II X4 955 Black Edition: BIOS too old?

    I just put my system together and can't get it to boot. I've found out that it could be a bios problem , is there any way to tell what bios version it is without getting to the boot screen. Also is there anyway to change the bios with no boot screen.
    it's a k9n2 diamond motherboard with a phenom II x4 955 BE CPU
    Add a reply

    Quote
    red
    green
    green
    red
    = Processor Initialization
    You have pretty much three options right now:
    1) Install a processor officially supported by BIOS Version 2.3 to start the system and then update your BIOS.
    2) Ask in a local computer shop or contact your reseller to do the same thing for you.
    3) Alternatively, you can try this (at your own risk, of course, and there is no guarantee that it will work):
    - Download the latest BIOS Archive: http://download1.msi.com/files/downloads/bos_exe/7375v24.zip
    - Unpack the BIOS File (A7375NMS.240) and rename it to AMIBOOT.ROM
    - Copy the AMIBOOT.ROM file to an empty floppy disk
    - hook up a floppy disk drive to your K9N2 Diamond and insert the floppy disk with AMIBOOT.ROM on it
    - hook up a PS/2 Keyboard and disconnect all hard drives, optical drives and USB Devices (and use one memory stick only)
    - Clear CMOS with main A/C power cable removed from PSU
    - Start-up the system and press CTRL + Home on your PS/2 Keyboard multiple times after start-up
    - If you are lucky, the key command will trigger the AMI BIOS Recovery Routine which will attempt to read and program the AMIBOOT.ROM File on the floppy disk.
    If option number 3) does not work for you, go back to 1) or 2).

  • BIOS recovery on Satellite C660D

    Hi
    I recently tried to update my bios (because i got a message from tempro telling my it needed updateing) which has left my laptop C660D effectively dead - blank screen on start up.
    I am in the process of creating a crisis recovery disk and the guidance i have obtained from the net tells me I need to extract the .ROM file from the correct BIOS update for my laptop and add it onto the crisis recovery disk.
    However when I unpack the Bios update for a Tosh c660D I see there are 2 folders, each with 2 .ROM files in them.
    Folder DIS
    BIOS.rom (2048KB)
    EC.rom (128KB)
    Folder UMA)
    BIOS.rom (2048KB)
    EC.rom (128KB)
    The files with the same names in both folders look identifical to one another. but can anyone advise which is the correct ROM I should drop onto the Crisis Recovery Disk
    Many thanks
    eddie

    Hi
    From my point of view its no matter what BIOS.rom file you will take since both looks identical

  • Best bios for z68-gd65 G3

    I am using the latest bios from the msi website (v25.8) and have a 2600K. Ever since upgrading to the newer bioses with the new management engine, my overclocking potential has really gone down.
    I ran at 4.6 Ghz stable before but now I am struggling with 4.3 GHz. I have tried to increase the voltage but that has very little impact on the stability.
    So do you have any input on what bios revision would be the best for overclocking a SB on this motherboard?
    I have seen post making it possible to downgrade the ME aswell?
    Regards M

    Ivy bios versions won't work well for oc with Sandy cpus on 6 series chipsets.
    You can try the betas with suggested method: https://forum-en.msi.com/index.php?topic=163866.0
    To be sure you can downgrade to the latest Sandy version 22.8 with the following method (it won't work any other way!):
    >>Use the MSI HQ Forum USB flasher<< and with it point to the attached and NOT unpacked (!) bios archive (Mode 1: Point to Archive). After flashstick has been prepared boot from it and let it flash the bios.

  • P35D3 Platinum will not POST, CPU: E8500, RAM: KVR1333D3N9/1G RAM HELP!

    Ok guys please help me...
    I received this item (P35D3 Platinum) back from MSI today after sending it to them RMA, they said there is nothing wrong with it, sent it back, and it is still doing the same thing. 
    Here is the issue:
    1st when i boot it up the computer turns off and on 4 times by it self, then it freezes up on "testing Base and extended memory Testing base memory from 240k to 640k and extended memory above 1mb using various patterns" (light pattern is as follows: Group 4 - Green, Group 3 - Red, Group 2 - Green, Group 1 - red).  On the screen/monitor it shows your "MSI" logo and says "press TAB to switch to POST or DEL to run BIOS setup."  But it does not respond my pressing any buttons on computer.
    Here is a link to your website that states my ram is compatible: http://www.ec.kingston.com/ecom/configurator_new/modelsinfo.asp?SysID=38177&mfr=MSI&model=P35D3+Platinum+Motherboard&root=&LinkBack=&Sys=38177-MSI-P35D3+Platinum+Motherboard&distributor=0&submit1=Search
    I have KVR1333D3N9/1G RAM i have tried a single dimm in all 4 slots (item is new)
    I have a Intel E8500 Dual Core Processor (item is new)
    I have a invidia 8800GTX OC, (pulled from working computer, and i know it works)
    I am using a USB mouse and keyboard.  <-- (is that ok or do i need PS2 keyboard since no OS is installed??)
    Why am i stuck, what am i missing here? Any help would be great
    Thanks for your help on this issue..
    Shawn

    Quote from: Jack the Newbie on 21-January-09, 09:58:02
    Okay, from the symptoms you describe, your problem is rather minor.  You seem to have the E0-Revision of the E8500 (which requires BIOS Version 1.6).  Your BIOS is probably older than that and does not include the proper microcode to fully support that processor.  The signs you describe are well known on P35 Mainboards. 
    Please check the following:
    1) The sSpec-Number of your processor:
    ---> SLB9K = E8500/E0
    ---> SLAPK = E8500/C0
    2) Check the factory BIOS-Version:
    It should be printed on a small sticker on the BIOS Chip itself. You can find the BIOS Chip here:
    Look for "A7356 IMS ? ? ?".  If it says "160" where I put the question marks, you have v1.6 (120 would be v1.20).
    Now, if your BIOS Version is older than v1.6, please try this:
    - Download the latest BIOS Archive from the product site of your board and unpack the BIOS File (A7356IMS.160)
    - Rename A7356IMS.160 to AMIBOOT.ROM and copy this file to an empty, formated and flawlesse floppy disk
    - attach an internal floppy drive to the mainboard (make sure that it is properly connected)
    - attach a PS/2 Keyboard
    - start-up the system and hit CTRL+Home on the keyboard continiously and check if the system accesses the floppy drive and initiates an AMI BIOS Recovery Flash
    If the you are able to update the BIOS via the AMI Recovery Routine, your processor should be properly supported and the system should be able to start-up properly after that.
    If the procedure does not start after pressing CTRL + Home, try to get you hands on an older processor to be able to flash the BIOS the regular way to support your E8500/E0.
    In case you cannot get your hands on a supported processor, I suggest you ask in a local computer shop for assistance.  This looks like a solvable problem.
    Ok Jack the newbie, i got a floppy disk and renamed the file, got a PS2 keyboard (and tab worked i was able to see i have v1.4 before it locked up on me.), did just as you instructed me...  New the computer keeps turning off and on when i press CTRL + Home, i hear it start reading the floppy but then it just turns off and on over and over and does not update.
    The only other processor i have is a intel P45 dual core, i think the mobo supports it but i dont know if it will work with the DDR3 ram i have.  Thanks for you help,
    One more thing, just so you know, after it started turning off and on i did pull the battery and press the reset bios button and tried again, but still it just turns off and on.
    Thanks,
    shawn

  • User guide: MSI HQ USB BIOS Flash Tool

    Guide based on USB tool v1.17c
    HOW TO properly use the MSI Forum HQ USB Flashing Tool to update your BIOS
    This user guide provides a step-by-step explanation for properly using the >>MSI Forum HQ USB Flashing Tool<< to prepare a USB Flash Drive for a safe BIOS-Flash in a pure DOS Environment. The tool itself will not perform the actual flashing operation.  It will "only" help you to get your USB Stick set up for an automated DOS flashing procedure which requires final confirmation.  (If you should run into any problems before you are prompted for final confirmation in DOS, no attempt to flash has been made yet and there is no danger of a bad flash.)
    NOTE: If you are having problems getting your USB device to boot correctly, you may need to format it correctly as the geometry data may be incorrect. You can do that by pickup option "Fix My USB key" from the Tool or by using >>> THIS <<< tool here! For future usage you can skip this step, it need to be done only once if your stick need adjustment.
    Symptoms that your USB key need a fix after booting from the USB key:
    * Error: "No bootable partition in table"
    * Blinking cursor in a top left corner and nothing happens
    * "RIVER2 MSI"
    * "Error loading operating system"
    * "Missing operating system"
    * "Disk in drive is not a bootable"
    * Booting from selected USB key is IGNORED, the other/typical OS continue to load as usual
    If still no change after using "Fix My USB key" Tool's option or HP Formatter Tool as alternative.
    Then try with different USB key, the issue is there.
    Note: Those USB keys who support "U3 Smart", this "feature" must be removed before proceed.
    Refer to followed link: http://u3.sandisk.com/launchpadremoval.htm
    Read the three notes that follow first before you move on:
    1. Note: Before you even think about flashing a different BIOS, be sure that your system is stable. If it is not stable, make it stable first. (Read >>here<<.)
    2. Note: Make sure your system meets the preconditions and system requirements mentioned below before you attempt to use the tool.
    3. Note: Do know that flashing your BIOS, be it with the help of the tool or otherwise, is done at your own risk.
    Contents of the Guide:
    0. Preconditions & System Requirements
    1. Basic Description of Functionality
    2. Installing/Starting the tool.
    3. Choosing a Preparation Method
      3.1. Method 1: Processing a BIOS Archive Directly (ZIP/RAR)
      3.2. Method 2: Processing a BIOS File Directly
      3.3. Method 3: SureHands Live Update
      3.4. Method 4: Geometry Change
    4. Selecting the USB Flash Drive for preparation
    5. BIOS Settings, Booting & Flashing
      5.1. BIOS Settings to Check
      5.2. Booting from USB Flash Drive
      5.3. Flashing Procedure/Running MemTest86+ & CMOS-Clear
    6. FAQ: Common Problems & Solutions
    7. Version History
    0. Preconditions & System Requirements
    The main precondition for using the tool is a working & healthy Windows installation on the system that needs the BIOS flash.  The Tool is designed to work with MSI Retail Boards & Laptops only.
    Please note mainboards of other brands and OEM boards that are manufactured by MSI but sold by Medion, HP, NEC and others are not supported. If you have an OEM board that needs a BIOS update read this topic: >>OEM boards manufactured by MSI<<
    Supported Operating Systems: All current Windows Versions (32bit & 64bit, any service pack (SP)): Windows NT, Windows 2000, Windows 2003, Windows XP, Windows Vista, and Windows 7.
    The second requirement is that you have a fully functional USB Flash Drive that uses the FAT file system (FAT/FAT32).  NTFS is not supported. If your USB Flash Drive is using the NTFS File System, reformat it to FAT or FAT32.
    As the tool also provides a Live Update Option ("SureHands"), you'll need a working internet connection if you want to choose this method. Not all boards are supported at this point.*
    * Check section 3.3 of this guide to see if your board is currently supported by the SureHands feature.
    1. Basic Description of Functionality
    The MSI Forum HQ USB Flashing Tool will help you to easily prepare an USB flash drive for an automated BIOS flash in a pure DOS environment, which is the safest way to perform such a procedure. The tool will also allow you to run MemTest86+ in a pure DOS environment. However, the preparation of your USB Stick is done in Windows and basically includes two steps:
    (1) The device will be made bootable.
    (2) All necessary files (incl. BIOS file, actual flasher and MemTest86+ executable) and all DOS commands that are needed to flash/test memory will automatically be implemented.
    Because the tool does not reformat your USB Flash Drive*, no files that may currently be on the stick will be lost during the procedure.  Just make sure that there is still some free drive space, otherwise there will not be enough room for the files that are needed for BIOS Flashing.
    * Excluding the Geometry Change method which will destroy all data on the USB storage device.
    2. Installing/Starting the tool
    Treat the forum's USB Flashing Tool like a regular application.  Download it to and run it from your hard drive, there is no need to copy & start it from the USB Flash Drive that you want to use for flashing.  Both, the installer version and the stand-alone version, do precisely the same job.  Which of the two versions you use, is solely up to you and your preferences.  The stand-alone version can be started directly by clicking on the executable file.  The installer version will perform an installation and provide you with an entry in your start menu and a desktop shortcut to start the tool.
    When you start the tool a DOS box should open up to provide you with status messages and prompts.  Do not close that box unless you want to abort the preparation procedure!
    Please ensure that you connect the USB flash drive you wish to use before starting the Tool!
    NOTE: If you do not connect your USB storage device before starting the tool, or the tool doesn't detect it. You can still insert the drive letter, as the tool will continue as normal.
    The tool will first check, if an MSI mainboard is installed in your system and show you its model name and PCB Version in a message box. Click >OK< to continue to choose the tool's preparation method that you want to use to prepare your USB Flash Drive.
    3. Choosing a Preparation Method
    If your MSI Retail Board is properly detected and you have pressed the >OK< button in the message box, an option box will pop up that allows you to choose between three different operating modes.  The options you can choose from are more or less self-explanatory, however, read the detailed description if you are unsure how to proceed at this point:
    3.1. Method 1: Processing a BIOS Archive Directly (ZIP/RAR)
    Official MSI BIOS-Updates that can be downloaded from the product site of your board model do usually come as .ZIP or .RAR archives that contain the actual BIOS File and the corresponding AWARD or AMI flashing utility (depending on the BIOS Type of your board).  If you have downloaded such an archive, you should choose the first method from the option box. 
    You do not need to extract the files from the BIOS archive.  The tool will ask you to point it to the archive you downloaded and automatically extract the BIOS File and the AMI or AWARD flashing utility and put it them on your USB Flash Drive.  You don't have to worry about anything else.  All you have to do is to remember where you saved the ZIP or RAR file you downloaded:
    3.2. Method 2: Processing a BIOS File Directly
    If you do not have a ZIP or RAR archive that already contains a BIOS File and the proper flashing utitility, but only the plain unpacked BIOS File, choose the second Method from the option box.  In most cases BETA BIOS Files supplied by MSI Support or shared here in the Forum do not come with the proper flashing utility.  If the MSI Forum HQ USB Flashing Tool is told to process a plain BIOS File, it will automatically check the type of BIOS File (AMI or AWARD) and then select the proper flashing utility that needs to be used.  All you need to do is point the tool to the BIOS-File that is supposed to be flashed:
    3.3. Method 3: SureHands Live Update
    "SureHands Live Update" is the third operation method you can choose from the option box.  It provides a much safer and more reliable alternative to MSI Live Update as the actual BIOS Flash is performed in a pure DOS environment as well.  If you decide to use this option, you do not to supply the tool with a BIOS-Archive or a BIOS-File.
    Not all MSI Retail Boards are currently supported.  With every update of the USB Flashing Tool more boards will be added.  At present, you can use the "SureHands" Live Update method with the following boards only (the list will be updated regularly):
    AMD based boards:
    K8N Neo4-F (MS-7125, PCB 3.0)
    K8NGM2-FID (MS-7207, PCB 2.0)
    K8N Diamond Plus (MS-7220, PCB 1.0)
    K8N Neo3 (MS-7135, PCB 1.0 & 2.0)
    K9A Platinum (MS-7280, PCB 1.0)
    K9A2 Platinum (MS-7376, PCB 1.0)
    K9A2 CF-F (MS-7388, PCB 1.0)
    K9N Neo-F (MS-7260, PCB 1.0 & 2.0)
    K9VGM-V (MS-7253, PCB1.0)
    K9N2GM-F V2 (MS-7509, PCB 1.0)
    K9N Neo V2 / V3 (MS-7369, PCB 1.1)
    K9N Platinum & K9N SLI Platinum (MS-7250, PCB1.0)
    K9N2 Diamond (MS-7375, PCB 1.1)
    K9N2 SLI Platinum (MS-7374, PCB 1.1)
    K9N2 Zilent (MS-7374, PCB 1.1)
    K9N2 Neo-F (MS-7511, PCB 1.1)
    DKA790GX Platinum (MS-7550, PCB 1.1)
    790FX-GD70 (MS-7577, PCB 1.0)
    790GX-G65 (MS-7576, PCB 1.0)
    Intel based boards
    HydroGenX48C & X48C Platinum (MS-7353, PCB 3.0)
    X48 Platinum (MS-7353, PCB 1.0)
    X38 Diamond Plus
    X38 Diamond (MS-7353, PCB 1.0)
    X38 Platinum (MS-7353, PCB 1.0)
    EFINITY-FP (MS-7395(E), PCB 1.0)
    P35 Neo Combo-F (MS-7365, PCB 1.0)
    P35 Neo2 Series (MS-7345, PCB 1.1)
    P35 Platinum (MS-7345, PCB 1.1)
    P35 Neo-F (MS-7360, PCB 1.0)
    G33 Platinum (MS-7345, PCB 1.1 & PCB 1.2)
    P965 Platinum (MS-7238, PCB 1.1)
    975X Platinum PowerUp Edition (MS-7246, PCB 2.1)
    865PE Neo2-P Platinum Edition (MS-6728, PCB 2.0C)
    P7N SLI Platinum (MS-7380, PCB 1.0)
    P7N2 Diamond (MS-7523 PCB 1.0)
    P7N Diamond (MS-7510, PCB 1.0)
    P7N SLI Platinum (MS-7380, PCB 1.0)
    P6N Diamond (MS-7320, PCB 1.0)
    P6N SLI Platinum (MS-7350, PCB 1.0)
    P6N SLI-FI (MS-7350 PCB 2.0)
    P6N SLI V2 (MS-7346 PCB 1.0)
    ECLIPSE SLI (MS-7520, PCB 1.0)
    ECLIPSE Plus (MS-7566, PCB 1.0)
    P35 Neo3-F (MS-7395, PCB 1.0)
    After selecting "SureHands" from the option box, the tool will automatically check for all available official BIOS-Versions for your mainboard.  It will also look for the latest available BETA BIOS Version for you board and save that information in a TXT-File on your Desktop:
    Note: The SureHands option will not provide you with the latest BETA BIOS, it will only provide the information.
    When the tool is done scanning for official BIOS releases for your board, it will give you the possibility to manually choose the BIOS Version you want to flash.  SureHands Live Update will not automatically select the latest version and use it for flashing, it will give you the chance of choosing between all available official BIOS releases that are available:
    Note that the "May not exist" comment that appears behind some versions does not mean that the BIOS does not exist.  If you know the latest BIOS for your board is e.g. v1.8, SureHands will retrieve it even though there may be such a comment.  That message is part of a prediction feature that tries to determine future BIOS Releases.  If a BIOS version that was predicted by the SureHands feature is not available yet, the tool will tell you if it cannot retrieve the files and ask you to select an earlier version.
    3.4 Geometry Change
    If the tool fails to make your USB storage device bootable then you will need to use this mode. It will make your drive bootable, select it:
    Select your drive then let the tool do it's business.
    Once the process is complete, run the tool again via method 1, 2 or 3, restart your computer and try booting from the USB storage device again.
    NOTE: This method will destroy ALL data on the USB storage device!
    NOTE: This method is available in v1.17 and beyond.
    4. Selecting the USB Flash Drive for preparation
    When you have chosen one of the three methods from the option list and pointed the tool at the corresponding archive, BIOS File or selected the desired BIOS Version from the list in case you chose to use SureHands Live Update, the MSI Forum HQ USB Flashing Tool will prompt you to enter the drive letter of the USB Flash Drive you want to use for flashing:
    Note that certain drive letters are reserved and will therefore not be accepted by the tool (currently A:, B: and C:). If you are sure you have connected an USB Flash Drive to the system that works properly but it does not appear in the table that appears in the DOS box, enter the corresponding drive letter anyway and see if the tool accepts it.  This can happen in rare cases, but it is usually no problem.
    The tool will check the selected drive and will provide you with status messages.  If everything is okay, the message should look like this:
    The tool will attempt to make the device bootable and automatically write all files that are needed for flashing to the drive to prepare it for flashing.  If the procedure was successful, you will get the following message in the DOS box:
    5. BIOS-Settings, Booting & Flashing
    If the Tool has prepared your drive for booting & flashing, no BIOS flash attempt has been made yet. Only the preparation process. In order to initiate the flashing procedure, you have to restart your system and make it boot from the USB Flash drive. Before you move on to do that, enter the BIOS Setup and check a few options:
    5.1. BIOS Settings to Check
    Check USB-related Options in BIOS:
    - USB Controller
    - USB 2.0 Controller
    - USB Legacy Support
    - USB Storage Support
    - Boot from other devices
    - etc.
    Not all of these options may be found in BIOS and the precise name may vary as well.  Just make sure you checked for such options and that they are enabled (if present).
    Another option you should check for is "Boot Sector Protection".  If such an option is present in your BIOS, make sure it is disabled because it may make a BIOS Flash impossible.
    @all Overclockers: In case your system is currently overclocked, make sure you roll back to default clock and voltage settings before you attempt to start the flashing procedure. Otherwise you increase the risk of an unsuccesful flash, and you most probably don't want something like that to happen.
    5.2. Booting from USB Flash Drive
    To boot from your USB drive you can either change the boot sequence in BIOS accordingly or just press F11 during POST* to get access to the BIOS Boot Menu.  From here, you can select you drive directly without having to adjust the boot sequence in BIOS.  Note that your USB Flash Drive may be listed as a hard drive (if you choose that entry you will get another list to choose from).
    * Not all mainboards use F11, for the boot menu. If F11 fails for you, please consult your manual for the correct key.
    Note: If you have problems booting from your drive, look at the FAQ-Section of this guide and see if any of the tips resolve the issue.
    5.3. Flashing Procedure/Running MemTest86+
    As soon as the system boots from the drive, DOS will be loaded and you will be displayed with two options. One option will start MemTest86+, the other will begin the flashing procedure. If no choice is made, MemTest86+ will automatically start.
    The flashing procedure will automatically be initiated from there.  You will see status messages on the screen that will supply you with information and also prompt you for final confirmation for the actual BIOS-Flash.  A backup of you current BIOS will automatically be saved to a file on the drive (backup.bin) before the flashing actually starts.  You do not need to enter any commands in DOS.  All you have to do is acknowledge the information on the screen by pressing a key.
    The flash itself will only take a couple of seconds (20-30s at the most).  If the flashing is successfully completed, shutdown the system and clear CMOS with main A/C power cable removed from PSU.  Read the >>Clear CMOS Guide<< for further information. 
    After clearing CMOS you have completed the BIOS-Flash. 
    Guide created by Jack The Newbie and the forum team

    Version updated to 1.18x:
    * Mode 3 Sure Hands, Live Update:
    - Removed beta BIOS query check[global]
    - Fixed issue K9N2 Diamond unable to be detected as supported unit if onboard is installed BIOS version 2.4,
     add dynamic detection for future versions.
    - Fixed issue 790FX-GD70 unable to be detected as supported unit and add dynamic detection for future versions.
    - Fixed issue 790GX-G65 unable to be detected as supported unit and add dynamic detection for future versions.
    - Add support for 785G-E65, add dynamic detection for future versions, prediction BIOS range 3.1 - 3.A
    - Add support for 785G-E53, add dynamic detection for future versions, prediction BIOS range 3.1 - 3.A
    - Add support for 790GX-G65 Winki ED, prediction BIOS range 2.1 - 2.A
    - Fixed issue P7N Diamond unable to be detected as supported unit if onboard BIOS installed is 1.3 and above,
     add dynamic detection for future versions.
    - Add support for K9A2 Neo2, prediction BIOS range 7.4 - 7.D
    - Add support for 790XT-G45, prediction BIOS range 2.2 - 2.B
    - Add support for 770T-C45, prediction BIOS range 8.4 - 8.D
    - Add support for 770T-C35, prediction BIOS range 8.4 - 8.D
    - Fixed issue K9A2 Platinum[V1,V2] unable to be detected as supported unit if onboard BIOS installed is 1.9,
     add dynamic detection for future versions, prediction BIOS range extended to 1.F0
    - 790GX-G65 board prediction BIOS range extended to ver: 1.D0
    - 790GX-G65 board update bios base ver from 1.xx to 4.xx [following new msi rule for this board jumping from 1.xx to 4.xx]
    - Add support for 770-C35|C45 boards [p1] BIOS range 1.40 - 1.D0
    - Add support for 770-G45 board [p2] BIOS range A10 - AA0
    * Add "Exit" option to navigation screen
    * Update version info related to boot part
    * Update boot part to handle newest features
    * Modify Self update sequence of Installer version
    * Update internal version check ID
    * Mode 4 minor update
    * Build and add new Tool's module for newest features
    * W32 Tool's exit time part decreased by 10 seconds
    * On received OS reboot user request, time delay before execution decreased by 15 seconds
    * Update EC decoder
    * Update start-up information screen
    * Auto store start-up detected information to user's desktop ==> [MSIHQ_INFO.TXT]
    Details:
    Easy to show machine information on request, instead write down from the screen manually, now just copy/paste can be used from MSIHQ_INFO.TXT
    User can check and compare information before and after the BIOS update
    Also usefull if didn't remember what was his original BIOS or EC versions before the update, Tool will auto store it there.
    And easy can be checked if needs. E.g Tool's log file of each Tool's execution, each report will include date and time as well.
    F.A.Q example:
    Q: I flashed BIOS on my notebook and now it doesn't work properly.. And i don't remember what was my old BIOS version.. What can i do?
    A: Take a look in MSIHQ_INFO.TXT at your desktop, there is auto recorded your detailed information about your notebook before the BIOS update.
    So you can easy find what was your original BIOS & EC versions.
    Is it OEM one or not, and the exact original BIOS & EC versions.
    So you can roll back easy or if crossflashing were done to reflash to correct versions.
    Example question:[this board now use 4.xx bios, but don't have time to make a new images.]
    It's just example, do not mean that this BIOS used in the example is bad. But generally often can need to roll back to older version.
    Or to use Sure Hands because[The BIOS is N/A for manual download, By SureHands no need to browse/search/download and point to the BIOS version, also eliminate any chances to pickup the wrong BIOS, and not at last its more quickly[save a time]]
    Q: I flashed my BIOS via MSI Live Update, but the new BIOS has an issues.
        How i can roll back to my old BIOS version?
        The MSI LiveUpdate can only update to the latest BIOS version, which is not good for me.
        And i can't download my old BIOS version manually... Because "This BIOS can only update via Live Update function"
        http://eu.msi.com/index.php?func=downloaddetail&type=bios&maincat_no=1&prod_no=1739
        How i can re-flash to my original BIOS version and from where can i get it?
    A: Run >>Use the MSI HQ Forum USB flasher<<,
    then choose Mode 3 [Live Update{aka SureHands}]:
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in ба 30.12.2009 Ј. at 21:09:45,15
    Mainboard:  790GX-G65 (MS-7576)       
    PCB Version:  1.0
    BIOS Version: V1.3
    BIOS Date:  05/08/2009
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in ба 30.12.2009 Ј. at 21:22:38,42
    Mainboard:  790GX-G65 (MS-7576)       
    PCB Version:  1.0
    BIOS Version: V1.6
    BIOS Date:  11/30/2009
    Then choose your old BIOS version from the list:
    The followed image used below is a sample from Eclipse board,[no time to make accurate image] but will look similar for others boards too:
    In a list will be noticed that there is a future BIOS versions.
    Some of them will be not released yet. If you pick some of those the Tool will note you:
    It's a part of Tool's BIOS prediction system called "Crystal Ball", when MSI release a future BIOSes for your board,
    Tool can find them immediately. By that way the Tool no need to be updated to be actual in each moment
    * Add new feature "True BIOS Version Ready"
    - Updated Mode 1
    - Updated Mode 2
    - Updated Mode 3
    Details:
    Q: What "True BIOS Version Ready" means? Does the Tool show the wrong BIOS version until now? 
    A: Of course not, the Tool always show accurate info.
    The same as CPU-Z/Everest of whatever other Tool.
    However Tool also detect EC-FW versions for notebooks:
    The "True BIOS Version Ready" Tool's feature is aimed to eliminate user's mass confusion about MSI BIOS versions.
    And not only users are confused, but MSI's Live Update is confused too... which confuse users even more..
    Few typical real examples of confusion:
    "K9A2 CF wont flash to Bios v. 1.A !!!" 
    Quote from: Fingon on 25-October-09, 16:53:15
    Hi MSI,
    I have a problem. I have bought a new processor: AMD Phenom II x545. I looked on the support page of my MB (MSI K9A2 CF) and there the CPU is supported from the bios version 1.A. So I wanted to flash the Bios the the newest version (1.A). I used the MSI live update 4 program to flash it via windows mode. But everytime it boots it writes "CMOS checksum BAD", then I hit F1 to Bios and I see the version of my BIOS fell to the oldest version 1.1. Then I tried to flash it thru Flash disc (with boot files) and dos mod. The result is the same. I can flash my MB to version 1.8 but when I try the 1.A it wont flash it and my Bios fell to the oldest version (1.1). I realised that the exe files in version 1.1-1.8 are the same (afud412.exe) but the exe file in 1.A is different (afud4310.exe).
    My questions are:
    1) How to flash my MB to the version 1.A ?
    2) Is version 1.A really needed for AMD Phenom II x545? I guess yes, because CPU was avaible in July 2009 and the bios 1.A went out in June 2009. I am able to flash it only to version 1.8 (december 2008).
    Thank you for any help!!
    EDIT: After reading this topic: https://forum-en.msi.com/index.php?topic=129204.0 I realised I have the VERSION 1 of this board (I purchased it right after the launch of the MB (November 2007). It means it doesnt support CPU over 95W, but my Phenpom II x545 has only 80W. I still cant update Bios to the 1.A version.
    So my third question is:
    3) Is the Bios update 1.A only for version 2 of this MB?
    Thx for replies!
    Quote from: Jack t.N. on 25-October-09, 17:16:16
    A CMOS Checksum error is normal and expected after a BIOS Flash and/or a CMOS Clear.  The fact that this message appears, shows, that there was actually something programmed to the chip.
    If you haven't done that yet, please clear CMOS with the main A/C power cable removed from your PSU and load "Optimized Defaults" in BIOS Setup.
    The BIOS Version should be shown on the POST Status Screen and there should be a date behind it.  Please check the BIOS Date and write it down:
    Are you absolutely and entirely sure that what you see is "1.1" and not "1.10"?  Because v1.A0 is actually just the hexadecimal notation for v1."10" (one dot ten).  The hexadecimal notation is only used in the BIOS File Ending.  Once flashed, the BIOS will not identify itself in hexadecimal notation but in decimal code (which means you will never see "v1.A0" after the flash but "v1.10" instead.
    Here is a piece of well-meant advice for now and the future:  MSI Live Update should be avoided under all circumstances when it comes to BIOS Updates and/or information retrieval regarding your current BIOS Version.  Why?  Because this tool is stupid and one of there most risky applications for performing a BIOS Flash.  Please uninstall it completely.
    Why do I call it stupid?  I call it stupid because it does not differentiate between hexadecimal notation and decimal notation.  It will show you that "v1.A0" is available.  The it will flash it, if you allow it to do so.  Of course, a v1.A0 Version will always come out as "v1.10" (one dot ten).  When you re-run MSI Live Update it will not recognize that v1.A0=v1.10 and tell you again that there is a newer version available (1.A0, which, again, is the same as v1.10, which was just properly flashed).
    I believe that the update went just fine, that you are currently using v1.A0=v1.10 and that MSI Live Update is actually just creating a pseudo-problem which is currently confusing you.  The pseudo-problem will immediately be out of the world, if you uninstall MSI Live Update and rely on the BIOS ID String as it appears on the POST Status Screen (this includes the date shown there).
    If a BIOS Update should ever be necessary again, please make sure that you won't use MSI Live Update but >>Use the MSI HQ Forum USB flasher<< instead.
    Quote from: Fingon on 25-October-09, 18:03:44
    Thank you for the quick reply!!
    Thats exactly what I have JUST found in this post by Svet: https://forum-en.msi.com/index.php?topic=127672.msg974800#msg974800
    Yes it is 1.10 of course!! I didnt know that 1.10 = 1.A0 ! Thank you for the reply. Then the MSI live update 4 program is dump that he wanted from me another update of Bios.
    So thank you! Problem is solved. 
    Edit: Yes, because of MSI live update I learned how to flash bios via flash disc. :-) But I was still confused by that 1.10 and of course by program saying me I should update again.. :-P
    Quote from: Lostsoul777 on 14-August-09, 05:46:25
    I had the same problem with 1.90 bios, so i updated to 1A, i just want to know why Bios Version says: v.1.10 instead v.1A?
    Quote from: LinuxGuy on 29-December-09, 01:17:45
    My computer does not have a floppy drive.  How do I update the BIOS?  (I tried the online utility 3 times.  It always updates the BIOS "successfully" and when I restart my PC, I have to do either F1 to config or F2 to load setup defaults.  So it looks like it's working, but the online update says that I have versions H.10 and version H.A0 is available (or maybe the other way around).  So either the BIOS is getting updated, but the online tool is not recognizing this or it's not getting updated.  Either way, I would like to manually flash it in DOS.  Is it safe to burn the setup files to CD and boot from CD into DOS?
    That's the same BIOS version... Just the "MSI Live Updater" is not very smart...
    H.A=H.10=17.A=17.10 [A=10, H=17], the last "0" suffix in H.A0 means its official version.
    Quote
    I tried the online utility 3 times.  It always updates the BIOS "successfully" and when I restart my PC, I have to do either F1 to config or F2 to load setup defaults.
    So it looks like it's working, but the online update says that I have versions H.10 and version H.A0 is available (or maybe the other way around).
    So ignore this MSI Live Updater's no sense, and stop flashing your BIOS. You already have the latest version installed.
    The Tool now will detect and shows BIOS versions alias when the MSI BIOS version is known with more than one name.
    So no more flashing and flashing and flashing to the same version because of MSI LiveUpdate suggest again BIOS update...
    Also no more confusion:
    "What's my BIOS version?" -> I flashed my BIOS to 1.A0 [A7520IMS.1A0], but BIOS says its 1.10
    And MSI Live Update also says that i have 1.10 and 1.A0 is available and i should update it. I flashed it again, but its still 1.10?
    What's going on?
    Just run the MSIHQ USB Flash Tool and will show you all that you need to know
    Examples[with real/accurate info]:
    MSI Eclipse:
    BIOS version 1.9:
    BIOS version 1.10:[Tool now shows both BIOS versions alias]
    Report stored respective in MSIHQ_INFO.TXT at user's desktop:
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in ба 30.12.2009 Ј. at  5:30:55,34
    Mainboard:  Eclipse SLI (MS-7520)
    PCB Version:  1.0
    BIOS Version: V1.9
    BIOS Date:  09/22/2009
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in ба 30.12.2009 Ј. at  5:37:25,66
    Mainboard:  Eclipse SLI (MS-7520)
    PCB Version:  1.0
    BIOS Version: V1.A (aka Version: V1.10)
    BIOS Date:  10/27/2009
    More examples =>K9N6SGM-V / K9N6PGM-FI / K9N6PGM-F :
    More examples =>945GCM5-F V2 (FSB 1333) :
    Report stored respective in MSIHQ_INFO.TXT at user's desktop:
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in ба 30.12.2009 Ј. at  5:47:34,35
    Mainboard:  MS-7267
    PCB Version:  4.0
    BIOS Version: VH.9 (aka Version: V17.9)
    BIOS Date:  11/20/2008
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in ба 30.12.2009 Ј. at  5:52:46,26
    Mainboard:  945GCM5-F V2  (MS-7267)
    PCB Version:  4.0
    BIOS Version: VH.A (aka Version: V17.10)
    BIOS Date:  06/02/2009
    More examples =>780GT-E63 [N/A at MSI web yet] :
    For MSI Notebooks such decoding isn't need, examples:
    * Add new feature "Triple BIOS flash Recovery Ready"
    - Updated Mode 1
    - Updated Mode 2
    - Updated Mode 3
    Details:
    The feature include 3 auto prepared BIOS backups for followed purpose:
    * Internal BIOS recovery:
     - In a failure case Tool perform auto flash recovery [3 attempts, check for success after each and stop flashing if successful] before give control to BK_IO2, notice users about results and give control for manual attempts[if need]. [This a case if system isn't lockup/reboot, if bad flash occur]
     - This mode also have own store up to 5 backups[+1, the last saved copy is always backup.bin, if there was older one they become backup1.bin .. till 5]
    * BIOS backup stored as AMIBOOT.ROM [AMI BIOS only] [Auto clean up older if there is any, before take a new backup to avoid recovery confusion]
    * BIOS backup detected and stored for M-Flash style boot/recovery [AMI BIOS only] [Auto clean up older if there is any, before take a new backup to avoid recovery confusion]
    Performing test simulations with random generated BIOS versions[including betas] for M-Flash boot/recovery style, some examples:
    Copy/paste Tool log file:
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in 03.01.2010 г. at  7:00:53,46
    Mainboard:  945GCM5-F V2  (MS-7267)
    PCB Version:  4.0
    BIOS Version: VD.XB2 (aka Version: V13.33B2)
    BIOS Date:  06/02/2009
    Co-respond BIOS backup created  ==> A7267IMS.DX2 
    Where:
    * V13.33B2 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
    * VD.XB2 ==> MSIHQ Tool "True BIOS Ready" detection feature
    * A7267IMS.DX2 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in 03.01.2010 г. at  7:12:23,95
    Mainboard:  945GCM5-F V2  (MS-7267)
    PCB Version:  4.0
    BIOS Version: VK.VB7 (aka Version: V20.31B7)
    BIOS Date:  06/02/2009
    Co-respond BIOS backup created ==> A7267IMS.KV7 
    Where:
    * V20.31B7 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
    * VK.VB7 ==> MSIHQ Tool "True BIOS Ready" detection feature
    * A7267IMS.KV7 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in 03.01.2010 г. at  7:18:34,46
    Mainboard:  945GCM5-F V2  (MS-7267)
    PCB Version:  4.0
    BIOS Version: V3.9
    BIOS Date:  06/02/2009
    Co-respond BIOS backup created ==> A7267IMS.390 
    Where:
    * V3.9 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
    * MSIHQ Tool "True BIOS Ready" detection feature isn't need here, since this BIOS version can be known only with one name.
    * A7267IMS.390 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in 03.01.2010 г. at  7:22:24,04
    Mainboard:  945GCM5-F V2  (MS-7267)
    PCB Version:  4.0
    BIOS Version: V8.1B9
    BIOS Date:  06/02/2009
    Co-respond BIOS backup created ==> A7267IMS.819 
    Where:
    * V8.1B9==> MSIHQ Tool detection [The same as CPU-Z, Everest]
    * MSIHQ Tool "True BIOS Ready" detection feature isn't need here, since this BIOS version can be known only with one name.
    * A7267IMS.819  ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in 03.01.2010 г. at  7:25:38,51
    Mainboard:  945GCM5-F V2  (MS-7267)
    PCB Version:  4.0
    BIOS Version: V4.E (aka Version: V4.14)
    BIOS Date:  06/02/2009
    Co-respond BIOS backup created ==> A7267IMS.4E0 
    Where:
    * V4.14 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
    * V4.E ==> MSIHQ Tool "True BIOS Ready" detection feature
    * A7267IMS.4E0 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in 03.01.2010 г. at  7:28:16,62
    Mainboard:  945GCM5-F V2  (MS-7267)
    PCB Version:  4.0
    BIOS Version: V1.BB1 (aka Version: V1.11B1)
    BIOS Date:  06/02/2009
    Co-respond BIOS backup created ==> A7267IMS.1B1 
    Where:
    * V1.11B1 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
    * V1.BB1 ==> MSIHQ Tool "True BIOS Ready" detection feature
    * A7267IMS.1B1 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in 03.01.2010 г. at  7:31:57,78
    Mainboard:  945GCM5-F V2  (MS-7267)
    PCB Version:  4.0
    BIOS Version: VI.FB5 (aka Version: V18.15B5)
    BIOS Date:  06/02/2009
    Co-respond BIOS backup created ==> A7267IMS.IF5 
    Where:
    * V18.15B5 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
    * VI.FB5 ==> MSIHQ Tool "True BIOS Ready" detection feature
    * A7267IMS.IF5 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in 03.01.2010 г. at  7:36:02,40
    Mainboard:  945GCM5-F V2  (MS-7267)
    PCB Version:  4.0
    BIOS Version: V7.O (aka Version: V7.24)
    BIOS Date:  06/02/2009
    Co-respond BIOS backup created ==> A7267IMS.7O0 
    Where:
    * V7.24 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
    * V7.O ==> MSIHQ Tool "True BIOS Ready" detection feature
    * A7267IMS.7O0 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in 03.01.2010 г. at  7:39:11,84
    Mainboard:  945GCM5-F V2  (MS-7267)
    PCB Version:  4.0
    BIOS Version: VC.8B6 (aka Version: V12.8B6)
    BIOS Date:  06/02/2009
    Co-respond BIOS backup created ==> A7267IMS.C86 
    Where:
    * V12.8B6 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
    * VC.8B6 ==> MSIHQ Tool "True BIOS Ready" detection feature
    * A7267IMS.C86 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in 03.01.2010 г. at  7:49:38,46
    Mainboard:  945GCM5-F V2  (MS-7267)
    PCB Version:  4.0
    BIOS Version: VG.PB6 (aka Version: V16.25B6)
    BIOS Date:  06/02/2009
    Co-respond BIOS backup created ==> A7267IMS.GP6 
    Where:
    * V16.25B6 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
    * VG.PB6 ==> MSIHQ Tool "True BIOS Ready" detection feature
    * A7267IMS.GP6 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in 03.01.2010 г. at  7:53:17,26
    Mainboard:  945GCM5-F V2  (MS-7267)
    PCB Version:  4.0
    BIOS Version: VU.H (aka Version: V30.17)
    BIOS Date:  06/02/2009
    Co-respond BIOS backup created ==> A7267IMS.UH0 
    Where:
    * V30.17 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
    * VU.H ==> MSIHQ Tool "True BIOS Ready" detection feature
    * A7267IMS.UH0 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]

  • Grub-BIOS UUID-base Arch/LXDE fails to boot completly 2/3 of times

    Hi,
    I have a GRUB-BIOS systemd based Arch/LXDE fresh installation (latest 2/2013 image).
    About 2 out of 3 times I boot the system freezes after  displaying that the  /dev/sda2 (my root) is clean.
    Yet, about 1 out of 3 trials, boot completes without problems.
    In either case I don't add any parameters, and just wait for Grub's timeout.
    The same happen with the Linux fallback as well.
    This is a single drive (sda) netbook installation.
    From the journalctl (see below) it seems to me that the alleged stuck boot almost completed!
    I'd appreciate any help!
    Below please find:
    1. Output of journalctl relating to the last two boots: the 17:33 boot got stuck, whereas I'm writing now after successfully rebooting at 17:36
    2. Copy of my fstab
    3. Copy of grub.cfg
    Thanks a lot!
    ----------copy of journalctl of last 2 boots (sorry, it's long)--------------------
    -- Logs begin at Sat 2013-02-16 11:47:04 IST, end at Sat 2013-02-23 17:36:36 IST. --
    [1;39m-- Reboot --[0m
    Feb 23 17:33:34 miki_netbook systemd-journal[119]: Allowing runtime journal files to grow to 100.3M.
    Feb 23 17:33:34 miki_netbook kernel: Initializing cgroup subsys cpuset
    Feb 23 17:33:34 miki_netbook kernel: Initializing cgroup subsys cpu
    Feb 23 17:33:34 miki_netbook kernel: Linux version 3.7.9-1-ARCH (nobody@foutrelis) (gcc version 4.7.2 (GCC) ) #1 SMP PREEMPT Mon Feb 18 02:27:20 EET 2013
    Feb 23 17:33:34 miki_netbook kernel: Atom PSE erratum detected, BIOS microcode update recommended
    Feb 23 17:33:34 miki_netbook kernel: Disabled fast string operations
    Feb 23 17:33:34 miki_netbook kernel: e820: BIOS-provided physical RAM map:
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x0000000000100000-0x000000007f375fff] usable
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x000000007f376000-0x000000007f3befff] reserved
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x000000007f3bf000-0x000000007f46cfff] ACPI data
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x000000007f46d000-0x000000007f4befff] ACPI NVS
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x000000007f4bf000-0x000000007f4fffff] ACPI data
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x000000007f500000-0x000000007fffffff] reserved
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x00000000fed14000-0x00000000fed19fff] reserved
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x00000000fff00000-0x00000000ffffffff] reserved
    Feb 23 17:33:34 miki_netbook kernel: Notice: NX (Execute Disable) protection missing in CPU!
    Feb 23 17:33:34 miki_netbook kernel: SMBIOS 2.4 present.
    Feb 23 17:33:34 miki_netbook kernel: DMI: Quanta UW1/Base Board Product Name, BIOS Q3A51 2/05/2009
    Feb 23 17:33:34 miki_netbook kernel: e820: update [mem 0x00000000-0x0000ffff] usable ==> reserved
    Feb 23 17:33:34 miki_netbook kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
    Feb 23 17:33:34 miki_netbook kernel: e820: last_pfn = 0x7f376 max_arch_pfn = 0x100000
    Feb 23 17:33:34 miki_netbook kernel: MTRR default type: uncachable
    Feb 23 17:33:34 miki_netbook kernel: MTRR fixed ranges enabled:
    Feb 23 17:33:34 miki_netbook kernel: 00000-9FFFF write-back
    Feb 23 17:33:34 miki_netbook kernel: A0000-BFFFF uncachable
    Feb 23 17:33:34 miki_netbook kernel: C0000-C7FFF write-protect
    Feb 23 17:33:34 miki_netbook kernel: C8000-EFFFF uncachable
    Feb 23 17:33:34 miki_netbook kernel: F0000-FFFFF write-protect
    Feb 23 17:33:34 miki_netbook kernel: MTRR variable ranges enabled:
    Feb 23 17:33:34 miki_netbook kernel: 0 base 0FFFE0000 mask 0FFFE0000 write-protect
    Feb 23 17:33:34 miki_netbook kernel: 1 base 0FFFC0000 mask 0FFFE0000 uncachable
    Feb 23 17:33:34 miki_netbook kernel: 2 base 000000000 mask 0C0000000 write-back
    Feb 23 17:33:34 miki_netbook kernel: 3 base 040000000 mask 0C0000000 write-back
    Feb 23 17:33:34 miki_netbook kernel: 4 base 07F800000 mask 0FF800000 uncachable
    Feb 23 17:33:34 miki_netbook kernel: 5 base 07F600000 mask 0FFE00000 uncachable
    Feb 23 17:33:34 miki_netbook kernel: 6 base 07F500000 mask 0FFF00000 uncachable
    Feb 23 17:33:34 miki_netbook kernel: 7 base 000000000 mask 0FFFE0000 uncachable
    Feb 23 17:33:34 miki_netbook kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    Feb 23 17:33:34 miki_netbook kernel: initial memory mapped: [mem 0x00000000-0x01bfffff]
    Feb 23 17:33:34 miki_netbook kernel: Base memory trampoline at [c009b000] 9b000 size 16384
    Feb 23 17:33:34 miki_netbook kernel: init_memory_mapping: [mem 0x00000000-0x377fdfff]
    Feb 23 17:33:34 miki_netbook kernel: [mem 0x00000000-0x377fdfff] page 4k
    Feb 23 17:33:34 miki_netbook kernel: kernel direct mapping tables up to 0x377fdfff @ [mem 0x01b1f000-0x01bfffff]
    Feb 23 17:33:34 miki_netbook kernel: RAMDISK: [mem 0x37a72000-0x37d30fff]
    Feb 23 17:33:34 miki_netbook kernel: Allocated new RAMDISK: [mem 0x3753f000-0x377fd99b]
    Feb 23 17:33:34 miki_netbook kernel: Move RAMDISK from [mem 0x37a72000-0x37d3099b] to [mem 0x3753f000-0x377fd99b]
    Feb 23 17:33:34 miki_netbook kernel: ACPI: RSDP 000fe020 00024 (v02 haier)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: XSDT 7f4fe120 00064 (v01 haier computer 00000001 01000013)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: FACP 7f4fc000 000F4 (v04 haier computer 00000001 MSFT 01000013)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: DSDT 7f4f3000 04DDE (v01 haier computer 00000001 MSFT 01000013)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: FACS 7f488000 00040
    Feb 23 17:33:34 miki_netbook kernel: ACPI: SSDT 7f4fd000 004C4 (v02 PmRef CpuPm 00003000 INTL 20051117)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: HPET 7f4fb000 00038 (v01 haier computer 00000001 MSFT 01000013)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: APIC 7f4fa000 00068 (v02 haier computer 00000001 MSFT 01000013)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: MCFG 7f4f9000 0003C (v01 haier computer 00000001 MSFT 01000013)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: ASF! 7f4f8000 000A5 (v32 haier computer 00000001 MSFT 01000013)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: SLIC 7f4f2000 00180 (v01 haier computer 00000001 MSFT 01000013)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: BOOT 7f4f1000 00028 (v01 haier computer 00000001 MSFT 01000013)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Local APIC address 0xfee00000
    Feb 23 17:33:34 miki_netbook kernel: 1147MB HIGHMEM available.
    Feb 23 17:33:34 miki_netbook kernel: 887MB LOWMEM available.
    Feb 23 17:33:34 miki_netbook kernel: mapped low ram: 0 - 377fe000
    Feb 23 17:33:34 miki_netbook kernel: low ram: 0 - 377fe000
    Feb 23 17:33:34 miki_netbook kernel: Zone ranges:
    Feb 23 17:33:34 miki_netbook kernel: DMA [mem 0x00010000-0x00ffffff]
    Feb 23 17:33:34 miki_netbook kernel: Normal [mem 0x01000000-0x377fdfff]
    Feb 23 17:33:34 miki_netbook kernel: HighMem [mem 0x377fe000-0x7f375fff]
    Feb 23 17:33:34 miki_netbook kernel: Movable zone start for each node
    Feb 23 17:33:34 miki_netbook kernel: Early memory node ranges
    Feb 23 17:33:34 miki_netbook kernel: node 0: [mem 0x00010000-0x0009efff]
    Feb 23 17:33:34 miki_netbook kernel: node 0: [mem 0x00100000-0x7f375fff]
    Feb 23 17:33:34 miki_netbook kernel: On node 0 totalpages: 520965
    Feb 23 17:33:34 miki_netbook kernel: free_area_init_node: node 0, pgdat c158d880, node_mem_map f6556200
    Feb 23 17:33:34 miki_netbook kernel: DMA zone: 32 pages used for memmap
    Feb 23 17:33:34 miki_netbook kernel: DMA zone: 0 pages reserved
    Feb 23 17:33:34 miki_netbook kernel: DMA zone: 3951 pages, LIFO batch:0
    Feb 23 17:33:34 miki_netbook kernel: Normal zone: 1744 pages used for memmap
    Feb 23 17:33:34 miki_netbook kernel: Normal zone: 221486 pages, LIFO batch:31
    Feb 23 17:33:34 miki_netbook kernel: HighMem zone: 2295 pages used for memmap
    Feb 23 17:33:34 miki_netbook kernel: HighMem zone: 291457 pages, LIFO batch:31
    Feb 23 17:33:34 miki_netbook kernel: Using APIC driver default
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PM-Timer IO Port: 0x408
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Local APIC address 0xfee00000
    Feb 23 17:33:34 miki_netbook kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
    Feb 23 17:33:34 miki_netbook kernel: ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
    Feb 23 17:33:34 miki_netbook kernel: ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
    Feb 23 17:33:34 miki_netbook kernel: IOAPIC[0]: apic_id 4, version 32, address 0xfec00000, GSI 0-23
    Feb 23 17:33:34 miki_netbook kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: IRQ0 used by override.
    Feb 23 17:33:34 miki_netbook kernel: ACPI: IRQ2 used by override.
    Feb 23 17:33:34 miki_netbook kernel: ACPI: IRQ9 used by override.
    Feb 23 17:33:34 miki_netbook kernel: Using ACPI (MADT) for SMP configuration information
    Feb 23 17:33:34 miki_netbook kernel: ACPI: HPET id: 0x8086a201 base: 0xfed00000
    Feb 23 17:33:34 miki_netbook kernel: smpboot: Allowing 2 CPUs, 0 hotplug CPUs
    Feb 23 17:33:34 miki_netbook kernel: nr_irqs_gsi: 40
    Feb 23 17:33:34 miki_netbook kernel: PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
    Feb 23 17:33:34 miki_netbook kernel: PM: Registered nosave memory: 00000000000a0000 - 00000000000e0000
    Feb 23 17:33:34 miki_netbook kernel: PM: Registered nosave memory: 00000000000e0000 - 0000000000100000
    Feb 23 17:33:34 miki_netbook kernel: e820: [mem 0x80000000-0xdfffffff] available for PCI devices
    Feb 23 17:33:34 miki_netbook kernel: Booting paravirtualized kernel on bare hardware
    Feb 23 17:33:34 miki_netbook kernel: setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:2 nr_node_ids:1
    Feb 23 17:33:34 miki_netbook kernel: PERCPU: Embedded 13 pages/cpu @f6530000 s32448 r0 d20800 u53248
    Feb 23 17:33:34 miki_netbook kernel: pcpu-alloc: s32448 r0 d20800 u53248 alloc=13*4096
    Feb 23 17:33:34 miki_netbook kernel: pcpu-alloc: [0] 0 [0] 1
    Feb 23 17:33:34 miki_netbook kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 516894
    Feb 23 17:33:34 miki_netbook kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=7cbfd7ba-38ed-40b5-b5b6-041c1c0f2677 ro quiet
    Feb 23 17:33:34 miki_netbook kernel: PID hash table entries: 4096 (order: 2, 16384 bytes)
    Feb 23 17:33:34 miki_netbook kernel: Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
    Feb 23 17:33:34 miki_netbook kernel: Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
    Feb 23 17:33:34 miki_netbook kernel: __ex_table already sorted, skipping sort
    Feb 23 17:33:34 miki_netbook kernel: Initializing CPU#0
    Feb 23 17:33:34 miki_netbook kernel: allocated 4168496 bytes of page_cgroup
    Feb 23 17:33:34 miki_netbook kernel: please try 'cgroup_disable=memory' option if you don't want memory cgroups
    Feb 23 17:33:34 miki_netbook kernel: Initializing HighMem for node 0 (000377fe:0007f376)
    Feb 23 17:33:34 miki_netbook kernel: Memory: 2051608k/2084312k available (4099k kernel code, 32252k reserved, 1644k data, 556k init, 1175008k highmem)
    Feb 23 17:33:34 miki_netbook kernel: [379B blob data]
    Feb 23 17:33:34 miki_netbook kernel: Checking if this processor honours the WP bit even in supervisor mode...Ok.
    Feb 23 17:33:34 miki_netbook kernel: SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
    Feb 23 17:33:34 miki_netbook kernel: Preemptible hierarchical RCU implementation.
    Feb 23 17:33:34 miki_netbook kernel: RCU dyntick-idle grace-period acceleration is enabled.
    Feb 23 17:33:34 miki_netbook kernel: Dump stacks of tasks blocking RCU-preempt GP.
    Feb 23 17:33:34 miki_netbook kernel: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=2.
    Feb 23 17:33:34 miki_netbook kernel: NR_IRQS:2304 nr_irqs:512 16
    Feb 23 17:33:34 miki_netbook kernel: CPU 0 irqstacks, hard=f5c08000 soft=f5c0a000
    Feb 23 17:33:34 miki_netbook kernel: Console: colour dummy device 80x25
    Feb 23 17:33:34 miki_netbook kernel: console [tty0] enabled
    Feb 23 17:33:34 miki_netbook kernel: hpet clockevent registered
    Feb 23 17:33:34 miki_netbook kernel: tsc: Fast TSC calibration failed
    Feb 23 17:33:34 miki_netbook kernel: tsc: PIT calibration matches HPET. 1 loops
    Feb 23 17:33:34 miki_netbook kernel: tsc: Detected 1595.989 MHz processor
    Feb 23 17:33:34 miki_netbook kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 3193.97 BogoMIPS (lpj=5319963)
    Feb 23 17:33:34 miki_netbook kernel: pid_max: default: 32768 minimum: 301
    Feb 23 17:33:34 miki_netbook kernel: Security Framework initialized
    Feb 23 17:33:34 miki_netbook kernel: AppArmor: AppArmor disabled by boot time parameter
    Feb 23 17:33:34 miki_netbook kernel: Mount-cache hash table entries: 512
    Feb 23 17:33:34 miki_netbook kernel: Initializing cgroup subsys cpuacct
    Feb 23 17:33:34 miki_netbook kernel: Initializing cgroup subsys memory
    Feb 23 17:33:34 miki_netbook kernel: Initializing cgroup subsys devices
    Feb 23 17:33:34 miki_netbook kernel: Initializing cgroup subsys freezer
    Feb 23 17:33:34 miki_netbook kernel: Initializing cgroup subsys net_cls
    Feb 23 17:33:34 miki_netbook kernel: Initializing cgroup subsys blkio
    Feb 23 17:33:34 miki_netbook kernel: Atom PSE erratum detected, BIOS microcode update recommended
    Feb 23 17:33:34 miki_netbook kernel: Disabled fast string operations
    Feb 23 17:33:34 miki_netbook kernel: CPU: Physical Processor ID: 0
    Feb 23 17:33:34 miki_netbook kernel: CPU: Processor Core ID: 0
    Feb 23 17:33:34 miki_netbook kernel: mce: CPU supports 5 MCE banks
    Feb 23 17:33:34 miki_netbook kernel: CPU0: Thermal monitoring enabled (TM2)
    Feb 23 17:33:34 miki_netbook kernel: process: using mwait in idle threads
    Feb 23 17:33:34 miki_netbook kernel: [113B blob data]
    Feb 23 17:33:34 miki_netbook kernel: Freeing SMP alternatives: 16k freed
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Core revision 20120913
    Feb 23 17:33:34 miki_netbook kernel: ftrace: allocating 17730 entries in 35 pages
    Feb 23 17:33:34 miki_netbook kernel: Enabling APIC mode: Flat. Using 1 I/O APICs
    Feb 23 17:33:34 miki_netbook kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    Feb 23 17:33:34 miki_netbook kernel: smpboot: CPU0: Intel(R) Atom(TM) CPU N270 @ 1.60GHz (fam: 06, model: 1c, stepping: 02)
    Feb 23 17:33:34 miki_netbook kernel: Performance Events: PEBS fmt0+, LBR disabled due to erratumAtom events, Intel PMU driver.
    Feb 23 17:33:34 miki_netbook kernel: ... version: 3
    Feb 23 17:33:34 miki_netbook kernel: ... bit width: 40
    Feb 23 17:33:34 miki_netbook kernel: ... generic registers: 2
    Feb 23 17:33:34 miki_netbook kernel: ... value mask: 000000ffffffffff
    Feb 23 17:33:34 miki_netbook kernel: ... max period: 000000007fffffff
    Feb 23 17:33:34 miki_netbook kernel: ... fixed-purpose events: 3
    Feb 23 17:33:34 miki_netbook kernel: ... event mask: 0000000700000003
    Feb 23 17:33:34 miki_netbook kernel: CPU 1 irqstacks, hard=f5cc0000 soft=f5cc2000
    Feb 23 17:33:34 miki_netbook kernel: smpboot: Booting Node 0, Processors #1 OK
    Feb 23 17:33:34 miki_netbook kernel: Initializing CPU#1
    Feb 23 17:33:34 miki_netbook kernel: Atom PSE erratum detected, BIOS microcode update recommended
    Feb 23 17:33:34 miki_netbook kernel: Disabled fast string operations
    Feb 23 17:33:34 miki_netbook kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
    Feb 23 17:33:34 miki_netbook kernel: Brought up 2 CPUs
    Feb 23 17:33:34 miki_netbook kernel: smpboot: Total of 2 processors activated (6386.95 BogoMIPS)
    Feb 23 17:33:34 miki_netbook kernel: devtmpfs: initialized
    Feb 23 17:33:34 miki_netbook kernel: PM: Registering ACPI NVS region [mem 0x7f46d000-0x7f4befff] (335872 bytes)
    Feb 23 17:33:34 miki_netbook kernel: RTC time: 15:33:30, date: 02/23/13
    Feb 23 17:33:34 miki_netbook kernel: NET: Registered protocol family 16
    Feb 23 17:33:34 miki_netbook kernel: ACPI: bus type pci registered
    Feb 23 17:33:34 miki_netbook kernel: PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
    Feb 23 17:33:34 miki_netbook kernel: PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820
    Feb 23 17:33:34 miki_netbook kernel: PCI: Using MMCONFIG for extended config space
    Feb 23 17:33:34 miki_netbook kernel: PCI: Using configuration type 1 for base access
    Feb 23 17:33:34 miki_netbook kernel: bio: create slab <bio-0> at 0
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Added _OSI(Module Device)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Added _OSI(Processor Device)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Added _OSI(Processor Aggregator Device)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: EC: Look up EC in DSDT
    Feb 23 17:33:34 miki_netbook kernel: [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
    Feb 23 17:33:34 miki_netbook kernel: ACPI: SSDT 7f380c90 00239 (v02 PmRef Cpu0Ist 00003000 INTL 20051117)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Dynamic OEM Table Load:
    Feb 23 17:33:34 miki_netbook kernel: ACPI: SSDT (null) 00239 (v02 PmRef Cpu0Ist 00003000 INTL 20051117)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: SSDT 7f37fe10 001C7 (v02 PmRef Cpu0Cst 00003001 INTL 20051117)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Dynamic OEM Table Load:
    Feb 23 17:33:34 miki_netbook kernel: ACPI: SSDT (null) 001C7 (v02 PmRef Cpu0Cst 00003001 INTL 20051117)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: SSDT 7f380f10 000D0 (v02 PmRef Cpu1Ist 00003000 INTL 20051117)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Dynamic OEM Table Load:
    Feb 23 17:33:34 miki_netbook kernel: ACPI: SSDT (null) 000D0 (v02 PmRef Cpu1Ist 00003000 INTL 20051117)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: SSDT 7f37ef10 00083 (v02 PmRef Cpu1Cst 00003000 INTL 20051117)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Dynamic OEM Table Load:
    Feb 23 17:33:34 miki_netbook kernel: ACPI: SSDT (null) 00083 (v02 PmRef Cpu1Cst 00003000 INTL 20051117)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Interpreter enabled
    Feb 23 17:33:34 miki_netbook kernel: ACPI: (supports S0 S3 S4 S5)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Using IOAPIC for interrupt routing
    Feb 23 17:33:34 miki_netbook kernel: ACPI: EC: GPE = 0x17, I/O: command/status = 0x66, data = 0x62
    Feb 23 17:33:34 miki_netbook kernel: ACPI: No dock devices found.
    Feb 23 17:33:34 miki_netbook kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
    Feb 23 17:33:34 miki_netbook kernel: ACPI Error: [CAPB] Namespace lookup failure, AE_ALREADY_EXISTS (20120913/dsfield-211)
    Feb 23 17:33:34 miki_netbook kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0._OSC] (Node f5c26dc8), AE_ALREADY_EXISTS (20120913/psparse-536)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Marking method _OSC as Serialized because of AE_ALREADY_EXISTS error
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
    Feb 23 17:33:34 miki_netbook kernel: PCI host bridge to bus 0000:00
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:00: root bus resource [bus 00-ff]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:00: root bus resource [mem 0x80000000-0xfebfffff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:00.0: [8086:27ac] type 00 class 0x060000
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:02.0: [8086:27ae] type 00 class 0x030000
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:02.0: reg 10: [mem 0x94280000-0x942fffff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:02.0: reg 14: [io 0x40c0-0x40c7]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:02.0: reg 18: [mem 0x80000000-0x8fffffff pref]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:02.0: reg 1c: [mem 0x94300000-0x9433ffff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:02.1: [8086:27a6] type 00 class 0x038000
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:02.1: reg 10: [mem 0x94200000-0x9427ffff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1b.0: [8086:27d8] type 00 class 0x040300
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1b.0: reg 10: [mem 0x94340000-0x94343fff 64bit]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.0: [8086:27d0] type 01 class 0x060400
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.1: [8086:27d2] type 01 class 0x060400
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1d.0: [8086:27c8] type 00 class 0x0c0300
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1d.0: reg 20: [io 0x4080-0x409f]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1d.1: [8086:27c9] type 00 class 0x0c0300
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1d.1: reg 20: [io 0x4060-0x407f]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1d.2: [8086:27ca] type 00 class 0x0c0300
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1d.2: reg 20: [io 0x4040-0x405f]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1d.3: [8086:27cb] type 00 class 0x0c0300
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1d.3: reg 20: [io 0x4020-0x403f]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1d.7: [8086:27cc] type 00 class 0x0c0320
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1d.7: reg 10: [mem 0x94344400-0x943447ff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1e.0: [8086:2448] type 01 class 0x060401
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1f.0: [8086:27b9] type 00 class 0x060100
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1f.0: ICH7 LPC Generic IO decode 4 PIO at 0068 (mask 0007)
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1f.2: [8086:27c4] type 00 class 0x010180
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1f.2: reg 10: [io 0x0000-0x0007]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1f.2: reg 14: [io 0x0000-0x0003]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1f.2: reg 18: [io 0x0000-0x0007]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1f.2: reg 1c: [io 0x0000-0x0003]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1f.2: reg 20: [io 0x40a0-0x40af]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1f.2: PME# supported from D3hot
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1f.3: [8086:27da] type 00 class 0x0c0500
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1f.3: reg 20: [io 0x4000-0x401f]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.0: PCI bridge to [bus 01]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.0: bridge window [io 0x3000-0x3fff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.0: bridge window [mem 0x93100000-0x941fffff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.0: bridge window [mem 0x90000000-0x90ffffff 64bit pref]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:02:00.0: [10ec:8136] type 00 class 0x020000
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:02:00.0: reg 10: [io 0x1000-0x10ff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:02:00.0: reg 18: [mem 0x91010000-0x91010fff 64bit pref]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:02:00.0: reg 20: [mem 0x91000000-0x9100ffff 64bit pref]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:02:00.0: reg 30: [mem 0xffff0000-0xffffffff pref]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:02:00.0: supports D1 D2
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.1: PCI bridge to [bus 02]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.1: bridge window [io 0x1000-0x2fff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.1: bridge window [mem 0x92100000-0x930fffff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.1: bridge window [mem 0x91000000-0x920fffff 64bit pref]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1e.0: PCI bridge to [bus 03] (subtractive decode)
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1e.0: bridge window [io 0x0000-0x0cf7] (subtractive decode)
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1e.0: bridge window [io 0x0d00-0xffff] (subtractive decode)
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1e.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1e.0: bridge window [mem 0x80000000-0xfebfffff] (subtractive decode)
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:00: on NUMA node 0
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P32_._PRT]
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP1._PRT]
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP2._PRT]
    Feb 23 17:33:34 miki_netbook kernel: ACPI Error: [CAPB] Namespace lookup failure, AE_ALREADY_EXISTS (20120913/dsfield-211)
    Feb 23 17:33:34 miki_netbook kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0._OSC] (Node f5c26dc8), AE_ALREADY_EXISTS (20120913/psparse-536)
    Feb 23 17:33:34 miki_netbook kernel: pci0000:00: ACPI _OSC support notification failed, disabling PCIe ASPM
    Feb 23 17:33:34 miki_netbook kernel: pci0000:00: Unable to request _OSC control (_OSC support mask: 0x08)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 9 10 *11 12)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 9 10 *11 12)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 9 10 *11 12)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 9 10 *11 12)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 9 10 11 12) *0, disabled.
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 9 10 11 12) *0, disabled.
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 7 9 10 11 12) *0, disabled.
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 7 9 10 11 12) *0, disabled.
    Feb 23 17:33:34 miki_netbook kernel: vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
    Feb 23 17:33:34 miki_netbook kernel: vgaarb: loaded
    Feb 23 17:33:34 miki_netbook kernel: vgaarb: bridge control possible 0000:00:02.0
    Feb 23 17:33:34 miki_netbook kernel: PCI: Using ACPI for IRQ routing
    Feb 23 17:33:34 miki_netbook kernel: PCI: pci_cache_line_size set to 64 bytes
    Feb 23 17:33:34 miki_netbook kernel: e820: reserve RAM buffer [mem 0x0009fc00-0x0009ffff]
    Feb 23 17:33:34 miki_netbook kernel: e820: reserve RAM buffer [mem 0x7f376000-0x7fffffff]
    Feb 23 17:33:34 miki_netbook kernel: NetLabel: Initializing
    Feb 23 17:33:34 miki_netbook kernel: NetLabel: domain hash size = 128
    Feb 23 17:33:34 miki_netbook kernel: NetLabel: protocols = UNLABELED CIPSOv4
    Feb 23 17:33:34 miki_netbook kernel: NetLabel: unlabeled traffic allowed by default
    Feb 23 17:33:34 miki_netbook kernel: HPET: 3 timers in total, 0 timers will be used for per-cpu timer
    Feb 23 17:33:34 miki_netbook kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
    Feb 23 17:33:34 miki_netbook kernel: hpet0: 3 comparators, 64-bit 14.318180 MHz counter
    Feb 23 17:33:34 miki_netbook kernel: Switching to clocksource hpet
    Feb 23 17:33:34 miki_netbook kernel: pnp: PnP ACPI init
    Feb 23 17:33:34 miki_netbook kernel: ACPI: bus type pnp registered
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [bus 00-ff]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [io 0x0000-0x0cf7 window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [io 0x0cf8-0x0cff]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [io 0x0d00-0xffff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000a0000-0x000bffff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000c0000-0x000c3fff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000c4000-0x000c7fff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000c8000-0x000cbfff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000cc000-0x000cffff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000d0000-0x000d3fff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000d4000-0x000d7fff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000d8000-0x000dbfff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000dc000-0x000dffff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000e0000-0x000e3fff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000e4000-0x000e7fff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000e8000-0x000ebfff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000ec000-0x000effff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000f0000-0x000fffff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x80000000-0xfebfffff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: Plug and Play ACPI device, IDs PNP0a08 PNP0a03 (active)
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x002e-0x002f]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0068-0x006f]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0200-0x020f]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0061]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0070]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0080]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0092]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x00b2-0x00b3]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0063]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0065]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0067]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0600-0x060f]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0610]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0800-0x080f]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0400-0x047f]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0500-0x053f]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [mem 0xe0000000-0xefffffff]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [mem 0xfed1c000-0xfed1ffff]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [mem 0xfed14000-0xfed17fff]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [mem 0xfed18000-0xfed18fff]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [mem 0xfed19000-0xfed19fff]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [mem 0xfec00000-0xfec00fff]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [mem 0xfee00000-0xfee00fff]
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [io 0x0200-0x020f] has been reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [io 0x0600-0x060f] has been reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [io 0x0610] has been reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [io 0x0800-0x080f] has been reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [io 0x0400-0x047f] has been reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [io 0x0500-0x053f] has been reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [mem 0xe0000000-0xefffffff] has been reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [mem 0xfed1c000-0xfed1ffff] has been reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [mem 0xfed14000-0xfed17fff] has been reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [mem 0xfed18000-0xfed18fff] has been reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [mem 0xfed19000-0xfed19fff] has been reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [mem 0xfec00000-0xfec00fff] could not be reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [mem 0xfee00000-0xfee00fff] has been reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:02: [io 0x0000-0x001f]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:02: [io 0x0081-0x0091]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:02: [io 0x0093-0x009f]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:02: [io 0x00c0-0x00df]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:02: [dma 4]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0200 (active)
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:03: [io 0x0070-0x0077]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active)
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:04: [irq 0 disabled]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:04: [irq 8]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:04: [mem 0xfed00000-0xfed003ff]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:04: Plug and Play ACPI device, IDs PNP0103 (active)
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:05: [io 0x00f0]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:05: [irq 13]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:05: Plug and Play ACPI device, IDs PNP0c04 (active)
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:06: [mem 0xff800000-0xffffffff]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:06: Plug and Play ACPI device, IDs INT0800 (active)
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:07: [io 0x0060]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:07: [io 0x0064]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:07: [irq 1]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:07: Plug and Play ACPI device, IDs PNP0303 (active)
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:08: [irq 12]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:08: Plug and Play ACPI device, IDs SYN102c SYN1000 SYN0002 PNP0f13 (active)
    Feb 23 17:33:34 miki_netbook kernel: pnp: PnP ACPI: found 9 devices
    Feb 23 17:33:34 miki_netbook kernel: ACPI: ACPI bus type pnp unregistered
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:02:00.0: no compatible bridge window for [mem 0xffff0000-0xffffffff pref]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.0: PCI bridge to [bus 01]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.0: bridge window [io 0x3000-0x3fff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.0: bridge window [mem 0x93100000-0x941fffff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.0: bridge window [mem 0x90000000-0x90ffffff 64bit pref]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:02:00.0: BAR 6: assigned [mem 0x91020000-0x9102ffff pref]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.1: PCI bridge to [bus 02]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.1: bridge window [io 0x1000-0x2fff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.1: bridge window [mem 0x92100000-0x930fffff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.1: bridge window [mem 0x91000000-0x920fffff 64bit pref]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1e.0: PCI bridge to [bus 03]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1e.0: setting latency timer to 64
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:00: resource 7 [mem 0x80000000-0xfebfffff]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:01: resource 0 [io 0x3000-0x3fff]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:01: resource 1 [mem 0x93100000-0x941fffff]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:01: resource 2 [mem 0x90000000-0x90ffffff 64bit pref]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:02: resource 0 [io 0x1000-0x2fff]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:02: resource 1 [mem 0x92100000-0x930fffff]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:02: resource 2 [mem 0x91000000-0x920fffff 64bit pref]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:03: resource 4 [io 0x0000-0x0cf7]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:03: resource 5 [io 0x0d00-0xffff]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:03: resource 6 [mem 0x000a0000-0x000bffff]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:03: resource 7 [mem 0x80000000-0xfebfffff]
    Feb 23 17:33:34 miki_netbook kernel: NET: Registered protocol family 2
    Feb 23 17:33:34 miki_netbook kernel: TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
    Feb 23 17:33:34 miki_netbook kernel: TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
    Feb 23 17:33:34 miki_netbook kernel: TCP: Hash tables configured (established 131072 bind 65536)
    Feb 23 17:33:34 miki_netbook kernel: TCP: reno registered
    Feb 23 17:33:34 miki_netbook kernel: UDP hash table entries: 512 (order: 2, 16384 bytes)
    Feb 23 17:33:34 miki_netbook kernel: UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
    Feb 23 17:33:34 miki_netbook kernel: NET: Registered protocol family 1
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:02.0: Boot video device
    Feb 23 17:33:34 miki_netbook kernel: PCI: CLS 0 bytes, default 64
    Feb 23 17:33:34 miki_netbook kernel: Unpacking initramfs...
    Feb 23 17:33:34 miki_netbook kernel: Freeing initrd memory: 2812k freed
    Feb 23 17:33:34 miki_netbook kernel: Simple Boot Flag value 0x5 read from CMOS RAM was invalid
    Feb 23 17:33:34 miki_netbook kernel: Simple Boot Flag at 0x44 set to 0x1
    Feb 23 17:33:34 miki_netbook kernel: apm: BIOS not found.
    Feb 23 17:33:34 miki_netbook kernel: audit: initializing netlink socket (disabled)
    Feb 23 17:33:34 miki_netbook kernel: type=2000 audit(1361633610.386:1): initialized
    Feb 23 17:33:34 miki_netbook kernel: bounce pool size: 64 pages
    Feb 23 17:33:34 miki_netbook kernel: HugeTLB registered 4 MB page size, pre-allocated 0 pages
    Feb 23 17:33:34 miki_netbook kernel: VFS: Disk quotas dquot_6.5.2
    Feb 23 17:33:34 miki_netbook kernel: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
    Feb 23 17:33:34 miki_netbook kernel: msgmni has been set to 1717
    Feb 23 17:33:34 miki_netbook kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
    Feb 23 17:33:34 miki_netbook kernel: io scheduler noop registered
    Feb 23 17:33:34 miki_netbook kernel: io scheduler deadline registered
    Feb 23 17:33:34 miki_netbook kernel: io scheduler cfq registered (default)
    Feb 23 17:33:34 miki_netbook kernel: pcieport 0000:00:1c.0: irq 40 for MSI/MSI-X
    Feb 23 17:33:34 miki_netbook kernel: pcieport 0000:00:1c.1: irq 41 for MSI/MSI-X
    Feb 23 17:33:34 miki_netbook kernel: vesafb: mode is 640x480x32, linelength=2560, pages=0
    Feb 23 17:33:34 miki_netbook kernel: vesafb: scrolling: redraw
    Feb 23 17:33:34 miki_netbook kernel: vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
    Feb 23 17:33:34 miki_netbook kernel: vesafb: framebuffer at 0x80000000, mapped to 0xf8080000, using 1216k, total 1216k
    Feb 23 17:33:34 miki_netbook kernel: Console: switching to colour frame buffer device 80x30
    Feb 23 17:33:34 miki_netbook kernel: fb0: VESA VGA frame buffer device
    Feb 23 17:33:34 miki_netbook kernel: intel_idle: MWAIT substates: 0x20220
    Feb 23 17:33:34 miki_netbook kernel: intel_idle: v0.4 model 0x1C
    Feb 23 17:33:34 miki_netbook kernel: intel_idle: lapic_timer_reliable_states 0x2
    Feb 23 17:33:34 miki_netbook kernel: tsc: Marking TSC unstable due to TSC halts in idle states deeper than C2
    Feb 23 17:33:34 miki_netbook kernel: GHES: HEST is not enabled!
    Feb 23 17:33:34 miki_netbook kernel: isapnp: Scanning for PnP cards...
    Feb 23 17:33:34 miki_netbook kernel: isapnp: No Plug & Play device found
    Feb 23 17:33:34 miki_netbook kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    Feb 23 17:33:34 miki_netbook kernel: i8042: PNP: PS/2 Controller [PNP0303:KBC,PNP0f13:MOUE] at 0x60,0x64 irq 1,12
    Feb 23 17:33:34 miki_netbook kernel: i8042: Warning: Keylock active
    Feb 23 17:33:34 miki_netbook kernel: i8042: Detected active multiplexing controller, rev 1.1
    Feb 23 17:33:34 miki_netbook kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
    Feb 23 17:33:34 miki_netbook kernel: serio: i8042 AUX0 port at 0x60,0x64 irq 12
    Feb 23 17:33:34 miki_netbook kernel: serio: i8042 AUX1 port at 0x60,0x64 irq 12
    Feb 23 17:33:34 miki_netbook kernel: serio: i8042 AUX2 port at 0x60,0x64 irq 12
    Feb 23 17:33:34 miki_netbook kernel: serio: i8042 AUX3 port at 0x60,0x64 irq 12
    Feb 23 17:33:34 miki_netbook kernel: mousedev: PS/2 mouse device common for all mice
    Feb 23 17:33:34 miki_netbook kernel: rtc_cmos 00:03: RTC can wake from S4
    Feb 23 17:33:34 miki_netbook kernel: rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
    Feb 23 17:33:34 miki_netbook kernel: rtc0: alarms up to one month, 242 bytes nvram, hpet irqs
    Feb 23 17:33:34 miki_netbook kernel: cpuidle: using governor ladder
    Feb 23 17:33:34 miki_netbook kernel: cpuidle: using governor menu
    Feb 23 17:33:34 miki_netbook kernel: EFI Variables Facility v0.08 2004-May-17
    Feb 23 17:33:34 miki_netbook kernel: drop_monitor: Initializing network drop monitor service
    Feb 23 17:33:34 miki_netbook kernel: TCP: cubic registered
    Feb 23 17:33:34 miki_netbook kernel: NET: Registered protocol family 10
    Feb 23 17:33:34 miki_netbook kernel: NET: Registered protocol family 17
    Feb 23 17:33:34 miki_netbook kernel: Key type dns_resolver registered
    Feb 23 17:33:34 miki_netbook kernel: Using IPI No-Shortcut mode
    Feb 23 17:33:34 miki_netbook kernel: PM: Hibernation image not present or could not be loaded.
    Feb 23 17:33:34 miki_netbook kernel: registered taskstats version 1
    Feb 23 17:33:34 miki_netbook kernel: Magic number: 1:324:589
    Feb 23 17:33:34 miki_netbook kernel: rtc_cmos 00:03: setting system clock to 2013-02-23 15:33:31 UTC (1361633611)
    Feb 23 17:33:34 miki_netbook kernel: Freeing unused kernel memory: 556k freed
    Feb 23 17:33:34 miki_netbook kernel: Write protecting the kernel text: 4100k
    Feb 23 17:33:34 miki_netbook kernel: Write protecting the kernel read-only data: 1256k
    Feb 23 17:33:34 miki_netbook kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
    Feb 23 17:33:34 miki_netbook systemd-udevd[44]: starting version 197
    Feb 23 17:33:34 miki_netbook kernel: ACPI: bus type usb registered
    Feb 23 17:33:34 miki_netbook kernel: usbcore: registered new interface driver usbfs
    Feb 23 17:33:34 miki_netbook kernel: usbcore: registered new interface driver hub
    Feb 23 17:33:34 miki_netbook kernel: usbcore: registered new device driver usb
    Feb 23 17:33:34 miki_netbook kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    Feb 23 17:33:34 miki_netbook kernel: ehci_hcd 0000:00:1d.7: setting latency timer to 64
    Feb 23 17:33:34 miki_netbook kernel: ehci_hcd 0000:00:1d.7: EHCI Host Controller
    Feb 23 17:33:34 miki_netbook kernel: ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
    Feb 23 17:33:34 miki_netbook kernel: ehci_hcd 0000:00:1d.7: debug port 1
    Feb 23 17:33:34 miki_netbook kernel: SCSI subsystem initialized
    Feb 23 17:33:34 miki_netbook kernel: ehci_hcd 0000:00:1d.7: cache line size of 64 is not supported
    Feb 23 17:33:34 miki_netbook kernel: ehci_hcd 0000:00:1d.7: irq 16, io mem 0x94344400
    Feb 23 17:33:34 miki_netbook kernel: ACPI: bus type scsi registered
    Feb 23 17:33:34 miki_netbook kernel: libata version 3.00 loaded.
    Feb 23 17:33:34 miki_netbook kernel: ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
    Feb 23 17:33:34 miki_netbook kernel: hub 1-0:1.0: USB hub found
    Feb 23 17:33:34 miki_netbook kernel: hub 1-0:1.0: 8 ports detected
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd: USB Universal Host Controller Interface driver
    Feb 23 17:33:34 miki_netbook kernel: ata_piix 0000:00:1f.2: version 2.13
    Feb 23 17:33:34 miki_netbook kernel: ata_piix 0000:00:1f.2: MAP [
    Feb 23 17:33:34 miki_netbook kernel: P0 P2 IDE IDE ]
    Feb 23 17:33:34 miki_netbook kernel: ata_piix 0000:00:1f.2: setting latency timer to 64
    Feb 23 17:33:34 miki_netbook kernel: scsi0 : ata_piix
    Feb 23 17:33:34 miki_netbook kernel: scsi1 : ata_piix
    Feb 23 17:33:34 miki_netbook kernel: ata1: SATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0x40a0 irq 14
    Feb 23 17:33:34 miki_netbook kernel: ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x40a8 irq 15
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.0: setting latency timer to 64
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.0: UHCI Host Controller
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.0: irq 16, io base 0x00004080
    Feb 23 17:33:34 miki_netbook kernel: hub 2-0:1.0: USB hub found
    Feb 23 17:33:34 miki_netbook kernel: hub 2-0:1.0: 2 ports detected
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.1: setting latency timer to 64
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.1: UHCI Host Controller
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.1: irq 17, io base 0x00004060
    Feb 23 17:33:34 miki_netbook kernel: hub 3-0:1.0: USB hub found
    Feb 23 17:33:34 miki_netbook kernel: hub 3-0:1.0: 2 ports detected
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.2: setting latency timer to 64
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.2: UHCI Host Controller
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.2: irq 18, io base 0x00004040
    Feb 23 17:33:34 miki_netbook kernel: hub 4-0:1.0: USB hub found
    Feb 23 17:33:34 miki_netbook kernel: hub 4-0:1.0: 2 ports detected
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.3: setting latency timer to 64
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.3: UHCI Host Controller
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.3: irq 19, io base 0x00004020
    Feb 23 17:33:34 miki_netbook kernel: hub 5-0:1.0: USB hub found
    Feb 23 17:33:34 miki_netbook kernel: hub 5-0:1.0: 2 ports detected
    Feb 23 17:33:34 miki_netbook kernel: ata1.00: ATA-8: SAMSUNG HM251JI, 2SS00_01, max UDMA7
    Feb 23 17:33:34 miki_netbook kernel: ata1.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 0/32)
    Feb 23 17:33:34 miki_netbook kernel: ata1.00: configured for UDMA/133
    Feb 23 17:33:34 miki_netbook kernel: scsi 0:0:0:0: Direct-Access ATA SAMSUNG HM251JI 2SS0 PQ: 0 ANSI: 5
    Feb 23 17:33:34 miki_netbook kernel: sd 0:0:0:0: [sda] 488397168 512-byte logical blocks: (250 GB/232 GiB)
    Feb 23 17:33:34 miki_netbook kernel: sd 0:0:0:0: [sda] Write Protect is off
    Feb 23 17:33:34 miki_netbook kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
    Feb 23 17:33:34 miki_netbook kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    Feb 23 17:33:34 miki_netbook kernel: sda: sda1 sda2 sda3 sda4
    Feb 23 17:33:34 miki_netbook kernel: sd 0:0:0:0: [sda] Attached SCSI disk
    Feb 23 17:33:34 miki_netbook kernel: usb 1-5: new high-speed USB device number 3 using ehci_hcd
    Feb 23 17:33:34 miki_netbook kernel: usb 1-7: new high-speed USB device number 4 using ehci_hcd
    Feb 23 17:33:34 miki_netbook kernel: EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
    Feb 23 17:33:34 miki_netbook kernel: usb 2-1: new low-speed USB device number 2 using uhci_hcd
    Feb 23 17:33:34 miki_netbook systemd[1]: systemd 197 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)
    Feb 23 17:33:34 miki_netbook systemd[1]: Set hostname to <miki_netbook>.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
    Feb 23 17:33:34 miki_netbook systemd[1]: Started Forward Password Requests to Wall Directory Watch.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Remote File Systems.
    Feb 23 17:33:34 miki_netbook systemd[1]: Reached target Remote File Systems.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Delayed Shutdown Socket.
    Feb 23 17:33:34 miki_netbook systemd[1]: Listening on Delayed Shutdown Socket.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Device-mapper event daemon FIFOs.
    Feb 23 17:33:34 miki_netbook systemd[1]: Listening on Device-mapper event daemon FIFOs.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
    Feb 23 17:33:34 miki_netbook systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting LVM2 metadata daemon socket.
    Feb 23 17:33:34 miki_netbook systemd[1]: Listening on LVM2 metadata daemon socket.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Encrypted Volumes.
    Feb 23 17:33:34 miki_netbook systemd[1]: Reached target Encrypted Volumes.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
    Feb 23 17:33:34 miki_netbook systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting udev Kernel Socket.
    Feb 23 17:33:34 miki_netbook systemd[1]: Listening on udev Kernel Socket.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting udev Control Socket.
    Feb 23 17:33:34 miki_netbook systemd[1]: Listening on udev Control Socket.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
    Feb 23 17:33:34 miki_netbook systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
    Feb 23 17:33:34 miki_netbook systemd[1]: Expecting device dev-disk-by\x2duuid-9501e2aa\x2d4efe\x2d4497\x2d9b55\x2ddb7ebc7afe5d.device...
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Journal Socket.
    Feb 23 17:33:34 miki_netbook systemd[1]: Listening on Journal Socket.
    Feb 23 17:33:34 miki_netbook systemd[1]: Started File System Check on Root Device.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Remount Root and Kernel File Systems...
    Feb 23 17:33:34 miki_netbook systemd[1]: Mounting Debug File System...
    Feb 23 17:33:34 miki_netbook systemd[1]: Mounting POSIX Message Queue File System...
    Feb 23 17:33:34 miki_netbook systemd[1]: Started Load Kernel Modules.
    Feb 23 17:33:34 miki_netbook systemd[1]: Mounted FUSE Control File System.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Setup Virtual Console...
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting udev Kernel Device Manager...
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Apply Kernel Variables...
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting udev Coldplug all Devices...
    Feb 23 17:33:34 miki_netbook systemd[1]: Mounting Configuration File System...
    Feb 23 17:33:34 miki_netbook systemd[1]: Mounting Huge Pages File System...
    Feb 23 17:33:34 miki_netbook systemd[1]: Started Set Up Additional Binary Formats.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Journal Service...
    Feb 23 17:33:34 miki_netbook systemd[1]: Started Journal Service.
    Feb 23 17:33:34 miki_netbook systemd[1]: Mounting Temporary Directory...
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting home.automount.
    Feb 23 17:33:34 miki_netbook systemd[1]: Set up automount home.automount.
    Feb 23 17:33:34 miki_netbook systemd[1]: Started Setup Virtual Console.
    Feb 23 17:33:34 miki_netbook systemd[1]: Started Apply Kernel Variables.
    Feb 23 17:33:34 miki_netbook systemd-udevd[111]: starting version 197
    Feb 23 17:33:34 miki_netbook kernel: EXT4-fs (sda2): re-mounted. Opts: (null)
    Feb 23 17:33:34 miki_netbook systemd-journal[119]: Journal started
    Feb 23 17:33:34 miki_netbook systemd[1]: Started udev Kernel Device Manager.
    Feb 23 17:33:34 miki_netbook systemd[1]: Started Remount Root and Kernel File Systems.
    Feb 23 17:33:34 miki_netbook systemd[1]: Mounted Debug File System.
    Feb 23 17:33:34 miki_netbook systemd[1]: Mounted POSIX Message Queue File System.
    Feb 23 17:33:34 miki_netbook systemd[1]: Mounted Configuration File System.
    Feb 23 17:33:34 miki_netbook systemd[1]: Mounted Huge Pages File System.
    Feb 23 17:33:34 miki_netbook systemd[1]: Mounted Temporary Directory.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Local File Systems.
    Feb 23 17:33:34 miki_netbook systemd[1]: Reached target Local File Systems.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Recreate Volatile Files and Directories...
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Trigger Flushing of Journal to Persistent Storage...
    Feb 23 17:33:34 miki_netbook systemd[1]: Started udev Coldplug all Devices.
    Feb 23 17:33:34 miki_netbook systemd-journal[119]: Allowing system journal files to grow to 1.4G.
    Feb 23 17:33:34 miki_netbook systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
    Feb 23 17:33:34 miki_netbook systemd[1]: Started Load Random Seed.
    Feb 23 17:33:34 miki_netbook systemd[1]: Started Recreate Volatile Files and Directories.
    Feb 23 17:33:37 miki_netbook systemd[1]: Starting Sound Card.
    Feb 23 17:33:37 miki_netbook systemd[1]: Reached target Sound Card.
    Feb 23 17:33:39 miki_netbook systemd[1]: Found device SAMSUNG_HM251JI.
    Feb 23 17:33:39 miki_netbook systemd[1]: Activating swap /dev/disk/by-uuid/9501e2aa-4efe-4497-9b55-db7ebc7afe5d...
    Feb 23 17:33:39 miki_netbook systemd[1]: Activated swap /dev/disk/by-uuid/9501e2aa-4efe-4497-9b55-db7ebc7afe5d.
    Feb 23 17:33:39 miki_netbook systemd[1]: Starting Swap.
    Feb 23 17:33:39 miki_netbook systemd[1]: Reached target Swap.
    Feb 23 17:33:39 miki_netbook systemd[1]: Starting System Initialization.
    Feb 23 17:33:41 miki_netbook NetworkManager[229]: <info> NetworkManager (version 0.9.6.4) is starting...
    Feb 23 17:33:41 miki_netbook NetworkManager[229]: <info> Read config file /etc/NetworkManager/NetworkManager.conf
    Feb 23 17:33:41 miki_netbook NetworkManager[229]: <info> WEXT support is enabled
    Feb 23 17:33:41 miki_netbook dbus[231]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
    Feb 23 17:33:41 miki_netbook polkitd[241]: Started polkitd version 0.109
    Feb 23 17:33:42 miki_netbook polkitd[241]: Loading rules from directory /etc/polkit-1/rules.d
    Feb 23 17:33:42 miki_netbook polkitd[241]: Loading rules from directory /usr/share/polkit-1/rules.d
    Feb 23 17:33:42 miki_netbook polkitd[241]: Finished loading, compiling and executing 1 rules
    Feb 23 17:33:42 miki_netbook dbus[231]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
    Feb 23 17:33:42 miki_netbook polkitd[241]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
    Feb 23 17:33:42 miki_netbook NetworkManager[229]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
    Feb 23 17:33:45 miki_netbook NetworkManager[229]: keyfile: parsing default ...
    Feb 23 17:33:45 miki_netbook NetworkManager[229]: keyfile: read connection 'default'
    Feb 23 17:33:46 miki_netbook NetworkManager[229]: keyfile: parsing Badt ...
    Feb 23 17:33:46 miki_netbook NetworkManager[229]: keyfile: read connection 'Badt'
    Feb 23 17:33:46 miki_netbook NetworkManager[229]: <info> trying to start the modem manager...
    Feb 23 17:33:46 miki_netbook NetworkManager[229]: <info> monitoring kernel firmware directory '/lib/firmware'.
    Feb 23 17:33:46 miki_netbook NetworkManager[229]: <warn> Failed to open plugin directory /usr/lib/NetworkManager: Error opening directory '/usr/lib/NetworkManager': No such file or directory
    Feb 23 17:33:46 miki_netbook NetworkManager[229]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/ieee80211/phy0/rfkill0) (driver rtl8187)
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> WiFi enabled by radio killswitch; enabled by state file
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> WWAN enabled by radio killswitch; enabled by state file
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> WiMAX enabled by radio killswitch; enabled by state file
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> Networking is enabled by state file
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <warn> failed to allocate link cache: (-10) Operation not supported
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (enp2s0): carrier is OFF
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (enp2s0): new Ethernet device (driver: 'r8169' ifindex: 2)
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (enp2s0): exported as /org/freedesktop/NetworkManager/Devices/0
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (enp2s0): now managed
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (enp2s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (enp2s0): bringing up device.
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (enp2s0): preparing device.
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (enp2s0): deactivating device (reason 'managed') [2]
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> Added default wired connection 'Wired connection 1' for /sys/devices/pci0000:00/0000:00:1c.1/0000:02:00.0/net/enp2s0
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (wlp0s29f7u7): using nl80211 for WiFi device control
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (wlp0s29f7u7): new 802.11 WiFi device (driver: 'rtl8187' ifindex: 3)
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (wlp0s29f7u7): exported as /org/freedesktop/NetworkManager/Devices/1
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (wlp0s29f7u7): now managed
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (wlp0s29f7u7): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (wlp0s29f7u7): bringing up device.
    Feb 23 17:33:47 miki_netbook kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
    Feb 23 17:33:47 miki_netbook systemd[1]: Started Network Manager.
    Feb 23 17:33:47 miki_netbook systemd[1]: Starting Network.
    Feb 23 17:33:47 miki_netbook systemd[1]: Reached target Network.
    Feb 23 17:33:47 miki_netbook systemd[1]: Starting Network Time Service...
    Feb 23 17:33:47 miki_netbook kernel: ACPI: Power Button [PWRB]
    Feb 23 17:33:47 miki_netbook kernel: input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input2
    Feb 23 17:33:47 miki_netbook kernel: ACPI: Lid Switch [LID0]
    Feb 23 17:33:47 miki_netbook kernel: input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input3
    Feb 23 17:33:47 miki_netbook dbus-daemon[231]: dbus[231]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
    Feb 23 17:33:47 miki_netbook dbus-daemon[231]: dbus[231]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
    Feb 23 17:33:47 miki_netbook kernel: ACPI: Sleep Button [SLPB]
    Feb 23 17:33:47 miki_netbook kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
    Feb 23 17:33:47 miki_netbook kernel: ACPI: Power Button [PWRF]
    Feb 23 17:33:47 miki_netbook kernel: intel_rng: FWH not detected
    Feb 23 17:33:47 miki_netbook kernel: ACPI: AC Adapter [ACAD] (on-line)
    Feb 23 17:33:47 miki_netbook kernel: ACPI: Requesting acpi_cpufreq
    Feb 23 17:33:47 miki_netbook kernel: ACPI: Video Device [OVGA] (multi-head: yes rom: yes post: no)
    Feb 23 17:33:47 miki_netbook kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5
    Feb 23 17:33:47 miki_netbook kernel: thermal LNXTHERM:00: registered as thermal_zone0
    Feb 23 17:33:47 miki_netbook kernel: ACPI: Thermal Zone [THRM] (56 C)
    Feb 23 17:33:47 miki_netbook kernel: ACPI: Battery Slot [BAT1] (battery present)
    Feb 23 17:33:47 miki_netbook kernel: input: PC Speaker as /devices/platform/pcspkr/input/input6
    Feb 23 17:33:47 miki_netbook kernel: ACPI: Invalid Power Resource to register!
    Feb 23 17:33:47 miki_netbook kernel: ACPI Warning:
    Feb 23 17:33:47 miki_netbook kernel: 0x00000428-0x0000042f SystemIO conflicts with Region \PMBA 1 (20120913/utaddress-251)
    Feb 23 17:33:47 miki_netbook kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
    Feb 23 17:33:47 miki_netbook kernel: ACPI Warning: 0x00000530-0x0000053f SystemIO conflicts with Region \GPIO 1 (20120913/utaddress-251)
    Feb 23 17:33:47 miki_netbook kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
    Feb 23 17:33:47 miki_netbook kernel: ACPI Warning: 0x00000500-0x0000052f SystemIO conflicts with Region \GPIO 1 (20120913/utaddress-251)
    Feb 23 17:33:47 miki_netbook kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
    Feb 23 17:33:47 miki_netbook kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
    Feb 23 17:33:47 miki_netbook kernel: leds_ss4200: no LED devices found
    Feb 23 17:33:47 miki_netbook kernel: iTCO_vendor_support: vendor-support=0
    Feb 23 17:33:47 miki_netbook kernel: iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10
    Feb 23 17:33:47 miki_netbook kernel: iTCO_wdt: Found a ICH7-M or ICH7-U TCO device (Version=2, TCOBASE=0x0460)
    Feb 23 17:33:47 miki_netbook kernel: iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
    Feb 23 17:33:47 miki_netbook kernel: microcode: CPU0 sig=0x106c2, pf=0x4, revision=0x208
    Feb 23 17:33:47 miki_netbook kernel: microcode: CPU1 sig=0x106c2, pf=0x4, revision=0x208
    Feb 23 17:33:47 miki_netbook kernel: microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
    Feb 23 17:33:47 miki_netbook kernel: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
    Feb 23 17:33:47 miki_netbook kernel: r8169 0000:02:00.0: irq 42 for MSI/MSI-X
    Feb 23 17:33:47 miki_netbook kernel: r8169 0000:02:00.0 eth0: RTL8102e at 0xf8814000, 00:23:8b:85:d8:aa, XID 04a00000 IRQ 42
    Feb 23 17:33:47 miki_netbook kernel: Linux agpgart interface v0.103
    Feb 23 17:33:47 miki_netbook kernel: cfg80211: Calling CRDA to update world regulatory domain
    Feb 23 17:33:47 miki_netbook kernel: [drm] Initialized drm 1.1.0 20060810
    Feb 23 17:33:47 miki_netbook kernel: usbcore: registered new interface driver usbhid
    Feb 23 17:33:47 miki_netbook kernel: usbhid: USB HID core driver
    Feb 23 17:33:47 miki_netbook kernel: media: Linux media interface: v0.10
    Feb 23 17:33:47 miki_netbook systemd-udevd[137]: renamed network interface eth0 to enp2s0
    Feb 23 17:33:47 miki_netbook kernel: Linux video capture interface: v2.00
    Feb 23 17:33:47 miki_netbook kernel: i801_smbus 0000:00:1f.3: SMBus using PCI Interrupt
    Feb 23 17:33:47 miki_netbook kernel: uvcvideo: Found UVC 1.00 device USB 2.0 Camera (064e:a127)
    Feb 23 17:33:47 miki_netbook kernel: agpgart-intel 0000:00:00.0: Intel 945GME Chipset
    Feb 23 17:33:47 miki_netbook kernel: agpgart-intel 0000:00:00.0: detected gtt size: 262144K total, 262144K mappable
    Feb 23 17:33:47 miki_netbook ntpd[253]: ntpd [email protected] Tue Dec 18 22:49:50 UTC 2012 (1)
    Feb 23 17:33:47 miki_netbook ntpd[254]: proto: precision = 1.955 usec
    Feb 23 17:33:47 miki_netbook ntpd[254]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
    Feb 23 17:33:47 miki_netbook ntpd[254]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
    Feb 23 17:33:47 miki_netbook ntpd[254]: Listen and drop on 1 v6wildcard :: UDP 123
    Feb 23 17:33:47 miki_netbook kernel: agpgart-intel 0000:00:00.0: detected 8192K stolen memory
    Feb 23 17:33:47 miki_netbook systemd[1]: Started Network Time Service.
    Feb 23 17:33:47 miki_netbook systemd[1]: Starting Multi-User.
    Feb 23 17:33:47 miki_netbook systemd[1]: Reached target Multi-User.
    Feb 23 17:33:47 miki_netbook systemd[1]: Starting Graphical Interface.
    Feb 23 17:33:47 miki_netbook systemd[1]: Reached target Graphical Interface.
    Feb 23 17:33:47 miki_netbook systemd[1]: Starting Update UTMP about System Runlevel Changes...
    Feb 23 17:33:47 miki_netbook systemd[1]: Started Update UTMP about System Runlevel Changes.
    Feb 23 17:33:47 miki_netbook systemd[1]: Startup finished in 2s 641ms 739us (kernel) + 14s 238ms 5

    I had the exact same problem. For me the problem was the user groups. Apparently usergroups is not necessary for most use cases with systemd. And my user was in a lot of groups :-) . So I backed up my /etc/group and removed my username from almost every group.
    Hope it solves your problem!

  • REQUEST: UEFI/GOP bios update for R9 290X GAMING 4G

    Greetings,
    I'd appreciate it if you could give me an updated bios for my graphics card (see title).
    Beforehand, could you tell me how to extract the binaries first, so I could supply those to you?
    BIOS: dm121506.students.fhstp.ac.at/ORIGINAL%20BIOS/Hawaii.rom
    S/N: 602-V308-01SB1401024664
    Best regards

    here it is attached below
    For flashing:
    Quote from: Flob
    Create a bootable usb stick (https://forum-en.msi.com/index.php?topic=165175.0).
    Then unpack the previously provided archive (101.rar) and put the included file (TV308MH.101) on that stick.
    Rename TV308MH.101 to 101.rom. Put the atiflash.exe also included in the archive on the USB stick too. Now boot from the stick.
    Type atiflash -p -f -noaper 0 101.rom [ENTER] and let it flash the vbios.
    flash tool: http://www.techpowerup.com/downloads/2306/atiflash-4-17/

  • P45 Neo3: Vista64 SP1 does not install with bios 1.4 (did with 1.3)

    Today I tried to reinstall Vista 64-bits SP1 and the system repeatedly hangs with an underscore-like blinking cursor when Vista (install) is supposed to boot from the hard disk... (after I've entered all info and Vista has unpacked and copied files to the hard disk)
    I think this is weird because the same DVD installed fine about a week ago when I was most probably still using the 1.3 BIOS (I've upgraded to 1.4 recently).
    Note that I chose not to enter a key during installation, so it should not be an activation problem (Vista has a 30-day grace period, right?)
    Do other P45 Neo3 (MS-7514) owners have the same problem? How did you solve it? (besides downgrading the BIOS - if that's possible at all)

    Quote
    I'm not sure how that would help.
    If for some reason there is something wrong with the Master Boot Record of the drive (it happens) repartitioning & reformating the drive should fix that.
    A problem with the hard drive's MBR can explain this:
    Quote
    repeatedly hangs with an underscore-like blinking cursor when Vista (install) is supposed to boot from the hard disk...
    Quote
    So, can I temporarily safely downgrade to the 1.3 BIOS, or does the flash software only allow upgrades?
    You can upgrade/downgrade to whatever BIOS Version you choose with the >>MSI HQ Forum USB flasher<<.

  • Downgrade vga bios

    Hi ,
    I have a NX6600GT VTD128 and I have updated  ( big mistake ) the vga bios to the latest version using Live update.
    The current bios is 5.43.02.64.00 but I don't have the previous one.
    The thing is that i lost the temp readings from the display manager .
    Is there any way I can retrieve the previous bios version?
    I did the upgrade because I had some artifacts when using 3d models in Autocad and when playing games ( Freelancer ) and I still
    having them even after formatting the HDD.
    After formatting I use first the MSI drivers , I unistall them and use the latest NV drivers (Fware 93.71 )
    Still the same.   
    thanks

    Coolbits is simply a small file that adds registry entries so that hidden capabilities in the nVidia settings panel become available.  You can get Coolbits from Guru3D, http://downloads.guru3d.com/download.php?det=815 .   RivaTuner has even more capabilities, http://www.guru3d.com/index.php?page=rivatuner&menu=8
    Quote from: Guru3D
    Software Description
    Coolbits 2 unleashes hidden function within ForceWare drivers, it enables several new Direct3d and OpenGL configuration tabs, and even more tweaking capability from the nVidia taskbar settings panel.
    FAQ:
    Q. I dont see the temperature settings, is this due to my card?
    A. The temp settings panel is only available with cards equipped with thermal sensors. Some cards that I know of have temp sensors are 5700 Ultra, 5800 Ultra, 5900 non-Ultra and Ultra, and 5950 ultra. But really it all comes down to the manufacturer. I have seen some 5700 and 5900 without temp sensor, but mainly the cheaper XT/LX/SE versions.
    Q. The Fan always on doesn`t seem to work
    A. The 'fan always on' option is for cards with the OTES (i.e. 5800U) or similar cooling system in which shuts off in 2d mode. It will force fan on even in 2D mode. Of course this means the fans on the hs/f be designed such a way that this option can work.
    Q. I thought it enabled Opengl 2.0. It doesn't though.
    A. OpenGL Shading Language 2.0 can only be enabled on 55.xx and higher Forceware drivers. It had not yet been implemented in older Detonator or pre 55 Forceware drivers.
    Q. Where is the application profiles page?
    A. It has been disabled to allow for OpenGL and Direct3d tabs. You can re-enable the application profiles page by changing its respective value to 1 in the coolbits file.
    If you experience any minor problems, simply uninstall/reinstall your display driver. I would recommend using Driver Cleaner as well, especially when switching driver versions.
    Unpack the achive (self extracting) and then in the setup directory simply click on the .reg file. To get to these options simply right-click on your desktop and go to 'NVIDIA Analog Display' (Win XP/2003). For Win 2000 and lower you may need to get to the Nvidia Control Panel the old way. Right click desktop > Properties > Settings > Advanced > GeForce xxxx
    *NOTE: Coolbits 2 is not fully compatible with driver versions older than 55.xx. If you do happen to run this tweak with drivers older than 55.xx you will more than likely get errors at startup! To enable full compatibility, you must disable the options that are causing issues with your current setup.

  • CQ61 restore Bios from USB

    I have a CQ61-429us that stopped working. When I power on I get all the lights, the HDD and CD drives spin, and sound like they are fine. I always have a black screen, so I tried hooking up to an external monitor, with no video signal even after function-F4. The lights will flash twice contiunally, from my reading I think that means no BIOS. I tried restoring the BIOS from  the HDD to no avail. Formatted an USB to FAT32 with volume "HP_TOOLS" and downloaded the BIOS unpacked to the usb Pressed the Windows + B button upon startup but no update. Am I missing something? 
    Thanks

    Usually it is the cap lock and number lock keys that give the blink codes.Is this the keys that are blinking? I ask because you said you get 'all' lights after powering on.
    Have you tried a hard reset? Have you tried removing 1 stick of memory at a time to see if it will boot?
    ******Clicking the Thumbs-Up button is a way to say -Thanks!.******
    **Click Accept as Solution on a Reply that solves your issue to help others**

  • Request GOP BIOS "R9 270 GAMING 2G"

    HI
    I would like to enable Windows 8.1 bios options on "MSI Z97S SLI PLUS" motherboard but I can't because of no GOP suport by graphic card.
    Could You also get me some information about how to flash graphic card bios.
    Below SN and link to oryginal bios:
    SN: 602-V305-03SB1406025095
    "speedy.sh/qubyJ/Pitcairn.rom"
    Thanks

    Use the attached.
    Decompress the attached .rar archive with Winrar: http://www.rarlab.com/download.htm
    Create a bootable usb stick (https://forum-en.msi.com/index.php?topic=165175.0).
    Then unpack the previously provided archive (100.rar) and put the included file (TV305MH.100) on that stick.
    Rename TV305MH.100 to 100.rom. Put the atiflash.exe also included in the archive provided on the USB stick too. Now boot from the stick.
    Type atiflash -p -f -noaper 0 100.rom [ENTER] and let it flash the vbios.

  • Request a GOP UEFI bios for MSI R9 270 Gaming 2g

    MSI R9 270 Gaming 2g
    sn:602-v305-010b1402051637
    Bios Version: 015.041.000.000.003038(113-C6300100-X01)
    Original vbios: speedy.sh/mD8uN/Pitcairn.rom
    Thank you very much.

    Use the attached vbios for your card.
    Unpack the provided archive (100.rar) and put the included file (TV305MH.100) on that stick.
    Rename TV305MH.100 to 100.rom. Put the atiflash.exe also included in the archive on the USB stick too. Now boot from the stick.
    Type atiflash -p -f -noaper 0 100.rom [ENTER] and let it flash the vbios.

  • Request: GOP UEFI BIOS for MSI Radeon HD 7870 HAWK

    Hi, please provide the bios,I need a bios for win8.1 and with secure boot support,thank you~
    Here is the SN, i am so sorry that i don't know if it is " S" or " 8 ",please help me……
    oh,I think the SN is:602-V281-08SC1306033160-2G3, "088C" can not be regesterd in MSI.COM,error format

    Use the attached.
    Create a bootable usb stick (https://forum-en.msi.com/index.php?topic=165175.0).
    Then unpack the provided archive (130.rar) and put the included file (TV281MH.130) on that stick.
    Rename TV281MH.130 to 130.rom. Put the atiflash.exe also included in the archive on the USB stick too. Now boot from the stick.
    Type atiflash -p -f -noaper 0 130.rom [ENTER] and let it flash the vbios.

Maybe you are looking for

  • HT1848 iTunes and music transfer from laptop to iPad 2

    I'm trying to transfer music on my laptop iTunes to my iPad.  How can I do this?

  • Can't drag and drop attachments into mail fullscreen

    Have a weird issue.  In lion I could drag and drog into a new mail message by dragging the attachment to the hot corner then to the fullscreen mail app then onto the new mail message. Now for some reason in Mt. Lion it will no longer do this. I can d

  • 27" iMac Monitor "refresh rate"

    Hello! I'm considering buying a 27" iMac but there's 1 more thing that I need to know before doing so. Before you go ahead and tell me that refresh rates on a CRT and LCD monitor are not the same: I'm aware of that. LCD screens still have a similar t

  • Readdle docs different in iTunes 10

    Before the latest iTunes upgrade, or iPad upgrade to 6 I could use Readdle docs in the application section of iTunes to "add" documents to the iPad from the PC.  With the new iTunes there doesn't seem to be this function.  I use this all the time as

  • Predictive text keyboard option is greyed out

    I have turned on/off all keyboard and spelling options in Settings. Restore and setup as new? Keeping finders crozzed.