Nforce2

Nforce2

[Markus Hästbacka]

[-- Attachment #1: Type: text/plain, Size: 389 bytes --]

Still problems with nvidia-agp on 2.6.0-test5(-mm1). I can't track down
the problem because my box needs a hard reboot. My card is nvidia. So
they should work together. On 2.4.23-pre3, there's no problem anymore.
Works fine, but why not in 2.6.0-test5? Any ideas why it crashes? Any
fix? If you need me to investigate more. Tell me how.
-- 
----
Markus Hästbacka <midian@ihme.org>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: Nforce2

[Alistair J Strachan]

On Tuesday 09 September 2003 14:34, Markus Hästbacka wrote:
> Still problems with nvidia-agp on 2.6.0-test5(-mm1). I can't track down
> the problem because my box needs a hard reboot. My card is nvidia. So
> they should work together. On 2.4.23-pre3, there's no problem anymore.
> Works fine, but why not in 2.6.0-test5? Any ideas why it crashes? Any
> fix? If you need me to investigate more. Tell me how.

I get similar crashes with minion.de's patches and the nForce2 AGPGART. I'm in 
the process of tracking it down.

For the moment you can just disable AGPGART in your kernel and use the 
provided NVAGP, Option "NvAGP" "1" in your XF86Config. You will get AGP 8x in 
XFree86, which is probably all you want.

[alistair] 06:00 PM [~] uname -r
2.6.0-test5-mm1

[alistair] 06:00 PM [~] cat /proc/driver/nvidia/version
NVRM version: NVIDIA Linux x86 nvidia.o Kernel Module  1.0-4496  Wed Jul 16 
19:03:09 PDT 2003
GCC version:  gcc version 3.3.1

[alistair] 06:00 PM [~] cat /proc/driver/nvidia/agp/status
Status:          Enabled
Driver:          NVIDIA
AGP Rate:        8x
Fast Writes:     Disabled
SBA:             Disabled

Cheers,
Alistair.

Re: Nforce2

[Markus Hästbacka]

[-- Attachment #1: Type: text/plain, Size: 2396 bytes --]

Hello Alistair,

I've tested everything, I think. It just can't use AGP 4x. I tryed with
NvAGP 1 and 3. Here's the output in /var/log/XFree86.0.log:
[...snip...]
(**) NVIDIA(0): Option "NvAGP" "3"
(**) NVIDIA(0): Use of any AGP requested (try AGPGART, then try NVIDIA's
AGP)
[...snip...]
(WW) NVIDIA(0): Failed to verify AGP usage
[...snip...]
And I just noticed that 2.4 is not telling me the truth. The agp isn't
enbaled there either. I don't know anything to do anymore.
Looks like linux totally lacks support for my Mobo. *sigh*.

midian@midux:~$ uname -r
2.6.0-test5-mm1

NVRM version: NVIDIA Linux x86 nvidia.o Kernel Module  1.0-4496  Wed Jul
16 19:03:09 PDT 2003
GCC version:  gcc version 3.3.2 20030831 (Debian prerelease)

midian@midux:~$ cat /proc/driver/nvidia/agp/status
Status:          Disabled

midian@midux:~$ lspci
00:00.0 Host bridge: nVidia Corporation: Unknown device 01e0 (rev c1)
00:00.1 RAM memory: nVidia Corporation: Unknown device 01eb (rev c1)
00:00.2 RAM memory: nVidia Corporation: Unknown device 01ee (rev c1)
00:00.3 RAM memory: nVidia Corporation: Unknown device 01ed (rev c1)
00:00.4 RAM memory: nVidia Corporation: Unknown device 01ec (rev c1)
00:00.5 RAM memory: nVidia Corporation: Unknown device 01ef (rev c1)
00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a4)
00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2)
00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev
a4)
00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev
a4)
00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev
a4)
00:04.0 Ethernet controller: nVidia Corporation nForce2 Ethernet
Controller (rev a1)
00:08.0 PCI bridge: nVidia Corporation: Unknown device 006c (rev a3)
00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2)
00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev c1)
01:06.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev
07)
01:06.1 Input device controller: Creative Labs SB Live! MIDI/Game Port
(rev 07)
01:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
01:0d.0 FireWire (IEEE 1394): Lucent Microelectronics FW323 (rev 61)
02:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 MX
440] (rev a3)

Thanks.
-- 
----
Markus Hästbacka <midian@ihme.org>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: Nforce2

[Rahul Karnik]

> Still problems with nvidia-agp on 2.6.0-test5(-mm1). I can't track down
> the problem because my box needs a hard reboot.

Did it work in previous 2.5/2.6 kernels? Does it work with the built-in
AGP drivers? (NvAGP=1 I think)

Thanks,
Rahul
--
Rahul Karnik
rahul@genebrew.com
http://www.genebrew.com/

Re: Nforce2

[Markus Hästbacka]

[-- Attachment #1: Type: text/plain, Size: 906 bytes --]

On Tue, 2003-09-09 at 20:10, Rahul Karnik wrote:
> > Still problems with nvidia-agp on 2.6.0-test5(-mm1). I can't track down
> > the problem because my box needs a hard reboot.
> 
> Did it work in previous 2.5/2.6 kernels? Does it work with the built-in
> AGP drivers? (NvAGP=1 I think)
> 
> Thanks,
> Rahul
> --
> Rahul Karnik
> rahul@genebrew.com
> http://www.genebrew.com/
Hello Rahul,
No, it havent worked atleast since -test2, because that's when I bought
the new CPU, board and RAM. I'll try to come up with something. This 2.4
is a bit slow with these things, that's why I want to use 2.6, with old
computer there was a noticeable differnce in speed from 2.4 to 2.6. And
for others, I have the patch for nvidia drivers from minion.de. The card
worked _GREAT_ with my old board, untill test2, when I bought my new
board.

Thanks.
-- 
----
Markus Hästbacka <midian@ihme.org>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: Nforce2

[Jose Luis Alarcon Sanchez]

---- Begin Original Message ----
Still problems with nvidia-agp on 2.6.0-test5(-mm1). I can't track down
the problem because my box needs a hard reboot. My card is nvidia. So
they should work together. On 2.4.23-pre3, there's no problem anymore.
Works fine, but why not in 2.6.0-test5? Any ideas why it crashes? Any
fix? If you need me to investigate more. Tell me how.
-- 
----
Markus Hästbacka <midian@ihme.org>
---- End Original Message ----


  Hi Markus.

  Have you the minion patches in http://www.minion.de/nvidia.html
installed?. It is necesary for the nvidia driver works on 2.6
kernels.

  Regards.

  Jose.


http://linuxespana.scripterz.org

FreeBSD RELEASE 4.8.
Mandrake Linux 9.1 Kernel 2.6.0-test5 XFS.
Registered BSD User 51101.
Registered Linux User #213309.
Memories..... You are talking about memories. 
Rick Deckard. Blade Runner.


Get your Free E-mail at http://chevy.zzn.com
__________________
http://www.zzn.com

nForce2

[Andrew Munday]

Hi..
I have a Shuttle SN41G2 XPC that uses the nForce2 chipset. I have installed 
Redhat Linux 9 and wish to use gKrellm for hardware monitoring, but the 
lm_sensors that comes bundled with Redhat 9 won't detect any of the sensors 
on my motherboard. I have read on your site that CVS version 2.8.0 has 
support for the nForce2 motherboards but all that is written in the 
changelog is:

Module i2c-nforce2: New

Does this mean it is still in development or it is a stable working version?
I look forward to your reply as I really wish to monitor my cpu temps in my 
new system.

Thank you.
Regards,
Andrew Munday
munday@globaldial.com

_________________________________________________________________
Hotmail is now available on Australian mobile phones. Go to  
http://ninemsn.com.au/mobilecentral/signup.asp

nForce2

[Jean Delvare]

> Hmm, seems like a lot of playing around.
> Could you tell me how I would go about detecting the sensors, just to 
> monitor them with an app like gkrellm? It is really that hard? I have
> a bit of experience with linux so I know how not to break a system. :)
> BTW, I'm running Redhat 9 (kernel 2.4.20-8) on a Shuttle SN41G2 XPC
> and an AthlonXP 2600+ 333FSB.

Gkrellm, just like any other monitoring app, makes use of libsensors,
which is part of our lm_sensors package, itself relying on our i2c
packages. These are dependencies you can't ignore, and versions of each
from your current Red Hat installation are not compatible with the new
(our) ones. This is why I said you would have to reinstall everything
from sources - if you really want to do it.

So here's the deal. Either you wait for us to release version 2.8.0 of
our packages (within a month if everything goes OK) and you then wait
for Red Hat to package it, or you are impatient and want it to work
right now. In the second case, you'll need to remove existing packages
and then install from sources. We'll help you doing so if that is what
you want, but only you know what you want to do.

