Comments (12)
  • Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

1 Tictac_NS commented Permalink

Your timing is impeccable :-) I spent some time yesterday, near the end of my day trying for the right vnc boot option combo, but ran out of time and this morning, there was your blog. <div>&nbsp;</div> Thanks a bunch. <div>&nbsp;</div> I hope someone from IBM sees this. My current issue with Linux on Power is licensing. There are people out there with Power gear that want to expand their Linux experience and the licensing costs for getting the "supported" Red Hat or Suse are prohibitive for someone who just wants a system to learn on. All because the hardware I have available happens to be on an enterprise level server.

2 Tictac_NS commented Permalink

Your timing is impeccable :-) I spent some time yesterday, near the end of my day trying for the right vnc boot option combo, but ran out of time and this morning, there was your blog. <div>&nbsp;</div> Thanks a bunch. <div>&nbsp;</div> I hope someone from IBM sees this. My current issue with Linux on Power is licensing. There are people out there with Power gear that want to expand their Linux experience and the licensing costs for getting the "supported" Red Hat or Suse are prohibitive for someone who just wants a system to learn on. All because the hardware I have available happens to be on an enterprise level server.

3 Tictac_NS commented Permalink

Your timing is impeccable :-) I spent some time yesterday, near the end of my day trying for the right vnc boot option combo, but ran out of time and this morning, there was your blog. <div>&nbsp;</div> Thanks a bunch. <div>&nbsp;</div> I hope someone from IBM sees this. My current issue with Linux on Power is licensing. There are people out there with Power gear that want to expand their Linux experience and the licensing costs for getting the "supported" Red Hat or Suse are prohibitive for someone who just wants a system to learn on. All because the hardware I have available happens to be on an enterprise level server.

4 JuergenVoss commented Permalink

Hi Nigel, <div>&nbsp;</div> Thanks for this. Worked pretty well for me. <br /> However, it took me quite some time to sort out that Fedora (Linux) can not handle large_receive turned on. <br /> (https://www.ibm.com/developerworks/community/forums/html/topic?id=b4196cbc-5d3d-49c5-9104-760a146dae33&amp;ps=10) <br /> Just for anybody else running into slow inbound file transfer. <br /> regards Jürgen

5 Nishith-Vyas commented Permalink

I am trying to install "Fedora 20 ppc64 bit" OS on IBM Power Server (Power6-p520) using your blog. My IBM Server Model is 8203-E4A. <div>&nbsp;</div> I have already installed RHEL 6.5 ppc64 on other server &amp; would like to test all "java related compatibility" using Fedora. As "fedora 20" is having proper compatibility over IBM Power Server segment, I would like to troubleshoot current installation issues. The installation screen just stuck up without further activity on screen. <div>&nbsp;</div> I am successfully getting fedora installation screen thru VNC, but then I can't ping VNC IP Address, which I have configured for installation. The VNC Viewer is located on the same Network Segment &amp; there is no firewall which blocks any type of traffic in between VNC Viewer &amp; VNC Server. <div>&nbsp;</div> Here, VNC Server means IBM Power Server, on which I am trying to install Fedora 20. Please help to resolve this issue.

6 nagger commented Permalink

Hi Nishith-Vyas, <br /> Which VIOS version are you running ? If you are running native on the box then all bets are off as that would mean Fedora would have to have device drivers in the installer to work all the adapters and you machine is too old. The above was done on a POWER8 machine. I would expect a POWER7 machine would probably work. But POWER6 is from years back and I would expect the current Fedora releases has never been tested. Hope this helps, Nigel

7 Nishith-Vyas commented Permalink

Hello Nagger, <div>&nbsp;</div> There is no VIOS (PowerVM) availableon my Server. Just it is a Power6 Server(p520) having 24 GB of RAM with total 8 CPUs(4 Cores-2 Sockets) with 560 GB Hard Drive (140 GB x 4 Drives) having Hardware RAID. <div>&nbsp;</div> Considering your blog to install Fedora 20 on IBM Power, I never had any error till Step:15 i.e. Please connect your VNC Client on ..... message. But, then, I really don't ping VNC IP nor able to connect VNC to start Fedora 20 installation. I really don't know how to deal with this problem. I tried to install RHEL 7, Fedora 21 too, but both OSes gives same message. <div>&nbsp;</div> Let me know if there is any possibility to get debug output for resolution. <div>&nbsp;</div> - Nishith

8 nagger commented Permalink

Hi Nishith-Vyas I do not think native Linux is a good idea. 1) you are throwing away a key POWER advantage in virtualisation with PowerVM and 2) you get in to exactly these problems. Given you are trying VNC over a network, I would suspect the network adapter is not working. Are you trying the complicated HEA/IVE built in Ethernet or a nice and simple network card. If something simple then it looks like a the Fedora installer does not know how to drive it. Sorry I don't know how to debug from here. I think you are trying a combination that has very little chance that its been tested = old HW, native and new OS. Install a VIOS and run the Fedora as a pure virtual VM to protect it from hardware. cheers Nigel

