logo Debian Debian Debian-France Debian-Facile Debian-fr.org Forum-Debian.fr Debian ? Communautés logo inclusivité

Debian-facile

Bienvenue sur Debian-Facile, site d'aide pour les nouveaux utilisateurs de Debian.

Vous n'êtes pas identifié(e).

Pages : 1 2 3 … 6

#1 Re : Système » problème au démarrage (initramfs) » 20-12-2022 15:17:31

Maud
J'ai fini par redémarrer après quelques counts défectueux. Par contre au redémarrage, le exim4 est noté à FAILED.

#2 Re : Système » problème au démarrage (initramfs) » 20-12-2022 15:16:27

Maud

fsck /dev/sda2


fsck from util-linux 2.36.1
e2fsck 1.46.2 (28_Feb_2021)
/dev/sda2 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Entry 'config.autogenerated' in /var/lib/exim4 (28053592) has an incorrect filetype (was 1, should be 2).
Fix<y>? yes
Invalid inode number for'.' in directory inode 28049983.
Fix<y>? yes
Entry 'state' in / var/lib/lightdm/.cache/lightdm-gtk-greeter (28049466) has delete/unused inode 28052918. Clear<y>? yes
Pass 3: Checking directory connectivity
'..' in /var/lib/exim4/config.autogenerated (28049983) is var/lib/lightdm/data (28049461), should be /var/lib/exim4 (28053592).
Fix<y>? yes
Pass 4: Checking reference counts
Unattached inode 28049573
Connect to /lost+found<y>? yes
Inode 28049573 ref count is 2, should be 1. Fix<y>? yes
Pass 5: Checking group summary information
Block bitmap differences:  +(300550--300575) -112231118 +112315404 -112766468
Fix<y>? yes

#3 Système » problème au démarrage (initramfs) » 18-12-2022 23:32:44

