X problems in FC4

Odins_Son · 07-16-2005, 10:39 AM

I have a dell 420c server and there was a problem with X and to solve it I followed what this guy did and X started just fine

Quote:

I downloaded the i810_drv.o file, dropped it into /usr/X11R6/lib/modules/drivers/i810_drv.o
and then restarted X (I just issued a kill -HUP to gdm).

Here's part of my xorg.conf (just noticed that I redefined it as i915 -- same driver, though).
# Xorg configuration created by system-config-display

Section "Device"
Identifier "Videocard0"
Driver "i810"
VendorName "Videocard vendor"
BoardName "Intel 915"
Option "noaccel"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 16
Modes "800x600" "640x480"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1280x1024" "1152x864" "1152x768" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
Modes "800x600" "640x480"
EndSubSection
EndSection

Section "DRI"
Group 0
Mode 0666
EndSection

I had to reboot the server a few days ago and I had the same problem as I had before. X would not load. Here is some of the error stuff that I recieved.

I noticed that you got your X to work on your server with the i810 module. I did the same changes as you did and I managed to get X to start and everything worked fine.

However a few days ago I had to reboot my server and the X wont load, same problem as before. Nothing has changed in my configs or anything. I seriously cannot figure out why this is happening. The only thing that I can think of that may have screwed things up is vnc, today I was buggering around with the vnc server.

This is the error message
-------------------------------
(II) Primary Device is: PCI 00:02:0
(--) Assigning device section with no busID to primary device
(EE) No devices detected.
Fatal server error:
no screens found

Any help on this would be awsome.

edong23 · 07-17-2005, 11:35 AM

could be a module unloading problem. do you have module unloading in the kernel? i think i have heard of this before, i cant see to remember the fix. if it is an intel card, y didnt you just use the intel kernel module that is in the kernel, or download the newest dri build from intel? you might want to try those things, since they will both compile the module on your system, for you system. It isnt always a good idea to use only precompiled software. if you are using a stock slackware kernel, and it is 2.4, then it doesnt have module unloading supported. however i have used the intel driver several times and rebooted the x server and it worked fine, so i would get the driver from intel and compile it on your system. HINT: since you cant unload the module, you will probaly have to download the driver package from intel, then reboot the computer and dont start up x when it come back up. then run the installer. the installer is as simple as:

tar zxvf I915-whatever.tar.gz
cd dripkg
su
password
sh install.sh

then just follow the instructions, and you might want to remove the driver file that you downloaded so that there is no interference. let us know waht happens.