=== sconklin is now known as sconklin-away [04:24] I think I found a bug in 2.6.31-xx-powerpc, but I want to make sure its a bug (and not my own stupidity). [05:52] hey guys.. if i have kernel 2.6.32-16-generic [05:53] and i want to test something with the mainline kernel [05:53] which one from... [05:53] http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=D;O=A [05:53] should i get? [06:26] holstein: meaning which one most closely is the basis? [06:26] holstein: 2.6.32.9 would be the closest [06:26] http://kernel.ubuntu.com/~kernel-ppa/info/kernel-version-map.html [06:26] yup [06:26] i should have said [06:27] i got linked the map over in #ubuntu+1 [06:27] my timing is spectacular :-) [06:27] hehe [06:27] but it would also be worth testing 2.6.33 === Hedge|Hog is now known as Hedgehog === Hedgehog is now known as Guest99513 === Hedge|Hog is now known as Hedgehog === Hedgehog is now known as Guest33956 === Hedge|Hog is now known as Hedgehog === Hedgehog is now known as Guest83325 === Hedge|Hog is now known as Hedgehog === Hedgehog is now known as Guest30693 === sconklin-away is now known as sconklin [22:37] Hi! I'm using Debian Squeeze's kernel to boot Ubuntu 9.10's DomU (cause that is the only kernel that works with Xen for me so far). If I were to use Debian Squeeze's initrd, I get this error: "No filesystem could mount root, tried:", "Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)". I suspect that that was caused by Ext-4 FS used on Ubuntu 9.10. I'm now trying to use Ubuntu 9.10's initrd, but copy Debian Squeeze's [22:37] initrd's lib/modules/2.6.32-trunk-686-bigmem directory into my Ubuntu-based custom initrd. I'm still getting the same error. Is there any tips if my approach can work and what other steps I need to carry out before it will work? [23:24] dyek: which 9.10 kernel specifically? [23:25] jjohansen: initrd.img-2.6.31-16-generic. [23:27] jjohansen: Debian Squeeze's vmlinuz-2.6.32-trunk-686-bigmem kernel, though, works with Xen (3.4.2 -- rather recent version.) [23:27] err modules in, lib/modules/2.6.32-trunk-686-bigmem won't work with a 2.6.31-16 kernel [23:28] ext4 should be builtin to the 2.6.31-16 kernel [23:29] jjohansen: OK. So, kernel module can never be moved to another minor version of kernel? Or with just a minor version difference, there is some chance that a kernel module will work with another kernel? [23:29] generally no, its based off of the abi [23:30] when building a kernel an abi "signature" is created and that has to match [23:30] so even just changing config options can result in a kernel that needs different modules [23:31] jjohansen: OK. So, the signature is the key! Thanks! ... I was told that "unknown-block(0,0)" means missing hdd-driver not FS. [23:31] dyek: right that is probably the hdd driver [23:32] but you mentioned 9.10 ext4 above [23:32] have you tried a lucid kernel? [23:32] its 2.6.32 based, and karmic will run ontop of the lucid kernel [23:33] jjohansen: Yeah...I could only guess as I don't understand enough. Lucid kernel? Any pointer to it? [23:34] https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-kernel-decision [23:35] http://packages.ubuntu.com/lucid/admin/ [23:35] look for linux-image [23:35] or you can grab the source from the git tree [23:36] Thanks! [23:38] http://lxr.linux.no/#linux+v2.6.33/Documentation/x86/boot.txt [23:38] Protocol 2.10: (Kernel 2.6.31) Added a protocol for relaxed alignment beyond the kernel_alignment added, new init_size and pref_address fields. Added extended boot loader IDs. [23:39] jjohansen: Do you think if this change could be why I had problems booting 2.6.31 as Xen DomU? (And that maybe it is fixed in 2.6.32?) [23:40] dyek: unlikely [23:41] OK! Thanks!