Go Back   nV News Forums > Linux Support Forums > NVIDIA Linux

Newegg Daily Deals

Reply
 
Thread Tools
Old 06-25-04, 10:08 PM   #1
Methradon
Registered User
 
Join Date: Jun 2004
Posts: 8
Arrow Strange lspci result. Kernel bug or bad hardware?

I have a LeadTek A250 LE TD and lcpci -v gives strange results...

Code:
0000:01:00.0 VGA compatible controller: nVidia Corporation NV25 [GeForce4 Ti 4200] (rev a3) (prog-if 00 [VGA])
        Subsystem: LeadTek Research Inc.: Unknown device 2897
        Flags: bus master, 66MHz, medium devsel, latency 248, IRQ 11
        Memory at d6000000 (32-bit, non-prefetchable) [size=d77e0000]
        Memory at d8000000 (32-bit, prefetchable) [size=128M]
        Memory at d7800000 (32-bit, prefetchable) [size=512K]
        Expansion ROM at 00020000 [disabled]
        Capabilities: [60] Power Management version 2
        Capabilities: [44] AGP version 2.0
It's a 64M card and 128M are reported... Isn't strange??

Also, insn't d77e0000 a strange number for a memory size?

At least the NVIDIA driver report the correct memory amount (/var/log/XFree86.0.log)

Code:
(--) NVIDIA(0): Linear framebuffer at 0xD8000000
(--) NVIDIA(0): MMIO registers at 0xD6000000
(II) NVIDIA(0): NVIDIA GPU detected as: GeForce4 Ti 4200
(--) NVIDIA(0): VideoBIOS: 04.25.00.30.00
(--) NVIDIA(0): VideoRAM: 65536 kBytes
Reason for asking : still looking to debug this problem.

Found something else in the log :

Code:
(--) PCI:*(1:0:0) nVidia Corporation NV25 [GeForce4 Ti 4200] rev 163, Mem @ 0xd6000000/24, 0xd8000000/27, 0xd7800000/19, BIOS @ 0xd77e0000/17
And in lspci -v :

Code:
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP] (prog-if 00 [Normal decode])
        Flags: bus master, 66MHz, medium devsel, latency 0
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
        Memory behind bridge: d6000000-d75fffff
        Prefetchable memory behind bridge: d7700000-e5ffffff
        Capabilities: [80] Power Management version 2
So, 0xd6000000 corresponds to my AGP memory and the "size" of 0xd77e0000 maps to the BIOS...?

Last edited by Methradon; 06-25-04 at 11:30 PM. Reason: Added info about XFree86.0.log
Methradon is offline   Reply With Quote
Old 06-27-04, 09:56 PM   #2
Methradon
Registered User
 
Join Date: Jun 2004
Posts: 8
Default Re: Strange lspci result. Kernel bug or bad hardware?

Let's add to the strangeness of the situation. According to some research on the Internet, the value of what is in bold below should be 16M and not some strange BIOS address...

Code:
0000:01:00.0 VGA compatible controller: nVidia Corporation NV25 [GeForce4 Ti 4200] (rev a3) (prog-if 00 [VGA])
        Subsystem: LeadTek Research Inc.: Unknown device 2897
        Flags: bus master, 66MHz, medium devsel, latency 248, IRQ 11
        Memory at d6000000 (32-bit, non-prefetchable) [size=d77e0000]
        Memory at d8000000 (32-bit, prefetchable) [size=128M]
        Memory at d7800000 (32-bit, prefetchable) [size=512K]
        Expansion ROM at 00020000 [disabled]
        Capabilities: [60] Power Management version 2
        Capabilities: [44] AGP version 2.0
I hope this info might help my cause...
Methradon is offline   Reply With Quote
Old 06-28-04, 01:03 AM   #3
LordMorgul
Electrical Engineer
 
LordMorgul's Avatar
 
Join Date: Dec 2002
Location: San Luis Obispo, CA
Posts: 872
Default Re: Strange lspci result. Kernel bug or bad hardware?

Quote:
Originally Posted by Methradon
Let's add to the strangeness of the situation. According to some research on the Internet, the value of what is in bold below should be 16M and not some strange BIOS address...

Memory at d6000000 (32-bit, non-prefetchable) [size=d77e0000]
Compare to my card:
Code:
01:00.0 VGA compatible controller: nVidia Corporation NV25 [GeForce4 Ti 4400] (rev a2) (prog-if 00 [VGA])
        Subsystem: VISIONTEK: Unknown device 003c
        Flags: bus master, VGA palette snoop, 66Mhz, medium devsel, latency 248, IRQ 16
        Memory at fc000000 (32-bit, non-prefetchable) [size=80000000]
        Memory at f0000000 (32-bit, prefetchable) [size=128M]
        Memory at eff80000 (32-bit, prefetchable) [size=512K]
        Expansion ROM at 00020000 [disabled]
        Capabilities: [60] Power Management version 2
        Capabilities: [44] AGP version 2.0
And the value is perhaps strange but it appears to be the correct expected format.

