LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices



Reply
 
Search this Thread
Old 12-31-2003, 09:27 PM   #76
Hooper
Member
 
Registered: Dec 2003
Location: FL
Distribution: Slack91-FBSD49
Posts: 80

Rep: Reputation: 15

Hmm. No errors to view. Weird. And your drivers are loading fine from what I see with the above. The excessive 99% CPU usage is out of the ordinary and I'm wondering if there aren't other issues with configuration. Maybe DaOne has some ideas, if it were me, I would first do a dmesg and look for failed attemts to load modules or any other obvious errors. If you have the configuration of some of your drivers loading via the kernel, remove the error giving modules from /etc/rc.d/rc.modules and rerun dmesg. This may well be a process of elimination and there may be other issues. I'm sure you already know all of this but check your memory usage prior to a failed X startup upon boot. Check your /var/log/syslog for errors as well.

Something else you can try, and I'm grasping at straws here, is uninstalling X and trying a reinstall. If your using slack, you may want swaret installed (I like swaret). Do a swaret --update, --upgrade etc... Don't forget swaret --dep to check for dependancies. Do an uninstall of X and then reinstall using swaret. Set your video settings in your conf file to "16Bit" to start off with (not 24bit) and work your way up from there. Your patch job worked it appears. That isn't how I usually do things (uninstalling and reinstalling) but I see no errors reported. Wish there was an error to view.

(II) fglrx(0): Acceleration enabled
(II) fglrx(0): X context handle = 0x00000001
(II) fglrx(0): [DRI] installation complete

Hmmm. That should be doing some fine glxgear numbers.

Last edited by Hooper; 12-31-2003 at 11:18 PM.
 
Old 01-01-2004, 02:56 AM   #77
waever
Member
 
Registered: Oct 2003
Location: Hamilton,ON
Distribution: LFS
Posts: 46

Rep: Reputation: 16
i unloaded almost all modules but it still doesnt work @_@
there was one time I tried, it showed my mouse pointer and I can move it but nothing else come out (cpu usage still 99%) and I cant get there anymore..
I also found an mtrr error (tried both mtrr on and off, still the same error)
"mtrr allocation failed (-22)" I wonder how to fix this one

* mtrr already in kernel
* tried both mtrr on and off in xfree86 config
* the mtrr error is the last line in syslog, but according to dmesg the agp loaded even after the error.

I searched google, haven't find anything useful...
I think keep trying to mess with the config isnt a good idea since everytime the crash happens, I have to hard-restart the computer, and getting something corrupted is not nice -_- Im all out of luck

how troublesome [-_-] I hope ATI make better drivers and support or maybe let me refund the card and get nVidia card if they don't want to support their product...
 
Old 01-01-2004, 09:25 AM   #78
DaOne
Member
 
Registered: Jan 2003
Location: USA
Distribution: Slackware
Posts: 498

Rep: Reputation: 30
I still think this comes down to a MTRR issue, perhaps. I am looking into this further...once I have some fresh ideas, or at least a clue, I'll post back. I wonder if the framebuffer support has anything to do with this? I am thinking...what if we disable framebuffer support for your card...the VESA FB should still be ok though. Just a thought...I'll get back to you.
 
Old 01-01-2004, 11:09 AM   #79
DaOne
Member
 
Registered: Jan 2003
Location: USA
Distribution: Slackware
Posts: 498

Rep: Reputation: 30
Looking back, I think you still have DRI enabled in the kernel...remove it completely...no module, and not in the kernel...re-compile the kernel...but FIRST...

Triple check the following...

1) MTRR is (*)...built in.
2) agpgart is a (M)...module.
3) Your chipset is (M) a module.
4) DRI is ( )...nothing.
5) Framebuffer VESA is (*)...built in.
6) Radeon framebuffer is (M)...a module.

After you re-compile, re-install the ATI drivers (you may or may not need the patch again), run fglrxconfig...use the external agpgart and disable advanced features and user page locking...and reboot. From a console, note the output of lsmod. Try to start x without loading any additional modules. If it starts, again note the output of lsmod. If all agp modules and fglrx are loaded, great. If not, kill x, then only load fglrx. lsmod and see if the agp modules are also loaded. startx and see what happens.
 
Old 01-01-2004, 01:27 PM   #80
Hooper
Member
 
Registered: Dec 2003
Location: FL
Distribution: Slack91-FBSD49
Posts: 80

Rep: Reputation: 15
Quote:
Originally posted by waever

I also found an mtrr error (tried both mtrr on and off, still the same error)
"mtrr allocation failed (-22)" I wonder how to fix this one