Maud
Réponses : 5
Bonjour,
Nous sommes 3 à utiliser le PC et après passage des enfants (qui disent n'avoir rien fait ni rien vu), voici ce que donne le démarrage du PC:

config.autogenerated in /var/lib/exim4 has an incorrect filetype (was1, should be 2)
/dev/sda: unexpected inconsistency; run fsck manually (i.e. without -a or -p options)
fsck exite with status code
The root filesystem on /dev/sda2 requires a manual fsck
BusyBox v1.30.1 (Debian1:1.30.1-6+b3)built-in shell (ash)
(initramfs)_


Alors j'ai bien compris qu'il y avait une erreur dans exim4, que du coup il n'y a pas moyen démarrer et qu'il attend de moi la combinaison gagnante sous forme de commande...
A part ça... Mes recherches donnent bien quelques résultats mais assez nébuleux et j'ai peur de faire plus de casse qu'autre chose en écrivant n'importe quoi.

Merci de votre aide.

#4 Re : Matériel » [résolu]problème résolution d'écran » 26-09-2022 20:11:19

Maud
Oui je suis bien en VGA.
Je viens de vérifier, j'ai trouvé l'hdmi coté écran mais comme il est lourd et pas très maniable avec le filtre acroché dessus, il va falloir que je bricole un peu. Côté carte mère elle y est je m'en suis déjà servie. Reste plus qu'à retrouver le câble. Merci en tout cas pour l'aide.

#5 Re : Matériel » [résolu]problème résolution d'écran » 22-09-2022 22:10:10

Maud
Le xrandr --prop est plus joli non?
Désoéle pour le dérangement et merci pour tout.

#6 Re : Matériel » [résolu]problème résolution d'écran » 22-09-2022 22:09:12

Maud
Bon bah ça y est, problème résolu d'un coup de baguette magique.
Suite à des manipulations de l'écran pour en savoir plus sur le modèle du moniteur, il y a eu plusieurs coupures de liaison avec le pc. Du coup j'ai redémarré pour avoir un dsmeg "intéressant".
Et bien l'écran était à la bonne résolution!!!:rolleyes:
Bon Merci quand même pour le temps passé à chercher un problème qui, a priori n'en était pas un (ou alors que de branchement). Si ça m'arrive à nouveau un jour, promis je commence par débrancher et rebrancher le moniteur...

xrandr --prop


Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 16384 x 16384
HDMI-1 disconnected primary (normal left inverted right x axis y axis)
  Content Protection: Undesired
    supported: Undesired, Desired, Enabled
  max bpc: 12
    range: (8, 12)
  content type: No Data
    supported: No Data, Graphics, Photo, Cinema, Game
  Colorspace: Default
    supported: Default, SMPTE_170M_YCC, BT709_YCC, XVYCC_601, XVYCC_709, SYCC_601, opYCC_601, opRGB, BT2020_CYCC, BT2020_RGB, BT2020_YCC, DCI-P3_RGB_D65, DCI-P3_RGB_Theater
  aspect ratio: Automatic
    supported: Automatic, 4:3, 16:9
  Broadcast RGB: Automatic
    supported: Automatic, Full, Limited 16:235
  audio: auto
    supported: force-dvi, off, auto, on
  link-status: Good
    supported: Good, Bad
  CONNECTOR_ID: 74
    supported: 74
  non-desktop: 0
    range: (0, 1)
DP-1 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 430mm x 270mm
  EDID:
    00ffffffffffff0022f0942601010101
    011201036e2b1b78eed105a655479d25
    155054adee808180b300b30f01010101
    01010101010121399030621a274068b0
    3600ae0e1100001c000000fd00324c18
    5d10000a202020202020000000fc0048
    50204c32303435770a202020000000ff
    00435a5438303130334e510a20200058
  Colorspace: Default
    supported: Default, RGB_Wide_Gamut_Fixed_Point, RGB_Wide_Gamut_Floating_Point, opRGB, DCI-P3_RGB_D65, BT2020_RGB, BT601_YCC, BT709_YCC, XVYCC_601, XVYCC_709, SYCC_601, opYCC_601, BT2020_CYCC, BT2020_YCC
  max bpc: 12
    range: (6, 12)
  Broadcast RGB: Automatic
    supported: Automatic, Full, Limited 16:235
  audio: auto
    supported: force-dvi, off, auto, on
  subconnector: VGA
    supported: Unknown, VGA, DVI-D, HDMI, DP, Wireless, Native
  link-status: Good
    supported: Good, Bad
  CONNECTOR_ID: 83
    supported: 83
  non-desktop: 0
    range: (0, 1)
   1680x1050     59.95*+
   1280x1024     60.02  
   1152x864      75.00  
   1024x768      75.03    70.07    60.00  
   832x624       74.55  
   800x600       72.19    75.00    60.32  
   640x480       75.00    72.81    59.94  
   720x400       70.08  

#7 Re : Matériel » [résolu]problème résolution d'écran » 22-09-2022 21:46:47

Maud
Bonjour,
MATE est bien mon environnement de travail. Mon moniteur est un vieil HP L2045w de décembre 2007.
Je suis en train de fouiller le dsmeg

#8 Re : Matériel » [résolu]problème résolution d'écran » 22-09-2022 21:24:22

Maud

xrandr --prop


Screen 0: minimum 320 x 200, current 1024 x 768, maximum 16384 x 16384
HDMI-1 disconnected (normal left inverted right x axis y axis)
  Content Protection: Undesired
    supported: Undesired, Desired, Enabled
  max bpc: 12
    range: (8, 12)
  content type: No Data
    supported: No Data, Graphics, Photo, Cinema, Game
  Colorspace: Default
    supported: Default, SMPTE_170M_YCC, BT709_YCC, XVYCC_601, XVYCC_709, SYCC_601, opYCC_601, opRGB, BT2020_CYCC, BT2020_RGB, BT2020_YCC, DCI-P3_RGB_D65, DCI-P3_RGB_Theater
  aspect ratio: Automatic
    supported: Automatic, 4:3, 16:9
  Broadcast RGB: Automatic
    supported: Automatic, Full, Limited 16:235
  audio: auto
    supported: force-dvi, off, auto, on
  link-status: Good
    supported: Good, Bad
  CONNECTOR_ID: 74
    supported: 74
  non-desktop: 0
    range: (0, 1)
DP-1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
  Colorspace: Default
    supported: Default, RGB_Wide_Gamut_Fixed_Point, RGB_Wide_Gamut_Floating_Point, opRGB, DCI-P3_RGB_D65, BT2020_RGB, BT601_YCC, BT709_YCC, XVYCC_601, XVYCC_709, SYCC_601, opYCC_601, BT2020_CYCC, BT2020_YCC
  max bpc: 12
    range: (6, 12)
  Broadcast RGB: Automatic
    supported: Automatic, Full, Limited 16:235
  audio: auto
    supported: force-dvi, off, auto, on
  subconnector: VGA
    supported: Unknown, VGA, DVI-D, HDMI, DP, Wireless, Native
  link-status: Good
    supported: Good, Bad
  CONNECTOR_ID: 83
    supported: 83
  non-desktop: 0
    range: (0, 1)
   1024x768      60.00*
   800x600       60.32    56.25  
   848x480       60.00  
   640x480       59.94

#9 Re : Matériel » [résolu]problème résolution d'écran » 22-09-2022 20:58:46

Maud

cat /var/log/Xorg.0.log


[    21.034]
X.Org X Server 1.20.11
X Protocol Version 11, Revision 0
[    21.034] Build Operating System: linux Debian
[    21.034] Current Operating System: Linux maud 5.10.0-18-amd64 #1 SMP Debian 5.10.140-1 (2022-09-02) x86_64
[    21.034] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-18-amd64 root=UUID=70faa44d-39d4-4fb3-a9b8-0e2bc65fa703 ro quiet
[    21.034] Build Date: 05 August 2022  08:00:36AM
[    21.034] xorg-server 2:1.20.11-1+deb11u2 (https://www.debian.org/support)
[    21.034] Current version of pixman: 0.40.0
[    21.034]  Before reporting problems, check http://wiki.x.org
  to make sure that you have the latest version.
[    21.034] Markers: (--) probed, (**) from config file, (==) default setting,
  (++) from command line, (!!) notice, (II) informational,
  (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    21.034] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Sep 22 21:49:27 2022
[    21.191] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    21.241] (==) No Layout section.  Using the first Screen section.
[    21.241] (==) No screen section available. Using defaults.
[    21.241] (**) |-->Screen "Default Screen Section" (0)
[    21.241] (**) |   |-->Monitor "<default monitor>"
[    21.242] (==) No monitor specified for screen "Default Screen Section".
  Using a default monitor configuration.
[    21.242] (==) Automatically adding devices
[    21.242] (==) Automatically enabling devices
[    21.242] (==) Automatically adding GPU devices
[    21.242] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    21.273] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[    21.273]  Entry deleted from font path.
[    21.370] (==) FontPath set to:
  /usr/share/fonts/X11/misc,
  /usr/share/fonts/X11/100dpi/:unscaled,
  /usr/share/fonts/X11/75dpi/:unscaled,
  /usr/share/fonts/X11/Type1,
  /usr/share/fonts/X11/100dpi,
  /usr/share/fonts/X11/75dpi,
  built-ins
