2004-04-02 12:54:11

by Michael Baehr

[permalink] [raw]
Subject: mm-kernels, 4K stacks, and NVIDIA... am I crazy?

I've been seeing posts on LKML, various forums, information sites,
etc. stating that the 4K stacks patch included with the latest mm
series kernels is incompatible with Nvidia's binary drivers. Even my
own friends have told me they were unable to get Nvidia drivers to
work with mm kernels.

However, I've been using pretty much every mm release for the last two
weeks (currently on 2.6.5-rc3-mm3) with the latest Nvidia driver
(5336) and, as far as I can tell, 4K stacks enabled:

06:55:05 <+delysid|~> grep 4K /usr/src/linux/.config
CONFIG_4KSTACKS=y
06:55:08 <+delysid|~>

And I have yet to have a single problem. In fact, everything is
working swimmingly!

So the question is... am I crazy? Is everyone else crazy? Am I
lucky? What is going on?

-- Michael Baehr


2004-04-02 14:22:22

by Norberto Bensa

[permalink] [raw]
Subject: Re: mm-kernels, 4K stacks, and NVIDIA... am I crazy?

Michael Baehr wrote:
> 06:55:05 <+delysid|~> grep 4K /usr/src/linux/.config
> CONFIG_4KSTACKS=y
> 06:55:08 <+delysid|~>
>
> And I have yet to have a single problem. In fact, everything is
> working swimmingly!

Are you sure you are using nvidia's binary driver?

$ dmesg | grep nvidia
$ grep -i nvidia /var/log/XF*

Regards,
Norberto

PS: I'm recompiling my kernel with 4KSTACKS, but I doubt it will work.

2004-04-02 19:07:28

by Michael Baehr

[permalink] [raw]
Subject: Re: mm-kernels, 4K stacks, and NVIDIA... am I crazy?

On 2004-04-02 08:21:46 -0600 Norberto Bensa
<[email protected]> wrote:

> Michael Baehr wrote:
>> 06:55:05 <+delysid|~> grep 4K /usr/src/linux/.config
>> CONFIG_4KSTACKS=y
>> 06:55:08 <+delysid|~>
>>
>> And I have yet to have a single problem. In fact, everything is
>> working swimmingly!
>
> Are you sure you are using nvidia's binary driver?
>
> $ dmesg | grep nvidia
> $ grep -i nvidia /var/log/XF*
>
> Regards,
> Norberto
>
> PS: I'm recompiling my kernel with 4KSTACKS, but I doubt it will work.
>
>

Output of dmesg | grep nvidia:

nvidia: module license 'NVIDIA' taints kernel.
0: nvidia: loading NVIDIA Linux x86 NVIDIA Kernel Module 1.0-5336
Wed Jan 14 18:29:26 PST 2004

Output of grep -i nvidia /var/log/XF* (I snipped some extraneous text
about sync ranges):

(**) | |-->Device "NVIDIA Quadro4 700 XGL"
(--) PCI:*(2:0:0) nVidia Corporation NV25GL [Quadro4 700 XGL] rev 163,
Mem @ 0xdc000000/24, 0xd4000000/26, 0xd8000000/19
(II) Module glx: vendor="NVIDIA Corporation"
(II) LoadModule: "nvidia"
(II) Loading /usr/X11R6/lib/modules/drivers/nvidia_drv.o
(II) Module nvidia: vendor="NVIDIA Corporation"
(II) NVIDIA XFree86 Driver 1.0-5336 Wed Jan 14 18:30:46 PST 2004
(II) NVIDIA Unified Driver for all NVIDIA GPUs
(--) Chipset NVIDIA GPU found
(**) 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 "NoLogo" "True"
(**) NVIDIA(0): Option "NoDDC" "true"
(**) NVIDIA(0): Ignoring EDIDs
(--) NVIDIA(0): Linear framebuffer at 0xD4000000
(--) NVIDIA(0): MMIO registers at 0xDC000000
(II) NVIDIA(0): NVIDIA GPU detected as: Quadro4 700 XGL
(--) NVIDIA(0): VideoBIOS: 04.25.00.25.01
(--) NVIDIA(0): VideoRAM: 65536 kBytes
(II) NVIDIA(0): Connected display device(s): CRT-1
(--) NVIDIA(0): Display device CRT-1: maximum pixel clock at 8 bpp:
350 MHz
(--) NVIDIA(0): Display device CRT-1: maximum pixel clock at 16 bpp:
350 MHz
(--) NVIDIA(0): Display device CRT-1: maximum pixel clock at 32 bpp:
350 MHz
(II) NVIDIA(0): Not probing EDIDs.
(II) NVIDIA(0): Multiscan 420GS: Using hsync range of 30.00-96.00 kHz
(II) NVIDIA(0): Multiscan 420GS: Using vrefresh range of 48.00-120.00
Hz
< lots of snippage due to me not setting up hsync/vsync right in
XF86Config >
(II) NVIDIA(0): Clock range: 12.00 to 350.00 MHz
(II) NVIDIA(0): Virtual screen size determined to be 1600 x 1200
(==) NVIDIA(0): DPI set to (75, 75)
(II) NVIDIA(0): AGP 4X successfully initialized
(II) NVIDIA(0): Setting mode "1600x1200"
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(**) NVIDIA(0): DPMS enabled
(II) XINPUT: Adding extended input device "NVIDIA Event Handler"
(type: Other)

output of uname -a:

Linux Diwanda 2.6.5-rc3-mm3 #1 Thu Apr 1 01:21:12 CST 2004 i686
unknown unknown GNU/Linux

output of grep -i 4K /usr/src/linux-`uname -r`/.config:

CONFIG_4KSTACKS=y

Using XFree 4.4 btw (don't tell RMS :o )

-- Mike

2004-04-07 01:48:22

by Sid Boyce

[permalink] [raw]
Subject: Re: mm-kernels, 4K stacks, and NVIDIA... am I crazy?

Believe it, I inadvertently mangled one disk completely when I forgot
and tried nvidia 5336 with 2.6.5-mm1 after I'd had success with
2.6.5-clo1 and had another one not completing boot up before I knew of
the problem. It would be nice if Andrew made it a config option until
NVidia fixes the problem. There is a patch to change back from 4KSTACKS
in the list recently. The last time, I changed it in .config then did a
make oldconfig which changed it back and BOOM!
Regards
Sid.

On 2004-04-02 08:21:46 -0600 Norberto Bensa
<norberto+linux-kernel@xxxxxxxxxxxx> wrote:

Michael Baehr wrote:

06:55:05 <+delysid|~> grep 4K /usr/src/linux/.config
CONFIG_4KSTACKS=y
06:55:08 <+delysid|~>

And I have yet to have a single problem. In fact, everything is
working swimmingly!


Are you sure you are using nvidia's binary driver?

$ dmesg | grep nvidia
$ grep -i nvidia /var/log/XF*

Regards,
Norberto

PS: I'm recompiling my kernel with 4KSTACKS, but I doubt it will work.