[opensuse-ppc] PPC64LE Install Issues
I'm trying to install using the ppc64le Factory Net ISO on a Power 7 LPAR, but I keep running in to issues. The first problem was caused by using an outdated ISO leading to symbol version issues for mount. Now, I can't even get the YaST installer to start. Here's what I get after I configure the HTTP server: Loading Installation System (1/5) - 100% Loading Installation System (2/5) - 100% Loading Installation System (3/5) - 100% Loading Installation System (4/5) - 100% Loading Installation System (5/5) - 100% Reading Driver Update... *** An error occurred during the installation. If I retry the operation using the same network/HTTP config, I get a little more helpful output: *** http://ftp5.gwdg.de/pub/opensuse/ports/ppc/factory/repo/oss/content: Invalid signature. Installation aborted. I originally was using download.opensuse.org, but switched to gwdg.de to see if maybe it was a bad mirror, but it didn't seem to help. :( This was with the 178 build ISO from June 24th. I do not get this problem with the 180 ppc64 build from the 25th. I have not tried the 180 ppc64le ISO. The little information I could find related to this error seemed to involve having the clock set wrong, but the existing Ubuntu ppc64 install shows the correct time and as I said, the ppc64 ISO seems to work fine. Has anyone gotten the ppc64le install working? -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
Hi, It seems problem with sync and rebuild cycle. I'll try to debug this locally. Thanks, Dinar On Thu, Jun 26, 2014 at 1:07 AM, Kevin Adler <zeke@zekesdominion.com> wrote:
I'm trying to install using the ppc64le Factory Net ISO on a Power 7 LPAR, but I keep running in to issues. The first problem was caused by using an outdated ISO leading to symbol version issues for mount. Now, I can't even get the YaST installer to start.
Here's what I get after I configure the HTTP server:
Loading Installation System (1/5) - 100% Loading Installation System (2/5) - 100% Loading Installation System (3/5) - 100% Loading Installation System (4/5) - 100% Loading Installation System (5/5) - 100% Reading Driver Update...
*** An error occurred during the installation.
If I retry the operation using the same network/HTTP config, I get a little more helpful output:
*** http://ftp5.gwdg.de/pub/opensuse/ports/ppc/factory/repo/oss/content: Invalid signature.
Installation aborted.
I originally was using download.opensuse.org, but switched to gwdg.de to see if maybe it was a bad mirror, but it didn't seem to help. :(
This was with the 178 build ISO from June 24th. I do not get this problem with the 180 ppc64 build from the 25th. I have not tried the 180 ppc64le ISO. The little information I could find related to this error seemed to involve having the clock set wrong, but the existing Ubuntu ppc64 install shows the correct time and as I said, the ppc64 ISO seems to work fine.
Has anyone gotten the ppc64le install working? -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
Hi, I've rebuilt iso and ftp tree. Should be fine now. Have fun, Dinar On Thu, Jun 26, 2014 at 1:07 AM, Kevin Adler <zeke@zekesdominion.com> wrote:
I'm trying to install using the ppc64le Factory Net ISO on a Power 7 LPAR, but I keep running in to issues. The first problem was caused by using an outdated ISO leading to symbol version issues for mount. Now, I can't even get the YaST installer to start.
Here's what I get after I configure the HTTP server:
Loading Installation System (1/5) - 100% Loading Installation System (2/5) - 100% Loading Installation System (3/5) - 100% Loading Installation System (4/5) - 100% Loading Installation System (5/5) - 100% Reading Driver Update...
*** An error occurred during the installation.
If I retry the operation using the same network/HTTP config, I get a little more helpful output:
*** http://ftp5.gwdg.de/pub/opensuse/ports/ppc/factory/repo/oss/content: Invalid signature.
Installation aborted.
I originally was using download.opensuse.org, but switched to gwdg.de to see if maybe it was a bad mirror, but it didn't seem to help. :(
This was with the 178 build ISO from June 24th. I do not get this problem with the 180 ppc64 build from the 25th. I have not tried the 180 ppc64le ISO. The little information I could find related to this error seemed to involve having the clock set wrong, but the existing Ubuntu ppc64 install shows the correct time and as I said, the ppc64 ISO seems to work fine.
Has anyone gotten the ppc64le install working? -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
Hi Dinar, I'm still getting the same issue with the latest build 197 ISO. -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
I've seen that today. And it seems wrong ISO got published (very old). Could you please try this iso instead? https://dl.dropboxusercontent.com/u/605074/openSUSE-Factory-NET-ppc64le-Buil... On Wed, Jul 9, 2014 at 9:07 PM, Kevin Adler <zeke@zekesdominion.com> wrote:
Hi Dinar, I'm still getting the same issue with the latest build 197 ISO. -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
With that ISO, I'm getting: Platform does not support Client Program headers of class 2 Detected bad memory access to address: ffffffffffffffff Package path = /packages/boot-mgr .----------------------------------. | No Operating Systems Installed | `----------------------------------' Looking at the ISO contents, it seems that the suseboot/ directory is gone and a bunch more stuff is under boot/ now. It looks like yaboot has been replaced by grub2 in this ISO. On Wed, Jul 9, 2014 at 2:41 PM, Dinar Valeev <k0da@opensuse.org> wrote:
I've seen that today. And it seems wrong ISO got published (very old). Could you please try this iso instead? https://dl.dropboxusercontent.com/u/605074/openSUSE-Factory-NET-ppc64le-Buil...
On Wed, Jul 9, 2014 at 9:07 PM, Kevin Adler <zeke@zekesdominion.com> wrote:
Hi Dinar, I'm still getting the same issue with the latest build 197 ISO. -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
Yes, we've switched to grub2 On Wed, Jul 9, 2014 at 10:21 PM, Kevin Adler <zeke@zekesdominion.com> wrote:
With that ISO, I'm getting:
Platform does not support Client Program headers of class 2
Detected bad memory access to address: ffffffffffffffff Package path = /packages/boot-mgr
.----------------------------------. | No Operating Systems Installed | `----------------------------------'
Looking at the ISO contents, it seems that the suseboot/ directory is gone and a bunch more stuff is under boot/ now. It looks like yaboot has been replaced by grub2 in this ISO.
On Wed, Jul 9, 2014 at 2:41 PM, Dinar Valeev <k0da@opensuse.org> wrote:
I've seen that today. And it seems wrong ISO got published (very old). Could you please try this iso instead? https://dl.dropboxusercontent.com/u/605074/openSUSE-Factory-NET-ppc64le-Buil...
On Wed, Jul 9, 2014 at 9:07 PM, Kevin Adler <zeke@zekesdominion.com> wrote:
Hi Dinar, I'm still getting the same issue with the latest build 197 ISO. -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
On 09.07.14 22:34, Dinar Valeev wrote:
Yes, we've switched to grub2
On Wed, Jul 9, 2014 at 10:21 PM, Kevin Adler <zeke@zekesdominion.com> wrote:
With that ISO, I'm getting:
Platform does not support Client Program headers of class 2
Detected bad memory access to address: ffffffffffffffff Package path = /packages/boot-mgr
.----------------------------------. | No Operating Systems Installed | `----------------------------------'
Looking at the ISO contents, it seems that the suseboot/ directory is gone and a bunch more stuff is under boot/ now. It looks like yaboot has been replaced by grub2 in this ISO.
It looks like your OFW doesn't want to load a little endian grub2 binary. What a shame. But I bet you already have a working yaboot setup on that system, right? Could you please copy the "linux" and "initrd" files from the installation media into your yaboot boot partition and add entries for them in yaboot.conf? Maybe you also need to replace the yaboot binary with one that can load little endian kernels. Fortunately the iso you downloaded earlier did have such a yaboot on it, so you can just grab it from there :). Alex -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
Thanks for the info Alex. This is a POWER7 LPAR running on a PS700 blade. I know this ppc64le is pretty cutting edge, so issues like this are bound to happen. I wonder if that is why I couldn't get Ubuntu 14.04 ppc64le booting either (which also uses grub2 for LE, but yaboot for BE). I'll have to test out your yaboot idea when I next get some time to play around with this. This was a new LPAR that I carved out, but while trying to get the ppc64le working, I did install Ubuntu 14.04 ppc64 and I think I then scratched that with openSUSE 13.1 (or maybe Factory) ppc64. In any event, I can get a working ppc64 install set up and try bootstrapping from there. On Wed, Jul 9, 2014 at 6:35 PM, Alexander Graf <agraf@suse.de> wrote:
On 09.07.14 22:34, Dinar Valeev wrote:
Yes, we've switched to grub2
On Wed, Jul 9, 2014 at 10:21 PM, Kevin Adler <zeke@zekesdominion.com> wrote:
With that ISO, I'm getting:
Platform does not support Client Program headers of class 2
Detected bad memory access to address: ffffffffffffffff Package path = /packages/boot-mgr
.----------------------------------. | No Operating Systems Installed | `----------------------------------'
Looking at the ISO contents, it seems that the suseboot/ directory is gone and a bunch more stuff is under boot/ now. It looks like yaboot has been replaced by grub2 in this ISO.
It looks like your OFW doesn't want to load a little endian grub2 binary. What a shame.
But I bet you already have a working yaboot setup on that system, right? Could you please copy the "linux" and "initrd" files from the installation media into your yaboot boot partition and add entries for them in yaboot.conf?
Maybe you also need to replace the yaboot binary with one that can load little endian kernels. Fortunately the iso you downloaded earlier did have such a yaboot on it, so you can just grab it from there :).
Alex
-- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
On 18.07.14 06:21, Kevin Adler wrote:
Thanks for the info Alex. This is a POWER7 LPAR running on a PS700 blade. I know this ppc64le is pretty cutting edge, so issues like this are bound to happen. I wonder if that is why I couldn't get Ubuntu 14.04 ppc64le booting either (which also uses grub2 for LE, but yaboot for BE).
It's most likely a part of the puzzle. We also carry a patch in openSUSE that enables you to run an LE kernel on hypervisors that don't implement the H_SET_MODE(ILE) hypercall. Your POWER7 pHyp definitely does not implement it, so you need the patch to run a kernel on it.
I'll have to test out your yaboot idea when I next get some time to play around with this. This was a new LPAR that I carved out, but while trying to get the ppc64le working, I did install Ubuntu 14.04 ppc64 and I think I then scratched that with openSUSE 13.1 (or maybe Factory) ppc64. In any event, I can get a working ppc64 install set up and try bootstrapping from there.
So did that work out for you? :) Alex -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
Well, it only took about 8 tries or so over 3 days, but I got it working. :) linux-nas6 login: root Password: Have a lot of fun... linux-nas6:~ # uname -a Linux linux-nas6 3.15.5-1.g01d2774-default #1 SMP Thu Jul 10 08:16:25 UTC 2014 (01d2774) ppc64le ppc64le ppc64le GNU/Linux My first mistake was trying to use the default btrfs root filesystem. I quickly realized that yaboot can't boot to btrfs. I then tried to use an ext4 /boot, but that didn't work either, figuring that it couldn't find yaboot.conf on the btrfs partition. Then I reinstalled with ext4 root partition, but it still didn't work. Turns out yaboot doesn't support ext4 either :( Finally set root to ext3 and everything went fine. I wonder now if I could have used an ext3 /boot and things would have been ok with a btrs /. I'm not sure how yaboot would read the yaboot.conf, however. Can this be put on the /boot? It also didn't help that the installer is a bit bugged. Here's the bugs I encountered, not sure where to file them: 1) After configuring the HTTP installation source, it attempts to download 5 files. If one of these fail, it continues onward and then fails with missing files. If you try again, it does not download the files again, even the ones which failed to finish downloading the first time. The only way to continue on is to restart the installer. FTP seemed to work better for me, but not all mirrors support FTP, especially those that mirror the PPC files. 2) The network setup on build 240 does not correctly set up the network. I had to configure my ethernet interface manually from a console. It looks like things work, but when it attempts to download the files it just gives a generic failure. 3) The network setup doesn't ask for a nameserver anymore, although it does ask for search domains, strangely enough. I had to look up the ip address for the mirror and specify it manually. Attempting to set the nameserver in /etc/resolv.conf didn't seem to work. Testing with curl http://google.com gave an error with no route to host for some reason. I didn't mess with it much, since the IP address was working fine. On Mon, Jul 28, 2014 at 7:41 AM, Alexander Graf <agraf@suse.de> wrote:
On 18.07.14 06:21, Kevin Adler wrote:
Thanks for the info Alex. This is a POWER7 LPAR running on a PS700 blade. I know this ppc64le is pretty cutting edge, so issues like this are bound to happen. I wonder if that is why I couldn't get Ubuntu 14.04 ppc64le booting either (which also uses grub2 for LE, but yaboot for BE).
It's most likely a part of the puzzle. We also carry a patch in openSUSE that enables you to run an LE kernel on hypervisors that don't implement the H_SET_MODE(ILE) hypercall. Your POWER7 pHyp definitely does not implement it, so you need the patch to run a kernel on it.
I'll have to test out your yaboot idea when I next get some time to play around with this. This was a new LPAR that I carved out, but while trying to get the ppc64le working, I did install Ubuntu 14.04 ppc64 and I think I then scratched that with openSUSE 13.1 (or maybe Factory) ppc64. In any event, I can get a working ppc64 install set up and try bootstrapping from there.
So did that work out for you? :)
Alex
-- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
Well, it only took about 8 tries or so over 3 days, but I got it working. :) Awesome!
linux-nas6 login: root Password: Have a lot of fun... linux-nas6:~ # uname -a Linux linux-nas6 3.15.5-1.g01d2774-default #1 SMP Thu Jul 10 08:16:25 UTC 2014 (01d2774) ppc64le ppc64le ppc64le GNU/Linux
My first mistake was trying to use the default btrfs root filesystem. I quickly realized that yaboot can't boot to btrfs. I then tried to use an ext4 /boot, but that didn't work either, figuring that it couldn't find yaboot.conf on the btrfs partition. Then I reinstalled with ext4 root partition, but it still didn't work. Turns out yaboot doesn't support ext4 either :( Finally set root to ext3 and everything went fine. I wonder now if I could have used an ext3 /boot and things would have been ok with a btrs /. I'm not sure how yaboot would read the yaboot.conf, however. Can this be put on the /boot? You can embed config file into the binary.
It also didn't help that the installer is a bit bugged. Here's the bugs I encountered, not sure where to file them:
1) After configuring the HTTP installation source, it attempts to download 5 files. If one of these fail, it continues onward and then fails with missing files. If you try again, it does not download the files again, even the ones which failed to finish downloading the first time. The only way to continue on is to restart the installer. FTP seemed to work better for me, but not all mirrors support FTP, especially those that mirror the PPC files.
2) The network setup on build 240 does not correctly set up the network. I had to configure my ethernet interface manually from a console. It looks like things work, but when it attempts to download the files it just gives a generic failure.
3) The network setup doesn't ask for a nameserver anymore, although it does ask for search domains, strangely enough. I had to look up the ip address for the mirror and specify it manually. Attempting to set the nameserver in /etc/resolv.conf didn't seem to work. Testing with curl http://google.com gave an error with no route to host for some reason. I didn't mess with it much, since the IP address was working fine. Could you please report those bugs to bugzilla? make sure you boot with:
On Thu, Jul 31, 2014 at 12:48 AM, Kevin Adler <zeke@zekesdominion.com> wrote: linuxrc.debug=1 linuxrc.log=/lrc.log Also there is a DVD media available, but it is not published yet. So you can download it manually with: osc getbinaries openSUSE:Factory:PowerPC/_product:openSUSE-dvd5-dvd-ppc64le/images/local
On Mon, Jul 28, 2014 at 7:41 AM, Alexander Graf <agraf@suse.de> wrote:
On 18.07.14 06:21, Kevin Adler wrote:
Thanks for the info Alex. This is a POWER7 LPAR running on a PS700 blade. I know this ppc64le is pretty cutting edge, so issues like this are bound to happen. I wonder if that is why I couldn't get Ubuntu 14.04 ppc64le booting either (which also uses grub2 for LE, but yaboot for BE).
It's most likely a part of the puzzle. We also carry a patch in openSUSE that enables you to run an LE kernel on hypervisors that don't implement the H_SET_MODE(ILE) hypercall. Your POWER7 pHyp definitely does not implement it, so you need the patch to run a kernel on it.
I'll have to test out your yaboot idea when I next get some time to play around with this. This was a new LPAR that I carved out, but while trying to get the ppc64le working, I did install Ubuntu 14.04 ppc64 and I think I then scratched that with openSUSE 13.1 (or maybe Factory) ppc64. In any event, I can get a working ppc64 install set up and try bootstrapping from there.
So did that work out for you? :)
Alex
-- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
participants (3)
-
Alexander Graf -
Dinar Valeev -
Kevin Adler