Susan Cragin wrote:
My drivers have worked great on Studio until a day or so ago.
You know what also happened? Updates. ;) Things like kernel updates
happen that will make you rebase you compiled drivers aginst these new
changes. Make sure you have latest kernel headers and all that.
Also just
Susan Cragin wrote:
Here's a puzzle.
My jaunty ubuntu studio needed to be re-installed today, and I did so using
a 2-week-old installation disk.
There were lots of updates.
Generally, that isn't advised. Grabbing the latest install disk during
development is always advised. Things are
Susan Cragin wrote:
I did a clean install today with today's daily build. I get the same problem.
I suspect a Ubuntu bug.
Straying from what's shipped with a self-compiled ALSA can also
introduce many problems where you could think it's a Ubuntu bug.
Have you had your self-compiled ALSA
Susan Cragin wrote:
I did a clean install today with today's daily build. I get the same
problem.
I suspect a Ubuntu bug.
Straying from what's shipped with a self-compiled ALSA can also introduce many
problems where you could think it's a Ubuntu bug.
Have you had your self-compiled
Susan Cragin wrote:
My drivers have worked great on Studio until a day or so ago.
You know what also happened? Updates. ;) Things like kernel updates
happen that will make you rebase you compiled drivers aginst these new
changes. Make sure you have latest kernel headers and all that.
Also
Here's a puzzle.
My jaunty ubuntu studio needed to be re-installed today, and I did so using a
2-week-old installation disk.
There were lots of updates.
When I finished, I needed to set the system up to use wine and my Creative X-fi
card, so I did the following:
apt-get purge pulseaudio
Susan Cragin wrote:
Here's a puzzle.
My jaunty ubuntu studio needed to be re-installed today, and I did so using a
2-week-old installation disk.
There were lots of updates.
Generally, that isn't advised. Grabbing the latest install disk during
development is always advised. Things are
