TonePort UX2 recognized but won't play audio
This bug report was converted into a question: question #94759: TonePort UX2 recognized but won't play audio.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
I see the card in the audio settings manager, but this message is repeated in the syslog:
kernel: [ 86.246910] line6usb 6-1:1.1: URB out #0 submission failed
kernel: [ 86.246908] line6usb 6-1:1.1: URB out #0 submission failed
kernel: [ 86.246908] line6usb 6-1:1.1: URB out #0 submission failed
Nothing I do seems to fix it! Help!
ProblemType: Bug
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Line6USB'/'Line6 TonePort UX2 at USB 6-1:1.0'
Mixer name : ''
Components : ''
Controls : 1
Simple ctrls : 1
Card1.Amixer.info:
Card hw:1 'Line6USB_1'/'Line6 TonePort UX2 at USB 6-1:1.1'
Mixer name : ''
Components : ''
Controls : 1
Simple ctrls : 1
Date: Sun Dec 20 16:21:49 2009
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
MachineType: System manufacturer P5K-E
NonfreeKernelMo
Package: linux-image-
PciMultimedia:
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.24
RfKill:
SourcePackage: linux
Uname: Linux 2.6.31-
XsessionErrors:
(gnome-
(gnome-
(polkit-
(nautilus:1985): Eel-CRITICAL **: eel_preferences
dmi.bios.date: 06/26/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0503
dmi.board.
dmi.board.name: P5K-E
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: P5K-E
dmi.product.
dmi.sys.vendor: System manufacturer
Problem may be a bug but there's a chance that it's a configuration issue. Please help! :) If it's actually a bug, this can be converted back into one.