Micro USB not working on 9300

I got yesterday the two Duracell cell USB chargers ( Instant and PowerHouse) and it is very funny but I can not charge my blackberry. I used obviously the micro USB, try different cables, lenghts, etc...and there is no way to charge it. Even a friend of mine has a Torch and it did charge either.... It charges my kindle, Droid;( all of them micro USB) but no the curve 9300 Any experience with the Duracell or other usb micro chargers othe than BB?

Might not be the answer you are looking for but I have used my BB USB cable on other phones like Nokia 2700, E63 with no problem, USB cables usually come as a standard so they should work on multiple devices. I dont think the USB chargers you have are made differently. One thing I know for sure is that if the battery is drained to 0% then USB charging will not work. I will look around and try another cable type and see if it does not work.

Similar Messages

Is it possible that i download an older version of firefox, mainly version 4. trend micro does not work with version 5 yet

is it possible to download firefox version 4, because trend micro does not work with version 5 yet

Yes you can download them at Firefox's Archive on just chose your os
url:
http://releases.mozilla.org/pub/mozilla.org/firefox/releases/4.0/

Trend Micro will not work with Firefox 9.0.1

With the latest upgrade (again) of Firefox 9.0.1 Trend Micro will not work and cannot be enabled. I use Trend Micro Titanium Maximum 2012. This feature worked fine before the latest upgrade. Why can't Firefox at least try to beta test their latest and greatest before problems like this happen?
Trend Micro BEP Firefox Extension7.0.0.1086false{38783831-6098-4faa-A9C9-1EE1E343F4D2}Trend Micro NSC Firefox Extension6.8.0.1066false{22C7F6C6-8D67-4534-92B5-529A0EC09405}Trend Micro Toolbar5.0.0.1361false{22181a4d-af90-4ca3-a569-faed9118d6bc}

