Re: MAO, jaunty, RT, asus eeepc

2009-05-24 Thread laurent.bellegarde
Luis de Bethencourt a écrit :
 Awesome! Are you planing on uploading it to youtube? I will probably
 want to blog about this.

 Luis

Hi all,

you have it here on youtube :

http://www.youtube.com/watch?v=yflMyGjOd3A

Laurent

-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: MAO, jaunty, RT, asus eeepc

2009-05-22 Thread Luis de Bethencourt
Awesome! Are you planing on uploading it to youtube? I will probably
want to blog about this.

Luis

On Thu, May 21, 2009 at 5:38 PM, laurent.bellegarde
laurent.bellega...@free.fr wrote:
 Luis de Bethencourt a écrit :
 where is the video? :)

 Im very interested.

 Luis

 Hi all, it takes time, but the editing in now complete. You can download
 it in DVD quality here in latests news :

 http://lprod.org/wiki/doku.php/en:accueil#latest_news

 I've forget to mention at the end that the flying ubuntu studio logo has
 been made with the powerfull free software jahshaka.

 Enjoy !!! it's free to use...

 Laurent

 --
 Ubuntu-Studio-users mailing list
 Ubuntu-Studio-users@lists.ubuntu.com
 Modify settings or unsubscribe at: 
 https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users




-- 
Luis de Bethencourt Guimerá
luisbg
lui...@ubuntu.com
GPG: B0ED1326

-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: MAO, jaunty, RT, asus eeepc

2009-05-21 Thread laurent.bellegarde
Luis de Bethencourt a écrit :
 where is the video? :)

 Im very interested.

 Luis

Hi all, it takes time, but the editing in now complete. You can download 
it in DVD quality here in latests news :

http://lprod.org/wiki/doku.php/en:accueil#latest_news

I've forget to mention at the end that the flying ubuntu studio logo has 
been made with the powerfull free software jahshaka.

Enjoy !!! it's free to use...

Laurent

-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: MAO, jaunty, RT, asus eeepc

2009-05-20 Thread Luis de Bethencourt
where is the video? :)

Im very interested.

Luis

On Mon, May 18, 2009 at 9:19 AM, laurent.bellegarde
laurent.bellega...@free.fr wrote:
 Hi all,

 last week-end, lprod.org team was in Paris, for the main Ubuntu's party
 jaunty 9.04.

 During 2 days, we present free audio and video editing under ubuntu
 studio Jaunty RT. 4000 persons visit our place.
 We have seen, beginners, intermediate user and advanced or
 professionnal, all have been very impressed by Ubuntu Studio performances.

 As jaunty RT kernel is better than hardy'one, we succeded to construct
 easily with only the integrate sound card a MAO station with asus eeepc
 1000 running under ubuntu studio 9.04 RT. Latency of internal card was
 5,3ms, and the system was running perfectly. I've made a small video of
 this extraordinay MAO station !!!

 Many congratultions to ubuntu studio team for the new RT kernel...

 Bye,

 Laurent
 lprod.org

 --
 Ubuntu-Studio-users mailing list
 Ubuntu-Studio-users@lists.ubuntu.com
 Modify settings or unsubscribe at: 
 https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users




-- 
Luis de Bethencourt Guimerá
luisbg
lui...@ubuntu.com
GPG: B0ED1326

-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


MAO, jaunty, RT, asus eeepc

2009-05-18 Thread laurent.bellegarde
Hi all,

last week-end, lprod.org team was in Paris, for the main Ubuntu's party 
jaunty 9.04.

During 2 days, we present free audio and video editing under ubuntu 
studio Jaunty RT. 4000 persons visit our place.
We have seen, beginners, intermediate user and advanced or 
professionnal, all have been very impressed by Ubuntu Studio performances.

As jaunty RT kernel is better than hardy'one, we succeded to construct 
easily with only the integrate sound card a MAO station with asus eeepc 
1000 running under ubuntu studio 9.04 RT. Latency of internal card was 
5,3ms, and the system was running perfectly. I've made a small video of 
this extraordinay MAO station !!!

Many congratultions to ubuntu studio team for the new RT kernel...

Bye,

Laurent
lprod.org

-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


jaunty, RT, ATI, 3D acceleration

2009-04-20 Thread laurent.bellegarde
Hi all,

This is my last test of jaunty studio.

There is still a large trouble with ATI 3D Flgrx driver with Jaunty RT 
32 bit kernel.

my laptop to test :

- dual-core Pentium 4-2 Ghz ; 4 Go ram ; ATI radeon HD3470 256 Mo

under hardy

- hardy studio 64 - ATI 3D flrgx - RT kernel (production system) : Ok 
for all, 3D acceleration gives excellents results

under jaunty

- jaunty studio 32 - ATI 2D open driver - RT kernel : ok for all, very 
small 3D acceleration, video editing tools are slowest during video effects.

- jaunty studio 32 - ATI 3D Fligrx - RT kernel : boot ok, i can hear the 
first sound of gdm appear but the image is a mid of black and colored 
square, if i give my user name/password, i can connect the desktop (i 
can hear the music of opening clearly) but without seeing something, the 
screen keeps his view. If i tried the CRTL+ALT+F2 to open a terminal, 
the system reboot suddenly !!! Nothing is possible.

- jaunty studio 32 - ATI 3D Fligrx - generic kernel : Ok for all, 3D 
acceleration gives medium results, video readers are slowed, same thing 
for video editing tools.

So if you need to use 3D acceleration and RT kernel under ubuntu with an 
ATI card, Hardy Studio is still the best at this time.

-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Re: Jaunty RT testing

2009-04-20 Thread wayne
On Sun, 2009-04-19 at 21:30 +, beej...@gmail.com wrote:

 On Apr 19, 2009 2:00pm, wayne wa...@jawnee.org wrote:
  maybe it is not jackd that is stuck, but qjackctl, the QT gui
 for using jack?  if so, killall qjackctl.bin may work.  the nice
 thing about killall (at least on 8.04), is that after typing
 killall, then entering a space, then start typing the name of the
 process, you can use the Tab key (ala Bash command completion) to
 finish the process name.  when JACK freezes, check with killall if
 jackd is even running.  it may just be that qtjackctl is stuck, which
 happens to me when the underlying jackd process crashes: jackd dies,
 but qtjackctl is frozen.  also, the qtjackctl process will prob be
 qtjackctl.bin, since that pre-script pauses PulseAudio using
 paususpender before starting jackd... again, at least on 8.04.  this
 way, no PulseAudio getting in the way, while not having to totally
 remove it.
  
  
  
  hope that helps.
 
 Thanks, I'll give these different techniques a shot, I'm sure one of
 them will work. I'm still a bit baffled as to why the GUI for qjackctl
 was changed at all to remove the ability to force quit. It worked
 fined in Hardy, but with Jaunty the ability to just hit the 'X' button
 on the windows and close it is now gone, along with the ability to
 right click and hit 'force quit'. It's the same for any windows that
 JACK opens up, such as the message window. Before, you could close it
 by hitting the 'X' button, but now you must close it by hitting the
 'Messages' button on the GUI itself. Did they just want to make sure
 people were using the GUI to do these things?
 
 -Brian

not sure about the changes, as i am still using 8.04 Hardy.  perhaps
it is as you said, making sure the qjackctl program can only be closed
certain ways, ensuring better cleanup of underlying jackd processes...
or maybe something changed in QT/GNOME/Metacity in 9.10 Jaunty.  let us
know if it works.

peace.
-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Jaunty RT testing

