CentOS - Dec 2010 - centos 5.5 x64 bit issues on sun blade X6270 SERVER MODULE

Dear All,

I have managed perfectly fine to install centos 5.5 x64 on a new sun blade  
x6270 server module .i had to install in text mode since GUI install mode  
was not working

Actually this machine is going to replace my current working very low  
hardware server
the server is used as my primary dns, mail server , webmail server also  
running Mailscanner, mailwatch etc.
Also I want to use this new sun blade server as a virtual machine using xen

i have installed xen and uts fine

but i have a issue with the diplay driver

I did run system-config-network and selected the card as ast-ASpeedTech  
chipsets since my lspci says i have a
20:05.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics  
Family (rev 10)

now I run startx and i get the below error
X Window System Version 7.1.1
Release Date: 12 May 2006
X Protocol Version 11, Revision 0, Release 7.1.1
Build Operating System: Linux 2.6.18-53.el5 x86_64 Red Hat, Inc.
Current Operating System: Linux kmundns 2.6.18-194.26.1.el5xen #1 SMP Tue  
Nov 9 13:35:30 EST 2010 x86_64
Build Date: 17 November 2010
Build ID: xorg-x11-server 1.1.1-48.76.el5_5.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Dec 16 21:17:19 2010
(==) Using config file: "/etc/X11/xorg.conf"
dlopen: /usr/lib64/xorg/modules/drivers/ast_drv.so: wrong ELF class:  
ELFCLASS32
(EE) Failed to load /usr/lib64/xorg/modules/drivers/ast_drv.so
(EE) Failed to load module "ast" (loader failed, 7)
(EE) No drivers available.

Fatal server error:
no screens found
XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"
after 0 requests (0 known processed) with 0 events remaining.
---------------------------------------------------------

then i did change the driver to vesa and running startx shows me as below

xauth: creating new authority file /root/.serverauth.16448


X Window System Version 7.1.1
Release Date: 12 May 2006
X Protocol Version 11, Revision 0, Release 7.1.1
Build Operating System: Linux 2.6.18-53.el5 x86_64 Red Hat, Inc.
Current Operating System: Linux kmundns 2.6.18-194.26.1.el5xen #1 SMP Tue  
Nov 9 13:35:30 EST 2010 x86_64
Build Date: 17 November 2010
Build ID: xorg-x11-server 1.1.1-48.76.el5_5.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Dec 16 21:10:35 2010
(==) Using config file: "/etc/X11/xorg.conf"
(EE) VESA(0): No valid modes
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found
XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"
after 0 requests (0 known processed) with 0 events remaining.
------------------------------------------------------------

i really apprecite if someone out there would help me and advise


Thanks and Regards

simon

I really need the graphic to setup virtual machine since in GUI is quite  
simple
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.centos.org/pipermail/centos/attachments/20101216/99f829a1/attachment-0002.html>

sylvan.dcunha at gmail.com wrote:
<snip>
> I did run system-config-network and selected the card as ast-ASpeedTech
> chipsets since my lspci says i have a
> 20:05.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics
> Family (rev 10)
<snip>
> (==) Using config file: "/etc/X11/xorg.conf"
> dlopen: /usr/lib64/xorg/modules/drivers/ast_drv.so: wrong ELF class:
> ELFCLASS32
> (EE) Failed to load /usr/lib64/xorg/modules/drivers/ast_drv.so
> (EE) Failed to load module "ast" (loader failed, 7)
> (EE) No drivers available.
Ok, so the driver in /usr/lib64/xorg/modules/drivers/ is actually a 32-bit
driver, not a 64 bit one. Something's wrong there, and that shouldn't
happen.
<snip>
> then i did change the driver to vesa and running startx shows me as below
<snip>
> (==) Using config file: "/etc/X11/xorg.conf"
> (EE) VESA(0): No valid modes
> (EE) Screen(s) found, but none have a usable configuration.
<snip>
Try deleting /etc/X11/xorg.conf, and then fire up system-config-display.
Let it generate a completely new one. Then you might look at that file in
your favorite editor, and see if it makes sense.

Unless you've got more than one monitor, it should have one monitor, one
screen, and one videocard.

           mark

sylvan.dcunha at gmail.com wrote:
<snip>
> here in the readme it does mention 64 bit
What does it say about 64 bit systems? As I said, it sounds like you've
got the driver in the wrong directory. You might check for the driver in
the 32-bit directory, and what does file say about it? You REALLY, REALLY
need to get the right proprietary driver in the right
place.
>
> as you said I delete the xorg.conf file and ran system-config-display
> selected vesa gives the same error
>
> here below is my xorg.conf file
>
Where's the monitor section?
For example, mine has a stanza
Section "Monitor"
 ### Comment all HorizSync and VertSync values to use DDC:
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "DELL 2007FP"
    HorizSync       30.0 - 83.0
    VertRefresh     56.0 - 76.0
EndSection

which is not right for yours, unless you happen to have the same make and
model monitor, but there ought to be one.

<snip>
> Section "Device"
> Identifier "Videocard0"
> Driver "vesa"
> EndSection
>
> Section "Screen"
> Identifier "Screen0"
> Device "Videocard0"
This ought to have a line like below.
  Monitor   "Monitor0"
> DefaultDepth 24
> SubSection "Display"
> Viewport 0 0
> Depth 24
> EndSubSection
> EndSection
>
Please stop replying directly to me - keep it onlist, so others can jump in.

          mark