/srv/irclogs.ubuntu.com/2011/10/21/#ubuntu-kernel.txt

=== ericm-Zzz is now known as ericm
EtienneGhey guys!  Quick q.: when is the next SRU for lucid scheduled?12:36
hertonEtienneG: if everything goes well, current one will probably released next week, once testing finishes (current SRU being tracked in bug 871899)12:43
ubot2Launchpad bug 871899 in kernel-sru-workflow "linux: 2.6.32-35.78 -proposed tracker" [Undecided,In progress] https://launchpad.net/bugs/87189912:43
hertonthe next one I think will be prepared right after UDS12:43
EtienneGherton, cool stuff, thanks herton!12:44
EtienneGherton, do we have a calendar, or a report, or somesuch to track these?  I'll bookmark it and refer t it in the future.12:45
hertonEtienneG: we have a report of all SRUs in progress here: http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html12:46
hertonwe also have a calendar, but it's not always reliable, because of regressions etc. it may offset sometimes12:46
hertonusually each SRU cycle is each 3 weeks12:47
EtienneGherton, yeah, I understand the cadence is three weeks but likely to slip due to regression.  At least, if I can track what the *plan*, it is already a start!  :)12:48
hertonEtienneG: we have an internal google calendar with the likely schedule, but it's not public I think12:53
hertons/it's not/nothing12:58
hggdhherton: btw, did you see my comment on bug 872660?13:21
ubot2Launchpad bug 872660 in kernel-sru-workflow/regression-testing "linux-lts-backport-maverick: 2.6.35-30.61~lucid1 -proposed tracker" [Undecided,In progress] https://launchpad.net/bugs/87266013:21
hertonhggdh: yep, https://bugs.launchpad.net/ubuntu/+source/linux-lts-backport-maverick/+bug/872660/comments/513:21
ubot2Launchpad bug 872660 in kernel-sru-workflow/regression-testing "linux-lts-backport-maverick: 2.6.35-30.61~lucid1 -proposed tracker" [Undecided,In progress]13:21
hggdhherton: I agree, but I needed it. I cannot decide for the kernel team13:23
hertonhggdh: sure, no problem. This warning shouldn't hold the update13:24
hggdhherton: all yours to promote to updates13:25
hertonack13:26
hggdhnow, for the next13:26
* ogasawara back in 2013:42
hertonppisati: on next fsl-imx51 update, you will be able to use verify-release-ready from kteam-tools to check for common problems like missing tracking bug etc., before pushing. The same is true for all other arm branches, except mvl-dove from maverick, as the script doesn't like the lucid version being used, I'll take a look if it's feasible to fix13:53
hertonops, in fact on mvl-dove from maverick it doesn't like the missing abi files13:58
ogra_lucid is dead for armel13:59
ogra_EOL message should have gone out last week (sadly it wasnt yet), dont put work into lucid distro stuff13:59
hertonogra_: true for lucid mvl-dove, but maverick mvl-dove should still be updated from what I got14:00
ogra_herton, i was more referring to fsl-imx5114:01
ogra_dove exists in maverick, but to my knowledge we never supported a kernel for it14:01
ogra_(in maverick that is)14:01
hertonogra_: good news, once official word gets out14:05
ogra_yeah, i was promised the announcement for last friday ... i'll hunt down kate today14:05
gentoo_drummerI used the command line installation since i hate unity and installed xfce. the system is incredible fast, even quicker than my debian and i was wondering if someone could tell me how can i get the default ubuntu font rendering14:28
gentoo_drummerany ideas guys/14:29
gentoo_drummer?14:29
ogra_and you expect the kernel team to know that ? thats brave :)14:31
gentoo_drummer:P14:32
ogra_try #ubuntu-desktop ;)14:32
gentoo_drummerwell.. i assume that kernel team tweks with things14:32
* ogra_ guesses they are to understaffed to have time for that :)14:32
ppisatiherton: cool, thanks! :)14:37
hggdhherton: do we have a backport from Oneiric?14:43
ogra_herton, so i just talked to kate ... the actual 18 months for lucid are only over on the 29th so EOL announcement for lucid will go out then, but please dont do any kernel work on lucid arm kernels anymore, would be wasted time14:44
hertonhggdh: yes, tracked in bug 87881114:45
ubot2Launchpad bug 878811 in linux-lts-backport-oneiric "linux-lts-backport-oneiric: 3.0.0-13.21~lucid1 -proposed tracker" [Medium,In progress] https://launchpad.net/bugs/87881114:45
hertonok14:45
hggdhherton: it does not show up on http://people.canonical.com/~kernel/reports/sru-report.html ?14:46
hertonhggdh: no, I don't know why, bjf ^14:48
hggdhherton: since I already have lucid loaded, I will go ahead and do 878811 also; of course, may redo if verification fails14:48
hertonhggdh: ok. http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html lists it though14:48
bjfherton, hggdh, will look into it14:49
ogra_herton, so i also just confirmed again, there was never a dove kernel in maverick, if there is thats a big mistake and its definitely not supported by any of us (or you)15:07
hertonhmm ok15:09
hertongoing to lunch, bbl15:09
bjfogra_: that is quite amusing since we did ship a mvl-dve maverick kernel (2.6.32 based) and have been supporting it since release15:20
ogra_bjf, yes, we never should have done that, that kernel was for NCommanders tests and should have been removed from the archive before release day15:21
ogra_bjf, wrt dove in maverick we only support the userspace15:21
bjfpgraner: ^ nice eh?15:21
ogra_(sorry, i didnt even know that kernel exists, i (nor anyone else but NCommander) wasnt involved in dove after lucid)15:22
ogra_the more intresting question is, is there a way to remove it from a released archive ....15:23
ogra_if its there now, i guess it should see security maintenance at least, would be good to avoid that15:23
bjfogra_: we work on it every 3 weeks15:24
ogra_ugh15:24
ogra_what a waste of manpower15:24
hggdhherton, bjf: bug 879516, I am failing this kernel16:05
bjfhggdh: any reason that bug is private ?16:08
hggdhbjf: a security test failed16:08
hggdhbjf: you should have access, I subscribed the kernel team16:08
hggdhbjf: I will move straight ahead to the Oneiric proposed kernel now, and check it16:09
bjfherton, hggdh, the lts-backport-oneiric tracking bug is not on the sru-report because the tracking bug was not added to the changelog16:20
hggdhbjf: ah, thank you16:21
hertonbjf: ack, I thought it could be this, since we weren't able to create the bug report earlier16:23
hertonand put in the changelog16:24
hggdhherton: jj found the issue on the oneiric backport to be a test case failure; as such, I am tagging it -passed17:54
cndbjf, do you know who does the wiki gardening for the kernel team?17:56
cndI'm wondering how to create a table with borders17:57
bjfcnd we've let it go to weeds17:57
cndurg17:57
bjfcnd there's a moin style/syntax help page that explains it17:58
bjfi think17:58
cndI can't find anything on borders though17:58
cndand the ubuntu wiki by default doesn't show borders17:58
cndwhich makes it hard to read tables17:58
cndoh wait, I can check the release schedule page17:58
cndthat has borders17:58
cndor not17:59
hertonhggdh: ok, cool18:28
tathiI just reformatted an old ubuntu box and installed 11.10, and while it installed the rt61pci driver automatically, my wireless card isn't picking up the router's SSID.19:54
tathi(connect to hidden network works fine, as do all other computers in the house)19:54
tathiShould I be reporting this as a bug?19:54
ohsixhow long did you wait for the ap to show up19:55
tathiIt took me probably 15-20 minutes to figure out how to get it up, find the SSID from another box, and all that.19:56
tathiSo long enough, I think.19:57
ohsixthere are a few moving parts, and unless something is very broken it's not the kernel or the driver19:57
tathiHrm.19:57
ohsixnm-tool can display what networkmanager sees, the applet might have its own criteria for displaying stuff19:57
tathiAny other suggestions?  It worked fine under Ubuntu 9.04 this morning, then I spent an hour or so reinstalling.  Didn't move the computer, so the hardware should still be fine.19:58
tathiWhat applet?19:59
ohsixthat fancy thing on your desktop that actually shows a list of things to connect to is just a small part of it20:00
tathiAh.  I was mostly poking around with command-line tools, though I didn't change anything.20:00
tathilspci, iwlist, lshw, that sort of thing.20:01
ohsixnm-tool should pretty much tell you all you need to know, delete the connection for the ap you're trying to accessing, disable networking, reenable; check and see if nm-tool shows the ap you're interested about20:01
tathiI'll try that.  Thanks!20:02
tathiNope, same thing.20:10
tathiWell, I suppose I could pull the card and test it on another computer in case it randomly broke at the same time I upgraded the software...20:18
tathiSeems odd that it can connect fine though.20:19
ohsixsame thing what? nm-tool doesn't list the ap?20:20
tathiright.20:20
tathiIf it's connected, it lists the normal stuff.20:20
tathiDisconnect, and it still lists the ap.20:21
ohsixwhat driver was it again?20:21
tathidisable networking and delete entry, enable it again and still no ap.20:21
tathirt61pci20:21
ohsixcan you post the output of dmesg to a pastebin20:23
tathigrr...don't have xclip.  yeah, hang on.20:25
tathihttp://pastebin.com/ebpjssCs20:27
tathiIs this the right place to ask this?  I could go find someone else to bother... :)20:28
=== yofel_ is now known as yofel
ohsixwell, #linux-wireless20:30
=== kentb is now known as kentb-out

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