search for: usb3.0

Would it be a usefull addition to memdisk's "pause" parameter if it showed the loading speed for the specified disk image file? The idea is to verify if a device is really loading an operating system's data at the intended device/controller/interface/bus (etc) speed. My own system has a habit of setting usb2.0 interface to 1.1-speeds for example. With (hopefully) bootable

Is there any documentation available about what block size MEMDISK uses to load (big iso/harddisk) image files? Experimenting with cptime.c32 on a Lexar Triton Jumpdrive (64GB, 170MB/s read in Windows, 150MB/s write in Windows) on bootable USB3.0 resulted in the following, depending on specified block size: * 2048 bytes --> 25MB/s * 2MB --> 61MB/s It would be nice to know at which speed

I was reading the Wiki page here: http://wiki.xen.org/wiki/VTd_HowTo don''t know how updated it is, BUT at the top it said: -------------------- -------------------- -------------------- -------------------- -------------------- -------------------- _Xen 4.1 xl tools notes _ * Only devices with FLR capabilities are supported. * Passing through a PCI card without FLR capability

Dear all, (please Cc) I am running latest kernel (3.17-rc6) and I see corruption of an usb3.0 device usb stick. Strange errors, impossibility to mount. Repeated unplugging and replugging helps sometimes, in all cases recovery is necessary. Is this a know problem, a problem of my system Debian/sid, uptodate, self-compiled kernel of the suspend program (that initiates the suspend), the usb

Hi all, I'm booting Centos6 from a usb 3.0 stick. This works fine as long as the usb-stick is connected to a usb 2.0 port. Once I plug the the usb-stick into a blue usb 3.0 port centos fails on mounting the root filesystem. Any hints on that? Regards .....Volker

On Sun, Nov 17, 2013 at 2:12 AM, Michael B Allen <ioplex at gmail.com> wrote: > The problem is USB. I have an external keyboard+mouse connected by USB > and if I remove it I can successfully suspend and resume. If I plug in > a USB MIDI keyboard, again, I cannot suspend. So it seems any USB > connection breaks suspend. It seems I have fixed the problem! If I disable the

On Nov 25, 2014, at 8:17 PM, Victor Porton <porton at narod.ru> wrote: > Well, also below in dmesg: > > [ 190.249219] usb 3-1.3: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 -110 is -ETIMEDOUT. > 26.11.2014, 03:05, "Victor Porton" <porton at narod.ru>: >> A fragment of dmesg output (here idVendor=0665, idProduct=5161 is the

Well, also below in dmesg: [ 190.249219] usb 3-1.3: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 26.11.2014, 03:05, "Victor Porton" <porton at narod.ru>: > A fragment of dmesg output (here idVendor=0665, idProduct=5161 is the UPS; the webcam is idVendor=17a1, idProduct=0128): > > [ ???1.317085] usb 4-1: new high-speed USB device number 2

On Sat, 27 Sep 2014, Norbert Preining wrote: > Dear all, > > (please Cc) > > I am running latest kernel (3.17-rc6) and I see corruption of an usb3.0 > device usb stick. Strange errors, impossibility to mount. > > Repeated unplugging and replugging helps sometimes, in all cases > recovery is necessary. > > Is this a know problem, a problem of my system >

Hello, I''m experimenting with Xen. I managed to get running Windows8 Enterprise Evaluation in domU and passed through an ExpressCard34 USB3.0 controller to which I connect things. I have an external USB sound card working in domU just fine but when I''m trying to connect another USB sound capable device I get that error. If I open properties of the faulty device in Windows Device

I am use to low random entropy on my arm boards, not an intel. On my Lenovo x120e, cat /proc/sys/kernel/random/entropy_avail reports 3190 bits of entropy. On my armv7 with Centos7 I would get 130 unless I installed rng-tools and then I get ~1300. SSH into one and it drops back to 30! for a few minutes. Sigh. Anyway on my new Zotac nano ad12 with an AMD E-1800 duo core, I am seeing 180.

https://bugzilla.samba.org/show_bug.cgi?id=11578 Bug ID: 11578 Summary: Rsync does start with an error directly connecting an USB drive to a port Product: rsync Version: 3.1.1 Hardware: x64 OS: Linux Status: NEW Severity: normal Priority: P5 Component: core

maybe i have solved this issue, i unplugged APC BackUPS from USB 2.0 and PLUGGED INTO USB 3.0 and now it works prefectly at first time without any side effects, strange, this shoud be working since USB 1.0 so ups driver is configured OK, this config works ok for backups, this looks like there is no problem with detection of UPS but with USB driver or something around so simply if somebody has