Posts: 3 | Thanked: 0 times | Joined on Feb 2008
#1
I've done a lot of searching and found a lot of posts that suggest it will work, but I haven't been able to make it work.

Here is what I want to do. I have a Dared USB amplifier. I would like to connect it to the n800 to play my music collection and Rhapsody. It appears as if there is no driver in OS2008 that recognizes the Burr-Brown DAC in the Dared.

If you haven't heard the Dared, it is an amazing little piece of hardware designed to make good music out of a USB stream. The Dared has a Burr-Brown DAC and works without any special software under WinDoze. I haven't tried it with a Linux PC but if I need to, I will find a way.

Here's the error I get on the screen of the N800 when I perform the
echo host > .../mode command.

Unable to Connect. No filesystem available.

Here is the dmesg output:

[383428.070312] tusb_source_power 629: VBUS a_wait_vrise, devctl 81 otg 184 conf c0010001 prcm 00a80500
[383428.242187] musb_stage0_irq 646: CONNECT (a_host) devctl 5d
[383428.242187] hub 1-0:1.0: state 8 ports 1 chg 0000 evt 0000
[383428.242187] usb usb1: usb auto-resume
[383428.242187] usb usb1: finish resume
[383428.242187] hub 1-0:1.0: hub_resume
[383428.265625] hub 1-0:1.0: port 1, status 0101, change 0001, 12 Mb/s
[383428.421875] hub 1-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101
[383428.546875] usb 1-1: new full speed USB device using musb_hdrc and address 2
[383428.679687] usb 1-1: ep0 maxpacket = 8
[383428.679687] usb 1-1: skipped 4 descriptors after interface
[383428.679687] usb 1-1: skipped 2 descriptors after interface
[383428.679687] usb 1-1: skipped 1 descriptor after endpoint
[383428.679687] usb 1-1: skipped 2 descriptors after interface
[383428.679687] usb 1-1: skipped 1 descriptor after endpoint
[383428.679687] usb 1-1: default language 0x0409
[383428.679687] usb 1-1: new device strings: Mfr=1, Product=2, SerialNumber=0
[383428.679687] usb 1-1: Product: Burr-Brown Japan PCM2702
[383428.679687] usb 1-1: Manufacturer: Burr-Brown Japan
[383428.679687] usb 1-1: device v08bb p2702 is not supported
[383428.679687] usb 1-1: uevent
[383428.679687] usb 1-1: usb_probe_device
[383428.679687] usb 1-1: configuration #1 chosen from 1 choice
[383428.679687] usb 1-1: adding 1-1:1.0 (config #1, interface 0)
[383428.679687] usb 1-1:1.0: uevent
[383428.679687] usbtest 1-1:1.0: usb_probe_interface
[383428.679687] usbtest 1-1:1.0: usb_probe_interface - got id
[383428.687500] usb 1-1: adding 1-1:1.1 (config #1, interface 1)
[383428.687500] usb 1-1:1.1: uevent
[383428.687500] usbtest 1-1:1.1: usb_probe_interface
[383428.687500] usbtest 1-1:1.1: usb_probe_interface - got id
[383428.687500] drivers/usb/core/inode.c: creating file '002'
[383428.687500] hub 1-0:1.0: 200mA power budget left
[383428.687500] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[383428.687500] hub 1-0:1.0: port 1 enable change, status 00000103
[383429.898437] cx3110x: PSM dynamic with 200 ms CAM timeout.
[383430.687500] usb 1-1: usb auto-suspend
[383432.710937] hub 1-0:1.0: hub_suspend
[383432.710937] usb usb1: usb auto-suspend
[383443.820312] EAC mode: play enabled, rec enabled
[383447.429687] EAC mode: play disabled, rec disabled


I assume that I need a driver that recognizes generic USB audio devices. I also need to know how to see the output device with Rhapsody. Are there other music player applications that allow you to specify an output device?

Of course, when I try to play music through the unit, it won't play, so I know something in audio registered.

Anybody have any luck doing this?

G
 
Posts: 67 | Thanked: 17 times | Joined on Aug 2007
#2
headfier?

can't say that i can help you, but i can root you on!
 
Cptnodegard's Avatar
Posts: 170 | Thanked: 40 times | Joined on Dec 2007 @ Norway
#3
any progress? would be itneresting to see if USB DACs work
 
Posts: 3 | Thanked: 0 times | Joined on Feb 2008
#4
I haven't made any progress yet myself except to come to the conclusion that I need to compile a new audio driver that includes USB audio functionality.

I suspect this isn't hard, but I haven't had time to set up the environment and figure out what I am doing:-}

If someone else does, I'd love a clue as to how to best get started. It is a busy time right now, so I hope to start after finishing the taxes (.. and the mother's taxes, and the mother-in-laws taxes, and ...).

I'm an engineer, not a tax man, Jim.
g
 
Cptnodegard's Avatar
Posts: 170 | Thanked: 40 times | Joined on Dec 2007 @ Norway
#5
does the dared require any drivers normally? there are some dacs that work on mac, linux and windows without any aditional **** installed
 
Posts: 3 | Thanked: 0 times | Joined on Feb 2008
#6
No. In Windows, it just shows up as "USB Audio Device". My Logitech headphones produce a very similar output:

[1468982.398437] usb 1-1: new device strings: Mfr=1, Product=2, SerialNumber=0
[1468982.398437] usb 1-1: Product: Logitech USB Headset
[1468982.398437] usb 1-1: Manufacturer: Logitech
[1468982.398437] usb 1-1: device v046d p0a01 is not supported
[1468982.398437] usb 1-1: uevent
[1468982.398437] usb 1-1: usb_probe_device
[1468982.398437] usb 1-1: configuration #1 chosen from 1 choice
[1468982.398437] usb 1-1: adding 1-1:1.0 (config #1, interface 0)
[1468982.398437] usb 1-1:1.0: uevent
[1468982.398437] usbtest 1-1:1.0: usb_probe_interface
[1468982.406250] usbtest 1-1:1.0: usb_probe_interface - got id
[1468982.406250] usb 1-1: adding 1-1:1.1 (config #1, interface 1)
[1468982.406250] usb 1-1:1.1: uevent
[1468982.406250] usbtest 1-1:1.1: usb_probe_interface
[1468982.406250] usbtest 1-1:1.1: usb_probe_interface - got id
[1468982.406250] usb 1-1: adding 1-1:1.2 (config #1, interface 2)
[1468982.406250] usb 1-1:1.2: uevent
[1468982.406250] usbtest 1-1:1.2: usb_probe_interface
[1468982.406250] usbtest 1-1:1.2: usb_probe_interface - got id
[1468982.406250] drivers/usb/core/inode.c: creating file '004'
[1468982.406250] hub 1-0:1.0: 100mA power budget left
[1468982.406250] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[1468982.406250] hub 1-0:1.0: port 1 enable change, status 00000103
[1468983.562500] cx3110x: PSM dynamic with 200 ms CAM timeout.
[1468984.406250] usb 1-1: usb auto-suspend
[1468986.429687] hub 1-0:1.0: hub_suspend
[1468986.429687] usb usb1: usb auto-suspend
[1468996.875000] EAC mode: play enabled, rec enabled

So, I'm making a gross assumption based on two devices that OS2008 isn't going to recognize USB audio devices.

Do I need to do a more granular analysis?

g
 
Posts: 1 | Thanked: 0 times | Joined on Jan 2008
#7
I have been having the exact same problem with the Headroom Total Bithead (USB DAC/amp). I have been trying to wrap my head around this for a while, and I have come up completely blank. I have some familiarity with linux and, by default, ALSA contains the drivers for USB DACs like the dared, but for some reason the version implemented in OS2008 does not. I have been trying to simply recompile ALSA but have failed rather miserably.
-- Tarag
 
Cptnodegard's Avatar
Posts: 170 | Thanked: 40 times | Joined on Dec 2007 @ Norway
#8
sure its not a problem with power? have anyone tried connecting the dac through a powered hub?
 
Benson's Avatar
Posts: 4,930 | Thanked: 2,272 times | Joined on Oct 2007
#9
Originally Posted by graphical View Post
No. In Windows, it just shows up as "USB Audio Device". My Logitech headphones produce a very similar output:

[1468982.398437] usb 1-1: new device strings: Mfr=1, Product=2, SerialNumber=0
[1468982.398437] usb 1-1: Product: Logitech USB Headset
[1468982.398437] usb 1-1: Manufacturer: Logitech
[1468982.398437] usb 1-1: device v046d p0a01 is not supported
[1468982.398437] usb 1-1: uevent
[1468982.398437] usb 1-1: usb_probe_device
[1468982.398437] usb 1-1: configuration #1 chosen from 1 choice
[1468982.398437] usb 1-1: adding 1-1:1.0 (config #1, interface 0)
[1468982.398437] usb 1-1:1.0: uevent
[1468982.398437] usbtest 1-1:1.0: usb_probe_interface
[1468982.406250] usbtest 1-1:1.0: usb_probe_interface - got id
[1468982.406250] usb 1-1: adding 1-1:1.1 (config #1, interface 1)
[1468982.406250] usb 1-1:1.1: uevent
[1468982.406250] usbtest 1-1:1.1: usb_probe_interface
[1468982.406250] usbtest 1-1:1.1: usb_probe_interface - got id
[1468982.406250] usb 1-1: adding 1-1:1.2 (config #1, interface 2)
[1468982.406250] usb 1-1:1.2: uevent
[1468982.406250] usbtest 1-1:1.2: usb_probe_interface
[1468982.406250] usbtest 1-1:1.2: usb_probe_interface - got id
[1468982.406250] drivers/usb/core/inode.c: creating file '004'
[1468982.406250] hub 1-0:1.0: 100mA power budget left
[1468982.406250] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[1468982.406250] hub 1-0:1.0: port 1 enable change, status 00000103
[1468983.562500] cx3110x: PSM dynamic with 200 ms CAM timeout.
[1468984.406250] usb 1-1: usb auto-suspend
[1468986.429687] hub 1-0:1.0: hub_suspend
[1468986.429687] usb usb1: usb auto-suspend
[1468996.875000] EAC mode: play enabled, rec enabled
Nope, not a power problem; it claims to have plenty of power. Unless the headphones are lying about their power req'ments, but even so, there would be messages about over-current. (I think.)
 
Cptnodegard's Avatar
Posts: 170 | Thanked: 40 times | Joined on Dec 2007 @ Norway
#10
I dont pretend to understand any of that, but from
[383443.820312] EAC mode: play enabled, rec enabled
[383447.429687] EAC mode: play disabled, rec disabled
doesnt it look like it does work then disconnects for some unkown reason?
 
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 13:00.