| View previous topic :: View next topic |
| Author |
Message |
pathfinder
l33t
Joined: 19 Jan 2006
Posts: 731
Location: Barcelona, Spain
|
 Posted: Mon Nov 20, 2006 8:47 pm Post subject: [ATI,AIGLX,DRI] Screen 0 is not DRI capable |
 |
|
salut a tous,
j ouvre ce nouveau topic car je pense qu il risque de se perdre sur mon ancien post (https://forums.gentoo.org/viewtopic-t-516248-start-50.html)
j ai un probleme au niveau des drivers open source de ati et du DRI:
voici plutot:
| Quote: | $ cat /var/log/Xorg.0.log | grep WW
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(WW) RADEON: No matching Device section for instance (BusID PCI:4:0:1) found
(WW) RADEON(0): Failed to detect secondary monitor, MergedFB/Clone mode disabled
(WW) (1152x864,Mitsubishi Diamond Scan) mode clock 108MHz exceeds DDC maximum 100MHz
(WW) (1280x960,Mitsubishi Diamond Scan) mode clock 108MHz exceeds DDC maximum 100MHz
(WW) (1280x960,Mitsubishi Diamond Scan) mode clock 148.5MHz exceeds DDC maximum 100MHz
(WW) (1280x1024,Mitsubishi Diamond Scan) mode clock 108MHz exceeds DDC maximum 100MHz
(WW) (1280x1024,Mitsubishi Diamond Scan) mode clock 135MHz exceeds DDC maximum 100MHz
(WW) (1280x1024,Mitsubishi Diamond Scan) mode clock 157.5MHz exceeds DDC maximum 100MHz
(WW) (1600x1200,Mitsubishi Diamond Scan) mode clock 162MHz exceeds DDC maximum 100MHz
(WW) (1600x1200,Mitsubishi Diamond Scan) mode clock 175.5MHz exceeds DDC maximum 100MHz
(WW) (1600x1200,Mitsubishi Diamond Scan) mode clock 189MHz exceeds DDC maximum 100MHz
(WW) (1600x1200,Mitsubishi Diamond Scan) mode clock 202.5MHz exceeds DDC maximum 100MHz
(WW) (1600x1200,Mitsubishi Diamond Scan) mode clock 229.5MHz exceeds DDC maximum 100MHz
(WW) (1792x1344,Mitsubishi Diamond Scan) mode clock 204.8MHz exceeds DDC maximum 100MHz
(WW) (1792x1344,Mitsubishi Diamond Scan) mode clock 261MHz exceeds DDC maximum 100MHz
(WW) (1856x1392,Mitsubishi Diamond Scan) mode clock 218.3MHz exceeds DDC maximum 100MHz
(WW) (1856x1392,Mitsubishi Diamond Scan) mode clock 288MHz exceeds DDC maximum 100MHz
(WW) (1920x1440,Mitsubishi Diamond Scan) mode clock 234MHz exceeds DDC maximum 100MHz
(WW) (1920x1440,Mitsubishi Diamond Scan) mode clock 297MHz exceeds DDC maximum 100MHz
(WW) (1400x1050,Mitsubishi Diamond Scan) mode clock 122MHz exceeds DDC maximum 100MHz
(WW) (1400x1050,Mitsubishi Diamond Scan) mode clock 155.8MHz exceeds DDC maximum 100MHz
(WW) (1600x1024,Mitsubishi Diamond Scan) mode clock 106.91MHz exceeds DDC maximum 100MHz
(WW) (1920x1440,Mitsubishi Diamond Scan) mode clock 341.35MHz exceeds DDC maximum 100MHz
(WW) (2048x1536,Mitsubishi Diamond Scan) mode clock 266.95MHz exceeds DDC maximum 100MHz
(WW) (2048x1536,Mitsubishi Diamond Scan) mode clock 340.48MHz exceeds DDC maximum 100MHz
(WW) (2048x1536,Mitsubishi Diamond Scan) mode clock 388.04MHz exceeds DDC maximum 100MHz
(WW) RADEON(0): Direct rendering disabled
(WW) RADEON(0): Option "dri" is not used
$ cat /var/log/Xorg.0.log | grep EE
Current Operating System: Linux atlantis 2.6.15-gentoo-r1 #15 SMP PREEMPT Mon Nov 20 20:33:16 CET 2006 i686
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(II) Loading extension MIT-SCREEN-SAVER
(EE) RADEON(0): [dri] RADEONDRIGetVersion failed to open the DRM
(EE) AIGLX: Screen 0 is not DRI capable
|
je ne sais pas trop dire quelle carte graphique j utilise, meme si j ai envie de dire que c est une ATI Radeon X300 RV370
mon kernel est un 2.6.15 mais ca devrait pas etre un probleme...
les drivers r300 sont ceux adaptes a ma carte? je comprends pas trop...
j ai jete un oeil au SAV officieux gentoo, mais il a l air un peu vieux et surtout il est la opour fglrx qui lui marche tres bien sur mon poste, mais je voulais passer aux libres.
bien, voila le xorg.conf:
| Quote: | Section "Extensions"
Option "Composite" "enable"
EndSection
Section "Device"
# 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.
# 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
Identifier "Standard VGA"
Driver "vga"
VendorName "Unknown"
BoardName "Unknown"
EndSection
Section "Device"
#VideoRam 262144
# Insert Clocks lines here if appropriate
Identifier "ATI Radeon X300 RV370"
VendorName "ATI Technologies Inc"
Driver "radeon"
# Driver "fglrx"
# Option "XAANoOffscreenPixmaps" "true"
Option "dri" "true"
# this may solve some issues
Option "BusType" "PCI"
# acceleration
Option "AGPMode" "4"
Option "AGPFastWrite" "yes"
Option "EnablePageFlip" "on"
# 1/0 Increases 3D performance substantially
# seemingly in XAA mode only
Option "RenderAccel" "on"
Option "GARTSize" "64"
Option "AccelMethod" "EXA" # or XXA
# from emerge xorgserver:
# * AIGLX patches will be applied.
# * These patches are known to cause problems with EXA enabled.
Option "BackingStore" "true"
# Option "ExaNoOffscreenPixmaps"
# enable (partial) PowerPlay features
Option "DynamicClocks" "on"
# use bios hot keys on thinkpad (aka fn+f7)
# Option "BIOSHotkeys" "on"
#
# # enable radeon specific xinerama
Option "MergedFB" "false"
## Option "CRT2Position" "RightOf"
## Option "CRT2Hsync" "50-75"
## Option "CRT2VRefresh" "30-82"
## Option "MetaModes" "1024x768-1280x1024"
## Option "MergedNonRectangular" "true"
# Color Tiling
Option "ColorTiling" "on"
#
# # Video overlay
# #Option "OverlayOnCRTC2" "on"
EndSection |
| Quote: | Section "ServerLayout"
Identifier "Simple Layout"
Screen "Screen 1" 0 0
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
Option "AIGLX" "true"
EndSection
Section "Module"
# This loads the DBE extension module.
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
# This loads the font modules
# Load "type1"
# Load "speedo"
# This loads the GLX module
Load "dbe" # Double buffer extension
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
Load "freetype"
# Load "xtt"
Load "glx"
# This loads the DRI module
Load "dri" JE NE SAIS JAMAIS SI c est CASE SENSITIVE (parfois DRI, d autres dri)
EndSection
Section "DRI"
Group 0
Mode 0666
EndSection
|
en ce qui concerne le glxinfo, vous vous en douterez:
| Quote: | $ glxinfo
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_EXT_texture_from_pixmap, GLX_OML_swap_method,
GLX_SGI_make_current_read, GLX_SGIS_multisample, GLX_SGIX_hyperpipe,
GLX_SGIX_swap_barrier, GLX_SGIX_fbconfig, GLX_MESA_copy_sub_buffer
client glx vendor string: SGI
client glx version string: 1.4
client glx extensions:
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context,
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_allocate_memory,
GLX_MESA_copy_sub_buffer, GLX_MESA_swap_control,
GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_OML_sync_control,
GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync,
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap
GLX version: 1.2
GLX extensions:
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context,
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer,
GLX_OML_swap_method, GLX_SGI_make_current_read, GLX_SGIS_multisample,
GLX_SGIX_fbconfig, GLX_EXT_texture_from_pixmap
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.5.1)
OpenGL extensions:
GL_ARB_depth_texture, GL_ARB_imaging, GL_ARB_multitexture,
GL_ARB_point_parameters, GL_ARB_point_sprite, GL_ARB_shadow,
GL_ARB_shadow_ambient, GL_ARB_texture_border_clamp,
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_texture_non_power_of_two, GL_ARB_texture_rectangle,
GL_ARB_transpose_matrix, GL_ARB_window_pos, GL_EXT_abgr, GL_EXT_bgra,
GL_EXT_blend_color, GL_EXT_blend_func_separate, GL_EXT_blend_logic_op,
GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_clip_volume_hint,
GL_EXT_copy_texture, GL_EXT_draw_range_elements, GL_EXT_fog_coord,
GL_EXT_framebuffer_object, GL_EXT_multi_draw_arrays, GL_EXT_packed_pixels,
GL_EXT_point_parameters, GL_EXT_polygon_offset, GL_EXT_rescale_normal,
GL_EXT_secondary_color, GL_EXT_separate_specular_color,
GL_EXT_shadow_funcs, GL_EXT_stencil_wrap, GL_EXT_subtexture,
GL_EXT_texture, GL_EXT_texture3D, GL_EXT_texture_edge_clamp,
GL_EXT_texture_env_add, GL_EXT_texture_env_combine,
GL_EXT_texture_env_dot3, GL_EXT_texture_lod_bias, GL_EXT_texture_object,
GL_EXT_texture_rectangle, GL_EXT_vertex_array, GL_APPLE_packed_pixels,
GL_ATI_texture_env_combine3, GL_ATI_texture_mirror_once,
GL_ATIX_texture_env_combine3, GL_IBM_texture_mirrored_repeat,
GL_INGR_blend_func_separate, GL_MESA_pack_invert, GL_MESA_ycbcr_texture,
GL_NV_blend_square, GL_NV_point_sprite, GL_NV_texgen_reflection,
GL_NV_texture_rectangle, GL_SGIS_generate_mipmap,
GL_SGIS_texture_border_clamp, GL_SGIS_texture_edge_clamp,
GL_SGIS_texture_lod, GL_SGIX_depth_texture, GL_SGIX_shadow,
GL_SGIX_shadow_ambient, GL_SUN_multi_draw_arrays
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 0 0 None
0x24 24 tc 0 24 0 r y . 8 8 8 0 0 16 8 16 16 16 0 0 0 None
0x25 24 tc 0 32 0 r y . 8 8 8 8 0 16 8 16 16 16 16 0 0 None
0x26 24 tc 0 32 0 r . . 8 8 8 8 0 16 8 16 16 16 16 0 0 None
0x27 24 dc 0 24 0 r y . 8 8 8 0 0 16 0 0 0 0 0 0 0 None
0x28 24 dc 0 24 0 r y . 8 8 8 0 0 16 8 16 16 16 0 0 0 None
0x29 24 dc 0 32 0 r y . 8 8 8 8 0 16 8 16 16 16 16 0 0 None
0x2a 24 dc 0 32 0 r . . 8 8 8 8 0 16 8 16 16 16 16 0 0 None
0x43 32 tc 0 32 0 r . . 8 8 8 8 0 0 0 0 0 0 0 0 0 Ncon
|
et moi je ne sais pas quoi faire, je n ai rien vu sur le forum concernant ceci,
j ai lu sur un forum ubuntu que parfois avec XGL (c est pas mon cas, si?) il y avait des issues pour le display 0 et qu il fallait passer en display 1... mais sinon, je vois pas du tout... EDIT: C EST BIDON, CA NE ME RESOUT RIEN DU TOUT
sudo /etc/init.d/xdm stop
startx -- :1.0 ca ne marche pas.
j ai aussi lu quelqu un qui suggerait de passer a un kernel plus nouveau (????!!!!!!)
mais rien de resolu et rien n avance.
un post sur le forum international n est pas resolu non plus, alors voila pourquoi je suis la.
a vous la regie!
Last edited by pathfinder on Wed Nov 29, 2006 1:52 pm; edited 2 times in total |
|
| Back to top |
|
 |
