I just did a fresh system install with the 20071220 version of the Addon CD, and it seems that the LVM step (step 8) is still needed. I built the kernel and modules without it, and it couldn't boot.
I also fixed the typo that Andrea pointed out regarding initrd-2.6.3.img
I am trying to figure out the best way to keep the instructions up to date. If I edit the original post the reflect the most current information, then the comments that follow won't make sense. If I start a new thread with every update then there will be several versions of the instructions out there, which could get confusing.
One option is to turn this into an article on developerWorks, and use this thread to keep people posted as to updates of the main article.
I had to use the 12/20 addon disc to get the system to even boot.
In step 10 the last command doesn't work unless I do not include "-rc3".
It appears to have worked
For sure keep updating the above guide. After it is stable for awhile maybe produce an article on it.
I made the -rc3 fix you pointed out, and also moved the instructions to a seperate developerWorks article. I think that will be the best way to keep it updated.
Like I said before, I did most of this work on a 20GB machine (no wifi), and ssh into it, so things like the graphics, wifi, and sound aren't used. If anyone knows of any issues, please feel free to bring them up, and I'll try to address them.
the current version of your install guide is very thorough now.
For people wanting to use the HugeTLB filesystem the article from the cell performace web site (the third link mentioned at the bottom) is also a very useful.
It also seems that FC8 would be a feasable (not supported) alternative if it wasn't for these two known issues:
It would be also nice to come up with a guide to slim down the services and the actual kernel to maximise the size of the memory available to the user... YellowDogLinux claims it can make available up to 192MB to the user.
Andrea,
The known issues both appear to have work arounds, so if someone wrote up a guide that used the work arounds I would think FC8 would work.
Jason,
Thanks for the guide; it was very helpful since I'm new to all this.
Some comments: I think that if you partition your disk the way the gnuradio page suggests (ie. without LVM) you won't need to install the updated lvm package and won't need to recompile the kernel. Also, it seems that "make install" for dtc will install it into $(HOME)/bin/, which is probably not where you want it to go. I got around this by running "HOME=/usr make install" so that it gets put into /usr/bin.
One thing I wasn't sure about was whether or not all of these steps should be run as root. Some of them say to run them as root and others don't so I wasn't sure. I ended up running them all as root; hopefully that won't cause permissions problems later on.
the URLs I have provided contain already details of work arounds, so it is not an unsurmountable problem. one just needs to be aware of them.
for the latter it is possible to specify root=/dev/ps3da1 at the kboot prompt (and yaboot.conf)
this is a very useful place to check for the Linux Kernel on PS3
https://ozlabs.org/mailman/listinfo/cbe-oss-dev
Does this fix the problems with PS3 firmware update 2.10? After I updated the firmware on my console, the PS3 wasn't able to send output to my monitor.
So I bought another PS3 and installed Linux without a problem. But when I try to start Linux, the console won't display data. And holding in the power button doesn't help either--it's completely non-responsive.
Does this fix the problems with PS3 firmware update 2.10? After I updated the firmware > on my console, the PS3 wasn't able to send output to my monitor.
that was initially fixed with v1.5.1 (20071220, kernel 2.6.23)
maturin wrote:
Does this fix the problems with PS3 firmware update 2.10? After I updated the firmware on my console, the PS3 wasn't able to send output to my monitor.
Do you mean the PS3 running the GameOS wasn't able to send output, or Linux running on the PS3 wasn't able to send output?
So I bought another PS3 and installed Linux without a problem. But when I try to start Linux, the console won't display data. And holding in the power button doesn't help either--it's completely non-responsive.
Holding the power button it's completely non-responsive? If the PS3 is running and you hold the power button down for 10 seconds, the PS3 should beep, the power light should start flashing, and eventually it should turn off (ie. power light turns red). None of this happens? If the PS3 is off, touching the power button doesn't make it beep and turn the PS3 on? If the PS3 is off, holding the power button down for more than 10 seconds doesn't cause it to beep a second time and boot the GameOS?
I'm revising the how-to to include this new update.
Also, I think I'm going to change the instructions so that LVM isn't used by default. Originally I wanted to keep the system as close to a default FC7 install as possible, but a friend of mine who was following these instructions hit a wall when the site that hosts the LVM patch became inaccessible for a day.
I'm currently installing a system with the new 20080201 add-on and no LVM. I'll use it for a day or so to make sure it's ok, and then post a new guide.
Does anyone think it's worth keeping the current (LVM based) guide around? Is there any specific scenerio where a non-LVM based install wouldn't be acceptible?
I admit... I found very simple the process of keeping the default anaconda (Fedora 7) disk partitioning even though it requires to install the LVM rpm package later on (also when using SDTV it's better not to have to make too many screen based changes given the very poor screen resolution!)
what would be ideal on the other hand is to provide a Fedora 8 installation guide and the two known workarounds.
