Hi, thanks Maxime, your patch works ok! Well, the nVIDIA driver is
labeled "beta quality" anyway, so, why not upgrade nvidia-driver port to
support 5-CURRENT too? I'm actually using it, with a ugly hack: applying
the patch, compacting and copying the new distfile, editing Makefile to
comment 4.x (
Maxime Henrion wrote:
walt wrote:
My mini 'disaster' of earlier today was caused by the nvidia kernel
module being autoloaded at boot, which causes an immediate kernel panic.
The newest kernel seems fine until I try to load the module manually,
at which time I still get the kernel panic even after
Maxime Henrion wrote:
> walt wrote:
> > My mini 'disaster' of earlier today was caused by the nvidia kernel
> > module being autoloaded at boot, which causes an immediate kernel panic.
> >
> > The newest kernel seems fine until I try to load the module manually,
> > at which time I still get the k
walt wrote:
> My mini 'disaster' of earlier today was caused by the nvidia kernel
> module being autoloaded at boot, which causes an immediate kernel panic.
>
> The newest kernel seems fine until I try to load the module manually,
> at which time I still get the kernel panic even after re-compilin
Andre Guibert de Bruet wrote:
If you really need to use your workstation, you can try the open source nv
XFree86 driver. It's not as fast as the nVidia detonator driver and it's
not accelerated, but you can at least use X11 at a reasonable resolution
and color depth.
It works well enough for my pu
> If you really need to use your workstation, you can try the open source nv
> XFree86 driver. It's not as fast as the nVidia detonator driver and it's
> not accelerated, but you can at least use X11 at a reasonable resolution
> and color depth.
>
> Regards,
If you have a nForce based machine tha
> If you really need to use your workstation, you can try the open source nv
> XFree86 driver. It's not as fast as the nVidia detonator driver and it's
> not accelerated, but you can at least use X11 at a reasonable resolution
> and color depth.
>
> Regards,
With nForce based motherboards, it see
On Mon, 3 Mar 2003, walt wrote:
> My mini 'disaster' of earlier today was caused by the nvidia kernel
> module being autoloaded at boot, which causes an immediate kernel panic.
>
> The newest kernel seems fine until I try to load the module manually,
> at which time I still get the kernel panic e
My mini 'disaster' of earlier today was caused by the nvidia kernel
module being autoloaded at boot, which causes an immediate kernel panic.
The newest kernel seems fine until I try to load the module manually,
at which time I still get the kernel panic even after re-compiling
the module.
Maxime, i
