[00:56] Not impressed with systemd - it replace cryptsetup scripts but refuses to use the crypttab keyscript= parameter - meaning any volume requiring unlocking via script and usually some key-file device, is now broken [01:45] good morning to all [01:45] \o [01:45] you had me check the clock then [01:45] "surely it's not that bad!" [01:45] :p [01:46] daftykins: im very early thats why [01:46] Yikes! it's late [01:46] 3h46 here [01:46] :) [01:46] TJ_on_Wily: i hope you fed the dogs! [01:46] else they'll be the ones getting Wily ;) [01:47] lol [01:47] * lotuspsychje hides the meat [01:49] * TJ_on_Wily rolls eyes [01:50] I wonder who actually came up with the release codename that didn't know it is spelt "Wiley" [01:51] lol [01:51] !wily [01:51] Ubuntu 15.10 (Wily Werewolf) will be the 23rd release of Ubuntu. Discussion in #ubuntu+1 [01:52] i hope they choose more wisely on LTS [01:52] a more stable codename :p [01:52] Let's hope 16.04 LTS is a improved over all the regressions in 15.10 [01:52] X will be quite funky indeed [01:57] I'm quite annoyed right now; systemd-cryptsetup broke keyscripts since 2011, someone eventually proposed patches to fix it, Poettering refused them and wants a massive generic framework building. [01:58] We need a rule, enforced by firing squad, that if you replace existing functionality with something new, to be accepted into a distro it *must* implement all existing functionality first [01:59] I've hit similar serious regressions in Bluetooth Bluez 5.3 ... it can't pair devices using PIN codes, it can't do headset profiles (functionality ripped out that was in Bluez 4.x) [02:00] !info bluez willy [02:00] 'willy' is not a valid distribution: kubuntu-backports, kubuntu-experimental, kubuntu-updates, partner, precise, precise-backports, precise-proposed, stable, testing, trusty, trusty-backports, trusty-proposed, unstable, utopic, utopic-backports, utopic-proposed, vivid, vivid-backports, vivid-proposed, wily, wily-backports, wily-proposed [02:00] !info bluez [02:00] LOL [02:00] bluez (source: bluez): Bluetooth tools and daemons. In component main, is optional. Version 4.101-0ubuntu25 (vivid), package size 625 kB, installed size 2647 kB [02:00] !info bluez wily [02:00] bluez (source: bluez): Bluetooth tools and daemons. In component main, is optional. Version 4.101-0ubuntu25 (wily), package size 625 kB, installed size 2647 kB [02:00] That's wrong! [02:00] apt-cache policy bluez ==> bluez: Installed: 5.33-0ubuntu4 [02:01] weird [02:01] the bot's mostly useless these days [02:01] werewolf [02:01] OerHeks: morning :p [02:01] 4 am [02:01] or still awake? [02:02] 3 dogs on the couch with one eye open [02:02] :p [02:04] https://wiki.ubuntu.com/DevelopmentCodeNames#A16.04 [02:10] just tested out pypar2 and nice lil tool :p [02:10] !info pypar2 [02:10] pypar2 (source: pypar2): graphical frontend for the par2 utility. In component universe, is extra. Version 1.4-7 (vivid), package size 37 kB, installed size 288 kB [02:33] Do you ever wonder how it is so many clients join #ubuntu but only about 1% speak? [02:34] yeah :S [02:34] champion idlers [02:35] judging by what that 1% say, it's best that the rest keep quiet... [02:36] myself, i learn alot by listening [02:41] yeah i picked up a fair chunk, hell i don't even use desktop ubuntu and yet solve peoples graphics issues [02:41] But do those silent clients actually have users looking at the channel? [02:42] maybe they're all Microsoft employees ;) [02:42] that's a good question TJ_on_Wily [02:42] :) [02:43] i admire you guys, you do a great job and have waaaay more patience than i do [02:48] hope Ops are watching "~root@ec2-54-152-74-3.compute-1.amazonaws.com" [05:45] Good morning. [05:50] o/ [12:53] TJ_on_Wily: good day sir [12:53] g'afternoon [13:01] grrr hexchat lags [13:04] !nvidia [13:04] For Ati/NVidia/Matrox video cards, see https://help.ubuntu.com/community/VideoDriverHowto [13:04] https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia [13:04] !binary [19:38] http://news.softpedia.com/news/lxle-14-04-3-linux-distro-is-now-based-on-lubuntu-14-04-3-lts-screenshot-tour-490492.shtml [19:39] * daftykins climbs off Bashing-om's toes [19:39] lol [19:39] so far for the serious quality ubuntu discussions... [19:39] daftykins joined tha house :p [19:39] * OerHeks bites daftykins bicycle tyres [19:40] haha [19:40] daftykins: Don;t hurt a bit for you to stand on my toes, sometimes I need all the help I can get . [19:40] :) nah you're doing just fine! [19:40] OerHeks: hey i need those for my trip this coming weekend :D [19:41] you lot will have to put up with me being gone for a week or so :P [19:41] Yes, we all are going offline because of you. [19:41] boycot irc! [19:42] lol [19:42] even when Ubuntu wants to pay us per Q, we won't .. [19:42] i think if we did i'd be deducted every time i'm grumpy and so earn nothing ;) [19:43] if you have nothing, you cant loose nothing [19:43] maybe, or it is JanC's fault. [19:43] lol [19:43] lets blame it all on him [19:43] sounds like a plan [19:43] last one in, first out ;) [19:43] lol [19:44] then wileee, then Bashing-om ... then you, lotuspsychje ;-D [19:45] you cant beat me with a stick im staying! [19:45] OerHeks: you scared JanC_ away [19:47] d'aww [19:47] or perhaps the hatred of a thousand help seekers vanquished him/her === JanC_ is now known as JanC [19:49] who needs a kick :p [19:50] * lotuspsychje slaps JanC with a ping timeout [19:51] #ubuntu-ops-bullying gets started [19:52] lol [19:57] daftykins: Help ! As " lspci' does not tell us the Nvidia chip set ( ralph4100_ ), what other means is there to make sure of what driver should be installed ? Faster than reading th log file . [19:58] "lspci -nn" gives the PCI Vendor:Product ID the driver matches to [19:58] Bashing-om: oh yeah didn't spot the output didn't even know the name for it - i guess we were lucky this guy knew what he had [19:59] not used to lspci being so vague, i wonder if that's a hint at being an older kernel for the card [20:01] daftykins: I was real perturbed not to get the info I expected, and began scrambling to find an alternate . I have to assume the GEforce 750TI - sure would be nice to have confirmation. Assuming has bit me bad more than once. [20:02] does that 750ti not need that edgers ppa? [20:02] not for a while no [20:02] trusty has 346 now [20:02] ah cool [20:02] well the 750 Ti is maxwell version 1 as well as the Titan X, so it's a similar generation [20:02] ive seen the nvidia binary page has improved for ubuntu [20:02] i think they're both maxwell 1 anyway, definitely both maxwell [20:03] https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia [20:04] lol at the wording on there [20:05] Bashing-om: mmm i never caught which ubuntu that user was on [20:05] Did the Fgrlx driver under 4.x kernels break in Ubuntu land? Does anyone know? [20:06] hrmm does anything even use a 4.x yet? or is that just with mainlines? [20:07] For background: https://bugs.gentoo.org/show_bug.cgi?id=548118 [20:07] bugs.gentoo.org bug 548118 in Unspecified "x11-drivers/ati-drivers-15.1 fails to build with kernel 4.0.0 - kcl_str.o failed" [Normal,Confirmed] [20:07] There seems to be some licensing issue. [20:07] Wily uses 4.1. [20:08] nite nite all [20:08] i'm sure they'll sort themselves out after release [20:08] lotuspsychje: o/ [20:08] aww lotus is out of date! trusty .2 :) [20:09] Bashing-om, Is that for ralph4100's device (10de:17c2) ? [20:09] Usually the pciids file will tell you, as in: grep "[[:space:]]17c2" /usr/share/misc/pci.ids ===> 17c2 GM200 [GeForce GTX TITAN X] [20:10] mmm, GM confirms M for Maxwell [20:10] whilst you'd get GK for the prior generation, Kepler [20:11] TJ-: Afirmed. And yeah I do have to learn to read the PCI id .. Researchimg now from your advise. [20:13] hmm handy file that one indeed! [20:20] That's what lspci uses [20:20] oic [20:20] You can update even older systems with the latest entries with "sudo update-pciids" [20:21] so since that users pastebin didn't show it, it must've been an outdated file [20:21] ah neat :D [20:21] Yes, older kernel/pciutils releases and newer hardware need that updating (its just a download) [20:22] this capitanooo is a handful already [20:22] daftykins: +1 [20:25] TJ-: daftykins !! As I live and learn . seems that Ralph's card would be real happy with 355 version driver . - http://www.geforce.com/drivers . To match the GPU/driver . [20:26] Bashing-om: yep, 346 should be ok too? hmm actually the Titan X is the second one isn't it, must be Maxwell 2 [20:26] Titan, Titan X, think there's a Titan Z too [20:27] daftykins: Yeah the 346 "should" work . Nvidia do suggest the 355 version . [20:27] mmm just usual 'stick to the latest' though i guess [20:27] well, that guy never came back :D [20:28] daftykins: When YOU are good he is good . [20:29] go team! [20:30] daftykins: "The latest" I often think of as "testing" see if it works or breaks ! [20:31] indeed :) [20:31] dear customer, please test this for us [20:34] exactly :) . Back in the day I used customers many times to troubleshoot a networking issue . Made my job so much easier, and they may not even know the difference. [20:58] TJ-: 8 and 10 (Windows) can grab everything required from windows update now, so a default install is impressively functional out of the box :) [20:59] Yes, but those drivers still have to be provided by the chipset manufacturers, they aren't written by Microsoft - MS are just distributing the WHQL apprpved drivers to make finding them easier/safer now [21:00] The Ms drivers are generic ones for things like AHCI, USB functions and the common x86 hardware. MS don't write wifi chipset drivers for example [21:00] yip, but it does mean the old model of needing to find and install everything isn't accurate [21:01] It is. Try installing Windows offline from a DVD and getting the drivers installed without networking ... if the networking drivers are needed to make the connection you're screwed [21:01] it's not far off how ubuntu is for most folk :) [21:02] but given the hardware support in the newer releases is better, it's less likely you'll have non working connectivity out of the box [21:12] Yeah, caused by companies like Broadcom not allowing redistribution of their firmware. [21:24] what's Realtek's excuse? same deal? [21:28] Realtek are like Broadcom but in another respect; they refuse to provide the technical documentation required to write a comprehensive driver for many chipsets, meaning what we do get is re-implemented from their out-of-tree driver releases, and by reverse-engineering the Windows drivers [21:29] ah so they're distributed but just work really badly [21:29] I've always thought it seems like these companies really don't want to sell anything. Take the RasPi example with Broadcom. Originally they kept the bootloader code proprietary since its in the GPU code, but after the RasPi did so well they finally relented and opened up the code for that, even though the chipset is a really old one anyhow [21:29] I usually picture the realtek drivers as written by press-ganged goblins in caves given about a week per driver :) [21:30] XD [21:39] * TJ- wonders if EriC^^ brought him a much-needed coffee :) [21:40] * EriC^^ gives TJ- a coffee [21:40] * TJ- slurps noisily [21:40] :) [21:43] ooh that's a good plan [21:44] i may go throw one on, but that might burn so i'll prepare it instead