Monday 26 October 2015

Linux Against Poverty Install Fest



Source :  Internet



Volunteer Michael Collins installs the Linux operating system on a group of donated computers during the Linux Against Poverty Install Fest at Union Park on Saturday, June 19, 2010.


Volunteer Tony Ikeda takes a look at a repair sheet attached to the side of a donated computer during the Linux Against Poverty Install Fest at Union Park on Saturday, June 19, 2010. At this stage, computers were being prepared to have the Linux operating system installed.



Volunteer Matthew Walsh inspects a recently-repaired donated computer during the Linux Against Poverty Install Fest at Union Park on Saturday, June 19, 2010.




A volunteer holds a damaged stick of RAM taken from a donated computer during the Linux Against Poverty Install Fest at Union Park on Saturday, June 19, 2010.



Volunteer Lionel Felix attempts to boot a donated computer with no luck during the Linux Against Poverty Install Fest at Union Park on Saturday, June 19, 2010. Volunteers later replaced the computer's RAM and it booted.

Friday 2 October 2015

USB audio device setup with Linux Operating System so that we can get sound coming out from the Linux Desktop or Linux Laptop


Source : Ubuntu forum



Ubuntu ForumsFAQ
Forum
Quick Links Forum Community Ubuntu Community Other Support Social Media Useful Links
Activity Page
Please read before SSO login
Submit
Advanced Search
HomeForumThe Ubuntu Forum CommunityOther Discussion and SupportTutorials HOWTO: USB Audio devicePage 1 of 1212311...NextLastLast Results 1 to 10 of 113
Thread: HOWTO: USB Audio device
Thread Tools
Display
May 1st, 2005 #1 SFN's Avatar SFN SFN is offline
Frothy Coffee!

Join Date
Oct 2004
Location
Indiana
Beans
230
Distro
Ubuntu Breezy 5.10
HOWTO: USB Audio device
I have a Tascam US-122 and was having trouble getting it to work. I had seen similar posts regarding other USB sound cards.

This process definitely got my US-122 to work on a number of different machines. Although I haven't tested it on any other devices (because I don't have any) I would think the process would be the same.

First, do

Code:
sudo apt-get install fxload
and download

http://ccrma.stanford.edu/mirrors/ag...0.5-2_i386.deb

Then do

Code:
sudo dpkg -i alsa-tools_1.0.5-2_i386.deb
Now, /usr/share/doc/alsa-tools/README.Debian reveals:

"The alsa-tools packages is almost useles without the alsa-firmware one!

Awfully alsa-firmware has broken license terms and it's to legally
distributable at the moment. The AGNULA team is trying to solve the
issue."
There is a link there to the source for alsa-firmware but I downloaded an RPM from

http://rpm.pbone.net/index.php3/stat....i386.rpm.html

then did

Code:
sudo alien --to-deb alsa-firmware-1.0.6-1.cvs.rhfc2.ccrma.i386.rpm
and

Code:
sudo dpkg -i alsa-firmware_1.0.6-2_i386.deb
Once you have your deb installed (or got the install done from source) download

http://langerland.de/audio/usx2y/usx2y-fw-0.1b.tar.bz2

and extract it.

Do

Code:
lsusb
and make note of the bus and device. In this case:

Bus 001 Device 005: ID 1604:8005 Tascam US-224 Audio/Midi Controller
Now do

Code:
sudo fxload -s /path/to/ld2-ezusb.hex -I /usr/share/alsa/firmware/usx2yloader/us122fw.ihx -D /proc/bus/usb/001/005
/path/to/ represents the location of your ld2-ezusb.hex file. It was in the archive you downloaded from langerland.de. The /001/005 comes from your lsusb results. 001 = Bus. 005 = Device

Finally, do

Code:
sudo usx2yloader
Lights on the US-122 come on. If you do

Code:
cat /proc/asound/cards
you will see something like

0 [Live ]: EMU10K1 - Sound Blaster Live!
Sound Blaster Live! (rev.10) at 0xd000, irq 18
1 [USX2Y ]: USB US-X2Y - TASCAM US-X2Y
TASCAM US-X2Y (1604:8007 if 0 at 001/006)
If you already had a sound card(s) installed, as I did, your USB card will be the last in the list.

Should you reboot or disconnect the device, you'll need to do

Code:
sudo usx2yloader
again to initialize the card.

I'd imagine you could even have usx2yloader run on startup, if the card was attached all the time.

Hope this helps.
In his later years, Oofty Goofty used to like to sit on the front porch of the General Store and
reminisce about the time he let the late, great John L. Sullivan hit him with a billiard cue.
Advanced reply Adv Reply
May 21st, 2005 #2 schdefan's Avatar schdefan schdefan is offline
Gee! These Aren't Roasted!

Join Date
May 2005
Location
vienna, austria
Beans
142
Distro
Ubuntu Breezy 5.10
Re: HOWTO: USB Audio device
Hi SFN!

I really appreciate your description. I have tried a lot of solution through the half last year to get my USB Soundcard working but without success. Now my TASCAM US-122 behaves properly.
Thank you.

