[00:40] <openfly> question.  using maverick kernel 2.6.35-30.58 with ixgbe driver 2.0.62-k2 i get like 2.8 gbit throughput from kvm instances
[00:41] <openfly> but upgrading to 3.4.24 ixgbe with NAPI enabled
[00:41] <openfly> i get like 80 mbit
[00:41] <openfly> anyone got any ideas on why that may be?
[01:40] <philipballew> hey I found a bug. ubuntu 10.10 and 11.04 will not restart
[07:21] <smb> morning
[07:22] <cking> morning smb
[07:23] <smb> cking, Early start today?
[07:23] <cking> smb, normally up at 8am nowadays
[07:23] <smb> sounds ghastly... :)
[07:24] <cking> needs must
[07:27] <_ruben> up at 8am .. the luxory :/
[07:28] <smb> sounds like having kids... :-P
[07:28] <FreezingCold> What does Ubuntu compile in the kernel by default?
[07:29] <diwic> does bjf run a script that automatically marks things new -> confirmed? 
[07:29] <jk--> FreezingCold: you can view the config options in /boot/config-$(uname -r)
[07:29] <smb> diwic, I think that is a bot doing things based on apport feedback
[07:30] <_ruben> smb: just one ;)
[07:30] <FreezingCold> jk-: For things like the LiveCD though, don't they have to have everything compiled already...?
[07:30] <diwic> smb, it's just surprising to find bjf being reported as the "changer" (see bug 832552)
[07:30] <ubot2> Launchpad bug 832552 in linux "Network problem - some pages load extremely slow" [Undecided,Confirmed] https://launchpad.net/bugs/832552
[07:31] <jk-> FreezingCold: no, they can still use modules. It needs to be compiled, but not necessarily *compiled-in*
[07:31] <jk-> (modules are still compiled on the CD image)
[07:31] <FreezingCold> All the modules are compiled?
[07:32] <smb> diwic, Usually things start being done in the name of whoever develops the scripts. Which is the user who runs them then. At some point it may be good to change it to a distinquishable bot name
[07:32] <diwic> smb, okay
[07:33] <smb> diwic, But I guess that way Brad gets to know when the scripts went wrong
[07:34] <smb> FreezingCold, Very roughly anything that can be compiled as a module is done that way. Except things marked experimental. And there is a certain set of very commonly used things that gets built in
[07:34] <FreezingCold> smb: I thought some things had to be built in?
[07:34] <FreezingCold> What the main differerence from built in and module?
[07:35] <ohsix> if they have to, then the kconfig won't let you build it as a module
[07:35] <_ruben> modules can be unloaded/reloaded
[07:35] <_ruben> and only loaded when needed
[07:36] <smb> There was a time when loading a module had time penalties. And of course you need anything built-in that you need to access additional modules. That would matter ore when not using an initrd
[07:37] <smb> And a module driver only takes up memory when loaded. So the main kernel binary is smaller
[07:38] <ohsix> there was some scsi stuff that was really slow when not built as a module back in the day, dunno if that is still true
[07:38]  * apw yawns
[07:38] <smb> ohsix, I believe there was that for any modules
[07:38]  * smb waves to apw
[07:39] <ohsix> specifically ones that had to wait for stuff internally
[07:39] <smb> ohsix, Well I mean to load a module delayed the boot
[07:39] <apw> smb, i think one of the issues was the locking was terrible so if you loaded loads of them there was a huge linearisation of the boot
[07:40] <smb> Yeah, and more serial stuff which is now done in paralel too
[07:40] <apw> once they sorted that out there was actually possibility to paralleised the boot more using modules than if builtin
[07:41]  * smb thinks he and apw are saying the same in different words. But /me is not wake enough to tell immediately ... 
[07:41] <ohsix> to the endless entertainment of the people who still cargo cult rules of thumb like building everything in is faster
[07:43] <smb> Oh an probably one other exception being when user-space is not clever enough to try loading a module in case it is needed and there is no other hook to make it autoload...
[07:43] <smb> apw, right? ;)
[07:44] <smb> Doh! Guess apw left his machine to succumb to relatime...
[07:45] <apw> smb, modules> right
[07:45] <apw> smb, relatime> also right
[07:46] <jk-> hey smb & apw
[07:46] <smb> jk-, Hello man from (down)underworld... :)
[07:47] <jk-> heh, I just queued up some Underworld songs, too :)
[07:47] <smb> :D
[07:50] <smb> Grrr... "your bug has been marked as  a duplicate of bug y" (which you cannot see because lp won't let you (timeout)
[07:50] <apw> smb, you clearly didi not need to know
[07:51] <smb> Oh well, who needs any zeitgeist anyway...
[07:51] <apw> smb, who can say given i 1) cannot say it, and 2) have no idea what it does
[07:52] <smb> apw, and 3) there does not seem to be anything missing when it crashes (again)
[08:05] <FreezingCold> What's the safest way to restart OpenSSH?  I'm connecting over SSH btw.
[08:07] <apw> FreezingCold, i believe you can /etc/init.d/restart ssh when connected thought it and it doesn't restart the connected sessions ... but really you should test on a system you don't care about
[08:09] <jk-> apw: init.d is *so* last year
[08:09] <jk-> :P
[08:10] <smb> The challenge is to remember what has been converted and whatnot... :-P
[08:10] <apw> right ... indeed.  ssh probabally is
[08:10] <apw> and i've even mixed the two syntaxes havn't i
[08:10] <smb> apw, thinkso
[08:11] <smb> /etc/init.d/openssh restart
[08:11] <smb> oh no
[08:11] <smb> openssh is last year too
[08:11] <smb> So only /etc/init.d/ssh restart
[08:12] <smb> or restart ssh
[08:20] <diwic> apw, btw, the lack of hw volume sync when switching ports in pulseuadio, I think that is fixed now. Can you verify?
[08:21] <apw> diwic, i assume that is a pulse update yes ?
[08:21] <diwic> any 0.99.2 based one should do it
[08:23] <diwic> apw, ah sorry, it is not yet fixed
[08:23] <apw> diwic, ok the affected machine is dist-upgrading ...
[08:23] <apw> diwic, bah, thats annoying
[08:23] <diwic> apw, just asked upstream about it.
[09:15] <philipballew> my computer hangs on reboot but shutdowns fine. can someone help tell me whats wrong
[09:16] <apw> philipballew, it would help to know what sort of computer and which release
[09:24] <philipballew> well apw its on 10.04 10.10 11.04 and it is a emachine t6420
[09:24] <smb> philipballew, Have you tried https://wiki.ubuntu.com/BIOSandUbuntu#Reboot_Methods ?
[09:25] <philipballew> i should mention is shuts down fine
[09:25] <philipballew> just not re-boot
[09:26] <smb> power off and reboot are done differently 
[09:26] <apw> yep, as smb says that likely means a buggy bios and we need to try the alternative means of rebooting to see if any of them work
[09:26] <apw> if they do then the kernel can be quirked to use one that works
[09:27]  * apw adds emachines bios writers to his "first against the wall" list and then uses his fork-lift to return it to the shelf
[09:27] <philipballew> i ran reboot force, pci, efi and acpi
[09:27] <philipballew> you were the one apw a few weeks ago who told me to :)
[09:28] <apw> philipballew, could well be, i could never remember even 1% of the irc conversations i have, i'd need another fork-lift for my brain
[09:29] <smb> ever? :)
[09:29] <philipballew> haha, also my bios not wont detect my cd drives...
[09:29] <philipballew> ^ not buying a emachine again
[09:30] <philipballew> but that is irrelvent
[09:32] <philipballew> and well, as a ubuntu member and user i figured i should see if a bug needs to be reported
[09:34] <smb> I think pci, efi and acpi may be the first things to be broken. And I believe f(orce) is a modifier to be used with any. You may try t(riple fault), k(eyboard controller) or r(eboot vector) if you have not yet.. You see the rebooting message as the last thing on the console, right?
[09:35] <philipballew> when i reboot it has the xubuntu logo and the text on the screen saying how its shutting down proccess. then it says will now restart and then it hangs
[09:37] <smb> Right, so at least from the description it sounds like being right at the final point of triggering a reboot and that not working for some reason...
[09:38] <philipballew> exactly
[09:39] <smb> So for completeness, I would at least try the other three methods above...
[09:41] <philipballew> that means having to manually hold the power button down and risk hardware damage
[09:42] <smb> why?
[09:42] <smb> At that point you are mostly shut down
[09:43] <smb> Ok, there is a few more stop start cycles to the hard drive
[09:43] <philipballew> well i dont want to break the desktop if i dont have to i guess
[09:43] <philipballew> i might try to remove all pci devices to see if any were causing the problem to
[09:44] <philipballew> not sure if thats messessery
[09:45] <philipballew> *nessessery 
[09:45] <smb> Maybe an last resort  option. Actually, is that a desktop machine (not a laptop / netbook). Just wondering whether they do not have reset buttons...
[09:45] <smb> (just to avoid the power off)
[09:46] <philipballew> its a desktop
[10:05]  * apw thinks that taking the entire macine appart to see if its the cards is more likely to break it than powering it off acouple of times
[12:47] <ashwinipatankar> I need to change the parameter of /proc/sys/fs/mqueue/* , any way to do that  ? specially msgsize_max
[13:12] <tgardner> apw, do you remember the system tap config option ? bug #832606
[13:12] <ubot2> Launchpad bug 832606 in linux-ti-omap4 "Build dbgsyms for use by systemtap" [Undecided,New] https://launchpad.net/bugs/832606
[13:12] <tgardner> cking, ^^
[13:15] <tgardner> ah, its not just one option. CONFIG_RELAY, CONFIG_DEBUG_FS, CONFIG_DEBUG_INFO, and CONFIG_KPROBES
[13:16] <cking> I've no idea what's required to build it
[13:16] <cking> bit lame, sorry
[13:16] <tgardner> cking, it turns out to require a number of options.
[13:16]  * cking hopes it does not add much bloat
[13:17] <tgardner> cking, its stuff we already have enabled.
[13:17] <cking> ah
[13:26] <tgardner> ogasawara, 'Review non-modular modular table'. wtf is that ?
[13:31] <ogasawara> tgardner: https://wiki.ubuntu.com/KernelTeam/Specs/KernelOneiricConfigReview#Non-modular_modules
[13:32] <tgardner> ogasawara, ah. the description cause a short circuit in my logic path somewhere
[13:33] <ogasawara> tgardner: basically the list of modules which should be =m but are not so need review as to why
[13:35] <ppisati> tgardner: i'm on it, and it seems everything is already there
[13:35] <ppisati> tgardner: some sample scripts i'm using work
[13:35] <ppisati> tgardner: but i had a failure with something that was supposed to work
[13:36] <tgardner> ppisati, you're referring to systemtap ?
[13:42] <herton> tgardner: it seems the patch for CVE-2011-2699 isn't applied on maverick master-next
[13:42] <ubot2> herton: ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem.  When the candidate has been publicized, the details for this candidate will be provided. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2699)
[13:42] <tgardner> herton, checking
[13:45] <brendand> sconklin - hi
[13:45] <apw> tgardner, i suspect you didn't push maverick ... meant to mention it
[13:45] <sconklin> brendand: good day, what's up?
[13:45] <brendand> sconklin - quick talk about the two up-coming kernels
[13:45] <ppisati> tgardner: yep
[13:45] <sconklin> yeah, go ahead
[13:46] <apw> tgardner, sounds like you got to the bottom of the systemtap thing
[13:46] <brendand> sconklin - we have a resourcing problem next week, in that one lab will be unmanned all of next week, as our engineers there are sprinting in london
[13:47] <tgardner> herton, pushed
[13:47] <herton> ack
[13:47] <brendand> sconklin - so we need to make a decision on whether to test like, tomorrow
[13:47] <brendand> sconklin - at the very latest
[13:48] <sconklin> brendand: you need to make a decision by tomorrow about whether to test when? Next week?
[13:48] <sconklin> Is next week unavailable in any case?
[13:49] <sconklin> Are you saying that the only opportunity to test is the rest of this week?
[13:50] <brendand> sconklin - essentially, yes
[13:50] <sconklin> Current status is here: http://people.canonical.com/~kernel/reports/sru-report.html
[13:50] <brendand> sconklin - yeah, i see there are 3 bugs still to be verified for both of them
[13:50] <sconklin> there are three bugs requiring verification. The same three for Lucid and Maverick.
[13:51] <sconklin> They will probably not be verified by tomorrow. However, if testing resources exist now and won't next week, you could test on the hope that verification will pass on all these (and I think it will)
[13:52] <brendand> sconklin - that's going to be the plan. if you need to respin, then i'm afraid there'll be a delay in getting cert testing done. let's up it all works out
[13:52] <brendand> s/up/hope/
[13:53] <sconklin> brendand: no, I think that's a good plan as long as it's ok to parallelize the tasks a bit. And if we have to respin, we'll just have to wait. 
[13:54] <sconklin> let me make sure the latest Lucid respin is actually in -proposed
[13:56] <sconklin> brendand: yes, Lucid in -proposed is good
[13:57] <lamont> ValueError: invalid literal for int() with base 10: '173-updates'
[13:57] <lamont> wtf.
[13:58] <apw> lamont, that doesn't look like a valid number to me, it has letters in it
[13:59] <ogasawara> bug 825259
[13:59] <ubot2> Launchpad bug 825259 in nvidia-common "File "/usr/lib/python2.7/dist-packages/NvidiaDetector/nvidiadetector.py", line 87, in __get_value_from_name v = int(name) - ValueError: invalid literal for int() with base 10: '173-updates'" [High,Fix released] https://launchpad.net/bugs/825259
[13:59] <lamont> and  yet, that would be why dist-upgrade fails.
[13:59] <lamont> bah.  stale mirror? ogasawara ?
[13:59] <ogasawara> lamont: was fixed last week I believe?  possibly a stale mirror.
[14:00] <apw> or you need to update nvidia-common first then dist-upgrade
[14:02] <lamont> ogasawara: only I'm running an oneiric kernel on a natty system
[14:02] <lamont> so no new nvidia-common
[14:03] <bobweaver> Hi there I was wondering what kernel is the most stable at the time ? 
[14:04] <apw> bobweaver, the latest in -updates in each series is normally the most stable we know of
[14:04] <ogasawara> lamont: hrm. could possibly ping tseliot to see if the fix is SRU'able.
[14:05] <bobweaver> apw:  I install nre kernel 3.0 and it is not stable so I want to install new one off mainline and would like to know what you think 
[14:05] <lamont> ah, right.  I'm running oneiric kernel because of r8169 being a great way to not run natty
[14:06] <bobweaver> I am running 10.10 
[14:06] <apw> bobweaver, i use the latest natty kernel on my natty boxes, which is where i am where i need stability
[14:06] <tseliot> ogasawara, lamont:  nvidia-173-updates is available only in oneiric, no wonder the nvidia-common in natty fails on dist-upgrade. I think we should SRU it
[14:07] <lamont> tseliot: I fully support this idea
[14:07] <lamont>             try:
[14:07] <lamont>                 v = int(name)
[14:07] <lamont>             except ValueError:
[14:07] <lamont>                 v = 0
[14:07] <lamont> ^^ because that is a horrible workaround
[14:08] <bobweaver> I tryed switching to 2.6.38-02063808-generic and nvidia has troubles ctrl+alt+f1  does nothing and also when I install nvida driver pymouth splash wont work 
[14:08] <lamont> tseliot: and to further confuse things for you, nvidia-173-updates is not installed  on the machine
[14:08] <tseliot> lamont: I'll backport it. Can you add the dist-upgrade use case in the bug report, please? (so as to support the SRU)
[14:09] <lamont> sure
[14:09] <tseliot> lamont: I know, it's enough to have it available in the apt cache, there's no need to have it installed any more
[14:09] <apw> oh so having src from a newer series would bite you ?
[14:10] <tseliot> yep
[14:10] <bobweaver> andy I am a n00b kinda lost 
[14:10] <lamont> tseliot: in the apt cache, with a priority of 60, fwiw
[14:11] <tseliot> apw, lamont: this is how we do hardware detection now for Jockey
[14:11] <lamont> tseliot: is it just nvidia-common that I need to grab from oneiric to make my machine truly happy atm?
[14:11] <tseliot> lamont: yep
[14:11] <apw> bobweaver, i am unsure why you are on all these odd versions in the first place.  it wouldn't be something we do a lot of, we only use them for testing
[14:12] <bobweaver> ohh cool
[14:12]  * apw bitches at tgardner as his build is crawling along
[14:12] <tgardner> apw, gomeisa ?
[14:12] <bobweaver> out of the main line what one would you choose 
[14:12] <apw> tgardner, yep, so either your parallel build code is bust, or you are killing the machine
[14:13] <tgardner> apw, its burying things, but it'll be done in 10 minutes
[14:13] <apw> tgardner, bah why is my build not getting a fair shake i wonder
[14:13]  * lamont finally reboots
[14:13] <tgardner> apw, dunno, but dpkg-buildpackage seems to have some magic that really thumps things.
[14:14] <apw> seems you have 3x the processes that i do, odd ... but the machine is really struggling under a high but not outragous load
[14:15] <tgardner> apw, I can drive tangerine into triple digits
[14:17] <photon> hi. I'm on 10.04 LTS, I manually updated my kernel to 2.6.38-something. Synaptic shows that Canonical provides only updates until October 2011 for that kernel. Is this a bug?
[14:17] <photon> Shouldn't it support the kernel until 2013?
[14:17] <apw> photon, which kernel did you install ?  where did you get it?
[14:18] <smb> apw, Do we maybe say lts backport kernels are only supported until the next one gets out?
[14:19] <bobweaver> I will try 2.6.9.2 now lastest natty one hope that that works 
[14:20] <apw> smb, the backport kernels are supported for servers currently up to the next LTS on approved hardware, is my understanding
[14:21] <photon> apw: sudo apt-get install linux-image-2.6.38-10-generic
[14:22] <photon> apw: in Synaptic it shows Canonical provides critical updates for linux-image-2.6.38-10-generic until October 2011.
[14:22] <photon> apw: I thought this kernel is used in 11.04, for which support does not run out this October, does it?
[14:23] <apw> photon, ok thats not an official kernel for the LTS and therefore it is likely getting an 18m lable by default
[14:24] <photon> apw: does this mean I *will* get security updates for this kernel after October and this is just a default label with no meaning? Or do I need to get a different kernel to have longer support?
[14:24] <apw> photon, to install a backports kernel you should be using 
[14:24] <apw> o
[14:24] <apw> bah
[14:25] <bobweaver> sudo dpkg -i linux*
[14:25] <bobweaver>  bob crosses fingers 
[14:25] <apw> photon, to be using the right backports kernel you should be using the linux-lts-backports-natty meta package
[14:25] <apw> else you won't get any updates at all even if they are available
[14:26] <apw> they are only supported currently i beleieve for servers but they will be recieving -security updates for that
[14:26] <photon> E: Couldn't find package linux-lts-backport-natty
[14:26] <apw> likely any support datage in synaptics is suspect
[14:27] <tgardner> photon, linux-image-server-lts-backport-natty
[14:27] <photon> install a server package on a desktop system won't break things?
[14:27] <apw> doh, yep
[14:27] <lamont> well then.
[14:28] <lamont> booting with certain usb drives plugged in causes the machine to take forever to boot, complaining about read errors...
[14:28] <tgardner> photon, it'll work fine, but you can also install linux-image-generic-lts-backport-natty
[14:28] <photon> ok, thanks, installing now.
[14:30] <tgardner> apw, despite your build annoyances (to me) it still completed in 15m9.060s
[14:31]  * apw has asked for clarification of the support dates from the powers that be, noting that synapics needs updating
[14:32] <photon> thank you apw. the backport-natty package is now installed. how should I continue? the newest kernel that is shown is still only linux-image-2.6.38-10-generic.
[14:33] <photon> or does the backport package simply ensure that I get updates even after October?
[14:33]  * photon is kind of new to this, apologizes.
[14:41] <photon> tgardner: are you still there?
[14:42] <tgardner> photon, have you rebooted ?
[14:42]  * photon rolls eyes
[14:42] <photon> brb
[14:58] <bobweaver> well that did not work nvida current wont even install now 
[14:58] <herton> tgardner, ppisati: I see we're missing cherry-picking commit 76597cd upstream for fsl-imx51 and ti-omap4 (maverick, natty) (the cve crasher fix)
[15:00] <bobweaver> what is pae ? 
[15:00] <bobweaver> compaired to mainline kernels 
[15:00] <bobweaver> ?
[15:00] <tgardner> herton, looking...
[15:02] <bobweaver> is it better to get kernel from synaptic or from mainline ? I cant seem to get just the right one nvidia-current either wont install or installs then ctrl+alt+f123456 dont work 
[15:03] <bobweaver> just not my day today I guess 
[15:04] <bobweaver> I guess I will try 3.0.3-030003 now 
[15:05] <bobweaver> cant belive it is this unstable 
[15:05] <bobweaver> or that noone will tell me which one is the most stable for 10.10 
[15:06] <bobweaver> nvidia-current (260.19.06)...                                                                      [fail] 
[15:06] <bobweaver> great 
[15:07] <bobweaver> oh this gets better 
[15:08] <bobweaver> all  nouveau are now not working and I lost xsession 
[15:08]  * bobweaver turns green 
[15:22] <apw> bobweaver, why are the official kernels not good enough?  
[15:23] <apw> bobweaver, and i have told you, the ones in the archive are the most stable those in -updates
[15:23] <apw> bobweaver, you are installing what seem like mainline kernels, which are even labelled as of unknown quality and for testing only
[15:24] <bobweaver> andy that is the only way that I know how to do it 
[15:24] <apw> if they break you get to make little sculptures with all the little shiney pieces
[15:24] <bobweaver> I try synaptic but it crashes  
[15:24] <apw> bobweaver, but what is it you are trying to do
[15:25] <bobweaver> install a stable kernel 
[15:25] <bobweaver> that can handle nvidia 
[15:25] <bobweaver> current 
[15:25] <apw> well all of the -updates kernels have paired up nvidia drivers, ones which ahve been tested
[15:25] <bobweaver> it fails every time 
[15:26] <apw> well that is a little out of our expertise.  i am not sure random kernels from god knows where is going to help any
[15:26] <bobweaver> or when it dont fail ctrl+alt+f1 dont work 
[15:26] <bobweaver> I need that 
[15:26] <bobweaver> ctrl+alt+f1 
[15:27] <bobweaver> maybe I am not installing right 
[15:27]  * ogasawara back in 20
[15:27] <bobweaver> this is how I do it 
[15:27] <bobweaver> douwnload the three files 
[15:27] <bobweaver> mkdir name 
[15:27] <bobweaver> cd name 
[15:27] <bobweaver> cd ..
[15:27] <bobweaver> opps 
[15:27] <apw> yeah but if you want the latest official kernel you should be able to get that using update-manager
[15:28] <apw> does update-manager not work for you?
[15:28] <bobweaver> sudo mv three files to name 
[15:28] <bobweaver> cd name 
[15:28] <bobweaver> sudo dpkg -i linux*
[15:29] <bobweaver> I see that there are patches on the mainline page do I have to put them in the folder when installing kernel ? 
[15:29] <apw> that is a reasonable command set to install a non-standard kernel, but you want a stable supported one right?  those don't come from the mainline kernles page
[15:29] <bobweaver> ohh thanks 
[15:29] <bobweaver> How do I use update manager 
[15:29] <bobweaver> to do this 
[15:30] <bobweaver> sudo apt-get update && sudo apt-get upgrade ??
[15:30] <apw> update-manager installs the latest and greatest of everything ... thats its job
[15:30] <apw> there is a command 'update-manager'
[15:30] <apw> if you do manual updates you are in riskier territory
[15:30] <bobweaver> not installed 
[15:31] <bobweaver> installing 
[15:31] <apw> how on earth have you manaaged to not have update-manager !?!  this is not a normal install (any more)
[15:31] <bobweaver> ob@bob:~/Downloads/3.1$ update-manager 
[15:31] <bobweaver> The program 'update-manager' is currently not installed.  You can install it by typing:
[15:31] <bobweaver> sudo apt-get install update-manager
[15:31] <bobweaver> bob@bob:~/Downloads/3.1$ sudo apt-get install update-manager
[15:32] <bobweaver> it si kubuntu 
[15:32] <bobweaver> might have something to do with it ?
[15:32] <apw> maybe no idea what you are meant to do there :(
[15:33] <bobweaver> says I have to reboot brb 
[15:33] <cking> apw has enough fun with unity
[15:33] <bobweaver> thanks for helping me bro 
[15:33]  * apw looks up the word fun just to be sure
[15:33] <smb> must be the kind of fun where you bedn over
[15:35] <cking> ho ho
[15:39] <bobweaver> ok installed update manager launched it and it says that there is no updates to install 
[15:39] <bobweaver> Oo
[15:42] <bobweaver> question do I have to uninstall all kernels that I have from main line. then install one from say synaptic then update-grub then try up-date manager again 
[15:43] <apw> bobweaver, now i am confused as to where you are, what kerenls do you have installed, perhaps pastebin the list 
[15:43] <bobweaver> sure 
[15:45] <bobweaver> http://paste.ubuntu.com/673917/
[15:46] <bobweaver> that is update-grub
[15:46] <bobweaver> let me know if you want to see any thing else 
[15:47] <bobweaver> right now I have loaded 3.1.0-0301rc2-generic
[15:47] <apw> bobweaver, so you don't have a single official kernel at all ?
[15:47] <bobweaver> no 
[15:47] <bobweaver> I removed it 
[15:47] <apw> because it didn't work?
[15:47] <bobweaver> when I had the bright idea to install 3.0 
[15:48] <bobweaver> no there was a nvidia bug 
[15:48] <bobweaver> could not use ctrl+alt+f1 or f2 or f3 ect 
[15:48] <bobweaver> to drop gui 
[15:48] <apw> using nvidia or nouveau ?
[15:49] <bobweaver> nouveau for when I cant load nvidia 
[15:49] <bobweaver> nouveau is deafult right ? 
[15:49]  * apw tries to remember if nvidia drivers do c-a-f1 or not
[15:50] <bobweaver> use to work 
[15:50] <bobweaver> untill I re-install 
[15:50] <bobweaver> lspci -nn | grep VGA 
[15:50] <bobweaver> 02:00.0 VGA compatible controller [0300]: nVidia Corporation C77 [GeForce 8200M G] [10de:0845] (rev a2)
[15:51] <tgardner> apw, pushed 'UBUNTU: [Config] Restore prepare-% target' to oneiric
[15:51] <apw> tgardner, thanks :)
[15:51] <tgardner> apw, read the commit log, yuo'll enjoy my bit of english prose.
[15:52]  * apw suspect that #ubuntu-x might have some ideas on the nvidia side of issues
[15:52]  * apw wonders how we ever coped before distributed vcss came on the scene
[15:53] <apw> tgardner, shouldn't that be w*nkers ?
[15:53] <smb> and what is preapre ? :-P
[15:53] <tgardner> apw, I thought that might be a bit obscene in some cultures. tossers is just understated enough...
[15:54] <tgardner> smb, argh! mis-spelling. well, it'll just have to remain.
[15:55] <smb> Its not as I would not be able to parse, but the opportunity to ask was just too sweet.
[15:56] <apw> tgardner, heh but so not very british :)
[15:56] <apw> would you like some scones ?
[15:56]  * smb would like some ice-cream...
[15:57] <tgardner> apw, I thought tossers and w*nkers were related ?
[15:57] <bobweaver> Once again I would like to say thank you so much for helping me. See I did not even know the difference between main line and the other one that you pointed out. Thank You again 
[16:01]  * herton -> lunch
[16:10] <jjohansen> rebooting
[16:44] <bobweaver> apw:  Andy you are the greatest man everything is working so good right now 
[16:44] <bobweaver> used synaptic to get kernel 
[16:45] <bobweaver> then removed all others from mainline 
[16:45] <bobweaver> rebooted and installed nvidia reboot again and everything I mean everything works 
[16:45] <bobweaver> I can not thank you enough 
[16:45] <apw> bobweaver, sounds good.
[16:45] <bobweaver> you made grey water turn clear 
[16:50] <bobweaver> maybe one day I can return fav to you or someone else 
[17:03] <cking> send apw a beer ;-)
[17:39]  * tgardner --> lunch
[19:15] <herton> seems I'm completely blind today, just ignore my 'adding to CCs' messages...
[20:27] <apw> herton, happens, only really embaressing when someone upstream is on there
[20:53]  * herton -> eod