01-08-2010
Help setting up XServer in Centos 5.4
Hi,
After I remove the external video card after setup, Centos 5.4 upon boot cannot start the XServer for the onboard video card. How can I configure XServer to get it working? Machine is a DELL OPTIPLEX 745
Last edited by Yogesh Sawant; 01-12-2010 at 05:01 AM..
10 More Discussions You Might Find Interesting
1. Solaris
Hi all,
My Ultra 10, running Solaris 8, is giving me problems :( Currently, whenever it boots, the Xserver will not come up, saying "Xserver cannot be started on display 0".
I thought this might have something to do with OWconfig, and so poked it a little (moving params onto different... (5 Replies)
Discussion started by: Gravity
5 Replies
2. UNIX for Advanced & Expert Users
I've recently patched my AIX box from ML02 to ML06 and somehow along the way the monitor no longer starts up in GUI mode.
Running the command xinit gives me the following errros
ioctl Bad file Number
1356- Unable to start the X server
I've checked the path variables, the monitor, the lai0... (0 Replies)
Discussion started by: mahartle
0 Replies
3. UNIX for Dummies Questions & Answers
Hello , im not sure if its the right forum... im sorry if not
im working with putty allot , but now I started to work with more graphical applications and
im looking for free simple and fast Xserver to remote connection, can someone recommend me
if there is something like that ? (3 Replies)
Discussion started by: umen
3 Replies
4. Solaris
Dear
When I restart the Xserver it works fine for less than half an hour and throw this error afterward.
After setting the display DISPLAY=10.195.2.13:0.0, I tried to run xclock. After few minutes it throws this error message
"X connection to 10.195.2.13:0.0 broken (explicit kill or... (0 Replies)
Discussion started by: tanvirscsa
0 Replies
5. UNIX for Advanced & Expert Users
Hi,
From my workstation (win XP)I open a telnet session on Linux(Red Hat) server.
When I issue :
# xclock
I have :
Error: Can't open display:
Then :
# export DISPLAY=192.16.1.87:0.0
# xclock
Error: Can't open display: 192.16.1.87:0.0
Do you have an idea ?
Many thanks. (6 Replies)
Discussion started by: big123456
6 Replies
6. Solaris
I have problem with my V490 server which running on solaris 8. The error show on log file
X_mkdir: nosuch file or directory
Fatal server error:
Failed to establish all listening sockets
error (pid 299): server unexpectedly died
error (pid 299): server for display :0 cant be started
... (1 Reply)
Discussion started by: shamsul
1 Replies
7. UNIX for Dummies Questions & Answers
Hello folks;
i have Linux CentOS server that is already on my corporate domain and I'm trying to configure Samba so i can browse or see it from my Windows machine. i followed a lot of threads but still can't login when trying to map a drive.
Is there a way to setup Samba on that server (with... (2 Replies)
Discussion started by: Katkota
2 Replies
8. Red Hat
Dear Linux Experts,
On my windows 7 desktop with the help of Vmware workstation (Version 7.1),
created virtual machine and installed Centos 5.7 successfully using ISO image.
Query : Is this possible to upgrade the Centos 5.7 using Centos 5.8 ISO image to Centos version 5.8?.. if yes kindly... (2 Replies)
Discussion started by: Ananthcn
2 Replies
9. Red Hat
Hey guys, I've reached the point of setting up VM's on XEN but the net installations seem to be failing when I am in the netinstall on the actual VM, so this leads me to believe that the networking on the host machine is not set up correctly. I am running CentOS 5.9 along with XEN and was just... (0 Replies)
Discussion started by: mccabec123
0 Replies
10. Solaris
I have this Xserver not display issues, I try search from the forum but found out it can have different errors from the Xerrors logs. Here I upload and hope admin can help.
root@ccs # more Xerrors
The loadable module for the display device SUNWast is not installed.
Fatal server error:... (1 Reply)
Discussion started by: mailbox80
1 Replies
VGA(4) BSD Kernel Interfaces Manual VGA(4)
NAME
vga -- generic video card interface
SYNOPSIS
options VESA
options VESA_DEBUG=N
options VGA_ALT_SEQACCESS
options VGA_NO_FONT_LOADING
options VGA_NO_MODE_CHANGE
options VGA_SLOW_IOACCESS
options VGA_WIDTH90
device vga
In /boot/device.hints:
hint.vga.0.at="isa"
DESCRIPTION
The vga driver is a generic video card driver which provides access to video cards. This driver is required for the console driver
syscons(4). The console driver will call the vga driver to manipulate video hardware (changing video modes, loading font, etc).
The vga driver supports the standard video cards: MDA, CGA, EGA and VGA. In addition, the driver can utilize VESA BIOS extensions if the
video card supports them. VESA support can either be statically included in the kernel or can be loaded as a separate module.
In order to statically link the VESA support to the kernel, the VESA option (see below) must be defined in the kernel configuration file.
The vesa module can be dynamically loaded into the kernel using kldload(8).
DRIVER CONFIGURATION
Kernel Configuration Options
The following kernel configuration options (see config(8)) can be used to control the vga driver. These options provide compatibility with
certain VGA cards.
VGA_ALT_SEQACCESS
You may want to try this option if the mouse pointer is not drawn correctly or the font does not seem to be loaded properly on the VGA
card. However, it may cause flicker on some systems.
VGA_SLOW_IOACCESS
Older VGA cards may require this option for proper operation. It makes the driver perform byte-wide I/O to VGA registers and slow
down a little.
VGA_WIDTH90
This option enables 90 column modes: 90x25, 90x30, 90x43, 90x50, 90x60. These modes are not always supported by the video card and
the display. It is highly likely that LCD display cannot work with these modes.
The following options add optional features to the driver.
VESA Add VESA BIOS support to the driver. If the VGA card has the VESA BIOS extension 1.2 or later, this option will utilize the VESA BIOS
service to switch to high resolution modes.
VESA_DEBUG=N
Set the VESA support debug level to N. The default value is zero, which suppresses all debugging output.
The following options will remove some features from the vga driver and save kernel memory.
VGA_NO_FONT_LOADING
The vga driver can load software font to EGA and VGA cards. This option removes this feature. Note that if you use this option and
still wish to use the mouse on the console then you must also use the SC_ALT_MOUSE_IMAGE option. See syscons(4).
VGA_NO_MODE_CHANGE
This option prevents the driver from changing video modes.
EXAMPLES
Your kernel configuration should normally have:
device vga
And you need the following line in /boot/device.hints.
hint.vga.0.at="isa"
The following lines should be included in the kernel configuration file in order to enable the VESA BIOS Extension support.
options VESA
device vga
If you do not want VESA support included in the kernel, but want to use occasionally, do not add the VESA option. And load the vesa module
as desired:
kldload vesa
SEE ALSO
vgl(3), syscons(4), config(8), kldload(8), kldunload(8)
STANDARDS
Video Electronics Standards Association, VESA BIOS Extension (VBE).
HISTORY
The vga driver first appeared in FreeBSD 3.1.
AUTHORS
The vga driver was written by Soren Schmidt <sos@FreeBSD.org> and Kazutaka Yokota <yokota@FreeBSD.org>. This manual page was written by
Kazutaka Yokota.
BSD
June 30, 1999 BSD