Setup Problem in Measure 2.0 with USB-6009

I purchased a USB-6009 for my laptop (running XP Pro), and installed the NiDAQmx vers. 7.5 that came with the unit. I opened NI explorer, and tested the unit in there (using Test Panel). It worked nicely there, though the indicator light on the DAQ board  was blinking. I then added my copy of Measure to the computer, but when starting MS Excel, I get the error message "Measure unable to detect a valid installation of NI-DAQ. Please install NIDAQ before using Measure for Windows Data Acquisition Add-In."
Is there a step I missed? or is there something wrong with my applications?

Hello dlclough,
Measure 2.0 is a Legacy application that works only with our Traditional NI-DAQ Legacy driver, not NI-DAQmx which supports the USB-6009.  The blinking light on the USB-6009 simply indicates that the device is receiving power.  However, if you go to this section in the Readme file for NI-DAQmx 7.5, you can look at your numerous options for programming NI-DAQmx.  You can also use VI Logger Lite which is installed with the driver for simple data logging applications.
Regards,
Laura

Similar Messages

  • Problem installing multi-disc software with USB Superdrive

    I'm trying to install a large virtual instrument library for music production (Komplete 5). On a brand new Macbook Pro Retina, using the USB Superdrive for installation.  Typically with these installers, once it's finished with one disc, it asks you to insert the next DVD in the sequence to continue installation. The problem I've run into with the Superdrive is that it won't allow me to eject the disc, giving me an error message that the disc is "in use by the installer." This never occured on other Macs with an internal optical drive. I can't find any way to force eject the disc in order to move on with the installation.  I'm stuck until I can find a workaround.  Any suggestions?

    The Disk Utility repair disk can't be run on the boot disk from the boot disk.  You must boot into another hard drive and run Disk Utility from it on your boot drive. Or you can try booting into the Recovery HD that Mt. Lion creates.  There you can run Disk Utility.  I'm not sure if you can repair disk with this method but it's worth a try. I've only used it to reinstall the system on my iMac. Apple - OS X Recovery restores your Mac with a few clicks.
    Another possibility is to boot into Safe Mode, Mac OS X: Starting up in Safe Mode.  During startup it will run some of the repair routines that disk utility does.  That may be sufficient.  Reboot and verify the disk again with DU.

  • Relay for use with USB 6009

    Hello
    I would like to control a Red Hat solenoid valve with the USB 6009 (Very neat and economical multifunction DAQ!). The USB 6009 has some digital output lines specified as TTL. Can someone advise me as to a suitable relay for a 120V AC valve with a 6Watts power consumption?
    Thanks John Brohan

    John,
    Here is the simple solution to your problem. You can tie two or more ports together which to get higher current capacity.Make sure you use the 4.7k pull up resistor after tieing them together.Then output all the tied ports together as if it is one port. In your case if you need 20ma you can tie-up 3 ports for 24ma capacity.
    Warning!!!! You have to turn all the ports ON or OFF at one time otherwise it may burn the board.
    Kanwar

  • Problems to measure a signal with 10kHz frequenz

    Hello,
    i want to measure a signal at 10khz frequenz.
    My problem is that from 100Hz above i dont get a clear Signal.

    Daniel,
    Could you provide more information about your task.
    - What type of signal is it (sine, square wave, etc.)?
    - What hardware are you using to measure the signal?
    - What type of input are you using (analog in, digital in, counter)?
    - How are you performing the measurement? What functions are you using? What development environment (LabVIEW, C, etc.) are you using? Can you attach an example of your code?
    Christian L
    NI Consulting Services
    Christian Loew, CLA
    Principal Systems Engineer, National Instruments
    Please tip your answer providers with kudos.
    Any attached Code is provided As Is. It has not been tested or validated as a product, for use in a deployed application or system,
    or for use in hazardous environments. You assume all risks for use of the Code and use of the Code is subject
    to the Sample Code License Terms which can be found at: http://ni.com/samplecodelicense

  • IRQ problems?, especially with USB.... read this

    Summary: the following things are listed to help people configure or disable USB and USB IRQ related options, some steps may help diagnose/eliminate other IRQ problems. Some Operating Systems/Motherboards may have Similiar or Alternative ways to preform the following options,(Some may not be compatible with these Options):
    From initial installation problems to suddenly not working USB, cleaning up the Device manager in Safe mode is the first step. Many hardware related problems in Windows can be traced to ghost devices and duplicate device entries. Obsolete and/or duplicate devices can ONLY be seen and removed in Windows Safe Mode. This procedure MUST be performed in SAFE MODE.
    USB can only share its IRQ with other USB Host controllers (such as a USB upgrade card, if applicable) and IRQ Holder for PCI Steering. (Some of the newer motherboards can share USB Devices with their On-Board Devices,ex: K7N2 Delta
    In most cases for mother boards the First and Last PCI slot share the same IRQ as the AGP slot. This is not always the case, and is usually addressed in the motherboard's manual. In some motherboards there are other slots that share IRQ's with other on board devices, these can lead to conflicts and errors later; try changing cards in PCI slots around.
    Sometimes you may find that when you have installed a new card (or device) into the system, other devices such as the sound card may stop working. Once again, the resource configuration needs to be changed. Do so by going to Control Panel, System, Hardware, Device Manager, (Com1) ,or other port's properties, disable usage. This is also the best way of disabling hardware so that if necessary the customer can turn the hardware back on through windows rather than having to play in the BIOS.After disabling a device in the BIOS boot to Safe Mode and delete the device from the Windows Device Manager. If the device is not removed from the Windows Device Manager in Safe Mode, Windows will continue to recognize the device and Windows will continue to assign it an IRQ.
    In some versions of the Award, AMI and Phenix bios you can select Plug and Play OS installed. This option lets you decide whether windows should handle the IRQ routing of devices or if the BIOS should handle the routing. Please note that if this option is enabled windows will show a completely different setup of IRQ's then what the BIOS reports You may wish to toggle this option if you find that moving the card dosn't work. This in some cases will change the way windows will assign IRQ's. In most cases this will help but not in all.
    Another section that you might want to look at is if the IRQ's are being assigned manually or automatically. Sometimes it is better to manually assign IRQ's and other times it is better to automatically assign them.You can do so by entering your BIOS... should be listed under PNP/OS or PNP/PCI Configuration. ( You must disable Plug N Play feature for this to work!)
    Properly installed IRQ Steering is critical to correctly working USB. If IRQ Steering is disabled the likely cause is improper BIOS settings. See the section on BIOS Settings. Go to Control Panel, System, Hardware, Device Manager, System Devices, PCI Bus...If you do not have the following options, then obviously your system shouldn't be configured this way. Seek alternative means to enable/disable them. View Status, go to Settings tab, Use Hardware should be enabled, go to IRQ Steering tab... The following options should be checked... Use IRQ Steering, Get IRQ table using ACPI BIOS, GET IRQ table using MS Specification table, Get IRQ table from Real Mode PCIBIOS 2.1 call.... Under IRQ Routing Status the following should be displayed: (AMD) system should read: IRQ Steering Enabled, IRQ Table read from ACPI BIOS. (Intel) system should read: IRQ Table read from MS IRQ Routing Specification), IRQ Miniport Data processed successfully, IRQ Miniport loaded successfully. If IRQ Steering is not enabled. Reboot the system to the BIOS setup (Usually holding the DEL key at bootup) and Enable (Plug and Play Operating System). Set (Assign IRQs) AUTO or System. IRQ Steering is essential to proper USB connectivity. BIOS control of Power Management should be Disabled or set to User...
    If all the above doesn't work, you can look at the hardware in the computer and disable any that is not nessasary. This will free up some IRQs and on the next reboot the IRQs may be reshuffled to a better configuration. Common hardware that is good to disable are com ports and USB controllers.  If you are not using your serial port for anything, disable COM1. If you are not using your USB try disabling the USB controllers and hubs. If you are using a USB mouse, try pulling it into the PS/2 port if possible. All these things will free up and change the available IRQ's, and allow USB devices to automatically select them.
    Disable USB Error Detection In Windows Standard Mode, Device Manager, USB Host Controllers, (SiS, Standard, ect..)USB Open Host Controller, Advanced, Enable the function (Disable USB Error Detection).
    With some motherboards you may need to install the newest version of the motherboard drivers and also may need to flash the BIOS.An example of this is VIA motherboards. The VIA or Apollo chipset boards require an update for their IRQ routing with windows. This update helps fix problems such as loss of data and such.
    If you still cannot isolate USB to it’s own IRQ, changing the I/O range of USB sometimes works.
    Possibly your last resort upgrading to USB by PCI/USB upgrade card is a recommended solution for systems with non-functioning onboard USB host controllers. Properly Installed the USB upgrade host controller should share the same IRQ as the onboard USB host controller. Check the motherboard manual or Manufacturers Web Site and install the new card into a PCI Slot that shares it's IRQ with USB. Do NOT disable USB in the BIOS as the upgrade card may not work if you do.
    If that won't fix it, you may want to contact your mother board's manufacturer, or retailer who sold you the unoperable System components, to see if your System is under any kind of waranty/recall; then order a new motherboard and components...there is always the possibility you will  end up with same problem. Or you can contact a computer tech in your area. Goodluck...
    Misc Tips....
    Check all Physical Connections (This includes: Motherboard mounting, cables, plugs, and visibly damaged components)...
    Don't use cables longer than what you need, this can decreases efficiency and or causes System instability...
    Check your Voltages in BIOS, and on your PSU (power supply unit); make sure your system is not underpowered...
    Check your CPU/System Temperature, check airflow/fans, then check with your CPU manufacturer for acceptable settings...
    Check BIOS, Drivers, Firmware, and Software for latest settings/updates...
    Check Compatability (can find information in your Motherboard, BIOS, and Device Manuals...
    Don't Overclock or Tweak settings you don't understand, unless you like the smell of toast...
    And finally, don't me scared to ask... no one here will think less of you for seeking info/help from those who know...

    Also if this has helped you or someone else in anyway please reply.
    -Michael

  • Power management problem with USB modem

    I now use a MS-6743 (i865G) board. My previous board was MS-6533, it did not have USB v2.0.
    The problem is my Aztech (originally Smartlink) USB modem prevents the system going into standby mode but this should be a USB 2.0 issue because I'm using the same driver for the modem like previous mainboard config. I could go into standby mode flawlessly with my old board.
    Furthermore I'm using USB keyboard, mouse but no power management property dialog box appear for those devices. So I'm pretty sure the problem is because of USB 2.0. Is there a way to come around this issue? Thanks in advance...

    To pin point whether or not IRQs conflicts is to be blamed, please kindly post your IRQs conflicts for us to verify.
    A signature of your system setup will proves greater help for others to advice you with more accurate directions and benefits you in the future.
    Please read this  Moan Guide too.

  • MSI K8N Diamond - Boot problems with USB devices attached.

    Hi There.
    I have been seeking the forums, but havent found the answer to my problem yet. 
    This is how it goes with ANY USB devices attached to either of the four USB ports on the Motherboard.
    When i turn on my system, it hangs in the POST right after displaying the BIOS version (Which I have updated to 1.6) - I cant use my Keyboard to get to the BIOS setup.
    Without USB devices attached...
    The system boots without problems. And in Windows XP SP2 i can insert my keyboard, mouse etc. and everything works great - both USB 1.1 & 2.0 devices.
    I have disabled the KB/USB.. in BIOS and I have disabled the "Boot on other device" option as well.
    As I have found on this forum, a lot of people have problems with USB Front panel and D-Bracket (USB ports) connectors causing the system to hang - But my D-Bracket (USB connectors) and my front USB port is at this time DISCONNECTED - so this cannot be the problem.
    The D-Bracket shows the "Bios Sign On" information - and stops at that point 
    Am I having a malfunctioning Motherboard here, or are there any solutions to this problem?
    Please help me as I am desperate to have my system work properly.
    Regards
    Stieper

    Well I have read about that somewhere in here, but my problem is NOT with an USB hub, but with any USB device attached to the motherboard's USB slots. It is driving me nuts to be honest!! I think it might be time for RMA 
    What do you say guys - is my Motherboard ready for RMA, or do I have to try something specific berfore sending it to the retailer??

  • K7N2 deltas mainboards have a problem with usb devices ??

    Ok here is my problem..
    I had installed WinXP Pro with SP1..
    I got a 20 GB USB2.0 disk.i connected it on the both front or rear usb ports.
    When i tried to transfer files to my usb disk or to my PC, in the middle of the copying, i got "Write Delay Failed" error and lost my usb connection..
    I had to plug it out and in again..
    Now, i have an DSL modem..Last night, i was disconnected from internet and my modem's lights gone..I plug it again, no lights..restarted my PC, also completely shutdown Windows XP..Again no lights..
    Then, formatted PC and installed windows 2000 Pr and SP4, until now, my modem worked fine..But USB 2.0 ports are still no use for my usb disk...
    In bios , it's enabled as USB 1.1+2.0..
    I think this K7N2 deltas have a problem with usb 2.0 devices and Win XP Pro..
    Some guys talking about, removing 9th wire earth, but couldn't understand which wire from where ? From mainboard or from usd device's cable ?
    Those cables are fabricated, i think it's impossible ?
    My processor is Athlon 2500+, ram Twinmos 512 DDR 400
    Thanks for reply

    I'm also having this problem. It's happening with my USB flash disk. I was almost buying another one when I tried it with Windows Vista on the same machine and it worked ok, then I tried Arch Linux (with kernel 2.6.30.5) on another machine and got the same error. After that I tried Ubuntu and it worked ok. Seems that Arch's kernel doesn't like my USB flash disk.
    Last edited by esdrasbeleza (2009-09-02 01:16:09)

  • If you're having problems with USB ports, read on...

    i'm reading that alot of people on here are having problems with their front (or top) usb on their cases not working with their k7n2 boards.  i have come across the correct solution to this problem in one of the posts (after having solved the problem on my own), however noone has posted the solution by itself on this forum so everyone can easily see it.
    The trick is to make sure that pin 10 (at least on a K7n2 delta-L), the pin labeled USBOC (USB Open Connection), is wired to NOTHING.  If the connector to your front usb ports is fused into one giant connector and it HAS a wire that will connect to this pin (labeled GND2 or Shield or something), CUT THAT WIRE.  Pin 10 on JUSB2 (at least on a K7n2 delta-L) must be OPEN.  If this pin IS connected to something (even if it is only GND), the motherboard will think something is connected to this usb port and you will get many unknown devices listed in your windows device manager and the rest of your usb ports may or may not work.
    As a general rule of thumb, if a pin on a motherboard is labeled OC for "Open Connection" and you wire something to it, you're asking for trouble.
    If you cannot understand this you should not be attempting to wire a motherboard in the first place. 
    Here is a picture to go along with this discussion.  If you cannot see this picture, I am sorry for it has probably been removed from the place I posted it online as I cannot attach pictures physically to this post.  If someone here has a way to permanently host this picture and post it to this thread permanently, that would be wonderful.
    In summary: all usb ports/headers have only four pins associated with it (VCC, USB+, USB-, GND).  If the connector (whether it's one big connector or individual sockets) to your front/top usb port has 5 sockets, don't connect the 5th socket to anything.  That goes for any case/motherboard combination.  This is what i'm talking about above.  I have no idea why motherboard and case manufacturers have a 5th pin involved in any way on either the pin or socket side.  It is not used for usb.
    EDIT:  I just noticed this has already been discussed in the trouble shooting guide in the above sticky post.  oh well, now we have a pretty picture to go along with it (i hope).

    :-D)Hello guys,
    as promised I come back here to give the results of my tests... and I have to say that you saved my day (even if I had to open back 60 secured cases).
    So the solution was the right one, when I unplugged the "ground" end of the front USB connector cable from the USBOC pin, those connectors finally worked as expected with USB 2.0 compliant devices.
    So thank you really much for this very usefull information !
    And even if maybe it's not only MSI's fault, I still believe that more information on those connectors in the user's manual would be really usefull (who knows what USBOC means except a few people and who could imagine that pluggin on it a "ground" cable would make it unserviceable ??). And who ever saw a user's manual bundled with a case ?? it's pretty unusual  
    Hope that someone at MSI will read that and take it into consideration, not for me (because now I'm aware) but for the thousands other consumers that will feel a little bit "annoyed" with that issue. I don't think that adding one line about it in user's manuals would be so much expensive  
    But I'm quite lucky myself... being able to understand and write english (even if I still have some progress to do  ) gave me the possibility to find the solution... but a lot of my french fellows can't do that... and there's no french forum here... How can they do ? They rely on user's manual
    Best regards,
    Nicolas

  • Zen vision:m chargin problem with USB ca

    I've got vision:m for months , and during this time I used to charge with USB cable , and didn't have any problem , but it doesn't charged earlier , actually I hooked it up to my USB last night , and there was blinking icon up to today , but no any progress . so I use its original cable(electricity) and?it's going to charge?.Should I going to warranty company for this problem(doesn't chargin with USB) ?thanks for sharing your mind ( and pardon for my english )?Message Edited by MTahmasebi on 2-3-200604:5 PM

    KRe: Zen Vision M Firmware Problem!!! Can't deal with this thing any more..._
    menios wrote:
    So you say that I actually have the Windows Media Player 0, because my Zen is being recognised..
    I have rebooted it several times but its just the same thing...it shows firmware problem!!
    Why isn't this player working?I've seen many people, not only from here, who have the same exact problem and they gave up on their mp3... I dont have this kind of luxury to buy a new one!!I don't know whether Creative has put on this a "time bomb" or is just faulty, but I really wish it could be saved..
    I'm saying it is WMP0 because the firmware file sees the player. The computer can recognize it but with WMP components that firmware file would be grayed-out..So when you reloaded the firmware did you choose "reload firmware" Before you connected it's?(That is what erases the firmware prior to uploading the firmware. If you did not do that it could cause it to fail.Do these ste
    ps.
    Open the firmware file,On the player format>cleanup>choose reload firmware, then connect & run the firmware file.

  • Airport Extreme - problem with usb printer and usb disk

    I have Airport extreme with firmware 7.1. I try connect usb disk and usb printer with usb-hub to airport. I can't get disk or printer working. Also try connect only disk or printer without usb-hub to airport getting same problem. How I get disk and printer working with wireless network (windows pc computers)?
    1)
    My printer is HP PSC 1210 all-in-one ( http://h10025.www1.hp.com/ewfrf/wc/product?product=90764&lc=fi&cc=fi&dlc=fi&lang =fi&cc=fi&y=0&x=0 )
    - printer seems working fine after installing bonjour printer installing wizard.
    - I get error (in windows) when I try print document from word. Error only says "error printing" in status value.
    - In airport utility all seems ok. Airport see usb printer "Hewlett-Packard psc 1200 series"
    - printer protocol is RAW and driver manufacture HP (also try with microsoft driver)
    2)
    USB disk is Targa Databox II 250
    - Airport utility says "Disk needs repair. Errors were found with a disk connected to your airport base station. please connect the usb disk to your mac or pc and use disk utility or another disk application to repair the disk"
    - I have connected Targa usb disk to windows pc and run scandisk and defreg. No errors found in windows. Result..no help for airport

    I have a similar problem to your second issue. Tried connecting a Netdisk to the USB port of the Airport Extreme and it also said there was a problem with the disk. Have performed a low level format on the disk and Airport Extreme still complained the disk had a problem.
    After unplugging the disk, my route decided to stop allowing wireless connections even after rebooting. Ended up having to hard reset the Airport Extreme and reconfigure it with my old settings to work again.
    FWIW, the first Airport Extreme I purchased today only worked on 802.11a and steadfastly refused to work on b/g so had to get a replacement. I suspect Apple's quality control is not quite as good as it used to be.

  • Officejet 7000 networking problems with usb printer

    connected up my new officejet 7000, replacing my deskjet 1280 on my pc, running xp sp3, networked on my work network. set up as shared printer. Showing on shared printer list on network, but when I try to install network printer on another machine on network it wont have it. comes up with cant connect, name may have changed or printer lost connection to server.
    anybody help?
    tried reinstalling, turning off firewall etc.. all to no effect.
    please help.........

    Tell me about your network - router brand/model and ISP type (DSL, Cable, etc).
    Is the printer also connected with USB and print sharing turned on?
    I am a bit confused as to your exact setup, sorry.
    Say thanks by clicking "Kudos" "thumbs up" in the post that helped you.
    I am employed by HP

  • Problem with usb devices

    hi guys,
    i have a problem with my usb devices.
    the dmesg:
    Linux version 2.6.30-ARCH (root@T-POWA-LX) (gcc version 4.4.1 (GCC) ) #1 SMP PREEMPT Fri Jul 31 07:30:28 CEST 2009
    Command line: root=/dev/sda5 vga=0x0361 ro
    KERNEL supported cpus:
    Intel GenuineIntel
    AMD AuthenticAMD
    Centaur CentaurHauls
    BIOS-provided physical RAM map:
    BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
    BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
    BIOS-e820: 00000000000ce000 - 00000000000d0000 (reserved)
    BIOS-e820: 00000000000dc000 - 0000000000100000 (reserved)
    BIOS-e820: 0000000000100000 - 000000007fed0000 (usable)
    BIOS-e820: 000000007fed0000 - 000000007fee3000 (ACPI NVS)
    BIOS-e820: 000000007fee3000 - 0000000080000000 (reserved)
    BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
    BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
    BIOS-e820: 00000000fed00000 - 00000000fed00400 (reserved)
    BIOS-e820: 00000000fed14000 - 00000000fed1a000 (reserved)
    BIOS-e820: 00000000fed1c000 - 00000000fed90000 (reserved)
    BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
    BIOS-e820: 00000000ff000000 - 0000000100000000 (reserved)
    DMI present.
    Phoenix BIOS detected: BIOS may corrupt low RAM, working around it.
    e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
    last_pfn = 0x7fed0 max_arch_pfn = 0x100000000
    MTRR default type: uncachable
    MTRR fixed ranges enabled:
    00000-9FFFF write-back
    A0000-BFFFF uncachable
    C0000-FFFFF write-protect
    MTRR variable ranges enabled:
    0 base 000000000 mask F80000000 write-back
    1 base 07FF00000 mask FFFF00000 uncachable
    2 disabled
    3 disabled
    4 disabled
    5 disabled
    6 disabled
    7 disabled
    x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    Scanning 0 areas for low memory corruption
    modified physical RAM map:
    modified: 0000000000000000 - 0000000000010000 (reserved)
    modified: 0000000000010000 - 000000000009f800 (usable)
    modified: 000000000009f800 - 00000000000a0000 (reserved)
    modified: 00000000000ce000 - 00000000000d0000 (reserved)
    modified: 00000000000dc000 - 0000000000100000 (reserved)
    modified: 0000000000100000 - 000000007fed0000 (usable)
    modified: 000000007fed0000 - 000000007fee3000 (ACPI NVS)
    modified: 000000007fee3000 - 0000000080000000 (reserved)
    modified: 00000000e0000000 - 00000000f0000000 (reserved)
    modified: 00000000fec00000 - 00000000fec10000 (reserved)
    modified: 00000000fed00000 - 00000000fed00400 (reserved)
    modified: 00000000fed14000 - 00000000fed1a000 (reserved)
    modified: 00000000fed1c000 - 00000000fed90000 (reserved)
    modified: 00000000fee00000 - 00000000fee01000 (reserved)
    modified: 00000000ff000000 - 0000000100000000 (reserved)
    init_memory_mapping: 0000000000000000-000000007fed0000
    0000000000 - 007fe00000 page 2M
    007fe00000 - 007fed0000 page 4k
    kernel direct mapping tables up to 7fed0000 @ 10000-14000
    RAMDISK: 37d42000 - 37fefc39
    ACPI: RSDP 00000000000f7fe0 00024 (v02 PTLTD )
    ACPI: XSDT 000000007fedab41 0008C (v01 Sony VAIO 20070418 PTL 00000000)
    ACPI: FACP 000000007fee1bd2 000F4 (v03 Sony VAIO 20070418 PTL 00000001)
    ACPI: DSDT 000000007fedbeeb 05C73 (v02 Sony VAIO 20070418 PTL 20050624)
    ACPI: FACS 000000007fee2fc0 00040
    ACPI: APIC 000000007fee1cc6 00068 (v01 Sony VAIO 20070418 PTL 0000005A)
    ACPI: HPET 000000007fee1d2e 00038 (v01 Sony VAIO 20070418 PTL 0000005A)
    ACPI: MCFG 000000007fee1d66 0003C (v01 Sony VAIO 20070418 PTL 0000005A)
    ACPI: TCPA 000000007fee1da2 00032 (v01 Sony VAIO 20070418 PTL 00005A52)
    ACPI: SLIC 000000007fee1dd4 00176 (v01 Sony VAIO 20070418 PTL 01000000)
    ACPI: TMOR 000000007fee1f4a 00026 (v01 Sony VAIO 20070418 PTL 00000003)
    ACPI: APIC 000000007fee1f70 00068 (v01 Sony VAIO 20070418 PTL 00000000)
    ACPI: BOOT 000000007fee1fd8 00028 (v01 Sony VAIO 20070418 PTL 00000001)
    ACPI: SSDT 000000007fedbc29 002C2 (v01 Sony VAIO 20070418 PTL 20050624)
    ACPI: SSDT 000000007fedb159 0025F (v01 Sony VAIO 20070418 PTL 20050624)
    ACPI: SSDT 000000007fedb0b3 000A6 (v01 Sony VAIO 20070418 PTL 20050624)
    ACPI: SSDT 000000007fedabcd 004E6 (v01 Sony VAIO 20070418 PTL 20050624)
    ACPI: BIOS bug: multiple APIC/MADT found, using 0
    ACPI: If "acpi_apic_instance=2" works better, notify [email protected]
    ACPI: Local APIC address 0xfee00000
    (7 early reservations) ==> bootmem [0000000000 - 007fed0000]
    #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
    #1 [0000006000 - 0000008000] TRAMPOLINE ==> [0000006000 - 0000008000]
    #2 [0000200000 - 000082d0d0] TEXT DATA BSS ==> [0000200000 - 000082d0d0]
    #3 [0037d42000 - 0037fefc39] RAMDISK ==> [0037d42000 - 0037fefc39]
    #4 [000009f800 - 0000100000] BIOS reserved ==> [000009f800 - 0000100000]
    #5 [000082e000 - 000082e204] BRK ==> [000082e000 - 000082e204]
    #6 [0000010000 - 0000012000] PGTABLE ==> [0000010000 - 0000012000]
    found SMP MP-table at [ffff8800000f8010] f8010
    [ffffe20000000000-ffffe20001bfffff] PMD -> [ffff880001200000-ffff880002dfffff] on node 0
    Zone PFN ranges:
    DMA 0x00000010 -> 0x00001000
    DMA32 0x00001000 -> 0x00100000
    Normal 0x00100000 -> 0x00100000
    Movable zone start PFN for each node
    early_node_map[2] active PFN ranges
    0: 0x00000010 -> 0x0000009f
    0: 0x00000100 -> 0x0007fed0
    On node 0 totalpages: 523871
    DMA zone: 56 pages used for memmap
    DMA zone: 1682 pages reserved
    DMA zone: 2245 pages, LIFO batch:0
    DMA32 zone: 7108 pages used for memmap
    DMA32 zone: 512780 pages, LIFO batch:31
    ACPI: PM-Timer IO Port: 0x1008
    ACPI: Local APIC address 0xfee00000
    ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
    ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
    ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
    ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
    ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
    IOAPIC[0]: apic_id 1, version 0, address 0xfec00000, GSI 0-23
    ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    ACPI: IRQ0 used by override.
    ACPI: IRQ2 used by override.
    ACPI: IRQ9 used by override.
    Using ACPI (MADT) for SMP configuration information
    ACPI: HPET id: 0x8086a201 base: 0xfed00000
    SMP: Allowing 2 CPUs, 0 hotplug CPUs
    nr_irqs_gsi: 24
    PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
    PM: Registered nosave memory: 00000000000a0000 - 00000000000ce000
    PM: Registered nosave memory: 00000000000ce000 - 00000000000d0000
    PM: Registered nosave memory: 00000000000d0000 - 00000000000dc000
    PM: Registered nosave memory: 00000000000dc000 - 0000000000100000
    Allocating PCI resources starting at 88000000 (gap: 80000000:60000000)
    NR_CPUS:16 nr_cpumask_bits:16 nr_cpu_ids:2 nr_node_ids:1
    PERCPU: Embedded 25 pages at ffff880001010000, static data 72352 bytes
    Built 1 zonelists in Zone order, mobility grouping on. Total pages: 515025
    Kernel command line: root=/dev/sda5 vga=0x0361 ro
    Initializing CPU#0
    NR_IRQS:768
    PID hash table entries: 4096 (order: 12, 32768 bytes)
    Extended CMOS year: 2000
    Fast TSC calibration using PIT
    Detected 1994.610 MHz processor.
    Console: colour dummy device 80x25
    console [tty0] enabled
    Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
    Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
    Checking aperture...
    No AGP bridge found
    Calgary: detecting Calgary via BIOS EBDA area
    Calgary: Unable to locate Rio Grande table in EBDA - bailing!
    Memory: 2053736k/2095936k available (3409k kernel code, 452k absent, 41160k reserved, 1239k data, 464k init)
    SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
    hpet clockevent registered
    HPET: 3 timers in total, 0 timers will be used for per-cpu timer
    Calibrating delay loop (skipped), value calculated using timer frequency.. 3990.43 BogoMIPS (lpj=6648700)
    Security Framework initialized
    Mount-cache hash table entries: 256
    CPU: L1 I cache: 32K, L1 D cache: 32K
    CPU: L2 cache: 4096K
    CPU: Physical Processor ID: 0
    CPU: Processor Core ID: 0
    CPU0: Thermal monitoring enabled (TM2)
    using mwait in idle threads.
    ACPI: Core revision 20090320
    Setting APIC routing to flat
    ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    CPU0: Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz stepping 0a
    Booting processor 1 APIC 0x1 ip 0x6000
    Initializing CPU#1
    Calibrating delay using timer specific routine.. 3991.23 BogoMIPS (lpj=6649976)
    CPU: L1 I cache: 32K, L1 D cache: 32K
    CPU: L2 cache: 4096K
    CPU: Physical Processor ID: 0
    CPU: Processor Core ID: 1
    CPU1: Thermal monitoring enabled (TM2)
    x86 PAT enabled: cpu 1, old 0x7040600070406, new 0x7010600070106
    CPU1: Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz stepping 0a
    checking TSC synchronization [CPU#0 -> CPU#1]: passed.
    Brought up 2 CPUs
    Total of 2 processors activated (7982.67 BogoMIPS).
    CPU0 attaching sched-domain:
    domain 0: span 0-1 level MC
    groups: 0 1
    CPU1 attaching sched-domain:
    domain 0: span 0-1 level MC
    groups: 1 0
    net_namespace: 1888 bytes
    Booting paravirtualized kernel on bare hardware
    NET: Registered protocol family 16
    ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
    ACPI: bus type pci registered
    PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
    PCI: MCFG area at e0000000 reserved in E820
    PCI: Using MMCONFIG at e0000000 - efffffff
    PCI: Using configuration type 1 for base access
    bio: create slab <bio-0> at 0
    ACPI: EC: Look up EC in DSDT
    ACPI: BIOS _OSI(Linux) query ignored
    ACPI: EC: non-query interrupt received, switching to interrupt mode
    ACPI: Interpreter enabled
    ACPI: (supports S0 S3 S4 S5)
    ACPI: Using IOAPIC for interrupt routing
    ACPI: EC: GPE storm detected, transactions will use polling mode
    ACPI: EC: missing confirmations, switch off interrupt mode.
    [Firmware Bug]: ACPI: ACPI brightness control misses _BQC function
    ACPI: EC: GPE = 0x17, I/O: command/status = 0x66, data = 0x62
    ACPI: EC: driver started in poll mode
    ACPI: No dock devices found.
    ACPI: PCI Root Bridge [PCI0] (0000:00)
    pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
    pci 0000:00:01.0: PME# disabled
    pci 0000:00:1a.0: reg 20 io port: [0x1800-0x181f]
    pci 0000:00:1a.1: reg 20 io port: [0x1820-0x183f]
    pci 0000:00:1a.7: reg 10 32bit mmio: [0xfc404800-0xfc404bff]
    pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
    pci 0000:00:1a.7: PME# disabled
    pci 0000:00:1b.0: reg 10 64bit mmio: [0xfc400000-0xfc403fff]
    pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
    pci 0000:00:1b.0: PME# disabled
    pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
    pci 0000:00:1c.0: PME# disabled
    pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
    pci 0000:00:1c.1: PME# disabled
    pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
    pci 0000:00:1c.2: PME# disabled
    pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
    pci 0000:00:1c.4: PME# disabled
    pci 0000:00:1d.0: reg 20 io port: [0x1840-0x185f]
    pci 0000:00:1d.1: reg 20 io port: [0x1860-0x187f]
    pci 0000:00:1d.2: reg 20 io port: [0x1880-0x189f]
    pci 0000:00:1d.7: reg 10 32bit mmio: [0xfc404c00-0xfc404fff]
    pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
    pci 0000:00:1d.7: PME# disabled
    pci 0000:00:1f.0: quirk: region 1000-107f claimed by ICH6 ACPI/GPIO/TCO
    pci 0000:00:1f.0: quirk: region 1180-11bf claimed by ICH6 GPIO
    pci 0000:00:1f.1: reg 10 io port: [0x00-0x07]
    pci 0000:00:1f.1: reg 14 io port: [0x00-0x03]
    pci 0000:00:1f.1: reg 18 io port: [0x00-0x07]
    pci 0000:00:1f.1: reg 1c io port: [0x00-0x03]
    pci 0000:00:1f.1: reg 20 io port: [0x18a0-0x18af]
    pci 0000:00:1f.2: reg 10 io port: [0x18d8-0x18df]
    pci 0000:00:1f.2: reg 14 io port: [0x18cc-0x18cf]
    pci 0000:00:1f.2: reg 18 io port: [0x18d0-0x18d7]
    pci 0000:00:1f.2: reg 1c io port: [0x18c8-0x18cb]
    pci 0000:00:1f.2: reg 20 io port: [0x18e0-0x18ff]
    pci 0000:00:1f.2: reg 24 32bit mmio: [0xfc404000-0xfc4047ff]
    pci 0000:00:1f.2: PME# supported from D3hot
    pci 0000:00:1f.2: PME# disabled
    pci 0000:00:1f.3: reg 10 32bit mmio: [0x000000-0x0000ff]
    pci 0000:00:1f.3: reg 20 io port: [0x1c00-0x1c1f]
    pci 0000:01:00.0: reg 10 32bit mmio: [0xce000000-0xceffffff]
    pci 0000:01:00.0: reg 14 64bit mmio: [0xd0000000-0xdfffffff]
    pci 0000:01:00.0: reg 1c 64bit mmio: [0xcc000000-0xcdffffff]
    pci 0000:01:00.0: reg 24 io port: [0x2000-0x207f]
    pci 0000:01:00.0: reg 30 32bit mmio: [0x000000-0x01ffff]
    pci 0000:00:01.0: bridge io port: [0x2000-0x2fff]
    pci 0000:00:01.0: bridge 32bit mmio: [0xcc000000-0xceffffff]
    pci 0000:00:01.0: bridge 64bit mmio pref: [0xd0000000-0xdfffffff]
    pci 0000:00:1c.0: bridge io port: [0x3000-0x3fff]
    pci 0000:00:1c.0: bridge 32bit mmio: [0xf6000000-0xf7ffffff]
    pci 0000:00:1c.0: bridge 64bit mmio pref: [0xf0000000-0xf1ffffff]
    pci 0000:00:1c.1: bridge io port: [0x4000-0x4fff]
    pci 0000:00:1c.1: bridge 32bit mmio: [0xf8000000-0xf9ffffff]
    pci 0000:00:1c.1: bridge 64bit mmio pref: [0xf2000000-0xf3ffffff]
    pci 0000:06:00.0: reg 10 32bit mmio: [0xfa000000-0xfa000fff]
    pci 0000:06:00.0: PME# supported from D0 D3hot D3cold
    pci 0000:06:00.0: PME# disabled
    pci 0000:00:1c.2: bridge io port: [0x5000-0x5fff]
    pci 0000:00:1c.2: bridge 32bit mmio: [0xfa000000-0xfbffffff]
    pci 0000:00:1c.2: bridge 64bit mmio pref: [0xf4000000-0xf5ffffff]
    pci 0000:08:00.0: reg 10 64bit mmio: [0xfc000000-0xfc003fff]
    pci 0000:08:00.0: reg 18 io port: [0x6000-0x60ff]
    pci 0000:08:00.0: supports D1 D2
    pci 0000:08:00.0: PME# supported from D0 D1 D2 D3hot D3cold
    pci 0000:08:00.0: PME# disabled
    pci 0000:00:1c.4: bridge io port: [0x6000-0x6fff]
    pci 0000:00:1c.4: bridge 32bit mmio: [0xfc000000-0xfc0fffff]
    pci 0000:09:03.0: reg 10 32bit mmio: [0xfc100000-0xfc100fff]
    pci 0000:09:03.0: supports D1 D2
    pci 0000:09:03.0: PME# supported from D0 D1 D2 D3hot D3cold
    pci 0000:09:03.0: PME# disabled
    pci 0000:09:03.1: reg 10 32bit mmio: [0xfc102000-0xfc1027ff]
    pci 0000:09:03.1: reg 14 32bit mmio: [0xfc104000-0xfc107fff]
    pci 0000:09:03.1: supports D1 D2
    pci 0000:09:03.1: PME# supported from D0 D1 D2 D3hot D3cold
    pci 0000:09:03.1: PME# disabled
    pci 0000:09:03.2: reg 10 32bit mmio: [0xfc101000-0xfc101fff]
    pci 0000:09:03.2: supports D1 D2
    pci 0000:09:03.2: PME# supported from D0 D1 D2 D3hot
    pci 0000:09:03.2: PME# disabled
    pci 0000:00:1e.0: transparent bridge
    pci 0000:00:1e.0: bridge 32bit mmio: [0xfc100000-0xfc1fffff]
    pci_bus 0000:00: on NUMA node 0
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEGP._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP01._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP02._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP03._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP05._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIB._PRT]
    ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 *5 6 7 10 12 14 15)
    ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 7 11 12 14 15) *10
    ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 *7 10 12 14 15)
    ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 11 12 14 15) *10
    ACPI: PCI Interrupt Link [LNKE] (IRQs 1 3 4 5 6 7 10 12 14 15) *0, disabled.
    ACPI: PCI Interrupt Link [LNKF] (IRQs 1 3 4 5 6 7 *11 12 14 15)
    ACPI: PCI Interrupt Link [LNKG] (IRQs 1 3 4 5 6 7 10 12 14 15) *11
    ACPI: PCI Interrupt Link [LNKH] (IRQs 1 3 4 5 6 7 11 12 14 15) *10
    PCI: Using ACPI for IRQ routing
    NetLabel: Initializing
    NetLabel: domain hash size = 128
    NetLabel: protocols = UNLABELED CIPSOv4
    NetLabel: unlabeled traffic allowed by default
    Switched to high resolution mode on CPU 0
    Switched to high resolution mode on CPU 1
    pnp: PnP ACPI init
    ACPI: bus type pnp registered
    pnp: PnP ACPI: found 10 devices
    ACPI: ACPI bus type pnp unregistered
    system 00:01: iomem range 0xfed1c000-0xfed1ffff has been reserved
    system 00:01: iomem range 0xfed14000-0xfed17fff has been reserved
    system 00:01: iomem range 0xfed18000-0xfed18fff has been reserved
    system 00:01: iomem range 0xfed19000-0xfed19fff has been reserved
    system 00:01: iomem range 0xe0000000-0xefffffff has been reserved
    system 00:01: iomem range 0xfed20000-0xfed3ffff has been reserved
    system 00:01: iomem range 0xfed40000-0xfed44fff has been reserved
    system 00:01: iomem range 0xfed45000-0xfed8ffff has been reserved
    system 00:04: iomem range 0xfed00000-0xfed003ff has been reserved
    system 00:06: ioport range 0x680-0x69f has been reserved
    system 00:06: ioport range 0x800-0x80f has been reserved
    system 00:06: ioport range 0x1000-0x107f has been reserved
    system 00:06: ioport range 0x1180-0x11bf has been reserved
    system 00:06: ioport range 0x1640-0x164f has been reserved
    system 00:06: ioport range 0xfe00-0xfe7f has been reserved
    system 00:06: ioport range 0xfe80-0xfeff has been reserved
    pci 0000:01:00.0: BAR 6: can't allocate mem resource [0xe0000000-0xdfffffff]
    pci 0000:00:01.0: PCI bridge, secondary bus 0000:01
    pci 0000:00:01.0: IO window: 0x2000-0x2fff
    pci 0000:00:01.0: MEM window: 0xcc000000-0xceffffff
    pci 0000:00:01.0: PREFETCH window: 0x000000d0000000-0x000000dfffffff
    pci 0000:00:1c.0: PCI bridge, secondary bus 0000:02
    pci 0000:00:1c.0: IO window: 0x3000-0x3fff
    pci 0000:00:1c.0: MEM window: 0xf6000000-0xf7ffffff
    pci 0000:00:1c.0: PREFETCH window: 0x000000f0000000-0x000000f1ffffff
    pci 0000:00:1c.1: PCI bridge, secondary bus 0000:04
    pci 0000:00:1c.1: IO window: 0x4000-0x4fff
    pci 0000:00:1c.1: MEM window: 0xf8000000-0xf9ffffff
    pci 0000:00:1c.1: PREFETCH window: 0x000000f2000000-0x000000f3ffffff
    pci 0000:00:1c.2: PCI bridge, secondary bus 0000:06
    pci 0000:00:1c.2: IO window: 0x5000-0x5fff
    pci 0000:00:1c.2: MEM window: 0xfa000000-0xfbffffff
    pci 0000:00:1c.2: PREFETCH window: 0x000000f4000000-0x000000f5ffffff
    pci 0000:00:1c.4: PCI bridge, secondary bus 0000:08
    pci 0000:00:1c.4: IO window: 0x6000-0x6fff
    pci 0000:00:1c.4: MEM window: 0xfc000000-0xfc0fffff
    pci 0000:00:1c.4: PREFETCH window: disabled
    pci 0000:09:03.0: CardBus bridge, secondary bus 0000:0a
    pci 0000:09:03.0: IO window: 0x007000-0x0070ff
    pci 0000:09:03.0: IO window: 0x007400-0x0074ff
    pci 0000:09:03.0: PREFETCH window: 0x88000000-0x8bffffff
    pci 0000:09:03.0: MEM window: 0x90000000-0x93ffffff
    pci 0000:00:1e.0: PCI bridge, secondary bus 0000:09
    pci 0000:00:1e.0: IO window: 0x7000-0x7fff
    pci 0000:00:1e.0: MEM window: 0xfc100000-0xfc1fffff
    pci 0000:00:1e.0: PREFETCH window: 0x00000088000000-0x0000008bffffff
    pci 0000:00:01.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    pci 0000:00:01.0: setting latency timer to 64
    pci 0000:00:1c.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    pci 0000:00:1c.0: setting latency timer to 64
    pci 0000:00:1c.1: PCI INT B -> GSI 16 (level, low) -> IRQ 16
    pci 0000:00:1c.1: setting latency timer to 64
    pci 0000:00:1c.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
    pci 0000:00:1c.2: setting latency timer to 64
    pci 0000:00:1c.4: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    pci 0000:00:1c.4: setting latency timer to 64
    pci 0000:00:1e.0: setting latency timer to 64
    pci 0000:09:03.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    pci_bus 0000:00: resource 0 io: [0x00-0xffff]
    pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffffffffffff]
    pci_bus 0000:01: resource 0 io: [0x2000-0x2fff]
    pci_bus 0000:01: resource 1 mem: [0xcc000000-0xceffffff]
    pci_bus 0000:01: resource 2 pref mem [0xd0000000-0xdfffffff]
    pci_bus 0000:02: resource 0 io: [0x3000-0x3fff]
    pci_bus 0000:02: resource 1 mem: [0xf6000000-0xf7ffffff]
    pci_bus 0000:02: resource 2 pref mem [0xf0000000-0xf1ffffff]
    pci_bus 0000:04: resource 0 io: [0x4000-0x4fff]
    pci_bus 0000:04: resource 1 mem: [0xf8000000-0xf9ffffff]
    pci_bus 0000:04: resource 2 pref mem [0xf2000000-0xf3ffffff]
    pci_bus 0000:06: resource 0 io: [0x5000-0x5fff]
    pci_bus 0000:06: resource 1 mem: [0xfa000000-0xfbffffff]
    pci_bus 0000:06: resource 2 pref mem [0xf4000000-0xf5ffffff]
    pci_bus 0000:08: resource 0 io: [0x6000-0x6fff]
    pci_bus 0000:08: resource 1 mem: [0xfc000000-0xfc0fffff]
    pci_bus 0000:09: resource 0 io: [0x7000-0x7fff]
    pci_bus 0000:09: resource 1 mem: [0xfc100000-0xfc1fffff]
    pci_bus 0000:09: resource 2 pref mem [0x88000000-0x8bffffff]
    pci_bus 0000:09: resource 3 io: [0x00-0xffff]
    pci_bus 0000:09: resource 4 mem: [0x000000-0xffffffffffffffff]
    pci_bus 0000:0a: resource 0 io: [0x7000-0x70ff]
    pci_bus 0000:0a: resource 1 io: [0x7400-0x74ff]
    pci_bus 0000:0a: resource 2 pref mem [0x88000000-0x8bffffff]
    pci_bus 0000:0a: resource 3 mem: [0x90000000-0x93ffffff]
    NET: Registered protocol family 2
    IP route cache hash table entries: 65536 (order: 7, 524288 bytes)
    TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
    TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
    TCP: Hash tables configured (established 262144 bind 65536)
    TCP reno registered
    NET: Registered protocol family 1
    Unpacking initramfs...
    Freeing initrd memory: 2743k freed
    Simple Boot Flag at 0x36 set to 0x1
    Scanning for low memory corruption every 60 seconds
    audit: initializing netlink socket (disabled)
    type=2000 audit(1249997463.944:1): initialized
    VFS: Disk quotas dquot_6.5.2
    Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
    msgmni has been set to 4017
    alg: No test for stdrng (krng)
    Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
    io scheduler noop registered
    io scheduler anticipatory registered
    io scheduler deadline registered
    io scheduler cfq registered (default)
    pci 0000:01:00.0: Boot video device
    pcieport-driver 0000:00:01.0: irq 24 for MSI/MSI-X
    pcieport-driver 0000:00:01.0: setting latency timer to 64
    pcieport-driver 0000:00:1c.0: irq 25 for MSI/MSI-X
    pcieport-driver 0000:00:1c.0: setting latency timer to 64
    pcieport-driver 0000:00:1c.1: irq 26 for MSI/MSI-X
    pcieport-driver 0000:00:1c.1: setting latency timer to 64
    pcieport-driver 0000:00:1c.2: irq 27 for MSI/MSI-X
    pcieport-driver 0000:00:1c.2: setting latency timer to 64
    pcieport-driver 0000:00:1c.4: irq 28 for MSI/MSI-X
    pcieport-driver 0000:00:1c.4: setting latency timer to 64
    vesafb: framebuffer at 0xcd000000, mapped to 0xffffc20010100000, using 8000k, total 14336k
    vesafb: mode is 1280x800x32, linelength=5120, pages=1
    vesafb: scrolling: redraw
    vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
    Console: switching to colour frame buffer device 160x50
    fb0: VESA VGA frame buffer device
    Linux agpgart interface v0.103
    Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    input: Macintosh mouse button emulation as /devices/virtual/input/input0
    PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
    i8042.c: Detected active multiplexing controller, rev 1.1.
    serio: i8042 KBD port at 0x60,0x64 irq 1
    serio: i8042 AUX0 port at 0x60,0x64 irq 12
    serio: i8042 AUX1 port at 0x60,0x64 irq 12
    serio: i8042 AUX2 port at 0x60,0x64 irq 12
    serio: i8042 AUX3 port at 0x60,0x64 irq 12
    mice: PS/2 mouse device common for all mice
    cpuidle: using governor ladder
    cpuidle: using governor menu
    TCP cubic registered
    NET: Registered protocol family 17
    registered taskstats version 1
    Initalizing network drop monitor service
    Freeing unused kernel memory: 464k freed
    SCSI subsystem initialized
    libata version 3.00 loaded.
    pata_acpi 0000:00:1f.1: PCI INT A -> GSI 19 (level, low) -> IRQ 19
    pata_acpi 0000:00:1f.1: setting latency timer to 64
    pata_acpi 0000:00:1f.1: PCI INT A disabled
    ahci 0000:00:1f.2: version 3.0
    ahci 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
    ahci 0000:00:1f.2: irq 29 for MSI/MSI-X
    ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 3 ports 3 Gbps 0x7 impl SATA mode
    ahci 0000:00:1f.2: flags: 64bit ncq sntf pm led clo pio slum part
    ahci 0000:00:1f.2: setting latency timer to 64
    scsi0 : ahci
    scsi1 : ahci
    scsi2 : ahci
    ata1: SATA max UDMA/133 abar m2048@0xfc404000 port 0xfc404100 irq 29
    ata2: SATA max UDMA/133 abar m2048@0xfc404000 port 0xfc404180 irq 29
    ata3: SATA max UDMA/133 abar m2048@0xfc404000 port 0xfc404200 irq 29
    input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
    ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    ata2: SATA link down (SStatus 0 SControl 300)
    ata3: SATA link down (SStatus 0 SControl 300)
    ata1.00: ACPI cmd ef/90:03:00:00:00:a0 succeeded
    ata1.00: ACPI cmd f5/00:00:00:00:00:a0 filtered out
    ata1.00: ATA-7: FUJITSU MHV2200BT, 0000004F, max UDMA/100
    ata1.00: 390721968 sectors, multi 16: LBA48 NCQ (depth 31/32)
    ata1.00: ACPI cmd ef/90:03:00:00:00:a0 succeeded
    ata1.00: ACPI cmd f5/00:00:00:00:00:a0 filtered out
    ata1.00: configured for UDMA/100
    scsi 0:0:0:0: Direct-Access ATA FUJITSU MHV2200B 0000 PQ: 0 ANSI: 5
    ata_piix 0000:00:1f.1: version 2.13
    ata_piix 0000:00:1f.1: PCI INT A -> GSI 19 (level, low) -> IRQ 19
    ata_piix 0000:00:1f.1: setting latency timer to 64
    scsi3 : ata_piix
    scsi4 : ata_piix
    ata4: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0x18a0 irq 14
    ata5: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x18a8 irq 15
    ata4.00: ATAPI: MATSHITABD-MLT UJ-220V, 1.00, max UDMA/33
    ata4.00: configured for UDMA/33
    scsi 3:0:0:0: CD-ROM MATSHITA BD-MLT UJ-220V 1.00 PQ: 0 ANSI: 5
    Driver 'sd' needs updating - please use bus_type methods
    sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors: (200 GB/186 GiB)
    sd 0:0:0:0: [sda] Write Protect is off
    sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
    sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 >
    sd 0:0:0:0: [sda] Attached SCSI disk
    device-mapper: uevent: version 1.0.3
    device-mapper: ioctl: 4.14.0-ioctl (2008-04-23) initialised: [email protected]
    Intel AES-NI instructions are not detected.
    kjournald starting. Commit interval 5 seconds
    EXT3-fs: mounted filesystem with writeback data mode.
    rtc_cmos 00:07: RTC can wake from S4
    rtc_cmos 00:07: rtc core: registered rtc_cmos as rtc0
    rtc0: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
    udev: starting version 141
    sky2 driver version 1.22
    sky2 0000:08:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    sky2 0000:08:00.0: setting latency timer to 64
    sky2 0000:08:00.0: Yukon-2 FE chip revision 1
    sky2 0000:08:00.0: irq 30 for MSI/MSI-X
    sky2 eth0: addr 00:13:a9:c1:09:33
    cfg80211: Calling CRDA to update world regulatory domain
    sd 0:0:0:0: Attached scsi generic sg0 type 0
    scsi 3:0:0:0: Attached scsi generic sg1 type 5
    ACPI: AC Adapter [ADP1] (on-line)
    input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input2
    ACPI: Lid Switch [LID0]
    input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input3
    ACPI: Power Button [PWRB]
    ACPI: SSDT 000000007fedb8e7 0027A (v01 Sony VAIO 20070418 PTL 20050624)
    ACPI: SSDT 000000007fedb3b8 004AA (v01 Sony VAIO 20070418 PTL 20050624)
    ACPI Warning (processor_throttling-0843): Invalid throttling state, reset [20090320]
    Monitor-Mwait will be used to enter C-1 state
    Monitor-Mwait will be used to enter C-2 state
    Monitor-Mwait will be used to enter C-3 state
    Marking TSC unstable due to TSC halts in idle
    ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
    processor ACPI_CPU:00: registered as cooling_device0
    ACPI: Processor [CPU0] (supports 8 throttling states)
    ACPI: SSDT 000000007fedbb61 000C8 (v01 Sony VAIO 20070418 PTL 20050624)
    ACPI: SSDT 000000007fedb862 00085 (v01 Sony VAIO 20070418 PTL 20050624)
    ACPI Warning (processor_throttling-0843): Invalid throttling state, reset [20090320]
    ACPI: CPU1 (power states: C1[C1] C2[C2] C3[C3])
    processor ACPI_CPU:01: registered as cooling_device1
    ACPI: Processor [CPU1] (supports 8 throttling states)
    thermal LNXTHERM:01: registered as thermal_zone0
    ACPI: Thermal Zone [TZ00] (58 C)
    input: PC Speaker as /devices/platform/pcspkr/input/input4
    sony-laptop: Sony Notebook Control Driver v0.6.
    input: Sony Vaio Keys as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:29/SNY5001:00/input/input5
    input: Sony Vaio Jogdial as /devices/virtual/input/input6
    ACPI: Invalid active0 threshold
    iTCO_vendor_support: vendor-support=0
    thermal LNXTHERM:02: registered as thermal_zone1
    ACPI: Thermal Zone [TZ01] (58 C)
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    usbcore: registered new device driver usb
    ACPI: Battery Slot [BAT0] (battery present)
    i801_smbus 0000:00:1f.3: PCI INT C -> GSI 19 (level, low) -> IRQ 19
    ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 18 (level, low) -> IRQ 18
    ehci_hcd 0000:00:1a.7: setting latency timer to 64
    ehci_hcd 0000:00:1a.7: EHCI Host Controller
    ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1
    ehci_hcd 0000:00:1a.7: debug port 1
    ehci_hcd 0000:00:1a.7: cache line size of 32 is not supported
    ehci_hcd 0000:00:1a.7: irq 18, io mem 0xfc404800
    ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00
    usb usb1: configuration #1 chosen from 1 choice
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 4 ports detected
    ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23
    ehci_hcd 0000:00:1d.7: setting latency timer to 64
    ehci_hcd 0000:00:1d.7: EHCI Host Controller
    ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2
    ehci_hcd 0000:00:1d.7: debug port 1
    ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported
    ehci_hcd 0000:00:1d.7: irq 23, io mem 0xfc404c00
    ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
    usb usb2: configuration #1 chosen from 1 choice
    hub 2-0:1.0: USB hub found
    hub 2-0:1.0: 6 ports detected
    uhci_hcd: USB Universal Host Controller Interface driver
    uhci_hcd 0000:00:1a.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    uhci_hcd 0000:00:1a.0: setting latency timer to 64
    uhci_hcd 0000:00:1a.0: UHCI Host Controller
    uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3
    uhci_hcd 0000:00:1a.0: irq 16, io base 0x00001800
    usb usb3: configuration #1 chosen from 1 choice
    hub 3-0:1.0: USB hub found
    hub 3-0:1.0: 2 ports detected
    uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21
    uhci_hcd 0000:00:1a.1: setting latency timer to 64
    uhci_hcd 0000:00:1a.1: UHCI Host Controller
    uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4
    uhci_hcd 0000:00:1a.1: irq 21, io base 0x00001820
    usb usb4: configuration #1 chosen from 1 choice
    hub 4-0:1.0: USB hub found
    hub 4-0:1.0: 2 ports detected
    uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
    uhci_hcd 0000:00:1d.0: setting latency timer to 64
    uhci_hcd 0000:00:1d.0: UHCI Host Controller
    uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 5
    uhci_hcd 0000:00:1d.0: irq 23, io base 0x00001840
    usb usb5: configuration #1 chosen from 1 choice
    hub 5-0:1.0: USB hub found
    hub 5-0:1.0: 2 ports detected
    uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
    uhci_hcd 0000:00:1d.1: setting latency timer to 64
    uhci_hcd 0000:00:1d.1: UHCI Host Controller
    uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 6
    uhci_hcd 0000:00:1d.1: irq 19, io base 0x00001860
    usb usb6: configuration #1 chosen from 1 choice
    hub 6-0:1.0: USB hub found
    hub 6-0:1.0: 2 ports detected
    uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
    uhci_hcd 0000:00:1d.2: setting latency timer to 64
    uhci_hcd 0000:00:1d.2: UHCI Host Controller
    uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 7
    uhci_hcd 0000:00:1d.2: irq 18, io base 0x00001880
    usb usb7: configuration #1 chosen from 1 choice
    hub 7-0:1.0: USB hub found
    hub 7-0:1.0: 2 ports detected
    input: PS/2 Mouse as /devices/platform/i8042/serio4/input/input7
    input: AlpsPS/2 ALPS GlidePoint as /devices/platform/i8042/serio4/input/input8
    usb 1-2: new high speed USB device using ehci_hcd and address 2
    usb 1-2: configuration #1 chosen from 1 choice
    usb 2-3: new high speed USB device using ehci_hcd and address 3
    nvidia: module license 'NVIDIA' taints kernel.
    Disabling lock debugging due to kernel taint
    iTCO_wdt: Intel TCO WatchDog Timer Driver v1.05
    iTCO_wdt: Found a ICH8M TCO device (Version=2, TCOBASE=0x1060)
    iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
    yenta_cardbus 0000:09:03.0: CardBus bridge found [104d:9005]
    yenta_cardbus 0000:09:03.0: Using CSCINT to route CSC interrupts to PCI
    yenta_cardbus 0000:09:03.0: Routing CardBus interrupts to PCI
    yenta_cardbus 0000:09:03.0: TI: mfunc 0x01121b22, devctl 0x64
    usb 2-3: configuration #1 chosen from 1 choice
    nvidia 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    nvidia 0000:01:00.0: setting latency timer to 64
    NVRM: loading NVIDIA UNIX x86_64 Kernel Module 185.18.31 Tue Jul 28 17:52:27 PDT 2009
    yenta_cardbus 0000:09:03.0: ISA IRQ mask 0x0cf8, PCI irq 16
    yenta_cardbus 0000:09:03.0: Socket status: 30000006
    pci_bus 0000:09: Raising subordinate bus# of parent bus (#09) from #0a to #0d
    yenta_cardbus 0000:09:03.0: pcmcia: parent PCI bridge I/O window: 0x7000 - 0x7fff
    yenta_cardbus 0000:09:03.0: pcmcia: parent PCI bridge Memory window: 0xfc100000 - 0xfc1fffff
    yenta_cardbus 0000:09:03.0: pcmcia: parent PCI bridge Memory window: 0x88000000 - 0x8bffffff
    iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26ks
    iwl3945: Copyright(c) 2003-2009 Intel Corporation
    iwl3945 0000:06:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
    iwl3945 0000:06:00.0: setting latency timer to 64
    ohci1394 0000:09:03.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
    Driver 'sr' needs updating - please use bus_type methods
    sr0: scsi3-mmc drive: 62x/62x writer dvd-ram cd/rw xa/form2 cdda tray
    Uniform CD-ROM driver Revision: 3.20
    sr 3:0:0:0: Attached scsi CD-ROM sr0
    ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[17] MMIO=[fc102000-fc1027ff] Max Packet=[2048] IR/IT contexts=[4/8]
    tifm_7xx1 0000:09:03.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
    HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
    HDA Intel 0000:00:1b.0: setting latency timer to 64
    hub 2-0:1.0: unable to enumerate USB device on port 5
    iwl3945 0000:06:00.0: Tunable channels: 13 802.11bg, 23 802.11a channels
    iwl3945 0000:06:00.0: Detected Intel Wireless WiFi Link 3945ABG
    iwl3945 0000:06:00.0: irq 31 for MSI/MSI-X
    Initializing USB Mass Storage driver...
    scsi5 : SCSI emulation for USB Mass Storage devices
    usbcore: registered new interface driver usb-storage
    USB Mass Storage support registered.
    usb-storage: device found at 3
    usb-storage: waiting for device to settle before scanning
    input: HDA Intel Mic at Ext Left Jack as /devices/pci0000:00/0000:00:1b.0/input/input9
    input: HDA Intel HP Out at Ext Left Jack as /devices/pci0000:00/0000:00:1b.0/input/input10
    usb 5-1: new low speed USB device using uhci_hcd and address 2
    usbcore: registered new interface driver hiddev
    Linux video capture interface: v2.00
    input: Western Digital My Book as /devices/pci0000:00/0000:00:1d.7/usb2/2-3/2-3:1.1/input/input11
    generic-usb 0003:1058:1102.0001: input,hidraw0: USB HID v1.11 Device [Western Digital My Book] on usb-0000:00:1d.7-3/input1
    usbcore: registered new interface driver usbhid
    usbhid: v2.6:USB HID core driver
    uvcvideo: Found UVC 1.00 device <unnamed> (05ca:1837)
    uvcvideo: UVC non compliance - GET_DEF(PROBE) not supported. Enabling workaround.
    uvcvideo: Failed to query (129) UVC probe control : -32 (exp. 26).
    uvcvideo: Failed to initialize the device (-5).
    usbcore: registered new interface driver uvcvideo
    USB Video Class driver (v0.1.0)
    phy0: Selected rate control algorithm 'iwl-3945-rs'
    usb 5-1: configuration #1 chosen from 1 choice
    input: Logitech USB Receiver as /devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.0/input/input12
    generic-usb 0003:046D:C518.0002: input,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:1d.0-1/input0
    input: Logitech USB Receiver as /devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.1/input/input13
    generic-usb 0003:046D:C518.0003: input,hiddev0,hidraw2: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:1d.0-1/input1
    fuse init (API version 7.11)
    vboxdrv: Trying to deactivate the NMI watchdog permanently...
    vboxdrv: Successfully done.
    vboxdrv: Found 2 processor cores.
    VBoxDrv: dbg - g_abExecMemory=ffffffffa0f05760
    vboxdrv: fAsync=0 offMin=0x1ae offMax=0x125c
    vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
    vboxdrv: Successfully loaded version 3.0.4 (interface 0x000e0000).
    VBoxNetFlt: dbg - g_abExecMemory=ffffffffa10a9f00
    hub 2-0:1.0: unable to enumerate USB device on port 5
    ieee1394: Host added: ID:BUS[0-00:1023] GUID[0800460302564f69]
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    Clocksource tsc unstable (delta = -435934901 ns)
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    EXT3 FS on dm-0, internal journal
    scsi 5:0:0:0: Direct-Access WD My Book 1028 PQ: 0 ANSI: 4
    sd 5:0:0:0: Attached scsi generic sg2 type 0
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    sd 5:0:0:0: [sdb] 625142448 512-byte hardware sectors: (320 GB/298 GiB)
    sd 5:0:0:0: [sdb] Write Protect is off
    sd 5:0:0:0: [sdb] Mode Sense: 10 00 00 00
    sd 5:0:0:0: [sdb] Assuming drive cache: write through
    usb-storage: device scan complete
    sd 5:0:0:0: [sdb] Assuming drive cache: write through
    sdb: sdb1
    sd 5:0:0:0: [sdb] Attached SCSI disk
    EXT4-fs: barriers enabled
    kjournald2 starting: pid 1929, dev dm-1:8, commit interval 5 seconds
    EXT4 FS on dm-1, internal journal on dm-1:8
    EXT4-fs: delayed allocation enabled
    EXT4-fs: file extents enabled
    EXT4-fs: mballoc enabled
    EXT4-fs: mounted filesystem dm-1 with ordered data mode
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    Adding 2449872k swap on /dev/sda6. Priority:-1 extents:1 across:2449872k
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    iwl3945 0000:06:00.0: firmware: requesting iwlwifi-3945-2.ucode
    hub 2-0:1.0: unable to enumerate USB device on port 5
    iwl3945 0000:06:00.0: loaded firmware version 15.32.2.9
    Registered led device: iwl-phy0::radio
    Registered led device: iwl-phy0::assoc
    Registered led device: iwl-phy0::RX
    Registered led device: iwl-phy0::TX
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    wlan0: authenticate with AP 00:11:6b:10:2f:bc
    wlan0: authenticated
    wlan0: associate with AP 00:11:6b:10:2f:bc
    wlan0: RX AssocResp from 00:11:6b:10:2f:bc (capab=0x471 status=0 aid=1)
    wlan0: associated
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    hub 2-0:1.0: unable to enumerate USB device on port 5
    i think the result is, that my bluetooth and webcam isn't working...
    can you help me pls.
    regards nigg
    Last edited by nigg (2009-08-11 14:14:57)

    I'm also having this problem. It's happening with my USB flash disk. I was almost buying another one when I tried it with Windows Vista on the same machine and it worked ok, then I tried Arch Linux (with kernel 2.6.30.5) on another machine and got the same error. After that I tried Ubuntu and it worked ok. Seems that Arch's kernel doesn't like my USB flash disk.
    Last edited by esdrasbeleza (2009-09-02 01:16:09)

  • Problems with usb / sd removable devices (not/badly copying)

    Hi everybody
    the problem is when I plug an usb stick or a SD card, all with FAT32 fs, GNOME (I use gnome-shell) asks me if I want to mount and open the device.
    so, it loads properly and when it's open I can do all the things you are supposed to do with them.
    The issue first appaired when I copied some pics to an SD card. It appaired the progress bar saying it completed the copy process.
    So I umounted the device and removed it. Some other people said that actually there weren't any files in the SD card.
    Supposing it was bad/corrupted fs I formatted the card and put back the images there. Same issue. I was starting to think the SD card was damaged
    until I had the same problem while copying music to my phone (via USB cable).
    I noticed it created all the files but didn't store any actual data (e.g. size of files was always 0 byte) or even didn't do anything (neither created the file) sometimes.
    Searching the web I found that it wasn't syncing - so they told me to do the sync command on the shell - nothing solved.
    So as I read on the wiki [fstab], I mounted the devices with options "sync,flush", which in fact solved the problem.
    [Actually I later found that it works even without the flush option, just with the sync option]
    Doing so I solved the problem and could copy all the data to the devices.
    What I want to know is: how can I say to GNOME (or anyother GNOME uses to mount devices) "well, whenever I put a removable device, mount it with the sync option" ?
    thank you in advance,
    azzka
    PS: [not so important]: I noticed very slow copying bitrate, and I did what the wiki says about but didn't solve anything. Any ideas?

    Yep HV,
    Verify the discs in the disc utility and see if that works. It'll probably take an hour or so cos the disc utility's performance has been less than favorable.
    Try this: Turn off the computer, disconnect the drives, then restart the computer. Now, re-connect the drives while the computer is running, let them mount and see if you can eject them. One would assume it is a permissions issue, however, with the multitude of glitches appearing with ext drives and USB devices in Leopard it's hard to assume anything.
    Persevere!

  • Continuing import problem with USB cameras.

    In other threads people have discussed problems they are having with iMovie 7.1.1 in importing with USB cameras. I have had the same experience with my Sony CX-7 on two different MacBook Pros including a brand new one. Once in a while the camera will trigger the import page but usually not. Is this a bug Apple is aware of and working on?? Other suggestions for a fix or work around. Very frustrating.

    Hmmm... I think there might be some sort of bug with the app regarding USB port connections. iMovie wouldn't even launch for me until I disconnected my 2 external drives. However, it seems that when I mount the external HD that's connected via firewire, iMovie is able to launch. But when it's the other external drive that's connected via USB that's mounted, that's when iMovie won't even open... And the weirdest thing is that, when the external HD that's mounted via USB is connected, just as you think the app has launched correctly, it sort of brings up an error message box that I can't even read for it just crashes immediately...

Maybe you are looking for