[01:32] <aboSamoor> any help with the booting, I have more than a minute booting !
[01:36] <Ravenkin> I can't even boot, the update nuked something, there's nothing in boot folder so I can only imagine that's it, can anyone help?
[01:40] <amason> Ravenkin: this with Karmic ?
[01:40] <Ravenkin> Yes amason
[01:42] <amason> you may be able to grab one of the mainline kernels.
[01:42] <amason> boot from a live cd
[01:42] <amason> then chroot into your partition with /boot on it
[01:42] <Ravenkin> I tried booting from a live cd and sticking a kernel from this version of linux into and and it didn't work
[01:42] <amason> and install the kernel
[01:42] <Ravenkin> how do I install the kernel into it?
[01:43] <amason> dpkg
[01:43] <Ravenkin> How would I do that though?
[01:43] <amason> i shoudl be more specific, you will need to mount your / and any other partitions needed for dpkg to function
[01:44] <Ravenkin> ok once I get it mounted what would I have to do?
[01:44] <Ravenkin> I know I can get it mounted I've done that once already, kind of a pain since it's encrypted, but once I get it mounted, then?
[01:45] <amason> chroot into it
[01:46] <Ravenkin> k?
[01:47] <amason> sorry, i am not a native english speaker. Which part are you having trouble with , I will attempt to rephrase the answer.
[01:47] <Ravenkin> I just don't know how to install a kernel once the drive is mounted, what is the command to do that?
[01:48] <amason> chroot
[01:48] <amason> you need to chroot into your mounted partition
[01:48] <amason> then use the dpkg command to install your kernel
[01:48] <Ravenkin> just type dpkg though?
[01:50] <amason> well no.
[01:51] <amason> dpkg -i
[01:51] <amason> the commands themselves are well documented
[01:51] <amason> i am just giving you the overall process of how you would go about getting a usable system
[01:51] <Ravenkin> thanks, you gave me a point to go off of
[01:52] <aboSamoor> amason: I have slow booting, I think it is still under development. how can I know when there is any progress so I can test mine and report any problem ?
[01:52] <amason> aboSamoor i don't know sorry. I am not a kernel developer.
[01:53] <aboSamoor> amason: ok, thanks :)
[01:59] <amason> I'm actually in the channel for assistance too =)
[02:39] <andersk> Is it known that the kernels in http://kernel.ubuntu.com/~kernel-ppa/ have been failing to build since 2009-09-15? 
[02:57] <amason> andersk: yeh
[03:52] <unixbomber> quit
[15:41] <rtg_> apw, are you still having fsck issues in your TZ? see comments on bug #427822
[15:41] <ubot3> Malone bug 427822 in linux "fsck says last write time in future" [Critical,Fix released] https://launchpad.net/bugs/427822
[15:44] <apw> rtg_ i haven't noticed them no
[15:45] <apw> hrm its not at all obvious which version those guys have
[15:46] <rtg_> apw, I was gonna ask 'em to blat version_signature
[15:46] <apw> yeah me too :)
[15:46] <apw> just checking the one who has a syslog
[15:46] <rtg_> apw, go ahead. I'm working on a linux-firmware issue
[15:46] <apw> ack
[15:47] <rtg_> apw, oh, speaking of which, I plan to collapse the linux-firmware repos into one, and just have a topic branch for each release.
[15:47] <apw> they are so similar i assume
[15:48] <rtg_> apw, quite
[15:48] <apw> and huge
[16:26] <rtg_> Keybuk, I'm thinking about reverting desktop to CFQ with the latest kernel patch 'sched: Disable NEW_FAIR_SLEEPERS for now'. Could you do a quick boot test with 'elevator=cfq' to see if boot times regress?
[16:27] <rtg_> you're sort of the rosetta stone for boot times
[16:27] <Keybuk> NOOOOOO!!!!!!!
[16:27] <Keybuk> seriously
[16:27] <Keybuk> leave it at deadline
[16:27] <Keybuk> lynx is the right time to experiment with this
[16:27] <rtg_> Keybuk, well, how about switching to CFQ after boot? I think its much better for my workload.
[16:28] <Keybuk> no!
[16:28] <Keybuk> seriously
[16:28] <Keybuk> we're seeing reports of performance improvements *across the board* with the switch to deadline
[16:28] <Keybuk> cfq is just fucked
[16:28] <rtg_> Keybuk, agreed, but with 'Disable NEW_FAIR_SLEEPERS' it works a hell of a lot better,
[16:29] <Keybuk> deadline works just fine for now
[16:29] <rtg_> better then deadline, IMHO
[16:29] <Keybuk> let's revisit for the next release
[16:35] <kaushal> hi
[16:35] <kaushal> when i do sudo modprobe snd_hda_intel on jaunty desktop, I get FATAL: Error inserting snd_hda_intel (/lib/modules/2.6.28-15-generic/kernel/sound/pci/hda/snd-hda-intel.ko): Unknown symbol in module, or unknown parameter (see dmesg)
[16:35] <kaushal> any ideas ?
[16:36] <rtg_> smb_tp, ^^
[16:37] <smb_tp> kaushal, whats the dmesg?
[16:38] <smb_tp> And which kernel version?
[16:38] <kaushal> [  292.500775] snd_hda_intel: Unknown symbol snd_pcm_hw_constraint_step
[16:38] <kaushal> 2.6.28-15-generic
[16:38] <kaushal> smb_tp: shall i pastebin the dmesg ?
[16:38] <smb_tp> kaushal, yes, please :)
[16:39] <kaushal> http://paste.ubuntu.com/282250/
[16:42] <smb_tp> kaushal, could you also paste your uname -r and modinfo snd-hda-intel? Its odd that the module would be out of sync with the kernel...
[16:42] <kaushal> sure
[16:44] <kaushal> http://paste.ubuntu.com/282254/
[16:49] <kaushal> smb_tp: http://packages.ubuntu.com/search?searchon=contents&keywords=snd-hda-intel.ko&mode=exactfilename&suite=jaunty&arch=any
[16:49] <kaushal> doesnot exist for 2.6.28-15-generic 
[16:49] <kaushal> :/
[16:50] <smb_tp> kaushal, Not sure what the search should do but it should be in the linux-image-* package...
[16:52] <smb_tp> Hm your modules magic number is like mine (which loads). Just realised uname -r is not what I wanted. :-P sorry. Just post here the output of /proc/version_signature 
[16:55] <smb_tp> Oh, next thing to look at would be the filename and the srcversion line of modinfo snd
[17:00] <kaushal> smb_tp: sure
[17:01] <kaushal> Ubuntu 2.6.28-15.52-generic
[17:01] <kaushal> srcversion:     2C925CEA7D312E7FA6C0F00
[17:01] <smb_tp> kaushal, Ok, same here
[17:02] <smb_tp> but different version of snd
[17:02] <smb_tp> kaushal, Could your path be containing acore ?
[17:02] <kaushal> /lib/modules/2.6.28-15-generic/kernel/sound/acore/snd.ko 
[17:03] <smb_tp> As I guessed. Might you happen to have a self/externally compiled alsa ?
[17:04] <kaushal> smb_tp: i did install ii  alsa-driver-linuxant                 1.0.20.3                             ALSA driver enhanced for Conexant HDA modem support
[17:04] <kaushal> to configure modem on my laptop
[17:05] <kaushal> it used to work for -11 generic kernel
[17:05] <smb_tp> kaushal, That might be the source. If you can make it recompile, you might be fine. As I do not know the package, maybe just reinstall it
[17:06] <kaushal> reinstall alsa-driver-linuxant ?
[17:07] <smb_tp> yes. I guess it creates a duplicate version of the alsa core drivers. There might be a reconfigure command...
[17:07] <kaushal> ok
[17:08] <smoser> rtg_, around ?
[17:08] <smb_tp> kaushal, The same thing could happen each time you update the kernel. 
[17:09] <rtg_> smoser, yep
[17:09] <smoser> can you confirm or refute the following: linux-image-2.6.31-300-ec2 will only ever have version 2.6.31-300.3 . any subsequent packages for that image will have different package names.
[17:09] <smoser> (note, that current version is 2.6.31-300.3)
[17:11] <rtg_> smoser, your statement is imprecise. Subsequent updates may or may not have a new package name, depending on if the ABI number changes.
[17:11] <smoser> ok. then i say 'false' to the above statement.
[17:11] <rtg_> smoser, correct
[17:12] <smoser> the outcome of which is that I have to include the '.3' in a kernel name that i put on ec2
[17:12] <smoser> thank you.
[17:12] <rtg_> smoser, in as much as you want to reference the specific version, then yes. however, I do not recommend that.
[17:15] <smoser> rtg_, well, i have to. as i'm stuck in a namespace
[17:16] <smoser> ie, if there were ever a .4 version, then i want to upload it. and i can't replace the .3 version or it would break anyone using it.
[17:17] <rtg_> smoser, you mean a version update to an existing package? why would that break anyone using it?
[17:17] <smoser> if i push a new kernel to ec2, i would upload it to somewhere like:
[17:17] <smoser> canonical-us/ubuntu-kernel-2.6.31-300.3-ec2-x86_64
[17:18] <smoser> right now i have the '.3' in there. if i remove it, a subsequent upload would overwrite that.
[17:18] <rtg_> smoser, pretty much like doing a 'apt-get -u dist-upgrade'
[17:18] <smoser> you can't replace a file because it has external information pointing to it (the "aki")
[17:19] <smoser> so, quick overview:
[17:19] <smoser> that path above is an s3 path (amazon storage)
[17:19] <smoser> s3 is used to store files that are used as kernel, ramdisk, or images for ec2
[17:20] <smoser> a file is registered with ec2, and is given a globally unique image id (aki-80a84be9)
[17:20] <rtg_> smoser, so, it sounds like you have to be name as well as version specific.
[17:20] <smoser> if i subsequently replace the file , then anyone using aki-80a84be9 will no longer be able to use it
[17:21] <smoser> because their tools will say "treason! someone is trying to swap your kernel!"
[17:21] <smoser> with obviously good reasons.
[17:22] <smoser> so, rtg_ you probalby have no care, but if i had to choose between:
[17:22] <smoser>   linux-image-2.6.31-300-ec2
[17:22] <smoser> and
[17:22] <smoser> oops
[17:22] <smoser> between
[17:22] <smoser>   linux-image-2.6.31-300-ec2.3
[17:22] <smoser> and
[17:22] <smoser>   linux-image-2.6.31-300.3-ec2
[17:22] <smoser> which would you pick? i think i lean towards the '.3' on the end rather than inserted into the middle.
[17:23] <rtg_> smoser, mox nix.
[17:23] <smoser> the other option is being possibly overly verbose:
[17:24] <smoser> ok. thanks for your time.
[17:24] <rtg_> smoser, np
[18:07] <akgraner> ogasawara, you're a rock star!!!  :-)
[18:08] <rtg_> akgraner, surely you're not just coming to that realization :) we've all known it for awhile.
[18:09] <akgraner> rtg_, oh I've known that  :-)
[18:10] <rtg_> akgraner, oh by the way, jjohansen muttered something about an AppArmor session during Open week
[18:10] <akgraner> rtg_, sweet... 
[18:11] <akgraner> just add it to the wiki..:-)
[18:11] <rtg_> akgraner, I'll annoy him to make sure he takes positive action.
[18:11] <akgraner> rtg_, great.. that way I don't have to annoy people... I have that skill perfected already...:-)
[18:11] <jjohansen> rtg_, akgraner: I was just doing that
[18:12] <akgraner> jjohansen, :-)  thanks you rock...  I don't care what rtg_ says ..:-)
[18:14] <akgraner> catch you all laters!!  Thanks a million!!!
[18:30] <rtg_> apw, until staging caTCHES UP, i'D SAY JUST DISABLE IT UNTIL ABOUT -RC2 OR -RC3
[18:30] <rtg_> damn keyboard
[18:30] <apw> heheh
[18:30] <apw> rtg ok
[18:30] <rtg_> CAN YOU HEAR ME NOW ?
[18:30] <apw> nope, my eyes are shot :)
[20:13] <rtg_> apw, what grub2 parameter was recently updated that stopped my server from auto-booting?
[20:17] <Keybuk> rtg_: noboot
[20:19] <rtg_> Keybuk, where? not in /boot/grub/grub.cfg or /etc/grub.d
[20:19] <Keybuk> sorry, that was me joking :)
[20:20] <rtg_> dude, you had me going.
[20:57] <jono> hey all
[20:57] <jono> rtg_, is https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/409361 on your radar?
[20:57] <ubot3> Malone bug 409361 in linux "Seeing drm:intel_dp_i2c_init errors on boot" [Low,Confirmed]