Hi Mike,
On Tue, 16 Dec 2014 11:22:34 -0600 Michael J Wolf mjwolf@us.ibm.com wrote:
Hi We briefly discussed priorities for Fedora 22 and I had taken an action item to start an email conversation about this. So here is what I would like to see for Fedora 22.
- Get the -mcpu and -mtune flags set properly for the LE build.
Should be -mcpu=power7 -mtune=power8
done, all packages that honour the Fedora system wide compiler flags use them, if they don't it's a packaging bug
- Have a cloud image available
- For BE I would like another subarch. Same packages as the current
one but tuned for P8.
you mean in addition to ppc64p7? can't we just switch ppc64p7 from -mcpu=power7 -mtune=power7 to -mcpu=power7 -mtune=power8?
- Looking into if we can get Docker enabled for POWER. I will send
out further emails about this as soon as I know more about the current development state 5) Start the ground work for a workstation release. But I think we should target the release for Fedora-23.
yeah, the deadlines in F-22 won't give us enough time to work on it
I seem to remember hearing that there is a quite a lot of workinvolved to get this build going.
we should have almost everything built (eg. LibreOffice is known to fail to build), but it's not tested and if broken, it will need to be fixed
One thing to not forgot is that also the mainline kernel needs to have the necessary support for the workstation class hw.
Dan
Hi We briefly discussed priorities for Fedora 22 and I had taken an action item to start an email conversation about this. So here is what I would like to see for Fedora 22.
- Get the -mcpu and -mtune flags set properly for the LE build.
Should be -mcpu=power7 -mtune=power8
done, all packages that honour the Fedora system wide compiler flags use them, if they don't it's a packaging bug
- Have a cloud image available
- For BE I would like another subarch. Same packages as the current
one but tuned for P8.
you mean in addition to ppc64p7? can't we just switch ppc64p7 from -mcpu=power7 -mtune=power7 to -mcpu=power7 -mtune=power8?
This makes sense to me as it then mirrors what we have in ppc64le and it saves having more targets.
- Looking into if we can get Docker enabled for POWER. I will send
out further emails about this as soon as I know more about the current development state 5) Start the ground work for a workstation release. But I think we should target the release for Fedora-23.
yeah, the deadlines in F-22 won't give us enough time to work on it
Agreed, ultimately all the packages are built and as a result it's possible to install and test all the main components of Workstation for those that actually have desktop capable hardware to do any development/testing/debug that is required to ensure all the underlying workstation components and dependencies are in a good state for Fedora 23.
It's likely there will be work needed on the X stack components like mesa etc to ensure all is working.
I seem to remember hearing that there is a quite a lot of workinvolved to get this build going.
we should have almost everything built (eg. LibreOffice is known to fail to build), but it's not tested and if broken, it will need to be fixed
One thing to not forgot is that also the mainline kernel needs to have the necessary support for the workstation class hw.
I think the biggest thing will be the graphics stack. While all the workstation bits are built I doubt they've had wide and varied testing to ensure they're al sufficiently optimised and robust for a good Workstation experience.
Peter
Subject:
Re: Fedora 22
Sent by:
ppc-bounces@lists.fedoraproject.org
Hi We briefly discussed priorities for Fedora 22 and I had taken an action item to start an email conversation about this. So here is what I would like to see for Fedora 22.
- Get the -mcpu and -mtune flags set properly for the LE build.
Should be -mcpu=power7 -mtune=power8
done, all packages that honour the Fedora system wide compiler flags use them, if they don't it's a packaging bug
- Have a cloud image available
- For BE I would like another subarch. Same packages as the current
one but tuned for P8.
you mean in addition to ppc64p7? can't we just switch ppc64p7 from -mcpu=power7 -mtune=power7 to -mcpu=power7 -mtune=power8?
This makes sense to me as it then mirrors what we have in ppc64le and it saves having more targets.
The disadvantage of this would be to cut off users that have Power 7 systems and optimized code. So why would people want to optimize from Fedora 21 to Fedora 22. You would be taking a big step back in performance. I don't want to suggest keeping a subarch for each type of POWER system out there. I was thinking of keeping two. So when the next POWER arch that comes out, the Power 7 subarch goes away and you would have Power 8 and the new Power arch.
- Looking into if we can get Docker enabled for POWER. I will send
out further emails about this as soon as I know more about the current development state 5) Start the ground work for a workstation release. But I think we should target the release for Fedora-23.
yeah, the deadlines in F-22 won't give us enough time to work on it
Agreed, ultimately all the packages are built and as a result it's possible to install and test all the main components of Workstation for those that actually have desktop capable hardware to do any development/testing/debug that is required to ensure all the underlying workstation components and dependencies are in a good state for Fedora 23.
It's likely there will be work needed on the X stack components like mesa etc to ensure all is working.
I seem to remember hearing that there is a quite a lot of workinvolved to get this build going.
we should have almost everything built (eg. LibreOffice is known to
fail
to build), but it's not tested and if broken, it will need to be fixed
One thing to not forgot is that also the mainline kernel needs to have the necessary support for the workstation class hw.
I think the biggest thing will be the graphics stack. While all the workstation bits are built I doubt they've had wide and varied testing to ensure they're al sufficiently optimised and robust for a good Workstation experience.
Peter _______________________________________________ ppc mailing list ppc@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/ppc
Subject:
Re: Fedora 22
Sent by:
ppc-bounces@lists.fedoraproject.org
Hi We briefly discussed priorities for Fedora 22 and I had taken an action item to start an email conversation about this. So here is what I would like to see for Fedora 22.
- Get the -mcpu and -mtune flags set properly for the LE build.
Should be -mcpu=power7 -mtune=power8
done, all packages that honour the Fedora system wide compiler flags use them, if they don't it's a packaging bug
- Have a cloud image available
- For BE I would like another subarch. Same packages as the
current
one but tuned for P8.
you mean in addition to ppc64p7? can't we just switch ppc64p7 from -mcpu=power7 -mtune=power7 to -mcpu=power7 -mtune=power8?
This makes sense to me as it then mirrors what we have in ppc64le and it saves having more targets.
The disadvantage of this would be to cut off users that have Power 7
systems
and optimized code. So why would people want to optimize from Fedora 21
to
Fedora 22. You would be taking a big step back in performance. I don't want to suggest keeping a subarch for each type of POWER system out
there. I
was thinking of keeping two. So when the next POWER arch that comes out, the Power 7 subarch goes away and you would have Power 8 and the new Power arch.
The above comment is not correct I was assuming -mcpu=power8 but your comment states -mcpu=power7 so yes that is reasonable and keeps things consistent across BE and LE. The only drawback here is that you would be leaving some performance behind as you would not be using all the new Power 8 instructions.
- Looking into if we can get Docker enabled for POWER. I will send
out further emails about this as soon as I know more about the current development state 5) Start the ground work for a workstation release. But I think we should target the release for Fedora-23.
yeah, the deadlines in F-22 won't give us enough time to work on it
Agreed, ultimately all the packages are built and as a result it's possible to install and test all the main components of Workstation for those that actually have desktop capable hardware to do any development/testing/debug that is required to ensure all the underlying workstation components and dependencies are in a good state for Fedora 23.
It's likely there will be work needed on the X stack components like mesa etc to ensure all is working.
I seem to remember hearing that there is a quite a lot of workinvolved to get this build going.
we should have almost everything built (eg. LibreOffice is known to
fail
to build), but it's not tested and if broken, it will need to be
fixed
One thing to not forgot is that also the mainline kernel needs to
have
the necessary support for the workstation class hw.
I think the biggest thing will be the graphics stack. While all the workstation bits are built I doubt they've had wide and varied testing to ensure they're al sufficiently optimised and robust for a good Workstation experience.
Peter _______________________________________________ ppc mailing list ppc@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/ppc
ppc mailing list ppc@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/ppc
On Tue, 16 Dec 2014 14:22:14 -0600 Michael J Wolf mjwolf@us.ibm.com wrote:
Subject:
Re: Fedora 22
Sent by:
ppc-bounces@lists.fedoraproject.org
Hi We briefly discussed priorities for Fedora 22 and I had taken an action item to start an email conversation about this. So here is what I would like to see for Fedora 22.
- Get the -mcpu and -mtune flags set properly for the LE
build. Should be -mcpu=power7 -mtune=power8
done, all packages that honour the Fedora system wide compiler flags use them, if they don't it's a packaging bug
- Have a cloud image available
- For BE I would like another subarch. Same packages as the
current
one but tuned for P8.
you mean in addition to ppc64p7? can't we just switch ppc64p7 from -mcpu=power7 -mtune=power7 to -mcpu=power7 -mtune=power8?
This makes sense to me as it then mirrors what we have in ppc64le and it saves having more targets.
The disadvantage of this would be to cut off users that have Power 7
systems
and optimized code. So why would people want to optimize from Fedora 21
to
Fedora 22. You would be taking a big step back in performance. I don't want to suggest keeping a subarch for each type of POWER system out
there. I
was thinking of keeping two. So when the next POWER arch that comes out, the Power 7 subarch goes away and you would have Power 8 and the new Power arch.
The above comment is not correct I was assuming -mcpu=power8 but your comment states -mcpu=power7 so yes that is reasonable and keeps things consistent across BE and LE. The only drawback here is that you would be leaving some performance behind as you would not be using all the new Power 8 instructions.
I think it (as not using P8 instructions) would be acceptable compromise for a binary distribution. But it would be interesting to see some numbers what the difference between the various combinations of -mcpu and -mtune and used hardware is.
Also introducing a new subarch means updating (patching) our build and release engineering tools starting with rpm itself.
Dan
Subject:
Re: Fedora 22
Sent by:
ppc-bounces@lists.fedoraproject.org
Hi We briefly discussed priorities for Fedora 22 and I had taken an action item to start an email conversation about this. So here is what I would like to see for Fedora 22.
- Get the -mcpu and -mtune flags set properly for the LE build.
Should be -mcpu=power7 -mtune=power8
done, all packages that honour the Fedora system wide compiler flags use them, if they don't it's a packaging bug
- Have a cloud image available
- For BE I would like another subarch. Same packages as the
current
one but tuned for P8.
you mean in addition to ppc64p7? can't we just switch ppc64p7 from -mcpu=power7 -mtune=power7 to -mcpu=power7 -mtune=power8?
This makes sense to me as it then mirrors what we have in ppc64le and it saves having more targets.
The disadvantage of this would be to cut off users that have Power 7
systems
and optimized code. So why would people want to optimize from Fedora 21
to
Fedora 22. You would be taking a big step back in performance. I don't want to suggest keeping a subarch for each type of POWER system out
there. I
was thinking of keeping two. So when the next POWER arch that comes out, the Power 7 subarch goes away and you would have Power 8 and the new Power arch.
- Looking into if we can get Docker enabled for POWER. I will send
out further emails about this as soon as I know more about the current development state 5) Start the ground work for a workstation release. But I think we should target the release for Fedora-23.
yeah, the deadlines in F-22 won't give us enough time to work on it
Agreed, ultimately all the packages are built and as a result it's possible to install and test all the main components of Workstation for those that actually have desktop capable hardware to do any development/testing/debug that is required to ensure all the underlying workstation components and dependencies are in a good state for Fedora 23.
It's likely there will be work needed on the X stack components like mesa etc to ensure all is working.
I seem to remember hearing that there is a quite a lot of workinvolved to get this build going.
we should have almost everything built (eg. LibreOffice is known to
fail
to build), but it's not tested and if broken, it will need to be
fixed
One thing to not forgot is that also the mainline kernel needs to
have
the necessary support for the workstation class hw.
I think the biggest thing will be the graphics stack. While all the workstation bits are built I doubt they've had wide and varied testing to ensure they're al sufficiently optimised and robust for a good Workstation experience.
Adding 5) update gcc to version 5. Will that be possible? It is my understanding that the gccgo changes needed to support Docker are in that release
We briefly discussed priorities for Fedora 22 and I had taken an action item to start an email conversation about this. So here is what I would like to see for Fedora 22.
- Get the -mcpu and -mtune flags set properly for the LE build.
Should be -mcpu=power7 -mtune=power8
done, all packages that honour the Fedora system wide compiler flags use them, if they don't it's a packaging bug
- Have a cloud image available
- For BE I would like another subarch. Same packages as the current
one but tuned for P8.
you mean in addition to ppc64p7? can't we just switch ppc64p7 from -mcpu=power7 -mtune=power7 to -mcpu=power7 -mtune=power8?
This makes sense to me as it then mirrors what we have in ppc64le and it saves having more targets.
The disadvantage of this would be to cut off users that have Power 7 systems and optimized code. So why would people want to optimize from Fedora 21 to Fedora 22. You would be taking a big step back in performance. I don't want to suggest keeping a subarch for each type of POWER system out there. I was thinking of keeping two. So when the next POWER arch that comes out, the Power 7 subarch goes away and you would have Power 8 and the new Power arch.
- Looking into if we can get Docker enabled for POWER. I will send
out further emails about this as soon as I know more about the current development state 5) Start the ground work for a workstation release. But I think we should target the release for Fedora-23.
yeah, the deadlines in F-22 won't give us enough time to work on it
Agreed, ultimately all the packages are built and as a result it's possible to install and test all the main components of Workstation for those that actually have desktop capable hardware to do any development/testing/debug that is required to ensure all the underlying workstation components and dependencies are in a good state for Fedora 23.
It's likely there will be work needed on the X stack components like mesa etc to ensure all is working.
I seem to remember hearing that there is a quite a lot of workinvolved to get this build going.
we should have almost everything built (eg. LibreOffice is known to fail to build), but it's not tested and if broken, it will need to be fixed
One thing to not forgot is that also the mainline kernel needs to have the necessary support for the workstation class hw.
I think the biggest thing will be the graphics stack. While all the workstation bits are built I doubt they've had wide and varied testing to ensure they're al sufficiently optimised and robust for a good Workstation experience.
Adding 5) update gcc to version 5. Will that be possible? It is my understanding that the gccgo changes needed to support Docker are in that release
That is only possible if it's done as part of mainline Fedora. The standard policy for all secondary architectures is to have identical package set (and NVRs) to that of the primary architectures. Otherwise it ceases to be the same as mainline and hence a fork of Fedora. That being said the maintainers of gcc in Fedora are also maintainers and developers upstream and will actively rebase the Fedora toolchain to newer releases as part of the development process but they only do it when they believe that it is ready. So if it's ready to go by the "System Wide Changes" Change checkpoint [1] in time for a mass rebuild it will be in F-22, else I suspect it'll be in F-22 else it will land in a subsequent release.
On 12/16/2014 08:03 PM, Michael J Wolf wrote:
Hi We briefly discussed priorities for Fedora 22 and I had taken an action item to start an email conversation about this. So here is what I would like to see for Fedora 22.
- Get the -mcpu and -mtune flags set properly for the LE build.
Should be -mcpu=power7 -mtune=power8
done, all packages that honour the Fedora system wide compiler flags use them, if they don't it's a packaging bug
- Have a cloud image available
- For BE I would like another subarch. Same packages as the current
one but tuned for P8.
you mean in addition to ppc64p7? can't we just switch ppc64p7 from -mcpu=power7 -mtune=power7 to -mcpu=power7 -mtune=power8?
This makes sense to me as it then mirrors what we have in ppc64le and it saves having more targets.
The disadvantage of this would be to cut off users that have Power 7 systems and optimized code. So why would people want to optimize from Fedora 21 to Fedora 22. You would be taking a big step back in performance. I don't want to suggest keeping a subarch for each type of POWER system out there. I was thinking of keeping two. So when the next POWER arch that comes out, the Power 7 subarch goes away and you would have Power 8 and the new Power arch.
That would mean that enthusiasts like myself, happily running Fedora on a Power 285 workstation, would lose Fedora?
I'd really like to keep it. Red Hat dropped Power5 support quite a time ago, so if there ever comes a CentOS 7 ppc to life, it'd had to be tweaked to run on those machines. *If*, that is. Furthermore, Power6 boxes aren't that old, either.
I just want to emphasize that with keeping "old" metal running (we're not talking of ancient hardware) the useable hardware available for people doing this on a hobbyists scale would be much bigger -- so would be the community. Having Power 7 and Power 8 only, that wouldn't be the case any longer.
Regards,
Timo
On Wed, Dec 17, 2014 at 3:00 AM, Timo Schöler timo@riscworks.net wrote:
On 12/16/2014 08:03 PM, Michael J Wolf wrote:
Hi We briefly discussed priorities for Fedora 22 and I had taken an action item to start an email conversation about this. So here is what I would like to see for Fedora 22.
- Get the -mcpu and -mtune flags set properly for the LE build.
Should be -mcpu=power7 -mtune=power8
done, all packages that honour the Fedora system wide compiler flags use them, if they don't it's a packaging bug
- Have a cloud image available
- For BE I would like another subarch. Same packages as the current
one but tuned for P8.
you mean in addition to ppc64p7? can't we just switch ppc64p7 from -mcpu=power7 -mtune=power7 to -mcpu=power7 -mtune=power8?
This makes sense to me as it then mirrors what we have in ppc64le and it saves having more targets.
The disadvantage of this would be to cut off users that have Power 7 systems and optimized code. So why would people want to optimize from Fedora 21 to Fedora 22. You would be taking a big step back in performance. I don't want to suggest keeping a subarch for each type of POWER system out there. I was thinking of keeping two. So when the next POWER arch that comes out, the Power 7 subarch goes away and you would have Power 8 and the new Power arch.
That would mean that enthusiasts like myself, happily running Fedora on a Power 285 workstation, would lose Fedora?
Um, what version of Fedora are you running on that? As far as I know, the recent (not End-of-Live) versions of Fedora for POWER don't really support anything less than POWER6.
josh
On Wed, 17 Dec 2014 08:43:49 -0500 Josh Boyer jwboyer@fedoraproject.org wrote:
On Wed, Dec 17, 2014 at 3:00 AM, Timo Schöler timo@riscworks.net wrote:
On 12/16/2014 08:03 PM, Michael J Wolf wrote:
Hi We briefly discussed priorities for Fedora 22 and I had taken an action item to start an email conversation about this. So here is what I would like to see for Fedora 22.
- Get the -mcpu and -mtune flags set properly for the LE
build. Should be -mcpu=power7 -mtune=power8
done, all packages that honour the Fedora system wide compiler flags use them, if they don't it's a packaging bug
- Have a cloud image available
- For BE I would like another subarch. Same packages as the
current one but tuned for P8.
you mean in addition to ppc64p7? can't we just switch ppc64p7 from -mcpu=power7 -mtune=power7 to -mcpu=power7 -mtune=power8?
This makes sense to me as it then mirrors what we have in ppc64le and it saves having more targets.
The disadvantage of this would be to cut off users that have Power 7 systems and optimized code. So why would people want to optimize from Fedora 21 to Fedora 22. You would be taking a big step back in performance. I don't want to suggest keeping a subarch for each type of POWER system out there. I was thinking of keeping two. So when the next POWER arch that comes out, the Power 7 subarch goes away and you would have Power 8 and the new Power arch.
That would mean that enthusiasts like myself, happily running Fedora on a Power 285 workstation, would lose Fedora?
Um, what version of Fedora are you running on that? As far as I know, the recent (not End-of-Live) versions of Fedora for POWER don't really support anything less than POWER6.
the kernel and user space should work on any Power CPU (some people successfully updated to F-21 on Mac G5), the limitation is the installer and how it is invoked
Dan
On Wed, Dec 17, 2014 at 8:49 AM, Dan Horák dan@danny.cz wrote:
On Wed, 17 Dec 2014 08:43:49 -0500 Josh Boyer jwboyer@fedoraproject.org wrote:
On Wed, Dec 17, 2014 at 3:00 AM, Timo Schöler timo@riscworks.net wrote:
On 12/16/2014 08:03 PM, Michael J Wolf wrote:
> Hi > We briefly discussed priorities for Fedora 22 and I had > taken an action item to start an email conversation about > this. So here is what I would like to see for Fedora 22. > > 1) Get the -mcpu and -mtune flags set properly for the LE > build. Should be -mcpu=power7 -mtune=power8
done, all packages that honour the Fedora system wide compiler flags use them, if they don't it's a packaging bug
> 2) Have a cloud image available > 3) For BE I would like another subarch. Same packages as the > current one but tuned for P8.
you mean in addition to ppc64p7? can't we just switch ppc64p7 from -mcpu=power7 -mtune=power7 to -mcpu=power7 -mtune=power8?
This makes sense to me as it then mirrors what we have in ppc64le and it saves having more targets.
The disadvantage of this would be to cut off users that have Power 7 systems and optimized code. So why would people want to optimize from Fedora 21 to Fedora 22. You would be taking a big step back in performance. I don't want to suggest keeping a subarch for each type of POWER system out there. I was thinking of keeping two. So when the next POWER arch that comes out, the Power 7 subarch goes away and you would have Power 8 and the new Power arch.
That would mean that enthusiasts like myself, happily running Fedora on a Power 285 workstation, would lose Fedora?
Um, what version of Fedora are you running on that? As far as I know, the recent (not End-of-Live) versions of Fedora for POWER don't really support anything less than POWER6.
the kernel and user space should work on any Power CPU (some people successfully updated to F-21 on Mac G5), the limitation is the installer and how it is invoked
Right, sorry. I should have been more clear. By "support" I meant "the secondary arch team is only focusing on POWER6 or newer" but really "POWER7 or newer". Which makes me wonder how older machines are getting installed when you factor in the installer thing.
josh
We briefly discussed priorities for Fedora 22 and I had taken an action item to start an email conversation about this. So here is what I would like to see for Fedora 22.
- Get the -mcpu and -mtune flags set properly for the LE build.
Should be -mcpu=power7 -mtune=power8
done, all packages that honour the Fedora system wide compiler flags use them, if they don't it's a packaging bug
- Have a cloud image available
- For BE I would like another subarch. Same packages as the current
one but tuned for P8.
you mean in addition to ppc64p7? can't we just switch ppc64p7 from -mcpu=power7 -mtune=power7 to -mcpu=power7 -mtune=power8?
This makes sense to me as it then mirrors what we have in ppc64le and it saves having more targets.
The disadvantage of this would be to cut off users that have Power 7 systems and optimized code. So why would people want to optimize from Fedora 21 to Fedora 22. You would be taking a big step back in performance. I don't want to suggest keeping a subarch for each type of POWER system out there. I was thinking of keeping two. So when the next POWER arch that comes out, the Power 7 subarch goes away and you would have Power 8 and the new Power arch.
That would mean that enthusiasts like myself, happily running Fedora on a Power 285 workstation, would lose Fedora?
No, there's a sub arch called ppc64p7 which provides optimised binaries for a sub set of packages which has been a feature for a few releases and is what is being discussed with the terms "For BE I would like another subarch"
I'd really like to keep it. Red Hat dropped Power5 support quite a time ago, so if there ever comes a CentOS 7 ppc to life, it'd had to be tweaked to run on those machines. *If*, that is. Furthermore, Power6 boxes aren't that old, either.
If there ever was a CentOS7 option for POWER I suspect they would take the same options for RHEL, and POWER6 dates back to 06/07 so define old.
I just want to emphasize that with keeping "old" metal running (we're not talking of ancient hardware) the useable hardware available for people doing this on a hobbyists scale would be much bigger -- so would be the community. Having Power 7 and Power 8 only, that wouldn't be the case any longer.
We're not dropping it, we're adjusting the ppc64p7 sub architecture for newer stuff, and that sub architecture was always POWER7 it's actually just adjusting the processors we optimise for. There is no change.
Peter
On 12/17/2014 03:23 PM, Peter Robinson wrote:
We briefly discussed priorities for Fedora 22 and I had taken an action item to start an email conversation about this. So here is what I would like to see for Fedora 22.
- Get the -mcpu and -mtune flags set properly for the LE build.
Should be -mcpu=power7 -mtune=power8
done, all packages that honour the Fedora system wide compiler flags use them, if they don't it's a packaging bug
- Have a cloud image available
- For BE I would like another subarch. Same packages as the current
one but tuned for P8.
you mean in addition to ppc64p7? can't we just switch ppc64p7 from -mcpu=power7 -mtune=power7 to -mcpu=power7 -mtune=power8?
This makes sense to me as it then mirrors what we have in ppc64le and it saves having more targets.
The disadvantage of this would be to cut off users that have Power 7 systems and optimized code. So why would people want to optimize from Fedora 21 to Fedora 22. You would be taking a big step back in performance. I don't want to suggest keeping a subarch for each type of POWER system out there. I was thinking of keeping two. So when the next POWER arch that comes out, the Power 7 subarch goes away and you would have Power 8 and the new Power arch.
That would mean that enthusiasts like myself, happily running Fedora on a Power 285 workstation, would lose Fedora?
No, there's a sub arch called ppc64p7 which provides optimised binaries for a sub set of packages which has been a feature for a few releases and is what is being discussed with the terms "For BE I would like another subarch"
Okay, then I got that wrong.
I'd really like to keep it. Red Hat dropped Power5 support quite a time ago, so if there ever comes a CentOS 7 ppc to life, it'd had to be tweaked to run on those machines. *If*, that is. Furthermore, Power6 boxes aren't that old, either.
If there ever was a CentOS7 option for POWER
There's chatting about this, yes.
Last year I started on porting CentOS 5 onto Power, but got stuck due to lack of spare time.
I suspect they would take the same options for RHEL, and POWER6 dates back to 06/07 so define old.
Sure. At least a Power 5 box isn't that old it would be the same category as a Sun SPARCstation 20, which is still supported by OpenBSD, e.g.
What may be of importance is that the 285 is the last *real* workstation, AFAIK.
Would happily buy a new workstation by IBM or the OpenPower consortium, too! :)
I am indeed just installing Final Release Candidate 6 (RC6)
https://lists.fedoraproject.org/pipermail/ppc/2014-December/003199.html
http://riscworks.net/static/Fedora/f21_285.jpg
I just want to emphasize that with keeping "old" metal running (we're not talking of ancient hardware) the useable hardware available for people doing this on a hobbyists scale would be much bigger -- so would be the community. Having Power 7 and Power 8 only, that wouldn't be the case any longer.
We're not dropping it, we're adjusting the ppc64p7 sub architecture for newer stuff, and that sub architecture was always POWER7 it's actually just adjusting the processors we optimise for. There is no change.
Peter
Thanks for clarifying this.
Timo
On Wed, 17 Dec 2014 15:40:49 +0100 Timo Schöler timo@riscworks.net wrote:
On 12/17/2014 03:23 PM, Peter Robinson wrote:
> We briefly discussed priorities for Fedora 22 and I had > taken an action item to start an email conversation about > this. So here is what I would like to see for Fedora 22. > > 1) Get the -mcpu and -mtune flags set properly for the LE > build. Should be -mcpu=power7 -mtune=power8
done, all packages that honour the Fedora system wide compiler flags use them, if they don't it's a packaging bug
> 2) Have a cloud image available > 3) For BE I would like another subarch. Same packages as the > current one but tuned for P8.
you mean in addition to ppc64p7? can't we just switch ppc64p7 from -mcpu=power7 -mtune=power7 to -mcpu=power7 -mtune=power8?
This makes sense to me as it then mirrors what we have in ppc64le and it saves having more targets.
The disadvantage of this would be to cut off users that have Power 7 systems and optimized code. So why would people want to optimize from Fedora 21 to Fedora 22. You would be taking a big step back in performance. I don't want to suggest keeping a subarch for each type of POWER system out there. I was thinking of keeping two. So when the next POWER arch that comes out, the Power 7 subarch goes away and you would have Power 8 and the new Power arch.
That would mean that enthusiasts like myself, happily running Fedora on a Power 285 workstation, would lose Fedora?
No, there's a sub arch called ppc64p7 which provides optimised binaries for a sub set of packages which has been a feature for a few releases and is what is being discussed with the terms "For BE I would like another subarch"
Okay, then I got that wrong.
I'd really like to keep it. Red Hat dropped Power5 support quite a time ago, so if there ever comes a CentOS 7 ppc to life, it'd had to be tweaked to run on those machines. *If*, that is. Furthermore, Power6 boxes aren't that old, either.
If there ever was a CentOS7 option for POWER
There's chatting about this, yes.
Last year I started on porting CentOS 5 onto Power, but got stuck due to lack of spare time.
I suspect they would take the same options for RHEL, and POWER6 dates back to 06/07 so define old.
Sure. At least a Power 5 box isn't that old it would be the same category as a Sun SPARCstation 20, which is still supported by OpenBSD, e.g.
What may be of importance is that the 285 is the last *real* workstation, AFAIK.
Would happily buy a new workstation by IBM or the OpenPower consortium, too! :)
I am indeed just installing Final Release Candidate 6 (RC6)
https://lists.fedoraproject.org/pipermail/ppc/2014-December/003199.html
Timo, how did the install go? Was is it as straightforward as placing a DVD in the drive and run?
Dan
On 01/06/2015 01:48 PM, Dan Horák wrote:
On Wed, 17 Dec 2014 15:40:49 +0100 Timo Schöler timo@riscworks.net wrote:
On 12/17/2014 03:23 PM, Peter Robinson wrote:
>> We briefly discussed priorities for Fedora 22 and I had >> taken an action item to start an email conversation about >> this. So here is what I would like to see for Fedora 22. >> >> 1) Get the -mcpu and -mtune flags set properly for the LE >> build. Should be -mcpu=power7 -mtune=power8 > > done, all packages that honour the Fedora system wide compiler > flags use them, if they don't it's a packaging bug > >> 2) Have a cloud image available >> 3) For BE I would like another subarch. Same packages as the >> current one but tuned for P8. > > you mean in addition to ppc64p7? can't we just switch ppc64p7 > from -mcpu=power7 -mtune=power7 to -mcpu=power7 -mtune=power8?
This makes sense to me as it then mirrors what we have in ppc64le and it saves having more targets.
The disadvantage of this would be to cut off users that have Power 7 systems and optimized code. So why would people want to optimize from Fedora 21 to Fedora 22. You would be taking a big step back in performance. I don't want to suggest keeping a subarch for each type of POWER system out there. I was thinking of keeping two. So when the next POWER arch that comes out, the Power 7 subarch goes away and you would have Power 8 and the new Power arch.
That would mean that enthusiasts like myself, happily running Fedora on a Power 285 workstation, would lose Fedora?
No, there's a sub arch called ppc64p7 which provides optimised binaries for a sub set of packages which has been a feature for a few releases and is what is being discussed with the terms "For BE I would like another subarch"
Okay, then I got that wrong.
I'd really like to keep it. Red Hat dropped Power5 support quite a time ago, so if there ever comes a CentOS 7 ppc to life, it'd had to be tweaked to run on those machines. *If*, that is. Furthermore, Power6 boxes aren't that old, either.
If there ever was a CentOS7 option for POWER
There's chatting about this, yes.
Last year I started on porting CentOS 5 onto Power, but got stuck due to lack of spare time.
I suspect they would take the same options for RHEL, and POWER6 dates back to 06/07 so define old.
Sure. At least a Power 5 box isn't that old it would be the same category as a Sun SPARCstation 20, which is still supported by OpenBSD, e.g.
What may be of importance is that the 285 is the last *real* workstation, AFAIK.
Would happily buy a new workstation by IBM or the OpenPower consortium, too! :)
I am indeed just installing Final Release Candidate 6 (RC6)
https://lists.fedoraproject.org/pipermail/ppc/2014-December/003199.html
Timo, how did the install go? Was is it as straightforward as placing a DVD in the drive and run?
Hi, yes, I just re-tested it with the most recent image and a 9111-285 (see dmesg etc attached). Works like a charm.
I used the GUI installer (not remote, using VNC, but really with screen and keyboard), which works well. Even without any palette mismatch, what I always got after first reboot.
I *think* the guys from cruxppc had a patch here, a friend of mine told me. I usually use console/network to work on that machine, my friend wants to use it as a real workstation, with GUI. AFAIR, the GXT6500P is supported by the kernel. I'll have a look at this -- if nobody has a hint here, I may open a bug report on this.
From drivers/video/fbdev/gxt4500.c:
/* * Frame buffer device for IBM GXT4500P/6500P and GXT4000P/6000P * display adaptors * Copyright (C) 2006 Paul Mackerras, IBM Corp. paulus@samba.org */
(...)
#define PCI_DEVICE_ID_IBM_GXT4500P 0x21c #define PCI_DEVICE_ID_IBM_GXT6500P 0x21b #define PCI_DEVICE_ID_IBM_GXT4000P 0x16e #define PCI_DEVICE_ID_IBM_GXT6000P 0x170
(...)
As said, anaconda plays well. Gnome3 does not.
If time allows, I'll try that on my 275 tomorrow, as well.
---
[ 0.000000] Allocated 2359296 bytes for 1024 pacas at c00000000f460000 [ 0.000000] Using pSeries machine description [ 0.000000] Page sizes from device-tree: [ 0.000000] base_shift=12: shift=12, sllp=0x0000, avpnm=0x00000000, tlbiel=1, penc=0 [ 0.000000] base_shift=16: shift=16, sllp=0x0110, avpnm=0x00000000, tlbiel=1, penc=1 [ 0.000000] base_shift=24: shift=24, sllp=0x0100, avpnm=0x00000001, tlbiel=0, penc=0 [ 0.000000] base_shift=34: shift=34, sllp=0x0120, avpnm=0x000007ff, tlbiel=0, penc=3 [ 0.000000] Page orders: linear mapping = 24, virtual = 16, io = 12, vmemmap = 24 [ 0.000000] Using 1TB segments [ 0.000000] cma: Reserved 1024 MiB at 3a0000000 [ 0.000000] Found initrd at 0xc000000003a00000:0xc000000004c4735c [ 0.000000] Partition configured for 2 cpus. [ 0.000000] CPU maps initialized for 2 threads per core [ 0.000000] (thread shift is 1) [ 0.000000] Freed 2293760 bytes for unused pacas [ 0.000000] Starting Linux PPC64 #1 SMP Mon Dec 1 07:50:54 UTC 2014 [ 0.000000] ----------------------------------------------------- [ 0.000000] ppc64_pft_size = 0x1c [ 0.000000] physicalMemorySize = 0x3e9000000 [ 0.000000] htab_hash_mask = 0x1fffff [ 0.000000] ----------------------------------------------------- [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.17.4-301.fc21.ppc64 (mockbuild@ppc-builder3.qa.fedoraproject.org) (gcc version 4.9.2 20141101 (Red Hat 4.9.2-1) (GCC) ) #1 SMP Mon Dec 1 07:50:54 UTC 2014 [ 0.000000] [boot]0012 Setup Arch [ 0.000000] Node 0 Memory: 0x0-0x3e9000000 [ 0.000000] PCI host bridge /pci@800000020000002 ranges: [ 0.000000] IO 0x000003fe00200000..0x000003fe002fffff -> 0x0000000000000000 [ 0.000000] MEM 0x0000040040000000..0x000004007fffffff -> 0x00000000c0000000 [ 0.000000] PCI host bridge /pci@800000020000003 ranges: [ 0.000000] IO 0x000003fe00300000..0x000003fe003fffff -> 0x0000000000000000 [ 0.000000] MEM 0x0000040080000000..0x00000400bfffffff -> 0x00000000c0000000 [ 0.000000] PCI host bridge /pci@800000020000004 ranges: [ 0.000000] IO 0x000003fe00400000..0x000003fe004fffff -> 0x0000000000000000 [ 0.000000] MEM 0x00000400c0000000..0x00000400ffffffff -> 0x00000000c0000000 [ 0.000000] PPC64 nvram contains 7168 bytes [ 0.000000] Zone ranges: [ 0.000000] DMA [mem 0x00000000-0x3e8ffffff] [ 0.000000] Normal empty [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x00000000-0x3e8ffffff] [ 0.000000] On node 0 totalpages: 256256 [ 0.000000] DMA zone: 219 pages used for memmap [ 0.000000] DMA zone: 0 pages reserved [ 0.000000] DMA zone: 256256 pages, LIFO batch:1 [ 0.000000] [boot]0015 Setup Done [ 0.000000] PERCPU: Embedded 3 pages/cpu @c000000001900000 s103168 r0 d93440 u524288 [ 0.000000] pcpu-alloc: s103168 r0 d93440 u524288 alloc=1*1048576 [ 0.000000] pcpu-alloc: [0] 0 1 [ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 256037 [ 0.000000] Policy zone: DMA [ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.17.4-301.fc21.ppc64 root=/dev/mapper/fedora--server-root ro rd.lvm.lv=fedora-server/root rd.lvm.lv=fedora-server/swap rhgb quiet LANG=en_US.UTF-8 single [ 0.000000] PID hash table entries: 4096 (order: -1, 32768 bytes) [ 0.000000] Sorting __ex_table... [ 0.000000] Memory: 15213312K/16400384K available (9408K kernel code, 1856K rwdata, 3508K rodata, 7232K init, 2683K bss, 1187072K reserved) [ 0.000000] SLUB: HWalign=128, Order=0-3, MinObjects=0, CPUs=2, Nodes=256 [ 0.000000] Hierarchical RCU implementation. [ 0.000000] RCU dyntick-idle grace-period acceleration is enabled. [ 0.000000] RCU restricting CPUs from NR_CPUS=1024 to nr_cpu_ids=2. [ 0.000000] Offload RCU callbacks from all CPUs [ 0.000000] Offload RCU callbacks from CPUs: 0-1. [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2 [ 0.000000] NR_IRQS:512 nr_irqs:512 16 [ 0.000000] pic: no ISA interrupt controller [ 0.000000] time_init: decrementer frequency = 237.336000 MHz [ 0.000000] time_init: processor frequency = 1898.100000 MHz [ 0.000003] clocksource: timebase mult[21b51dd] shift[23] registered [ 0.000007] clockevent: decrementer mult[3cc20d56] shift[32] cpu[0] [ 0.000065] Console: colour dummy device 80x25 [ 0.000145] console [tty0] enabled [ 0.015392] allocated 4100096 bytes of page_cgroup [ 0.015395] please try 'cgroup_disable=memory' option if you don't want memory cgroups [ 0.015454] mempolicy: Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl [ 0.015460] pid_max: default: 32768 minimum: 301 [ 0.015530] Security Framework initialized [ 0.015544] SELinux: Initializing. [ 0.015557] SELinux: Starting in permissive mode [ 0.015969] Dentry cache hash table entries: 2097152 (order: 8, 16777216 bytes) [ 0.021417] Inode-cache hash table entries: 1048576 (order: 7, 8388608 bytes) [ 0.024350] Mount-cache hash table entries: 32768 (order: 2, 262144 bytes) [ 0.024358] Mountpoint-cache hash table entries: 32768 (order: 2, 262144 bytes) [ 0.024925] Initializing cgroup subsys memory [ 0.025067] Initializing cgroup subsys devices [ 0.025072] Initializing cgroup subsys freezer [ 0.025077] Initializing cgroup subsys net_cls [ 0.025081] Initializing cgroup subsys blkio [ 0.025085] Initializing cgroup subsys perf_event [ 0.025090] Initializing cgroup subsys net_prio [ 0.025094] Initializing cgroup subsys hugetlb [ 0.025113] ftrace: allocating 24570 entries in 10 pages [ 0.040333] EEH: pSeries platform initialized [ 0.040344] POWER5+/++ performance monitor hardware support registered [ 0.043202] Brought up 2 CPUs [ 0.043209] Node 0 CPUs: 0-1 [ 0.045489] devtmpfs: initialized [ 0.217625] EEH: devices created [ 0.218856] atomic64_test: passed [ 0.234650] NET: Registered protocol family 16 [ 0.261367] EEH: PCI Enhanced I/O Error Handling Enabled [ 0.261486] IBM eBus Device Driver [ 0.262617] cpuidle: using governor menu [ 0.262794] pstore: Registered nvram as persistent store backend [ 0.269135] PCI: Probing PCI hardware [ 0.269148] no ibm,pcie-link-speed-stats property [ 0.269214] PCI host bridge to bus 0000:00 [ 0.269220] pci_bus 0000:00: root bus resource [io 0x10000-0x10ffff] (bus address [0x0000-0xfffff]) [ 0.269225] pci_bus 0000:00: root bus resource [mem 0x40040000000-0x4007fffffff] (bus address [0xc0000000-0xffffffff]) [ 0.269230] pci_bus 0000:00: root bus resource [bus 00-ff] [ 0.270670] pci 0000:00:01.0: supports D1 D2 [ 0.272055] IOMMU table initialized, virtual merging enabled [ 0.272187] no ibm,pcie-link-speed-stats property [ 0.272256] PCI host bridge to bus 0001:00 [ 0.272262] pci_bus 0001:00: root bus resource [io 0x120000-0x21ffff] (bus address [0x0000-0xfffff]) [ 0.272267] pci_bus 0001:00: root bus resource [mem 0x40080000000-0x400bfffffff] (bus address [0xc0000000-0xffffffff]) [ 0.272272] pci_bus 0001:00: root bus resource [bus 00-ff] [ 0.283278] pci 0001:cc:01.0: supports D1 [ 0.288890] no ibm,pcie-link-speed-stats property [ 0.288965] PCI host bridge to bus 0002:00 [ 0.288971] pci_bus 0002:00: root bus resource [io 0x230000-0x32ffff] (bus address [0x0000-0xfffff]) [ 0.288976] pci_bus 0002:00: root bus resource [mem 0x400c0000000-0x400ffffffff] (bus address [0xc0000000-0xffffffff]) [ 0.288980] pci_bus 0002:00: root bus resource [bus 00-ff] [ 0.298650] pci 0002:cc:01.0: supports D1 D2 [ 0.298655] pci 0002:cc:01.0: PME# supported from D0 D1 D2 D3hot [ 0.300627] pci 0002:cc:01.1: supports D1 D2 [ 0.300631] pci 0002:cc:01.1: PME# supported from D0 D1 D2 D3hot [ 0.302587] pci 0002:cc:01.2: supports D1 D2 [ 0.302591] pci 0002:cc:01.2: PME# supported from D0 D1 D2 D3hot [ 0.306402] pci 0002:d0:01.0: PME# supported from D0 D3hot D3cold [ 0.309729] pci 0002:d0:01.1: PME# supported from D0 D3hot D3cold [ 0.314377] PCI: Probing PCI hardware done [ 0.321498] vgaarb: device added: PCI:0000:00:01.0,decodes=io+mem,owns=mem,locks=none [ 0.321512] vgaarb: loaded [ 0.321514] vgaarb: bridge control possible 0000:00:01.0 [ 0.321636] SCSI subsystem initialized [ 0.321714] libata version 3.00 loaded. [ 0.321807] usbcore: registered new interface driver usbfs [ 0.321826] usbcore: registered new interface driver hub [ 0.321886] usbcore: registered new device driver usb [ 0.322233] NetLabel: Initializing [ 0.322236] NetLabel: domain hash size = 128 [ 0.322238] NetLabel: protocols = UNLABELED CIPSOv4 [ 0.322258] NetLabel: unlabeled traffic allowed by default [ 0.322495] Switched to clocksource timebase [ 0.334051] NET: Registered protocol family 2 [ 0.334382] TCP established hash table entries: 131072 (order: 4, 1048576 bytes) [ 0.334771] TCP bind hash table entries: 65536 (order: 4, 1048576 bytes) [ 0.334993] TCP: Hash tables configured (established 131072 bind 65536) [ 0.335032] TCP: reno registered [ 0.335042] UDP hash table entries: 8192 (order: 2, 262144 bytes) [ 0.335115] UDP-Lite hash table entries: 8192 (order: 2, 262144 bytes) [ 0.335266] NET: Registered protocol family 1 [ 0.453425] PCI: CLS 128 bytes, default 128 [ 0.453524] Unpacking initramfs... [ 0.996210] Freeing initrd memory: 18688K (c000000003a00000 - c000000004c40000) [ 0.996736] RTAS daemon started [ 0.997444] RTAS: event: 2, Type: EPOW, Severity: 2 [ 1.032917] futex hash table entries: 512 (order: 0, 65536 bytes) [ 1.032962] audit: initializing netlink subsys (disabled) [ 1.032987] audit: type=2000 audit(1421141880.030:1): initialized [ 1.033378] HugeTLB registered 16 MB page size, pre-allocated 0 pages [ 1.033381] HugeTLB registered 16 GB page size, pre-allocated 0 pages [ 1.037327] zpool: loaded [ 1.037693] VFS: Disk quotas dquot_6.5.2 [ 1.037787] Dquot-cache hash table entries: 8192 (order 0, 65536 bytes) [ 1.038708] msgmni has been set to 31928 [ 1.038841] Key type big_key registered [ 1.038847] SELinux: Registering netfilter hooks [ 1.040291] alg: No test for stdrng (krng) [ 1.040314] NET: Registered protocol family 38 [ 1.040406] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252) [ 1.040474] io scheduler noop registered [ 1.040483] io scheduler deadline registered [ 1.040553] io scheduler cfq registered (default) [ 1.040718] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [ 1.092554] Console: switching to colour frame buffer device 160x64 [ 1.135045] fb0: IBM GXT6500P frame buffer device [ 1.135881] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 1.137864] Linux agpgart interface v0.103 [ 1.138007] Uniform Multi-Platform E-IDE driver [ 1.138064] ide-gd driver 1.18 [ 1.138303] libphy: Fixed MDIO Bus: probed [ 1.138406] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 1.138427] ehci-pci: EHCI PCI platform driver [ 1.138849] ehci-pci 0002:cc:01.2: EHCI Host Controller [ 1.138934] ehci-pci 0002:cc:01.2: new USB bus registered, assigned bus number 1 [ 1.139359] ehci-pci 0002:cc:01.2: irq 276, io mem 0x400f8002000 [ 1.152503] ehci-pci 0002:cc:01.2: USB 2.0 started, EHCI 1.00 [ 1.152583] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 1.152587] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.152591] usb usb1: Product: EHCI Host Controller [ 1.152594] usb usb1: Manufacturer: Linux 3.17.4-301.fc21.ppc64 ehci_hcd [ 1.152598] usb usb1: SerialNumber: 0002:cc:01.2 [ 1.152844] hub 1-0:1.0: USB hub found [ 1.152855] hub 1-0:1.0: 5 ports detected [ 1.153191] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 1.153213] ohci-pci: OHCI PCI platform driver [ 1.153608] ohci-pci 0002:cc:01.0: OHCI PCI host controller [ 1.153695] ohci-pci 0002:cc:01.0: new USB bus registered, assigned bus number 2 [ 1.153735] ohci-pci 0002:cc:01.0: irq 276, io mem 0x400f8001000 [ 1.242544] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001 [ 1.242548] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.242552] usb usb2: Product: OHCI PCI host controller [ 1.242556] usb usb2: Manufacturer: Linux 3.17.4-301.fc21.ppc64 ohci_hcd [ 1.242559] usb usb2: SerialNumber: 0002:cc:01.0 [ 1.242777] hub 2-0:1.0: USB hub found [ 1.242791] hub 2-0:1.0: 3 ports detected [ 1.243364] ohci-pci 0002:cc:01.1: OHCI PCI host controller [ 1.243450] ohci-pci 0002:cc:01.1: new USB bus registered, assigned bus number 3 [ 1.243489] ohci-pci 0002:cc:01.1: irq 276, io mem 0x400f8000000 [ 1.332540] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001 [ 1.332544] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.332548] usb usb3: Product: OHCI PCI host controller [ 1.332552] usb usb3: Manufacturer: Linux 3.17.4-301.fc21.ppc64 ohci_hcd [ 1.332555] usb usb3: SerialNumber: 0002:cc:01.1 [ 1.332761] hub 3-0:1.0: USB hub found [ 1.332774] hub 3-0:1.0: 2 ports detected [ 1.332951] uhci_hcd: USB Universal Host Controller Interface driver [ 1.333062] usbcore: registered new interface driver usbserial [ 1.333077] usbcore: registered new interface driver usbserial_generic [ 1.333092] usbserial: USB Serial support registered for generic [ 1.333513] mousedev: PS/2 mouse device common for all mice [ 1.333844] rtc-generic rtc-generic: rtc core: registered rtc-generic as rtc0 [ 1.334210] ibmpowernv ibmpowernv.0: Opal node 'sensors' not found [ 1.334301] ibmpowernv: Platfrom driver probe failed [ 1.334520] device-mapper: uevent: version 1.0.3 [ 1.334749] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com [ 1.334972] pseries_idle_driver registered [ 1.335007] hidraw: raw HID events driver (C) Jiri Kosina [ 1.335234] usbcore: registered new interface driver usbhid [ 1.335236] usbhid: USB HID core driver [ 1.335252] drop_monitor: Initializing network drop monitor service [ 1.335370] ip_tables: (C) 2000-2006 Netfilter Core Team [ 1.335393] TCP: cubic registered [ 1.335403] Initializing XFRM netlink socket [ 1.335647] NET: Registered protocol family 10 [ 1.336014] mip6: Mobile IPv6 [ 1.336022] NET: Registered protocol family 17 [ 1.336141] Running MSI bitmap self-tests ... [ 1.339080] registered taskstats version 1 [ 1.344088] rtc-generic rtc-generic: setting system clock to 2015-01-13 09:38:00 UTC (1421141880) [ 1.344100] PM: Hibernation image not present or could not be loaded. [ 1.345344] Freeing unused kernel memory: 7232K (c000000000cb0000 - c0000000013c0000) [ 1.353097] random: systemd urandom read with 8 bits of entropy available [ 1.504923] systemd-journald[90]: File /var/log/journal/467519b2e44a45d5a02b256ebf9249de/system.journal corrupted or uncleanly shut down, renaming and replacing. [ 1.961531] pata_pdc2027x 0001:cc:01.0: version 1.0 [ 1.961964] pata_pdc2027x 0001:cc:01.0: enabling device (0002 -> 0003) [ 2.049360] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI [ 2.049366] e1000: Copyright (c) 1999-2006 Intel Corporation. [ 2.049773] e1000 0002:d0:01.0: enabling device (0000 -> 0002) [ 2.062114] pata_pdc2027x 0001:cc:01.0: PLL input clock 32754 kHz [ 2.099426] scsi host0: pata_pdc2027x [ 2.099700] scsi host1: pata_pdc2027x [ 2.099813] ata1: PATA max UDMA/133 mmio m16384@0x400b8000000 cmd 0x400b80017c0 irq 324 [ 2.099818] ata2: PATA max UDMA/133 mmio m16384@0x400b8000000 cmd 0x400b80015c0 irq 324 [ 2.116759] ipr: IBM Power RAID SCSI Device Driver version: 2.6.0 (November 16, 2012) [ 2.116789] ipr 0001:d0:01.0: Found IOA with IRQ: 325 [ 2.242529] usb 2-1: new low-speed USB device number 2 using ohci-pci [ 2.258970] ipr 0001:d0:01.0: Cannot enable MSI. [ 2.260999] ipr 0001:d0:01.0: Starting IOA initialization sequence. [ 2.265908] ipr 0001:d0:01.0: Adapter firmware version: 0510006D [ 2.273324] ata1.00: ATAPI: IBM DROM00205L1 H0, P533, max UDMA/66 [ 2.290155] ipr 0001:d0:01.0: IOA initialized. [ 2.290178] scsi host2: IBM 573E Storage Adapter [ 2.303821] scsi 2:0:3:0: Direct-Access SEAGATE ST3146707LC 0005 PQ: 0 ANSI: 3 [ 2.313090] ata1.00: configured for UDMA/66 [ 2.314245] scsi: waiting for bus probes to complete ... [ 2.315579] scsi 2:0:4:0: Direct-Access IBM-ESXS ST373405LC !# B243 PQ: 0 ANSI: 3 [ 2.323186] scsi 2:0:15:0: Enclosure IBM VSBPD4E1 U4SCSI 6000 PQ: 0 ANSI: 2 [ 2.398189] e1000 0002:d0:01.0 eth0: (PCI-X:133MHz:64-bit) 00:14:5e:96:4b:18 [ 2.398199] e1000 0002:d0:01.0 eth0: Intel(R) PRO/1000 Network Connection [ 2.398375] e1000 0002:d0:01.1: enabling device (0000 -> 0002) [ 2.469532] usb 2-1: New USB device found, idVendor=046a, idProduct=0023 [ 2.469539] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 2.548267] sd 2:0:3:0: Attached scsi generic sg0 type 0 [ 2.548652] sd 2:0:3:0: [sda] 286749488 512-byte logical blocks: (146 GB/136 GiB) [ 2.548705] sd 2:0:4:0: Attached scsi generic sg1 type 0 [ 2.549039] scsi 2:0:15:0: Attached scsi generic sg2 type 13 [ 2.550162] sd 2:0:3:0: [sda] Write Protect is off [ 2.550168] sd 2:0:3:0: [sda] Mode Sense: ab 00 10 08 [ 2.551287] scsi 0:0:0:0: CD-ROM IBM DROM00205L1 H0 P533 PQ: 0 ANSI: 2 [ 2.551516] sd 2:0:4:0: [sdb] 143374000 512-byte logical blocks: (73.4 GB/68.3 GiB) [ 2.552187] sd 2:0:3:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 2.554579] sd 2:0:4:0: [sdb] Write Protect is off [ 2.554586] sd 2:0:4:0: [sdb] Mode Sense: ab 00 10 08 [ 2.555785] sr 0:0:0:0: [sr0] scsi3-mmc drive: 24x/24x cd/rw xa/form2 cdda tray [ 2.555789] cdrom: Uniform CD-ROM driver Revision: 3.20 [ 2.556045] sr 0:0:0:0: Attached scsi CD-ROM sr0 [ 2.556254] sr 0:0:0:0: Attached scsi generic sg3 type 5 [ 2.557153] sd 2:0:4:0: [sdb] Write cache: disabled, read cache: enabled, supports DPO and FUA [ 2.564279] input: HID 046a:0023 as /devices/pci0002:00/0002:00:02.3/0002:cc:01.0/usb2/2-1/2-1:1.0/0003:046A:0023.0001/input/input0 [ 2.564449] cherry 0003:046A:0023.0001: input,hidraw0: USB HID v1.11 Keyboard [HID 046a:0023] on usb-0002:cc:01.0-1/input0 [ 2.570787] sda: sda1 sda2 sda3 [ 2.573394] sdb: sdb1 sdb2 sdb3 [ 2.576719] sd 2:0:3:0: [sda] Attached SCSI disk [ 2.578318] sd 2:0:4:0: [sdb] Attached SCSI disk [ 2.581748] input: HID 046a:0023 as /devices/pci0002:00/0002:00:02.3/0002:cc:01.0/usb2/2-1/2-1:1.1/0003:046A:0023.0002/input/input1 [ 2.581905] cherry 0003:046A:0023.0002: input,hidraw1: USB HID v1.11 Device [HID 046a:0023] on usb-0002:cc:01.0-1/input1 [ 2.734672] e1000 0002:d0:01.1 eth1: (PCI-X:133MHz:64-bit) 00:14:5e:96:4b:19 [ 2.734681] e1000 0002:d0:01.1 eth1: Intel(R) PRO/1000 Network Connection [ 2.736316] e1000 0002:d0:01.1 enP2p208s1f1: renamed from eth1 [ 2.743514] scsi 2:255:255:255: No Device IBM 573E001 0150 PQ: 0 ANSI: 0 [ 2.745338] scsi 2:255:255:255: Attached scsi generic sg4 type 31 [ 2.784012] e1000 0002:d0:01.0 enP2p208s1f0: renamed from eth0 [ 4.769462] PM: Starting manual resume from disk [ 4.769469] PM: Hibernation image partition 253:0 present [ 4.769472] PM: Looking for hibernation image. [ 4.787557] PM: Image not found (code -22) [ 4.787561] PM: Hibernation image not present or could not be loaded. [ 5.563982] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null) [ 5.933035] random: nonblocking pool is initialized [ 6.330248] systemd-journald[90]: Received SIGTERM from PID 1 (systemd). [ 6.786925] audit: type=1404 audit(1421141885.930:2): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295 [ 6.921916] SELinux: 2048 avtab hash slots, 111331 rules. [ 6.955192] SELinux: 2048 avtab hash slots, 111331 rules. [ 7.002283] SELinux: 8 users, 103 roles, 4980 types, 295 bools, 1 sens, 1024 cats [ 7.002289] SELinux: 83 classes, 111331 rules [ 7.011185] SELinux: Permission audit_read in class capability2 not defined in policy. [ 7.011195] SELinux: the above unknown classes and permissions will be allowed [ 7.011203] SELinux: Completing initialization. [ 7.011205] SELinux: Setting up existing superblocks. [ 7.011216] SELinux: initialized (dev rootfs, type rootfs), uses genfs_contexts [ 7.011234] SELinux: initialized (dev bdev, type bdev), uses genfs_contexts [ 7.011243] SELinux: initialized (dev proc, type proc), uses genfs_contexts [ 7.011364] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs [ 7.011378] SELinux: initialized (dev devtmpfs, type devtmpfs), uses transition SIDs [ 7.012370] SELinux: initialized (dev sockfs, type sockfs), uses task SIDs [ 7.012378] SELinux: initialized (dev debugfs, type debugfs), uses genfs_contexts [ 7.014023] SELinux: initialized (dev pipefs, type pipefs), uses task SIDs [ 7.014033] SELinux: initialized (dev anon_inodefs, type anon_inodefs), uses genfs_contexts [ 7.014039] SELinux: initialized (dev aio, type aio), not configured for labeling [ 7.014045] SELinux: initialized (dev devpts, type devpts), uses transition SIDs [ 7.014064] SELinux: initialized (dev hugetlbfs, type hugetlbfs), uses transition SIDs [ 7.014073] SELinux: initialized (dev hugetlbfs, type hugetlbfs), uses transition SIDs [ 7.014080] SELinux: initialized (dev mqueue, type mqueue), uses transition SIDs [ 7.014090] SELinux: initialized (dev selinuxfs, type selinuxfs), uses genfs_contexts [ 7.014130] SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts [ 7.016957] SELinux: initialized (dev securityfs, type securityfs), uses genfs_contexts [ 7.016962] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs [ 7.016971] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs [ 7.017095] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs [ 7.017149] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts [ 7.017161] SELinux: initialized (dev pstore, type pstore), uses genfs_contexts [ 7.017168] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts [ 7.017173] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts [ 7.017178] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts [ 7.017203] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts [ 7.017213] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts [ 7.017218] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts [ 7.017222] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts [ 7.017248] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts [ 7.017252] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts [ 7.017259] SELinux: initialized (dev configfs, type configfs), uses genfs_contexts [ 7.017269] SELinux: initialized (dev dm-1, type ext4), uses xattr [ 7.035942] audit: type=1403 audit(1421141886.180:3): policy loaded auid=4294967295 ses=4294967295 [ 7.064563] systemd[1]: Successfully loaded SELinux policy in 283.013ms. [ 7.181685] systemd[1]: Relabelled /dev and /run in 43.689ms. [ 8.961916] SELinux: initialized (dev autofs, type autofs), uses genfs_contexts [ 9.414749] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs [ 9.417034] SELinux: initialized (dev hugetlbfs, type hugetlbfs), uses transition SIDs [ 9.623216] EXT4-fs (dm-1): re-mounted. Opts: (null) [ 9.770029] systemd-journald[471]: Received request to flush runtime journal from PID 1 [ 10.032201] systemd-journald[471]: File /var/log/journal/467519b2e44a45d5a02b256ebf9249de/system.journal corrupted or uncleanly shut down, renaming and replacing. [ 11.464808] ttyn0 at MMIO 0x0 (irq = 275, base_baud = 921600) is a jsm [ 11.466513] jsm: Port 0 added [ 11.466520] ttyn1 at MMIO 0x0 (irq = 275, base_baud = 921600) is a jsm [ 11.466668] jsm: Port 1 added [ 11.466675] jsm 0002:c8:01.0: board 1: Digi Neo (rev 2), irq 275 [ 11.591946] scsi 2:0:15:0: Resetting device [ 11.612748] ipr 0001:d0:01.0: Adapter being reset as a result of error recovery. [ 14.714633] ipr 0001:d0:01.0: Initializing IOA. [ 24.085437] ipr 0001:d0:01.0: Starting IOA initialization sequence. [ 24.091152] ipr 0001:d0:01.0: Adapter firmware version: 0510006D [ 24.115407] ipr 0001:d0:01.0: IOA initialized. [ 34.408570] ses 2:0:15:0: Attached Enclosure device [ 35.072199] Adding 8191936k swap on /dev/mapper/fedora--server-swap. Priority:-1 extents:1 across:8191936k FS [ 35.352247] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) [ 35.356682] SELinux: initialized (dev sda2, type ext4), uses xattr [ 35.728105] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null) [ 35.728118] SELinux: initialized (dev dm-4, type ext4), uses xattr [ 159.308241] IPv6: ADDRCONF(NETDEV_UP): enP2p208s1f0: link is not ready [ 159.313125] e1000: enP2p208s1f0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [ 159.313261] IPv6: ADDRCONF(NETDEV_CHANGE): enP2p208s1f0: link becomes ready [ 236.957368] 8021q: 802.1Q VLAN Support v1.8 [ 236.957385] 8021q: adding VLAN 0 to HW filter on device enP2p208s1f0 [ 384.970540] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [ 385.045854] ip6_tables: (C) 2000-2006 Netfilter Core Team [ 385.449389] Ebtables v2.0 registered [ 385.479306] Bridge firewalling registered [ 412.123540] audit: type=1305 audit(1421142291.269:4): audit_pid=2411 old=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:auditd_t:s0 res=1 [ 416.362234] sd 2:0:3:0: [sda] Resetting device [ 417.023278] ipr 0001:d0:01.0: Adapter being reset as a result of error recovery. [ 420.124613] ipr 0001:d0:01.0: Initializing IOA. [ 429.498401] ipr 0001:d0:01.0: Starting IOA initialization sequence. [ 429.504117] ipr 0001:d0:01.0: Adapter firmware version: 0510006D [ 429.528372] ipr 0001:d0:01.0: IOA initialized. [ 440.282475] sd 2:0:4:0: [sdb] Resetting device [ 441.502151] ipr 0001:d0:01.0: Adapter being reset as a result of error recovery. [ 444.604620] ipr 0001:d0:01.0: Initializing IOA. [ 453.977474] ipr 0001:d0:01.0: Starting IOA initialization sequence. [ 453.983190] ipr 0001:d0:01.0: Adapter firmware version: 0510006D [ 454.007440] ipr 0001:d0:01.0: IOA initialized. [ 464.093683] cfg80211: Calling CRDA to update world regulatory domain [ 464.233032] cfg80211: World regulatory domain updated: [ 464.233039] cfg80211: DFS Master region: unset [ 464.233043] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 464.233049] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) [ 464.233055] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) [ 464.233061] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) [ 464.233066] cfg80211: (5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A, 2000 mBm), (N/A) [ 464.233071] cfg80211: (5250000 KHz - 5330000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) [ 464.233076] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) [ 464.233081] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) [ 464.233087] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) [ 464.774238] IPv6: ADDRCONF(NETDEV_UP): enP2p208s1f1: link is not ready [ 464.774245] 8021q: adding VLAN 0 to HW filter on device enP2p208s1f1 [ 497.293112] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
---
lspci:
0000:00:01.0 VGA compatible controller: IBM GXT6500P Graphics Adapter (rev 04) 0001:00:02.0 PCI bridge: IBM EADS-X PCI-X to PCI-X Bridge (rev 03) 0001:00:02.2 PCI bridge: IBM EADS-X PCI-X to PCI-X Bridge (rev 03) 0001:00:02.3 PCI bridge: IBM EADS-X PCI-X to PCI-X Bridge (rev 03) 0001:00:02.4 PCI bridge: IBM EADS-X PCI-X to PCI-X Bridge (rev 03) 0001:00:02.6 PCI bridge: IBM EADS-X PCI-X to PCI-X Bridge (rev 03) 0001:cc:01.0 Mass storage controller: Promise Technology, Inc. 20275 (rev 01) 0001:d0:01.0 SCSI storage controller: Mylex Corporation AcceleRAID 600/500/400/Sapphire support Device (rev 04) 0002:00:02.0 PCI bridge: IBM EADS-X PCI-X to PCI-X Bridge (rev 03) 0002:00:02.2 PCI bridge: IBM EADS-X PCI-X to PCI-X Bridge (rev 03) 0002:00:02.3 PCI bridge: IBM EADS-X PCI-X to PCI-X Bridge (rev 03) 0002:00:02.4 PCI bridge: IBM EADS-X PCI-X to PCI-X Bridge (rev 03) 0002:c8:01.0 Serial controller: Digi International Digi Neo 2 DB9 (rev 02) 0002:cc:01.0 USB controller: NEC Corporation OHCI USB Controller (rev 43) 0002:cc:01.1 USB controller: NEC Corporation OHCI USB Controller (rev 43) 0002:cc:01.2 USB controller: NEC Corporation uPD72010x USB 2.0 Controller (rev 04) 0002:d0:01.0 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet Controller (rev 03) 0002:d0:01.1 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet Controller (rev 03)
---
[root@localhost ~]# cat /proc/cpuinfo processor : 0 cpu : POWER5+ (gs) clock : 1898.100000MHz revision : 2.0 (pvr 003b 0200)
processor : 1 cpu : POWER5+ (gs) clock : 1898.100000MHz revision : 2.0 (pvr 003b 0200)
timebase : 237336000 platform : pSeries model : IBM,9111-285 machine : CHRP IBM,9111-285
---
[root@localhost ~]# lscpu Architecture: ppc64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Big Endian CPU(s): 2 On-line CPU(s) list: 0,1 Thread(s) per core: 2 Core(s) per socket: 1 Socket(s): 1 NUMA node(s): 1 Model: IBM,9111-285 L1d cache: 32K L1i cache: 64K L2 cache: 1920K L3 cache: 36864K NUMA node0 CPU(s): 0,1
---
Regards,
Timo
On 01/13/2015 12:12 PM, Timo Schöler wrote:
On 01/06/2015 01:48 PM, Dan Horák wrote:
On Wed, 17 Dec 2014 15:40:49 +0100 Timo Schöler timo@riscworks.net wrote:
On 12/17/2014 03:23 PM, Peter Robinson wrote:
>>> We briefly discussed priorities for Fedora 22 and I had >>> taken an action item to start an email conversation about >>> this. So here is what I would like to see for Fedora 22. >>> >>> 1) Get the -mcpu and -mtune flags set properly for the LE >>> build. Should be -mcpu=power7 -mtune=power8 >> >> done, all packages that honour the Fedora system wide compiler >> flags use them, if they don't it's a packaging bug >> >>> 2) Have a cloud image available >>> 3) For BE I would like another subarch. Same packages as the >>> current one but tuned for P8. >> >> you mean in addition to ppc64p7? can't we just switch ppc64p7 >> from -mcpu=power7 -mtune=power7 to -mcpu=power7 -mtune=power8? > > This makes sense to me as it then mirrors what we have in > ppc64le and it saves having more targets.
The disadvantage of this would be to cut off users that have Power 7 systems and optimized code. So why would people want to optimize from Fedora 21 to Fedora 22. You would be taking a big step back in performance. I don't want to suggest keeping a subarch for each type of POWER system out there. I was thinking of keeping two. So when the next POWER arch that comes out, the Power 7 subarch goes away and you would have Power 8 and the new Power arch.
That would mean that enthusiasts like myself, happily running Fedora on a Power 285 workstation, would lose Fedora?
No, there's a sub arch called ppc64p7 which provides optimised binaries for a sub set of packages which has been a feature for a few releases and is what is being discussed with the terms "For BE I would like another subarch"
Okay, then I got that wrong.
I'd really like to keep it. Red Hat dropped Power5 support quite a time ago, so if there ever comes a CentOS 7 ppc to life, it'd had to be tweaked to run on those machines. *If*, that is. Furthermore, Power6 boxes aren't that old, either.
If there ever was a CentOS7 option for POWER
There's chatting about this, yes.
Last year I started on porting CentOS 5 onto Power, but got stuck due to lack of spare time.
I suspect they would take the same options for RHEL, and POWER6 dates back to 06/07 so define old.
Sure. At least a Power 5 box isn't that old it would be the same category as a Sun SPARCstation 20, which is still supported by OpenBSD, e.g.
What may be of importance is that the 285 is the last *real* workstation, AFAIK.
Would happily buy a new workstation by IBM or the OpenPower consortium, too! :)
I am indeed just installing Final Release Candidate 6 (RC6)
https://lists.fedoraproject.org/pipermail/ppc/2014-December/003199.html
Timo, how did the install go? Was is it as straightforward as placing a DVD in the drive and run?
Hi, yes, I just re-tested it with the most recent image and a 9111-285 (see dmesg etc attached). Works like a charm.
I used the GUI installer (not remote, using VNC, but really with screen and keyboard), which works well. Even without any palette mismatch, what I always got after first reboot.
I *think* the guys from cruxppc had a patch here, a friend of mine told me. I usually use console/network to work on that machine, my friend wants to use it as a real workstation, with GUI. AFAIR, the GXT6500P is supported by the kernel. I'll have a look at this -- if nobody has a hint here, I may open a bug report on this.
From drivers/video/fbdev/gxt4500.c:
/*
- Frame buffer device for IBM GXT4500P/6500P and GXT4000P/6000P
- display adaptors
- Copyright (C) 2006 Paul Mackerras, IBM Corp. paulus@samba.org
*/
(...)
#define PCI_DEVICE_ID_IBM_GXT4500P 0x21c #define PCI_DEVICE_ID_IBM_GXT6500P 0x21b #define PCI_DEVICE_ID_IBM_GXT4000P 0x16e #define PCI_DEVICE_ID_IBM_GXT6000P 0x170
(...)
As said, anaconda plays well. Gnome3 does not.
If time allows, I'll try that on my 275 tomorrow, as well.
I think that this machine suffers from a broken CD/DVD drive. I'll have a look at it ASAP.
Cheers,
Timo
[ 0.000000] Allocated 2359296 bytes for 1024 pacas at c00000000f460000 [ 0.000000] Using pSeries machine description [ 0.000000] Page sizes from device-tree: [ 0.000000] base_shift=12: shift=12, sllp=0x0000, avpnm=0x00000000, tlbiel=1, penc=0 [ 0.000000] base_shift=16: shift=16, sllp=0x0110, avpnm=0x00000000, tlbiel=1, penc=1 [ 0.000000] base_shift=24: shift=24, sllp=0x0100, avpnm=0x00000001, tlbiel=0, penc=0 [ 0.000000] base_shift=34: shift=34, sllp=0x0120, avpnm=0x000007ff, tlbiel=0, penc=3 [ 0.000000] Page orders: linear mapping = 24, virtual = 16, io = 12, vmemmap = 24 [ 0.000000] Using 1TB segments [ 0.000000] cma: Reserved 1024 MiB at 3a0000000 [ 0.000000] Found initrd at 0xc000000003a00000:0xc000000004c4735c [ 0.000000] Partition configured for 2 cpus. [ 0.000000] CPU maps initialized for 2 threads per core [ 0.000000] (thread shift is 1) [ 0.000000] Freed 2293760 bytes for unused pacas [ 0.000000] Starting Linux PPC64 #1 SMP Mon Dec 1 07:50:54 UTC 2014 [ 0.000000] ----------------------------------------------------- [ 0.000000] ppc64_pft_size = 0x1c [ 0.000000] physicalMemorySize = 0x3e9000000 [ 0.000000] htab_hash_mask = 0x1fffff [ 0.000000] ----------------------------------------------------- [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.17.4-301.fc21.ppc64 (mockbuild@ppc-builder3.qa.fedoraproject.org) (gcc version 4.9.2 20141101 (Red Hat 4.9.2-1) (GCC) ) #1 SMP Mon Dec 1 07:50:54 UTC 2014 [ 0.000000] [boot]0012 Setup Arch [ 0.000000] Node 0 Memory: 0x0-0x3e9000000 [ 0.000000] PCI host bridge /pci@800000020000002 ranges: [ 0.000000] IO 0x000003fe00200000..0x000003fe002fffff -> 0x0000000000000000 [ 0.000000] MEM 0x0000040040000000..0x000004007fffffff -> 0x00000000c0000000 [ 0.000000] PCI host bridge /pci@800000020000003 ranges: [ 0.000000] IO 0x000003fe00300000..0x000003fe003fffff -> 0x0000000000000000 [ 0.000000] MEM 0x0000040080000000..0x00000400bfffffff -> 0x00000000c0000000 [ 0.000000] PCI host bridge /pci@800000020000004 ranges: [ 0.000000] IO 0x000003fe00400000..0x000003fe004fffff -> 0x0000000000000000 [ 0.000000] MEM 0x00000400c0000000..0x00000400ffffffff -> 0x00000000c0000000 [ 0.000000] PPC64 nvram contains 7168 bytes [ 0.000000] Zone ranges: [ 0.000000] DMA [mem 0x00000000-0x3e8ffffff] [ 0.000000] Normal empty [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x00000000-0x3e8ffffff] [ 0.000000] On node 0 totalpages: 256256 [ 0.000000] DMA zone: 219 pages used for memmap [ 0.000000] DMA zone: 0 pages reserved [ 0.000000] DMA zone: 256256 pages, LIFO batch:1 [ 0.000000] [boot]0015 Setup Done [ 0.000000] PERCPU: Embedded 3 pages/cpu @c000000001900000 s103168 r0 d93440 u524288 [ 0.000000] pcpu-alloc: s103168 r0 d93440 u524288 alloc=1*1048576 [ 0.000000] pcpu-alloc: [0] 0 1 [ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 256037 [ 0.000000] Policy zone: DMA [ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.17.4-301.fc21.ppc64 root=/dev/mapper/fedora--server-root ro rd.lvm.lv=fedora-server/root rd.lvm.lv=fedora-server/swap rhgb quiet LANG=en_US.UTF-8 single [ 0.000000] PID hash table entries: 4096 (order: -1, 32768 bytes) [ 0.000000] Sorting __ex_table... [ 0.000000] Memory: 15213312K/16400384K available (9408K kernel code, 1856K rwdata, 3508K rodata, 7232K init, 2683K bss, 1187072K reserved) [ 0.000000] SLUB: HWalign=128, Order=0-3, MinObjects=0, CPUs=2, Nodes=256 [ 0.000000] Hierarchical RCU implementation. [ 0.000000] RCU dyntick-idle grace-period acceleration is enabled. [ 0.000000] RCU restricting CPUs from NR_CPUS=1024 to nr_cpu_ids=2. [ 0.000000] Offload RCU callbacks from all CPUs [ 0.000000] Offload RCU callbacks from CPUs: 0-1. [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2 [ 0.000000] NR_IRQS:512 nr_irqs:512 16 [ 0.000000] pic: no ISA interrupt controller [ 0.000000] time_init: decrementer frequency = 237.336000 MHz [ 0.000000] time_init: processor frequency = 1898.100000 MHz [ 0.000003] clocksource: timebase mult[21b51dd] shift[23] registered [ 0.000007] clockevent: decrementer mult[3cc20d56] shift[32] cpu[0] [ 0.000065] Console: colour dummy device 80x25 [ 0.000145] console [tty0] enabled [ 0.015392] allocated 4100096 bytes of page_cgroup [ 0.015395] please try 'cgroup_disable=memory' option if you don't want memory cgroups [ 0.015454] mempolicy: Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl [ 0.015460] pid_max: default: 32768 minimum: 301 [ 0.015530] Security Framework initialized [ 0.015544] SELinux: Initializing. [ 0.015557] SELinux: Starting in permissive mode [ 0.015969] Dentry cache hash table entries: 2097152 (order: 8, 16777216 bytes) [ 0.021417] Inode-cache hash table entries: 1048576 (order: 7, 8388608 bytes) [ 0.024350] Mount-cache hash table entries: 32768 (order: 2, 262144 bytes) [ 0.024358] Mountpoint-cache hash table entries: 32768 (order: 2, 262144 bytes) [ 0.024925] Initializing cgroup subsys memory [ 0.025067] Initializing cgroup subsys devices [ 0.025072] Initializing cgroup subsys freezer [ 0.025077] Initializing cgroup subsys net_cls [ 0.025081] Initializing cgroup subsys blkio [ 0.025085] Initializing cgroup subsys perf_event [ 0.025090] Initializing cgroup subsys net_prio [ 0.025094] Initializing cgroup subsys hugetlb [ 0.025113] ftrace: allocating 24570 entries in 10 pages [ 0.040333] EEH: pSeries platform initialized [ 0.040344] POWER5+/++ performance monitor hardware support registered [ 0.043202] Brought up 2 CPUs [ 0.043209] Node 0 CPUs: 0-1 [ 0.045489] devtmpfs: initialized [ 0.217625] EEH: devices created [ 0.218856] atomic64_test: passed [ 0.234650] NET: Registered protocol family 16 [ 0.261367] EEH: PCI Enhanced I/O Error Handling Enabled [ 0.261486] IBM eBus Device Driver [ 0.262617] cpuidle: using governor menu [ 0.262794] pstore: Registered nvram as persistent store backend [ 0.269135] PCI: Probing PCI hardware [ 0.269148] no ibm,pcie-link-speed-stats property [ 0.269214] PCI host bridge to bus 0000:00 [ 0.269220] pci_bus 0000:00: root bus resource [io 0x10000-0x10ffff] (bus address [0x0000-0xfffff]) [ 0.269225] pci_bus 0000:00: root bus resource [mem 0x40040000000-0x4007fffffff] (bus address [0xc0000000-0xffffffff]) [ 0.269230] pci_bus 0000:00: root bus resource [bus 00-ff] [ 0.270670] pci 0000:00:01.0: supports D1 D2 [ 0.272055] IOMMU table initialized, virtual merging enabled [ 0.272187] no ibm,pcie-link-speed-stats property [ 0.272256] PCI host bridge to bus 0001:00 [ 0.272262] pci_bus 0001:00: root bus resource [io 0x120000-0x21ffff] (bus address [0x0000-0xfffff]) [ 0.272267] pci_bus 0001:00: root bus resource [mem 0x40080000000-0x400bfffffff] (bus address [0xc0000000-0xffffffff]) [ 0.272272] pci_bus 0001:00: root bus resource [bus 00-ff] [ 0.283278] pci 0001:cc:01.0: supports D1 [ 0.288890] no ibm,pcie-link-speed-stats property [ 0.288965] PCI host bridge to bus 0002:00 [ 0.288971] pci_bus 0002:00: root bus resource [io 0x230000-0x32ffff] (bus address [0x0000-0xfffff]) [ 0.288976] pci_bus 0002:00: root bus resource [mem 0x400c0000000-0x400ffffffff] (bus address [0xc0000000-0xffffffff]) [ 0.288980] pci_bus 0002:00: root bus resource [bus 00-ff] [ 0.298650] pci 0002:cc:01.0: supports D1 D2 [ 0.298655] pci 0002:cc:01.0: PME# supported from D0 D1 D2 D3hot [ 0.300627] pci 0002:cc:01.1: supports D1 D2 [ 0.300631] pci 0002:cc:01.1: PME# supported from D0 D1 D2 D3hot [ 0.302587] pci 0002:cc:01.2: supports D1 D2 [ 0.302591] pci 0002:cc:01.2: PME# supported from D0 D1 D2 D3hot [ 0.306402] pci 0002:d0:01.0: PME# supported from D0 D3hot D3cold [ 0.309729] pci 0002:d0:01.1: PME# supported from D0 D3hot D3cold [ 0.314377] PCI: Probing PCI hardware done [ 0.321498] vgaarb: device added: PCI:0000:00:01.0,decodes=io+mem,owns=mem,locks=none [ 0.321512] vgaarb: loaded [ 0.321514] vgaarb: bridge control possible 0000:00:01.0 [ 0.321636] SCSI subsystem initialized [ 0.321714] libata version 3.00 loaded. [ 0.321807] usbcore: registered new interface driver usbfs [ 0.321826] usbcore: registered new interface driver hub [ 0.321886] usbcore: registered new device driver usb [ 0.322233] NetLabel: Initializing [ 0.322236] NetLabel: domain hash size = 128 [ 0.322238] NetLabel: protocols = UNLABELED CIPSOv4 [ 0.322258] NetLabel: unlabeled traffic allowed by default [ 0.322495] Switched to clocksource timebase [ 0.334051] NET: Registered protocol family 2 [ 0.334382] TCP established hash table entries: 131072 (order: 4, 1048576 bytes) [ 0.334771] TCP bind hash table entries: 65536 (order: 4, 1048576 bytes) [ 0.334993] TCP: Hash tables configured (established 131072 bind 65536) [ 0.335032] TCP: reno registered [ 0.335042] UDP hash table entries: 8192 (order: 2, 262144 bytes) [ 0.335115] UDP-Lite hash table entries: 8192 (order: 2, 262144 bytes) [ 0.335266] NET: Registered protocol family 1 [ 0.453425] PCI: CLS 128 bytes, default 128 [ 0.453524] Unpacking initramfs... [ 0.996210] Freeing initrd memory: 18688K (c000000003a00000 - c000000004c40000) [ 0.996736] RTAS daemon started [ 0.997444] RTAS: event: 2, Type: EPOW, Severity: 2 [ 1.032917] futex hash table entries: 512 (order: 0, 65536 bytes) [ 1.032962] audit: initializing netlink subsys (disabled) [ 1.032987] audit: type=2000 audit(1421141880.030:1): initialized [ 1.033378] HugeTLB registered 16 MB page size, pre-allocated 0 pages [ 1.033381] HugeTLB registered 16 GB page size, pre-allocated 0 pages [ 1.037327] zpool: loaded [ 1.037693] VFS: Disk quotas dquot_6.5.2 [ 1.037787] Dquot-cache hash table entries: 8192 (order 0, 65536 bytes) [ 1.038708] msgmni has been set to 31928 [ 1.038841] Key type big_key registered [ 1.038847] SELinux: Registering netfilter hooks [ 1.040291] alg: No test for stdrng (krng) [ 1.040314] NET: Registered protocol family 38 [ 1.040406] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252) [ 1.040474] io scheduler noop registered [ 1.040483] io scheduler deadline registered [ 1.040553] io scheduler cfq registered (default) [ 1.040718] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [ 1.092554] Console: switching to colour frame buffer device 160x64 [ 1.135045] fb0: IBM GXT6500P frame buffer device [ 1.135881] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 1.137864] Linux agpgart interface v0.103 [ 1.138007] Uniform Multi-Platform E-IDE driver [ 1.138064] ide-gd driver 1.18 [ 1.138303] libphy: Fixed MDIO Bus: probed [ 1.138406] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 1.138427] ehci-pci: EHCI PCI platform driver [ 1.138849] ehci-pci 0002:cc:01.2: EHCI Host Controller [ 1.138934] ehci-pci 0002:cc:01.2: new USB bus registered, assigned bus number 1 [ 1.139359] ehci-pci 0002:cc:01.2: irq 276, io mem 0x400f8002000 [ 1.152503] ehci-pci 0002:cc:01.2: USB 2.0 started, EHCI 1.00 [ 1.152583] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 1.152587] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.152591] usb usb1: Product: EHCI Host Controller [ 1.152594] usb usb1: Manufacturer: Linux 3.17.4-301.fc21.ppc64 ehci_hcd [ 1.152598] usb usb1: SerialNumber: 0002:cc:01.2 [ 1.152844] hub 1-0:1.0: USB hub found [ 1.152855] hub 1-0:1.0: 5 ports detected [ 1.153191] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 1.153213] ohci-pci: OHCI PCI platform driver [ 1.153608] ohci-pci 0002:cc:01.0: OHCI PCI host controller [ 1.153695] ohci-pci 0002:cc:01.0: new USB bus registered, assigned bus number 2 [ 1.153735] ohci-pci 0002:cc:01.0: irq 276, io mem 0x400f8001000 [ 1.242544] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001 [ 1.242548] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.242552] usb usb2: Product: OHCI PCI host controller [ 1.242556] usb usb2: Manufacturer: Linux 3.17.4-301.fc21.ppc64 ohci_hcd [ 1.242559] usb usb2: SerialNumber: 0002:cc:01.0 [ 1.242777] hub 2-0:1.0: USB hub found [ 1.242791] hub 2-0:1.0: 3 ports detected [ 1.243364] ohci-pci 0002:cc:01.1: OHCI PCI host controller [ 1.243450] ohci-pci 0002:cc:01.1: new USB bus registered, assigned bus number 3 [ 1.243489] ohci-pci 0002:cc:01.1: irq 276, io mem 0x400f8000000 [ 1.332540] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001 [ 1.332544] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.332548] usb usb3: Product: OHCI PCI host controller [ 1.332552] usb usb3: Manufacturer: Linux 3.17.4-301.fc21.ppc64 ohci_hcd [ 1.332555] usb usb3: SerialNumber: 0002:cc:01.1 [ 1.332761] hub 3-0:1.0: USB hub found [ 1.332774] hub 3-0:1.0: 2 ports detected [ 1.332951] uhci_hcd: USB Universal Host Controller Interface driver [ 1.333062] usbcore: registered new interface driver usbserial [ 1.333077] usbcore: registered new interface driver usbserial_generic [ 1.333092] usbserial: USB Serial support registered for generic [ 1.333513] mousedev: PS/2 mouse device common for all mice [ 1.333844] rtc-generic rtc-generic: rtc core: registered rtc-generic as rtc0 [ 1.334210] ibmpowernv ibmpowernv.0: Opal node 'sensors' not found [ 1.334301] ibmpowernv: Platfrom driver probe failed [ 1.334520] device-mapper: uevent: version 1.0.3 [ 1.334749] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com [ 1.334972] pseries_idle_driver registered [ 1.335007] hidraw: raw HID events driver (C) Jiri Kosina [ 1.335234] usbcore: registered new interface driver usbhid [ 1.335236] usbhid: USB HID core driver [ 1.335252] drop_monitor: Initializing network drop monitor service [ 1.335370] ip_tables: (C) 2000-2006 Netfilter Core Team [ 1.335393] TCP: cubic registered [ 1.335403] Initializing XFRM netlink socket [ 1.335647] NET: Registered protocol family 10 [ 1.336014] mip6: Mobile IPv6 [ 1.336022] NET: Registered protocol family 17 [ 1.336141] Running MSI bitmap self-tests ... [ 1.339080] registered taskstats version 1 [ 1.344088] rtc-generic rtc-generic: setting system clock to 2015-01-13 09:38:00 UTC (1421141880) [ 1.344100] PM: Hibernation image not present or could not be loaded. [ 1.345344] Freeing unused kernel memory: 7232K (c000000000cb0000 - c0000000013c0000) [ 1.353097] random: systemd urandom read with 8 bits of entropy available [ 1.504923] systemd-journald[90]: File /var/log/journal/467519b2e44a45d5a02b256ebf9249de/system.journal corrupted or uncleanly shut down, renaming and replacing. [ 1.961531] pata_pdc2027x 0001:cc:01.0: version 1.0 [ 1.961964] pata_pdc2027x 0001:cc:01.0: enabling device (0002 -> 0003) [ 2.049360] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI [ 2.049366] e1000: Copyright (c) 1999-2006 Intel Corporation. [ 2.049773] e1000 0002:d0:01.0: enabling device (0000 -> 0002) [ 2.062114] pata_pdc2027x 0001:cc:01.0: PLL input clock 32754 kHz [ 2.099426] scsi host0: pata_pdc2027x [ 2.099700] scsi host1: pata_pdc2027x [ 2.099813] ata1: PATA max UDMA/133 mmio m16384@0x400b8000000 cmd 0x400b80017c0 irq 324 [ 2.099818] ata2: PATA max UDMA/133 mmio m16384@0x400b8000000 cmd 0x400b80015c0 irq 324 [ 2.116759] ipr: IBM Power RAID SCSI Device Driver version: 2.6.0 (November 16, 2012) [ 2.116789] ipr 0001:d0:01.0: Found IOA with IRQ: 325 [ 2.242529] usb 2-1: new low-speed USB device number 2 using ohci-pci [ 2.258970] ipr 0001:d0:01.0: Cannot enable MSI. [ 2.260999] ipr 0001:d0:01.0: Starting IOA initialization sequence. [ 2.265908] ipr 0001:d0:01.0: Adapter firmware version: 0510006D [ 2.273324] ata1.00: ATAPI: IBM DROM00205L1 H0, P533, max UDMA/66 [ 2.290155] ipr 0001:d0:01.0: IOA initialized. [ 2.290178] scsi host2: IBM 573E Storage Adapter [ 2.303821] scsi 2:0:3:0: Direct-Access SEAGATE ST3146707LC 0005 PQ: 0 ANSI: 3 [ 2.313090] ata1.00: configured for UDMA/66 [ 2.314245] scsi: waiting for bus probes to complete ... [ 2.315579] scsi 2:0:4:0: Direct-Access IBM-ESXS ST373405LC !# B243 PQ: 0 ANSI: 3 [ 2.323186] scsi 2:0:15:0: Enclosure IBM VSBPD4E1 U4SCSI 6000 PQ: 0 ANSI: 2 [ 2.398189] e1000 0002:d0:01.0 eth0: (PCI-X:133MHz:64-bit) 00:14:5e:96:4b:18 [ 2.398199] e1000 0002:d0:01.0 eth0: Intel(R) PRO/1000 Network Connection [ 2.398375] e1000 0002:d0:01.1: enabling device (0000 -> 0002) [ 2.469532] usb 2-1: New USB device found, idVendor=046a, idProduct=0023 [ 2.469539] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 2.548267] sd 2:0:3:0: Attached scsi generic sg0 type 0 [ 2.548652] sd 2:0:3:0: [sda] 286749488 512-byte logical blocks: (146 GB/136 GiB) [ 2.548705] sd 2:0:4:0: Attached scsi generic sg1 type 0 [ 2.549039] scsi 2:0:15:0: Attached scsi generic sg2 type 13 [ 2.550162] sd 2:0:3:0: [sda] Write Protect is off [ 2.550168] sd 2:0:3:0: [sda] Mode Sense: ab 00 10 08 [ 2.551287] scsi 0:0:0:0: CD-ROM IBM DROM00205L1 H0 P533 PQ: 0 ANSI: 2 [ 2.551516] sd 2:0:4:0: [sdb] 143374000 512-byte logical blocks: (73.4 GB/68.3 GiB) [ 2.552187] sd 2:0:3:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 2.554579] sd 2:0:4:0: [sdb] Write Protect is off [ 2.554586] sd 2:0:4:0: [sdb] Mode Sense: ab 00 10 08 [ 2.555785] sr 0:0:0:0: [sr0] scsi3-mmc drive: 24x/24x cd/rw xa/form2 cdda tray [ 2.555789] cdrom: Uniform CD-ROM driver Revision: 3.20 [ 2.556045] sr 0:0:0:0: Attached scsi CD-ROM sr0 [ 2.556254] sr 0:0:0:0: Attached scsi generic sg3 type 5 [ 2.557153] sd 2:0:4:0: [sdb] Write cache: disabled, read cache: enabled, supports DPO and FUA [ 2.564279] input: HID 046a:0023 as /devices/pci0002:00/0002:00:02.3/0002:cc:01.0/usb2/2-1/2-1:1.0/0003:046A:0023.0001/input/input0 [ 2.564449] cherry 0003:046A:0023.0001: input,hidraw0: USB HID v1.11 Keyboard [HID 046a:0023] on usb-0002:cc:01.0-1/input0 [ 2.570787] sda: sda1 sda2 sda3 [ 2.573394] sdb: sdb1 sdb2 sdb3 [ 2.576719] sd 2:0:3:0: [sda] Attached SCSI disk [ 2.578318] sd 2:0:4:0: [sdb] Attached SCSI disk [ 2.581748] input: HID 046a:0023 as /devices/pci0002:00/0002:00:02.3/0002:cc:01.0/usb2/2-1/2-1:1.1/0003:046A:0023.0002/input/input1 [ 2.581905] cherry 0003:046A:0023.0002: input,hidraw1: USB HID v1.11 Device [HID 046a:0023] on usb-0002:cc:01.0-1/input1 [ 2.734672] e1000 0002:d0:01.1 eth1: (PCI-X:133MHz:64-bit) 00:14:5e:96:4b:19 [ 2.734681] e1000 0002:d0:01.1 eth1: Intel(R) PRO/1000 Network Connection [ 2.736316] e1000 0002:d0:01.1 enP2p208s1f1: renamed from eth1 [ 2.743514] scsi 2:255:255:255: No Device IBM 573E001 0150 PQ: 0 ANSI: 0 [ 2.745338] scsi 2:255:255:255: Attached scsi generic sg4 type 31 [ 2.784012] e1000 0002:d0:01.0 enP2p208s1f0: renamed from eth0 [ 4.769462] PM: Starting manual resume from disk [ 4.769469] PM: Hibernation image partition 253:0 present [ 4.769472] PM: Looking for hibernation image. [ 4.787557] PM: Image not found (code -22) [ 4.787561] PM: Hibernation image not present or could not be loaded. [ 5.563982] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null) [ 5.933035] random: nonblocking pool is initialized [ 6.330248] systemd-journald[90]: Received SIGTERM from PID 1 (systemd). [ 6.786925] audit: type=1404 audit(1421141885.930:2): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295 [ 6.921916] SELinux: 2048 avtab hash slots, 111331 rules. [ 6.955192] SELinux: 2048 avtab hash slots, 111331 rules. [ 7.002283] SELinux: 8 users, 103 roles, 4980 types, 295 bools, 1 sens, 1024 cats [ 7.002289] SELinux: 83 classes, 111331 rules [ 7.011185] SELinux: Permission audit_read in class capability2 not defined in policy. [ 7.011195] SELinux: the above unknown classes and permissions will be allowed [ 7.011203] SELinux: Completing initialization. [ 7.011205] SELinux: Setting up existing superblocks. [ 7.011216] SELinux: initialized (dev rootfs, type rootfs), uses genfs_contexts [ 7.011234] SELinux: initialized (dev bdev, type bdev), uses genfs_contexts [ 7.011243] SELinux: initialized (dev proc, type proc), uses genfs_contexts [ 7.011364] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs [ 7.011378] SELinux: initialized (dev devtmpfs, type devtmpfs), uses transition SIDs [ 7.012370] SELinux: initialized (dev sockfs, type sockfs), uses task SIDs [ 7.012378] SELinux: initialized (dev debugfs, type debugfs), uses genfs_contexts [ 7.014023] SELinux: initialized (dev pipefs, type pipefs), uses task SIDs [ 7.014033] SELinux: initialized (dev anon_inodefs, type anon_inodefs), uses genfs_contexts [ 7.014039] SELinux: initialized (dev aio, type aio), not configured for labeling [ 7.014045] SELinux: initialized (dev devpts, type devpts), uses transition SIDs [ 7.014064] SELinux: initialized (dev hugetlbfs, type hugetlbfs), uses transition SIDs [ 7.014073] SELinux: initialized (dev hugetlbfs, type hugetlbfs), uses transition SIDs [ 7.014080] SELinux: initialized (dev mqueue, type mqueue), uses transition SIDs [ 7.014090] SELinux: initialized (dev selinuxfs, type selinuxfs), uses genfs_contexts [ 7.014130] SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts [ 7.016957] SELinux: initialized (dev securityfs, type securityfs), uses genfs_contexts [ 7.016962] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs [ 7.016971] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs [ 7.017095] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs [ 7.017149] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts [ 7.017161] SELinux: initialized (dev pstore, type pstore), uses genfs_contexts [ 7.017168] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts [ 7.017173] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts [ 7.017178] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts [ 7.017203] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts [ 7.017213] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts [ 7.017218] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts [ 7.017222] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts [ 7.017248] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts [ 7.017252] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts [ 7.017259] SELinux: initialized (dev configfs, type configfs), uses genfs_contexts [ 7.017269] SELinux: initialized (dev dm-1, type ext4), uses xattr [ 7.035942] audit: type=1403 audit(1421141886.180:3): policy loaded auid=4294967295 ses=4294967295 [ 7.064563] systemd[1]: Successfully loaded SELinux policy in 283.013ms. [ 7.181685] systemd[1]: Relabelled /dev and /run in 43.689ms. [ 8.961916] SELinux: initialized (dev autofs, type autofs), uses genfs_contexts [ 9.414749] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs [ 9.417034] SELinux: initialized (dev hugetlbfs, type hugetlbfs), uses transition SIDs [ 9.623216] EXT4-fs (dm-1): re-mounted. Opts: (null) [ 9.770029] systemd-journald[471]: Received request to flush runtime journal from PID 1 [ 10.032201] systemd-journald[471]: File /var/log/journal/467519b2e44a45d5a02b256ebf9249de/system.journal corrupted or uncleanly shut down, renaming and replacing. [ 11.464808] ttyn0 at MMIO 0x0 (irq = 275, base_baud = 921600) is a jsm [ 11.466513] jsm: Port 0 added [ 11.466520] ttyn1 at MMIO 0x0 (irq = 275, base_baud = 921600) is a jsm [ 11.466668] jsm: Port 1 added [ 11.466675] jsm 0002:c8:01.0: board 1: Digi Neo (rev 2), irq 275 [ 11.591946] scsi 2:0:15:0: Resetting device [ 11.612748] ipr 0001:d0:01.0: Adapter being reset as a result of error recovery. [ 14.714633] ipr 0001:d0:01.0: Initializing IOA. [ 24.085437] ipr 0001:d0:01.0: Starting IOA initialization sequence. [ 24.091152] ipr 0001:d0:01.0: Adapter firmware version: 0510006D [ 24.115407] ipr 0001:d0:01.0: IOA initialized. [ 34.408570] ses 2:0:15:0: Attached Enclosure device [ 35.072199] Adding 8191936k swap on /dev/mapper/fedora--server-swap. Priority:-1 extents:1 across:8191936k FS [ 35.352247] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) [ 35.356682] SELinux: initialized (dev sda2, type ext4), uses xattr [ 35.728105] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null) [ 35.728118] SELinux: initialized (dev dm-4, type ext4), uses xattr [ 159.308241] IPv6: ADDRCONF(NETDEV_UP): enP2p208s1f0: link is not ready [ 159.313125] e1000: enP2p208s1f0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [ 159.313261] IPv6: ADDRCONF(NETDEV_CHANGE): enP2p208s1f0: link becomes ready [ 236.957368] 8021q: 802.1Q VLAN Support v1.8 [ 236.957385] 8021q: adding VLAN 0 to HW filter on device enP2p208s1f0 [ 384.970540] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [ 385.045854] ip6_tables: (C) 2000-2006 Netfilter Core Team [ 385.449389] Ebtables v2.0 registered [ 385.479306] Bridge firewalling registered [ 412.123540] audit: type=1305 audit(1421142291.269:4): audit_pid=2411 old=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:auditd_t:s0 res=1 [ 416.362234] sd 2:0:3:0: [sda] Resetting device [ 417.023278] ipr 0001:d0:01.0: Adapter being reset as a result of error recovery. [ 420.124613] ipr 0001:d0:01.0: Initializing IOA. [ 429.498401] ipr 0001:d0:01.0: Starting IOA initialization sequence. [ 429.504117] ipr 0001:d0:01.0: Adapter firmware version: 0510006D [ 429.528372] ipr 0001:d0:01.0: IOA initialized. [ 440.282475] sd 2:0:4:0: [sdb] Resetting device [ 441.502151] ipr 0001:d0:01.0: Adapter being reset as a result of error recovery. [ 444.604620] ipr 0001:d0:01.0: Initializing IOA. [ 453.977474] ipr 0001:d0:01.0: Starting IOA initialization sequence. [ 453.983190] ipr 0001:d0:01.0: Adapter firmware version: 0510006D [ 454.007440] ipr 0001:d0:01.0: IOA initialized. [ 464.093683] cfg80211: Calling CRDA to update world regulatory domain [ 464.233032] cfg80211: World regulatory domain updated: [ 464.233039] cfg80211: DFS Master region: unset [ 464.233043] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 464.233049] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) [ 464.233055] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) [ 464.233061] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) [ 464.233066] cfg80211: (5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A, 2000 mBm), (N/A) [ 464.233071] cfg80211: (5250000 KHz - 5330000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) [ 464.233076] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) [ 464.233081] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) [ 464.233087] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) [ 464.774238] IPv6: ADDRCONF(NETDEV_UP): enP2p208s1f1: link is not ready [ 464.774245] 8021q: adding VLAN 0 to HW filter on device enP2p208s1f1 [ 497.293112] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
lspci:
0000:00:01.0 VGA compatible controller: IBM GXT6500P Graphics Adapter (rev 04) 0001:00:02.0 PCI bridge: IBM EADS-X PCI-X to PCI-X Bridge (rev 03) 0001:00:02.2 PCI bridge: IBM EADS-X PCI-X to PCI-X Bridge (rev 03) 0001:00:02.3 PCI bridge: IBM EADS-X PCI-X to PCI-X Bridge (rev 03) 0001:00:02.4 PCI bridge: IBM EADS-X PCI-X to PCI-X Bridge (rev 03) 0001:00:02.6 PCI bridge: IBM EADS-X PCI-X to PCI-X Bridge (rev 03) 0001:cc:01.0 Mass storage controller: Promise Technology, Inc. 20275 (rev 01) 0001:d0:01.0 SCSI storage controller: Mylex Corporation AcceleRAID 600/500/400/Sapphire support Device (rev 04) 0002:00:02.0 PCI bridge: IBM EADS-X PCI-X to PCI-X Bridge (rev 03) 0002:00:02.2 PCI bridge: IBM EADS-X PCI-X to PCI-X Bridge (rev 03) 0002:00:02.3 PCI bridge: IBM EADS-X PCI-X to PCI-X Bridge (rev 03) 0002:00:02.4 PCI bridge: IBM EADS-X PCI-X to PCI-X Bridge (rev 03) 0002:c8:01.0 Serial controller: Digi International Digi Neo 2 DB9 (rev 02) 0002:cc:01.0 USB controller: NEC Corporation OHCI USB Controller (rev 43) 0002:cc:01.1 USB controller: NEC Corporation OHCI USB Controller (rev 43) 0002:cc:01.2 USB controller: NEC Corporation uPD72010x USB 2.0 Controller (rev 04) 0002:d0:01.0 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet Controller (rev 03) 0002:d0:01.1 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet Controller (rev 03)
[root@localhost ~]# cat /proc/cpuinfo processor : 0 cpu : POWER5+ (gs) clock : 1898.100000MHz revision : 2.0 (pvr 003b 0200)
processor : 1 cpu : POWER5+ (gs) clock : 1898.100000MHz revision : 2.0 (pvr 003b 0200)
timebase : 237336000 platform : pSeries model : IBM,9111-285 machine : CHRP IBM,9111-285
[root@localhost ~]# lscpu Architecture: ppc64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Big Endian CPU(s): 2 On-line CPU(s) list: 0,1 Thread(s) per core: 2 Core(s) per socket: 1 Socket(s): 1 NUMA node(s): 1 Model: IBM,9111-285 L1d cache: 32K L1i cache: 64K L2 cache: 1920K L3 cache: 36864K NUMA node0 CPU(s): 0,1
Regards,
Timo
On Tue, 13 Jan 2015 12:12:00 +0100 Timo Schöler timo@riscworks.net wrote:
If there ever was a CentOS7 option for POWER
There's chatting about this, yes.
Last year I started on porting CentOS 5 onto Power, but got stuck due to lack of spare time.
I suspect they would take the same options for RHEL, and POWER6 dates back to 06/07 so define old.
Sure. At least a Power 5 box isn't that old it would be the same category as a Sun SPARCstation 20, which is still supported by OpenBSD, e.g.
What may be of importance is that the 285 is the last *real* workstation, AFAIK.
Would happily buy a new workstation by IBM or the OpenPower consortium, too! :)
I am indeed just installing Final Release Candidate 6 (RC6)
https://lists.fedoraproject.org/pipermail/ppc/2014-December/003199.html
Timo, how did the install go? Was is it as straightforward as placing a DVD in the drive and run?
Hi, yes, I just re-tested it with the most recent image and a 9111-285 (see dmesg etc attached). Works like a charm.
sounds great and I've already updated the hardware section in the release notes
I used the GUI installer (not remote, using VNC, but really with screen and keyboard), which works well. Even without any palette mismatch, what I always got after first reboot.
I *think* the guys from cruxppc had a patch here, a friend of mine
there was a patch to "Add GXT4000P and GXT6500P support to the gxt4500 driver" which is now in the mainline kernel for some time
told me. I usually use console/network to work on that machine, my friend wants to use it as a real workstation, with GUI. AFAIR, the GXT6500P is supported by the kernel. I'll have a look at this -- if nobody has a hint here, I may open a bug report on this.
Dan
On 01/15/2015 12:28 PM, Dan Horák wrote:
On Tue, 13 Jan 2015 12:12:00 +0100 Timo Schöler timo@riscworks.net wrote:
If there ever was a CentOS7 option for POWER
There's chatting about this, yes.
Last year I started on porting CentOS 5 onto Power, but got stuck due to lack of spare time.
I suspect they would take the same options for RHEL, and POWER6 dates back to 06/07 so define old.
Sure. At least a Power 5 box isn't that old it would be the same category as a Sun SPARCstation 20, which is still supported by OpenBSD, e.g.
What may be of importance is that the 285 is the last *real* workstation, AFAIK.
Would happily buy a new workstation by IBM or the OpenPower consortium, too! :)
I am indeed just installing Final Release Candidate 6 (RC6)
https://lists.fedoraproject.org/pipermail/ppc/2014-December/003199.html
Timo, how did the install go? Was is it as straightforward as placing a DVD in the drive and run?
Hi, yes, I just re-tested it with the most recent image and a 9111-285 (see dmesg etc attached). Works like a charm.
sounds great and I've already updated the hardware section in the release notes
Thanks a lot! :)
I used the GUI installer (not remote, using VNC, but really with screen and keyboard), which works well. Even without any palette mismatch, what I always got after first reboot.
I *think* the guys from cruxppc had a patch here, a friend of mine
there was a patch to "Add GXT4000P and GXT6500P support to the gxt4500 driver" which is now in the mainline kernel for some time
So, everything should work as intended? I'll fire up that machine and try it.
told me. I usually use console/network to work on that machine, my friend wants to use it as a real workstation, with GUI. AFAIR, the GXT6500P is supported by the kernel. I'll have a look at this -- if nobody has a hint here, I may open a bug report on this.
Dan
Timo
On Thu, 15 Jan 2015 12:34:48 +0100 Timo Schöler timo@riscworks.net wrote:
On 01/15/2015 12:28 PM, Dan Horák wrote:
On Tue, 13 Jan 2015 12:12:00 +0100 Timo Schöler timo@riscworks.net wrote:
If there ever was a CentOS7 option for POWER
There's chatting about this, yes.
Last year I started on porting CentOS 5 onto Power, but got stuck due to lack of spare time.
I suspect they would take the same options for RHEL, and POWER6 dates back to 06/07 so define old.
Sure. At least a Power 5 box isn't that old it would be the same category as a Sun SPARCstation 20, which is still supported by OpenBSD, e.g.
What may be of importance is that the 285 is the last *real* workstation, AFAIK.
Would happily buy a new workstation by IBM or the OpenPower consortium, too! :)
I am indeed just installing Final Release Candidate 6 (RC6)
https://lists.fedoraproject.org/pipermail/ppc/2014-December/003199.html
Timo, how did the install go? Was is it as straightforward as placing a DVD in the drive and run?
Hi, yes, I just re-tested it with the most recent image and a 9111-285 (see dmesg etc attached). Works like a charm.
sounds great and I've already updated the hardware section in the release notes
Thanks a lot! :)
I used the GUI installer (not remote, using VNC, but really with screen and keyboard), which works well. Even without any palette mismatch, what I always got after first reboot.
I *think* the guys from cruxppc had a patch here, a friend of mine
there was a patch to "Add GXT4000P and GXT6500P support to the gxt4500 driver" which is now in the mainline kernel for some time
So, everything should work as intended? I'll fire up that machine and try it.
it should, I have a GXT6500P card in my 9114-275 and I did the tests before it got accepted in the kernel.
told me. I usually use console/network to work on that machine, my friend wants to use it as a real workstation, with GUI. AFAIR, the GXT6500P is supported by the kernel. I'll have a look at this -- if nobody has a hint here, I may open a bug report on this.
Dan
On 01/15/2015 12:39 PM, Dan Horák wrote:
<snip>
Hi, yes, I just re-tested it with the most recent image and a 9111-285 (see dmesg etc attached). Works like a charm.
sounds great and I've already updated the hardware section in the release notes
Thanks a lot! :)
I used the GUI installer (not remote, using VNC, but really with screen and keyboard), which works well. Even without any palette mismatch, what I always got after first reboot.
I *think* the guys from cruxppc had a patch here, a friend of mine
there was a patch to "Add GXT4000P and GXT6500P support to the gxt4500 driver" which is now in the mainline kernel for some time
So, everything should work as intended? I'll fire up that machine and try it.
it should, I have a GXT6500P card in my 9114-275 and I did the tests before it got accepted in the kernel.
Great. Do you recall when this patch got in?
told me. I usually use console/network to work on that machine, my friend wants to use it as a real workstation, with GUI. AFAIR, the GXT6500P is supported by the kernel. I'll have a look at this -- if nobody has a hint here, I may open a bug report on this.
On Thu, 15 Jan 2015 12:43:59 +0100 Timo Schöler timo@riscworks.net wrote:
On 01/15/2015 12:39 PM, Dan Horák wrote:
<snip>
Hi, yes, I just re-tested it with the most recent image and a 9111-285 (see dmesg etc attached). Works like a charm.
sounds great and I've already updated the hardware section in the release notes
Thanks a lot! :)
I used the GUI installer (not remote, using VNC, but really with screen and keyboard), which works well. Even without any palette mismatch, what I always got after first reboot.
I *think* the guys from cruxppc had a patch here, a friend of mine
there was a patch to "Add GXT4000P and GXT6500P support to the gxt4500 driver" which is now in the mainline kernel for some time
So, everything should work as intended? I'll fire up that machine and try it.
it should, I have a GXT6500P card in my 9114-275 and I did the tests before it got accepted in the kernel.
Great. Do you recall when this patch got in?
end of year 2012 = http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=6c...
Dan
On 01/15/2015 12:57 PM, Dan Horák wrote:
On Thu, 15 Jan 2015 12:43:59 +0100 Timo Schöler timo@riscworks.net wrote:
On 01/15/2015 12:39 PM, Dan Horák wrote:
<snip>
Hi, yes, I just re-tested it with the most recent image and a 9111-285 (see dmesg etc attached). Works like a charm.
sounds great and I've already updated the hardware section in the release notes
Thanks a lot! :)
I used the GUI installer (not remote, using VNC, but really with screen and keyboard), which works well. Even without any palette mismatch, what I always got after first reboot.
I *think* the guys from cruxppc had a patch here, a friend of mine
there was a patch to "Add GXT4000P and GXT6500P support to the gxt4500 driver" which is now in the mainline kernel for some time
So, everything should work as intended? I'll fire up that machine and try it.
it should, I have a GXT6500P card in my 9114-275 and I did the tests before it got accepted in the kernel.
Great. Do you recall when this patch got in?
end of year 2012 = http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=6c...
Awesome, thanks a lot!
Timo
-
Dan Horák -
Josh Boyer -
Michael J Wolf -
Peter Robinson -
Timo Schöler