Multiple USB devices
So I use Logic Pro on my Macbook A LOT! I use my firewire port for a mixer (works perfect) but I've got numerous devices that use USB (e.g. trigger finger, conntectiv box, external hard drive etc.) I want to have them all hooked up to my mac at the same time. I've got one adapter for a USB that adds 4 ports to it but it isn't powered so runs sooooo slowly its painful!
Should I look into buying a powered 4-way USB adapter? If so, can you suggest one? And would it affect the performance of any of my devices/mac?
Cheers
AreMad wrote:
So I use Logic Pro on my Macbook A LOT! I use my firewire port for a mixer (works perfect) but I've got numerous devices that use USB (e.g. trigger finger, conntectiv box, external hard drive etc.) I want to have them all hooked up to my mac at the same time. I've got one adapter for a USB that adds 4 ports to it but it isn't powered so runs sooooo slowly its painful!
Powered or passive doesn't affect the speeds through a USB hub.
Only one USB device can actually communicate through USB at a given instant. The host device operating system handles all of this and hooking up multiple devices that are bandwidth hungry means that they will inevitably be slowed down.
Similar Messages
-
Qemu/kvm: multiple USB devices from the same vendor
Hi fellow gurus,
Trying to pass-through two USB devices. One works just fine, but two produces an error.
They are the same type from the same vendor and libvirt seems to have no way to differentiate between the two, as it only uses the <vendor id='0xnnnn'/> & <product id='0xnnn'/> strings and not serial number of the device.
There is a reference -unanswered- here: https://bugs.launchpad.net/qemu/+bug/1090602
The error message from virt-manager:
Error starting domain: operation failed: Multiple USB devices for 10c4:ea60, use <address> to specify one
Detailed output
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 44, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 65, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/domain.py", line 1063, in startup
self._backend.create()
File "/usr/lib64/python2.6/site-packages/libvirt.py", line 678, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: operation failed: Multiple USB devices for 10c4:ea60, use <address> to specify one
The devices themselves:
Bus 001 Device 009: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light
Bus 001 Device 008: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light
Is there any workaround or fix for this?
Cheers,
Mike.
Last edited by DrMikeDuke (2013-07-22 14:01:18)As I understand it, host:bus.addr is an alternative to host:vendor_id:product_id. So if I wanted to pass both of these thumb drives:
$ lsusb
Bus 001 Device 002: ID 1e3d:2093 Chipsbank Microelectronics Co., Ltd CBM209x Flash Drive (OEM)
Bus 001 Device 003: ID 1e3d:2093 Chipsbank Microelectronics Co., Ltd CBM209x Flash Drive (OEM)
I would use host:001.002 and host:001.003 . Note I said would use, because I've never tried it.
And usb_add is a qemu monitor command. See sections 3.4 and 3.5 of the doc you linked for info on the monitor.
All this being said, I don't use libvirt stuff so I don't know if it has the capability to specify USB devices by bus.addr or whether or not it enables the monitor. -
Is it possible, to add multiple USB devices to TC
Is it possible, to add multiple USB devices using a hub to Time Capsule (as stated for Airport Extreme)?
Thanks in advance.
StefanThe Time Capsule is an AirPort Extreme with a built-in hard drive, so you can add multiple USB devices if you use a powered USB hub.
-
Problems with multiple USB devices. (Possible Low Power on USB Bus)
I believe I'm having an issue with the USB bus or one of my devices that I have installed on my iMac.
I purchased this iMac along with a printer (HP C4280 All-in-One) as part of a promotion deal. I also have wireless logitech USB mouse, and iPhone and an 80gb 5th Gen iPod.
My problem has to do with syncing the iPod and iPhone. Normally I have the printer attached to the iMac along with the USB mouse. Both devices function as expected. However I have problems when I connect the iPhone or iPod.
iPod Symptoms: When I connect the iPod the iPod screen shows the flashing red circle with a line but iTunes never launches and the iPod never syncs.
iPhone Symptoms: When I connect the iPhone the iPhone screen says Sync in Progress and iTunes does show the iPhone in the list of devices but a dialog appears giving me one of two messages (that I've seen so far) - [msg 1] Your iPhone is corrupt please disconnect then reconnect to restore. [msg 2] iPhone device timed out.
I've been dealing with this problem for a couple months and found that if I disconnect the printer (HP C4280) then connected either other device then everything works just fine.
I downloaded XCode 2.5 and launched the USB Prober utility. Then plugged in each device in turn and found some interesting findings.
When connecting the iPhone (1st attempt) the USB Logger reported; (iTunes displayed msg 1 from above)
128.517 [1] USB Device iPhone is violating Section 9.3.5 of the USB Specification -- Error in GetConfigDescriptor( wLength = 4)
128.520 [1] USB Low Power Notice: The device "iPhone" cannot be used because there is not enough power to configure it
128.528 [1] USB Low Power Notice: The device "iPhone" cannot be used because there is not enough power to configure it
128.629 [1] AppleIRController[0x2dc8e00]::RearmInterruptRead immediate error 0xe000404f queueing read, clearing stall and trying again(1)
When connecting the iPod (1st attempt) the USB Logger reported; (iTunes never showed that the iPod devices was connected)
938.797 [1] USB Device IOUSBDevice is violating Section 9.3.5 of the USB Specification -- Error in GetConfigDescriptor( wLength = 4)
938.801 [1] IOUSBCompositeDriver[0x39b9f80](IOUSBDevice) SetConfiguration (1) returned 0xe00002ed
938.900 [1] AppleIRController[0x2dc8e00]::RearmInterruptRead immediate error 0xe000404f queueing read, clearing stall and trying again(1)
When connecting the iPhone (2nd attempt) the USB Logger reported; (iTunes displayed msg 2 from above)
1789.023 [1] AppleIRController[0x2dc8e00]::RearmInterruptRead immediate error 0xe000404f queueing read, clearing stall and trying again(1)
1802.166 [1] AppleUSBEHCI[0x28a7000]::Found a transaction which hasn't moved in 5 seconds on bus 253, timing out!
1809.166 [1] AppleUSBEHCI[0x28a7000]::Found a transaction which hasn't moved in 5 seconds on bus 253, timing out!
I'm suspicious of the USB Low Power Notice. If this is true then I suspect the my iMac might need some type of repair. However I am also suspicious of USB Device violating the USB Spec Error. Although this is the message that appears when I plug in the iPhone or iPod I don't think I can assume that error relates to the iPod or iPhone. The error doesn't specify which USB Device is in violation.
My current workaround is to unplug the printer every time I sync the iPhone or iPod which is cumbersome. I'm also worried that repeated connecting/disconnecting of USB plug for the printer will over time damage the USB port.
I'm not sure what options I have here. Can anyone provide some suggestions or information that might provide some insight.
Best Regards,
xgnomexA-Ha! Now I'm feeling like my 1.5 hours of reading this forum are not wasted, since I've found others with similar symptoms.
I've only had my iMac for two weeks today. I've got some new accessories & have experimented with the ones I've had awhile (various USB external drives). My model has 3 USB ports, one of which is taken by the keyboard, of course.
Over the weekend, I picked up an MS Office 2008 Upgrade and also an HP Officejet Pro L7680 all-in-one. I only mention the Office upgrade because I installed it on the same day as the printer, but it's possibly unrelated.
I actually have a Belkin 4-port hub--not the same one suggested in this thread, but externally powered with it's own A/C adapter. (It's a Hi-Speed USB 2.0 r-Port Hub, model F5U234 Rev.3, and I used it with a previous iMac G3 CRT with no problem.)
So with a LaCie 100 GB USB Mobile Drive in one of the iMac's ports, and the HP L7680 in the iMac's third port, or the HP via the Belkin hub in iMacs the third hub, here are some of the symptoms I've seen:
1) while browsing in Firefox, suddenly the mouse-cursor will "freeze" (get stuck) in a pull-down selector...sometimes it unfreezes, but eventually (like on the next pull-down menu) the keyboard & mouse will shut off (and if you wait & the iMac goes to sleep, the keyboard won't let me enter my unlock password when I wake the iMac with the Apple Remote)
2) when trying to open a document from the LaCie in MS Word, Word freezes and the keyboard & mouse go dead--terminal beachball--to restart the computer, I have to hold in the power button
3) when trying to print a message in Mail, Finder freezes (though the print job does finish)
These symptoms seem strange! Hey, it's just supposed to work, right? But everything has limits, so my question becomes, "how much stuff can I hook up at once?"
I wonder if this Apple article is addressing this issue:
http://docs.info.apple.com/article.html?artnum=25243
especially when it says "Two high-bandwidth devices or two isochronous devices cannot be connected to a single Universal Serial Bus (USB)."
So only two hi-speed USB devices can be connected "to the same bus" simultaneously? I'm not entirely sure I understand what "isochronous" means, but I'm thinking I need to peel my printer off the USB somehow, maybe via Airport Express--?
Does anyone know for sure about USB limitations? Thanks.
Also, xgnomex, how/where did you find that "USB Logger"? Is that something iPhone-specific, or is it an OS X log in a Library somewhere? -
Multiple USB Device Driver Installations Failing
Windows 7 64 Bit / MSI P965 Platinum Mother Board
I have three USB driver installations failing. I believe this is related to ' USB', because installations of other software unrelated to USB devices install just fine. Might it be a Windows Installer Service, appears to be running fine?
Failing Device Driver Installations;
1) IOGEAR USB 3 PCIe card
Problem: The installer runs part way through the "Preparing to install' process and goes into limbo. I have tried three USB cards by different manufacturers and get the same problem. Tried several Renesas installers, all failed.
Microsoft Windows Installer says: 'Stopped working. Files that help describe the problem: AppCompat.txt, WERInternalMetadata.xml, WERDataCollection failure'.
2) APC Battery Backup 'PowerChute' Software
Problem: : The installer runs part way through the "Preparing to install' process and goes into limbo -or- I get an error message telling me to check the USB connection. APC cable is pulgged into a native port, not a hub. APC has no solution.
3) Logitech Harmony One Remote Software (Finally installed in 'Safe' Mode
Error: : The installer runs part way through the "Preparing to install' process and goes into limbo, but, when I went into 'Safe Mode' the software installed properly. Installation of the other two examples yield the Windows 'can't be installed in safe mode'
Help Appreciated - IMTo rule out a Windows problem, have you tested with a fresh parallel installation?
-
Multiple USB devices with LKIF.dll
I am successfully using a single USB Keyence LK-G3001 laser displacement controller with 2 heads and making function calls to LKIF.dll
The next step is to implement a second controller.
According to Keyence, the LKIF.dll will only support a single device. They suggested disabling the 1st USB port and then enabling the 2nd port.
How can I programmatically
determine which device is attached to which port?
enable/disable the USB port?If you're running on a Windows machine you can try using devcon. It's a command-line based utility. For other operating systems you would need to use the old Google to find an equivalent utility.
-
MyRio multiple USB (devices) webcams, how ?
I'd like to connect more than 1 camera to myRio.
- I tried to connect them through a USB hub, no success, I don't see the camera anymore in MAX
- I tried to connect them using the other USB (square) connector using a gender adaptator, no success.
I wonder if one can connect anything beside a PC in this additionnal USB (square) connector ?
Any idea ?
Chris
FYI I was able to connected to the ethernet using the Apple USB/Ethernet adaptator.Hello Chris,
there is already a post for the same issue.
Take a look here:
http://forums.ni.com/t5/LabVIEW/USB-Hub-for-myRIO/td-p/2603237
Regards,
Branni -
How do I use more than one USB device with Airport Extreme?
I would like to plug a shared hard drive into my new airport extreme and still be able to plug in a shared printer as well. How am I supposed to do this with only one USB port. Do I use a USB hub???
Is it possible to connect a hard drive using one of the ethernet ports?To use multiple USB devices you would use a powered USB hub.
You can connect a hard drive to one of the Ethernet ports providing the hard drive is a NAS and supports Ethernet connections. In that situation the NAS hard drive is just like any other Ethernet client and the AirPort Extreme base station (AEBS) does not handle the file sharing services. The drive itself would provide the file sharing services. -
I was told that make mats that cool the laptop. My friend told me there was one that hooked up via USB then had 3-4 ports on it for multiple USB devices. That would really be perfect for me. Anyone know where i could find them online?
http://www.newegg.com/Product/Product.aspx?Item=N82E16834999017&Tpk=notepal
2 usb, so just 1 empty after you plug in to the MBP; $28; I don't turn on the fans unless the idiot light goes on ... then it cools the MBP quick ... the NotePal is about one and one-half inches not wide enough, but that is ok; I'd rather have the smooth corners of the MBP than the sharper corners of the NotePal being outermost ... -
Synchronize multiple tasks and multiple boards with X-series USB devices
Hi all,
I am trying to figure out how to synchronize multiple tasks across multiple X-series USB boards (6353, to be precise).
I have to run a digital output task AND an analog output task on each board. All four tasks (the DO and AO on Board 1, and the DO and AO on Board 2) must be synchronized.
I know how to synchronize multiple tasks on a single board. I've been doing that for years. That works fine.
I know how to synchronize a single task across multiple boards (say, a DO task across 2 different boards). That works fine too.
For the life of me, I can't figure out how to marry the two. Everything I've seen, all of the examples, etc. assume you want to do one or the other, or that you have a RTSI cable available. Are there any examples out there that synchronize multiple tasks across multiple USB boards?
I tried exporting the AO clock signal from my master AO task to PFI12, and then using the signal on PFI12 to as the clock source for the remaining tasks (Dev1/PFI12 physically connected to Dev2/PFI12, and Dev1/PFI12 set as the clock source for Dev1's DO task).
I have also tried setting Dev1/aoSampClock as the source for Dev1's DO task.
Under both configurations, I invariably get error -89137 when I try to start the tasks -- required resources (PFI12) in use by Dev1/do/SampClock. I understand what the error is telling me. What I don't understand is why I'm receiving this error when I don't have any of my tasks configured to use the DO Sample Clock. It seems as though it is not possible to export a clock signal to a PFI line and simultaneously run a clocked digital task, even if the clock source for that task is specified as something other than the DO Sample Clock?
So, my question is, is it possible to do what I want to do? And if so, how do I do it? How do I configure a common clock source across multiple tasks running on multiple USB boards?
Hoping for insight from those wiser than I...
Diane
Solved!
Go to Solution.Update: I decided to try using a counter as the source clock. One cannot use counter 0 to accomplish this, but it does appear to work with counter 1.
I'll take what I can get. Fortunately I have two spare counters. (Yes, I'm running counter tasks too -- 6 of them -- but they don't have to be synchronized.)
I have to add both digital and analog input tasks as well -- all synchronous with each other, but not with the output tasks since they'll be running at different sample rates. I hope I'm able to use a counter as the source clock for those as well.
My head aches. -
Ejecting iPod causes other USB devices to be ejected at the same time.
When ejecting an iPod Nano 4g from iTunes under Windows Vista, all other USB devices attached to the computer are also ejected at the same time (external hard drives, thumb drives, scanners, etc.). Is there a way to prevent this from happening?
Express is slow ethernet.. 10/100 only. The max speed of any connection to a USB hard disk is limited severely by the 100mbit..
USB is always slow btw.. This is actually a poor way to share a drive. A cheap NAS.. ie ethernet to Sata directly is far far superior and a single disk NAS can be had cheaply.. you will never get close with USB in network situations.
If you use a hub though, you can plug multiple disks into an Extreme.. I guess the network speed is at least no worse than the USB hub -- ethernet devices which are lousy as a whole.
Never forget you have the fastest ethernet adapters and fastest possible connectors already on computers on the network.. people are so utterly mesmerized by NAS they forget.. a FW800 or better USB3 if you have a newer computer shared to the network from a computer has much higher throughput and is much cheaper than even the very low end network stand alone boxes. -
Death of a USB device... natural causes or foul play?
I've had a little usb flash drive mp3 player for years. The last time that I mounted it (mount -o umask=0 ...) to replace some songs, the songs were correctly copied but umount hung when I tried to dismount it.
After about 5 minutes I killed umount and checked that the device was unmounted, which it was. After removing the device, I turned it on to check it but it wouldn't proceed past the initial logo screen.
I can no longer mount the device. Here's the dmesg output from multiple attempts:
[ 101.066671] usb 6-2: new full speed USB device number 2 using uhci_hcd
[ 101.515930] usbcore: registered new interface driver uas
[ 101.520972] Initializing USB Mass Storage driver...
[ 101.521079] scsi10 : usb-storage 6-2:1.0
[ 101.521176] usbcore: registered new interface driver usb-storage
[ 101.521182] USB Mass Storage support registered.
[ 102.903338] usb 6-2: reset full speed USB device number 2 using uhci_hcd
[ 103.020004] usb 6-2: device descriptor read/64, error -71
[ 103.240002] usb 6-2: device descriptor read/64, error -71
[ 103.450003] usb 6-2: reset full speed USB device number 2 using uhci_hcd
[ 103.620002] usb 6-2: device descriptor read/64, error -71
[ 103.840000] usb 6-2: device descriptor read/64, error -71
[ 104.050005] usb 6-2: reset full speed USB device number 2 using uhci_hcd
[ 104.463350] usb 6-2: device not accepting address 2, error -71
[ 104.570003] usb 6-2: reset full speed USB device number 2 using uhci_hcd
[ 104.983340] usb 6-2: device not accepting address 2, error -71
[ 104.983365] usb 6-2: USB disconnect, device number 2
[ 105.090003] usb 6-2: new full speed USB device number 3 using uhci_hcd
[ 105.260002] usb 6-2: device descriptor read/64, error -71
[ 105.480006] usb 6-2: device descriptor read/64, error -71
[ 105.690003] usb 6-2: new full speed USB device number 4 using uhci_hcd
[ 105.806673] usb 6-2: device descriptor read/64, error -71
[ 106.080003] usb 6-2: device descriptor read/64, error -71
[ 106.290002] usb 6-2: new full speed USB device number 5 using uhci_hcd
[ 106.703342] usb 6-2: device not accepting address 5, error -71
[ 106.810006] usb 6-2: new full speed USB device number 6 using uhci_hcd
[ 107.223340] usb 6-2: device not accepting address 6, error -71
[ 107.223350] hub 6-0:1.0: unable to enumerate USB device on port 2
[ 847.596593] usb 6-2: new full speed USB device number 7 using uhci_hcd
[ 847.781385] scsi11 : usb-storage 6-2:1.0
[ 869.493259] usb 6-2: reset full speed USB device number 7 using uhci_hcd
[ 879.739928] usb 6-2: reset full speed USB device number 7 using uhci_hcd
[ 895.993259] usb 6-2: reset full speed USB device number 7 using uhci_hcd
[ 896.243260] usb 6-2: reset full speed USB device number 7 using uhci_hcd
[ 906.489922] usb 6-2: reset full speed USB device number 7 using uhci_hcd
[ 906.636310] scsi 11:0:0:0: Device offlined - not ready after error recovery
[ 1240.346582] usb 6-2: USB disconnect, device number 7
[ 1242.973223] usb 6-1: new full speed USB device number 8 using uhci_hcd
[ 1243.141696] scsi12 : usb-storage 6-1:1.0
[ 1265.439888] usb 6-1: reset full speed USB device number 8 using uhci_hcd
[ 1275.693217] usb 6-1: reset full speed USB device number 8 using uhci_hcd
[ 1291.943223] usb 6-1: reset full speed USB device number 8 using uhci_hcd
[ 1292.193219] usb 6-1: reset full speed USB device number 8 using uhci_hcd
[ 1302.439883] usb 6-1: reset full speed USB device number 8 using uhci_hcd
[ 1302.586484] scsi 12:0:0:0: Device offlined - not ready after error recovery
I get the same messages on a different system.
I've tried removing the ehci-hcd module as recommended in the Linux USB FAQ and in several threads concerning similar issues. I've even taken the device apart to see if anything was broken, fried or disconnected, but I didn't notice anything.
Before I give up and accept that it's an irreparable hardware failure, is there anything that I should try?
I should also mention that I swapped some songs recently, so if this was caused by recent kernel changes, then they were probably introduced in 2.6.39.3. I've found the following in the kernel changelog, which may be relevant:
commit b8680d130d565da6eb07567bd6ff20b73f747498
Author: Alan Stern <[email protected]>
Date: Wed Jul 6 17:03:45 2011 -0400
USB: additional regression fix for device removal
commit ca5c485f55d326d9a23e4badd05890148aa53f74 upstream.
Commit e534c5b831c8b8e9f5edee5c8a37753c808b80dc (USB: fix regression
occurring during device removal) didn't go far enough. It failed to
take into account that when a driver claims multiple interfaces, it may
release them all at the same time. As a result, some interfaces can
get released before they are unregistered, and we deadlock trying to
acquire the bandwidth_mutex that we already own.
This patch (asl478) handles this case by setting the "unregistering"
flag on all the interfaces before removing any of them.
Signed-off-by: Alan Stern <[email protected]>
Tested-by: Éric Piel <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
commit 042fe1a2805b175b318db0fa10cf8c9df192fa7c
Author: Alan Stern <[email protected]>
Date: Fri Jul 1 16:43:02 2011 -0400
USB: fix regression occurring during device removal
commit e534c5b831c8b8e9f5edee5c8a37753c808b80dc upstream.
This patch (as1476) fixes a regression introduced by
fccf4e86200b8f5edd9a65da26f150e32ba79808 (USB: Free bandwidth when
usb_disable_device is called). usb_disconnect() grabs the
bandwidth_mutex before calling usb_disable_device(), which calls down
indirectly to usb_set_interface(), which tries to acquire the
bandwidth_mutex.
The fix causes usb_set_interface() to return early when it is called
for an interface that has already been unregistered, which is what
happens in usb_disable_device().
Signed-off-by: Alan Stern <[email protected]>
Tested-by: Sarah Sharp <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
commit 8c603fc5c6608bac3e3df537f8f4a70a24e4edd0
Author: Alan Stern <[email protected]>
Date: Wed Jun 15 16:29:16 2011 -0400
USB: don't let the hub driver prevent system sleep
commit cbb330045e5df8f665ac60227ff898421fc8fb92 upstream.
This patch (as1465) continues implementation of the policy that errors
during suspend or hibernation should not prevent the system from going
to sleep.
In this case, failure to turn on the Suspend feature for a hub port
shouldn't be reported as an error. There are situations where this
does actually occur (such as when the device plugged into that port
was disconnected in the recent past), and it turns out to be harmless.
There's no reason for it to prevent a system sleep.
Also, don't allow the hub driver to fail a system suspend if the
downstream ports aren't all suspended. This is also harmless (and
should never happen, given the change mentioned above); printing a
warning message in the kernel log is all we really need to do.
Signed-off-by: Alan Stern <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
commit c4c3048b2bda6562bcdf5507bb9c6c248a87f675
Author: Alan Stern <[email protected]>
Date: Wed Jun 15 16:27:43 2011 -0400
USB: don't let errors prevent system sleep
commit 0af212ba8f123c2eba151af7726c34a50b127962 upstream.
This patch (as1464) implements the recommended policy that most errors
during suspend or hibernation should not prevent the system from going
to sleep. In particular, failure to suspend a USB driver or a USB
device should not prevent the sleep from succeeding:
Failure to suspend a device won't matter, because the device will
automatically go into suspend mode when the USB bus stops carrying
packets. (This might be less true for USB-3.0 devices, but let's not
worry about them now.)
Failure of a driver to suspend might lead to trouble later on when the
system wakes up, but it isn't sufficient reason to prevent the system
from going to sleep.
Signed-off-by: Alan Stern <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
commit a96e5158f0cab04b29e9236f04214c056efe3a04
Author: Sarah Sharp <[email protected]>
Date: Sun Jun 5 23:22:22 2011 -0700
USB: Free bandwidth when usb_disable_device is called.
commit fccf4e86200b8f5edd9a65da26f150e32ba79808 upstream.
Tanya ran into an issue when trying to switch a UAS device from the BOT
configuration to the UAS configuration via the bConfigurationValue sysfs
file. Before installing the UAS configuration, set_bConfigurationValue()
calls usb_disable_device(). That function is supposed to remove all host
controller resources associated with that device, but it leaves some state
in the xHCI host controller.
Commit 0791971ba8fbc44e4f476079f856335ed45e6324
usb: allow drivers to use allocated bandwidth until unbound
added a call to usb_disable_device() in usb_set_configuration(), before
the xHCI bandwidth functions were invoked. That commit fixed a bug, but
also introduced a bug that is triggered when a configured device is
switched to a new configuration.
usb_disable_device() goes through all the motions of unbinding the drivers
attached to active interfaces and removing the USB core structures
associated with those interfaces, but it doesn't actually remove the
endpoints from the internal xHCI host controller bandwidth structures.
When usb_disable_device() calls usb_disable_endpoint() with reset_hardware
set to true, the entries in udev->ep_out and udev->ep_in will be set to
NULL. Usually, when the USB core installs a new configuration,
usb_hcd_alloc_bandwidth() will drop all non-NULL endpoints in udev->ep_out
and udev->ep_in before adding any new endpoints. However, when the new
UAS configuration was added, all those entries were null, so none of the
old endpoints in the BOT configuration were dropped.
The xHCI driver blindly added the UAS configuration endpoints, and some of
the endpoint addresses overlapped with the old BOT configuration
endpoints. This caused the xHCI host to reject the Configure Endpoint
command. Now that the xHCI driver code is cleaned up to reject a
double-add of active endpoints, we need to fix the USB core to properly
drop old endpoints in usb_disable_device().
If the host controller driver needs bandwidth checking support, make
usb_disable_device() call usb_disable_endpoint() with
reset_hardware set to false, drop the endpoints from the xHCI host
controller, and then call usb_disable_endpoint() again with
reset_hardware set to true.
The first call to usb_disable_endpoint() will cancel any pending URBs and
wait on them to be freed in usb_hcd_disable_endpoint(), but will keep the
pointers in udev->ep_out and udev->ep in intact. Then
usb_hcd_alloc_bandwidth() will use those pointers to know which endpoints
to drop.
The final call to usb_disable_endpoint() will do two things:
1. It will call usb_hcd_disable_endpoint() again, which should be harmless
since the ep->urb_list should be empty after the first call to
usb_disable_endpoint() returns.
2. It will set the entries in udev->ep_out and udev->ep in to NULL, and call
usb_hcd_disable_endpoint(). That call will have no effect, since the xHCI
driver doesn't set the endpoint_disable function pointer.
Note that usb_disable_device() will now need to be called with
hcd->bandwidth_mutex held.
This should be backported to kernels as old as 2.6.32.
Signed-off-by: Sarah Sharp <[email protected]>
Reported-by: Tanya Brokhman <[email protected]>
Cc: [email protected]
Cc: Alan Stern <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Does anyone know if any of those changes could kill a USB flash drive?
Linux fun fact #3487: if you remove the uhci-hcd module, your usb keyboard and mouse stop working (luckily I still have an old non-usb keyboard)
Last edited by Xyne (2011-07-22 11:49:37)I had a while ago similar problem with USB memory stick. At the end, I don't know why, just formatting it using WinXP helped me.
S-
Last edited by StenM (2011-07-22 17:56:32) -
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) -
Hi,
I am running XP SP 2, on a Dell Vostro 1000, Palm OS Garnet v5.4.7 on a Tungsten E2. I have worked though issues relating to synchronization, Outlook 2007, Docs to Go, etc., in the past. Thank you board members!
Once I worked thru all the initial problems, my Tungsten E2 was sync' ing beautifully to my laptop until a few days ago. There have been no changes (I know of) to the configuration, but now I receive "The connection between your device and the desktop could not be established. Please check your setup and try again." On the laptop I sometimes get "USB device not recognized." I am unclear why I get the PC message sometimes and not others.
I have tried the following: (not necc exactly in this order)
Double checked Hot Sync Mgr settings: Local USB (ver. 6.0.1)
Reset the Palm (multiple times)
Rebooted the laptop (multiple times before and after the Palm resets)
Went to Support Libraries including http://kb.palm.com/SRVS/CGI-BIN/WEBCGI.EXE/,/?St=57,E=0000000001060189973,K=9550,Sxi=3,Case=Obj(3695...)
and http://kb.palm.com/SRVS/CGI-BIN/WEBCGI.EXE?New,Kb=PalmSupportKB,ts=Palm_External2001,Case=obj(1409)
Followed the steps in "Start Here" found at http://forums.palm.com/palm/board/message?board.id=windows_hotsync&thread.id=26057
Moved Backup directory as per a post on this forum
Looked for a deleted a file called "Graffiti_ShortCuts_____________" per a post on this forum
Followed the steps in HotSync troubleshooter guide you can run through located on
http://kb.palm.com
Went into Device Manager - found it shows no yellow ! 's
Followed Device Mgr Troubleshooter - went all the way thru with no solution
Tried all four USB ports - the PC's bell-like tone does not sound when I disconnect or reconnect the Plam's cradle like it does when I conn/disconnect other USB devices -I think that is a clue. ...?
Cleaned the Palm's contacts (and cradle's contacts with a old, dry toothbrush)
Read all the posts under "USB device not recognized."
OK, I'm at a loss, can anyone help me? Many thanks in advance!
~Bob
Post relates to: Tungsten E2Hello!
Using a cradle with the Tungsten E2? Tried bypassing the cradle and just use the hotsync cable? Tried a different computer yet? Somehow, the PC is having problems getting a signal from the device. I assume you have the laptop charger plugged into the laptop during this? Not going through a docking station or port-replicator.
One crazy thing you can try is unplug the charger from your laptop, remove the battery from the laptop and leave it out for like 10mins and put it back in and reboot the laptop. This should not cause side effects but still contact your OEM to make sure that nothing else is needed after leaving the battery out for extended period of time. Keep me posted.
Post relates to: Treo 650 (Unlocked GSM) -
AFTER TYPING INCORRECT PASSCODE MULTIPLE TIMES MY PHONE GOT DISABLED. IT SAYS CONNECT TO ITUNES BUT ON CONNECTING IT SAYS USB DEVICE NOT FOUND.
See this support document for instructions on how to deal with a disabled device or forgetting your passcode. iOS: Forgot passcode or device disabled
Maybe you are looking for
-
Trace file in different location
Dear all, 11g on Solaris 10. My oracle home (dump location) located in a file system of 10GB.. I need to trace a session which will generate huge trace file. Is there anyway I can have the trace file generated in a different location where I have eno
-
Steps to hookup my HP Officejet G85xi to Airport Express Base Station
felix, could you please provide me the steps to connect the above printer to the base station. currently i have the base station connected directly to a G5 iMac. however, i wish to use the printer from other computers in my house. thanks, Dave
-
HT201210 cannot restore ipod due to passode and new laptop
Hi, this is a tough one! Daughter disabled ipod touch with wrong passcodes. I have since got a new laptop which this ipod was not synct to. Therefore itunes does not recognise it and will not restore, even in recovery mode. HELP! lol
-
Can I use my Iphone 5c (bought in Belgium) in the USA?
Hello, I'm belgian and am going to spend one year in America. As I bought my Iphone 5C (A1507) in Belgium, I would like to know if I will be able to use it in the USA? Thanks
-
ClassCastException using bpelx:append
When attempting to model sample 126 Data Aggregator I receive a ClassCastException. The snippet of bpel code I'm using looks like this: <assign name="Assign_1"> <copy> <from expression="string('one')"/> <to variable="outputVariabl