[    21.370] (==) ModulePath set to "/usr/lib/xorg/modules"
[    21.370] (II) The server relies on udev to provide the list of input devices.
  If no devices become available, reconfigure udev or disable AutoAddDevices.
[    21.370] (II) Loader magic: 0x560948d96e40
[    21.370] (II) Module ABI versions:
[    21.370]  X.Org ANSI C Emulation: 0.4
[    21.370]  X.Org Video Driver: 24.1
[    21.370]  X.Org XInput driver : 24.1
[    21.370]  X.Org Server Extension : 10.0
[    21.372] (++) using VT number 7

[    21.372] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[    21.374] (II) xfree86: Adding drm device (/dev/dri/card0)
[    21.384] (--) PCI:*(0@0:2:0) 8086:1902:1043:8694 rev 6, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, I/O @ 0x0000f000/64, BIOS @ 0x????????/131072
[    21.386] (II) LoadModule: "glx"
[    21.388] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    21.608] (II) Module glx: vendor="X.Org Foundation"
[    21.609]  compiled for 1.20.11, module version = 1.0.0
[    21.609]  ABI class: X.Org Server Extension, version 10.0
[    21.609] (==) Matched modesetting as autoconfigured driver 0
[    21.609] (==) Matched fbdev as autoconfigured driver 1
[    21.609] (==) Matched vesa as autoconfigured driver 2
[    21.609] (==) Assigned the driver to the xf86ConfigLayout
[    21.609] (II) LoadModule: "modesetting"
[    21.609] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[    21.676] (II) Module modesetting: vendor="X.Org Foundation"
[    21.676]  compiled for 1.20.11, module version = 1.20.11
[    21.676]  Module class: X.Org Video Driver
[    21.676]  ABI class: X.Org Video Driver, version 24.1
[    21.676] (II) LoadModule: "fbdev"
[    21.677] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[    21.709] (II) Module fbdev: vendor="X.Org Foundation"
[    21.709]  compiled for 1.20.0, module version = 0.5.0
[    21.709]  Module class: X.Org Video Driver
[    21.709]  ABI class: X.Org Video Driver, version 24.0
[    21.709] (II) LoadModule: "vesa"
[    21.709] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[    21.725] (II) Module vesa: vendor="X.Org Foundation"
[    21.725]  compiled for 1.20.9, module version = 2.5.0
[    21.725]  Module class: X.Org Video Driver
[    21.725]  ABI class: X.Org Video Driver, version 24.1
[    21.725] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    21.725] (II) FBDEV: driver for framebuffer: fbdev
[    21.725] (II) VESA: driver for VESA chipsets: vesa
[    21.762] (II) modeset(0): using drv /dev/dri/card0
[    21.762] (WW) Falling back to old probe method for fbdev
[    21.762] (II) Loading sub module "fbdevhw"
[    21.762] (II) LoadModule: "fbdevhw"
[    21.762] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[    21.767] (II) Module fbdevhw: vendor="X.Org Foundation"
[    21.767]  compiled for 1.20.11, module version = 0.0.2
[    21.767]  ABI class: X.Org Video Driver, version 24.1
[    21.768] (II) modeset(0): Creating default Display subsection in Screen section
  "Default Screen Section" for depth/fbbpp 24/32