pathfinder
l33t
Joined: 19 Jan 2006
Posts: 731
Location: Barcelona, Spain
|
| Posted: Mon Nov 20, 2006 8:54 pm Post subject: |
|
|
| Quote: | $ sudo dmesg | egrep -i "drm|agp"
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected an Intel 915G Chipset.
agpgart: AGP aperture is 256M @ 0x0
[drm] Initialized drm 1.0.0 20040925
|
|
|
| Back to top |
|
|
Prophidys
n00b
Joined: 23 May 2006
Posts: 42
|
| Posted: Mon Nov 20, 2006 8:56 pm Post subject: |
|
|
| tu n'as pas une ati mais une Intel 915G |
|
| Back to top |
|
|
pathfinder
l33t
Joined: 19 Jan 2006
Posts: 731
Location: Barcelona, Spain
|
| Posted: Mon Nov 20, 2006 9:12 pm Post subject: |
|
|
| Quote: | atlantis linux # dmesg | grep drm
[drm] Initialized drm 1.0.0 20040925
atlantis linux # dmesg | grep agp
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected an Intel 915G Chipset.
agpgart: AGP aperture is 256M @ 0x0
|
car je suis l info sur le site:http://dri.freedesktop.org/wiki/AGP
ensuite:
| Quote: | x This option gives you AGP support for the GLX component of XFree86 4.x x
x on Intel 440LX/BX/GX, 815, 820, 830, 840, 845, 850, 860, 875, x
x E7205 and E7505 chipsets and full support for the 810, 815, 830M, 845G, x
x 852GM, 855GM, 865G and I915 integrated graphics chipsets. |
c est un module que j ai charge dans le kernel:
| Code: | <M> /dev/agpgart (AGP Support) x x
x x < > ALI chipset support x x
x x <M> ATI chipset support x x
x x < > AMD Irongate, 761, and 762 chipset support x x
x x < > AMD Opteron/Athlon64 on-CPU GART support x x
x x <M> Intel 440LX/BX/GX, I8xx and E7x05 chipset support x x
x x < > NVIDIA nForce/nForce2 chipset support x x
x x < > SiS chipset support x x
x x < > Serverworks LE/HE chipset support x x
x x < > VIA chipset support x x
x x < > Transmeta Efficeon support x x
x x <M> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) x x
x x < > 3dfx Banshee/Voodoo3+ x x
x x < > ATI Rage 128 x x
x x <M> ATI Radeon x x
x x < > Intel I810 x x
x x < > Intel 830M, 845G, 852GM, 855GM, 865G |
... est ce le bon dans mon cas?
ca peut etre un truc de mesa qui coince? |
|
| Back to top |
|
|
pathfinder
l33t
Joined: 19 Jan 2006
Posts: 731
Location: Barcelona, Spain
|
| Posted: Mon Nov 20, 2006 9:14 pm Post subject: |
|
|
d apres le wiki sur DRI,
il peut que j aie un problemee la, mais je pige pas bien:
| Quote: | Linux:
[drm] AGP 0.99 on Intel i815 @ 0xe8000000 64MB
[drm] Initialized radeon 1.1.1 20010405 on minor 0
Note that 64MB is not the size of the card's memory; it's the size of the AGP aperture (how much system memory can be accessed by the card if X chooses to use that much).
FreeBSD:
*
If kldload <card> (card being one of mga, r128, radeon, sis, tdfx) says Exec format error, check your dmesg for complaints about unresolved symbols. If the unresolved symbols are agp, look at the AGP instructions above.
*
If kldstat shows your card module is loaded but nothing shows up in dmesg | grep drm, you may not have a supported card, or it may not be getting probed due to the PCI ID being missing from the driver.
Linux:
*
If you get DRM version output but not your card-specific DRM version output, you may not have a supported card, or it may not be getting probed due to the PCI ID being missing from the driver.
If your card isn't getting probed, please make sure you are using current DRM CVS sources before submitting a report of missing support. Instructions for building the DRM are at: Building.
If you are using current DRM sources and your card should be supported by an existing driver but isn't, please submit a report to http://bugs.freedesktop.org/ with the output of scanpci
|
|
|
| Back to top |
|
|
Prophidys
n00b
Joined: 23 May 2006
Posts: 42
|
| Posted: Mon Nov 20, 2006 9:23 pm Post subject: |
|
|
dans ton xorg.conf tu charge les pilotes radeon ...
charge les bon pilotes intel et aprés ca devrai marcher un peu mieux ! |
|
| Back to top |
|
|
pathfinder
l33t
Joined: 19 Jan 2006
Posts: 731
Location: Barcelona, Spain
|
| Posted: Mon Nov 20, 2006 9:28 pm Post subject: |
|
|
?!?!?!!!!!!
euh!?!?!??
:S
ma carte graphique est une ATI RADEON X300 RV370
je sais pas ce qu est le AGPGART ni ou ca se trouve ni ou savoir ou il est branche, mais j avoue que le je pige rien a ta remarque...
je suis quasi sur que ma carte, et donc le driver associe, est une ATI
da illeurs fglrx marchait tres bien.
donc je crois qu il y a confusion quelque part... |
|
| Back to top |
|
|
YetiBarBar
Guru
Joined: 23 Dec 2005
Posts: 532
|
| Posted: Mon Nov 20, 2006 9:41 pm Post subject: |
|
|
| pathfinder wrote: | ?!?!?!!!!!!
euh!?!?!??
:S
ma carte graphique est une ATI RADEON X300 RV370
je sais pas ce qu est le AGPGART ni ou ca se trouve ni ou savoir ou il est branche, mais j avoue que le je pige rien a ta remarque...
je suis quasi sur que ma carte, et donc le driver associe, est une ATI
da illeurs fglrx marchait tres bien.
donc je crois qu il y a confusion quelque part... |
L'agpgart est un module qui te permet de faire fonctionner l'AGP (ce qui a un interet certain si ta carte est en AGP ...) Par contre, si tu utilises de l'AMD64, il me semble qu'il faut désactiver une option dans le noyau pour pouvoir le faire fonctionner correctement (Processor Type and features -> [ ] K8 gart IOMMU ) |
|
| Back to top |
|
|
nemo13
Veteran
Joined: 08 Oct 2004
Posts: 1016
Location: France/Istres
|
| Posted: Mon Nov 20, 2006 9:47 pm Post subject: |
|
|
| pathfinder wrote: | ?!?!?!!!!!!
euh!?!?!??
:S
ma carte graphique est une ATI RADEON X300 RV370
je sais pas ce qu est le AGPGART ni ou ca se trouve ni ou savoir ou il est branche, mais j avoue que le je pige rien a ta remarque...
je suis quasi sur que ma carte, et donc le driver associe, est une ATI
da illeurs fglrx marchait tres bien.
donc je crois qu il y a confusion quelque part... |
Et si nous revenions au début 
par : ta carte est agp ou pci ?
car sur le clubic il semblerait qu'elle soit pci
donc la question à 100 sous que dit
( désolé si tu l'as déja dit mais ton fil précédent ...est long )
Prophidys> il peut très bien avoir un chipset 915g et une carte ati
A+ |
|
| Back to top |
|
|
pathfinder
l33t
Joined: 19 Jan 2006
Posts: 731
Location: Barcelona, Spain
|
| Posted: Mon Nov 20, 2006 9:49 pm Post subject: |
|
|
je suis pas en AMD64
| Quote: | $ sudo emerge --info
Portage 2.1.1-r1 (default-linux/x86/2006.0, gcc-4.1.1, glibc-2.4-r4, 2.6.15-gentoo-r1 i686)
=================================================================
System uname: 2.6.15-gentoo-r1 i686 Intel(R) Pentium(R) 4 CPU 3.20GHz
Gentoo Base System version 1.12.6
Last Sync: Thu, 16 Nov 2006 13:01:01 +0000
ccache version 2.3 [enabled]
app-admin/eselect-compiler: [Not Present]
dev-java/java-config: 1.3.7, 2.0.30
dev-lang/python: 2.4.3-r4
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache: 2.3
dev-util/confcache: [Not Present]
sys-apps/sandbox: 1.2.17
sys-devel/autoconf: 2.13, 2.60
sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2
sys-devel/binutils: 2.16.1-r3
sys-devel/gcc-config: 1.3.13-r4
sys-devel/libtool: 1.5.22
virtual/os-headers: 2.6.17-r1
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O3 -march=pentium4 -pipe"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/X11/xkb"
CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/java-config/vms/ /etc/revdep-rebuild /etc/splash /etc/terminfo /etc
/texmf/web2c"
CXXFLAGS="-O3 -march=pentium4 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig buildsyspkg ccache cvs distlocks metadata-transfer sandbox sfperms strict userpriv usersandbox"
GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo"
LINGUAS="es fr en_GB en"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats
--timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/sci /usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 X a52 aac acpi alsa apache2 apm berkdb bitmap-fonts bzip2 cairo cdr cli cracklib crypt cups dbus dlloader dri dvd dvdr dvdr
ead eds elibc_glibc emacs emboss encode esd firefox foomaticdb fortran gdbm gif gnome gpm gs gstreamer gtk gtk2 hal hald howl iconv
imagemagick imlib input_devices_evdev input_devices_keyboard input_devices_mouse ipv6 isdnlog java jpeg kernel_linux ldap libg++ lib
www linguas_en linguas_en_GB linguas_es linguas_fr mad matroska mikmod mmx motif mp3 mpeg nautilus ncurses nls nptl nsplugin ogg ope
ngl openmotif oss pam pcre perl png ppds pppd python qt3 qt4 quicktime readline reflection sdl session spell spl sse sse2 ssl tcpd t
iff truetype truetype-fonts type1-fonts udev unicode userland_GNU video_cards_fbdev video_cards_radeon video_cards_vesa vorbis win32
codecs xemacs xine xinerama xml xorg xv xvid zlib"
Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, PORTAGE_RSYNC_EXTRA_OPTS
|
je sais pas si ma carte est AGP... |
|
| Back to top |
|
|
nykos
Guru
Joined: 08 Jun 2005
Posts: 488
Location: Strasbourg
|
| Posted: Mon Nov 20, 2006 10:02 pm Post subject: |
|
|
je réitère la question posée plus haut, que te donne la commande ?
_________________
-=Nykos=-
TARGA Traveller 826T - AMD Turion 64 MT 32 1,8GHz - ATI Radeon X700 Mobility (ati-drivers) |
|
| Back to top |
|
|
pathfinder
l33t
Joined: 19 Jan 2006
Posts: 731
Location: Barcelona, Spain
|
| Posted: Mon Nov 20, 2006 10:08 pm Post subject: |
|
|
pardon j avais pas vu!
| Quote: | $ sudo lspci
00:00.0 Host bridge: Intel Corporation 82915G/P/GV/GL/PL/910GL Memory Controller Hub (rev 0e)
00:01.0 PCI bridge: Intel Corporation 82915G/P/GV/GL/PL/910GL PCI Express Root Port (rev 0e)
00:1b.0 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 2 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 03)
00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d3)
00:1f.0 ISA bridge: Intel Corporation 82801FB/FR (ICH6/ICH6R) LPC Interface Bridge (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) IDE Controller (rev 03)
00:1f.2 IDE interface: Intel Corporation 82801FB/FW (ICH6/ICH6W) SATA Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller (rev 03)
02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053 PCI-E Gigabit Ethernet Controller (rev 19)
04:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)]
04:00.1 Display controller: ATI Technologies Inc RV370 [Radeon X300SE]
|
_________________
Cuando un tonto coge un camino, el camino se acaba, pero el tonto sigue |
|
| Back to top |
|
|
nemo13
Veteran
Joined: 08 Oct 2004
Posts: 1016
Location: France/Istres
|
| Posted: Mon Nov 20, 2006 10:23 pm Post subject: |
|
|
| pathfinder wrote: | | je sais pas si ma carte est AGP... |
bon on va chercher ensemble
que donne
"chez moi" sur mon fixe
| Quote: | lspci |grep -i vga
01:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6600] (rev a2) |
c'est une pci express et c'est confirmé par | Quote: | lspci |grep -i express
00:01.0 PCI bridge: Intel Corporation 82915G/P/GV/GL/PL/910GL PCI Express Root Port (rev 04) |
par contre sur le portable
(là je donne à la main car pas encore ssh entre les deux )
| Quote: | lspci |grep -i vga donne
...blabla ...ATI technologie rage mobility AGP 2X |
et c'est confirmé par | Quote: | lspci |grep -i agp
PCI bridge ....VIA KT133/KM133 AGP |
donc "envoies ton lspci et on voit.
A+ |
|
| Back to top |
|
|
Magic Banana
Veteran
Joined: 13 Dec 2005
Posts: 1912
Location: Belo Horizonte, Minas Gerais, Brasil
|
| Posted: Tue Nov 21, 2006 9:32 am Post subject: |
|
|
D'après ton lspci ta carte est bien PCI. Je te conseille de virer des options de la section Device de ton /etc/X11/xorg.conf pour y voir plus clair (essaie ensuite de les remmettre). Contente toi de cela pour le moment :
| Code: | Section "Device"
Identifier "ATI Radeon X300 RV370"
Driver "radeon"
Option "dri" "true"
Option "BusType" "PCI"
EndSection |
Ça ne te rappelle rien ce dégraissage de fichier ?
Tu peux déjà essayer de voir si cela résoud ton problème. Si non tu pourais aussi nous poster la section Screen avec l'identifiant "Screen 1" que tu semble utiliser.
Remarque : Rien ne t'empêche de te faire deux sections "Screen" différentes qui utiliseraient deux "Device" différents (un avec les drivers radeon, l'autre avec les drivers fglrx). Ainsi tu pourrais en peu de temps passer d'une configuration à l'autre.
EDIT : Je viens de penser à quelque chose. Il faut, il me semble avoir "radeon" dans une variable VIDEO_CARDS (dans /etc/make.conf) lorsque xorg-server est compilé. Si quelqu'un pouvait confirmer (je ne suis pas sur ma Gentoo et ne suis pas sûr des noms). Si tu n'as pas cela tu es bon pour une recompilation de xorg-server (avec l'option "-1" ).
EDIT2 : Il me semble que si tu n'as pas cette variable VIDEO_CARDS, le support pour toutes les cartes vidéos est installé. Donc cela ne te résoudra pas ton problème. Néanmoins, une fois définie, un "emerge --depclean" va te permettre de nettoyer un peu ton serveur X.
Last edited by Magic Banana on Tue Nov 21, 2006 9:52 am; edited 2 times in total |
|
| Back to top |
|
|
Prophidys
n00b
Joined: 23 May 2006
Posts: 42
|
| Posted: Tue Nov 21, 2006 9:42 am Post subject: |
|
|
| ptain faut que j'arrete l'alcool moi -_- |
|
| Back to top |
|
|
El_Goretto
Moderator
Joined: 29 May 2004
Posts: 3174
Location: Paris
|
| Posted: Tue Nov 21, 2006 10:25 am Post subject: |
|
|
Euuuh, ya du DRI pour les carte PCI?
C'est pas uniquement pour les cartes AGP?
(et pis le SAVAGE HQ, il est pas vieux d'abord. Il référence les pépins et solutions à propos de fglrx sur le forum français. Donc soit ya plus aucun pépin et les drivers fonctionnent correctement, soit plus personne ne l'utilise  ).
_________________
-TrueNAS & jails: µ-serv Gen8 E3-1260L, 16Go ECC + µ-serv N40L, 10Go ECC
-Réseau: APU2C4 (OpenWRT) + GS726Tv3 + 2x GS108Tv2 + Archer C5v1 (OpenWRT) |
|
| Back to top |
|
|
pathfinder
l33t
Joined: 19 Jan 2006
Posts: 731
Location: Barcelona, Spain
|
| Posted: Tue Nov 21, 2006 10:30 am Post subject: |
|
|
edit:
El Goretto: te fache pas, je voulais dire que pour moi puisque j etais en drivers libres c etait pas utile.
PCI/DRI ou AGP/DRI: je suis completement largue, j y connais absolument rien, je peux pas trop dire... ca serait en effet assez tranchant...
MagicBanana: il y a un post plus haut où j'ai mis
.../etc/make.conf
edit2: c est faux... c etait sur l autre post...
| pathfinder wrote: | /etc/make.conf...
avait fglrx et pas radeon...
je suppose qu il faut emerger en onshot xorg-x11 maintenant...
je relance et vous dis quoi
oups, trop pressé: j ai emerge x11 et ca ma mis un virtual dans world
quel idiot!
donc rebelotte, et voici quelque chose d interessant:
| Quote: | dep -ps
To remove:
* sys-libs/db-4.2.52_p4-r2 normal, c est une dep d emacs et ce sera reinstalle avec un revdep-rebuild...
To install:
* x11-drivers/xf86-video-ati-6.6.3 je suppose que ce sont les drivers FREE de ati. il fallait bien les installer... non?
>>> These are the packages that would be unmerged:
sys-libs/db
selected: 4.2.52_p4-r2
protected: none
omitted: 4.3.29-r2 1.85-r2
>>> 'Selected' packages are slated for removal.
>>> 'Protected' and 'omitted' packages will not be removed.
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild N ] x11-drivers/xf86-video-ati-6.6.3 USE="dri -debug" 706 kB
Total size of downloads: 706 kB
|
puis je refais un emerge -auvDN world et revdep-rebuild
et ainsi je remets le xorg-conf avec radeon, je relance le tout, et on verra!
edit:
pour le moment, le dep -s est passé impecc.
emerge -auvDN world a voulu installer mesa, xorg-server111, db, et (pas encore fini, xorg-server est LONG)
et suite a l install de xorgserver (cache dans l install) il y avait ceci:
| Quote: | # * AIGLX patches will be applied.
# * These patches are known to cause problems with EXA enabled.
# * Forcing on xorg-x11 for new enough glxtokens.h...
# Switching to xorg-x11 OpenGL interface... done
|
je m attends donc a ce que EXA en true dans mon xorg.conf soit peut etre ennuyeux (ce serait VRAIMENT le seul souci, ce serait GENIAL)
J ai toujours eu cette question: comment, si on fait un emerge world, et que 30 paquets se reinstallent, ou 55, et qu on ne reste pas devant son ecran, COMMENT peut on voir tous ces petits messages en VERT et en jaune TRES UTILES voire INDISPENSABLES vue la vitesse de defilement des infos sur l ecran?
genre "Do not forget to...
You should...
If you arer using java... you should enable...."
et autres...
ca me tracasse depuis pas mal de temps, parce que je crois qu on perd une info tres tres importante.
exemple ci dessus, avec la remarque concernant EXA. si j etais parti et j avais laisse mon PC tourner, jen aurais rien su du tout... |
ensuite j avais rajouté
emerge --oneshot xorg-x11
 je pensais que tu aurais remarqué (mea culpa)
