tomreynhi, is there something I could do to encourage lucid backports of the current maverick kernel at https://launchpad.net/~kernel-ppa/+archive/ppa ?10:25
tomreyn(Where "I" is just a random Ubuntu user)10:26
lifelessthere already is onw10:27
lifelessdifferent ppa I think10:27
lifelessdeb http://ppa.launchpad.net/kernel-ppa/ppa/ubuntu lucid main10:28
lifelesshas been pretty up to date for me10:28
tomreynlifeless: that's the same PPA, and there's not the current maverick kernel there.10:29
lifelessmy bad, sorry10:30
tomreynI'm looking for a version => 2.6.35-20.29 specifically10:30
=== xfaf is now known as zul
=== BenC__ is now known as BenC
=== kamalmostafa is now known as kanal
=== kanal is now known as kamal
crimsun_tomreyn: that I can see, tim hasn't submitted the current maverick linux for build yet16:30
tomreyncrimsun_: "tim" being the maintainer of which PPA/package?16:57
crimsun_tomreyn: tim gardner17:03
tomreynthanks crimsun17:54
=== yofel_ is now known as yofel
=== yofel_ is now known as yofel
=== tm__ is now known as tm
KjetilKI hope you don't mind a "user" question in this channel: I need the mantis driver which was added to mainline in 2.6.33-rc5 on my 10.04 system, and I've been looking around for a kernel to use. Currently, I've built from git, but I guess there has to be easier ways to get that.22:00
KjetilKI've looked around, and I'm a bit confused about what kernel builds would be the most stable in my situation. Mainline builds? The kernels in this PPA: https://launchpad.net/~kernel-ppa/+archive/ppa ? Any others?22:01
jolanyou could backport it yourself and use DKMS22:03
JanCKjetilK: you could try the kernel packages in http://kernel.ubuntu.com/~kernel-ppa/mainline/22:04
KjetilKjolan, yeah, I suppose that's what I've done with my current solution22:05
KjetilKJanC, yeah, but what would be the best of those packages, or the https://launchpad.net/~kernel-ppa/+archive/ppa ?22:05
KjetilKthey're not the same, right?22:06
JanCthe "mainline" packages are mainline kernel builds using the Ubuntu kernel config, I think the other one includes additional patches22:07
KjetilKthe mainline has not gone through any Ubuntu QA, I suppose? 22:11
JanCKjetilK: BTW: the 2.6.32 kernel might see a lot of backports over time, as it was selected by most distros to provide long ter msupport or enterprise releases22:11
JanCnot sure if that includes your driver though22:11
KjetilKinteresting, but I suppose the mantis hardware isn't amongst the most common :-)22:11
KjetilKit is used on DVB-C TV cards22:12
KjetilKit is my MythBuntu box :-)22:12
JanChm, that doesn't sound too "enterprisey"  ;)22:13
KjetilKnope :-)22:13
JanCah well, at least you can use a DVB-C card, over here the cable company uses proprietary encryption not supported by anybody but their own crappy hardware  :-(22:14
JanCnot that I'm really affected, as I don't have a TV, but I'm sad out of principle  ;)22:15
KjetilKso, I was thinking, if I had packages that were backports of the Maverick betas, they would have had more QA, is that reasonable?22:15
KjetilKyeah, I know. I wouldn't have had a TV either if it hadn't been for Myth. But it is the same thing here, they have some crappy encryption. People have cracked it though, the legal status is somewhat complicated, but since I do not run any card-sharing or anything, I believe I am on the right side of the law22:17
JanCthe encryption they use here is pretty strong AFAIK, but could be used if they allowed cardreader modules for 3rd party hardware22:19
KjetilKI was quite involved when we got DMCA style legislation, and politicians reassured us that encryption would only be protected if it was relevant to copyright, and for my personal use, it isn't. So, the question remains if the cable provider's ToS overrules the law, which the consumer ombudsman has said it doesn't22:19
KjetilKyeah, things are getting worse here too, CI+ is making stuff harder22:19
JanCwell, CI+ would at least allow third party hardware  ;)22:20
KjetilKit constantly baffles the mind why they can't just make things could instead of making things crappy with strong encryption...22:20
KjetilKerr, s/could/good/ 22:20
JanCCI+ provides at least some way out of lock-in into crappy hardware22:21
=== brot_away is now known as brot
KjetilKyeah, that's true, but I suspect they will never give you the certificates you need to use non-crappy hardware...22:22
JanCnow people have to buy a 30W box that (according to the manual) has to run 24/7, becomes slow after 1 day of operation (Java VM not being able to collect garbage?), after any important issues peopel lose their recorded stuff, etc.22:23
JanCthe stupid thing doesn't even spin down the hard disks...22:23
* KjetilK wants a 15W thin client to run mythfrontend in 1080i with Power over Ethernet only22:24
JanC"spinning down hard disks is bad for their lifetime"22:24
KjetilKAtom Z6xx seems capable of doing that...22:24
JanCbut of course you have to replace the box every 3-4 years anyway  ;)22:24
KjetilKloosing everything every time22:25
JanCI mean, whatever if the hard disk dies after 3 years instead of 6 years if you only use it for 3 years  ;)22:25
KjetilKmmm, back to my original question, it seems the latest mainline build for lucid is 2.6.34 and 2.6.35-rc122:26
KjetilKwhereas the other kernels are more recent, seems to follow the maverick releases?22:27
JanCI assume that means they use mavericks kernel config22:31
* KjetilK nods22:34
KjetilKfrom the name linux-meta-lts-backport-maverick, it sounds like it is a backport to lts, which is a good sign, I suppose...22:35
* KjetilK tries it22:42
JanCBTW: you should be able to build a 1080p system that needs *significantly* less than 15W nowadays22:51

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!