[    21.768] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
[    21.768] (==) modeset(0): RGB weight 888
[    21.768] (==) modeset(0): Default visual is TrueColor
[    21.768] (II) Loading sub module "glamoregl"
[    21.768] (II) LoadModule: "glamoregl"
[    21.768] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[    21.819] (II) Module glamoregl: vendor="X.Org Foundation"
[    21.820]  compiled for 1.20.11, module version = 1.0.1
[    21.820]  ABI class: X.Org ANSI C Emulation, version 0.4
[    24.603] (II) modeset(0): glamor X acceleration enabled on Mesa Intel(R) HD Graphics 510 (SKL GT1)
[    24.603] (II) modeset(0): glamor initialized
[    24.607] (II) modeset(0): Output HDMI-1 has no monitor section
[    24.617] (II) modeset(0): Output DP-1 has no monitor section
[    24.621] (II) modeset(0): EDID for output HDMI-1
[    24.631] (II) modeset(0): EDID for output DP-1
[    24.631] (II) modeset(0): Printing probed modes for output DP-1
[    24.631] (II) modeset(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[    24.631] (II) modeset(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[    24.632] (II) modeset(0): Modeline "800x600"x56.2   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz e)
[    24.632] (II) modeset(0): Modeline "848x480"x60.0   33.75  848 864 976 1088  480 486 494 517 +hsync +vsync (31.0 kHz e)
[    24.632] (II) modeset(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[    24.632] (II) modeset(0): Output HDMI-1 disconnected
[    24.632] (II) modeset(0): Output DP-1 connected
[    24.632] (II) modeset(0): Using exact sizes for initial modes
[    24.632] (II) modeset(0): Output DP-1 using initial mode 1024x768 +0+0
[    24.632] (==) modeset(0): Using gamma correction (1.0, 1.0, 1.0)
[    24.632] (==) modeset(0): DPI set to (96, 96)
[    24.632] (II) Loading sub module "fb"
[    24.632] (II) LoadModule: "fb"
[    24.632] (II) Loading /usr/lib/xorg/modules/libfb.so
[    24.666] (II) Module fb: vendor="X.Org Foundation"
[    24.666]  compiled for 1.20.11, module version = 1.0.0
[    24.666]  ABI class: X.Org ANSI C Emulation, version 0.4
[    24.666] (II) UnloadModule: "fbdev"
[    24.666] (II) Unloading fbdev
[    24.666] (II) UnloadSubModule: "fbdevhw"
[    24.666] (II) Unloading fbdevhw
[    24.666] (II) UnloadModule: "vesa"
[    24.666] (II) Unloading vesa
[    25.169] (==) modeset(0): Backing store enabled
[    25.169] (==) modeset(0): Silken mouse enabled
[    25.245] (II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
[    25.245] (==) modeset(0): DPMS enabled
[    25.261] (II) modeset(0): [DRI2] Setup complete
[    25.261] (II) modeset(0): [DRI2]   DRI driver: iris
[    25.261] (II) modeset(0): [DRI2]   VDPAU driver: va_gl
[    25.261] (II) Initializing extension Generic Event Extension
[    25.261] (II) Initializing extension SHAPE
[    25.262] (II) Initializing extension MIT-SHM
[    25.262] (II) Initializing extension XInputExtension
[    25.293] (II) Initializing extension XTEST
[    25.294] (II) Initializing extension BIG-REQUESTS
[    25.294] (II) Initializing extension SYNC
[    25.295] (II) Initializing extension XKEYBOARD
[    25.295] (II) Initializing extension XC-MISC
[    25.295] (II) Initializing extension SECURITY
[    25.296] (II) Initializing extension XFIXES
[    25.296] (II) Initializing extension RENDER
[    25.297] (II) Initializing extension RANDR
[    25.297] (II) Initializing extension COMPOSITE
[    25.298] (II) Initializing extension DAMAGE
[    25.298] (II) Initializing extension MIT-SCREEN-SAVER
[    25.299] (II) Initializing extension DOUBLE-BUFFER
[    25.299] (II) Initializing extension RECORD
[    25.300] (II) Initializing extension DPMS
[    25.300] (II) Initializing extension Present
[    25.300] (II) Initializing extension DRI3
[    25.301] (II) Initializing extension X-Resource
[    25.301] (II) Initializing extension XVideo
[    25.302] (II) Initializing extension XVideo-MotionCompensation
[    25.302] (II) Initializing extension SELinux
[    25.302] (II) SELinux: Disabled on system
[    25.302] (II) Initializing extension GLX
[    25.326] (II) AIGLX: Loaded and initialized iris
[    25.326] (II) GLX: Initialized DRI2 GL provider for screen 0
[    25.326] (II) Initializing extension XFree86-VidModeExtension
[    25.326] (II) Initializing extension XFree86-DGA
[    25.326] (II) Initializing extension XFree86-DRI
[    25.326] (II) Initializing extension DRI2
[    25.427] (II) modeset(0): Damage tracking initialized
[    25.427] (II) modeset(0): Setting screen physical size to 270 x 203
[    26.110] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[    26.110] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[    26.110] (II) LoadModule: "libinput"
[    26.129] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[    26.211] (II) Module libinput: vendor="X.Org Foundation"
[    26.211]  compiled for 1.20.8, module version = 0.30.0
[    26.211]  Module class: X.Org XInput Driver
[    26.211]  ABI class: X.Org XInput driver, version 24.1
[    26.211] (II) Using input driver 'libinput' for 'Power Button'
[    26.211] (**) Power Button: always reports core events
[    26.211] (**) Option "Device" "/dev/input/event2"
[    26.212] (**) Option "_source" "server/udev"
[    26.258] (II) event2  - Power Button: is tagged by udev as: Keyboard
[    26.258] (II) event2  - Power Button: device is a keyboard
[    26.258] (II) event2  - Power Button: device removed
[    26.274] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event2"
[    26.274] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[    26.274] (**) Option "xkb_model" "pc105"
[    26.274] (**) Option "xkb_layout" "fr"
[    26.274] (**) Option "xkb_variant" "latin9"
[    26.337] (II) event2  - Power Button: is tagged by udev as: Keyboard
[    26.337] (II) event2  - Power Button: device is a keyboard
[    26.338] (II) config/udev: Adding input device Video Bus (/dev/input/event3)
[    26.338] (**) Video Bus: Applying InputClass "libinput keyboard catchall"
[    26.338] (II) Using input driver 'libinput' for 'Video Bus'
[    26.338] (**) Video Bus: always reports core events
[    26.338] (**) Option "Device" "/dev/input/event3"
[    26.338] (**) Option "_source" "server/udev"
[    26.341] (II) event3  - Video Bus: is tagged by udev as: Keyboard
[    26.341] (II) event3  - Video Bus: device is a keyboard
[    26.341] (II) event3  - Video Bus: device removed
[    26.370] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6/event3"
[    26.370] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[    26.370] (**) Option "xkb_model" "pc105"
[    26.370] (**) Option "xkb_layout" "fr"
[    26.370] (**) Option "xkb_variant" "latin9"
[    26.373] (II) event3  - Video Bus: is tagged by udev as: Keyboard
[    26.373] (II) event3  - Video Bus: device is a keyboard
[    26.374] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[    26.374] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[    26.374] (II) Using input driver 'libinput' for 'Power Button'
[    26.374] (**) Power Button: always reports core events
[    26.374] (**) Option "Device" "/dev/input/event1"
[    26.374] (**) Option "_source" "server/udev"
[    26.377] (II) event1  - Power Button: is tagged by udev as: Keyboard
[    26.377] (II) event1  - Power Button: device is a keyboard
[    26.377] (II) event1  - Power Button: device removed
[    26.398] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3/event1"
[    26.398] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
[    26.398] (**) Option "xkb_model" "pc105"
[    26.398] (**) Option "xkb_layout" "fr"
[    26.398] (**) Option "xkb_variant" "latin9"
[    26.403] (II) event1  - Power Button: is tagged by udev as: Keyboard
[    26.403] (II) event1  - Power Button: device is a keyboard
[    26.405] (II) config/udev: Adding input device Sleep Button (/dev/input/event0)
[    26.405] (**) Sleep Button: Applying InputClass "libinput keyboard catchall"
[    26.405] (II) Using input driver 'libinput' for 'Sleep Button'
[    26.405] (**) Sleep Button: always reports core events
[    26.405] (**) Option "Device" "/dev/input/event0"
[    26.406] (**) Option "_source" "server/udev"
[    26.409] (II) event0  - Sleep Button: is tagged by udev as: Keyboard
[    26.410] (II) event0  - Sleep Button: device is a keyboard
[    26.410] (II) event0  - Sleep Button: device removed
[    26.430] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2/event0"
[    26.430] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 9)
[    26.430] (**) Option "xkb_model" "pc105"
[    26.430] (**) Option "xkb_layout" "fr"
[    26.430] (**) Option "xkb_variant" "latin9"
[    26.435] (II) event0  - Sleep Button: is tagged by udev as: Keyboard
[    26.435] (II) event0  - Sleep Button: device is a keyboard
[    26.439] (II) config/udev: Adding input device Dell Dell USB Keyboard (/dev/input/event4)
[    26.440] (**) Dell Dell USB Keyboard: Applying InputClass "libinput keyboard catchall"
[    26.440] (II) Using input driver 'libinput' for 'Dell Dell USB Keyboard'
[    26.440] (**) Dell Dell USB Keyboard: always reports core events
[    26.440] (**) Option "Device" "/dev/input/event4"
[    26.440] (**) Option "_source" "server/udev"
[    26.446] (II) event4  - Dell Dell USB Keyboard: is tagged by udev as: Keyboard
[    26.446] (II) event4  - Dell Dell USB Keyboard: device is a keyboard
[    26.447] (II) event4  - Dell Dell USB Keyboard: device removed
[    26.470] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/0003:413C:2105.0001/input/input7/event4"
[    26.470] (II) XINPUT: Adding extended input device "Dell Dell USB Keyboard" (type: KEYBOARD, id 10)
[    26.470] (**) Option "xkb_model" "pc105"
[    26.470] (**) Option "xkb_layout" "fr"
[    26.470] (**) Option "xkb_variant" "latin9"
[    26.477] (II) event4  - Dell Dell USB Keyboard: is tagged by udev as: Keyboard
[    26.477] (II) event4  - Dell Dell USB Keyboard: device is a keyboard
[    26.481] (II) config/udev: Adding input device Logitech USB Trackball (/dev/input/event5)
[    26.481] (**) Logitech USB Trackball: Applying InputClass "libinput pointer catchall"
[    26.481] (II) Using input driver 'libinput' for 'Logitech USB Trackball'
[    26.481] (**) Logitech USB Trackball: always reports core events
[    26.481] (**) Option "Device" "/dev/input/event5"
[    26.481] (**) Option "_source" "server/udev"
[    26.547] (II) event5  - Logitech USB Trackball: is tagged by udev as: Mouse Trackball
[    26.548] (II) event5  - Logitech USB Trackball: device is a pointer
[    26.548] (II) event5  - Logitech USB Trackball: device removed
[    26.586] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6:1.0/0003:046D:C408.0002/input/input8/event5"
[    26.586] (II) XINPUT: Adding extended input device "Logitech USB Trackball" (type: MOUSE, id 11)
[    26.587] (**) Option "AccelerationScheme" "none"
[    26.587] (**) Logitech USB Trackball: (accel) selected scheme none/0
[    26.587] (**) Logitech USB Trackball: (accel) acceleration factor: 2.000
[    26.587] (**) Logitech USB Trackball: (accel) acceleration threshold: 4
[    26.650] (II) event5  - Logitech USB Trackball: is tagged by udev as: Mouse Trackball
[    26.653] (II) event5  - Logitech USB Trackball: device is a pointer
[    26.655] (II) config/udev: Adding input device Logitech USB Trackball (/dev/input/mouse0)
[    26.655] (II) No input driver specified, ignoring this device.
[    26.655] (II) This device may have been added with another device file.
[    26.656] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event8)
[    26.656] (II) No input driver specified, ignoring this device.
[    26.656] (II) This device may have been added with another device file.
[    26.660] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event9)
[    26.660] (II) No input driver specified, ignoring this device.
[    26.660] (II) This device may have been added with another device file.
[    26.663] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event10)
[    26.663] (II) No input driver specified, ignoring this device.
[    26.663] (II) This device may have been added with another device file.
[    26.665] (II) config/udev: Adding input device HDA Intel PCH Line Out (/dev/input/event11)
[    26.665] (II) No input driver specified, ignoring this device.
[    26.665] (II) This device may have been added with another device file.
[    26.666] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event12)
[    26.666] (II) No input driver specified, ignoring this device.
[    26.666] (II) This device may have been added with another device file.
[    26.667] (II) config/udev: Adding input device Eee PC WMI hotkeys (/dev/input/event7)
[    26.667] (**) Eee PC WMI hotkeys: Applying InputClass "libinput keyboard catchall"
[    26.667] (II) Using input driver 'libinput' for 'Eee PC WMI hotkeys'
[    26.667] (**) Eee PC WMI hotkeys: always reports core events
[    26.667] (**) Option "Device" "/dev/input/event7"
[    26.667] (**) Option "_source" "server/udev"
[    26.669] (II) event7  - Eee PC WMI hotkeys: is tagged by udev as: Keyboard
[    26.669] (II) event7  - Eee PC WMI hotkeys: device is a keyboard
[    26.669] (II) event7  - Eee PC WMI hotkeys: device removed
[    26.690] (**) Option "config_info" "udev:/sys/devices/platform/eeepc-wmi/input/input10/event7"
[    26.690] (II) XINPUT: Adding extended input device "Eee PC WMI hotkeys" (type: KEYBOARD, id 12)
[    26.690] (**) Option "xkb_model" "pc105"
[    26.690] (**) Option "xkb_layout" "fr"
[    26.690] (**) Option "xkb_variant" "latin9"
[    26.694] (II) event7  - Eee PC WMI hotkeys: is tagged by udev as: Keyboard
[    26.695] (II) event7  - Eee PC WMI hotkeys: device is a keyboard
[    26.697] (II) config/udev: Adding input device PC Speaker (/dev/input/event6)
[    26.697] (II) No input driver specified, ignoring this device.
[    26.697] (II) This device may have been added with another device file.

