/srv/irclogs.ubuntu.com/2016/08/09/#ubuntu-kernel.txt

=== zokko is now known as Guest42347
lorddoskiaswhere can i see the changelogs for the latest ubuntu kernel releases?06:47
smblorddoskias, If those are not yet shown in the update notifications, one place would be https://launchpad.net/ubuntu/+source/linux/+publishinghistory (you would need to click on the version numbers in the last column)07:30
lorddoskiassmb: thank you 07:30
alkisgHi, while adding support for raspberry pi in LTSP, I'm wondering which one should be the recommented kernel, linux-image-raspi2 from the stock ubuntu repositories, or raspberrypi-bootloader which is what ubuntu-mate ships with...08:14
alkisgAnd if it's the first one, where would the users get the firmware then, is it available in another .deb package?08:15
ppisatialkisg: i'm not familiar with raspberrypi-bootloader in ubuntu-mate, does it contain a kernel?08:28
alkisgppisati: yes, and also the firmware08:28
alkisgLet me upload the dpkg -L somewhere...08:28
alkisgppisati: http://paste.ubuntu.com/22784924/08:30
alkisgIt's very convinent because I only need to copy the /boot folder to netbooted clients, it has config.txt and kernel.img and the device tree and everything inside there08:31
alkisg*convenient08:32
ppisatilooks like they packaged the binary kernel from the raspberry foundation08:32
ppisatialkisg: for the ubuntu side of your question, linux-raspi2 contains only the kernel and dtbs08:36
ppisatialkisg: while for the firmware (bootloaders stuff&c), it's here: linux-firmware-raspi208:36
alkisgppisati: thank you... I guess the other part of the question should by asked to flexiondotorg, for which specific reasons he bothered to create raspberrypi-bootloader...08:39
flexiondotorgThe Pi image for Ubuntu MATE use the kernel from the Raspberry Pi Foundation, as it is packaged for Raspbian. Therefore, I also use the same bootloader, firmware and blobs that that kernel requires.08:49
flexiondotorgI would like to start working towards using the raspi2 kernel in Ubuntu in future releases though.08:50
alkisgflexiondotorg: so for newly created chroots, e.g. for LTSP netbooted clients, would you recommend the -raspi2 approach?08:53
alkisgLTSP users normally have an i386/amd64 server, and run `ltsp-build-client -a armhf` to generate a chroot for their raspberries, which is something like `debootstrap` and `apt install ubuntu-mate-desktop ltsp-client`, so they don't need to download the ubuntu mate image at all...08:56
alkisgppisati: linux-firmware-raspi2.postinst fails in chroots for 2 reasons, (1) the directory /boot/firmware doesn't exist, and then after manually creating it, (2) /bin/sync: error syncing '/boot/firmware/bootcode.bin': Function not implemented09:09
alkisgShould I file a bug report there?09:09
alkisgFor (1), a `mkdir -p /boot/firmware` should suffice, while for (2), a `|| true` should allow it to finish until qemu implements the sync call...09:10
alkisg...or, maybe it shouldn't bother creating a firmware folder at all, chroots don't need it09:15
ppisatialkisg: wait, hold on09:40
* alkisg waits :)09:42
ppisatialkisg: i thought these problems were already resolved09:55
alkisgppisati: I have: linux-firmware-raspi2 1.20151118+b70b451-0ubuntu109:58
alkisg(whatever comes with 16.04)09:59
alkisgMaybe some missing SRU? /me checks the bug reports...09:59
alkisgNope, I couldn't find any related bug reports, and it's the same version that even yakkety ships, so I guess the problems are still there10:00
=== mwhudson_ is now known as mwhudson
=== jibel_ is now known as jibel
=== JanC is now known as Guest75507
=== JanC_ is now known as JanC
=== Guest42347 is now known as zokko
=== jdstrand_ is now known as jdstrand
=== ghostcube_ is now known as ghostcube
xnoxbjf, given apw is afk can we cowboy  zfcpdump-kernel into yakkety new? =)15:46
* xnox highlights ogasawara too15:46
xnoxfrom the bootstrap ppa15:46
ogasawaraxnox: I thought we just agreed that it could wait until apw returns?15:51
xnoxogasawara, is he gonna be back before feature-freeze, or will it not matter for the feature freeze as it's not really new package?15:53
ogasawarahrm, when is feature freeze?15:53
xnox18th of august, next thursday15:54
* xnox checks again15:54
xnoxlast i pinged apw, he was like yeah it should be uploaded - somewhere in this channel backscroll.15:54
xnox1715:54
xnoxAugust 18th15:54
xnoxWarning /!\ FeatureFreeze, Warning /!\ DebianImportFreeze15:54
xnox17 is WorkWeek number15:55
ogasawaraxnox: ack.  so no, apw will not be back before then.15:55
xnoxalthough we should have it in 16.10, it will only matter to ibm once it's in 16.04. And we will have to SRU it somehow anyway.15:56
xnoxIt does Build-Depends: debhelper (>= 9), linux-source-4.4.0, bc15:56
xnoxsuch that when 4.6 hits the archive, it will stop be buildable in yakkety =(15:57
xnoxogasawara, are you gonna land 4.6 without apw?15:57
xnoxoh, 4.8 is targetted for 16.10, as per newsletters15:58
ogasawaraxnox: indeed, the final target is v4.8, and v4.7 is released...ideally we'd get v4.6 up now-ish and then rev to v4.715:59
ogasawaraxnox: indeed it would be nice to have apw around when we made the jump though15:59
xnoxrightio, and i think apw only ever wanted to maintain one series of zfcdump-kernel, and i'm guessing he'd want 4.4 one in both yakkety & xenial.16:00
xnoxso i think i'm gonna rest the case until he is back, to figure out what to do, cause possibly zfcdump-kernel will need to include linux-source-4.4 inside it, rather than as a build-dep.16:00
ogasawaraxnox: ack16:01
=== bguthro_ is now known as bguthro

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