Gentoo on PS3

[Drikus]

Copied kboot.conf from kboot.conf.example as instructed and checked the entries against the files,symlinks in /boot. Can't go wrong there. Had to edit fstab but checked that multiple times and didn't find any typo in there.

But tried the 64ul stage and that booted fine... Followed the exact same steps Again network wasn't started when trying to download the stage4 tarball. Had this already back in May when I installed 2.6.16 on the ps3 for the first time so nothing changed there...

Some other minor things I noticed following the instructions/docs.

- why not provide a working fstab or example like with kboot.conf ? It's specific for a 2.6.23 PS3 kernel so why not.
- in the printed fstab in the instructions and the fstab file itself in /etc, entry spufs, the 's' is fallen of the default, but it doesn't matter really because spufs isn't provided in 64ul stage4.. why is that btw. ?
- the note about kboot.conf and 64ul isn't needed anymore because there symlinks now.
- after exiting chroot those umounts aren't really needed.

[rangerpb]

I cannot provide a working fstab because I cannot predict your environment. Youi might be installed on an external HD, etc etc. Really, it's no big deal to edit fstab as with any other architecture using gentoo.

There are some known issues with the networking. I'm not going to pursue the problem right now as other functions are more pressing.

spufs is provided in the 64ul. if there is a problem with it, please check with me on irc.

the note abiout the kboot.conf is needed as again we cannot predict the environment. people have the right to mess around with stuff and the note is still valid isn't it?

Unmounts are neccesary in the case that you actually want the mounts to unmount cleanly.
_________________
-->
rangerpb
<--

[f5inet]

i am having problems with the GCC 4.3.0_alpha10071109 install in PS3.

i installed the cell/toolchain overlays, as seen in http://overlays.gentoo.org/proj/cell/wiki/InstallToolchain

i am working with a 64bits UserLand

i know that the GCC4.3 has a issue with fortran, and i add to package.use the "=sys-devel/gcc-4.3.0_alpha20071109 -fortran" line for disable the fortran compilation, but the compiler (GCC 4.1.2) throws:

