MuxInterfacev2Receive expected sequence ..

15 posts / 0 new
Last post
thebrew
MuxInterfacev2Receive expected sequence ..

Here's a strange one:

I set up an Ubuntu server to share a USB device to my Mac running Mavericks 10.9.2 and the VirtualHere.app.

Worked like a charm! So, so awesome.

In a heart beat I ordered a Raspberry Pi to make that the main sharing "machine" instead.

But with this one, there's no love. The Raspberry Hub and my iPod shows up under USB Hubs, but when I connect to it, nothing happens except my my console continually outputs the following lines:

05/03/14 20.58.36,143 com.apple.usbmuxd[47]: MuxInterfacev2Receive expected sequence 25 got 31 from 0x4-bc1cfec091994fc75c1cde43e0e4ce98fb091feb@0x1100000
05/03/14 20.58.36,152 com.apple.usbmuxd[47]: MuxInterfacev2Receive expected sequence 25 got 32 from 0x4-bc1cfec091994fc75c1cde43e0e4ce98fb091feb@0x1100000
05/03/14 20.58.36,152 com.apple.usbmuxd[47]: MuxInterfacev2Receive expected sequence 25 got 33 from 0x4-bc1cfec091994fc75c1cde43e0e4ce98fb091feb@0x1100000

Any ideas?

Linux raspberrypi 3.10.32+ #648 PREEMPT Fri Feb 28 16:29:56 GMT 2014 armv6l GNU/Linux (Wheezy hard float)
vcgencmd version:
Feb 28 2014 16:46:25
Copyright (c) 2012 Broadcom
version a9ba6435869933cdfd1ad5631b6b9a97affd8806 (clean) (release)

Michael
That looks like a bug in the

Looking at

https://discussions.apple.com/message/23658693#23658693

could you try another cable, also make sure there is a powered hub between the pi and the ipad.

Otherwise its probably a bug in the raspbian kernel...

thebrew
I've tried 3 different cables

I've tried 3 different cables with an iPod 5th gen. (Lightning, iOS 7.1b5), iPad mini (Lightning, iOS 7.1b5), and an iPad 2nd gen. (30-pin iOS 6.0)

All through a powered hub. I've also tried both ports on the Raspberry Pi ..but sadly no luck. Same behavior. :(

I have debug log from VirtualHere.app I can mail to you if you're interested?

The VirtualHere.app occasionally crashes when I test, just as I plug in the device. The following is the output to the console and the resulting crash report. I wonder if that has any clues?

