swift I followed your instructions and I was able to get the resolution of 1214 x 654 as best to see all the screen when I type sudo etc/init.d/gdm start. But I have one serious problem. After doing sudo etc/init.d/gdm stop type fbset -a -xres 1214 -yres 654 and then after sudo etc/init.d/gdm start, I am able to see all the workspace. The problem is when I configure that rc.local file and set vxres to 1214 and vyres to 654(the same values as above xres and yres as you did at your howto) and restart the ps3, when boot screen loads it shows a broken image, the screen does not show nothing. it seems that setting vxres and vyres values to the same ones as xres and yres brings this problem. When I boot using just the command fbset -a xres 1214 yres 654 without putting at rc.local file the vxres and vyres the screen shows ok (I mean without overscan) but gnome panels are not shown at the screen and at login screen the bottom buttons(shutdown and restart buttons do not appear). So, how do I fix this? the things just work when I boot with overscan gnome sessions, make gdm stop and type fbset xres 1214 and yres 654 then make gdm start. it shows everything normal until I reboot(crazy because when I make gdm start and then after open terminal and type fbset it shows xres 1214 yres 654 and vxres 1280 and vyres 720, I tried to put this config at rc.local but what happens is as I said the panels dissapear at gnome and the buttons at login page,shutdown and restart button, dessapear too. So help me, I want to keep my xres yres without these problems. I have here a 32 inch lcd tv panasonic. Thanks

mode "1214x654-60"
# D: 74.178 MHz, H: 44.957 kHz, V: 59.942 Hz
geometry 1214 654 1214 654 32
timings 13481 253 103 52 39 80 5
bcast true
rgba 8/16,8/8,8/0,8/24
endmode

This is What I get typing fbset after doing gdm stop fbset -a xres 1214 vyres 654 vxres 1214 vyres 654 and then after gdm start. This way Everything shows ok, but when I open rc.local put this values and reboot, the screen goes broken, nothing shows and I always have to reboot, make ctrl+alt+del and delete rc.local fbset command to be able to see the screen. Please help me config rc.local the correct way so that I can use my 1214 x 654 resolution and finally be able to see all the screen.

Carlos

@calj17 i have same problem with vxres and vyres so im using only xres and vres... Im dont using graphical login http://psubuntu.com/forum/viewtopic.php?t=1408 and before i startx (gnome or fluxbox) i set manualy fbset (linux "remember" my settings i just use cursor up).
But i have problem with new kernel. In mplayer i have :
error unable to find simle control PCM
edit:
I solved, by simply enabling "Enable Software Mixer" under the audio tab in Mplayer preferences.

Thanks again for this tutorial, setting was very easy to do.
If someone happens to have same 37" JVC LT-37DM7BU model following values should work perfectly.

kboot videomode number 132

rc.local file
fbset -a -xres 1825 -yres 1024

for 720p
fbset -a -xres 1216 -yres 680 -vxres 1216 -vyres 680

Ok cali, it is not a must too set the virtual resolutions. just put this line in your /etc/rc.local file.

fbset -a -xres 1214 -yres 654

Once you have saved that in rc.local your file should look like this.

#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.
fbset -a -xres 1214 -yres 654
exit 0


Now just reboot your ps3, if the screen starts and it is garbled hit ctrl+alt+backspace and that will cause the xserver to restart, if it does not look right try rebooting again and see what happens. Once in awhile when I boot my screen will do that same thing, that is because fbset did not run at the right time. I am looking for a better place to put the fbset command than rc.local but just use it for now. If that still does not work for you then please post back.

I tried to use it the way you told me. What happens is that gnome panels are not shown at the screen when programing rc.local with the resolution. But I noticed something interesting: the problem may be at the vxres and vyres. When I peform stop gdm and type fbset -a xres 1214 -yres 654 then the prompt command fixes it overscan and after doing gdm start the overscan is fixed(as I mentioned before). So I did fbset command at gnome after gdm start to see the vxres and vyres values and peformed too fbset command while in command prompt screen before doing gdm start. For my surprise at the command prompt after typing fbset -a xres 1214 -yres 654 the fbset command shows xres= 1214 yres= 654 vxres= 1280 and vyres= 720, but after when I do gdm start and inside gnome open a terminal and type fbset it shows this xres= 1216 yres= 654 vxres= 1216 vyres= 654. How can it be? two diferrent values of vxres and vyres deppending if I am running gnome or in command prompt? Why vxres and vyres values are different when I run fbset command at gnome terminal and at command prompt after gdm stop? Can this help to solve my problem and make my resolution permanent. Thanks

The virtual resolution has nothing to do with being able to see the panels when you start gnome. What virtual resolution does is allow you to have a work area larger than your screen, or put more simply, it allows you to slide applications off of the viewable work area. For example, have you ever opened up firefox and moved it to the left or right so that some of it slid off of your desktop? That is virtual resolution. If you set your virtual resolution to the same depth as your desktop, you can not do this. But it does NOT affect your panels.

I suspect *although I could be wrong* that for some reason your fbset command is not being run properly when gnome starts, and your panels are missing because you have overscan issues again. Try putting this into your rc.local and rebooting.

fbset -a xres 1214 -yres 654 &

Make sure the & is on there and see if that helps.

fbset command is not being run properly when gnome starts, and your panels are missing because you have overscan issues again... That is what exact happens. I think I was not very clear when I explained the problem. I get overscan again after setting fbset, when I start gnome my panels are at the bottom but are not showed because of the overscan issue. So i Think fbset is not starting at the right time as you said. I will try doing fbset with that symbol you said and see if it works.

Hopefully it does work for you, if not do you use msn messenger? You can add me and maybe we can work something out. If worse comes to worse I can always vnc to your ps3 and see what is going on. If you trust me enough that is

please add me at msn messenger mine is: calj17@hotmail.com

It will be a pleasure to talk with you and be your friend of course. bye and thanks

Carlos