Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
ati treiber 8.10.19 [gelößt]
View unanswered posts
View posts from last 24 hours
View posts from last 7 days

Goto page 1, 2  Next  
Reply to topic    Gentoo Forums Forum Index Deutsches Forum (German)
View previous topic :: View next topic  
Author Message
mopar
n00b
n00b


Joined: 01 Mar 2005
Posts: 47

PostPosted: Tue Mar 01, 2005 11:08 am    Post subject: ati treiber 8.10.19 [gelößt] Reply with quote

hallo ich hab eine ati mobility radeon 9700 und habe bisher den treiber der version 8.8.25 benutzt. Nun habe ich den neuen 8.10.19 Treiber emerged und habe unter X keine 3d Beschleunigung mehr. Wenn ich fglrxinfo ausführe steht anstatt der Karte die Mesa3d adresse drin. Mit dem 8.8.25 Treiber habe ich 3d Unterstützung. Das seltsame ist nur das wenn ich den alten Treiber benutze ich bei glxgears extrem wenig Frames habe. Wenn ich den neuen mit glxgears benutze steigt die Framrate deutlich an obwohl ja eigentlich keine 3d unterstützung da sein sollte.

Wiso wird der neue Treiber von X nicht erkannt ?

hat schon irgendjemand Erfahrung damit??

meine Xorg.conf habe ich mit fglrxconfig erstellt. Ist dabei vielleicht eine Nachbearbeitung erforderlich ?? Theorethisch könnte ich doch die alte weiter benutzen oder nicht??


Last edited by mopar on Wed Mar 02, 2005 6:15 pm; edited 1 time in total
Back to top
View user's profile Send private message
Anarcho
Advocate
Advocate


Joined: 06 Jun 2004
Posts: 2959
Location: Wuppertal (Germany)

PostPosted: Tue Mar 01, 2005 11:17 am    Post subject: Reply with quote

Hast du mal "opengl-update ati" probier?
_________________
...it's only Rock'n'Roll, but I like it!
HOWTO:WLAN mit OpenVPN absichern | TOOL:useedit - USE-flag editor/changer
Back to top
View user's profile Send private message
mopar
n00b
n00b


Joined: 01 Mar 2005
Posts: 47

PostPosted: Tue Mar 01, 2005 11:24 am    Post subject: Reply with quote

ja hab ich gemacht hat keine wirkung gezeigt
Back to top
View user's profile Send private message
flubber
Tux's lil' helper
Tux's lil' helper


Joined: 28 Dec 2004
Posts: 136

PostPosted: Tue Mar 01, 2005 1:31 pm    Post subject: Reply with quote

Nachbearbeitung ist eigentlich keine Erforderlich, der kbd-Eintrag ist jetzt gefixt. Eventuell bei der maus nachsehen.
Sind aber ganauso Schrott wie die alten. Wenn man, wie ich, DVI nutzt.

Flubber
Back to top
View user's profile Send private message
mopar
n00b
n00b


Joined: 01 Mar 2005
Posts: 47

PostPosted: Tue Mar 01, 2005 2:09 pm    Post subject: Reply with quote

das komische ist ja aber das die karte beim alten treiber reibungslos erkannt wird und beim neuen nicht.

Wenn ich mit emerge ati-drivers die Version 8.8.25 emerge und danach opengl-update mache und x neu starte wird mir bei fglrxinfo die karte vollständig erkannt und ich habe 3d beschleunigung in X.

Wenn ich die neuen Treiber der Version 8.10.19 emerge und opengl-update mache wird die karte nicht mehr bei fglrxinfo erkannt und die 3d beschleunigung unter x ist weg wiso??
Back to top
View user's profile Send private message
STiGMaTa_ch
Veteran
Veteran


Joined: 28 Dec 2004
Posts: 1686
Location: Rüti ZH / Schweiz

PostPosted: Tue Mar 01, 2005 2:37 pm    Post subject: Reply with quote

Hallo mopar

Ich hatte Anfangs auch Probleme mit den 8.10.19 Treibern. Dann habe ich den nachfolgenden Link gefunden und seither funktionieren die Treiber ohne Probleme.

http://odin.prohosting.com/wedge01/gentoo-radeon-faq.html