After the crash, I get a "The application "VirtualHere.app" cannot be opened. -600" error message. A reboot gets things back on track. (I read that Bonjour could cause some wackiness, so I've turned off Auto-find Hubs and manually put on the IP and port of the Pi.)

06/03/14 09.37.17,011 VirtualHere[4731]: VirtualHere crashed, backtrace follows...
06/03/14 09.37.17,012 VirtualHere[4731]: [bt]: 0 VirtualHere 0x0000000100009446 _ZN11Application20OnFatalExceptionImplEv + 66
06/03/14 09.37.17,012 VirtualHere[4731]: [bt]: 1 VirtualHere 0x00000001004a986f wxFatalSignalHandler + 31
06/03/14 09.37.17,012 VirtualHere[4731]: [bt]: 2 libsystem_platform.dylib 0x00007fff972205aa _sigtramp + 26
06/03/14 09.37.17,012 VirtualHere[4731]: [bt]: 3 ??? 0x000061000013b760 0x0 + 106652629186400
06/03/14 09.37.17,012 VirtualHere[4731]: [bt]: 4 VirtualHere 0x00000001004af1bf _ZN12wxEvtHandler23ProcessEventIfMatchesIdERK21wxEventTableEntryBasePS_R7wxEvent + 93
06/03/14 09.37.17,013 VirtualHere[4731]: [bt]: 5 VirtualHere 0x00000001004afbf7 _ZN12wxEvtHandler23SearchDynamicEventTableER7wxEvent + 179
06/03/14 09.37.17,013 VirtualHere[4731]: [bt]: 6 VirtualHere 0x00000001004b0f3a _ZN12wxEvtHandler11TryHereOnlyER7wxEvent + 44
06/03/14 09.37.17,013 VirtualHere[4731]: [bt]: 7 VirtualHere 0x00000001004b0fba _ZN12wxEvtHandler19ProcessEventLocallyER7wxEvent + 46
06/03/14 09.37.17,013 VirtualHere[4731]: [bt]: 8 VirtualHere 0x00000001004b06e4 _ZN12wxEvtHandler12ProcessEventER7wxEvent + 238
06/03/14 09.37.17,013 VirtualHere[4731]: [bt]: 9 VirtualHere 0x00000001004b0084 _ZN12wxEvtHandler20ProcessPendingEventsEv + 638
06/03/14 09.37.17,013 VirtualHere[4731]: [bt]: 10 VirtualHere 0x00000001003edb7b _ZN16wxAppConsoleBase20ProcessPendingEventsEv + 193
06/03/14 09.37.17,013 VirtualHere[4731]: [bt]: 11 VirtualHere 0x0000000100493832 _ZN13wxCFEventLoop26CommonModeObserverCallBackEP19__CFRunLoopObserveri + 48
06/03/14 09.37.17,013 VirtualHere[4731]: [bt]: 12 CoreFoundation 0x00007fff8bf04ee7 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23
06/03/14 09.37.17,013 VirtualHere[4731]: [bt]: 13 CoreFoundation 0x00007fff8bf04e57 __CFRunLoopDoObservers + 391
06/03/14 09.37.17,013 VirtualHere[4731]: [bt]: 14 CoreFoundation 0x00007fff8bef65f8 __CFRunLoopRun + 776
06/03/14 09.37.17,013 VirtualHere[4731]: [bt]: 15 CoreFoundation 0x00007fff8bef60b5 CFRunLoopRunSpecific + 309
06/03/14 09.37.17,013 VirtualHere[4731]: VirtualHere backtrace complete
06/03/14 09.37.17,470 ReportCrash[4901]: Failed to create CSSymbolicatorRef for VirtualHere[4731]
06/03/14 09.37.17,912 ReportCrash[4901]: Failed to create dSYM-less CSSymbolicatorRef for VirtualHere[4731]
06/03/14 09.37.18,306 ReportCrash[4901]: Saved crash report for VirtualHere[4731] version 2.0.9 (2.0.9) to VirtualHere_2014-03-06-093718_Mac-3.crash

->

Process: VirtualHere [4731]
Path: /Applications/VirtualHere.app/Contents/MacOS/VirtualHere
Identifier: com.virtualhere.vhui
Version: 2.0.9 (2.0.9)
Code Type: X86-64 (Native)
Parent Process: launchd [184]
Responsible: VirtualHere [4731]
User ID: 501

Date/Time: 2014-03-06 09:37:17.030 +0100
OS Version: Mac OS X 10.9.2 (13C64)
Report Version: 11
Anonymous UUID: 3DB8A444-E19B-5FAC-4770-25F4E040AF31

Sleep/Wake UUID: 2F65FA09-AA0A-462C-A6B7-CC7157E65D44

Crashed Thread: Unknown

Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000030000005c

Backtrace not available

Unknown thread crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x00007fff7c138310 rcx: 0x00007fff5fbfdb28 rdx: 0x0000000000000000
rdi: 0x0000000000000707 rsi: 0x0000000000000006 rbp: 0x00007fff5fbfdb50 rsp: 0x00007fff5fbfdb28
r8: 0x00000000002172f0 r9: 0x00000000d0dbf380 r10: 0x0000000008000000 r11: 0x0000000000000206
r12: 0x00006080002293a0 r13: 0x0000000100724eae r14: 0x0000000000000006 r15: 0x0000610000245ac0
rip: 0x00007fff8afa2866 rfl: 0x0000000000000206 cr2: 0x0000000004ddc000

Logical CPU: 0
Error Code: 0x02000148
Trap Number: 133

Binary images description not available

External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 5
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 9897
thread_create: 1
thread_set_state: 2425

thebrew
Edit: crashes don't occur

Edit: crashes don't occur when I plug in the device, but at the point where the app tries to connect to the device.

It'll be displayed as available in the tree, but then occasionally crashes when I right click and choose to connect to it.

Michael
Hi thebrew, I think i fixed

Hi thebrew, I think i fixed the crash, could you download version 2.1.0. If it crashes again could you send me the crash report log to mail@virtualhere.com that will now contain a detailed stack trace when using 2.1.0 of the client.

thebrew
So far no crashes. :)

So far no crashes. :)

Still the same MuxInterfacev2Receive issue though. I've been troubleshooting a bit more, so here's my findings:

vhusbdpi for the latest Raspberry Pi (currently 3.10.33+ #654) works fine with every USB device I've tested (keyboard, mouse, BD-writer, hard disk USB interface). But any iOS device running version 6.0 or above produces the console log messages I pasted above. Sadly I don't have any iOS devices with iOS 5 but my iPod and iPhone 3G with iOS 4.6.1 works fine.

I don't know if 6.0 silently added the beginnings of the iOS 7 "Trust This Computer" dialog that pops up the first time you connect a new device, but I wonder if this could be at least part of the reason. Whenever I attach my device it asks me to trust it, when I tap "Trust" VirtualHere disconnects from it and it then shows up a second or two later, but reconnecting just shows the "Trust" dialog again. And so on.

As you said, it could be a Raspbian kernel issue, I just wanted to feed you some more info in case it could be related to vhusbdpi.

Is it just me experiencing this issue?

thebrew
Damn. I need a copy editor.

Damn. I need a copy editor. Make that "iOS 4.2.1".

Michael
Thanks for the detailed

Thanks for the detailed feedback. I made a change to the threading in the osx driver, could download version 2.1.2 and see if that helps. Reboot your mac before running version 2.1.2 as it will need to upgrade the driver...

thebrew
Sorry, no. Same.

Sorry, no. Same.

Michael
OK good news is ive been able

OK good news is ive been able to reproduce the issue on my office test setup, havent found out why it is doing that yet, but at least i can use my usb hardware protocol sniffer...

thebrew
Beautiful :) Fingers crossed!

