LinuxQuestions.org
Help answer threads with 0 replies.
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 07-21-2005, 05:50 PM   #1
PSIPHON
Member
 
Registered: Jul 2005
Distribution: SuSe 10.0
Posts: 39

Rep: Reputation: 15
kde freeze


If i can solve this i may know what is wrong with my system.

Once logged into kde on slack 10.1 if i try and crtl + alt + 1-6 etc and then back into 7 in any order the display looks like it corrupts and the system hardlocks. since i am new to this stuff i cant say i know how to assess something like this. Can any one help?

I dont belive this is relevant but i AM running the ati drivers i can try an run m,y backed up default xorg.conf and see how teh system responds.
 
Old 07-21-2005, 05:59 PM   #2
egag
Senior Member
 
Registered: Jul 2004
Location: Netherlands
Distribution: Slackware
Posts: 2,721

Rep: Reputation: 53
------------
I dont belive this is relevant but i AM running the ati drivers i can try an run m,y backed up default xorg.conf and see how teh system responds
------------

i think that's very relevant...
can you try your old xorg.conf ?

also tell smth. about your hardware....
i mean graphics card, mobo.
also , which kernel do you use ?

egag
 
Old 07-21-2005, 06:15 PM   #3
PSIPHON
Member
 
Registered: Jul 2005
Distribution: SuSe 10.0
Posts: 39

Original Poster
Rep: Reputation: 15
this is the information i know:

P4 1.7
128 + 256 RDRAM (aka rambus PC800)
Radeon 9800 Pro (ATI Retail card)

mother board is a dell the machine is a Dimenstion 8100

2.4.29 kernel
KDE 3.3.2
 
Old 07-21-2005, 06:17 PM   #4
PSIPHON
Member
 
Registered: Jul 2005
Distribution: SuSe 10.0
Posts: 39

Original Poster
Rep: Reputation: 15
the only errors i can see when i do ctrl alt 1 is this:

QPixmap: Cannot create a QPixmap when no GUI is being used

message is repeated 4 times.

[EDIT]: using my defalt generated xorg.conf i can jump in and out of KDE, i do see the same artifiacting but then it cleans up and i am able to use it again.

Last edited by PSIPHON; 07-21-2005 at 06:18 PM.
 
Old 07-21-2005, 06:27 PM   #5
egag
Senior Member
 
Registered: Jul 2004
Location: Netherlands
Distribution: Slackware
Posts: 2,721

Rep: Reputation: 53
maybe post here your " device " section of the xorg.conf that you use for the ati ( fglrx) driver.

i know there are many settings, so it might be solved by changing one or two of them.
someone who uses the ati-drivers can take a look at it then.

egag
 
Old 07-21-2005, 07:22 PM   #6
PSIPHON
Member
 
Registered: Jul 2005
Distribution: SuSe 10.0
Posts: 39

Original Poster
Rep: Reputation: 15
yes it does seem to be an issue with the ati drivers if any one is knowledge able about this it would be greatly appreciated

# **********************************************************************
# Monitor section
# **********************************************************************

# Any number of monitor sections may be present

Section "Monitor"
Identifier "Monitor0"
HorizSync 30 - 120
VertRefresh 60 - 85
Option "DPMS"

# === mode lines based on GTF ===

## for the sake of readability i removed all the mode lines that i was not using for posting pourposes

# 1280x960 @ 100Hz
Modeline "1280x960@100" 178.992 1280 1376 1520 1760 960 961 964 1017 +hsync +vsync


EndSection


# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

# Standard VGA Device:

Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"

# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.

# Chipset "generic"

# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.

Driver "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# installed.

# BusID "PCI:0:10:0"

# VideoRam 256

# Clocks 25.2 28.3

EndSection

# === 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" "yes"
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" "0"
Option "BlockSignalsOnLock" "on"
Option "UseInternalAGPGART" "yes"
Option "ForceGenericCPU" "no"
BusID "PCI:1:0:0" # vendor=1002, device=4e48
Screen 0
EndSection

# **********************************************************************
# Screen sections
# **********************************************************************

# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen0"
Device "ATI Graphics Adapter"
Monitor "Monitor0"
DefaultDepth 24
#Option "backingstore"

Subsection "Display"
Depth 24
Modes "1280x960" "1152x864" "1024x768" "800x600" "640x480"
ViewPort 0 0 # initial origin if mode is smaller than desktop
# Virtual 1280 1024
EndSubsection
EndSection
 
Old 07-21-2005, 07:47 PM   #7
egag
Senior Member
 
Registered: Jul 2004
Location: Netherlands
Distribution: Slackware
Posts: 2,721

Rep: Reputation: 53
---------
Option "UseInternalAGPGART" "yes"
---------

maybe try to change that to "no".
i read that it's better to use the kernel's agp driver.

egag
 
Old 07-21-2005, 08:57 PM   #8
PSIPHON
Member
 
Registered: Jul 2005
Distribution: SuSe 10.0
Posts: 39

Original Poster
Rep: Reputation: 15
yeah i set these two:

Option "BlockSignalsOnLock" "on"
Option "UseInternalAGPGART" "yes"

to this

Option "BlockSignalsOnLock" "off"
Option "UseInternalAGPGART" "no"

and it still does the minor shredding and then locks.
 
  


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
KDE, Gnome freeze... djib Debian 4 05-18-2005 06:38 PM
KDE freeze 13blue Slackware 11 02-05-2005 10:42 PM
KDE 3.3 - Freeze on logout stl1859 Linux - Software 1 01-02-2005 04:29 PM
under kde kppp freeze when used demmylls Linux - General 0 02-15-2004 10:39 AM
How to escape KDE FReeze supersport Linux - Newbie 2 11-01-2001 02:16 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 12:37 AM.

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
Open Source Consulting | Domain Registration