I'm still using CentOS 4.6, but have been planning an upgrade to CentOS 5 for quite a while. One of the things that was holding me back is that the CentOS 5.0 kernel did not have the framebuffer support enabled by default. So I waited for CentOS 5.1. However, on one of my test systems I ran into the bad NFS performance issue (see CentOS bug 2635), so I plan to use the centosplus kernel. However, it appears that this kernel does not have the framebuffer support enabled -- arrgghhh!
So, is this just an oversight or is there a reason for not enabling the framebuffer support on the centosplus kernel?
Alfred (who really wants to upgrade to CentOS 5 but cannot live with the NFS performance issue and does not want to build his own kernel RPMs)
On Wed, Apr 16, 2008 at 2:46 PM, Alfred von Campe alfred@von-campe.com wrote:
I'm still using CentOS 4.6, but have been planning an upgrade to CentOS 5 for quite a while. One of the things that was holding me back is that the CentOS 5.0 kernel did not have the framebuffer support enabled by default. So I waited for CentOS 5.1. However, on one of my test systems I ran into the bad NFS performance issue (see CentOS bug 2635), so I plan to use the centosplus kernel. However, it appears that this kernel does not have the framebuffer support enabled -- arrgghhh!
So, is this just an oversight or is there a reason for not enabling the framebuffer support on the centosplus kernel?
Alfred (who really wants to upgrade to CentOS 5 but cannot live with the NFS performance issue and does not want to build his own kernel RPMs)
I confirm that the centosplus kernel has the framebuffer support disabled:
# CONFIG_FB_VESA is not set
I don't know how this has happened but am sure we will hear from Johnny Hughes :-D
You have another choice here if you would rather not wait for the next update of the centosplus kernel. The standard kernel with the same NFS bug fix is available from:
http://people.centos.org/hughesjr/kernel/5/
I have just checked the kernels in there; they do have the framebuffer support enabled.
Akemi
On Apr 16, 2008, at 19:21, Akemi Yagi wrote:
You have another choice here if you would rather not wait for the next update of the centosplus kernel. The standard kernel with the same NFS bug fix is available from:
http://people.centos.org/hughesjr/kernel/5/
I have just checked the kernels in there; they do have the framebuffer support enabled.
But what is the best way to include all the appropriate kernel RPMs from that location in an automated kickstart build? I mirror my own repo, so I guess I could do what I want, but this is how I currently get the centosplus kernel from a script called in the kickstart %post section:
yum --enablerepo centosplus -y update
Voila, I get all the latest updates as well as the centosplus kernel.
Alfred
On Thu, Apr 17, 2008 at 7:11 AM, Alfred von Campe alfred@von-campe.com wrote:
On Apr 16, 2008, at 19:21, Akemi Yagi wrote:
You have another choice here if you would rather not wait for the next update of the centosplus kernel. The standard kernel with the same NFS bug fix is available from:
http://people.centos.org/hughesjr/kernel/5/
I have just checked the kernels in there; they do have the framebuffer support enabled.
But what is the best way to include all the appropriate kernel RPMs from that location in an automated kickstart build? I mirror my own repo, so I guess I could do what I want, but this is how I currently get the centosplus kernel from a script called in the kickstart %post section:
yum --enablerepo centosplus -y updateVoila, I get all the latest updates as well as the centosplus kernel.
If you have your own mirror, the easiest way would be to get those bz321111 kernels in your repo. Johnny Hughes or other CentOS devs need to chime in here about the plan for those kernels, but my (wild) guess is that those kernels stay there until they are no longer needed, namely until 5.2 comes out in which the NFS bug is (supposedly) fixed.
Or else, depending on how soon the next kernel update comes out, you may want to wait for the centosplus kernel with the vesa framebuffer support turned on (provided the change is made in the next release). I will do my best in reminding Johnny of the corrections. :-)
Akemi
On Apr 17, 2008, at 10:34, Akemi Yagi wrote:
If you have your own mirror, the easiest way would be to get those bz321111 kernels in your repo. Johnny Hughes or other CentOS devs need to chime in here about the plan for those kernels, but my (wild) guess is that those kernels stay there until they are no longer needed, namely until 5.2 comes out in which the NFS bug is (supposedly) fixed.
Well, the way I set up my mirror is by rsync'ing the entire directory structure from one of the public mirrors. What are the steps I would have to run to update my local mirror to include Johnny's RPMs? I would also have to redo this update after every rsync. And how will these kernels then be automatically installed if they are in the repo? This does not seem to be that easy.
Or else, depending on how soon the next kernel update comes out, you may want to wait for the centosplus kernel with the vesa framebuffer support turned on (provided the change is made in the next release). I will do my best in reminding Johnny of the corrections. :-)
Any chance this will happen before next Wednesday? That's when I'm planning to start my upgrades...
Alfred
On Thu, Apr 17, 2008 at 10:41 AM, Alfred von Campe alfred@von-campe.com wrote:
On Apr 17, 2008, at 10:34, Akemi Yagi wrote:
If you have your own mirror, the easiest way would be to get those bz321111 kernels in your repo. Johnny Hughes or other CentOS devs need to chime in here about the plan for those kernels, but my (wild) guess is that those kernels stay there until they are no longer needed, namely until 5.2 comes out in which the NFS bug is (supposedly) fixed.
Well, the way I set up my mirror is by rsync'ing the entire directory structure from one of the public mirrors. What are the steps I would have to run to update my local mirror to include Johnny's RPMs? I would also have to redo this update after every rsync. And how will these kernels then be automatically installed if they are in the repo? This does not seem to be that easy.
Regarding how to set up your own local repo, please refer to this CentOS wiki:
http://wiki.centos.org/HowTos/CreateLocalRepos
Then you should be able to install the kernel from your local repo in the same way as you did with the centosplus kernel.
Or else, depending on how soon the next kernel update comes out, you may want to wait for the centosplus kernel with the vesa framebuffer support turned on (provided the change is made in the next release). I will do my best in reminding Johnny of the corrections. :-)
Any chance this will happen before next Wednesday? That's when I'm planning to start my upgrades...
I doubt it, but you never know because this is up to our upstream vendor.
Akemi
On Apr 17, 2008, at 14:02, Akemi Yagi wrote:
Any chance this will happen before next Wednesday? That's when I'm planning to start my upgrades...
I doubt it, but you never know because this is up to our upstream vendor.
I was thinking about a new centosplus kernel before next week -- is that dependent on upstream? In other words, are centosplus kernels released only when there is an upstream kernl release or can they be released at any time a CentOS maintainer deems necessary?
Alfred
On Thu, Apr 17, 2008 at 12:09 PM, Alfred von Campe alfred@von-campe.com wrote:
On Apr 17, 2008, at 14:02, Akemi Yagi wrote:
Any chance this will happen before next Wednesday? That's when I'm planning to start my upgrades...
I doubt it, but you never know because this is up to our upstream vendor.
I was thinking about a new centosplus kernel before next week -- is that dependent on upstream? In other words, are centosplus kernels released only when there is an upstream kernl release or can they be released at any time a CentOS maintainer deems necessary?
As far as I know, centosplus kernels are released only when the distro kernel is updated. However, only Johnny Hughes or CentOS devs can give you an "official" answer to your question. Johnny, where are you? Wake up :-D
Akemi
Akemi Yagi wrote:
On Thu, Apr 17, 2008 at 12:09 PM, Alfred von Campe alfred@von-campe.com wrote:
On Apr 17, 2008, at 14:02, Akemi Yagi wrote:
Any chance this will happen before next Wednesday? That's when I'm planning to start my upgrades...
I doubt it, but you never know because this is up to our upstream vendor.
I was thinking about a new centosplus kernel before next week -- is that dependent on upstream? In other words, are centosplus kernels released only when there is an upstream kernl release or can they be released at any time a CentOS maintainer deems necessary?
As far as I know, centosplus kernels are released only when the distro kernel is updated. However, only Johnny Hughes or CentOS devs can give you an "official" answer to your question. Johnny, where are you? Wake up :-D
Sorry,
I have been busy with trying to roll out puppet on the centos infrastructure.
I normally only release kernels for CentOS Plus with the same numbers and at the same times as the upstream kernels.
Right now we are also trying to get several versions of openoffice.org built for the latest updates just released by upstream, which is tying up the builders.
Since I did screw this up, I will release a new version as soon as I can after the current set of updates are done, but that might not be by Wednesday.
Thanks, Johnny Hughes
2008/4/19 Johnny Hughes johnny@centos.org:
Akemi Yagi wrote:
I normally only release kernels for CentOS Plus with the same numbers and at the same times as the upstream kernels.
Since I did screw this up, I will release a new version as soon as I can after the current set of updates are done, but that might not be by Wednesday.
Thanks, Johnny Hughes
The centosplus kernel update that just came out (2.6.18-53.1.19.el5.centos.plus) does have vesafb support enabled. Thank you, Johnny, for the work. :-)
Akemi
On May 11, 2008, at 9:06, Akemi Yagi wrote
The centosplus kernel update that just came out (2.6.18-53.1.19.el5.centos.plus) does have vesafb support enabled. Thank you, Johnny, for the work. :-)
It finally trickled down to my mirror, and a quick install this morning shows that is indeed fixed. This is great! I do have a couple of issues with CentOS 5.1, but I'll start a separate thread for those.
Thanks again, Alfred
-
Akemi Yagi -
Alfred von Campe -
Johnny Hughes