I'm trying to use my Line 6 Pocket POD with my ArchLinux system. However it does not work.
With current svn (revision 598), I only get the following result when plugging the device:
usb 6-2: new full speed USB device using uhci_hcd and address 4
usb 6-2: configuration #1 chosen from 1 choice
line6usb 6-2:1.0: Line6 Pocket POD found
usb 6-2: selecting invalid altsetting 1
line6usb 6-2:1.0: set_interface failed
line6usb: probe of 6-2:1.0 failed with error -22
I am using the following kernel version:
$ uname -a
Linux brebre 2.6.32-ARCH #1 SMP PREEMPT Mon Mar 15 20:44:03 CET 2010 x86_64 Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz GenuineIntel GNU/Linux
I am almost sure I had the same problem with kernel 2.6.31.
Do you have any idea of the problem ? Tell me if you need more information.
This driver is really interresting me and I would be very happy to be able to use it.
Just in case, here are some informations about the PocketPod device seen by lsusb (I don't know if it can help):
$ lsusb -v -d 0e41:5051
I'm reviewing some unresolved issues and came across your posting. The Pocked POD has no audio interface (see http://line6.com/pocketpod/ins_outs.html), but it should be possible to access the sound settings via the driver. I made some changes according to the data you provided (revision 644), but can't test it without the device at hand. Can you please check if the driver now at least detects the device successfully? If it does not, please enable the new checkpoint feature in the driver (see https://line6linux.svn.sourceforge.net/svnroot/line6linux/driver/trunk/checkpoint/README.txt) and send the relevant syslog sections to me.
Kind regards,
Markus
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the report! I did some modifications, so could you please try release 645? You can test if the driver communicates with the device by the following steps:
1.) compile and load the driver
2.) run the command "amidi -l" and look for the line similar to "IO hw:3,0 Pocket POD"
3.) run the command "cat /dev/snd/midiC3D0" (replace the "3" and "0" by the numbers following "hw:" in the output of step 2.)
4.) turn some dials on the Pocket POD, and you should see some seemingly random characters in the window where you typed the command of step 3.
5.) if the Pocket POD uses the same protocol as other devices of the POD series, you should be able to control the device as described in sections 3 and 4 of "http://www.tanzband-scream.at/line6/driverdocs.pdf".
Please let me know which of the above steps succeed for you!
Kind regards,
Markus
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I'm trying to use my Line 6 Pocket POD with my ArchLinux system. However it does not work.
With current svn (revision 598), I only get the following result when plugging the device:
usb 6-2: new full speed USB device using uhci_hcd and address 4
usb 6-2: configuration #1 chosen from 1 choice
line6usb 6-2:1.0: Line6 Pocket POD found
usb 6-2: selecting invalid altsetting 1
line6usb 6-2:1.0: set_interface failed
line6usb: probe of 6-2:1.0 failed with error -22
I am using the following kernel version:
$ uname -a
Linux brebre 2.6.32-ARCH #1 SMP PREEMPT Mon Mar 15 20:44:03 CET 2010 x86_64 Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz GenuineIntel GNU/Linux
I am almost sure I had the same problem with kernel 2.6.31.
Do you have any idea of the problem ? Tell me if you need more information.
This driver is really interresting me and I would be very happy to be able to use it.
Just in case, here are some informations about the PocketPod device seen by lsusb (I don't know if it can help):
$ lsusb -v -d 0e41:5051
Bus 006 Device 004: ID 0e41:5051 Line6, Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0e41 Line6, Inc.
idProduct 0x5051
bcdDevice 1.00
iManufacturer 1 Line 6
iProduct 2 Line 6 Pocket POD
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 86
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 1 Audio
bInterfaceSubClass 1 Control Device
bInterfaceProtocol 0
iInterface 2 Line 6 Pocket POD
AudioControl Interface Descriptor:
bLength 9
bDescriptorType 36
bDescriptorSubtype 1 (HEADER)
bcdADC 1.00
wTotalLength 9
bInCollection 1
baInterfaceNr( 0) 1
Interface Descriptor:
bLength 9
bDescriptorType 4
(HEADER)
(MIDI_IN_JACK)
(MIDI_OUT_JACK)
( 0)
( 0)
(GENERAL)
( 0)
(GENERAL)
( 0)
Device Status:
(Bus Powered)klzzwxh:22139klzzwxh:22140klzzwxh:22141klzzwxh:22142klzzwxh:22143klzzwxh:22144klzzwxh:22145klzzwxh:22146klzzwxh:22147klzzwxh:22148klzzwxh:22149klzzwxh:22150klzzwxh:22151klzzwxh:22152klzzwxh:22153klzzwxh:22154klzzwxh:22155klzzwxh:22156klzzwxh:22157klzzwxh:22158klzzwxh:22159klzzwxh:22160klzzwxh:22161klzzwxh:22162
Best regards,klzzwxh:22163Cedric.
I'm reviewing some unresolved issues and came across your posting. The Pocked POD has no audio interface (see http://line6.com/pocketpod/ins_outs.html), but it should be possible to access the sound settings via the driver. I made some changes according to the data you provided (revision 644), but can't test it without the device at hand. Can you please check if the driver now at least detects the device successfully? If it does not, please enable the new checkpoint feature in the driver (see https://line6linux.svn.sourceforge.net/svnroot/line6linux/driver/trunk/checkpoint/README.txt) and send the relevant syslog sections to me.
Kind regards,
Markus
Thanks for your support. I still have problem with revision 644. Here is the log with checkpoint activated:
I also encountered a problem to compile the driver with checkpoint activated (because of localized version of gcc). I have modified cc1 as follow:
$ svn diff Index: checkpoint/cc1 =================================================================== --- checkpoint/cc1 (révision 644) +++ checkpoint/cc1 (copie de travail) @@ -12,7 +12,7 @@ fi done } - +unset LANG INSTALL_DIR=$(/usr/bin/gcc -print-search-dirs | awk '/install:/{print$2}') $INSTALL_DIR/cc1 $*Best regards,
Cedric
Thanks for the report! I did some modifications, so could you please try release 645? You can test if the driver communicates with the device by the following steps:
1.) compile and load the driver
2.) run the command "amidi -l" and look for the line similar to "IO hw:3,0 Pocket POD"
3.) run the command "cat /dev/snd/midiC3D0" (replace the "3" and "0" by the numbers following "hw:" in the output of step 2.)
4.) turn some dials on the Pocket POD, and you should see some seemingly random characters in the window where you typed the command of step 3.
5.) if the Pocket POD uses the same protocol as other devices of the POD series, you should be able to control the device as described in sections 3 and 4 of "http://www.tanzband-scream.at/line6/driverdocs.pdf".
Please let me know which of the above steps succeed for you!
Kind regards,
Markus
Here is the result with revision 645.
1) Syslog trace when plugging Pocket POD:
2) amidi command:
3 & 4) cat /dev/snd/midiC1D0 and moving some pots -> working
5) Sections 3 and 4 of documentation:
Ok
With revision 645, it is the first time that it is working. However the sysfs interface is quite empty:
Thank you,
Cedric.