![]() ![]() I copy these from a generic kernel configuration. I also, when I need to, check the net section to make sure that the firewall modules that I need are loaded. I then run 'make menuconfig' and select all the usb device drivers for sound cards and other hardware that I might use. This generates a kernel configuration file that contains all of the modules selected that exist in your running kernel. What I do to speed things up, is to copy over the config file and then instead of running the command, 'make menuconfig' to edit the configuration by hand, I plugin the usb hardware, micro-sd cards etc, and anything else that loads a kernel module into the running kernel that I am currently using, and then run the command 'make localmodconfig'. Then it is only a matter of selecting the correct rt_preempt option to get the realtime kernel.īecause I'm lazy and forgetful, I tend to use the following set of instructions to build it.īecause you are using a generic kernel configuration, your build process will take a few hours, perhaps. But in general you can copy over the configuration file from your installed o/s and, because it is generic - for all machines - it has the kernel config that will match your machine. This can be fun to experiment with, and in general doesn't risk any harm, the kernel will go into panic if there is some issue that means it is wrong for your machine. ![]() The building of a kernel is not difficult, unless you want to modify the kernel configuration options. Simply type apt-get install linux-lowlatency. The low latency kernel can be installed from the apt. I would highly recommend not installing a kernel from some unknown source, and building it yourself, if you want a realtime kernel. So understand what you are getting into (it's a rocky road) and good luck. There are endless issues which, until you become familiar with them, is going to lead to problems down the road. System libraries (as provided by the OS vendors) are often old and missing functionality which some packages require.Ĭore audio libraries (like jack) are provided with things like DBus enabled which often screws up and can be very confusing to troubleshoot for newcomers. In such cases you're better off knowing how to fix it yourself, but then you need to be more self-reliant and this takes much more effort & time to learn. The more you rely on distros and pre-baked stuff the more you become a hostage to it (it's a bit like being trapped in a walled garden from commercial software vendors) and you'll soon realise that when things don't work that you need to work, you cannot really do much about it until whoever maintains packages & distros fix the particular issue. There are a lot of compromises between having a system set up the easy way (ie via repos, pre baked distros, packages etc) and having your system work reliably and the way you need it to work. The learning curve (to really get to the point where you understand things and your system is mostly working well) is quite steep, so be prepared to do a lot of reading & experimentation.Īlso, if you really want to learn about kernels, configuration etc you probably need a spare drive (drives are cheap) so you can practice things on there and if you break the OS, it doesn't matter and you can start over. I personally stay even more native to the system, and prefer LV2 (over VSTs), and Ardour (over any existing emulated or ported software). It might help to read Glen's thoughts about 32 and 64 bits, and to check Carla to integrate Windows VSTs in case you want them. I haven't tried Reaper except on Windows, but I hear that it should run just fine by now. If yes, then you can go on with the low latency kernel, Jack, and so on. Just see if it is registered as a class compliant USB device, and if the system settings in Ubuntu see it as an audio device. You have the Komplete Audio interface? I don't know much about that, but chances are that if it doesn't need drivers for Macs (because of their CoreOS), you will probably also have that plug & play experience on Linux. Asio4allmusic wrote:i want to keep things very clean and easy so only os,lowlatency kernel,drivers & reaper stopĪs for drivers, you probably don't need them. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |