Been struggling with this issue for a week - but I'm getting closer!
I downloaded all the files from the TRUNK and did: 'sudo make install'
It looks like it finally compiled correctly, but the modprobe fails. Here's my output:
tclong@rubeus:~/Downloads/line6usb-0.8.1$ sudo make install
password for tclong:
./set_revision.sh
make -C /lib/modules/2.6.31-22-generic/build CONFIG_LINE6_USB=m SUBDIRS=/home/tclong/Downloads/line6usb-0.8.1 modules
make: Entering directory `/usr/src/linux-headers-2.6.31-22-generic'
Building modules, stage 2.
MODPOST 1 modules
make: Leaving directory `/usr/src/linux-headers-2.6.31-22-generic'
mkdir -p /lib/modules/2.6.31-22-generic/kernel/drivers/staging/line6
find /lib/modules/2.6.31-22-generic -name line6usb.ko -delete
cp line6usb.ko /lib/modules/2.6.31-22-generic/kernel/drivers/staging/line6
mkdir -p /usr/bin
cp *.sh *.pl /usr/bin
/sbin/depmod -a
/sbin/modprobe line6usb
FATAL: Error inserting line6usb (/lib/modules/2.6.31-22-generic/kernel/drivers/staging/line6/line6usb.ko): Unknown symbol in module, or unknown parameter (see dmesg)
make: *** Error 1
When I look at dmesg, I see the same old disagreements:
line6usb: disagrees about version of symbol snd_rawmidi_receive
line6usb: Unknown symbol snd_rawmidi_receive
line6usb: disagrees about version of symbol snd_ctl_add
line6usb: Unknown symbol snd_ctl_add
line6usb: disagrees about version of symbol snd_pcm_new
line6usb: Unknown symbol snd_pcm_new
line6usb: disagrees about version of symbol snd_pcm_lib_preallocate_pages_for_all
line6usb: Unknown symbol snd_pcm_lib_preallocate_pages_for_all
line6usb: disagrees about version of symbol snd_pcm_stop
line6usb: Unknown symbol snd_pcm_stop
line6usb: disagrees about version of symbol snd_ctl_new1
line6usb: Unknown symbol snd_ctl_new1
line6usb: disagrees about version of symbol snd_rawmidi_transmit_ack
line6usb: Unknown symbol snd_rawmidi_transmit_ack
line6usb: disagrees about version of symbol snd_pcm_hw_constraint_ratdens
line6usb: Unknown symbol snd_pcm_hw_constraint_ratdens
line6usb: disagrees about version of symbol snd_pcm_lib_malloc_pages
line6usb: Unknown symbol snd_pcm_lib_malloc_pages
line6usb: disagrees about version of symbol snd_pcm_lib_ioctl
line6usb: Unknown symbol snd_pcm_lib_ioctl
line6usb: disagrees about version of symbol snd_pcm_lib_free_pages
line6usb: Unknown symbol snd_pcm_lib_free_pages
line6usb: disagrees about version of symbol snd_rawmidi_transmit_peek
line6usb: Unknown symbol snd_rawmidi_transmit_peek
line6usb: disagrees about version of symbol snd_pcm_set_ops
line6usb: Unknown symbol snd_pcm_set_ops
line6usb: disagrees about version of symbol snd_rawmidi_set_ops
line6usb: Unknown symbol snd_rawmidi_set_ops
line6usb: disagrees about version of symbol snd_pcm_period_elapsed
line6usb: Unknown symbol snd_pcm_period_elapsed
Anyone have a suggestion?
Regards!
tc
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Update:
I upgraded to Ubuntu Studio 10.04 which uses kernel 2.6.32.
The kernel compiled and loaded without any error.
Tonight I will plug in the PODxt Live and see if I can get a recording.
tc
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Update: After I got the driver loaded on Monday, I followed an ubuntu tutorial to update my ALSA drivers to the current version and get my soundcard functioning properly. The upgrade to 10.04 managed to break that part of the system.
I was able to get the internal sound working, but updating the ALSA drivers ended up breaking the line6usb drivers. In an attempt to get the ALSA drivers back to 10.04's original settings, I broke gnome and had to reinstall Ubuntu Studio from scratch.
I'm glad to say that I've gotten everything back up and running (Ubuntu Studio, Ardour, Jack, line6usb) and I am now able to record and playback THROUGH the PODxt Live in Ardour. But I haven't attempted any ALSA driver updates because I don't want to mess anything up.
Anyone else notice the ALSA update breaking the line6usb drivers?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Did you compile the Line6 driver from source code, or did you use some pre-packaged binaries? The latter is less robust against changes in related software (such as ALSA).
Kind regards,
Markus
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I compiled from source using the subversion trunk. I may be wrong about ALSA drivers causing the problem. But that was the only system change that I recalled making between the time I got the line6usb driver loaded and the time I actually got home and tried it out.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Did you recompile the driver after the ALSA upgrade? Are you sure that the previous ALSA version has been completely overwritten (i.e., no old header files remaining), and that the new Line6 driver module has been loaded? I've experienced several times that the driver failed to compile after a kernel upgrade (including the ALSA kernel component), but if it compiled successfully, it showed the same behaviour as before the kernel upgrade. You probably don't want to repeat the experiment, but is there any additional information you can provide? How exactly did the driver fail after the upgrade? Does the syslog contain any messages related to the (unsuccessful) operation of the driver?
Kind regards,
Markus
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Been struggling with this issue for a week - but I'm getting closer!
I downloaded all the files from the TRUNK and did: 'sudo make install'
It looks like it finally compiled correctly, but the modprobe fails. Here's my output:
tclong@rubeus:~/Downloads/line6usb-0.8.1$ sudo make install
password for tclong:
./set_revision.sh
make -C /lib/modules/2.6.31-22-generic/build CONFIG_LINE6_USB=m SUBDIRS=/home/tclong/Downloads/line6usb-0.8.1 modules
make: Entering directory `/usr/src/linux-headers-2.6.31-22-generic'
Building modules, stage 2.
MODPOST 1 modules
make: Leaving directory `/usr/src/linux-headers-2.6.31-22-generic'
mkdir -p /lib/modules/2.6.31-22-generic/kernel/drivers/staging/line6
find /lib/modules/2.6.31-22-generic -name line6usb.ko -delete
cp line6usb.ko /lib/modules/2.6.31-22-generic/kernel/drivers/staging/line6
mkdir -p /usr/bin
cp *.sh *.pl /usr/bin
/sbin/depmod -a
/sbin/modprobe line6usb
FATAL: Error inserting line6usb (/lib/modules/2.6.31-22-generic/kernel/drivers/staging/line6/line6usb.ko): Unknown symbol in module, or unknown parameter (see dmesg)
make: *** Error 1
When I look at dmesg, I see the same old disagreements:
line6usb: disagrees about version of symbol snd_rawmidi_receive
line6usb: Unknown symbol snd_rawmidi_receive
line6usb: disagrees about version of symbol snd_ctl_add
line6usb: Unknown symbol snd_ctl_add
line6usb: disagrees about version of symbol snd_pcm_new
line6usb: Unknown symbol snd_pcm_new
line6usb: disagrees about version of symbol snd_pcm_lib_preallocate_pages_for_all
line6usb: Unknown symbol snd_pcm_lib_preallocate_pages_for_all
line6usb: disagrees about version of symbol snd_pcm_stop
line6usb: Unknown symbol snd_pcm_stop
line6usb: disagrees about version of symbol snd_ctl_new1
line6usb: Unknown symbol snd_ctl_new1
line6usb: disagrees about version of symbol snd_rawmidi_transmit_ack
line6usb: Unknown symbol snd_rawmidi_transmit_ack
line6usb: disagrees about version of symbol snd_pcm_hw_constraint_ratdens
line6usb: Unknown symbol snd_pcm_hw_constraint_ratdens
line6usb: disagrees about version of symbol snd_pcm_lib_malloc_pages
line6usb: Unknown symbol snd_pcm_lib_malloc_pages
line6usb: disagrees about version of symbol snd_pcm_lib_ioctl
line6usb: Unknown symbol snd_pcm_lib_ioctl
line6usb: disagrees about version of symbol snd_pcm_lib_free_pages
line6usb: Unknown symbol snd_pcm_lib_free_pages
line6usb: disagrees about version of symbol snd_rawmidi_transmit_peek
line6usb: Unknown symbol snd_rawmidi_transmit_peek
line6usb: disagrees about version of symbol snd_pcm_set_ops
line6usb: Unknown symbol snd_pcm_set_ops
line6usb: disagrees about version of symbol snd_rawmidi_set_ops
line6usb: Unknown symbol snd_rawmidi_set_ops
line6usb: disagrees about version of symbol snd_pcm_period_elapsed
line6usb: Unknown symbol snd_pcm_period_elapsed
Anyone have a suggestion?
Regards!
tc
Update:
I upgraded to Ubuntu Studio 10.04 which uses kernel 2.6.32.
The kernel compiled and loaded without any error.
Tonight I will plug in the PODxt Live and see if I can get a recording.
tc
Correction: "The kernel compiled and loaded…"
Should read: "The line6usb module compiled and loaded…"
sorry 'bout that!
tc
Update: After I got the driver loaded on Monday, I followed an ubuntu tutorial to update my ALSA drivers to the current version and get my soundcard functioning properly. The upgrade to 10.04 managed to break that part of the system.
I was able to get the internal sound working, but updating the ALSA drivers ended up breaking the line6usb drivers. In an attempt to get the ALSA drivers back to 10.04's original settings, I broke gnome and had to reinstall Ubuntu Studio from scratch.
I'm glad to say that I've gotten everything back up and running (Ubuntu Studio, Ardour, Jack, line6usb) and I am now able to record and playback THROUGH the PODxt Live in Ardour. But I haven't attempted any ALSA driver updates because I don't want to mess anything up.
Anyone else notice the ALSA update breaking the line6usb drivers?
Did you compile the Line6 driver from source code, or did you use some pre-packaged binaries? The latter is less robust against changes in related software (such as ALSA).
Kind regards,
Markus
I compiled from source using the subversion trunk. I may be wrong about ALSA drivers causing the problem. But that was the only system change that I recalled making between the time I got the line6usb driver loaded and the time I actually got home and tried it out.
Did you recompile the driver after the ALSA upgrade? Are you sure that the previous ALSA version has been completely overwritten (i.e., no old header files remaining), and that the new Line6 driver module has been loaded? I've experienced several times that the driver failed to compile after a kernel upgrade (including the ALSA kernel component), but if it compiled successfully, it showed the same behaviour as before the kernel upgrade. You probably don't want to repeat the experiment, but is there any additional information you can provide? How exactly did the driver fail after the upgrade? Does the syslog contain any messages related to the (unsuccessful) operation of the driver?
Kind regards,
Markus