2009-04-19 Thread wayne

 2009/4/19 wayne wa...@jawnee.org
 
 
 On Mon, 2009-04-13 at 22:37 -0500, Brian David wrote:
 
  On Mon, Apr 13, 2009 at 1:49 PM, Cory K.
  coryis...@ubuntu.com wrote:
  
  beej...@gmail.com wrote:
   On Apr 13, 2009 1:07pm, Cory K.
  coryis...@ubuntu.com wrote:
  
   System-Admin-Ubuntu Studio Controls
  
  
  
   Believe me, I tried to use Studio Controls. Jaunty
  changed the
   relevant permissions file from
   /etc/udev/rules.d/40-basic-permissions.rules
  (which is, I believe, the
   file that Studio Controls is editing) to
   /lib/udev/rules.d/50-udev-default.rules. When I
  selected the
   appropriate box in Studio Controls to allow
  raw1394 permission, this
   did not fix my problem. I had to use the solution
  I mentioned in the
   earlier post. The original
  40-basic-permissions.rules found in Ibex
   and Hardy is not in Jaunty.
  
  
  
  Please don't email me directly. ;)
  
  I'll have someone look at it. I seem to remember
  some changes that
  address what you said above. Maybe the changes
  didn't hit yet. 
  
  
  
  -Cory K.
  
  --
  Ubuntu-Studio-users mailing list
  Ubuntu-Studio-users@lists.ubuntu.com
  Modify settings or unsubscribe at:
  
 https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
  
  
  
  Oh, hey, I just remembered another small annoyance.
  
  For whatever reason, the new version of JACK doesn't allow
  me to force quit if JACK freezes (which is common when
  you're testing the settings)  Instead, I need to restart X
  now in order to get JACK turned off after a freeze, because
  I'm a noob and I'm not sure how to do it via command line.
  It's not a huge inconvenience, and I'm not even sure it's
  something the Ubuntu Studio team can do anything about, but
  it would be nice if I could just force quit JACK like the
  old days.
 
 you can try killall jackd from the command line.  or use
 the GUI-enabled System Monitor available in the menu under
 System/Administration, at least on 8.04 Hardy UBS.
 
 good luck.
 
 
  
  -- 
  -Brian David
 
 
 --
 Ubuntu-Studio-users mailing list
 Ubuntu-Studio-users@lists.ubuntu.com
 Modify settings or unsubscribe at:
 https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
 
 
 

On Sun, 2009-04-19 at 20:05 +0200, Christian Masser wrote:

 Same Problem to me, but killall jackd doesn't work, but I didn't try
 it with the system monitor, thanks for the tip
 
 ~Christian Masser
 
 


maybe it is not jackd that is stuck, but qjackctl, the QT gui for
using jack?  if so, killall qjackctl.bin may work.  the nice thing
about killall (at least on 8.04), is that after typing killall, then
entering a space, then start typing the name of the process, you can use
the Tab key (ala Bash command completion) to finish the process name.
when JACK freezes, check with killall if jackd is even running.  it may
just be that qtjackctl is stuck, which happens to me when the underlying
jackd process crashes: jackd dies, but qtjackctl is frozen.  also, the
qtjackctl process will prob be qtjackctl.bin, since that pre-script
pauses PulseAudio using paususpender before starting jackd... again, at
least on 8.04.  this way, no PulseAudio getting in the way, while not
having to totally remove it.

hope that helps.

-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Jaunty RT testing

2009-04-19 Thread Fernando Gomes
Hi, I'm running ubuntustudio 8.04 and today I tried to install a
second boot with Jaunty. The normal Jaunty setup works well, not a
problem detected (didn't test it much, only used the normal office
internet applications and they were running well with the standard
kernel)). Then I installed the ubuntustudio packages (including the RT
kernel). After this step, if I try to boot using the RT kernel, it
locks during boot. The kernel is the 2.6.28-3-rt, the last message
during boot is:

[0.392000] io scheduler cfq registered (default)

The same machine is working well with 8.04 and kernel 2.6.24-23-rt

The PC is a AMD Athlon(tm) 64 X2 Dual Core Processor 4400+, with 1GB
RAM and 500 GB SATA HDD (Samsung)
The motherboard is an Elite A780GM-A Black Edition with integrated
graphics (AMD 780G-based with ATI™ Radeon HD3200 graphics)

Do you want me to test anything else on this hardware setup?

Fernando


