[mythtv-users] Nvidia problem with atrpms kernel.
Bryan Ware
bryan at hb-computers.com
Tue Jun 1 09:46:04 EDT 2004
I have the rivers and the kernel modules installed, it just won't load.
Here is the error when I try to modprobe nvidia:
[root at myth-be1 etc]# modprobe nvidia
modprobe: Can't locate module nvidia
Bryan
On Tue, 2004-06-01 at 09:11, Cyber Source wrote:
> If you redid your system, you would need to reinstall the nvidia driver
> so it gets loaded into the current kernel
>
> Bryan Ware wrote:
>
> >Ok, I am sorry for the verbose message, but wanted to make sure that I
> >got you all all the information. I had this working before I rebuilt my
> >systems to do a clean install of .15. I now it is something stupid that
> >I am missing so I thought that I would pose the question to the masses.
> >Why am I getting this?
> >
> >XFree86.log:
> >
> >(II) Setting vga for screen 0.
> >(II) Loading sub module "vgahw"
> >(II) LoadModule: "vgahw"
> >(II) Loading /usr/X11R6/lib/modules/libvgahw.a
> >(II) Module vgahw: vendor="The XFree86 Project"
> > compiled for 4.3.0, module version = 0.1.0
> > ABI class: XFree86 Video Driver, version 0.6
> >(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
> >(==) NVIDIA(0): RGB weight 888
> >(==) NVIDIA(0): Default visual is TrueColor
> >(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
> >(**) NVIDIA(0): Option "NvAGP" "1"
> >(**) NVIDIA(0): Option "TVStandard" "NTSC-M"
> >(**) NVIDIA(0): Option "RenderAccel" "1"
> >(**) NVIDIA(0): Option "TVOverScan" "0.7"
> >(**) NVIDIA(0): Enabling experimental RENDER acceleration
> >(**) NVIDIA(0): Use of NVIDIA internal AGP requested
> >(**) NVIDIA(0): TV Standard string: "NTSC-M"
> >(--) NVIDIA(0): Linear framebuffer at 0xD8000000
> >(--) NVIDIA(0): MMIO registers at 0xFD000000
> >(EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module!
> >(EE) NVIDIA(0): *** Aborting ***
> >(II) UnloadModule: "nvidia"
> >(II) UnloadModule: "vgahw"
> >(II) Unloading /usr/X11R6/lib/modules/libvgahw.a
> >(EE) Screen(s) found, but none have a usable configuration.
> >
> >Fatal server error:
> >no screens found
> >
> >If you encounter a server crash, please report the problem by filing a
> >bug
> >report in the XFree86.org bugzilla at http://bugs.xfree86.org and/or Red
> >Hat
> >bugzilla at http://bugzilla.redhat.com/bugzilla. When filing your
> >report, it
> >is very important that you explain your problem in as much detail as
> >possible,
> >and include a complete description on how to reproduce the problem.
> >After
> >submitting the bug report, attach the following files as uncompressed
> >individual file attachments using the bugzilla file attachment feature:
> > - X server log file: /var/log/XFree86.0.log
> > - X server config file: /etc/X11/XF86Config
> > - Kernel log file: /var/log/messages
> >
> >
> >lspci -v output:
> >01:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 MX
> >440] (rev a3) (prog-if 00 [VGA])
> > Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 11
> > Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
> > Memory at d8000000 (32-bit, prefetchable) [size=128M]
> > Memory at e4680000 (32-bit, prefetchable) [size=512K]
> > Expansion ROM at fe9e0000 [disabled] [size=128K]
> > Capabilities: [60] Power Management version 2
> > Capabilities: [44] AGP version 2.0
> >
> >rpm -qa \*nvidia\* output:
> >
> >nvidia-graphics4363-libs-1.0_4363-54.rhfc1.at
> >kernel-module-nvidia-graphics4363-2.4.22-1.2188.nptl-1.0_4363-54.rhfc1.at
> >nvidia-graphics-helpers-0.0.3-3.at
> >nvidia-graphics4363-devel-1.0_4363-54.rhfc1.at
> >nvidia-graphics4363-1.0_4363-54.rhfc1.at
> >
> >XF86Config File contents:
> >
> ># XFree86 4 configuration created by pyxf86config
> >
> >Section "ServerLayout"
> > Identifier "Default Layout"
> > Screen 0 "Screen0" 0 0
> > InputDevice "Mouse0" "CorePointer"
> > InputDevice "Keyboard0" "CoreKeyboard"
> > InputDevice "DevInputMice" "AlwaysCore"
> >EndSection
> >
> >Section "Files"
> >
> ># RgbPath is the location of the RGB database. Note, this is the name
> >of the
> ># file minus the extension (like ".txt" or ".db"). There is normally
> ># no need to change the default.
> ># Multiple FontPath entries are allowed (they are concatenated together)
> ># By default, Red Hat 6.0 and later now use a font server independent of
> ># the X server to render fonts.
> > RgbPath "/usr/X11R6/lib/X11/rgb"
> > ModulePath "/usr/X11R6/lib/modules/extensions/nvidia"
> > ModulePath "/usr/X11R6/lib/modules/extensions"
> > ModulePath "/usr/X11R6/lib/modules"
> > FontPath "unix/:7100"
> >EndSection
> >
> >Section "Module"
> > Load "dbe"
> > Load "extmod"
> > Load "fbdevhw"
> > Load "glx"
> > Load "record"
> > Load "freetype"
> > Load "type1"
> > Load "v4l
> >EndSection
> >
> >Section "InputDevice"
> >
> ># Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
> ># Option "Xleds" "1 2 3"
> ># To disable the XKEYBOARD extension, uncomment XkbDisable.
> ># Option "XkbDisable"
> ># To customise the XKB settings to suit your keyboard, modify the
> ># lines below (which are the defaults). For example, for a non-U.S.
> ># keyboard, you will probably want to use:
> ># Option "XkbModel" "pc102"
> ># If you have a US Microsoft Natural keyboard, you can use:
> ># Option "XkbModel" "microsoft"
> >#
> ># Then to change the language, change the Layout setting.
> ># For example, a german layout can be obtained with:
> ># Option "XkbLayout" "de"
> ># or:
> ># Option "XkbLayout" "de"
> ># Option "XkbVariant" "nodeadkeys"
> >#
> ># If you'd like to switch the positions of your capslock and
> ># control keys, use:
> ># Option "XkbOptions" "ctrl:swapcaps"
> ># Or if you just want both to be control, use:
> ># Option "XkbOptions" "ctrl:nocaps"
> >#
> > Identifier "Keyboard0"
> > Driver "keyboard"
> > Option "XkbRules" "xfree86"
> > Option "XkbModel" "pc105"
> > Option "XkbLayout" "us"
> >EndSection
> >
> >Section "InputDevice"
> > Identifier "Mouse0"
> > Driver "mouse"
> > Option "Protocol" "IMPS/2"
> > Option "Device" "/dev/psaux"
> > Option "ZAxisMapping" "4 5"
> > Option "Emulate3Buttons" "yes"
> >EndSection
> >
> >Section "InputDevice"
> >
> ># If the normal CorePointer mouse is not a USB mouse then
> ># this input device can be used in AlwaysCore mode to let you
> ># also use USB mice at the same time.
> > Identifier "DevInputMice"
> > Driver "mouse"
> > Option "Protocol" "IMPS/2"
> > Option "Device" "/dev/input/mice"
> > Option "ZAxisMapping" "4 5"
> > Option "Emulate3Buttons" "no"
> >EndSection
> >
> >Section "Monitor"
> > Identifier "Monitor0"
> > VendorName "Monitor Vendor"
> > ModelName "27in Analog TV"
> > HorizSync 30.0 - 50.0
> > VertRefresh 60.0 - 60.0
> > Option "dpms"
> >EndSection
> >
> >Section "Device"
> > Identifier "Videocard0"
> > Driver "nvidia"
> > BoardName "nVidia GeForce 4 MX 440"
> > Option "RenderAccel" "1"
> > Option "TVStandard" "NTSC-M"
> > Option "TVOverScan" "0.7"
> > Option "NvAGP" "1"
> >EndSection
> >
> >Section "Screen"
> > Identifier "Screen0"
> > Device "Videocard0"
> > Monitor "Monitor0"
> > DefaultDepth 24
> > SubSection "Display"
> > Depth 24
> > Modes "800x600" "640x480"
> > EndSubSection
> >EndSection
> >
> >Section "DRI"
> > Group 0
> > Mode 0666
> >EndSection
> >
> >
> >Thanks in advanced for your info. I appreciate everyone that helps
> >
> >
> >
> >
> >------------------------------------------------------------------------
> >
> >_______________________________________________
> >mythtv-users mailing list
> >mythtv-users at mythtv.org
> >http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> >
> >
--
Bryan Ware <bryan at hb-computers.com>
More information about the mythtv-users
mailing list