Befolge doch davon einfach mal Section 1-3, vielleicht hilft es. Die Troubleshooting Section ist auch ganz hilfreich.

P.s. Ich habe die entsprechenden Kernel Treiber FIX kompiliert (also keine Module). Dafür musste ich in der xorg.conf Datei folgenden Befehl setzen:

Code:
Option "UseInternalAGPGART"         "no"


Wer weiss, vielleicht hilft es...

Lieber Gruss
STiGMaTa
Back to top
View user's profile Send private message
NightDragon
Veteran
Veteran


Joined: 21 Aug 2004
Posts: 1144
Location: Vienna (Austria)

PostPosted: Tue Mar 01, 2005 4:02 pm    Post subject: Reply with quote

Seit blos vorsichtig, wenn ihr den externen verwendet.

Ich hab hier nen Sis 645DX Chipsatz und das Sis-Chipsatz AGP-Modul bringt ATI dazu sich aufzuhängen.
Deswegen verwende ich den internet AGPGART Treiber und der funktioniert wunderbar.
inkl. 3D (DRM, MTRR und co).

Schau am besten mal ins Howto (siehe Tipps und Tricks - hier im Forum ganz oben im Thread).
_________________
You are the problem too all my solutions ;)
Back to top
View user's profile Send private message
mopar
n00b
n00b


Joined: 01 Mar 2005
Posts: 47

PostPosted: Tue Mar 01, 2005 4:30 pm    Post subject: Reply with quote

hat bis jetzt alles net viel gebracht

wenn ich dmesg eingeb bekomm ich die meldung

fglrx: Unknown symbol remap_pfn_range
fglrx: Unknown symbol remap_pfn_range


und fgl_glxgears

X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 142 (GLX)
Minor opcode of failed request: 5 (X_GLXMakeCurrent)
Serial number of failed request: 32
Current serial number in output stream: 32

irgend ne idee ??
Back to top
View user's profile Send private message
mopar
n00b
n00b


Joined: 01 Mar 2005
Posts: 47

PostPosted: Tue Mar 01, 2005 4:38 pm    Post subject: Reply with quote

danke übrigens für die antworten


was ich nicht verstehe (ich weiß wir reden ja von ati :cry: ) ist das die alten wunderbar funktionieren und die neuen auf einmal nicht mehr
Back to top
View user's profile Send private message
NightDragon
Veteran
Veteran


Joined: 21 Aug 2004
Posts: 1144
Location: Vienna (Austria)

PostPosted: Tue Mar 01, 2005 4:55 pm    Post subject: Reply with quote

Okay... gib mir mal die Ausgabe von

lsmod und den Device Abschnitt der Grafikkarte aus der xorg.conf.

Was sagt glxinfo beim alten und beim neuen treiber?
und spuckt glxgears beim alten bzw, neuen was aus? also ne fehlermeldung oder ne komische meldung allgemein?

schau dir mal stückchen für stücken die Xorg.log in /var/log/ durch. aber alles. weil oft findet man dort den grund wieso es nicht geht. und das oftmals im klartext.
_________________
You are the problem too all my solutions ;)
Back to top
View user's profile Send private message
mopar
n00b
n00b


Joined: 01 Mar 2005
Posts: 47

PostPosted: Tue Mar 01, 2005 5:21 pm    Post subject: Reply with quote

also fglrxinfo beim alten treiber sagt

display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: MOBILITY RADEON 9700 Generic
OpenGL version string: 1.3.4769 (X4.3.0-8.8.25)

glxinfo beim alten treiber sagt

