=== truexfan81_ is now known as truexfan81
[04:06] <BradenBraden> in grub -> additional options, what is "upstart"?
[04:42] <ChibaPet> Hey all. I'm wondering what the general opinion of Xenial is in terms of stability. I know the official answer, but I'm curious about what folks running it think so far.
[04:42] <ChibaPet> I'm particularly interested in hearing about folks running it with root on ZFS, but any experiences are welcome. (I'm thinking about running it.)
=== nolsen is now known as GabeN
=== GabeN is now known as nolsen
[06:25] <CryptoSiD> ChibaPet running fine here
[06:26] <CryptoSiD> but im running it on a server, no X (gnome/kde/fce)
[06:26] <CryptoSiD> and no ZFS
[06:26] <ChibaPet> I've not really run Ubuntu much... Are we in a period of stabilization, or are there likely to be big changes left? Or mostly just fixing stuff leading to an RC?
[06:27] <CryptoSiD> https://wiki.ubuntu.com/XenialXerus/ReleaseSchedule
[06:27] <ChibaPet> I've run Debian for years and other stuff, so knowing how this compares to, for instance, Testing before a release would mean something to me.
[06:27] <ChibaPet> Yar, seen that, which is why I've taken an interest now.
[06:27] <CryptoSiD> I've also been running debian for years, I'm running both now, can't really tell the difference on server side
[06:27] <ChibaPet> I'm just not wholly sure how to interpret it all.
[06:28] <ChibaPet> I'll spin it up in a VM as a starter then.
[06:30] <CryptoSiD> I'd like to tell you but i dont really know either:D
[06:30] <ChibaPet> Oh, that's fine.
[06:31] <ChibaPet> I'm mostly deciding whether I want to focus on 14.04 or 16.04. I'm almost ready to swallow systemd.
[06:31] <ChibaPet> The presence of ZFS and the promise of a nice long time without having to upgrade make 16.04 kind of tempting.
[06:31] <ChibaPet> (Vendor-supplied, as it can be had otherwise anyway.)
[07:15] <BradenBraden> have 16.04 installed. have an optimus setup. installed the intel and nvidia drivers with nvidia-prime (tried drivers 340, 352 and 355). Works when I have prime-select intel but with nvidia, the login screen is just black (backlight working). any suggestions?
[07:17] <lotuspsychje> BradenBraden: did you enable performance mode in nvidia-settings?
[07:18] <BradenBraden> lotuspsychje, yes (it was selected by default after installing the drivers) but I didnt have the whole host of options available for the screen like I did when I had it all setup on 15.10
[07:19] <lotuspsychje> BradenBraden: did you try with opensource drivers also<?
[07:20] <lotuspsychje> BradenBraden: and did you clean install xenial or upgrade?
[07:20] <BradenBraden> did a clean xenial install from an image i downloaded last night. i currently have the 355 open source drivers installed.
[07:21] <lotuspsychje> BradenBraden: ok can you sudo apt-get purge nvidia and reboot please
[07:21] <lotuspsychje> lets test the opensource drivers before you file a bug
[07:21] <BradenBraden> give me a moment. must do it via recovery mode.
[07:21] <lotuspsychje> sure mate
[07:21] <BradenBraden> (it does work btw, when I do that. done it about 7 times so far lol)
[07:21] <lotuspsychje> right so we dont need to test then BradenBraden
[07:22] <BradenBraden> it loads with the intel drivers
[07:22] <BradenBraden> and they work
[07:22] <lotuspsychje> BradenBraden: i suggest you file a bug againt nvidia-355 then and also mention all other drivers
[07:22] <lotuspsychje> !bug
[07:22] <ubottu> If you find a bug in Ubuntu or any of its derivatives, please file a bug using the command « ubuntu-bug <package> » - See https://help.ubuntu.com/community/ReportingBugs for other ways to report bugs.
[07:22] <lotuspsychje> BradenBraden: i also suggest after you try 14.04.3 LTS
[07:23] <BradenBraden> lotuspsychje, Im only using Xenial because of the 4.3 kernel. Wily has the 4.2 kernel and my Elantech touchpad didnt work properly. It does now though (but graphics not so much lol)
[07:24] <lotuspsychje> BradenBraden: i really recommend you try an LTS for stability also, just to make sure of some stuff
[07:24] <BradenBraden> maybe I just get over it and use the intel drivers. I mean, everything works, and its not like I intend to play games or anything
[07:24] <lotuspsychje> BradenBraden: if your system has an nvidia card, you should at least be able to use it
[07:24] <lotuspsychje> kinda silly otherwise
[07:25] <BradenBraden> yea I use it in Windows when I game
[07:25] <BradenBraden> in nix, all I look at is the web, my IDE and code
[07:25] <lotuspsychje> BradenBraden: with that card you should be able to game nicely on ubuntu
[07:25] <lotuspsychje> BradenBraden: join the #gamingonlinx channel they pretty active there
[07:25] <BradenBraden> im sure, but the games I want to play arent available on linux yet
[07:26] <BradenBraden> doesnt matter anyway. nicer to have seperate environments for work and for play
[07:26] <BradenBraden> helps keep one focused
[07:26] <lotuspsychje> right
[07:27] <lotuspsychje> BradenBraden: so can you file that bug, help make xenial better and try LTS after you file the bug perhaps
[07:27] <lotuspsychje> it will make a big deal for all of us in april
[07:28] <BradenBraden> lotuspsychje, i believe it. but not going to 14.04. need the touchpad working and I really like gnome3.
[07:28] <BradenBraden> will look at filing that bug though
[07:29] <lotuspsychje> BradenBraden: im sure there's a way to fix your touchpad on LTS though
[07:29] <BradenBraden> well sausages... basically no gnome extensions are available for xenial... aaaaahhhhhhh gosh lol
[07:29] <lotuspsychje> xenial still in testphase mate, things can break
[07:29] <BradenBraden> yea i know
[07:30] <BradenBraden> who doesnt like living on the edge though? :P
[07:30] <lotuspsychje> hehe
[07:30] <lotuspsychje> im testing xenial on my desktop also
[07:31] <lotuspsychje> running pretty stable here
[07:32] <BradenBraden> hmm i wonder though... when I installed 15.10, the touchpad wasnt properly recognized. doing xinput showed something random like ELAN:0129:1092 or whatever. Now it shows "Elan Touchpad". I wonder if something just went a bit screwy during the Wily install
[07:32] <lotuspsychje> BradenBraden: im sure its an ACPI bug, thats why i recommend LTS and check on your syslog/dmesg
[07:33] <BradenBraden> ok lotuspsychje , since you insist on LTS lol. but quick question (or two) first. Will I be able to upgrade the kernel but keep LTS? or is it locked at a kernel version?
[07:34] <lotuspsychje> BradenBraden: well think of this way, if you install 14.04.3 few months later you can upgrade safely to xenial working with 4.4 kernel
[07:34] <lotuspsychje> im sure thatl fix alot of stuff
[07:34] <BradenBraden> so the answer is no then
[07:34] <BradenBraden> which means I will be stuck with gnome2 right?
[07:35] <BradenBraden> (or unity blegh)
[07:35] <lotuspsychje> BradenBraden: and yes you can also upgrade kernel on trusty aswell
[07:35] <BradenBraden> I can? all the way to 4.3?
[07:35] <lotuspsychje> think so
[07:35] <lotuspsychje> !mainline
[07:35] <ubottu> The kernel team supply continuous mainline kernel builds which can be useful for tracking down issues or testing recent changes in the Linux kernel. More information is available at https://wiki.ubuntu.com/Kernel/MainlineBuilds
[07:35] <lotuspsychje> read this
[07:37] <BradenBraden> lotuspsychje, hmm ok..
[07:38] <lotuspsychje> !kernel
[07:38] <ubottu> The core of Ubuntu is the Linux kernel: see https://help.ubuntu.com/community/Kernel - You shouldn't have to compile your own, and if you need to troubleshoot issues, you can try a !Mainline kernel instead, but if you insist, see https://help.ubuntu.com/community/Kernel/Compile (see also !Stages)
[07:38] <BradenBraden> yea not so sure about compiling it myself
[07:39] <lotuspsychje> BradenBraden: dont need to
[07:39] <BradenBraden> Will the LTS version play alright with Optimus arch?
[07:39] <lotuspsychje> BradenBraden: thats what we need to test on your card
[07:40] <lotuspsychje> all systems are different, hard to say in front
[07:40] <BradenBraden> ahh I'm a guinea pig. fun times :P
[07:40] <lotuspsychje> but LTS should at least give you stable times
[07:40] <lotuspsychje> if not==> bug
[07:40] <BradenBraden> right.
[07:40] <lotuspsychje> and make everyone happy
[07:41] <BradenBraden> copying the 14.04 image onto flash now to copy across
[07:41] <lotuspsychje> BradenBraden: cool, dont forget to enable internet + updates enable during setup
[07:41] <BradenBraden> ive formatted and installed linux about 8 times in the last week lol
[07:41] <lotuspsychje> lol
[07:41] <BradenBraden> lotuspsychje, yea not sure about the internet thing.
[07:42] <lotuspsychje> BradenBraden: you got cable mate?
[07:42] <BradenBraden> I always get hit with a Hard Block
[07:42] <BradenBraden> no cable. its a slim laptop
[07:42] <BradenBraden> although, it if supports tethering, I can use USB
[07:42] <lotuspsychje> ok
[07:42] <lotuspsychje> its important you get connected during setup
[07:43] <BradenBraden> hmm ok. i havent been connected for any of the installs ive done so far
[07:43] <BradenBraden> have to blacklist an asus module to get wifi working
[07:43] <lotuspsychje> BradenBraden: makes a big deail, letting ubuntu choose the best drivers
[07:43] <lotuspsychje> deal
[07:44] <BradenBraden> right
[07:44] <BradenBraden> only had 4 hours sleep last night. want to have this done by today else i'll have a sour weekend.
[07:44] <lotuspsychje> maybe LTS will sort that wifi by default?
[07:45] <BradenBraden> we'll see
[07:45] <BradenBraden> but ive noticed that even in the live session, airplane mode light comes on
[07:45] <lotuspsychje> BradenBraden: ok good luck mate
[07:45] <BradenBraden> i'll let you know how it goes.
[07:45] <BradenBraden> but since  this is now 14.04, i guess this is the wrong channel to be in
[07:46] <lotuspsychje> normally we have lot users working good with nvidia-prime+340 or 346+performance mode on
[07:46] <lotuspsychje> BradenBraden: yeah if you encouter trusty issues back to #ubuntu :p
[07:46] <BradenBraden> dont want daftykin to boot me into #ubuntu-lts or something :P
[07:47] <lotuspsychje> well i understand his frustration for details on issues
[07:47] <lotuspsychje> but lets move on calmly ok :p
[07:47] <BradenBraden> im game for that
[07:47] <lotuspsychje> great
[07:48] <lotuspsychje> ill be afk for a while, ilde as you wish ok
[07:48] <BradenBraden> cool
[07:48] <lotuspsychje> BradenBraden: others will help you on the trusty part also
[07:48] <BradenBraden> :)
[07:48] <lotuspsychje> cheers
[07:48] <BradenBraden> chau chau
=== BradenBraden is now known as BrazenBraden
[09:43] <nitesh`> Hello All
[09:43] <nitesh`> How do I find the right repo link for Ubuntu version 1604?
[09:48] <lordievader> nitesh`: It is the same as allways but with codename xenial, instead of, for example, wily.
[09:48] <nitesh`> lordievader: So I just need to copy the repo list from a ubuntu 1404(say), and replace the name as u said?
[09:55] <lordievader> Yes.
[10:00] <nitesh`> Hey, But I cant see the apt directory under /etc although I am the root . I assume I need to add the repo list in /etc/apt/sources.list.d/
[10:11] <nitesh`> lordievader: I dont have any other ubuntu installed to copy-paste its /etc/apt/sources.list.d/ and then replace the ubuntu verison name with xenial. Any other way to get it?
[10:17] <lordievader> nitesh`: Ubuntu repos are usually in /etc/apt/sources.list, sources.list.d is usually used for third party/ppa's.
[10:21] <nitesh`> lordievader: If some repos that belong to sources.list are put inot sources.list.d , does it matter?
[10:21] <nitesh`> I would follow the protocol, just asking out of curiosity
[10:21] <lordievader> No, it is just a matter of convention.
[10:21] <nitesh`> Okay
[10:31] <nitesh`> lordievader: In sources.list.d  directory, If I just create  a file with all the repo list of ubuntu 1404 and then replace the names with xenial, will ubuntu use this repo list while downloading pkgs
[10:32] <lordievader> Yes.
[10:32] <lordievader> Or at least if the priority is high enough.
[10:35] <nitesh`> Coz its still not working OR I am not doing it properly
[10:35] <nitesh`> root@Ubuntu1604:/etc/apt/sources.list.d# ls
[10:35] <nitesh`> repo.list
[10:35] <nitesh`> root@Ubuntu1604:/etc/apt/sources.list.d# sudo apt-get install vim
[10:35] <nitesh`> Reading package lists... Done
[10:35] <nitesh`> Building dependency tree
[10:35] <nitesh`> Reading state information... Done
[10:35] <nitesh`> Package vim is not available, but is referred to by another package.
[10:35] <nitesh`> This may mean that the package is missing, has been obsoleted, or
[10:35] <nitesh`> is only available from another source
[10:39] <nitesh`> lordievader: ^^
[10:40] <lordievader> nitesh`: Have you updated your sources? (sudo apt-get update)
[11:23] <nitesh`> lordievader: Worked :-)
[11:28] <lordievader> whoop whoop
[11:45] <lotuspsychje> !info linux-image-generic xenial
[11:45] <ubottu> linux-image-generic (source: linux-meta): Generic Linux kernel image. In component main, is optional. Version 4.3.0.5.6 (xenial), package size 2 kB, installed size 11 kB
[14:35] <phillw> Hi, I'm sure you are bored of this question, but will 4.4 kernel be in Xenial and, if so, when will it land in the daily spins for testing?
[14:44] <TJ-> yes it will, when testing is finalised
[14:48] <phillw> TJ-: is there any time scale for that re: https://wiki.ubuntu.com/XenialXerus/ReleaseSchedule Just to keep our testers 'in the loop' ?
[14:50] <TJ-> I've not seen specific mention of it, but mainline v4.4 was released 5 days ago. Ubuntu SAUCE needs rebasing and testing on top
[14:53] <phillw> TJ-: the sooner we (testers) get told, the sooner we can drum up more 'volunteers' to soak test it. We are good little borg drones :P
[14:56] <TJ-> I see b355d01d 2016-01-11 06:26:40 -0700 N Tim Gardner UBUNTU: rebase to v4.4
[15:19] <TJ-> probably 10 days or so, possibly earlier
[16:24] <phillw> TJ-: thanks, (sorry reboot required as I am running 16.04 in production). If it can land prior to 25th January that would be great as the Alpha 2 test cycle begins then for the flavours following the alphas and it would get a good testing scenario for real life.
[16:26] <TJ-> the kernel image itself is available for testing in the kernel-team unstable PPA repo
[16:28] <phillw> TJ-: for the testers, I do think having it in the daily spins on the iso tracker http://iso.qa.ubuntu.com/qatracker would be great, as that is geared up for tests and reporting anything 'odd'. I'm also happy to have the link to the ppa in order to grab the kernel, they have a very annoying habit of being stable these days :D
[16:31] <phillw> TJ-: http://www.ubuntuupdates.org/ppa/canonical_kernel_team does not show it... would you be so kind as to post up the link for it.
[16:32] <TJ-> "apt-add-repository ppa:canonical-kernel-team/ubuntu/unstable"
[16:34] <phillw> TJ-: " Cowboy builders all the way." ... I guess I have it correctly there. Good to see humour is still alive on here :)
[16:38] <phillw> TJ-: hmm... apt-get update && sudo apt-get upgrade
[16:38] <phillw> has not pulled it in, I dimly recall you need a slightly different command to pull in a new kernel.
[16:42] <TJ-> you'll need to specify the exact package name since it's not a regular dependency update via linux-image-generic
[16:44] <phillw> TJ-: sorry for being new to this, but http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D has no mentioin of Xenial. Where would I find the up to date kernel name in order to specify the exact package name ?
[16:48] <TJ-> phillw: that's not the correct place to be looking. You want the unstable PPA
[16:49] <TJ-> "apt-add-repository ppa:canonical-kernel-team/ubuntu/unstable" then "sudo apt-get update" then "apt list linux-image*" to get the list of available packages
[16:57] <phillw> TJ-: so I see the entry "linux-image-generic/xenial 4.4.0.0.2 amd64 [upgradable from: 4.3.0.5.6]" is it
[16:57] <phillw> sudo apt-get install linux-image-generic/xenial 4.4.0.0.2
[16:57] <phillw> ?
[16:58] <TJ-> phillw: it'll be something like linux-image-4.4.0.0-2-generic I'd expet
[17:06] <phillw> Oh the joys of dependency hell :)
[17:14] <phillw> he he.. I got linux-image-4.4.0-0-lowlatency as an added bonus :)
[17:16] <TJ-> I prefer -lowlatency for desktops
[17:17] <phillw> TJ-: piglet (is a laptop) and would have been called a "desktop replacement unit" back in the days when a multi processor machine with RAM that can happily run a couple of KVM instances :)
[17:18] <phillw> TJ-: btw, please accept....
[17:20] <phillw> TJ-: see you after the reboot..
[17:29] <lotuspsychje> !info gnome-software xenial
[17:29] <ubottu> Package gnome-software does not exist in xenial
[17:30] <lotuspsychje> anyone wanna test/bug out gnome software try this:
[17:30] <lotuspsychje> http://news.softpedia.com/news/gnome-software-now-available-in-ubuntu-16-04-with-a-ppa-498977.shtml
[17:43] <phillw> TJ-: new kernel does not play with network manager. I lost WiFi connection at a low level (as if I'd manually disabled it)
[17:43] <phillw> would the guys like a bug report?
[17:44] <TJ-> phillw: depends on which device, and whether you've got an out-of-tree driver installed for it. Also, could depend on having the correct firmware image which may have been updated (check dmesg or /var/log/kern.log for clues)
[17:56] <phillw> TJ-: I used synaptic package manager to sync things up (hence me having two kernels)
[17:57] <phillw> This is a bog standard HP machine, running 16.04 with the 4.3 kernel quite happily. So, something got fairly broken for 4.4 to lose internet.
[18:00] <phillw> TJ-: actually, that's a good point.... not something I'm used to seeing in *buntu, but each kernel has a firmware side-kick in RHEL. I'm surmising that it also needs to be installed?
[18:05] <TJ-> phillw: linux-firmware should already be installed, but there may be a more recent one to bring in additional firmware images for 4.4. check with "apt-cache policy linux-firmware"
[18:16] <phillw> TJ-: well, so much for that idea....
[18:16] <phillw> linux-firmware:
[18:16] <phillw>   Installed: 1.155
[18:16] <phillw>   Candidate: 1.155
[18:17] <TJ-> phillw: dmesg/kern.log/syslog are the places to look for indications of why the device hasn't initialised
[18:18] <phillw> TJ-: I'l fire up a KVM instance and see if it behaves on there. If it does, I'll come back to bare metal testing.
[18:19] <phillw> But, I do think it is a firmware issue..
[18:21] <TJ-> phillw: if there's a missing firmware the kernel will report it
[18:23] <phillw> TJ-: as I had a failure under 4.4, will the logs still be there after a reboot into 4.3, or do I have to capture them running 4.4?
[18:24] <TJ-> the /var/log/kern.log will have it, or if that also logrotates, it'll be in /var/log/kern.log.1
[18:25] <phillw> TJ-: I'm assuming that the kern.log will have what is needed?
[18:25] <phillw> phillw@piglet:/var/log$ ls -al kern*
[18:25] <phillw> -rw-r----- 1 syslog adm 613903 Jan 15 18:20 kern.log
[18:25] <phillw> -rw-r----- 1 syslog adm 655141 Jan  9 17:27 kern.log.1
[18:26] <TJ-> phillw: yes, you can see from the timestamps when they were last touched
[18:31] <phillw> TJ-: http://phillw.net/kern.log
[18:32] <phillw> sorry for delay, SEL in enforcing mode is a bitch some times to post something up :P
[18:33] <TJ-> LOL yeah, we persecute ourselves :)
[18:34] <TJ-> did you say the wifi lan wasn't up?
[18:34] <TJ-> ath9k module ... "Jan 15 17:39:54 piglet kernel: [   36.757303] wlan1: associated"
[18:35] <TJ-> maybe this has confused you? "[   24.619502] ath9k 0000:03:00.0 wlan1: renamed from wlan0"
[18:35] <phillw> TJ-: yep, no WiFi
[18:36] <phillw> the keyboard monitor for Wifi is white when enabled, and orange when disabled. It was orange.
[18:37] <TJ-> oh hang on that's not the 4.4 kernel, its "Linux version 4.3.0-5-generic "
[18:38] <phillw> the 4.4 would most likely be further back. I had to revert to 4.3 to gain WiFi..
[18:39] <TJ-> oh, hang on then
[18:40] <TJ-> OK, I see the 4.4 now
[18:42] <TJ-> "Jan 15 17:21:52 piglet kernel: [    0.692349] pci 0000:03:00.0: can't claim BAR 6 [mem 0xffff0000-0xffffffff pref]: no compatible bridge window"
[18:42] <TJ-> phillw: try adding to the kernel's command-line at boot-time "pci=realloc"
[18:43] <phillw> I'm so glad that means something to you!
[18:43] <phillw> TJ-: I cannot get the grub to into command mode..... This is another royal PITA.
[18:43] <TJ-> it means that one of the memory mappings the device needs couldn't be satisfied because there was not a sutiablly sized window
[18:44] <TJ-> phillw: edit /etc/default/grub, add it in the GRUB_CMDLINE_LINUX="" string, then do "sudo update-grub"
[18:47] <phillw> TJ-: and now re-install the 4.4 kernel and reboot?
[18:47] <TJ-> phillw: that's a worry regression; those issues have been getting worse for about 17 months; I've been actively working on getting the fixes into mainline but it keeps dropping back
[18:48] <TJ-> phillw: no reinstall needed if you haven't removed it, just reboot
[18:48] <phillw> phillw@piglet:/var/log$ grep CMDLINE_LINUX /etc/default/grub
[18:48] <phillw> GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw"
[18:48] <phillw> GRUB_CMDLINE_LINUX="pci=realloc"
[18:50] <phillw> TJ-: I have to re-install 4.4 - grub is being a bitch and does not allow me to select which kernel I want to boot into.... Yet another bug that needs sorting out.
[18:51] <TJ-> you mean holding down the Shift key from when the PC begins to reboot doesn't interrupt?
[18:52] <phillw> indeed...
[18:52] <phillw> but I usually tap it, I'll try the holding it down next time.
[18:53] <TJ-> yes, holding down is the way to do it. Shift/Ctrl set flags, they're not detected as key-down/key-up sequences
[18:53] <TJ-> they were chosen for exactly this reason
[18:54] <TJ-> because otherwise it is a lottery as to whether you can hit the key at the exact moment GRUB checks
[18:54] <phillw> let me just gently ask Synaptics to re-install 4.4 for me :)
[18:57] <phillw> TJ-: if you know grub, you must have known Dave Stan from when *buntu changed from v1 to v2 grub?
[18:57] <phillw> drs305
[19:01] <phillw> bbs ... rebooting into 4.4
[19:10] <phillw> TJ-: nope, that did not work... I've pushed the file back to http://phillw.net/kern.log
[19:14] <TJ-> similar again "pci 0000:03:00.0: can't claim BAR 6 [mem 0xffff0000-0xffffffff pref]: no compatible bridge window"
[19:15] <phillw> Well, here we are.. same computer with 4.3 happy as it always is.
[19:18] <TJ-> phillw: you could amend that previous change to read "pci=realloc,assign-busses"
[19:18] <TJ-> phillw: that allows the kernel to ignore the bridge config the PC's firmware configured, and redo it
[19:19] <phillw> TJ-: I'm sorry to give you a headache on a friday... I was just winding down and wanted to have a quick poke at the 4.4 kernel as weekends is when we have the most volunteer testers available.
[19:20] <phillw> edit /etc/default/grub, add it in the GRUB_CMDLINE_LINUX="" == change to "pci=realloc,assign-busses"
[19:20] <phillw> ?
[19:25] <TJ-> yes
[19:25] <TJ-> I use that here; to work around some regression in the PCI bridge window code
[19:26] <phillw> reboot is next :)
[19:26]  * TJ- crosses fingers
[19:32] <phillw> TJ-: WiFi failed, the log file has been re-sent to http://phillw.net/kern.log
[19:35] <TJ-> I'm chatting to the kernel devs now about it. You might want to /join #ubuntu-kernel (talking to rtg and apw)
[19:36] <phillw> I think I'm still allowed on there :) Long story, head over to #phillw for it..
=== truexfan81_ is now known as truexfan81
[21:30] <ChibaPet> My next noob question... In #ubuntu someone pointed me to https://help.ubuntu.com/community/Upgrades - I'm curious if there's anything interesting do-release-upgrade does beyond the manual apt-get (or I guess aptitude now) steps noted in the Debian method on that page.
[21:30] <ChibaPet> (Firing up my laptop now to snag the package in case it's a shell script.)
=== nolsen is now known as GabeN
=== GabeN is now known as nolsen