cannot start GUI in FC6

[S.V.]

Hi all,
I have a modest system: AMD Sempron 2800+ s754, ASUS K8V-VM Ultra mainboard with VIA chipset(K8M890 and 8237A), 256MB DDR400.
I dont have a seperate graphics card.

I've dualboot system with XP. When installing FC6 the installer told me that I dont have enough memory to use graphical installation and was taken to text-mode installion. Installation went smothly but there was nothing monitor(video) related settings. First, I couldnot boot into FC but then I edited my boot.ini. Now I can boot into FC6.

But I have this problem-By default I'm taken to terminal and if I type startx, the screen goes blank with a box having Hz ? moving around. Similar to what we get if monitor's data cable is removed.
If I press Ctrl+Alt+F1, I get the following msg:

(==)Logfile: "/var/log/Xorg.0.log", Time Sun Jan 7 13:25:25 2007
(==)Using config file: "/etc/X11/xorg.conf"
(EE) AIGLX: Screen0 is not DRI capable
localuser:root being added to access control list
SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2617
**(eggcups:2685):WARNING**: IPP request failed with status 1030

**(eggcups:2685):WARNING**: IPP request failed with status 1030
error getting update info: Cannot find avalid baseurl for repo:core
You cannot run beagle as root. Beagle is designed to run from your own user account. If you want to create multiuser or system-wide indexes, use the beagle-build-index tool.

You can override this setting using the beagle-config or beagle-settings tools.

The following is my /etc/X11/xorg.conf file:

# Xorg configuration created by pyxf86config

Section "ServerLayout"
	Identifier "Default Layout"
	Screen 0 "Screen0" 0 0
	Input device "Keyboard0" "Corekeyboard"
EndSection

Section "Input Device"
	Identifier "Keyboard0"
	Driver "kbd"
	Option "XkbModel" "pc105"
	Option "XkbLayout" "us"
EndSection

Section "Device"
	Identifier "Videocard0"
	Driver "vesa"
EndSection

Section "Screen"
	Identifier "Screen0"
	Device "Videocard0"
	DefaultDepth 24
	SubSection "Display"
		Viewport 0 0 
		Depth 24
	EndSubSection
EndSection

Note again that I don't have seperate graphics card. I'm using onboard VIA chipset(K8M890 and 8237A). My memory is 256MB DDR400 of which only 192MB is available. 64MB is for VGA frame buffer.

I tried something on my own:
1. changed 'vesa' to 'via'
2. changed depth to 16
3. Is Videocard0 PCI 1st slot? I changed it to 'Integrated VGA'
4. In BIOS, the Primary Graphics Adapter was PCIE VGA. tried changing it to Integrated VGA.
Needless to say nothing worked.
I'd taken a backup of the xorg.conf file and restored it for the moment.

I don't want funky 3D-4D wobble-gobble stuff if AIGLX and DRI are related to it. Just a simple working desktop so that I get productive immediately.

In need of urgent help,
SV.

[S.V.]

Hi all,
My problem is solved. One of my friends asked me to try the following command.

system-config-display

And immediately I was greeted with GUI. I had to choose my monitor and display adapter. Ofcourse my hardware wasnot detected but was given an option to set them to 'Generic'. And my GUI is up and running.

Hope this post will help someone else.

Thanxs again.
SV.

[tcomputerchip]

I am getting something similar to the messages you experienced.

Though, I know my vesa/nv drivers work. I want my "nvidia" drivers to work. I have been able to get them to work several times on this machine. But, after rebooting I am always back to square one.

So I started investigating files that have been overwritten. As my nvidia.ko file kept being rewritten. Installing the driver at runlevel 3 works for the session, but rebooting once again brought back the same messages.

Well, after long and hard work, even with some help with some co-workers, we are stumped to how this machine has gotten this way.

So, I did a % yum -y update
Now that went fine, but I noticed my X server has stayed at version 7.0.0 (maybe I need to update this somehow, not sure how to go about that).

Sorry to get off-topic a bit, but I think the X server is what is causing all these issues with the nvidia drivers not working. I think the driver is fine, and the X server is the problem. Or some rights to files are currupted.

So, here are the messages I get on running startx,
can anyone tell me what is going on?


_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/xeon:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6

X Window System Version 7.0.0
Release Date: 21 December 2005
X Protocol Version 11, Revision 0, Release 7.0
Build Operating System:Linux 2.6.9-34.ELsmp i686Red Hat, Inc.
Current Operating System: Linux xeon 2.6.18-1.2257.fc5smp #1 SMP Fri Dec 15 16:33:51 EST 2006 i686
Build Date: 09 January 2007
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: Tue Jan 16 23:30:07 2007
(==) Using config file: "/etc/X11/xorg.conf"
SESSION_MANAGER=local/xeon:/tmp/.ICE-unix/10599

** (eggcups:10646): WARNING **: IPP request failed with status 1030

** (eggcups:10646): WARNING **: IPP request failed with status 1030
Gnome-Message: gnome_execute_async_with_env_fds: returning -1

** (nm-applet:10667): WARNING **: <WARNING> nma_dbus_init (): nma_dbus_init() could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.60" is not allowed to own the service "org.freedesktop.NetworkManagerInfo" due to security policies in the configuration file'


waiting for X server to shut down The application 'gnome-panel' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
The application 'nautilus' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
nm-applet: Fatal IO error 104 (Connection reset by peer) on X server :0.0.

(gnome-panel:10640): GLib-GObject-CRITICAL **: g_object_run_dispose: assertion `G_IS_OBJECT (object)' failed
Window manager warning: Lost connection to the display ':0.0';
most likely the X server was shut down or you killed/destroyed
the window manager.
The application 'bluez-pin' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.


xinit: unexpected signal 2.
Couldnt get a file descriptor referring to the console