| View previous topic :: View next topic |
| Author |
Message |
SpecialAgent
n00b
Joined: 02 Jan 2005
Posts: 13
|
 Posted: Sun Jan 02, 2005 10:21 am Post subject: Probleme: DMA, KDE |
 |
|
Hallo Leute,
habe mir gerade (die letzten 3 Tage) Gentoo Stage 1 mit Xorg und KDE3.3.2 installiert! Ist alles super und ich bin begeistert von Gentoo und von der guten deutschen Doku. Allerdinsg sind ein paar Sachen bei denen ich nicht weiterkomme:
KDE(X): startet grundsätzlich mit einem virtuellem Screen, obwohl ich das mit xorgconfig für alle screens mit n beantwortet hab! ?!
KDE(X): Wenn ich im KDE bin und mich dann auslogge, dann bekomme ich einen schwarzen Bildschirm mit einem Mauszeiger der sich nicht mehr bewegen lässt. Die Tastatur ist abgestürzt, sogar die NUM Taste (Rechner abgestürzt?->kann nicht an Hardware liegen da XP einwandfrei lange läuft)
DMA: Ich bekomme beim booten, eine fette Warnmeldung das DMA ausgeschaltet ist. Habe im Kernel (2.4.26) nachgeschaut und ja hatte es angekreuzt. Mit hdparm -d 1 /dev/hda (wie in der Installdoku) bekomme ich nur ein: Permission denied, obwohl ich root bin!?
Wäre um eine kleine Hilfestellung sehr dankbar.
Gruss SA
PS: Sagt mir config Files die ich posten soll.
_________________
I'm using OpenBSD, because I would like to knock on heavons door. |
|
| Back to top |
|
 |
