Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
radeon 9200
View unanswered posts
View posts from last 24 hours

Goto page 1, 2, 3  Next  
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
timop
n00b
n00b


Joined: 07 Aug 2002
Posts: 59
Location: Finland

PostPosted: Wed Sep 17, 2003 6:37 am    Post subject: radeon 9200 Reply with quote

I found so many radeon topics but didn't found clear answer to my problem.

I have this radeon 9200 128Mb board and ati-driver 3.2.5 in my gentoo.amd Xp2600+, asrock K7S8X motherboard, kernel is vanilla 2.4.22

If I wanna use xfree-drm drivers,
- should I unmerge ati-drivers,
- which opengl-update command I should use (opengl-update ati ...)
- should I use, ChipID 0x514D in XF86Config file?

I did install newest ati-drivers like [HOWTO] ATI Radeon Binary Drivers on Gentoo told, but if I "opengl-update ati" , glxgears runs only ~200 fps and when used "opengl-update xfree" it goes ~1300fps (both with 24bit color depth)

when use opengl-update xfree with glxinfo is direct rendering: Yes and with ati command it's direct rendering: No

my configs and log and other files :

[url]
http://pumo.homelinux.org/files/omat_testit/xfree/
[/url]

I just wan't to get 3d to work ...

adds:
/proc/dri/0/name shows radeon 0xe200
in make.conf I have USE="radeon ..."
And no efect if I put XF86Config UseInternalAGPGAR "yes" or "no"
Back to top
View user's profile Send private message
Wedge_
Advocate
Advocate


Joined: 08 Aug 2002
Posts: 3614
Location: Scotland

PostPosted: Wed Sep 17, 2003 10:02 am    Post subject: Reply with quote

Right. In all of your logfiles, you seem to be using the radeon DRM driver. If you want to use ati-drivers, you should be using the "fglrx" driver, which is commented out in both your configs. "opengl-update ati" won't work with the radeon driver, which is why glxgears was so slow - there wasn't any acceleration. You're also having problems because the radeon DRM module is being loaded before the fglrx module. If you look at the end of your "dmesg" file:
Code:
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: Detected SiS 746 chipset
agpgart: AGP aperture is 64M @ 0xd0000000
[drm] AGP 0.99 aperture @ 0xd0000000 64MB
[drm] Initialized radeon 1.9.0 20020828 on minor 0
[drm] Loading R200 Microcode
[fglrx] Maximum main memory to use for locked dma buffers: 431 MBytes.
[fglrx:firegl_stub_register] *ERROR* Fire GL kernel module has to be loaded prior to any other DRM kernel module!
[fglrx] Maximum main memory to use for locked dma buffers: 431 MBytes.
[fglrx:firegl_stub_register] *ERROR* Fire GL kernel module has to be loaded prior to any other DRM kernel module!
spurious 8259A interrupt: IRQ7.

