Re: Re: Re: Jaunty RT testing
On Apr 20, 2009 7:03am, wayne wrote: 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. Well, I went to test some of these fixes out, and a surprising thing happened. I attempted to push JACK way beyond any reasonable limit in order to cause it to crash. But, instead of crashing, it simply. . .stopped, and allowed me to try different settings until something worked. That's actually very nice, and it eliminates the need to kill JACK in any other manner. Something must've changed in the last few days to cause this. I'll keep testing over the next few days to see if this behavior maintains. If this is the way JACK is going to act from here on out, then I have to say I'm rather pleased. Good job! -- 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
On Sun, 2009-04-19 at 21:30 +, beej...@gmail.com wrote: > On Apr 19, 2009 2:00pm, wayne 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: Re: Jaunty RT testing
On Apr 19, 2009 2:00pm, wayne 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 -- 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
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 wrote: > > 2009/4/19 wayne > > On Mon, 2009-04-13 at 22:37 -0500, Brian David wrote: > > On Mon, Apr 13, 2009 at 1:49 PM, Cory K. wrote: > > beej...@gmail.com wrote: >> On Apr 13, 2009 1:07pm, "Cory K." 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 testing
> 2009/4/19 wayne > > > On Mon, 2009-04-13 at 22:37 -0500, Brian David wrote: > > > On Mon, Apr 13, 2009 at 1:49 PM, Cory K. > > wrote: > > > > beej...@gmail.com wrote: > > > On Apr 13, 2009 1:07pm, "Cory K." > > 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
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 2009/4/19 wayne > On Mon, 2009-04-13 at 22:37 -0500, Brian David wrote: > > On Mon, Apr 13, 2009 at 1:49 PM, Cory K. wrote: > > beej...@gmail.com wrote: > > On Apr 13, 2009 1:07pm, "Cory K." 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 > > -- 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
On Mon, 2009-04-13 at 22:37 -0500, Brian David wrote: > On Mon, Apr 13, 2009 at 1:49 PM, Cory K. wrote: > > beej...@gmail.com wrote: > > On Apr 13, 2009 1:07pm, "Cory K." > 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
Re: Jaunty RT testing
On Mon, Apr 13, 2009 at 1:49 PM, Cory K. wrote: > beej...@gmail.com wrote: > > On Apr 13, 2009 1:07pm, "Cory K." 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. -- -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
beej...@gmail.com wrote: > On Apr 13, 2009 1:07pm, "Cory K." 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
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
On Thu, Apr 2, 2009 at 5:33 PM, Brian David 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
On Thu, Apr 2, 2009 at 5:33 PM, Brian David 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
Re: Jaunty -RT testing
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
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=15&t=15525&sid=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
>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
Re: Jaunty -RT testing
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
Re: Jaunty -RT testing
Joseph Reagle wrote: > I need to use NaturallySpeaking in a virtualized Win2K environment which > requires real-time like performance. I run a KDE desktop. I know this is going off topic a bit but I'm going to throw my two cents worth and then bow out unless there is further interest in discussing this topic. I'm in the same position. I run Ubuntu 8.04 as my host and XP as my guest. virtualization software is VM Ware. AFAIK, Speech recognition needs very clean audio without any dropouts in order to function properly. One of the most consistent ways of getting clean audio is through USB. It eliminates most if not all of the audio flakiness, bugs, inconsistency, internal noise etc. it's a cheaper solution than what you can get with a sound card. Functional, reliable, cheap what more can you ask for when it comes to USB audio? How about a good set of linux drivers? when I tried to use wine to run NaturallySpeaking, I discovered that 8.04 didn't even recognize my USB microphone(vxi b200). Then I remembered the last time I tried USB audio with OSS, it didn't really work very well and it prevented me from using the built-in soundcard at the same time. Fortunately, VM Ware proxies the USB audio device into the guest so that NaturallySpeaking can attach to it. Since my goal was to have working speech recognition without counting on Windows as a host OS, I stuck with VM Ware (i.e. functionality trumps politics). unfortunately, this virtual system solution isn't sufficient and naturally speaking plus wine works better everyday. Someday, I (and other crypts like myself) will need speech recognition quality audio from USB devices and it would be nice if a no hassle solution was available. Believe me, even though I can use my hands to do cryptic stuff, I would rather save them for more important tasks related to work or having a life. Seriously, it sucks having to decide how you're going to use your hands instead of just using them. -- 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
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Joseph Reagle wrote: > 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.) > I am an ongoing VMWare customer (Workstation 6.5.1 currently) so I am more than familiar with the any-any patches. I do not do realtime work inside a guest but I do use the same kernel for audio and vmware. The latest workstation build did not require an any-any patch so I am pretty happy there. > Once Jaunty is released and if -rt isn't satisfactory (e.g., suspend) I have been running Linux on Laptops for nearly 10 years. I let go of suspend a long time ago. With -rt patches, video binary blobs, ndiswrapper, etc. I just don't bother. I just got the new laptop Friday, so we shall see how this goes as there should not be the need for binary blobs (chipset, wifi, video are all Intel and thus all upstream). > 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. I have a custom 2.6.28, the one difference I see is that I have HZ=1000. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkm+PckACgkQwRXgH3rKGfPmawCgnMLPt//ZyCfHsgl4p1EeTMI8 EUcAoJSK14pZpBm/qQYGuBd6J0BDJ2qq =sq+h -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
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
>> 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. > >How does it not boot up? Do you get a kernel panic, are you dropped to the >initramfs/busybox prompt? Does GDM/X not load? > >With a bit more information, we may be able to help you work out the problem >you are having. > >Luke Here's what happens. When I turn my computer on, it goes to the "UbuntuStudio" screen, lights up "Ub" and then freezes. If I go to "Recovery Mode" and then hit "Resume Normal Boot" I can log on. However, bad things happen when I try to run the only audio program I run, which is Dragon NaturallySpeaking 10, running in wine. I start up DNS. It lets me adjust the volume, and then I try to run it and everything freezes. So I push the button to re-boot. When I come back in (again through Recovery mode) it informs me that DNS is not completely installed, because it is missing a DLL. When I boot back into my regular kernel, DNS still is missing the DLL, and I have to re-install the program. I have an Xorg.0.log I can send you. Don't know if this listserve takes attachments, most of them don't. Susan -- 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
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
On Sun, Mar 15, 2009 at 08:49:58AM EST, Susan Cragin wrote: > 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. How does it not boot up? Do you get a kernel panic, are you dropped to the initramfs/busybox prompt? Does GDM/X not load? With a bit more information, we may be able to help you work out the problem you are having. 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
-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
Gustin Johnson wrote: > -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. > Yes, but it's hard to set when it wont even boot my disk ;-) btw. I have been using radeonh on Hardy and Ipex, and I just wanted to test if the propriotary driver from ATI worked. I only have one pc, so I use it for playing games also (too lazy to dualboot) and the radeonhd dosnt play well with 3d (at least not the one I tried). /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
-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
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
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
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
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
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
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
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
On Tue, Mar 10, 2009 at 11:49 PM, Eric Hedekar wrote: > On Tue, Mar 10, 2009 at 7:26 PM, Cory K. wrote: > >> Cory K. wrote: >> > Eric Hedekar wrote: >> > >> >> > 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 > I'd like to give a quick update on my experience with 2.6.28-2-rt. I have yet to be able to sucsessfully "log out" of my gnome session without a freeze. I haven't tried many times, because freezes are annoying - but as of last check, it's an issue. I also have found both jaunty generic and jaunty rt to be more stable for audio than intrepid's rt kernel. I'm glad to have read somewhere[1] that upstream development has caught some time from both Thomas Gleixner and Ingo Molnar. [1.] http://lwn.net/Articles/319544/ -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
On Wed, Mar 11, 2009 at 5:49 PM, Eric Hedekar wrote: > > >> 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
On Tue, Mar 10, 2009 at 1:22 PM, Cory K. 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. > We all know you guys wanted this and are starting to use it. Just let us know (specially if the results are good). We need some love :P after all, feedback is all we get from you folks. I'm testing it with good results, but won't be happy until we have proper testing feedback. Luis -- 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
On Tue, Mar 10, 2009 at 7:26 PM, Cory K. wrote: > Cory K. wrote: > > Eric Hedekar wrote: > > > >> > >> > > > > 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
Cory K. wrote: > Eric Hedekar wrote: > >> >> > > 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
Re: Jaunty -RT testing
On Tue, Mar 10, 2009 at 8:18 PM, Eric Hedekar wrote: > > > On Tue, Mar 10, 2009 at 7:22 PM, Cory K. wrote: > >> Eric Hedekar wrote: >> > >> >> Really, it sucks, but everything you've posted I've also seen with >> -generic. :( (minus the audio results) >> >> -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
On Tue, Mar 10, 2009 at 7:22 PM, Cory K. wrote: > Eric Hedekar wrote: > > > > Really, it sucks, but everything you've posted I've also seen with > -generic. :( (minus the audio results) > > -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
Eric Hedekar wrote: > 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
On Tue, Mar 10, 2009 at 6:22 AM, Cory K. 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
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