On Sun, Apr 19, 2009 at 8:00 PM, wayne wa...@jawnee.org wrote:

 2009/4/19 wayne wa...@jawnee.org

 On Mon, 2009-04-13 at 22:37 -0500, Brian David wrote:

 On Mon, Apr 13, 2009 at 1:49 PM, Cory K. coryis...@ubuntu.com wrote:

 beej...@gmail.com wrote:
 On Apr 13, 2009 1:07pm, Cory K. coryis...@ubuntu.com wrote:

 System-Admin-Ubuntu Studio Controls



 Believe me, I tried to use Studio Controls. Jaunty changed the
 relevant permissions file from
 /etc/udev/rules.d/40-basic-permissions.rules (which is, I believe, the
 file that Studio Controls is editing) to
 /lib/udev/rules.d/50-udev-default.rules. When I selected the
 appropriate box in Studio Controls to allow raw1394 permission, this
 did not fix my problem. I had to use the solution I mentioned in the
 earlier post. The original 40-basic-permissions.rules found in Ibex
 and Hardy is not in Jaunty.



 Please don't email me directly. ;)

 I'll have someone look at it. I seem to remember some changes that
 address what you said above. Maybe the changes didn't hit yet.



 -Cory K.

 --
 Ubuntu-Studio-users mailing list
 Ubuntu-Studio-users@lists.ubuntu.com
 Modify settings or unsubscribe at:
 https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


 Oh, hey, I just remembered another small annoyance.

 For whatever reason, the new version of JACK doesn't allow me to force quit
 if JACK freezes (which is common when you're testing the settings)  Instead,
 I need to restart X now in order to get JACK turned off after a freeze,
 because I'm a noob and I'm not sure how to do it via command line.  It's not
 a huge inconvenience, and I'm not even sure it's something the Ubuntu Studio
 team can do anything about, but it would be nice if I could just force quit
 JACK like the old days.

     you can try killall jackd from the command line.  or use the
 GUI-enabled System Monitor available in the menu under
 System/Administration, at least on 8.04 Hardy UBS.

 good luck.


 --
 -Brian David

 --
 Ubuntu-Studio-users mailing list
 Ubuntu-Studio-users@lists.ubuntu.com
 Modify settings or unsubscribe at:
 https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


 On Sun, 2009-04-19 at 20:05 +0200, Christian Masser wrote:

 Same Problem to me, but killall jackd doesn't work, but I didn't try it with
 the system monitor, thanks for the tip

 ~Christian Masser



     maybe it is not jackd that is stuck, but qjackctl, the QT gui for using
 jack?  if so, killall qjackctl.bin may work.  the nice thing about killall
 (at least on 8.04), is that after typing killall, then entering a space,
 then start typing the name of the process, you can use the Tab key (ala Bash
 command completion) to finish the process name.  when JACK freezes, check
 with killall if jackd is even running.  it may just be that qtjackctl is
 stuck, which happens to me when the underlying jackd process crashes: jackd
 dies, but qtjackctl is frozen.  also, the qtjackctl process will prob be
 qtjackctl.bin, since that pre-script pauses PulseAudio using paususpender
 before starting jackd... again, at least on 8.04.  this way, no PulseAudio
 getting in the way, while not having to totally remove it.

     hope that helps.


 --
 Ubuntu-Studio-users mailing list
 Ubuntu-Studio-users@lists.ubuntu.com
 Modify settings or unsubscribe at:
 https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users



-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Jaunty RT kernel and NVidia drivers

2009-04-13 Thread Cory K.
Fabien Juchniewicz wrote:
 Hello,

 I can't install the NVidia v180 driver on my Jaunty 64 bits test machine with 
 the 2.6.28-3 RT kernel. If I use the Kubuntu hardware manager, it breaks xorg 
 : I have to reconfigure.

 Is there a way with dkms ?
   

Make sure you have the header packages installed.


-Cory K.


-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Jaunty RT kernel and NVidia drivers

2009-04-13 Thread Fabien Juchniewicz
Le Monday 13 April 2009 08:50:16 Cory K., vous avez écrit :
 Fabien Juchniewicz wrote:
  Hello,
 
  I can't install the NVidia v180 driver on my Jaunty 64 bits test machine
  with the 2.6.28-3 RT kernel. If I use the Kubuntu hardware manager, it
  breaks xorg
 
  : I have to reconfigure.
 
  Is there a way with dkms ?

 Make sure you have the header packages installed.


 -Cory K.

Thanx very much.

That was the point.

I had a problem with the header installed. I had to purge and install back the 
header package, then the dkms in the post-install did the trick.

Thanks again.

/Fabien
-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Jaunty RT testing

2009-04-13 Thread Brian David
On Thu, Apr 2, 2009 at 5:33 PM, Brian David beej...@gmail.com wrote:

 I've been reading this list in the archives for a while now, and decided to
 join up so I could pitch in with the Jaunty Beta testing.  Still fairly new
 to Linux, and to using e-mail lists for that matter, so keep that in mind as
 you read this.

 First up, here's my hardware.  It's a fairly old desktop that I use for
 testing:

 Motherboard: Asrock K7VT4A
 Processor: AMD Sempron 2400+
 Video: ATI Radeon 9600+
 Memory: 2 GB
 Audio Interface: Presonus Firepod

 *SNIP*
 --
 -Brian David


I realize that testing the actual Ubuntu Studio distro as opposed to an
upgraded regular Ubuntu install is more helpful to the dev team.  So I went
ahead and downloaded the Jaunty daily (per Cory's reccommendation) from
yesterday, installed, and did some more test runs.  Same hardware as
mentioned in the e-mail above.

Install went just fine, booted up with no problems.

As a quick aside, while the new artwork is indeed very fancy, I personally
don't think it's as classy as the old versions.  The old style was more
'earthy' and this new artwork is a bit too slick.  Obviously, that's neither
her nor there, since I can just change that, but I figured I'd mention it.

I'd also like to note that it's a bit of a hassle getting the permissions
for firewire devices worked out.  I either had to manually change the
permissions on /dev/raw1394 using chmod every time I booted up, run JACK as
root every time I used JACK, or edit my
/lib/udev/rules.d/50-udev-default.rules file to put the firewire device in
the 'audio' group.  I went for that last one because it provided a somewhat
permanent, one-time solution.  Would it be possible to have Ubuntu Studio
itself fix this issue in some way on install, so that firewire users can get
closer to the desired 'works out of the box' goal?

However, once I got my rig going, the tests themselves went well.  I put up
a single mic to record one track into Ardour, then I ran several tests at
different sample rates.  My first test was a push-the-limits thing.  I
recorded at 96 khz, 256 frames/period.  I used software monitoring in
Ardour, and even browsed the internet while I recorded.  After I recorded
about ten minutes using ffado, I had around 17 xruns, which is, for this
machine, actually very good.  Similar results were had from freebob (freebob
seems to work much better under Ubuntu Studio then under a regular Ubuntu
install).  I then redid the test just recording, still using software
monitoring, but without doing any other programs running.  Freebob had 2
xruns after ten minutes, and ffado had a whopping 0.  Impressive!  This
thing should be very stable at lower sampling rates.

I then opened up an 11 track drum session originally recorded in Pro Tools
and futzed around for a bit.  I'm still having problems with the Ardour
plug-ins, similar to what I mentioned in my original post.  Many of the
parameters are frozen in place and unchangeable.  On a regular Ubuntu
install I fixed this by removing Ardour and reinstalling from a deb from
getdeb.net.  I have not done this with Ubuntu Sudio, yet.  This is the
biggest problem so far, and I'd appreciate it if anyone had info on any
possible fixes, or if it will be fixed in the offical release.  I'm farily
sure it must have something to do with the Ubuntu packages, and not Ardour
itself.

I'll keep testing.  So far, the RT kernel itself seems to be working very
well.  Thanks for all the hard work everyone!


-- 
-Brian David
-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Jaunty RT testing

2009-04-13 Thread Cory K.
Brian David wrote:
 I'd also like to note that it's a bit of a hassle getting the permissions
 for firewire devices worked out.

System-Admin-Ubuntu Studio Controls


-Cory K.

-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Jaunty RT testing

2009-04-13 Thread Cory K.
beej...@gmail.com wrote:
 On Apr 13, 2009 1:07pm, Cory K. coryis...@ubuntu.com wrote:
 System-Admin-Ubuntu Studio Controls


 Believe me, I tried to use Studio Controls. Jaunty changed the
 relevant permissions file from
 /etc/udev/rules.d/40-basic-permissions.rules (which is, I believe, the
 file that Studio Controls is editing) to
 /lib/udev/rules.d/50-udev-default.rules. When I selected the
 appropriate box in Studio Controls to allow raw1394 permission, this
 did not fix my problem. I had to use the solution I mentioned in the
 earlier post. The original 40-basic-permissions.rules found in Ibex
 and Hardy is not in Jaunty.


Please don't email me directly. ;)

I'll have someone look at it. I seem to remember some changes that
address what you said above. Maybe the changes didn't hit yet.


-Cory K.

-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Jaunty RT testing

2009-04-06 Thread Brian David
On Thu, Apr 2, 2009 at 5:33 PM, Brian David beej...@gmail.com wrote:

 I've been reading this list in the archives for a while now, and decided to
 join up so I could pitch in with the Jaunty Beta testing.  Still fairly new
 to Linux, and to using e-mail lists for that matter, so keep that in mind as
 you read this.

 *SNIP*

 --
 -Brian David


Just a quick follow up, I'm not sure what it is that's come down the update
pipe recently, but it has fixed my shut-down and restart problems.  So
that's good!

-- 
-Brian David
-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Severe crashes with JACK/FFADO on Jaunty RT

2009-04-03 Thread Артём Попов
Hello, everyone!

I'm desperately looking for help with the following problem, and I
guess this is the first place to ask for directions.

Some time ago I have tried an Echo Audiofire 2 audio card (firewire)
with my Ubuntu systems and it worked very well with Intrepid and
Jaunty alpha 4 even without a realtime kernel. I have installed the
FFADO and JACK packages from Khashayar's PPA, and had nearly 100%
success (occasional XRUNs don't count). The card is flashed with the
latest firmware, as recommended.

Right now I don't have Intrepid, and my Jaunty system is fully
updated, but JACK and FFADO produce heavy xruns with the generic
kernel and crash very often with the rt-kernel. The crashes are
random, they happen with and without actual audio apps. My primary
testing app is MOC audio player for now :)

My system is Athlon64x2 laptop with an ATI Radeon (no proprietary drivers used).

$ uname -a
Linux teaquetzl 2.6.28-3-rt #9-Ubuntu SMP PREEMPT RT Fri Mar 27
23:23:50 UTC 2009 i686 GNU/Linux

Here's my limits.conf:
@admin - rtprio 99
@admin - nice -19
@admin - memlock unlimited

/etc/default/rtirq is tweaked the following way:
RTIRQ_NAME_LIST=rtc ohci1394 snd usb i8042
RTIRQ_NON_THREADED=rtc ohci1394 snd

I have attached the logs produced with jackd -R -d firewire -v2. The
warning about loadFromMemory appeared in the past, but it didn't seem
to break anything.

I have also rebuilt the FFADO debs using the latest SVN checkout
(1.999.41) today and the whole bunch or error messages changed to
something different, so I am attaching this log as well.
a...@teaquetzl:~$ jackd -R -d firewire -v2
no message buffer overruns
jackd 0.116.1
Copyright 2001-2005 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

JACK compiled with System V SHM support.
loading driver ..
01577676472:  (ffado.cpp)[  92] ffado_streaming_init: libffado 1.999.40- built 
Feb 24 2009 00:53:39
01577969078: Warning (fireworks_session_block.cpp)[ 257] loadFromMemory: size 
not correct: got 13392, should be 0 according to data
libiec61883 warning: Established connection on channel 0.
You may need to manually set the channel on the receiving node.
libiec61883 warning: Established connection on channel 1.
You may need to manually set the channel on the transmitting node.
01661008217: Fatal (IsoHandlerManager.cpp)[ 342] Execute: (0x9983858, Receive) 
Handler died: now: 204A048F, last: 1C46258A, diff: 49342213 (max: 49152000)
firewire ERR: wait status  0! (= -1)
DRIVER NT: could not run driver cycle
01665125319: Error (IsoHandler.cpp)[ 646] prepare: Incorrect state, expected 
E_Initialized, got 4
01665125346: Fatal (IsoHandler.cpp)[ 692] enable: Could not prepare handler
01665125353: Error (StreamProcessor.cpp)[1167] scheduleStartDryRunning: Could 
not start handler for SP 0x9995ac8
01665125360: Error (StreamProcessorManager.cpp)[ 412] startDryRunning: Could 
not put SP 0x9995ac8 into the dry-running state
01665125370: Error (IsoHandler.cpp)[ 646] prepare: Incorrect state, expected 
E_Initialized, got 4
01665125376: Fatal (IsoHandler.cpp)[ 692] enable: Could not prepare handler
01665125381: Error (StreamProcessor.cpp)[1167] scheduleStartDryRunning: Could 
not start handler for SP 0x9995ac8
01665125386: Error (StreamProcessorManager.cpp)[ 412] startDryRunning: Could 
not put SP 0x9995ac8 into the dry-running state
01665125396: Error (IsoHandler.cpp)[ 646] prepare: Incorrect state, expected 
E_Initialized, got 4
01665125401: Fatal (IsoHandler.cpp)[ 692] enable: Could not prepare handler
01665125407: Error (StreamProcessor.cpp)[1167] scheduleStartDryRunning: Could 
not start handler for SP 0x9995ac8
01665125412: Error (StreamProcessorManager.cpp)[ 412] startDryRunning: Could 
not put SP 0x9995ac8 into the dry-running state
01665125421: Error (IsoHandler.cpp)[ 646] prepare: Incorrect state, expected 
E_Initialized, got 4
01665125427: Fatal (IsoHandler.cpp)[ 692] enable: Could not prepare handler
01665125431: Error (StreamProcessor.cpp)[1167] scheduleStartDryRunning: Could 
not start handler for SP 0x9995ac8
01665125437: Error (StreamProcessorManager.cpp)[ 412] startDryRunning: Could 
not put SP 0x9995ac8 into the dry-running state
01665125447: Error (IsoHandler.cpp)[ 646] prepare: Incorrect state, expected 
E_Initialized, got 4
01665125452: Fatal (IsoHandler.cpp)[ 692] enable: Could not prepare handler
01665125457: Error (StreamProcessor.cpp)[1167] scheduleStartDryRunning: Could 
not start handler for SP 0x9995ac8
01665125462: Error (StreamProcessorManager.cpp)[ 412] startDryRunning: Could 
not put SP 0x9995ac8 into the dry-running state
01665125472: Error (IsoHandler.cpp)[ 646] prepare: Incorrect state, expected 
E_Initialized, got 4
01665125477: Fatal (IsoHandler.cpp)[ 692] enable: Could not prepare handler
01665125482: Error (StreamProcessor.cpp)[1167] scheduleStartDryRunning: Could 
not start handler for SP 0x9995ac8

Jaunty RT testing

2009-04-02 Thread Brian David
I've been reading this list in the archives for a while now, and decided to
join up so I could pitch in with the Jaunty Beta testing.  Still fairly new
to Linux, and to using e-mail lists for that matter, so keep that in mind as
you read this.

First up, here's my hardware.  It's a fairly old desktop that I use for
testing:

Motherboard: Asrock K7VT4A
Processor: AMD Sempron 2400+
Video: ATI Radeon 9600+
Memory: 2 GB
Audio Interface: Presonus Firepod

I grabbed the Beta on the day of its release, and the good news is that the
install ran smoothly and I had the RT kernel up and running after not too
much hassle.  I should say that I was using a regular Jaunty CD with the
UbuntuStudio audio and graphics meta-packages installed, and not the actual
UbuntuStudio CD.

My Firepod has always worked well with Linux, which I'm thankful for.  As
for performance, the freebob driver in Jack is essentially useless on this
computer, too many X-runs (although it seems to work great on my MacBook
booted into Hardy, which is my production machine).  However, the firewire
driver (FFADO, right?) works wonderfully.  I spent an hour or so messing
around with a simple three-track live recording, and there was not a single
X-run (JACK settings were Frame/Periods: 256, Sample Rate: 44100
Periods/Buffer: 3).

BUT, I ran into problems while trying to do my final mixdowns from Ardour.
To be exact, I couldn't mix down a full track without JACK shutting down.  I
tried easing the JACK settings back a little, but still no luck.  The tracks
would mixdown, but JACK would immediately then crash, and I'd have to
restart the Firepod and JACK to get things going again.  It's hard to tell
if this is due to the age of the computer, or the RT kernel.

Also, I ran into problems with some of the plug-ins in Ardour.  I found that
I could not adjust many of the settings (for instance, the frequency setting
in a parametric EQ I was using could not be changed at all).  I remember
reading on the Ardour website that there might be some problems with the
packages in the Ubuntu repos.  So I re-installed Ardour using a .deb I
downloaded from getdeb.net, and the problem disappeared.  Is this something
your package managers can fix?

The final HUGE glaring bug is that the RT kernel will not shut down or
restart.  When I try, it just freezes, and I need to shutdown the computer
manually.  This is not a problem with the generic kernel.

Overall, everything is working suprisingly well for a beta.  I'm really
looking forward to using this kernel on my MacBook.

-- 
-Brian David
-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Jaunty -RT testing

2009-03-22 Thread Eric S. Johansson
Joseph Reagle wrote:
 As an aside, while I wasn't comfortable with with Jaunty RT oddness, I don't
 think NaturallySpeaking in a VirtualBox Machine requires RT, just
 low-latency. So I actually tried Intrepid again and built a kernel [1] with
 the following settings. I'm also using the new vbox 2.2b1 [2] -- with much
 improved USB performance -- and things seem quite good.

interesting.  2.2 Beta one with the standard kernel of 8.10 gives me choppy
audio.  I've put a note on the mailing list about this and offer to try and help
gather some information to figure out what's wrong.  I wonder if a different
scheduler might help.


-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Jaunty -RT testing

2009-03-21 Thread Joseph Reagle

As an aside, while I wasn't comfortable with with Jaunty RT oddness, I don't 
think NaturallySpeaking in a VirtualBox Machine requires RT, just low-latency. 
So I actually tried Intrepid again and built a kernel [1] with the following 
settings. I'm also using the new vbox 2.2b1 [2] -- with much improved USB 
performance -- and things seem quite good.

CONFIG_MCORE2=y
# CONFIG_NO_HZ is not set
CONFIG_HIGHMEM64G=y
CONFIG_HZ_1000=y
CONFIG_HZ=1000
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
CONFIG_PREEMPT=y
# CONFIG_PREEMPT_RCU is not set
# CONFIG_PREEMPT_TRACER is not set
# CONFIG_DEBUG_KERNEL is not set


[1]:https://help.ubuntu.com/community/Kernel/Compile#Alternate%20Build%20Method:%20The%20Old-Fashioned%20Debian%20Way
 
[2]:http://forums.virtualbox.org/viewtopic.php?f=15t=15525sid=121f0f57ec7b7bf0bf65a0e18cd97bf5

-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Jaunty -RT testing

2009-03-18 Thread Joseph Reagle
On Monday 16 March 2009, Gustin Johnson wrote:
 I have a custom 2.6.28, the one difference I see is that I have HZ=1000.

Yes, turns out I use 1000 too. (My notes said 250, but I check my .config which 
is HZ=1000.)

Are you running 2.6.28 with jaunty?


-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Jaunty -RT testing

2009-03-18 Thread Joseph Reagle

This test was with Virtualbox. I can use that and VMWare with hardy and a 
tweaked custom kernel. (Using VMWare has been increasingly difficult, given all 
the vmware-any-any patches one must deal with.)

Once Jaunty is released and if -rt isn't satisfactory (e.g., suspend) I'll 
probably try building a custom kernel off the generic kernel with options like 
CONFIG_PREEMPT_VOLUNTARY=y CONFIG_HIGHMEM64G=y CONFIG_HZ_250=y and see if 
that is sufficient to my task... Not RT, and no patches, but perhaps good 
enough.

-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Jaunty -RT testing

2009-03-18 Thread Susan Cragin
With a bit more information, we may be able to help you work out the problem 
you are having.

Luke
Here is my xorg.0.log
By the way, I just tried Audacity and that seems to work fine. 


X.Org X Server 1.6.0
Release Date: 2009-2-25
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-19-server i686 Ubuntu
Current Operating System: Linux ubuntu 2.6.28-2-rt #6-Ubuntu SMP PREEMPT RT Tue Mar 10 02:10:25 UTC 2009 i686
Build Date: 07 March 2009  02:18:57AM
xorg-server 2:1.6.0-0ubuntu1 (bui...@rothera.buildd) 
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: [0.001568] (--) probed, [0.001581] (**) from config file, [0.001589] (==) default setting,
	[0.001597] (++) from command line, [0.001605] (!!) notice, [0.001613] (II) informational,
	[0.001623] (WW) warning, [0.001631] (EE) error, [0.001639] (NI) not implemented, [0.001647] (??) unknown.
[0.001712] (==) Log file: /var/log/Xorg.0.log, Time: Sun Mar 15 21:02:28 2009
[0.002313] (==) Using config file: /etc/X11/xorg.conf
[0.002398] (==) No Layout section.  Using the first Screen section.
[0.002637] (**) |--Screen Default Screen (0)
[0.002656] (**) |   |--Monitor Configured Monitor
[0.002873] (**) |   |--Device Configured Video Device
[0.002897] (==) Automatically adding devices
[0.002903] (==) Automatically enabling devices
[0.005949] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist.
	Entry deleted from font path.
[0.008570] (==) FontPath set to:
	/usr/share/fonts/X11/misc,
	/usr/share/fonts/X11/100dpi/:unscaled,
	/usr/share/fonts/X11/75dpi/:unscaled,
	/usr/share/fonts/X11/Type1,
	/usr/share/fonts/X11/100dpi,
	/usr/share/fonts/X11/75dpi,
	/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,
	built-ins
[0.008583] (==) ModulePath set to /usr/lib/xorg/modules
[0.008590] (II) Cannot locate a core pointer device.
[0.008596] (II) Cannot locate a core keyboard device.
[0.008601] (II) The server relies on HAL to provide the list of input devices.
	If no devices become available, reconfigure HAL or disable AllowEmptyInput.
[0.008621] (II) Loader magic: 0x3bc0
[0.008627] (II) Module ABI versions:
	X.Org ANSI C Emulation: 0.4
	X.Org Video Driver: 5.0
	X.Org XInput driver : 4.0
	X.Org Server Extension : 2.0
[0.008656] (II) Loader running on linux
[0.008667] (++) using VT number 7

[0.060086] (--) PCI:*(0...@1:0:0) nVidia Corporation GeForce 8600M GT rev 161, Mem @ 0xfc00/16777216, 0xe000/268435456, 0xfa00/33554432, I/O @ 0x8c00/128, BIOS @ 0x/131072
[0.060176] (II) Open ACPI successful (/var/run/acpid.socket)
[0.060193] (II) System resource ranges:
	[0] -1	0	0x - 0x (0x1) MX[B]
	[1] -1	0	0x000f - 0x000f (0x1) MX[B]
	[2] -1	0	0x000c - 0x000e (0x3) MX[B]
	[3] -1	0	0x - 0x0009 (0xa) MX[B]
	[4] -1	0	0x - 0x (0x1) IX[B]
	[5] -1	0	0x - 0x (0x1) IX[B]
[0.060319] (II) LoadModule: extmod
[0.062632] (II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
[0.062797] (II) Module extmod: vendor=X.Org Foundation
	compiled for 1.6.0, module version = 1.0.0
	Module class: X.Org Server Extension
	ABI class: X.Org Server Extension, version 2.0
[0.062826] (II) Loading extension MIT-SCREEN-SAVER
[0.062832] (II) Loading extension XFree86-VidModeExtension
[0.062838] (II) Loading extension XFree86-DGA
[0.062846] (II) Loading extension DPMS
[0.062851] (II) Loading extension XVideo
[0.062859] (II) Loading extension XVideo-MotionCompensation
[0.062865] (II) Loading extension X-Resource
[0.062871] (II) LoadModule: dbe
[0.063133] (II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
[0.063203] (II) Module dbe: vendor=X.Org Foundation
	compiled for 1.6.0, module version = 1.0.0
	Module class: X.Org Server Extension
	ABI class: X.Org Server Extension, version 2.0
[0.063229] (II) Loading extension DOUBLE-BUFFER
[0.063236] (II) LoadModule: glx
[0.063491] (II) Loading /usr/lib/xorg/modules/extensions//libglx.so
[0.063610] (II) Module glx: vendor=X.Org Foundation
	compiled for 1.6.0, module version = 1.0.0
	ABI class: X.Org Server Extension, version 2.0
[0.063648] (==) AIGLX enabled
[0.063659] (II) Loading extension GLX
[0.063668] (II) LoadModule: record
[0.063947] (II) Loading /usr/lib/xorg/modules/extensions//librecord.so
[0.064025] (II) Module record: vendor=X.Org Foundation
	compiled for 1.6.0, module version = 1.13.0
	Module class: X.Org Server Extension
	ABI class: X.Org Server Extension, version 2.0
[0.064052] (II) Loading extension RECORD
[0.064058] (II) LoadModule: dri
[0.064307] (II) Loading /usr/lib/xorg/modules/extensions//libdri.so
[0.065848] (II) Module dri: vendor=X.Org Foundation
	compiled for 1.6.0, module version = 1.0.0
	ABI class: X.Org Server Extension, 

RE: Jaunty -RT testing

2009-03-16 Thread Jim Miller
Hi Cory,

Please excuse me if I mess this up this posting (as I'm new to this
newsgroup).  I just wanted to add that the latest rt kernel (2.26.8.2)
does not seem to work very well on a Atom 330 based Intel board
(D945GCLF2).  While it boots and runs fine for a period of time, it
seems to just dies after about 10 mins of use.  And when I say die, I
mean nothing to do but power off.  The system does not seems to
respond to any keystrokes or mouse moves at that point.

I have tried the generic kernel and it does not seem to have this
problem.  Also, I have turned off compiz as suggested by others on
this group.

If you need me to test anything for you, let me know.  I would be
happy to help any way.

Thanks,
-Jim

-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Jaunty -RT testing

2009-03-15 Thread Gustin Johnson
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Joseph Reagle wrote:
 I need to use NaturallySpeaking in a virtualized Win2K environment which 
 requires real-time like performance. I run a KDE desktop.
 
Out of curiosity, what virtualization technology are you using?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkm9LGUACgkQwRXgH3rKGfNK6ACfZkZR9hMOxotFw0VdM2C/oqOS
4HIAn3XKRRNSOdl30VnaA+HEgn7YwrPp
=q7N+
-END PGP SIGNATURE-

-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Jaunty -RT testing

2009-03-15 Thread Luke Yelavich
On Sun, Mar 15, 2009 at 09:33:33AM EST, Joseph Reagle wrote:
 2. Can not recover from going to sleep with kpowersave or Kickoff Suspend2RAM.

I would suggest you do not rely on the rt kernel if you wish to suspend/resume. 
We barely have the resources to get an RT kernel available in the first place, 
let alone test suspend resume. In addition, so much in the rt kernel source 
changes to get realtime performance, that it is no surprise suspend/resume 
breaks.

Luke


signature.asc
Description: Digital signature
-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Jaunty -RT testing

2009-03-14 Thread Cory K.
As of now everything has hit the archive to use -RT. Please test on
whatever kind of system you have.

I currently have -RT running on 32/64bit w/nVidia and Intel GFX. Any
feedback is great, especially from ATI users.


-Cory K.

-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Jaunty -RT testing

2009-03-14 Thread sandie
Cory K. wrote:
 As of now everything has hit the archive to use -RT. Please test on
 whatever kind of system you have.

 I currently have -RT running on 32/64bit w/nVidia and Intel GFX. Any
 feedback is great, especially from ATI users.


 -Cory K.
   
I intend to test later today.

Is there any news of a propriotary ATI driver yet, or should I stick to 
the open-source ?

/Sandie

-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Jaunty -RT testing

2009-03-14 Thread Cory K.
sandie wrote:
 Cory K. wrote:
   
 As of now everything has hit the archive to use -RT. Please test on
 whatever kind of system you have.

 I currently have -RT running on 32/64bit w/nVidia and Intel GFX. Any
 feedback is great, especially from ATI users.

 
 I intend to test later today.

 Is there any news of a propriotary ATI driver yet, or should I stick to 
 the open-source ?

Sorry, I did mean to specify proprietary ATI drivers should be tested.
The necessary patches /should/ be there now to support -rt.


-Cory K.

-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Jaunty -RT testing

2009-03-14 Thread sandie
Cory K. wrote:
 As of now everything has hit the archive to use -RT. Please test on
 whatever kind of system you have.

 I currently have -RT running on 32/64bit w/nVidia and Intel GFX. Any
 feedback is great, especially from ATI users.


 -Cory K.

   
I have tested both Jaunty-desktop and Ubustu-9.04-Alpha6 on my pc :

Athlon 64 X2 5000+
ASUS M2N68
4 Gb Ram
Samsung 200 Gb HD
ATI Radeon HD 4830 512 MB PCIe

Jaunty didnt get very far, it complained about a Firmware bug... 
ACPI...Powernow k8 (sorry I dont have the complete message, it went 
past so quickly) and then gave me a ubu...@ubuntu:~$ and nothing else.

Ubuntustudio got a little further, I did see the same Firmware bug but 
all looked fine until the instalation was complete and I rebooted, then 
I got a grub error 2 (tried two times with same result).

btw. both where 32bit installs, (I never use 64bit because of problems 
with things like wine and java).

/Sandie

-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Jaunty -RT testing

2009-03-14 Thread Fabien Juchniewicz
Le Saturday 14 March 2009 13:57:59 Cory K., vous avez écrit :
 As of now everything has hit the archive to use -RT. Please test on
 whatever kind of system you have.

 I currently have -RT running on 32/64bit w/nVidia and Intel GFX. Any
 feedback is great, especially from ATI users.


 -Cory K.

Done some tests today on my PC.

Config : Intel Core2Duo 6600 / 4Gb / Nividia 7300 / M-audio delta 1010lt on 
kunbutu Jaunty 64 bits with the latest updates. Kernel = 2.6.28-2rt 64bits.

No freeze.

I achieve 0,667 ms with no xrun doing nothing (jackd realtime with P=89 and 
nice -n-19 before)

Done some tests at 5 ms playing some songs on Ardour. No freeze at all, no 
xrun.

But, I can't install nvidia drivers. Xorg never start. I use free drivers.

This kernel rocks.

/Fabien
-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Jaunty -RT testing

2009-03-14 Thread Asmo Koskinen

Intel Core2Duo 6400 / 2Gb /  Intel 965 / M-Audio Delta 66 / Ubuntu Alpha 
5 i386, all updates.

Linux ubuntu-studio 2.6.28-2-rt #6-Ubuntu SMP PREEMPT RT Tue Mar 10 
02:10:25 UTC 2009 i686 GNU/Linux

ps ax | grep jack
   ?S  0:00 /bin/sh /usr/bin/qjackctl
  4454 ?S  0:00 /usr/bin/pasuspender -- /usr/bin/qjackctl.bin
  4455 ?SLl0:06 /usr/bin/qjackctl.bin
  4463 ?SLsl   0:07 /usr/bin/jackd -R -dalsa -dhw:0 -r44100 
-p256 -n2 -Xraw

Works here now just fine.

Best Regards Asmo 'colon is not comma' Koskinen.

-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Jaunty -RT testing

2009-03-14 Thread Susan Cragin
I just downloaded the -RT kernel from the repository and tried to boot into it 
on my ASUS G1S. 
It did not boot up. 
It could be because I have compiled a sound driver against the generic kernel 
from the alsa-drivers testing repository. Oddly, I seem to remember it working 
a few days ago. 
Hmmm. Will check further. 
S



-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Jaunty -RT testing

2009-03-14 Thread Gustin Johnson
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

sandie wrote:
 Cory K. wrote:
 As of now everything has hit the archive to use -RT. Please test on
 whatever kind of system you have.

 I currently have -RT running on 32/64bit w/nVidia and Intel GFX. Any
 feedback is great, especially from ATI users.


 -Cory K.

   
 I have tested both Jaunty-desktop and Ubustu-9.04-Alpha6 on my pc :
 
 Athlon 64 X2 5000+
 ASUS M2N68
 4 Gb Ram
 Samsung 200 Gb HD
 ATI Radeon HD 4830 512 MB PCIe
 
With that video card you should be using the radeonhd driver, not the
fglrx one.

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

iEYEARECAAYFAkm8KKYACgkQwRXgH3rKGfO5agCfbLfm5HCW6FTCQJKJY7cy6eVf
m2oAn1z3GWJ/MfcYKvFpdVbuMmRHYRRO
=cz3/
-END PGP SIGNATURE-

-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Jaunty -RT testing

2009-03-11 Thread Eric Hedekar
On Tue, Mar 10, 2009 at 7:26 PM, Cory K. coryis...@ubuntu.com wrote:

 Cory K. wrote:
  Eric Hedekar wrote:
 
  snip
 
 
  Are you running Compiz?
 

 Nevermind. I see you are. /This/ could very well be the cause of your
 issues on -rt because of drivers. Which, we're still working on a couple
 of issues.

 I'd like to ask you to run the same tests with effects off. Also, how
 much RAM do you have?


 -Cory K.

 I turned Compiz off and have yet to see a freeze so far (just a short test
of audio) - that may have been the issue.
As noted previously (in my hardware specs) I have 2gig of ram.

-Eric

-- 
___
http://greyrockstudio.blogspot.com
-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Jaunty -RT testing

2009-03-11 Thread Chris Wenn
On Wed, Mar 11, 2009 at 5:49 PM, Eric Hedekar aftertheb...@gmail.comwrote:



 I turned Compiz off and have yet to see a freeze so far (just a short test
 of audio) - that may have been the issue.
 As noted previously (in my hardware specs) I have 2gig of ram.




This Compiz update does seem pretty flaky - I'm getting memory usage and CPU
spikes, and generally poor performance. I do wish the bling fanboys would
stop pressuring for the newest and fastest eye-candy - I had a nice system
that worked up until now :)

Chris
-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Jaunty -RT testing

2009-03-10 Thread Cory K.
Cory K. wrote:
 *This thread for feedback and issues for Jaunty's development -RT kernel*

 So the new -RT packages are starting to hit the Jaunty archive.
 Currently only AMD64 has hit.

 No LRM or linux-rt meta yet. We're waiting on the packages to be processed.

 So if you are running Jaunty-AMD64 and use free drivers: sudo apt-get
 install linux-image-2.6.28-1-rt should get you a working kernel. If you
 are one of those lucky few for now, please report any issues *aside*
 from what has already been mentioned in *this thread only*.

The lack of a response is a little disheartening. I do not believe no
news is good news. ;)

In any case, -RT has now hit for 386. Still no LRM yet but those on
Intel should be fine.

sudo apt-get install linux-image-2.6.28-2-rt

Please report any issues. Performance or otherwise. Especially those who
were saying that they were getting good results with -generic.


-Cory K.

-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Jaunty -RT testing

2009-03-10 Thread Eric Hedekar
On Tue, Mar 10, 2009 at 6:22 AM, Cory K. coryis...@ubuntu.com wrote:

 Cory K. wrote:
  *This thread for feedback and issues for Jaunty's development -RT kernel*
 
  So the new -RT packages are starting to hit the Jaunty archive.
  Currently only AMD64 has hit.
 
  No LRM or linux-rt meta yet. We're waiting on the packages to be
 processed.
 
  So if you are running Jaunty-AMD64 and use free drivers: sudo apt-get
  install linux-image-2.6.28-1-rt should get you a working kernel. If you
  are one of those lucky few for now, please report any issues *aside*
  from what has already been mentioned in *this thread only*.

 The lack of a response is a little disheartening. I do not believe no
 news is good news. ;)

 In any case, -RT has now hit for 386. Still no LRM yet but those on
 Intel should be fine.

 sudo apt-get install linux-image-2.6.28-2-rt

 Please report any issues. Performance or otherwise. Especially those who
 were saying that they were getting good results with -generic.


 -Cory K.



So after a morning of runing the i386 2.6.28-2-rt kernel I give it a totally
subjective rating of 'moderately unstable' and totally not release ready.
First, I think it's valid to mention my hardware specs and that all my
drivers did work.  I run a AMD Turion single core 1.4ghz (or so) processor,
2gig ram, ATI RadeonXPress200m video card (running open source drivers),
Broadcom 43xx wireless chipset, Presonus Firepod soundcard (running FFADO).
Desktop effects are turned on and running smoothly (less smoothly with the
rt kernel than vanilla, but still smooth)

I ran four 'real world' tests:

1. Basic use, left on overnight, continued basic use (included web browsing,
compiling some programs, running gdb, etc...).  No audio use.  This test
resulted in a catastrophic freeze after about three hours of basic use in
the morning.  I was browsing Youtube videos in Epiphany-browser at the time;
gedit had a few files open, and gdb was sitting idle with firefox at a
breakpoint.  First epiphany 'greyed out', then would not close, then the
keyboard became unresponsive and after waiting a bit, I killed everything by
holding down the power switch.  No particular action sparked this freeze
from what I could tell.

2. Strenuous use while running audio.  I started jack with realtime enabled,
44100, 256, verbose messages, then proceeded to try to make an XRun by
opening a detailed Ardour session (many files, automation, etc...), a rack
of effects, a PD patch that involved audio analysis, Hydrogen,
OpenOffice.org writer, and moving between things via gnome-do docky.  This
test continued for at least 10-15min probably more like 20 and I only
experienced one XRun, however eventually some programs became greyed out
(hydrogen was first, followed by Ardour and Qjackctl) and unresponsive.  I
tried killing (not just ending process, but killing) these processes via
gnome-system monitor but that just led to it being greyed out too.  Tried to
shut down via gnome menu but it did nothing (no shutdown/reboot/suspend
dialog) and not long after, the keyboard became non-responsive.  I waited,
then finally killed the computer via the power switch.

3. Prolonged dedicated recording session.  I setup a stereo pair of mics,
jackd -R, 44100, 256, an Ardour session with a single stereo track, start
Jamin (just to add a touch of processing weight) and put it in between the
mics and Ardour's capture, hit record and wend for a shopping trip.  Two and
a half hours later I came back to a fully recorded track, only 5 XRuns (one
@ 2min in, the other four in the last half-hour - the last was right at the
end, so barely counts).  This is a much lower XRun rate than I was getting
with vanilla kernel, so the rt did positively affect this test.  I thought
Okay, success!! so I quit Jamin, then moved to Ardour, pressed Ctrl+Q and
Ardour greyed out along with qjackctl.  I waited and waited, coiled some
cables, thinking well that's a big chunk of data to
close/deallocate/whatever  I'll give it some time, but no - it didn't need
any time.  A few minutes later I tried opening gnome-system monitor, a
terminal, and even epiphany, but all did not open.  I moved to a non-X
(tty3) login, tried sudo init 6 but it failed to turn off - chose to kill
the computer with the power switch.

4. Boot, open gnome-terminal, run uname -r, exit, shutdown.  This test went
off with no hickups, perfect success.

I'd be happy to dig up any logs that people would like to point me to (but
I'm very unfamiliar with the log system) - just direct me where.

-Eric Hedekar


-- 
___
http://greyrockstudio.blogspot.com
-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Jaunty -RT testing

2009-03-10 Thread Cory K.
Eric Hedekar wrote:
 snip

Really, it sucks, but everything you've posted I've also seen with
-generic. :( (minus the audio results)

Anything audio-related looked great from what you posted. Everything on
the outside could be another issue. Remember, Jaunty is still in great
flux. I got over 100 updates today. Are you running Compiz?

Actually, the best thing that came from your response is that it's
apparent that a comprehensive, user-followable, audio-specific testing
procedure needs to be developed.

I appreciate your email and will pour over it again to see if there's
anything I missed.


-Cory K.



-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Jaunty -RT testing

2009-03-10 Thread Eric Hedekar
On Tue, Mar 10, 2009 at 7:22 PM, Cory K. coryis...@ubuntu.com wrote:

 Eric Hedekar wrote:
  snip

 Really, it sucks, but everything you've posted I've also seen with
 -generic. :( (minus the audio results)
 snip
  -Cory K.


I should add that I have not experienced a single freeze with the
vanilla/generic since installing a month ago.  I was also able to run jackd
in realtime (but have not done much comprehensive testing) with generic
though with more frequent XRuns.  The freezing on this machine has been
limited to the rt kernel.  This might possibly be explained that the generic
I run is 2.6.28-8 whereas the rt is 2.6.28-2 (as is the case with most
jaunty users).

-Eric

-- 
___
http://greyrockstudio.blogspot.com
-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Jaunty -RT testing

2009-03-10 Thread Eric Hedekar
On Tue, Mar 10, 2009 at 8:18 PM, Eric Hedekar aftertheb...@gmail.comwrote:



 On Tue, Mar 10, 2009 at 7:22 PM, Cory K. coryis...@ubuntu.com wrote:

 Eric Hedekar wrote:
  snip

 Really, it sucks, but everything you've posted I've also seen with
 -generic. :( (minus the audio results)
 snip
  -Cory K.


 I should add that I have not experienced a single freeze with the
 vanilla/generic since installing a month ago.  I was also able to run jackd
 in realtime (but have not done much comprehensive testing) with generic
 though with more frequent XRuns.  The freezing on this machine has been
 limited to the rt kernel.  This might possibly be explained that the generic
 I run is 2.6.28-8 whereas the rt is 2.6.28-2 (as is the case with most
 jaunty users).

 -Eric

I feel I should clarify that I have had programs freeze up in Jaunty with
generic, but not the whole system.  They've always been freezes that have
been recoverable by a simple force quit.

-Eric


-- 
___
http://greyrockstudio.blogspot.com
-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Jaunty -RT testing

2009-03-10 Thread Cory K.
Cory K. wrote:
 Eric Hedekar wrote:
   
 snip
 

 Are you running Compiz?
   

Nevermind. I see you are. /This/ could very well be the cause of your
issues on -rt because of drivers. Which, we're still working on a couple
of issues.

I'd like to ask you to run the same tests with effects off. Also, how
much RAM do you have?


-Cory K.


-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Jaunty -RT testing

2009-03-08 Thread Cory K.
*This thread for feedback and issues for Jaunty's development -RT kernel*

So the new -RT packages are starting to hit the Jaunty archive.
Currently only AMD64 has hit.

No LRM or linux-rt meta yet. We're waiting on the packages to be processed.

So if you are running Jaunty-AMD64 and use free drivers: sudo apt-get
install linux-image-2.6.28-1-rt should get you a working kernel. If you
are one of those lucky few for now, please report any issues *aside*
from what has already been mentioned in *this thread only*.


-Cory K.

-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Jaunty RT

2009-01-26 Thread Cory K.
Cory K. wrote:
 Gustin Johnson wrote:
   
 I have RT in 8.10.  All that it required was building my own kernel (a
 2.6.28)
 

 I'm assuming you have SMP support broken or disabled?

I'm still looking for a response on this. ATM the test builds have this
broken. So only 1 CPU is supported. Also, the kernel just isn't plain
booting. So Alessio is stuck waiting for some things to clear up.


-Cory K.


-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Jaunty RT

2009-01-21 Thread alex stone
We had this discussion a while ago about the lack of rt kernel in Intrepid.
There were varying views, but a very general consensus seemd to reach a
conclusion of If it ain't broke... Sticking with Hardy, as tempting as new
packages may seem, was a shared view among a decent percentage of views. But
we had plenty of warning, and a decent explanation on why. Cory also
expressed a real view of the state at the time, and didn't try to lead us
into uncertain territory with any speculation

It's my guess here that the changes in the vanilla kernel that resulted in
questionable midi performance are ongoing, and it's quite likely the
UBStudio team are as much in the dark as we are on the current state of the
vanilla kernel, and when it's likely to settle into an RT capable and
useable state. (not to mention the required standards for building in the
ubuntu environment)

Taking a step back here, and trying to view the wider picture, we already
have a highly useable distro version in Hardy, and if you're inclined, in
Gutsy (Which proved to highly stable a worked a treat.. We know the state of
Intrepid, and why, and also understand that Jaunty may also offer challenges
as well, with all of us waiting for news on the vanilla kernel state.

Cory also explained that the jump in Ubuntu RT preparation between Hardy
(2.6.24.xxx) and a 'new' RT kernel would be a lot more work than usual due
to new features, and rebuilding added to any new kernel (I don't pretend to
understand what they are, or why it's so different, i'm taking Cory's words
here, and he's been honest with us in the past), and would occupy a
formidable amount of time for the Ubuntu RT kernel dev, who does this for
us, for free, as in decent cognac. (or beer, if that's your particular
imbibable refreshment)

I'm as keen as anyone else to enjoy the new features being added to the apps
i use as much as any of you, and have enjoyed testing them in anticipation
of a future UBStudio that returns to an RT configuration we know, and enjoy
using.

But i'm ever mindful, and appreciative, of the considerable work that goes
into a project like UBStudio, from fellow human beings who apply their
considerable skills for OUR benefit.

Yes, i use linux for a living, and no, staying on a highly stable Hardy,
with some source packages i've ventured to install, hasn't hurt me at all.
Quite the contrary, i've increased my pitifully poor knowledge of all things
linux, in general. (To slightly less pitiful)

Can i 'respectfully' suggest (A clumsy attempt at diplomacy here...), in the
interim period between Ubuntu RT kernel nirvanas, that others might like to
take advantage of this lull in the breakneck development whirlwind that is
the ever mighty Linux Audio world and use the time writing music instead?
:)

2 roubles worth from a ordinary linux audio user who knows he can't code,
and is reliant on the continued good will, superb craftsmanship, endless
patience, and unfailing generosity of others to realise musical ambitions.


Alex the linux crash test dummy Stone.






On Wed, Jan 21, 2009 at 7:14 PM, sue...@empire.net sue...@empire.netwrote:

 
 Original Message:
 -
 From: Gustin Johnson gus...@echostar.ca
 Date: Wed, 21 Jan 2009 08:18:55 -0700
 To: ubuntu-studio-users@lists.ubuntu.com
 Subject: Re: Jaunty RT
 
 
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Christopher Stamper wrote:
 
 
  On Tue, Jan 20, 2009 at 5:37 PM, Gustin Johnson gus...@echostar.ca
  mailto:gus...@echostar.ca wrote:
 
  
   So, looking forward: will we be able to switch to 9.04? In other
  words,
   will 9.04 have RT support, or will we still be stuck with 8.04?
  
  I have RT in 8.10.  All that it required was building my own kernel
 (a
  2.6.28), so you are not stuck with 8.04 right now if you do not
 want
  to be.
 
 
  People who don't want to bother compiling a kernel are 'stuck'; anyway,
  it's easier to stay with 8.04.
 
 You mean to say that people who *choose* not to investigate their
 options are stuck.  You are only stuck if you want to be.


 stuck could mean many things.

 Building this and building that is rarely without time
 consuming issues. UX's have always been like uncle on the
 Jackie Chan cartoon: ...ah...one more thing

 If the goal of having Ubuntu Studio is to use it as a tool
 to do billable work, then staying with a known working tool
 rather than exploring options, and choosing to be stuck is the
 prudent business decision.



 
 mail2web.com - Microsoft(R) Exchange solutions from a leading provider -
 http://link.mail2web.com/Business/Exchange



 --
 Ubuntu-Studio-users mailing list
 Ubuntu-Studio-users@lists.ubuntu.com
 Modify settings or unsubscribe at:
 https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users

-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com

Re: Jaunty RT

2009-01-21 Thread Susan Cragin
 On Tue, Jan 20, 2009 at 5:37 PM, Gustin Johnson gus...@echostar.ca
 mailto:gus...@echostar.ca wrote:
 
 
  So, looking forward: will we be able to switch to 9.04? In other
 words,
  will 9.04 have RT support, or will we still be stuck with 8.04?
 
 I have RT in 8.10.  All that it required was building my own kernel
(a
 2.6.28), so you are not stuck with 8.04 right now if you do not
want
 to be.
 
 
 People who don't want to bother compiling a kernel are 'stuck'; anyway,
 it's easier to stay with 8.04.
 
You mean to say that people who *choose* not to investigate their
options are stuck.  You are only stuck if you want to be.


stuck could mean many things.

Building this and building that is rarely without time 
consuming issues. UX's have always been like uncle on the 
Jackie Chan cartoon: ...ah...one more thing

If the goal of having Ubuntu Studio is to use it as a tool 
to do billable work, then staying with a known working tool 
rather than exploring options, and choosing to be stuck is the
prudent business decision.

I think part of it may be that they are waiting for the next kernel (2.6.29) 
because it may contain support for btrfs. Just a guess. Btrfs is supposed to 
seek faster anyway, than ext3, or whatever we've got. 



-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Jaunty RT

2009-01-21 Thread Christopher Stamper
On Wed, Jan 21, 2009 at 11:49 AM, alex stone compos...@gmail.com wrote:

 We had this discussion a while ago about the lack of rt kernel in Intrepid.
 There were varying views, but a very general consensus seemd to reach a
 conclusion of If it ain't broke... Sticking with Hardy, as tempting as new
 packages may seem, was a shared view among a decent percentage of views. But
 we had plenty of warning, and a decent explanation on why. Cory also
 expressed a real view of the state at the time, and didn't try to lead us
 into uncertain territory with any speculation

 Taking a step back here, and trying to view the wider picture, we already
 have a highly useable distro version in Hardy, and if you're inclined, in
 Gutsy


I totally agree with you. But still, there will come a point when Hardy is
just 'too old' to use (you have the right to disagree). Which is why I was
wondering when we'll be able to upgrade.

[I know that I could upgrade now if i wanted to compile a kernel, and spend
a month debugging it]




 (Which proved to highly stable a worked a treat.. We know the state of
 Intrepid, and why, and also understand that Jaunty may also offer challenges
 as well, with all of us waiting for news on the vanilla kernel state.

 Cory also explained that the jump in Ubuntu RT preparation between Hardy
 (2.6.24.xxx) and a 'new' RT kernel would be a lot more work than usual due
 to new features, and rebuilding added to any new kernel (I don't pretend to
 understand what they are, or why it's so different, i'm taking Cory's words
 here, and he's been honest with us in the past), and would occupy a
 formidable amount of time for the Ubuntu RT kernel dev, who does this for
 us, for free, as in decent cognac. (or beer, if that's your particular
 imbibable refreshment)

 I'm as keen as anyone else to enjoy the new features being added to the
 apps i use as much as any of you, and have enjoyed testing them in
 anticipation of a future UBStudio that returns to an RT configuration we
 know, and enjoy using.

 But i'm ever mindful, and appreciative, of the considerable work that goes
 into a project like UBStudio, from fellow human beings who apply their
 considerable skills for OUR benefit.


Agreed. Many thanks to all the UStudio Team!


-- 
Christopher Stamper

Email: christopherstam...@gmail.com
Web: http://tinyurl.com/2ooncg
gTalk: http://tinyurl.com/6e359r
Skype: cdstamper
-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Jaunty RT

2009-01-21 Thread Gustin Johnson
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Christopher Stamper wrote:
snip
 
 The original question was: will 9.04 have a RT kernel?
 
 I did some googling, but couldn't find any solid answer.
 
Probably because there is no certain answer as yet.  Having said that,
since I was able to get RT support myself (ie. there was no special
magic or skillset involved) in Intrepid, I would say the chances are
good that 9.04 will have an RT kernel.

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

iEYEARECAAYFAkl3a1UACgkQwRXgH3rKGfMbKgCfSwwycshcI911txfXluFFBcms
uQwAniRImKpdo+eo01X18dT1Y6SX/lR2
=mqsf
-END PGP SIGNATURE-

-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Jaunty RT

2009-01-21 Thread Christopher Stamper
On Wed, Jan 21, 2009 at 1:37 PM, Gustin Johnson gus...@echostar.ca wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Christopher Stamper wrote:
 snip
 
  The original question was: will 9.04 have a RT kernel?
 
  I did some googling, but couldn't find any solid answer.
 
 Probably because there is no certain answer as yet.  Having said that,
 since I was able to get RT support myself (ie. there was no special
 magic or skillset involved) in Intrepid, I would say the chances are
 good that 9.04 will have an RT kernel.


Sounds reasonable enough.

Thanks!


-- 
Christopher Stamper

Email: christopherstam...@gmail.com
Web: http://tinyurl.com/2ooncg
gTalk: http://tinyurl.com/6e359r
Skype: cdstamper
-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users


Re: Jaunty RT

2009-01-20 Thread Christopher Stamper
On Tue, Jan 20, 2009 at 5:37 PM, Gustin Johnson gus...@echostar.ca wrote:

 
  So, looking forward: will we be able to switch to 9.04? In other words,
  will 9.04 have RT support, or will we still be stuck with 8.04?
 
 I have RT in 8.10.  All that it required was building my own kernel (a
 2.6.28), so you are not stuck with 8.04 right now if you do not want
 to be.


People who don't want to bother compiling a kernel are 'stuck'; anyway, it's
easier to stay with 8.04.

-- 
Christopher Stamper

Email: christopherstam...@gmail.com
Web: http://tinyurl.com/2ooncg
gTalk: http://tinyurl.com/6e359r
Skype: cdstamper
-- 
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users