[Hardy] Toshiba laptop screen at max 800x600 rather than 1024x768

[Caroline Ford]

New fully updated install of Hardy on a Toshiba satellite pro 6050. Screen should be 1024x768, Ubuntu is using 800x600 leaving a large black border.

Graphics chipset is Trident CyberBladeXPAi1

Looking at Xorg.0.log the TRIDENT driver has identified that it has a 1024x768 panel

TFT Panel 1024x768 found

But presumes it has 24 bit colour earlier. I suspect this machine cannot do 24 bit colour and use the entire screen, In these cases Ubuntu should use 16 bit colour and the full resolution.

[Caroline Ford (secretlondon)]

Duplicate attachments - connection problems.

[Caroline Ford (secretlondon)]

secret@celery:~$ lspci -nn | grep VGA
01:00.0 VGA compatible controller [0300]: Trident Microsystems CyberBlade XPAi1 [1023:8820] (rev 82)

[Caroline Ford (secretlondon)]

secret@celery:~$ sudo lspci -vvnn
[sudo] password for secret:
00:00.0 Host bridge [0600]: ALi Corporation M1644/M1644T Northbridge+Trident [10b9:1644] (rev 01)
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR+
 Latency: 0
 Region 0: Memory at f0000000 (32-bit, prefetchable) [size=64M]
 Capabilities: [b0] AGP version 2.0
  Status: RQ=28 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4
  Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none>
 Capabilities: [a4] Power Management version 1
  Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:01.0 PCI bridge [0604]: ALi Corporation PCI to AGP Controller [10b9:5247] (prog-if 00 [Normal decode])
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR-
 Latency: 0
 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
 Memory behind bridge: f7f00000-fdffffff
 Prefetchable memory behind bridge: 50000000-500fffff
 Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR+
 BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- >Reset- FastB2B-

00:02.0 USB Controller [0c03]: ALi Corporation USB 1.1 Controller [10b9:5237] (rev 03) (prog-if 10 [OHCI])
 Subsystem: Toshiba America Info Systems Unknown device [1179:0004]
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
 Latency: 64 (20000ns max), Cache Line Size: 32 bytes
 Interrupt: pin A routed to IRQ 11
 Region 0: Memory at f7eff000 (32-bit, non-prefetchable) [size=4K]
 Capabilities: [60] Power Management version 2
  Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:04.0 IDE interface [0101]: ALi Corporation M5229 IDE [10b9:5229] (rev c3) (prog-if f0)
 Subsystem: Toshiba America Info Systems Unknown device [1179:0004]
 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
 Latency: 64 (500ns min, 1000ns max)
 Interrupt: pin A routed to IRQ 255
 Region 0: [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [disabled] [size=8]
 Region 1: [virtual] Memory at 000003f0 (type 3, non-prefetchable) [disabled] [size=1]
 Region 2: [virtual] Memory at 00000170 (32-bit, non-prefetchable) [disabled] [size=8]
 Region 3: [virtual] Memory at 00000370 (type 3, non-prefetchable) [disabled] [size=1]
 Region 4: I/O ports at eff0 [size=16]
 Capabilities: [60] Power Management version 2
  Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:06.0 Multimedia audio controller [0401]: ALi Corporation M5451 PCI AC-Link Controller Audio D...

[Caroline Ford (secretlondon)]

secret@celery:~$ sudo ddcprobe
vbe: VESA 2.0 detected.
oem: Trident CYBER 8820
memory: 16384kb
mode: 1280x1024x16m
mode: 1280x1024x64k
mode: 1280x1024x32k
mode: 1024x768x16m
mode: 1280x1024x256
mode: 640x480x16m
mode: 800x600x16m
mode: 1024x768x32k
mode: 1024x768x64k
mode: 800x600x32k
mode: 800x600x64k
mode: 640x480x32k
mode: 640x480x64k
mode: 1024x768x256
mode: 1280x1024x16
mode: 320x200x32k
mode: 320x200x64k
mode: 320x200x16m
mode: 640x400x256
mode: 640x480x256
mode: 800x600x256
mode: 1024x768x16
mode: 132x25 (text)
mode: 132x43 (text)
mode: 132x60 (text)
mode: 80x60 (text)
mode: 800x600x16
edid:
edid: 1 3
id: 5082
eisa: TOS5082
serial: 00000000
manufacture: 0 1990
input: analog signal.
screensize: 29 22
gamma: 1.000000
dpms: RGB, no active off, suspend, standby
timing: 720x400@70 Hz (VGA 640x400, IBM)
timing: 640x480@75 Hz (VESA)
timing: 800x600@72 Hz (VESA)
timing: 1024x768@87 Hz Interlaced (8514A)
ctiming: 1280x1024@60
ctiming: 1600x1200@60
dtiming: 1024x768@74
monitorname: TOSHIBA Inte
monitorname: rnal Panel
monitorname:

[Caroline Ford (secretlondon)]

secret@celery:~$ xrandr
Screen 0: minimum 320 x 240, current 800 x 600, maximum 800 x 600
default connected 800x600+0+0 0mm x 0mm
   800x600 60.0* 56.0
   640x480 60.0
   400x300 60.0 56.0
   320x240 60.0

[Caroline Ford (secretlondon)]

From xorg.0.conf TRIDENT seems to be using the defaults:

(II) TRIDENT(0): Configured Monitor: Using default hsync range of 31.50-37.90 kHz
(II) TRIDENT(0): Configured Monitor: Using default vrefresh range of 50.00-70.00 Hz
(WW) TRIDENT(0): Unable to estimate virtual size

[Caroline Ford (secretlondon)]

Configured Monitor: Using default hsync range of 31.50-37.90 kHz
(II) TRIDENT(0): Configured Monitor: Using default vrefresh range of 50.00-70.00 Hz
(WW) TRIDENT(0): Unable to estimate virtual size

Google has found working xorg.confs with the following figures:

Section "Monitor"
    Identifier "Monitor0"
    VendorName "Monitor Vendor"
    ModelName "Toshiba TOS5082"
    DisplaySize 240 180
    HorizSync 31.0 - 48.0
    VertRefresh 50.0 - 70.0
    Option "dpms"
EndSection

Is this a problem with the hsync?

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in xorg.

[Mike Basil (mbasil77)]

I'm having this exact same issue. Is there a work around or eta for this?

mb

[Caroline Ford (secretlondon)]

There is a workround which is to manually edit your xorg.conf file. I
will attach mine if it helps.

[Mike Basil (mbasil77)]

That fixed it. Much appreciated.

mb

[Gareth Walker (gareth-r-walker)]

Hi, I have the same model of Toshiba laptop (although I have had to replace the screen), I am having the same problem, but the modified xorg.conf above does not work for me; I get a messed up screen at the login. (I have the Kubuntu KDE4 version of Hardy installed btw)

I've tried copying what I think are the relevant sections from it, the "Device" and "Screen" sections, one at a time and I got the same messed up screen after I added the "Screen" section. I'm afraid it is a bit beyond me now as to what I should be doing to resolve this. Can someone please advise?

thanks,
G

[Zsolt Branyiczky (brazso)]

I use Kubuntu and setting monitor #1 to "LCD Panel 1024x768" in "System Settings / Monitor & Display" solved the problem, the slider was extended with 1024x768 resolution after 800x600. I did not have to touch xorg.conf at all.

[Poli (poli-mr)]

I fell into this problem when upgrading from 6.06 to 8.04 on my Toshiba Satellite A25-S207 that has this Trident CyberBlade XPAi1 graphics chip.

I got it running by following http://ubuntuforums.org/showthread.php?p=4772671

It is always a great inconvenient when something stops working as it should in a upgrade. Found some forum posts describing the bug before 8.04 release.

[Bryce Harrington (bryce)]

Hi secretlondon,

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with the latest development release of Ubuntu? (ISOs are available from cdimage.ubuntu.com)

If it remains an issue, could you also attach a new /var/log/Xorg.0.log?
Thanks in advance.

The output of lspci -vvnn would also be worth having.

[chrisubuntu (chrisplx)]

Hi,
After installing ubuntu 8.10 I had the same issue.
Thanks to Caroline for the xorg.conf fix. It worked for me on my Toshiba A25-S307 .
I wanted to configure xorg.conf myself like Poli did using displayconfig-gtk but it isn't present in 8.10 .

And I also have attach what Bryce is asking.
Hopping to see this fix included in later release.

Chris

[chrisubuntu (chrisplx)]

I forgot to sudo the first lspci -vvnn

[Genti L (webmaster-setupmypage)]

I have the same problem.
I think this bug was introduced with an update because with the an older CD ( I believe 8.04) it worked fine.
After all the updates (when version became 8.04.1) it started happening. The link above to the Ubuntu forum might work because of this.
dpkg -l *trident* returns:
ii xserver-xorg-video-tri 1:1.2.4-1 X.Org X server -- Trident display driver

#
#

root@neta-toshiba:/etc/X11# ddcprobe
vbe: VESA 2.0 detected.
oem: Trident CYBER 8820
memory: 16384kb
mode: 1280x1024x16m
mode: 1280x1024x64k
mode: 1280x1024x32k
mode: 1024x768x16m
mode: 1280x1024x256
mode: 640x480x16m
mode: 800x600x16m
mode: 1024x768x32k
mode: 1024x768x64k
mode: 800x600x32k
mode: 800x600x64k
mode: 640x480x32k
mode: 640x480x64k
mode: 1024x768x256
mode: 1280x1024x16
mode: 320x200x32k
mode: 320x200x64k
mode: 320x200x16m
mode: 640x400x256
mode: 640x480x256
mode: 800x600x256
mode: 1024x768x16
mode: 132x25 (text)
mode: 132x43 (text)
mode: 132x60 (text)
mode: 80x60 (text)
mode: 800x600x16
edid:
edid: 1 3
id: 5082
eisa: TOS5082
serial: 00000000
manufacture: 0 1990
input: analog signal.
screensize: 29 22
gamma: 1.000000
dpms: RGB, no active off, suspend, standby
timing: 720x400@70 Hz (VGA 640x400, IBM)
timing: 640x480@75 Hz (VESA)
timing: 800x600@72 Hz (VESA)
timing: 1024x768@87 Hz Interlaced (8514A)
ctiming: 1280x1024@60
ctiming: 1600x1200@60
dtiming: 1024x768@74
monitorname: TOSHIBA Inte
monitorname: rnal Panel
monitorname:

#
#

I have tried to leave the xorg.conf blank and also added the driver and various HorizSync and VertRefresh.
In a previous file I also tried to manually set modes with up to 16bit color but still the same.

[Genti L (webmaster-setupmypage)]

I noticed that on the previous lspci -vvnn I had used the normal user. Here is the info as root:

00:00.0 Host bridge [0600]: ALi Corporation M1644/M1644T Northbridge+Trident [10b9:1644] (rev 01)
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR+
 Latency: 0
 Region 0: Memory at f0000000 (32-bit, prefetchable) [size=64M]
 Capabilities: [b0] AGP version 2.0
  Status: RQ=28 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4
  Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none>
 Capabilities: [a4] Power Management version 1
  Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:01.0 PCI bridge [0604]: ALi Corporation PCI to AGP Controller [10b9:5247] (prog-if 00 [Normal decode])
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR-
 Latency: 0
 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
 Memory behind bridge: f7f00000-fdffffff
 Prefetchable memory behind bridge: 40000000-400fffff
 Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR+
 BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- >Reset- FastB2B-

00:02.0 USB Controller [0c03]: ALi Corporation USB 1.1 Controller [10b9:5237] (rev 03) (prog-if 10 [OHCI])
 Subsystem: Toshiba America Info Systems Unknown device [1179:0004]
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
 Latency: 64 (20000ns max), Cache Line Size: 32 bytes
 Interrupt: pin A routed to IRQ 11
 Region 0: Memory at f7eff000 (32-bit, non-prefetchable) [size=4K]
 Capabilities: [60] Power Management version 2
  Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:04.0 IDE interface [0101]: ALi Corporation M5229 IDE [10b9:5229] (rev c3) (prog-if f0)
 Subsystem: Toshiba America Info Systems Unknown device [1179:0004]
 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
 Latency: 64 (500ns min, 1000ns max)
 Interrupt: pin A routed to IRQ 255
 Region 0: [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [disabled] [size=8]
 Region 1: [virtual] Memory at 000003f0 (type 3, non-prefetchable) [disabled] [size=1]
 Region 2: [virtual] Memory at 00000170 (32-bit, non-prefetchable) [disabled] [size=8]
 Region 3: [virtual] Memory at 00000370 (type 3, non-prefetchable) [disabled] [size=1]
 Region 4: I/O ports at eff0 [size=16]
 Capabilities: [60] Power Management version 2
  Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:06.0 Multimedia audio controller [0401]: ALi Corporation M...

[Genti L (webmaster-setupmypage)]

Has anyone tried the latest version of trident?
http://packages.debian.org/changelogs/pool/main/x/xserver-xorg-video-trident/xserver-xorg-video-trident_1.3.0-2/changelog#year2008

Possibly the unstable (not experimental) 1.3.0-1.
You might need to update some packages.

[David Gerard (dgerard)]

It's still bad in Karmic (I'm now using the same Satellite Pro 6050 that Caroline filed this bug concerning) - this is Xorg Server 1.6.2rc1 with latest everything.

It's a very crusty old driver. I asked on the xorg mailing list about hints and tips on fixing it, they suggested faking an EDID response, which worked in a similar Trident bug. xorg is unlikely to fix it upstream until someone sends a patch, which we could do.

[Caroline Ford (secretlondon)]

xserver-xorg-video-trident (1:1.3.1-1) in Karmic.

We have a lot of broken resolution bugs on xserver-xorg-video-trident

bug #209018 - think this is actually a dupe of this one, but that one worked in pre-hardy
bug #239722 - says worked in hardy using displayconfig-gtk, not in intrepid
bug #271987 -
bug #289491 - says autodetected hardy, but not intrepid?
bug #312840 - possibly the same, lacks details
bug #315329 - says worked in hardy using displayconfig-gtk, not in intrepid

[Caroline Ford (secretlondon)]

And expired bugs:

bug #205802

Xorg comment as referenced above:

http://lists.freedesktop.org/archives/xorg/2009-July/046320.html

[Yuhong Bao (yuhongbao-386)]

Ported the patch.
Untested, use at your own risk, corrections welcome.
Have an affected machine, but it does not have Linux installed right now

[Bryce Harrington (bryce)]

When you feel the patch is adequately tested and ready for inclusion in ubuntu, please subscribe the 'ubuntu-sponsors' team.

Also, it would be a good idea to forward the patch upstream to freedesktop.org for review.

[Ryann Pinnegar (ryannpinnegar)]

Toshiba laptop screen at max 800x600 rather than 1024x768: This applies to me!

I have a Toshiba Satellite and a Trident Microsystems CyberBlade XPAi1 video card

Here is my operating system info from my Xorg log:
Build Operating System: Linux 2.6.24-27-server i686 Ubuntu
Current Operating System: Linux ubuntu 2.6.32-34-generic #77-Ubuntu SMP Tue Sep 13 19:40:53 UTC 2011 i686

[Thomas Hotz (thotz-deactivatedaccount)]

Any updates about applying the patch? The status is In Progress for a very long time.

[bugbot (bugbot)]

We're closing this bug since there has not been a response from the original reporter. However, the issue still exists please feel free to reopen with the requested information. If you're not the original reporter, we'd prefer you file a new bug report.

Some tips:

  * Report X.org bugs via the command: `ubuntu-bug xorg`

  * Test against the latest development Ubuntu. http://cdimage.ubuntu.com/daily-live/
    Bugs marked as affecting the development version tend to get priority attention.

  * The `xdiagnose` utility has functionality for enabling debugging and
    analyzing a few common X problems.

  * Tag your bugs with the Ubuntu versions you have reproduced the issue in.

  * See https://wiki.ubuntu.com/X/Reporting for tips on writing good bug reports.