name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
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: ATI Technologies Inc.
OpenGL renderer string: MOBILITY RADEON 9700 Generic
OpenGL version string: 1.3.4769 (X4.3.0-8.8.25)
OpenGL extensions:
GL_ARB_multitexture, GL_EXT_texture_env_add, GL_EXT_compiled_vertex_array,
GL_S3_s3tc, GL_ARB_depth_texture, GL_ARB_fragment_program,
GL_ARB_fragment_program_shadow, GL_ARB_fragment_shader,
GL_ARB_multisample, GL_ARB_occlusion_query, GL_ARB_point_parameters,
GL_ARB_point_sprite, GL_ARB_shader_objects, GL_ARB_shading_language_100,
GL_ARB_shadow, GL_ARB_shadow_ambient, GL_ARB_texture_border_clamp,
GL_ARB_texture_compression, GL_ARB_texture_cube_map,
GL_ARB_texture_env_add, GL_ARB_texture_env_combine,
GL_ARB_texture_env_crossbar, GL_ARB_texture_env_dot3,
GL_ARB_texture_mirrored_repeat, GL_ARB_transpose_matrix,
GL_ARB_vertex_blend, GL_ARB_vertex_buffer_object, GL_ARB_vertex_program,
GL_ARB_vertex_shader, GL_ARB_window_pos, GL_ATI_draw_buffers,
GL_ATI_element_array, GL_ATI_envmap_bumpmap, GL_ATI_fragment_shader,
GL_ATI_map_object_buffer, GL_ATI_separate_stencil,
GL_ATI_texture_env_combine3, GL_ATI_texture_float,
GL_ATI_texture_mirror_once, GL_ATI_vertex_array_object,
GL_ATI_vertex_attrib_array_object, GL_ATI_vertex_streams,
GL_ATIX_texture_env_combine3, GL_ATIX_texture_env_route,
GL_ATIX_vertex_shader_output_point_size, GL_EXT_abgr, GL_EXT_bgra,
GL_EXT_blend_color, GL_EXT_blend_func_separate, GL_EXT_blend_minmax,
GL_EXT_blend_subtract, GL_EXT_clip_volume_hint,
GL_EXT_draw_range_elements, GL_EXT_fog_coord, GL_EXT_multi_draw_arrays,
GL_EXT_packed_pixels, GL_EXT_point_parameters, GL_EXT_rescale_normal,
GL_EXT_secondary_color, GL_EXT_separate_specular_color,
GL_EXT_shadow_funcs, GL_EXT_stencil_wrap, GL_EXT_texgen_reflection,
GL_EXT_texture3D, GL_EXT_texture_compression_s3tc,
GL_EXT_texture_cube_map, GL_EXT_texture_edge_clamp,
GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3,
GL_EXT_texture_filter_anisotropic, GL_EXT_texture_lod_bias,
GL_EXT_texture_mirror_clamp, GL_EXT_texture_object,
GL_EXT_texture_rectangle, GL_EXT_vertex_array, GL_EXT_vertex_shader,
GL_HP_occlusion_test, GL_NV_texgen_reflection, GL_NV_blend_square,
GL_NV_occlusion_query, GL_SGI_color_matrix, GL_SGIS_texture_edge_clamp,
GL_SGIS_texture_border_clamp, GL_SGIS_texture_lod,
GL_SGIS_generate_mipmap, GL_SUN_multi_draw_arrays
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 32 0 r y . 8 8 8 8 0 24 8 16 16 16 16 1 0 None
0x24 24 tc 0 32 0 r . . 8 8 8 8 0 24 8 16 16 16 16 1 0 None
0x25 24 tc 0 32 0 r y . 8 8 8 8 0 24 0 16 16 16 16 1 0 None
0x26 24 tc 0 32 0 r . . 8 8 8 8 0 24 0 16 16 16 16 1 0 None
0x27 24 tc 0 32 0 r y . 8 8 8 8 0 24 8 0 0 0 0 1 0 None
0x28 24 tc 0 32 0 r . . 8 8 8 8 0 24 8 0 0 0 0 1 0 None
0x29 24 tc 0 32 0 r y . 8 8 8 8 0 24 0 0 0 0 0 1 0 None
0x2a 24 tc 0 32 0 r . . 8 8 8 8 0 24 0 0 0 0 0 1 0 None
0x2b 24 dc 0 32 0 r y . 8 8 8 8 0 24 8 16 16 16 16 1 0 None
0x2c 24 dc 0 32 0 r . . 8 8 8 8 0 24 8 16 16 16 16 1 0 None
0x2d 24 dc 0 32 0 r y . 8 8 8 8 0 24 0 16 16 16 16 1 0 None
0x2e 24 dc 0 32 0 r . . 8 8 8 8 0 24 0 16 16 16 16 1 0 None
0x2f 24 dc 0 32 0 r y . 8 8 8 8 0 24 8 0 0 0 0 1 0 None
0x30 24 dc 0 32 0 r . . 8 8 8 8 0 24 8 0 0 0 0 1 0 None
0x31 24 dc 0 32 0 r y . 8 8 8 8 0 24 0 0 0 0 0 1 0 None
0x32 24 dc 0 32 0 r . . 8 8 8 8 0 24 0 0 0 0 0 1 0 None

