My glxinfo this morning:

name of display: :0.0
display: :0 screen: 0
direct rendering: No
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating,
GLX_EXT_import_context, GLX_OML_swap_method, GLX_SGI_make_current_read,
GLX_SGIS_multisample, GLX_SGIX_fbconfig
client glx vendor string: ATI
client glx version string: 1.3
client glx extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context,
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_ATI_pixel_format_float,
GLX_ATI_render_texture
GLX extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context,
GLX_ARB_multisample
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.2.1)
OpenGL extensions:
GL_ARB_imaging, GL_ARB_multitexture, GL_ARB_texture_border_clamp,
GL_ARB_texture_cube_map, GL_ARB_texture_env_add,
GL_ARB_texture_env_combine, GL_ARB_texture_env_dot3,
GL_ARB_transpose_matrix, GL_EXT_abgr, GL_EXT_blend_color,
GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_texture_env_add,
GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3,
GL_EXT_texture_lod_bias
glu version: 1.3
glu extensions:
GLU_EXT_nurbs_tessellator, GLU_EXT_object_space_tess

visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav
id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat
----------------------------------------------------------------------
0x23 24 tc 0 24 0 r y . 8 8 8 0 0 16 0 0 0 0 0 1 0 None
0x24 24 tc 0 24 0 r y . 8 8 8 0 0 16 8 16 16 16 0 1 0 None
0x25 24 tc 0 32 0 r y . 8 8 8 8 0 16 8 16 16 16 16 1 0 None
0x26 24 tc 0 32 0 r . . 8 8 8 8 0 16 8 16 16 16 16 1 0 None
0x27 24 dc 0 24 0 r y . 8 8 8 0 0 16 0 0 0 0 0 1 0 None
0x28 24 dc 0 24 0 r y . 8 8 8 0 0 16 8 16 16 16 0 1 0 None
0x29 24 dc 0 32 0 r y . 8 8 8 8 0 16 8 16 16 16 16 1 0 None
0x2a 24 dc 0 32 0 r . . 8 8 8 8 0 16 8 16 16 16 16 1 0 None

dmesg:


agpgart: Detected AGP bridge 0
agpgart: Aperture conflicts with PCI mapping.
agpgart: Aperture from AGP @ f0000000 size 4096 MB
agpgart: Aperture too small (0 MB)
agpgart: No usable aperture found.
agpgart: Consider rebooting with iommu=memaper=2 to get a good aperture.


fglrx: module not supported by Novell, setting U taint flag.
fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERM
ANY' taints kernel.
[fglrx] Maximum main memory to use for locked dma buffers: 366 MBytes.


bgorjup@Bogomir:~> fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.2.1)

gorjup@Bogomir:~> lsmod
Module Size Used by
bluetooth 55620 0
fglrx 289372 0

gorjup@Bogomir:~> dmesg | grep agpgart
agpgart: Detected AGP bridge 0
agpgart: Aperture conflicts with PCI mapping.
agpgart: Aperture from AGP @ f0000000 size 4096 MB
agpgart: Aperture too small (0 MB)
agpgart: No usable aperture found.
agpgart: Consider rebooting with iommu=memaper=2 to get a good aperture.
Linux agpgart interface v0.101 (c) Dave Jones

I run sax2 -r -m....... and I am back again


bgorjup@Bogomir:~> dmesg | grep agpgart
agpgart: Detected AGP bridge 0
agpgart: Setting up Nforce3 AGP.
agpgart: AGP aperture is 512M @ 0xc0000000
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode
agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode
bgorjup@Bogomir:~> glxgears
8320 frames in 5.0 seconds = 1664.000 FPS
10123 frames in 5.0 seconds = 2024.600 FPS

Yes, that's exactly what I'm seeing and it's as far back as I've traced my problem. On your first boot, AGPGART detects that your apeture is 0, but when you run sax2... and reboot it sees that your apeture size is proper @ 512M. It has nothing to do with the ATI drivers, your ATI drivers are good.

Tomorrow, or on your next cold boot, your apeture will be 0, and just try rebooting without your sax command and see if the agp is redetected.

Here are a few more things you might want to try. Remember, a cold boot is power off, a warm boot is any kind of reboot keeping power on.
Scenario 1.
a) Cold boot and check for your AGPGART size (no need to check anything else, it all depends on this)
b) Warm Reboot, without running anything else, and check AGPGART again.
c) If it's still 0 then that is interesting. It rules out power supply/ cold boot hardware problems, it's purly a software problem.
d) if it's not 0, i.e. ok, then all you have to do is boot your computer twice, which is better than my current solution (warm boot to windows, warm reboot back to linux)

e) If c) was 0, then run the sax command and COLD boot and check AGPGART. (I honestly don't know what sax does, I run slack and it doesn't seem to have sax preinstalled)
f) my expectation is that the apeture will again be 0.

My guess is that it's a bug in some aspect of the 2.6.13 kernel with the nForce3 (maybe only the -250 variant) chipset, and is seen in the output of agpgart. I was previously running 2.6.12.5 and everything was ok.

I had read a kernel development message on google groups about an nforce3 and 2.6.13 kernel crash situation, but I can't seem to find it now. My computer does crash, but at the oddest times and I can't predict it - although I feel it's network or OpenGL activity based. i.e. it crashes when downloading and crashes with an OpenGL screen saver - and it crashes hard, reset button at the minimum.

Brian

p.s. some links of crashing, not sure if still relevant.

http://www.ussg.iu.edu/hypermail/lin...08.3/0725.html

http://www.ussg.iu.edu/hypermail/lin...08.3/0725.html

Hi Slim Backwater,

Well, here is my agpgart this morning (cold boot):

bgorjup@Bogomir:~> dmesg | grep agpgart
agpgart: Detected AGP bridge 0
agpgart: Setting up Nforce3 AGP.
agpgart: AGP aperture is 512M @ 0xc0000000
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode
agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode
bgorjup@Bogomir:~>

As I said I am not a game player or someone who needs 3D etc. But because I have ATI card, I would like to know where the problem is and what can be done to avoid it.

Thanks for your answer, I will try and see if I could find a solution. But because I am new to Linux (and a little bit too old too), it will be more difficult for me to find it alone.

Regards


and this is after warm reboot:

bgorjup@Bogomir:~> dmesg | grep agpgart
agpgart: Detected AGP bridge 0
agpgart: Setting up Nforce3 AGP.
agpgart: AGP aperture is 512M @ 0xc0000000
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode
agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode
bgorjup@Bogomir:~>

it is the same.

It is not like this every time. Normally I get Mesa after cold reboot - my computer has to be off for an hour or so. If I restart it immediately, then - normally - there is no change.

I've just installed SUSE 10.0 on my portable (acer aspire 1690). It has a ati radeon X700 driver. During installation everything was looking fine, but after the installation I've got a black screen. What is here the problem? Can I install in some way an other driver without doing a reinstall?

Did you actually try to add iommu=memaper=2 to GRUB boot options at boot?

Thanks to your threat I have become aware of ATI fglrx and installed it last night using the simple auto install.
This was done on SuSE 9.3
Mine is up and running fine. But have a look at YAST/Sax and see if you now have 2 display drivers. I deleted one and leaving me with no issues except for MPlayer but gears runs fine.

sorry to ressurect an old thread, but I found a solution from http://www.ubuntuforums.org/showpost...6&postcount=12 and the solution for us K8N-E Deluxe owners is to downgrade the BIOS to 1006. Just did it myself and it worked.