Linuxpeter
Guru
Joined: 28 May 2004
Posts: 403
Location: Dresden, Germany
|
| Posted: Sun Jan 02, 2005 11:01 am Post subject: |
|
|
Poste mal bitte deine xorg.conf (ohne Kommentarzeilen bitte).
_________________
Regards, Linuxpeter
Wenn "Windows" die Antwort ist, war es eine dumme Frage. 
Is "Windows" the answer, then it was a stupid question. |
|
| Back to top |
|
|
SpecialAgent
n00b
Joined: 02 Jan 2005
Posts: 13
|
| Posted: Sun Jan 02, 2005 11:39 am Post subject: |
|
|
Ohne Komentare? Das ist ja Arbeit! (siehe weiter unten für die xorg.conf)
Standard Installationsanweisung für KDE Desktop System:
| Code: |
Im obrigen Beispiel, heißt die KDE-Session kde-3.2.1. Nun geben Sie dies in /etc/rc.conf bei der XSESSION Variable ein. Wenn Sie dies tun, können Sie auch gleich den DISPLAYMANAGER mit kdm setzen.
Code Listing 3.3: Einstellen der XSESSION in /etc/rc.conf
# nano -w /etc/rc.conf
(Bearbeiten Sie folgende zwei Variablen)
XSESSION="kde-3.2.1"
DISPLAYMANAGER="kdm"
Zum Schluss fügen wir nun xdm zum standardmäßigen Runlevel hinzu:
Code Listing 3.4: Hinzufügen von xdm zum standardmäßigen Runlevel
# rc-update add xdm default
|
Ok, ich benutze doch kdm, wieso muss ich xdm dem runlevel hinzufügen?
Und hier die xorg.conf:
| Code: |
Section "Module"
# This loads the DBE extension module.
Load "dbe" # Double buffer extension
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
Load "type1"
# Load "speedo"
Load "freetype"
# Load "xtt"
# This loads the GLX module
# Load "glx"
# This loads the DRI module
# Load "dri"
EndSection
# **********************************************************************
# Files section. This allows default font and rgb paths to be set
# **********************************************************************
Section "Files"
# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
RgbPath "/usr/X11R6/lib/X11/rgb"
# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
#
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/Type1/"
# FontPath "/usr/share/fonts/CID/"
FontPath "/usr/share/fonts/75dpi/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/local/"
# FontPath "/usr/share/fonts/Speedo/"
# FontPath "/usr/share/fonts/TrueType/"
# FontPath "/usr/share/fonts/freefont/"
# The module search path. The default path is shown here.
# ModulePath "/usr/X11R6/lib/modules"
EndSection
# **********************************************************************
# Server flags section.
# **********************************************************************
Section "ServerFlags"
# Uncomment this to cause a core dump at the spot where a signal is
# received. This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging
# Option "NoTrapSignals"
# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.
# Option "DontVTSwitch"
# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.
# Option "DontZap"
# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.
# Option "Dont Zoom"
# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.
# Option "DisableVidModeExtension"
# Uncomment this to enable the use of a non-local xvidtune client.
# Option "AllowNonLocalXvidtune"
# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.
# Option "DisableModInDev"
# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).
# Option "AllowNonLocalModInDev"
EndSection
# **********************************************************************
# Input devices
# **********************************************************************
# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************
Section "InputDevice"
Identifier "Keyboard1"
Driver "kbd"
# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.
# Option "Protocol" "Xqueue"
Option "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# These are the default XKB settings for Xorg
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Option "XkbRules" "xorg"
Option "XkbModel" "pc104"
Option "XkbLayout" "de"
EndSection
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "Auto"
Option "Device" "/dev/mouse"
# Mouse-speed setting for PS/2 mouse.
# Option "Resolution" "256"
# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
# Option "Protocol" "Xqueue"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"
# ChordMiddle is an option for some 3-button Logitech mice
# Option "ChordMiddle"
EndSection
# **********************************************************************
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the xorg.conf man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# **********************************************************************
# Monitor section
# **********************************************************************
# Any number of monitor sections may be present
Section "Monitor"
Identifier "My Monitor"
# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
HorizSync 30-115
# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies
# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
VertRefresh 50-160
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
# intalled.
# BusID "PCI:0:10:0"
# VideoRam 256
# Clocks 25.2 28.3
EndSection
# Device configured by xorgconfig:
Section "Device"
Identifier "** NVIDIA (generic) [nv]"
Driver "nv"
#VideoRam 65536
# Insert Clocks lines here if appropriate
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 "Screen 1"
Device "** NVIDIA (generic) [nv]"
Monitor "My Monitor"
DefaultDepth 24
Subsection "Display"
Depth 8
Modes "1024x768" "1280x1024" "800x600"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1024x768" "1280x1024" "800x600"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1024x768" "1280x1024" "800x600"
ViewPort 0 0
EndSubsection
EndSection
# **********************************************************************
# ServerLayout sections.
# **********************************************************************
# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.
Section "ServerLayout"
# The Identifier line must be present
Identifier "Simple Layout"
# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# right of screen 1.
Screen "Screen 1"
# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
# Section "DRI"
# Mode 0666
# EndSection
|
_________________
I'm using OpenBSD, because I would like to knock on heavons door. |
|
| Back to top |
|
|
c07
Veteran
Joined: 25 Oct 2002
Posts: 1091
|
| Posted: Sun Jan 02, 2005 1:19 pm Post subject: |
|
|
| SpecialAgent wrote: | | Ohne Komentare? Das ist ja Arbeit! |
Wenn alle, die das lesen, die Kommentare mitlesen müssen, die sie eh fast auswendig können, ist es noch mehr Arbeit (bzw. niemand wird sie sich machen).
Es gibt aber unter Unix mehrere Möglichkeiten, das zu automatisieren, z.B.
| Code: | | < /etc/X11/xorg.conf sed /^#/d | cat -s |
oder noch gründlicher
| Code: | | < /etc/X11/xorg.conf sed '/^[[:space:]]*#/d' | cat -s |
|
|
| Back to top |
|
|
Jinidog
Guru
Joined: 26 Nov 2003
Posts: 593
Location: Berlin
|
| Posted: Sun Jan 02, 2005 7:36 pm Post subject: |
|
|
Zu dem DMA-Problem.
Hast du denn auch den DMA-Support für deinen Chipsatz einkompiliert?
Der ist bitter von Nöten.
(dein Chipsatz lässt sich wahrscheinlich recht gut mit der Ausgabe von lspci ermitteln).
Ansonsten lautet das Kommando zum Aktiviere hdparm -d1 /dev/hda -
Bei dir war da ein Leerzeichen zuviel, kann aber auch ein Tippfehler sein.
_________________
Just unused Microsoft-Software is good Microsoft-Software |
|
| Back to top |
|
|
kahler
n00b
Joined: 01 Nov 2003
Posts: 62
|
| Posted: Sun Jan 02, 2005 7:38 pm Post subject: |
|
|
| Jinidog wrote: | | ...Bei dir war da ein Leerzeichen zuviel, kann aber auch ein Tippfehler sein. |
Das macht nichts...
| Code: | | hdparm -d 1 /dev/hda |
funktioniert genauso wie | Code: | | hdparm -d1 /dev/hda |
_________________
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GIT d- s:+ a-- C++++ UL++++$ P+>+++ L++ E--- W+++$ N+ o+ K? w O M V- PS+ PE++ Y+ PGP- t--- 5--- X-- R tv b DI++ D+ G e h r y?+
------END GEEK CODE BLOCK------ |
|
| Back to top |
|
|
Tranalogic1987
Tux's lil' helper
Joined: 27 Oct 2004
Posts: 91
Location: Schwechat / Austria
|
| Posted: Sun Jan 02, 2005 8:59 pm Post subject: |
|
|
Jo wegen DMA, hatte auch das Problem => mein Kernel war auf INTEL Chipsätze kompiliert aber dann mit nForce und AMD Support (charakter Devices) Funktioniert DMA 
MfG
_________________
System: Gentoo 2005.1, Gnome 2.18.x, Linux: 2.6.x-gentoo on an AMD Athlon64 Machine |
|
| Back to top |
|
|
SpecialAgent
n00b
Joined: 02 Jan 2005
Posts: 13
|
| Posted: Mon Jan 03, 2005 10:37 am Post subject: |
|
|
Hey,
erstmal Danke für die Hilfe.
Ok, sed für das automatische Kommentarrausreissen... gut! Werd ich mir merken!
DMA Problem:
Habe jetzt mal den neusten Gentoo Dev Kernel (2.6.9-r14 oder so) emerged und den kompiliert. Habe nach meinem Chipsatz VIA KT600 gesucht, aber nichts gefunden. lspci habe ich noch nicht ausprobiert, werd ich noch tun.
Auf jeden Fall ist bei dem neuen Kernel das gleiche DMA Problem.. nunja... ich schau dann mal mit lspci...
KDE Problem:
hat keiner eine Ahnung was das für ein Fehler sein kann?
Hat das evtl. damit zu tun, das ich nach dem emergen immer die /etc/konfigfileUpdate Warnung ignoriert habe? (Stand ja so in der InstAnleitung!)
Gruss SA[/quote]
_________________
I'm using OpenBSD, because I would like to knock on heavons door. |
|
| Back to top |
|
|
Jinidog
Guru
Joined: 26 Nov 2003
Posts: 593
Location: Berlin
|
| Posted: Mon Jan 03, 2005 6:03 pm Post subject: |
|
|
Na, VIA82CXX sieht doch sehr danach aus, das der Treiber passen könnte.
Ansonsten solltest du dich mal informieren, welcher Treiber für den KT600 nötig ist.
Teste mal, ob dein "KDE"-Problem auch beim Abmelden aus anderen Windowmanagern auftritt. (fluxbox ist schnell kompiliert)
Wenn ja, dann ist das kein KDE-Problem, sondern ein X-Server Problem.
Hast du einen Framebuffer für die Konsole aktiviert?
Wenn ja, welche Treiber verwendet der?
Wenn es ein Treiber für deine Nvidia-Karte ist, solltest du auf VESA umstellen.
Es gibt immerwieder die von dir beschriebenen Probleme, wenn man kein VESA verwendet, sondern die Treiber, die "eigentlich" für die eigene Karte gemacht sind.
_________________
Just unused Microsoft-Software is good Microsoft-Software |
|
| Back to top |
|
|
SpecialAgent
n00b
Joined: 02 Jan 2005
Posts: 13
|
| Posted: Tue Jan 04, 2005 8:40 am Post subject: |
|
|
Hey,
also laut der Gigabyte Homepage für mein Mainboard habe ich folgende Chipsätze:
| Code: |
Chipset:
Northbridge : VIA KT600
Southbridge : VIA 8235(8237)
Integrated Peripherals
Realtek ALC655 AC97 codec Chip
Realtek 8101L LAN Chip (Vers. 1)
VIA 6103 LAN Chip (Vers. 2)
Internal I/O Connectors
1 x FDD port
2 x UDMA ATA133/100/66 Bus Master IDE ports
2 x USB 2.0 connectors (support 4 ports)
2 x cooling fan pin header
1 x GAME/ MIDI connector
|
Kann ich denn den VIA82CXX auch für einen VIA 8235(8237) (bedenke kein C!) benutzen? Wenn nein, es gibt sonst nix von VIA im Kernel für HD Controller.
Den Framebuffer muß ich wo einstellen?
Wie sehe ich welchen Treiber ich benutze?
Danke für die Antworten!
Gruss SA
_________________
I'm using OpenBSD, because I would like to knock on heavons door. |
|
| Back to top |
|
|
Jinidog
Guru
Joined: 26 Nov 2003
Posts: 593
Location: Berlin
|
| Posted: Tue Jan 04, 2005 2:13 pm Post subject: |
|
|
Welcher Treiber benutzt wird, steht in den Kernelmeldungen beim Booten.
(werden auch durch das Kommando dmesg ausgegeben)
Es wird der Treiber verwendet, der von denen in den Kernel einkompilierten funktioniert.
Versuch doch einfach den VIA-Treiber, was fragst du da noch lange rum?
Mehr als das DMA nicht funktioniert, kann ja nicht passieren.
(Der Name passt außerdem auf deine Southbridge, der wird's also höchstwahrscheinlich tun)
_________________
Just unused Microsoft-Software is good Microsoft-Software |
|
| Back to top |
|
|
|
|
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
|
|
Deutsches Forum (German)
