Nemesis update april-06-2017 discussion

Arch based Porteus community project
User avatar
istinnjazz
Samurai
Samurai
Posts: 114
Joined: 15 May 2016, 14:10
Distribution: Manjaro-OpenRC/Nemesis

Re: Nemesis update april-06-2017 discussion

Post#16 by istinnjazz » 14 Apr 2017, 22:12

new gui core module does break my nvidia driver version (constant... acpid client disconnected... @console messages). It works ok with nouveau though, it would probably work with a new nvidia driver of the 340.x branch (most likely with a new compile).
For now I have successfully loaded and used the original gui file alongside with all the other core updates. No problems till now.

Hopefully someone can still use the old gui module without any conflicts. Maybe... later on... if I will have time... I will try to compile a new kernel/nvidia... but for now I am ok.

I cannot say how the updated files will interact with my old savefile.... and all the changes made there from time to time... but it seems manageable...
So the old one with version:
X.Org X Server 1.17.4
Release Date: 2015-10-28
has been used

just for the record:

Code: Select all

[    26.725] 
X.Org X Server 1.17.4
Release Date: 2015-10-28
[    26.725] X Protocol Version 11, Revision 0
[    26.725] Build Operating System: Linux 4.2.5-1-ARCH x86_64 
[    26.725] Current Operating System: Linux porteus 4.6.3-xanmod5-porteus #2 SMP PREEMPT Tue Jul 12 19:06:47 UTC 2016 x86_64
[    26.725] Kernel command line: quiet initrd=dsdt_fixed2_init acpi.debug_level=0x2 acpi.debug_layer=0xFFFFFFFF acpi_osi="!Windows2006" zswap.enabled=1 zswap.compressor=lzo zswap.max_pool_percent=15 zswap.zpool=zbud fsck changes=/porteus/save.dat BOOT_IMAGE=vmlinuz 
[    26.725] Build Date: 01 November 2015  10:36:50AM
[    26.725]  
[    26.725] Current version of pixman: 0.32.8
[    26.725] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[    26.725] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    26.725] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Apr 15 00:41:03 2017
[    26.742] (==) Using config file: "/etc/X11/xorg.conf"
[    26.742] (==) Using config directory: "/etc/X11/xorg.conf.d"
[    26.742] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    26.751] (==) ServerLayout "Layout0"
[    26.751] (**) |-->Screen "Screen0" (0)
[    26.751] (**) |   |-->Monitor "Monitor0"
[    26.751] (**) |   |-->Device "Device0"
[    26.751] (**) |-->Input Device "Keyboard0"
[    26.751] (**) |-->Input Device "Mouse0"
[    26.751] (**) Option "Xinerama" "0"
[    26.751] (==) Automatically adding devices
[    26.751] (==) Automatically enabling devices
[    26.751] (==) Automatically adding GPU devices
[    26.753] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/misc/".
[    26.753] 	Entry deleted from font path.
[    26.753] 	(Run 'mkfontdir' on "/usr/share/fonts/misc/").
[    26.753] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/OTF/".
[    26.753] 	Entry deleted from font path.
[    26.753] 	(Run 'mkfontdir' on "/usr/share/fonts/OTF/").
[    26.754] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[    26.754] 	Entry deleted from font path.
[    26.754] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[    26.754] 	Entry deleted from font path.
[    26.754] 	(Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[    26.754] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[    26.754] 	Entry deleted from font path.
[    26.754] 	(Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[    26.754] (==) FontPath set to:
	/usr/share/fonts/TTF/
[    26.754] (==) ModulePath set to "/usr/lib/xorg/modules"
[    26.754] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[    26.754] (WW) Disabling Keyboard0
[    26.754] (WW) Disabling Mouse0
[    26.754] (II) Loader magic: 0x817d60
[    26.754] (II) Module ABI versions:
[    26.754] 	X.Org ANSI C Emulation: 0.4
[    26.754] 	X.Org Video Driver: 19.0
[    26.754] 	X.Org XInput driver : 21.1
[    26.754] 	X.Org Server Extension : 9.0
[    26.755] (EE) systemd-logind: failed to get session: The name org.freedesktop.login1 was not provided by any .service files
[    26.755] (II) xfree86: Adding drm device (/dev/dri/card0)
[    26.758] (--) PCI:*(0:1:0:0) 10de:040d:103c:30c3 rev 161, Mem @ 0xe5000000/16777216, 0xd0000000/268435456, 0xe6000000/33554432, I/O @ 0x00004000/128, BIOS @ 0x????????/131072
[    26.758] (II) Open ACPI successful (/var/run/acpid.socket)
[    26.758] (II) LoadModule: "glx"
[    26.760] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    26.797] (EE) Failed to load /usr/lib/xorg/modules/extensions/libglx.so: libnvidia-glcore.so.340.96: wrong ELF class: ELFCLASS32
[    26.797] (II) UnloadModule: "glx"
[    26.797] (II) Unloading glx
[    26.797] (EE) Failed to load module "glx" (loader failed, 7)
[    26.797] (II) LoadModule: "nvidia"
[    26.798] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[    26.915] (II) Module nvidia: vendor="NVIDIA Corporation"
[    26.915] 	compiled for 4.0.2, module version = 1.0.0
[    26.915] 	Module class: X.Org Video Driver
[    26.936] (II) NVIDIA dlloader X Driver  340.96  Sun Nov  8 21:46:28 PST 2015
[    26.936] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[    26.936] (++) using VT number 1

[    26.949] (II) Loading sub module "fb"
[    26.949] (II) LoadModule: "fb"
[    26.951] (II) Loading /usr/lib/xorg/modules/libfb.so
[    26.974] (II) Module fb: vendor="X.Org Foundation"
[    26.974] 	compiled for 1.17.4, module version = 1.0.0
[    26.974] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    26.974] (WW) Unresolved symbol: fbGetGCPrivateKey
[    26.974] (II) Loading sub module "wfb"
[    26.974] (II) LoadModule: "wfb"
[    26.975] (II) Loading /usr/lib/xorg/modules/libwfb.so
[    26.976] (II) Module wfb: vendor="X.Org Foundation"
[    26.976] 	compiled for 1.17.4, module version = 1.0.0
[    26.976] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    26.976] (II) Loading sub module "ramdac"
[    26.976] (II) LoadModule: "ramdac"
[    26.976] (II) Module "ramdac" already built-in
[    27.002] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[    27.002] (==) NVIDIA(0): RGB weight 888
[    27.002] (==) NVIDIA(0): Default visual is TrueColor
[    27.002] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[    27.002] (**) NVIDIA(0): Option "Stereo" "0"
[    27.002] (**) NVIDIA(0): Option "nvidiaXineramaInfoOrder" "DFP-1"
[    27.002] (**) NVIDIA(0): Option "SLI" "Off"
[    27.003] (**) NVIDIA(0): Option "MultiGPU" "Off"
[    27.003] (**) NVIDIA(0): Option "BaseMosaic" "off"
[    27.003] (**) NVIDIA(0): Stereo disabled by request
[    27.003] (**) NVIDIA(0): NVIDIA SLI disabled.
[    27.003] (**) NVIDIA(0): NVIDIA Multi-GPU disabled.
[    27.003] (**) NVIDIA(0): Option "MetaModes" "LVDS-0: nvidia-auto-select +1920+0, DVI-D-0: nvidia-auto-select +0+0"
[    27.003] (**) NVIDIA(0): Enabling 2D acceleration
[    27.003] (EE) NVIDIA(0): Failed to initialize the GLX module; please check in your X
[    27.003] (EE) NVIDIA(0):     log file that the GLX module has been loaded in your X
[    27.003] (EE) NVIDIA(0):     server, and that the module is the NVIDIA GLX module.  If
[    27.003] (EE) NVIDIA(0):     you continue to encounter problems, Please try
[    27.003] (EE) NVIDIA(0):     reinstalling the NVIDIA driver.
[    28.132] (II) NVIDIA(0): Display (LPL (DFP-0)) does not support NVIDIA 3D Vision
[    28.132] (II) NVIDIA(0):     stereo.
[    28.209] (II) NVIDIA(0): Display (Eizo SX2461W (DFP-1)) does not support NVIDIA 3D
[    28.209] (II) NVIDIA(0):     Vision stereo.
[    28.209] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20150116)
[    28.211] (II) NVIDIA(0): NVIDIA GPU Quadro FX 1600M (G84GL) at PCI:1:0:0 (GPU-0)
[    28.211] (--) NVIDIA(0): Memory: 524288 kBytes
[    28.211] (--) NVIDIA(0): VideoBIOS: 60.84.74.00.11
[    28.211] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[    28.219] (--) NVIDIA(0): Valid display device(s) on Quadro FX 1600M at PCI:1:0:0
[    28.219] (--) NVIDIA(0):     CRT-0
[    28.219] (--) NVIDIA(0):     TV-0
[    28.219] (--) NVIDIA(0):     LPL (DFP-0) (boot, connected)
[    28.219] (--) NVIDIA(0):     Eizo SX2461W (DFP-1) (connected)
[    28.219] (--) NVIDIA(0):     DFP-2
[    28.219] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
[    28.219] (--) NVIDIA(GPU-0): TV-0: 400.0 MHz maximum pixel clock
[    28.219] (--) NVIDIA(0): LPL (DFP-0): Internal LVDS
[    28.219] (--) NVIDIA(GPU-0): LPL (DFP-0): 330.0 MHz maximum pixel clock
[    28.219] (--) NVIDIA(0): Eizo SX2461W (DFP-1): Internal TMDS
[    28.219] (--) NVIDIA(GPU-0): Eizo SX2461W (DFP-1): 330.0 MHz maximum pixel clock
[    28.219] (--) NVIDIA(0): DFP-2: Internal TMDS
[    28.219] (--) NVIDIA(GPU-0): DFP-2: 330.0 MHz maximum pixel clock
[    28.219] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[    28.219] (**) NVIDIA(0):     device LPL (DFP-0) (Using EDID frequencies has been
[    28.219] (**) NVIDIA(0):     enabled on all display devices.)
[    28.219] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[    28.219] (**) NVIDIA(0):     device Eizo SX2461W (DFP-1) (Using EDID frequencies has
[    28.220] (**) NVIDIA(0):     been enabled on all display devices.)
[    28.221] (II) NVIDIA(0): Validated MetaModes:
[    28.221] (II) NVIDIA(0):    
[    28.221] (II) NVIDIA(0):     "LVDS-0:nvidia-auto-select+1920+0,DVI-D-0:nvidia-auto-select+0+0"
[    28.221] (II) NVIDIA(0): Virtual screen size determined to be 3600 x 1200
[    29.234] (--) NVIDIA(0): DPI set to (115, 115); computed from "UseEdidDpi" X config
[    29.234] (--) NVIDIA(0):     option
[    29.234] (--) Depth 24 pixmap format is 32 bpp
[    29.235] (II) NVIDIA: Using 768.00 MB of virtual memory for indirect memory access.
[    29.271] (II) NVIDIA(0): Setting mode "LVDS-0:nvidia-auto-select+1920+0,DVI-D-0:nvidia-auto-select+0+0"
[    29.752] (==) NVIDIA(0): Disabling shared memory pixmaps
[    29.752] (==) NVIDIA(0): Backing store enabled
[    29.752] (==) NVIDIA(0): Silken mouse enabled
[    29.752] (**) NVIDIA(0): DPMS enabled
[    29.753] (II) Loading sub module "dri2"
[    29.753] (II) LoadModule: "dri2"
[    29.753] (II) Module "dri2" already built-in
[    29.753] (II) NVIDIA(0): [DRI2] Setup complete
[    29.753] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
[    29.753] (--) RandR disabled
[    29.971] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[    29.971] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[    29.971] (**) Power Button: Applying InputClass "Generic Keyboard"
[    29.971] (II) LoadModule: "evdev"
[    29.972] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[    30.006] (II) Module evdev: vendor="X.Org Foundation"
[    30.006] 	compiled for 1.17.4, module version = 2.10.0
[    30.006] 	Module class: X.Org XInput Driver
[    30.006] 	ABI class: X.Org XInput driver, version 21.1
[    30.006] (II) Using input driver 'evdev' for 'Power Button'
[    30.006] (**) Option "CoreKeyboard"
[    30.006] (**) Power Button: always reports core events
[    30.006] (**) evdev: Power Button: Device: "/dev/input/event2"
[    30.006] (--) evdev: Power Button: Vendor 0 Product 0x1
[    30.006] (--) evdev: Power Button: Found keys
[    30.006] (II) evdev: Power Button: Configuring as keyboard
[    30.006] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2"
[    30.006] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[    30.006] (**) Option "xkb_rules" "evdev"
[    30.006] (**) Option "xkb_model" "pc105"
[    30.006] (**) Option "xkb_layout" "us,el"
[    30.006] (**) Option "xkb_options" "grp:alt_shift_toggle,compose:menu,grp_led:scroll"
[    30.049] (II) config/udev: Adding input device Video Bus (/dev/input/event3)
[    30.049] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[    30.049] (**) Video Bus: Applying InputClass "Generic Keyboard"
[    30.049] (II) Using input driver 'evdev' for 'Video Bus'
[    30.049] (**) Option "CoreKeyboard"
[    30.049] (**) Video Bus: always reports core events
[    30.049] (**) evdev: Video Bus: Device: "/dev/input/event3"
[    30.049] (--) evdev: Video Bus: Vendor 0 Product 0x6
[    30.049] (--) evdev: Video Bus: Found keys
[    30.049] (II) evdev: Video Bus: Configuring as keyboard
[    30.049] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/LNXVIDEO:00/input/input3/event3"
[    30.049] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[    30.049] (**) Option "xkb_rules" "evdev"
[    30.049] (**) Option "xkb_model" "pc105"
[    30.049] (**) Option "xkb_layout" "us,el"
[    30.049] (**) Option "xkb_options" "grp:alt_shift_toggle,compose:menu,grp_led:scroll"
[    30.049] (II) config/udev: Adding input device Lid Switch (/dev/input/event1)
[    30.050] (II) No input driver specified, ignoring this device.
[    30.050] (II) This device may have been added with another device file.
[    30.050] (II) config/udev: Adding input device Sleep Button (/dev/input/event0)
[    30.050] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[    30.050] (**) Sleep Button: Applying InputClass "Generic Keyboard"
[    30.050] (II) Using input driver 'evdev' for 'Sleep Button'
[    30.050] (**) Option "CoreKeyboard"
[    30.050] (**) Sleep Button: always reports core events
[    30.050] (**) evdev: Sleep Button: Device: "/dev/input/event0"
[    30.050] (--) evdev: Sleep Button: Vendor 0 Product 0x3
[    30.050] (--) evdev: Sleep Button: Found keys
[    30.050] (II) evdev: Sleep Button: Configuring as keyboard
[    30.050] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0/event0"
[    30.050] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 8)
[    30.050] (**) Option "xkb_rules" "evdev"
[    30.050] (**) Option "xkb_model" "pc105"
[    30.050] (**) Option "xkb_layout" "us,el"
[    30.050] (**) Option "xkb_options" "grp:alt_shift_toggle,compose:menu,grp_led:scroll"
[    30.051] (II) config/udev: Adding input device HDA Intel Mic (/dev/input/event10)
[    30.051] (II) No input driver specified, ignoring this device.
[    30.051] (II) This device may have been added with another device file.
[    30.051] (II) config/udev: Adding input device HDA Intel Line (/dev/input/event11)
[    30.051] (II) No input driver specified, ignoring this device.
[    30.051] (II) This device may have been added with another device file.
[    30.051] (II) config/udev: Adding input device HDA Intel Headphone (/dev/input/event12)
[    30.051] (II) No input driver specified, ignoring this device.
[    30.051] (II) This device may have been added with another device file.
[    30.051] (II) config/udev: Adding input device A4Tech USB Mouse (/dev/input/event13)
[    30.051] (**) A4Tech USB Mouse: Applying InputClass "evdev pointer catchall"
[    30.051] (II) Using input driver 'evdev' for 'A4Tech USB Mouse'
[    30.051] (**) A4Tech USB Mouse: always reports core events
[    30.052] (**) evdev: A4Tech USB Mouse: Device: "/dev/input/event13"
[    30.103] (--) evdev: A4Tech USB Mouse: Vendor 0x9da Product 0xa
[    30.103] (--) evdev: A4Tech USB Mouse: Found 12 mouse buttons
[    30.103] (--) evdev: A4Tech USB Mouse: Found scroll wheel(s)
[    30.103] (--) evdev: A4Tech USB Mouse: Found relative axes
[    30.103] (--) evdev: A4Tech USB Mouse: Found x and y relative axes
[    30.103] (II) evdev: A4Tech USB Mouse: Configuring as mouse
[    30.103] (II) evdev: A4Tech USB Mouse: Adding scrollwheel support
[    30.103] (**) evdev: A4Tech USB Mouse: YAxisMapping: buttons 4 and 5
[    30.103] (**) evdev: A4Tech USB Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[    30.103] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.1/usb6/6-1/6-1:1.0/0003:09DA:000A.0003/input/input20/event13"
[    30.103] (II) XINPUT: Adding extended input device "A4Tech USB Mouse" (type: MOUSE, id 9)
[    30.103] (II) evdev: A4Tech USB Mouse: initialized for relative axes.
[    30.103] (**) A4Tech USB Mouse: (accel) keeping acceleration scheme 1
[    30.103] (**) A4Tech USB Mouse: (accel) acceleration profile 0
[    30.103] (**) A4Tech USB Mouse: (accel) acceleration factor: 2.000
[    30.103] (**) A4Tech USB Mouse: (accel) acceleration threshold: 4
[    30.103] (II) config/udev: Adding input device A4Tech USB Mouse (/dev/input/mouse2)
[    30.103] (II) No input driver specified, ignoring this device.
[    30.103] (II) This device may have been added with another device file.
[    30.104] (II) config/udev: Adding input device CHESEN USB Keyboard (/dev/input/event6)
[    30.104] (**) CHESEN USB Keyboard: Applying InputClass "evdev keyboard catchall"
[    30.104] (**) CHESEN USB Keyboard: Applying InputClass "Generic Keyboard"
[    30.104] (II) Using input driver 'evdev' for 'CHESEN USB Keyboard'
[    30.104] (**) Option "CoreKeyboard"
[    30.104] (**) CHESEN USB Keyboard: always reports core events
[    30.104] (**) evdev: CHESEN USB Keyboard: Device: "/dev/input/event6"
[    30.104] (--) evdev: CHESEN USB Keyboard: Vendor 0xa81 Product 0x101
[    30.104] (--) evdev: CHESEN USB Keyboard: Found keys
[    30.104] (II) evdev: CHESEN USB Keyboard: Configuring as keyboard
[    30.104] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1.2/2-1.2:1.0/0003:0A81:0101.0001/input/input14/event6"
[    30.104] (II) XINPUT: Adding extended input device "CHESEN USB Keyboard" (type: KEYBOARD, id 10)
[    30.104] (**) Option "xkb_rules" "evdev"
[    30.104] (**) Option "xkb_model" "pc105"
[    30.104] (**) Option "xkb_layout" "us,el"
[    30.104] (**) Option "xkb_options" "grp:alt_shift_toggle,compose:menu,grp_led:scroll"
[    30.106] (II) config/udev: Adding input device CHESEN USB Keyboard (/dev/input/event7)
[    30.106] (**) CHESEN USB Keyboard: Applying InputClass "evdev keyboard catchall"
[    30.106] (**) CHESEN USB Keyboard: Applying InputClass "Generic Keyboard"
[    30.106] (II) Using input driver 'evdev' for 'CHESEN USB Keyboard'
[    30.106] (**) Option "CoreKeyboard"
[    30.106] (**) CHESEN USB Keyboard: always reports core events
[    30.106] (**) evdev: CHESEN USB Keyboard: Device: "/dev/input/event7"
[    30.106] (--) evdev: CHESEN USB Keyboard: Vendor 0xa81 Product 0x101
[    30.106] (--) evdev: CHESEN USB Keyboard: Found keys
[    30.106] (II) evdev: CHESEN USB Keyboard: Configuring as keyboard
[    30.106] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1.2/2-1.2:1.1/0003:0A81:0101.0002/input/input15/event7"
[    30.106] (II) XINPUT: Adding extended input device "CHESEN USB Keyboard" (type: KEYBOARD, id 11)
[    30.106] (**) Option "xkb_rules" "evdev"
[    30.106] (**) Option "xkb_model" "pc105"
[    30.106] (**) Option "xkb_layout" "us,el"
[    30.106] (**) Option "xkb_options" "grp:alt_shift_toggle,compose:menu,grp_led:scroll"
[    30.107] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event4)
[    30.107] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[    30.107] (**) AT Translated Set 2 keyboard: Applying InputClass "Generic Keyboard"
[    30.108] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[    30.108] (**) Option "CoreKeyboard"
[    30.108] (**) AT Translated Set 2 keyboard: always reports core events
[    30.108] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event4"
[    30.108] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[    30.108] (--) evdev: AT Translated Set 2 keyboard: Found keys
[    30.108] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[    30.108] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input4/event4"
[    30.108] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 12)
[    30.108] (**) Option "xkb_rules" "evdev"
[    30.108] (**) Option "xkb_model" "pc105"
[    30.108] (**) Option "xkb_layout" "us,el"
[    30.108] (**) Option "xkb_options" "grp:alt_shift_toggle,compose:menu,grp_led:scroll"
[    30.109] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event5)
[    30.109] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
[    30.109] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
[    30.109] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
[    30.109] (II) LoadModule: "synaptics"
[    30.111] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[    30.124] (II) Module synaptics: vendor="X.Org Foundation"
[    30.124] 	compiled for 1.17.4, module version = 1.8.3
[    30.124] 	Module class: X.Org XInput Driver
[    30.124] 	ABI class: X.Org XInput driver, version 21.1
[    30.124] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
[    30.124] (**) SynPS/2 Synaptics TouchPad: always reports core events
[    30.125] (**) Option "Device" "/dev/input/event5"
[    30.147] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5472 (res 70)
[    30.147] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4448 (res 107)
[    30.147] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
[    30.147] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
[    30.147] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left right middle double triple
[    30.147] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
[    30.147] (**) Option "TapButton1" "1"
[    30.147] (**) Option "TapButton2" "2"
[    30.147] (**) Option "TapButton3" "3"
[    30.147] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[    30.147] (**) SynPS/2 Synaptics TouchPad: always reports core events
[    30.159] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio4/input/input12/event5"
[    30.159] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 13)
[    30.159] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
[    30.159] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
[    30.159] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.040
[    30.159] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
[    30.159] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
[    30.159] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
[    30.159] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
[    30.159] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[    30.159] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
[    30.159] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
[    30.159] (II) config/udev: Adding input device PS/2 Generic Mouse (/dev/input/event8)
[    30.159] (**) PS/2 Generic Mouse: Applying InputClass "evdev pointer catchall"
[    30.159] (II) Using input driver 'evdev' for 'PS/2 Generic Mouse'
[    30.159] (**) PS/2 Generic Mouse: always reports core events
[    30.160] (**) evdev: PS/2 Generic Mouse: Device: "/dev/input/event8"
[    30.160] (--) evdev: PS/2 Generic Mouse: Vendor 0x2 Product 0x1
[    30.160] (--) evdev: PS/2 Generic Mouse: Found 3 mouse buttons
[    30.160] (--) evdev: PS/2 Generic Mouse: Found relative axes
[    30.160] (--) evdev: PS/2 Generic Mouse: Found x and y relative axes
[    30.160] (II) evdev: PS/2 Generic Mouse: Configuring as mouse
[    30.160] (**) evdev: PS/2 Generic Mouse: YAxisMapping: buttons 4 and 5
[    30.160] (**) evdev: PS/2 Generic Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[    30.160] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio4/serio5/input/input13/event8"
[    30.160] (II) XINPUT: Adding extended input device "PS/2 Generic Mouse" (type: MOUSE, id 14)
[    30.160] (II) evdev: PS/2 Generic Mouse: initialized for relative axes.
[    30.160] (**) PS/2 Generic Mouse: (accel) keeping acceleration scheme 1
[    30.160] (**) PS/2 Generic Mouse: (accel) acceleration profile 0
[    30.160] (**) PS/2 Generic Mouse: (accel) acceleration factor: 2.000
[    30.160] (**) PS/2 Generic Mouse: (accel) acceleration threshold: 4
[    30.160] (II) config/udev: Adding input device PS/2 Generic Mouse (/dev/input/mouse1)
[    30.160] (II) No input driver specified, ignoring this device.
[    30.160] (II) This device may have been added with another device file.
[    30.160] (II) config/udev: Adding input device ST LIS3LV02DL Accelerometer (/dev/input/event9)
[    30.160] (II) No input driver specified, ignoring this device.
[    30.160] (II) This device may have been added with another device file.
[    30.161] (II) config/udev: Adding input device ST LIS3LV02DL Accelerometer (/dev/input/js0)
[    30.161] (II) No input driver specified, ignoring this device.
[    30.161] (II) This device may have been added with another device file.
[    30.161] (II) config/udev: Adding input device HP WMI hotkeys (/dev/input/event14)
[    30.161] (**) HP WMI hotkeys: Applying InputClass "evdev keyboard catchall"
[    30.161] (**) HP WMI hotkeys: Applying InputClass "Generic Keyboard"
[    30.161] (II) Using input driver 'evdev' for 'HP WMI hotkeys'
[    30.161] (**) Option "CoreKeyboard"
[    30.161] (**) HP WMI hotkeys: always reports core events
[    30.161] (**) evdev: HP WMI hotkeys: Device: "/dev/input/event14"
[    30.161] (--) evdev: HP WMI hotkeys: Vendor 0 Product 0
[    30.161] (--) evdev: HP WMI hotkeys: Found keys
[    30.161] (II) evdev: HP WMI hotkeys: Configuring as keyboard
[    30.161] (**) Option "config_info" "udev:/sys/devices/virtual/input/input21/event14"
[    30.161] (II) XINPUT: Adding extended input device "HP WMI hotkeys" (type: KEYBOARD, id 15)
[    30.161] (**) Option "xkb_rules" "evdev"
[    30.161] (**) Option "xkb_model" "pc105"
[    30.161] (**) Option "xkb_layout" "us,el"
[    30.161] (**) Option "xkb_options" "grp:alt_shift_toggle,compose:menu,grp_led:scroll"
[    40.704] (II) NVIDIA(GPU-0): Display (LPL (DFP-0)) does not support NVIDIA 3D Vision
[    40.704] (II) NVIDIA(GPU-0):     stereo.
[    40.759] (II) NVIDIA(GPU-0): Display (Eizo SX2461W (DFP-1)) does not support NVIDIA 3D
[    40.759] (II) NVIDIA(GPU-0):     Vision stereo.
Keep it up...

