Autoplay is disabled (freedom is freedom ...). Don't hesitate!
2010-09-27
Well, I don't use Mandriva, but the different steps are very similar for any Linux distributions. The driver is now (alsa) part of the kernel, and somebody said here that US-122l or US-144 may work directly from alsa (no need to use jack) and Audacity (I do not use it) address directly from alsa if I remember well.
Now, the only difficulty for you is to know how to disable USB 2.0 (ehci-hcd module) before plugin the US-144; this may easily done or not depending on your distro. You will have to ask for some informed user of Mandriva. Have before a look to the different pages of the present site.
Phil
2010-09-21
HI! NEED HELP ! ! i have Mandriva- Linux.. i have the Tascam us -144 interface. im trying to use Audacity to record.. I AM COMPUTER E LITERATE .. I know tascam drivers and cube base will not work with linux. In simple terms how do i make this work????
2010-09-21
HI! NEED HELP ! ! i have Mandriva- Linux.. i have the Tascam us -144 interface. im trying to use Audacity to record.. I AM COMPUTER E LITERATE .. I know tascam drivers and cube base will not work with linux. In simple terms how do i make this work????
2010-09-21
i have mandriva linux. i have tascam us 144. I am computer illiterate......i am trying to use Audacity to record tracks.need help step by step directions on how to start ? LOST?!?
2010-01-13
Very nice site!
2009-08-28
Philippe Carriere wrote:
> Hi,
>
> I thought you said using alsa 1.0.20 in a email to Takashi, while
> Fedora is using alsa 1.0.21; probably I am mistaking somewhere.
> Whatever, for Fedora user, the patch has to be compatible with F10 and
> F11.
First, thanks for testing the patch!
My alsa-packages are 1.0.20, but us122l.c is part of the kernel so it's
that version that matters: 2.6.31 here.
> but to the fact that ehci-hcd is built-in and not a module since F10
Same here on Ubuntu 9.10. But I didn't know that Fedora did it too. ;)
>
> But in fact, modifying the set-up of jack (using period 1024), sound
> was available from US-122L.
>
> Thus your patched us122l.c has no consequences on US-122L as you expected.
Yes, did you try using uhci-hcd with the old version of us122l.c?
Because the only thing the patch changes for US-122L is incrementing the
usage counter for both interfaces and not only for one (usb_get_intf()).
That should be no problem (especially for 2.6-kernels, since this is a
legacy function for older kernels).
> I just wonder about the setup required for jack: period 1024 induces a
> lot of latency (about 41ms) and possibly using more complex
> combinations (I just use audacious reading an mp3 file) would require
> still larger period: what about your own setup ? Possibly, it may
> depend on the PC itself. Do you still schedule the future use of
> ehci-hcd (I know, it's a lot of work) ?
I can go down to 128 frames/period without getting xruns when playing a
mp3. 64 doesn't start. About ehci-hcd: I guess I will look at it a
little more, but I doubt I will be able to get it running. I had a look
at the URBs using USB Snoopy and the patterns look completely different
when using USB2 instead of USB1. Maybe I will ask Karsten Wiese on some
advice about usb-stream.c.
Regards,
Tobias
2009-09-25
Hi,
I thought you said using alsa 1.0.20 in a email to Takashi, while Fedora is using alsa 1.0.21; probably I am
mistaking somewhere. Whatever, for Fedora user, the patch has to be compatible with F10 and F11.
Concerning the fact that compiling a whole kernel is required, this is not due to us122l which is module (and then
may be patched separately using a specific procedure in Fedora - kmod) but to the fact that ehci-hcd is
built-in and not a module since F10 (I have emailed to Fedora guys at a time about this point, they said: "it speeds up the boot process ...").
Thus a kernel (with just ehci-hcd a module, but by the way including the patched us122l.c) has to be compiled !
This is quite stupid, but this is so.
Now I tested rapidly this morning:
- US-122L still works with ehci-hcd
- disabling ehci-hcd, I was firstly afraid since jack stopped immediately while system messages were:
Sep 25 08:54:32 pollux kernel: usb 2-2: new full speed USB device using uhci_hcd and address 2
Sep 25 08:54:32 pollux kernel: usb 2-2: New USB device found, idVendor=0644, idProduct=800e
Sep 25 08:54:32 pollux kernel: usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 25 08:54:32 pollux kernel: usb 2-2: Product: US-122L
Sep 25 08:54:32 pollux kernel: usb 2-2: Manufacturer: TASCAM
Sep 25 08:54:32 pollux kernel: usb 2-2: SerialNumber: no serial number
Sep 25 08:54:32 pollux kernel: usb 2-2: configuration #1 chosen from 1 choice
Sep 25 08:54:36 pollux kernel: Machine check events logged
Sep 25 08:54:49 pollux kernel: ALSA sound/usb/usx2y/usb_stream.c:479: -2
Sep 25 08:54:52 pollux kernel: ALSA sound/usb/usx2y/usb_stream.c:479: -2
Sep 25 08:54:52 pollux kernel: ALSA sound/usb/usx2y/usb_stream.c:457: underrun, status=0
Sep 25 08:55:22 pollux kernel: ALSA sound/usb/usx2y/usb_stream.c:479: -3
Sep 25 08:55:25 pollux kernel: ALSA sound/usb/usx2y/usb_stream.c:479: -2
Sep 25 08:55:25 pollux kernel: ALSA sound/usb/usx2y/usb_stream.c:457: underrun, status=0
But in fact, modifying the set-up of jack (using period 1024), sound was available from US-122L.
Thus your patched us122l.c has no consequences on US-122L as you expected.
I just wonder about the setup required for jack: period 1024 induces a lot of latency (about 41ms) and possibly using
more complex combinations (I just use audacious reading an mp3 file) would require still larger period: what about
your own setup ? Possibly, it may depend on the PC itself.
Do you still schedule the future use of ehci-hcd (I know, it's a lot of work) ?
Regards,
Phil.
2009-09-25
Hi,
maybe us122l.c was patched since 2.6.29. I use 2.6.31.
When you had snd-usb-us122l as a module before, you don't need to
compile the whole kernel:
Just patch us122l.c in a fresh fedora source tree, go to
sound/usb/usx2y, do
make -C /usr/src/linux-headers-`uname -r` M=`pwd` modules
(maybe change the path to your kernel headers in fedora)
Then you can replace the module:
/lib/modules/`uname -r`/kernel/sound/usb/usx2y/snd-usb-us122l.ko (here on Ubuntu).
Regards,
Tobias
2009-09-24
Hi Tobias,
well, i'm sorry, it was probably a mis cut and paste from me. So I returned back and applied the patch to
kernel 2.6.29 (alsa 1.0.21, if I'm right). The patch is rejected but it seems not very significant so I
modified us122l.c conforming to the original patch, then generated a new patch; finally, for fedora 10 (the
kernel of which is additionally patched) I had also to generate a different patch.
I'm now compiling the kernel (indeed, packaging a Fedora kernel). It will take a while so I will let you know if us122l is still working with the
patched kernel (since I have no US-144 to test).
Regards,
Phil.
2009-09-23
Hi,
that is strange. I didn't attach the patchfile (exept the first
version), because in
Documentation/SubmittingPatches it is suggested to
copy the text directly into the email.
I don't see truncated lines and
again tried copying the text into a file and patching: works.
Nevertheless, here is it as a file.
If it still doesn't work, you could
check if you have the same us122l.c:
http://git.alsa-project.org/?p=alsa-kernel.git;a=blob_plain;f=sound/usb/usx2y/us122l.c;hb=HEAD
Regards,
Tobias
2009-09-23
Hi Tobias,
trying to apply your patch I obtained a "non conformal" error message. Having a look to the patch file, I saw that long lines have been truncated, probably an effect of attached file. I saw it is similar on the alsa page so it does not seem to be a side effect of my pwner mailer.
Of course I can manually apply the patch but it would be better to have a single file.
Regards,
Phil.
2009-09-23
If you are still searching for your US-144, there is now a patch for making it working usin uhci-hcd:
http://mailman.alsa-project.org/pipermail/alsa-devel/2009-September/021379.html
Regards
Phil.
2009-09-23
Salut,
il y a maintenant une réponse au problème !
http://mailman.alsa-project.org/pipermail/alsa-devel/2009-September/021379.html
Il ne reste plus qu'à patcher et recompiler (et désactiver ehci-hcd).
Bon courage.
Phil
2009-09-23
Hi Federico,
some happy good news for Tascam US-144 owners at:
http://mailman.alsa-project.org/pipermail/alsa-devel/2009-September/021379.html
Tobias wrote me last week and we concluded that us122l.c has to be modified; he was able to rapidly patch
us122l.c so as to work with US-144 (using uhci-hcd presently).
You will have to update your wiki !
Best regards,
Phil.
2009-09-23
Philippe Carriere wrote:
> Probably it would be useful to test the patched us122l.c with US-122L.
> I will try to find some time to have a look at this.
That would be nice, thanks! :)
Regards,
Tobias
2009-09-22
Fine, Tobias !
I imagine a lot of people will be pleased to know that they will have their US-144 working under Linux.
I'm following your exchange with Takashi Iwai: the final version of your patch is almost all set.
Probably it would be useful to test the patched us122l.c with US-122L. I will try to find some time to have a look at this.
Best regards
Phil
2009-09-22
Hi,
I forgot to test my latest patch with uhci-hcd. If somebody asks you
again, here is the patch:
http://mailman.alsa-project.org/pipermail/alsa-devel/2009-September/021363.html
Regards,
Tobias
2009-09-21
Hi Phil,
I put some effort in understanding parts of the driver and edited
us122l.c to match the differing USB
interface structure (US-144 uses two
interfaces), but now the errors seem to occur in usb_stream.c.
I guess the next thing to do is snooping the USB traffic using Windows.
That will either take its time or be of no success, we'll see.
Nevertheless, it was nice having someone to buoy me up. :)
AND at least now we know US-144 is not working without some more effort.
Better than nothing. ;)
Regards,
Tobias
2009-09-16
Hi Tobias,
first I saw that the web site of Federico is available again: you can email him at federico@briata.org.
Possibly he is aware of somebody able to make US-144 working under Linux in which case it will be of help for you.
Now, if nobody was able to do this up to now, it is probably due to the fact that the driver for US-122L has to be
modified in order to work with US-144.
I know that Karsten was not able to test the driver since he has no US-144 to do the job.
Possibly only a few modifications are required but I don't know; and I am whatever unable to do this.
Now, since you possess a US-144, possibly you would be interested in patching the driver; in that case, if
you did not do so up to now, you would have first to look at the documentation about writing a driver at Alsa site
http://www.alsa-project.org/main/index.php/Developer_Zone
Then, if you have some ideas about how the driver works, you will be able to ask some help at alsa-devel@alsa-project.org
(it just require to ask for registering), possibly contacting indirectly Karsten Wiese, for having
some guides to know where the driver would have to be modified.
This is not of great help, I apologize for this.
Regards
Phil.
2009-09-11
One more thing:
The outputs from my last mail were produced with this .asoundrc:
# The usb_stream plugin configuration
pcm.!usb_stream {
@args [ CARD ]
@args.CARD {
type string
default "1"
}
type usb_stream
card $CARD
}
ctl.!usb_stream {
@args [ CARD ]
@args.CARD {
type string
default "1"
}
type hw
card $CARD
}
With this .asoundrc:
# The usb_stream plugin configuration
pcm.!usb_stream {
@args [ CARD ]
@args.CARD {
type string
default "1"
}
type usb_stream
card $CARD
}
I just get this:
[ 2930.304050] usb 7-2: new high speed USB device using ehci_hcd and
address 5
[ 2930.437197] usb 7-2: configuration #1 chosen from 1 choice
[ 2930.438570] couldn't __get_free_pages()
[ 2930.438591] snd-usb-us122l: probe of 7-2:1.1 failed with error -22
or
[ 2698.632056] usb 3-2: new full speed USB device using uhci_hcd and
address 6
[ 2698.796635] usb 3-2: configuration #1 chosen from 1 choice
[ 2698.809894] couldn't __get_free_pages()
[ 2698.809928] snd-usb-us122l: probe of 3-2:1.1 failed with error -22
Which .asoundrc is better?
Regards, Tobias
2009-09-11
Hi Phil,
your mail was quite useful, thanks. But it doesn't work so far. Here is
what I did and the results:
Except from creating the right .asoundrc, I recompiled the kernel,
changing the Product ID in sound/usb/usx2y/us122l.c
to the US144 one and
editing the configuration to make ehci-hcd a module.
Here is what dmesg returned with ehci-hdc:
[ 108.209085] usb 2-2: new high speed USB device using ehci_hcd and
address 2
[ 108.345326] usb 2-2: configuration #1 chosen from 1 choice
[ 108.406969] ------------[ cut here ]------------
[ 108.406982] WARNING: at
/home/tobi/us144/linux-2.6.31/mm/page_alloc.c:1751
__alloc_pages_slowpath+0x41b/0x4e0()
[ 108.406986] Hardware name: TravelMate 6292
[ 108.406989] Modules linked in: snd_usb_us122l(+) snd_usb_lib
snd_hwdep binfmt_misc nls_iso8859_1 nls_cp437 vfat fat vhba lp
snd_hda_codec_realtek snd_hda_intel snd_hda_codec joydev snd_pcm_oss
snd_mixer_oss snd_pcm snd_seq_dummy pcmcia snd_seq_oss snd_seq_midi
snd_rawmidi snd_seq_midi_event snd_seq snd_timer uvcvideo arc4
snd_seq_device ecb yenta_socket videodev rsrc_nonstatic v4l1_compat
pcmcia_core snd soundcore iwlagn snd_page_alloc v4l2_compat_ioctl32
iwlcore sdhci_pci psmouse sdhci serio_raw mac80211 cfg80211 acer_wmi
led_class ppdev irda parport_pc parport crc_ccitt ohci1394 ieee1394 tg3
fbcon tileblit font bitblit softcursor i915 drm i2c_algo_bit video
output intel_agp
[ 108.407075] Pid: 3601, comm: modprobe Not tainted 2.6.31-10-generic #30
[ 108.407078] Call Trace:
[ 108.407087] [<ffffffff81059778>] warn_slowpath_common+0x78/0xb0
[ 108.407093] [<ffffffff810597bf>] warn_slowpath_null+0xf/0x20
[ 108.407098] [<ffffffff810db7fb>] __alloc_pages_slowpath+0x41b/0x4e0
[ 108.407106] [<ffffffff810661c0>] ? process_timeout+0x0/0x10
[ 108.407112] [<ffffffff810dba0e>] __alloc_pages_nodemask+0x14e/0x150
[ 108.407119] [<ffffffff813999d0>] ? urb_destroy+0x0/0x30
[ 108.407124] [<ffffffff81107e92>] alloc_pages_current+0x82/0xd0
[ 108.407130] [<ffffffff810da9e9>] __get_free_pages+0x9/0x50
[ 108.407139] [<ffffffffa01a4bf2>] usb_stream_new+0x1a2/0x390
[snd_usb_us122l]
[ 108.407145] [<ffffffff8139af6a>] ? usb_control_msg+0xfa/0x180
[ 108.407152] [<ffffffffa01a4e28>] us122l_start+0x48/0x130
[snd_usb_us122l]
[ 108.407159] [<ffffffffa01a3264>] ? pt_info_set+0x44/0x50
[snd_usb_us122l]
[ 108.407167] [<ffffffffa01a4f70>] us122l_create_card+0x60/0x200
[snd_usb_us122l]
[ 108.407174] [<ffffffffa01a5164>] us122l_usb_probe+0x54/0xc0
[snd_usb_us122l]
[ 108.407181] [<ffffffffa01a5209>] snd_us122l_probe+0x39/0x70
[snd_usb_us122l]
[ 108.407187] [<ffffffff8139db81>] usb_probe_interface+0xb1/0x190
[ 108.407194] [<ffffffff8131bc04>] really_probe+0x64/0x160
[ 108.407199] [<ffffffff8131bd23>] driver_probe_device+0x23/0x30
[ 108.407204] [<ffffffff8131bdc3>] __driver_attach+0x93/0xa0
[ 108.407210] [<ffffffff8131bd30>] ? __driver_attach+0x0/0xa0
[ 108.407215] [<ffffffff8131b0e8>] bus_for_each_dev+0x68/0x90
[ 108.407221] [<ffffffff8131ba89>] driver_attach+0x19/0x20
[ 108.407226] [<ffffffff8131b39d>] bus_add_driver+0xcd/0x2a0
[ 108.407231] [<ffffffff8131c0b8>] driver_register+0x78/0x140
[ 108.407238] [<ffffffff8127329a>] ? __up_read+0x9a/0xc0
[ 108.407243] [<ffffffff8139cfd8>] usb_register_driver+0xb8/0x130
[ 108.407250] [<ffffffffa0010000>] ? snd_us122l_module_init+0x0/0x20
[snd_usb_us122l]
[ 108.407257] [<ffffffffa001001e>] snd_us122l_module_init+0x1e/0x20
[snd_usb_us122l]
[ 108.407265] [<ffffffff8100a047>] do_one_initcall+0x37/0x1a0
[ 108.407271] [<ffffffff8108cbc7>] sys_init_module+0xd7/0x230
[ 108.407278] [<ffffffff81011fc2>] system_call_fastpath+0x16/0x1b
[ 108.407282] ---[ end trace 803064b9ac6d7dd9 ]---
[ 108.407285] couldn't __get_free_pages()
[ 108.407308] snd-usb-us122l: probe of 2-2:1.1 failed with error -22
[ 108.407341] usbcore: registered new interface driver snd-usb-us122l
...and without ehci-hdc:
[ 120.400043] usb 3-2: new full speed USB device using uhci_hcd and
address 2
[ 120.568195] usb 3-2: configuration #1 chosen from 1 choice
[ 120.630078] ------------[ cut here ]------------
[ 120.630091] WARNING: at
/home/tobi/us144/linux-2.6.31/mm/page_alloc.c:1751
__alloc_pages_slowpath+0x41b/0x4e0()
[ 120.630096] Hardware name: TravelMate 6292
[ 120.630098] Modules linked in: snd_usb_us122l(+) snd_usb_lib
snd_hwdep binfmt_misc nls_iso8859_1 nls_cp437 vfat fat vhba lp
snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_pcm_oss
snd_mixer_oss snd_pcm snd_seq_dummy joydev snd_seq_oss pcmcia arc4
snd_seq_midi snd_rawmidi ecb snd_seq_midi_event snd_seq snd_timer iwlagn
snd_seq_device iwlcore uvcvideo yenta_socket mac80211 videodev snd
sdhci_pci v4l1_compat rsrc_nonstatic sdhci soundcore snd_page_alloc
pcmcia_core v4l2_compat_ioctl32 cfg80211 psmouse serio_raw acer_wmi
led_class ppdev irda parport_pc parport crc_ccitt ohci1394 ieee1394 tg3
fbcon tileblit font bitblit softcursor i915 drm i2c_algo_bit video
output intel_agp [last unloaded: ehci_hcd]
[ 120.630187] Pid: 3423, comm: modprobe Not tainted 2.6.31-10-generic #30
[ 120.630191] Call Trace:
[ 120.630200] [<ffffffff81059778>] warn_slowpath_common+0x78/0xb0
[ 120.630206] [<ffffffff810597bf>] warn_slowpath_null+0xf/0x20
[ 120.630212] [<ffffffff810db7fb>] __alloc_pages_slowpath+0x41b/0x4e0
[ 120.630219] [<ffffffff810661c0>] ? process_timeout+0x0/0x10
[ 120.630224] [<ffffffff810dba0e>] __alloc_pages_nodemask+0x14e/0x150
[ 120.630231] [<ffffffff813999d0>] ? urb_destroy+0x0/0x30
[ 120.630237] [<ffffffff81107e92>] alloc_pages_current+0x82/0xd0
[ 120.630242] [<ffffffff810da9e9>] __get_free_pages+0x9/0x50
[ 120.630252] [<ffffffffa0456bf2>] usb_stream_new+0x1a2/0x390
[snd_usb_us122l]
[ 120.630257] [<ffffffff8139af6a>] ? usb_control_msg+0xfa/0x180
[ 120.630265] [<ffffffffa0456e28>] us122l_start+0x48/0x130
[snd_usb_us122l]
[ 120.630271] [<ffffffffa0455264>] ? pt_info_set+0x44/0x50
[snd_usb_us122l]
[ 120.630278] [<ffffffffa0456f70>] us122l_create_card+0x60/0x200
[snd_usb_us122l]
[ 120.630286] [<ffffffffa0457164>] us122l_usb_probe+0x54/0xc0
[snd_usb_us122l]
[ 120.630293] [<ffffffffa0457209>] snd_us122l_probe+0x39/0x70
[snd_usb_us122l]
[ 120.630299] [<ffffffff8139db81>] usb_probe_interface+0xb1/0x190
[ 120.630306] [<ffffffff8131bc04>] really_probe+0x64/0x160
[ 120.630311] [<ffffffff8131bd23>] driver_probe_device+0x23/0x30
[ 120.630316] [<ffffffff8131bdc3>] __driver_attach+0x93/0xa0
[ 120.630321] [<ffffffff8131bd30>] ? __driver_attach+0x0/0xa0
[ 120.630327] [<ffffffff8131b0e8>] bus_for_each_dev+0x68/0x90
[ 120.630332] [<ffffffff8131ba89>] driver_attach+0x19/0x20
[ 120.630337] [<ffffffff8131b39d>] bus_add_driver+0xcd/0x2a0
[ 120.630342] [<ffffffff8131c0b8>] driver_register+0x78/0x140
[ 120.630349] [<ffffffff8127329a>] ? __up_read+0x9a/0xc0
[ 120.630354] [<ffffffff8139cfd8>] usb_register_driver+0xb8/0x130
[ 120.630361] [<ffffffffa045c000>] ? snd_us122l_module_init+0x0/0x20
[snd_usb_us122l]
[ 120.630368] [<ffffffffa045c01e>] snd_us122l_module_init+0x1e/0x20
[snd_usb_us122l]
[ 120.630375] [<ffffffff8100a047>] do_one_initcall+0x37/0x1a0
[ 120.630381] [<ffffffff8108cbc7>] sys_init_module+0xd7/0x230
[ 120.630388] [<ffffffff81011fc2>] system_call_fastpath+0x16/0x1b
[ 120.630392] ---[ end trace b2ff6c8535f3d554 ]---
[ 120.630395] couldn't __get_free_pages()
[ 120.630420] snd-usb-us122l: probe of 3-2:1.1 failed with error -22
[ 120.630458] usbcore: registered new interface driver snd-usb-us122l
As you see, pretty much the same.. It never appeared at /proc/asound/cards.
If you would like to see any other outputs or have any further ideas
what I could do, let me know. The pages at briata.org seem to be down.
I'd like to ask Federico for advice though. Do you know his email-address?
Regards, Tobias
2009-09-10
Hi Tobias,
in fact I received more questions about US 144 than reported in my web site.
Here follows my answer to one other people, written in french so I summarize right now in english:
- first I am not able, up to now, to know if US 144 is able to work with the driver of US 122L.
Karsten Wiese (the guy who wrote the US-122L driver) just mentionned that possibly it would work when using the uhci-hcd (USB 1.1) port.
- What I can first recommend:
. follow strictly the same recommandations for software installation than for the US-122L;
. look at all messages from the system when plugging/unplugging the US-144 in addition to what I mentionned on my page;
. probably it will not work as it stands so first try to deactivate the ehci-hcd port, namely:
$ su -c 'rmmod ehci-hcd'
or since you use ubuntu, probably
sudo rmmod ehic-hcd
. does it work ? I don't know, but it would be useful to compare messages from the system with the previous ones.
. have a look to http://ubuntuforums.org/showthread.php?t=863109&page=2
. finally ask to Federico http://wiki.briata.org/
Let me know !
Regards,
Phil.
2009-09-08
Hi Phil,
I found your homepage searching for a way to get my Tascam US-144 to
work on Linux. I found no indication for one working US-144 so far.
In the comments you offered somebody your help on that. Do you know if
anything regarding 144 happened since then?
Are you still interested in testing with the 144? I have no experience
in writing drivers, but should be able
to follow you advice patching and
compiling etc.
I'm using Ubuntu 9.10 Alpha with a 2.6.31 kernel right now, but would
also install Fedora if necessary.
Kind Regards,
Tobias Hansen
2009-07-04
Salut,
désolé, j'ai un peu tardé mais j'étais très occupé en ce moment.
La US-144, c'est un peu le serpent de mer: quelques personnes m'ont déjà demandé; je leur ai envoyé quelques trucs, mais je n'ai jamais eu de
réponses, donc je ne sais même pas si quelqu'un a pu faire fonctionner une telle carte avec le pilote de la US-122L.
Ce forum: http://ubuntuforums.org/showthread.php?t=863109&page=2 en parle, mais c'est un peu ancien.
Sans doute vaudrait-il mieux demander à Federico (Briata: http://wiki.briata.org/doku.php?id=testing_us122l_under_linux )
d'autant que tu es sous Ubuntu (j'utilise Fedora): les dernières versions du kernel contiennent les
pilotes alsa et le patch pour l'USB 2.0.
Maintenant, tout ça, c'est pour l'US-122L; Karsten Wiese n'a rien testé concernant la US-144 (il n'en possède pas, à ma connaissance).
Donc déjà, il faut t'assurer que tu as les dernières versions du noyau et d'alsa (noyau >= 2.6.29 et alsa >= 1.0.18), démarrer le système (carte son
unplugged) et regarder ce que disent les messages systèmes (/var/log/messages) lorsque tu plug la US-144.
Phil.
2009-06-30
Salut Phil,
j'ai une interface Tascam 144 qui devrait tourner avec le meme pilote que la 122L, malhereusement elle n'est pas
reconnue comme carte son par mon systeme. Je fais tourner ubuntu 9.04 sur un Dell 1525 core duo 64 bit.
Pourrais-tu me donner un coup de main?
cu
La page Web of Phil - www.la-page-web-of-phil.fr; contact: La-Page-Web-of-Phil {point} contact {à} orange {point} fr