#10 Re : Matériel » [résolu]problème résolution d'écran » 22-09-2022 20:48:19

Maud

lspci -nnkd ::300


00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 510 [8086:1902] (rev 06)
  DeviceName:  Onboard IGD
  Subsystem: ASUSTeK Computer Inc. HD Graphics 510 [1043:8694]
  Kernel driver in use: i915
  Kernel modules: i915
 

#11 Re : Matériel » [résolu]problème résolution d'écran » 21-09-2022 13:33:22

Maud
Bonjour,
Merci pour l'aide. J'ai fait tout ce que tu m'as dit (modifs dans les sources.list, installation de firmware-realtek firmware-misc-nonfree intel-microcode, un petit update, redémarrage). Et mon écran est encore en mode vieille résolution comme si j'avais soudainement besoin de voir tout en gros... Voici quelques résultats après redémarrage.

apt update


Atteint :1 http://deb.debian.org/debian bullseye InRelease
Atteint :2 http://deb.debian.org/debian-security bullseye-security InRelease
Atteint :3 http://deb.debian.org/debian bullseye-updates InRelease
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances... Fait
Lecture des informations d'état... Fait      
Tous les paquets sont à jour.
root@maud:/home/maud#



journalctl -b -r -p err


-- Journal begins at Sun 2022-02-06 10:24:51 CET, ends at Wed 2022-09-21 14:21:57 CEST. --
sept. 21 14:13:23 maud pipewire[1008]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.>
sept. 21 14:13:23 maud pulseaudio[949]: Error opening PCM device front:0: Aucun fichier ou dossier de ce type
sept. 21 14:13:22 maud lightdm[988]: gkr-pam: unable to locate daemon control file
sept. 21 14:13:11 maud pipewire[948]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.f>
sept. 21 14:12:59 maud avahi-daemon[536]: chroot.c: open() failed: No such file or directory
sept. 21 14:12:48 maud kernel: x86/cpu: VMX (outside TXT) disabled by BIOS
 

