Kernel Testers Needed

Actually the problem I'm having is running it. Does anyone have an idea for a fix. I think every time I try and install one part or another says "failed to install". I don't know what that means, but I'd like to be able use 64 studio. Thanks for any help in advance. ^_^

Hi James, You are doing good work, and I follow your development with great interest. Last kernel config\build here was *2.6.29.3-rt13.090517*. My time here has been spent comparing the various distros kernel configurations including Sidux, avlinux2r1, ubuntustudio, Musix, Quentin's, 64studio 2.6.21, 2.6.26, 2.6.29-beta3 and others found on the linux-audio-lists etc., The conclusion I've come to at this point in time is that there isn't a common configuration base between any of the audio disrtibutions kernels-rt. They all do the Preempt-rt and that's as far as *common* settings go. Methods of comparison: 64studio 3.0 beta3 Today sees an upgrade available for 64studio 3.0 beta3 kernel. $ dpkg -l |grep 2.6.29 ii linux-image-2.6.29-1-multimedia-686 2.6.29-2 $ cp /boot/config-2.6.29-1-multimedia-686 ~/config-2629-1-mm-686-2 After the kernel upgrade we have: $ dpkg -l |grep 2.6.29 ii linux-image-2.6.29-1-multimedia-686 2.6.29-9 $ cp /boot/config-2.6.29-1-multimedia-686 ~/config-2629-1-mm-686-9 We now have two .configs for comparison: config-2629-1-mm-686-2 & config-2629-1-mm-686-9 1) ediff-files: Emacs users, highlights diffs and informs how many diffs there are = 94diffs 2) $ sdiff --suppress-common-lines config-2629-1-mm-686-2 config-2629-1-mm-686-9 > sdiff-2629-2-2629-9-94diffs Compares the two configs and creates a file *sdiff-2629-2-2629-9-94diffs* 3) $ diff -uN config-2629-1-mm-686-2 config-2629-1-mm-686-9 > config-diff-2629-2-2629-9 Compares the two configs and creates a file *config-diff-2629-2-2629-9* Then run: $ grep -v "^ " config-diff-2629-2-2629-9 | grep -v @@ | grep -v '\\-\\-\\-' | grep -v '+++' | grep -v '\\#' > config-diff-2629-2-2629-9-grep Creates the file *config-diff-2629-2-2629-9-grep* All three diffs methods have there own qualities and result in text files that can be viewed at a later date. The basic code = $ diff .config1 .config2 (using: *> creates-file*) Another method I'm liking is to have Two computers side by side and use $ make menuconfig $ make xconfig $ make gconfig Then browse the variations on both PC's and read the help files in the menu browser. READ: /linux-source/Documentation/kernel-parameters.txt Slow work, best done in sessions and with constant note taking. If your interested in kernel development today is a fine opportunity to view the recent changes to the 64studio 3.0beta3 kernel. Use one or all of the above methods to compare the recent changes. These backup .configs are a great starting place for you to configure\build your own custom kernel starting from make oldconfig. Cheers! Dave.

Hi Dave, I am anxiously awaiting the rc on 64Studio in hopes it will fix/work on my new system. In the meantime, I am trying an rt-kernel for Sidux with this link. Have you tried this one? http://sidux.com/index.php?module=pnWikka&tag=englishAudiostudio Wish me luck, James

Hi James, Good to hear you're making music and learning how to use your software:) Keep notes on configuration settings etc., They will come in useful later. No problem with staying away from testing, you took the time to report the issues and that's great. James> As to beta3,..... [.....] I've mailed your concerns upstream and am waiting for a responce, I'll get back to you on this one. I installed ubuntustudio and posted my report so you could see how things work for one install and fail on another. You have to find the best option for your system and use the information to compare the processes. Again, confirmation of the need to sometimes distrohop. Enjoy your new computer:) Cheers! Dave.

Again sorry about the delay in responding. My second computer decided to roll over and play dead. It's the one I compile the kernels on. It turned out to be the PSU was broken. I've fitted another and I'm all up and running again. Cheers! Dave.

Hi Dave, I have my new system screaming under UbuntuStudio 9.04 using Ardour 2.8 and Rosegarden. (slowly learning how to use these two programs). I am getting 1.5ms latency under ardour and jack with a 12% cpu use. I have so much to learn though the process is slow. We will see how this changes as I add more tracks. I am presently staying away from a lot of testing because I need to learn how to use the software to actually make some music. I have quite a lot in the works right now. As to beta3, I still cannot get anything to work and have left it alone for the time being. I intend to go back to the vesa driver but am not sure that is it because I get no video at all not even bad video. I must be doing something wrong but cannot think of it. It looks like a lot of things have developed recently though and any suggestions you might have are certainly intriguing to me. My experience with ubuntustudio and nvidia drivers was (interestingly) directly opposite of yours. It went in with no problem and all seems to work. I have the Geforce 8200 chipset which seems to a problem under 64Studio. Could it be because 64Studio is built on top of Ubuntu 8.04? Thanks, I will monkey around with more later this week. James

When source is installed via apt-get it merely installs the archive into /usr/src

You need to unzip it..

$ cd /usr/src
$ sudo bzip2 -d linux-source-2.6.29.2*.tar.bz2
$ sudo tar xvf linux-source-2.6.29.2*.tar

and then you create a symlink

$ sudo ln -s linux-source-2.6.29.2-rt11.2b3.2.090508 linux

Now you can try again.

Cheers,
Quentin

Hi James, Sorry it took so long to get back to you, how are you doing? Did you manage to get beta3 booted with the vesa driver? Spent this weekend getting ubuntustudio 9.04 to use my nVidia card. I ended up having to build a kernel myself, it was the only way I could get the nvidia binary driver installed. It's the first time I've had to do this. Ubuntustudio is normally straightforward here. This kernel build method should have been the same as the one I've been using for 64studio, but alas, not quite. This is why it's not easy to write a howto, because you have to figure out issues as you proceed. Quentin kindly replaced the kernel, headers & source I uploaded to his repository for a newer build I've done, again compiled with the stable firewire stack. The idea was that users could use these temporary kernel packages to let them compile packages and install binary drivers. However when apt-get is used to install kernel, headers & source the binary drivers still wont install? which is strange because when I build the packages everything compiles and installs fine. So I need to look more into what's going on here. I hope you're making progress with your new computer:) Cheers! Dave.

Hi, I got stuck with the boot up to the rt-kernel. It kept saying it was ext2 rather than ext3 which I knew it was. Thus, I believe I configured the rt kernel incorrectly but don't know how to remedy that. I recall not really knowing at all what I was to do with the configure process and probably made a few errors or had a few oversights. As it was I tried a few other things and really mucked it up to the point where I had no idea so I reinstalled. I tried uninstalling the existing rt-kernel, etc. Mind you this is all on Sidux. I still cannot get 64Beta 3 to display video on my system. It installs just fine, I can see my Mona soundcard light up on boot, I see the menu options but when it finishes loading it just goes black. I have tried to fix xserver, I have tried editing the xorg.conf file from the root shell, I have tried to install the binary from root shell with no luck. It is very odd, I tried several variations of the xorg.conf file, tried several variations on the cheat codes employed by Sidux to get it to work. It is odd because, Sidux and UbuntuStudio 9.04 install and display without any issues. On each, I can install the binary nVidia driver easily. It is truly a mystery to me. So, at this point, I am working with Sidux and Ubuntu but want to get to 64 again. Thanks, James

Hi James, I'm on with a howto now but because I'm trying new methods all the time I'm constantly changing it. I've tried quite a few methods of building the packages this week but the first method is the one I've gone back to. I'll post the howto as soon as I get a basic method I'm happy with. Where exactly are you having problems, and what method are you using? I got the impression you were really close on your other post. If you post back how you're working we might be able to see your next step. Cheers! Dave.

Hi Dave, I am wondering if you could put together a short how-to on building a kernel? I am close but feel I am missing something because it is not working. It is interesting that you mention the vga problem because that is the setting Sidux uses on its install disc and works whereas if I add it to the Beta3 it does not. Thanks, James

$ uname -r 2.6.29.2-rt11.2b3.090503 Configured (with stable firewire) nVidia binary installed. On with audio performance testing. Cheers! Dave. **Update:** 090507: 2.6.29-1-multimedia-686 upgrade. The kernel upgrade bug is fixed. We now have an upgradable kernel :) The kernel is now based on rt-11 and is configured with (stable firewire). $ cp /boot/config-2.6.29-1-multimedia-686 ~/config-2629-1-mm-686beta3-8 There are 94 diffs between the 3.0beta3 default kernel and the new kernel. Dave sdiff-2629-2-2629-8 (94 diffs) I've tested the upgrade on a couple of different PC's here and all went smoothly. On with testing audio performance. https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/54346

$ uname -r 2.6.29.2-rt11.090503 Built 2.6.29.2-rt11.090503 using rt-11-config-Q Build went smooth and nVidia installed fine. On with more tests. Cheers! Dave. Revision: Check Entry: $ sudo gedit /etc/sysctl.conf kernel.sched_rt_runtime_us = -1

Enjoyed playing around yesterday. It's back to the realtime kernel today. Today I'm using Quentin's .config (which is working well here) with the new 2.6.29.2-rt11 patch. Build is running now. Update: $ uname -r 2.6.29.2-rt11 Cheers! Dave.

Today I decided to try & build\install Linus Torvalds latest kernel. You don't have to build\install the kernel, you can download and browse the source without installing it. You need git installed to pull the source. Be warned, it's a big download. $ sudo apt-get update $ sudo apt-get install git-core gitk git-doc build-essential $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git $ cd linux-2.6/ READ the Documentation & README files. $ make menuconfig This will allow you to browse through the config options. If space is an issue delete linux-2.6/ directory once you're done. I decided to go for a build\install for Desktop use. The linux-2.6.30-rc4.deb is 300MB when built. The install went ok. $ uname -r 2.6.30-rc4 A smaller download would be the latest released source, unpack it and browse it in the same manner. linux-2.6.29.tar.bz2 23-Mar-2009 23:27 54M $ tar xfvj linux-2.6.29.tar.bz2 $ cd linux-2.6.29/ READ the Documentation & README files. $ make menuconfig If you want to build with realtime preempt you have to patch the source before building! See: How to get a git repository Cheers! Dave.

Installed nVidia binary driver on 2.6.29.2-rt10 $ dpkg -l |grep 2.6.29.2-rt10 ii linux-headers-2.6.29.2-rt10 ii linux-image-2.6.29.2-rt10 ii linux-source-2.6.29.2-rt10 $ apt-cache policy linux-kbuild-2.6.29 linux-kbuild-2.6.29: Installed: (none) Candidate: 2.6.29-1~hardy1 Version table: 2.6.29-1~hardy1 0 500 http://apt.64studio.com hardy-backports/main Packages So linux-kbuild-2.6.29 is available again, but not installed. nVidia installed without any problems. $ cat /proc/driver/nvidia/agp/status Status: Enabled Driver: NVIDIA AGP Rate: 4x Fast Writes: Enabled SBA: Enabled Cheers! Dave.

Things are moving along at quite a pace now. Yesterday I installed Quentin's kernel and for any testers who haven't installed and tried it yet, you should do so. There's a lot of work gone into building the kernel and your feedback will help Quentin to carry on his work, *for us*. Test kernel for amd64 (with stable firewire) /kernel/linux-2.6.29-rt8 /kernel/linux-2.6.29.1-rt9/ From the links in post: *Real-Time Linux* I'm now also running: /kernel/linux-2.6.29.2-rt10/ $ uname -r 2.6.29.2-rt10 Built today with these: linux-2.6.29.2.tar.bz2 patch-2.6.29.2-rt10.bz2 For anyone with interest in the GNU\Linux kernel-rt now is the perfect time to get curious and try a build yourself. The last year has seen the kernel go through a pretty rough ride with regards to real time preemption and the kernel. To make a start now will help you understand what's been going on. As things improve you will be part of this movement. Using the config from your installed kernel as a blueprint for your next build sees the build time decrease as you disable drivers\modules etc., you don't need. You don't have to build\install the kernel, just browsing through the *make menuconfig* options is amazing. Presently running 2.6.29.2-rt10 Initial audio benchmarks are good. The next step is to copy this config and reduce the fat even more until I end up with a lean custom kernel-rt for this system. Tuz, the Tasmanian devil: Cheers! Dave.

Hi Quentin, Yes I'm trying a build using the old firewire stack as the only change to the last .config. Variations on the 2.6.29-2 based config base works best for me. The later versions give poorer performance. Performance is good here. It's good to know you're getting close to your target. Cheers! Dave.

Hi Dave, I built a 2.6.29 kernel with the old firewire stack and it is working ok, but I have a slight performance degreadation on the kernel I built. I need to tweak a bit it seems. Did you compile your kernel with the old firewire stack? When I am happy with the kernel I will post the .deb files on my apt repository. Cheers, Q

Pleased with yesterdays build. The audio benchmarks are all fine. On with another build today. If the build is ok I'll post a link to the .config & diifs files. More links: [Audio-FireWire-USB-Video-and-more](http://www.h-online.com/open/Kernel-Log-What-s-new-in-2-6-29-Part-7-Audio-FireWire-USB-Video-and-more--/news/112854/ "Audio-FireWire-USB-Video-and-more") Cheers! Dave.

Built -rt kernel today using the beta3 2.6.29-2 config as a base. config-2.6.29-1-multimedia-686 config-2.6.292b3 Dave 64s30-config2629-2b3 Even though I tried to make an exact copy of the beta3 config. I ended up with the config files showing 35 diffs. $ sdiff --suppress-common-lines config-2.6.29-1-multimedia-686 config-2.6.292b3 > sdiff-2629-2def-2b3build sdiff-2629-2def-2b3build (35 diffs) I'm still resisting tweaking the config to suit just this system as I want to build a distro-rt kernel. I'll try a more adventurous build next. Audio performance looks good initially I need to run more tests. nVidia binary driver installed on this kernel. Cheers! Dave.

Links: building & Real-Time Linux kernel. Index of /pub/linux/kernel/v2.6 Index of /pub/linux/kernel/projects/rt Cheers! Dave.

The new beta3 testing kernel is showing the same upgrade error as the beta2 kernel. It's a known bug. I ReCreated this error on an install here. E: linux-image-2.6.29-1-multimedia-686: subprocess post-installation script returned error exit status 20 There is a problem with the postinst script for this package, on line 569. This is a known bug... Here's a fix. $ sudo cp /etc/kernel-img.conf /etc/kernel-img.conf-backup $ sudo cp /usr/share/doc/kernel-package/examples/sample.kernel-img.conf /etc/kernel-img.conf $ sudo apt-get upgrade (configures the kernel now) $ sudo update-grub Then I replaced my original config $ sudo cp /etc/kernel-img.conf-backup /etc/kernel-img.conf Seems to have worked here. The kernel has fully installed. It's an older install so I took the chance. Not sure if it's an accepted fix? So you use it at your own risk. $ dpkg -l |grep linux-image ii linux-image-2.6.29-1-multimedia-686 2.6.29-4 Testers: Before you begin, backup your beta3-config $ mkdir ~/kernel $ cp /boot/config-2.6.29-1-multimedia-686 kernel/config-2.6.29-1-multimedia-686-b3 If you now upgrade to the testing kernel. Then use sdiff to compare the changes. $ cp /boot/config-2.6.29-1-multimedia-686 kernel/config-2.6.29-1-multimedia-686-b3-4 $ cd kernel/ $ sdiff $ sdiff config-2.6.29-1-multimedia-686-b3 config-2.6.29-1-multimedia-686-b3-4 > sdiff-config-b3-b3-4 Will create the file *sdiff-config-b3-b3-4* $ gedit sdiff-config-b3-b3-4 Also you can use emacs "ediff" to compare the differences. Or grep e.g. kernel$ grep HZ config-2.6.29-1-multimedia-686-b3-4 $ grep HZ /boot/config-2.6.29-1-multimedia-686 Cheers! Dave. Testing alphabetas rc's & daily-builds

Back on kernel testing install after Ardour 2.8 compile\build\install. Running 3.0 alphabeta kernel last build. Ref last post: $ uname -a Linux 64studio 2.6.29-rc4-rt2-tip #3 SMP PREEMPT RT Wed Feb 25 18:09:08 GMT 2009 i686 GNU/Linux $ grep HZ /boot/config-2.6.29-rc4-rt2-tip CONFIG_HZ_1000=y So this was my last kernel compile\build\install report..... Kernel 2.6.29 is released now so its time to move on and download, patch compile\build\install 2.6.29-rt1. The Linux audio tuning mailing list: Note: This install has two kernels at present (1) 2.6.29-rc4-rt2-tip. I'll build the new kernel using (2) 2.6.26-1-multimedia-686. Update: I haven't started to build yet, been testing Ardour 2.8 with 2.6.29-rc4-rt2-tip and its working great. I really must spend some time learning how to use Ardour better, it's just a matter of there's only 24 hours in a day. We are heading towards a top class release with 3.0. Its an amazing journey. Cheers! Dave.

Hi All, The beta3 2.6.29 1000hz kernel is working very well here. I don't use firewire but many users do so it would be the icing on the cake if the 3.0 final works with firewire out of the box. Free will work his magic as always and we'll have a leading edge distro/kernel and still keep to the main goal of stability. I've just finished a 2.6.26 compile at 1000hz. I started the test so I thought it only just to complete it. The 2.6.29 works best here, then I like the 2.6.26, The 2.6.28 (git pull version) deserves another build\compile but I want to focus on package building\maintaining studies for Debian Multimedia, so kernel testing will have to go on the back burner for a while. If you are a kernel builder\tester please contribute and post your findings, 64studio is an awesome distribution and your feedback will make sure it stays that way. Cheers! Dave

Hi Justin, Thanks! it's very useful, three reports of FreeWheeling failing to shutdown. The Hydrogen issue is new to me. Hydrogen is fine here using ice1712. $ cat .jackdrc /usr/bin/jackd -R -dalsa -dhw:0 -r48000 -p128 -n2 Keep the reports coming and thanks again. Cheers! dave

Hi Dave, FreeWheeling does not shut down. Aeolus-- startup results in xruns. Hydrogen- the pitch of drums is raised drastically, no matter what I set the sample rate to, tends to crash. resulting in xruns. When not running jackd, just using the alsa device on my onboard soundcard, the sound is distorted, but when I export to *.wav, the audio is fine using 'aplay file.wav'. fmit tuner is running smooth. This is all I have time for this morning. I hope this info is useful. Justin

Hi myrddinemrys, Thread, 64 Studio 3.0 Beta 2 released: post, kernel development - Upgrades "Warning" here: Great news about your beta2 performance :-) The hanging at system halt should clean up with the next kernel, also adding kernel boot options will improve. Does FreeWheeling shut down ok?. Looking forward to reading more of your feedback. Cheers! dave

My system: Asus Crosshair II Formula mobo EVGA NVidia 9800 GTX+ 512GB M-audio Delta 44 SupremeFX II AD1988 onboard sound Asus TV/FM card 4GB memory Seagate Barracuda 250 GB hdd Initial notes Restart hangs, doesn't poweroff properly Hibernate shuts down, whereupon a boot into 64Studio hangs, need to boot into single-user mode SupremeFX II card works well, haven't tested jackd yet. m-audio delta 44 running jackd at following settings: 96000 128 no xruns 96000 64 no xruns 96000 32 no xruns 96000 16 no xruns Jammed on my guitar for a while, sounds amazing! Ran AMS and ZynAddSubFX, equally amazing. Stay tuned for more tests. Test requests welcome . . .

Hi Testing is not for everyone, I enjoy seeing improvement and reading other users reports. Please post the results when you test the kernel, or anything else. Testers are always needed. The living on the edge reports, result in a stable environment for the released version, with the testers happy because they are doing, just what they always do. Experimenting. Keeping notes & posting them is the key to helping maintain a release in full flow. Stable 64studio, sounds fine to me. $ sudo dpkg -i 2.6.29-rc4-rt2 build-2 1000hz First impressions are good, The desktop feels excited, going to try to calm it a bit. When you install 64studio, a post/mail with how everything performs before you install anything, is important, Notes about Sound/Audio performance are always needed. It's maybe frustrating when something isn't working, but that note you make now about how your sound is working "before" you install anything, could help others. If it's Network problems you have the note can be posted when it's up and running, only so much can be done, the alpha/beta is moving very fast. Cheers! dave

Well, I hear the 2.6.29 kernel is already available in the repo, so I'll give it a shot. Thanks for the info anyway!

Thanks for the info. Will look into it. I just tried to compile kernel 2.6.29 with rt patch, but didn't work. I will try again during the week end, and see what went wrong. I'll get back as soon as posible.

Hi angelsguitar, If you have built kernels before then you can help a lot, I built my first kernel-rt just last week. Here's my notes. $ ls -la /boot/ $ cp /boot/config-2.6.26-1-multimedia-686 config-2.6.26-1-multimedia-686-0 I have done this with the 3 kernerl configs to compare against each other, I keep $ cp .config /home/user/config-xxxxx-01 config-xxxxx-02 config-xxxxx-03 etc., then use sdiff in the gnome-terminal, or my favourite, ediff-files in emacs. $ cp config-2.6.26-1-multimedia-686-0 config-2.6.26-1-multimedia-686-0a (open and delete the text "don't edit" from the first line in config-2.6.26-1-multimedia-686-0a) Once you have changed the text slightly in config-2.6.26-1-multimedia-686-0a run: $ sdiff config-2.6.26-1-multimedia-686-0 config-2.6.26-1-multimedia-686-0a > changes1.txt $ gedit changes1.txt ( you will see a | symbol showing you the changes between the two files) $ ls -l config-2.6.26-1-multimedia-686-0 config-2.6.28-rt-0 config-2.6.29-rc4-rt-0 $ grep CONFIG_NETDEVICES_MULTIQUEUE config-2.6.26-1-multimedia-686-0 $ grep CONFIG_NET_SCHED config-2.6.26-1-multimedia-686-0 $ grep NET config-2.6.26-1-multimedia-686-0 These are just examples, I don't use wireless so can't really give you practical help. Use your documentation to grep for the configs you need to have. $ sudo apt-get install git gitk git-doc Nice starter here: (you will need the tools for kernel building) $ git-clone git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-rt.git $ cd into the downloaded source folder $ make menuconfig save and copy the default .config as /home/user/config-xxxxx-01 Now you can spend some time looking for your wifi config settings, Also use sdiff on 2.6.26 & 2.6.28 backup configs to compare the config differences.e.g. $ sdiff config-2.6.26 config-2.6.28 > changes-2626-2628.txt Cheers! dave

Ok. I'm running the 2.6.26 kernel on Alpha 3.0 right now. Haven't done extensive testing yet; will post back when I do some. But my wifi card does not work in this kernel. It is one of the newer Atheros cards. lspci on my other Ubuntu installation gives this: Network controller: Atheros Communications Inc. AR928X Wireless Network Adapter (PCI-Express) (rev 01) It is supposed to work with this kernel with the ath9k driver. Quoted from http://wireless.kernel.org/en/users/Download : // Known issues * ath9k on older kernels ath9k is currently only enabled on kernels >= 2.6.26. If a developer is interested in older kernels they'll have to add compatibility support for it. // Is it really enabled in this kernel? I tried to compile this same kernel version on Mepis, but never found the section to enable support for ath9k cards. Another problem I have is my video card; I'm running it now in VESA mode, because for some reason it was not correctly detected during install. It is an Intel card. lspci gives this: Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) Is it that the drivers that come in hardy are a little dated? Well, back to the main subject (this thing about my wifi and video is driving me crazy...), I was thinking about compiling a 2.6.29 kernel, just to see how it goes and behaves. I would like to compile a 2.6.28 kernel too, but I didn't see any rt patches for it. And what's git? (I see it around a lot but really don't know) Sorry for the question; I have compiled a few kernels in Debian but don't have a lot of experience. I'm willing to help a little if pointed in the right direction, though.

Hi angelsguitar, You can install the 2.6.26 kernel from the hardy-backports repository, if you are on 3.0 alpha version or 2.1 dist-upgraded to lenny. See post "linux-image-2.6.26-1" (two posts down): You would have to build 2.6.28 or 2.6.29 yourself. If you do, your feedback would be greatly appreciated. We are trying to find which kernel is the best for the 3.0 release. I've got 2.6.28-rt (git-cloned) & 2.6.29-rc4-rt (patched) built and installed on 3.0 alpha. They both need testing to see which is best. Cheers! dave

Is the 2.6.28 (or later) kernel built for 64studio available for 64bit? Where can I obtain it? I'd like to test it, as my new machine needs at least a 2.6.26 kernel for the hardware to work properly ( a newer Intel card and an Atheros ath9k wifi card)