9 Nishith-Vyas commented Permalink

@ Nagger. <div>&nbsp;</div> Is VIOS free? Actually, I don't have that much expertise to run VIOS on IBM Power. I am a certified VMWare &amp; RedHat Engineer. So, start working on it isn't a big challenge. <div>&nbsp;</div> Previously, these IBM Servers were having AIX 5.3 oslevel 6, which is of NO USE for the ongoing projects. <div>&nbsp;</div> My goal is to install RHEV(Red Hat Enterprise VIrtualization) on IBM Power Server as Hypervisor &amp; then, configure multiple VM's using RHEV-Manager. But, RHEV license is too much costly &amp; company won't allow me to pursue. <div>&nbsp;</div> So, 2nd phase is, Install RHEL 6.5 PPC or Fedora 20 PPC on IBM &amp; then install oVirt Package to create Virtual Machines. What you suggest ? I am having problems to install "Java-1.7.0-openJDK-1.7" packages on RHEL PPC &amp; Fedora 20 is giving all packages in setup DVD...!!! That's why I am interested to install Fedora 20.

10 nagger commented Permalink

Hi, Nishith-Vyas all of this sounds marvellous but not on a POWER6 machine - its like getting a old Intel Pentium box out of the attic and giving virtualisation a go but finding it does not have the CPU features required. I don't think the POWER6 from something like 2007-2009 (roughly) will have firmware to support what you are trying. RedHat native should work as it was available at the time. The rest (RHEV and Fedora) is blue sky research and more likely to fail than work. Sorry - but you might get lucky. Yes, PowerVM has to be purchased and includes VIOS - might be a long shot but most POWER6 machines were sold with PowerVM.

11 Nishith-Vyas commented Permalink

@ Nagger, <div>&nbsp;</div> Finally, I am able to install Fedora 20 on IBM Power6. The problem was related to Network Interface, as this server contains 4 Network Cards. What I have noticed that, when you start installation of Fedora 20 using VNC, it will create "Virtual IP Address", which was assigned to any of the Network Card. I thought that I am giving VNC IP Address to "ethernet 0" only...!!! <div>&nbsp;</div> As you suggest, I checked each &amp; every interface for PING REPLY &amp; Finally, I got REPLY from :ethernet 2"... &amp; then, rest worked well as per your documentation. <div>&nbsp;</div> Tha you very much for the blog &amp; I will try to add my experience on it. Please let me know how to create BLOG for IBM Power with RHEL/Fedora under "aixpert".

12 nagger commented Permalink

Excellent news - Thanks for your persistence. I will go looking for some POWER6 on the retirement list and rescue them for a second life. AIXpert is my Blog - you will have to find your own. Comments and tips here are always welcome.