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
LEARN ABOUT REDHAT
dummy_cs
DUMMY_CS(4) Kernel Interfaces Manual DUMMY_CS(4)
NAME
dummy_cs - PCMCIA dummy device driver
SYNOPSIS
insmod dummy_cs.o [pc_debug=n] [free_ports=n] [irq_list=i,j,...]
DESCRIPTION
The dummy_cs module has two purposes. It is intended as a demonstration of how to write the PCMCIA interface code for a client driver, and
the source code is heavily commented. It is also written to function as a sort of generic ``point enabler'': when bound to any PCMCIA IO
card, it will read the card's Configuration Information Structure, and configure the card appropriately. The configuration includes set-
ting up IO and memory windows, configuring the card for interrupts, and initializing the card's PCMCIA configuration registers.
It turns out that many cards report incomplete or inaccurate configuration information, due to vendor carelessness and the complexity of
the data format. A vendor driver can generally take for granted many configuration details, so there is not much incentive for vendors to
ensure that the on-card information is complete. Thus, the dummy_cs module is limited by its generality: since it makes no assumptions
about card types, it is forced to rely on the card information, for better or worse.
PARAMETERS
pc_debug=n
Selects the PCMCIA debugging level. This parameter is only available if the module is compiled with debugging enabled. A non-zero
value enables debugging.
free_ports=n
A flag indicating if the IO ports allocated for the card should be freed from the kernel resource maps. This is useful if the dummy
driver is being used to configure a card in preparation for loading a specific PCMCIA-unaware driver. The default is 0 (false).
irq_list=i,j,...
Specifies the set of interrupts that may be allocated by this driver.
AUTHOR
David Hinds - dahinds@users.sourceforge.net
SEE ALSO
cardmgr(8), pcmcia(5).
pcmcia-cs 2000/06/12 21:24:47 DUMMY_CS(4)