Hi All, I have built 2.6.29-rc4-rt on two different machines, one uses snd_ice1712 and the other snd_intel8x0. Here's my notes. Linux 64studio 2.6.29-rc4-rt2-tip #3 SMP PREEMPT RT Wed Feb 18 08:59:40 GMT 2009 I686 GNU/Linux 0_snd_ice1712 Graphics = "nv" No binary drivers installed. boot: ro acpi=off noapic pci=noacpi vga=791 qjackctl & ardour coldduck-unmastered test project = max = 9.2% Shutdown "hangs" on NetworkManager nm_dbus_init 'cb_data->dbus_connection' failed. Use: [ctrl]+[alt]+[del] boot: ro acpi=off noapic pci=noacpi qjackctl & ardour coldduck-unmastered test project = max = 8.8% Shutdown hangs on NetworkManager nm_dbus_init 'cb_data->dbus_connection' failed. boot: ro qjackctl & ardour coldduck-unmastered test project = max = 9% Overall a very nice crisp desktop indeed. Using vga=791 seems fine with the 2.6.29-rc4-rt kernel, the "acpi=off noapic pci=noacpi" option causes the shutdown process to hang... Build 2 on different computer. Using the same config as Build 1. This second build was running along side the above one, on the second computer. This is my desktop computer using intel graphics/audio. Linux 64studio 2.6.29-rc4-rt2-tip #3 SMP PREEMPT RT Wed Feb 18 12:11:22 GMT 2009 i686 GNU/Linux 0 snd_intel8x0 qjackctl & ardour coldduck-unmastered test project = max = 8% I don't use acpi=off on this machine. It shuts down fine, without problems. I'm letting the Ardour project play/looped whilst running other tasks and up to now all seems fine. Going to rebuild git-clone 2.6.28-rt again, so I have both kernels on the same machine for testing. Cheers! dave

Hi Daniel, Thanks, I'm using the tweak on the new kernel. The 2.6.28-rt kernel is working really well here, it's been running for long sessions and it's not giving any issues except the vga=791 which is not really a major problem. I still haven't found out why it happens though? Cheers! dave

If you're running a plain 2.6.28 or later there's a tweak needed to run qjackctl (Jack Control) with the realtime box checked: echo -1 > /proc/sys/kernel/sched_rt_runtime_us or, edit the file /etc/sysctl.conf and add the line: kernel.sched_rt_runtime_us = -1 Without this tweak, Jack is likely to throw out an 'cannot use real-time scheduling' error. Cheers! Daniel

Hi Quentin, I'm enjoying myself, and learning more each day. The 2.6.26 kernel is fine here but it would be great to have a choice of kernels for the 3.0 release. The 2.6.28 is very good, performance wise it is similar to the 2.6.26 but I don't understand why vga=791 would give the problems it does? I've just started another build this morning. Cheers! dave

I am going to add this thread as a reference in the kernel ticket. Nice job, Q

Hi All, 64studio 3.0 alpha clean install & optimize for audio. git-clone git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-rt.git Notes: max8 envy24chip ice1712. 2.6.28-rt #4 SMP PREEMPT RT Fri Feb 13 15:29:02 gmt 2009 i686 GNU/Linux No nVidia binary driver installed yet. using "nv" No xruns (first time ever on 2.6.28 kernel) Must remember to copy config file as backup. qjackctl & ardour (coldduck-unmastered) test project = max = 8.3% Next Morning: *qjackctl%* Has changed? qjackctl% = constant flux 1% 22% 33% 38% up to 70% It's not an erratic jumping as reported in the past with other 2.6.28 kernel, the fluctuation is smooth and doesn't result in any xruns. Changes I made before I shutdown last night: add to kernel options acpi=off noapic vga=791. Installed emacs22, plug in flash usb to make backups. Connected to other computer, again backups (ssh). edit /etc/sysctl.conf & comment out "kernel.maps_protect = 1 (boot verbose warning) Don't think I've changed anything else? [!!] Booting *without* options: acpi=off noapic vga=791 qjackctl & ardour drum track test project back to = max = 8% plug in flash usb to make backups. qjackctl & ardour (coldduck-unmastered) test project = max = 8% Connected to other computer, again backups (ssh). qjackctl & ardour (coldduck-unmastered) test project = max = 8% All OK! So kernel options "acpi=off noapic vga=791" need checking one by one. Still No nVidia binary driver installed yet. using "nv" Shutdown: Restart: ro qjackctl & ardour (coldduck-unmastered) test project = max = 9.3% Shutdown: Restart: ro acpi=off noapic vga=791 qjackctl idle = max =erratic = 1.2% 19% 38% up qjackctl & ardour (coldduck-unmastered) test project = max = 70% Shutdown: Restart: ro vga=791 qjackctl idle = max =erratic = 1.2% 19% 38% qjackctl & ardour (coldduck-unmastered) test project = max = 70% boot: vga=791 Gives erratic behavior and high qjackctl% but No xruns. Also loading gnome desktop hangs when logging in to desktop. Shutdown: Restart: ro acpi=off noapic pci=noacpi qjackctl & ardour (coldduck-unmastered) test project = max = 9% *ok* The Ardour project has been playing looped for an hour, I've browsed the web, opened gnome-terminal and edited files using emacs22 and the qjackctl% is stable, the desktop seems fine. vga=791 is the only issue. Cheers! dave

