[03:12] Are there any issues with getting a generic (torvalds branch) kernel to work with 10.04? [03:14] shouldn't be - you can grab the autobuilt upstream kernels after all :) [03:16] lifeless: I was just trying to figure out why when I use it it can't find my root partition. I musta screwed up. I checked lscpi -k and everything is set right there. [03:16] lifeless: I was trying to mess around with 2.6.34-rc3 [03:17] I wish I had my generic .config I use with almost everything and it almost always works... [03:18] lifeless: thanks- I just wanted to make sure there wasn't anything funky that might be messing me up [14:16] hi [14:16] does an hang where the sysrq does not respond usually means a kernel freeze ? [14:25] yes, I think so. But I'm no kernel dev. [14:25] http://www.av8n.com/computer/htm/kernel-lockup.htm [14:26] I've been having such lockups when plugging in a USB stick: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/514485 [14:26] Malone bug 514485 in linux "kernel lockup when plugging in USB stick" [Undecided,New] [14:27] switched to Gnome now and haven't been able to reproduce it yet. === yofel_ is now known as yofel [21:34] I'm lost. I use the exact same config as what's in the generic kernel, but i still get a kernel panic on boot and an error about not being able to find sda2 (root=/dev/sda2) [21:41] * abogani waves [21:41] I'm looking for sponsors: https://wiki.ubuntu.com/AlessioIgorBogani/linux-rtPPUApplication [21:41] Thanks! [21:42] MTecknology: got initrd? [21:45] hyperair: is that a kernel option that I'm not finding? [21:46] MTecknology: No it is *mandatory* kernel installation step. [21:47] abogani: I've been taking the easy route - make all modules_install install && update-grub2 [21:47] MTecknology: Not enough [21:47] it has been for everything up until 10.04 [21:47] what changed? [21:48] MTecknology: Some modules are modularized for improve speed at boot [21:50] MTecknology: Could you see into /boot directory if you have the initrd.img-* file for you custom kernel? [21:50] there isn't [21:51] so I need to make the initrd.img* file [21:51] MTecknology: I use this: mkinitramfs -o boot/initrd.img-$VERSION $VERSION [21:54] Is there any way to see which modules are in the .img? [22:01] abogani: Is there any way to see which modules are in the .img? Or anything that says which modules were put in there to decrease boot time? [22:02] MTecknology: You should gunzip it and extract contents with cpio. [22:07] MTecknology: make-kpkg --initrd [22:08] i think there was something else you had to do [22:08] Sarvatt: ? [22:08] hyperair: AFAIK make-kpkg isn't supported on Ubuntu. [22:08] it isn't? [22:08] * hyperair has been using it all this time =\ [22:09] I thought initrd was just a collection of modules.. [22:09] nah [22:09] I was hoping I could just change things form =m to =y and not need to worry about initrd.img-* [22:09] initrd sets up things [22:09] I guess not [22:09] including usplash in karmic [22:10] and udev [22:10] hyperair is right. [22:10] there's a devfs option in the kernel you could use to avoid initrd though [22:11] I don't see devfs in there - or does it have a different name? [22:11] i forgot [22:11] CONFIG_DEVTMPFS [22:12] No CONFIG_BLK_DEV_INITRD [22:12] heh? [22:12] what's that? [22:12] Prompt: Initial RAM filesystem and RAM disk (initramfs/initrd) support [22:13] hyperair: Are you also in -motu? [22:13] hyperair: instead of making you look it up :) [22:13] abogani: yes i am. [22:13] abogani: why? [22:13] so if i disable those options it won't look for initrd? [22:13] hyperair: I recall your suggestions about my doubts about packaging so I would want thanks to you again. [22:13] er i have no idea [22:14] O_o [22:14] * hyperair doesn't remember.. [22:14] but yw anyway =) [22:14] MTecknology: Don't try it. You waste your time no one in Ubuntu have tested that way. [22:15] abogani: I can try it and then somebody will have :P [22:15] abogani: from looking at that - I could just cp initrd.img-2.6.32-19-generic initrd.img-2.6.34-rc3 - right? [22:16] * hyperair facepalms [22:16] that won't work. [22:16] hyperair: I'm sorry :( Don't hurt yourself over me [22:17] hyperair: I'm just a novice noob that likes mucking with things that have no business being mucked with [22:17] heh [22:18] well just use the initrd [22:18] what are you trying to achieve by dropping it? [22:19] nothing, I was just wondering if I could avoid making it by copying it [22:20] well, you know how kernel modules can't be used in another kernel? [22:21] initrds contain kernel modules, naturally they can't be used in another kernel [22:21] if you have no modules at all, then maybe it can be copied [22:21] oh [22:21] but anyway initrd is basically a temporary root [22:21] that bootstraps everything and then moves to the real root [22:22] what benefits are there in that? [22:23] hyperair: I'm not trying to say it shouldn't be there - I'm jsut curious what it offers [22:34] MTecknology: well, for stuff like lvm and cryptostuff, the kernel cannot boot directly using those as some setup needs to be done in userspace. [22:34] MTecknology: also, i'm sure you know that you can't fsck a filesystem while it's mounted [22:35] ya [22:35] ok, that makes sense [22:37] hyperair: so you could have your entire drive on one lvm volume and boot from it wtih initrd? [22:45] MTecknology: right. but you need /boot in ext4/ext3 or something supported by grub, for example [22:45] as long as the initrd can be supplied [22:47] hyperair: cool [22:58] hyperair: heh - I tried without initrd and the only issue with that /dev/mapper/cryptswap1 and lvm volumes won't mount, nee to run mount /home, mount /misc, etc. manually and there's no errors [22:58] heh, see? =p [22:59] MTecknology: besides, i think ubuntu's boot process is engineered around the fact that you have an initrd, so it might not work properly if you don't. [23:03] hyperair: I wouldn't even use lvm if I didn't have to deal with having windows on the drive [23:17] hyperair: nifty stuff [23:38] sysrq not responding indicates a kernel hang ?