[00:43] rlameiro, the audio-plugin tasksel should be fixed for alpha2 tomorrow or the next day :) [00:43] nice [00:44] * ScottL feels kinda silly though thinking that the meta packages needed to be rebuilt because of the tasksel problem when i knew cjwatson runs a script to generate them [00:45] oops [01:14] i've been having a LOT of kernel panics on a machine i bought from ebay, it's a dell p4 with hyperthreading [01:14] but it also has 3.25 gigs of memory and it's a 32 bit machine [01:15] anyone have any idea if the extra memory or the HT would cause kernel panics about 2/3rds of the time? [01:27] it might [01:27] maybe the RAM is malfuncioning [01:43] rlameiro, i'm going to do a fresh install of maverick and see how it behaves, this way i can do some backporting tonight and tomorrow, then test the iso image for natty next [01:43] if maverick doesn't have these problems then i think it may be the new kernel [01:44] if the problem persists then i probably tear down the computer and start building it piece by piece until i find the failing part :/ [01:44] ScottL: I had problems with memory before [01:44] in windows it crashed all the time [01:44] in linux it run way better, but you never know [01:45] well i did find that it had two 1gig sticks on memory in one channel, the other had a 1gig and a 512megabtye stick [01:46] i thought maybe having one channel not matching might have done it but i've already removed the 1 and the 0.25 gig sticks [01:46] it still is giving me problems [01:46] I don't know if faulty memory would cause kernel panic. Usually the system just freezes for me. Try using only one stick [01:46] Ah, ok [01:47] How about pci cards, anything added to the machine? [01:48] Though, still, why kernel panic? [01:49] I'm having trouble booting -lowlatency sometimes. [01:49] Don't get any message. It stops at the purple screen [01:50] Im worried that I have a hardware problem. Maybe the drive. It's newly bought, but I started having issues after I replaced the drive. [01:50] ailo [01:51] do ctrl-alt-FN1 [01:51] ctrl-alt-F1? [01:52] My usb keyboard is shut down too during that process. I should try replacing that too [01:53] weird [01:53] you should enable that on bios [01:54] that key shortcut is to acces to tty1 [01:54] virtual consoles [01:54] Aha [01:54] maybe it outputs some data [01:54] or press esc during boot [01:54] I should try with a non-usb keyboard [01:55] i forget to mention that it usually stops during boot, maybe before grub, maybe right after grub, sometimes just before completing boot [01:56] but the reason i think it's kernel panic is because the caps lock and one other light begin to flashing in sync [01:56] ScottL: what hardware / modules? [01:57] ScottL: any hardware changes? Is this on boot or during runtime? [01:57] ScottL: Do you have this problem with -generic? Have you tried evaluating that? [01:57] oh you just said it [01:58] ScottL: lucid? [01:58] natty [01:58] ah, hum. [02:00] ScottL: try bisecting the kernel deltas from maverick [02:00] ScottL: was it working in maverick? [02:01] Before raw bisect, one can get value from just trying different packaged versions. bisect between two revisions tends to be easier. [02:02] persia: +1 [02:02] Technically a bisect is faster, but requires a fair bit more attention :) [02:03] persia: truth :) [02:03] * paultag gets back to family guy [02:10] rlameiro: About our audio-test program. I'm working on the script, which will probably be pretty simple, but I need to work out some details. Do you want us to share the work on the pd patch? [02:11] its ok [02:11] we can share the work :D [02:11] I'm also considering if we should use git or something. I have a git account we could use for it [02:12] Just need to get your ssh key, so you can push your patches there [02:12] Or do you have your own CVS, or the like? [02:24] i've already installed maverick and am getting updates, i'll reboot after that a few times and see what happens...i notice the kernel is 2.6.35 [02:25] i believe i had this machine running ubuntu studio lucid for a month or so without the problems i'm experiencing recently now that i think about it [02:49] maverick seems to work just fine for me, paultag or persia, do you have any suggestions for figuring out what my problem might be? [02:49] even if you recommend posting a question on #ubuntu-kernel, that would be a welcome suggestion [02:50] or even suggestions on how to provide an adequate bug report in this case [02:50] ScottL, Maverick works with the latest kernel in -updates? [02:55] If so, upgrade to Natty, except not upgrading the kernel, then install each Natty kernel until one breaks. [02:56] If not, then install each Maverick kernel between the base kernel and the latest in -updates until one breaks. [02:56] Once you have one that breaks, hunt down JFo and ask what information beyond the kernel versions is useful in a bug report for a regression in bootability. [03:02] persia, eh, i hadn't enabled updates yet, i will do that and see if anything breaks [03:05] oh, i had -updates enabled by default, it was -backports that i was thinking wasn't enabled [03:08] persia, how should i upgrade to natty from a maverick install [03:24] -backports should never contain a kernel, so you ought be safe there. [03:24] So, the *right* way to upgrade is `update-manager -d` or `do-release-upgrade -d`, but we're not going to do it that way :) [03:25] The following should only be used for debugging purposes: [03:25] 1) Go to https://launchpad.net/ubuntu/+source/linux and get all the kernel packages that were uploaded to Natty. [03:26] 2) Make sure aptitude is installed on your system [03:26] 3) edit /etc/apt/sources.list and change every occurance of maverick to natty [03:26] 4) run `sudo aptitude -u` to get all the new updates [03:27] 5) Press '+' when "Upgradable Packages" is highlighted [03:27] 6) Press 'g' [03:28] 7) Navigate the package selection ('Enter' opens a submenu), and find the attempt to upgrade "linux" or "linux-generic" or "generic-linux" or whichever one you have installed (the kernel metapackage) [03:28] persia, just to make sure, you realize that natty is development currently? [03:28] 8) When the kernel metapackage is highlighted, press ':' to not upgrade that. [03:29] ScottL, Yes. This is a fresh install you're willing to reinstall tomorrow after filing the bug if necessary, right? [03:29] I run natty one one of my laptops, just to keep track of the changes, but yeah, it's not really suitable for getting real work done. [03:30] 9) Press 'g' again to upgrade most of the packages [03:30] 10) Press 'q' as many times as required to quit aptitude once the upgrade is complete. [03:30] 11) Reboot [03:30] persia, i have a fresh maverick install that i am ready to reinstall tomorrow, yes :) [03:30] 12) In order, install each kernel package that was published in natty, and reboot [03:31] At some point, whilst repeating step 12, you will not be able to boot (if you can replicate the bug noted above). [03:31] At that point, report the version that worked and the version that didn't work in a bug report, and bug JFo for what other details are useful. [03:32] This is actually a fairly safe time to upgrade to natty, because of the Alpha 2 freeze (which should have started 3:30 ago, but ... ) [03:33] persia, did you see that i got the tasksel hopefully fixed with cjwatson :) [03:33] I did. Nice work. [03:39] persia, i went to https://launchpad.net/ubuntu/+source/linux, but i'm not show how to get all the kernel packages for natty [03:40] at https://launchpad.net/ubuntu/natty/+source/linux i found thirty release of the kernel for natty [04:04] Heh, yeah, there's been a few uploads :) [04:05] When did it last seem to work? I'd recommend starting from there. [04:07] persia, but how do i get them? navigate to the page with a .deb file and download it? [04:07] Right. I tend to find https://launchpad.net/ubuntu/+source/linux/+publishinghistory useful, with the links on the right. [04:08] Starting from https://launchpad.net/ubuntu/karmic/+source/linux/2.6.31-22.71 might well be a reasonable place: I think that's the last 2.6.37 that was uploaded. [04:08] And I suspect you would have encountered an issue before now if that was bad. [04:09] Unless I'm guessing wrong, the issue came with the 2.6.38 kernel (as that was the more significant change) [04:09] Err, wrong link :( [04:12] https://launchpad.net/ubuntu/natty/+source/linux/2.6.37-12.26 was the one I thought might be a safe starting point. [04:13] i was having trouble with the 2.6.37 kernel as well, don't know how far back though [04:16] Hmm. Well, you're choice where to start. I'm not sure what would succeed/fail. [15:26] wow...looks like all the xorg packages blew up this morning :/ [15:26] scott-work: in general? [15:26] or relating to gnome? [15:27] holstein: it looks like in general, they failed to build for some reason, i'm guessing a change someone made yesterday which will be fixed by tomorrow :) [15:27] * holstein ponders the term 'freeze' ;) [15:29] we're only under debian import freeze with feature freeze coming up soon [15:30] OIC [15:30] they'll sort it out anyways [18:44] persia: i think i messed something up last night updating my maverick install as i was quite tired when i got to attempting it and was driven to distraction by the dogs barking to go outside at almost midnight :/ [18:45] persia: nonetheless, this morning i resinstalled maverick again and after updating again will try it again [19:24] new blog post if anyone is interested: http://dullass.blogspot.com/ [19:30] congrats jussi on the council wins [19:57] council wins? [20:12] astraljava: http://ubuntu-news.org/2011/02/01/new-irc-council-members/ [20:15] cool [20:15] congrats jussi :) [20:15] coolness! conga-rats jussi01! but I thought he was already a part of the council. oh well, I must be out of my mind... which is nothing new [20:27] astraljava: it was re-election [20:30] Ahh... sorry that wasn't clear to me from the page. [21:44] There is a xorg transition going on in Ubuntu, hense the CD blow up. [21:44] It should all be settled come the next build.