> PS. If possible, please reply to munday@globaldial.com . Thanks.

Free to you to set a "Reply-To: munday@globaldial.com" header, the same
way I set a "Reply-To: sensors@stimpy.netroedge.com" header on my side.

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/

nForce2

[Jean Delvare]

> I have a Shuttle SN41G2 XPC that uses the nForce2 chipset. I have
> installed Redhat Linux 9 and wish to use gKrellm for hardware
> monitoring, but the lm_sensors that comes bundled with Redhat 9 won't
> detect any of the sensors on my motherboard. I have read on your site
> that CVS version 2.8.0 has support for the nForce2 motherboards but
> all that is written in the changelog is:
> 
> Module i2c-nforce2: New
> 
> Does this mean it is still in development or it is a stable working
> version? I look forward to your reply as I really wish to monitor my
> cpu temps in my new system.

The driver really exist, but hasn't been extensively tested. We had both
positive and negative (to say the less) feedback, so feel free to give
it a try, but expect your mileage to vary.

You'll probably have difficulties too, because Gkrellm depends
(package-wise) from lm_sensors which itself could depend form i2c
(unless Red Hat integrated it into the kernel). If you install
lm_sensors from CVS, you'll need i2c from CVS too (tag lk2-4) (which in
turn may conflict with your kernel if i2c was built-in). And the new
library isn't compatible with the old one, so the Gkrellm package won't
work. All this mean that if you want to try CVS, you'll have to remove
all your packages that deal with lm sensors in any way, and install
everything from sources.

This would of course be very welcome since we need testers for this new
driver, but a reasonable skill with this kind of stuff is required if
you don't want to break your system down within a hour.

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/

nForce2

[Andrew Munday]

Hmm, seems like a lot of playing around.
Could you tell me how I would go about detecting the sensors, just to 
monitor them with an app like gkrellm? It is really that hard? I have a bit 
of experience with linux so I know how not to break a system. :)
BTW, I'm running Redhat 9 (kernel 2.4.20-8) on a Shuttle SN41G2 XPC and an 
AthlonXP 2600+ 333FSB.

Thank you and much appreciated.
Regards
Andrew

PS. If possible, please reply to munday@globaldial.com . Thanks.


>From: Jean Delvare <khali@linux-fr.org>
>Reply-To: sensors@stimpy.netroedge.com
>To: "Andrew Munday" <illmunday@hotmail.com>
>CC: sensors@Stimpy.netroedge.com
>Subject: Re: nForce2
>Date: Wed, 25 Jun 2003 15:34:54 +0200
>
>
> > I have a Shuttle SN41G2 XPC that uses the nForce2 chipset. I have
> > installed Redhat Linux 9 and wish to use gKrellm for hardware
> > monitoring, but the lm_sensors that comes bundled with Redhat 9 won't
> > detect any of the sensors on my motherboard. I have read on your site
> > that CVS version 2.8.0 has support for the nForce2 motherboards but
> > all that is written in the changelog is:
> >
> > Module i2c-nforce2: New
> >
> > Does this mean it is still in development or it is a stable working
> > version? I look forward to your reply as I really wish to monitor my
> > cpu temps in my new system.
>
>The driver really exist, but hasn't been extensively tested. We had both
>positive and negative (to say the less) feedback, so feel free to give
>it a try, but expect your mileage to vary.
>
>You'll probably have difficulties too, because Gkrellm depends
>(package-wise) from lm_sensors which itself could depend form i2c
>(unless Red Hat integrated it into the kernel). If you install
>lm_sensors from CVS, you'll need i2c from CVS too (tag lk2-4) (which in
>turn may conflict with your kernel if i2c was built-in). And the new
>library isn't compatible with the old one, so the Gkrellm package won't
>work. All this mean that if you want to try CVS, you'll have to remove
>all your packages that deal with lm sensors in any way, and install
>everything from sources.
>
>This would of course be very welcome since we need testers for this new
>driver, but a reasonable skill with this kind of stuff is required if
>you don't want to break your system down within a hour.
>
>--
>Jean Delvare
>http://www.ensicaen.ismra.fr/~delvare/

_________________________________________________________________
Hotmail is now available on Australian mobile phones. Go to  
http://ninemsn.com.au/mobilecentral/signup.asp