[RV350 9600 Pro] 1280x800 missing, only 1920x1200 available

[Dascon]

Hello,

I am testing Ubuntu intrepid beta1 and have troubles with my screen resolution.

Hardware:
Laptop Dell Inspiron 8600 with Mobility ATI Radeon 9600Pro 128MB
Screen resolution: 1920x1200, but normally used at 1280x800

Under Hardy 1280x800 worked fine with build-in driver and fglrx-driver. With Intrepid this resolution is not available and also the laptop screen is shown only as 15".

How can I add 1280x800 to the resolution list?

Regards
[lspci]
00:00.0 Host bridge [0600]: Intel Corporation 82855PM Processor to I/O Controller [8086:3340] (rev 03)
     Subsystem: Dell Device [1028:016a]
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10] [1002:4e50]
     Subsystem: Dell Device [1028:2001]

[Dascon (daniel-schimrik)]

I figured out how to add 1280x800 manually, but this has to be done on each start of Intrepid. To run this script automatically on boot up, nothing happens.

Is there a way to permanently add a resolution to xrandr?

xrandr --newmode "1280x800" 83.46 1280 1344 1480 1680 800 801 804 828 -HSync +Vsync &
xrandr --addmode LVDS 1280x800 &
xrandr --output LVDS --mode 1280x800

[Bryce Harrington (bryce)]

Could you also please attach the output of `lspci -vvnn`? Thanks ahead of time.

Meanwhile, one way to work around the issue is to place your xrandr command into your ~/.xprofile (remember to set that files execute bit). You could also add it to your global gdm/kdm startup scripts.

[Dascon (daniel-schimrik)]

Attached you find the result of 'lspci -vvnn'.
Your solution with .xprofile works perfect, thanks.

[Bryce Harrington (bryce)]

Hi Dascon,

I'm glad to hear the .xprofile workaround helped. Next step is to figure out what it's doing wrong.

For this, can you please attach the output from the following commands?

  * xrandr --verbose
  * get-edid | parse-edid # from the read-edid package

This should give us some ideas about what resolutions your monitor thinks it can provide.

[Dascon (daniel-schimrik)]

Hello Bryce,

unfortunately I cannot help you on that question right now. Cause of some other effects on Intrepid I switched back to Hardy (no fglrx working with mobile RV350, cpufreq-problems)

What I could send you right now is the output of your commands under hardy, where everything works fine.

I will download intrepid live-cd and get the results of your commands.

Regards, Dascon

[exactt (giesbert)]

i am attaching my logs as well...

can anybody help my create the xrandr commands. i am always getting errors issueing the first command:

 X Error of failed request: BadName (named color or font does not exist)
  Major opcode of failed request: 153 (RANDR)
  Minor opcode of failed request: 16 ()
  Serial number of failed request: 13
  Current serial number in output stream: 13

thank you...

[exactt (giesbert)]

all on intrepid by the way...

[exactt (giesbert)]

seems i messed up the files last time... here they come again...

[exactt (giesbert)]

i just added that this bug affects me with the vesa driver.

ati driver is not working because of https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/294653

thx for your help!

[Bryce Harrington (bryce)]

exactt, if you're seeing it on -vesa you are having a different bug since this one is particular to -avi. You should report your bug separately.

[Bryce Harrington (bryce)]

Dascon, okay actually the problem is that you were having a bug in Hardy that went away in Intrepid. It seems that in Hardy X was unable to read your monitor's EDID. Compare the get-edid|parse-edid results you posted for each, and you'll see in Hardy it says "Call failed" so it is falling back to some default stuff that puts in a bunch of other resolutions, including the one you liked. In Intrepid, the EDID works properly, and X is not putting in the default modes like 1280x800.

Anyway, the problem was fixed in the xserver we have in Jaunty. Feel free to reopen this bug if you still see the problem after upgrading to that.

[Bryce Harrington (bryce)]

I've documented this at

https://wiki.ubuntu.com/X/Troubleshooting/Resolution#Problem:%20%20The%20LCD%27s%20maximum%20resolution%20is%20detected%20automatically,%20but%20lower%20resolutions%20are%20not%20available