* mtrr already in kernel
* tried both mtrr on and off in xfree86 config
* the mtrr error is the last line in syslog, but according to dmesg the agp loaded even after the error.
Ah, I see you found an error. Good. I believe with what you show that DaOne is correct. I don't think the kernel is configured as needed yet for your AMD.

Let's hope after a recompile making sure dri isn't loading that you will advance in this quest.

As far as the statement about a refund on the card and a nvidia replacement. I do understand your feelings. I have a geforce4 setting here as well. Nvidia makes far better strides at the linux drivers and you would have far fewer hassles. But I wouldn't blow your candle out on the ATI card yet either. Although frustrating, if you can get this to work after your numerous hours of prodding at the errors, then document the fixes, I think you'll find your ATI card to be quite nice on linux and you'll be able to do this again if need be in a fraction of the time. Even 2D is better.


Last edited by Hooper; 01-01-2004 at 02:12 PM.
 
Old 01-01-2004, 01:38 PM   #81
rush_pl
LQ Newbie
 
Registered: Jul 2003
Posts: 20

Rep: Reputation: 0
My screen would just go blank when I do startx. Same problem that weaver had. But after I applied the AMD Patch, it fixed the problem. I also had agp and the chipset build into the kernel. The text is little choppy now.

Last edited by rush_pl; 01-01-2004 at 01:40 PM.
 
Old 01-01-2004, 02:12 PM   #82
sarahan
LQ Newbie
 
Registered: Aug 2003
Location: Livermore, CA
Distribution: Ubuntu Dapper, Gentoo, Win2k, WinXP
Posts: 28

Rep: Reputation: 15
I found that disabling the radeon framebuffer helped out a whole lot with any blank screen problems/X hard locking computer. Sounds like Waever's prob is MTRR, but you might check this just in case. It fixed my problems with both slack and gentoo.
 
Old 01-01-2004, 02:17 PM   #83
Hooper
Member
 
Registered: Dec 2003
Location: FL
Distribution: Slack91-FBSD49
Posts: 80

Rep: Reputation: 15
Good tips for the AMD. Hope waever is watching.

Maybe someone might post their relevent (cpu, graphics settings, character devices ) AMD processor kernel configs. This might just help out a bit. Those of us with an Intel aren't having the same issues with the driver.

Last edited by Hooper; 01-01-2004 at 02:22 PM.
 
Old 01-01-2004, 08:19 PM   #84
waever
Member
 
Registered: Oct 2003
Location: Hamilton,ON
Distribution: LFS
Posts: 46

Rep: Reputation: 16
thx.. will try one by one tonight... I will give the result ^^
 
Old 01-02-2004, 03:57 AM   #85
sarahan
LQ Newbie
 
Registered: Aug 2003
Location: Livermore, CA
Distribution: Ubuntu Dapper, Gentoo, Win2k, WinXP
Posts: 28

Rep: Reputation: 15
my XF86config-4 file

Relevant ATI section (as generated by fglrxconfig). I don't think this will help you much, but maybe on some off the wall chance, your file is wacky for some bizarre reason. Next post will be relevant kernel config options.

Code:
# === ATI device section ===

Section "Device"
    Identifier                          "ATI Graphics Adapter"
    Driver                              "fglrx"
# ### generic DRI settings ###
# === disable PnP Monitor  ===
    #Option                              "NoDDC"
# === disable/enable XAA/DRI ===
    Option "no_accel"                   "no"
    Option "no_dri"                     "no"
# === misc DRI settings ===
    Option "mtrr"                       "off" # disable DRI mtrr mapper, driver has its own code for mtrr
# ### 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"                       "no"     
    Option "TVStandard"                 "NTSC-M"     
    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"
# === Center Mode (Laptops only) ===
    Option "CenterMode"                 "off"
# === Pseudo Color Visuals (8-bit visuals) ===
    Option "PseudoColorVisuals"         "off"
# === QBS Management ===
    Option "Stereo"                     "off"
    Option "StereoSyncEnable"           "1"
# === FSAA Management ===
    Option "FSAAEnable"                 "no"
    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"
# === Misc Options ===
    Option "UseFastTLS"                 "1"
    Option "BlockSignalsOnLock"         "on"
    Option "UseInternalAGPGART"         "no"
    Option "ForceGenericCPU"            "no"
    Option "KernelModuleParm"           "agplock=0" # AGP locked user pages: disabled
#    BusID "PCI:3:0:0"    # vendor=1002, device=4e48
    Screen 0
EndSection
 
Old 01-02-2004, 02:33 PM   #86
sarahan
LQ Newbie
 
Registered: Aug 2003
Location: Livermore, CA
Distribution: Ubuntu Dapper, Gentoo, Win2k, WinXP
Posts: 28

