Home of the Squeezebox™ & Transporter® network music players.
Page 2 of 4 FirstFirst 1234 LastLast
Results 11 to 20 of 36
  1. #11
    Senior Member chill's Avatar
    Join Date
    Mar 2007
    Location
    Nottingham, UK
    Posts
    2,095
    Quote Originally Posted by scslite View Post
    Logs attached. Also tried to make sure pins have good contact.
    From the generic cable:
    Code:
    [    1.131641] usb 1-1: new high-speed USB device number 2 using xhci_hcd\
    [    1.314285] usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.21\
    [    1.314293] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0\
    [    1.314300] usb 1-1: Product: USB2.0 Hub\
    [    1.315758] hub 1-1:1.0: USB hub found\
    [    1.316011] hub 1-1:1.0: 4 ports detected\
    [    1.641619] usb 1-1.4: new high-speed USB device number 3 using xhci_hcd\
    [    1.772399] usb 1-1.4: New USB device found, idVendor=245f, idProduct=0815, bcdDevice= 1.97\
    [    1.772406] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3\
    [    1.772413] usb 1-1.4: Product: Qutest\
    [    1.772420] usb 1-1.4: Manufacturer: Chord Electronics Ltd\
    [    1.772426] usb 1-1.4: SerialNumber: 413-001\
    From the Curious cable:
    Code:
    [    1.141638] usb 1-1: new high-speed USB device number 2 using xhci_hcd\
    [    1.324076] usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.21\
    [    1.324084] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0\
    [    1.324091] usb 1-1: Product: USB2.0 Hub\
    [    1.330887] hub 1-1:1.0: USB hub found\
    [    1.331135] hub 1-1:1.0: 4 ports detected\
    [    2.462149] usb 1-1-port4: Cannot enable. Maybe the USB cable is bad?\

  2. #12
    Senior Member
    Join Date
    Jan 2011
    Location
    Staffordshire. UK
    Posts
    4,238
    Quote Originally Posted by LiFePO4 View Post
    I have zero experience with pcp on the USB side. I only use optical solutions, so just making a suggestion. I wasn't even aware there is a Qutest USB setting. I thought USB Audio is the only option on the dropdown box for USB DACs, so total noob here.

    My suggestion is try powering on the Qutest with your MBA. Turn on your RPi. Unplug USB A from MBA and plug into RPi.

    I believe Chord DACs need the 5V VBUS (Thin orange cable on your Curious) to initiate a handshake to activate the Qutest. Maybe after activating, if it stays PWR ON, pcp will recognize?

    Maybe some setting not initiating the handshake? Just hope the Qutest doesn't PWR OFF or de-activate when you pull out the USB cable.

    If it's recognized, you can troubleshoot the setting from there...

    GL

    EDIT: USB Audio setting the same issue? Have you tried another OS on the RPI to narrow down?

    From the online info

    Device power supply: 5v 2amp Micro USB
    so I don't think the Mac will meet that requirement, otherwise I agree, try it on a raspberry pi OS, simple Desktop, browser playback.

    I know hot plugging can sometimes stir things up but at the OP's own risk

    Quote Originally Posted by chill View Post
    From the generic cable:
    Code:
    [    1.131641] usb 1-1: new high-speed USB device number 2 using xhci_hcd\
    [    1.314285] usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.21\
    [    1.314293] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0\
    [    1.314300] usb 1-1: Product: USB2.0 Hub\
    [    1.315758] hub 1-1:1.0: USB hub found\
    [    1.316011] hub 1-1:1.0: 4 ports detected\
    [    1.641619] usb 1-1.4: new high-speed USB device number 3 using xhci_hcd\
    [    1.772399] usb 1-1.4: New USB device found, idVendor=245f, idProduct=0815, bcdDevice= 1.97\
    [    1.772406] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3\
    [    1.772413] usb 1-1.4: Product: Qutest\
    [    1.772420] usb 1-1.4: Manufacturer: Chord Electronics Ltd\
    [    1.772426] usb 1-1.4: SerialNumber: 413-001\
    From the Curious cable:
    Code:
    [    1.141638] usb 1-1: new high-speed USB device number 2 using xhci_hcd\
    [    1.324076] usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.21\
    [    1.324084] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0\
    [    1.324091] usb 1-1: Product: USB2.0 Hub\
    [    1.330887] hub 1-1:1.0: USB hub found\
    [    1.331135] hub 1-1:1.0: 4 ports detected\
    [    2.462149] usb 1-1-port4: Cannot enable. Maybe the USB cable is bad?\
    Says it all really, at least in this user context of pCP OS

    ronnie

  3. #13
    Senior Member
    Join Date
    Oct 2005
    Location
    Ireland
    Posts
    20,318
    Quote Originally Posted by Man in a van View Post
    I know hot plugging can sometimes stir things up but at the OP's own risk
    I wouldn't go as far as messing with hot pluggin but OP could try enable monitor udev actions/triggers with udevadm and see if anything show up.

    However from the log I think the issue is before udev gets into action.

    I don't know how OP checked the contacts especially if it is just a single pin not making contact.

  4. #14
    Junior Member
    Join Date
    Feb 2021
    Posts
    6
    I'll try to test as suggested by LifePO4 and report back later. The fact that the cable works perfectly when plugged into my MBA means there's some signal that's not on the RPi USB that Squeezlite is not recognizing the Qutest.

    Another thought is does the Qobuz plugin require Squeezlite or is it a more native integration? I'm wondering if Qobuz will work if Squeezelite is bypassed?

    Also have sent my issue to Curious just waiting to hear back.

    Thanks for all the suggestions. Not giving up yet.

  5. #15
    Senior Member chill's Avatar
    Join Date
    Mar 2007
    Location
    Nottingham, UK
    Posts
    2,095
    Quote Originally Posted by scslite View Post
    I'll try to test as suggested by LifePO4 and report back later. The fact that the cable works perfectly when plugged into my MBA means there's some signal that's not on the RPi USB that Squeezlite is not recognizing the Qutest.

    Another thought is does the Qobuz plugin require Squeezlite or is it a more native integration? I'm wondering if Qobuz will work if Squeezelite is bypassed?

    Also have sent my issue to Curious just waiting to hear back.

    Thanks for all the suggestions. Not giving up yet.
    I don't think this has anything to do with Squeezelite. The Pi isn't enabling the Qutest with this cable. Did Squeezelite work with the generic cable? I would send Curious the two log file snippets that I posted above. I would hope that they'll stand by their product and send you a replacement.

  6. #16
    Senior Member
    Join Date
    Oct 2005
    Location
    Ireland
    Posts
    20,318
    Quote Originally Posted by scslite View Post
    I'll try to test as suggested by LifePO4 and report back later. The fact that the cable works perfectly when plugged into my MBA means there's some signal that's not on the RPi USB that Squeezlite is not recognizing the Qutest..
    It is is not squeezelite but from log at level of pcp USB support.

  7. #17
    Junior Member
    Join Date
    Feb 2021
    Posts
    6
    Quote Originally Posted by chill View Post
    I don't think this has anything to do with Squeezelite. The Pi isn't enabling the Qutest with this cable. Did Squeezelite work with the generic cable? I would send Curious the two log file snippets that I posted above. I would hope that they'll stand by their product and send you a replacement.
    Yes squeezlite works with the generic cable and another USB cable I have which is a BBQ Full Rack similar design to the Curious with an isolated power line.

    The logs do show something with the Curious is bad but what? I have not tried another OS on the RPi but may try it as it's also one of the suggested tips on the Curious FAQ.

    As for pins I carefully pulled them up on the RPi to ensure a snug fit of the cable but made no difference.

    BTW, good suggestion. Will send the log files to Curious as well. Also, how do I do this? "enable monitor udev actions/triggers with udevadm"
    Last edited by scslite; 2021-02-22 at 03:36.

  8. #18
    Senior Member
    Join Date
    Oct 2005
    Location
    Ireland
    Posts
    20,318
    Quote Originally Posted by scslite View Post
    "enable monitor udev actions/triggers with udevadm"
    command at shell prompt

    udevadm monitor

    Do a test by plugging and unplugging a "good" device to see messages appear, then try the problem device. If no messages then problem is at a lower level of USB interfacing which would what dmesg log indicates.

  9. #19
    Senior Member
    Join Date
    Jan 2010
    Location
    Hertfordshire
    Posts
    6,594
    Quote Originally Posted by scslite View Post
    Yes squeezlite works with the generic cable and another USB cable I have which is a BBQ Full Rack similar design to the Curious with an isolated power line.

    The logs do show something with the Curious is bad but what? I have not tried another OS on the RPi but may try it as it's also one of the suggested tips on the Curious FAQ.

    As for pins I carefully pulled them up on the RPi to ensure a snug fit of the cable but made no difference.

    BTW, good suggestion. Will send the log files to Curious as well. Also, how do I do this? "enable monitor udev actions/triggers with udevadm"
    If other cables work with your Pi then changing the OS isn't going to help.

    Sent from my Pixel 3a using Tapatalk

  10. #20
    Senior Member
    Join Date
    Oct 2005
    Location
    Ireland
    Posts
    20,318
    Quote Originally Posted by slartibartfast View Post
    If other cables work with your Pi then changing the OS isn't going to help.
    I agree it doesn't seem logical but trying an different OS at least eliminates the possibility of some sort of weird chip initialisation or timing issue which is only apparent with the problem cable.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •