=== psivaa is now known as psivaa_afk [07:15] moin [07:33] morning === ghostcube_ is now known as ghostcube === fmasi_afk is now known as fmasi === fmasi is now known as fmasi_afk [11:52] * henrix -> lunch === fmasi_afk is now known as fmasi [12:24] guys, do you have problem with R and cracking audio? [12:25] no... though admittedly my workplace still is P [12:26] while i'm playing a song, whenever skype/mumble/whatever emits a 'beep', i get a cracking noise coming out of my speakers [12:26] :( [12:46] struggling with mumble [12:46] smb: ^^ [13:10] ppisati, actually there was just a thread on pulseaudio-discuss labeled "skype sound effects create a buzzing noise" [13:13] ppisati, according to thread, Arun thinks I've fixed it in a patch which is in 4.0-rc1 (3.99.1). I'm not so sure, but feel free to try ( ppa:ubuntu-audio-dev/pulse-testing ) === fmasi is now known as fmasi_afk [14:55] diwic: pulseaudio 4.0-rc1? [14:55] ppisati, or 3.99.* [14:55] diwic: weid [14:55] *weird [14:55] ppisati, how come? [14:56] [flag@luxor ~]$ dpkg -l | grep pulseaudio [14:56] ii gstreamer0.10-pulseaudio:amd64 0.10.31-3+nmu1ubuntu2 amd64 GStreamer plugin for PulseAudio [14:56] ii gstreamer1.0-pulseaudio:amd64 1.0.6-1ubuntu1 amd64 GStreamer plugin for PulseAudio [14:56] ii pulseaudio 1:3.0-0ubuntu6 amd64 PulseAudio sound server [14:56] ii pulseaudio-module-bluetooth 1:3.0-0ubuntu6 amd64 Bluetooth module for PulseAudio sound server [14:56] ii pulseaudio-module-gconf 1:3.0-0ubuntu6 amd64 GConf module for PulseAudio sound server [14:56] ii pulseaudio-module-x11 1:3.0-0ubuntu6 amd64 X11 module for PulseAudio sound server [14:56] ii pulseaudio-utils 1:3.0-0ubuntu6 amd64 Command line tools for the PulseAudio sound server [14:56] ppisati, that's 3.0 [14:56] diwic: ^ [14:56] ppisati, we're currently testing 3.99 in ppa:ubuntu-audio-dev/pulse-testing [14:57] diwic: ah... actually i read '1.3.0-0' instead of 3.0.0 [14:57] diwic: ok, lemme try the ppa [14:57] ppisati, ok, let me know how it goes. [14:58] * diwic bbl === fmasi_afk is now known as fmasi === fmasi is now known as fmasi_afk [15:40] hi [15:41] is zcache enabled in the default 13.04 kernel? [15:41] I'd like to enable zcache but I'm not finding a lot of information [16:15] I'm guessing no one knows about zcache [16:21] isnt it claching with zram ? [16:21] we do have a bunch of images that rely on zram being available [16:21] (so thats definitely enabled in the kernels) [16:26] ogra_, after my googling, I added zcache to grub.conf and got this to happen --> http://pastebin.com/p5yF4zRm [16:26] ogra_, am I using this wrong? [16:27] looks ok i think [16:28] i never used zcache ... but it doesnt seem to error [16:30] I would have kept zram only but I ran across a thread that had an idea of using both zram and zcache together [16:31] ogra_, that is why I'm not just sticking to using zram only [16:31] ogra_, http://comments.gmane.org/gmane.linux.kernel.mm/91769 [16:31] iirc zcache requires that you have swap already [16:31] I do [16:32] that doesnt work in many contexts where we use zram in ubuntu [16:32] (if you use zram its often because you dont have a disk to use swap on) [16:33] I was just trying to speed up things [16:33] after enabling zram my system does not hang anymore [16:33] zram definitely helps with that .... i doubt zcache is any faster than zram [16:34] well if what I did with enabling zcache was right, then enabling both didn't seem to hurt or help any from what I see so far [16:34] yeah [16:34] it wont change much [16:35] (if you already use zram) [16:35] ogra_, let me get this straight, zram is a faster swap replacement, zcache speeds up the use of swap [16:36] zram grabs parts of yout ram, compresses it and provides it as swap space [16:36] if it speeds up your system the actual thing you want is to buy more ram :) [16:36] so zram or zcache? or just stay where I have it now, both enabled [16:37] ? [16:37] i dont think it matters much [16:37] mmk [16:37] the conclusion is that yoou dont have enough physical ram [16:37] yea [16:37] if any possible you should get more [16:37] can't I have a netbook [16:37] 1.5 is my limit [16:38] 1.5 gigs [16:38] zram and zcache will only help a little until you hit the ram barrier again [16:38] seems to have solved my issues [16:38] right, if you keep your habits .... [16:38] is the init=/bin/sh kernel command line parameter read by upstart or by the kernel? I thought it used to be the kernel. Is there a way to persuade Ubuntu /not/ to run upstart first (I want to run a pivot_root an a debootstrapped initramfs) [16:39] people tend to open more borwser tabs once it works better [16:39] and at some point you are back at the point where it gets slow [16:39] ogra_, I think I'll be upgrading to a i3 or better laptop by this fall for college [16:40] alexbligh, it works fine here [16:40] ogra_, well thank you for the info and help, google wasn't that much of help [16:41] ogra_, even if you aren't using an autogenerated initramfs? I mean in the normal case, it must be the initramfs which runs the pivot root then /sbin/init, yes? [16:41] ie it must be userspace that looks at it [16:41] as long as /bin/sh exists both, the kernel as well as the initramfs respect init= [16:42] (teh kernel only comes into play without initrd indeed, but it uses the parameter) [16:43] Aaah, well I do have an initrd - it contains my full root filing system. Is the kernel ignoring init= because it thinks it's up to my initrd to do that? [16:43] ti shouldnt [16:43] I can cat /proc/cmdline and init=/bin/sh appears there [16:43] it should just hand over the parameter to your userspace [16:43] but it runs upstart [16:43] indeed that requires that something in your userspace handles it [16:44] it does hand the parameter to userspace. I'm wondering if the kernel ALWAYS runs /sbin/init (whatever init= says) if initrd= is specified. [16:46] it might [16:46] ubuntus initramfs definitely has a handler for it [16:47] Yeah I am using debootstrap to make an initramfs of my own [16:47] i know if you boot without initrd the kernel hands it over properly [16:47] I want it to run a different program [16:47] I think I need go read the source [16:47] that might help :) [16:48] Aha, rdinit= === fmasi_afk is now known as fmasi === fmasi is now known as fmasi_afk === popey_ is now known as popey === tyhicks` is now known as tyhicks