Skip to contentSkip to conversation

Two agpgart probes at boot.

DISCUSSION Nick Warne 2 participants 4 messages Jun 17, 2005 – Nov 16, 2005

lore
Share & tools
lore

Nick Warne

author
#0 lore raw

Hi all,

Can anybody point me in the direction of why I get 'what appears' to be two agpgart probes on boot (2.6.11.12 on updated Slack 10):

Jun 17 18:40:27 linuxamd kernel: agpgart: Found an AGP 2.0 compliant device at 
0000:00:00.0.
Jun 17 18:40:27 linuxamd kernel: agpgart: Putting AGP V2 device at 
0000:00:00.0 into 4x mode
Jun 17 18:40:27 linuxamd kernel: agpgart: Putting AGP V2 device at 
0000:01:00.0 into 4x mode
Jun 17 18:40:27 linuxamd kernel: agpgart: Found an AGP 2.0 compliant device at 
0000:00:00.0.
Jun 17 18:40:27 linuxamd kernel: agpgart: Putting AGP V2 device at 
0000:00:00.0 into 4x mode
Jun 17 18:40:27 linuxamd kernel: agpgart: Putting AGP V2 device at 

0000:01:00.0 into 4x mode

TIA,

Nick

Signature · 2 lines
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."
#1 lore raw
Quoted 11 lines · Nick Warne

Hi all,

Can anybody point me in the direction of why I get 'what appears' to be two agpgart probes on boot (2.6.11.12 on updated Slack 10):

Jun 17 18:40:27 linuxamd kernel: agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Jun 17 18:40:27 linuxamd kernel: agpgart: Putting AGP V2 device at  0000:00:00.0 into 4x mode
Jun 17 18:40:27 linuxamd kernel: agpgart: Putting AGP V2 device at  0000:01:00.0 into 4x mode
Jun 17 18:40:27 linuxamd kernel: agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Jun 17 18:40:27 linuxamd kernel: agpgart: Putting AGP V2 device at  0000:00:00.0 into 4x mode
Jun 17 18:40:27 linuxamd kernel: agpgart: Putting AGP V2 device at  0000:01:00.0 into 4x mode

These messages aren't probing messages per se. They happen when something (typically X) opens /dev/agpgart and sets up dri. It'll get logged every time that X gets restarted. That there are two of them with the same datestamp is odd though. For some reason your X did this twice.

Dave

author
#2 lore raw
Quoted 4 lines · Dave Jones

These messages aren't probing messages per se. They happen when something (typically X) opens /dev/agpgart and sets up dri. It'll get logged every time that X gets restarted. That there are two of them with the same datestamp is odd though. For some reason your X did this twice.

Ok, thanks for the info on what is going on. I have just spent a few minutes looking at all the logs and configs, but can see nothing untoward.

I don't load the DRI module in xorg.conf, btw.

It doesn't harm anything, so I will stumble on the reason why one day when doing something else, I expect. It maybe a nVidia thing...

Nick

Signature · 2 lines
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."
author
#3 lore raw
Quoted 6 lines · Nick Warne
Quoted 4 lines · Dave Jones

These messages aren't probing messages per se. They happen when something (typically X) opens /dev/agpgart and sets up dri. It'll get logged every time that X gets restarted. That there are two of them with the same datestamp is odd though. For some reason your X did this twice.

Quoted 7 lines

Ok, thanks for the info on what is going on. I have just spent a few minutes looking at all the logs and configs, but can see nothing untoward.

I don't load the DRI module in xorg.conf, btw.

It doesn't harm anything, so I will stumble on the reason why one day when doing something else, I expect. It maybe a nVidia thing...

Well, after all this time, it is a nVidia thing:

http://www.nvnews.net/vbulletin/showthread.php?t=59748

Hopefully google bot will index this and anybody else will find the answer.

Give nVidia their binary due though - at least they have bods on the forum to answer.

Nick

Signature · 4 lines
http://sourceforge.net/projects/quake2plus/

"Person who say it cannot be done should not interrupt person doing it."
-Chinese Proverb