Rep: Reputation: 15
Processor Section:

Subarchitecture Type (PC-compatible)--->
Processor family (Athlon/Duron/K7)
[ ] Generic x86 support[*] HPET Timer Support[*] Symmetric multi-processing support
(8) Maximum number of CPUs (2-255)[*] Preemptible Kernel[*] Machine Check Exception[*] Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4[*] check for P4 thermal throttling interrupt.
< > Toshiba Laptop support
< > Dell laptop support
< > /dev/cpu/microcode - Intel IA32 CPU microcode support
< > /dev/cpu/*/msr - Model-specific register support
<*> /dev/cpu/*/cpuid - CPU information support
< > BIOS Enhanced Disk Drive calls determine boot disk (EXPERIMENTAL)
High Memory Support (off) --->
[ ] Math emulation[*] MTRR (Memory Type Range Register) support

Device Drivers Section
Graphics subsection[*] Support for frame buffer devices [*] VESA VGA graphics support
<M> ATI Radeon display support

Character Devices Subsection
<*> /dev/agpgart (AGP Support)
<M> ATI chipset support (I don't think this is necessary, it's probably for ATI's igp, but i left it in anyway) <*> NVIDIA nForce/nForce2 chipset support (change this to your chipset, I've got an nforce 2 board.)

That all seems to me like it's already been said, but now it's been said by an AMD user. I hope it helps. Good luck.

Last edited by sarahan; 01-02-2004 at 02:38 PM.
 
Old 01-03-2004, 02:04 AM   #87
fitz9948
Member
 
Registered: Aug 2003
Posts: 44

Rep: Reputation: 15
I just installed the new ati drivers and am pretty disapointed. First off I had to patch the driver with the amd fix. Now everything loads up but glxgears is reporting less fps, less by around 500-750 less fps. Also I can no longer go into a console. I try going into one and my monitor just reports "out of sync range". I also tried to try the tv out of the driver and have had no luck. What I get on the screen is what appears to be the desktop but the refresh rates must be really screwed up but of there are lines and odd colors going all over the screen. If any of you have had anyluck gettin tv-out to work, please post your XF86Config file.
 
Old 01-03-2004, 08:19 AM   #88
XStorm
Member
 
Registered: Nov 2003
Distribution: Slack 10.0 / 2.6.8.1
Posts: 63

Rep: Reputation: 15
~

I to have just installed fglrx 3.7.0, have patched it, and with :
1) MTRR (*) built in.
2) agpgart (M) module.
3) ATI Radeon Chipset (M) module.
4) DRI ( ) nothing.
5) Framebuffer VESA (*) built in.
6) Radeon framebuffer is (M) a module,
and with fglrx and agpgart loaded,
I have ~200 fps (!?!) in glxgears. flg_glxgears doesn't even work.
I'm running an intel, and a Radeon 9700. In fglrxconfig I have agpgart external (n) and disabled paging.
 
Old 01-03-2004, 08:21 AM   #89
XStorm
Member
 
Registered: Nov 2003
Distribution: Slack 10.0 / 2.6.8.1
Posts: 63

Rep: Reputation: 15
~

I to have just installed fglrx 3.7.0, have patched it, modified the two files as DaOne said ,and with :
1) MTRR (*) built in.
2) agpgart (M) module.
3) ATI Radeon Chipset (M) module.
4) DRI ( ) nothing.
5) Framebuffer VESA (*) built in.
6) Radeon framebuffer is (M) a module,
and with fglrx and agpgart loaded,
I have ~200 fps (!?!) in glxgears. flg_glxgears doesn't even work.
I'm running an intel, and a Radeon 9700. In fglrxconfig I have agpgart external (n) and disabled paging.
 
Old 01-03-2004, 08:22 AM   #90
XStorm
Member
 
Registered: Nov 2003
Distribution: Slack 10.0 / 2.6.8.1
Posts: 63

Rep: Reputation: 15
sorry double post
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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 Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
ATi Radeon 9000 Pro and Radeon(flgrx) driver included on Mandrake 10.1 Official St3althcAt Linux - Hardware 1 05-07-2005 09:30 PM
new radeon driver in 2.6.11 short101 Debian 3 04-06-2005 03:22 AM
can't install newest radeon driver on kernel 2.6.11; what's up with this? schatoor General 9 03-14-2005 04:26 AM
HELP!! Install ATI Mobility RADEON 9000 driver on Debian Kernel 2.4.18-bf2.4?? herbu Linux - Laptop and Netbook 3 11-21-2004 04:37 AM
Radeon 9700 probs/driver downloaded/kernel generator missing NBN Mandriva 18 01-15-2004 03:52 PM


All times are GMT -5. The time now is 08:04 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration