Forum |  HardWare.fr | News | Articles | PC | S'identifier | S'inscrire | Shop Recherche
2219 connectés 

  FORUM HardWare.fr
  Linux et OS Alternatifs
  Installation

  probleme installation slack 10 [résolu :jap:]

 



 Mot :   Pseudo :  
 
Bas de page
Auteur Sujet :

probleme installation slack 10 [résolu :jap:]

n°595572
marcelp182
Plop
Posté le 24-11-2004 à 18:58:55  profilanswer
 

salut tout le monde !  :hello:  
ca va faire un moment que j'essaye d'installer slackware 10 sur mon portable DELL latitude C400
pour ne plus avoir de probleme, j'ai fait l'installation compléte de tous les packages.
mais lorsque je lance avec la commande startx, ca beugue  :cry:  
je vous met les lignes de cmd avec des erreurs:
 
(EE) VESA(0): No Matching Modes
(EE) Screen(s) found but none have a usable configuration.
 
Fatal server error:
no screens found
 
please also check the log file at "/var/log/Xorg.O.log" for additional infotmation.
 
XIO: fatal error 104 (connection reset by peer) on X server ":0.0"
     after 0 request (0 know pro cessed) with 0 events remaining.

 
je sais oas si c'est tres clair, mais j'ai l'impression que c'est un probleme au niveau carte graphique.
 
voila si qq pouvait m'aider, merci
 
la config du porrtable:
http://img9.exs.cx/img9/360/Sandra1.th.jpg
http://img9.exs.cx/img9/97/Sandra2.th.jpg


Message édité par marcelp182 le 24-11-2004 à 23:05:44
mood
Publicité
Posté le 24-11-2004 à 18:58:55  profilanswer
 

n°595635
marcelp182
Plop
Posté le 24-11-2004 à 20:13:30  profilanswer
 

[:eternity_78]

n°595636
j_c_p
Linux user
Posté le 24-11-2004 à 20:18:32  profilanswer
 

Faut configurer ton écran, c'est tt [:mrbrelle].
 
Ça se passe ds le fichier /etc/X11/xorg.conf.
 
Sandra : c'est quoi ce truc avec tes fontes ttes moches :p.

n°595638
marcelp182
Plop
Posté le 24-11-2004 à 20:23:48  profilanswer
 

merci je m'en doutait  :pt1cable:  
mais où ds ce fichu fichier?
 
pour la font c pour opimiser le portable

n°595642
marcelp182
Plop
Posté le 24-11-2004 à 20:27:26  profilanswer
 

je l'ai chercher ce fichier mais je le trouve pas


Message édité par marcelp182 le 24-11-2004 à 20:28:01
n°595643
j_c_p
Linux user
Posté le 24-11-2004 à 20:28:09  profilanswer
 

mirtouf : Xorg :o -> cf le message d'erreur :p

n°595644
mirtouf
Light is right !
Posté le 24-11-2004 à 20:32:24  profilanswer
 

j_c_p a écrit :

mirtouf : Xorg :o -> cf le message d'erreur :p


Où ça ? :whistle:


Message édité par mirtouf le 24-11-2004 à 20:32:36

---------------
-~- Libérez Datoune ! -~- Camarade, toi aussi rejoins le FLD pour que la flamme de la Révolution ne s'éteigne pas ! -~- A VENDRE
n°595648
j_c_p
Linux user
Posté le 24-11-2004 à 20:40:07  profilanswer
 


:D -> "please also check the log file at "/var/log/Xorg.O.log" for additional infotmation"

n°595651
sme@gol
Gheu ?!?!?
Posté le 24-11-2004 à 20:58:32  profilanswer
 

le fichier a édite est /etc/X11/xorg.conf
pour cela un petit

Code :
  1. vi /etc/X11.xorg.conf

suffira.
 
Il faut que dans "monitor section" tu renseigne les champs :
HorizSync :
VertRefresh :

n°595654
marcelp182
Plop
Posté le 24-11-2004 à 21:02:25  profilanswer
 

j'ai reussi a recupere le fichier xorg
 
# File generated by xf86config.
 
#
# Copyright (c) 1999 by The XFree86 Project, Inc.
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software" ),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
#  
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#  
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
# THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
#  
# Except as contained in this notice, the name of the XFree86 Project shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from the
# XFree86 Project.
#
 
# **********************************************************************
# Refer to the XF86Config(4/5) man page for details about the format of  
# this file.
# **********************************************************************
 
# NOTE:  This is a NEW IMPROVED version of XF86Config-fbdev that uses the vesa
# driver instead of the fbdev driver.  Thanks to Kenneth Fanyo who pointed
# this out to me. :)
 
# This XF86Config file is designed for use with the VESA framebuffer.
# This generic interface should work with nearly all video cards
# (although not every card will support every resolution).
 
# With the new driver, it should no longer be required to have frame buffer
# support in the kernel, or to run it on the console.
#
# Enjoy! :)
# -- volkerdi@slackware.com
#
 
# **********************************************************************
# 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 font modules
    Load        "type1"
    Load        "freetype"
    Load        "speedo"
 
# This loads the GLX module
    Load       "glx"
 
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/CID/"
    FontPath   "/usr/X11R6/lib/X11/fonts/Speedo/"
    FontPath   "/usr/X11R6/lib/X11/fonts/75dpi/"
    FontPath   "/usr/X11R6/lib/X11/fonts/100dpi/"
    FontPath   "/usr/X11R6/lib/X11/fonts/cyrillic/"
 
# ModulePath can be used to set a search path for the X server modules.
# 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     "DontZoom"
 
# 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"
 
# Set the basic blanking screen saver timeout.
 
#    Option      "blank time"    "10"    # 10 minutes
 
# Set the DPMS timeouts.  These are set here because they are global
# rather than screen-specific.  These settings alone don't enable DPMS.
# It is enabled per-screen (or per-monitor), and even then only when
# the driver supports it.
 
#    Option      "standby time"  "20"
#    Option      "suspend time"  "30"
#    Option      "off time"      "60"
 
# On some platform the server needs to estimate the sizes of PCI
# memory and pio ranges. This is done by assuming that PCI ranges
# don't overlap. Some broken BIOSes tend to set ranges of inactive
# devices wrong. Here one can adjust how aggressive the assumptions
# should be. Default is 0.
 
# Option   "EstimateSizesAggresively" "0"
 
EndSection
 
# **********************************************************************
# Input devices
# **********************************************************************
 
# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************
 
Section "InputDevice"
 
    Identifier "Keyboard1"
    Driver "Keyboard"
# 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"
 
# Set the keyboard auto repeat parameters.  Not all platforms implement
# this.
 
#    Option     "AutoRepeat"    "500 5"
 
# Specifiy which keyboard LEDs can be user-controlled (eg, with xset(1)).
 
#    Option     "Xleds" "1 2 3"
 
# To disable the XKEYBOARD extension, uncomment XkbDisable.
 
#    Option     "XkbDisable"
 
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a European
# keyboard, you will probably want to use one of:
#
#    Option     "XkbModel"      "pc102"
#    Option     "XkbModel"      "pc105"
#
# If you have a Microsoft Natural keyboard, you can use:
#
#    Option     "XkbModel"      "microsoft"
#
# If you have a US "windows" keyboard you will want:
#
#    Option     "XkbModel"      "pc104"
#
# 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 X.Org
#
#    Option     "XkbRules"      "xorg"
#    Option     "XkbModel"      "pc101"
#    Option     "XkbLayout"     "us"
#    Option     "XkbVariant"    ""
#    Option     "XkbOptions"    ""
 
EndSection
 
 
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
 
Section "InputDevice"
 
# Identifier and driver
 
    Identifier "Mouse1"
    Driver "mouse"
 
# On platforms where PnP mouse detection is supported the following
# protocol setting can be used when using a newer PnP mouse:
 
#    Option     "Protocol"      "Auto"
 
# The available mouse protocols types that you can set below are:
#    Auto BusMouse GlidePoint GlidePointPS/2 IntelliMouse IMPS/2
#    Logitech Microsoft MMHitTab MMSeries Mouseman MouseManPlusPS/2
#    MouseSystems NetMousePS/2 NetScrollPS/2 OSMouse PS/2 SysMouse
#    ThinkingMouse ThinkingMousePS/2 Xqueue
    Option "Protocol"    "PS/2"
 
# The mouse device.  The device is normally set to /dev/mouse,
# which is usually a symbolic link to the real device.
 
    Option "Device"      "/dev/mouse"
#   Option "Device"      "/dev/psaux"
#   Option "Device"      "/dev/ttyS0"
#   Option "Device"      "/dev/ttyS1"
 
# 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
 
# Some examples of extended input devices
 
# 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   31.5 - 50.0
 
#    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 40-90
 
EndSection
 
 
# **********************************************************************
# Graphics device section
# **********************************************************************
 
# Any number of graphics device sections may be present
 
Section "Device"
    Identifier  "VESA Framebuffer"
    Driver      "vesa"
    #VideoRam    4096
    # 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      "VESA Framebuffer"
    Monitor     "My Monitor"
 
# If your card can handle it, a higher default color depth (like 24 or 32)
# is highly recommended.
 
#   DefaultDepth 8
#   DefaultDepth 16
   DefaultDepth 24
#   DefaultDepth 32
 
# "1024x768" is also a conservative usable default resolution.  If you
# have a better monitor, feel free to try resolutions such as
# "1152x864", "1280x1024", "1600x1200", and "1800x1400" (or whatever your
# card/monitor can produce)
 
    Subsection "Display"
        Depth       8
        Modes "1024x768" "800x600" "640x480"
    EndSubsection
    Subsection "Display"
        Depth       16
        Modes "1024x768" "800x600" "640x480"
    EndSubsection
    Subsection "Display"
        Depth       24
        Modes "1024x768" "800x600" "640x480"
    EndSubsection
    Subsection "Display"
        Depth       32
        Modes "1024x768" "800x600" "640x480"
    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


Message édité par marcelp182 le 24-11-2004 à 21:04:15
mood
Publicité
Posté le 24-11-2004 à 21:02:25  profilanswer
 

n°595665
sme@gol
Gheu ?!?!?
Posté le 24-11-2004 à 21:20:26  profilanswer
 

mais tu n'as pa renseigné les champs HorizSync et VertRefresh avec les valeurs appropriées. Pour les trouvers, google est ton ami.

n°595691
marcelp182
Plop
Posté le 24-11-2004 à 22:02:18  profilanswer
 

pour HorizSync j'ai mis 30 - 64 et pour VertRefresh 60
mais ca marche toujours pas  :cry:  :cry:  :cry:

n°595694
sme@gol
Gheu ?!?!?
Posté le 24-11-2004 à 22:05:10  profilanswer
 

HorizSync 30-110
VertRefresh 60-110
 
Voila tes valeurs. Et tu exagère un peu il m'as fallut moins d'une minutes pour les trouvés. T'aurais pu y mettre un peu du tien.

n°595695
sme@gol
Gheu ?!?!?
Posté le 24-11-2004 à 22:05:53  profilanswer
 

C bien parceque c'est pour une slack va :D

n°595704
marcelp182
Plop
Posté le 24-11-2004 à 22:19:45  profilanswer
 

j'ai aussi essayer avec celles là
pareil  :pt1cable:

n°595710
sme@gol
Gheu ?!?!?
Posté le 24-11-2004 à 22:24:58  profilanswer
 

essaye en remplaçant ta section Graphics device section par celle ci :

Code :
  1. Section "Device"
  2.   Identifier "ATI Rage Mobility"
  3.   Driver "ati"
  4.   VendorName "ATI Rage Mobility"
  5.   BoardName "ATI Rage Mobility"
  6. EndSection


Message édité par sme@gol le 24-11-2004 à 22:27:21
n°595712
marcelp182
Plop
Posté le 24-11-2004 à 22:28:31  profilanswer
 

c'est pas une ati ma CG c une intel 82830M

n°595714
sme@gol
Gheu ?!?!?
Posté le 24-11-2004 à 22:29:37  profilanswer
 

ben g trouver cette page qui avait l'air de correspondre http://open.bsdcow.net/config/mach [...] itude-l400 t sur que c pas le chipset graphique de ta carte mère sa ?

n°595715
sme@gol
Gheu ?!?!?
Posté le 24-11-2004 à 22:32:14  profilanswer
 

trouvé.
 

Code :
  1. # DELL LATITUDE C400
  2. # Driver  "i810"  # Intel 82830M
  3. # VendorName "Intel Corp."
  4. # BoardName "82830 CGC [Chipset Graphics Controller]"
  5. # ChipSet  "i830M"
  6. ## VideoRam ?
  7. # Option  "NoAccel" # Sometimes would hungup with Accel
  8. # Option  "SWCursor" # Sometimes would hungup with HWCursor
  9. # BusID  "PCI:00:02:0"
  10. EndSection


 
y' interet a ce que sa marche  :D


Message édité par sme@gol le 24-11-2004 à 22:32:49
n°595716
marcelp182
Plop
Posté le 24-11-2004 à 22:33:32  profilanswer
 

jvais essayer
dans graphique device toujours?


Message édité par marcelp182 le 24-11-2004 à 22:34:46
n°595722
sme@gol
Gheu ?!?!?
Posté le 24-11-2004 à 22:40:14  profilanswer
 

toujours mais fait gaffe, il manque une ligne au début je vien de m'en apercevoir :

Code :
  1. Section "Device"
  2. Identifier "Card0"


 
et n'oubli pas de remplacer

Code :
  1. Device      "VESA Framebuffer"

par

Code :
  1. Device      "Card0"

dans # Screen sections

n°595725
marcelp182
Plop
Posté le 24-11-2004 à 22:49:31  profilanswer
 

franchement t trop fort  [:nekromanttik]  
ca marche nikel !!!!!
 
Merci beaucoup !
probleme resolu
 
tu peut me dire ou ta trouvé les infos ? merci  [:augie]  [:augie]  [:augie]  [:augie]
 
 [:zcoold]  [:zcoold]  [:fenston]  [:kahn21]  [:kahn21]  

n°595730
sme@gol
Gheu ?!?!?
Posté le 24-11-2004 à 22:52:56  profilanswer
 

google  :??:  
 
http://www.fenix.ne.jp/~G-HAL/comp/XF86Config
pour la partie qui a marché

n°595731
sme@gol
Gheu ?!?!?
Posté le 24-11-2004 à 22:53:44  profilanswer
 

et encore toi tu as eu de la chance, moi j'ai mis 6 mois pour les trouver mes valeurs HorizSync et VertRefresh  :fou:

n°595737
marcelp182
Plop
Posté le 24-11-2004 à 22:57:48  profilanswer
 

merci en tout cas :jap:

mood
Publicité
Posté le   profilanswer
 


Aller à :
Ajouter une réponse
  FORUM HardWare.fr
  Linux et OS Alternatifs
  Installation

  probleme installation slack 10 [résolu :jap:]

 

Sujets relatifs
Nagios : probleme de cgi[SHELL] help, probleme de pipe
Probleme chargement des modulesProbleme d'instalation de fedora core 3
Installation de mandrake 10.1? problèmeFC3 Probleme INSATLLATION
probleme son via sous mandrake 10.1[Mandrake 10.1 Off] Très long temps au démarage [Résolu]
probleme execution gimp 
Plus de sujets relatifs à : probleme installation slack 10 [résolu :jap:]


Copyright © 1997-2018 Hardware.fr SARL (Signaler un contenu illicite / Données personnelles) / Groupe LDLC / Shop HFR