Bug 133677 - X server crashes in FC3T2
X server crashes in FC3T2
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: xorg-x11 (Show other bugs)
3
i386 Linux
medium Severity high
: ---
: ---
Assigned To: X/OpenGL Maintenance List
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-09-25 23:16 EDT by Debo
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-10-06 14:37:22 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Debo 2004-09-25 23:16:14 EDT
Description of problem:

Installed FC3T2 on a Dell Precision 360. X server crashes frequently.
Installed Nvidia driver 1.0.6111 .... Every time on boot I need to be
root and manually modprobe the nvidia kernel module else X complains
that kernel module not found. 

Config: precision 360, quadro nvs280, 1GB ram, 40gb HDD, intel eth, p4
2.4G

Version-Release number of selected component (if applicable):


How reproducible:

Everytime

Steps to Reproduce:
1. boot
2. login as a non superuser
3. startx
  
Actual results:

X says kernel module not found screens not found

Expected results:

normal Xserver start

Additional info:
Comment 1 Chris Tencati 2004-10-01 06:20:02 EDT
I get this too with nvidia drivers...it seems that nvidia won't setup
the system so kerneld will load the module itself if rivafb is
present.  Apparently rivafb conflicts with nvidia, so if the rivafb
module is present for your kernel (doesn't even need to be loaded),
the nvidia installer won't setup the loading of its own module.  I'm
pretty sure you can just edit the scripts yourself to make sure
kerneld loads it on boot, and it should work then.
Comment 2 Chris Tencati 2004-10-01 10:11:34 EDT
er well, not kerneld per se since it's gone in 2.6 :)  But you should
be able to just add it to /etc/modprobe.conf and have it work.
Comment 3 Søren Sandmann Pedersen 2004-10-06 14:37:22 EDT
As Chris said, you should make sure the module is installed by
/etc/modprobe.conf

Note You need to log in before you can comment on or make changes to this bug.