--------------------------------------------
Making all in include
make[4]: Entering directory `/var/tmp/portage/sys-devel/gcc-4.3.0_alpha20071109/work/build/powerpc64-unknown-linux-gnu/libstdc++-v3/include'
if [ ! -d "./powerpc64-unknown-linux-gnu/bits/stdc++.h.gch" ]; then \
mkdir -p ./powerpc64-unknown-linux-gnu/bits/stdc++.h.gch; \
fi; \
/var/tmp/portage/sys-devel/gcc-4.3.0_alpha20071109/work/build/./gcc/xgcc -shared-libgcc -B/var/tmp/portage/sys-devel/gcc-4.3.0_alpha20071109/work/build/./gcc -nostdinc++ -L/var/tmp/portage/sys-devel/gcc-4.3.0_alpha20071109/work/build/powerpc64-unknown-linux-gnu/libstdc++-v3/src -L/var/tmp/portage/sys-devel/gcc-4.3.0_alpha20071109/work/build/powerpc64-unknown-linux-gnu/libstdc++-v3/src/.libs -B/usr/powerpc64-unknown-linux-gnu/bin/ -B/usr/powerpc64-unknown-linux-gnu/lib/ -isystem /usr/powerpc64-unknown-linux-gnu/include -isystem /usr/powerpc64-unknown-linux-gnu/sys-include -Winvalid-pch -x c++-header -O2 -pipe -mcpu=970 -mtune=970 -D_GNU_SOURCE -I/var/tmp/portage/sys-devel/gcc-4.3.0_alpha20071109/work/build/powerpc64-unknown-linux-gnu/libstdc++-v3/include/powerpc64-unknown-linux-gnu -I/var/tmp/portage/sys-devel/gcc-4.3.0_alpha20071109/work/build/powerpc64-unknown-linux-gnu/libstdc++-v3/include -I/var/tmp/portage/sys-devel/gcc-4.3.0_alpha20071109/work/gcc-4.3-20071109/libstdc++-v3/libsupc++ -O0 -g /var/tmp/portage/sys-devel/gcc-4.3.0_alpha20071109/work/gcc-4.3-20071109/libstdc++-v3/include/precompiled/stdc++.h -o powerpc64-unknown-linux-gnu/bits/stdc++.h.gch/O0g.gch
In file included from /var/tmp/portage/sys-devel/gcc-4.3.0_alpha20071109/work/gcc-4.3-20071109/libstdc++-v3/include/precompiled/stdc++.h:68:
/var/tmp/portage/sys-devel/gcc-4.3.0_alpha20071109/work/build/powerpc64-unknown-linux-gnu/libstdc++-v3/include/limits:1047: error: stray '\275' in program
/var/tmp/portage/sys-devel/gcc-4.3.0_alpha20071109/work/build/powerpc64-unknown-linux-gnu/libstdc++-v3/include/limits:1079: error: stray '\230' in program
/var/tmp/portage/sys-devel/gcc-4.3.0_alpha20071109/work/build/powerpc64-unknown-linux-gnu/libstdc++-v3/include/limits:1104: error: stray '\275' in program
/var/tmp/portage/sys-devel/gcc-4.3.0_alpha20071109/work/build/powerpc64-unknown-linux-gnu/libstdc++-v3/include/limits:1113: error: stray '\230' in program
/var/tmp/portage/sys-devel/gcc-4.3.0_alpha20071109/work/build/powerpc64-unknown-linux-gnu/libstdc++-v3/include/limits:1137: error: stray '\230' in program
make[4]: *** [powerpc64-unknown-linux-gnu/bits/stdc++.h.gch/O0g.gch] Error 1
make[4]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.3.0_alpha20071109/work/build/powerpc64-unknown-linux-gnu/libstdc++-v3/include'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.3.0_alpha20071109/work/build/powerpc64-unknown-linux-gnu/libstdc++-v3'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.3.0_alpha20071109/work/build/powerpc64-unknown-linux-gnu/libstdc++-v3'
make[1]: *** [all-target-libstdc++-v3] Error 2
make[1]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.3.0_alpha20071109/work/build'
make: *** [profiledbootstrap] Error 2
*
* ERROR: sys-devel/gcc-4.3.0_alpha20071109 failed.
* Call stack:
* ebuild.sh, line 1701: Called dyn_compile
* ebuild.sh, line 1039: Called qa_call 'src_compile'
* ebuild.sh, line 44: Called src_compile
* ebuild.sh, line 1383: Called toolchain_src_compile
* toolchain.eclass, line 26: Called gcc_src_compile
* toolchain.eclass, line 1547: Called gcc_do_make
* toolchain.eclass, line 1421: Called die
* The specific snippet of code:
* emake \
* LDFLAGS="${LDFLAGS}" \
* STAGE1_CFLAGS="${STAGE1_CFLAGS}" \
* LIBPATH="${LIBPATH}" \
* BOOT_CFLAGS="${BOOT_CFLAGS}" \
* ${GCC_MAKE_TARGET} \
* || die "emake failed with ${GCC_MAKE_TARGET}"
* The die message:
* emake failed with profiledbootstrap
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/sys-devel/gcc-4.3.0_alpha20071109/temp/build.log'.
*
---------------------------------------------

any tips?

[andrewpea]

Hi,

I'm having the exact same problem as f5inet and it seems that it also effects people here:

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33992

All the errors in limits feature __DBL_MAX__ or variations of it so it seems like __DBL_MAX__ and __LDBL_MAX__ etc are not being defined correctly on some 64bit systems.

However when I run:

[h41cyon]

Ok, I've followed the directions to a T and upon first boot with my 2.6.23-ps3 kernel I get the following message:

cannot determine the file type of /mnt:tnp:9c1172bde5292ce117e92539.................. .......//ppc/ppc64/kernel-2.6.23-ps3


.... I've searched and I've searched and nothing tells me what could possibly be going wrong. Bad initrd maybe?

IDK

[h41cyon]

[Boblenain]

I habe just got a play3
I will try gentoo@ps3 soon i hope

[eae]

Hi, is it possible to get kboot to start in 720p or 1080p mode? I'm referring to kboot itself, not the linux kernel it loads. I have my ps3 connected to my pc monitor through a vga transcoder and can't display 480i images.
Thanks and excuse me if it's an old/stupid question.

[garlicbread]

Kboot is basically another Kernel + an initial initird (small filesystem with a set of files)
it loads the 2nd kernel (the one on the hard disk) and then switches across to it using kexec
(it also reads in kboot.conf from the HD to figure out what it needs to look at)

the reason for this approach is so you don't need to keep reflashing the firmware on the PS3 each time you want to try out another kernel / also you can have kernels larger that the firmware storage area

I'm guessing there's no options in the kboot.conf to control this, which means you'd ether need to create a custom kboot image, or perhaps use petite boot (similar to kboot but with a graphical menu / X built in)

[epsilon72]

I'm having a couple small problems with my PS3. It's mostly up and running except for these.

1) The clock is never read correctly at startup, and the system throws out the usual "modification time in the future!" stuff until ntp kicks in.

2) There is no sound. When I try to modprobe for snd_ps3, it says "module not found". Which leads to #3....

3) I found the config file for the kernel, and decided to compile my own up to date kernel, with one benefit being that I get my sound module. However...my kernel is 64 bit, but it appears to be a 32 bit userland for the stage that I chose. Something called kgcc64 is installed, but when I try to 'make' my kernel from the config it complains about compiling a 64-bit kernel. Any thoughts?

[rangerpb]

[epsilon72]

[dthsqd]

Here are some bonnie++ results on a PS3 laptop drive and an NFS share.

Filesystem benchmarks for Local PS3 partition

[sternn]

[va1210]

Is there currently any active Linux PS3 development going on to get more out of the hardware? Seems to me that most stuff I can find on Google regarding optimizing decoders and video drivers for the cell processor are almost one year old. The PS3 overlay http://overlays.gentoo.org/proj/cell/wiki/InstallGentooOnPS3 has also been rather slow lately..

[antonlacon]

There are still some interesting media projects being done.

http://code.google.com/p/cell-mpeg2-decoder/ was released earlier this month.

http://forums.ps2dev.org/viewforum.php?f=27 is occasionally useful for new information. They have another subforum for running media off the SPEs.

[va1210]

Thanks for the links, looks interesting!

[epsilon72]

I'm still not having much luck with audio (alsa still complains when I try to run alsamixer, etc), but maybe I'm missing something obvious here...

Is audio over HDMI not (yet) supported?

[Pliablemammal]

Hey guys I got my 2008.0 stage 3 install up and going and made a kernel. But now... I am having a bit of trouble getting GCC 4.3.... something what ever the new alpha is. I set the I_PROMISE_TO_SUBMIT....=1 thing, but it's failing to compile due to some sort of toolchain setting.

Does anyone know what the setting is to change, or if it's something I can do to the ebuild?

Thanks again,
Bob
_________________
Linux ps3-betabox 2.6.28-rc7-00948-gc5fd701 #5 SMP PREEMPT Sun Dec 14 18:25:40 PST 2008 ppc64 Cell Broadband Engine, altivec supported GNU/Linux - gcc version 4.4.0 20081212 (experimental) (GCC) Videos

[Occasus]

Hello.

I'm going to install Gentoo on my PS3.

I downloaded installcd-ps3-minimal-20071212-r1.iso from OSUOSL, but its kboot is broken.
I couldn't switch back to GameOs with `ps3-boot-game-os`, because of I/O errors with the flash memory.
So I've installed petitboot, but I'm afraid it's a wrong choice Isn't there any properly working otheros.bld kboot?

Then, isn't stage4-970-ps3_64ul.tar.bz2 a bit outdated? Is doing a regular ppc64 installation+PS3 software a crazy idea?

I don't want to end up with a bloated, outdated stage4 system
_________________
Guru Meditation

[antonlacon]

You can get the latest otheros.bld for kboot from here:

http://www.kernel.org/pub/linux/kernel/people/geoff/cell/ps3-kboot/

It was my experience that the experimental stage 4 would destroy itself after a few weeks. I ended up using one of the release 2008.0 stages, but one of the weekly stages would probably save you some time.

[Occasus]

[antonlacon]

I use the stable ppc keyword, and mark unstable the packages I need. I had ACCEPT_KEYWORDS burn me a few years back on ~x86 and won't use it anymore.

[Occasus]

[hexonn]

My ps3 recently gave up on me and I got a replacement, and I was wondering re-installing Gentoo but maybe using a new stage

So, just using something from 2008.0, for example, would be okay?
ftp://lug.mtu.edu/gentoo/releases/ppc/2008.0/stages/

Also, I'd still use the 20071212 minimal livecd right?
_________________
working on it