#12 Re : Matériel » [résolu]problème résolution d'écran » 20-09-2022 20:29:22

Maud
Bonjour,
Merci pour ta réponse, j'ai tout indiqué ci-dessous. Par contre j'ai fait un upgrate suite à l'apparition du problème. La version qui était avant, je ne m'en souviens plus.

#13 Re : Matériel » [résolu]problème résolution d'écran » 20-09-2022 20:27:44

Maud

cat /etc/apt/sources.list


#deb http://ftp.fr.debian.org/debian/ bullseye main
#deb-src http://ftp.fr.debian.org/debian/ bullseye main

#deb http://security.debian.org/debian-security bullseye-security main
#deb-src http://security.debian.org/debian-security bullseye-security main

# bullseye-updates, previously known as 'volatile'
#deb http://ftp.fr.debian.org/debian/ bullseye-updates main
#deb-src http://ftp.fr.debian.org/debian/ bullseye-updates main


# Debian bullseye, dépôt principal
deb http://deb.debian.org/debian/ bullseye main
deb-src http://deb.debian.org/debian/ bullseye main
     
# Debian bullseye, mises à jour de sécurité
deb http://deb.debian.org/debian-security/ bullseye-security main
deb-src http://deb.debian.org/debian-security/ bullseye-security main
     
