Question: Linux for Pseries 615 RS6000
UnixUser
use Linux Mint but don't think they have a port for power.
I enjoy AIX but may also install a 64 bit Linux on my RS6000 as well.
Please recommend a Linux 64 bit distro that also supports KDE v4 and Gnome.
PS - Please list a download link so I can burn a Linux 64 bit iso image.
Thank You
Tony Rodriguez
Gerard H. Pille
You're sure you don't want us to burn it for you?
UnixUser
FYI, PPC/Power architecture isn't mainstream in Linux and I'd rather use
something stable and recommended by others. Doing so should save a
bunch of time troubleshooting compatibility issues. I'd rather spend
that time developing software. In other words, why re-invent the wheel?
Also If you don't want to share a recommendation that is okay but why be
rude about it?
Tony Rodriguez
Jo
> Come on now, I am only requesting a good distro and link (if known).
> FYI, PPC/Power architecture isn't mainstream in Linux and I'd rather use
> something stable and recommended by others. Doing so should save a
> bunch of time troubleshooting compatibility issues. I'd rather spend
> that time developing software. In other words, why re-invent the wheel?
> Also If you don't want to share a recommendation that is okay but why be
> rude about it?
>
(I also tested Debian ppc flavour but seems to be actualy more for Mac
ppc, though)
Hth,
J.
Frank Fegert
> (I also tested Debian ppc flavour but seems to be actualy more for Mac
> ppc, though)
I cannot second that. Debian/PPC runs smoothly on all pSeries
i tried it (9114-275 Power4, p570 Power5+, p550 Power6, p550
Power6+). Although i'll admit that those were "server" installs,
no X11, KDE, GNOME or other unneeded stuff was tested.
Best regards,
Frank
Jo
Frank,
I am sincerely very happy for you ;<)
Too bad for me, Debian is my very favorit (that's about then years
that I run unstable on my home i386 with obviously some minor issue
from time to time ;<)).
Well that also a server installation but I didn't have any other
possibilty then try it on a lpar over a vios (but should be also most
probably your case?)
That said the installation itself works fine (I can even access it as
chroot through next opensuse) but I never reach to make it boot itself
(and even thought I report the issue on debian ml, I nerver get
relevant help?) since few days ago while trying grub2 (but still with
some work-around).
Thanks again for feedback,
J.
UnixUser
RS6000/Pseries questions. It has been a number of years since I worked
with RS6000's and much of it is coming back to me. But I honestly forgot
about the nightmares with hardware/microcode compatibility issues, etc.
This is why I'd rather ask others in the newsgroup because it saves a
bunch of time with troubleshooting.
For the most part, I really appreciate your recommendations and helpful
nature.
All the best...
Tony Rodriguez
Frank Fegert
> Well that also a server installation but I didn't have any other
> possibilty then try it on a lpar over a vios (but should be also most
> probably your case?)
On the p5xx systems i used LPARs with dual VIOS. On the 9114-275
the full system, because the machine doesn't support LPARs.
> That said the installation itself works fine (I can even access it as
> chroot through next opensuse) but I never reach to make it boot itself
> (and even thought I report the issue on debian ml, I nerver get
> relevant help?) since few days ago while trying grub2 (but still with
> some work-around).
Strange. Although i admit the whole yaboot thing is a bit different
if you are used to x86 systems, i had only minor issues getting the
LPAR booted. One was a buggy firmware level which for some reason
prevented Linux from booting. The other was with multipathing the
VSCSI devices over two VIOS, but this has been addressed in a bugfix.
What is your console output when you try to boot the LPAR? What does
your partition table in the Debian LPAR look like? What does your
/etc/yaboot.conf look like? Did the ibmvscsi kernel modules get
picked up into the initrd?
Best regards,
Frank
Jo
Sorry for delay (I was busy elsewhere: tbh on grub2).
On Nov 10, 11:14 am, Frank Fegert <fra.nospam...@gmx.de> wrote:
Well I think that all details were in my pr <http://lists.debian.org/
debian-powerpc/2008/03/msg00038.html>
So most probably that the initrd didn't contain ibmvscsi modules,
though?
That said, I am now able to boot grub2 and this installation; we still
have to understand why I am not yet able to boot a full lvm install?
> Best regards,
>
> Frank
Tx again,
J.
Frank Fegert
On 2009-12-06, Jo <rubi...@scarlet.be> wrote:
> Well I think that all details were in my pr <http://lists.debian.org/
> debian-powerpc/2008/03/msg00038.html>
>
> So most probably that the initrd didn't contain ibmvscsi modules,
> though?
>
> That said, I am now able to boot grub2 and this installation; we still
> have to understand why I am not yet able to boot a full lvm install?
i'd second that you're probably missing the ibmvscsi module in
the initrd. Could you check this by unpacking the initrd image
and looking at its /lib/modules/$VERSION/kernel/drivers/scsi/ibmvscsi
subdirectory? If the directory or the *.ko files within are missing
add the entry:
ibmvscsic
to /etc/modules, run 'update-initramfs' and reboot.
Best regards,
Frank
Jo
> Hello,
Frank,
Since this time, thanks to the opensuse installation, I could mount
this debian installation and chroot it to update it regulary with
unstable target. So the kernel image was also updated and trust me the
last initrd contains well the ibmvscsi.
I just need to check if the initrd of this time is still on the boot
fs and if yaboot is still installed?
I will check and advise.
Cheers,
J.
Jo
On Dec 6, 3:17 pm, Jo <rubis...@scarlet.be> wrote:
> On Dec 6, 1:00 pm, Frank Fegert <fra.nospam...@gmx.de> wrote:
>
>
>
> > Hello,
>
> > On 2009-12-06, Jo <rubis...@scarlet.be> wrote:
>
> > > Well I think that all details were in my pr <http://lists.debian.org/
> > > debian-powerpc/2008/03/msg00038.html>
>
> > > So most probably that the initrd didn't contain ibmvscsi modules,
> > > though?
>
> > > That said, I am now able to boot grub2 and this installation; we still
> > > have to understand why I am not yet able to boot a full lvm install?
>
> > i'd second that you're probably missing the ibmvscsi module in
> > the initrd. Could you check this by unpacking the initrd image
> > and looking at its /lib/modules/$VERSION/kernel/drivers/scsi/ibmvscsi
> > subdirectory? If the directory or the *.ko files within are missing
> > add the entry:
> > ibmvscsic
> > to /etc/modules, run 'update-initramfs' and reboot.
>
Afaik nothing to do as I find well the module ibmvscsi in the initrd
image.
But it wasn't loaded' automaticaly, so I would guess that I would just
need to add a simple "insmod=ibmvscsi" to the 'append =' line of
yaboot.conf file?
I will try to reinstall yaboot and try it asap.
Tx,
J.