/srv/irclogs.ubuntu.com/2013/12/13/#ubuntu-kernel.txt

infinityphillw: A 486 kernel would do you no good, our userspace targets 686.00:16
infinityphillw: So, your kernel would boot and then nothing would run.00:17
phillwhiyas infinity so, can you see any way around 32 bit non-pae and a working kernel?00:17
infinityphillw: non-pae is an entirely different question than 486.00:18
infinityphillw: The answer to non-pae is to build your own kernel, we intentionally dropped the support, we won't pick it up again.00:18
infinityphillw: There are a few PPAs that rebuild the archive kernels as non-pae, if I recall.00:19
infinity(Sorry, don't know which PPAs, but Google or launchpad's search might know)00:19
infinityphillw: If you wanted it on your images, it would have to be in the archive, which means a lubuntu dev would need to commit to supporting it, because we won't.00:19
phillwinfinity: could you have a look at http://packages.debian.org/cgi-bin/search_packages.pl?keywords=kernel-image and let me know if you spot a non-pae version? I spotted powerppc etc.00:26
infinityphillw: You don't want a Debian kernel, you want a fork of the Ubuntu kernel with CONFIG_PAE turned off.00:34
infinityphillw: And like I said, this would need to be something you'd need to get someone to commit to maintaining as a rebase, or you're doing your users a disservice.00:35
infinity(stable security support, etc)00:35
phillwinfinity: it would be a one off respin for 13.10, then with 14.04 a respin for the .1, .2, .3. .... I'm just trying to get some ideas in my head. As these people have no other option, locking the kernel is the least of their security worries. Having ability to update the browsers is far more important. I do fully understand what you, from the kernel team say in terms of no security updates; but, when stuck between a rock and a hard place, would y00:48
infinityphillw: Being able to update their browser can be done with 12.0400:54
phillwinfinity: lubuntu did not have an lts back then :) Tech Board prohibited it, for a start and we were still too young to ask :)00:55
infinityphillw: Not being an LTS doesn't mean your users somehow magically don't get the updates from the archive.00:55
phillwindeed not, but it does stop the browser updates, which are the most at risk.00:56
phillwinfinity: "The package information was last updated 290 days ago" There are no updates to install.01:02
phillwinfinity: can we swap to another channel, as this is off-topic for kernel? :)01:03
phillwinfinity: a thousand apologies, the VM has just found a shed load of updates that it wants. ::SIGH:: I am really sorry.01:14
phillwinfinity: after update of the 12.04 I have http://packages.debian.org/cgi-bin/search_packages.pl?keywords=kernel-image02:20
phillwgrrrrrr....02:20
=== shuduo_afk is now known as shuduo
=== shuduo is now known as shuduo_afk
=== shuduo_afk is now known as shuduo
=== gfrog_meeting is now known as gfrog
=== shuduo is now known as shuduo_afk
=== shuduo_afk is now known as shuduo
=== shuduo is now known as shuduo_afk
=== shuduo_afk is now known as shuduo
=== shuduo is now known as shuduo_away
arahello!10:43
ara12.04.4 kernel freeze was scheduled for yesterday10:43
araI would like to confirm that it actually happened10:43
arathanks!10:43
rtgsmb, cking: are you guys aware of any new grub issues ? I'm updating a kernel in Precise. Its been stuck here for 10 minutes:13:03
rtg32503 pts/4    S+     0:00 /bin/sh /usr/lib/os-probes/50mounted-tests /dev/sda113:03
rtg32508 pts/4    D+     0:00 grub-mount /dev/sda1 /var/lib/os-prober/mount13:03
rtg32541 ?        S      0:00 /sbin/udevd --daemon13:03
rtg32672 ?        S      0:00 /sbin/udevd --daemon13:03
ckingnew one to me13:03
rtgah, I have an outstanding nfs mount I'll bet13:03
smbHm... not sure somehow os-prober stuck does ring a faint distant bell13:03
rtghow about this ? '[403127.854359] nfs: server 10.0.2.254 not responding, still trying'13:04
rtgthat server is turned off13:04
smbNot really sure about the relation. Just that nagging feeling I have seen someone saying something about grub and stuck recently13:05
smbMay have been on #ubuntu-devel or ... 13:05
smbBut could be something smart thinking some OS might be on the nfs side13:06
=== psivaa_ is now known as psivaa
=== marrusl_ is now known as marrusl
bjfkamal, can you interpret bug 1163720 for me? as i read it the -proposed kernels do not fix the issue. 18:08
ubot2Launchpad bug 1163720 in Linux "Brightness control broken on XPS13 and 3.8.0-16, 3.8.0-22 and 3.11.0-12" [Medium,Incomplete] https://launchpad.net/bugs/116372018:08
* kamal reads the tea leaves18:09
bjfkamal, i can't tell what comment #81 is supposed to be telling me18:10
kamalbjf -- here's the scoop ...18:11
bjfthis should be *good* :-P18:11
kamalno18:12
kamalits not18:12
kamalthis problem still isn't fixed upstream and I got sick of waiting, so (see comment #76) I implemented a boot param ...18:12
kamalin comment #77, Dan from Dell confirmed that the boot param does resolve the problem (which only affects a small (?) number of XPS13 users, who opt to enable a particular UEFI configuration).18:13
kamalthe boot param fix did get SRU'd for P through S ... that's about the best we're going to be able to do for this issue, until upstream fixes backlight "for good" (hahahaha!)18:14
kamalit looks to me like commenters #81, #82, #83 didn't try using the new boot param, so (not surprisingly) they saw no change in behavior.18:14
kamalI'll add a comment to the bug asking them to test that.18:15
bjfkamal, cool ... i'm good with that18:15
kamalbjf, you should just clear it from your list18:15
bjfkamal, i'm not going to give it another thought18:15
kamalbjf, wish I could say the same :-/18:15
sforsheethe fact that we have so much trouble with friggin' backlights makes me want to weep18:16
mjg59Well, it doesn't help that people keep trying to fix them with boot parameters18:18
mjg59Or quirks18:18
kamalmjg59, I'm not happy about it either, but given the choice between quirk out *one* register set in i915, vs. making hundreds of users suffer another 12 months of broken backlight ...  well, I'll stick by my choice.18:23
* rtg -> lunch18:25
=== infinity_ is now known as infinity
bjfmanjo, can you verify bug 1248233 is fixed?18:44
ubot2Launchpad bug 1248233 in linux (Ubuntu) "[saucy][armhf] No early printk because there's no defined device tree binding for earlyprintk UART" [Medium,Confirmed] https://launchpad.net/bugs/124823318:44
manjobjf, yes I did verify that it is fixed ... I can add a comment to that bug with more info 18:45
manjobjf, give me 20mts 18:45
bjfmanjo, just need the tags fixed18:45
bjfmanjo, i'll take care of it18:45
manjobjf, you don't need testing info there then ? 18:46
bjfmanjo, i just need the tags fixed. that indicates you did the testing.18:47
manjobjf, look like you already moved it to done .. thanks I also added some test data 18:49
bjfmanjo, ack18:50
* rtg -> EOD21:13

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