Hi All, jam-tut/cold-duck_master01/sounds/coldduck-unmastered.wav is the best file to use. Much larger and better to test with. Here's 64studio 3.0 alpha using the envy24 chip. $ uname -r 2.6.26-1-multimedia-686 $ cat /proc/asound/modules 0 snd_ice1712 $ cat .jackdrc /usr/bin/jackd -R -dalsa -dhw:0 -r48000 -p128 -n2 $ oggdec coldduck-unmastered.ogg Import .wav into Ardour Project: coldduck-unmastered.wav qjackctl idle max 6% qjackctl Ardour project idle max 12% qjackctl Ardour project running/play/looped max 18% $ sudo gedit /etc/sysctl.conf and add: kernel.sched_rt_runtime_us = -1 qjackctl Ardour project running/play/looped max 18% Now down to: qjackctl Ardour project running/play/looped max 10% Cheers! dave

Thanks stevea, That just what we need, Benchmark & Tutorial :-) Here's the results from my 64studio 3.0 alpha on an intel desktop using onboard Sound & Graphics. $ uname -r 2.6.26-1-multimedia-686 $ cat /proc/asound/modules 0 snd_intel8x0 $ cat .jackdrc /usr/bin/jackd -R -dalsa -dhw:0 -r48000 -p128 -n2 $ sudo apt-get install vorbis-tools $ oggdec coldduck-comparison01.ogg Import .wav into Ardour Project: coldduck-comparison01 qjackctl idle max 4% qjackctl Ardour project idle max 9.7% qjackctl Ardour project running/play/looped max 13% When the main studio computer is finished compiling I'll check that out too. Edit: Use coldduck-unmastered.wav instead: See Below!. coldduck-unmastered.wav 0 snd_intel8x0 qjackctl idle max 4% qjackctl Ardour project idle max 10% qjackctl Ardour project running/play/looped max 14% Cheers! dave

Hi All, It's a real pity Ardour doesn't have a default demo project so we could all have the same project as a benchmark/test. What we need is a common project for ardour. A .wav file that we can import into Ardour, so we have the most uniform results we can achieve. We all need to download the same file, it can be a .ogg file and we can use oggdec to convert it to .wav. Then we need to report our findings using the same method.e.g. Post back the results of: $ cat .jackdrc max qjackctl% with qjackctl idle max qjackctl% with qjackctl & ardour project idle max qjackctl% with qjackctl & ardour project running You would have to run the project and watch to see the maximum qjackctl% used during the playback of the project. I use a 48k drum track here and always use it as a test with a new install to help set up the system. We all need the same file.wav to run the test. I'm new to compiling and patching RT kernels. The 2.6.26-1-multimedia-686 kernel is fine here but I'm checking out it's configuration. Also looking at option 4: 2.6.28 + development RT patch (there's now a git repo for it) git-clone git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-rt.git Cheers! dave

I using 2.6.24-23-rt with Ubuntu Studio Hardy and run sessions of Ardour, Hydrogen and Jamin on Jack with no xruns(except the occasionaly when starting/quiting an app). EDIT: I don't know if I cursed myself or what, but 5 minutes after I posted the above statement I was editing in Ardour and scrolling through the song with the timecode and the DSP got stuck at 100% load and XRuns skyrocketed. Odd, but it happened, not sure why. I have been seeing some posts and list comments about 2.6.28 having good audio preformance without the RT patch. If it does have really good performance and stable, I'm sure we all woudn't mind the newer features and hardware support. :)

I am currently running 2.6.26 and it seems stable. the x-runs that i experience is only at startup of Ardour but do not cause problems after that. I figure that the engagement of a audio app through jack could cause such an xrun but i leave the little icon "red" and proceed with projects, checking from time time the status and there is no additional xruns..... on a different note...Lenny is said to be released on Saturday