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
Re: [usersUbuntuStudio] Jack lags...
So, a somewhat conclusive update. I have now gotten it to work properly, it had to do with the audio buffert and the IRQ-priority for my soundcard, both of which I'd tested, figures the problem :), had to put the buffert somewhere between 512 and 1024 and on top of that increase priority to my soundcard to 80-something, anyways, now it works. I'm looking forward to a long lasting and productive relationship with US, currently I'm using Renoise for the most, backed up by Ardour and Hydrogen. Cheers. //Paco On Sat, Mar 7, 2009 at 2:05 PM, Robert Klaar wrote: > Update, so after a nights configuring I think I know wherein the problem > lies. :), I added Jack to the tray and now, when I start it, it gets > completely red. I checked this up and supposedly it has to do with xruns(?). > I also noticed that it helps changing the frames/period setting, but only to > a degree(even at highest it's no good). I see now that this is not strange > at all since it's the xruns that are causing it to slow down in the first > place... Now all I have to figure out is why the xruns are being sent. Also > I noticed something when starting alsamixer, I only have the masterbar. > //paco > > > On Fri, Mar 6, 2009 at 10:21 PM, Robert Klaar wrote: > >> Hi there again! >> Been configuring audio now for the most of my friday-evening, everything >> works fine except it doesn't :(. Pulseaudio works, mediaplayers routing to >> pulseaudio too, but things like Ardour, Hydrogen, everything Jack-based >> doesn't. It lags when I try to use any samples and everything that's not >> working can in one way or another be related to Jack. When I started up a >> new project in Ardour, a notice came up stating that I had locked my memory >> or something, I looked up how to unlock this and now the notice is gone but >> nothing has changed with how it sounds, allthought it seemed reasonable(I'm >> sitting on a dual core 2.3 ghz with a ram of 3 g so I find it hard to think >> anything's wrong with the hardware per sey), I also checked with system >> monitor and it is hardly working it would seem when running jack. Also Jack >> shows, in the Jack-ctrl window something like 1(249), "249 is increasing", >> don't know if this is normal or not since I'm new to the whole thing. Anyone >> care to take a guess?... so that I might go out and get oen or two beers at >> least this friday evening :)... >> //paco >> > > -- 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
