Ubuntu-Studio-users Digest, Vol 18, Issue 22

[Gustin Johnson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

suemac at empire.net wrote:
> Thank you for the reply.
> 
> I have printed this and will check out the things you note.
> 
> From the specs in the Dell docs: 256MB NVIDIA GeForce 8600M GT Intel
> Pro/Wireless 3945 802.11 a/g Mini Card Wireless

I have CC'd the list.  This is useful for the archives, for other users
having similar problems, and insurance against me making mistakes.  If I
screwed up (sooner or later this is likely), someone there will likely
spot and correct the mistake(s).

I have used that wireless adaptor and it is supported by Linux out of
the box (right now I am using the iwl4965 that I put into my Acer Aspire
One).  IIRC it requires firmware to be loaded as well.

That video card will require the latest nVidia driver directly from the
nVidia web site.  You are in for a bundle of fun.  Just a tip, when
installing the nVidia package (which you will have to do for every
kernel you use), the second kernel you install to, use the -K flag so it
only builds the kernel module.

> As for the rt kernel, I got the one defined here: 
> https://help.ubuntu.com/community/UbuntuStudioPreparation they
> specified the command:
> 
> sudo apt-get install linux-rt
> 
> I used Synatic instead of apt-get.
> 
Try it again with apt-get, you may be missing dependencies.  I do not
use synaptic so I have no idea what differences there are from the CLI
programs (I personally use aptitude, but I prefer the CLI for most tasks).

The other possability is that there is no /lib/firmware directory for
your rt kernel.  The easiest way to solve this is to simply create a
soft link to the existing firmware directory.

sudo ln -s /lib/firmware/2.6.24-19-generic /lib/firmware/`uname -r`

Of course check the /lib/firmware directory first, to see whats there.

> As for the Tascam US-122 I followed the instructions on these alsa
> and the Ubuntu pages: http://alsa.opensrc.org/index.php/Tascam_US-122
>  https://help.ubuntu.com/community/TASCAM_US-122
> 
> I suspect the two have ahd me create a couple of different /firmware 
> directories and I suspect there may be file access rights issues
> since some of the files are owned by root and some by my generic
> user...not sure if this poses a problem.
> 
> I won't be able to look at this project again until next week.
> 
> Would you mind my asking more questions later?
> 
Not at all, but I strongly encourage you to use the list to do so.
There are a lot of smarter people there who can probably also help.
Since I do not have the same sound card as you, there may be someone one
the list who does.  It just makes sense to use the list.

> "Personally I enjoy leaving batch/wsh behind." I have no problem
> leaving those behind as well...but, I was rather hoping to avoid
> digging into the innerds of boot scripts and such. I spent enough
> time setting up pf and such on my OpenBSD firewall a couple years
> back. That was a refresher course after not doing any uniix flavored
> stuff for 15 years before that...

Unfortunately you don't always get that choice.  I have learned the hard
way to do my hardware homework so that I don't have to dig into the
innards.  The flip side, is that knowing how the system is put together
allows me to bend it to my will.

In the future avoid hardware that forces you to use binary drivers.  I
am a little more forgiving of binary firmware due to the legal
requirements placed on vendors here in North America (I am specifically
thinking of the Intel wireless adaptors, thanks a lot CRTC/FCC).

Hth,
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFI9RdxwRXgH3rKGfMRAvvOAJkBhmYQK8YNEcsHA1CCmun9s5APaQCgsBIT
t9t1jSOE+AVexUwJcXxyYsc=
=uz1a
-----END PGP SIGNATURE-----