Ok, I figured out the create and remove. Silly me!
It's the tty where the graphics is displayed. Everytime I log in and out, the x-server gets restarted. Therefor udev removes and creates it again. Sorry for this.
But where do the agpgart messages keep coming from?


regards,

ilja Siera wrote:

Hi,

When I start X, I run into some trouble with my graphics card. When I select a resolutions that enables me to use direct rendering ( I got a Matrox 200 so I can't go that high) I get the following message

Feb 24 08:47:00 xxxxxxxxxxxx [drm] Initialized mga 3.1.0 20021029 on minor 0: Matrox Graphics, Inc. MGA G200 AGP
Feb 24 08:47:00 xxxxxxxxxxxx agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Feb 24 08:47:00 xxxxxxxxxxxx agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
Feb 24 08:47:00 xxxxxxxxxxxx agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode
Feb 24 08:47:00 xxxxxxxxxxxx udev[2548]: creating device node '/dev/mga'
Feb 24 08:47:26 xxxxxxxxxxxx udev[2600]: removing device node '/dev/vcs7'
Feb 24 08:47:26 xxxxxxxxxxxx udev[2602]: removing device node '/dev/vcsa7'
Feb 24 08:47:27 xxxxxxxxxxxx udev[2640]: creating device node '/dev/vcs7'
Feb 24 08:47:27 xxxxxxxxxxxx udev[2642]: creating device node '/dev/vcsa7'


Then, after a while (not to long actually) I get messeges like this:

Feb 24 11:52:59 xxxxxxxxxxxx udev[2772]: removing device node '/dev/vcs7'
Feb 24 11:52:59 xxxxxxxxxxxx udev[2774]: removing device node '/dev/vcsa7'
Feb 24 11:53:00 xxxxxxxxxxxx udev[2790]: creating device node '/dev/vcs7'
Feb 24 11:53:00 xxxxxxxxxxxx udev[2792]: creating device node '/dev/vcsa7'
Feb 24 11:53:55 xxxxxxxxxxxx udev[2866]: removing device node '/dev/vcs7'
Feb 24 11:53:55 xxxxxxxxxxxx udev[2869]: removing device node '/dev/vcsa7'
Feb 24 11:53:57 xxxxxxxxxxxx udev[2884]: creating device node '/dev/vcs7'
Feb 24 11:53:57 xxxxxxxxxxxx udev[2885]: creating device node '/dev/vcsa7'
Feb 24 11:53:58 xxxxxxxxxxxx udev[2897]: removing device node '/dev/vcs7'
Feb 24 11:53:58 xxxxxxxxxxxx udev[2899]: removing device node '/dev/vcsa7'
Feb 24 11:53:59 xxxxxxxxxxxx udev[2917]: creating device node '/dev/vcsa7'
Feb 24 11:53:59 xxxxxxxxxxxx udev[2916]: creating device node '/dev/vcs7'
Feb 24 11:54:00 xxxxxxxxxxxx udev[2929]: removing device node '/dev/vcs7'
Feb 24 11:54:00 xxxxxxxxxxxx udev[2931]: removing device node '/dev/vcsa7'
Feb 24 11:54:02 xxxxxxxxxxxx udev[2947]: creating device node '/dev/vcs7'
Feb 24 11:54:02 xxxxxxxxxxxx udev[2949]: creating device node '/dev/vcsa7'
Feb 24 11:54:03 xxxxxxxxxxxx udev[2960]: removing device node '/dev/vcs7'
Feb 24 11:54:03 xxxxxxxxxxxx udev[2964]: removing device node '/dev/vcsa7'
Feb 24 11:54:04 xxxxxxxxxxxx udev[2979]: creating device node '/dev/vcs7'
Feb 24 11:54:04 xxxxxxxxxxxx udev[2980]: creating device node '/dev/vcsa7'
Feb 24 11:54:05 xxxxxxxxxxxx udev[2992]: removing device node '/dev/vcs7'
Feb 24 11:54:05 xxxxxxxxxxxx udev[2996]: removing device node '/dev/vcsa7'


and like this:

Feb 24 11:56:57 xxxxxxxxxxxx udev[3189]: creating device node '/dev/vcs7'
Feb 24 11:56:57 xxxxxxxxxxxx udev[3194]: creating device node '/dev/vcsa7'
Feb 24 11:56:57 xxxxxxxxxxxx agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Feb 24 11:56:57 xxxxxxxxxxxx agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
Feb 24 11:56:57 xxxxxxxxxxxx agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode
Feb 24 11:57:24 xxxxxxxxxxxx syslog-ng[2354]: STATS: dropped 0
Feb 24 11:59:57 xxxxxxxxxxxx udev[3357]: removing device node '/dev/vcs7'
Feb 24 11:59:57 xxxxxxxxxxxx udev[3358]: removing device node '/dev/vcsa7'
Feb 24 11:59:58 xxxxxxxxxxxx udev[3375]: creating device node '/dev/vcs7'
Feb 24 11:59:58 xxxxxxxxxxxx udev[3376]: creating device node '/dev/vcsa7'
Feb 24 11:59:58 xxxxxxxxxxxx agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Feb 24 11:59:58 xxxxxxxxxxxx agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
Feb 24 11:59:58 xxxxxxxxxxxx agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode


Looks like the card keeps initialising itself. Does someone what's the reason? Is it a software problem or could it be hardware?
It's got to be related to the drm cause when I put the resolution up and during boot drm get disabled, it disappears.


Regards,

ilja

-- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page

Reply via email to