Perform the suggestions mentioned in the following TrendMicro Community post:
* [http://esupport.trendmicro.com/solution/en-us/1059975.aspx]
Check and tell if its working.

Zen Micro Photo not working with new XP SP2 install

Okay so my Zen Micro Photo stopped being recognised on my computer about ten months ago when I upgraded to WMP (for BBC iPlayer - it's compulsory to have it). Anyway I li'ved with this and have now got thoroughly sick of the same songs and nothing new so I have done a fresh install (on a brand new hard dri've) of Windows XP SP2 WMP9 with the sole intention of using this install/hard dri've?for the player. I used the original installation disk and it prompted me to upgrade to WMP0 as I installed everything. There were no errors during the install and I rebooted when prompted to.
When I attach the player it is recognised by the machine (task bar icon and correctly labelled in System > Hardware > Device Manager which reports it to be?working okay) but the Creative media software says "player not attached" when it is. It is not visible on My Computer as a dri've so I STILL have no access to the player. Player screen reports "docked" with a logo and is flashes a charging icon. Driver v5.2.0.0. The player plays fine but hasn't had new music on in almost a year
There is nothing else on the XP install (IE6 and everything - argh!) I did the registry permission tweak thing mentioned?here:?http://support.creative.com/kb/showa....aspx?sid=9287?but it didn't do anything.
Any help greatfully received!

Re: Zen Micro Photo not working with new XP SP2 install. Have you installed this plug-in?
Creative PlaysForSure Devices Plugin 5.00.36 for Creative MediaSource 5 Player/Organizer
Filesize : 27.9 MBDownload

Bluetooth AND USB not working

Hi friends i'm facing 2 problems1. my bluetooth is not working properly, initially it wont show any blutooth icon when i start up, but after i restart it shows and start working, every time i need to repeat this to use bluetooth. kindly suggest me the solution.2. the usb ports (3.0 and2.0) both doesnt work properly, they only detect devices wen i go to device manager and scan for hardware devices.

I was also worried that bluetooth is not working. But eventually came to know that this model 15R203TX has bluetooth version 4.0 which is backward compatible to other bluetooth devices of version 2.0 to 2.1 EDR. Means if your hand set or any bluetooth device is having version 2.0 or 2.1 EDR it won't able to send any data or see this laptop model while transferring data. Moreover if you try to send data from laptop to other bluetooth device irrespective of version it is able to send data. Now it is Same with WiFi this model is backward compatible to IEEE 802.11 a/b/g. means you can't receive signals from this devices unless the router is having IEEE 802.11 b/g/n/ac. For USB not working may be its a BIOS issue. While boot up try to press F2 key. And enter the diagonistic blue page. There you can check the version of BIOS or try to reinstall the updated BIOS by downloading it from HP support. If USB still not woking then try to go to nearest authorised HP service centre.

I bought Hp 15 g207ax, 2 out of 3 usb not working, and all drivers missing, no ethernet or no wifi

i bought a new Hp 15 G207AX.
issue 1 - 2 out of 3 usb not working, 1 usb 3.0 and 1 usb2.0 not working. 1 usb 2.0 is working properly
question 1- is it because of faulty laptop or driver issue? also, if it is driver issue, then why 1 usb 2.0 is working?
issue 2 - All Drivers are missing.
question 2 - where can i find all the drivers?
issue 3 - no ethernet and no wifi connecting
question 3 - is there a driver for ethernet too? can you tell me what drivers i need to install for ethernet or wifi. because without those, i cant do anything?
looking for your immediate reply. as if in 1st question, if usb ports are defective and laptop is faulty, i will ask for a replacement or refund.

Likely all of these issues would be fixed with the chipset driver.
Did you look at the solutions listed in that other forum post I linked to above?
...an HP employee just trying to help where I can, but not speaking on behalf of HP.

K7T Turbo limited - USB not working

I have a K7T turbo limited edition motherboard. The rear usb ports work fine. There are two USB ports on the front which do not work. appreciate any ideas on how to clear up this problem.

https://forum-en.msi.com/index.php?threadid=52338&sid=
one to many wire is usual problem

ADC Studio Display 17" USB not working

Hi,
I hope someone can help.
I have a 17" Apple Studio Display that connects via ADC left over from my old Powermac G4. I recently bought the new Mac Mini (Unibody) and an Apple DVI to ADC Display Adapter to use with the HDMI to DVI Adapter to connect with the Apple Display.
This works perfectly however I have noticed the USB ports on the back of the display does not work. Could this be because the Apple DVI to ADC Display Adapter can not supply enough power via the connected HDMI to DVI Adapter to support the display and its USB ports? Is there a way too get them working again?
Thanks.
Chris

Hi. Thanks for that. As you say there must be something wrong with my display's USB circuitry then.
Just one more question, is the USB cable from the DVI to ADC adapter only for supplying power to the USBs on the display? Since the display's USBs are not working, will the adapter still work and power my display without using the USB connecter from this adapter? If so this will free up one of my USB2 ports on the mini.
Thanks again.

Why dosen't my micro USB cable work??

I am trying to connect my apple TV to my macbook pro using a micro usb cable, but neither the computer nor
the apple tv registers the connection, i.e. nothing happens. What am I doing wrong?

what are you trying to do?
the usb cable only works for restoring the firmware on the appletv

MSI P67A-C43 (B3) USB not working but theres a twist! Help!

:lol_anim:I Have built a new rig with the MSI P67A-C43 (B3) Motherboard, 16GB DDR3 PC3-10600 1333MHz Memory (4GB x 4), Intel Core i5-2500K 3.3GHz 6M LGA1155 Processor, 550 Watt 80 PLUS Bronze Power Supply,24x DVDRW, 3.5" Internal Card Reader with 2 USB ports, 500GB 7200RPM 3.5" SATA Hard Drive(which i plan on upgrading just didnt want to waste money on the shitty HD they had.....
So down to the nitty gritty . My computer is running Windows 7 64 Bit, i have downloaded all of the updates and all of the Chip-set drivers, Bios, etc... i ran a system registry tool to clean up any errors in my registry and i have ALL of my drivers up to date.
I have my USB mouse and keyboard that connect fine and are recognized by my computer, sometimes they stop working and start back up within seconds but windows does display any type of error or disconnection "this may have been fixed due to the registry cleaner i used i haven't had any hiccups yet" so i have my USB mouse and USB keyboard working fine and dandy now i think. got a new headset and the windows finds the USB Headset and it works Perfectly fine. BUT and this is where my whole frustration comes out. Whenever i connect my I-Pod Touch, I-Pod Nano, My Cell phone to copy files to from my SD Card, or my External My Passport drive Windows says "USB Device was not recognized" notification and in the Device manager it shows the one device with a yellow exclamation point and says "Unknown Device" I have tried to uninstall the USB hubs and reinstalled them perfectly restarted windows, still non of the devices work. i have tried making sure that windows tries not to turn off the device to save power, when i say i have tried almost everything i mean everything that is related with USB Device not Recognized. So i do not know what to do now, i have contacted the Manufacturer and they don't know squat about it or what could be causing it. the only thing i can think of is there is some hardware maybe that is not compatible i do hear some beeps when i start up i will have to come back and update how many beeps" i saw another post that it means the motherboard is trying to tell me something maybe this could be the issue. but i have tried every single usb port and non of them Recognize the device but when i plus in my mouse and keyboard in diff ports they still work so i am a bit confused. my last step is to return the computer to the manufacturer for a replacement or repair w/e i do not want to do this cause this should be working. my friend has almost the exact same MB and equipment and his works fine so i am getting a little frustrated with the issue Someone Pls Help me out. And yes i have tried turning off the computer, unplugging it and pressing the power button, and waiting like 1 Hour etc and still nothing. Drivers are Up-to-Date and Mother board bios and chip-set drivers are Up-to-Date as well. I hope someone knows or has an answer to help me out!

Yes the Bios is Up-to-Date and they are not plugged into the Blue USB 3.0 ports(x2). oh and forgot to mention already did a clean install again of Windows 7 64bit and still nothing. Im also wondering if the power supply is enough?? maybe?

Ovi Suite + 5230 USB not working

Preamble:
I recently connected my Nokia 5230 mobile phone to my PC via USB connection and loaded up Ovi Suite (2.2.1.23). Everything worked lovely. But alas! Both an Ovi suite update was available, as well as a update for the phone itself! So I downloaded the latest version of Ovi Suite (3.0.0.284).
Unfortunately, now Ovi Suite does not detect when I select "PC Suite" USB mode (selected on the phone screen). This essentially makes Ovi Suite useless.
So I followed some advice on other discussion pages (more on that later) and reinstalled the Ovi Suite. The problem persisted.
Here are some pictures to help you understand my problem:
http://i.imgur.com/5IknF.jpg
The computer is able detect the phone is connected via USB. I can even browse the contents of the phone memory and memory card. Upon detecting the connected phone, and me pressing 'PC Suite' on the phone screen, it will show this:
http://i.imgur.com/lV0rs.jpg
I cannot progress past this screen. The Ovi Suite simply does not recognise that I've selected that option on the phone.
Defense:
I know what your thinking. "Just another USB thread". Well, I did in fact read plenty of threads on this forum before posting, and have spent the last few hours uninstalling and reinstalling Ovi Suite and drivers in various ways (as suggested in those threads), with no success.
The following is a list of forum threads which I have read and tried all the solutions found in each, and I have copied the solutions (which appear to have worked for other people), for your convenience:
/t5/Nokia-Ovi-Suite/Ovi-Suite-PC-Suite-USB-Connection-Problem/td-p/682828
Solutions which did not work for me:
Could you please follow these steps and check?
1. Disconnect your phone from PC if connected.
2 .Open Control Panel and go to ‘Programs and Features’
3. From the list of available programs, choose ‘Nokia Connectivity Cable Driver’
4. Click on the ‘Change’ button on top toolbar.
5. In the setup dialog box that pops up next, choose ‘Repair’ and select ok. Wait for setup to complete.
6. Restart the computer if prompted.
7. Now connect your phone to the PC. Driver installation should complete and PC suite (hopefully) should detect your mobile properly now.
1. Uninstall all nokia related applications like Ovisuite, pc suite, connectivity cable driver,pc connectivity solutions, nokia software updater etc. from ur PC.
2. Restart your PC
3. Now download and install the recent ovisuite from http://www.ovi.com/suite
4. After installation, disconnect/disable your internet connection (this will make sure that the PC use the drivers which comes with ovisuite and prevent the PC from downloading any new drivers from internet) and then connect your mobile and wait for drivers and support software installation.
5. After drivers installation you can connect your mobile to ovisuite from ovisuite screen.
/t5/Nokia-Ovi-Suite/Can-t-connect-to-Nokia-Ovi-Suite-on-Nokia-6700/m-p/757938#M5623
Solution which did not work for me:
Hi GannonC,
Uninstall the following Programs, if any, from Control Panel -> Programs and Features or Add or Remove Programs.
Nokia Connectivity Cable Driver
Nokia Ovi Suite
PC Connectivity Solution
Later download and install the latest OVi Suite from the following location.
http://www.ovi.com/suite
After OVi Suite installation, restart your PC, disconnect your internet from PC and connect your mobile to the PC. This is to prevent the PC searching for a new drivers from internet. OVi suite has all the required drivers for all the nokia phones available in market.
Once all the required drivers are installed automatically, you try connecting the mobile by selecting 'Connect your device' from the bottom left on the OVi suite screen. You should be able to connect your device now.
After connecting you can go ahead and update your maps/ download new country maps.
NOTE: before updating your maps/ download new country maps, you should have used your maps in you mobile atleast once.
Hope this will resolve your issue.
You can connect back your internet anytime after the drivers installation.
/t5/Nokia-Ovi-Suite/OVI-suite-not-reconizing-the-OVI-suite-USB-mode-N8/m-p/809893#M7107
Solution which did not work for me:
Hi,
Please check the suggestions below:
Select Ovi Suite via Tools -> Options -> My device -> Remove this device.
Once you add the device back to Ovi Suite, Select tools -> Add device, reconfigure the Sync -> Option - device sync settings and sync again.
If it does not help:
Go to
Control Panel--> Right click and Programs and Features or add/remove programs "Repair" Nokia Ovi Suite.
Go to
Control Panel--> Programs and Features or add/remove programs - > Right click and "Repair" Nokia Connectivity cable driver & PC Connectivity solution.
If it does not help:
Uninstall the following Programs,from Control Panel -> Programs and Features or Add or Remove Programs.
Nokia Connectivity Cable Driver
Nokia Ovi Suite
PC Connectivity Solution
Later download and install the latest OVi Suite from the Nokia.com/support.
After OVi Suite installation, restart your PC, disconnect your internet from PC and connect your mobile to the PC. This is to prevent the PC searching for a new drivers from internet. OVi suite has all the required drivers for all the nokia phones available in market.
Once all the required drivers are installed automatically, you try connecting the mobile by selecting
'Connect your device' from the bottom left on the OVi suite screen. You should be able to connect your device now.
Br
Mahyav
/t5/Nokia-Ovi-Suite/E5-Ovi-Suite-keeps-telling-me-that-my-device-isn-t-in-PC-suite/m-p/856573#M7752
Solution which did not work for me:
Maarten, I had the same issue and it started after I updated Ovi Suite as well as my device software. I found this in another thread and thought it might help you. I just uninstalled the 3 items and downloaded and installed as prescribed by going to nokia.com/support and downloading and reinstalling Ovi Suite.... Merry Christmas
Re: OVI suite not reconizing the 'OVI suite USB mode 22-Nov-2010 11:36 AM
***** Select Ovi Suite via Tools -> Options -> My device -> Remove this device.
Once you add the device back to Ovi Suite, Select tools -> Add device,
reconfigure the Sync -> Option - device sync settings and sync again.
*****If it does not help:
Go to
Control Panel--> Right click and Programs and Features or add/remove programs
"Repair" Nokia Ovi Suite.
Go to
Control Panel--> Programs and Features or add/remove programs - > Right click
and "Repair" Nokia Connectivity cable driver & PC Connectivity solution.
***** If it does not help:
Uninstall the following Programs,from Control Panel -> Programs and Features or
Add or Remove Programs.
Nokia Connectivity Cable Driver
Nokia Ovi Suite
PC Connectivity Solution
Later download and install the latest OVi Suite from the Nokia.com/support.
After OVi Suite installation, restart your PC, disconnect your internet from PC and
connect your mobile to the PC. This is to prevent the PC searching for a new drivers
from internet. OVi suite has all the required drivers for all the nokia phones available
in market.
Once all the required drivers are installed automatically, you try connecting the mobile
by selecting
'Connect your device' from the bottom left on the OVi suite screen. You should be able
to connect your device now.
/t5/Nokia-Ovi-Suite/not-recognizing-USB-mode-on-E73/m-p/780655#M6383
Solution which did not work for me (simmilar to above):
frauk:
I found this on the Europe forum and it worked for me--finally!
From /t5/Nseries-and-S60-Smartphones/Synchronisation-error-code-8393f010/m-p/734155/highlight/true#M21944...
Click Start
Click Control Panel
Click Programs and Features or Add/remove Programs
Choose Nokia Nokia Cable Connectivity then Change and repair
Do the same for PC Connectivity Solution - Change then repair
Reboot computer
After re-starting the computer, I also followed this portion of a suggestion from another post (don't know if it made a difference or not):
"connected the device, waited till all the drivers were loaded.
Then launched Ovi suite"
(From /t5/Nokia-Ovi-Suite/E52-Sync-Error-8393f010-838c03ee/m-p/740481)
Ovi Suite then recognized my device and the sync appears to have gone smoothly. I hope it works for you too! It's ridiculous that it causes so many problems though--I've wasted many hours on something that should have installed correctly the first time.
Other threads with this problem, which I came across that mention the same problem with various other phones:
/t5/Nokia-Ovi-Suite/5230-won-t-establish-USB-connection-with-Ovi-Suite/td-p/824037
/t5/Nokia-Ovi-Suite/OVI-Suite-2-2-0-245-problem-recognizing-Nokia-device/m-p/719958#M4079
More data:
Now that I have shared a detailed description of my failings with you, here is some information about my phone and the Ovi suite:
Phone information (Keypad: *#0000#):
Software version
V 20.0.005
Software version date
23-03-2010
Custom version
20.0.005.C02.01
Custom version date
23-03-2010
Language set
19
Model
5230
Type
RM-588
Latest update
Not needed (<-- is this another bug Nokia? The phone regularly informs me that a update is available...)
Ovi Suite System information:
Nokia Ovi Suite 3.0.0.284
PC Connectivity Solution 10.50.2.0
Connectivity Cable Driver 7.1.36.0
Nokia Ovi Suite Software Updater 2010.44.0.60888
Maps Service API 4.0.24.1
Nokia mPlatform 2.7.44
Ovi Desktop Sync Engine 1.4.1.42
Operating system:
Microsoft Windows Vista 64-bit Edition, Service Pack 2
Language: English
Detected internet browsers:
- Microsoft Internet Explorer 8.0.6001.18999
- Mozilla Firefox 3.6.13 (Default browser)
Detected Bluetooth stacks:
- Microsoft (Version: 6.0.6000, Build: 16386), In use.
Detected USB drivers:
- Default Hub Driver for USB 6.0.6002.18005
- USB Modem Driver 6.0.6002.18005
- EHCI eUSB Miniport Driver 6.0.6002.18005
Additional information:
Windows Vista Home Premium SP2 64-bit (with all updates installed)
I have no problems with USB or drivers with another components
Zship's revelations:
So this is not really a problem for me. I have the working, older (2.2.1.23) version of Ovi Suite installed on my netbook, and sure enough, it works fine, I just tried it. I wont be updating Ovi Suite on it though. I also could probably just download the update via 3.5G using just the phone itself, but the problem remains that a simple software update has caused a critical connectivity problem between your software and hardware. Given that many Nokia customers would have less technical know-how than say, myself or anyone else on this forum, this problem is a quite likely a huge inconvenience to them, they probably wouldn't visit these discussions and spend 5 hours reinstalling software like I just did, and they surely would be thinking twice before purchasing another Nokia device in the future.
tl;dr - Nokia recommended update breaks connectivity between software and device, various attempts to fix seemingly simple problem don't work.
Solved!
Go to Solution.

SAME PROBLEM. And none of the many suggested solutions has worked for me yet. I want to thank all on this thread (and many others) for their help. I've learned a lot but I haven't gotten to the bottom of it. I think maybe Nokia needs to ... uh ... bloody well BOTHER TO FIX THIS ISSUE themselves, maybe. Like, cuz they're PAID FOR IT and I'M NOT. Harrumph.
I run Windows XP, and was on Media Player 11, but have rolled back to 9 and 10. I have a Nokia E 72. I have all the latest Nokia cable-drivers, PC Suite, OVI Suite, Connectivity software, etc.. The symptoms are as follows: when I plug in the phone by USB cable, the laptop won't recognize it. It says "USB device faulty" or "failed to load properly" and refuses to get the hardware into its brain. The Device Manager shows only a "Unknown Device" which I cannot install drivers onto. Taking the extra media-card out of the phone doesn't make any difference -- nothing I've done will make the computer recognize the main (built-in) card in the phone. I can't browse to it via any sort of populate / repopulate disk drive, or any other method of connecting it.
As I understand it, this is some conflict with the phone and the new concept of MTP. Media Transfer Protocol confuses the computer, causing it to kind-of think that the phone is kind-of a media player, when in fact it's a whole lot more. So, the "parent" doesn't get loaded, then the rest of the phone doesn't get loaded, then it kind-of tries to load some MTP but fails, etc.. If I could browse to the phone through a non-Nokia connection I'd be happy to do so in order to implement any of a number of the suggestions above. But I can't get the computer to recognize the phone when the phone is plugged in by USB, regardless of all the solutions above.
The problem began a few days ago. It just up and wouldn't recognize the phone. I hadn't installed any updates that I knew of on either item, but it's possible that my memory is faulty and a newer version of this or that snuck in there and screwed it all up. I have tried a serious roll-back to a Restore Point about six weeks old, but that didn't solve the problem. This suggests to me that the problem is phone-resident, since the rollback was to a computer-based Restore Point and I don't have phone rollback capability.
This seriously hampers me. PC Suite, OVI, and some future version of Nokia Suite, will all be useless to me unless Nokia accomplishes the stunning act of supporting their software. I won't hold my breath. Just in general, you'd think that plug-and-play of a phone into your computer would be a lot simpler. Just take the cord -- stick it in the phone; stick it in the computer -- and shazam, you're plugged in. But NOOOOOO we're on NOOOOOOKIA ... Now I know why Microsoft wanted to buy them so badly. They knew they'd all get along and have the same assumptions about software -- that it doesn't really matter whether it works reliably on a user's computer at his home, as long as it works in theory on some programmer's ideal personal computer in Seattle once in a rare while. Nokia? Meet Microsoft. Microsoft? You and Nokia will get along juuuust fiiiine ...

[SLOVED] All my USB not work after upgrade system.

Hello all,
I'm new in Arch, and i install my system with your LiveCD (2005).
In the first boot, all work good. But after upgrade (pacman -Syu), all my USB device (Keyboard, Mouse) not work.
I'm not using (yet) with Xorg, just in command shell (tty1), But i can't press anything cuz my keyboard not work.
I try to do that (https://bbs.archlinux.org/viewtopic.php … 19#p906119), but no work to me too.
What i can to do to fix this?
My dmesg:
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Linux version 2.6.33-ARCH (thomas@evey) (gcc version 4.5.0 (GCC) ) #1 SMP PREEMPT Thu May 13 11:32:37 CEST 2010
Command line: BOOT_IMAGE=/vmlinuz26 root=/dev/sdb5 ro
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009ec00 (usable)
BIOS-e820: 000000000009ec00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 00000000bf564000 (usable)
BIOS-e820: 00000000bf564000 - 00000000bf5bb000 (ACPI NVS)
BIOS-e820: 00000000bf5bb000 - 00000000bf5db000 (reserved)
BIOS-e820: 00000000bf5db000 - 00000000bf5ec000 (ACPI NVS)
BIOS-e820: 00000000bf5ec000 - 00000000bf600000 (reserved)
BIOS-e820: 00000000bf600000 - 00000000bf602000 (usable)
BIOS-e820: 00000000bf602000 - 00000000bf603000 (ACPI data)
BIOS-e820: 00000000bf603000 - 00000000bf60b000 (reserved)
BIOS-e820: 00000000bf60b000 - 00000000bf615000 (ACPI NVS)
BIOS-e820: 00000000bf615000 - 00000000bf63e000 (reserved)
BIOS-e820: 00000000bf63e000 - 00000000bf681000 (ACPI NVS)
BIOS-e820: 00000000bf681000 - 00000000bf800000 (usable)
BIOS-e820: 00000000fed1c000 - 00000000fed20000 (reserved)
BIOS-e820: 00000000ff000000 - 0000000100000000 (reserved)
BIOS-e820: 0000000100000000 - 000000023f800000 (usable)
NX (Execute Disable) protection: active
DMI 2.6 present.
AMI BIOS detected: BIOS may corrupt low RAM, working around it.
e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
No AGP bridge found
last_pfn = 0x23f800 max_arch_pfn = 0x400000000
MTRR default type: uncachable
MTRR fixed ranges enabled:
00000-9FFFF write-back
A0000-BFFFF uncachable
C0000-CFFFF write-protect
D0000-E7FFF uncachable
E8000-FFFFF write-protect
MTRR variable ranges enabled:
0 base 000000000 mask E00000000 write-back
1 base 200000000 mask FC0000000 write-back
2 base 0C0000000 mask FC0000000 uncachable
3 base 23F800000 mask FFF800000 uncachable
4 disabled
5 disabled
6 disabled
7 disabled
8 disabled
9 disabled
x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
e820 update range: 00000000c0000000 - 0000000100000000 (usable) ==> (reserved)
last_pfn = 0xbf800 max_arch_pfn = 0x400000000
Scanning 0 areas for low memory corruption
modified physical RAM map:
modified: 0000000000000000 - 0000000000010000 (reserved)
modified: 0000000000010000 - 000000000009ec00 (usable)
modified: 000000000009ec00 - 00000000000a0000 (reserved)
modified: 00000000000e0000 - 0000000000100000 (reserved)
modified: 0000000000100000 - 00000000bf564000 (usable)
modified: 00000000bf564000 - 00000000bf5bb000 (ACPI NVS)
modified: 00000000bf5bb000 - 00000000bf5db000 (reserved)
modified: 00000000bf5db000 - 00000000bf5ec000 (ACPI NVS)
modified: 00000000bf5ec000 - 00000000bf600000 (reserved)
modified: 00000000bf600000 - 00000000bf602000 (usable)
modified: 00000000bf602000 - 00000000bf603000 (ACPI data)
modified: 00000000bf603000 - 00000000bf60b000 (reserved)
modified: 00000000bf60b000 - 00000000bf615000 (ACPI NVS)
modified: 00000000bf615000 - 00000000bf63e000 (reserved)
modified: 00000000bf63e000 - 00000000bf681000 (ACPI NVS)
modified: 00000000bf681000 - 00000000bf800000 (usable)
modified: 00000000fed1c000 - 00000000fed20000 (reserved)
modified: 00000000ff000000 - 0000000100000000 (reserved)
modified: 0000000100000000 - 000000023f800000 (usable)
initial memory mapped : 0 - 20000000
found SMP MP-table at [ffff8800000fcda0] fcda0
init_memory_mapping: 0000000000000000-00000000bf800000
0000000000 - 00bf800000 page 2M
kernel direct mapping tables up to bf800000 @ 16000-1a000
init_memory_mapping: 0000000100000000-000000023f800000
0100000000 - 023f800000 page 2M
kernel direct mapping tables up to 23f800000 @ 18000-22000
RAMDISK: 37c44000 - 37e19ab8
ACPI: RSDP 00000000000f0420 00024 (v02 ALASKA)
ACPI: XSDT 00000000bf5ae068 0004C (v01 ALASKA A M I 01072009 AMI 00010013)
ACPI: FACP 00000000bf5b7ba0 000F4 (v04 ALASKA A M I 01072009 AMI 00010013)
ACPI: DSDT 00000000bf5ae140 09A5C (v02 ALASKA A M I 00000000 INTL 20051117)
ACPI: FACS 00000000bf60cf80 00040
ACPI: APIC 00000000bf5b7c98 00072 (v03 ALASKA A M I 01072009 AMI 00010013)
ACPI: SSDT 00000000bf5b7d10 00102 (v01 AMICPU PROC 00000001 MSFT 03000001)
ACPI: MCFG 00000000bf5b7e18 0003C (v01 ALASKA A M I 01072009 MSFT 00000097)
ACPI: HPET 00000000bf5b7e58 00038 (v01 ALASKA A M I 01072009 AMI. 00000004)
ACPI: Local APIC address 0xfee00000
(13 early reservations) ==> bootmem [0000000000 - 023f800000]
#0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
#1 [0001000000 - 00016d7b38] TEXT DATA BSS ==> [0001000000 - 00016d7b38]
#2 [0037c44000 - 0037e19ab8] RAMDISK ==> [0037c44000 - 0037e19ab8]
#3 [00016d8000 - 00016d826b] BRK ==> [00016d8000 - 00016d826b]
#4 [00000fcdb0 - 0000100000] BIOS reserved ==> [00000fcdb0 - 0000100000]
#5 [00000fcda0 - 00000fcdb0] MP-table mpf ==> [00000fcda0 - 00000fcdb0]
#6 [000009ec00 - 00000fca90] BIOS reserved ==> [000009ec00 - 00000fca90]
#7 [00000fcd24 - 00000fcda0] BIOS reserved ==> [00000fcd24 - 00000fcda0]
#8 [00000fca90 - 00000fcd24] MP-table mpc ==> [00000fca90 - 00000fcd24]
#9 [0000010000 - 0000012000] TRAMPOLINE ==> [0000010000 - 0000012000]
#10 [0000012000 - 0000016000] ACPI WAKEUP ==> [0000012000 - 0000016000]
#11 [0000016000 - 0000018000] PGTABLE ==> [0000016000 - 0000018000]
#12 [0000018000 - 000001d000] PGTABLE ==> [0000018000 - 000001d000]
[ffffea0000000000-ffffea0007dfffff] PMD -> [ffff880001800000-ffff8800087fffff] on node 0
Zone PFN ranges:
DMA 0x00000010 -> 0x00001000
DMA32 0x00001000 -> 0x00100000
Normal 0x00100000 -> 0x0023f800
Movable zone start PFN for each node
early_node_map[5] active PFN ranges
0: 0x00000010 -> 0x0000009e
0: 0x00000100 -> 0x000bf564
0: 0x000bf600 -> 0x000bf602
0: 0x000bf681 -> 0x000bf800
0: 0x00100000 -> 0x0023f800
On node 0 totalpages: 2092659
DMA zone: 56 pages used for memmap
DMA zone: 110 pages reserved
DMA zone: 3816 pages, LIFO batch:0
DMA32 zone: 14280 pages used for memmap
DMA32 zone: 765725 pages, LIFO batch:31
Normal zone: 17892 pages used for memmap
Normal zone: 1290780 pages, LIFO batch:31
ACPI: PM-Timer IO Port: 0x408
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)
ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 0, version 32, 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: 0x8086a701 base: 0xfed00000
SMP: Allowing 4 CPUs, 0 hotplug CPUs
nr_irqs_gsi: 24
PM: Registered nosave memory: 000000000009e000 - 000000000009f000
PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
PM: Registered nosave memory: 00000000000a0000 - 00000000000e0000
PM: Registered nosave memory: 00000000000e0000 - 0000000000100000
PM: Registered nosave memory: 00000000bf564000 - 00000000bf5bb000
PM: Registered nosave memory: 00000000bf5bb000 - 00000000bf5db000
PM: Registered nosave memory: 00000000bf5db000 - 00000000bf5ec000
PM: Registered nosave memory: 00000000bf5ec000 - 00000000bf600000
PM: Registered nosave memory: 00000000bf602000 - 00000000bf603000
PM: Registered nosave memory: 00000000bf603000 - 00000000bf60b000
PM: Registered nosave memory: 00000000bf60b000 - 00000000bf615000
PM: Registered nosave memory: 00000000bf615000 - 00000000bf63e000
PM: Registered nosave memory: 00000000bf63e000 - 00000000bf681000
PM: Registered nosave memory: 00000000bf800000 - 00000000fed1c000
PM: Registered nosave memory: 00000000fed1c000 - 00000000fed20000
PM: Registered nosave memory: 00000000fed20000 - 00000000ff000000
PM: Registered nosave memory: 00000000ff000000 - 0000000100000000
Allocating PCI resources starting at bf800000 (gap: bf800000:3f51c000)
Booting paravirtualized kernel on bare hardware
setup_percpu: NR_CPUS:16 nr_cpumask_bits:16 nr_cpu_ids:4 nr_node_ids:1
PERCPU: Embedded 29 pages/cpu @ffff880008a00000 s89176 r8192 d21416 u524288
pcpu-alloc: s89176 r8192 d21416 u524288 alloc=1*2097152
pcpu-alloc: [0] 0 1 2 3
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 2060321
Kernel command line: BOOT_IMAGE=/vmlinuz26 root=/dev/sdb5 ro
PID hash table entries: 4096 (order: 3, 32768 bytes)
Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
xsave/xrstor: enabled xstate_bv 0x7, cntxt size 0x340
Checking aperture...
No AGP bridge found
Calgary: detecting Calgary via BIOS EBDA area
Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Memory: 8167004k/9428992k available (3449k kernel code, 1058356k absent, 202696k reserved, 1818k data, 484k init)
SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:768
Extended CMOS year: 2000
Console: colour VGA+ 80x25
console [tty0] enabled
allocated 83886080 bytes of page_cgroup
please try 'cgroup_disable=memory' option if you don't want memory cgroups
hpet clockevent registered
Fast TSC calibration using PIT
Detected 3311.105 MHz processor.
Calibrating delay loop (skipped), value calculated using timer frequency.. 6624.13 BogoMIPS (lpj=11037016)
Security Framework initialized
Mount-cache hash table entries: 256
Initializing cgroup subsys ns
Initializing cgroup subsys cpuacct
Initializing cgroup subsys memory
Initializing cgroup subsys devices
Initializing cgroup subsys freezer
Initializing cgroup subsys net_cls
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
mce: CPU supports 9 MCE banks
CPU0: Thermal monitoring enabled (TM1)
CPU 0 MCA banks CMCI:0 CMCI:1 CMCI:3 CMCI:5 CMCI:6 CMCI:7 CMCI:8
using mwait in idle threads.
Performance Events: Nehalem/Corei7 events, Intel PMU driver.
... version: 3
... bit width: 48
... generic registers: 8
... value mask: 0000ffffffffffff
... max period: 000000007fffffff
... fixed-purpose events: 3
... event mask: 00000007000000ff
ACPI: Core revision 20091214
Setting APIC routing to flat
..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
CPU0: Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz stepping 07
Booting Node 0, Processors #1
CPU 1 MCA banks CMCI:0 CMCI:1 CMCI:3 SHD:5 SHD:6 SHD:7 SHD:8
#2
CPU 2 MCA banks CMCI:0 CMCI:1 CMCI:3 SHD:5 SHD:6 SHD:7 SHD:8
#3 Ok.
CPU 3 MCA banks CMCI:0 CMCI:1 CMCI:3 SHD:5 SHD:6 SHD:7 SHD:8
Brought up 4 CPUs
Total of 4 processors activated (26499.22 BogoMIPS).
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xe0000000-0xe3ffffff] (base 0xe0000000)
PCI: not using MMCONFIG
PCI: Using configuration type 1 for base access
bio: create slab <bio-0> at 0
ACPI: EC: Look up EC in DSDT
ACPI: Executed 1 blocks of module-level executable AML code
ACPI Error (psargs-0359): [RAMB] Namespace lookup failure, AE_NOT_FOUND
ACPI Exception: AE_NOT_FOUND, Could not execute arguments for [RAMW] (Region) (20091214/nsinit-340)
ACPI: Interpreter enabled
ACPI: (supports S0 S1 S3 S4 S5)
ACPI: Using IOAPIC for interrupt routing
PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xe0000000-0xe3ffffff] (base 0xe0000000)
PCI: MMCONFIG at [mem 0xe0000000-0xe3ffffff] reserved in ACPI motherboard resources
ACPI: BIOS _OSI(Linux) query ignored
ACPI: No dock devices found.
ACPI: PCI Root Bridge [PCI0] (0000:00)
pci_root PNP0A08:00: ignoring host bridge windows from ACPI; boot with "pci=use_crs" to use them
pci_root PNP0A08:00: host bridge window [io 0x0000-0x0cf7] (ignored)
pci_root PNP0A08:00: host bridge window [io 0x0d00-0xffff] (ignored)
pci_root PNP0A08:00: host bridge window [mem 0x000a0000-0x000bffff] (ignored)
pci_root PNP0A08:00: host bridge window [mem 0x000c8000-0x000dffff] (ignored)
pci_root PNP0A08:00: host bridge window [mem 0xc0000000-0xffffffff] (ignored)
pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
pci 0000:00:01.0: PME# disabled
pci 0000:00:16.0: reg 10: [mem 0xfe707000-0xfe70700f 64bit]
pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
pci 0000:00:16.0: PME# disabled
pci 0000:00:1a.0: reg 10: [mem 0xfe706000-0xfe7063ff]
pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1a.0: PME# disabled
pci 0000:00:1b.0: reg 10: [mem 0xfe700000-0xfe703fff 64bit]
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.4: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.4: PME# disabled
pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.5: PME# disabled
pci 0000:00:1c.6: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.6: PME# disabled
pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.7: PME# disabled
pci 0000:00:1d.0: reg 10: [mem 0xfe705000-0xfe7053ff]
pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1d.0: PME# disabled
pci 0000:00:1f.2: reg 10: [io 0xf0d0-0xf0d7]
pci 0000:00:1f.2: reg 14: [io 0xf0c0-0xf0c3]
pci 0000:00:1f.2: reg 18: [io 0xf0b0-0xf0b7]
pci 0000:00:1f.2: reg 1c: [io 0xf0a0-0xf0a3]
pci 0000:00:1f.2: reg 20: [io 0xf090-0xf09f]
pci 0000:00:1f.2: reg 24: [io 0xf080-0xf08f]
pci 0000:00:1f.3: reg 10: [mem 0xfe704000-0xfe7040ff 64bit]
pci 0000:00:1f.3: reg 20: [io 0xf000-0xf01f]
pci 0000:00:1f.5: reg 10: [io 0xf070-0xf077]
pci 0000:00:1f.5: reg 14: [io 0xf060-0xf063]
pci 0000:00:1f.5: reg 18: [io 0xf050-0xf057]
pci 0000:00:1f.5: reg 1c: [io 0xf040-0xf043]
pci 0000:00:1f.5: reg 20: [io 0xf030-0xf03f]
pci 0000:00:1f.5: reg 24: [io 0xf020-0xf02f]
pci 0000:01:00.0: reg 10: [mem 0xc0000000-0xcfffffff 64bit pref]
pci 0000:01:00.0: reg 18: [mem 0xfe620000-0xfe63ffff 64bit]
pci 0000:01:00.0: reg 20: [io 0xe000-0xe0ff]
pci 0000:01:00.0: reg 30: [mem 0xfe600000-0xfe61ffff pref]
pci 0000:01:00.0: supports D1 D2
pci 0000:01:00.1: reg 10: [mem 0xfe640000-0xfe643fff 64bit]
pci 0000:01:00.1: supports D1 D2
pci 0000:00:01.0: PCI bridge to [bus 01-01]
pci 0000:00:01.0: bridge window [io 0xe000-0xefff]
pci 0000:00:01.0: bridge window [mem 0xfe600000-0xfe6fffff]
pci 0000:00:01.0: bridge window [mem 0xc0000000-0xcfffffff 64bit pref]
pci 0000:00:1c.0: PCI bridge to [bus 02-02]
pci 0000:03:00.0: reg 10: [io 0xd040-0xd047]
pci 0000:03:00.0: reg 14: [io 0xd030-0xd033]
pci 0000:03:00.0: reg 18: [io 0xd020-0xd027]
pci 0000:03:00.0: reg 1c: [io 0xd010-0xd013]
pci 0000:03:00.0: reg 20: [io 0xd000-0xd00f]
pci 0000:03:00.0: reg 30: [mem 0xfe500000-0xfe50ffff pref]
pci 0000:03:00.0: supports D1 D2
pci 0000:03:00.0: PME# supported from D1 D2 D3hot
pci 0000:03:00.0: PME# disabled
pci 0000:00:1c.4: PCI bridge to [bus 03-03]
pci 0000:00:1c.4: bridge window [io 0xd000-0xdfff]
pci 0000:00:1c.4: bridge window [mem 0xfe500000-0xfe5fffff]
pci 0000:00:1c.5: PCI bridge to [bus 04-04]
pci 0000:05:00.0: reg 10: [io 0xc000-0xc0ff]
pci 0000:05:00.0: reg 18: [mem 0xd0004000-0xd0004fff 64bit pref]
pci 0000:05:00.0: reg 20: [mem 0xd0000000-0xd0003fff 64bit pref]
pci 0000:05:00.0: supports D1 D2
pci 0000:05:00.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:05:00.0: PME# disabled
pci 0000:00:1c.6: PCI bridge to [bus 05-05]
pci 0000:00:1c.6: bridge window [io 0xc000-0xcfff]
pci 0000:00:1c.6: bridge window [mem 0xd0000000-0xd00fffff 64bit pref]
pci 0000:00:1c.7: PCI bridge to [bus 06-07] (subtractive decode)
pci 0000:06:00.0: PCI bridge to [bus 07-07] (subtractive decode)
pci_bus 0000:00: on NUMA node 0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX4._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX5._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX6._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX7.BR19._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs *3 4 5 6 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 *7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKF] (IRQs *3 4 5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 *7 10 11 12 14 15)
vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
vgaarb: loaded
PCI: Using ACPI for IRQ routing
PCI: pci_cache_line_size set to 64 bytes
NetLabel: Initializing
NetLabel: domain hash size = 128
NetLabel: protocols = UNLABELED CIPSOv4
NetLabel: unlabeled traffic allowed by default
hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Switching to clocksource tsc
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 14 devices
ACPI: ACPI bus type pnp unregistered
system 00:01: [mem 0xfed10000-0xfed19fff] has been reserved
system 00:01: [mem 0xe0000000-0xe3ffffff] has been reserved
system 00:01: [mem 0xfed90000-0xfed93fff] has been reserved
system 00:01: [mem 0xfed20000-0xfed3ffff] has been reserved
system 00:01: [mem 0xfee00000-0xfee0ffff] has been reserved
system 00:02: [io 0x0290-0x029f] has been reserved
system 00:07: [io 0x04d0-0x04d1] has been reserved
system 00:0b: [io 0x0400-0x0453] has been reserved
system 00:0b: [io 0x0458-0x047f] has been reserved
system 00:0b: [io 0x0500-0x057f] has been reserved
system 00:0b: [mem 0xfed1c000-0xfed1ffff] has been reserved
system 00:0b: [mem 0xfec00000-0xfecfffff] could not be reserved
system 00:0b: [mem 0xfed08000-0xfed08fff] has been reserved
system 00:0b: [mem 0xff000000-0xffffffff] has been reserved
system 00:0c: [io 0x0454-0x0457] has been reserved
pci 0000:00:01.0: PCI bridge to [bus 01-01]
pci 0000:00:01.0: bridge window [io 0xe000-0xefff]
pci 0000:00:01.0: bridge window [mem 0xfe600000-0xfe6fffff]
pci 0000:00:01.0: bridge window [mem 0xc0000000-0xcfffffff 64bit pref]
pci 0000:00:1c.0: PCI bridge to [bus 02-02]
pci 0000:00:1c.0: bridge window [io disabled]
pci 0000:00:1c.0: bridge window [mem disabled]
pci 0000:00:1c.0: bridge window [mem pref disabled]
pci 0000:00:1c.4: PCI bridge to [bus 03-03]
pci 0000:00:1c.4: bridge window [io 0xd000-0xdfff]
pci 0000:00:1c.4: bridge window [mem 0xfe500000-0xfe5fffff]
pci 0000:00:1c.4: bridge window [mem pref disabled]
pci 0000:00:1c.5: PCI bridge to [bus 04-04]
pci 0000:00:1c.5: bridge window [io disabled]
pci 0000:00:1c.5: bridge window [mem disabled]
pci 0000:00:1c.5: bridge window [mem pref disabled]
pci 0000:00:1c.6: PCI bridge to [bus 05-05]
pci 0000:00:1c.6: bridge window [io 0xc000-0xcfff]
pci 0000:00:1c.6: bridge window [mem disabled]
pci 0000:00:1c.6: bridge window [mem 0xd0000000-0xd00fffff 64bit pref]
pci 0000:06:00.0: PCI bridge to [bus 07-07]
pci 0000:06:00.0: bridge window [io disabled]
pci 0000:06:00.0: bridge window [mem disabled]
pci 0000:06:00.0: bridge window [mem pref disabled]
pci 0000:00:1c.7: PCI bridge to [bus 06-07]
pci 0000:00:1c.7: bridge window [io disabled]
pci 0000:00:1c.7: bridge window [mem disabled]
pci 0000:00:1c.7: bridge window [mem pref disabled]
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.4: PCI INT A -> GSI 17 (level, low) -> IRQ 17
pci 0000:00:1c.4: setting latency timer to 64
pci 0000:00:1c.5: PCI INT B -> GSI 16 (level, low) -> IRQ 16
pci 0000:00:1c.5: setting latency timer to 64
pci 0000:00:1c.6: PCI INT C -> GSI 18 (level, low) -> IRQ 18
pci 0000:00:1c.6: setting latency timer to 64
pci 0000:00:1c.7: PCI INT D -> GSI 19 (level, low) -> IRQ 19
pci 0000:00:1c.7: setting latency timer to 64
pci 0000:06:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
pci 0000:06:00.0: setting latency timer to 64
pci_bus 0000:00: resource 0 [io 0x0000-0xffff]
pci_bus 0000:00: resource 1 [mem 0x00000000-0xffffffffffffffff]
pci_bus 0000:01: resource 0 [io 0xe000-0xefff]
pci_bus 0000:01: resource 1 [mem 0xfe600000-0xfe6fffff]
pci_bus 0000:01: resource 2 [mem 0xc0000000-0xcfffffff 64bit pref]
pci_bus 0000:03: resource 0 [io 0xd000-0xdfff]
pci_bus 0000:03: resource 1 [mem 0xfe500000-0xfe5fffff]
pci_bus 0000:05: resource 0 [io 0xc000-0xcfff]
pci_bus 0000:05: resource 2 [mem 0xd0000000-0xd00fffff 64bit pref]
pci_bus 0000:06: resource 3 [io 0x0000-0xffff]
pci_bus 0000:06: resource 4 [mem 0x00000000-0xffffffffffffffff]
pci_bus 0000:07: resource 6 [io 0x0000-0xffff]
pci_bus 0000:07: resource 7 [mem 0x00000000-0xffffffffffffffff]
NET: Registered protocol family 2
IP route cache hash table entries: 262144 (order: 9, 2097152 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
UDP hash table entries: 4096 (order: 5, 131072 bytes)
UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
NET: Registered protocol family 1
pci 0000:01:00.0: Boot video device
PCI: CLS 64 bytes, default 64
Unpacking initramfs...
Freeing initrd memory: 1878k freed
PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Placing 64MB software IO TLB between ffff88000979e000 - ffff88000d79e000
software IO TLB at phys 0x979e000 - 0xd79e000
Scanning for low memory corruption every 60 seconds
audit: initializing netlink socket (disabled)
type=2000 audit(1304838033.699:1): initialized
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
msgmni has been set to 15956
alg: No test for stdrng (krng)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
pcieport 0000:00:01.0: setting latency timer to 64
pcieport 0000:00:01.0: irq 24 for MSI/MSI-X
pcieport 0000:00:1c.0: setting latency timer to 64
pcieport 0000:00:1c.0: irq 25 for MSI/MSI-X
pcieport 0000:00:1c.4: setting latency timer to 64
pcieport 0000:00:1c.4: irq 26 for MSI/MSI-X
pcieport 0000:00:1c.5: setting latency timer to 64
pcieport 0000:00:1c.5: irq 27 for MSI/MSI-X
pcieport 0000:00:1c.6: setting latency timer to 64
pcieport 0000:00:1c.6: irq 28 for MSI/MSI-X
Linux agpgart interface v0.103
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
input: Macintosh mouse button emulation as /devices/virtual/input/input0
PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
serio: i8042 KBD port at 0x60,0x64 irq 1
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
PM: Resume from disk failed.
registered taskstats version 1
Initalizing network drop monitor service
Freeing unused kernel memory: 484k freed
SCSI subsystem initialized
libata version 3.00 loaded.
ata_piix 0000:00:1f.2: version 2.13
ata_piix 0000:00:1f.2: PCI INT B -> GSI 20 (level, low) -> IRQ 20
ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
ata_piix 0000:00:1f.2: setting latency timer to 64
scsi0 : ata_piix
scsi1 : ata_piix
ata1: SATA max UDMA/133 cmd 0xf0d0 ctl 0xf0c0 bmdma 0xf090 irq 20
ata2: SATA max UDMA/133 cmd 0xf0b0 ctl 0xf0a0 bmdma 0xf098 irq 20
ata_piix 0000:00:1f.5: PCI INT B -> GSI 20 (level, low) -> IRQ 20
ata_piix 0000:00:1f.5: MAP [ P0 -- P1 -- ]
ata_piix 0000:00:1f.5: SCR access via SIDPR is available but doesn't work
ata_piix 0000:00:1f.5: setting latency timer to 64
scsi2 : ata_piix
scsi3 : ata_piix
ata3: SATA max UDMA/133 cmd 0xf070 ctl 0xf060 bmdma 0xf030 irq 20
ata4: SATA max UDMA/133 cmd 0xf050 ctl 0xf040 bmdma 0xf038 irq 20
pata_acpi 0000:03:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
pata_acpi 0000:03:00.0: setting latency timer to 64
pata_acpi 0000:03:00.0: PCI INT A disabled
ata1.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.01: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: ATA-8: SAMSUNG HD103SJ, 1AJ10001, max UDMA/133
ata1.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata1.01: ATA-6: WDC WD1200JD-00GBB0, 02.05D02, max UDMA/100
ata1.01: 234441648 sectors, multi 16: LBA48
ata1.01: applying bridge limits
ata1.00: configured for UDMA/133
ata1.01: configured for UDMA/100
scsi 0:0:0:0: Direct-Access ATA SAMSUNG HD103SJ 1AJ1 PQ: 0 ANSI: 5
scsi 0:0:1:0: Direct-Access ATA WDC WD1200JD-00G 02.0 PQ: 0 ANSI: 5
ata2.01: failed to resume link (SControl 0)
ata2.00: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.01: SATA link down (SStatus 0 SControl 0)
ata2.01: link offline, clearing class 3 to NONE
ata2.00: ATAPI: TSSTcorp CDDVDW SH-S223C, SB05, max MWDMA2
ata2.00: configured for MWDMA2
ata2.00: qc timeout (cmd 0xa0)
ata2.00: TEST_UNIT_READY failed (err_mask=0x4)
ata2.01: failed to resume link (SControl 0)
ata2.00: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.01: SATA link down (SStatus 0 SControl 0)
ata2.01: link offline, clearing class 3 to NONE
ata2.00: configured for MWDMA2
ata2.00: qc timeout (cmd 0xa0)
ata2.00: TEST_UNIT_READY failed (err_mask=0x4)
ata2.00: limiting SATA link speed to 1.5 Gbps
ata2.00: limiting speed to MWDMA2:PIO3
ata2.01: failed to resume link (SControl 0)
ata2.00: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata2.01: SATA link down (SStatus 0 SControl 0)
ata2.01: link offline, clearing class 3 to NONE
ata2.00: configured for MWDMA2
ata2.00: qc timeout (cmd 0xa0)
ata2.00: TEST_UNIT_READY failed (err_mask=0x4)
ata2.00: disabled
ata2.00: hard resetting link
ata2.01: hard resetting link
ata2.01: failed to resume link (SControl 0)
ata2.00: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata2.01: SATA link down (SStatus 0 SControl 0)
ata2.01: link offline, clearing class 3 to NONE
ata2: EH complete
pata_via 0000:03:00.0: version 0.3.4
pata_via 0000:03:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
pata_via 0000:03:00.0: setting latency timer to 64
scsi4 : pata_via
scsi5 : pata_via
ata5: PATA max UDMA/133 cmd 0xd040 ctl 0xd030 bmdma 0xd000 irq 16
ata6: PATA max UDMA/133 cmd 0xd020 ctl 0xd010 bmdma 0xd008 irq 16
sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
sd 0:0:1:0: [sdb] 234441648 512-byte logical blocks: (120 GB/111 GiB)
sd 0:0:1:0: [sdb] Write Protect is off
sd 0:0:1:0: [sdb] Mode Sense: 00 3a 00 00
sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdb: sdb1
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
sdb2 sdb3 sdb4 < sdb5 >
sda: sda1 sda2
sd 0:0:1:0: [sdb] Attached SCSI disk
sda3
sd 0:0:0:0: [sda] Attached SCSI disk
EXT4-fs (sdb5): mounted filesystem with ordered data mode
<30>udev[901]: starting version 167
Adding 7030776k swap on /dev/sdb2. Priority:-1 extents:1 across:7030776k
Thanks a lots.
Last edited by KingYes (2011-05-08 11:03:55)

FYI, the latest installation CD version is "2010.05". It's best to use the latest. Get it from http://www.archlinux.org/download/
I'm not sure but I believe all other LiveCDs are custom made outside of the official Archlinux development team.
I recommend downloading the CD I mentioned and follow this guide: https://wiki.archlinux.org/index.php/Beginners%27_Guide
I've installed arch many times on different hardware and the only time I lost mouse and keyboard was after I removed "10-evdev.conf" and "10-quirks.conf" from /etc/X11/xorg.conf.d/. I copied both back from backups, rebooted and m&k were functional again. My guess is "10-evdev.conf" was the file I needed. Check both these files exist.

5th generation video iPod USB not working

Hi, my 15 month old iPod 5th generation video no longer connects with USB on my iBook (all my other USB devices work just fine in the two USB 2 ports).
The screen lights when iPod is plugged in and when unplugged using USB, but that appears to be the in toto communication performed.
I have performed the five Rs, and putting the iPod into disc mode yields the expected result on the screen of the iPod (tick and OK to disconnect) but no connection to the computer (yes, I have plugged/unplugged a number of times).
I have disconnected the battery (as another poster suggested) for several minutes and that does not seem to have helped in resetting the system.
It charges just fine via Firewire (either by a Firewire port on my iBook or by an Apple Firewire AC adaptor type charger), with absolutely no charging taking place when connected with USB (either by a USB 2 port on my iBook (G4 2004 model) or by an Apple USB AC adaptor type charger).
I have also tried three different USB cables, one old, two brand new Apple ones (all of which work just fine on my old 4th gen iPod, my daughter's 3rd gen iPod and my partner's two 4th gen iPods).
When I run the inbuilt diagnostics on the iPod, all of them come back as ok, including USB, both as charging and communication, so, in theory, everything should be ok, but most patently isn't.
I have tried to use the iPod on a Windows 2000 computer and an older iMac (both of which otherwise work fine with other iPods either using USB and Firewire) with nil recognition by any.
I've looked in the wide dock connection plug at the bottom of the iPod as another poster said that the connection pins might be bent, however, I can't see any actual pins, just a wide tongue in the middle, the same as on my other older iPod. Or do I need to open up the iPod and look for something in there?
Judging by the nr of comments and questions on similar issues here with the 5th generation video iPod, there should be a definitive fix for this problem, although, after looking through as much of the forums that might relate to this problem, no one seems to have come up with an explanation, let alone a solution for it.
So, my question remains, my iPod 5th generation video no longer connects with USB on my iBook, has anyone else (taking into account the above information), either had/have this problem and or found a resolution to it?
Cheers, Peter
iBook G4 Mac OS X (10.4.9) 5th generation video iPod

Dear deggie, hi, thanks for the tip as to what I should be looking for in the slot. However, sadly, it all looks to be fine (well, at least the same as my other iPod).
HR, thanks for the tip re opening the iPod, unfortunately, it is 15 months old, so well past the 12 month warranty expiry (ridiculous, isn't it?).
Here in Australia, we don't have access to Genius Bars and Apple Stores, just the local distributors, and they want $210 to repair/replace the iPod, which, frankly I find a bit rich, considering that it hasn't been mistreated in any way and the other iPod I have has been running fine for more than two years.
I get the feeling, judging by the many complaints on these forums regarding the problems that the gen 5 iPod being recognised and connecting to both Mac and Windows, that this cannot just be purely user error or maltreatment. However, I'm unsure as to what can be done to resolve them or get Apple to admit to there being a problem.
One of the things that confuses me, is that all the internal diagnostics (menu + select then select + back) including USB communication, all come back fine, when, as mentioned in an above post, it most patently is not. Anyone have any clues as to what this might be due to?
If, by some bizarre fluke, I manage to find a resolution to this problem (short of going and paying Apple $210), I'll post back here with it.
Again, thanks for the help, cheers, Peter

Hard drive and usb not working

Greetings,
My notebook is cq60-214dx compaq presario with a windows vista basic operating system. I have pentium dual core inside.
Recently, My usb stop working, there is nothing else hooked up to it for the past year. It is not detecting my flash drive. I did the shut down and unplug thing. I also did the F10 bios test and the hard drive test failed at 61%. I went into the usb root hub and it shows each one is fine and is at 0 mA. The only thing that I see is the microsoft Isatap adapter code 31. A toredo tunneling pseudo interface -code 10 with a caution sign. I 've tried the hp down load and all kind of suggestions that is not working. Is there something I can try to fix the hard drive. I'd like to eventually go to windows 8 operatiing system but I am not fearful.

Hi newbie-515,
Unfortunately, the failure code for the hard drive is fortelling you of what is to come. In my opinion I would address the solution by the following specific actions:
1: Back up any data that can be accessed from the original drive, onto an external hard drive. To minimize the risk of losing any information.
2: Replace the failing hard drive, before it gets to the point of complete failure. This may also prevent loss of personal data.
and 3: Decide whether you want to upgrade/restore Microsoft Windows 7 onto the pc. That particular pc has current drivers available online at HP Support for the Microsoft Windows 7 operating system.
Once this has been completed, then you can recover any personal data that was backed up to the external hard drive, onto the newly installed hard drive.
***In this forum support is available for HP hardware/software assistance. I will provide best-effort support with your HP hardware/software. If you need assistance with software that is from any other vendor, then I may re-direct you to the appropriate reference at that time.
-------------How do I give Kudos? | How do I mark a post as Solved? --------------------------------------------------------
Make it easier for other people to find solutions, by marking my answer with 'Accept as Solution', if it solves your problem. Click on the BLUE KUDOS button on the left to say "Thanks"
Although I am an HP employee, I am speaking for myself and not for HP.

Macbook pro usb not working

Hello. One (of the two) USB ports is not working. Now what? Please help. Thanks. :-)
OSX 10.9.4

Possibly use canned air to blow out any dust, crumbs, or paper bits that may have gotten into the port while in transit?
Other than that - I guess replace the port.

Micro USB not working on 9300

Similar Messages

Maybe you are looking for