You are not logged in.
- Topics: Active | Unanswered
#1 Re: Desktop and Multimedia » Devuan-Beowulf Resolution, 4k-monitor, 10-bit. » 2021-01-28 13:47:28
Thanks @jay00,
The problem is not only the resolution, I ask also about the resolution in order to get at least a reasonable resolution in the VM.
The biggest problem is that the DE not start at all on real machine and apparently is not of interest to communicate a step-by-step procedure to investigate and solve the issue.
Other OS like Cento (or Gento, I don't remember exactly) also not using 'systemd' have big graphical problems too. On most notebooks are not usable if the user is not cooder or geek.
Maybe Beowulf will start on my hardware if I install XFCE (standard) and add KDE later-on but this is the same as to install Ubuntu with encrypted ZFS-ROOT and install on the top KDE with the result of a kind of Kubuntu (but with all advertisement of Ubuntu on it) with ZFS-encrypted-ROOT. I don't want it!
The other biggest problem is GTK (now announced GTK-4). If someone want an homogeneous DE-UI than is CSD (client-side-decoration) worse and very similar to Windows, Qt use SSD (server-side-decoration). Of course, also under Qt are some apps with hard-cooded appearances.
Lastly I tested Manjaro-KDE that was perfect, all EDID information recognized by default and inserted/reported perfectly in 'xorg', 'xrandir' with the right dimensions, quantity of pixels, etc.. BTW easy installation, rock-solid and all additional software (e.g. motherboard, mouse, keyboard-lighting, printers, etc., etc.) is in the AUR and all in 64-bit. Long story short, all notebooks became this OS, the two big-ones became Arch-KDE.
#2 Re: Desktop and Multimedia » amdgpu-pro drivers » 2020-09-07 16:45:43
Looks like MX is booted in VirtualBox (they include the guest additions in the stock system), was Devuan also in VirtualBox and if so did it also have the guest additions installed?
'Synaptic' report a 'virtualbox-guest-addition.iso' is installed, I remove it. To be able to copy/paste between host and guest I installed it in the virtual-os. In this way I have full resolution as expected, but... you say 'it's crap'.
Does it mean that if I install the OS on real hardware will start and run normally?
Now with Guest-addition.iso can I post /var/log/
[ 5.984] (--) Log file renamed from "/var/log/Xorg.pid-3050.log" to "/var/log/Xorg.0.log"
[ 5.985]
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
[ 5.985] Build Operating System: Linux 4.19.0-10-amd64 x86_64 Debian
[ 5.985] Current Operating System: Linux devuan3 5.7.0-0.bpo.2-amd64 #1 SMP Debian 5.7.10-1~bpo10+1 (2020-07-30) x86_64
[ 5.985] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.7.0-0.bpo.2-amd64 root=UUID=617b22fa-55d1-4a35-94fa-73bd82eadd69 ro quiet
[ 5.985] Build Date: 27 August 2020 08:51:48AM
[ 5.985] xorg-server 2:1.20.4-1+deb10u1 (https://www.debian.org/support)
[ 5.985] Current version of pixman: 0.36.0
[ 5.985] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 5.985] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 5.985] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Sep 7 11:53:01 2020
[ 5.987] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 5.988] (==) No Layout section. Using the first Screen section.
[ 5.988] (==) No screen section available. Using defaults.
[ 5.988] (**) |-->Screen "Default Screen Section" (0)
[ 5.988] (**) | |-->Monitor "<default monitor>"
[ 5.988] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 5.988] (==) Automatically adding devices
[ 5.988] (==) Automatically enabling devices
[ 5.988] (==) Automatically adding GPU devices
[ 5.989] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 5.989] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 5.989] Entry deleted from font path.
[ 5.991] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[ 5.991] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 5.991] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 5.991] (II) Loader magic: 0x558131fe2e20
[ 5.991] (II) Module ABI versions:
[ 5.991] X.Org ANSI C Emulation: 0.4
[ 5.991] X.Org Video Driver: 24.0
[ 5.991] X.Org XInput driver : 24.1
[ 5.991] X.Org Server Extension : 10.0
[ 5.991] (++) using VT number 7
[ 5.991] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[ 5.992] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 5.993] (--) PCI:*(0@0:2:0) 15ad:0405:15ad:0405 rev 0, Mem @ 0xf0000000/134217728, 0xf8000000/2097152, I/O @ 0x0000d010/16, BIOS @ 0x????????/131072
[ 5.993] (II) LoadModule: "glx"
[ 5.993] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 6.000] (II) Module glx: vendor="X.Org Foundation"
[ 6.000] compiled for 1.20.4, module version = 1.0.0
[ 6.000] ABI class: X.Org Server Extension, version 10.0
[ 6.000] (==) Matched vmware as autoconfigured driver 0
[ 6.000] (==) Matched modesetting as autoconfigured driver 1
[ 6.000] (==) Matched fbdev as autoconfigured driver 2
[ 6.000] (==) Matched vesa as autoconfigured driver 3
[ 6.000] (==) Assigned the driver to the xf86ConfigLayout
[ 6.000] (II) LoadModule: "vmware"
[ 6.001] (II) Loading /usr/lib/xorg/modules/drivers/vmware_drv.so
[ 6.068] (II) Module vmware: vendor="X.Org Foundation"
[ 6.068] compiled for 1.20.0, module version = 13.3.0
[ 6.068] Module class: X.Org Video Driver
[ 6.068] ABI class: X.Org Video Driver, version 24.0
[ 6.068] (II) LoadModule: "modesetting"
[ 6.068] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 6.068] (II) Module modesetting: vendor="X.Org Foundation"
[ 6.068] compiled for 1.20.4, module version = 1.20.4
[ 6.069] Module class: X.Org Video Driver
[ 6.069] ABI class: X.Org Video Driver, version 24.0
[ 6.069] (II) LoadModule: "fbdev"
[ 6.069] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 6.069] (II) Module fbdev: vendor="X.Org Foundation"
[ 6.069] compiled for 1.20.0, module version = 0.5.0
[ 6.069] Module class: X.Org Video Driver
[ 6.069] ABI class: X.Org Video Driver, version 24.0
[ 6.069] (II) LoadModule: "vesa"
[ 6.069] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 6.069] (II) Module vesa: vendor="X.Org Foundation"
[ 6.069] compiled for 1.20.1, module version = 2.4.0
[ 6.069] Module class: X.Org Video Driver
[ 6.069] ABI class: X.Org Video Driver, version 24.0
[ 6.069] (II) vmware: driver for VMware SVGA: vmware0405, vmware0710
[ 6.069] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 6.069] (II) FBDEV: driver for framebuffer: fbdev
[ 6.069] (II) VESA: driver for VESA chipsets: vesa
[ 6.071] (WW) Falling back to old probe method for modesetting
[ 6.071] (WW) Falling back to old probe method for fbdev
[ 6.071] (II) Loading sub module "fbdevhw"
[ 6.071] (II) LoadModule: "fbdevhw"
[ 6.071] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 6.072] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 6.072] compiled for 1.20.4, module version = 0.0.2
[ 6.072] ABI class: X.Org Video Driver, version 24.0
[ 6.072] (II) vmware(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 6.072] (--) vmware(0): DRM driver version is 2.18.0
[ 6.072] (==) vmware(0): Depth 24, (--) framebuffer bpp 32
[ 6.072] (==) vmware(0): RGB weight 888
[ 6.072] (==) vmware(0): Default visual is TrueColor
[ 6.072] (--) vmware(0): Min width 1, Max Width 8192.
[ 6.072] (--) vmware(0): Min height 1, Max Height 8192.
[ 6.072] (II) vmware(0): Output Virtual1 has no monitor section
[ 6.072] (II) vmware(0): Output Virtual2 has no monitor section
[ 6.072] (II) vmware(0): Output Virtual3 has no monitor section
[ 6.072] (II) vmware(0): Output Virtual4 has no monitor section
[ 6.072] (II) vmware(0): Output Virtual5 has no monitor section
[ 6.072] (II) vmware(0): Output Virtual6 has no monitor section
[ 6.072] (II) vmware(0): Output Virtual7 has no monitor section
[ 6.072] (II) vmware(0): Output Virtual8 has no monitor section
[ 6.072] (II) vmware(0): Printing probed modes for output Virtual1
[ 6.072] (II) vmware(0): Modeline "800x600"x60.0 42.75 800 850 900 950 600 650 700 750 -hsync +vsync (45.0 kHz eP)
[ 6.073] (II) vmware(0): Modeline "2560x1600"x60.0 348.50 2560 2752 3032 3504 1600 1603 1609 1658 -hsync +vsync (99.5 kHz e)
[ 6.073] (II) vmware(0): Modeline "1920x1440"x60.0 234.00 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync (90.0 kHz e)
[ 6.073] (II) vmware(0): Modeline "1856x1392"x60.0 218.25 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync (86.3 kHz e)
[ 6.073] (II) vmware(0): Modeline "1792x1344"x60.0 204.75 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync (83.6 kHz e)
[ 6.073] (II) vmware(0): Modeline "1920x1200"x59.9 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync (74.6 kHz e)
[ 6.073] (II) vmware(0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
[ 6.073] (II) vmware(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)
[ 6.073] (II) vmware(0): Modeline "1400x1050"x60.0 121.75 1400 1488 1632 1864 1050 1053 1057 1089 -hsync +vsync (65.3 kHz e)
[ 6.073] (II) vmware(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 6.073] (II) vmware(0): Modeline "1440x900"x59.9 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz e)
[ 6.073] (II) vmware(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 6.073] (II) vmware(0): Modeline "1360x768"x60.0 85.50 1360 1424 1536 1792 768 771 777 795 +hsync +vsync (47.7 kHz e)
[ 6.073] (II) vmware(0): Modeline "1280x800"x59.8 83.50 1280 1352 1480 1680 800 803 809 831 +hsync -vsync (49.7 kHz e)
[ 6.073] (II) vmware(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 6.073] (II) vmware(0): Modeline "1280x768"x59.9 79.50 1280 1344 1472 1664 768 771 778 798 -hsync +vsync (47.8 kHz e)
[ 6.073] (II) vmware(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 6.073] (II) vmware(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 6.073] (II) vmware(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 489 492 525 -hsync -vsync (31.5 kHz e)
[ 6.073] (II) vmware(0): EDID for output Virtual2
[ 6.073] (II) vmware(0): EDID for output Virtual3
[ 6.073] (II) vmware(0): EDID for output Virtual4
[ 6.073] (II) vmware(0): EDID for output Virtual5
[ 6.073] (II) vmware(0): EDID for output Virtual6
[ 6.073] (II) vmware(0): EDID for output Virtual7
[ 6.073] (II) vmware(0): EDID for output Virtual8
[ 6.073] (II) vmware(0): Output Virtual1 connected
[ 6.073] (II) vmware(0): Output Virtual2 disconnected
[ 6.073] (II) vmware(0): Output Virtual3 disconnected
[ 6.073] (II) vmware(0): Output Virtual4 disconnected
[ 6.073] (II) vmware(0): Output Virtual5 disconnected
[ 6.073] (II) vmware(0): Output Virtual6 disconnected
[ 6.073] (II) vmware(0): Output Virtual7 disconnected
[ 6.073] (II) vmware(0): Output Virtual8 disconnected
[ 6.073] (II) vmware(0): Using exact sizes for initial modes
[ 6.073] (II) vmware(0): Output Virtual1 using initial mode 800x600 +0+0
[ 6.073] (==) vmware(0): DPI set to (96, 96)
[ 6.073] (==) vmware(0): Using gamma correction (1.0, 1.0, 1.0)
[ 6.073] (II) Loading sub module "fb"
[ 6.073] (II) LoadModule: "fb"
[ 6.073] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 6.074] (II) Module fb: vendor="X.Org Foundation"
[ 6.074] compiled for 1.20.4, module version = 1.0.0
[ 6.074] ABI class: X.Org ANSI C Emulation, version 0.4
[ 6.074] (II) Loading sub module "dri2"
[ 6.074] (II) LoadModule: "dri2"
[ 6.074] (II) Module "dri2" already built-in
[ 6.074] (II) Loading sub module "dri3"
[ 6.074] (II) LoadModule: "dri3"
[ 6.074] (II) Module "dri3" already built-in
[ 6.074] (II) UnloadModule: "modesetting"
[ 6.074] (II) Unloading modesetting
[ 6.074] (II) UnloadModule: "fbdev"
[ 6.074] (II) Unloading fbdev
[ 6.074] (II) UnloadSubModule: "fbdevhw"
[ 6.074] (II) Unloading fbdevhw
[ 6.074] (II) UnloadModule: "vesa"
[ 6.074] (II) Unloading vesa
[ 6.074] (II) vmware(0): Initialized VMWARE_CTRL extension version 0.2
[ 6.094] (II) vmware(0): Gallium3D XA version: 2.4.0.
[ 6.094] (II) vmware(0): Path of drm device is "/dev/dri/card0".
[ 6.094] (II) vmware(0): [DRI2] Setup complete
[ 6.094] (II) vmware(0): [DRI2] DRI driver: vmwgfx
[ 6.094] (EE) vmware(0): Failed to initialize direct rendering DRI3.
[ 6.094] (--) vmware(0): Render acceleration is enabled.
[ 6.094] (==) vmware(0): Rendercheck mode is disabled.
[ 6.094] (--) vmware(0): Direct rendering (DRI2 3D) is enabled.
[ 6.094] (--) vmware(0): Direct rendering (DRI3 3D) is disabled.
[ 6.094] (==) vmware(0): Direct presents are disabled.
[ 6.094] (==) vmware(0): Hardware only presents are disabled.
[ 6.094] (==) vmware(0): Backing store enabled
[ 6.094] (==) vmware(0): Silken mouse enabled
[ 6.095] (==) vmware(0): DPMS enabled
[ 6.095] (II) Initializing extension Generic Event Extension
[ 6.095] (II) Initializing extension SHAPE
[ 6.095] (II) Initializing extension MIT-SHM
[ 6.095] (II) Initializing extension XInputExtension
[ 6.096] (II) Initializing extension XTEST
[ 6.096] (II) Initializing extension BIG-REQUESTS
[ 6.096] (II) Initializing extension SYNC
[ 6.096] (II) Initializing extension XKEYBOARD
[ 6.096] (II) Initializing extension XC-MISC
[ 6.097] (II) Initializing extension SECURITY
[ 6.097] (II) Initializing extension XFIXES
[ 6.097] (II) Initializing extension RENDER
[ 6.097] (II) Initializing extension RANDR
[ 6.097] (II) Initializing extension COMPOSITE
[ 6.097] (II) Initializing extension DAMAGE
[ 6.097] (II) Initializing extension MIT-SCREEN-SAVER
[ 6.097] (II) Initializing extension DOUBLE-BUFFER
[ 6.097] (II) Initializing extension RECORD
[ 6.098] (II) Initializing extension DPMS
[ 6.098] (II) Initializing extension Present
[ 6.098] (II) Initializing extension DRI3
[ 6.098] (II) Initializing extension X-Resource
[ 6.098] (II) Initializing extension XVideo
[ 6.098] (II) Initializing extension XVideo-MotionCompensation
[ 6.098] (II) Initializing extension SELinux
[ 6.098] (II) SELinux: Disabled on system
[ 6.098] (II) Initializing extension GLX
[ 6.115] (II) AIGLX: Loaded and initialized vmwgfx
[ 6.115] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 6.115] (II) Initializing extension XFree86-VidModeExtension
[ 6.115] (II) Initializing extension XFree86-DGA
[ 6.115] (II) Initializing extension XFree86-DRI
[ 6.115] (II) Initializing extension DRI2
[ 6.118] (II) vmware(0): Setting screen physical size to 211 x 158
[ 6.160] (II) config/udev: Adding input device Power Button (/dev/input/event3)
[ 6.160] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[ 6.160] (II) LoadModule: "libinput"
[ 6.160] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[ 6.164] (II) Module libinput: vendor="X.Org Foundation"
[ 6.164] compiled for 1.20.4, module version = 0.28.2
[ 6.164] Module class: X.Org XInput Driver
[ 6.164] ABI class: X.Org XInput driver, version 24.1
[ 6.164] (II) Using input driver 'libinput' for 'Power Button'
[ 6.164] (**) Power Button: always reports core events
[ 6.164] (**) Option "Device" "/dev/input/event3"
[ 6.164] (**) Option "_source" "server/udev"
[ 6.169] (II) event3 - Power Button: is tagged by udev as: Keyboard
[ 6.169] (II) event3 - Power Button: device is a keyboard
[ 6.169] (II) event3 - Power Button: device removed
[ 6.251] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event3"
[ 6.251] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 6.251] (**) Option "xkb_model" "pc105"
[ 6.251] (**) Option "xkb_layout" "de"
[ 6.275] (II) event3 - Power Button: is tagged by udev as: Keyboard
[ 6.275] (II) event3 - Power Button: device is a keyboard
[ 6.275] (II) config/udev: Adding input device Sleep Button (/dev/input/event4)
[ 6.275] (**) Sleep Button: Applying InputClass "libinput keyboard catchall"
[ 6.275] (II) Using input driver 'libinput' for 'Sleep Button'
[ 6.275] (**) Sleep Button: always reports core events
[ 6.275] (**) Option "Device" "/dev/input/event4"
[ 6.275] (**) Option "_source" "server/udev"
[ 6.276] (II) event4 - Sleep Button: is tagged by udev as: Keyboard
[ 6.276] (II) event4 - Sleep Button: device is a keyboard
[ 6.276] (II) event4 - Sleep Button: device removed
[ 6.304] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSLPBN:00/input/input5/event4"
[ 6.304] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 7)
[ 6.304] (**) Option "xkb_model" "pc105"
[ 6.304] (**) Option "xkb_layout" "de"
[ 6.305] (II) event4 - Sleep Button: is tagged by udev as: Keyboard
[ 6.305] (II) event4 - Sleep Button: device is a keyboard
[ 6.305] (II) config/udev: Adding input device Video Bus (/dev/input/event1)
[ 6.305] (**) Video Bus: Applying InputClass "libinput keyboard catchall"
[ 6.305] (II) Using input driver 'libinput' for 'Video Bus'
[ 6.305] (**) Video Bus: always reports core events
[ 6.305] (**) Option "Device" "/dev/input/event1"
[ 6.305] (**) Option "_source" "server/udev"
[ 6.306] (II) event1 - Video Bus: is tagged by udev as: Keyboard
[ 6.306] (II) event1 - Video Bus: device is a keyboard
[ 6.306] (II) event1 - Video Bus: device removed
[ 6.364] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/LNXVIDEO:00/input/input2/event1"
[ 6.364] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 8)
[ 6.364] (**) Option "xkb_model" "pc105"
[ 6.364] (**) Option "xkb_layout" "de"
[ 6.365] (II) event1 - Video Bus: is tagged by udev as: Keyboard
[ 6.365] (II) event1 - Video Bus: device is a keyboard
[ 6.366] (II) config/udev: Adding input device VirtualBox mouse integration (/dev/input/event5)
[ 6.366] (**) VirtualBox mouse integration: Applying InputClass "libinput pointer catchall"
[ 6.366] (II) Using input driver 'libinput' for 'VirtualBox mouse integration'
[ 6.366] (**) VirtualBox mouse integration: always reports core events
[ 6.366] (**) Option "Device" "/dev/input/event5"
[ 6.366] (**) Option "_source" "server/udev"
[ 6.366] (II) event5 - VirtualBox mouse integration: is tagged by udev as: Mouse
[ 6.366] (II) event5 - VirtualBox mouse integration: device is a pointer
[ 6.366] (II) event5 - VirtualBox mouse integration: device removed
[ 6.481] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:04.0/input/input6/event5"
[ 6.481] (II) XINPUT: Adding extended input device "VirtualBox mouse integration" (type: MOUSE, id 9)
[ 6.481] (**) Option "AccelerationScheme" "none"
[ 6.481] (**) VirtualBox mouse integration: (accel) selected scheme none/0
[ 6.481] (**) VirtualBox mouse integration: (accel) acceleration factor: 2.000
[ 6.481] (**) VirtualBox mouse integration: (accel) acceleration threshold: 4
[ 6.482] (II) event5 - VirtualBox mouse integration: is tagged by udev as: Mouse
[ 6.482] (II) event5 - VirtualBox mouse integration: device is a pointer
[ 6.482] (II) config/udev: Adding input device VirtualBox mouse integration (/dev/input/js0)
[ 6.482] (II) No input driver specified, ignoring this device.
[ 6.482] (II) This device may have been added with another device file.
[ 6.482] (II) config/udev: Adding input device HDA Intel Line (/dev/input/event9)
[ 6.483] (II) No input driver specified, ignoring this device.
[ 6.483] (II) This device may have been added with another device file.
[ 6.483] (II) config/udev: Adding input device HDA Intel Speaker Front (/dev/input/event10)
[ 6.483] (II) No input driver specified, ignoring this device.
[ 6.483] (II) This device may have been added with another device file.
[ 6.483] (II) config/udev: Adding input device HDA Intel Speaker CLFE (/dev/input/event11)
[ 6.483] (II) No input driver specified, ignoring this device.
[ 6.483] (II) This device may have been added with another device file.
[ 6.483] (II) config/udev: Adding input device HDA Intel Front Headphone (/dev/input/event12)
[ 6.483] (II) No input driver specified, ignoring this device.
[ 6.483] (II) This device may have been added with another device file.
[ 6.483] (II) config/udev: Adding input device HDA Intel SPDIF In (/dev/input/event13)
[ 6.483] (II) No input driver specified, ignoring this device.
[ 6.483] (II) This device may have been added with another device file.
[ 6.484] (II) config/udev: Adding input device HDA Intel Mic (/dev/input/event8)
[ 6.484] (II) No input driver specified, ignoring this device.
[ 6.484] (II) This device may have been added with another device file.
[ 6.484] (II) config/udev: Adding input device VirtualBox USB Tablet (/dev/input/event7)
[ 6.484] (**) VirtualBox USB Tablet: Applying InputClass "libinput pointer catchall"
[ 6.484] (II) Using input driver 'libinput' for 'VirtualBox USB Tablet'
[ 6.484] (**) VirtualBox USB Tablet: always reports core events
[ 6.484] (**) Option "Device" "/dev/input/event7"
[ 6.484] (**) Option "_source" "server/udev"
[ 6.485] (II) event7 - VirtualBox USB Tablet: is tagged by udev as: Mouse
[ 6.486] (II) event7 - VirtualBox USB Tablet: device is a pointer
[ 6.486] (II) event7 - VirtualBox USB Tablet: device removed
[ 6.573] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:06.0/usb1/1-1/1-1:1.0/0003:80EE:0021.0001/input/input8/event7"
[ 6.573] (II) XINPUT: Adding extended input device "VirtualBox USB Tablet" (type: MOUSE, id 10)
[ 6.573] (**) Option "AccelerationScheme" "none"
[ 6.573] (**) VirtualBox USB Tablet: (accel) selected scheme none/0
[ 6.573] (**) VirtualBox USB Tablet: (accel) acceleration factor: 2.000
[ 6.573] (**) VirtualBox USB Tablet: (accel) acceleration threshold: 4
[ 6.574] (II) event7 - VirtualBox USB Tablet: is tagged by udev as: Mouse
[ 6.574] (II) event7 - VirtualBox USB Tablet: device is a pointer
[ 6.575] (II) config/udev: Adding input device VirtualBox USB Tablet (/dev/input/js1)
[ 6.575] (II) No input driver specified, ignoring this device.
[ 6.575] (II) This device may have been added with another device file.
[ 6.575] (II) config/udev: Adding input device VirtualBox USB Tablet (/dev/input/mouse1)
[ 6.575] (II) No input driver specified, ignoring this device.
[ 6.575] (II) This device may have been added with another device file.
[ 6.575] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 6.575] (**) AT Translated Set 2 keyboard: Applying InputClass "libinput keyboard catchall"
[ 6.575] (II) Using input driver 'libinput' for 'AT Translated Set 2 keyboard'
[ 6.575] (**) AT Translated Set 2 keyboard: always reports core events
[ 6.575] (**) Option "Device" "/dev/input/event0"
[ 6.575] (**) Option "_source" "server/udev"
[ 6.576] (II) event0 - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard
[ 6.576] (II) event0 - AT Translated Set 2 keyboard: device is a keyboard
[ 6.576] (II) event0 - AT Translated Set 2 keyboard: device removed
[ 6.604] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 6.604] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 11)
[ 6.604] (**) Option "xkb_model" "pc105"
[ 6.604] (**) Option "xkb_layout" "de"
[ 6.605] (II) event0 - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard
[ 6.605] (II) event0 - AT Translated Set 2 keyboard: device is a keyboard
[ 6.605] (II) config/udev: Adding input device ImExPS/2 Generic Explorer Mouse (/dev/input/event2)
[ 6.606] (**) ImExPS/2 Generic Explorer Mouse: Applying InputClass "libinput pointer catchall"
[ 6.606] (II) Using input driver 'libinput' for 'ImExPS/2 Generic Explorer Mouse'
[ 6.606] (**) ImExPS/2 Generic Explorer Mouse: always reports core events
[ 6.606] (**) Option "Device" "/dev/input/event2"
[ 6.606] (**) Option "_source" "server/udev"
[ 6.606] (II) event2 - ImExPS/2 Generic Explorer Mouse: is tagged by udev as: Mouse
[ 6.606] (II) event2 - ImExPS/2 Generic Explorer Mouse: device is a pointer
[ 6.606] (II) event2 - ImExPS/2 Generic Explorer Mouse: device removed
[ 6.636] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input3/event2"
[ 6.636] (II) XINPUT: Adding extended input device "ImExPS/2 Generic Explorer Mouse" (type: MOUSE, id 12)
[ 6.637] (**) Option "AccelerationScheme" "none"
[ 6.637] (**) ImExPS/2 Generic Explorer Mouse: (accel) selected scheme none/0
[ 6.637] (**) ImExPS/2 Generic Explorer Mouse: (accel) acceleration factor: 2.000
[ 6.637] (**) ImExPS/2 Generic Explorer Mouse: (accel) acceleration threshold: 4
[ 6.637] (II) event2 - ImExPS/2 Generic Explorer Mouse: is tagged by udev as: Mouse
[ 6.637] (II) event2 - ImExPS/2 Generic Explorer Mouse: device is a pointer
[ 6.638] (II) config/udev: Adding input device ImExPS/2 Generic Explorer Mouse (/dev/input/mouse0)
[ 6.638] (II) No input driver specified, ignoring this device.
[ 6.638] (II) This device may have been added with another device file.
[ 6.638] (II) config/udev: Adding input device PC Speaker (/dev/input/event6)
[ 6.638] (II) No input driver specified, ignoring this device.
[ 6.638] (II) This device may have been added with another device file.
[ 6.638] (II) config/udev: Adding input device BRLTTY 5.6 Linux Screen Driver Keyboard (/dev/input/event14)
[ 6.638] (**) BRLTTY 5.6 Linux Screen Driver Keyboard: Applying InputClass "libinput keyboard catchall"
[ 6.638] (II) Using input driver 'libinput' for 'BRLTTY 5.6 Linux Screen Driver Keyboard'
[ 6.638] (**) BRLTTY 5.6 Linux Screen Driver Keyboard: always reports core events
[ 6.638] (**) Option "Device" "/dev/input/event14"
[ 6.638] (**) Option "_source" "server/udev"
[ 6.639] (II) event14 - BRLTTY 5.6 Linux Screen Driver Keyboard: is tagged by udev as: Keyboard
[ 6.639] (II) event14 - BRLTTY 5.6 Linux Screen Driver Keyboard: device is a keyboard
[ 6.639] (II) event14 - BRLTTY 5.6 Linux Screen Driver Keyboard: device removed
[ 6.668] (**) Option "config_info" "udev:/sys/devices/virtual/input/input15/event14"
[ 6.668] (II) XINPUT: Adding extended input device "BRLTTY 5.6 Linux Screen Driver Keyboard" (type: KEYBOARD, id 13)
[ 6.668] (**) Option "xkb_model" "pc105"
[ 6.668] (**) Option "xkb_layout" "de"
[ 6.669] (II) event14 - BRLTTY 5.6 Linux Screen Driver Keyboard: is tagged by udev as: Keyboard
[ 6.669] (II) event14 - BRLTTY 5.6 Linux Screen Driver Keyboard: device is a keyboard
[ 6.678] (EE) Failed to open authorization file "/var/run/sddm/{ef1bdd82-bcc6-4542-a191-42a6a538ca11}": No such file or directory
[ 24.311] (II) event5 - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[ 25.180] (II) event5 - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[ 85.749] (II) event5 - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[ 87.485] (II) event5 - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[ 89.511] (II) event5 - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[ 107.392] (II) event5 - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[ 277.380] (II) event5 - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[ 279.062] (II) event5 - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[ 318.389] (II) event5 - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[ 320.225] (II) event5 - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[ 346.250] (II) event5 - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[ 451.094] (II) event5 - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[ 797.315] (II) event5 - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[ 797.345] (II) event5 - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[ 797.468] (II) event5 - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[ 797.534] (II) event5 - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[ 799.237] (II) event5 - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[ 799.237] (II) event5 - VirtualBox mouse integration: WARNING: log rate limit exceeded (5 msgs per 30000ms). Discarding future messages.
[ 3415.268] (II) event5 - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[ 3417.142] (II) event5 - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[ 3417.180] (II) event5 - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[ 3527.153] (II) event5 - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[ 3529.147] (II) event5 - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[ 3529.471] (II) event5 - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[ 3531.272] (II) event5 - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[ 3629.784] (II) event5 - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[ 3652.497] (II) event5 - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[ 3654.330] (II) event5 - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[ 4082.251] (II) event5 - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[ 4434.640] (II) event5 - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[ 4434.710] (II) event5 - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[ 4434.737] (II) event5 - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[ 4436.252] (II) event5 - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[ 4436.322] (II) event5 - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
[ 4436.322] (II) event5 - VirtualBox mouse integration: WARNING: log rate limit exceeded (5 msgs per 30000ms). Discarding future messages.the max. reported resolution is still 2560*1600.
What video card and kernel driver does lspci -k report for the VMs?
Here the whole output with enabled/installed guest-addition.iso
terence@devuan3:~$ lspci -k
00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
00:01.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
Kernel driver in use: ata_piix
Kernel modules: ata_piix, ata_generic
00:02.0 VGA compatible controller: VMware SVGA II Adapter
Subsystem: VMware SVGA II Adapter
Kernel driver in use: vmwgfx
Kernel modules: vmwgfx
00:03.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02)
Subsystem: Intel Corporation PRO/1000 MT Desktop Adapter
Kernel driver in use: e1000
Kernel modules: e1000
00:04.0 System peripheral: InnoTek Systemberatung GmbH VirtualBox Guest Service
Kernel driver in use: vboxguest
Kernel modules: vboxguest
00:05.0 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 01)
Subsystem: SigmaTel 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:06.0 USB controller: Apple Inc. KeyLargo/Intrepid USB
Kernel driver in use: ohci-pci
Kernel modules: ohci_pci
00:07.0 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 08)
Kernel driver in use: piix4_smbus
Kernel modules: i2c_piix4
00:0d.0 SATA controller: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) SATA Controller [AHCI mode] (rev 02)
Kernel driver in use: ahci
Kernel modules: ahciterence@devuan3:~$ uname -r
5.7.0-0.bpo.2-amd64qemu-system-x86_64 -enable kvm -m 4G -vga qxl -soundhw hda -cdrom /path/to/ISO.imgSee also http://forums.debian.net/viewtopic.php?f=16&t=144775
That's a good explanation, thanks! First I would state to use KVM like in the trhead for getting 'spice' and I have some questions:
Following your linked thread by 'shared-folder' is this command qemu_mount /shared 9p rw,sync,dirsync,access=client,trans=virtio,x-systemd.automount 0 0 but I have 'openrc' installed on the client.
How to modify the /etc/fstab accordignly?
Upload the file to a pastebin and share the link:
curl -F 'f:1=<-' ix.io < /var/log/Xorg.0.logI'm not interested in the MX log, that is of no use for this thread.
Thanks for commit the command and OK for MX I was not sure.
I just can't be arsed posting a "newbie explanation" for how to create an X.Org configuration file, that's all. I'm sure there are some out there if you search a bit, or maybe another forum member with more patience than me will take pity on you.
I search since months now with very poor results on knowledge, each distro has own scheme, can you recommend some link-s? the qemu-link is very good (only one open question from my side).
Terence wrote:If I not get a working solution for Devuan I will aquantaine myself with Gentoo.
What makes you think I care which distribution you use?
I'm sure, by the way... Gentoo latest stable has 'systemd' too. Who will take care now about 'openrc'?
Thanks again for your patience.
#3 Re: Desktop and Multimedia » Devuan-Beowulf Resolution, 4k-monitor, 10-bit. » 2020-09-07 08:28:20
Yes Sir, I did.
Here the instruction I collect, this is .md (Markdown) syntax... that in case could be useful for other users.
The (kernel) version I got is the 5.7. automatically choosen from beowulf-backports as well firmware-amd-graphics in the version '20200721' like all debian-dased-distros like MX-Linux, etc.
# Devuan 'backports', 'kernel-' and 'firmware-upgrade' [Link 1:](https://unix.stackexchange.com/questions/545601/how-to-upgrade-the-debian-10-kernel-from-backports-without-recompiling-it-from-s) [Link 2:](https://www.taste-of-it.de/debian-buster-kernel-5-2-aus-backports-installieren/).
**Note-s:**
1. This guide is for people want to get primarily newer drivers for graphic-cards, wifi, etc.
2. The new kernel will be installed alongside the already present-one. In case of problems you can start the "old-one" at boot time.
### Step 1. Detect actual kernel
* For this use `terminal` opening with (CTRL + ALT + T), Code:
```
uname -r
```
### Step 2. Enable 'backports' Code:
* Methode 1.:
```
sudo su
nano /etc/apt/sources.list
```
* Text to insert (leave one empty line at end) Code:
```
# Beowulf-Backports
deb http://packmaster.devuan.org/merged beowulf-backports main contrib non-free
deb-src http://packmaster.devuan.org/merged beowulf-backports main contrib non-free
```
* Save and close file:
- Save with (CTRL + O), hit (Enter) to confirm
- Close with (CTRL + X)
* Check results with code:
```
cat /etc/apt/sources.list
```
* Methode 2.:
- Open Dolphin
- Navigate to `/etc/apt/`
- Open `sources.list` with `kate`
- Copy and paste the 2-3 lines and leave one empty line at end.
- Save (CTRL + S), insert password and (ENTER).
- Close with (CTRL + W).
### Step 3. Update and Upgrade
** Note:** You are still `root`!
* read the new sources, Code:
```
apt update
apt -t beowulf-backports upgrade
> or
apt-get update
apt-get -t beowulf-backports upgrade
apt-get install -f
```
* install `firmware-amd-graphics` (if not yet done), Code:
```
apt install -t beowulf-backports firmware-amd-graphics
```
* install new kernel, Code:
```
apt install -t boewulf-backports linux-image-amd64
```
* search for installed `linux-image`, Code:
```
apt list --installed linux-image*
```
- output example (note newest installed):
```
Listing... Done
linux-image-4.19.0-10-amd64/stable,now 4.19.132-1 [installed, automatic]
linux-image-5.7.0-0.bpo.2-amd64/stable-backports,now 5.7.10-1~bpo10+1 amd64 [inistalled,automatic]
linux-image-amd64/stable-backports,now 5.7.10-1~bpo10+1 amd64 [installed]
```
* search for correlated `linux-headers`
```
apt search linux-headers-5.7.0*
```
- output example:
```
Sorting... Done
Full Text Search... Done
linux-headers-5.7.0-0.bpo.2-amd64/stable-backports 5.7.10-1~bpo10+1 amd64
Header files for Linux 5.7.0-0.bpo.2-amd64
linux-headers-5.7.0-0.bpo.2-cloud-amd64/stable-backports 5.7.10-1~bpo10+1 amd64
Header files for Linux 5.7.0-0.bpo.2-cloud-amd64
linux-headers-5.7.0-0.bpo.2-commom-amd64/stable-backports 5.7.10-1~bpo10+1 all
Header files for Linux 5.7.0-0.bpo.2
```
* install `linux-headers`, Code:
```
apt install -t beowulf-backports linux-headers-5.7.0-0.bpo.2-amd64
```
* install the firmware, Code:
```
sudo apt install -t beowulf-backports firmware-linux firmware-linux-nonfree
```
### Step 4. Assure everything is installed correctly, Code:
```
apt-get update && apt-get upgrade && apt-get install -f && apt-get dist-upgrade && update-grub
```
* in case of error message..., Code:
```
dpkg --configure -a
```
- alternatively, open `synaptic`-package-manager, click `Edit`, click `Fix Broken Packages`. Repeat the fix until no error-messages appear anymore.
* clean the system (optional), Code:
```
apt autoremove --purge
```
### Step 5. Reboot, Code:
```
reboot
> or
shutdown -r now
```
* alternatively, use the GUI
* switch-off command, Code:
```
shutdown -h now
```The edid on real machine (Kubuntu) is perfect as well on VMs (without 'guest-iso-addition') using systemd, like MX-Linux-KDE and others.
By the way, I install also edid-decode and read-edid, but those apps read the edid-part of /var/log/Xorg.0.log. They don't read the edid from hardware.
I don't know which application read the hardware-edid and pass it to 'Xorg', 'xorg' same?
xrandr work ok, I can set there other resolution's but after a while of running the resolution fall back to 'xorg'-value.
Issuing the command sudo -i systemsettings5 (under all OS) and try to change resolution and scaling belong display-menu I get following out:
kscreen: Requesting missing EDID for outputs (71)searching for '71' in file-manager I discover /lib/udev/rules.d/71-seat-rules, that's no good.
Reading many threads (for all Gentoo-threads, using and care-taking of 'openrc') about 'kscreen'-errors it appear to be a common error for OSs not using 'systemd' and maybe this is the reason, also for Gento, to issue latest stable without 'openrc'.
I look also for 'EDID' in the real installation (Kubuntu), the file-search don't bring any results but in a gentoo-thread I found where to be, this is /sys/class/drm/, in my case (using display-port-2) /sys/class/drm/card0-DP-2 but there only empty folders and files.
I install also beowulf with 'sysvinit', reading /var/log/Xorg.0.log no changes. This should be also the reason to get black screen with cursor like in a server under real conditions.
A 'step-by-step' instructions how to remedy or how to setup a proper 'xorg' is still missing on my side.
Consideration-s:
1. All OSs using 'systemd' blacklist: 'amd', 'intel' and 'nvidia' modules. How they get all EDID inside 'xorg' is a mistery for me.
2. Mouse, keyboards and thouch-phad are obsolete in 'xorg' (see xorg-wiki).
3. For a 30-40 years old 'xorg' that should be replaced (Wayland and/or + Systemd, maybe) are too few information about and each distribution make own things and place in different folders the config.files. That's not freedom, tha's confusion.
Fact-s:
1. EDID-informations are given by hardware correctly because other ditros recognize them also perfectly even in VM/VB without 'guest-iso'.
2. All firmware (linux and amd) and kernel are up to date from 'beowulf-backports' (see instructions).
3. No seldom hardware, all amd and samsung, see list above.
4. We cannot blame 'openrc', 'syvinit' bring exact the same results= missing resolution-information in the /var/log/Xorg.0.log.
5. Other distro's (e.g. MX-Linux-KDE) recognize available resolution and let modify/change it latest by installing 'kde-full' and use 'sddm' as choosen, devuan don't. This (Devuan) stick with slim at start, does that make a difference? Former installation where the choice was between lightdm and sddm present the same slick slim or lightdm screen.
#4 Desktop and Multimedia » Devuan-Beowulf Resolution, 4k-monitor, 10-bit. » 2020-09-04 18:54:08
- Terence
- Replies: 4
Hardware:
- X399 motherboard, socket TR4
- Threadripper 1900, 8 CPUs 16 threads
- 64-GB RAM, 3.000 MHz
- Samsung 970 pro NVMe, 512-GB
- AMD Vega 64, 8-GB GPU-RAM
- Samsung 10-Bit deep display, native resolution 3.840x2.048
All the rest is also new, PSU, mouse, keyboard, case, even table and chair ;-)
History:
- Installed Beowulf alone (I use only Linux since 10 years) and from scratch on NVMe. At first reboot I got only black screen with cursor.
- Start the machine with a live system, check 'repository', chroot, make all updates, restart... same as above.
- Chroot it again enable 'backports', install 'firmware-amd-graphics', 'dpkg', update, upgrade, restart... nothing changes.
- 'startx' or 'startkde' don't help either.
- I can use the 'black screen' as 'konsole/terminal' to make update and all other things possible on normal terminal but can't start the UI.
I want definitely leave Kubuntu, Neon is too unstable, Xfce is not for us (200% scaling + flickering to reduce to 150%), MX-Linux is Xfce with sysvinit additionally can be installed kde but scale remain to 200%.
Making experiments with different OSs in the VB see amdgpu-pro drivers all OS recognize the right resolution, Beowulf don't.
Reading file:///var/log/Xorg.0.log of all machine (real & virtual) something going wrong and need help.
Could someone tell me what and in which order I have to install in order to get the full 3840x2160 resolution?
#5 Re: Desktop and Multimedia » amdgpu-pro drivers » 2020-09-04 16:04:39
You don't need a backported kernel or the AMD graphics firmware if you're running in a VM because the VM isn't exposed to the AMD card (as I already explained and as you already claimed to have understood).
I recognize a dissonance between your writing and the pseudo-reality of VM's, in fact I installed now also MX-Linux (another Xfce with sysvinit) with MVs exact same adjustments. Here the xrandr-outputs...
Kubuntu real OS:
xrandr
Screen 0: minimum 320 x 200, current 3840 x 2160, maximum 16384 x 16384
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-1 disconnected (normal left inverted right x axis y axis)
DisplayPort-2 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 607mm x 345mm
3840x2160 60.00*+
2560x1440 59.95
1920x1200 60.00
1920x1080 60.00 59.94
1600x1200 60.00
1680x1050 59.95
1600x900 60.00
1280x1024 60.02
1440x900 59.89
1280x800 59.81
1280x720 60.00 59.94
1024x768 60.00
800x600 60.32 56.25
640x480 60.00 59.94 this OS hasn't 'firmware-amd-graphics' but 'linux-firmware' Ver. 1.187.3
Devuan-Beowulf VM:
xrandr
Screen 0: minimum 1 x 1, current 2560 x 1600, maximum 8192 x 8192
Virtual1 connected primary 2560x1600+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
800x600 60.00 + 60.32
2560x1600 59.99*
1920x1440 60.00
1856x1392 60.00
1792x1344 60.00
1920x1200 59.88
1600x1200 60.00
1680x1050 59.95
1400x1050 59.98
1280x1024 60.02
1440x900 59.89
1280x960 60.00
1360x768 60.02
1280x800 59.81
1152x864 75.00
1280x768 59.87
1024x768 60.00
640x480 59.94this OS has 'firmware-amd-graphics' Vers. '20190114-2' and 'firmware-linux-free' Vers. '3.4`and 'firmware-linux-nonfree' Vers. '20190114-2'. Here in Devuan is all completely different, even from MX-Linux (also Debian-like with 'sysvinit').
MX-Linux VM:
xrandr
Screen 0: minimum 1 x 1, current 3840 x 2160, maximum 8192 x 8192
Virtual1 connected 3840x2160+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
800x600 60.00 + 60.32
2560x1600 59.99
1920x1440 60.00
1856x1392 60.00
1792x1344 60.00
1920x1200 59.88
1600x1200 60.00
1680x1050 59.95
1400x1050 59.98
1280x1024 60.02
1440x900 59.89
1280x960 60.00
1360x768 60.02
1280x800 59.81
1152x864 75.00
1280x768 59.87
1024x768 60.00
640x480 59.94
3840x2160_vbox 59.98* this OS has 'firmware-amd-graphics' Vers. '20200721-1~mx19+1' and 'firmware-linux-free' Vers. '20200721-1~mx19+1`and 'firmware-linux-nonfree' Vers. '20200721-1~mx19+1'
Note-s:
1. All, in the VM installed OS show natively (just after install) a reduced resolution (1024x768 Devuan, 2500x1600 MX-linux), the full or possible max. resolution is given only after installing 'firmware-amd-graphics'. This all without 'guest-addition.iso'
2. I delete the old VM's and reinstall them new.
3. Beowulf install by default 'firmware-linux-free' Vers. '3.4' the 'firmware-linux-nonfree' (I have installed afterwards for testing) don't bring anythings.
I don't use virt-manager but I know that the default -vga std option for QEMU supports up to 2560x1600. The -vga qxl option will support up to 2560x1440 and higher resolutions are available if the VGA memory size for the QXL drivers is increased: https://wiki.archlinux.org/index.php/QE … or_support
It doesn't or 'Beowulf' is not able. Reading instructions I increase the memory amount to 128K (the same quantity as in Virtual-Box), didn't help, here the outputs:
/etc/libvirt/qemu/devuan3.xml
sudo virsh edit devuan3
Select an editor. To change later, run 'select-editor'.
1. /bin/nano <---- easiest
2. /usr/bin/vim.tiny
3. /usr/bin/emacs
4. /bin/ed
Choose 1-4 [1]: 1
<video>
<model type='qxl' ram='131072' vram='131072' vgamem='131072' heads='1' primary='yes'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
</video>If you don't use 'virt-manager' what are you using? Do we make only a theoretical discussion or we tray to find a practical solution? Maybe detailed instructions `step-by-step` so we can help also other people besides of our-self.
I presume your guest has the xserver-xorg-video-qxl package installed?
of course.
No, it will never end unless you start providing some logs that are relevant to the problem (in this case the X.Org log) and clearly state which version of the kernel and firmware packages are installed.
Packages and Version delivered, see above, 'X.Org log' (I think) will only help if drivers/firmware-version is mentioned, anyway here are the '/var/log/Xorg.0log's...
Sorry to big; I can't post them complete (not of real system, nor of Devuan) but...
MX-Linux VM:
[ 11.340] (--) Log file renamed from "/var/log/Xorg.pid-2808.log" to "/var/log/Xorg.0.log"
[ 11.341]
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
[ 11.341] Build Operating System: Linux 4.9.0-8-amd64 x86_64 Debian
[ 11.341] Current Operating System: Linux mx-tony 4.19.0-10-amd64 #1 SMP Debian 4.19.132-1 (2020-07-24) x86_64
[ 11.341] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-10-amd64 root=UUID=2833381e-bcce-4f95-80ef-73a6a47e984b ro quiet splash
[ 11.341] Build Date: 05 March 2019 08:11:12PM
[ 11.341] xorg-server 2:1.20.4-1 (https://www.debian.org/support)
[ 11.341] Current version of pixman: 0.36.0
[ 11.341] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 11.341] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 11.341] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Sep 4 09:46:13 2020
[ 11.344] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 11.344] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 11.348] (==) No Layout section. Using the first Screen section.
[ 11.348] (==) No screen section available. Using defaults.
[ 11.348] (**) |-->Screen "Default Screen Section" (0)
[ 11.348] (**) | |-->Monitor "<default monitor>"
[ 11.350] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 11.350] (==) Automatically adding devices
[ 11.350] (==) Automatically enabling devices
[ 11.350] (==) Automatically adding GPU devices
[ 11.350] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 11.356] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 11.356] Entry deleted from font path.
[ 11.360] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[ 11.360] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 11.360] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 11.360] (II) Loader magic: 0x55a07dc1ee20
[ 11.360] (II) Module ABI versions:
[ 11.360] X.Org ANSI C Emulation: 0.4
[ 11.360] X.Org Video Driver: 24.0
[ 11.360] X.Org XInput driver : 24.1
[ 11.360] X.Org Server Extension : 10.0
[ 11.362] (++) using VT number 7
[ 11.362] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[ 11.363] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 11.366] (--) PCI:*(0@0:2:0) 15ad:0405:15ad:0405 rev 0, Mem @ 0xf0000000/134217728, 0xf8000000/2097152, I/O @ 0x0000d010/16, BIOS @ 0x????????/131072
[ 11.366] (II) LoadModule: "glx"
[ 11.367] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 11.373] (II) Module glx: vendor="X.Org Foundation"
[ 11.373] compiled for 1.20.4, module version = 1.0.0
[ 11.373] ABI class: X.Org Server Extension, version 10.0
[ 11.373] (==) Matched vmware as autoconfigured driver 0
[ 11.373] (==) Matched modesetting as autoconfigured driver 1
[ 11.373] (==) Matched fbdev as autoconfigured driver 2
[ 11.373] (==) Matched vesa as autoconfigured driver 3
[ 11.373] (==) Assigned the driver to the xf86ConfigLayout
[ 11.373] (II) LoadModule: "vmware"
[ 11.373] (II) Loading /usr/lib/xorg/modules/drivers/vmware_drv.so
[ 11.477] (II) Module vmware: vendor="X.Org Foundation"
[ 11.477] compiled for 1.20.0, module version = 13.3.0
[ 11.477] Module class: X.Org Video Driver
[ 11.477] ABI class: X.Org Video Driver, version 24.0
[ 11.477] (II) LoadModule: "modesetting"
[ 11.477] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 11.479] (II) Module modesetting: vendor="X.Org Foundation"
[ 11.479] compiled for 1.20.4, module version = 1.20.4
[ 11.479] Module class: X.Org Video Driver
[ 11.479] ABI class: X.Org Video Driver, version 24.0
[ 11.479] (II) LoadModule: "fbdev"
[ 11.479] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 11.480] (II) Module fbdev: vendor="X.Org Foundation"
[ 11.480] compiled for 1.20.0, module version = 0.5.0
[ 11.480] Module class: X.Org Video Driver
[ 11.480] ABI class: X.Org Video Driver, version 24.0
[ 11.480] (II) LoadModule: "vesa"
[ 11.480] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 11.481] (II) Module vesa: vendor="X.Org Foundation"
[ 11.481] compiled for 1.20.1, module version = 2.4.0
[ 11.481] Module class: X.Org Video Driver
[ 11.481] ABI class: X.Org Video Driver, version 24.0
[ 11.481] (II) vmware: driver for VMware SVGA: vmware0405, vmware0710
[ 11.481] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 11.481] (II) FBDEV: driver for framebuffer: fbdev
[ 11.481] (II) VESA: driver for VESA chipsets: vesa
[ 11.482] (WW) Falling back to old probe method for modesetting
[ 11.482] (WW) Falling back to old probe method for fbdev
[ 11.482] (II) Loading sub module "fbdevhw"
[ 11.482] (II) LoadModule: "fbdevhw"
[ 11.483] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 11.483] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 11.483] compiled for 1.20.4, module version = 0.0.2
[ 11.483] ABI class: X.Org Video Driver, version 24.0
[ 11.483] (II) vmware(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 11.484] (--) vmware(0): DRM driver version is 2.15.0
[ 11.484] (==) vmware(0): Depth 24, (--) framebuffer bpp 32
[ 11.484] (==) vmware(0): RGB weight 888
[ 11.484] (==) vmware(0): Default visual is TrueColor
[ 11.484] (--) vmware(0): Min width 1, Max Width 8192.
[ 11.484] (--) vmware(0): Min height 1, Max Height 8192.
[ 11.484] (II) vmware(0): Output Virtual1 has no monitor section
[ 11.484] (II) vmware(0): Output Virtual2 has no monitor section
[ 11.484] (II) vmware(0): Output Virtual3 has no monitor section
[ 11.484] (II) vmware(0): Output Virtual4 has no monitor section
[ 11.484] (II) vmware(0): Output Virtual5 has no monitor section
[ 11.484] (II) vmware(0): Output Virtual6 has no monitor section
[ 11.484] (II) vmware(0): Output Virtual7 has no monitor section
[ 11.484] (II) vmware(0): Output Virtual8 has no monitor section
[ 11.484] (II) vmware(0): Printing probed modes for output Virtual1
[ 11.484] (II) vmware(0): Modeline "800x600"x60.0 42.75 800 850 900 950 600 650 700 750 -hsync +vsync (45.0 kHz eP)
[ 11.484] (II) vmware(0): Modeline "2560x1600"x60.0 348.50 2560 2752 3032 3504 1600 1603 1609 1658 -hsync +vsync (99.5 kHz e)
[ 11.484] (II) vmware(0): Modeline "1920x1440"x60.0 234.00 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync (90.0 kHz e)
[ 11.484] (II) vmware(0): Modeline "1856x1392"x60.0 218.25 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync (86.3 kHz e)
[ 11.484] (II) vmware(0): Modeline "1792x1344"x60.0 204.75 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync (83.6 kHz e)
[ 11.484] (II) vmware(0): Modeline "1920x1200"x59.9 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync (74.6 kHz e)
[ 11.484] (II) vmware(0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
[ 11.484] (II) vmware(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)
[ 11.484] (II) vmware(0): Modeline "1400x1050"x60.0 121.75 1400 1488 1632 1864 1050 1053 1057 1089 -hsync +vsync (65.3 kHz e)
[ 11.484] (II) vmware(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 11.484] (II) vmware(0): Modeline "1440x900"x59.9 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz e)
[ 11.484] (II) vmware(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 11.484] (II) vmware(0): Modeline "1360x768"x60.0 85.50 1360 1424 1536 1792 768 771 777 795 +hsync +vsync (47.7 kHz e)
[ 11.484] (II) vmware(0): Modeline "1280x800"x59.8 83.50 1280 1352 1480 1680 800 803 809 831 +hsync -vsync (49.7 kHz e)
[ 11.484] (II) vmware(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 11.484] (II) vmware(0): Modeline "1280x768"x59.9 79.50 1280 1344 1472 1664 768 771 778 798 -hsync +vsync (47.8 kHz e)
[ 11.484] (II) vmware(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 11.484] (II) vmware(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 11.484] (II) vmware(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 489 492 525 -hsync -vsync (31.5 kHz e)
[ 11.484] (II) vmware(0): EDID for output Virtual2
[ 11.484] (II) vmware(0): EDID for output Virtual3
[ 11.484] (II) vmware(0): EDID for output Virtual4
[ 11.484] (II) vmware(0): EDID for output Virtual5
[ 11.484] (II) vmware(0): EDID for output Virtual6
[ 11.484] (II) vmware(0): EDID for output Virtual7
[ 11.484] (II) vmware(0): EDID for output Virtual8
[ 11.484] (II) vmware(0): Output Virtual1 connected
[ 11.484] (II) vmware(0): Output Virtual2 disconnected
[ 11.484] (II) vmware(0): Output Virtual3 disconnected
[ 11.484] (II) vmware(0): Output Virtual4 disconnected
[ 11.484] (II) vmware(0): Output Virtual5 disconnected
[ 11.484] (II) vmware(0): Output Virtual6 disconnected
[ 11.484] (II) vmware(0): Output Virtual7 disconnected
[ 11.484] (II) vmware(0): Output Virtual8 disconnected
[ 11.484] (II) vmware(0): Using exact sizes for initial modes
[ 11.484] (II) vmware(0): Output Virtual1 using initial mode 800x600 +0+0
[ 11.484] (==) vmware(0): DPI set to (96, 96)
[ 11.484] (==) vmware(0): Using gamma correction (1.0, 1.0, 1.0)
[ 11.484] (II) Loading sub module "fb"
[ 11.484] (II) LoadModule: "fb"
[ 11.484] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 11.485] (II) Module fb: vendor="X.Org Foundation"
[ 11.485] compiled for 1.20.4, module version = 1.0.0
[ 11.485] ABI class: X.Org ANSI C Emulation, version 0.4
[ 11.485] (II) Loading sub module "dri2"
[ 11.485] (II) LoadModule: "dri2"
[ 11.485] (II) Module "dri2" already built-in
[ 11.485] (II) Loading sub module "dri3"
[ 11.485] (II) LoadModule: "dri3"
[ 11.485] (II) Module "dri3" already built-in
[ 11.485] (II) UnloadModule: "modesetting"
[ 11.485] (II) Unloading modesetting
[ 11.485] (II) UnloadModule: "fbdev"
[ 11.485] (II) Unloading fbdev
[ 11.485] (II) UnloadSubModule: "fbdevhw"
[ 11.485] (II) Unloading fbdevhw
[ 11.485] (II) UnloadModule: "vesa"
[ 11.485] (II) Unloading vesa
[ 11.486] (II) vmware(0): Initialized VMWARE_CTRL extension version 0.2
[ 11.511] (II) vmware(0): Gallium3D XA version: 2.5.0.
[ 11.511] (II) vmware(0): Path of drm device is "/dev/dri/card0".
[ 11.512] (II) vmware(0): [DRI2] Setup complete
[ 11.512] (II) vmware(0): [DRI2] DRI driver: vmwgfx
[ 11.512] (EE) vmware(0): Failed to initialize direct rendering DRI3.
[ 11.512] (--) vmware(0): Render acceleration is enabled.
[ 11.512] (==) vmware(0): Rendercheck mode is disabled.
[ 11.512] (--) vmware(0): Direct rendering (DRI2 3D) is enabled.
[ 11.512] (--) vmware(0): Direct rendering (DRI3 3D) is disabled.
[ 11.512] (==) vmware(0): Direct presents are disabled.
[ 11.512] (==) vmware(0): Hardware only presents are disabled.
[ 11.512] (==) vmware(0): Backing store enabled
[ 11.512] (==) vmware(0): Silken mouse enabled
[ 11.513] (==) vmware(0): DPMS enabled
[ 11.513] (II) Initializing extension Generic Event Extension
[ 11.513] (II) Initializing extension SHAPE
[ 11.513] (II) Initializing extension MIT-SHM
[ 11.513] (II) Initializing extension XInputExtension
[ 11.514] (II) Initializing extension XTEST
[ 11.514] (II) Initializing extension BIG-REQUESTS
[ 11.514] (II) Initializing extension SYNC
[ 11.514] (II) Initializing extension XKEYBOARD
[ 11.515] (II) Initializing extension XC-MISC
[ 11.515] (II) Initializing extension SECURITY
[ 11.515] (II) Initializing extension XFIXES
[ 11.515] (II) Initializing extension RENDER
[ 11.515] (II) Initializing extension RANDR
[ 11.516] (II) Initializing extension COMPOSITE
[ 11.516] (II) Initializing extension DAMAGE
[ 11.516] (II) Initializing extension MIT-SCREEN-SAVER
[ 11.516] (II) Initializing extension DOUBLE-BUFFER
[ 11.517] (II) Initializing extension RECORD
[ 11.517] (II) Initializing extension DPMS
[ 11.517] (II) Initializing extension Present
[ 11.517] (II) Initializing extension DRI3
[ 11.517] (II) Initializing extension X-Resource
[ 11.517] (II) Initializing extension XVideo
[ 11.517] (II) Initializing extension XVideo-MotionCompensation
[ 11.517] (II) Initializing extension SELinux
[ 11.517] (II) SELinux: Disabled on system
[ 11.517] (II) Initializing extension GLX
[ 11.548] (II) AIGLX: Loaded and initialized vmwgfx
[ 11.548] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 11.548] (II) Initializing extension XFree86-VidModeExtension
[ 11.548] (II) Initializing extension XFree86-DGA
[ 11.548] (II) Initializing extension XFree86-DRI
[ 11.548] (II) Initializing extension DRI2
[ 11.551] (II) vmware(0): Setting screen physical size to 211 x 158
[ 11.618] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[ 11.618] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 11.618] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[ 11.618] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 11.618] (II) LoadModule: "evdev"
[ 11.618] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 11.620] (II) Module evdev: vendor="X.Org Foundation"
[ 11.620] compiled for 1.20.1, module version = 2.10.6
[ 11.620] Module class: X.Org XInput Driver
[ 11.620] ABI class: X.Org XInput driver, version 24.1
[ 11.620] (II) Using input driver 'evdev' for 'Power Button'
[ 11.620] (**) Power Button: always reports core events
[ 11.620] (**) evdev: Power Button: Device: "/dev/input/event1"
[ 11.620] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 11.620] (--) evdev: Power Button: Found keys
[ 11.620] (II) evdev: Power Button: Configuring as keyboard
[ 11.620] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event1"
[ 11.620] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 11.620] (**) Option "xkb_rules" "evdev"
[ 11.620] (**) Option "xkb_model" "pc105"
[ 11.620] (**) Option "xkb_layout" "de"
[ 11.620] (**) Option "xkb_variant" "nodeadkeys"
[ 11.620] (**) Option "xkb_options" "grp:alt_shift_toggle,grp_led:scroll,terminate:ctrl_alt_bksp"
[ 11.641] (II) config/udev: Adding input device Sleep Button (/dev/input/event2)
[ 11.641] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[ 11.641] (**) Sleep Button: Applying InputClass "libinput keyboard catchall"
[ 11.641] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[ 11.641] (II) Using input driver 'evdev' for 'Sleep Button'
[ 11.641] (**) Sleep Button: always reports core events
[ 11.641] (**) evdev: Sleep Button: Device: "/dev/input/event2"
[ 11.641] (--) evdev: Sleep Button: Vendor 0 Product 0x3
[ 11.641] (--) evdev: Sleep Button: Found keys
[ 11.641] (II) evdev: Sleep Button: Configuring as keyboard
[ 11.641] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSLPBN:00/input/input3/event2"
[ 11.641] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 7)
[ 11.641] (**) Option "xkb_rules" "evdev"
[ 11.641] (**) Option "xkb_model" "pc105"
[ 11.641] (**) Option "xkb_layout" "de"
[ 11.641] (**) Option "xkb_variant" "nodeadkeys"
[ 11.642] (**) Option "xkb_options" "grp:alt_shift_toggle,grp_led:scroll,terminate:ctrl_alt_bksp"
[ 11.642] (II) config/udev: Adding input device Video Bus (/dev/input/event3)
[ 11.642] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 11.642] (**) Video Bus: Applying InputClass "libinput keyboard catchall"
[ 11.643] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 11.643] (II) Using input driver 'evdev' for 'Video Bus'
[ 11.643] (**) Video Bus: always reports core events
[ 11.643] (**) evdev: Video Bus: Device: "/dev/input/event3"
[ 11.643] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 11.643] (--) evdev: Video Bus: Found keys
[ 11.643] (II) evdev: Video Bus: Configuring as keyboard
[ 11.643] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/LNXVIDEO:00/input/input4/event3"
[ 11.643] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 8)
[ 11.643] (**) Option "xkb_rules" "evdev"
[ 11.643] (**) Option "xkb_model" "pc105"
[ 11.643] (**) Option "xkb_layout" "de"
[ 11.643] (**) Option "xkb_variant" "nodeadkeys"
[ 11.643] (**) Option "xkb_options" "grp:alt_shift_toggle,grp_led:scroll,terminate:ctrl_alt_bksp"
[ 11.644] (II) config/udev: Adding input device VirtualBox mouse integration (/dev/input/event6)
[ 11.645] (**) VirtualBox mouse integration: Applying InputClass "evdev pointer catchall"
[ 11.645] (**) VirtualBox mouse integration: Applying InputClass "libinput pointer catchall"
[ 11.645] (**) VirtualBox mouse integration: Applying InputClass "evdev pointer catchall"
[ 11.645] (II) Using input driver 'evdev' for 'VirtualBox mouse integration'
[ 11.645] (**) VirtualBox mouse integration: always reports core events
[ 11.645] (**) evdev: VirtualBox mouse integration: Device: "/dev/input/event6"
[ 11.645] (--) evdev: VirtualBox mouse integration: Vendor 0x80ee Product 0xcafe
[ 11.645] (--) evdev: VirtualBox mouse integration: Found 1 mouse buttons
[ 11.645] (--) evdev: VirtualBox mouse integration: Found absolute axes
[ 11.645] (--) evdev: VirtualBox mouse integration: Found x and y absolute axes
[ 11.645] (--) evdev: VirtualBox mouse integration: Found absolute touchscreen
[ 11.645] (II) evdev: VirtualBox mouse integration: Configuring as touchscreen
[ 11.645] (**) evdev: VirtualBox mouse integration: YAxisMapping: buttons 4 and 5
[ 11.645] (**) evdev: VirtualBox mouse integration: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 11.645] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:04.0/input/input7/event6"
[ 11.645] (II) XINPUT: Adding extended input device "VirtualBox mouse integration" (type: TOUCHSCREEN, id 9)
[ 11.645] (II) evdev: VirtualBox mouse integration: initialized for absolute axes.
[ 11.645] (**) VirtualBox mouse integration: (accel) keeping acceleration scheme 1
[ 11.645] (**) VirtualBox mouse integration: (accel) acceleration profile 0
[ 11.645] (**) VirtualBox mouse integration: (accel) acceleration factor: 2.000
[ 11.645] (**) VirtualBox mouse integration: (accel) acceleration threshold: 4
[ 11.646] (II) config/udev: Adding input device VirtualBox mouse integration (/dev/input/js1)
[ 11.646] (II) No input driver specified, ignoring this device.
[ 11.646] (II) This device may have been added with another device file.
[ 11.646] (II) config/udev: Adding input device HDA Intel Speaker Front (/dev/input/event9)
[ 11.646] (II) No input driver specified, ignoring this device.
[ 11.646] (II) This device may have been added with another device file.
[ 11.646] (II) config/udev: Adding input device HDA Intel Speaker CLFE (/dev/input/event10)
[ 11.646] (II) No input driver specified, ignoring this device.
[ 11.646] (II) This device may have been added with another device file.
[ 11.647] (II) config/udev: Adding input device HDA Intel Front Headphone (/dev/input/event11)
[ 11.647] (II) No input driver specified, ignoring this device.
[ 11.647] (II) This device may have been added with another device file.
[ 11.647] (II) config/udev: Adding input device HDA Intel SPDIF In (/dev/input/event12)
[ 11.647] (II) No input driver specified, ignoring this device.
[ 11.647] (II) This device may have been added with another device file.
[ 11.647] (II) config/udev: Adding input device HDA Intel Mic (/dev/input/event7)
[ 11.647] (II) No input driver specified, ignoring this device.
[ 11.647] (II) This device may have been added with another device file.
[ 11.647] (II) config/udev: Adding input device HDA Intel Line (/dev/input/event8)
[ 11.647] (II) No input driver specified, ignoring this device.
[ 11.647] (II) This device may have been added with another device file.
[ 11.648] (II) config/udev: Adding input device VirtualBox USB Tablet (/dev/input/event5)
[ 11.648] (**) VirtualBox USB Tablet: Applying InputClass "evdev pointer catchall"
[ 11.648] (**) VirtualBox USB Tablet: Applying InputClass "libinput pointer catchall"
[ 11.648] (**) VirtualBox USB Tablet: Applying InputClass "evdev pointer catchall"
[ 11.648] (II) Using input driver 'evdev' for 'VirtualBox USB Tablet'
[ 11.648] (**) VirtualBox USB Tablet: always reports core events
[ 11.648] (**) evdev: VirtualBox USB Tablet: Device: "/dev/input/event5"
[ 11.708] (--) evdev: VirtualBox USB Tablet: Vendor 0x80ee Product 0x21
[ 11.708] (--) evdev: VirtualBox USB Tablet: Found 9 mouse buttons
[ 11.708] (--) evdev: VirtualBox USB Tablet: Found scroll wheel(s)
[ 11.708] (--) evdev: VirtualBox USB Tablet: Found relative axes
[ 11.709] (--) evdev: VirtualBox USB Tablet: Found absolute axes
[ 11.709] (--) evdev: VirtualBox USB Tablet: Found x and y absolute axes
[ 11.709] (--) evdev: VirtualBox USB Tablet: Found absolute touchscreen
[ 11.709] (II) evdev: VirtualBox USB Tablet: Configuring as touchscreen
[ 11.709] (II) evdev: VirtualBox USB Tablet: Adding scrollwheel support
[ 11.709] (**) evdev: VirtualBox USB Tablet: YAxisMapping: buttons 4 and 5
[ 11.709] (**) evdev: VirtualBox USB Tablet: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 11.709] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:06.0/usb1/1-1/1-1:1.0/0003:80EE:0021.0001/input/input6/event5"
[ 11.709] (II) XINPUT: Adding extended input device "VirtualBox USB Tablet" (type: TOUCHSCREEN, id 10)
[ 11.709] (WW) evdev: VirtualBox USB Tablet: touchpads, tablets and touchscreens ignore relative axes.
[ 11.709] (II) evdev: VirtualBox USB Tablet: initialized for absolute axes.
[ 11.709] (**) VirtualBox USB Tablet: (accel) keeping acceleration scheme 1
[ 11.709] (**) VirtualBox USB Tablet: (accel) acceleration profile 0
[ 11.709] (**) VirtualBox USB Tablet: (accel) acceleration factor: 2.000
[ 11.709] (**) VirtualBox USB Tablet: (accel) acceleration threshold: 4
[ 11.710] (II) config/udev: Adding input device VirtualBox USB Tablet (/dev/input/js0)
[ 11.710] (II) No input driver specified, ignoring this device.
[ 11.710] (II) This device may have been added with another device file.
[ 11.710] (II) config/udev: Adding input device VirtualBox USB Tablet (/dev/input/mouse1)
[ 11.710] (II) No input driver specified, ignoring this device.
[ 11.710] (II) This device may have been added with another device file.
[ 11.711] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 11.711] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 11.711] (**) AT Translated Set 2 keyboard: Applying InputClass "libinput keyboard catchall"
[ 11.711] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 11.711] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 11.711] (**) AT Translated Set 2 keyboard: always reports core events
[ 11.711] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 11.711] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 11.711] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 11.711] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 11.711] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 11.711] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 11)
[ 11.711] (**) Option "xkb_rules" "evdev"
[ 11.711] (**) Option "xkb_model" "pc105"
[ 11.711] (**) Option "xkb_layout" "de"
[ 11.711] (**) Option "xkb_variant" "nodeadkeys"
[ 11.711] (**) Option "xkb_options" "grp:alt_shift_toggle,grp_led:scroll,terminate:ctrl_alt_bksp"
[ 11.712] (II) config/udev: Adding input device ImExPS/2 Generic Explorer Mouse (/dev/input/event4)
[ 11.712] (**) ImExPS/2 Generic Explorer Mouse: Applying InputClass "evdev pointer catchall"
[ 11.712] (**) ImExPS/2 Generic Explorer Mouse: Applying InputClass "libinput pointer catchall"
[ 11.712] (**) ImExPS/2 Generic Explorer Mouse: Applying InputClass "evdev pointer catchall"
[ 11.712] (II) Using input driver 'evdev' for 'ImExPS/2 Generic Explorer Mouse'
[ 11.712] (**) ImExPS/2 Generic Explorer Mouse: always reports core events
[ 11.712] (**) evdev: ImExPS/2 Generic Explorer Mouse: Device: "/dev/input/event4"
[ 11.712] (--) evdev: ImExPS/2 Generic Explorer Mouse: Vendor 0x2 Product 0x6
[ 11.712] (--) evdev: ImExPS/2 Generic Explorer Mouse: Found 9 mouse buttons
[ 11.712] (--) evdev: ImExPS/2 Generic Explorer Mouse: Found scroll wheel(s)
[ 11.712] (--) evdev: ImExPS/2 Generic Explorer Mouse: Found relative axes
[ 11.712] (--) evdev: ImExPS/2 Generic Explorer Mouse: Found x and y relative axes
[ 11.712] (II) evdev: ImExPS/2 Generic Explorer Mouse: Configuring as mouse
[ 11.712] (II) evdev: ImExPS/2 Generic Explorer Mouse: Adding scrollwheel support
[ 11.712] (**) evdev: ImExPS/2 Generic Explorer Mouse: YAxisMapping: buttons 4 and 5
[ 11.712] (**) evdev: ImExPS/2 Generic Explorer Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 11.712] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input5/event4"
[ 11.712] (II) XINPUT: Adding extended input device "ImExPS/2 Generic Explorer Mouse" (type: MOUSE, id 12)
[ 11.712] (II) evdev: ImExPS/2 Generic Explorer Mouse: initialized for relative axes.
[ 11.712] (**) ImExPS/2 Generic Explorer Mouse: (accel) keeping acceleration scheme 1
[ 11.712] (**) ImExPS/2 Generic Explorer Mouse: (accel) acceleration profile 0
[ 11.712] (**) ImExPS/2 Generic Explorer Mouse: (accel) acceleration factor: 2.000
[ 11.712] (**) ImExPS/2 Generic Explorer Mouse: (accel) acceleration threshold: 4
[ 11.713] (II) config/udev: Adding input device ImExPS/2 Generic Explorer Mouse (/dev/input/mouse0)
[ 11.713] (II) No input driver specified, ignoring this device.
[ 11.713] (II) This device may have been added with another device file.
[ 11.714] (II) config/udev: Adding input device ACPI Virtual Keyboard Device (/dev/input/event13)
[ 11.714] (**) ACPI Virtual Keyboard Device: Applying InputClass "evdev keyboard catchall"
[ 11.714] (**) ACPI Virtual Keyboard Device: Applying InputClass "libinput keyboard catchall"
[ 11.714] (**) ACPI Virtual Keyboard Device: Applying InputClass "evdev keyboard catchall"
[ 11.714] (II) Using input driver 'evdev' for 'ACPI Virtual Keyboard Device'
[ 11.714] (**) ACPI Virtual Keyboard Device: always reports core events
[ 11.714] (**) evdev: ACPI Virtual Keyboard Device: Device: "/dev/input/event13"
[ 11.714] (--) evdev: ACPI Virtual Keyboard Device: Vendor 0 Product 0
[ 11.714] (--) evdev: ACPI Virtual Keyboard Device: Found keys
[ 11.714] (II) evdev: ACPI Virtual Keyboard Device: Configuring as keyboard
[ 11.714] (**) Option "config_info" "udev:/sys/devices/virtual/input/input14/event13"
[ 11.714] (II) XINPUT: Adding extended input device "ACPI Virtual Keyboard Device" (type: KEYBOARD, id 13)
[ 11.714] (**) Option "xkb_rules" "evdev"
[ 11.714] (**) Option "xkb_model" "pc105"
[ 11.714] (**) Option "xkb_layout" "de"
[ 11.714] (**) Option "xkb_variant" "nodeadkeys"
[ 11.714] (**) Option "xkb_options" "grp:alt_shift_toggle,grp_led:scroll,terminate:ctrl_alt_bksp"
[ 11.726] (EE) Failed to open authorization file "/var/run/sddm/{0d86ffd0-aeec-4ffa-9ba1-7f2fa7edf610}": No such file or directoryNote: The same kernel-version as beowulf
@rolfie says that the RX580 works for them, I don't have that card or a 4k monitor so I can't really comment directly.
He as well other claim to have done something functioning but... either don't know how they have doing that or just need to write someone with the hope respond.
Terence wrote:vbeinfo is deprecated, videoinfo is actual command
Oops, sorry.
NoPs
Terence wrote:I meant the installation-representation, under *buntus is called `ubiquity`. There is much more to read and write. Maybe I can switch shortly to terminal command and force `os-installer-resolution` to higher value and be able to read the installer-text.
Well just use the non-graphical installer then. I was under the impression that the beowulf ISO didn't provide a graphical installer anyway.
Of course, and that's problem (with 4k-monitor), while kubuntu-installer (graphic/live) can scaale the resolution ('systemsettings5') or Virtual-Box can scale up (for seeing better by installation) and down (to 100%) after the installation... on real install is only a kind of colored terminal. This one ('colored terminal') I want scale up, anyway it not influence the installed system (for this remaine all mentioned 'problems').
Terence wrote:No newbie explanation here?
Apparently not, no.
If so, that's bad, very bad.
Considerations:
1. Xfce is not my solution (as well gnome and Co.) due to 200% scaling (and scaling back with writing in numerouse config.files).
2. Gtk is even not a solution (getting error messages even in synaptic besides Xfce).
3. Nobody know how to setup a good 4k or want not tell or I put the wrong questions (maybe I start a new thread).
4. If I not get a working solution for Devuan I will aquantaine myself with Gentoo.
#6 Re: Desktop and Multimedia » amdgpu-pro drivers » 2020-08-30 09:09:11
For Devuan the backports have a pin value of 100 by default and so will only be installed and upgraded from there if the --target option is used: https://backports.debian.org/Instructions/
I have tested in the VM, the addition of `backports` don't automatically update/upgrade all installed packages, but only the special picked. Buntu-Distros update/upgrade everything.
Kubuntu include the firmware blobs in the kernel (bunch of degenerates) and a beowulf VM will not "see" your video card unless you pass through the PCI address.
Check the lspci output in the VM, it will almost certainly show a virtual video card.
That's clear.
Well the RX580 card is definitely supported, as confirmed by rolfie earlier in this thread.
It is now a Vega64
If you're using VirtualBox (which you shouldn't because it's shit) then you need the "guest additions" for proper graphics support. Ask the interweb about it (or switch to QEMU/KVM, which is faster and generally better all-round).
Well, I followed your recommendation. Installed Beowulf on KVM (`virt-manager`) with `backports` and `firmaware-amd-graphics`.
Max. chooseable resolution is 1920*1200. Does it mean, due the fact that in KVM hasn't 'guest.iso', that if I install `Beowulf`on my NVMe I will have a max of ca. 1k instead of 4k?
Terence wrote:Installed former Devuan3.iso as main system and got black screen, can login, make apdates, install software but was not able to start GUI.
For a bare metal installation you will need the firmware-amd-graphics package, as I have mentioned several times now.
Baremetal yes, 4k (3840*2160) not at all. EDID is OK, firmware is OK, xrandr is ok, resolution not, the thread will never close this way.
Reading this https://wiki.gentoo.org/wiki/Xorg/Guide (start plasma5 with `openrc`) and due already tentative (in the past) to `startx` with the same commands:
startx
startkde
startx /usr/bin/startkde
startx -- vt7it appear that (former) installation on real machine failed completely/was not able to start plasma5.
Terence wrote:How can I increase the resolution during Installation? I cannot see anything!
Press c at the GRUB screen, use the vbeinfo command to list the supported resolutions then press escape and edit the installer GRUB menuentry to add the desired resolution to the end of the line that starts with linux; for example:
video=800x600@75
vbeinfo is deprecated, videoinfo is actual command, but by the ISO-start I can use a magnifier for that. Later on I can increase font-dpi for grub, etc. if I need.
I meant the installation-representation, under *buntus is called `ubiquity`. There is much more to read and write. Maybe I can switch shortly to terminal command and force `os-installer-resolution` to higher value and be able to read the installer-text.
Terence wrote:How to create the `Xorg-configuration-file` properly and how to point the system to look at that during start?
Read man xorg.conf. The system will automatically read the file if it is placed in the correct location.
I don't think I have to use # Xorg :0 -configure as here https://wiki.archlinux.org/index.php/Xorg explained because `xorg` already exist, what I need is:
1. Right placement of GPU-drivers
2. Resolution 3840*2160
3. 144*144 dpi
4. 10-bit color deepness
That's absolutely not clear for me, so far not clear that I cannot even start an attempt in the virtual OS. No newbie explanation here?
#7 Re: Desktop and Multimedia » amdgpu-pro drivers » 2020-08-27 12:59:57
Terence wrote:How to install 'kernel 5.4.0-42-generic'?
Do not do that, that kernel is hopelessly outdated and only available from Ubuntu.
If you want to try a newer kernel than the 4.19 LTS branch supplied with beowulf then install the linux-image-amd64 metapackage from the beowulf-backports repository.
And to repeat: you *do not* need to install the AMDGPU-PRO drivers, they will offer worse performance than the stock open-source drivers supplied with the kernel (and written by AMD themselves).
Regarding the backports-repository, I could install `Header files for Linux 5.4.0-0.bpo.2-amd64` from `backports/main` but... there are also things like `libreoffice 1.7` and generally I made bad experience with backports at least under kubuntu.
You are right. For comparison, I made a list of *ubuntu, Debian and Devuan and all three Distros use completely different Kernel even between different flavour (by ubuntu some times).
And you are also right about AMD-Drivers. I was accustomed to use (until three years ago) NVidia proprietary drivers and continue to do so also at (my) beginning with AMD-GPU. Not only daily update/upgrade of those drivers (PPA) but also daily change of display-quality with system-crash/freezing. I stop this.
Please post the output of
apt policy firmware-amd-graphics # dmesg | grep firmware # needs to be run as root uname -a
Actually (see above) I run Kubuntu as host and Beowulf in the VM
Host
$ apt policy firmware-amd-graphics
firmware-amd-graphics:
Installed: (none)
Candidate: (none)
Version table:searching for `firmware-amd` in `synaptic`, show me `amd64-microcode`, this one is blacklisted (see above post).
# dmesg | grep firmware
> no output there on the hostthis I posted already but, here is:
$ uname -a
Linux ter-Kub-20-04 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linuxand thus it's works under kubuntu
Client after inserting `backports`
$ apt policy firmware-amd-graphics
firmware-amd-graphics:
Installed: (none)
Candidate: 20190114-2
Version table:
20190114-2 500
500 http://deb.devuan.org/merged beowulf/non-free amd64 Packagesand after installation:
$ apt policy firmware-amd-graphics
firmware-amd-graphics:
Installed: 20190114-2
Candidate: 20190114-2
Version table:
*** 20190114-2 500
500 http://deb.devuan.org/merged beowulf/non-free amd64 Packages
100 /var/lib/dpkg/status# dmesg | grep firmware
> also here no output (client)this I posted (too) already but, here is:
uname -a
Linux devuan 4.19.0-10-amd64 #1 SMP Debian 4.19.132-1 (2020-07-24) x86_64 GNU/LinuxTerence wrote:It's not (meanwhile) a question of `sources.list`, it's a question of to small resolution
Your desired resolution will only be supported if you have the firmware package from the non-free component of the repositories so they are entirely relevant here.
It is possible that your monitor isn't supplying a valid EDID block (or perhaps the cable or connector is sub-standard) but the most likely cause is a lack of firmware.
EDIT:
Terence wrote:Another 'nice to have' could be 10 Bit deep color representation
Create an X.Org configuration file with a Screen section containing this option:
DefaultDepth 30See also https://linuxreviews.org/HOWTO_enable_1 … r_on_Linux
I install each OS with `non-free` components due online games (for my wife) using `flash`, netflix, etc. and I'm sure to have installed `firmware-amd-graphics` on beowulf want not start at all on my main machine giving me only black-screen and cursor. By the way, this is not newbie-friendly at all, I mean: this package, if crucial for displaying even 1k (1920*1080) and today even smart-phones has such resolution.
Thanks for your submitted link at first, that allowed me to find EDID-report, and here is a part of them to find under `/var/log/Xorg.0log` in the kubuntu-machine
[ 7.139] (II) AMDGPU(0): EDID Version: 1.4
[ 7.139] (II) AMDGPU(0): Digital Display Input
[ 7.139] (II) AMDGPU(0): 10 bits per channel
[ 7.139] (II) AMDGPU(0): Digital interface is DisplayPort
[ 7.139] (II) AMDGPU(0): Max Image Size [cm]: horiz.: 61 vert.: 35
[ 7.139] (II) AMDGPU(0): Gamma: 2.20
[ 7.139] (II) AMDGPU(0): DPMS capabilities: Off
[ 7.139] (II) AMDGPU(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4 YCrCb 4:2:2
[ 7.139] (II) AMDGPU(0): First detailed timing is preferred mode
[ 7.139] (II) AMDGPU(0): Preferred mode is native pixel format and refresh rate
[ 7.139] (II) AMDGPU(0): Display is continuous-frequency
[ 7.139] (II) AMDGPU(0): redX: 0.634 redY: 0.341 greenX: 0.312 greenY: 0.636
[ 7.139] (II) AMDGPU(0): blueX: 0.158 blueY: 0.062 whiteX: 0.312 whiteY: 0.329
[ 7.139] (II) AMDGPU(0): Supported established timings:
[ 7.139] (II) AMDGPU(0): 640x480@60Hz
[ 7.139] (II) AMDGPU(0): 800x600@56Hz
[ 7.139] (II) AMDGPU(0): 800x600@60Hz
[ 7.139] (II) AMDGPU(0): 1024x768@60Hz
[ 7.139] (II) AMDGPU(0): Manufacturer's mask: 0
[ 7.139] (II) AMDGPU(0): Supported standard timings:
[ 7.139] (II) AMDGPU(0): #0: hsize: 1280 vsize 800 refresh: 60 vid: 129
[ 7.139] (II) AMDGPU(0): #1: hsize: 1280 vsize 720 refresh: 60 vid: 49281
[ 7.139] (II) AMDGPU(0): #2: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
[ 7.139] (II) AMDGPU(0): #3: hsize: 1600 vsize 900 refresh: 60 vid: 49321
[ 7.139] (II) AMDGPU(0): #4: hsize: 1680 vsize 1050 refresh: 60 vid: 179
[ 7.139] (II) AMDGPU(0): #5: hsize: 1440 vsize 900 refresh: 60 vid: 149
[ 7.139] (II) AMDGPU(0): Supported detailed timing:
[ 7.139] (II) AMDGPU(0): clock: 533.2 MHz Image Size: 607 x 345 mm
[ 7.139] (II) AMDGPU(0): h_active: 3840 h_sync: 3888 h_sync_end 3920 h_blank_end 4000 h_border: 0
[ 7.139] (II) AMDGPU(0): v_active: 2160 v_sync: 2163 v_sync_end 2168 v_blanking: 2222 v_border: 0
[ 7.139] (II) AMDGPU(0): Ranges: V min: 40 V max: 60 Hz, H min: 135 H max: 135 kHz, PixClock max 605 MHz
[ 7.139] (II) AMDGPU(0): Monitor name: U28E590
[ 7.139] (II) AMDGPU(0): Serial No: HTPK402543
[ 7.139] (II) AMDGPU(0): Supported detailed timing:
[ 7.139] (II) AMDGPU(0): clock: 148.5 MHz Image Size: 607 x 345 mm
[ 7.139] (II) AMDGPU(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
[ 7.139] (II) AMDGPU(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
[ 7.139] (II) AMDGPU(0): Supported detailed timing:
[ 7.139] (II) AMDGPU(0): clock: 241.5 MHz Image Size: 607 x 345 mm
[ 7.139] (II) AMDGPU(0): h_active: 2560 h_sync: 2608 h_sync_end 2640 h_blank_end 2720 h_border: 0
[ 7.139] (II) AMDGPU(0): v_active: 1440 v_sync: 1443 v_sync_end 1448 v_blanking: 1481 v_border: 0
[ 7.139] (II) AMDGPU(0): Number of EDID sections to follow: 1
[ 7.139] (II) AMDGPU(0): EDID (in hex):
[ 7.139] (II) AMDGPU(0): 00ffffffffffff004c2d4d0c46584d30
[ 7.139] (II) AMDGPU(0): 0f1c0104b53d23783b5fb1a2574fa228
[ 7.139] (II) AMDGPU(0): 0f5054230800810081c08180a9c0b300
[ 7.139] (II) AMDGPU(0): 9500010101014dd000a0f0703e803020
[ 7.139] (II) AMDGPU(0): 35005f592100001a000000fd00283c87
[ 7.139] (II) AMDGPU(0): 873c010a202020202020000000fc0055
[ 7.139] (II) AMDGPU(0): 3238453539300a2020202020000000ff
[ 7.139] (II) AMDGPU(0): 004854504b3430323534330a202001e5
[ 7.139] (II) AMDGPU(0): 02030ef041102309070783010000023a
[ 7.139] (II) AMDGPU(0): 801871382d40582c45005f592100001e
[ 7.139] (II) AMDGPU(0): 565e00a0a0a02950302035005f592100
[ 7.139] (II) AMDGPU(0): 001a0000000000000000000000000000
[ 7.139] (II) AMDGPU(0): 00000000000000000000000000000000
[ 7.139] (II) AMDGPU(0): 00000000000000000000000000000000
[ 7.139] (II) AMDGPU(0): 00000000000000000000000000000000
[ 7.139] (II) AMDGPU(0): 000000000000000000000000000000bf
[ 7.139] (II) AMDGPU(0): Printing probed modes for output DisplayPort-2
[ 7.139] (II) AMDGPU(0): Modeline "3840x2160"x60.0 533.25 3840 3888 3920 4000 2160 2163 2168 2222 +hsync -vsync (133.3 kHz eP)
[ 7.139] (II) AMDGPU(0): Modeline "2560x1440"x60.0 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync (88.8 kHz e)
[ 7.139] (II) AMDGPU(0): Modeline "1920x1200"x60.0 533.25 1920 3888 3920 4000 1200 2163 2168 2222 +hsync -vsync (133.3 kHz e)
[ 7.139] (II) AMDGPU(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
[ 7.139] (II) AMDGPU(0): Modeline "1920x1080"x59.9 148.35 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.4 kHz e)
[ 7.139] (II) AMDGPU(0): Modeline "1600x1200"x60.0 533.25 1600 3888 3920 4000 1200 2163 2168 2222 +hsync -vsync (133.3 kHz e)
[ 7.139] (II) AMDGPU(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)
[ 7.139] (II) AMDGPU(0): Modeline "1600x900"x60.0 108.00 1600 1624 1704 1800 900 901 904 1000 +hsync +vsync (60.0 kHz e)
[ 7.139] (II) AMDGPU(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 7.139] (II) AMDGPU(0): Modeline "1440x900"x59.9 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz e)
[ 7.139] (II) AMDGPU(0): Modeline "1280x800"x59.8 83.50 1280 1352 1480 1680 800 803 809 831 -hsync +vsync (49.7 kHz e)
[ 7.139] (II) AMDGPU(0): Modeline "1280x720"x60.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
[ 7.139] (II) AMDGPU(0): Modeline "1280x720"x59.9 74.18 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
[ 7.139] (II) AMDGPU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 7.139] (II) AMDGPU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 7.139] (II) AMDGPU(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 7.139] (II) AMDGPU(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 7.139] (II) AMDGPU(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)and no, I don't touch cable or move hardware, just insert USB-stick with Devuan, install it and got black screen.
If you ask me (as newbie) I would say: Devuan take anyway
Supported established timings:with/at 1024 instead of
Supported detailed timing:or
Printing probed modes for output DisplayPort-2with/at 4k.
But, that's just nagging from my side. Facts are:
1. Installed former Devuan3.iso in VM and cannot get a bigger resolution than 1024, no matter what I try.
2. Installed former Devuan3.iso as main system and got black screen, can login, make apdates, install software but was not able to start GUI.
3. Installed newer Devuan3 in VM and (thank you) this time can I get under `systemsettings5` the full choice on resolutions.
4. In the link you provide (was anyway useful) is not explained how to create the necessary file and how to point the system during start to look at this file, besides no explanation on how to start applications (not supporting 10 ) in 8-bit-mode.
My questions:
1. Start Xorg anyway even in text-mode without GUI?
2. Does GRUB use Xorg?
3. If yes, how can I set the right resolution for GUI, TTY and GRUB?
4. How can I increase the resolution during Installation? I cannot see anything!
5. How to start GUI in Devuan with KDE and OpenRC?
6. How to create the `Xorg-configuration-file` properly and how to point the system to look at that during start?
7. How to let read the system at EDID and configure Xorg properly?
8. Where to store the information/data of `xrandr`?
I read/study now this since almost one year, everydody write someting but all is fractionary, nothing complete, even not in the Arch-Linux wiki, e.g. there is written how to crate a `xorg.conf` but not where to fing the right data to write/insert in the right section.
Can you help me? Do you know a newbie-wiki?
#8 Re: Desktop and Multimedia » amdgpu-pro drivers » 2020-08-25 14:16:59
@Terence
I recently bought Asus 8GB RX 580 graphics card just for Blender 2.8x's rendering engine. Blender supports OpenCL for rendering.
It was on fresh installation of Devuan 3.0.0 in new partition (/dev/sda1) after spending hours to setup the AMD's graphics driver without success.
Here is the steps I've done to setup for RX 580.Installed amd64-microcode, firmware-amd-graphics packages.
Switched to text mode during boot by removing /etc/rc2.d/S04slim
Created ~/.xinitrc
#!/bin/sh # /etc/X11/xinit/xinitrc # # global xinitrc file, used by all X sessions started by xinit (startx) exec startxfce4It solved "permission denied", "/bin/sh: Can't open /usr/bin/X" failures.
To start Xfce, run startx.
> inxi -G Graphics: Device-1: AMD Ellesmere [Radeon RX 470/480] driver: amdgpu v: kernel Display: tty server: X.Org 1.20.4 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Radeon RX 580 Series (POLARIS10 DRM 3.35.0 5.4.0-0.bpo.2-amd64 LLVM 7.0.1) v: 4.5 Mesa 18.3.6
Installation of AMD's graphics driverDownloaded amdgpu-pro-19.50-967956-ubuntu-18.04.tar.xz
I found the page and followed the instruction but it did not work out.
https://gist.github.com/kytulendu/3351b … 1ea3c95cbeI extracted the amdgpu-pro package and moved to the directory
amdgpu-pro-19.50-967956-ubuntu-18.04ran the installation script with options
./amdgpu-pro-install --opencl=legacy,pal --headless --no-dkms....
Thanks for your answer, that's great.
I read about advantages of newer Kernel, newer Plasma5 and newer drivers, but... I'm newbie.
I installed `Beowulf` in the past in the VM and on NVMe. The VM give me only 1024 resolution with no chance to change it anyway, the NVMe give me no GUI; only text and cursor. This time, the VM give me full 4k-resolution and I hope to be successful with your help.
My hardware: x399 MB, TR4 1900 CPU, Vega 64 GPU (the x580 got my wife), 512GB NVMe, 64 GB RAM.
OS: Kubuntu 20.04
Target OS: Beowulf (Devuan 3), newer Kernel (5.4), newer GPU-drivers, 4k resolution and maybe Plasma 5.18.5 instead of 5.14.5, but Plasma is secondary/not mandatory. Another 'nice to have' could be 10 Bit deep color representation, but... maybe is only a dream at moment under Linux.
Target OS-details: Devuan-Beowulf, KDE, parallelized OpenRC. That I know how to but... I don't know how to start/stop GUI (you use xfce). Note: KDE is a must (for my wife), the only given alternative is "Astra-Linux" (I dislike this one).
Following the outputs of running system (Kubuntu 20.04 = host) and virtual system (Beowulf 3 = client)
> `Virtualbox:` inxi -G
Graphics: Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.15.0.0
Display: x11 server: X.Org 1.20.4 driver: vmware unloaded: fbdev,modesetting,vesa resolution: 3840x2160_vbox~60Hz
OpenGL: renderer: SVGA3D; build v: 2.1 Mesa 18.3.6> `Kubuntu 20.20:` inxi -G
Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Vega 10 XL/XT [Radeon RX Vega 56/64] driver: amdgpu v: kernel
Display: x11 server: X.Org 1.20.8 driver: amdgpu FAILED: ati unloaded: fbdev,modesetting,vesa
resolution: 3840x2160~60Hz
OpenGL: renderer: Radeon RX Vega (VEGA10 DRM 3.35.0 5.4.0-42-generic LLVM 10.0.0) v: 4.6 Mesa 20.0.8 > `Virtualbox:` glxinfo | grep AMD
GL_AMD_shader_trinary_minmax, GL_ANGLE_texture_compression_dxt3,> `Kubuntu 20.20:` glxinfo | grep AMD
> no output here
>`Virtualbox: uname -a
Linux devuan 4.19.0-10-amd64 #1 SMP Debian 4.19.132-1 (2020-07-24) x86_64 GNU/Linux> `Kubuntu 20.20:` uname -a
Linux ter-Kub-20-04 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/LinuxMy questions:
1. How to install 'kernel 5.4.0-42-generic'? have you a guide for newbie?
2. Have I to reinstall the GPU-driver by each kernel upgrade? You don't install 'dkms'!
3. I haven't "/etc/rc2.d/S04slim" (at least in the VM), will I have on NVMe? Even if I use 'openrc' and 'kde'? Just rename, displace or remove? How to boot in GUI afterward?
4. In this thread http://dev1galaxy.org/viewtopic.php?pid=5067#p5067 and on my kubuntu machine are `/etc/modprobe.d/fbdev-blacklist.conf` and `/etc/modprobe.d/amd64-microcode-blacklist.conf`. Whats about that?
5. To can start the `./amdgpu-pro-install --opencl=legacy,pal --headless --no-dkms` is needed to modify the `case "$ID" in` or not? Can you be more precise please?
Thanks and best regards
#9 Re: Desktop and Multimedia » amdgpu-pro drivers » 2020-08-25 10:46:08
@ http://dev1galaxy.org/profile.php?id=5581.
Yes, I know. It was a (failed) tentative/attempt to get 4k resolution.
@ http://dev1galaxy.org/profile.php?id=5048.
It's not (meanwhile) a question of `sources.list`, it's a question of to small resolution.
After long time and reading this http://dev1galaxy.org/viewtopic.php?pid=5067#p5067 I loose almost the hope to setup Devuan as main OS.
I will open a new thread for 4k.
#10 Re: Installation » Devuan on native ZFS-Root » 2020-03-22 14:11:49
Good morning ladies & gentleman's,
now I try a couple of days to get Devuan 2.1 up and running with ZFS in the Virtualbox with no good results, but enabling EFI and try acces the "shell" as soon as permitted I learn a lot... e.g. "ash" as shell, "nano" as editor...
I tray even other OS's like Kubuntu 20.04 but reading this... it appear to be a big problem with "SystemD", also no chance, hence I abandon finally waste of time with this.
Due the fact "FreeNAS" & co. use "OpenRC" as "Init-System", it appear to me, as absolutely new regarding "BSD", but acquainted with some Linux-commands... I have the only possibility with Devuan + OpenRC + KDE.
Reading the above article it appear to be a must to set up much more "Data-Sets" as I previously expect, if it's necessary!? I don't know!
Finally i found this Devuan on ZFS and the "LUKS-Cryprosetup" look very good even if by reading linked article is not clear if "/boot" should have own extra partition or not, here, apparently not. Anyway, since I have 0,5 TB NVMe for the OS and UEFI (extra partition), but, these instructions (can) works by installing "desktop-ISO" (GTK), by "DVD-ISO" too? I will see.
Here my Hardware:
- MB one of latest PCI-3e
- CPU 8 core 16 Threads
- RAM 64 GiB (8-banks)
- NVMe 512 MiB
- GPU 8 GiB PCI-3e
- Data-HDD 4 TiB Sata3
Here my wish:
- Devuan "latest stable" 2.1
- ZFS on whole system, excluding "EFI-partition"?
- LUKS-Cryptosetup, excluding "EFI-partition"?
- OpenRC (parallelized)
- KDE as DE
Here my questions:
1. Why dividing "/" (root) from "/home" under "LUKS"?
2. Why dividing "/" (root) from "/home" under "ZFS"?
3. Do I need an extra "/boot"-partition even if I have EFI?
4. What sould be necessarily "snapshotted" with ZFS and what not?
5. ZFS don't need "Swap" but Devuan?. A "Swap-file" instead of partition? how do it? Ones ZFS up and runnig delete "Swap" and "entry" in "/etc/fstab"?
6. Which version of ASH is in Devuan 2.1? Could I get a link with command-list?
7. Want use "GPT", is "parted" OK? Under point "5." is a link that mention "--script", is a selfmade scripts or standard in "parted"?
Thanks again and sorry for silly questions from my side.
#11 Installation » Devuan on native ZFS-Root » 2020-03-19 14:46:28
- Terence
- Replies: 5
Dear dev1ers,
i have installed Kubuntu 18.04 in VB with native ZFS-Root following those instructions and works.
Now, trying to do the same with Devuan_Ascii_DVD.iso /expert install) not working, maybe has not "ubuquity"? Maybe is configured different? Anyway, as soon appear the possibility to access the "bash-terminal" and bevore "partitioning"... the bash don't let me use "apt", "apt-get" to install "zfsutils".
I don't know if the "desktop-live.iso" allow me that ==> "ubiquity" (if any) is working like under Kubuntu but... for me is anyway unusefull because I need the DVD for installing KDE & OpenRC too.
Can you provide me some link-s with reliable and easy to understand instructions on how to do this? Please consider, I'm only user/newbee.
Considering the readed posting on the web and here in forum... appear ZFS more stable, fast and resistent to attacks too. Please consider, for next Devuan (maybe 3.0) to add the option of installing the OS on native ZFS-Root, here is a adaptable program, I read also about some Proxmox-packages that allow a kind of "webmanaging-GUI" for ZFS, maybe can be ported to Devuan.
That could be great for Linux-acquainted-users want build a own server completely on ZFS-basis, of-course could be great to backport "zfsutils" 0.8 to Devuan (if possible).
Other instruction I read are for Xenial (16.04), I read also these here and these.
P.S.: For me is coming the time to abbandone completely the *ubuntu-family and make our family-systems secure and fast, please for your help!
Thanks in advance and best regards. Terence
#12 Re: Other Issues » Devuan + paralleized OpenRC + KDE » 2019-10-06 00:04:59
@ b3bgd
I admit to be a Newbie and I'm not ashamed for that, I accept and welcome each constructive criticism.
Don't take me wrong, but, if you convey the rights commands how should be... I will correct immediately as already in the past have done.
ᑟ ᐒ
#13 Re: Desktop and Multimedia » How to install and configure Roger-Router in Devuan 2 » 2019-09-01 08:02:28
Thanks for your answer first,
i know this link including the instruction to install in "Debian 9 Strech", equivalent of our Devuan ASCII
https://software.opensuse.org//download … kage=roger, but... do you mean i should install the *deb-Package (of Debian) or use the method mentioned here https://wiki.debian.org/CreatePackageFromPPA by including "debian 9"-repo and adapt to ascii? And how do this? I'm not so experienced with it!
Sincerely!? The tests under normal Kubuntu (18.04) was not god even with PPA and instructions picked around, besides, Tabos (and other places/pages) instruct to add the "Fax-Printer" manually with:
lpadmin -p Roger-Router-Fax -m drv:///sample.drv/generic.ppd -v socket://localhost:9100/ -E -o PageSize=A4this don't work under Devuan (at least not in VM/VB).
In my Fritz!Box is a fax already integrated but this has a very big headline taking 25-33% of DIN-A4, this want avoid because, even fax is no more required on daily-basis (as in the past) but when today needed, cannot send such "transformed" pages.
The original "ffgtk" was god (practically the copy of original "Fritz!Fax) as well the first versions of "roger", but become worse and worse with time.
Nonetheless, the addition of a PPA for "Debian 9", picking only the source as mentioned in second Link and build the packages from those for Devuan could be interesting thing for other (more reliable) applications or mess completely the system.
But That's another story.
#14 Desktop and Multimedia » How to install and configure Roger-Router in Devuan 2 » 2019-08-31 09:09:49
- Terence
- Replies: 2
Hello everybody,
was surprised to find the package in my VM with:
apt-cache search rogerfirst installed only "roger-router" than also "ffgtk" and finally everything with:
sudo apt install --reinstall roger-router* ffgtkfirst start "roger" from Application-Menu, an error-message could not open /var/spool/roger no permission,
starting over the "cli" didn't happen nothing no error message, nada, even the start with:
sudo -i roger-router don't bring anything.
After install of "ffgtk" got the same, after installed "roger-router-cli" starting it with and without "Root-Privileges" give the same results.
The only thing happen after starting "roger-router-cli" with Root-Privs..., if afterward i start "roger" over menu disappear fast immediately without any error message.
Have someone of you step-by-step instruction (better for newbie) on how to install and configure "Roger" properly?
Thank you All in advance and best regards.
#15 Re: Other Issues » Devuan + paralleized OpenRC + KDE » 2019-08-08 08:46:36
Terence wrote:Dear All, dear Devs,
Counter-check everything is like you want!
1. Check 'OpenRC' is up and running:pidof /sbin/init && echo "openrc" || echo "other"Output:
1
openrcThanks to all you guys (Terence, golinux, fmithred, et.al.) I followed your instructions to the letter, reinstalled Devuan, moved to Ceres and got openrc, kudos to the devs and you too. THANKS!
By the way, small typo: there is a quotation mark missing after the word 'other', no biggie...
Thanks a lot for your feedback & forall your correction, i apply it and appreciate, thanks again.
#16 Re: Other Issues » Devuan + paralleized OpenRC + KDE » 2019-08-07 07:36:21
Hello I have a question for OpenRC users who use the option paralleized OpenRC
Parallel startup in OpenRC was disabled by default due to https://bugs.gentoo.org/show_bug.cgi?id=391945 this bug. I understand this is a critical bug. Is any of you is affected by this bug? How do you think it is safe to use this feature?
https://bugs.gentoo.org/show_bug.cgi?id=391945This bug same to be solved, see https://bugs.gentoo.org/391945#c42last post, here the plain text:
Benda Xu gentoo-dev 2019-07-09 10:40:44 UTC
This bug is has been turned into a feature request to upstream the boot dependency loop solver implemented for Debian.The present status: in Debian the loop solver by Okunev worked perfectly well for more than 5 years.
#17 Re: Desktop and Multimedia » KDE-5/Plasma-5 homogeneous Appearance, missing Icons & irregular Fonts » 2018-09-05 21:06:48
I followed the instructions but on the second stage, I got:
root@devuan:/home/astheroth# mv /etc/xdg/Trolltech.conf /etc/xdg/bak.Trolltech.conf mv: it couldn't be done `stat' over '/etc/xdg/Trolltech.conf': the file or directory doesn't exist. root@devuan:/home/astheroth# mv /etc/gtk-3.0/settings.ini /etc/gtk-3.0/bak.settings.ini mv: it couldn't be done `stat' over '/etc/gtk-3.0/settings.ini': the file or directory doesn't existAny idea?
That's mine the file is not present, so you don't need to rename/move the original (of course is not present).
Just continue with the other steps.
Best regards
#18 Re: Other Issues » Devuan + paralleized OpenRC + KDE » 2018-07-30 15:52:51
No, i use 8 cores. It is Intel i7 920 (8) @ 2.7GHz
May i ask you which file-system you use? 'ext4', 'btrfs' other?
Our motherboard should be similar, i use an MSI-x58 over-clocked CPU from 2.93 to 4.0 GHz (182x22).
#19 Re: Other Issues » Devuan + paralleized OpenRC + KDE » 2018-07-30 13:16:52
OpenRC, in my opinion, is not ready for production. Anyone using OpenRC should have that in mind. In addition, I did not notice practically any difference between sysvinit and OpenRC (I mean loading and reloading speeds). So, I decided to stay with a verified sysvinit. Thank you for your attention.
Thanks for your feedback first.
Till now i installed Devuan+OpenRC+KDE "only" in the VirtualBox using 4 of 12 CPU-cores (Xeon 6 core 12 threads), the new PC-Parts (on which was supposed to install the final system) are on the way, hence i cannot tell you about the behavior in real machine.
I also not seen the warning message (cause of VM?), however i start the machine several time @ day and never got any problem.
Do you use only one core? I can imagine that one core managing 20 processes running all under PID N°1 can cause difficulties.
I also tested TrueOS (FreeBSD) in the past on real machine there use also "OpenRC" but @ time i not yet knew how to parallelize it.
Those test was abandoned due too slow network and my incapability to set up a dark UI.
The dark UI (e.g. obsidian coast or breeze dark) is essential for my eyes and even if KDE take (for me) the wrong way (wit Dolphin, Kate, Kdesudo) i'm forced to use it (even if the appearances are to be settled twice (as user and as admin)) because is the only UI i learn to modify the appearance properly. For other machines @ home i have to use KDE too because of similarity of Kick-Off with Windows (used in the company) and for maintenance simplicity (only one UI).
Now, i would't go back to Kubuntu (cause of systemd). OpenRC is relatively new (@ least in Linux (as far i know)) nonetheless it is daily improved.
I hope, soon will be removed the latter rest of systemd from Devuan so i can sleep quieter.
Additional feedback will follow after assembly and install on latest incoming hardware.
#20 Re: Other Issues » Devuan + paralleized OpenRC + KDE » 2018-07-24 10:21:11
Thanks a lot
Now I got a lot of more understanding about the install process of Devuan-Linux, sincerely thanks again.
For me , as linux-newbie, is then Devuan_DVD-ISO_Graphical-Expert-Install the best solution to reach the target and hope other user can help it too.
Thank you make it possible through your efforts/work.
It would be great if someone could make a "Wiki" about, also because can be applied to all available desktops-environment offered in Devuan.
Parallelized OpenRC is SystemD-Myths-BUSTER !!!
#21 Re: Other Issues » Devuan + paralleized OpenRC + KDE » 2018-07-23 09:24:38
xe-non wrote:Can I choose mate like kde (on 4th step)?
Yes, Mate is there to choose from.
Terence wrote:Sorry but that's wrong, I post the Link with ISO let you install 'OpenRC' and KDE from beginning, NO Postinstall, only Post-Parallelism!
fsmithred was speaking about the "Live .isos" which are different than the DVDs that you installed with.
So, it would indeed have to be done post-install if a user has installed Devuan with a Live .iso.
I understand, but, I'm also newbie and can tell that the only substantial difference between "Live-ISO" and "DVD-ISO" is to make a 'click' to select the "Init-System". That's much more easier than substitute the "Init-System" post-install.
I hope we are still talking about "Graphical Expert Install" contained in the "DVD-ISO".
I'm scared too using "command-line" by installation.
Naturally could be a great thing if DEVs add the "Init-System" option in the Live-Iso and maybe out of the box "OpenRC" already parallelized.
Sure is, I never seen and had KDE full installed and operating using only 510 MB RAM and never seen OS booting faster than BIOS-POST.
At this point again: Greatest Job done by Devuan-DEVs!
#22 Re: Other Issues » Devuan + paralleized OpenRC + KDE » 2018-07-22 16:09:54
Can I do it (mate+openrc) using devuan_..._dvd-1.iso?
Sorry I have no idea about Mate but with the DVD-ISO in 'expert graphical mode' you cann install the 'OpenRC' @ beginning.
That's much easier than Post-Install + deleting/deactivate former 'sysinit'
#23 Re: Other Issues » Devuan + paralleized OpenRC + KDE » 2018-07-22 16:02:44
Since openrc is not installed in the current live isos, it won't be installed with the system. You can add it after you reboot into the new system. If openrc becomes the default init system in devuan at some time in the future, you will get it in the live isos, and in that case, if you want sysvinit, you'd have to add it after the initial installation.
If you want to install devuan with openrc on a lot of computers, you could make your own live iso with openrc. You would install the first system with sysvinit, change it to openrc, then run refractasnapshot to make a new iso. Then, any installs you did with the new iso would have openrc right from the start. I've already tried this, and it works.
Sorry but that's wrong, I post the Link with ISO let you install 'OpenRC' and KDE from beginning, NO Postinstall, only Post-Parallelism!
#24 Re: DIY » Miyo (make it your own) KDE Plasma » 2018-07-22 15:52:30
Hi Guys, HI
For anyone interested, I'll make a "How to Miyo Devuan LXQt" soon. Believe it or not, it's a little more involved than Plasma.
Here how to make Devuan faster than each other Linux/Unix, tested with Devuan KDE, compared to Devuan Xfce, KDE-Neon, Kubuntu 18.04. To whom is interested, Enjoy!
#25 Re: DIY » Miyo (make it your own) KDE Plasma » 2018-07-22 15:41:20
Hi guys. HI
Couple of other things, and I'll edit the post of packages needed....
look @ this posting for homogeneous Plasma-5
https://dev1galaxy.org/viewtopic.php?id=2252
ENJOY !
Board footer
