-
Notifications
You must be signed in to change notification settings - Fork 126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to Linux 4.14 #49
base: master
Are you sure you want to change the base?
Conversation
How can I upgrade my box to test it ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
everything seems to be fine, I think that it should be merged and allow the pi64-update tool to perform the upgrade automatically
I think that we should upgrade to 4.14.11 and release to users as soon as possible given the current meltdown security issue ... |
Not that updating the kernel is not important anyway, but regarding Meltdown and Spectre, they don't affect the SoC used in any of the Raspberry Pi (including 3). https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/ |
Can this be merged then? what is blocking this merge? |
It has been a long time since last upgrade is released. I have tried to build the 4.14 kernel, but I don't know how to deal with the "firmware". I wonder if this repository is maintained? |
If there will be no update: https://github.com/Debian/raspi3-image-spec --EDIT-- those are the bits from the build script but you have to dist-upgrade to buster first and then cross fingers it will reboot :) TODO: install raspi3-firmware and linux-image-arm64 from buster once theymigrated in sufficiently recent versions.
|
Would it be possible to have instructions on how to upgrade to the 4.14 kernels? I mean using this: cc3bfd2 I'm not sure what to do with that. |
@Xnyle |
Any news here, @bamarni? |
@xilopaint |
This upgrades to Linux 4.14, I'm not pushing this directly to master as I just have made a build locally without releasing for now.