=== mamarley_ is now known as mamarley | ||
=== inaddy is now known as tinoco | ||
=== Elimin8r is now known as Elimin8er | ||
=== eichiro_ is now known as eichiro | ||
=== samkottler_ is now known as samkottler | ||
=== AceLan_ is now known as AceLan | ||
=== manjo` is now known as manjo | ||
=== alai` is now known as alai | ||
=== _ruben_ is now known as _ruben | ||
LocutusOfBorg | apw, please sync kernel modules from virtualbox | 08:53 |
---|---|---|
LocutusOfBorg | 5.1.14 has important fixes | 08:53 |
LocutusOfBorg | also the kernel that will go in 16.04.2 probably needs updates from here https://launchpad.net/ubuntu/+source/virtualbox/5.0.32-dfsg-0ubuntu1.16.04.2 | 08:54 |
LocutusOfBorg | apw, I'm back :) | 09:57 |
=== mhcerri_ is now known as mhcerri | ||
apw | LocutusOfBorg, the .2 kernel will be the hwe kernel and has (in theory) | 11:35 |
apw | Vileda SuperMocio 3 Action Refill - Twin Pack by Vileda | 11:35 |
apw | no not that | 11:35 |
apw | 5.1.6-dfsg-2 | 11:35 |
LocutusOfBorg | tooo old | 11:35 |
LocutusOfBorg | 5.1.14 has fixes | 11:35 |
apw | that is what is _in_ yakkety, which is where the kernel comes from | 11:35 |
LocutusOfBorg | so kernel 4.8? | 11:36 |
apw | yes, it will be essentially yakkety's kernel | 11:36 |
LocutusOfBorg | ok fine then | 11:36 |
LocutusOfBorg | fixes are for kernel 4.9+ | 11:36 |
LocutusOfBorg | so, please apply them for zesty only | 11:37 |
apw | ack | 11:52 |
LocutusOfBorg | but question: most changes are build fixes for newer kernels, how do you handle them? I can't understand how you can update the kernel without updating vbox kernel modules too | 11:58 |
=== jdstrand_ is now known as jdstrand | ||
jsalisbury | stgraber, I'll post a link to a test kernel in bug 1655842? shortly | 13:05 |
ubot5 | bug 1655842 in linux (Ubuntu Xenial) ""Out of memory" errors after upgrade to 4.4.0-59" [High,Triaged] https://launchpad.net/bugs/1655842 | 13:05 |
=== ben_r_ is now known as ben_r | ||
montvid | hi there. i would like to ask for a kernel fix as written in http://askubuntu.com/questions/674179/ubuntu-device-flash-fails-on-nexus-7-2013-android-5-0-2-cant-copy-image-to the device is officialy supported but completly not installing for more than a year now. see bug https://bugs.launchpad.net/canonical-devices-system-image/+bug/1496756 | 14:33 |
ubot5 | Ubuntu bug 1496756 in Canonical System Image "Nexus 7 devices which ship with android 5 need revised storage drivers" [High,Confirmed] | 14:33 |
montvid | how come a device that is supported officialy does not work at all for over a year? | 14:34 |
montvid | i asked popey in ubuntu touch and he answered he has no idea what to do... | 14:35 |
montvid | i see people in xda fixed their twrp recovery, made a kitkat boot image and are good. is there a possibility to merge these changes in ubuntu touch kernel? | 14:38 |
montvid | because the nexus 7 device bought in 2015 and later do not install at all. How can it have support if it does not boot? | 14:41 |
montvid | any ideas? | 14:43 |
montvid | :) | 14:43 |
LocutusOfBorg | montvid, the patch posted on askubuntu is already inside the kernel AFAIK | 14:48 |
LocutusOfBorg | commit 6636bad839d9936e73e48c4841eda83a58fcdb53 | 14:48 |
LocutusOfBorg | $ git tag --contains 6636bad839d9936e73e48c4841eda83a58fcdb53 |head -n 1 | 14:48 |
LocutusOfBorg | v3.11 | 14:48 |
LocutusOfBorg | the first one was kernel 3.11, shipping that fix | 14:48 |
montvid | but nexus 7 is on 3.4.0 as i understand? | 14:49 |
LocutusOfBorg | so, the fix is already there | 14:50 |
LocutusOfBorg | s/is/should be | 14:50 |
montvid | is the fix applied to ubuntu recovery too? because yesterday it did not install. it installed with github files only. | 14:51 |
montvid | https://github.com/ddagunts/UTCWM_N7_patch/blob/master/boot.img?raw=true | 14:52 |
montvid | using this repo i could install ubuntu touch stable | 14:53 |
montvid | i get the same error as in the bug link | 14:54 |
montvid | if i try to use official builds of boot.img and recovery.img | 14:54 |
montvid | thanks for the info LocutusOfBorg | 14:55 |
LocutusOfBorg | I'm not an Ubuntu kernel developer unfortunately, so I don't know how they patch it | 14:55 |
montvid | well android devices can not change kernel versions. they stay in the same branch nexus 7 2013 is in 3.4 branch and cant go to 3.5 | 14:58 |
montvid | or 3.11 | 14:58 |
montvid | can anyone change the bug status from high to critical? | 14:59 |
montvid | because of this bug one cant install and run the system. seems critical :) | 15:00 |
LocutusOfBorg | which bug? | 15:06 |
montvid | <montvid> hi there. i would like to ask for a kernel fix as written in http://askubuntu.com/questions/674179/ubuntu-device-flash-fails-on-nexus-7-2013-android-5-0-2-cant-copy-image-to the device is officialy supported but completly not installing for more than a year now. see bug https://bugs.launchpad.net/canonical-devices-system-image/+bug/1496756 | 15:07 |
ubot5 | Ubuntu bug 1496756 in Canonical System Image "Nexus 7 devices which ship with android 5 need revised storage drivers" [High,Confirmed] | 15:07 |
montvid | sorry for the dublicate | 15:07 |
LocutusOfBorg | mterry, ^^ seems that I can't change the bug severity :) | 15:10 |
montvid | thanks for trying | 15:10 |
montvid | maybe you could add a comment? i dont have a login... | 15:11 |
LocutusOfBorg | it won't add much value :/ | 15:11 |
montvid | i understand. | 15:15 |
caribou | smb: FYI, uploaded crash 7.1.7-1ubuntu1; autopkgtest found a bug which is fixed in post 7.1.7 so I have just uploaded a ubuntu2 with the upstream fix | 15:36 |
=== JanC_ is now known as JanC | ||
smb | caribou, oh ok. I just recently saw some crash going to the archive but have not looked closely at the version numbers | 15:44 |
caribou | smb: well, it got stucked into -proposed following a failure in DEP8 test | 15:45 |
caribou | smb: the failure is specific to live crash session so I missed it by testing on a _real_ kernel crash | 15:45 |
smb | caribou, Ah, but at least good to see the dep8 testing being good for something | 15:46 |
caribou | smb: indeed; I should have run it before uploading though | 15:46 |
smb | caribou, True, though I must admit that often I forget that part, too. | 15:48 |
stgraber | jsalisbury: thanks | 15:59 |
jsalisbury | stgraber, good timing. The build just finished. Once second, I'll scp it and drop a link | 15:59 |
jsalisbury | stgraber, http://kernel.ubuntu.com/~jsalisbury/lp1655842/armhf/ | 16:01 |
stgraber | jsalisbury: thanks. I'll install that on one of the boards and see if it shows OOM over the next 24 hours (it's a jenkins runner) | 16:01 |
jsalisbury | stgraber, thanks | 16:01 |
=== ratliff_ is now known as ratliff | ||
setuid | Is there a way to parallelize update-initramfs on a test box with hundreds of kernels? | 19:58 |
setuid | update-grub takes hours | 19:58 |
setuid | It | 20:00 |
setuid | It's a pipeline from a failed apt-get, so running dpkg --configure -a | 20:00 |
setuid | This sort of works, but it's ugly: ls -1 /boot/vmlinuz* | cut -b9-40 | while read line; do sudo update-initramfs -c -k $line & done; | 20:17 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!