User avatar
istinnjazz
Samurai
Samurai
Posts: 114
Joined: 15 May 2016, 14:10
Distribution: Manjaro-OpenRC/Nemesis

Re: Nemesis update april-06-2017 discussion

Post#17 by istinnjazz » 14 Apr 2017, 22:15

beny wrote:hi istinnjazz but nemesis work for you the first edition? if yes you can upgrade only the x package with the last xorg and the last mesa and repack .
thanks!!, I have just did this ...before reading your message... nice1 :)

it is very clever to have a separated and independent xorg module... this could be very beneficial for old gpu compatibility and of course to keep hard to recompile driver/kernel compilations.

User avatar
ncmprhnsbl
Full of knowledge
Full of knowledge
Posts: 786
Joined: 20 Mar 2012, 03:42
Distribution: 3.2.2-64bit xfce/openbox
Location: australia
Contact:

Re: Nemesis update april-06-2017 discussion

Post#18 by ncmprhnsbl » 14 Apr 2017, 22:36

@istinnjazz .. my comment was directed at you (i didnt notice francois' comment for some reason)
i see you have found a solution :good:
this topic: viewtopic.php?f=138&t=6484 outlines a method/commands that can be used to upgrade other modules you may have..
Forum Rules : http://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
istinnjazz
Samurai
Samurai
Posts: 114
Joined: 15 May 2016, 14:10
Distribution: Manjaro-OpenRC/Nemesis

Re: Nemesis update april-06-2017 discussion

Post#19 by istinnjazz » 14 Apr 2017, 22:56

nice...

I will have to study a bit because I tend to forget some parts i have left behind...

so lets say I have an almost updated file system through my savefile... and then I will try to update a base module like yours or the lxde one by the new method...
Is there a possibility that might be a conflict? what is the aufs layer priority in that case? savefile or the core module (or a simple module)?

is this order right? savefile ->user-module->base-core-module ?

what about a clean function for the savefile that can remove some old outdated duplicated files that are older than core? (of course there might be constant garbage files @ savefile, but I guess without any harm, until a package or system update function will replace them or delete them in the future again and again.

So if savefile has previous versions of the updated core files will the system know and refine this?

User avatar
ncmprhnsbl
Full of knowledge
Full of knowledge
Posts: 786
Joined: 20 Mar 2012, 03:42
Distribution: 3.2.2-64bit xfce/openbox
Location: australia
Contact:

Re: Nemesis update april-06-2017 discussion

Post#20 by ncmprhnsbl » 15 Apr 2017, 09:21

istinnjazz wrote:what is the aufs layer priority in that case?
order is: base modules first , user modules, then changes
each layering on top of the last, potentially overwriting an underlying file..
so, yes changes takes priority..
istinnjazz wrote:Is there a possibility that might be a conflict?
yes, this could present a problem..
running #pacman -Syu will complain of duplicated database entries if package(s) are in more than one place(modules or changes)
if it also wants to upgrade that package it/they can probly be removed from the changes folder using :
#pacman -R --root=/path/to/changes <package(s)> (i think thats the right command)
as opposed to just pacman -R <package> which will put whiteouts in the changes folder(which effectively removes the package completely from the live system)
istinnjazz wrote:what about a clean function for the savefile that can remove some old outdated duplicated files that are older than core?
sounds nice :) but beyond my feeble scripting abilities... :cry:
istinnjazz wrote:So if savefile has previous versions of the updated core files will the system know and refine this?
the system knows nothing.. :unknown:
Forum Rules : http://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
istinnjazz
Samurai
Samurai
Posts: 114
Joined: 15 May 2016, 14:10
Distribution: Manjaro-OpenRC/Nemesis

Re: Nemesis update april-06-2017 discussion

Post#21 by istinnjazz » 15 Apr 2017, 09:41

ncmprhnsbl wrote:
istinnjazz wrote:what is the aufs layer priority in that case?
order is: base modules first , user modules, then changes

...
...
thanks for the explanation

User avatar
istinnjazz
Samurai
Samurai
Posts: 114
Joined: 15 May 2016, 14:10
Distribution: Manjaro-OpenRC/Nemesis

Re: Nemesis update april-06-2017 discussion

Post#22 by istinnjazz » 15 Apr 2017, 10:29

the duplicated files, pacman shows the related packages, so I have a very first clue of the conflicting entries

Code: Select all

guest ~ $ su
Password: 
root /home/guest # pacman -S pacman
error: duplicated database entry 'alsa-utils-openrc'
error: duplicated database entry 'libpulse'
error: duplicated database entry 'acpid'
error: duplicated database entry 'acpid-openrc'
error: duplicated database entry 'archlinux-keyring'
error: duplicated database entry 'ca-certificates'
error: duplicated database entry 'cgmanager-openrc'
error: duplicated database entry 'consolekit'
error: duplicated database entry 'consolekit-openrc'
error: duplicated database entry 'cronie'
error: duplicated database entry 'cronie-openrc'
error: duplicated database entry 'dbus-glib'
error: duplicated database entry 'dbus-openrc'
error: duplicated database entry 'device-mapper'
error: duplicated database entry 'device-mapper-openrc'
error: duplicated database entry 'dhcpcd'
error: duplicated database entry 'dhcpcd-openrc'
error: duplicated database entry 'downgrade'
error: duplicated database entry 'eudev'
error: duplicated database entry 'gcc-libs'
error: duplicated database entry 'glib-networking'
error: duplicated database entry 'glib2'
error: duplicated database entry 'glibc'
error: duplicated database entry 'glibc-openrc'
error: duplicated database entry 'gpm'
error: duplicated database entry 'gpm-openrc'
error: duplicated database entry 'haveged-openrc'
error: duplicated database entry 'inetutils-openrc'
error: duplicated database entry 'iptables-openrc'
error: duplicated database entry 'json-c'
error: duplicated database entry 'libmnl'
error: duplicated database entry 'libnftnl'
error: duplicated database entry 'libnm-glib'
error: duplicated database entry 'libsecret'
error: duplicated database entry 'lzo'
error: duplicated database entry 'mdadm'
error: duplicated database entry 'mdadm-openrc'
error: duplicated database entry 'networkmanager-consolekit'
error: duplicated database entry 'networkmanager-openrc'
error: duplicated database entry 'ntp'
error: duplicated database entry 'ntp-openrc'
error: duplicated database entry 'openrc'
error: duplicated database entry 'openssh'
error: duplicated database entry 'openssh-openrc'
error: duplicated database entry 'openvpn'
error: duplicated database entry 'openvpn-openrc'
error: duplicated database entry 'pacman'
error: duplicated database entry 'perl'
error: duplicated database entry 'syslog-ng'
error: duplicated database entry 'syslog-ng-openrc'
error: duplicated database entry 'udev-openrc'
:: Some packages should be upgraded first...
resolving dependencies...
looking for conflicting packages...

Packages (1) archlinux-keyring-20170320-1

Total Download Size:   0.62 MiB
Total Installed Size:  0.86 MiB
Net Upgrade Size:      0.08 MiB

:: Proceed with installation? [Y/n] 

User avatar
istinnjazz
Samurai
Samurai
Posts: 114
Joined: 15 May 2016, 14:10
Distribution: Manjaro-OpenRC/Nemesis

Re: Nemesis update april-06-2017 discussion

Post#23 by istinnjazz » 15 Apr 2017, 17:13

for those who might use nvidia linux driver and 304.xx or 340.xx branch, support for xorg 1.19 included in this update. Not tested but should work if compiled with the kernel in use.
http://www.nvidia.com/object/unix.html

Version: 340.102
Release Date: 2017.2.14
Operating System: Linux 64-bit
Language: English (US)
File Size: 66.72 MB

Version: 304.135
Release Date: 2017.2.14
Operating System: Linux 64-bit
Language: English (US)
File Size: 66.53 MB

Added support for X.Org xserver ABI 23 (xorg-server 1.19)
Fixed a bug that allowed nvidia-installer to attempt loading kernel modules that were built against non-running kernels.

User avatar
francois
Contributor
Contributor
Posts: 4902
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: Nemesis update april-06-2017 discussion

Post#24 by francois » 15 Apr 2017, 19:05

Hello istinjazz. Welcome back!

A separate thread, maybe a howto for nvidia drivers under nemesis would be a great contribution. :wink:

And as you have a special type of computer, a thread on your hardware and nemesis would be a treat. :twisted:

Are you working on fat32 or linux filesystem?
Voltaire: Le mieux est l'ennemi du bien.

User avatar
istinnjazz
Samurai
Samurai
Posts: 114
Joined: 15 May 2016, 14:10
Distribution: Manjaro-OpenRC/Nemesis

Re: Nemesis update april-06-2017 discussion

Post#25 by istinnjazz » 15 Apr 2017, 21:23

francois wrote: A separate thread, maybe a howto for nvidia drivers under nemesis would be a great contribution. :wink:

And as you have a special type of computer, a thread on your hardware and nemesis would be a treat. :twisted:
francois wrote:Are you working on fat32 or linux filesystem?
Yap, I see your point francois, if I will have a reason to do this again I will log the steps for a howto, it is a combination of the main porteus website kernel-compile how-to and blaze's nvidia topic (Russian).. but I cannot tell if or when this will happen.
Some additional info...
For my notebook I also have used a custom dsdt table, loaded via the compiled kernel with special config parameters and additional initrd modification to include the dsdt override. This was a tricky one , there is a strange and sometimes dangerous fan speed acpi bug @ this notebook not resolved at any of the kernels later of 3.12

Finally, I also had tested btrfs file system with success as an alternative to ext4 for the changes file, slower but I guess safer. Also with customized kernel configuration @ compile stage.

For a bit of experimentation I had used a sort of "modified" version of the kernel called "xanmod", you can search for it if you want and download the sources, it includes already the aufs patch if I remember correctly. https://xanmod.org/

System: SD card @ fat32

User avatar
francois
Contributor
Contributor
Posts: 4902
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: Nemesis update april-06-2017 discussion

Post#26 by francois » 15 Apr 2017, 23:16

With a small fat32 first partition, you could install nemesis on a second partition which could be linux. This way the changes file is no more a container, thus size limited to the second partition. A first partition in fat32 is necessary if you use to boot windows once and a while. It is more natural to have a linux OS on a linux filesystem. But I imagine that you knew that already. :wink:
Voltaire: Le mieux est l'ennemi du bien.

User avatar
istinnjazz
Samurai
Samurai
Posts: 114
Joined: 15 May 2016, 14:10
Distribution: Manjaro-OpenRC/Nemesis

Re: Nemesis update april-06-2017 discussion

Post#27 by istinnjazz » 16 Apr 2017, 10:50

francois wrote:With a small fat32 first partition, you could install nemesis on a second partition which could be linux. This way the changes file is no more a container, thus size limited to the second partition. A first partition in fat32 is necessary if you use to boot windows once and a while. It is more natural to have a linux OS on a linux filesystem. But I imagine that you knew that already. :wink:
Yap, I know, I just like the container for various reasons but I had used native also, there has been a discussion about it some time ago considering flash memory life span and Linux file systems if you remember (file system corruption, ext4 journaling on/off, btrfs etc).
I agree with you about the native fs superiority, Fat32 has limits, e.g max container file size on fat32. I was wondering what other file systems the system could support for the sd formatting (ntfs, ext4) to hold a container more than 4GB. Is this possible?

User avatar
Ed_P
Contributor
Contributor
Posts: 3058
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Nemesis update april-06-2017 discussion

Post#28 by Ed_P » 16 Apr 2017, 18:04

istinnjazz wrote:Fat32 has limits, e.g max container file size on fat32. I was wondering what other file systems the system could support for the sd formatting (ntfs, ext4) to hold a container more than 4GB. Is this possible?
I'm pretty sure NTFS is supported and possibly exFAT. But not everything has to be stored in a "container", large downloads for example can be stored directly on the drive. My save.dat file for years use to be 320 MB, then 512 MB and now it is 1 GB due to Wine's requirements. Basically my save.dat is for system settings and configurations and caches, and my bash scripts. Even my modules are stored directly on the drive.
Ed

User avatar
istinnjazz
Samurai
Samurai
Posts: 114
Joined: 15 May 2016, 14:10
Distribution: Manjaro-OpenRC/Nemesis

Re: Nemesis update april-06-2017 discussion

Post#29 by istinnjazz » 22 Apr 2017, 18:47

Ed_P wrote:
istinnjazz wrote:Fat32 has limits, e.g max container file size on fat32. I was wondering what other file systems the system could support for the sd formatting (ntfs, ext4) to hold a container more than 4GB. Is this possible?
I'm pretty sure NTFS is supported and possibly exFAT. But not everything has to be stored in a "container", large downloads for example can be stored directly on the drive. My save.dat file for years use to be 320 MB, then 512 MB and now it is 1 GB due to Wine's requirements. Basically my save.dat is for system settings and configurations and caches, and my bash scripts. Even my modules are stored directly on the drive.
@ ed_p, thanks for the info. I will test ntfs probably and report back. I suppose it will have some benefits over fat32 at least for possible inconsistencies or corruption. I do not know.
I have used savefile a lot for some packages because I was a bit lazy to create some xzm packages or big xzm changes versions, but I use a ext4 hdd partition for pacman full package cache (a grow up fast directory).

So if I want to create a xzm from an already installed package, I think I will have to uninstall it and then reinstall with pman, or create a full changes file xzm snapshot and free up the changes file.
But then, if I will need to clean things up later, it might be difficult because of the lack of clean up functions. But if someone is careful could do it with minimal garbage files around.

@fransois, I have tried to recompile a recent kernel (4.9 LTS) but it gives me acpi errors and breaks the custom dsdt table I use @ initrd level, for the time being I have not have time to research this, so I will keep the old one for some months and see. I will let you know if I will do a full kernel-nvidia compile with logged instructions.

User avatar
istinnjazz
Samurai
Samurai
Posts: 114
Joined: 15 May 2016, 14:10
Distribution: Manjaro-OpenRC/Nemesis

Re: Nemesis update april-06-2017 discussion

Post#30 by istinnjazz » 22 Apr 2017, 20:21

I would like to note that I have just seen significant changes to the latest update of openrc manjaro packages, there will be conflicts updating to the latest base, messages like this may come out:

Code: Select all

:: Starting full system upgrade...
:: Replace cgmanager-openrc with community/elogind-openrc? [Y/n] y
:: Replace consolekit with community/elogind? [Y/n] y
:: Replace consolekit-openrc with community/elogind-openrc? [Y/n] y
:: Replace libdbus with core/dbus? [Y/n] y
:: Replace pacman-mirrorlist with core/pacman-mirrors? [Y/n] y
:: Replace pm-utils with community/elogind? [Y/n] y
:: Replace polkit-consolekit with community/polkit-elogind? [Y/n] y
:: Replace udev-openrc with community/eudev-openrc? [Y/n] y
and after this there might be many conflicting packages and forced removals maybe needed depending on installation, preventing the update and/or break the system apart. So.. backup.
I did not update, but some help might be this post: https://forum.manjaro.org/t/solved-just ... cies/21818

Post Reply