fgl_glxgears beim alten spuckt gar nichts aus sondern funktioniert einfach und zählt die frames

fglrxinfo beim neuen treiber sagt

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.1)

glxinfo beim neuen sagt

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
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context,
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.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

fgl_glxgears beim neuen sagt

X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 142 (GLX)
Minor opcode of failed request: 5 (X_GLXMakeCurrent)
Serial number of failed request: 32
Current serial number in output stream: 32


der Device Abschnitt der Graka in der xorg.conf

# **********************************************************************
# 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" "0x00000100"
Option "MonitorLayout" "AUTO, NONE"
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" "2"
Option "BlockSignalsOnLock" "on"
Option "UseInternalAGPGART" "no"
Option "ForceGenericCPU" "no"
BusID "PCI:1:0:0" # vendor=1002, device=4e50
Screen 0
EndSection
Back to top
View user's profile Send private message
mopar
n00b
n00b


Joined: 01 Mar 2005
Posts: 47

PostPosted: Tue Mar 01, 2005 5:32 pm    Post subject: Reply with quote

diese fehlermeldung mit dem neuen treiber hab ich in der Xlog Datei gefunden

(WW) fglrx(0): could not detect XFree86 version (query_status=-3)
drmOpenDevice: Open failed
[drm] failed to load kernel module "fglrx"
(II) fglrx(0): [drm] drmOpen failed
(EE) fglrx(0): DRIScreenInit failed!
(WW) fglrx(0): ***********************************************
(WW) fglrx(0): * DRI initialization failed! *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available *
(WW) fglrx(0): ********************************************* *
Back to top
View user's profile Send private message
NightDragon
Veteran
Veteran


Joined: 21 Aug 2004
Posts: 1144
Location: Vienna (Austria)

PostPosted: Tue Mar 01, 2005 8:45 pm    Post subject: Reply with quote

Quote:
(WW) fglrx(0): could not detect XFree86 version (query_status=-3)

Kann man ruhig ignorieren, das hab ich hier auch.

Ändern sich was am LOG wenn du UseInternalAGPGART auf 1 stellst?

Hast du UseFastTLS mal auf 0 gestellt?

Was sagt lsmod?
Wo ladest Du deine Module?
_________________
You are the problem too all my solutions ;)
Back to top
View user's profile Send private message
fitzroy23
n00b
n00b


Joined: 23 Jan 2005
Posts: 4

PostPosted: Tue Mar 01, 2005 9:33 pm    Post subject: Reply with quote

Hallo,

entschuldigt bitte die Zwischenfrage. Ich hoffe Sie ist leicht zu beantworten deswegen diese Treistigkeit.

Hintergrund

1.Ich habe zurzeit kein Internet an meinem linux Rechner. Ich kann deshalb nicht die neuesten Packete aus dem Netz installieren

2.Auf dem Rechner ist gentoo 2004.3 frisch installiert.
( X Version 6.8.0 )

3.Ich habe mir die Datei fglrx_.._8.10.19.1 runtergeladen.

Frage: Wie kann ich jetzt dafür sorgen das bei

"emerge ati-drivers"

diese Version genommen wird ?
( wohin kopieren ? welche emerge Optionen ? )

Ich würde mich sehr über einen Hinweis freuen.

Danke im Vorraus.
Back to top
View user's profile Send private message
mopar
n00b
n00b


Joined: 01 Mar 2005
Posts: 47

PostPosted: Tue Mar 01, 2005 9:52 pm    Post subject: Reply with quote

also an der log ändert sich nichts wenn ich den agpgart auf yes stelle

[drm] failed to load kernel module "fglrx"
(II) fglrx(0): [drm] drmOpen failed
(EE) fglrx(0): DRIScreenInit failed!
(WW) fglrx(0): ***********************************************
(WW) fglrx(0): * DRI initialization failed! *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available *
(WW) fglrx(0): ********************************************* *

