/srv/irclogs.ubuntu.com/2013/02/22/#ubuntu-kernel.txt

infinityzequence: You got the bug closure syntax wrong in your lowlatency upload to precise, BTW.00:05
infinityzequence: Needs to be "LP: #1234" not "LP:#1234"00:06
ubot2`Launchpad bug 1234 in Launchpad itself "Gina is an unmaintainable mess of command line options, environment variables and shell scripts" [Medium,Fix released] https://launchpad.net/bugs/123400:06
infinityzequence: (Closing the bug manually this time)00:06
infinitysmb`: And you just completely missed having the right tracking bug in the linux-ec2 upload. :)00:07
Kanohi, what was the reason to switch CONFIG_SATA_AHCI=y to CONFIG_SATA_AHCI=m?00:09
Kanowith =m the kernel alone of course does not boot with efibootmgr, initrd is required which is slower00:09
Kanoswitched from 3.8 rc6 to rc700:11
infinityKano: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/105656300:13
ubot2`Ubuntu bug 1056563 in linux (Ubuntu) "Please change AHCI driver back to module in 12.10" [Medium,Fix released]00:13
infinityKano: In short, it can conflict with other modules, so builtin is the wrong answer for a generic kernel.00:13
Kanowhy is that raid ahci not mainline00:14
Kanothat would be the correct answer00:15
Kanohttp://kanotix.com/files/dragonfire/linux-3.8.0-6.13kanotix1/0001-Bluetooth-Add-support-for-AR3012-0489-e04e.patch00:16
Kanothat should be added as well. if you want signed it and push to mainine00:16
Kanodid you add that to your kernel?00:16
Kanohttp://kanotix.com/files/dragonfire/linux-3.8.0-6.13kanotix1/media-cx18-ivtv-fix-regression-remove-__init-from-a-non-init-function.patch00:16
Kanowithout you can not boot 3.8 with ivtv or cx18 card installed00:17
infinityKano: There's a mailing list for your patches.00:17
Kanoi hate mailinglists, btw. the 2nd is from one00:18
Kanoit is not my patch only the first00:18
infinitys/patches/pull requests/00:18
Kanohttp://patchwork.linuxtv.org/patch/16734/00:18
Kanothat patch is critical00:19
Kanoso you see, it was on the list and was not added00:21
ohsix"i hate the thing everyone uses to do this, but i insist on doing this"00:21
infinityKano: Fine.  Can you mail a pull request to kernel-team@?  Thanks.00:22
Kanowell you can tell your users to use kanotix instead too, there it is fixed ;)00:22
Kanobye00:23
ohsixsomehow that's a reasonable thing to do, but not for the reason he stated :d00:23
=== rsalveti is now known as rsalveti|afk
zequenceinfinity: Sorry, and thanks06:41
ppisatimoin07:51
=== smb` is now known as smb
smbinfinity, meh.... :-P08:28
smbmorning08:28
ppisatismb: moin08:35
apwmoin09:08
apwinfinity, bah i missed that too09:08
* apw self flagilates, and it is far too early for such things09:08
smbapw, isn't it also too early to start punching oneself09:15
apwi am not very accurate at this time of day for sure09:18
=== henrix_ is now known as henrix
apwppisati, there was some resaon we had CONFIG_CPU_FREQ turned off for omap wasn't there09:32
ppisatiapw: yes, upstream is missing some pieces for omap409:33
apwppisati, sweet09:33
ppisatiapw: if we turn if on, it crashses on boot09:33
apwppisati, now that is a good reason indeed09:33
ppisatiapw: there should be a link to the upstream discussion about it in the config change that i sent09:34
apwppisati, no that is enough info, i trust your judgement on these things.  i am annotating it so the config checker doesn't try and turn it back on09:36
ppisatiapw: ack09:36
apwppisati, CONFIG_IMX_SDMA and CONFIG_IMX_DMA are off for -omap, are they not useful for imx ?09:45
ppisatiapw: probably not fr the board that we support, but letme check09:46
apwppisati, thanks09:46
* ppisati is eating strawberries.. and he loves it... :)09:47
aissenAny idea why why tigon and bnx2x were removed from linux-firmware in 1.88 ?09:47
apwaissen, have you checked the changelog ?09:48
apwaissen, and in which release are you talking abuot ?09:49
aissenI checked the changelog, it says: "Remove boot essential duplicated firmware files that are also carried in the linux-image package."09:50
aissenthe release is quantal but it carried over raring.09:50
apwaissen, ahh there you go, so we think it is in linux09:51
aissenIs it to save some space then ?09:51
apwaissen, yeah there is no point in having two copies on the system for sure09:52
apwnow if we have ended up with zero copies that is broken09:52
aissenyeah, I would have removed the copy in linux-image; but maybe there's something I don't understand. Is linux-image used in places where linux-firmware isn't ? (network boot?)09:53
apwaissen, i suspect so indeed09:54
aissenthat's what I thought but I wanted input from someone who knew the rationale.09:55
apwrtg would have done the changes, he has been on a mission for firware upstream and in ubuntu, trying to rationlise it all09:55
aissenyeah, first thing I noticed is that rtg wasn't here. I'll wait till he comes back09:57
=== Nafallo_ is now known as Nafallo
ppisatiapw: right, IMX_SDMA and IMX_DMA are all for boards that we don't support (imx 31/35/51/53 and imx 21/27)10:16
=== yofel_ is now known as yofel
ppisatiapw: actually support for those boards is all upstream, so if anyone has the hw we could easily add support for it10:17
apwppisati, but for now off makes sense ?10:21
ppisatiapw: yep10:21
ogra_oh, a fix for adhoc wifi support on the nexus7 https://launchpadlibrarian.net/132034143/linux-nexus7_3.1.10-9.27-adhoc.patch10:42
ogra_(thats bug 1077704 )10:42
ubot2`Launchpad bug 1077704 in ubuntu-nexus7 "Can't connect to ad-hoc wifi networks" [Medium,Confirmed] https://launchpad.net/bugs/107770410:42
apwppisati, CONFIG_HWSPINLOCK_OMAP is off in -omap, is that deliberate11:28
apwppisati, CONFIG_KEYBOARD_IMX is off in -omap ... what about that one11:32
ppisatiapw: HWSPINLOCK_OMAP seems omap4-only, i'll have to check it11:33
ppisatiapw: KEYBOARD_IMX can be compiled as a module11:33
apwppisati, it may be that the first one is not possible when you have a generic thing going on indeed.  thanks for investigating11:34
apwppisati, K_IMX ack11:35
ppisatiapw: i'll give the first option a try11:36
apwppisati, CONFIG_MTD_NAND_MXC on -omap ?11:36
apwONFIG_MMC_MXC too11:38
ppisatiapw: /me checking11:38
ppisatiapw: MMC_MXC is !imx6 (our board)11:39
apwppisati, ack will leave it be then11:39
ppisatiapw: apw same for MTD_NAND_MXC (is for the imx31)11:41
apwppisati, ack ta11:41
apwppisati, CONFIG_PWM_IMX ?11:48
ppisatiapw: =m?11:49
apwppisati, will do 11:50
cnfhi. I'm trying to compile some 3rd party kernel modules for packaging in a .deb however, my kernel modules won't load on any system it wasn't compiled on12:06
cnfi'm compiling against the same ubuntu stock kernel (3.2.0-29-generic)12:06
apwcnf, if you are able to distribute the source, then you might want to be using dkms12:06
cnfapw: i don't want compilers on all the servers12:06
apwcnf, well as we build LBM that exact same way it should work as far as i know12:07
apwcnf, what happens when you try to load them12:07
cnfeb 22 11:46:38 62-213-199-42 kernel: [ 2652.522284] saa716x_core: disagrees about version of symbol dvb_frontend_detach12:07
cnfFeb 22 11:46:38 62-213-199-42 kernel: [ 2652.522288] saa716x_core: Unknown symbol dvb_frontend_detach (err -22)12:07
cnftimes a lot :P12:07
apwcnf, and you are absolutly sure it was the same version of the kernel, and the very same compiler version as built the kernel12:08
apwcnf, and you are sure you used the right .config12:09
cnfapw: i'm building in a vm, if i delete de vm right after compilation, and reinstall the same kernel12:09
cnfit fails12:09
cnfif i load them right after i compiled them, it works12:09
cnfboth with linux-image-3.2.0-29-generic12:10
cnfmaybe i'm doing something wrong, or missing something, but i can not figure out what12:10
cnfapw: and the .config in the kernel source tree is identical to the one in /boot/ for the running kernel12:11
apwcnf, and if you reboot the original VM and try installing them again does that work12:11
apwas that should be equivalent to your delete and recreate VM12:11
apwin theory as the bits should be the same12:11
cnfapw: yeah, i can reboot the vm, and reinstall the .deb12:12
cnfworks fine12:12
cnfwipe the vm, bring it up again (vagrant), install kernel image and my package12:12
cnfno go12:12
cnfi'm sure i'm doing something stupid, but what :/12:13
apwcnf, i struggle to see how that could not work, as otherwise we could not ship lbm12:13
apwcnf, what release12:13
cnfapw: of?12:13
apwubuntu12:13
cnfoh,12:14
cnfUbuntu 12.04 LTS12:14
cnf(target is 12.04.1, but i'm ignoring that one for now)12:14
apwcnf, can i have a full dmesg from a failure please12:15
cnfsure, hold on12:15
cnfhttp://pastie.org/631612212:15
cnfapw: i could even share the vagrant project, if you have ny use for it12:18
apwcnf, can i get the whole dmesg from the top pls12:24
apwcnf, and a cat /proc/version and a gcc -v from the system failing to load them12:25
cnfapw: how far back? that is everything related to the loading12:26
apwcnf, i want to see the top mostly but you never know what clues are in there12:26
cnf(and there is no gcc on the systems failing to load)12:27
apwcnf, point, actually i want it from the one building it when it is building it really don't i12:27
cnfhttp://pastie.org/631616512:27
cnfLinux version 3.2.0-29-generic (buildd@allspice) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #46-Ubuntu SMP Fri Jul 27 17:03:23 UTC 201212:29
cnflet me rebuild the builder12:29
cnf(takes a few minutes)12:29
cnfand http://pastie.org/6316179 for gcc version12:31
apwcnf, get me a /proc/version and well as gcc -v off that one12:31
cnfit's not running the kernel i compile for12:31
cnfbut Linux version 3.2.0-23-generic (buildd@crested) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu4) ) #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 on the builder12:32
apwcnf, does it have the headers for the one you are compiling for installed ?12:32
cnf(i install the right headers and image for the kernel i _do_ compile for, obviously)12:32
apwcnf, but then it would not be possible to load them on the builder12:33
apwcnf, and you say that _does_ work ?  which it shouldn't12:33
cnfsure, but i reboot to test that :P12:33
cnfthe builder installes the linux-headers and linux-image of the target kernel specified12:33
cnfautomatically12:33
cnfif i reboot to test (so it runs the right kernel)12:33
cnfthen it does work12:33
apwbuilds against them, then you reboot it and load them12:34
cnfyep12:34
cnfso _building_ is done on another kernel, but after a reboot to the right kernel, it works12:34
apwok can we do that next, reboot it, and get me /proc/version and the dmesg shen they do load12:34
apwwhen12:34
cnfyep12:34
cnfi do this, btw, so i can automate my package building, and just speficy what the target kernel is in my config12:35
apwyes that makes sense indeed12:35
apwand we build all our stuff in a similar way, in a chroot for the release12:35
cnfuhu12:35
apwwith the wrong kernel running, so it should just work as it works for us12:35
cnfok, package is build12:35
cnflet me reboot the vm12:35
apwbut there must be something different between the two somewhere12:36
cnfyeah...12:36
apwcan we keep this vm rebooted in the working and loads state12:36
apwand get the saame exact .ko copied to one you made fresh12:36
cnfsorry?12:36
apwand confirm 1) it doesn't load12:36
apwcan we keep the builder VM in the testing state, so on the right kernel with the module proven loaded12:37
apwand at the saem time make a consumer VM and pull the .ko off the12:37
apwbuilder VM and hand put it on the other VM12:37
apwand see if that loads12:37
apwif it does, we know it is a 'copying' issue when making the .deb to carry it12:37
cnfsure12:37
apwif it does not we know it is somehow a differnece in the two VMs12:37
cnfthough i did md5sum some of the modules12:38
apwand perhaps with both running we can find it12:38
cnfbut i'll try it none the less12:38
apwsensible indeed12:38
apwas it seems impossible as stated of course12:38
cnfit's a bit of juggling though, because this is vagrant12:38
apwso it must be subtle12:38
cnfas soon as i reboot, my setup breaks12:38
cnf(no more vbox modules, so no more shared folders etc)12:38
cnfalso, it's not just one .ko, it's a mess of modules ^^;12:40
apwcnf, well i mostly only care about the one which fails first :)12:40
cnf:P12:41
cnfsetting up the 2nd vm12:42
cnfit's installing the right kernel now12:42
apwone thing i would like to know is that md5sum /boot/vmlinuz-`uname -r` sort of thing really matches on the working and not working ones12:42
cnfok12:42
apwi am sure it will but ... never hurts to test the basicxs12:43
cnfi'm gonna take some snapshots, so i can revert a bit faster :P12:44
apwplan indeed12:45
apwVMs have their uses12:45
cnfindeed12:45
cnfok, 2nd vm is up12:46
cnfso _not_ install the package, you said?12:46
apwwell i am happy if you use the package, if we compare them md5sum with the ones you loaded successfully on the rebooted builder12:50
cnfok12:50
apwi want to know they are bit for bit the same12:50
apwi would like to see lsmod on the builder against lsmod when it fails to load as well12:50
cnfok12:52
cnf(faling at scp atm ^^;)12:52
cnfthere we go ^^;12:52
cnfhttp://pastie.org/6316289 success12:54
cnfhttp://pastie.org/6316299 fail12:56
cnfapw: see those tbs6??? modules?12:56
cnfthose are part of my package...12:56
apwWARNING: Error inserting rc_core (/lib/modules/3.2.0-29-generic/kernel/drivers/media/rc/rc-core.ko): Invalid argument12:56
apwbut that one not ?12:56
cnfno, i don't think it is part of my package12:57
apwand they are auto loading on the test system?  or do you have the modprobe command12:57
cnfnope, it isn't12:57
cnfautoload12:57
cnfsorry12:57
cnfsec12:57
cnfmodprobe saa716x_tbs_dvb12:58
cnfis what i run12:58
cnfon either system12:58
apwand got no output when it worked ?12:58
cnfapw: exactly12:58
apwok note rc_core is loaded on the working system12:58
apwso modprove rc_core on the broken one12:58
apwmodprobe even ...12:59
apwwhat does that say, and does it say anything in dmesg for it12:59
cnf# modprobe rc_core12:59
cnfroot@precise64:~# lsmod |grep rc_core12:59
cnfrc_core                26412  7 ir_lirc_codec,ir_mce_kbd_decoder,ir_sony_decoder,ir_jvc_decoder,ir_rc6_decoder,ir_rc5_decoder,ir_nec_decoder12:59
apwnow try probing your module 13:00
cnfon the broken system13:00
cnfWARNING: Error inserting rc_core (/lib/modules/3.2.0-29-generic/kernel/drivers/media/rc/rc-core.ko): Invalid argument13:00
cnf(and the same following lines)13:00
apw?13:00
cnfhttp://pastie.org/631632213:01
apwlsmod | grep rc_core works on the broken system13:01
cnfyes13:01
apwbut modprobe of your module still triggers an error loading it ?13:01
cnfyes13:01
apwi find that hard to believe13:01
apwand it wasn't probed in the lsmod you pasted originally13:01
apwcan i have a new lsmod off it13:02
apwsomethign really screwey is going on, or we are not understanding each other13:02
cnfhttp://pastie.org/631632913:02
cnfyeah13:02
cnfhmm13:03
cnfok, rc-core has a different md5sum on both system13:03
cnfo,O13:03
apwcnf, !?!13:03
apwwell that would cirtainly not be right13:04
cnfindeed13:04
cnfdamned screwey 3rd party software :/13:04
apwwas it wrong before you installed your package13:04
apwyeah you have to hate it13:04
cnfapw: it's part of the default system13:05
cnfso i didn't touch it with my package13:05
apwso which one is wrong13:05
cnfbut aparently, this driver package recompiles rc-core.ko13:05
cnfand i guess depends on the changed version?13:06
apwouch13:06
apwso you need to bring that too i assume13:06
apwvile vile vile vile13:06
cnfhmm, i guess13:06
apwwell easy to test, scp it over13:06
apwrmmod it, and try again13:06
cnfbut _can_ i even overwrite existing files managed by a different package?13:06
apwthen send hatemail to someone :)13:06
cnfwith a .deb?13:07
apwcnf, with difficulty13:07
apwcnf, though in this case you can put it in /lib/modules/<version>/update/<path> as well13:07
apwand that takes precident over the 'real' one13:07
cnfaha?13:07
cnfoh, shiny!13:07
cnfok, lets start the scping13:07
apwor is it updates, anyhow it should exist whatever it is called13:07
apwthat is where dkms makes its mess as well13:08
cnfhehe13:08
ppisatiapw: do you have native ipv6 or you use a tunnel?13:10
cnfapw: thank you for your help so far13:10
apwppisati, an HE tunnel, the uk isn't very advanced in ipv6 land13:10
cnfapw: i'm gonna give my brain a small break, and hack on this a bit13:10
ppisatiapw: ok13:10
cnfapw: i'll probably be back in a bit :P but you have been a great help so far!13:10
cnfapw: oh, should the path under updates mirror the path under kernel?13:12
apwcnf, i think it doesn't matter as it is found by depmod13:12
cnfaha, ok13:12
apwcnf, but i would probabally make it so13:12
cnfright :P13:14
cnfhmz13:21
cnfapw: ok, same error13:21
apwdid you rmmod rc-core13:22
apwand modprobe it again ?13:22
apwand did you run depmod? to pick up the new one13:22
cnfi did a rollback13:22
cnfand ERROR: Module rc_core does not exist in /proc/modules13:22
cnfon an rmmod13:22
cnfand yeah, my package runs depmod -a on install13:24
cnfi think you got it right when you used the word "vile" :P13:31
cnfhmm13:32
cnfapw: the _new_ rc-core module loads on the new system, but gives similar "disagrees about version of symbol" messages in dmesg13:32
cnfso i am going to go out on a limb, and say they did the same thing to a bunch of other modules...13:33
apwbah13:33
cnfyeah :/13:33
apwmd5sum is your friend13:34
cnfso i guess i'll be writing a script that does a find and a md5sum on everything13:34
cnfand compares before and aftyer13:34
=== yofel_ is now known as yofel
=== rsalveti|afk is now known as rsalveti
* cnf facepalms14:01
cnfapw: they are actually recompiling the rc-*.ko drivers for _other_ cards as well14:01
apwcnf, i think you should send that s/w back with a brick attached14:07
cnfapw: considering it14:08
cnfapw: and herpes14:08
apwa good combination14:08
cnfisn't it :P14:08
cnfapw: normally if one where to write kernel modules14:10
cnfhow would you make it easy for packagers?14:10
cnfsomething like --prefix or $DESTDIR, no?14:10
apwnot changing existing ones, using the prefixes we have for updates, or make new names14:10
apwreally they should make new names14:11
cnfuhu14:11
apwas they are recompiling all of rc-* becaure they are renaming rc-core14:11
apwcause they are rebuilding rc-core14:11
apwthey should be making a copy and calling it my-rc-core to avoid all this14:11
cnfindeed :/14:12
cnfi did a `find . -exec md5sum {} \; > file` pre and post14:12
cnfthe nr "recompiled" modules is appalling!14:13
cnftotally unrelated modules have different sums14:13
apwprobabally dependancies of those other ones14:13
apwor ones which use them14:13
cnfyeah, indeed14:13
apwwhich is doubly why one should not do this14:13
cnfyeah!14:14
apwor one should just apply the patches to our source and build your own kernel14:14
cnfi'm not a C coder (doing learn C the hard way atm :P ) but _i_ know this, damnit >,<14:14
apwas you are not runnign our kernel, and nothing about your kernel should call itself the version we shipped14:14
apwthat is just confusing ... 14:14
apwhello choir14:14
cnfyeah :P14:15
=== kentb-out is now known as kentb
=== cheako911 is now known as cheako
ppisatibrb15:06
=== rsalveti_ is now known as rsalveti
cnfi'm going home, thanks again apw !15:11
cnf\o15:11
apwBenC, yo .. do you have a v3.8 rebase in the works.  i am working on the configuration updates for master, and want to do teh same for ppc, but you are 'behind'15:24
BenCapw: I'll push out a rebase real quick and pull your changes before uploading15:25
apwcool15:25
BenCapw: should I rebase against master or master-next?15:26
apwi would rebase whever you normally do i guess, master, as the changes are outside the tree for ppc15:27
apwBenC, it may make sense to rebase and upload a v3.8 rebase to match master15:27
BenCapw: normally I rebase against the latest tag15:27
apwthen we isolate any breakage from v3.8 against any breakage from teh config changes15:27
apwour config changes are separate to the v3.8 final rebase as well15:28
apwi can then do the config changes against your tag and it will be all nice and claen15:29
apwBenC, ^15:29
BenCapw: my ppc branch is pushed and synced to ubuntu/master15:32
apwsweet15:32
BenCapw: Thanks15:33
* ogasawara back in 2015:36
apwogasawara, just pushed the result of the full by-menu config-review for v3.8 final15:44
apw(it even builds)15:44
ppisatiapw: is your panda alive? if i provide you with a kernel in ~20mins can you give it a spin?16:02
apwppisati, if this board is a panda, i think it is alive16:03
ppisatiapw: got a patch from rmk about the align/ipv6 problem we had, and i can't reproduce the BUG() here16:06
ppisatiapw: i mean, after i applied the patch i can't reproduce it anymore16:06
ppisatiapw: sounds like it fixes it16:06
apwppisati, sweet, it seemed to kill my machine in the face on a regular basis16:06
apwso i should know just by leaving it on16:06
ppisatiapw: right16:06
* ppisati is building a test kernel16:06
apwgreat16:07
ppisatiapw: check it out - http://people.canonical.com/~ppisati/linux-image-3.8.0-7-omap_3.8.0-7.15~ipv6align_armhf.deb16:19
apwppisati, ack16:20
smosersmb, apw thank you for your console/ttyS0 help.16:28
sforsheeogasawara, rtg, apw: there's a message on ubuntu-devel about proprietary drivers failing to install due to not having the kernel headers, and I've been working a bug that looks to be the same issue. Shouldn't dkms have a dependency on linux-headers-generic?16:29
sforshee(note that it doesn't, at least not in raring)16:29
apwsforshee, nope, because you should have linux-foo installed which gives you the right ones16:29
apwsforshee, and depending on one just means you have the wrong ones for your kernel force installed when you install dkms and things still don't work16:30
smbsmoser, welcome. lets see whether we can find a working way16:31
infinitysforshee: Are these 12.10 users?16:31
sforsheeinfinity, yes for the ones I'm aware of16:31
apwsforshee, ie you are using linux-image-generic-pae but have no headers, you install dkms, that has a dep of 'linnux-headers-generic | linux-headers-generic-pae' that installs the first one, which is useless and you don't get anywhere16:31
apwsforshee, upgrades or fresh installs16:32
infinitysforshee: 12.10 has a bug where the installer removes the headers (and the metapackage) at the end of the install.16:32
apwheh that would do it16:32
sforsheeinfinity, ah. Yes, the bug I'm looking at seems to be a fresh install16:33
infinitysforshee: Other than doing a point release of 12.10, I'm not sure how best to resolve that.  And that still won't get old installs the metapackage back.16:33
infinitysforshee: tseliot was working on a fix to jockey/drivers-common that would try to ensure the right metapackages were installed.  Not sure if that's made it in.16:33
sforsheeinfinity, makes sense16:33
sforsheeapw, thanks for the explanation, I wasn't thinking about pae being a separate metapackage16:34
infinitytseliot: ^16:34
infinitysforshee: Well, not just -pae, but the ARM variants, etc.16:35
sforsheeright16:35
apwit is the inability of the dkms dependancies to make a sensible decision that is the real issue16:36
tseliotinfinity: that would be bug #1123107 and my packages are waiting for approval16:36
ubot2`Launchpad bug 1123107 in jockey (Ubuntu) "Jockey should install the linux-$flavour metapackage" [High,Fix committed] https://launchpad.net/bugs/112310716:36
infinitytseliot: I don't see any Q tasks for that.16:36
infinitytseliot: Which is where most of the affected users are.16:36
tseliotinfinity: if that's desirable, I can backport it from raring to quantal. I think precise has the highest priority though16:39
infinitytseliot: Sure, precise is more important for a variety of reasons, it's just that Q had the unfortunate installer bug that means many/most amd64 users don't have any headers installed by default (oops).16:40
tseliotinfinity: oh, I wasn't aware of this16:41
infinitytseliot: Was a slightly overzealously greedy glob when removing linux-signed (for non-SB systems), if I recall, that led to a few more packages than intended being removed at the end of the install. :/16:42
tseliotouch16:42
infinityOr something along those lines.  I forget the exact bug now, just the symptom.16:43
apwBenC, i have just pushed a startnewrelease pile onto that ppc branch for you, if i push the config changes are you able to reset them off if they don't work for you?16:46
BenCapw: yes16:46
BenCapw: when will ubuntu/master be uploaded?16:46
apwthen that sounds like a plan, it'll be there shortly16:46
apwBenC, actuall the v3.8 final -7 has already been pushed, perhaps we should upload that as is16:47
BenCapw: is master still the same as the -7 tag?16:47
infinityEh, why waste build resources, if there's another one in the pipe?16:47
apwBenC, and then i'll do the confi changes relative to it separatly, to keep the two changes easy to test16:47
BenCRight16:47
apwdiagnosability agasist build resources indeed16:48
apwBenC, so whats uploaded was the clean rebase, ie -7, i'll see about getting this config update uploaded soon i think16:48
BenCOk, I'll hold out for that upload16:48
apwogasawara, what do you think about me uploading this config change today16:49
BenCNothing in the rebase or config is critical to ppc right now, other than making it match ubuntu/master16:49
ogasawaraapw: works for me16:49
apwBenC, reasonable16:49
* ppisati goes for some sweating17:25
ppisatilater17:25
=== henrix is now known as henrix_
=== henrix_ is now known as henrix
=== chrisccoulson is now known as rmadison
=== rmadison is now known as chrisccoulson
* apw idly wonders if pp understands just how that sounds ...17:49
ogra_heh17:50
ogra_i was wondering the same a few days ago 17:50
infinityapw: Who doesn't enjoy some good sweating?18:18
neoshadesHi Just joined to ask a question - What complier is used to create mainline kernel 3.7.9-raring?18:18
infinityneoshades: If you're running the kernel, /proc/version will tell you which compiler was used.18:18
apwneoshades, we may record that too18:19
neoshadesI tried but could not get gnome to run as nvidia drivers 3.10.32 to create dkms module as it complained about the compiler version 18:21
* infinity wonders idly why the GCC version string has a trailing space...18:24
neoshadesI am running 3.7.5-030705-generic at moment and have managed to install 3.10.32 nvidia - /proc/version shows it was compiled with gcc 4.6.3 but installed vrsion is gcc (Ubuntu/Linaro 4.7.2-2ubuntu1 18:25
neoshadesdamm yo many chars18:26
neoshadesam running 3.7.5-030705-generic with nvidia 3.10.32 ok18:27
neoshades3.7.9 won't compile with nvidia 3.10.32 for dkms18:28
infinitySo, you might need to either install gcc-4.6 and export CC=gcc-4.6, or convince your binary driver build that compiler versions don't matter.18:28
apwneoshades, pretty much that is very likely18:29
apwneoshades, what release are you running it on?18:29
neoshadeswhy is mainline using gcc 4.6.3 instead of 4.7.2?18:29
apwso that was built pre the change to 4.718:30
apwneoshades, it is using the default compiler when it was built18:30
apwthey are meant for testing only and we don't expect binary driver to work with them18:30
apwthat is the way of the world18:30
infinityapw: From his GCC version, I assume he's running quantal.18:30
neoshadesyes quantal originally18:31
neoshadesmainline build downloaded from site http://kernel.ubuntu.com/~kernel-ppa/mainline/18:31
apwyes those are the ones, they are pretty much guarenteed to not work with binary drivers cause of the compiler skew18:32
neoshadescompiler skew?18:32
apwthe compiler on teh system not matching that they are built with18:33
infinityThe thing you were just complaining about...18:33
apwas they are not built with the compiler for your system, but the one for precise18:33
apwto allow maximal use of the kernel across versions to allow baseline testing18:33
infinityneoshades: Is there a reason you need to be running mainline kernels?18:34
neoshadesthat's what I thought but I suppose I assumed that mainline builds would be using latest gcc18:34
infinityneoshades: The packaged kernels in the archive are, generally, a much better idea for most people.18:34
neoshadesno reason apart from testing18:34
apwneoshades, well if they were they would be using raring's compiler, which would skew from your locla compiler anyhow18:36
apwsame problem18:36
neoshadeserm so what is raring comipler version?18:37
sforsheeapw, you have a machine with BCM4313 wireless don't you?18:37
apwsforshee, it has brcm something yes18:38
infinityraring's compiler is 4.7.2, shouldn't cause too many issues with quantal.18:38
infinity(And, in fact, a raring kernel package installed on Q should behave just fine)18:38
apw02:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01)18:38
sforsheeapw, someone is complaining about brcmsmac with BCM4313 so if you had that hardware I wondered how well it's working for you18:38
apwsforshee, ^^18:38
apwsforshee, its the normal pile of shit all brcm drivers are, expect to rmmod modprobe it at least daily18:39
apwits been much better since your last fixes, but not perfect18:39
sforsheehuh, okay18:39
apwbut given it is brcm, its purfect18:39
apwand given i run full ipv6, and i have to nail network-manager and nm-applet about as often18:39
sforsheeI rarely have problems with by BCM43224 in 3.818:39
apwi cannot be sure it is completly brcms fault18:40
apwcan you tell i am bitter about it18:40
apwbroadcom please sort out your drivers18:40
neoshadesbut as ubuntu now install 3.7.2 on quantal why are mainline not built with such - no worries will compile my own from git18:40
apwand no shipping random source on your website does not fit the definition of 'sort out'18:40
apwneoshades, it is built in a precise environment to let us use them on the LTS and later18:41
sforsheeI think broadcom generally cares more about the fullmac drivers because that's what android devices use ...18:41
apwthe only downside is that binary drivers do not work, and frankly we don't care about them18:41
apwsforshee, and therefore they should not make devices for anything else18:41
apwsforshee, or they shoudl sort out something useful18:41
apweither or, don't care18:42
apwjust don't make me live with their lazyness18:42
sforsheemaybe I need to try and get my hands on a BCM4313 card18:42
apwi should try swapping my pcix card in this machine with something from intel18:42
apwand give you the thing18:42
sforsheeI can get one of amazon for about $1218:43
sforsheemight cost you more to ship it to me ;-)18:43
apwsforshee, expense it18:43
* henrix -> EOD18:44
=== henrix is now known as henrix_
neoshadesso what u are saying is that as gcc is updated the kernels in the archive are compiled with latest gcc18:50
neoshadesas per LTS18:50
apwa mainline kernel is built with the nearest configuration series wise, and in the previous LTS chroot wise18:57
apwto maximise what it can be installed safely on18:57
apw(given it is a completly automated build and no brains are applied in their making)18:59
apwneoshades, ^^18:59
infinityneoshades: The mainline kernels are meant for nothing more than quick testing of "if this is broken in the distro kernel, does it work with mainline?", they're not meant for people to run.19:01
apwBenC, i ahve pushed the config change and abi bump to the branch, it builds for me in a cross environment but a proper build test on something ppc would be good19:35
=== mainerror is now known as mainerror^away
=== mainerror^away is now known as mainerror
=== emma is now known as em
=== kentb is now known as kentb-afk

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