# Debian bullseye, mises à jour "volatiles"
deb http://deb.debian.org/debian/ bullseye-updates main
deb-src http://deb.debian.org/debian/ bullseye-updates main
 

#14 Re : Matériel » [résolu]problème résolution d'écran » 20-09-2022 20:26:47

Maud

uname -a


Linux maud 5.10.0-9-amd64 #1 SMP Debian 5.10.70-1 (2021-09-30) x86_64 GNU/Linux
 



cat /etc/os-release


PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

#15 Re : Matériel » [résolu]problème résolution d'écran » 20-09-2022 20:23:27

Maud

 


-- Journal begins at Sun 2022-02-06 10:24:51 CET, ends at Tue 2022-09-20 21:17:26 CEST. --
sept. 20 21:05:08 maud pipewire[1006]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org>
sept. 20 21:05:07 maud lightdm[986]: gkr-pam: unable to locate daemon control file
sept. 20 21:04:55 maud pipewire[946]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.>
sept. 20 21:04:46 maud kernel: r8169 0000:02:00.0: Unable to load firmware rtl_nic/rtl8168h-2.fw (-2)
sept. 20 21:04:46 maud kernel: r8169 0000:02:00.0: firmware: failed to load rtl_nic/rtl8168h-2.fw (-2)
sept. 20 21:04:43 maud avahi-daemon[514]: chroot.c: open() failed: No such file or directory
sept. 20 21:04:31 maud kernel: firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware
sept. 20 21:04:31 maud kernel: i915 0000:00:02.0: firmware: failed to load i915/skl_dmc_ver1_27.bin (-2)
sept. 20 21:04:31 maud kernel: x86/cpu: VMX (outside TXT) disabled by BIOS
sept. 20 21:04:31 maud kernel: [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0xb2 (or later)
 

#16 Re : Matériel » [résolu]problème résolution d'écran » 20-09-2022 20:17:07

Maud

lspci


00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 07)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 510 (rev 06)
00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31)
00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 (rev 31)
00:17.0 SATA controller: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] (rev 31)
00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #5 (rev f1)
00:1c.7 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #8 (rev f1)
00:1d.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #9 (rev f1)
00:1f.0 ISA bridge: Intel Corporation H110 Chipset LPC/eSPI Controller (rev 31)
00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller (rev 31)
00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller (rev 31)
00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus (rev 31)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)

#17 Re : Matériel » [résolu]problème résolution d'écran » 19-09-2022 20:59:24

Maud

xrandr --prop