wenn ich UseFastTLS auf 0 stelle ebenfalls nicht

dann mal ne vielleicht blöde frage aber was ist diese Ismod ??

falls das in der xorg.conf steht muss ich das wohle leider übersehen haben deswegen post ich jetzt einfach mal die komplette xorg.conf

# **********************************************************************
# DRI Section
# **********************************************************************
Section "dri"
# Access to OpenGL ICD is allowed for all users:
Mode 0666
# Access to OpenGL ICD is restricted to a specific user group:
# Group 100 # users
# Mode 0660
EndSection

# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"

# This loads the DBE extension module.

Load "dbe" # Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection

# This loads the Type1 and FreeType font modules
Load "type1"
Load "freetype"

# This loads the GLX module
Load "glx" # libglx.a
Load "dri" # libdri.a

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)
#
# If you don't have a floating point coprocessor and emacs, Mosaic or other
# programs take long to start up, try moving the Type1 and Speedo directory
# to the end of this list (or comment them out).
#

FontPath "/usr/X11R6/lib/X11/fonts/local/"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"

# 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><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 XFree86
# Option "XkbRules" "xfree86"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""

# Option "XkbDisable"

Option "XkbRules" "xfree86"
Option "XkbModel" "pc101"
Option "XkbLayout" "de"

EndSection


# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Device" "/dev/input/mice"

# 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 XF86Config 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 "Monitor0"
HorizSync 31.5 - 80.5
VertRefresh 60 - 85
Option "DPMS"

# === mode lines based on GTF ===
# VGA @ 100Hz
# Modeline "640x480@100" 43.163 640 680 744 848 480 481 484 509 +hsync +vsync
# SVGA @ 100Hz
# Modeline "800x600@100" 68.179 800 848 936 1072 600 601 604 636 +hsync +vsync
# XVGA @ 100Hz
# Modeline "1024x768@100" 113.309 1024 1096 1208 1392 768 769 772 814 +hsync +vsync
# 1152x864 @ 60Hz
# Modeline "1152x864@60" 81.642 1152 1216 1336 1520 864 865 868 895 +hsync +vsync
# 1152x864 @ 85Hz
# Modeline "1152x864@85" 119.651 1152 1224 1352 1552 864 865 868 907 +hsync +vsync
# 1152x864 @ 100Hz
# Modeline "1152x864@100" 143.472 1152 1232 1360 1568 864 865 868 915 +hsync +vsync
# 1280x960 @ 75Hz
# Modeline "1280x960@75" 129.859 1280 1368 1504 1728 960 961 964 1002 +hsync +vsync
# 1280x960 @ 100Hz
# Modeline "1280x960@100" 178.992 1280 1376 1520 1760 960 961 964 1017 +hsync +vsync
# SXGA @ 100Hz
# Modeline "1280x1024@100" 190.960 1280 1376 1520 1760 1024 1025 1028 1085 +hsync +vsync
# SPEA GDM-1950 (60Hz,64kHz,110MHz,-,-): 1280x1024 @ V-freq: 60.00 Hz, H-freq: 63.73 KHz
# Modeline "GDM-1950" 109.62 1280 1336 1472 1720 1024 1024 1026 1062 -hsync -vsync
# 1600x1000 @ 60Hz
# Modeline "1600x1000" 133.142 1600 1704 1872 2144 1000 1001 1004 1035 +hsync +vsync
# 1600x1000 @ 75Hz
# Modeline "1600x1000" 169.128 1600 1704 1880 2160 1000 1001 1004 1044 +hsync +vsync
# 1600x1000 @ 85Hz
# Modeline "1600x1000" 194.202 1600 1712 1888 2176 1000 1001 1004 1050 +hsync +vsync
# 1600x1000 @ 100Hz
# Modeline "1600x1000" 232.133 1600 1720 1896 2192 1000 1001 1004 1059 +hsync +vsync
# 1600x1024 @ 60Hz
# Modeline "1600x1024" 136.385 1600 1704 1872 2144 1024 1027 1030 1060 +hsync +vsync
# 1600x1024 @ 75Hz
# Modeline "1600x1024" 174.416 1600 1712 1888 2176 1024 1025 1028 1069 +hsync +vsync
# 1600x1024 @ 76Hz
# Modeline "1600x1024" 170.450 1600 1632 1792 2096 1024 1027 1030 1070 +hsync +vsync
# 1600x1024 @ 85Hz
# Modeline "1600x1024" 198.832 1600 1712 1888 2176 1024 1027 1030 1075 +hsync +vsync
# 1920x1080 @ 60Hz
# Modeline "1920x1080" 172.798 1920 2040 2248 2576 1080 1081 1084 1118 -hsync -vsync
# 1920x1080 @ 75Hz
# Modeline "1920x1080" 211.436 1920 2056 2264 2608 1080 1081 1084 1126 +hsync +vsync
# 1920x1200 @ 60Hz
# Modeline "1920x1200" 193.156 1920 2048 2256 2592 1200 1201 1203 1242 +hsync +vsync
# 1920x1200 @ 75Hz
# Modeline "1920x1200" 246.590 1920 2064 2272 2624 1200 1201 1203 1253 +hsync +vsync
# 2048x1536 @ 60
# Modeline "2048x1536" 266.952 2048 2200 2424 2800 1536 1537 1540 1589 +hsync +vsync
# 2048x1536 @ 60
# Modeline "2048x1536" 266.952 2048 2200 2424 2800 1536 1537 1540 1589 +hsync +vsync
# 1400x1050 @ 60Hz M9 Laptop mode
# ModeLine "1400x1050" 122.000 1400 1488 1640 1880 1050 1052 1064 1082 +hsync +vsync
# 1920x2400 @ 25Hz for IBM T221, VS VP2290 and compatible display devices
# Modeline "1920x2400@25" 124.620 1920 1928 1980 2048 2400 2401 2403 2434 +hsync +vsync
# 1920x2400 @ 30Hz for IBM T221, VS VP2290 and compatible display devices
# Modeline "1920x2400@30" 149.250 1920 1928 1982 2044 2400 2402 2404 2434 +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" "0x00000100"
Option "MonitorLayout" "AUTO, NONE"
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=4e50
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 "1280x1024"
ViewPort 0 0 # initial origin if mode is smaller than desktop
# Virtual 1280 1024
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 "Server 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.

Screen "Screen0"

# 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

### EOF ###
Back to top
View user's profile Send private message
NightDragon
Veteran
Veteran


Joined: 21 Aug 2004
Posts: 1144
Location: Vienna (Austria)

PostPosted: Tue Mar 01, 2005 10:50 pm    Post subject: Reply with quote

@ fitzroy23

Wie hast Du die Daten und vorallem wo hast Du sie dir runtergeladen?
auf einem Fremdsystem via emerge ati-drivers -f oder einafch nur den quellcode von wo anderst?
Falls du es mittels emerge gemacht hast, kopierst du die datei einafch nach /usr/portage/distfiles


@ mopar
Blöde Fragen gibts nicht ;) Man lernt ja so oder so nie aus und muss daher eh voft nachfragen.

Also es gibt da folgendes.

Module, wie Du sie ja schon kennst, werden verwendet um Geräte zum Arbeiten zu bekommen. Also als eine Art Treiber.

Diese werden im normalfall autoamtisch bei bedarf geladen, wenn das Gerät eingesteckt ist. Aber das haut oft nicht sauber hin.
Also gibts da 2 Dateien auf deinem System die die Module automatisch beim hochbooten laden, voraussgesetzt du hast sie dort eingetragen.
Diese Dateien heißen /etc/modules.autload.d/kernel-2.4 und kernel-2.6 Welche beim boot geladen wird und in Welche Du die Treiber eintragen musst, hängt von der verwendeten Kernel-Version ab.

mit
Code:
echo "Modulname" >> /etc/modules.autoload.d/kernel-2.X
(X für 4 oder 6, je nach kernel) kannst du deinem system sagen es soll die Treiber laden.
Ein
Code:
echo "fglrx" >> /etc/modules.autoload.d/kernel-2.X
empfehle ich dir auf jedenfall. aber evetl schaust du ob er nicht schon drinnen steht.
das geht schnell und einfach mit
Code:
cat /etc/modules.autoload.d/kernel-2.X


Okay. soweit so gut.
Der Hauptbefehl für Module nennt sich modprobe