What those errors mean is that to use the fglrx module, the radeon module must NOT be loaded, or you won't get any acceleration. What you should do is:
- unload the radeon module with "rmmod radeon" (remove it from your modules.autoload if it's in there).
- unmerge xfree-drm if you'd already emerged it
- edit your current XF86Config and make sure the Driver setting is "fglrx".
- remove the ChipID setting, you shouldn't need to use it with the fglrx driver.
- "modprobe fglrx"
- "opengl-update ati"
- start X and check glxinfo/glxgears etc
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ
Back to top
View user's profile Send private message
timop
n00b
n00b


Joined: 07 Aug 2002
Posts: 59
Location: Finland

PostPosted: Wed Sep 17, 2003 5:03 pm    Post subject: Reply with quote

aaaaargh 8O

i did like you said, now black screen when X should be up and it doesn't react to nothing.
I did put fglrx to modules.autoload and even it goes ok at boot.

part of XF86Config-4

Code:

# === ATI device section ===

Section "Device"
    Identifier                          "ATI Graphics Adapter"
    Driver                              "fglrx"
# === disable PnP Monitor  ===
    #Option                              "NoDDC"
# === disable/enable XAA/DRI ===
    Option "no_accel"                   "no"
    Option "no_dri"                     "no"
# === FireGL DDX driver module specific settings ===
# === Screen Management ===
    Option "DesktopSetup"               "0x00000000"
    Option "MonitorLayout"              "AUTO, AUTO"
    Option "IgnoreEDID"                 "off"
    Option "HSync2"                     "unspecified"
    Option "VRefresh2"                  "unspecified"
    Option "ScreenOverlap"              "0"
# === TV-out Management ===
    Option "NoTV"                       "yes"     
    Option "TVStandard"                 "PAL-G"     
    Option "TVHSizeAdj"                 "0"     
    Option "TVVSizeAdj"                 "0"     
    Option "TVHPosAdj"                  "0"     
    Option "TVVPosAdj"                  "0"     
    Option "TVHStartAdj"                "0"     
    Option "TVColorAdj"                 "0"     
    Option "GammaCorrectionI"           "0x00000000"
    Option "GammaCorrectionII"          "0x00000000"
# === OpenGL specific profiles/settings ===
    Option "Capabilities"               "0x00000000"
# === Video Overlay for the Xv extension ===
    Option "VideoOverlay"               "on"
# === OpenGL Overlay ===
# Note: When OpenGL Overlay is enabled, Video Overlay
#       will be disabled automatically
    Option "OpenGLOverlay"              "off"
    Option "CenterMode"                 "off"
# === QBS Support ===
    Option "Stereo"                     "off"
    Option "StereoSyncEnable"           "1"
# === Misc Options ===
    Option "UseFastTLS"                 "0"
    Option "BlockSignalsOnLock"         "on"
    Option "UseInternalAGPGART"         "yes"
    Option "ForceGenericCPU"            "no"
# === FSAA ===
    Option "FSAAScale"                  "1"
    Option "FSAADisableGamma"           "no"
    Option "FSAACustomizeMSPos"         "no"
    Option "FSAAMSPosX0"                "0.000000"
    Option "FSAAMSPosY0"                "0.000000"
    Option "FSAAMSPosX1"                "0.000000"
    Option "FSAAMSPosY1"                "0.000000"
    Option "FSAAMSPosX2"                "0.000000"
    Option "FSAAMSPosY2"                "0.000000"
    Option "FSAAMSPosX3"                "0.000000"
    Option "FSAAMSPosY3"                "0.000000"
    Option "FSAAMSPosX4"                "0.000000"
    Option "FSAAMSPosY4"                "0.000000"
    Option "FSAAMSPosX5"                "0.000000"
    Option "FSAAMSPosY5"                "0.000000"
    BusID "PCI:1:0:0"    # vendor=1002, device=5961
    Screen 0
EndSection
Back to top
View user's profile Send private message
Wedge_
Advocate
Advocate


Joined: 08 Aug 2002
Posts: 3614
Location: Scotland

PostPosted: Wed Sep 17, 2003 5:13 pm    Post subject: Reply with quote

When it goes to the black screen, can you get back to a console with CTRL-ALT-F1 etc? If not, try setting UseInternalAGPGART to "no" (you'll need the kernel AGP module(s) loaded for this to work).
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ
Back to top
View user's profile Send private message
timop
n00b
n00b


Joined: 07 Aug 2002
Posts: 59
Location: Finland

PostPosted: Wed Sep 17, 2003 7:16 pm    Post subject: Reply with quote

no I can't get to console with ctrl+alt+Fanykey
I did set UseInternalAGPGART to "no", no help still black screen.
I have boot option with gentoo sources, and I did edit XF86Config-4 from that way.
should agp module (agpgart) load by adding it to modules.autoload ?
Back to top
View user's profile Send private message
Wedge_
Advocate
Advocate


Joined: 08 Aug 2002
Posts: 3614
Location: Scotland

PostPosted: Wed Sep 17, 2003 7:35 pm    Post subject: Reply with quote

You should have the agpgart module loaded before you try to start X with UseInternalAGPGART set to "no". Can you post your latest dmesg output and logfile?
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ
Back to top
View user's profile Send private message
timop
n00b
n00b


Joined: 07 Aug 2002
Posts: 59
Location: Finland

PostPosted: Wed Sep 17, 2003 8:29 pm    Post subject: Reply with quote

well I only can boot with this kernel by putting radeon driver to XF86Config so I am not sure is it latesta logs and dmesg

http://pumo.homelinux.org/files/omat_testit/xfree2/

I did also try this:
-boot with 2.4.22 kernel ati driver in XF86Config file
-rmmod agpgart
-adding agpgart and fglrx to modules.autoload (agpgart firstplace)
and both are ok at boot.
booted again to 2.4.22 and black screen ...
Back to top
View user's profile Send private message
Wedge_
Advocate
Advocate


Joined: 08 Aug 2002
Posts: 3614
Location: Scotland

PostPosted: Wed Sep 17, 2003 8:51 pm    Post subject: Reply with quote

X copies the existing logfile to /var/log/XFree86.0.log.old when you start it, so if you run it with the fglrx driver, followed by the radeon driver, then /var/log/XFree86.0.log will contain the log messages from the radeon driver, while /var/log/XFree86.0.log.old will contain the log messages from the fglrx driver, so that's the one you should post.

Have you got X set to run automatically on bootup? If you have, do "rc-update del xdm default" to stop it doing this until this is fixed. It makes it easier to troubleshoot.
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ
Back to top
View user's profile Send private message
timop
n00b
n00b


Joined: 07 Aug 2002
Posts: 59
Location: Finland

PostPosted: Wed Sep 17, 2003 9:07 pm    Post subject: Reply with quote

ok, I did rc-update del xdm default
startx starts ok, kdm starts ok but no direct rendering :(

I did put newest files to same overwriting olds in address :

http://pumo.homelinux.org/files/omat_testit/xfree2/
Back to top
View user's profile Send private message
Wedge_
Advocate
Advocate


Joined: 08 Aug 2002
Posts: 3614
Location: Scotland

PostPosted: Thu Sep 18, 2003 8:27 am    Post subject: Reply with quote

Both the logs you posted are using the radeon driver, not fglrx :( Try this:
- Edit XF86Config-4, and set the driver to "fglrx".
Code:
startx

- Exit back to a console
Code:
cp /var/log/XFree86.0.log ~/XFree86.0.log

- Edit XF86Config-4 and set the driver to "radeon"
- Post ~/XFree86.0.log
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ
Back to top
View user's profile Send private message
timop
n00b
n00b


Joined: 07 Aug 2002
Posts: 59
Location: Finland

PostPosted: Thu Sep 18, 2003 5:31 pm    Post subject: Reply with quote

here it is:
http://pumo.homelinux.org/files/omat_testit/xfree3/XFree86.0.log.startx

I didn't set driver radeon and started kdm and it works only without direct rendering and ~200fps glxgears.
I don't understand why it works this way, but no with xdm/kdm in "automatic mode"

should start from beginning, unmerging all and merging all again ?

what fbconfig means ?
bash-2.05b$ fgl_glxgears
Error: couldn't get fbconfig
Back to top
View user's profile Send private message
Wedge_
Advocate
Advocate


Joined: 08 Aug 2002
Posts: 3614
Location: Scotland

PostPosted: Thu Sep 18, 2003 6:19 pm    Post subject: Reply with quote

timop wrote:
here it is:
http://pumo.homelinux.org/files/omat_testit/xfree3/XFree86.0.log.startx

I didn't set driver radeon and started kdm and it works only without direct rendering and ~200fps glxgears.

The log is still using the radeon driver :P:
Code:
(II) RADEON(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
(II) RADEON(0): PCI bus 1 card 0 func 0
(**) RADEON(0): Depth 24, (--) framebuffer bpp 32
(II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
(==) RADEON(0): Default visual is TrueColor
(**) RADEON(0): Option "AGPFastWrite" "True"
(**) RADEON(0): Option "MonitorLayout" "AUTO, AUTO"
(**) RADEON(0): Option "IgnoreEDID" "off"

Edit XF86Config-4, and check that there is only one "Driver" line, and that it says Driver "fglrx". Then do startx, and exit back to a console. Do "grep fglrx /var/log/XFree86.0.log", and if you get lots of lines back, then that's the logfile you should post. Another way to check is just to look at the messages in the file. For the radeon driver, a lot of lines will start with something like "(II) RADEON(0):". With the fglrx driver, it'll be "(II) fglrx(0):" instead, so a quick search of the file in an editor should indicate which driver is being used.
timop wrote:
should start from beginning, unmerging all and merging all again ?

Not yet, if you can post the logfile from when you try to use fglrx it should give a better idea of what's wrong.

timop wrote:
what fbconfig means ?
bash-2.05b$ fgl_glxgears
Error: couldn't get fbconfig

fgl_glxgears will only work with ATI's OpenGL libraries AFAIK. When the drivers are installed and working properly, you can usually fix that error with "opengl-update ati", but since you're using the radeon driver it won't work at all.
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ
Back to top
View user's profile Send private message
timop
n00b
n00b


Joined: 07 Aug 2002
Posts: 59
Location: Finland

PostPosted: Thu Sep 18, 2003 7:36 pm    Post subject: Reply with quote

I did remove hole line
# Driver "radeon" from XF86Config-4 file and even that it uses radeon !!
no fglrx lines in log file...
I did ran opengl-update ati after editing file.
should I remove xfont server at boot?

files again :
http://pumo.homelinux.org/files/omat_testit/xfree3/

I did search other XF86Config-4 files but bad success, could there be any "hidden" settings which forces it to radeon ?

I have now in my gentoo:
xfree-4.3.0-r2
ati-drivers-3.2.5 (should I downgrade ?)
opengl-update-1.5
Back to top
View user's profile Send private message
Wedge_
Advocate
Advocate


Joined: 08 Aug 2002
Posts: 3614
Location: Scotland

PostPosted: Thu Sep 18, 2003 8:14 pm    Post subject: Reply with quote

In your logfile, near the start, there should always be a line which tells you the name of the config file X is using. In the log you posted, it's using "/root/XF86Config". The fglrxconfig program uses "/etc/X11/XF86Config-4" by default, so you've maybe edited the wrong file. To check which file X is currently using, do
Code:
grep "Using config" /var/log/XFree86.0.log
and you should see the line with the name of the file. Only make changes to the named file or they won't have any effect. If you've got several configs, delete the ones you don't need so you only have one or two, it won't be as easy to get confused.
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ
Back to top
View user's profile Send private message
timop
n00b
n00b


Joined: 07 Aug 2002
Posts: 59
Location: Finland

PostPosted: Fri Sep 19, 2003 5:23 am    Post subject: Reply with quote

ups !
yes there is XF86Config file in /root directory, I did put older versions safe there.
but how X uses that file?? shouldn't it use always from /etc/X11/ ?
but I will move XF* files from root directory to somewhere else.

I've been so blind... :oops:

I will test today evening.
Back to top
View user's profile Send private message
Wedge_
Advocate
Advocate


Joined: 08 Aug 2002
Posts: 3614
Location: Scotland

PostPosted: Fri Sep 19, 2003 11:03 am    Post subject: Reply with quote

X will search several directories for config files, and just uses the first one it finds. I don't know exactly which directories it searches, but /root is obviously one of them. You can always work out which one it used by looking at the log like I said. If you make a directory called config_backups somewhere and put all the older configs in there, it should keep them out of the way.
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ
Back to top
View user's profile Send private message
timop
n00b
n00b


Joined: 07 Aug 2002
Posts: 59
Location: Finland

PostPosted: Fri Sep 19, 2003 2:24 pm    Post subject: Reply with quote

ok, now it uses right XF86Config file, But no log file generated when screen goes black !!!

but when I changed color from 24 to 16 bit this log file did appear
http://pumo.homelinux.org/files/omat_testit/xfree4/XFree86.0.log


and my config
http://pumo.homelinux.org/files/omat_testit/xfree4/XF86Config
and dmesg
http://pumo.homelinux.org/files/omat_testit/xfree4/dmesg

I did opengl-update ati before startx command.
Back to top
View user's profile Send private message
Wedge_
Advocate
Advocate


Joined: 08 Aug 2002
Posts: 3614
Location: Scotland

PostPosted: Fri Sep 19, 2003 2:47 pm    Post subject: Reply with quote

The driver currrently will not work in 16 bit mode at all. Try changing this section of your config
Code:
Section "Screen"
    Identifier  "Screen0"
    Device      "ATI Graphics Adapter"
    Monitor     "Monitor0"
    DefaultDepth 16
    #Option "backingstore"

    Subsection "Display"
        Depth       16
        Modes       "1280x1024" "1024x768" "800x600"
        ViewPort    0 0  # initial origin if mode is smaller than desktop
#        Virtual     1280 1024
    EndSubsection
EndSection
to
Code:
Section "Screen"
    Identifier  "Screen0"
    Device      "ATI Graphics Adapter"
    Monitor     "Monitor0"
    DefaultDepth 24
    #Option "backingstore"

    Subsection "Display"
        Depth       24
        Modes       "1280x1024" "1024x768" "800x600"
        ViewPort    0 0  # initial origin if mode is smaller than desktop
#        Virtual     1280 1024
    EndSubsection
EndSection


Then try startx again. If it hangs at a black screen, it should still produce a logfile in the usual place.
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ
Back to top
View user's profile Send private message
timop
n00b
n00b


Joined: 07 Aug 2002
Posts: 59
Location: Finland

PostPosted: Fri Sep 19, 2003 3:28 pm    Post subject: Reply with quote

this is just what I did only opposite way.
1. moved XF86Configs from /root to otherplace
2. checked /etc/X11/XF86Config that it's ok
3. opengl-update ati
4. startx --> black screen no response from any key, only power button --> boot
5. after boot no log file /var/log/XF....log or old (i did remove older log files)
6. edited to 16 bit colors no start -> generates that logfile
Back to top
View user's profile Send private message
Wedge_
Advocate
Advocate


Joined: 08 Aug 2002
Posts: 3614
Location: Scotland

PostPosted: Fri Sep 19, 2003 4:55 pm    Post subject: Reply with quote

What happens if you set "UseInternalAGPGART" back to "yes"?
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ
Back to top
View user's profile Send private message
timop
n00b
n00b


Joined: 07 Aug 2002
Posts: 59
Location: Finland

PostPosted: Fri Sep 19, 2003 5:25 pm    Post subject: Reply with quote

:D same "flashed" to my mind and I allready tested it
and here is log file
http://pumo.homelinux.org/files/omat_testit/xfree4/XFree86.0.log
Back to top
View user's profile Send private message
timop
n00b
n00b


Joined: 07 Aug 2002
Posts: 59
Location: Finland

PostPosted: Fri Sep 19, 2003 8:44 pm    Post subject: Reply with quote

I did mean no it doesn't work, black screen and halt only log file generated.

could this be causing black screen?
Code:
 
(WW) fglrx: No matching Device section for instance (BusID PCI:1:0:1) found
Back to top
View user's profile Send private message
Wedge_
Advocate
Advocate


Joined: 08 Aug 2002
Posts: 3614
Location: Scotland

PostPosted: Fri Sep 19, 2003 8:47 pm    Post subject: Reply with quote

So this is what happens:
- UseInternalAGPGART="no" -> black screen + no log at all
- UseInternalAGPGART="yes" -> black screen + a weird logfile
Right?

I don't know why the log stops where it does, or why the AGP setting would even make a difference. It doesn't even start to set up AGP until later, so it shouldn't have any effect :?: Try setting "no_dri" to "yes", just to see if it'll start that way (you won't get any 3D accel). Also try uncommenting the line #Option "NoDDC" in the config file, it seems to be the DDC section that the log stops at.
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ
Back to top
View user's profile Send private message
Wedge_
Advocate
Advocate


Joined: 08 Aug 2002
Posts: 3614
Location: Scotland

PostPosted: Fri Sep 19, 2003 8:51 pm    Post subject: Reply with quote

timop wrote:
could this be causing black screen?
Code:
(WW) fglrx: No matching Device section for instance (BusID PCI:1:0:1) found

Nope, that's just a warning, you can ignore it.
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ
Back to top
View user's profile Send private message
timop
n00b
n00b


Joined: 07 Aug 2002
Posts: 59
Location: Finland

PostPosted: Fri Sep 19, 2003 9:22 pm    Post subject: Reply with quote

Wedge_ wrote:
So this is what happens:
- UseInternalAGPGART="no" -> black screen + no log at all
- UseInternalAGPGART="yes" -> black screen + a weird logfile
Right?

correct

Wedge_ wrote:

I don't know why the log stops where it does, or why the AGP setting would even make a difference. It doesn't even start to set up AGP until later, so it shouldn't have any effect :?: Try setting "no_dri" to "yes", just to see if it'll start that way (you won't get any 3D accel). Also try uncommenting the line #Option "NoDDC" in the config file, it seems to be the DDC section that the log stops at.


tested both.
setting nodri "yes" startx works, glxinfo DR no, glxgears:
Xlib:extension "XFree86-DRI" missing on display ":0.0.". and gears still rolls, ~300fps


update:
I did set Option "UseInternalAGPGART" "no"
and leave nodri "yes"
glxinfo -> DR no ->gears 300fps

files
http://pumo.homelinux.org/files/omat_testit/xfree5/

should I try older ati-drivers? emerge ati-drivers offers 2.9.12
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Goto page 1, 2, 3  Next
Page 1 of 3

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum