Ubuntu 8.10 running in low-graphics mode with AST2000

[Y.C. Chen]

Hi,
I'm S/W engineer in ASPEED Technology Inc. The system will show "Ubuntu is running in low-graphics mode" when launch X Server.
Here are some test we do:
1. reconfiure graphics; Create new configuration for the hardware; cp xorg.conf.new to /etc/X11/xorg.conf; cp AST2000 driver to /usr/lib/xorg/modules/drivers; reboot => the problem still exist (see attachment)
2. if I change the driver from 'ast' to 'vesa' in xorg.conf and reboot => the problem still exist
I tried to check Xorg.0.log, it looks like the AST2000's driver had been enabled properly. I don't know why the system still force to failsafe mode. Please comment.
Besides, we found the 'ast' driver didn't be included in Ubuntu in default. If we hope we can be included in later Ubuntu release, what should we do?

Regards,

Y.C. Chen

[Fernando Miguel (fernandomiguel)]

I'm setting this to ATI packages. if this is not correct, please assing to the proper driver package.
Thanks

[Fernando Miguel (fernandomiguel)]

Chen can you please execute the following command from a ubuntu karmic live cd?
apport-collect 345215

this will try to collect all necessary logs from your system and attach them to the bug.
daily live cds are here http://cdimage.ubuntu.com/daily-live/current/
and for alternate images: http://cdimage.ubuntu.com/live/current/

[kimus (kimus)]

Architecture: amd64
DistroRelease: Ubuntu 9.04
Package: xserver-xorg-video-ati 1:6.12.99+git20090908.fad9ee6c-0ubuntu0tormod~jaunty
PackageArchitecture: amd64
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersion: Linux version 2.6.28-11-generic (buildd@crested) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Xrandr:

glxinfo:

setxkbmap:

xdpyinfo:

xkbcomp:

[kimus (kimus)]

I build the driver from ftp://x.org/pub/individual/driver/xf86-video-ast-0.89.9.tar.gz and now the module loads fine... but xorg still does not load.

(II) AST: Driver for ASPEED Graphics Chipsets: ASPEED Graphics Family,
 ASPEED Graphics Family
(--) Chipset ASPEED Graphics Family found
(--) AST(0): Chipset: "ASPEED Graphics Family"
(II) AST(0): VESA VBE OEM: ASPEED
(II) AST(0): VESA VBE OEM Vendor: ASPEED Technology, Inc.
....
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) AIGLX: Screen 0 is not DRI2 capable
(II) AIGLX: Screen 0 is not DRI capable
(II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so
(II) GLX: Initialized DRISWRAST GL provider for screen 0
 ddxSigGiveUp: Closing log

[kimus (kimus)]

after installing xorg-driver-fglrx (using with compiled source that I described in comment #9) all went well.

[kimus (kimus)]

I must say I talked to soon... everything seems OK but the monitor shows a blank screen! :-S

[Y.C. Chen (yc-chen)]

Hi Kimus,
Thanks for your support. The "ast" driver is developed by ASPEED Technology Inc. There is no any relationship with "ati". We found this issue is our VBIOS take too much time to read EDID and cause this issue. I'm sorry miss to update the status on bugzilla. By the way, Could you let us know how to let 'ast' driver built into to Ubuntu release package in future?

Regards,

Y.C. Chen

[kimus (kimus)]

I found that running startx by hand works fine. starting gdm does not!
I can help you building a package after this is fixed :-)

[kimus (kimus)]

installed xdm and works !! finally! :-D

[Sebastien Bacher (seb128)]

Could you add your /var/log/Xorg.0.log* to the bug? and the message and syslog logs too

[kimus (kimus)]

Sorry, I can't attach the logs now. The machine is being used now.

BTW I was using Ubuntu 9.04 maybe Y.C. Chen can test on this version and attach the logs using gdm and using xdm.

Thank You

[Y.C. Chen (yc-chen)]

Hi,
The root cause is our previous VBIOS take too much time to read EDID and cause GDM time out. We had fixed it in VBIOS in v.89. If anyone doesn't like to update the VBIOS, use xdm instead or extend the GdmXserverTimeout in gdm.conf are the other options. I'm so appreciate if Ubuntu members can agree to modify the default settings of GdmXserverTimeout above than 15 in later release becasue the ASPEED's users use the previous VBIOS will not meet this issue.
Here are the parts of the syslog when gdm failed:
    Jul 29 07:04:28 ubuntu gdm[2909]: DEBUG: Attempting to parse key string: daemon/GdmXserverTimeout=10
    Jul 29 07:04:28 ubuntu gdm[2909]: DEBUG: Attempting to parse key string: daemon/GdmXserverTimeout=10
    Jul 29 07:04:28 ubuntu acpid: client connected from 2914[0:0]
    Jul 29 07:04:38 ubuntu gdm[2909]: DEBUG: Attempting to parse key string: daemon/GdmXserverTimeout=10
    Jul 29 07:04:39 ubuntu last message repeated 2 times
    Jul 29 07:04:39 ubuntu gdm[2909]: DEBUG: do_server_wait: Server timeout
    Jul 29 07:04:39 ubuntu gdm[2909]: DEBUG: gdm_server_start: After mainloop waiting for server
    Jul 29 07:04:42 ubuntu gdm[2909]: DEBUG: gdm_server_start: Temporary server failure (:0)
    Jul 29 07:04:42 ubuntu gdm[2909]: DEBUG: Attempting to parse key string: daemon/LogDir=/var/log/gdm
    Jul 29 07:04:42 ubuntu gdm[2508]: DEBUG: mainloop_sig_callback: Got signal 17
    Jul 29 07:04:42 ubuntu gdm[2508]: DEBUG: gdm_cleanup_children: child 2909 returned 64
    Jul 29 07:04:42 ubuntu gdm[2508]: DEBUG: X failed!

Regards,

Y.C. Chen

[Sebastien Bacher (seb128)]

the issue there was not a gdm one

[Y.C. Chen (yc-chen)]

Hi,
This issue had been fixed in VBIOS but I have no privilege to close this issue.
Please someone help to close this issue,

Regards,

Y.C. Chen