Skip to main content

MTP - Oh how I love to hate you....

TL; DR:  I can't sync my android tablet (Nvidia Shield) with Fedora via MTP if I am using a USB Hub?


So, in fairness... I don't actually *hate* MTP.  I'm sure it is probably fairly awesome at doing whatever it is that MTP should do.  I'm just miffed at the moment because Android switched (a long time ago, I might add) to MTP for USB connections.

Before, I could (essentially) directly mount the SD card in my tablet/phone/toaster and manage it using my archaic methods.  Now.. I have to conform to using the mtp methodology... which is fine.

However - now I am stuck..

Feb  3 10:15:18 neo mtp-probe: bus: 1, device: 28 was not an MTP device

Fun...
Syslog tells me the device is:
 /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2.3/1-1.2.3.3

At some point I will need to dig in to the output from...
# udevadm test /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2.3/1-1.2.3.




 Specifially...
/usr/lib/udev/rules.d/50-udev-default.rules
/usr/lib/udev/rules.d/69-libmtp.rules


Now... fortunately before I got too out of control trying to "fix" this... I tried plugging my tablet directly in to the machine... and everything was fine?
/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2




Comments

Popular posts from this blog

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...

PXE boot a LiveCD image

Summary: I have wanted to build a kickstart environment which hosted a "rescue CD" or LiveCD to allow you to boot over the network after you blew your stuff up and needed to repair a few things.  Today I have worked through a method of doing so, with the help of the people who published a succinct script with the Red Hat Enterprise Virtualization Hypervisor.  (the script will be at the bottom of this post - if I have somehow not followed the GPL, please let me know and I will correct whatever is necessary) NOTE/Warning: The boot will fail due the initrd being too large (645mb).  I'm not sure how to proceed.  This procedure worked for RHEVh, because it is quite a bit smaller.  Hopefully I can report back with progress on this? :-$ Procedure: download your LiveCD image to /export/isos/RESCUE/Fedora-16-i686-Live-Desktop.iso # cd /var/tmp # vi livecd-iso-to-pxeboot (populate the file with the script shown below) # chmod 754 ./livecd-iso-to-pxeb...

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.