line6linux-user Mailing List for Line6 Linux software
Status: Pre-Alpha
Brought to you by:
mgrabner
Menu
▾
▴
line6linux-user — mailing list for users of Line6 Linux software
You can subscribe to this list here.
| 2008 |
Jan
(3) |
Feb
(1) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
(2) |
Aug
(7) |
Sep
(3) |
Oct
|
Nov
(2) |
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(2) |
Jun
(2) |
Jul
(1) |
Aug
|
Sep
|
Oct
(5) |
Nov
(2) |
Dec
|
| 2012 |
Jan
(5) |
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
(1) |
Jul
(3) |
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
(16) |
| 2013 |
Jan
(42) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
(12) |
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(4) |
Oct
(1) |
Nov
|
Dec
|
| 2017 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
(5) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Hans P. M. <hm...@gm...> - 2017-06-13 00:08:38
|
Could you post your dmesg after you plug the device? Also an lsusb of vendor:device could help sl2 Hans P. Möller > El 12-06-2017, a las 01:31, Patrick Chase <pm...@ve...> escribió: > > Yes, sorry. I missed your point completely. For me, it stopped working with kernel 3.2 or so. My understanding is that they made some changes in the USB structure in the kernel and it may have broke the line6 driver (which appears to load fine, but doesn't actually work). I mis-read your post to mean "I got it work again". I didn't realize it was support for something new. > > I haven't tried a newer linux in a while so I could do that and see if it fixed itself. I switched to a Focusrite Scarlet in the meantime and do analog podxt > focusrite which is a little kludgey but works. > > Thanks Hans. > > -Patrick > >> On 06/10/2017 07:20 PM, Hans Peter Möller wrote: >> Hi Patrick, >> mi understanding is that pod xt was one of the firsts (if not the first) to be included in the driver. It also is already in the kernel (at least from 4.4 and above) which kernel and distro do you have? I don't have a pod xt to test it but it should be working long ago. >> brgds >> HPM >> >>> On Fri, Jun 9, 2017 at 6:59 PM, Patrick Chase <pm...@ve...> wrote: >>> Excellent news. >>> >>> Possible to make work with a PodXT too? This model precedes the HD series. >>> >>> https://en.wikipedia.org/wiki/Pod_%28amp_modeler%29 >>> >>> I hate that this guitar equipment is only good for a couple of years and then you need to replace. Still fighting the Linux fight anyway but general going back to vintage technology... >>> >>> -Patrick >>> >>> On 06/09/2017 11:05 AM, Hans Peter Möller wrote: >>>> Hi, I have good news. >>>> We could patch the line6usb drivers and make pod hd500x capture and playback in linux with kernel above or equal 4.9. >>>> I'm writing a guide on how to do it, when ready I will let you know. >>>> With a small change I believe it could work with pod hd pro, but I don't have one to test it. >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Check out the vibrant tech community on one of the world's most >>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >>>> >>>> _______________________________________________ >>>> Line6linux-user mailing list >>>> Lin...@li... >>>> https://lists.sourceforge.net/lists/listinfo/line6linux-user |
|
From: Patrick C. <pm...@ve...> - 2017-06-12 05:31:43
|
Yes, sorry. I missed your point completely. For me, it stopped working with kernel 3.2 or so. My understanding is that they made some changes in the USB structure in the kernel and it may have broke the line6 driver (which appears to load fine, but doesn't actually work). I mis-read your post to mean "I got it work again". I didn't realize it was support for something new. I haven't tried a newer linux in a while so I could do that and see if it fixed itself. I switched to a Focusrite Scarlet in the meantime and do analog podxt > focusrite which is a little kludgey but works. Thanks Hans. -Patrick On 06/10/2017 07:20 PM, Hans Peter Möller wrote: > Hi Patrick, > mi understanding is that pod xt was one of the firsts (if not the > first) to be included in the driver. It also is already in the kernel > (at least from 4.4 and above) which kernel and distro do you have? I > don't have a pod xt to test it but it should be working long ago. > brgds > HPM > > On Fri, Jun 9, 2017 at 6:59 PM, Patrick Chase <pm...@ve... > <mailto:pm...@ve...>> wrote: > > Excellent news. > > Possible to make work with a PodXT too? This model precedes the HD > series. > > https://en.wikipedia.org/wiki/Pod_%28amp_modeler%29 > <https://en.wikipedia.org/wiki/Pod_%28amp_modeler%29> > I hate that this guitar equipment is only good for a couple of > years and then you need to replace. Still fighting the Linux fight > anyway but general going back to vintage technology... > > -Patrick > > On 06/09/2017 11:05 AM, Hans Peter Möller wrote: >> >> Hi, I have good news. >> >> We could patch the line6usb drivers and make pod hd500x capture >> and playback in linux with kernel above or equal 4.9. >> >> I'm writing a guide on how to do it, when ready I will let you know. >> >> With a small change I believe it could work with pod hd pro, but >> I don't have one to test it. >> >> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org!http://sdm.link/slashdot >> >> _______________________________________________ >> Line6linux-user mailing list >> Lin...@li... >> <mailto:Lin...@li...> >> https://lists.sourceforge.net/lists/listinfo/line6linux-user >> <https://lists.sourceforge.net/lists/listinfo/line6linux-user> > |
|
From: Hans P. M. <hm...@gm...> - 2017-06-10 23:20:24
|
Hi Patrick, mi understanding is that pod xt was one of the firsts (if not the first) to be included in the driver. It also is already in the kernel (at least from 4.4 and above) which kernel and distro do you have? I don't have a pod xt to test it but it should be working long ago. brgds HPM On Fri, Jun 9, 2017 at 6:59 PM, Patrick Chase <pm...@ve...> wrote: > Excellent news. > > Possible to make work with a PodXT too? This model precedes the HD series. > > https://en.wikipedia.org/wiki/Pod_%28amp_modeler%29 > > I hate that this guitar equipment is only good for a couple of years and > then you need to replace. Still fighting the Linux fight anyway but general > going back to vintage technology... > > -Patrick > > On 06/09/2017 11:05 AM, Hans Peter Möller wrote: > > Hi, I have good news. > > We could patch the line6usb drivers and make pod hd500x capture and > playback in linux with kernel above or equal 4.9. > > I'm writing a guide on how to do it, when ready I will let you know. > > With a small change I believe it could work with pod hd pro, but I don't > have one to test it. > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > > _______________________________________________ > Line6linux-user mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/line6linux-user > > > |
|
From: Patrick C. <pm...@ve...> - 2017-06-09 22:59:37
|
Excellent news. Possible to make work with a PodXT too? This model precedes the HD series. https://en.wikipedia.org/wiki/Pod_%28amp_modeler%29 I hate that this guitar equipment is only good for a couple of years and then you need to replace. Still fighting the Linux fight anyway but general going back to vintage technology... -Patrick On 06/09/2017 11:05 AM, Hans Peter Möller wrote: > > Hi, I have good news. > > We could patch the line6usb drivers and make pod hd500x capture and > playback in linux with kernel above or equal 4.9. > > I'm writing a guide on how to do it, when ready I will let you know. > > With a small change I believe it could work with pod hd pro, but I > don't have one to test it. > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > _______________________________________________ > Line6linux-user mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/line6linux-user |
|
From: Hans P. M. <hm...@gm...> - 2017-06-09 15:05:10
|
Hi, I have good news. We could patch the line6usb drivers and make pod hd500x capture and playback in linux with kernel above or equal 4.9. I'm writing a guide on how to do it, when ready I will let you know. With a small change I believe it could work with pod hd pro, but I don't have one to test it. |
|
From: Pablo H E. <pho...@gm...> - 2017-05-16 09:41:01
|
Hi all again: After face the year's frustration I saw two options: Write a driver to face more frustrations with endless, and securely fruitless, reverse engineering sessions or buy a Behringer Q502USB (~60€) Ubuntu 16.04 recognized it at the first time. I think companies as Line 6 can invest a little time and resources to support Linux. Business Mysteries. Anyway, thank you. You did a great job, almost magic. There are no documentation, specifications or somethis similar available in internet. That's reverse magic. Yes. -Pablo. |
|
From: Pablo H E. <pho...@gm...> - 2017-05-13 01:31:35
|
Hi all: I have an, almost, old Toneport kb37 and I wondering why this device is not supported. I've read that KB37 has the same architecture than UX2 interface. I searched references of id 0e41:4143 in the code and it isn't. Some orientation? Have I to drop my kb37 and buy a new one? Thanks in advance. -Pablo |
|
From: Hans P. M. <hm...@gm...> - 2017-01-04 01:06:19
|
Sorry, I had an error using modprobe. Butr the thing is that the module is already in the kernel: $sudo modprobe --first-time snd-usb-podhd modprobe: ERROR: could not insert 'snd_usb_podhd': Module already in kernel and still alsamixer nor $cat /proc/asound/cards shows me the pod. Thanks! On Mon, Jan 2, 2017 at 11:14 PM, Hans Peter Möller <hm...@gm...> wrote: > Hi, I also try with modprobe, but I recieved a FATAL not found, although > the snd-usb-podhd.ko is in that directory > > $ sudo modprobe /lib/modules/4.4.0-57-generic/kernel/sound/usb/line6/snd- > usb-podhd.ko > modprobe: FATAL: Module /lib/modules/4.4.0-57-generic/ > kernel/sound/usb/line6/snd-usb-podhd.ko not found in directory > /lib/modules/4.4.0-57-generic > > here is an ls in the directory: > /lib/modules/4.4.0-57-generic/kernel/sound/usb/line6$ ls > snd-usb-line6.ko snd-usb-pod.ko snd-usb-variax.ko > snd-usb-podhd.ko snd-usb-toneport.ko > > thanks! brgds > HPM > > > > > > On Sat, Sep 24, 2016 at 3:43 PM, Hans Peter Möller <hm...@gm...> > wrote: > >> Hi! >> I wanted to know if the pod hd 500x is supported. I plug in to my >> system (ubuntu 16.04 64bit) and it appear recognized in dmesg but I don't >> see it in alsamixer. I see in dmesg an "invalid maxpacket 64" and in lsusb >> I get "bmAttributes 0x40 >> (Missing must-be-set bit!)" >> >> This is everything I get: >> >> $ dmesg >> [11294.716070] usb 1-3: new high-speed USB device number 8 using ehci-pci >> [11294.848437] usb 1-3: config 1 interface 1 altsetting 0 bulk endpoint >> 0x1 has invalid maxpacket 64 >> [11294.848449] usb 1-3: config 1 interface 1 altsetting 0 bulk endpoint >> 0x81 has invalid maxpacket 64 >> [11294.849045] usb 1-3: New USB device found, idVendor=0e41, >> idProduct=4159 >> [11294.849053] usb 1-3: New USB device strings: Mfr=1, Product=2, >> SerialNumber=0 >> [11294.849059] usb 1-3: Product: POD HD500X >> [11294.849066] usb 1-3: Manufacturer: Line 6 >> >> $ sudo lsusb -d 0e41: -v >> Bus 001 Device 008: ID 0e41:4159 Line6, Inc. >> Device Descriptor: >> bLength 18 >> bDescriptorType 1 >> bcdUSB 2.00 >> bDeviceClass 255 Vendor Specific Class >> bDeviceSubClass 255 Vendor Specific Subclass >> bDeviceProtocol 255 Vendor Specific Protocol >> bMaxPacketSize0 64 >> idVendor 0x0e41 Line6, Inc. >> idProduct 0x4159 >> bcdDevice 0.00 >> iManufacturer 1 Line 6 >> iProduct 2 POD HD500X >> iSerial 0 >> bNumConfigurations 1 >> Configuration Descriptor: >> bLength 9 >> bDescriptorType 2 >> wTotalLength 64 >> bNumInterfaces 2 >> bConfigurationValue 1 >> iConfiguration 0 >> bmAttributes 0x40 >> (Missing must-be-set bit!) >> Self Powered >> MaxPower 100mA >> Interface Descriptor: >> bLength 9 >> bDescriptorType 4 >> bInterfaceNumber 0 >> bAlternateSetting 0 >> bNumEndpoints 0 >> bInterfaceClass 255 Vendor Specific Class >> bInterfaceSubClass 255 Vendor Specific Subclass >> bInterfaceProtocol 255 Vendor Specific Protocol >> iInterface 3 Audio >> Interface Descriptor: >> bLength 9 >> bDescriptorType 4 >> bInterfaceNumber 0 >> bAlternateSetting 1 >> bNumEndpoints 2 >> bInterfaceClass 255 Vendor Specific Class >> bInterfaceSubClass 255 Vendor Specific Subclass >> bInterfaceProtocol 255 Vendor Specific Protocol >> iInterface 3 Audio >> Endpoint Descriptor: >> bLength 7 >> bDescriptorType 5 >> bEndpointAddress 0x02 EP 2 OUT >> bmAttributes 1 >> Transfer Type Isochronous >> Synch Type None >> Usage Type Data >> wMaxPacketSize 0x002e 1x 46 bytes >> bInterval 1 >> Endpoint Descriptor: >> bLength 7 >> bDescriptorType 5 >> bEndpointAddress 0x86 EP 6 IN >> bmAttributes 1 >> Transfer Type Isochronous >> Synch Type None >> Usage Type Data >> wMaxPacketSize 0x002e 1x 46 bytes >> bInterval 1 >> Interface Descriptor: >> bLength 9 >> bDescriptorType 4 >> bInterfaceNumber 1 >> bAlternateSetting 0 >> bNumEndpoints 2 >> bInterfaceClass 255 Vendor Specific Class >> bInterfaceSubClass 255 Vendor Specific Subclass >> bInterfaceProtocol 255 Vendor Specific Protocol >> iInterface 4 User >> Endpoint Descriptor: >> bLength 7 >> bDescriptorType 5 >> bEndpointAddress 0x01 EP 1 OUT >> bmAttributes 2 >> Transfer Type Bulk >> Synch Type None >> Usage Type Data >> wMaxPacketSize 0x0040 1x 64 bytes >> bInterval 1 >> Endpoint Descriptor: >> bLength 7 >> bDescriptorType 5 >> bEndpointAddress 0x81 EP 1 IN >> bmAttributes 2 >> Transfer Type Bulk >> Synch Type None >> Usage Type Data >> wMaxPacketSize 0x0040 1x 64 bytes >> bInterval 1 >> Device Qualifier (for other device speed): >> bLength 10 >> bDescriptorType 6 >> bcdUSB 2.00 >> bDeviceClass 255 Vendor Specific Class >> bDeviceSubClass 255 Vendor Specific Subclass >> bDeviceProtocol 255 Vendor Specific Protocol >> bMaxPacketSize0 64 >> bNumConfigurations 1 >> Device Status: 0x0001 >> Self Powered >> >> thanks >> HPM >> > > |
|
From: Hans P. M. <hm...@gm...> - 2017-01-03 02:14:48
|
Hi, I also try with modprobe, but I recieved a FATAL not found, although the snd-usb-podhd.ko is in that directory $ sudo modprobe /lib/modules/4.4.0-57-generic/kernel/sound/usb/line6/snd-usb-podhd.ko modprobe: FATAL: Module /lib/modules/4.4.0-57-generic/kernel/sound/usb/line6/snd-usb-podhd.ko not found in directory /lib/modules/4.4.0-57-generic here is an ls in the directory: /lib/modules/4.4.0-57-generic/kernel/sound/usb/line6$ ls snd-usb-line6.ko snd-usb-pod.ko snd-usb-variax.ko snd-usb-podhd.ko snd-usb-toneport.ko thanks! brgds HPM On Sat, Sep 24, 2016 at 3:43 PM, Hans Peter Möller <hm...@gm...> wrote: > Hi! > I wanted to know if the pod hd 500x is supported. I plug in to my > system (ubuntu 16.04 64bit) and it appear recognized in dmesg but I don't > see it in alsamixer. I see in dmesg an "invalid maxpacket 64" and in lsusb > I get "bmAttributes 0x40 > (Missing must-be-set bit!)" > > This is everything I get: > > $ dmesg > [11294.716070] usb 1-3: new high-speed USB device number 8 using ehci-pci > [11294.848437] usb 1-3: config 1 interface 1 altsetting 0 bulk endpoint > 0x1 has invalid maxpacket 64 > [11294.848449] usb 1-3: config 1 interface 1 altsetting 0 bulk endpoint > 0x81 has invalid maxpacket 64 > [11294.849045] usb 1-3: New USB device found, idVendor=0e41, idProduct=4159 > [11294.849053] usb 1-3: New USB device strings: Mfr=1, Product=2, > SerialNumber=0 > [11294.849059] usb 1-3: Product: POD HD500X > [11294.849066] usb 1-3: Manufacturer: Line 6 > > $ sudo lsusb -d 0e41: -v > Bus 001 Device 008: ID 0e41:4159 Line6, Inc. > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 2.00 > bDeviceClass 255 Vendor Specific Class > bDeviceSubClass 255 Vendor Specific Subclass > bDeviceProtocol 255 Vendor Specific Protocol > bMaxPacketSize0 64 > idVendor 0x0e41 Line6, Inc. > idProduct 0x4159 > bcdDevice 0.00 > iManufacturer 1 Line 6 > iProduct 2 POD HD500X > iSerial 0 > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 64 > bNumInterfaces 2 > bConfigurationValue 1 > iConfiguration 0 > bmAttributes 0x40 > (Missing must-be-set bit!) > Self Powered > MaxPower 100mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 0 > bInterfaceClass 255 Vendor Specific Class > bInterfaceSubClass 255 Vendor Specific Subclass > bInterfaceProtocol 255 Vendor Specific Protocol > iInterface 3 Audio > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 1 > bNumEndpoints 2 > bInterfaceClass 255 Vendor Specific Class > bInterfaceSubClass 255 Vendor Specific Subclass > bInterfaceProtocol 255 Vendor Specific Protocol > iInterface 3 Audio > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x02 EP 2 OUT > bmAttributes 1 > Transfer Type Isochronous > Synch Type None > Usage Type Data > wMaxPacketSize 0x002e 1x 46 bytes > bInterval 1 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x86 EP 6 IN > bmAttributes 1 > Transfer Type Isochronous > Synch Type None > Usage Type Data > wMaxPacketSize 0x002e 1x 46 bytes > bInterval 1 > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 1 > bAlternateSetting 0 > bNumEndpoints 2 > bInterfaceClass 255 Vendor Specific Class > bInterfaceSubClass 255 Vendor Specific Subclass > bInterfaceProtocol 255 Vendor Specific Protocol > iInterface 4 User > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x01 EP 1 OUT > bmAttributes 2 > Transfer Type Bulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0040 1x 64 bytes > bInterval 1 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes 2 > Transfer Type Bulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0040 1x 64 bytes > bInterval 1 > Device Qualifier (for other device speed): > bLength 10 > bDescriptorType 6 > bcdUSB 2.00 > bDeviceClass 255 Vendor Specific Class > bDeviceSubClass 255 Vendor Specific Subclass > bDeviceProtocol 255 Vendor Specific Protocol > bMaxPacketSize0 64 > bNumConfigurations 1 > Device Status: 0x0001 > Self Powered > > thanks > HPM > |
|
From: Kalle A. <sat...@lo...> - 2016-10-07 21:00:56
|
Hey guys! Sorry to bother you again with the same matter. I'm trying to compile the driver from the linux kernel tree, and I get the following: saturnine@Host-001:/lib/modules/4.4.0-38-lowlatency/build/sound/usb/line6$ sudo make install ./set_revision.sh make -C /lib/modules/4.4.0-38-generic/build CONFIG_LINE6_USB=m SUBDIRS=/usr/src/linux-headers-4.4.0-38/sound/usb/line6 modules make[1]: Entering directory '/usr/src/linux-headers-4.4.0-38-generic' CC [M] /usr/src/linux-headers-4.4.0-38/sound/usb/line6/capture.o CC [M] /usr/src/linux-headers-4.4.0-38/sound/usb/line6/driver.o CC [M] /usr/src/linux-headers-4.4.0-38/sound/usb/line6/midi.o CC [M] /usr/src/linux-headers-4.4.0-38/sound/usb/line6/midibuf.o CC [M] /usr/src/linux-headers-4.4.0-38/sound/usb/line6/pcm.o CC [M] /usr/src/linux-headers-4.4.0-38/sound/usb/line6/playback.o LD [M] /usr/src/linux-headers-4.4.0-38/sound/usb/line6/snd-usb-line6.o CC [M] /usr/src/linux-headers-4.4.0-38/sound/usb/line6/pod.o LD [M] /usr/src/linux-headers-4.4.0-38/sound/usb/line6/snd-usb-pod.o CC [M] /usr/src/linux-headers-4.4.0-38/sound/usb/line6/podhd.o LD [M] /usr/src/linux-headers-4.4.0-38/sound/usb/line6/snd-usb-podhd.o CC [M] /usr/src/linux-headers-4.4.0-38/sound/usb/line6/toneport.o LD [M] /usr/src/linux-headers-4.4.0-38/sound/usb/line6/snd-usb-toneport.o CC [M] /usr/src/linux-headers-4.4.0-38/sound/usb/line6/variax.o LD [M] /usr/src/linux-headers-4.4.0-38/sound/usb/line6/snd-usb-variax.o Building modules, stage 2. MODPOST 5 modules CC /usr/src/linux-headers-4.4.0-38/sound/usb/line6/snd-usb-line6.mod.o LD [M] /usr/src/linux-headers-4.4.0-38/sound/usb/line6/snd-usb-line6.ko CC /usr/src/linux-headers-4.4.0-38/sound/usb/line6/snd-usb-pod.mod.o LD [M] /usr/src/linux-headers-4.4.0-38/sound/usb/line6/snd-usb-pod.ko CC /usr/src/linux-headers-4.4.0-38/sound/usb/line6/snd-usb-podhd.mod.o LD [M] /usr/src/linux-headers-4.4.0-38/sound/usb/line6/snd-usb-podhd.ko CC /usr/src/linux-headers-4.4.0-38/sound/usb/line6/snd-usb-toneport.mod.o LD [M] /usr/src/linux-headers-4.4.0-38/sound/usb/line6/snd-usb-toneport.ko CC /usr/src/linux-headers-4.4.0-38/sound/usb/line6/snd-usb-variax.mod.o LD [M] /usr/src/linux-headers-4.4.0-38/sound/usb/line6/snd-usb-variax.ko make[1]: Leaving directory '/usr/src/linux-headers-4.4.0-38-generic' mkdir -p /lib/modules/4.4.0-38-generic/kernel/drivers/staging/line6 /usr/bin /usr/share/doc/packages/line6usb find /lib/modules/4.4.0-38-generic -name line6usb.ko -delete cp line6usb.ko /lib/modules/4.4.0-38-generic/kernel/drivers/staging/line6 cp: cannot stat 'line6usb.ko': No such file or directory GNUmakefile:25: recipe for target 'install-only' failed make: *** [install-only] Error 1 Thanks in advance :) Kalle -- sat...@ik... |
|
From: Hans P. M. <hm...@gm...> - 2016-09-24 18:44:02
|
Hi!
I wanted to know if the pod hd 500x is supported. I plug in to my system
(ubuntu 16.04 64bit) and it appear recognized in dmesg but I don't see it
in alsamixer. I see in dmesg an "invalid maxpacket 64" and in lsusb I get
"bmAttributes 0x40
(Missing must-be-set bit!)"
This is everything I get:
$ dmesg
[11294.716070] usb 1-3: new high-speed USB device number 8 using ehci-pci
[11294.848437] usb 1-3: config 1 interface 1 altsetting 0 bulk endpoint 0x1
has invalid maxpacket 64
[11294.848449] usb 1-3: config 1 interface 1 altsetting 0 bulk endpoint
0x81 has invalid maxpacket 64
[11294.849045] usb 1-3: New USB device found, idVendor=0e41, idProduct=4159
[11294.849053] usb 1-3: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[11294.849059] usb 1-3: Product: POD HD500X
[11294.849066] usb 1-3: Manufacturer: Line 6
$ sudo lsusb -d 0e41: -v
Bus 001 Device 008: ID 0e41:4159 Line6, Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 64
idVendor 0x0e41 Line6, Inc.
idProduct 0x4159
bcdDevice 0.00
iManufacturer 1 Line 6
iProduct 2 POD HD500X
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 64
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x40
(Missing must-be-set bit!)
Self Powered
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 3 Audio
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 3 Audio
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x002e 1x 46 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x86 EP 6 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x002e 1x 46 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 4 User
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0001
Self Powered
thanks
HPM
|
|
From: Laurent N. <lau...@gm...> - 2016-09-24 15:34:41
|
Hi Kalle, You need the kernel source code and the line6 module should be compiled from within. If your not familiar with this non trivial task, maybe the best idea is to ask on a dedicated distribution forum. Maybe it is already available packaged. Regards, -- « On ne résout pas un problème avec les modes de pensée qui l’ont engendré. » « You cannot solve current problems with current thinking. Current problems are the result of current thinking » |
|
From: Laurent N. <lau...@gm...> - 2016-09-21 21:00:36
|
Hi, line6 driver is now merged in kernel tree, try from here https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/sound/usb/line6 -- « On ne résout pas un problème avec les modes de pensée qui l’ont engendré. » « You cannot solve current problems with current thinking. Current problems are the result of current thinking » |
|
From: Kalle A. <sat...@lo...> - 2016-09-21 20:44:16
|
Hey! Just got Line6 KB37 from a mate and tried it with my Ubuntu. Of course it doesn't work so I found this driver. But I'm having trouble compiling the module. Here's what is says: --- root@Host-001:/home/saturnine/laini/line6linux-code/driver/trunk# make install ./set_revision.sh make -C /lib/modules/4.4.0-36-generic/build CONFIG_LINE6_USB=m SUBDIRS=/home/saturnine/laini/line6linux-code/driver/trunk modules make[1]: Entering directory '/usr/src/linux-headers-4.4.0-36-generic' CC [M] /home/saturnine/laini/line6linux-code/driver/trunk/capture.o CC [M] /home/saturnine/laini/line6linux-code/driver/trunk/driver.o CC [M] /home/saturnine/laini/line6linux-code/driver/trunk/midi.o CC [M] /home/saturnine/laini/line6linux-code/driver/trunk/midibuf.o CC [M] /home/saturnine/laini/line6linux-code/driver/trunk/pcm.o CC [M] /home/saturnine/laini/line6linux-code/driver/trunk/playback.o LD [M] /home/saturnine/laini/line6linux-code/driver/trunk/snd-usb-line6.o CC [M] /home/saturnine/laini/line6linux-code/driver/trunk/pod.o LD [M] /home/saturnine/laini/line6linux-code/driver/trunk/snd-usb-pod.o CC [M] /home/saturnine/laini/line6linux-code/driver/trunk/podhd.o LD [M] /home/saturnine/laini/line6linux-code/driver/trunk/snd-usb-podhd.o CC [M] /home/saturnine/laini/line6linux-code/driver/trunk/toneport.o LD [M] /home/saturnine/laini/line6linux-code/driver/trunk/snd-usb-toneport.o CC [M] /home/saturnine/laini/line6linux-code/driver/trunk/variax.o LD [M] /home/saturnine/laini/line6linux-code/driver/trunk/snd-usb-variax.o Building modules, stage 2. MODPOST 5 modules CC /home/saturnine/laini/line6linux-code/driver/trunk/snd-usb-line6.mod.o LD [M] /home/saturnine/laini/line6linux-code/driver/trunk/snd-usb-line6.ko CC /home/saturnine/laini/line6linux-code/driver/trunk/snd-usb-pod.mod.o LD [M] /home/saturnine/laini/line6linux-code/driver/trunk/snd-usb-pod.ko CC /home/saturnine/laini/line6linux-code/driver/trunk/snd-usb-podhd.mod.o LD [M] /home/saturnine/laini/line6linux-code/driver/trunk/snd-usb-podhd.ko CC /home/saturnine/laini/line6linux-code/driver/trunk/snd-usb-toneport.mod.o LD [M] /home/saturnine/laini/line6linux-code/driver/trunk/snd-usb-toneport.ko CC /home/saturnine/laini/line6linux-code/driver/trunk/snd-usb-variax.mod.o LD [M] /home/saturnine/laini/line6linux-code/driver/trunk/snd-usb-variax.ko make[1]: Leaving directory '/usr/src/linux-headers-4.4.0-36-generic' mkdir -p /lib/modules/4.4.0-36-generic/kernel/drivers/staging/line6 /usr/bin /usr/share/doc/packages/line6usb find /lib/modules/4.4.0-36-generic -name line6usb.ko -delete cp line6usb.ko /lib/modules/4.4.0-36-generic/kernel/drivers/staging/line6 cp: cannot stat 'line6usb.ko': No such file or directory GNUmakefile:25: recipe for target 'install-only' failed make: *** [install-only] Error 1 --- Is there a file missing, line6usb.ko ? Thanks, Kalle -- sat...@ik... |
|
From: Fragula <fra...@go...> - 2015-10-17 20:22:33
|
My Pod XT Live works really well. (built from "staging" in raspbian/debian 3.18.10 source, as i'm using a Raspberry Pi for my project) As does, though marginally less well, the Toneport UX2. The Guitarport doesn't seem to work at all for me though, which is a shame, as it would be nice for 24 bit DAC functionality on the media centre (Kodi at present) Pi in the living room. Anyone else tried Guitarport? I've also got a Toneport UX8 that I'd like to make work with Linux, and I'm wondering if there is any point in me probing it (or stripping, cataloging/photographing chips etc.) and posting the results here? Is there interest? Cheers! Mark. |
|
From: Stefan H. <ste...@gm...> - 2014-06-04 04:38:37
|
On Wed, Jun 4, 2014 at 5:49 AM, Patrick Chase <pm...@ve...> wrote: > > On 05/28/2014 11:58 AM, Stefan Hajnoczi wrote: >> >> On Wed, May 28, 2014 at 5:51 PM, Patrick Chase <pm...@ve...> wrote: >>> >>> Hi Stephan. USB looks fine, but it's not available as a soundcard. >>> Details on my troubleshooting is in the AV Linux support forum here: >>> http://www.remastersys.com/forums/index.php?topic=3291 Bottom-line is that >>> the drivers are there, they load properly, the USB device attaches and >>> disconnects as expected, but the device does not show up as a soundcard and >>> is not available in alsamixer. I suspect either a kernel support issue or an >>> alsa support issue (i.e. drivers OK, but not supported). It works >>> out-of-the-box with the included kernel module in Mint 13 (kernel 3.2.0-23) >>> and Ubuntu Studio 12.04 (all in 64-bit fwiw). I can't remember which kernel >>> AV Linux uses but can check. I had planned on trying alternate kernels >>> anyway (to get this working). Thanks in advance for any guidance you can >>> provide. >> >> Hard to say what the issue is. Personally, I don't use the svn source >> tree. Instead I check out the linux.git release tag for the >> appropriate kernel version (check uname -r) and compile the module. >> >> That way I know the driver is running on the kernel version it was >> intended for. The downside is that you don't get fixes that were >> committed in svn after the kernel release. But since development is >> not very active anyway, that's only an issue if you are using a very >> old kernel version. >> >> Anyway, if you want to get to the bottom of it, try adding printk() >> calls or use perf-probe(1) to see which functions in the driver are >> getting called. If it doesn't register an ALSA sound card then >> something must be going pretty wrong during initialization. >> > > Hi Stefan. I can tell you that AV Linux 6.02 is using kernel 3.6.11.2. I bet > if I found an old AV Linux version that used a 3.2 kernel it would work. If you have a working and a non-working version, then the most straightforward way to solve the mystery is bisection. http://git-scm.com/book/en/Git-Tools-Debugging-with-Git#Binary-Search https://www.kernel.org/pub/software/scm/git/docs/git-bisect.html git-bisect(1) performs a binary search on the commit history between two commits. At each step in the search you compile and test the kernel. In the end it leaves you at the commit when the bug was introduced. There are plenty of tutorials online about using git-bisect(1). It can be time-consuming due to the kernel compilation time, but it will identify the exact commit where the bug was introduced. Good luck! Stefan |
|
From: Patrick C. <pm...@ve...> - 2014-06-04 03:49:43
|
On 05/28/2014 11:58 AM, Stefan Hajnoczi wrote: > On Wed, May 28, 2014 at 5:51 PM, Patrick Chase <pm...@ve...> wrote: >> Hi Stephan. USB looks fine, but it's not available as a soundcard. >> Details on my troubleshooting is in the AV Linux support forum here: >> http://www.remastersys.com/forums/index.php?topic=3291 Bottom-line is >> that the drivers are there, they load properly, the USB device >> attaches and disconnects as expected, but the device does not show up >> as a soundcard and is not available in alsamixer. I suspect either a >> kernel support issue or an alsa support issue (i.e. drivers OK, but >> not supported). It works out-of-the-box with the included kernel >> module in Mint 13 (kernel 3.2.0-23) and Ubuntu Studio 12.04 (all in >> 64-bit fwiw). I can't remember which kernel AV Linux uses but can >> check. I had planned on trying alternate kernels anyway (to get this >> working). Thanks in advance for any guidance you can provide. > Hard to say what the issue is. Personally, I don't use the svn source > tree. Instead I check out the linux.git release tag for the > appropriate kernel version (check uname -r) and compile the module. > > That way I know the driver is running on the kernel version it was > intended for. The downside is that you don't get fixes that were > committed in svn after the kernel release. But since development is > not very active anyway, that's only an issue if you are using a very > old kernel version. > > Anyway, if you want to get to the bottom of it, try adding printk() > calls or use perf-probe(1) to see which functions in the driver are > getting called. If it doesn't register an ALSA sound card then > something must be going pretty wrong during initialization. > Hi Stefan. I can tell you that AV Linux 6.02 is using kernel 3.6.11.2. I bet if I found an old AV Linux version that used a 3.2 kernel it would work. Anyway, before switching to Ubuntu Studio, yes I would like to get to the bottom of it. The AV Linux guys may be able to fix this if they knew what was happening. Can you tell me where to add printk() calls? Or can you point me to a tutorial or similar? I'm at the edge of my knowledge here. Thanks. |
|
From: Stefan H. <ste...@gm...> - 2014-05-28 19:44:56
|
On Wed, May 28, 2014 at 9:39 PM, Cristiano Alessandro <cri...@ti...> wrote: >> >> When you record in Ardour you should see the guitar waveform. > I can see it! >> >> When you play back the recorded waveform or an imported audio file in >> Ardour, you should hear it from your PC speakers. > > This is the bit that does not work. When I play back I can hear the > sound in the headphones connected to the POD. Essentially, the list > "system" (input and output) refer to the POD, not to the sound card. Okay, sounds like a JACK problem. I only use JACK with the HD300 as input and output, so I never encountered this problem. Maybe there is a JACK IRC channel or mailing list where you can ask for help. Stefan |
|
From: Cristiano A. <cri...@ti...> - 2014-05-28 19:39:30
|
> Does the Interface list widget in qjackctl Setup turn gray (disabled) > when you select input and output devices that are not the same > soundcard? Yes it does. > > Just to clarify, you need the following connections to record into > Ardour and hear what Ardour plays: > > System Out connected to Ardour In. Ardour Out connected to System In. Connections are fine! > > When you record in Ardour you should see the guitar waveform. I can see it! > > When you play back the recorded waveform or an imported audio file in > Ardour, you should hear it from your PC speakers. This is the bit that does not work. When I play back I can hear the sound in the headphones connected to the POD. Essentially, the list "system" (input and output) refer to the POD, not to the sound card. Any idea? Cristiano |
|
From: Stefan H. <ste...@gm...> - 2014-05-28 19:25:58
|
On Wed, May 28, 2014 at 8:48 PM, Cristiano Alessandro <cri...@ti...> wrote: > ok, after some more testing I have understood the problem! > It seems that Jack does not recognize the audio card of my PC. In the > Setup window of QJackCtl I select duplex, and I can see the interfaces > of both the POD and the built-in audio card. Thus I select the POD as > input and the audio card as output device. However, when I open the > Connection window, the built-in card does not show up. In the audio tab > I can only see the menu for ardour and a menu "system" that refers to > the POD (yes, I am sure...if I disconnect the system output to the > system input I cannot hear sound from the headphones attached to the > POD, and if I disconnect system out to ardour input, ardour does not get > the guitar signal). Does the Interface list widget in qjackctl Setup turn gray (disabled) when you select input and output devices that are not the same soundcard? Just to clarify, you need the following connections to record into Ardour and hear what Ardour plays: System Out connected to Ardour In. Ardour Out connected to System In. When you record in Ardour you should see the guitar waveform. When you play back the recorded waveform or an imported audio file in Ardour, you should hear it from your PC speakers. Do either of these work? Stefan |
|
From: Cristiano A. <cri...@ti...> - 2014-05-28 18:48:27
|
ok, after some more testing I have understood the problem! It seems that Jack does not recognize the audio card of my PC. In the Setup window of QJackCtl I select duplex, and I can see the interfaces of both the POD and the built-in audio card. Thus I select the POD as input and the audio card as output device. However, when I open the Connection window, the built-in card does not show up. In the audio tab I can only see the menu for ardour and a menu "system" that refers to the POD (yes, I am sure...if I disconnect the system output to the system input I cannot hear sound from the headphones attached to the POD, and if I disconnect system out to ardour input, ardour does not get the guitar signal). Any help would be highly appreciated! Thanks Cristiano On 05/28/2014 08:22 PM, Cristiano Alessandro wrote: > Hi Stefan, > > thanks for your reply. > I have followed your suggestions and everything seems to be running. I > can start the Jack server, and I can even define different audio cards > for input and output. It works! > > However nothing comes out of the speakers. I have checked Alsa mixer > and all the lines are in maximum volume. I am sure that the signals > arrives to the PC, because I can record in Ardour and I can see the > waveform, but I cannot hear anything. Not even if I play the track > recorded in Ardour. > Any idea? > > Thanks > Cristiano > > > > On 05/28/2014 10:42 AM, Stefan Hajnoczi wrote: >> On Wed, May 28, 2014 at 9:47 AM, Cristiano Alessandro >> <cri...@ti...> wrote: >> >> Great, the driver is working and the sound card is available. >> >> First, launch pavucontrol and disable the HD300 in the Configuration >> tab. This ensures that PulseAudio will not interfere while JACK is >> using the device. >> >> If you wish to hear the guitar on your PC speakers, also disable your >> PC sound card in pavucontrol. >> >> Now launch qjackctl. If you want to use the HD300 for playback and >> capture, select HD300 as the Interface and make sure Audio is Duplex. >> Set Frames/Period to 128, Sample Rate to 48000, and Periods/Buffer to >> 2. Now click click Start to launch the JACK daemon. This is the >> configuration that I use. >> >> But it sounds like you want to use the HD300 as the capture (in) >> device and your PC soundcard as the playback (out) device. In that >> case you need select the Input Device and Output Device separately. >> I'm not sure how great JACK is at using two different sound devices - >> the reason is that they have independent sampling clocks which will >> drift apart over time. >> >> In my setup where everything goes through the HD300 I connect either >> headphones to the HD300's headphone socket or a PA speaker to the >> HD300's L/Mono socket. >> >> Hope this helps, >> Stefan > |
|
From: Cristiano A. <cri...@ti...> - 2014-05-28 18:40:42
|
Hi Stefan, thanks for your reply. I have followed your suggestions and everything seems to be running. I can start the Jack server, and I can even define different audio cards for input and output. It works! However nothing comes out of the speakers. I have checked Alsa mixer and all the lines are in maximum volume. I am sure that the signals arrives to the PC, because I can record in Ardour and I can see the waveform, but I cannot hear anything. Not even if I play the track recorded in Ardour. Any idea? Thanks Cristiano On 05/28/2014 10:42 AM, Stefan Hajnoczi wrote: > On Wed, May 28, 2014 at 9:47 AM, Cristiano Alessandro > <cri...@ti...> wrote: > > Great, the driver is working and the sound card is available. > > First, launch pavucontrol and disable the HD300 in the Configuration > tab. This ensures that PulseAudio will not interfere while JACK is > using the device. > > If you wish to hear the guitar on your PC speakers, also disable your > PC sound card in pavucontrol. > > Now launch qjackctl. If you want to use the HD300 for playback and > capture, select HD300 as the Interface and make sure Audio is Duplex. > Set Frames/Period to 128, Sample Rate to 48000, and Periods/Buffer to > 2. Now click click Start to launch the JACK daemon. This is the > configuration that I use. > > But it sounds like you want to use the HD300 as the capture (in) > device and your PC soundcard as the playback (out) device. In that > case you need select the Input Device and Output Device separately. > I'm not sure how great JACK is at using two different sound devices - > the reason is that they have independent sampling clocks which will > drift apart over time. > > In my setup where everything goes through the HD300 I connect either > headphones to the HD300's headphone socket or a PA speaker to the > HD300's L/Mono socket. > > Hope this helps, > Stefan |
|
From: Stefan H. <ste...@gm...> - 2014-05-28 15:58:59
|
On Wed, May 28, 2014 at 5:51 PM, Patrick Chase <pm...@ve...> wrote: > > On 05/28/2014 09:17 AM, Stefan Hajnoczi wrote: >>> >>> >>> Out of curiosity, what Linux distro and kernel are you using? It bothers >>> me that the driver appears to work with Mint 13 and the current Ubuntu >>> Studio version, but does not with AV Linux 6.0.1. The driver is there, >>> and loads properly, but my PodXT doesn't show up as a soundcard. >> >> Are there any relevant messages in dmesg showing the USB device >> connecting and the line6usb driver loading? >> >> Are you checking for the soundcard using cat /proc/asound/cards? >> >> What does lsusb | grep 0e41 say? > > > Hi Stephan. USB looks fine, but it's not available as a soundcard. Details > on my troubleshooting is in the AV Linux support forum here: > > http://www.remastersys.com/forums/index.php?topic=3291 > > Bottom-line is that the drivers are there, they load properly, the USB > device attaches and disconnects as expected, but the device does not show up > as a soundcard and is not available in alsamixer. I suspect either a kernel > support issue or an alsa support issue (i.e. drivers OK, but not supported). > It works out-of-the-box with the included kernel module in Mint 13 (kernel > 3.2.0-23) and Ubuntu Studio 12.04 (all in 64-bit fwiw). > > I can't remember which kernel AV Linux uses but can check. I had planned on > trying alternate kernels anyway (to get this working). > > Thanks in advance for any guidance you can provide. Hard to say what the issue is. Personally, I don't use the svn source tree. Instead I check out the linux.git release tag for the appropriate kernel version (check uname -r) and compile the module. That way I know the driver is running on the kernel version it was intended for. The downside is that you don't get fixes that were committed in svn after the kernel release. But since development is not very active anyway, that's only an issue if you are using a very old kernel version. Anyway, if you want to get to the bottom of it, try adding printk() calls or use perf-probe(1) to see which functions in the driver are getting called. If it doesn't register an ALSA sound card then something must be going pretty wrong during initialization. Stefan |
|
From: Patrick C. <pm...@ve...> - 2014-05-28 15:51:42
|
On 05/28/2014 09:17 AM, Stefan Hajnoczi wrote: >> >> Out of curiosity, what Linux distro and kernel are you using? It bothers >> me that the driver appears to work with Mint 13 and the current Ubuntu >> Studio version, but does not with AV Linux 6.0.1. The driver is there, >> and loads properly, but my PodXT doesn't show up as a soundcard. > Are there any relevant messages in dmesg showing the USB device > connecting and the line6usb driver loading? > > Are you checking for the soundcard using cat /proc/asound/cards? > > What does lsusb | grep 0e41 say? Hi Stephan. USB looks fine, but it's not available as a soundcard. Details on my troubleshooting is in the AV Linux support forum here: http://www.remastersys.com/forums/index.php?topic=3291 Bottom-line is that the drivers are there, they load properly, the USB device attaches and disconnects as expected, but the device does not show up as a soundcard and is not available in alsamixer. I suspect either a kernel support issue or an alsa support issue (i.e. drivers OK, but not supported). It works out-of-the-box with the included kernel module in Mint 13 (kernel 3.2.0-23) and Ubuntu Studio 12.04 (all in 64-bit fwiw). I can't remember which kernel AV Linux uses but can check. I had planned on trying alternate kernels anyway (to get this working). Thanks in advance for any guidance you can provide. -Patrick |
|
From: Cristiano A. <cri...@ti...> - 2014-05-28 15:23:51
|
I am on Ubuntu 12.04 LTS. And I had to install no drivers myself, it was already there... Cristiano > Out of curiosity, what Linux distro and kernel are you using? It bothers > me that the driver appears to work with Mint 13 and the current Ubuntu > Studio version, but does not with AV Linux 6.0.1. The driver is there, > and loads properly, but my PodXT doesn't show up as a soundcard. I'm > ready to dump my PodXT for an Eleven Rack but I get the sense that that > won't work either (no driver at all and no evidence that anyone is using > it under Linux). Scopri istella, il nuovo motore per il web italiano. Istella garantisce risultati di qualità e la possibilità di condividere, in modo semplice e veloce, documenti, immagini, audio e video. Usa istella, vai su http://www.istella.it?wtk=amc138614816829636 [1] Links: ------ [1] http://www.istella.it?wtk=amc138614816829636 Scopri istella, il nuovo motore per il web italiano. Istella garantisce risultati di qualità e la possibilità di condividere, in modo semplice e veloce, documenti, immagini, audio e video. Usa istella, vai su http://www.istella.it?wtk=amc138614816829636 |
1 message has been excluded from this view by a project administrator.
