[03:15] delt: i'll tell you what i do on my production rig... i have a shortcut to the terminal command on my desktop.. i click it and put in the sudo password. [05:39] anyone seen distrozapper? [05:40] !anyone|TerranceWarrior [05:40] TerranceWarrior ask your actual ubuntu question [05:45] hi [05:46] i an having problems with my touchscreen [05:58] cfhowlett: nevermind he left me a message. [05:58] but on a sidenote my zorin recognizes my soundblaster but gets no sound, same configuration works in sound under windows 7. [05:59] TerranceWarrior sorry, zorin isn't supported in the ubuntu channels. [06:04] cfhowlett: how would you handle it under Ubuntu? [06:06] TerranceWarrior different distro, different rules. see zorin for support of your distro. [06:23] cfhowlett: thats not what I asked. [06:36] how can I get independence free sound working again under Ubuntu? [06:37] I had sound working before but upgrade from wine 1.4.1 to 1.6.1-rt. [07:56] nevermind i have it [12:45] distrozapper [13:12] hi, just checking in to claim total unawarenes of this system [14:05] sebio "this system"? [14:07] ubuntu studio, yesterday i installed, started from cd, nothing worked properly, gone to bed... today went better by removing the disc [14:08] sebio proper sleep actually fixes many technical problems. [14:09] TerranceWarrior: you can visti #kxstudio for support.. thanks! [14:09] indeed [15:46] holstein: for that cpu governor thing.. i wrote a small script that sets all cores at once and i call it from my xfce session startup. works perfectly =) [15:48] the main part of it goes like... cd /sys/devices/system/cpu; for core in cpu?; do echo "$1" > /sys/devices/system/cpu/${core}/cpufreq/scaling_governor; done [15:49] (kind of simplified, but you get the idea) [15:49] delt: sounds good! [15:50] holstein: of course it checks for root acces, and sudo's itself if it doesn't have it [15:50] :) [15:51] i'm just wondering why running it from /etc/rc.local doesn't work... there must be something that sets the governor back to "ondemand" afterwards [16:01] sounds plausible [16:16] OvenWerk1: has some idea about that, I think [16:17] delt: I seem to remember there's some process in Ubuntu that sets it ondemand [16:17] yeah, he had another alternative that worked well [16:17] i forget... [18:05] interesting... [18:05] lrwxrwxrwx 1 root root 18 Mar 28 22:38 /etc/rc2.d/S99ondemand -> ../init.d/ondemand [18:05] lrwxrwxrwx 1 root root 18 Mar 28 22:38 /etc/rc3.d/S99ondemand -> ../init.d/ondemand [18:05] lrwxrwxrwx 1 root root 18 Mar 28 22:38 /etc/rc4.d/S99ondemand -> ../init.d/ondemand [18:05] lrwxrwxrwx 1 root root 18 Mar 28 22:38 /etc/rc5.d/S99ondemand -> ../init.d/ondemand [18:07] chmodded -x that file just for good measure -) [18:13] whoa, this seems complicated for nothing, /etc/rc2.d/README: "To disable a service in this runlevel, rename its script in this directory so that the new name begins with a 'K' and a two-digit number, and run 'update-rc.d script defaults' to reorder the scripts according to dependencies. A warning about the current runlevels being enabled not matching the LSB header in the init.d script will be printed. To re-enable the service, rename the script back to its [18:14] oh yeah i see why.. the same script in init.d might be symlinked from several runlevels, and you might want it enabled in one but not the other [18:14] so disabling +x on it isn't really a good option [18:17] (sorry about that :D ) [21:21] delt: I say, just rename it. If you want control yourself, you don't really need it. [23:20] delt: re changing ondemand to performance. If you wish to change from rc.local put a 90 second delay in front... The default puts a 60 second delay so ondemand gets set (again) about 60 seconds after X (lightdm) starts. This is supposed to allow X to have full speed to start up... but allas someone else has already set ondemand earlier. [23:20] This is to say cpu speed setup is kind of a mess... or was the last time I looked at it. [23:23] Studio can't really fix this as this is done in packages we depend on. It was not worth while trying to fix upstream at the time because of the phase in of upstart... now we are headed to systemd and the same thing all over so I will wait till the dust settles once again before poking at it. [23:25] With regard to CPU speed. I have found that running at half speed (user set) gives better performance than ondemand. So you may wish to remember that if you find performance (full speed) makes your cpu to hot. [23:27] Also remember there is stuff in the chipset on the MB in all new computers that will change cpu speed if it gets too hot without the OS even knowing the cpu cycles have been stolen to do so. So it is good to monitor the cpu temperature and make sure performance will not make things too hot. [23:30] If it does, it is better to set cpu speed to user and choose a slower (but constant speed) to stay within a good temp range. [23:31] My personal findings are that ondemand does generate xruns sometimes.