Beautiful :) Fingers crossed!

Michael
OK i got it working on my pi,

OK i got it working on my pi, indeed it is a bug in the latest raspbian, i dont know what it is but this seems to fix it:

1. Download an old raspbian image, i found one here
http://www.xs4all.nl/~sbp/rpi/2013-09-10-wheezy-raspbian-nox.zip

2. wget http://www.virtualhere.com/sites/default/files/usbserver/raspbian_wheezy...

3. chmod +x ./vhusbdpin

4. sudo apt-get avahi-daemon avahi-client-dev

5. ./vhusbdpin -b

Then give it a try.

thebrew
This is fantastic. Working!

This is fantastic. Working! Thank you so much for your time. License bought in a heartbeat.

It doesn't even need an external hub when using a Retina iPad mini. :)

For other Mac users following along at home, here's a step-by-step guide:

* Download http://www.xs4all.nl/~sbp/rpi/2013-09-10-wheezy-raspbian-nox.zip and unzip the .img file.
* Insert the SD card you want to wipe and install to into your Mac.
* Open Terminal and run:
* "diskutil list" to see what the card has been mounted as. In this example it's: /dev/disk3
* "diskutil unmountDisk /dev/disk3" to take it offline. (Verify that it disappears from the Finder so you don't accidentally wipe the wrong drive..!)
* "sudo dd bs=1m if= of=/dev/disk3". It'll ask for your super user password. Wait patiently as it transfers the 2 gigs. If you like watching paint dry, you can open Activity Monitor, click the "Disk" tab and filter on "dd" to see how long it's gotten in the process.
* "diskutil eject /dev/disk3" when it's done to eject the card safely.

Insert the card into your Raspberry Pi and connect the power.
Back to the Terminal on your Mac:

* "ssh pi@" (If you don't know the IP, you can either check the DHCP clients on your router or you can type in "ifconfig" to see what eth0 says for "inet addr".
* The default password for user pi is: raspberry

In the remote session type:

* "passwd" to change the default password.

Install the service:

* "wget http://www.virtualhere.com/sites/default/files/usbserver/raspbian_wheezy..."
* "chmod +x ./vhusbdpi"
* "sudo apt-get update"
* "sudo apt-get install avahi-daemon libavahi-client-dev libgtk2.0-0"
* "sudo mv vhusbdpi /usr/sbin"
* "wget http://www.virtualhere.com/sites/default/files/usbserver/scripts/vhusbdpi"
* "sudo chmod +x ./vhusbdpi"
* "sudo mv vhusbdpi /etc/init.d"
* "sudo update-rc.d vhusbdpi defaults"
* "sudo reboot"

Boom. You have a remote USB port. :)

thebrew
Please delete my previous

Please delete my previous post (and this one :) - I forgot it would be posted as HTML.. Next post will have the complete guide.

thebrew
This is fantastic. Working!

This is fantastic. Working! Thank you so much for your time. License bought in a heartbeat.

It doesn't even need an external hub when using a Retina iPad mini. :)

For other Mac users following along at home, here's a step-by-step guide:

* Download http://www.xs4all.nl/~sbp/rpi/2013-09-10-wheezy-raspbian-nox.zip and unzip the .img file.
* Insert the SD card you want to wipe and install to into your Mac.
* Open Terminal and run:
* "diskutil list" to see what the card has been mounted as. In this example it's: /dev/disk3
* "diskutil unmountDisk /dev/disk3" to take it offline. (Verify that it disappears from the Finder so you don't accidentally wipe the wrong drive..!)
* "sudo dd bs=1m if=/path/to/the/unzipped.img of=/dev/disk3". (It'll ask for your super user password.) Wait patiently as it transfers the 2 gigs. If you like watching paint dry, you can open Activity Monitor, click the "Disk" tab and filter on "dd" to see how long it's gotten in the progress.
* "diskutil eject /dev/disk3" when it's done to eject the card safely.

Insert the card into your Raspberry Pi and connect the power.
Back to the Terminal on your Mac:

* "ssh pi@192.168.1.101" ..replacing 192.168.1.101 with the address of your Pi. (If you don't know the IP, you can either check the DHCP clients on your router or you can type in "ifconfig" to see what eth0 says for "inet addr".
* The default password for user pi is: raspberry

In the remote session type:

* "passwd" to change the default password.

Install the service:

* "wget http://www.virtualhere.com/sites/default/files/usbserver/raspbian_wheezy...
* "chmod +x ./vhusbdpi"
* "sudo apt-get update"
* "sudo apt-get install avahi-daemon libavahi-client-dev libgtk2.0-0"
* "sudo mv vhusbdpi /usr/sbin"
* "wget http://www.virtualhere.com/sites/default/files/usbserver/scripts/vhusbdpi"
* "sudo chmod +x ./vhusbdpi"
* "sudo mv vhusbdpi /etc/init.d"
* "sudo update-rc.d vhusbdpi defaults"
* "sudo reboot"

Boom. You have a remote USB port. :)

Log in or register to post comments