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
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