• Set up you monitor

Monitor

The first thing you should do is set up your monitor to initiate the correct resolution at boot. To determine the correct video mode for your screen, use a tool called ps3videomode. It can be run from a terminal window ([Applications] > [Accessories] > [Terminal]) by typing:
ps3videomode will return a list of supported resolutions, with a number in front to represent the mode:
If you have a “Full HD” monitor with 1920×1080 resolution, use a 1080i or 1080p mode. If your TV is “HD Ready”, use one of the 720p modes (3, 8, 35 or 40).
Testing video modes
To check how a resolution works on your system you need to stop and start the Gnome desktop manager (gdm) between each test. Pressing Alt + F1 will give you a text console in which you enter your username and password.
Now stop gdm:
Set a temporary video using ps3videomode -v and a number, for instance:
or
(both commands represent various 1080p modes. You need to check with the table above which number corresponds with your monitor).
Start gdm using the new videomode with
Make the resolution permanent
When you have found a decent videomode, make the setting permanent by having Ubuntu load this mode on each startup. In a terminal window, type:
This will start the console text editor nano with an empty file called ps3videomode in the event.d folder. In this file, type:
Replace the 0 with the number key for your videomode.
In nano, save the file with Ctrl + o. Hit enter to confirm. Then Ctrl + x to exit nano.
You should now be able to reboot your system with your resolution of choice.
PSUbuntu forum: Audio & Video∞

Wireless

Wireless works great on WEP-encrypted networks, but WPA is problematic. If your WiFi is WEP-encrypted, it can be enabled by clicking on the network icon (top right panel) and selecting manual configuration. Go to the Wireless connection properties, and type in the name of your network (ESSID). Select your WEP password type and enter the key for your router.
In Connection Settings, choose Automatic configuration (DHCP). Click OK, and enable the connection by clicking the radio button for Wireless. You should now have wifi internet access. If anyone has gotten WPA to work, please let us know!
PSUbuntu forum: Network & Connectivity∞

Sixaxis support

Coming soon
PSUbuntu forum: Network & Connectivity∞

Applications

Running Ubuntu on a PS3 can be quite resource intensive due to the low amount of RAM available on the system, so try to minimize the number of running services. From [System] > [Preferences] > [Sessions] you can disable all of the startup programs in the list that you don’t need (if you have already configured your internet connection with WEP, you can even disable the Network Manager).
Overall, Linux is not known as a resource hog. The free operating system is a fairly lean machine out of the box -- some distributions moreso than others. Still, there are some tweaks you can make to any Linux installation to speed things up.
Most of the tips covered in this article involve using the command line and editing system files. Therefore, it goes without saying that you should be fairly comfortable with your command line skills before attempting any of these tweaks. However, if you're new to Linux, these system tweaks can serve as excellent feet-wetting exercises.
Tip: Remember to always make a backup when you're editing a system file. The quickest approach is to use the Terminal command cp. For example, to back up /etc/sysctl.conf you'd type:
Drop Unnecessary Processes
Ubuntu, like most other operating systems ship with some processes you probably don't need. Luckily you can disable many of them in the System > Preferences > Sessions box.
Unless you sync your phone with your computer, there's no need for the sync process to be running. Same with the Bluetooth process. If you're using Gnome, but not Evolution (the Gnome desktop's default mail client), get rid of the Evolution Alarm.
While the Sessions panel lists most of the common processes, it doesn't show everything. For the full list, you'll need the command line app sysv-rc-conf. To install the package, type:
sudo apt-get install sysv-rc-conf
You've entered into advanced user territory at this point, so be very careful about what you change since you can permanently hose your system using this editor. Remember to backup files and make small changes to single items rather than deleting in batches. After making a change, log out and then log back in to make sure everything still works as you would expect.
Swap Less Often
Swap files are what the Linux system uses to temporarily write things to disk. If you have enough RAM available, Linux uses that instead of the hard drive. But sometimes it's still over aggressive in writing to the swap drive.
Naturally, you can configure how often the OS falls back on the swap disk. How much this will speed things up is debatable -- the out-of-the-box setting will strike a nice balance most of the time -- but if you're really suffering, it's worth a try.
Before you change anything, run this command and look at the output number. The higher the number, the more often the kernel will use the swap disk.
Most distros set this number around 50 or 60. If you'd like to lower that, open up /etc/sysctl.conf:
Naturally, if you're on KDE, swap kate for gedit (or use emacs, vi or any other text editor you're comfortable with).
Add this line to the sysctl.conf file:
Speed Up Your Applications
OpenOffice. It's full featured, and it acts like it when it starts up. Suffer through that long wait one last time, then open the app's Preferences window. Look for the Memory option under OpenOffice.org and increase the memory allotted to the Graphics cache, under both the "Use for OpenOffice.org" and "Memory per Object." If you're a heavy Office user and you have RAM to spare, don't be afraid to set these high. Say 100+ for the Graphics Cache and around 10MB per Object. Play around and see what works on your system.
Firefox. If the Fox has you down, try Konqueror if you're on KDE or, otherwise, Opera. Both use less RAM than Firefox and may be faster on older hardware. Of course, Firefox 3 addresses hundreds of Firefox 2's memory leaks, so this may be less of an issue when version 3 of the browser is released.
Use a "Lighter" Desktop Environment. KDE and Gnome both look very nice and offer some great advanced features, but both can be pretty tough on the processor. Give fvwm, fluxbox IceWM or even Xfce (which is still quite nice to look at) a try. They'll be much snappier. Even better, master the command line -- it's fast, lightweight and simple once you adjust to its way of thinking.
You can also consider installing the more lightweight XFCE desktop manager for Ubuntu by typing
See this forum thread for some excellent tips on how to reduce memory usage.
PSUbuntu forum: Applications & Games

This page will help you configure and set up Ubuntu on a Playstation 3, following a fresh installation of the OS. Thanks to all contributions from the PSUbuntu forums.
PSUbuntu forum: Audio & Video
PSUbuntu forum: Network & Connectivity
Coming soon (we hope)
PSUbuntu forum: Network & Connectivity
$ sudo cat /proc/sys/vm/swappiness
$ sudo gedit /etc/sysctl.conf
vm.swappiness=10

Post-installation tweaks