HP PSC 1400 wont get recognized properly

2 posts / 0 new
Last post
tristank
HP PSC 1400 wont get recognized properly

I'm running 10.9.4 with a raspberry pi (model B) and latest raspbian. I've a HP PSC 1400 Series Printer connected to the Pi with powered usb hub, which works properly with CUPS and all that stuff. When trying to make the printer available to Mac OS X for the first time, my computer immediately crashed and rebooted. The second time the device connect but still isnt available for Mac OS X.

Some pictures:
https://img.bi/#/91alg9m!JpVxbS3e9PvURkDpN7RopuuWAXC4g8e1L7eJ0d1Z
https://img.bi/#/zc50UGn!qiW9brM7JUiXAoziIp5liBOqC5TBMVXuLIbso4sQ

Excerpt from the console log

06.08.14 16:08:02,000 kernel[0] USBF: 3.182 com_virtualhere_vhhcd::init, compiled Jul 28 2014 15:30:02
06.08.14 16:47:42,000 kernel[0] VirtualHere (map: 0xffffff8021dedf00) triggered DYLD shared region unnest for map: 0xffffff8021dedf00, region 0x7fff92a00000->0x7fff92c00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
06.08.14 16:48:18,000 kernel[0] USBF: 3.452 com_virtualhere_vhhcd::init, compiled Jul 28 2014 15:30:02
06.08.14 16:50:01,773 VirtualHere[631] Bartender: Loaded BartenderHelperSeventy
06.08.14 16:50:12,000 kernel[0] USBF: 116. 49 com_virtualhere_vhhcd::bindDevice, Full speed device at remote address 1134 is now attached to local port 1 and is device zero
06.08.14 16:50:12,000 kernel[0] VirtualHere (map: 0xffffff802a56f690) triggered DYLD shared region unnest for map: 0xffffff802a56f690, region 0x7fff8a200000->0x7fff8a400000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
06.08.14 16:50:12,000 kernel[0] USBF: 116.361 com_virtualhere_vhhcd::setDeviceAddress(2) port 1 assigned to remote address 1134
06.08.14 16:50:12,000 kernel[0] USBF: 116.522 com_virtualhere_vhhcd::handleUIMDeleteEndpointForNonRootHub port 1 now back to device zero
06.08.14 16:50:12,000 kernel[0] USBF: 116.705 com_virtualhere_vhhcd::setDeviceAddress(2) port 1 assigned to remote address 1134
06.08.14 16:50:40,000 kernel[0] USBF: 144.785 com_virtualhere_vhhcd::RootHubResetChangeConnection device at port 1 has been disconnected
06.08.14 16:51:43,000 kernel[0] USBF: 3.852 com_virtualhere_vhhcd::init, compiled Jul 28 2014 15:30:02
06.08.14 16:56:07,000 kernel[0] VirtualHere (map: 0xffffff8029c6cb40) triggered DYLD shared region unnest for map: 0xffffff8029c6cb40, region 0x7fff8fe00000->0x7fff90000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
06.08.14 16:56:09,173 VirtualHere[1319] Bartender: Loaded BartenderHelperSeventy
06.08.14 16:56:16,000 kernel[0] USBF: 275.927 com_virtualhere_vhhcd::bindDevice, Full speed device at remote address 1134 is now attached to local port 1 and is device zero
06.08.14 16:56:16,000 kernel[0] USBF: 276.222 com_virtualhere_vhhcd::setDeviceAddress(2) port 1 assigned to remote address 1134
06.08.14 16:56:16,000 kernel[0] USBF: 276.600 com_virtualhere_vhhcd::handleUIMDeleteEndpointForNonRootHub port 1 now back to device zero
06.08.14 16:56:16,000 kernel[0] USBF: 276.798 com_virtualhere_vhhcd::setDeviceAddress(2) port 1 assigned to remote address 1134

Michael
Could you try the following

Could you try the following

Open the osx command terminal and type :

sudo kextcache -system-prelinked-kernel

then type

sudo kextcache -system-caches

Then reboot and see if that fixes the issue. if not perhaps if you could send your ip details i will remotely connect with my client. mail@virtualhere.com and debug that way

Log in or register to post comments