[solved]no keyboard/mouse after xorg-xinit upgrade (startxfce4 broken)
Today's upgrade and subsequent downgrade (with testing repos disabled)
[root@KISE-005 ~]# cat /var/log/pacman.log | grep 2015-03-17 | grep upgraded
[2015-03-17 09:54] [ALPM] upgraded conky (1.9.0-4 -> 1.9.0-5)
[2015-03-17 09:54] [ALPM] upgraded gsfonts (20130917-1 -> 20150122-1)
[2015-03-17 09:54] [ALPM] upgraded libmatekbd (1.8.0-1 -> 1.8.1-1)
[2015-03-17 09:54] [ALPM] upgraded libvdpau (1.0-1 -> 1.1-1)
[2015-03-17 09:54] [ALPM] upgraded mate-desktop (1.8.1-2 -> 1.8.2-1)
[2015-03-17 09:54] [ALPM] upgraded marco (1.8.2-4 -> 1.8.3-1)
[2015-03-17 09:54] [ALPM] upgraded mate-settings-daemon-gstreamer (1.8.2-3 -> 1.8.3-1)
[2015-03-17 09:54] [ALPM] upgraded python-setuptools (1:14.1.1-1 -> 1:14.3-1)
[2015-03-17 09:54] [ALPM] upgraded python2-setuptools (1:14.1.1-1 -> 1:14.3-1)
[2015-03-17 09:54] [ALPM] upgraded vim-runtime (7.4.617-1 -> 7.4.663-1)
[2015-03-17 09:54] [ALPM] upgraded vim (7.4.617-1 -> 7.4.663-1)
[2015-03-17 09:54] [ALPM] upgraded xdg-utils (1.1.0.git20141009-1 -> 1.1.0.git20150302-1)
[2015-03-17 09:54] [ALPM] upgraded xorg-xinit (1.3.4-1 -> 1.3.4-2)
[2015-03-17 09:56] [ALPM] upgraded insync (1.1.5-1 -> 1.2.1-1)
[2015-03-17 09:59] [ALPM] upgraded ttf-google-fonts-git (20140805-1 -> 20150316-1)
[root@KISE-005 ~]# cat /var/log/pacman.log | grep 2015-03-17 | grep downgraded
[2015-03-17 10:56] [ALPM] downgraded libutil-linux (2.26.1-3 -> 2.25.2-1)
[2015-03-17 10:56] [ALPM] downgraded libsystemd (219-3 -> 218-2)
[2015-03-17 10:56] [ALPM] downgraded shadow (4.2.1-3 -> 4.2.1-2)
[2015-03-17 10:56] [ALPM] downgraded util-linux (2.26.1-3 -> 2.25.2-1)
[2015-03-17 10:56] [ALPM] downgraded systemd (219-3 -> 218-2)
[2015-03-17 10:56] [ALPM] downgraded libcups (2.0.2-2 -> 2.0.2-1)
[2015-03-17 10:56] [ALPM] downgraded cups (2.0.2-2 -> 2.0.2-1)
[2015-03-17 10:56] [ALPM] downgraded libssh2 (1.5.0-1 -> 1.4.3-2)
[2015-03-17 10:56] [ALPM] downgraded lib32-libssh2 (1.5.0-1 -> 1.4.3-2)
[2015-03-17 10:56] [ALPM] downgraded lib32-libx11 (1.6.3-1 -> 1.6.2-1)
[2015-03-17 10:56] [ALPM] downgraded lib32-util-linux (2.26-1 -> 2.25.2-1)
[2015-03-17 10:57] [ALPM] downgraded linux (3.19.1-1 -> 3.18.6-1)
[2015-03-17 10:57] [ALPM] downgraded nvidia (346.47-9 -> 346.47-3)
[2015-03-17 10:57] [ALPM] downgraded systemd-sysvcompat (219-3 -> 218-2)
[2015-03-17 10:57] [ALPM] downgraded vim-runtime (7.4.663-1 -> 7.4.617-1)
[2015-03-17 10:57] [ALPM] downgraded vim (7.4.663-1 -> 7.4.617-1)
[2015-03-17 10:57] [ALPM] downgraded xdg-utils (1.1.0.git20150302-1 -> 1.1.0.git20141009-1)
[2015-03-17 10:57] [ALPM] downgraded xorg-xinit (1.3.4-2 -> 1.3.4-1)
After upgrade the keyboard and mouse were unresponsive. Restored by downgrading with testing repos disabled.
Also upgraded today with testing repos enabled was i686 and no anomalies detected.
Xorg.0.log for failed boot is here http://pastebin.com/aarDvve2
Last edited by keepitsimpleengineer (2015-03-24 19:30:45)
hello ,
after an upgrade yesterday , it is not possible to launch xfce4 on tty , when i do startxfce4 , i had this error :
xinit giving up
xinit unable to connect to x server ..................
xinit server error
this my xorg log :
[ 198.530]
X.Org X Server 1.17.1
Release Date: 2015-02-10
[ 198.536] X Protocol Version 11, Revision 0
[ 198.538] Build Operating System: Linux 3.18.6-1-ARCH i686
[ 198.540] Current Operating System: Linux eternity 3.14.36-1-lts #1 SMP Wed Mar 18 18:32:14 CET 2015 i686
[ 198.541] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux-lts root=UUID=b52f032b-9579-4da9-9a9b-d15b4dd7e565 rw quiet
[ 198.545] Build Date: 14 March 2015 06:47:44PM
[ 198.547]
[ 198.550] Current version of pixman: 0.32.6
[ 198.554] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 198.554] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 198.564] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Mar 23 10:03:55 2015
[ 198.567] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 198.567] (==) No Layout section. Using the first Screen section.
[ 198.567] (==) No screen section available. Using defaults.
[ 198.567] (**) |-->Screen "Default Screen Section" (0)
[ 198.567] (**) | |-->Monitor "<default monitor>"
[ 198.568] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 198.568] (==) Automatically adding devices
[ 198.568] (==) Automatically enabling devices
[ 198.568] (==) Automatically adding GPU devices
[ 198.568] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/OTF/".
[ 198.568] Entry deleted from font path.
[ 198.568] (Run 'mkfontdir' on "/usr/share/fonts/OTF/").
[ 198.568] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 198.568] Entry deleted from font path.
[ 198.568] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 198.568] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 198.568] Entry deleted from font path.
[ 198.568] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 198.568] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/
[ 198.568] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 198.568] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 198.568] (II) Loader magic: 0x829e700
[ 198.568] (II) Module ABI versions:
[ 198.568] X.Org ANSI C Emulation: 0.4
[ 198.568] X.Org Video Driver: 19.0
[ 198.568] X.Org XInput driver : 21.0
[ 198.568] X.Org Server Extension : 9.0
[ 198.570] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c1
[ 198.571] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 198.571] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 8 paused 0
[ 198.573] (--) PCI:*(0:1:5:0) 1002:5a62:1043:1402 rev 0, Mem @ 0xa0000000/268435456, 0xfa8f0000/65536, I/O @ 0x00009800/256, BIOS @ 0x????????/131072
[ 198.573] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 198.573] (II) LoadModule: "glx"
[ 198.574] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 198.576] (II) Module glx: vendor="X.Org Foundation"
[ 198.576] compiled for 1.17.1, module version = 1.0.0
[ 198.576] ABI class: X.Org Server Extension, version 9.0
[ 198.576] (==) AIGLX enabled
[ 198.576] (==) Matched ati as autoconfigured driver 0
[ 198.576] (==) Matched ati as autoconfigured driver 1
[ 198.576] (==) Matched modesetting as autoconfigured driver 2
[ 198.576] (==) Matched fbdev as autoconfigured driver 3
[ 198.576] (==) Matched vesa as autoconfigured driver 4
[ 198.576] (==) Assigned the driver to the xf86ConfigLayout
[ 198.576] (II) LoadModule: "ati"
[ 198.576] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so
[ 198.576] (II) Module ati: vendor="X.Org Foundation"
[ 198.576] compiled for 1.17.0, module version = 7.5.0
[ 198.576] Module class: X.Org Video Driver
[ 198.576] ABI class: X.Org Video Driver, version 19.0
[ 198.576] (II) LoadModule: "radeon"
[ 198.576] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so
[ 198.577] (II) Module radeon: vendor="X.Org Foundation"
[ 198.577] compiled for 1.17.0, module version = 7.5.0
[ 198.577] Module class: X.Org Video Driver
[ 198.577] ABI class: X.Org Video Driver, version 19.0
[ 198.577] (II) LoadModule: "modesetting"
[ 198.577] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 198.577] (II) Module modesetting: vendor="X.Org Foundation"
[ 198.577] compiled for 1.17.1, module version = 1.17.1
[ 198.577] Module class: X.Org Video Driver
[ 198.577] ABI class: X.Org Video Driver, version 19.0
[ 198.577] (II) LoadModule: "fbdev"
[ 198.577] (WW) Warning, couldn't open module fbdev
[ 198.577] (II) UnloadModule: "fbdev"
[ 198.577] (II) Unloading fbdev
[ 198.577] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 198.577] (II) LoadModule: "vesa"
[ 198.578] (WW) Warning, couldn't open module vesa
[ 198.578] (II) UnloadModule: "vesa"
[ 198.578] (II) Unloading vesa
[ 198.578] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 198.578] (II) RADEON: Driver for ATI Radeon chipsets:
ATI Radeon Mobility X600 (M24) 3150 (PCIE), ATI FireMV 2400 (PCI),
ATI Radeon Mobility X300 (M24) 3152 (PCIE),
ATI FireGL M24 GL 3154 (PCIE), ATI FireMV 2400 3155 (PCI),
ATI Radeon X600 (RV380) 3E50 (PCIE),
ATI FireGL V3200 (RV380) 3E54 (PCIE), ATI Radeon IGP320 (A3) 4136,
ATI Radeon IGP330/340/350 (A4) 4137, ATI Radeon 9500 AD (AGP),
ATI Radeon 9500 AE (AGP), ATI Radeon 9600TX AF (AGP),
ATI FireGL Z1 AG (AGP), ATI Radeon 9800SE AH (AGP),
ATI Radeon 9800 AI (AGP), ATI Radeon 9800 AJ (AGP),
ATI FireGL X2 AK (AGP), ATI Radeon 9600 AP (AGP),
ATI Radeon 9600SE AQ (AGP), ATI Radeon 9600XT AR (AGP),
ATI Radeon 9600 AS (AGP), ATI FireGL T2 AT (AGP), ATI Radeon 9650,
ATI FireGL RV360 AV (AGP), ATI Radeon 7000 IGP (A4+) 4237,
ATI Radeon 8500 AIW BB (AGP), ATI Radeon IGP320M (U1) 4336,
ATI Radeon IGP330M/340M/350M (U2) 4337,
ATI Radeon Mobility 7000 IGP 4437, ATI Radeon 9000/PRO If (AGP/PCI),
ATI Radeon 9000 Ig (AGP/PCI), ATI Radeon X800 (R420) JH (AGP),
ATI Radeon X800PRO (R420) JI (AGP),
ATI Radeon X800SE (R420) JJ (AGP), ATI Radeon X800 (R420) JK (AGP),
ATI Radeon X800 (R420) JL (AGP), ATI FireGL X3 (R420) JM (AGP),
ATI Radeon Mobility 9800 (M18) JN (AGP),
ATI Radeon X800 SE (R420) (AGP), ATI Radeon X800XT (R420) JP (AGP),
ATI Radeon X800 VE (R420) JT (AGP), ATI Radeon X850 (R480) (AGP),
ATI Radeon X850 XT (R480) (AGP), ATI Radeon X850 SE (R480) (AGP),
ATI Radeon X850 PRO (R480) (AGP), ATI Radeon X850 XT PE (R480) (AGP),
ATI Radeon Mobility M7 LW (AGP),
ATI Mobility FireGL 7800 M7 LX (AGP),
ATI Radeon Mobility M6 LY (AGP), ATI Radeon Mobility M6 LZ (AGP),
ATI FireGL Mobility 9000 (M9) Ld (AGP),
ATI Radeon Mobility 9000 (M9) Lf (AGP),
ATI Radeon Mobility 9000 (M9) Lg (AGP), ATI FireMV 2400 PCI,
ATI Radeon 9700 Pro ND (AGP), ATI Radeon 9700/9500Pro NE (AGP),
ATI Radeon 9600TX NF (AGP), ATI FireGL X1 NG (AGP),
ATI Radeon 9800PRO NH (AGP), ATI Radeon 9800 NI (AGP),
ATI FireGL X2 NK (AGP), ATI Radeon 9800XT NJ (AGP),
ATI Radeon Mobility 9600/9700 (M10/M11) NP (AGP),
ATI Radeon Mobility 9600 (M10) NQ (AGP),
ATI Radeon Mobility 9600 (M11) NR (AGP),
ATI Radeon Mobility 9600 (M10) NS (AGP),
ATI FireGL Mobility T2 (M10) NT (AGP),
ATI FireGL Mobility T2e (M11) NV (AGP), ATI Radeon QD (AGP),
ATI Radeon QE (AGP), ATI Radeon QF (AGP), ATI Radeon QG (AGP),
ATI FireGL 8700/8800 QH (AGP), ATI Radeon 8500 QL (AGP),
ATI Radeon 9100 QM (AGP), ATI Radeon 7500 QW (AGP/PCI),
ATI Radeon 7500 QX (AGP/PCI), ATI Radeon VE/7000 QY (AGP/PCI),
ATI Radeon VE/7000 QZ (AGP/PCI), ATI ES1000 515E (PCI),
ATI Radeon Mobility X300 (M22) 5460 (PCIE),
ATI Radeon Mobility X600 SE (M24C) 5462 (PCIE),
ATI FireGL M22 GL 5464 (PCIE), ATI Radeon X800 (R423) UH (PCIE),
ATI Radeon X800PRO (R423) UI (PCIE),
ATI Radeon X800LE (R423) UJ (PCIE),
ATI Radeon X800SE (R423) UK (PCIE),
ATI Radeon X800 XTP (R430) (PCIE), ATI Radeon X800 XL (R430) (PCIE),
ATI Radeon X800 SE (R430) (PCIE), ATI Radeon X800 (R430) (PCIE),
ATI FireGL V7100 (R423) (PCIE), ATI FireGL V5100 (R423) UQ (PCIE),
ATI FireGL unknown (R423) UR (PCIE),
ATI FireGL unknown (R423) UT (PCIE),
ATI Mobility FireGL V5000 (M26) (PCIE),
ATI Mobility FireGL V5000 (M26) (PCIE),
ATI Mobility Radeon X700 XL (M26) (PCIE),
ATI Mobility Radeon X700 (M26) (PCIE),
ATI Mobility Radeon X700 (M26) (PCIE),
ATI Radeon X550XTX 5657 (PCIE), ATI Radeon 9100 IGP (A5) 5834,
ATI Radeon Mobility 9100 IGP (U3) 5835,
ATI Radeon XPRESS 200 5954 (PCIE),
ATI Radeon XPRESS 200M 5955 (PCIE), ATI Radeon 9250 5960 (AGP),
ATI Radeon 9200 5961 (AGP), ATI Radeon 9200 5962 (AGP),
ATI Radeon 9200SE 5964 (AGP), ATI FireMV 2200 (PCI),
ATI ES1000 5969 (PCI), ATI Radeon XPRESS 200 5974 (PCIE),
ATI Radeon XPRESS 200M 5975 (PCIE),
ATI Radeon XPRESS 200 5A41 (PCIE),
ATI Radeon XPRESS 200M 5A42 (PCIE),
ATI Radeon XPRESS 200 5A61 (PCIE),
ATI Radeon XPRESS 200M 5A62 (PCIE),
ATI Radeon X300 (RV370) 5B60 (PCIE),
ATI Radeon X600 (RV370) 5B62 (PCIE),
ATI Radeon X550 (RV370) 5B63 (PCIE),
ATI FireGL V3100 (RV370) 5B64 (PCIE),
ATI FireMV 2200 PCIE (RV370) 5B65 (PCIE),
ATI Radeon Mobility 9200 (M9+) 5C61 (AGP),
ATI Radeon Mobility 9200 (M9+) 5C63 (AGP),
ATI Mobility Radeon X800 XT (M28) (PCIE),
ATI Mobility FireGL V5100 (M28) (PCIE),
ATI Mobility Radeon X800 (M28) (PCIE), ATI Radeon X850 5D4C (PCIE),
ATI Radeon X850 XT PE (R480) (PCIE),
ATI Radeon X850 SE (R480) (PCIE), ATI Radeon X850 PRO (R480) (PCIE),
ATI unknown Radeon / FireGL (R480) 5D50 (PCIE),
ATI Radeon X850 XT (R480) (PCIE),
ATI Radeon X800XT (R423) 5D57 (PCIE),
ATI FireGL V5000 (RV410) (PCIE), ATI Radeon X700 XT (RV410) (PCIE),
ATI Radeon X700 PRO (RV410) (PCIE),
ATI Radeon X700 SE (RV410) (PCIE), ATI Radeon X700 (RV410) (PCIE),
ATI Radeon X700 SE (RV410) (PCIE), ATI Radeon X1800,
ATI Mobility Radeon X1800 XT, ATI Mobility Radeon X1800,
ATI Mobility FireGL V7200, ATI FireGL V7200, ATI FireGL V5300,
ATI Mobility FireGL V7100, ATI Radeon X1800, ATI Radeon X1800,
ATI Radeon X1800, ATI Radeon X1800, ATI Radeon X1800,
ATI FireGL V7300, ATI FireGL V7350, ATI Radeon X1600, ATI RV505,
ATI Radeon X1300/X1550, ATI Radeon X1550, ATI M54-GL,
ATI Mobility Radeon X1400, ATI Radeon X1300/X1550,
ATI Radeon X1550 64-bit, ATI Mobility Radeon X1300,
ATI Mobility Radeon X1300, ATI Mobility Radeon X1300,
ATI Mobility Radeon X1300, ATI Radeon X1300, ATI Radeon X1300,
ATI RV505, ATI RV505, ATI FireGL V3300, ATI FireGL V3350,
ATI Radeon X1300, ATI Radeon X1550 64-bit, ATI Radeon X1300/X1550,
ATI Radeon X1600, ATI Radeon X1300/X1550, ATI Mobility Radeon X1450,
ATI Radeon X1300/X1550, ATI Mobility Radeon X2300,
ATI Mobility Radeon X2300, ATI Mobility Radeon X1350,
ATI Mobility Radeon X1350, ATI Mobility Radeon X1450,
ATI Radeon X1300, ATI Radeon X1550, ATI Mobility Radeon X1350,
ATI FireMV 2250, ATI Radeon X1550 64-bit, ATI Radeon X1600,
ATI Radeon X1650, ATI Radeon X1600, ATI Radeon X1600,
ATI Mobility FireGL V5200, ATI Mobility Radeon X1600,
ATI Radeon X1650, ATI Radeon X1650, ATI Radeon X1600,
ATI Radeon X1300 XT/X1600 Pro, ATI FireGL V3400,
ATI Mobility FireGL V5250, ATI Mobility Radeon X1700,
ATI Mobility Radeon X1700 XT, ATI FireGL V5200,
ATI Mobility Radeon X1700, ATI Radeon X2300HD,
ATI Mobility Radeon HD 2300, ATI Mobility Radeon HD 2300,
ATI Radeon X1950, ATI Radeon X1900, ATI Radeon X1950,
ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900,
ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900,
ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900,
ATI AMD Stream Processor, ATI Radeon X1900, ATI Radeon X1950,
ATI RV560, ATI RV560, ATI Mobility Radeon X1900, ATI RV560,
ATI Radeon X1950 GT, ATI RV570, ATI RV570, ATI FireGL V7400,
ATI RV560, ATI Radeon X1650, ATI Radeon X1650, ATI RV560,
ATI Radeon 9100 PRO IGP 7834, ATI Radeon Mobility 9200 IGP 7835,
ATI Radeon X1200, ATI Radeon X1200, ATI Radeon X1200,
ATI Radeon X1200, ATI Radeon X1200, ATI RS740, ATI RS740M, ATI RS740,
ATI RS740M, ATI Radeon HD 2900 XT, ATI Radeon HD 2900 XT,
ATI Radeon HD 2900 XT, ATI Radeon HD 2900 Pro, ATI Radeon HD 2900 GT,
ATI FireGL V8650, ATI FireGL V8600, ATI FireGL V7600,
ATI Radeon 4800 Series, ATI Radeon HD 4870 x2,
ATI Radeon 4800 Series, ATI Radeon HD 4850 x2,
ATI FirePro V8750 (FireGL), ATI FirePro V7760 (FireGL),
ATI Mobility RADEON HD 4850, ATI Mobility RADEON HD 4850 X2,
ATI Radeon 4800 Series, ATI FirePro RV770, AMD FireStream 9270,
AMD FireStream 9250, ATI FirePro V8700 (FireGL),
ATI Mobility RADEON HD 4870, ATI Mobility RADEON M98,
ATI Mobility RADEON HD 4870, ATI Radeon 4800 Series,
ATI Radeon 4800 Series, ATI FirePro M7750, ATI M98, ATI M98, ATI M98,
ATI Mobility Radeon HD 4650, ATI Radeon RV730 (AGP),
ATI Mobility Radeon HD 4670, ATI FirePro M5750,
ATI Mobility Radeon HD 4670, ATI Radeon RV730 (AGP),
ATI RV730XT [Radeon HD 4670], ATI RADEON E4600,
ATI Radeon HD 4600 Series, ATI RV730 PRO [Radeon HD 4650],
ATI FirePro V7750 (FireGL), ATI FirePro V5700 (FireGL),
ATI FirePro V3750 (FireGL), ATI Mobility Radeon HD 4830,
ATI Mobility Radeon HD 4850, ATI FirePro M7740, ATI RV740,
ATI Radeon HD 4770, ATI Radeon HD 4700 Series, ATI Radeon HD 4770,
ATI FirePro M5750, ATI RV610, ATI Radeon HD 2400 XT,
ATI Radeon HD 2400 Pro, ATI Radeon HD 2400 PRO AGP, ATI FireGL V4000,
ATI RV610, ATI Radeon HD 2350, ATI Mobility Radeon HD 2400 XT,
ATI Mobility Radeon HD 2400, ATI RADEON E2400, ATI RV610,
ATI FireMV 2260, ATI RV670, ATI Radeon HD3870,
ATI Mobility Radeon HD 3850, ATI Radeon HD3850,
ATI Mobility Radeon HD 3850 X2, ATI RV670,
ATI Mobility Radeon HD 3870, ATI Mobility Radeon HD 3870 X2,
ATI Radeon HD3870 X2, ATI FireGL V7700, ATI Radeon HD3850,
ATI Radeon HD3690, AMD Firestream 9170, ATI Radeon HD 4550,
ATI Radeon RV710, ATI Radeon RV710, ATI Radeon RV710,
ATI Radeon HD 4350, ATI Mobility Radeon 4300 Series,
ATI Mobility Radeon 4500 Series, ATI Mobility Radeon 4500 Series,
ATI FirePro RG220, ATI Mobility Radeon 4330, ATI RV630,
ATI Mobility Radeon HD 2600, ATI Mobility Radeon HD 2600 XT,
ATI Radeon HD 2600 XT AGP, ATI Radeon HD 2600 Pro AGP,
ATI Radeon HD 2600 XT, ATI Radeon HD 2600 Pro, ATI Gemini RV630,
ATI Gemini Mobility Radeon HD 2600 XT, ATI FireGL V5600,
ATI FireGL V3600, ATI Radeon HD 2600 LE,
ATI Mobility FireGL Graphics Processor, ATI Radeon HD 3470,
ATI Mobility Radeon HD 3430, ATI Mobility Radeon HD 3400 Series,
ATI Radeon HD 3450, ATI Radeon HD 3450, ATI Radeon HD 3430,
ATI Radeon HD 3450, ATI FirePro V3700, ATI FireMV 2450,
ATI FireMV 2260, ATI FireMV 2260, ATI Radeon HD 3600 Series,
ATI Radeon HD 3650 AGP, ATI Radeon HD 3600 PRO,
ATI Radeon HD 3600 XT, ATI Radeon HD 3600 PRO,
ATI Mobility Radeon HD 3650, ATI Mobility Radeon HD 3670,
ATI Mobility FireGL V5700, ATI Mobility FireGL V5725,
ATI Radeon HD 3200 Graphics, ATI Radeon 3100 Graphics,
ATI Radeon HD 3200 Graphics, ATI Radeon 3100 Graphics,
ATI Radeon HD 3300 Graphics, ATI Radeon HD 3200 Graphics,
ATI Radeon 3000 Graphics, SUMO, SUMO, SUMO2, SUMO2, SUMO2, SUMO2,
SUMO, SUMO, SUMO2, SUMO, SUMO, SUMO, SUMO, SUMO, ATI Radeon HD 4200,
ATI Radeon 4100, ATI Mobility Radeon HD 4200,
ATI Mobility Radeon 4100, ATI Radeon HD 4290, ATI Radeon HD 4250,
AMD Radeon HD 6310 Graphics, AMD Radeon HD 6310 Graphics,
AMD Radeon HD 6250 Graphics, AMD Radeon HD 6250 Graphics,
AMD Radeon HD 6300 Series Graphics,
AMD Radeon HD 6200 Series Graphics, PALM, PALM, PALM, CYPRESS,
ATI FirePro (FireGL) Graphics Adapter,
ATI FirePro (FireGL) Graphics Adapter,
ATI FirePro (FireGL) Graphics Adapter, AMD Firestream 9370,
AMD Firestream 9350, ATI Radeon HD 5800 Series,
ATI Radeon HD 5800 Series, ATI Radeon HD 5800 Series,
ATI Radeon HD 5800 Series, ATI Radeon HD 5900 Series,
ATI Radeon HD 5900 Series, ATI Mobility Radeon HD 5800 Series,
ATI Mobility Radeon HD 5800 Series,
ATI FirePro (FireGL) Graphics Adapter,
ATI FirePro (FireGL) Graphics Adapter,
ATI Mobility Radeon HD 5800 Series, ATI Radeon HD 5700 Series,
ATI Radeon HD 5700 Series, ATI Radeon HD 6700 Series,
ATI Radeon HD 5700 Series, ATI Radeon HD 6700 Series,
ATI Mobility Radeon HD 5000 Series,
ATI Mobility Radeon HD 5000 Series, ATI Mobility Radeon HD 5570,
ATI FirePro (FireGL) Graphics Adapter,
ATI FirePro (FireGL) Graphics Adapter, ATI Radeon HD 5670,
ATI Radeon HD 5570, ATI Radeon HD 5500 Series, REDWOOD,
ATI Mobility Radeon HD 5000 Series,
ATI Mobility Radeon HD 5000 Series, ATI Mobility Radeon Graphics,
ATI Mobility Radeon Graphics, CEDAR,
ATI FirePro (FireGL) Graphics Adapter,
ATI FirePro (FireGL) Graphics Adapter, ATI FirePro 2270, CEDAR,
ATI Radeon HD 5450, CEDAR, CEDAR, CAYMAN, CAYMAN, CAYMAN, CAYMAN,
CAYMAN, CAYMAN, CAYMAN, CAYMAN, CAYMAN, CAYMAN,
AMD Radeon HD 6900 Series, AMD Radeon HD 6900 Series, CAYMAN, CAYMAN,
CAYMAN, AMD Radeon HD 6900M Series, Mobility Radeon HD 6000 Series,
BARTS, BARTS, Mobility Radeon HD 6000 Series,
Mobility Radeon HD 6000 Series, BARTS, BARTS, BARTS, BARTS,
AMD Radeon HD 6800 Series, AMD Radeon HD 6800 Series,
AMD Radeon HD 6700 Series, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS,
TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS,
TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS,
CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS,
CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, ARUBA, ARUBA,
ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA,
ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA,
ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA,
ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, TAHITI, TAHITI, TAHITI, TAHITI,
TAHITI, TAHITI, TAHITI, TAHITI, TAHITI, TAHITI, TAHITI, TAHITI,
TAHITI, PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN,
PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN,
VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE,
VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE,
VERDE, VERDE, VERDE, VERDE, OLAND, OLAND, OLAND, OLAND, OLAND, OLAND,
OLAND, OLAND, OLAND, OLAND, OLAND, OLAND, OLAND, OLAND, OLAND, OLAND,
HAINAN, HAINAN, HAINAN, HAINAN, HAINAN, HAINAN, BONAIRE, BONAIRE,
BONAIRE, BONAIRE, BONAIRE, BONAIRE, BONAIRE, BONAIRE, BONAIRE,
BONAIRE, KABINI, KABINI, KABINI, KABINI, KABINI, KABINI, KABINI,
KABINI, KABINI, KABINI, KABINI, KABINI, KABINI, KABINI, KABINI,
KABINI, MULLINS, MULLINS, MULLINS, MULLINS, MULLINS, MULLINS,
MULLINS, MULLINS, MULLINS, MULLINS, MULLINS, MULLINS, MULLINS,
MULLINS, MULLINS, MULLINS, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI,
KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI,
KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI,
KAVERI, HAWAII, HAWAII, HAWAII, HAWAII, HAWAII, HAWAII, HAWAII,
HAWAII, HAWAII, HAWAII, HAWAII, HAWAII
[ 198.591] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 198.591] (--) using VT number 2
[ 198.642] (II) [KMS] Kernel modesetting enabled.
[ 198.642] (WW) Falling back to old probe method for modesetting
[ 198.642] (II) RADEON(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 198.642] (==) RADEON(0): Depth 24, (--) framebuffer bpp 32
[ 198.642] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
[ 198.642] (==) RADEON(0): Default visual is TrueColor
[ 198.642] (==) RADEON(0): RGB weight 888
[ 198.642] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC)
[ 198.642] (--) RADEON(0): Chipset: "ATI Radeon XPRESS 200M 5A62 (PCIE)" (ChipID = 0x5a62)
[ 198.642] (EE) RADEON(0): [drm] failed to set drm interface version.
[ 198.642] (EE) RADEON(0): Kernel modesetting setup failed
[ 198.642] (II) UnloadModule: "radeon"
[ 198.643] (EE) Screen(s) found, but none have a usable configuration.
[ 198.643] (EE)
Fatal server error:
[ 198.643] (EE) no screens found(EE)
[ 198.643] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 198.643] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 198.643] (EE)
[ 198.673] (EE) Server terminated with error (1). Closing log file.
so i think i have module and/or config problem , what i need to do to recover server X ????
thx .
Similar Messages
-
[SOLVED]No Keyboard/Mouse on Xorg
Hi,
After an update a few days ago, my network devices weren't working anymore, but running dhcpcd could fix that. Today i updated again and used pacdiff to merge some new configs (i can't remember which one - great i know) and now there is no reaction of my input devices when xorg is started. As long as i boot into init3 everything is ok. Some ideas what i could have messed up?
Thanks
VR
EDIT: I just realised that HAL fails to start
EDIT2: Ok seems that i've accidentially deleted hal from /etc/groups. Input works again but network is as dead as before...weird.
Last edited by VirtualRider (2010-02-05 12:54:59)EDIT: oops - never mind - forgot to add the hal group to new /etc/groups file. Still Solved!:rolleyes:
Similar problem here - after merging old /etc/groups file into new groups config file, my mouse and keyboard become dead. I use qingy in runlevel 3 to login and that works. Booting into my fallback (and not yet updated) Arch system, I reactivated the old /etc/groups config (which I had saved ) and the mouse and keyboard work again.
Can anyone save me from a line-by-line examination of the new /etc/groups file? What is the problem here? Without a working keyboard or mouse it is difficult to diagnose this on a running system.
Last edited by sonoran (2010-02-06 23:06:08) -
Not responding to keyboard/mouse after windows 10 upgrade
Hi, I upgraded my home computer yesterday to Windows 10. I came to work today and are trying to use my logmein for some offsite testing. I can connect just fine and see the desktop of my home PC, but no mouse or keyboard activity is responding. Even the "ctrl-alt-delete" function of the LogmeIn client does nothing. Has anyone experienced similar issues? And if so, is there a solution to this? I am running Windows 10 Enterprise x64 both at home and at work, and yesterday it was working fine when connecting from Win 10 Ent. at work to Win 8.1 Ent. at home. Any info would be greatly appreciated. Regards Dan
I have same problem
-
[Trick] Use Keyboard + Mouse from Xorg to control another Xorg session
So you have two computers sitting together, you don't have a kvm switch, and using two keyboards and mice is just plan annoying!
X2X is the solution. This program allows you to use your mouse and keyboard from Computer A on Computer B.
From the man page
x2x allows the keyboard and mouse on one ("from") X display to be used to control another ("to") X display.
How to make it work?
Allow TCP from xorg on both systems
Edit /etc/X11/xinit/xserverrc and change
exec /usr/bin/X -nolisten tcp
to
exec /usr/bin/X
Computer A = computer that has the keyboard and mouse you want to use
Computer B = computer that does not have the keyboard and mouse you want to use hooked up to it
On Computer B run the command
xhost +ComputerA
Where ComputerA is the hostname/ip address of ComputerA
This allows ComputerA to connect to ComputerB's xorg server
On Computer A run the command
x2x -to ComputerB:0.0 -west
Where ComputerB is the hostname/ip address of ComputerB
Now on ComputerA you should be able to move the mouse left, off the screen, and be able to control ComputerB!
I use this to control my laptop using my desktop's mouse and keyboard. It's a lot easier than switching between my desktop keyboard/mouse and laptop keyboard/mouse!diederick76 wrote:
I have used x2x for some time before I started using Arch, but recently I decided to start using it again to control my laptop from my desktop box. I have installed x2x on the laptop. However, when I do
# ssh -X laptop 'x2x -west -to :0'
I get:
X Error of failed request: BadWindow (invalid Window parameter)
Major opcode of failed request: 25 (X_SendEvent)
Resource id in failed request: 0x400001b
Serial number of failed request: 21
Current serial number in output stream: 21
I have tried following your howto, but I seem unable to start X with tcp support. I have changed /etc/X11/xinit/xserverrc as you instructed, but when I start X and issue
ps ax | grep X
from a console, I still get:
1670 tty7 Ss+ 0:15 /usr/bin/X -nolisten tcp vt07 -auth /var/run/slim.auth
Can you tell me what I'm missing? Are these at all related?
Thanks!
Today I was looking into this and got working very fast using this thread. Are you sure you restarted your X server after changing xserverrc? Are you sure your display is at :0?
Use
echo $DISPLAY
on the terminal to find out. Also you need x2x installed on both machines.
Last edited by quiquex (2011-11-08 18:59:08) -
[SOLVED] Getting theme errors after a recent upgrade in gtk3 apps
I have recently started getting errors like these after a recent upgrade.
(nautilus:12329): Gtk-WARNING **: Theme parsing error: *-*:*:*: Not using units is deprecated. Assuming 'px'.
Full error while opening nautilus can be see here. http://sprunge.us/IQOM
Relevant pacman log: http://sprunge.us/YYgY
~/.config/gtk-3.0/settings.ini : http://sprunge.us/VJMT
I have tried few themes (Fear, Hope, Aldabra), all seem to give me this error. Also, theme Fear broke (gave white text with white background) after the upgrade.
Can anyone else reproduce this error?
If there is any theme that doesn't have problems with updated system, please share.
Last edited by shadyabhi (2012-04-28 02:41:54)shadyabhi wrote:Can anyone else reproduce this error?
Apparently yes:
https://bbs.archlinux.org/viewtopic.php?id=140402
https://bbs.archlinux.org/viewtopic.php?id=140277
There are a couple other threads as well - some have alleged solutions, or at least some themes that work. -
[SOLVED] startx: no keyboard/mouse after upgrade
Hello,
After an upgrade during which X was upgraded to 1.16 the keyboard and mouse stopped working after using startx. When I start X with startx as root the keyboard and mouse work.
After the upgrade I made a .xinitrc like in the wiki article about xinitrc and I copied /etc/X/xinit/xserverrc to ~/.xserverrc
Any help would be appreciated.
Thanks!
Last edited by basdi (2014-09-15 17:13:45)Hey,
Thanks for your answer.
I start X using startx and this .xinitrc in my home directory:
#!/bin/sh
#~/.xinitrc
# Executed by startx (run your windows manager from here
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi
xrdb /merge ~/.Xresources
setxkbmap de
# Here awesome is kept as default
# no va: session=${1: -awesome}
case $session in
awesome) exec awesome;;
fluxbox) exec startfluxbox;;
# No known session, try to run it as command
# no va *) exec $1;;
*) exec awesome;;
esac
I created the .xinitrc after this wiki article
https://wiki.archlinux.org/index.php/Xinitrc
I tried it without the .xserverrc in the home directory and it is the same. I read that in a forum. But probably it is not necessary because the behaviour is the same...
Before the upgrade, I started X using xinit, but now using xinit I get the error :
(EE) xf86OpenConsole: Cannot open /dev/tty0 (No such file or directory)
And I read on a forum that I should use startx.
I'm not running as root. I try to run X as a normal user. When I run it as root it works.
In the boot messages from systemd journal I see these messages:
systemd-logind[642]: Failed to connect to system bus: No such file or directory
systemd-logind[642]: Failed to fully start up daemon: No such file or directory
systemd-logind[675]Failed to connect to system bus: No such file or directory
systemd-logind[675]: Failed to fully start up daemon: No such file or directory
Sorry I don't really know what to look for in the logs...
I have a nvidia card and I use the proprietary drivers and Bumblebee. -
No keyboard & mouse after udev upgrade
Hello,
I've upgraded to udev-158-1 and after reboot the keyboard and mouse (http://www.logitech.com/en-us/keyboards … vices/3481) stoped working. Rebooted several times and got the same result. I reverted to the old version and everything is ok. It's also possible that the system was frozen, i haven't tried to ssh it. Any ideeas? Thanks.
Last edited by WladyX (2010-07-01 20:31:49)http://bugs.archlinux.org/task/20039
-
[Solved] RAID 5 degraded after 3.13 upgrade
Hi there,
after upgrading my home server to the latest kernel 3.13 I've found out, that my RAID 5 got degraded. One of the drives has been kicked out, but I don't know why. The drive seems okay, I've also done a SMART short test, completed without any errors. The only suspicious looking error message, when upgrading to Linux 3.13 was:
ERROR: Module 'hci_vhci' has devname (vhci) but lacks major and minor information. Ignoring.
This is mdstat output:
[tolga@Ragnarok ~]$ cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md127 : active raid5 sda1[0] sdc1[3] sdb1[1]
5860145664 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/3] [UUU_]
unused devices: <none>
smartctl:
[tolga@Ragnarok ~]$ sudo smartctl -a /dev/sdd
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.4-1-ARCH] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Western Digital Red (AF)
Device Model: WDC WD20EFRX-68AX9N0
Serial Number: [removed]
LU WWN Device Id: 5 0014ee 2b2cd537a
Firmware Version: 80.00A80
User Capacity: 2,000,398,934,016 bytes [2.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2 (minor revision not indicated)
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Fri Feb 21 22:26:30 2014 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (26580) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 268) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x70bd) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0
3 Spin_Up_Time 0x0027 164 163 021 Pre-fail Always - 6766
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 273
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0
9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 1954
10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 273
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 6
193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 266
194 Temperature_Celsius 0x0022 115 104 000 Old_age Always - 35
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0
SMART Error Log Version: 1
ATA Error Count: 306 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 306 occurred at disk power-on lifetime: 1706 hours (71 days + 2 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
04 61 02 00 00 00 a0 Device Fault; Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
ef 10 02 00 00 00 a0 08 22:17:38.065 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 a0 08 22:17:38.065 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 08 22:17:38.064 SET FEATURES [Set transfer mode]
ef 10 02 00 00 00 a0 08 22:17:38.064 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 a0 08 22:17:38.064 IDENTIFY DEVICE
Error 305 occurred at disk power-on lifetime: 1706 hours (71 days + 2 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
04 61 46 00 00 00 a0 Device Fault; Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
ef 03 46 00 00 00 a0 08 22:17:38.064 SET FEATURES [Set transfer mode]
ef 10 02 00 00 00 a0 08 22:17:38.064 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 a0 08 22:17:38.064 IDENTIFY DEVICE
ef 10 02 00 00 00 a0 08 22:17:38.063 SET FEATURES [Enable SATA feature]
Error 304 occurred at disk power-on lifetime: 1706 hours (71 days + 2 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
04 61 02 00 00 00 a0 Device Fault; Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
ef 10 02 00 00 00 a0 08 22:17:38.064 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 a0 08 22:17:38.064 IDENTIFY DEVICE
ef 10 02 00 00 00 a0 08 22:17:38.063 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 a0 08 22:17:38.063 IDENTIFY DEVICE
Error 303 occurred at disk power-on lifetime: 1706 hours (71 days + 2 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
04 61 02 00 00 00 a0 Device Fault; Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
ef 10 02 00 00 00 a0 08 22:17:38.063 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 a0 08 22:17:38.063 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 08 22:17:38.063 SET FEATURES [Set transfer mode]
ef 10 02 00 00 00 a0 08 22:17:38.063 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 a0 08 22:17:38.062 IDENTIFY DEVICE
Error 302 occurred at disk power-on lifetime: 1706 hours (71 days + 2 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
04 61 46 00 00 00 a0 Device Fault; Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
ef 03 46 00 00 00 a0 08 22:17:38.063 SET FEATURES [Set transfer mode]
ef 10 02 00 00 00 a0 08 22:17:38.063 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 a0 08 22:17:38.062 IDENTIFY DEVICE
ef 10 02 00 00 00 a0 08 22:17:38.062 SET FEATURES [Enable SATA feature]
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 1954 -
# 2 Short offline Completed without error 00% 0 -
# 3 Conveyance offline Completed without error 00% 0 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
This is my mdadm configuration:
[tolga@Ragnarok ~]$ cat /etc/mdadm.conf
ARRAY /dev/md/Asura metadata=1.2 UUID=34bab60a:4d640b50:6228c429:0679bb34 name=Ragnarok:Asura
I've checked all partition tables, everything seems ok. "Error 30[x] occurred at disk power-on lifetime: 1706 hours (71 days + 2 hours)" seems to be a one-time event, which happened on 1706 hours (I don't know why; no power loss or something similar). Other than those smartctl errors, everything seems fine. I've also inspected the drive; no suspicious noises or anything else, works like the other 3 drives. Am I safe to simply re-add the drive using "sudo mdadm --manage --re-add /dev/md127 /dev/sdd1" and let it re-sync or should I flag it as failed and then re-add it to the RAID?
I am using 4x 2TB Western Digital Red drives in a RAID 5, which are about 1 year old and they ran perfectly fine until now. The server is currently shut down until this problem is fixed. I currently got a partial backup of my data (most important ones) and will make a full backup, before attempting a repair. At the moment, I'm still able to access all my data, so nothing's wrong there.
So, what do you guys think, what should I do?
Last edited by tolga9009 (2014-09-13 12:48:13)Thank you brian for the fast reply. I've backed up all my important data and tried the command. It's not working ...
[tolga@Ragnarok ~]$ sudo mdadm --manage --re-add /dev/md127 /dev/sdd1
mdadm: --re-add for /dev/sdd1 to /dev/md127 is not possible
[tolga@Ragnarok ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 1.8T 0 disk
ââsda1 8:1 0 1.8T 0 part
ââmd127 9:127 0 5.5T 0 raid5 /media/Asura
sdb 8:16 0 1.8T 0 disk
ââsdb1 8:17 0 1.8T 0 part
ââmd127 9:127 0 5.5T 0 raid5 /media/Asura
sdc 8:32 0 1.8T 0 disk
ââsdc1 8:33 0 1.8T 0 part
ââmd127 9:127 0 5.5T 0 raid5 /media/Asura
sdd 8:48 0 1.8T 0 disk
ââsdd1 8:49 0 1.8T 0 part
sde 8:64 0 59.6G 0 disk
ââsde1 8:65 0 512M 0 part /boot/efi
ââsde2 8:66 0 4G 0 part [SWAP]
ââsde3 8:67 0 54.6G 0 part /
ââsde4 8:68 0 512M 0 part /boot
Out of curiosity, I've compared "mdadm -E" of the corrupted and a healthy drive. Here's the output:
[tolga@Ragnarok ~]$ diff -u sdc sdd
--- sdc 2014-02-21 23:28:51.051674496 +0100
+++ sdd 2014-02-21 23:28:55.911816816 +0100
@@ -1,4 +1,4 @@
-/dev/sdc1:
+/dev/sdd1:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
@@ -14,15 +14,15 @@
Data Offset : 262144 sectors
Super Offset : 8 sectors
Unused Space : before=262064 sectors, after=1167 sectors
- State : clean
- Device UUID : 4ce2ba99:645b1cc6:60c23336:c4428e2f
+ State : active
+ Device UUID : 4aeef598:64ff6631:826f445e:dbf77ab5
- Update Time : Fri Feb 21 23:18:20 2014
- Checksum : a6c42392 - correct
- Events : 16736
+ Update Time : Sun Jan 12 06:40:56 2014
+ Checksum : bf106b2a - correct
+ Events : 7295
Layout : left-symmetric
Chunk Size : 512K
- Device Role : Active device 2
- Array State : AAA. ('A' == active, '.' == missing, 'R' == replacing)
+ Device Role : Active device 3
+ Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)
So, I guess my only way to fix this is remove the faulty drive from the RAID, zero out the superblock and then re-add it as a new drive. Or is there any other way to fix this?
//Edit: I've used "mdadm --detail /dev/md127" and found out, that the faulty drive wasn't even listed anymore. So instead of using "re-add", I simply added it as a new drive and it's resyncing now. In about 220mins, I'll know more ! Is there a way to check for corruption after syncing the drives?
//Edit: ^ this worked. My drive probably didn't got kicked after the 3.13 upgrade, but I've simply noticed it then. The drive seems to be kicked after ~1700 hours for some unknown reason - I've now disconnected and reconnected all drives to opt out any wiring issues. Since the drive was out of sync, simply re-adding it didn't work. I had to manually add it to the array again and this caused a resync, which took around 3,5 hours. I think that's okay for a 4x 2TB RAID 5 array. Everything is working fine again, no data corruption, nothing. I'll mark it as solved.
Last edited by tolga9009 (2014-09-13 12:59:22) -
Bizarre keyboard behaviour after 4.2 upgrade
Since upgrading to KDE 4.2 (from 4.1) as part of a system upgrade, my system has been practically unusable due to the bizarre keyboard behaviour within KDE.
Right from the KDM login screen, most of the keys do not work as normal. For most letters, the key has to be pressed twice in order to generate the letter. However, I cannot type anything with a "u" because it is interpreted as a shortcut to undo everything I have just entered! Letter "f" has to be typed 4 times. If I type "h" once it appears; if I type it again it disappears. Letter "l" produces a vertical division in the window. I could go on....
Since my password ends in "u" I even had to change the password in order to login to KDE because the "u" would delete the characters I'd already entered! But once logged in the problem is just the same.
I have tried setting a different keyboard layout within KDE but this made no difference.
I have tried uninstalling and reinstalling KDE.
The problem seems to be KDE related, because outside KDE, in a system console, the keyboard works absolutely normally. And it doesn't seem to be related to the individual KDE user, since as I said, the problem is present as soon as the KDM login screen appears.
Has anyone got any ideas please?Thanks for the suggestions. Although they did not prove to be the answer, I have now overcome the problem. I suspect it was a one-off caused by corrupted data, probably in the xorg installation rather than KDE. I removed xorg then reinstalled it - some of the pkg files were corrupt and had to be replaced. Then I had trouble starting the X server at all, and had to reinstall several library packages. The system is running more normally now, though I think there are still some data corruptions in there and time will tell whether the installation is salvageable.
-
[Solved] iwlwifi very unstable after 3.4 upgrade (Centrino 1030 BGN)
Since the 3.4 kernel upgrade my wireless (iwlwifi, Intel Centrino-N 1030) has been extremely unstable and essentially unusable. There have been reports of problems on Intel 6x00 wifi cards, but I've not seen any on the 1030. I've tested this on 3.4.2 and 3.4.3.
The current workaround is to stay on 3.3.x kernel. A dmesg log is included below. It shows "Queue 2 stuck" and a firmware reload.
$ dmesg | grep iwl
[ 3.006555] iwlwifi 0000:09:00.0: pci_resource_len = 0x00002000
[ 3.006557] iwlwifi 0000:09:00.0: pci_resource_base = ffffc900050b8000
[ 3.006558] iwlwifi 0000:09:00.0: HW Revision ID = 0x34
[ 3.006644] iwlwifi 0000:09:00.0: irq 49 for MSI/MSI-X
[ 3.049251] iwlwifi 0000:09:00.0: loaded firmware version 18.168.6.1
[ 3.049511] iwlwifi 0000:09:00.0: CONFIG_IWLWIFI_DEBUG disabled
[ 3.049513] iwlwifi 0000:09:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
[ 3.049516] iwlwifi 0000:09:00.0: CONFIG_IWLWIFI_DEVICE_TRACING enabled
[ 3.049518] iwlwifi 0000:09:00.0: CONFIG_IWLWIFI_DEVICE_TESTMODE enabled
[ 3.049520] iwlwifi 0000:09:00.0: CONFIG_IWLWIFI_P2P disabled
[ 3.049523] iwlwifi 0000:09:00.0: Detected Intel(R) Centrino(R) Wireless-N 1030 BGN, REV=0xB0
[ 3.049582] iwlwifi 0000:09:00.0: L1 Disabled; Enabling L0S
[ 3.065387] iwlwifi 0000:09:00.0: device EEPROM VER=0x71a, CALIB=0x6
[ 3.065392] iwlwifi 0000:09:00.0: Device SKU: 0x150
[ 3.065395] iwlwifi 0000:09:00.0: Valid Tx ant: 0x1, Valid Rx ant: 0x3
[ 3.065417] iwlwifi 0000:09:00.0: Tunable channels: 13 802.11bg, 0 802.11a channels
[ 3.081022] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
[ 6.781462] iwlwifi 0000:09:00.0: L1 Disabled; Enabling L0S
[ 6.788151] iwlwifi 0000:09:00.0: Radio type=0x2-0x2-0x1
[ 6.872549] iwlwifi 0000:09:00.0: L1 Disabled; Enabling L0S
[ 6.879316] iwlwifi 0000:09:00.0: Radio type=0x2-0x2-0x1
[ 718.479232] iwlwifi 0000:09:00.0: Queue 2 stuck for 10000 ms.
[ 718.479236] iwlwifi 0000:09:00.0: Current SW read_ptr 223 write_ptr 235
[ 718.479265] iwlwifi 0000:09:00.0: Current HW read_ptr 223 write_ptr 235
[ 718.479267] iwlwifi 0000:09:00.0: On demand firmware reload
[ 718.479665] iwlwifi 0000:09:00.0: L1 Disabled; Enabling L0S
[ 718.486377] iwlwifi 0000:09:00.0: Radio type=0x2-0x2-0x1
$
Last edited by mervinb (2012-06-24 05:48:00)I tried testing/linux-3.4.4-1, and the problem appears fixed.
There's a fix for in 3.4.4 for iwlwifi firmware version for 6000g2 (which is what the 1030 card uses). Marking as solved. -
The keyboard /mouse unresponsive in yosemite on my Mac Air Late 2010
How do I fix the problem of lack of responsiveness with my keyboard/mouse after installing yosemite on my late 2010 Mac Air? Losing typing ability in mid sentence!!
If the following doesn't work, then there is a server error.
Reinstalling OS X Without Erasing the Drive
Boot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the main menu. Repair the Hard Drive and Permissions as follows.
When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu.
Reinstall OS X: Select Reinstall OS X and click on the Continue button.
Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.
Also see:
Reinstall OS X Without Erasing the Drive
Choose the version you have installed now:
OS X Yosemite- Reinstall OS X
Note: You will need an active Internet connection. I suggest using Ethernet
if possible because it is three times faster than wireless. -
System Preferences - Keyboard & Mouse
I've some trouble with my 2 macbooks in the system preferences / keyboard&mouse , after update my leopard. The panel do not appear. Did you have some explanation about it?
Thanks for att
GuguThe same here!
And I really need to change those configurations!
I'm so sad... Can someone fix this? Please! -
HT4623 keyboard delay on iPad following upgrade
has anyone experienced problems with their ipad keyboard responding after the IS07 upgrade?
Reset all settings
Settings>General>Reset>Reset All Settings -
[Solved] Problems with xinit after upgrade xorg-xinit to 1.3.4-2 versi
Hi,
Today I've upgraded my system with pacman -Syu and after upgrading xorg-xinit to 1.3.4-2 version I cannot use X.
When I run "xinit" then single white window appears but there is not any reaction for mouse or keyboard events.
I cannot even get back to VT by ctrl-alt-Fx or switch on/off NumLock. The only reaction on keyboard is issuing sysrq commands (ctrl-alt-sysrq E) which kills X.
I also discovered that running following command helps: "xinit -- vt12" - I mean it launches X and mouse and keyboard are working fine.
Is this a bug or I have misconfigured system?
Last edited by wtx (2015-03-23 15:08:14)I can confirm what appears to be the same problem on my two machines running Arch with systemd. On both machines, after upgrading the xorg-* packages yesterday, X would not start as it normally did: I'd get a blank screen with only a _ up in the top left corner. Pressing ctrl-alt-(number) had no effect, nor did anything else I tried. (I didn't try killing X like the OP did.) Googled and searched the forums yesterday to no avail; nothing I tried worked.
Caveat: In my case(s), I use 'startxfce4' instead of 'startx', so it might not be the exact issue. Trying 'startx' just took me to a default X installation setup, with three terminal windows and a clock. I'm sure anyone who's set up Arch for the first time has seen the same windows.
So in case it helps, here's what I did to get them working again:
1. This morning, I checked the forums again and saw the thread at https://bbs.archlinux.org/viewtopic.php?id=195107, which recommended changing a line in the file /etc/X11/xinit/xserverrc from:
exec /usr/bin/X -nolisten tcp "$@"
to
exec /usr/bin/X -nolisten tcp "$@" vt$XDG_VTNR
2. I didn't want to change the default file, so I created a ~/.xserverrc file (note that it's in my home directory, so it will only work for my one user; if you want it to work for multiple users you'd follow step one exactly, as recommended in the other thread). I put the line
exec /usr/bin/X -nolisten tcp "$@" vt$XDG_VTNR
in that file, saved it, and fired up 'startxfce4'. Everything works perfectly.
Again, since I use XFCE I don't know if it's exactly the same issue you have, but at least this might help point you towards a solution.
PS
In case you're wondering why I tried the solution in the other thread: The blank screen error only appears when I had
needs_root_rights=yes
in /etc/X11/Xwrapper.config. When I changed it to 'no' (or removed the file entirely), I would get an error message like "xf860OpenConsole: Cannot open /dev/tty0", which is similar to the error message the OP on that thread would get.
EDIT:
Actually, the more I think about it, the less I think this is the same problem. And the lack of details from the OP doesn't help. Still, it does appear that both of these problems concern passing a virtual terminal parameter to X, or failing to do so.
Last edited by Massimiliano (2015-03-23 13:21:58) -
[SOLVED] Keyboard layout changed to English after xorg update
Hello all,
I just logged in to my Arch box after a few days of not using it, and issued
pacman -Syu
and upgraded, among others, xorg-server and xorg-server-common to versions 1.11.1-2. Now, after logging out and back in to restart X, I find that my keyboard layout is now (presumably American) English. However, looking under Menu -> Settings -> Keyboard in the XFCE menu, I still see the preferred layout set to Norwegian, as I want. Messing with the settings in this GUI seems to have no effect. However,
setxkbmap no
still works. Anybody experience something similar or have any hints?
Here's the output of
sudo less /var/log/pacman.log | grep 2011-10-12
[2011-10-12 21:05] Running 'pacman -Syu'
[2011-10-12 21:05] synchronizing package lists
[2011-10-12 21:05] starting full system upgrade
[2011-10-12 21:07] update desktop mime database...
[2011-10-12 21:07] removed comix (4.0.4-5)
[2011-10-12 21:07] installed python2-distribute (0.6.21-1)
[2011-10-12 21:07] update desktop mime database...
[2011-10-12 21:07] installed mcomix (0.94-2)
[2011-10-12 21:07] upgraded gtksourceview3 (3.2.0-1 -> 3.2.1-1)
[2011-10-12 21:07] upgraded imagemagick (6.7.2.8-1 -> 6.7.3.0-1)
[2011-10-12 21:07] upgraded libass (0.9.13-1 -> 0.10.0-1)
[2011-10-12 21:07] upgraded libsasl (2.1.23-7 -> 2.1.23-8)
[2011-10-12 21:07] upgraded lsof (4.84-3 -> 4.85-1)
[2011-10-12 21:07] upgraded mkinitcpio (0.7.2-1 -> 0.7.3-1)
[2011-10-12 21:07] upgraded mpfr (3.1.0-2 -> 3.1.0.p1-1)
[2011-10-12 21:07] upgraded python2-pytz (2011h-1 -> 2011k-1)
[2011-10-12 21:07] upgraded shared-mime-info (0.90-1 -> 0.91-1)
[2011-10-12 21:07] upgraded transmission-gtk (2.33-1 -> 2.41-2)
[2011-10-12 21:07] upgraded wine (1.3.29-2 -> 1.3.30-1)
[2011-10-12 21:07] upgraded xf86-input-evdev (2.6.0-3 -> 2.6.0-4)
[2011-10-12 21:07] upgraded xf86-video-nouveau (0.0.16_git20110726-1 -> 0.0.16_git20110829-1)
[2011-10-12 21:07] upgraded xkeyboard-config (2.2.1-1 -> 2.4.1-1)
[2011-10-12 21:07] upgraded xorg-server-common (1.10.4-1 -> 1.11.1-2)
[2011-10-12 21:07] upgraded xorg-server (1.10.4-1 -> 1.11.1-2)
[2011-10-12 21:07] upgraded xorg-xinit (1.3.0-3 -> 1.3.1-1)
[2011-10-12 21:07] Running 'pacman -S alsa-plugins lib32-alsa-plugins'
[2011-10-12 21:07] installed alsa-plugins (1.0.24-2)
[2011-10-12 21:07] installed lib32-alsa-plugins (1.0.24-1)
[2011-10-12 21:09] Running 'pacman -Rs libcanberra lib32-libxxf86dga'
[2011-10-12 21:09] removed lib32-libxxf86dga (1.1.2-1)
[2011-10-12 21:09] removed libcanberra (0.28-2)
And of
sudo less /var/log/Xorg.0.log | grep key
[ 679.213] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 679.213] (--) Power Button: Found keys
[ 679.213] (II) Power Button: Configuring as keyboard
[ 679.242] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 679.242] (--) Power Button: Found keys
[ 679.242] (II) Power Button: Configuring as keyboard
[ 679.242] (**) LITEON Technology USB Multimedia Keyboard: Applying InputClass "evdev keyboard catchall"
[ 679.242] (--) LITEON Technology USB Multimedia Keyboard: Found keys
[ 679.242] (II) LITEON Technology USB Multimedia Keyboard: Configuring as keyboard
Thank you for any help!
Last edited by mariusmeyer (2011-10-12 21:52:19)It seems to be treated as standard behavior here (I had the same problem though):
https://wiki.archlinux.org/index.php/Beginners'_Guide#Non-US_keyboard
https://wiki.archlinux.org/index.php/GN … ard_layout
Last edited by viking60 (2011-10-12 20:47:37)
Maybe you are looking for
-
Barcodes are not shown in the client machine
Hi, We are using asp.net web forms for launching crystal reports. Crystal Reports rpt with barcode has been designed in Crystal 2008. Barcode field has been defined by right clicking the required field and selecting Change to Barcode u2026 and the
-
Lost mobile functions after upgrade from Adobe PDF Pack to Creative Cloud
I think mobile functions ar part of Creative Cloud (Student) with respect to Acrobat Pro XI module: e.g. PDF conversion I have contacted Adobe Chat already and shall now contact this forum as very next step. However, my Reader App does not support P
-
Printing GR/GI Slip "Collective output"
Hi, I am trying set the print indicator in MIGO by default for "Collective Slip" I can see the "Collective slip"appearing there ... but we manually are checking the checkbox. We want this to be checked by default. I tried setting the NDR paramater in
-
Scroll bar direction will not change
When I go to general preferences, there is no way to change the scroll direction any longer.
-
Ugh tI have gray thumbnails of my photos. I cannot find my photos through the finder. what do I do?
I have gray thumbnails of my photos. I cannot find my photos through the finder. what do I do?