500 Internal Server Error

[07:42] RAOF: so, with the 3.4 kernel the screen gets detected on the DP port (according to xrandr and the display settings), but i get no signal. do i need any userspace updates too? [07:42] htorque: Not as far as I'm aware. [07:43] There'll be shiny new userspace in Quantal soon, but I'm not aware of any specific fixes for that. [07:44] RAOF: bummer. thanks, anyway! [07:46] * apw yawns [08:54] htorque: what gfxcard? [08:58] dileks: nvidia nvs 4200m [08:59] dileks: (gf119/nvd9) [09:04] * dileks was looking into stable-queue-3.4 patchset this morning, but nothing for nvidia [09:04] http://git.kernel.org/?p=linux/kernel/git/stable/stable-queue.git;a=tree;f=queue-3.4;hb=HEAD [10:30] doh! [10:30] 500 Internal Server Error [10:30] did i kill the wiki? :) [10:33] yeah, nobody can reach it anymore and at the bottom of the error page it says "killed by ppisati" ! [10:33] :) [10:34] (works fine here) [10:34] ;) [10:34] i know [10:34] it even swallowed my stuff [11:14] https://wiki.ubuntu.com/QuantalQuetzal/ReleaseSchedule [11:15] hmm, where is the feature-definition page? [11:16] status.ubuntu.com ? [11:17] Google calendar of Precise Schedule <--- should be quantal [11:18] http://fedoraproject.org/wiki/Releases/18/FeatureList [11:18] I am looking for sth like this for upcoming F18 [11:19] well,l i think status.u.c is the closest you can get, not sure we have another aggregation page [11:21] (look at the team pages, features are listed by team) [11:23] we seems to have way more features defined than fedora, adding all feature definitions (blueprints) to a single list would be huge === rsalveti` is now known as rsalveti [12:33] apw: CONFIG_*_PHY have a "=y" policy because "PHY drivers are not autoloadable", but all these options are tristate, so they can actually be built as modules [12:34] ppisati, yes but as the annotation says, they cannot be autoloaded [12:34] there is no id to detect and load them as a result of detecting same [12:35] though i will say i have not personally verified that, that came from rtg [12:35] uhm, ok [12:35] so if they wern't Y we would have to modprobe them all i believe, or know which ones we need in any machine [12:35] which for x86 is a non-starter [12:36] now, you are welcome to go away and confirm/deny this assertion and we can change it for Q based on that [12:37] actually i expect the phy module to be loaded by the nic chip driver [12:38] so it makes sense to not have ids there [12:38] that would depend on them being able to detect the phy type inserted [12:38] as often they are replaceable at least in concept [12:39] but as i say, i have not confirmed this personally [12:39] so if you can a test case then you could try it out [12:39] right [12:40] i would be delighted to be wrong and be able to pull them all out [13:12] ogra_: https://wiki.ubuntu.com/QuantalQuetzal/TechnicalOverview/Alpha1#New_features_in_Quantal [13:12] looks more like what I was looking for [13:13] well, thats a past doc ... i thought you wanted the features for the quantal release [13:13] (future doc instead) [15:07] * ogasawara back in 20 [15:41] apw, in .gitignore there's .orig but not .rej - is this so that git status shows the .rej files ? [15:42] probally just an oversight, that likely comes unchanged from upstream [15:45] apw, ah discussed on lkml a couple years ago, intentional for various workflow related reasons [15:46] would have been nice to add a comment detailing it in .gitignore at least :) [16:47] * cking --> food === infinity is now known as ogfinity === ogfinity is now known as infinity [17:34] ogasawara: Do you know if the plan for precise is to integrate highbank into master, like you've done for quantal, or will it be an out-of-tree build with its own ABI? [17:35] ogasawara: (The latter will be a tiny bit more confusing, given that we'll have to remember they're "different", but not a big deal) [17:35] infinity: plan is to integrate into master [17:35] ogasawara: Sexy. Thanks. [17:35] infinity: apw's just sent out a config review [17:37] * henrix -> EOD [17:47] hello! it is possible to compile a vanilla kernel on ubuntu? [17:50] in the last but one post in the following link, somebody says it is not legal ... O_O ... http://ubuntuforums.org/showthread.php?t=1387046 [17:52] adrenalink: we provide mainline builds for ubuntu -> http://kernel.ubuntu.com/~kernel-ppa/mainline/ [17:52] adrenalink: https://wiki.ubuntu.com/Kernel/MainlineBuilds <- that wiki has some details === yofel_ is now known as yofel [17:58] ogasawara: i want manage the kernel by myself (for instructive purposes), so I don't need a .deb package.. [17:59] I would know what ubuntu insert in vanilla kernel in its distribution [17:59] and why... [17:59] (I hope this is the right channel for this question) [18:00] adrenalink: I'm not quite parsing your statement, you want to know the delta of patches we carry on top of the mainline kernel? [18:01] yes. You appy a patch to vanilla kernel [18:01] what does this patch do? and why? [18:02] adrenalink: take a look at https://wiki.ubuntu.com/KernelTeam/Specs/QKernelDeltaReview, that's the most recent delta review we did for the Quantal kernel [18:02] is it possible to run ubuntu with a vanilla kernel instead an ubuntu kernel? [18:02] adrenalink: yes, as I noted above, you could install one of the pre built mainline vanilla kernels we're pre packaged for you and you'd be running a vanilla kernel in ubuntu [18:03] adrenalink: if you want to build and run the upstream kernel yourself as an excersice, there's plenty of docs out there describing how to do so [18:04] i know how i can compile by myself [18:04] and I did it. [18:05] but the system does not work. So i wanted to know if you insert something particular on ubuntu kernel.. [18:05] I'll read that link. thank you ogasawara ! [18:06] adrenalink, all our sources are public you can see everything we put into them [18:07] ogasawara: of course! But asking to people that work on it, is more helpful that trying to find in the code. XD [18:08] just another question: is what people say on this post false or not? http://ubuntuforums.org/showthread.php?t=1387046 [18:09] adrenalink, so it's better for us to drop what we are working on and answer questions that you could just as easily find out for yourself [18:11] adrenalink, i think the person was trying to be funny. there is nothing that says you can't build your own kernel and use it [18:11] bjf: you're in reason on this. But consider also that more people know (quickly) about something, more people can help about that! [18:12] bjf: ok. I was trying to find this famous "terms of service"... :D [18:14] adrenalink: you can use make deb-pkg together with the kernel-config of your installed kernel [18:16] dileks: which are the advantages of creating a .deb for my kernel? (i usually do not use it) [18:16] easier install/remove [18:19] dileks: on installation I need a simple make install [18:19] uninstalling require removing the images and config from /boot and eventually /lib/modules/kernelversion modules [18:20] so you seem to know what to do [18:20] it is clearly faster to remove a .deb .... [18:21] (it is not in doubt..) [18:21] but this is not so a great thing [18:21] you forgot include $mykernel into $bootmanager [18:21] (dileks: correct me if I'm wrong..) [18:22] https://github.com/lll-project/kernel/wiki/kernel_build_instructions -> "the normal way" [18:22] yes, of course! updating grub/lilo [18:22] a wiki I have written when building upstream-linux with clang [18:27] returning on the problem of ubuntu kernel... [18:27] ogasawara: (and others) yesterday I compile this ubuntu kernel source (after applying the patch) https://launchpad.net/ubuntu/+source/linux/3.2.0-23.36 with the config file i found in my ubuntu 12.04 distro (installed by iso) [18:28] the compilation took about 5 hours, generating me an initrd.img of about 122 MB !!! [18:28] see pointed wiki [18:29] I suspect something is not necessary in that image... [18:30] dileks: I would know why the image by the iso was about 14 MB, while the image for the same kernel but compiled by myself (with the same config file) is about 122 MB.. [18:30] * ogasawara lunch [18:30] ogasawara: good lunch! XD [18:30] and thanks for all the fish.. [18:31] ;) [18:31] WARNING: With CONFIG_DEBUG_INFO=y the linux-image Debian package can have a huge filesize (minimal kernel-config: >=40MiB vs. >=8MiB without debug-info)! [18:38] dileks: thanks! I'll try without it. But I can't understand why in the config file that comes with ubuntu iso CONFIG_DEBUG_INFO is set to yes (but the kernel image is small...) [18:41] moreover it seems to me that it is not the real problem, because during compilation I noted a lot of driver compilation that weren't useful for my system, so I suspect the config file is too generic for my system. [18:44] but again: [18:44] 1) I can't understand why the same config file has generated a small image with the "ubuntu iso", while compiling by myself it generate a kernel image greater than 120 MB. [18:44] 2) How can I set by myself the necessary flags without trying them one by one until my system works? [18:49] if you wanna play with a highly customized kernel - plug-in all hw you use, load all modules you want and create a new kernel-confog with make localmodconfig [18:50] this will give you a "minimal" kernel-config [18:50] ...and reduce build-time [18:51] dileks: what "plug-in all hw you use" means for a PC machine? [18:51] for example [18:52] I wanted to load pics from my sd-card [18:52] forgot to enable vfat-fs [18:54] I think I'm not so skilled about this field... [18:54] yupp [18:55] thus trust the experts and use the distro kernel-config [18:56] I aim to understand something about it, so I can't trust on somebody else, because I want learn! [18:57] can you give me any reference about the make localmodconfig prerequisites? [18:57] (what I have to set/plug-in before that command...) [18:57] its shipped with the linux-kernel kbuild-system [19:00] ok. thanks for all the references and answers. [19:00] stay tuned for next questions XD === lifeless_ is now known as lifeless [19:37] * cking -> EOD