/srv/irclogs.ubuntu.com/2015/08/13/#ubuntu-kernel.txt

=== zyga-afk is now known as zyga
jsalisburybdmurray, Upstream replied with a recently found work around for bug 1436940 .  However, it's not the most elegant solution.  It requires booting with unofficial windows-extracted firmware images.  More info in comment #20 of bug. 10:20
ubot5bug 1436940 in linux (Ubuntu Wily) "Atheros wifi 168c:0041(QCA6164) is not supported" [Medium,Confirmed] https://launchpad.net/bugs/143694010:20
jsalisburybdmurray, well that was fast.  There is now real firmware here: https://github.com/kvalo/ath10k-firmware/commit/7f7e7dda33676ced293de477b03711199ffe5256  I'll update the bug report.10:35
tseliotapw: how do I find out what (upstream) kernel release linux 3.19.0-26 is based on? (I need to add a check in my kernel code for fglrx)11:07
apwtseliot, http://people.canonical.com/~kernel/info/kernel-version-map.html11:09
tseliotapw: thansk11:21
tseliot*thanks11:21
tseliotapw: so 3.19.0-26 = 3.19.8-ckt2, but how do I use that with the KERNEL_VERSION macro?11:31
apwoh you can't11:31
apwdon't be sillly converting to a number broke you11:31
tseliotapw: apparently 3.19.0-25 -> 3.19.0-26 made a symbol gpl-only11:32
apwto a ckt-N name, well and that it is in 4th11:32
apwwelll you can tell -25 and -26 apart11:32
tseliothow?11:32
apwUTS_UBUNTU_RELEASE_ABI11:32
apwwhich is defined in the same place as you get other versions from11:33
apwyou want something like11:33
apw#ifdef UTS_UBUNTU_RELEASE_ABI11:33
apw#define UBUNTU_VERSION KERNEL_VERSION * 100 + UTS_UBUNTU_RELEASE_ABI11:33
apw#else11:33
apw#define UBUNTU_VERSION KERNEL_VERSION * 10011:33
apw#endif11:33
apwor something11:33
apw100 isn't enough i expect11:34
tseliotI think checking the Ubuntu ABI would be enough. So, if none is available I can define the ABI as 011:36
tseliotand check the kernel version11:36
tseliotok, that helps11:37
tseliotthanks11:37
apwyeah11:39
apwtseliot, yeah thats why we don't provide accessors, as you have to check they exist and provide your own if no11:39
apwas you can't assume we are ubuntu, ugg11:39
* tseliot nods11:39
tseliotapw: are you sure that UTS_UBUNTU_RELEASE_ABI is available in the lts-vivid kernel?16:00
tseliotI'm doing this:16:00
tseliot#ifndef UTS_UBUNTU_RELEASE_ABI16:00
tseliot#define UTS_UBUNTU_RELEASE_ABI -116:00
tseliot#endif16:00
tseliot#if UTS_UBUNTU_RELEASE_ABI < 016:00
tseliotand that always seems to be true16:01
* tseliot clones the git repository...16:02
apwdebian/rules.d/2-binary-arch.mk:        echo "#define UTS_UBUNTU_RELEASE_ABI $(abinum)" >> $(hdrdir)/include/generated/utsrelease.h16:03
tseliothmm...16:03
apw/usr/src/linux-headers-3.19.0-14-generic/include/generated/utsrelease.h:#define UTS_UBUNTU_RELEASE_ABI 1416:04
apwand there it is in a 3.19 i have installed16:05
tseliotok16:05
apwso unless it is getting lost in the lts-backport, which is pretty unlikely16:05
tseliotI can see it here. Do I have to include that header or is that already exported?16:06
apwi thouoght if you included the one with KERNEL_VERSION it was incldued16:07
apwbut perhaps not16:07
tseliotthat would be a  bit of a problem16:08
tseliotas custom kernels won't have utsrelease.h16:09
apwwhy not ?16:10
apwits a standard include16:10
apw#define UTS_RELEASE "3.19.0-14-generic"16:11
apw#define UTS_UBUNTU_RELEASE_ABI 1416:11
apwit has the UTS_RELEASE string in it16:11
apwwhich would be 3.19.8-ckt3 normally16:11
tseliotmy fix has to go into fglrx, and I need it to build against custom kernels that may not have that header16:12
tseliotif I add an #include in the fglrx code, it won't find the header in /usr/src/linux-headers-$(uname -r)/include/generated/16:13
tseliotapw: oh, wait, fglrx already does that16:15
tseliotexcept they get it wrong16:16
tseliotas they include it only #ifndef UTS_RELEASE16:16
tseliotno they don't16:17
tseliotok16:17
tseliotit's included in the wrong file16:18
tseliotapw: problem solved :)16:23
dkesseli want to run the trusty kernel version (3.13) on my vivid and wily installations. is there an easy way of doing that?16:54
dkesseli have the problem that power saving is properly working with the trusty kernel, but with vivid and wily's kernels, only one "performance" and "powersave" governors seem to be available. and "powersave" uses more power than in trusty, which i notice because the fan is working all the time, instead only when doing cpu-intensive tasks16:58
ohsixthat could just be a matter of the fan never going off, and those governors are going to be separate from thermal policy stuff thaty may have also changed17:06
ohsixare you looking at powertop to see if more power is actually being used? (disregarding just fan being on uses more)17:07
apwdkessel, no easy way of doing that no, we do not assume compatibility in that direction17:17
dkesselokay. ok, so i did some more searching and found that disabling intel_pstate works for me, as i found in bug 118864717:19
ubot5bug 1188647 in linux (Ubuntu) "Please change intel_pstate default to disable" [High,Fix released] https://launchpad.net/bugs/118864717:19
dkesselkernel 4.1.0-3 does not work good without disabling it17:20
dkesseldo you think i should collect some more information and file a bug? (yes, i have read the channel topic....)17:22
apwdkessel, yes you should file a bug indeed if pstate_idle is breaking you on 4.1, it should be "purfect" by now17:28
apwdkessel, ubuntu-bug linux so we get appropriate h/w info17:28
dkesselok, here's bug 1484616 . if i can provide any more info, try anything else, just tell me :)17:34
ubot5bug 1484616 in linux (Ubuntu) "pstate_idle is broken on 4.1, high fan speed when idle" [Undecided,New] https://launchpad.net/bugs/148461617:34
=== zyga is now known as zyga-afk

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