Mit ihm kann man Module schnell und einfach laden.

Z. Bsp.:
Code:
modprobe fglrx
und mit
Code:
modprobe -l
kannst du dir eine Liste aller möglichen module anzeigen. mit
Code:
modprobe -l | grep suchbegriff
kannst du nach einem modul suchen. aber suche da immer nacht bergriffen wie "net" oder "acpi" oder "agp" oder "ati" usw... nicht nach grafik. Weil Grep in dieser Funktion wie ein filter arbeitet.

mit
Code:
modprobe -r modulname
kannst du ein modul wieder entladen.

Und NUN zu lsmod.

lsmod Zeigt dir an, welche Module aktuell geladen sind. Das ist dann angenehm, um zu prüfen obs geht.

Eine Mögliche und Häufige Vorgehnsweise ist das man mit modprobe ein Modul läd und dann mit lsmod überprüft obs läuft :)

Alles klar?
_________________
You are the problem too all my solutions ;)
Back to top
View user's profile Send private message
Anarcho
Advocate
Advocate


Joined: 06 Jun 2004
Posts: 2959
Location: Wuppertal (Germany)

PostPosted: Wed Mar 02, 2005 6:55 am    Post subject: Reply with quote

Quote:
dann mal ne vielleicht blöde frage aber was ist diese Ismod ??


Es heisst "lsmod", also mit "L" am anfang und es ist ein befehl den du in der Konsole eingeben kannst um dir alle geladenen Module anzeigen zu lassen.
_________________
...it's only Rock'n'Roll, but I like it!
HOWTO:WLAN mit OpenVPN absichern | TOOL:useedit - USE-flag editor/changer
Back to top
View user's profile Send private message
fitzroy23
n00b
n00b


Joined: 23 Jan 2005
Posts: 4

PostPosted: Wed Mar 02, 2005 11:25 am    Post subject: Reply with quote

Danke das Du mir hilfst !

Also das ist so :)

Ich hab die CD's gentoo 2004.3 (universal live cd + package cd) von nem freund gezogen und gebrannt bekommen.
Und damit installiert (stage 3) - erstmal langsam anfange. Hab bisher nur etwas Erfahrung mit Suse und Debian gehabt.

Auf der Package CD ist xorg-x11 6.8.0 dabei, welches sich auch problemlos installieren liess.

Nun wollte ich noch den zu meiner Radeon 9800 (pro) passenden Treiber installieren, sprich ati-drivers.
Die vorhandene ati-drivers Version 3.14 will aber logischerweise auch fglrx...3.1.4 installieren wenn ich ihn versuche zu emergen und er will dann auch auf x11 6.7 downgraden (welches sich aber nicht auf den CD's befindet).

Aber für x11 6.8.0 brauch man ja mindestens fglrx... Version 8.8.25 wie ich gelesen habe.

Die fglrx.. 8.10.9 hab ich gefunden als rpm(?). Aber ich kann nirgendwo den passenden ati-drivers ebuild finden.
Back to top
View user's profile Send private message
fitzroy23
n00b
n00b


Joined: 23 Jan 2005
Posts: 4

PostPosted: Wed Mar 02, 2005 11:29 am    Post subject: Reply with quote

Nachtrag

Ich hab auch versucht das rpm einfach so zu installieren.
Also mit rpm2targz (oder so ähnlich) bearbeitet und dann mit tar entpackt.
Aber ich war unsicher ob es jetzt ausreichen würde einfach die entpackten Dateien an die entsprechende Stelle
zu kopieren.
Back to top
View user's profile Send private message
mopar
n00b
n00b


Joined: 01 Mar 2005
Posts: 47

PostPosted: Wed Mar 02, 2005 2:56 pm    Post subject: Reply with quote

danke für die erklärung :)

also das fglrx modul wurde beim booten noch nicht geladen das hab ich dann mit
cho "fglrx" >> /etc/modules.autoload.d/kernel-2.6
abgeändert

wenn ich nun mit dmesg nachschaue was sich bim booten so getan hat bekomm ich bei fglrx die meldung

fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
fglrx: Unknown symbol remap_pfn_range

modprobe fglrx sagt mir

FATAL: Error inserting fglrx (/lib/modules/2.6.9-gentoo-r1/video/fglrx.ko): Unknown symbol in module, or unknown parameter (see dmesg)

