=== zokko is now known as Guest42347 | ||
lorddoskias | where can i see the changelogs for the latest ubuntu kernel releases? | 06:47 |
---|---|---|
smb | lorddoskias, 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 |
lorddoskias | smb: thank you | 07:30 |
alkisg | Hi, 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 |
alkisg | And if it's the first one, where would the users get the firmware then, is it available in another .deb package? | 08:15 |
ppisati | alkisg: i'm not familiar with raspberrypi-bootloader in ubuntu-mate, does it contain a kernel? | 08:28 |
alkisg | ppisati: yes, and also the firmware | 08:28 |
alkisg | Let me upload the dpkg -L somewhere... | 08:28 |
alkisg | ppisati: http://paste.ubuntu.com/22784924/ | 08:30 |
alkisg | It'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 there | 08:31 |
alkisg | *convenient | 08:32 |
ppisati | looks like they packaged the binary kernel from the raspberry foundation | 08:32 |
ppisati | alkisg: for the ubuntu side of your question, linux-raspi2 contains only the kernel and dtbs | 08:36 |
ppisati | alkisg: while for the firmware (bootloaders stuff&c), it's here: linux-firmware-raspi2 | 08:36 |
alkisg | ppisati: 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 |
flexiondotorg | The 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 |
flexiondotorg | I would like to start working towards using the raspi2 kernel in Ubuntu in future releases though. | 08:50 |
alkisg | flexiondotorg: so for newly created chroots, e.g. for LTSP netbooted clients, would you recommend the -raspi2 approach? | 08:53 |
alkisg | LTSP 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 |
alkisg | ppisati: 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 implemented | 09:09 |
alkisg | Should I file a bug report there? | 09:09 |
alkisg | For (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 it | 09:15 |
ppisati | alkisg: wait, hold on | 09:40 |
* alkisg waits :) | 09:42 | |
ppisati | alkisg: i thought these problems were already resolved | 09:55 |
alkisg | ppisati: I have: linux-firmware-raspi2 1.20151118+b70b451-0ubuntu1 | 09:58 |
alkisg | (whatever comes with 16.04) | 09:59 |
alkisg | Maybe some missing SRU? /me checks the bug reports... | 09:59 |
alkisg | Nope, 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 there | 10: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 | ||
xnox | bjf, given apw is afk can we cowboy zfcpdump-kernel into yakkety new? =) | 15:46 |
* xnox highlights ogasawara too | 15:46 | |
xnox | from the bootstrap ppa | 15:46 |
ogasawara | xnox: I thought we just agreed that it could wait until apw returns? | 15:51 |
xnox | ogasawara, 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 |
ogasawara | hrm, when is feature freeze? | 15:53 |
xnox | 18th of august, next thursday | 15:54 |
* xnox checks again | 15:54 | |
xnox | last i pinged apw, he was like yeah it should be uploaded - somewhere in this channel backscroll. | 15:54 |
xnox | 17 | 15:54 |
xnox | August 18th | 15:54 |
xnox | Warning /!\ FeatureFreeze, Warning /!\ DebianImportFreeze | 15:54 |
xnox | 17 is WorkWeek number | 15:55 |
ogasawara | xnox: ack. so no, apw will not be back before then. | 15:55 |
xnox | although 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 |
xnox | It does Build-Depends: debhelper (>= 9), linux-source-4.4.0, bc | 15:56 |
xnox | such that when 4.6 hits the archive, it will stop be buildable in yakkety =( | 15:57 |
xnox | ogasawara, are you gonna land 4.6 without apw? | 15:57 |
xnox | oh, 4.8 is targetted for 16.10, as per newsletters | 15:58 |
ogasawara | xnox: 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.7 | 15:59 |
ogasawara | xnox: indeed it would be nice to have apw around when we made the jump though | 15:59 |
xnox | rightio, 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 |
xnox | so 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 |
ogasawara | xnox: ack | 16:01 |
=== bguthro_ is now known as bguthro |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!