Yes, please: nvidia taints the kernel - so flame at your will - but
this is a more general question regarding module loading:
If I load the nvidia kernel module like this:
% modprobe nvidia NVreg_Mobile=2 NVreg_SoftEDIDs=0
and start kdm afterwards, it works as in 2.4 -- I get a two screen
setup with one screen on my laptop TFT and one on my external TFT
screen.
If I use this /etc/modules.conf:
... snip ...
### update-modules: start processing /etc/modutils/nvidia-kernel
alias /dev/nvidia* nvidia
alias char-major-195 nvidia
### update-modules: end processing /etc/modutils/nvidia-kernel
### update-modules: start processing /etc/modutils/nvidia-options
options nvidia NVreg_Mobile=2 NVreg_SoftEDIDs=0
### update-modules: end processing /etc/modutils/nvidia-options
... snap ...
the X11 will barf upon start -- but the module will be loaded. From
Xfree.0.log:
...
(II) Loading /usr/X11R6/lib/modules/libvbe.a
(II) Module vbe: vendor="The XFree86 Project"
compiled for 4.2.1.1, module version = 1.0.0
ABI class: XFree86 Video Driver, version 0.5
(II) LoadModule: "nvidia"
(II) Loading /usr/X11R6/lib/modules/drivers/nvidia_drv.o
(II) Module nvidia: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.4363
Module class: XFree86 Video Driver
(II) LoadModule: "mouse"
(II) Loading /usr/X11R6/lib/modules/input/mouse_drv.o
(II) Module mouse: vendor="The XFree86 Project"
compiled for 4.2.1.1, module version = 1.0.0
Module class: XFree86 XInput Driver
ABI class: XFree86 XInput driver, version 0.3
(II) NVIDIA XFree86 Driver 1.0-4363 Sat Apr 19 17:49:42 PDT 2003
(II) NVIDIA Unified Driver for all NVIDIA GPUs
...
(**) NVIDIA(1): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(1): RGB weight 888
(==) NVIDIA(1): Default visual is TrueColor
(==) NVIDIA(1): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(1): Option "ConnectedMonitor" "CRT,DFP"
(**) NVIDIA(1): ConnectedMonitor string: "CRT,DFP"
(--) NVIDIA(1): Linear framebuffer at 0xEC000000
(--) NVIDIA(1): MMIO registers at 0xFD000000
(EE) NVIDIA(1): Failed to initialize the NVIDIA kernel module!
(EE) NVIDIA(1): *** Aborting ***
(II) UnloadModule: "nvidia"
(II) UnloadModule: "vgahw"
(II) UnloadModule: "nvidia"
(II) UnloadModule: "vgahw"
(II) Unloading /usr/X11R6/lib/modules/libvgahw.a
(EE) Screen(s) found, but none have a usable configuration.
--
Ralf Hildebrandt (Im Auftrag des Referat V a) [email protected]
Charite Campus Mitte Tel. +49 (0)30-450 570-155
Referat V a - Kommunikationsnetze - Fax. +49 (0)30-450 570-916
AIM: ralfpostfix
On Friday 18 Jul 2003 16:49, Ralf Hildebrandt wrote:
> Yes, please: nvidia taints the kernel - so flame at your will - but
> this is a more general question regarding module loading:
>
> If I load the nvidia kernel module like this:
>
> % modprobe nvidia NVreg_Mobile=2 NVreg_SoftEDIDs=0
>
> and start kdm afterwards, it works as in 2.4 -- I get a two screen
> setup with one screen on my laptop TFT and one on my external TFT
> screen.
>
> If I use this /etc/modules.conf:
And that's the problem. The new modprobe uses /etc/modprobe.conf rather than
/etc/modules.conf. In Debian you now need to put the component files into
/etc/modprobe.d instead of /etc/modutils. However the syntax appears to be
mostly the same so the configuration files you already have should still
work.
--
Ian.
* Ian Hastie <[email protected]>:
> And that's the problem. The new modprobe uses /etc/modprobe.conf
> rather than /etc/modules.conf. In Debian you now need to put the
> component files into /etc/modprobe.d instead of /etc/modutils.
Thanks for the enlightenment!
> However the syntax appears to be mostly the same so the configuration
> files you already have should still work.
So a cp will do. I'll try that.
--
Ralf Hildebrandt (Im Auftrag des Referat V a) [email protected]
Charite Campus Mitte Tel. +49 (0)30-450 570-155
Referat V a - Kommunikationsnetze - Fax. +49 (0)30-450 570-916
AIM: ralfpostfix
* Ian Hastie <[email protected]> [2003-07-19 12:22:06]:
> And that's the problem. The new modprobe uses /etc/modprobe.conf rather than
> /etc/modules.conf. In Debian you now need to put the component files into
> /etc/modprobe.d instead of /etc/modutils. However the syntax appears to be
> mostly the same so the configuration files you already have should still
> work.
Oh! Thanks for this info. I have had problems figuring out why my
aliases in /etc/modutils/aliases and other stuff didn't work... Now even
ALSA runs perfectly on my system. Thank you very much.
--
Med Venlig Hilsen/Best Regards/Mit freundlichen Gr??en
Michael Kristensen <[email protected]>