=== ath_ is now known as athe [00:55] Hmm, what can I do about the 2.6.26 kernel missing nvidia driver? [00:55] Use nouveau? :) [00:55] I can't seem to even manually install the driver. [00:56] I've gone back to 2.6.24 for now. [00:56] I actually had to roll back to the Hardy repo temporarily to get it, though -- the 2.6.24 have been removed from Intrepid! [00:56] Yup. [00:57] There's a patch on ubuntuforums.org to allow you to build the nvidia kernel module against 2.6.26, though. [00:57] Oddly enough, /sbin/lrm-manager is entirely MISSING. [00:57] !find lrm-manager [00:57] !find lrm-manager hardy [00:57] But you won't need lrm-manager? [00:57] Package/file lrm-manager does not exist in intrepid [00:57] File lrm-manager found in linux-restricted-modules-common [00:58] Still, it's bad that it mysteriously disappeared. [00:58] And the failsafe-X thing doesn't actually show what caused the failure -- that's bad. You have to look for Xorg.0.log.old . [00:59] Anyway, can you link me to that forum post, please? [00:59] nvm [00:59] found it. [01:00] Oh, 173.14.09? [01:00] Ya? [01:00] I currently have 177.13 installed. [01:00] Luckily, I don't actually NEED that new of a driver. [01:01] T'is good not to have bleeding-edge closed-source hardware. [01:02] I currently have old closed-source hardware.... and next time, I may have semi-bleeding-edge open-source hardware. [01:02] ATI 3-series or 4-series. [01:03] I like the new numbering. [01:03] Now I can just say, "3-series" [01:04] * DanaG goes off to init 3 temporarily. [01:04] ... and install a new kernel. [01:07] * DanaG opts to just reboot, instead. [01:09] is this the room in need to be in if i need help? [01:09] Help with Intrepid, yes [01:10] where would i go for network help? [01:11] darkreaction: in here, if you are using Intrepid (to be 8.10), the development series [01:11] guess not [01:16] I have a question about updates I recieve. I am always interested, why I am getting those updates, and what they actually portend. [01:16] I seem to have gotten quite a few compiz related updates recently here. [01:16] Do those updates actually add new features, even well into the Hardy life span or what exactly are those updates likely to be doing? [01:16] Most of the time I notice the updates are for obscure things, or things I certainly never use. [01:19] RAOF: lrm-manager and lrm-video went away because there is no use for them without nvidia or fglrx modules [01:19] RAOF: but they forgot to remove the modprobe rule to call them [01:20] I just uninstalled lrm and did my nvidia thing (that DanaG was looking for) so I didn't have a problem [01:20] Hi Amaranth I haven't seen you about in a while. [01:22] yeah, been busy [01:23] Cool nice to see you back. :) [01:23] You work on compiz so you might have some insight into my question or maybe you can tell me a better ubuntu channel to ask it in :) [01:24] I have been away, I have no idea what is going on with compiz [01:24] Odd, usplash is all screwy on the new console. [01:25] Imagine cutting the screen into 8 vertical strips... and then removing every other one and shoving the remnants leftwards. [01:25] ... and then when X failed to start (due to lrm-video missing!)... I was left with a totally black screen. [01:25] And if I loaded nvidiafb.... the screen was shoved halfway off to the left... and didn't wrap around to the right. [01:26] wtf? pcsp stole index 1! [01:27] ... and it doesn't even work on my laptop, anyway. [01:27] DanaG: edit /etc/modprobe.d/lrm-video [01:27] comment out the nvidia stuff [01:27] Yup, did that. [01:27] I just wonder why lrm-video is missing. [01:27] Is it accidental? [01:27] no [01:27] no video drivers, no need for lrm-video [01:28] But then it breaks manually-installed ones, too. [01:28] Amaranth: well I'm not specifically asking about compiz really. I would just like to know generally speaking when we get a list of updates in our pannel, what is usually going on there. [01:28] emma: *shrug* [01:28] They should also remove that modprobe.d file, then. [01:28] emma: bug fixes [01:28] DanaG: I thought they did, I guess not [01:28] Do release cycles actually continue to add features to software or are those mostly minor patches or.. [01:28] I read changelogs. [01:28] emma: during hardy you'll get no new features [01:28] And if something doesn't have a changelog, I try not to install that package until it DOES have one. [01:29] Amaranth: So in the case of something big like Firefox or pulseaudio or the major troubles such as that, it is conceivable that something just not working at all could magically start working some day after an update? [01:29] That keeps me one upgrade cycle behind -- so I get advance warning of major breakage. [01:29] emma: sure [01:29] DanaG: my rule is if I can't boot without it I wait 24 hours and see if a new update came out [01:30] except the kernel, since you can boot an old one [01:30] and soon the kernel will never be a problem with last-known-good [01:30] I also keep around at least one previous major version kernel. [01:30] And update it periodically, too! [01:31] Amaranth - No new features after any release or just the LTS ones? [01:31] you're more likely to get new features in the LTS releases, actually [01:31] they may put in things during their 6 month updates [01:31] but in general you get security and severe bug fixes [01:33] I wonder why snd_pcsp autoloads now. [01:35] I wonder why PulseAudio uses index instead of CARD= [01:36] like, front:0 and surround51:1 instead of front:CARD=Intel and surround51:CARD=Audigy2 [01:36] That'd make it a bit more human readable. [01:36] it really isn't meant to be human readable [01:37] I like the idea of PulseAudio thingies in the windeco. [01:38] Even better if you can go from app->checkboxes for each device [01:38] (with a hotkey to move and unset the old) [01:46] Hmm, is there anything actually majorly new in 2.6.26? [01:46] Majorly, as in, visible to the end-user. [01:50] DanaG: http://kernelnewbies.org/LinuxChanges shows the changes in 2.6.25 [01:51] since we had 2.6.24 those should be new to you [01:51] they won't do 2.6.26 until it is actually released [01:51] Ooh, latencytop. [01:51] Good for tracking down those damn audio dropouts on lid close, and such. [01:52] Oh yeah, how about ext4 stuff? Do you know anything about that? [01:53] Please enable the CONFIG_LATENCYTOP configuration in your kernel. [01:53] argh. [01:54] What's up with that? === DanaG1 is now known as DanaG [01:58] Dang, my laptop doesn't use the iwl3945 LEDs. [01:58] Bummer. [01:58] The only LED is a BIOS-controlled LED that supersedes all drivers -- and even toggles at the Grub screen. :( [02:00] gahhhh [02:00] * ethana2 reaches for snippers [02:00] no wait [02:01] ohhhhh, wireless card [02:01] not keyboard, I was going to say I didn't think that was still the case after bootup [02:01] now I getcha [02:04] DanaG: The scheduler no longer sucks in .36 [02:04] s/36/26. [02:04] they fixed the issues with nicing and CFS? [02:06] They certainly fixed the issues where audio would crackle under tiny burst loads. [02:07] indeed [02:08] although that also went away if you stopped using pulseaudio [02:08] I stopped using pulseaudio [02:08] I use PulseAudio because I have, and use, multiple audio devices. [02:08] I need the niftyness of PulseAudio. [02:09] But why is latencytop not enabled in the Ubuntu kernel? [02:10] because it slows down the general case (not caring about latencytop) [02:12] Aah. [02:12] It actually slows things down? Bummer. [02:12] Reminds me of schroedinger's cat. [02:12] Observation affects it. [02:13] heh [02:13] I use PA as an intercom system [02:13] it's not something you can just watch every couple of seconds like wakeups [02:13] and on a dual seat setup to split my stereo into two mono [02:13] for two simultaneous users [02:13] you have to add instrumentation to all the code where you want to check latency [02:13] I also use the niftiness of it [02:13] basically a "start timer, do work, end timer" thing [02:19] Heh, I wouldn't like having just mono. [02:19] well [02:19] with dual seat on a netburst celeron with 768MB of RAM [02:20] it's not exactly about 'like' [02:20] no 3d acceleration for instance [02:20] because I had both seats on one gpu [02:20] because x can't handle what I needed to do [02:20] one seat intel, one seat ati [02:20] a crying shame as compiz would save a lot of cpu [02:20] with simple proper compositing [02:20] Enable metacity's compositor? [02:21] ......no 3d acceleration [02:21] at all [02:21] X needs a ground up rewrite [02:21] .....I wish linus took up an interest in it [02:21] that would be amazing [02:22] ethana2: You don't need 3d accel to do compositing. [02:22] ethana2: Also, multi-user DRI is now available on Intel. If you're an X hacker :) [02:22] well that's good [02:22] but I had no EXA or anythign either [02:22] simply no acceleration [02:22] the cursors would lag [02:22] I'm always a corner case [02:23] part of why I alpha test [02:23] I run into odd bugs [02:23] that nobody wants to fix after freezes [02:23] for instance, I use a dark theme [02:23] breaks every web site on the internet [02:23] Hm. I thought you should be able to get 2d accel on two different servers. [02:23] that hardcodes one color, and uses your theme for the other [02:23] both or neither to work [02:24] I don't know if I was running two servers or one [02:24] whatever userful does [02:24] I tried attacking it manually with the terminal [02:24] gave up [02:24] had to use propietary software [02:26] ethana2: if you can't mix an intel and an ati gpu that is because you are using fglrx [02:26] and thus you fail [02:27] I use radeion [02:27] radeon** [02:27] but it's an old card [02:27] with specs just coming out now [02:28] the driver sucks so bad I just took it out [02:28] using the integrated [02:28] ethana2: specs just coming out now? that'd be r500 [02:28] half the power [02:28] radeon 9200se [02:28] specs for 'educational purposes' [02:28] we had specs for that long ago [02:28] oh? [02:28] that's r200 [02:28] I got a different idea from an amd employee on phoronix [02:28] hmm [02:29] well they gave the specs to a couple people and stopped giving them out so no current developer had them [02:29] but they do now [02:29] and they mostly had everything done for it already [02:29] oh [02:29] except like [02:29] forgot what it is [02:30] some param gives decent performance [02:30] but its unstable [02:30] the windows driver performed over twice as fast [02:30] tremulous as test [02:30] super-z sound familiar? [02:30] whatever it is, it's crucial to performing decently, and it's off by default [02:31] IRSeekBot got k-lined? [02:31] I do hope the driver continues to improve.. [02:31] super-z is only useful for saving bandwidth in 3d games [02:31] large scenes were a killer [02:31] PCI card [02:32] I should just recycle it [02:32] probably on like [02:32] 180nm node anyway [02:32] anything above that, instant recycle [02:32] when we start seeing 32 nm, I will recommend [02:33] that all 180 node silicon be recycled as well [02:33] when we hit 22, all 130nm node, including this cpu here [02:33] people act like they're being resourceful when they're wasting watts [02:34] ethana2: can you please move this to #ubuntu-offtopic as it has nothing to do with Intrepid AFAICT [02:34] oh sorry [02:34] (I have a tendency to go offtopic..) === BHSPitLappy_ is now known as BHSPitLappy [06:38] hi all :) [07:25] Has Intrepid diverged that much from Hardy yet? [07:25] Lycus: Not visibly [07:26] But in terms of packages, yes. [07:26] bzr [07:26] Bazaar -- a free distributed version-control tool [07:29] thanks RAOFbot [07:29] :D [07:29] heh [07:30] :) [07:39] Has anyone seen any GNOME themes that are mock-ups of what Intrepid is supposed to look like? [07:41] I saw some that were simply awesome [07:41] such as? [07:41] but there's no way to know where they came from [07:41] I don't remember, I don't have a url either sorry [07:41] https://wiki.ubuntu.com/Artwork/Incoming/Intrepid/NewWave - ? [07:42] ooh [07:43] ooooh, newsplash [07:43] very close to what I've been thinking [07:44] you want a screenshot? [07:45] No, I [07:45] would like the theme. [07:45] =/ [07:45] it's just the ubuntustudio theme modified to be brown [07:45] looks like crap, really [07:47] it was more "we're going dark, get used to it" [07:47] it'll be changed later [07:47] firefox still ships with separate navigation and menu bars, status bar turned on [07:47] oo, I got it installed and I approve. [07:47] still those worthless arrow things at the ends of scroll bars.... [07:48] Amaranth: Are you talking about the ubuntulooks-murrine engineything? [07:48] New Wave 0.4.3 is nice. [07:48] ^_^ [07:48] RAOF: yes [07:48] Sorry, Human-murrine. Yes, it's very ugly. [07:48] Lycus: that's not the theme we're going to have [07:48] Also, transparent widgets sound much much cooler than they actually are. [07:49] Amaranth: I see, well, it's the theme I'm going to have. ^_^ [07:49] Are you going to stick with something orange/brownish? [07:49] yes [07:49] RAOF: yeah, the logout and screensaver dialogs and just weird [07:49] * RAOF thinks we should break into something showing our roots, like Debian magenta :) [07:49] So, why does New Wave exist? Just something that is getting scrapped? [07:49] and they fake compiz animations [07:49] Coiotes: Just something a user made [07:50] Amaranth: Ah. [07:51] Is the screensaver dialog transparent? [07:51] * RAOF finds it hard to tell, sitting as it does on a matte black background. [07:52] i think it looked like it once [07:52] but I guess not [07:52] they need to use the compiz plugin for the logout window though [07:52] my fade code sucks [07:53] Oh, is it _your_ fade code that's terribly, terribly slow? [07:53] :) [07:54] Oh, that time it worked better. Although it _did_ bring in some windows from the other workspace in the fade :) [07:54] * RAOF plays with breaking metacity's compositor. [07:55] they may have dropped my code [07:55] it seems to be the non-composited version again [07:55] probably because that dialog is fake transparent [07:56] Is it really non-composited? Because I seem to be able to pick up fragments of other windows with it, like composite fun. [07:57] yeah, it looks like the old "grab a screenshot and darken it" code [07:58] you can tell because the whole thing doesn't darken evenly [07:58] my code would sometimes stutter (damn fade plugin) but would evenly darken the screen [08:00] Is there some reason not to create a great big black argb window and fill it with progressively more solid alpha? [08:00] * Amaranth wants his MB 13.3/2.4/2X1GB/160/SD-DL:WHITE-USA already [08:00] RAOF: that's what my code for the logout dialog and gksu does/did [08:01] Ah, right. And it interacted badly with the fade plugin? [08:01] RAOF: instead of filling the window with a screenshot and darkening it with gdk it would make it transparent black and up the opacity in a timer [08:01] Oh, because of dueling alpha values. [08:01] the fade plugin would fade my fade :P [08:01] man, we've got some interesting stuff in the pipeline [08:01] Right. [08:01] the thing about humans === sourcode is now known as sourcode[0] [08:01] is that we're all different [08:01] so it would be in the middle of fading and i'd change the opacity again [08:02] I hate all colors longer than green === sourcode[0] is now known as sourcode [08:02] "Longer" as in wavelength? That's a pretty large swathe. [08:02] yes [08:02] it is [08:03] white, black, green, blue, purple, violet are all awesome [08:03] the others I dislike very much [08:03] do you like x-ray? [08:03] my display does not produce it [08:03] ;) [08:03] actually [08:03] it probably does [08:03] That's what _you_ think. [08:03] heh [08:03] I'll have an lcd soon.. [08:04] you know what I mean though [08:04] Huzzah for accelerating electrons to relativistic speeds! [08:04] heh [08:04] .7c [08:05] also, there are two theme families: white on black, black on white [08:05] the former breaks half the web [08:05] but it is my preference [08:05] and there's always greasemonkey [08:05] I actually chose ubuntu studio instead of ubuntu [08:05] because of the theme [08:06] I should go to bed now [08:06] good night === stdin_ is now known as stdin [09:09] Random thing I just noticed: [09:10] Audio capture now works! [09:10] My onboard audio device didn't used to have working capture. [09:11] * DanaG uses this theme: http://picpaste.com/pics/screenshot-orange-nodoka.1213694702.png === catweazle_ is now known as catweazle === pen_ is now known as pen === sebner_ is now known as sebner [13:32] Bah, my Intrepid VM has screwed up. Mouse is stuck in a tiny square in the top left :( [13:41] when is 8.10 test version coming out? [13:41] bluecake: first alpha should be soon but i dont suggest you test until beta releases [13:42] gnomefreak, i heard new GUI will be there for 8.10 [13:42] bluecake: there is a very big chance all the alphas will be broken at one time or another and if you cant fix it you might be without a working system [13:42] bluecake: that wont happen until last alpha [13:42] oh... [13:42] i have a test machine, i wipe it out every 6 months [14:06] morning all:) has anyone successfully gotten intrepid to act as a xen dom0? [14:09] or is it still unsupported in 2.6.26? (I know it isn't supported in 2.6.25, and I need to run 2.6.25+ to have working wireless :/) [14:56] brb\ === acuster is now known as avc_lurk === pen_ is now known as pen === dmb_ is now known as dmb [18:16] will sound be fixed in ibex? [18:16] it seems default like sampling rates of alsa and pulse are not set to the same value [18:17] I have incredibly bad sound quality when recording! [18:50] pulse makes terrible quality or latency in my experience [18:50] even when its set to just pass through# [19:09] h3sp4wn_: Have you reported a bug for this? [19:52] Heh, so how unstable is Intrepid? [19:53] I certainly am not going to use it for production work, but just curious if it's even possible to install and fool around with in a VM [19:53] VM should be fine [19:54] but it's not exciting and unique yet [19:54] it's just like debian sid [19:54] Does it still use Hardy's kernel? [19:54] it'll get more intrepid-ish as it goes on.. [19:54] ...i don't know [19:55] ethana2: I was talking to someone earlier that said it was still using nm .6 instead of .7... Is Intrepid going to use nm .7 when it ships in the fall? [19:56] ethana2: I know it's most speculation at this point, but just curious if there's any idea whether or not it will still be using nm .6.6 [19:56] if .7 comes out before code freeze [19:56] it'll probably be using it [19:56] unless they do some odd number unstable thing [19:56] like the kernel does [20:12] ethana2: I think you were thinking of broadcom, btw [20:12] the broadcom driver team had two groups [20:12] one did documentation, the other wrote code based on that documentation [20:12] yeah [20:13] I'd give my money to an effort like that with nvidia hardware [20:13] equal to the cost of the nvidia gpu I bought [20:13] evidently you're in #nouveau [20:13] heh [20:16] Amaranth: we need organization [20:16] someone needs to take donation pledges [20:16] and set up this effort [20:16] ethana2: afaik they have all the hardware they need at this point [20:16] but labor wages? [20:16] and they aren't doing documentation, just writing the driver [20:17] well no [20:17] hmm [20:17] hopefully marcheu will be hired by someone to keep working on it [20:17] yes [20:17] he is the main guy that started the project [20:17] we could do that [20:17] as a community [20:17] employ him full time at $20 an hour to work on it [20:44] <^Ocean^> I am trying too upgrade too Hardy, I did a dist-upgrade and cron, failed too install... What did I do wrong [20:53] ^Ocean^: This is for Intrepid Ibex not Hardy Heron? [20:53] ^Ocean^: file a bug please and include the files in /var/log/dist-upgrade/ to the bugreport === Amaranth_ is now known as Amaranth [22:01] Is there an intrepid cd image yet? [22:02] maybe dailies, no alpha yet [22:02] ethana2: Yeah that's what I wanted [22:03] * ethana2 looks [22:03] http://cdimage.ubuntu.com/daily/current/ [22:03] hmm...broken links [22:03] guess not [22:04] http://cdimage.ubuntu.com/daily/20080624/ has downloads though [22:04] which is odd that's not in current... [22:06] YokoZar: iso.qa.ubuntu.com has alternate CDs for testing. [22:25] hi [23:11] not inrepid related but i'm upgrading a gutsy box to hardy. i know i've changed config files. i'm going to run the upgrade unattended and i'd like it to default to replace when it encounters changed config files. [23:11] Is this possible? I'd rather not come back to a half-done install awaiting a keep/replace [23:12] i would this would be possible for an unattended upgrade, but can't find anything on this [23:29] mcquaid: I hear you, find the name of the app that does all that [23:30] and go to those folks [23:30] because they'll know more about all of it than anyone else [23:30] you may end up filing a feature request [23:30] ok === effie is now known as effie_jayx