und das sagt mir dann lsmod

Module Size Used by
snd_intel8x0 29736 0
snd_ac97_codec 68560 1 snd_intel8x0
snd_mpu401_uart 7168 1 snd_intel8x0
snd_rawmidi 20900 1 snd_mpu401_uart

ich habe halt um die neuesten treiber zu bekommen

ACCEPT_KEYWORDS="~x86" emerge ati-drivers

gemacht

weil wenn ich emerge ati-drivers mache bekomme ich ja nur die version 8.8.25 (die ja funktioniert)
Back to top
View user's profile Send private message
mopar
n00b
n00b


Joined: 01 Mar 2005
Posts: 47

PostPosted: Wed Mar 02, 2005 3:00 pm    Post subject: Reply with quote

das es an den kernel einstellungen liegt kann ja fast nicht sein da es ja mit dem alten treiber wunderbar funktioniert oder??
Back to top
View user's profile Send private message
bbgermany
Veteran
Veteran


Joined: 21 Feb 2005
Posts: 1478
Location: Oranienburg/Germany

PostPosted: Wed Mar 02, 2005 3:41 pm    Post subject: Reply with quote

das symbol remap_pfn_range findest du auf jeden fall im agpgart modul. hast du ein modul passend für dein agp port ???

mach mal ne vollständige ausgabe von lsmod bitte.
Back to top
View user's profile Send private message
mopar
n00b
n00b


Joined: 01 Mar 2005
Posts: 47

PostPosted: Wed Mar 02, 2005 3:44 pm    Post subject: Reply with quote

das war eine vollständige ausgabe

Module Size Used by
snd_intel8x0 29736 0
snd_ac97_codec 68560 1 snd_intel8x0
snd_mpu401_uart 7168 1 snd_intel8x0
snd_rawmidi 20900 1 snd_mpu401_uart
Back to top
View user's profile Send private message
bbgermany
Veteran
Veteran


Joined: 21 Feb 2005
Posts: 1478
Location: Oranienburg/Germany

PostPosted: Wed Mar 02, 2005 3:56 pm    Post subject: Reply with quote

dann wirst du wohl mal schnell agpgart support und für dein board/agp bridge den treiber kompilieren müssen.

meine ausgabe:

Quote:

apollo linux # lsmod
Module Size Used by
snd_pcm_oss 56100 0
snd_mixer_oss 20736 1 snd_pcm_oss
fglrx 242556 7
usblp 13056 0
eth1394 21256 0
ohci1394 35204 0
ieee1394 311736 2 eth1394,ohci1394
ehci_hcd 42884 0
vfat 14592 1
fat 43040 1 vfat
ntfs 110832 3
snd_intel8x0 32544 1
snd_ac97_codec 75616 1 snd_intel8x0
snd_pcm 97544 3 snd_pcm_oss,snd_intel8x0,snd_ac97_codec
snd_timer 26756 1 snd_pcm
snd 55524 8 snd_pcm_oss,snd_mixer_oss,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer
snd_page_alloc 10116 2 snd_intel8x0,snd_pcm
i2c_dev 10496 0
w83627hf 30112 0
i2c_sensor 3712 1 w83627hf
i2c_nforce2 6784 0
i2c_isa 2176 0
i2c_core 22928 5 i2c_dev,w83627hf,i2c_sensor,i2c_nforce2,i2c_isa
sd_mod 17296 5
nvidia_agp 7964 1
agpgart 34600 2 nvidia_agp
apollo linux #
Back to top
View user's profile Send private message
mopar
n00b
n00b


Joined: 01 Mar 2005
Posts: 47

PostPosted: Wed Mar 02, 2005 4:03 pm    Post subject: Reply with quote

ich hab nen laptop wie bekomm ich des mit dem treiber raus welchen ich verwenden soll?

und dev/agpgart is bereits in den kernel kompiliert
als unterpunkt stehen dann da noch
Intel 440LX/BX/GX, I8xx and E7x05 chipset support
Intel i865 chipset support
ebenso
Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)
und in diesem unterpunkt ati radeon
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Deutsches Forum (German) All times are GMT
Goto page 1, 2  Next
Page 1 of 2

 
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