j ai deja en effet mis radeon dans etc/make.conf, et c est d ailleurs pour ca que ca marche (meme si pas de DRI) cf ci dessus et autre post. il fallait recompiler et un emerge world d ailleurs installait en plus les drivers ATI libres que j avais pas...
Bien, sinon, pour PCI, euh, je comprends donc que c est soit PCI Express soit AGP?
Et que je suis en pciExpress?
| Quote: |
atlantis ~ $ sudo lspci | grep -i express
00:01.0 PCI bridge: Intel Corporation 82915G/P/GV/GL/PL/910GL PCI Express Root Port (rev 0e)
00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 2 (rev 03)
atlantis ~ $ sudo lspci | grep -i vga
04:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)]
atlantis ~ $ sudo lspci | grep -i agp |
pour le xorg.conf, oui, il y a plein de # et d options, mais j aime les garder avec bcp de commentaires pour savoir quoi utiliser le jour venu.
mais je le nettoierai un peu
| Quote: | Section "Screen"
Identifier "Screen 1"
Device "ATI Radeon X300 RV370"
Monitor "Mitsubishi Diamond Scan"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 8
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection |
| Quote: | Section "Device"
#VideoRam 262144
# Insert Clocks lines here if appropriate
Identifier "ATI Radeon X300 RV370"
VendorName "ATI Technologies Inc"
Driver "radeon"
# Driver "fglrx"
# Option "XAANoOffscreenPixmaps" "true"
Option "dri" "true"
# this may solve some issues
Option "BusType" "PCI"
EndSection |
et voila! (je reviens)[/quote] |
|
| Back to top |
|
|
pathfinder
l33t
Joined: 19 Jan 2006
Posts: 731
Location: Barcelona, Spain
|
| Posted: Tue Nov 21, 2006 10:45 am Post subject: |
|
|
ca ne marche pas...
j ai pas de dri.
pourquoi PCIexpress et DRI sont pas compatibles? ils le sont? ou pas?
je peux donc pas avoir beryl?! pas aiglx?
rien?
http://dri.freedesktop.org/wiki/ATIRadeon#head-2f5098616350345fc8b9d26888cb729d63303cf2
| Quote: | R300
driver radeon/r300_dri.so
Status (see also the [Self]r300 portal) Unstable.
Started as [WWW]r300 project, currently maintained in Mesa 3D , 3D driver for r300 and some r4XX chips. To build the latest version see Building.
Radeon 3:
*
Radeon 9500
*
Radeon 9500 Pro
*
Radeon 9700
*
Radeon 9700 Pro
The main difference between the 9500 Pro, and the 9500 is the number or rendering pipelines, half have been disabled in the 9500.
The main difference between the 9500 cards, and the 9700 cards is the bus width, 128 bit for 9500's, 256 bit for 9700's.
The difference between the 9700 Pro, and the 9700 is clockspeed. The 9700 is made by third party manufacturers.
All are based on the R300 chipset (this is probably why they can all use the FireGL drivers) and have DDR.
rv350 / M10
Radeon 3:
*
Radeon 9600
*
Radeon 9600 Pro
The 9600 uses the Rv350 chipset which is a heavily modified R300 chip, the clockspeed increased, the memory interface and Hyper-Z optimized, the number of pipelines halved, using a 0.13µm process.
R350
Radeon 3:
*
Radeon 9800
*
Radeon 9800 Pro
Both these cards use the R350 chip which is a R300 chip which has been modified to be more efficient by improving its Hyper-Z implementation and colour compression algorithms, they also have a higher clock.
The difference between the 9800 Pro and the 9800 is clockspeed.
rv360
*
Radeon 9600 XT
The only differences between the rv350 and the rv360 appear to be an improvement in the manufacturing process and a boost in speed.
R360
*
Radeon 9800 XT
RV370
*
Radeon Xpress 200M
*
Radeon X300
etc...
|
http://www.thinkwiki.org/wiki/ATI_Mobility_Radeon_X300
| Quote: | X.org drivers
The X.org radeon driver works well and support 2D acceleration and some other functionality such as basic power amangement. In conjunction with the r300 DRI driver, radeon also provides 3D acceleration (the latter is not yet stable). ATI provides fglrx, a closed-source Linux-only alternative which adds some functionality such as TV output and advanced power amangement (but has its own stability issues). |
ca s applique dans mon cas? |
|
| Back to top |
|
|
pathfinder
l33t
Joined: 19 Jan 2006
Posts: 731
Location: Barcelona, Spain
|
| Posted: Tue Nov 21, 2006 10:55 am Post subject: |
|
|
pardon, il y avait aussi ceci:
| Quote: | 3D acceleration
OpenGL 3D acceleration is provided by the proprietary fglrx driver (when DRI is enabled). Note that performance is affected by the power saving mode.
The open source r300 DRM module also aims to provide 3D acceleration. This currently requires the CVS/GIT versions of X.org, DRM and Mesa, and has been observed to occasionally crash (e.g., when running Google Earth or ppraceron a T43). You can install it experimentally for testing. |
c est ce qui me semblait hier d apres les conseils de nemo13, en allant voir la page DRI et mesa...http://dri.freedesktop.org/wiki/Building
vous trouvez pas ca trop complique?
il y est d ailleurs dit:
| Quote: | 1. Building the DRI with X.org and Mesa
This is a basic guide to building DRI from source. This guide only covers building the client-side 3D drivers. Since the transition to the modular X.org build, building an X-server and 2D drivers is beyond the scope of this document. That information can be found in the [WWW]X.org Modular Developer's Guide. c est donc obsolete pour mon cas?
KDrive servers are not supported at this time. Please report any problems with these instructions on the dri-users mailing list or on IRC.
The 2D drivers with DRI support, server-side GLX support and the GL library capable of loading DRI 3D drivers are developed upstream in X.org CVS. The 3D drivers now live in the Mesa tree, so you will have to check out the Mesa CVS tree too. You should also get the DRM tree for the updated kernel modules. The following instructions will guide you through the process step by step.
Warning: In case you didn't notice, you are about to compile and install experimental software. This will allow you to test the latest features and bug fixes. It may, however, also introduce new bugs. Be prepared for problems every now and then.
|
je m en sens pas trop capable, c est testing... si vous sentez la chose bien, dites-le, je me lance, mais je sais vraiment pas ar ou comencer...
en fait, CVS ca m inspire le respect... et j ose pas me lancer... |
|
| Back to top |
|
|
Magic Banana
Veteran
Joined: 13 Dec 2005
Posts: 1912
Location: Belo Horizonte, Minas Gerais, Brasil
|
| Posted: Tue Nov 21, 2006 11:20 am Post subject: |
|
|
Et bien il faut a version CVS de xorg-x11 pour avoir le DRI avec le driver radeon.
Mais AIGLX (et donc Beryl) fonctionnera tout de même. En tout cas cela fonctionne chez moi (et je fais tourner des jeux 3D pas trop gourmand) sans que le DRI ne soit activé. |
|
| Back to top |
|
|
pathfinder
l33t
Joined: 19 Jan 2006
Posts: 731
Location: Barcelona, Spain
|
| Posted: Tue Nov 21, 2006 11:42 am Post subject: |
|
|
ok
je prefere ne pas me lancer alors.
si tu dis que aiglx marche, je te crois.
j ai compile xorg avec, en suivant le tuto.
je pars donc vers beryl.
je crois que ce topic est "resolu" dans le sens ou il a repondu aux questions et que ma decision est de rester prudent et stable. patient et peureux :=)
merci a tous.
je repars sur le topic original |
|
| Back to top |
|
|
_droop_
l33t
Joined: 30 May 2004
Posts: 957
|
| Posted: Tue Nov 21, 2006 12:09 pm Post subject: |
|
|
| Magic Banana wrote: | | Et bien il faut a version CVS de xorg-x11 pour avoir le DRI avec le driver radeon. |
Salut,
En fait non, les documentations citées dans ce thread ont l'air un peu vieilles.
Le driver radeon supporte l'accéleration 3D sur toutes les "vieilles" radéon (9800 sûr, peut être X850). Un peu plus d'infos sur le site officiel DRI.
Le support des cartes pour les radéon > 9250 (r300) a été ajouté à Xorg 7.0. A noter que ce driver n'est toujours pas finalisé (problèmes de performance, freeze de Xorg (ca fait un moment que j'en ai plus eu)) mais il s'amèliore régulièrement (en tout cas la différence entre Xorg 7.0 et Xorg 7.1 est flagrante, la version 7.2 ne devrait pas tarder, il y a des ebuilds pour la version CVS pour les impatients). |
|
| Back to top |
|
|
pathfinder
l33t
Joined: 19 Jan 2006
Posts: 731
Location: Barcelona, Spain
|
| Posted: Tue Nov 21, 2006 12:17 pm Post subject: |
|
|
ok, mais alors?! je fais quoi et comment?
comment je charge le driver? je le trouve ou?
j ai bien vu cette page que tu indiques, mais on idrait plus une liste que des drivers...
est ce tu peux m aider un peu plus? pleaaaaaaaaaaaase....
edit:
http://dri.freedesktop.org/wiki/Download[url] | Quote: | Note: Binary snapshots that are currently available for download are not up-to-date. They are likely to have bugs that are fixed in CVS/GIT in the mean time. Please do not report bugs against them.
Note: Binary snapshots are currently not being built. The value of binary snapshots with modular Xorg is questionable and technical problems make it very hard to build one snapshot that works with both modular and monolithic Xorg. |
c est pas super top et ca renvoit a GIT et CVS. non? |
|
| Back to top |
|
|
_droop_
l33t
Joined: 30 May 2004
Posts: 957
|
| Posted: Tue Nov 21, 2006 12:29 pm Post subject: |
|
|
Je te le fais de mémoire, j'éspère ne pas être trop loin sur les noms de variables
1/ dans /etc/make.conf, tu mets VIDEO_CARDS="radeon". Ce que tu sembles avoir fait vu qu'il t as installe xf86-video-ati (qui contient les driver radeon r200 et r300).
2/ Dans le noyau, il faut ajouter Device Driver -> Direct Rendering Interface -> radeon. Si tu as un noyau ancien (<2.6.16), il faut installer x11-drm.
3/ Dans le xorg.conf, tu met driver "radeon" à la section device. Dans la section module, il faut "load dri" et "load glx". Il faut ajouter une section pour DRI.
edit : Un peu plus de détail sur le how to dri gentoo |
|
| Back to top |
|
|
pathfinder
l33t
Joined: 19 Jan 2006
Posts: 731
Location: Barcelona, Spain
|
| Posted: Tue Nov 21, 2006 12:39 pm Post subject: |
|
|
le how to est TRES VIEUX... ils parlent de noyaux 2.4
et ils contredisent ce que j ai lu dans plusieurs wikis...
je pige plus rien.
| Quote: | Exemple de code 2.3 : Les options de make menuconfig
Processor type and features --->
<*> MTRR (Memory Type Range Register) support
Character devices --->
<M> /dev/agpgart (AGP Support)
(Activez le support de votre jeu de composants.)
[M] Intel 440LX/BX/GX and I815/I820/I830M/I830MP/I840/I845/I850/I860 support
< > Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)
Vérifiez que le gestionnaire DRI (DRM - Direct Rendering Manager) est désactivé. Le paquet X11-DRM fournira le sien.
|
moi, j ai DRI d active.
et drm modules non installes
| Quote: | # eix x11-drm
* x11-base/x11-drm
Available versions: 4.3.0-r7:2.6.14-hardened-r8 20050502:2.6.14-hardened-r8 ~20050807 ~20051028 ~20051223 20060608
Installed: none
Homepage: http://dri.sf.net
Description: DRM Kernel Modules for X11
|
mais j ai peur de faire LA BOULETTE si j emerge -1 x11-drm car je vois pas trop qui est recent et qui a vrai.
tu dis que si j ai un noyau ancien, (2.6.15) il faut que j installe x11-drm
Ok.
Que me conseilles tu?
passer a un nouveau noyau? (je fais comment ca, vite et bien, en gardant MES options de config, et pas d autres)
ou emerger x11-drm en enlevant celui du noyau?
edit:
on oublie parfois La Source...
http://www.gentoo.org/doc/en/kernel-upgrade.xml
| Quote: | 10. Advanced: Using your old kernel .config to configure a new one
It is sometimes possible to save time by re-using the configuration file from your old kernel when configuring the new one. Note that this is generally unsafe -- too many changes between every kernel release for this to be a reliable upgrade path.
The only situation where this is appropriate is when upgrading from one Gentoo kernel revision to another. For example, the changes made between gentoo-sources-2.6.9-r1 and gentoo-sources-2.6.9-r2 will be very small, so it is usually OK to use the following method. However, it is not appropriate to use it in the example used throughout this document: upgrading from 2.6.8 to 2.6.9. Too many changes between the official releases, and the method described below does not display enough context to the user, often resulting in the user running into problems because they disabled options that they really didn't want to.
To reuse your old .config, you simply need to copy it over and then run make oldconfig. In the following example, we take the configuration from gentoo-sources-2.6.9-r1 and import it into gentoo-sources-2.6.9-r2.
Code Listing 10.1: Reusing your old config
# cd /usr/src/linux-2.6.9-gentoo-r2
# cp ../linux-2.6.9-gentoo-r1/.config .
# make oldconfig
Code Listing 10.2: Reusing your old config with genkernel
# cd /etc/kernels
# cp kernel-config-x86-2.6.9-gentoo-r1 kernel-config-x86-2.6.9-gentoo-r2
# genkernel all
At this point, you may be asked to produce answers for configuration options which have changed between the two versions. Once you have done that, you can compile and install your kernel as normal, without having to go through the menuconfig configuration process. |
donc apparemment, vite et bien, ca le fera pas.
je dois refaire la config du kernel... ca m ennuie...
et apres, je dois reemerger quoi?
x11-drm?
drivers ati?
tous les modules presents dans autoload? |
|
| 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
|
|
French