schdefan
Advanced reply Adv Reply
June 13th, 2005 #3 goye2cz goye2cz is offline
First Cup of Ubuntu

Join Date
Jun 2005
Beans
3
Re: HOWTO: USB Audio device
I am stuck at this step:

sudo fxload -s /path/to/ld2-ezusb.hex -I /usr/share/alsa/firmware/usx2yloader/us122fw.ihx -D /proc/bus/usb/001/005

/path/to/ represents the location of your ld2-ezusb.hex file. It was in the archive you downloaded from langerland.de. The /001/005 comes from your lsusb results. 001 = Bus. 005 = Device

It keeps giving me this message: unable to open for input.

It's possible that I have the syntax wrong, but I've trid it many different ways.

Any help?

goye2cz
Advanced reply Adv Reply
June 13th, 2005 #4 SFN's Avatar SFN SFN is offline
Frothy Coffee!

Join Date
Oct 2004
Location
Indiana
Beans
230
Distro
Ubuntu Breezy 5.10
Re: HOWTO: USB Audio device
Quote Originally Posted by goye2cz
I am stuck at this step:

sudo fxload -s /path/to/ld2-ezusb.hex -I /usr/share/alsa/firmware/usx2yloader/ -D /proc/bus/usb/001/005

/path/to/ represents the location of your ld2-ezusb.hex file. It was in the archive you downloaded from langerland.de. The /001/005 comes from your lsusb results. 001 = Bus. 005 = Device

It keeps giving me this message: unable to open for input.

It's possible that I have the syntax wrong, but I've trid it many different ways.

Any help?

goye2cz
If you will, do me a favor. Paste the responses from

Code:
sudo find / -name ld2-ezusb.hex
Code:
sudo find / -name us122fw.ihx
and

Code:
lusb
here.
Last edited by SFN; June 14th, 2005 at 02:46 PM.
In his later years, Oofty Goofty used to like to sit on the front porch of the General Store and
reminisce about the time he let the late, great John L. Sullivan hit him with a billiard cue.
Advanced reply Adv Reply
June 14th, 2005 #5 goye2cz goye2cz is offline
First Cup of Ubuntu

Join Date
Jun 2005
Beans
3
Re: HOWTO: USB Audio device
Actually, I tried really hard this morning and finally got my tascam installed. I still seem to be having trouble with jack.

I get this in the messages after I start jackd (using qjackctl):
17:44:16.741 Statistics reset.
17:44:16.768 Could not open ALSA sequencer as a client. MIDI patchbay will be not available.
ALSA lib seq_hw.c:446snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory
17:44:24.497 Startup script...
17:44:24.506 artsshell -q terminate
sh: artsshell: command not found
17:44:24.839 Startup script terminated with exit status=32512.
17:44:24.842 JACK is starting...
17:44:24.844 /usr/bin/jackd -dalsa -dhw:1 -r48000 -p4096 -n2
17:44:24.867 JACK was started with PID=13211 (0x339b).
jackd 0.99.0
Copyright 2001-2003 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
loading driver ..
apparent rate = 48000
creating alsa driver ... hw:1|hw:1|4096|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:1
configuring for 48000Hz, period = 4096 frames, buffer = 2 periods
Couldn't open hw:1 for 32bit samples trying 24bit instead
Couldn't open hw:1 for 32bit samples trying 24bit instead
could not start playback (Broken pipe)
17:44:26.891 Server configuration saved to "/home/goye2cz/.jackdrc".
17:44:26.893 Statistics reset.
17:44:26.911 Client activated.
17:44:26.914 Audio connection change.
17:44:26.957 Audio connection graph change.

I have deactivated realtime and frames/period is set to 4096.

What do you make of it?

goye2cz
Advanced reply Adv Reply
June 15th, 2005 #6 goye2cz goye2cz is offline
First Cup of Ubuntu

Join Date
Jun 2005
Beans
3
Re: HOWTO: USB Audio device
another strange thing is, every time i connect my us-122, I end up with different results at this step:

lsusb

a while ago when I connected, I got these results:

Bus 001 Device 005: ID 1604:8007 Tascam US-122 Audio/Midi Interface

just now, I got these results:

Bus 001 Device 007: ID 1604:8007 Tascam US-122 Audio/Midi Interface

could this be causing me problems?
Advanced reply Adv Reply
June 16th, 2005 #7 satchnut's Avatar satchnut satchnut is offline
First Cup of Ubuntu

Join Date
Jun 2005
Beans
5
Re: HOWTO: USB Audio device
I also own a US-122, but when I enter
sudo usx2yloader

I get
usx2yloader: no US-X2Y-compatible cards found

$ lsusb
Bus 003 Device 007: ID 1604:8007 Tascam US-122 Audio/Midi Interface

Any help would be greatly appreciated, as I've been trying to get this working under Linux for YEARS! Thanks!
Last edited by satchnut; June 16th, 2005 at 06:41 AM.
Advanced reply Adv Reply
June 17th, 2005 #8 SFN's Avatar SFN SFN is offline
Frothy Coffee!

Join Date
Oct 2004
Location
Indiana
Beans
230
Distro
Ubuntu Breezy 5.10
Re: HOWTO: USB Audio device
Quote Originally Posted by goye2cz
another strange thing is, every time i connect my us-122, I end up with different results at this step:

lsusb

a while ago when I connected, I got these results:

Bus 001 Device 005: ID 1604:8007 Tascam US-122 Audio/Midi Interface

just now, I got these results:

Bus 001 Device 007: ID 1604:8007 Tascam US-122 Audio/Midi Interface

could this be causing me problems?
Well, I'm not Mr. USB but as I understand it, the device ID is assigned when you plug a device in. Let's say the first itme you plug in a USB device, that device gets ID 005. The next device you plug in gets IS 006. The next one, 007 and so on. Now let's say the next time you start up, you plugin the device that got ID 007 first. It would get the first available device ID - in this case 005.

Somebody feel free to crrect me if I'm wrong here.

The way I did mine, I had no USB devices plugged in befoer I plugged in the US-122. From that point on, I always made sure that I plugged in the US-122 first. I got the same ID every time.
In his later years, Oofty Goofty used to like to sit on the front porch of the General Store and
reminisce about the time he let the late, great John L. Sullivan hit him with a billiard cue.
Advanced reply Adv Reply
June 17th, 2005 #9 SFN's Avatar SFN SFN is offline
Frothy Coffee!

Join Date
Oct 2004
Location
Indiana
Beans
230
Distro
Ubuntu Breezy 5.10
Re: HOWTO: USB Audio device
Quote Originally Posted by satchnut
I also own a US-122, but when I enter
sudo usx2yloader

I get
usx2yloader: no US-X2Y-compatible cards found

$ lsusb
Bus 003 Device 007: ID 1604:8007 Tascam US-122 Audio/Midi Interface

Any help would be greatly appreciated, as I've been trying to get this working under Linux for YEARS! Thanks!

Paste the responses from
Code:
sudo find / -name ld2-ezusb.hex
and
Code:
sudo find / -name us122fw.ihx
here.
In his later years, Oofty Goofty used to like to sit on the front porch of the General Store and
reminisce about the time he let the late, great John L. Sullivan hit him with a billiard cue.
Advanced reply Adv Reply
June 17th, 2005 #10 SFN's Avatar SFN SFN is offline
Frothy Coffee!

Join Date
Oct 2004
Location
Indiana
Beans
230
Distro
Ubuntu Breezy 5.10
Re: HOWTO: USB Audio device
Quote Originally Posted by goye2cz
Actually, I tried really hard this morning and finally got my tascam installed. I still seem to be having trouble with jack.

I get this in the messages after I start jackd (using qjackctl):
17:44:16.741 Statistics reset.
17:44:16.768 Could not open ALSA sequencer as a client. MIDI patchbay will be not available.
ALSA lib seq_hw.c:446snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory
17:44:24.497 Startup script...
17:44:24.506 artsshell -q terminate
sh: artsshell: command not found
17:44:24.839 Startup script terminated with exit status=32512.
17:44:24.842 JACK is starting...
17:44:24.844 /usr/bin/jackd -dalsa -dhw:1 -r48000 -p4096 -n2
17:44:24.867 JACK was started with PID=13211 (0x339b).
jackd 0.99.0
Copyright 2001-2003 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
loading driver ..
apparent rate = 48000
creating alsa driver ... hw:1|hw:1|4096|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:1
configuring for 48000Hz, period = 4096 frames, buffer = 2 periods
Couldn't open hw:1 for 32bit samples trying 24bit instead
Couldn't open hw:1 for 32bit samples trying 24bit instead
could not start playback (Broken pipe)
17:44:26.891 Server configuration saved to "/home/goye2cz/.jackdrc".
17:44:26.893 Statistics reset.
17:44:26.911 Client activated.
17:44:26.914 Audio connection change.
17:44:26.957 Audio connection graph change.

I have deactivated realtime and frames/period is set to 4096.

What do you make of it?

goye2cz
Just want to double-check. You have two sound cards on your system? Whatever existing card was in the computer and your US-122? Is that right?
Last edited by SFN; June 17th, 2005 at 08:57 PM.
In his later years, Oofty Goofty used to like to sit on the front porch of the General Store and
reminisce about the time he let the late, great John L. Sullivan hit him with a billiard cue.
Advanced reply Adv Reply
Page 1 of 1212311...NextLastLast
Quick Navigation Tutorials Top
« Previous Thread | Next Thread »
Tags for this Thread
fxload
View Tag Cloud
Bookmarks
Submit to Digg Digg Submit to del.icio.us del.icio.us Submit to StumbleUpon StumbleUpon Submit to Google Google
Posting Permissions
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
[VIDEO] code is Off
HTML code is Off
Ubuntu Forums Code of Conduct

Ubuntu Forums Archive Top
All times are GMT +1. The time now is 02:52 AM.
vBulletin ©2000 - 2015, Jelsoft Enterprises Ltd. Ubuntu Logo, Ubuntu and Canonical © Canonical Ltd. Tango Icons © Tango Desktop Project.

User contributions on this site are licensed under the Creative Commons Attribution Share Alike 4.0 International License. For details and our forum data attribution, retention and privacy policy, see here