Screen 0: minimum 320 x 200, current 1024 x 768, maximum 16384 x 16384
HDMI-1 disconnected (normal left inverted right x axis y axis)
  Content Protection: Undesired
    supported: Undesired, Desired, Enabled
  max bpc: 12
    range: (8, 12)
  content type: No Data
    supported: No Data, Graphics, Photo, Cinema, Game
  Colorspace: Default
    supported: Default, SMPTE_170M_YCC, BT709_YCC, XVYCC_601, XVYCC_709, SYCC_601, opYCC_601, opRGB, BT2020_CYCC, BT2020_RGB, BT2020_YCC, DCI-P3_RGB_D65, DCI-P3_RGB_Theater
  aspect ratio: Automatic
    supported: Automatic, 4:3, 16:9
  Broadcast RGB: Automatic
    supported: Automatic, Full, Limited 16:235
  audio: auto
    supported: force-dvi, off, auto, on
  link-status: Good
    supported: Good, Bad
  CONNECTOR_ID: 74
    supported: 74
  non-desktop: 0
    range: (0, 1)
DP-1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
  Colorspace: Default
    supported: Default, RGB_Wide_Gamut_Fixed_Point, RGB_Wide_Gamut_Floating_Point, opRGB, DCI-P3_RGB_D65, BT2020_RGB, BT601_YCC, BT709_YCC, XVYCC_601, XVYCC_709, SYCC_601, opYCC_601, BT2020_CYCC, BT2020_YCC
  max bpc: 12
    range: (6, 12)
  Broadcast RGB: Automatic
    supported: Automatic, Full, Limited 16:235
  audio: auto
    supported: force-dvi, off, auto, on
  subconnector: VGA
    supported: Unknown, VGA, DVI-D, HDMI, DP, Wireless, Native
  link-status: Good
    supported: Good, Bad
  CONNECTOR_ID: 83
    supported: 83
  non-desktop: 0
    range: (0, 1)
   1024x768      60.00*
   800x600       60.32    56.25  
   848x480       60.00  
   640x480       59.94  
 

#18 Matériel » [résolu]problème résolution d'écran » 19-09-2022 20:50:37

Maud
Réponses : 22
Bonjour,
Suite à un redémarrage de mon pc, j'ai une résolution d'écran toute pourrie.
Sauf que quand je regarde la résolution d'écran, elle est notée à 1024x768 sans possililité de l'améliorer en manuel.

Alors j'ai fait un

xrandr


Screen 0: minimum 320 x 200, current 1024 x 768, maximum 16384 x 16384
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1024x768      60.00*
   800x600       60.32    56.25  
   848x480       60.00  
   640x480       59.94  



Mais après, je ne sais pas quoi en faire. Et j'ai tellement une résolution pourrie que j'ai l'impression d'être en mode sans échec de windows c'est pour dire! Mais il a apparemment perdu celle qu'il avait avant puisqu'il ne m'en  propose pas de meilleure. Et pourquoi la résolution d'écran a t'elle changé soudainement? Problème électrique? Bizarre... Ce pourrait-il que ma carte graphique ait morflé?
Merci pour votre aide.

#19 Matériel » imprimante canon pixma mg3650 non reconnue en wifi » 01-12-2021 23:40:30

Maud
Réponses : 1
Bonjour,
On vient de me filer une canon mg3650 que j'aimerai rajouter en wifi (j'ai déjà une samsung installée en local aavec cups). Le problème est que cups ne voit absolument pas d'imprimante wifi en plus de ma samsung qui est aussi reconnue en wifi en plus d'en local...
C'est comme si le signal wifi de l'imprimante n'existait pas...
Merci de votre aide.

#20 Re : Système » [résolu] ne boot plus après coupure de courant » 16-08-2021 23:11:48

Maud
redémarrage ok. Reste plusqu'à sauvegarder et penser à commander un dd pour au cas où...
Merci beaucoup.

#21 Re : Système » [résolu] ne boot plus après coupure de courant » 16-08-2021 23:11:02

Maud

e2fsck  /dev/sda2


e2fsck 1.44.5 (15-Dec-2018)
/dev/sda2: clean, 437034/60768256 files, 43118353/243043328 blocks



Tout est ok donc.

#22 Re : Système » [résolu] ne boot plus après coupure de courant » 16-08-2021 23:09:21

Maud

e2fsck -f /dev/sda2


e2fsck 1.44.5 (15-Dec-2018)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda2: 437034/60768256 files (0.8% non-contiguous), 43118353/243043328 blocks

#23 Re : Système » [résolu] ne boot plus après coupure de courant » 16-08-2021 22:09:21

Maud
je relance pour voir

#24 Re : Système » [résolu] ne boot plus après coupure de courant » 16-08-2021 22:07:05

Maud
Ca me donne ça à la fin.

 


/dev/sda2: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda2: 437034/60768256 files (0.8% non-contiguous), 43118353/243043328 blocks

#25 Re : Système » [résolu] ne boot plus après coupure de courant » 16-08-2021 22:04:43

Maud
Bon je ne met pas le résultat de tout parce que j'utiliserais tout le quota mémoire du site... Non mais blague à part, il me dit que tout est fixé après ma commande.

Pages : 1 2 3 … 6

Pied de page des forums

Propulsé par FluxBB