-
Notifications
You must be signed in to change notification settings - Fork 3
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
Kernel updates? #18
Comments
I've been to sick to work on the project lately, but here is the long term strategy https://aur.archlinux.org/packages/linux-jwrdegoede-git/ Possibly the repo this ISO installed for you can be updated to include that package instead of its package that is unable to be updated. @joshskidmore |
I have an optimized version of linux-pf. |
linux-pf-silvermont |
@Thaodan Have you made any optimizations that are relevant to the GPD Pocket? |
I enabled all needed kernel flags that were missing from ARCH and pf and build the kernel with march silvermont (the soc of the device).
I also split the packages present In the repos to the minimum and wrote a script for non interactive install.
Am 16. Juli 2018 12:59:03 MESZ schrieb "Sigurd Bøe" <[email protected]>:
…
@Thaodan Have you made any optimizations that are relevant to the GPD
Pocket?
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#18 (comment)
|
I set up my Pocket in January using archlinux-gpd-pocket-2018.01.05-x86_64.iso and your guide.
Updating with pacman -Syu every couple of weeks since, I've seen some minor system issues appear and disappear, but uname still shows
Arch Linux 4.15.0-rc6-jwrdegoede
so I'm assuming I'm still running a kernel from four months back.Can I do anything to get a newer kernel? Or is this still the latest version with Pocket patches? I can't find a GPDPocket kernel repo at https://github.com/jwrdegoede, so where does it come from?
Basically, what's the longer-term strategy for keeping Arch fully up-to-date on the Pocket, after installing from the ISO?
The text was updated successfully, but these errors were encountered: