Package Details: linux-linode 5.17.5.hardened1-1

Git Clone URL: (read-only, click to copy)
Package Base: linux-linode
Description: Kernel for Linode servers
Upstream URL:
Licenses: GPL2
Conflicts: grub-legacy
Submitter: yar
Maintainer: yar
Last Packager: yar
Votes: 7
Popularity: 0.000000
First Submitted: 2012-07-21 04:06 (UTC)
Last Updated: 2022-05-03 23:11 (UTC)

Latest Comments

Scimmia commented on 2020-12-10 16:40 (UTC)

Please see the warning here:

tea commented on 2016-01-20 14:34 (UTC)

CFLAGS should target haswell rather than corei7. That is according to the steps on Gentoo wiki for determining the correct -march type.

tea commented on 2015-08-15 00:46 (UTC)

Do any changes to this need to be made now that Linode has KVM nodes?

akiirui commented on 2014-12-18 10:31 (UTC)

Some wrong in the menu.lst Kernel optional config -> console=hvc0 loglevel=4 ro rootflags=noatime,nodiratime,data=journal,barrier=0,commit=5,journal=update,errors=remount-ro kaslr ->journal=update can't working on Linode. So, remember delete this line/words.

m0ikz commented on 2014-09-20 17:32 (UTC)

I'm getting this error while trying to load a module, the system is fully updated. modprobe: ERROR: could not insert 'bridge': Cannot allocate memory I can't find the reason for this error, is not only for the bridge module, i con't load any module.

m0ikz commented on 2014-06-12 17:18 (UTC)

Hello, can you please enable "CONFIG_DM_THIN_PROVISIONING" it's needed for docker devicemapper graphdriver. Thanks

tea commented on 2014-04-19 01:35 (UTC)

Another comment about CONFIG_NR_CPUS. Linode now has variable vcpu sizes depending on your plan. So I guess that should be set to the highest possible value? The largest Linode plan has 20 vcpus.

yar commented on 2013-12-12 23:31 (UTC)

@xyproto Thanks so much for the tips and feedback. I think containers should work now - let me know if you still have problems!

xyproto commented on 2013-12-10 11:12 (UTC)

See also the output from lxc-checkconfig. It would he nice to run docker containers on linode, but also understandable if you feel it is out of scope for this package. I think it will only grow in popularity, though.

xyproto commented on 2013-12-09 13:44 (UTC)

Please set CONFIG_BRIDGE=y so that it is possible to run docker containers. (docker is an official package in [community]). Thanks for maintaining!

yar commented on 2013-09-17 21:47 (UTC)

Just to update you all, for the past few months I have been using and testing both i686 and x86_64 versions. Please report any problems as always.

Det commented on 2013-05-12 11:14 (UTC)

I meant more like "does it really need GRUB1", but apparently it does.

yar commented on 2013-05-07 00:25 (UTC)

menu.lst is in the backup array, so it should be very easy to use your own.

Det commented on 2013-05-07 00:12 (UTC)

Does it have to install menu.lst?

tea commented on 2013-04-14 23:02 (UTC)

CONFIG_NR_CPUS has been set to 4 while Linode has 8 vcpu instances at the moment, should probably change that back to 8.

yar commented on 2013-04-10 05:27 (UTC)

@tea: Yes, that's normal. I opened this bug report about that message last year, but it wasn't really a priority: If the message annoys you, you can remove autodetect from HOOKS in /etc/mkinitcpio.conf - personally I leave it in anyway. By the way, I haven't pushed the 3.8 PKGBUILD here yet because it had some filesystem and/or block errors on one of my linodes and I'm still not certain why. But I'm working on it. Sorry for the delay!

tea commented on 2013-04-10 00:25 (UTC)

It is normal for mkinitcpio to tell me: -> Running build hook: [fsck] ==> WARNING: No modules were added to the image. This is probably not what you want. ==> Creating gzip initcpio image: /boot/initramfs-linux-linode.img ==> WARNING: errors were encountered during the build. The image may not be complete. Right? This is with the PKGBUILD straight from git (so 3.8.6).

yar commented on 2012-12-14 00:07 (UTC)

I am not able to test 3.7 on i686 right now. While it is a good guess that if 64-bit works, so does 32, I will in general not be able to test or guarantee i686 in the future. Feedback, testing and pull requests always welcome!

yar commented on 2012-12-07 04:24 (UTC)

Now supports 32-bit, thanks to Xreaper's configging and testing!

yar commented on 2012-11-05 20:52 (UTC)

I don't have any 32-bit linodes to test on atm. Working on making it happen, though! Thanks for your patience. :)

tea commented on 2012-11-05 11:35 (UTC)

Yeah I'd be interested in getting this on 32bit. I'm not quite adventurous enough to against Linode's recommendation for a 32bit distribution just yet.

ChrisW commented on 2012-10-11 05:28 (UTC)

Linode recommends 32 bit distributions for the smaller 512 MB Linodes. What changes would you recommend to adapt this package to i686?