Quote:
(II) NVIDIA(0): NVIDIA GPU detected as: GeForce4 Ti 4200
(--) NVIDIA(0): VideoBIOS: 04.25.00.30.00
(--) NVIDIA(0): VideoRAM: 65536 kBytes
Is your X config specifying the VideoRAM size? It is my understanding that the option to specify the ram size is obselete and now ignored.. but that may not be strictly true. Make sure your config is not limiting the ram size by specifying it directly.

Quote:
(--) PCI:*(1:0:0) nVidia Corporation NV25 [GeForce4 Ti 4200] rev 163, Mem @ 0xd6000000/24, 0xd8000000/27, 0xd7800000/19, BIOS @ 0xd77e0000/17
The PCI leading this log line indicates that the card is being registered as a PCI card and not as AGP at all.. was this log created while attempting to use AGP? Was AGP disabled in the motherboard or in the driver? Are you certain the motherboard has AGP enabled? (yes.. I'm sorry but the basic question needs to be asked)

This is your card? http://www.leadtek.com.tw/3d_graphic...myvivo_2.shtml
It comes in both 64Mb and 128Mb configurations, there is the possibility what you have isn't what you thought you bought or what you paid for.
__________________
"..the triumph of evil is for good men to do nothing." (Edmond Burke)
nVIDIA video driver RPMs for Fedora :: see yum repo at livna.org.
LordMorgul is offline   Reply With Quote
Old 06-28-04, 01:08 AM   #4
Thunderbird
 
Join Date: Jul 2002
Location: Netherlands, Europe
Posts: 2,105
Default Re: Strange lspci result. Kernel bug or bad hardware?

First various of the memory addresses you see there are not really pointing to physical memory. That d6000000 for example is memory mapped io. In short lots of registers of the videocard are mapped to that memory range so it is easy for the driver to get access to the card.

Further the AGP bus is a special implementation of the PCI bus, so the pci stuff you see is normal. (programming wise there's no difference between pci and agp)

Last edited by Thunderbird; 06-28-04 at 03:43 PM.
Thunderbird is offline   Reply With Quote
Old 06-28-04, 02:42 PM   #5
Willis
Registered User
 
Join Date: Jun 2004
Posts: 11
Default Re: Strange lspci result. Kernel bug or bad hardware?

can we get a "cat /proc/mtrr"
just for good measure
__________________
user #276351
http://counter.li.org
Willis is offline   Reply With Quote
Old 06-28-04, 11:50 PM   #6
Methradon
Registered User
 
Join Date: Jun 2004
Posts: 8
Default Re: Strange lspci result. Kernel bug or bad hardware?

Quote:
Originally Posted by LordMorgul
Is your X config specifying the VideoRAM size?
Nope. That could have certainly explained the difference between the 64M that XFree sees and the 128M that lspci sees, but my config does not contain the VideoRAM option.

Quote:
Originally Posted by LordMorgul
The PCI leading this log line indicates that the card is being registered as a PCI card and not as AGP at all.. was this log created while attempting to use AGP? Was AGP disabled in the motherboard or in the driver? Are you certain the motherboard has AGP enabled? (yes.. I'm sorry but the basic question needs to be asked)
I was not running in AGP mode, because it does not work :-)

I posted all logs I could in the "Display problem : AGP image is distorted, but PCI is fine" thread, and in this thread the logs posted are when I was running in AGP mode.

Quote:
Originally Posted by LordMorgul
This is your card? http://www.leadtek.com.tw/3d_graphic...myvivo_2.shtml
It comes in both 64Mb and 128Mb configurations, there is the possibility what you have isn't what you thought you bought or what you paid for.
Yes, it's my card.

I think I will try to install the drivers under Windows, to see if AGP works and what amout of memory is reported.
Methradon is offline   Reply With Quote
Old 06-28-04, 11:50 PM   #7
Methradon
Registered User
 
Join Date: Jun 2004
Posts: 8
Default Re: Strange lspci result. Kernel bug or bad hardware?

Quote:
Originally Posted by Willis
can we get a "cat /proc/mtrr"
just for good measure
Here it is :

Code:
/proc/mtrr

reg00: base=0x00000000 (   0MB), size= 256MB: write-back, count=1
reg01: base=0xd8000000 (3456MB), size= 128MB: write-combining, count=1
reg02: base=0xe6000000 (3680MB), size=  32MB: write-combining, count=1
Other very usefull info here.
Methradon is offline   Reply With Quote
Reply


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


Similar Threads
Thread Thread Starter Forum Replies Last Post
Random crashes, NVRM Xid messages Iesos NVIDIA Linux 90 10-04-12 03:27 AM
Corrupted display - 302.17 - Dell Precision T3500 (G98 [Quadro NVS 295]) gbailey NVIDIA Linux 1 06-27-12 10:24 AM
UEFI+Nvidia - NVRM: Your system is not currently configured to drive a VGA console... interzoneuk NVIDIA Linux 0 06-26-12 04:51 AM
xorg locks-up with newest nvidia drivers w/ vdpau. theroot NVIDIA Linux 1 06-24-12 11:04 AM
Crash when logout from X TGL NVIDIA Linux 10 09-13-02 08:22 PM

All times are GMT -5. The time now is 11:26 PM.


Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.