You are not logged in.
- Topics: Active | Unanswered
#126 Re: Hardware & System Configuration » Ascii kernel update borks laptop » 2021-08-11 01:53:35
Fatigue got me. I didn't see any chance of progress so I just gave up. Anyway, for the sake of completion, here is the output. Still nothing useful.
root@nautilus:~# apt install icedtea-netx-common --dry-run
Reading package lists... Done
Building dependency tree
Reading state information... Done
icedtea-netx-common is already the newest version (1.6.2-3.1+deb9u1).
icedtea-netx-common set to manually installed.
The following package was automatically installed and is no longer required:
linux-image-4.9.0-14-amd64
Use 'apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.But... there has been another kernel update since this one that cause the weird problem. For some reason, it was not installed even though the headers were. (That's how I know about it.) Why? I did not use the hold command. I just purged the kernel version that was causing the problem. Could I install it manually? I'm thinking of trying that, and if it still cause the problem, at least I can get the xorg.log that is produced.
#127 Re: Hardware & System Configuration » Ascii kernel update borks laptop » 2021-07-09 00:11:42
nemo@nautilus:~$ apt list | grep installed | grep openjdk
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
openjdk-8-jre/oldstable-security,now 8u292-b10-0+deb9u1 amd64 [installed,automatic]
openjdk-8-jre-headless/oldstable-security,now 8u292-b10-0+deb9u1 amd64 [installed,automatic]
nemo@nautilus:~$ apt list | grep installed | grep icedtea
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
icedtea-8-plugin/now 1.6.2-3.1 amd64 [installed,local]
icedtea-netx-common/oldstable,now 1.6.2-3.1+deb9u1 all [installed,automatic]#128 Re: Hardware & System Configuration » Ascii kernel update borks laptop » 2021-07-08 22:57:10
OK, we finally have a result.
nemo@nautilus:~$ apt-cache rdepends icedtea-netx
icedtea-netx
Reverse Depends:
icedtea-8-plugin
icedtea-netx-common
libbiojava4.0-java
nemo@nautilus:~$ apt-cache depends icedtea-netx
icedtea-netx
Depends: openjdk-8-jre
Depends: icedtea-netx-common
Conflicts: <openjdk-6-jre>
Conflicts: <openjdk-6-jre-headless>
Replaces: <openjdk-6-jre>
Replaces: <openjdk-6-jre-headless>#129 Re: Hardware & System Configuration » Ascii kernel update borks laptop » 2021-07-08 17:53:36
Well, Linux command line programs are ingenius in their ability to find nitpicks in commands. I couldn't figure out how to get apt-cache to not interpret the - inside a file name as a command switch.
root@nautilus:~# apt list | grep installed | grep icedtea
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
icedtea-8-plugin/now 1.6.2-3.1 amd64 [installed,local]
icedtea-netx-common/oldstable,now 1.6.2-3.1+deb9u1 all [installed,automatic]
root@nautilus:~# apt-cache rdepends --installed $icedtea-netx
E: Command line option 'n' [from -netx] is not understood in combination with the other options.
root@nautilus:~# apt-cache rdepends --installed "$icedtea-netx"
E: Command line option 'n' [from -netx] is not understood in combination with the other options.
root@nautilus:~# apt-cache rdepends --installed $icedtea
E: No packages found#130 Re: Hardware & System Configuration » Ascii kernel update borks laptop » 2021-07-08 00:23:36
It complains that "apt upgrade --dry-run" is not a valid combination of options. Without the --dry-run, it just updates the package databases. Did you mean something else? The other works, but doesn't seem to produce any new information.
root@nautilus:/# apt upgrade --dry-run
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following package was automatically installed and is no longer required:
linux-image-4.9.0-14-amd64
Use 'apt autoremove' to remove it.
The following packages have been kept back:
icedtea-netx
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
#131 Re: Hardware & System Configuration » Ascii kernel update borks laptop » 2021-07-07 23:39:05
Linux nautilus 4.9.0-15-amd64 #1 SMP Debian 4.9.258-1 (2021-03-08) x86_64 GNU/Linux
#132 Re: Hardware & System Configuration » Ascii kernel update borks laptop » 2021-07-07 22:49:36
Please also post the X.Org and display manager logs.
Does it save X.Org.log past the last boot? All I could find was the current version and the .old from the previous boot, which is after I had purged the problematic kernel. Where would it put any older saves?
[ 1687.349]
X.Org X Server 1.19.2
Release Date: 2017-03-02
[ 1687.349] X Protocol Version 11, Revision 0
[ 1687.349] Build Operating System: Linux 5.10.0-5-amd64 x86_64 Debian
[ 1687.349] Current Operating System: Linux nautilus 4.9.0-15-amd64 #1 SMP Debian 4.9.258-1 (2021-03-08) x86_64
[ 1687.349] Kernel command line: BOOT_IMAGE=/vmlinuz-4.9.0-15-amd64 root=UUID=95bc46a7-4cfa-4d61-820d-206e3ff12230 ro quiet acpi_backlight=vendor
[ 1687.349] Build Date: 15 April 2021 11:19:14AM
[ 1687.349] xorg-server 2:1.19.2-1+deb9u8 ([url]https://www.debian.org/support[/url])
[ 1687.349] Current version of pixman: 0.34.0
[ 1687.349] Before reporting problems, check [url]http://wiki.x.org[/url]
to make sure that you have the latest version.
[ 1687.349] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 1687.349] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jul 6 19:32:24 2021
[ 1687.350] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 1687.350] (==) No Layout section. Using the first Screen section.
[ 1687.350] (==) No screen section available. Using defaults.
[ 1687.350] (**) |-->Screen "Default Screen Section" (0)
[ 1687.350] (**) | |-->Monitor "<default monitor>"
[ 1687.350] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[ 1687.350] (**) | |-->Device "Intel"
[ 1687.350] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 1687.350] (==) Automatically adding devices
[ 1687.350] (==) Automatically enabling devices
[ 1687.350] (==) Automatically adding GPU devices
[ 1687.350] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 1687.350] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 1687.351] Entry deleted from font path.
[ 1687.351] (==) 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
[ 1687.351] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 1687.351] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 1687.351] (II) Loader magic: 0x55ed25733e00
[ 1687.351] (II) Module ABI versions:
[ 1687.351] X.Org ANSI C Emulation: 0.4
[ 1687.351] X.Org Video Driver: 23.0
[ 1687.351] X.Org XInput driver : 24.1
[ 1687.351] X.Org Server Extension : 10.0
[ 1687.353] (++) using VT number 7
[ 1687.353] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[ 1687.353] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 1687.360] (--) PCI:*(0:0:2:0) 8086:0106:1025:0511 rev 9, Mem @ 0xc0000000/4194304, 0xb0000000/268435456, I/O @ 0x00002000/64, BIOS @ 0x????????/131072
[ 1687.360] (II) LoadModule: "glx"
[ 1687.360] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 1687.362] (II) Module glx: vendor="X.Org Foundation"
[ 1687.362] compiled for 1.19.2, module version = 1.0.0
[ 1687.363] ABI class: X.Org Server Extension, version 10.0
[ 1687.363] (II) LoadModule: "intel"
[ 1687.363] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 1687.363] (II) Module intel: vendor="X.Org Foundation"
[ 1687.363] compiled for 1.19.0, module version = 2.99.917
[ 1687.363] Module class: X.Org Video Driver
[ 1687.363] ABI class: X.Org Video Driver, version 23.0
[ 1687.363] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
[ 1687.364] (II) intel: Driver for Intel(R) HD Graphics
[ 1687.364] (II) intel: Driver for Intel(R) Iris(TM) Graphics
[ 1687.364] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics
[ 1687.379] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20160919
[ 1687.379] (II) intel(0): SNA compiled: xserver-xorg-video-intel 2:2.99.917+git20161206-1 (Timo Aaltonen <tjaalton@debian.org>)
[ 1687.379] (II) intel(0): SNA compiled for use with valgrind
[ 1687.379] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics 2000
[ 1687.379] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2; using a maximum of 2 threads
[ 1687.379] (II) intel(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 1687.380] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[ 1687.380] (==) intel(0): RGB weight 888
[ 1687.380] (==) intel(0): Default visual is TrueColor
[ 1687.380] (II) intel(0): Output LVDS1 has no monitor section
[ 1687.381] (**) intel(0): Found backlight control interface intel_backlight (type 'raw') for output LVDS1
[ 1687.381] (II) intel(0): Enabled output LVDS1
[ 1687.381] (II) intel(0): Output VGA1 has no monitor section
[ 1687.381] (II) intel(0): Enabled output VGA1
[ 1687.381] (II) intel(0): Output HDMI1 has no monitor section
[ 1687.381] (II) intel(0): Enabled output HDMI1
[ 1687.381] (II) intel(0): Output DP1 has no monitor section
[ 1687.381] (II) intel(0): Enabled output DP1
[ 1687.381] (--) intel(0): Using a maximum size of 256x256 for hardware cursors
[ 1687.382] (II) intel(0): Output VIRTUAL1 has no monitor section
[ 1687.382] (II) intel(0): Enabled output VIRTUAL1
[ 1687.382] (--) intel(0): Output LVDS1 using initial mode 1366x768 on pipe 0
[ 1687.382] (==) intel(0): TearFree disabled
[ 1687.382] (==) intel(0): Using gamma correction (1.0, 1.0, 1.0)
[ 1687.382] (==) intel(0): DPI set to (96, 96)
[ 1687.382] (II) Loading sub module "dri3"
[ 1687.382] (II) LoadModule: "dri3"
[ 1687.382] (II) Module "dri3" already built-in
[ 1687.382] (II) Loading sub module "dri2"
[ 1687.382] (II) LoadModule: "dri2"
[ 1687.382] (II) Module "dri2" already built-in
[ 1687.382] (II) Loading sub module "present"
[ 1687.382] (II) LoadModule: "present"
[ 1687.382] (II) Module "present" already built-in
[ 1687.382] (==) Depth 24 pixmap format is 32 bpp
[ 1687.382] (II) intel(0): SNA initialized with Sandybridge (gen6, gt1) backend
[ 1687.383] (==) intel(0): Backing store enabled
[ 1687.383] (==) intel(0): Silken mouse enabled
[ 1687.383] (II) intel(0): HW Cursor enabled
[ 1687.383] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 1687.383] (==) intel(0): DPMS enabled
[ 1687.383] (==) intel(0): Display hotplug detection enabled
[ 1687.383] (II) intel(0): [DRI2] Setup complete
[ 1687.383] (II) intel(0): [DRI2] DRI driver: i965
[ 1687.383] (II) intel(0): [DRI2] VDPAU driver: va_gl
[ 1687.383] (II) intel(0): direct rendering: DRI2 enabled
[ 1687.383] (II) intel(0): hardware support for Present enabled
[ 1687.383] (--) RandR disabled
[ 1687.390] (II) SELinux: Disabled on system
[ 1687.413] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 1687.413] (II) AIGLX: enabled GLX_ARB_create_context
[ 1687.413] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 1687.413] (II) AIGLX: enabled GLX_EXT_create_context_es{,2}_profile
[ 1687.413] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 1687.413] (II) AIGLX: enabled GLX_SGI_swap_control
[ 1687.413] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[ 1687.413] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[ 1687.413] (II) AIGLX: enabled GLX_EXT_fbconfig_packed_float
[ 1687.413] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 1687.413] (II) AIGLX: enabled GLX_ARB_create_context_robustness
[ 1687.413] (II) AIGLX: Loaded and initialized i965
[ 1687.413] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 1687.416] (II) intel(0): switch to mode 1366x768@60.0 on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
[ 1687.423] (II) intel(0): Setting screen physical size to 361 x 203
[ 1687.472] (II) config/udev: Adding input device Power Button (/dev/input/event8)
[ 1687.472] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[ 1687.472] (II) LoadModule: "libinput"
[ 1687.472] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[ 1687.474] (II) Module libinput: vendor="X.Org Foundation"
[ 1687.474] compiled for 1.19.0, module version = 0.23.0
[ 1687.474] Module class: X.Org XInput Driver
[ 1687.474] ABI class: X.Org XInput driver, version 24.1
[ 1687.474] (II) Using input driver 'libinput' for 'Power Button'
[ 1687.474] (**) Power Button: always reports core events
[ 1687.474] (**) Option "Device" "/dev/input/event8"
[ 1687.474] (**) Option "_source" "server/udev"
[ 1687.474] (II) input device 'Power Button', /dev/input/event8 is tagged by udev as: Keyboard
[ 1687.474] (II) input device 'Power Button', /dev/input/event8 is a keyboard
[ 1687.488] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input9/event8"
[ 1687.488] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 1687.488] (**) Option "xkb_model" "pc105"
[ 1687.488] (**) Option "xkb_layout" "us"
[ 1687.488] (II) input device 'Power Button', /dev/input/event8 is tagged by udev as: Keyboard
[ 1687.488] (II) input device 'Power Button', /dev/input/event8 is a keyboard
[ 1687.489] (II) config/udev: Adding input device Video Bus (/dev/input/event9)
[ 1687.489] (**) Video Bus: Applying InputClass "libinput keyboard catchall"
[ 1687.489] (II) Using input driver 'libinput' for 'Video Bus'
[ 1687.489] (**) Video Bus: always reports core events
[ 1687.489] (**) Option "Device" "/dev/input/event9"
[ 1687.489] (**) Option "_source" "server/udev"
[ 1687.489] (II) input device 'Video Bus', /dev/input/event9 is tagged by udev as: Keyboard
[ 1687.489] (II) input device 'Video Bus', /dev/input/event9 is a keyboard
[ 1687.520] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input10/event9"
[ 1687.520] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[ 1687.520] (**) Option "xkb_model" "pc105"
[ 1687.520] (**) Option "xkb_layout" "us"
[ 1687.521] (II) input device 'Video Bus', /dev/input/event9 is tagged by udev as: Keyboard
[ 1687.521] (II) input device 'Video Bus', /dev/input/event9 is a keyboard
[ 1687.522] (II) config/udev: Adding input device Power Button (/dev/input/event5)
[ 1687.522] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[ 1687.522] (II) Using input driver 'libinput' for 'Power Button'
[ 1687.522] (**) Power Button: always reports core events
[ 1687.522] (**) Option "Device" "/dev/input/event5"
[ 1687.522] (**) Option "_source" "server/udev"
[ 1687.522] (II) input device 'Power Button', /dev/input/event5 is tagged by udev as: Keyboard
[ 1687.522] (II) input device 'Power Button', /dev/input/event5 is a keyboard
[ 1687.536] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:01/PNP0C0C:00/input/input6/event5"
[ 1687.536] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
[ 1687.536] (**) Option "xkb_model" "pc105"
[ 1687.536] (**) Option "xkb_layout" "us"
[ 1687.537] (II) input device 'Power Button', /dev/input/event5 is tagged by udev as: Keyboard
[ 1687.537] (II) input device 'Power Button', /dev/input/event5 is a keyboard
[ 1687.537] (II) config/udev: Adding input device Lid Switch (/dev/input/event6)
[ 1687.537] (II) No input driver specified, ignoring this device.
[ 1687.538] (II) This device may have been added with another device file.
[ 1687.538] (II) config/udev: Adding input device Sleep Button (/dev/input/event7)
[ 1687.538] (**) Sleep Button: Applying InputClass "libinput keyboard catchall"
[ 1687.538] (II) Using input driver 'libinput' for 'Sleep Button'
[ 1687.538] (**) Sleep Button: always reports core events
[ 1687.538] (**) Option "Device" "/dev/input/event7"
[ 1687.538] (**) Option "_source" "server/udev"
[ 1687.539] (II) input device 'Sleep Button', /dev/input/event7 is tagged by udev as: Keyboard
[ 1687.539] (II) input device 'Sleep Button', /dev/input/event7 is a keyboard
[ 1687.552] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:01/PNP0C0E:00/input/input8/event7"
[ 1687.552] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 9)
[ 1687.552] (**) Option "xkb_model" "pc105"
[ 1687.552] (**) Option "xkb_layout" "us"
[ 1687.553] (II) input device 'Sleep Button', /dev/input/event7 is tagged by udev as: Keyboard
[ 1687.553] (II) input device 'Sleep Button', /dev/input/event7 is a keyboard
[ 1687.554] (II) config/udev: Adding input device 1.3M HD WebCam (/dev/input/event16)
[ 1687.554] (**) 1.3M HD WebCam: Applying InputClass "libinput keyboard catchall"
[ 1687.554] (II) Using input driver 'libinput' for '1.3M HD WebCam'
[ 1687.554] (**) 1.3M HD WebCam: always reports core events
[ 1687.554] (**) Option "Device" "/dev/input/event16"
[ 1687.554] (**) Option "_source" "server/udev"
[ 1687.555] (II) input device '1.3M HD WebCam', /dev/input/event16 is tagged by udev as: Keyboard
[ 1687.555] (II) input device '1.3M HD WebCam', /dev/input/event16 is a keyboard
[ 1687.584] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input17/event16"
[ 1687.584] (II) XINPUT: Adding extended input device "1.3M HD WebCam" (type: KEYBOARD, id 10)
[ 1687.584] (**) Option "xkb_model" "pc105"
[ 1687.584] (**) Option "xkb_layout" "us"
[ 1687.585] (II) input device '1.3M HD WebCam', /dev/input/event16 is tagged by udev as: Keyboard
[ 1687.585] (II) input device '1.3M HD WebCam', /dev/input/event16 is a keyboard
[ 1687.586] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event11)
[ 1687.586] (II) No input driver specified, ignoring this device.
[ 1687.586] (II) This device may have been added with another device file.
[ 1687.586] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event12)
[ 1687.586] (II) No input driver specified, ignoring this device.
[ 1687.586] (II) This device may have been added with another device file.
[ 1687.587] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event13)
[ 1687.587] (II) No input driver specified, ignoring this device.
[ 1687.587] (II) This device may have been added with another device file.
[ 1687.587] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event14)
[ 1687.587] (II) No input driver specified, ignoring this device.
[ 1687.587] (II) This device may have been added with another device file.
[ 1687.588] (II) config/udev: Adding input device Microsoft Microsoft® Nano Transceiver v2.0 (/dev/input/event1)
[ 1687.588] (**) Microsoft Microsoft® Nano Transceiver v2.0: Applying InputClass "libinput keyboard catchall"
[ 1687.588] (II) Using input driver 'libinput' for 'Microsoft Microsoft® Nano Transceiver v2.0'
[ 1687.588] (**) Microsoft Microsoft® Nano Transceiver v2.0: always reports core events
[ 1687.588] (**) Option "Device" "/dev/input/event1"
[ 1687.588] (**) Option "_source" "server/udev"
[ 1687.589] (II) input device 'Microsoft Microsoft® Nano Transceiver v2.0', /dev/input/event1 is tagged by udev as: Keyboard
[ 1687.589] (II) input device 'Microsoft Microsoft® Nano Transceiver v2.0', /dev/input/event1 is a keyboard
[ 1687.608] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.4/4-1.4:1.0/0003:045E:0745.0001/input/input3/event1"
[ 1687.608] (II) XINPUT: Adding extended input device "Microsoft Microsoft® Nano Transceiver v2.0" (type: KEYBOARD, id 11)
[ 1687.608] (**) Option "xkb_model" "pc105"
[ 1687.608] (**) Option "xkb_layout" "us"
[ 1687.609] (II) input device 'Microsoft Microsoft® Nano Transceiver v2.0', /dev/input/event1 is tagged by udev as: Keyboard
[ 1687.609] (II) input device 'Microsoft Microsoft® Nano Transceiver v2.0', /dev/input/event1 is a keyboard
[ 1687.610] (II) config/udev: Adding input device Microsoft Microsoft® Nano Transceiver v2.0 (/dev/input/event2)
[ 1687.610] (**) Microsoft Microsoft® Nano Transceiver v2.0: Applying InputClass "libinput pointer catchall"
[ 1687.610] (**) Microsoft Microsoft® Nano Transceiver v2.0: Applying InputClass "libinput keyboard catchall"
[ 1687.610] (II) Using input driver 'libinput' for 'Microsoft Microsoft® Nano Transceiver v2.0'
[ 1687.611] (**) Microsoft Microsoft® Nano Transceiver v2.0: always reports core events
[ 1687.611] (**) Option "Device" "/dev/input/event2"
[ 1687.611] (**) Option "_source" "server/udev"
[ 1687.611] (II) input device 'Microsoft Microsoft® Nano Transceiver v2.0', /dev/input/event2 is tagged by udev as: Keyboard Mouse
[ 1687.611] (II) Device 'Microsoft Microsoft® Nano Transceiver v2.0' set to 1000 DPI
[ 1687.611] (II) input device 'Microsoft Microsoft® Nano Transceiver v2.0', /dev/input/event2 is a pointer caps
[ 1687.611] (II) input device 'Microsoft Microsoft® Nano Transceiver v2.0', /dev/input/event2 is a keyboard
[ 1687.624] (II) libinput: Microsoft Microsoft® Nano Transceiver v2.0: needs a virtual subdevice
[ 1687.624] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.4/4-1.4:1.1/0003:045E:0745.0002/input/input4/event2"
[ 1687.624] (II) XINPUT: Adding extended input device "Microsoft Microsoft® Nano Transceiver v2.0" (type: MOUSE, id 12)
[ 1687.625] (**) Option "AccelerationScheme" "none"
[ 1687.625] (**) Microsoft Microsoft® Nano Transceiver v2.0: (accel) selected scheme none/0
[ 1687.625] (**) Microsoft Microsoft® Nano Transceiver v2.0: (accel) acceleration factor: 2.000
[ 1687.625] (**) Microsoft Microsoft® Nano Transceiver v2.0: (accel) acceleration threshold: 4
[ 1687.625] (II) input device 'Microsoft Microsoft® Nano Transceiver v2.0', /dev/input/event2 is tagged by udev as: Keyboard Mouse
[ 1687.626] (II) Device 'Microsoft Microsoft® Nano Transceiver v2.0' set to 1000 DPI
[ 1687.626] (II) input device 'Microsoft Microsoft® Nano Transceiver v2.0', /dev/input/event2 is a pointer caps
[ 1687.626] (II) input device 'Microsoft Microsoft® Nano Transceiver v2.0', /dev/input/event2 is a keyboard
[ 1687.626] (II) config/udev: Adding input device Microsoft Microsoft® Nano Transceiver v2.0 (/dev/input/mouse0)
[ 1687.626] (II) No input driver specified, ignoring this device.
[ 1687.626] (II) This device may have been added with another device file.
[ 1687.627] (II) config/udev: Adding input device Microsoft Microsoft® Nano Transceiver v2.0 (/dev/input/event3)
[ 1687.627] (**) Microsoft Microsoft® Nano Transceiver v2.0: Applying InputClass "libinput keyboard catchall"
[ 1687.627] (II) Using input driver 'libinput' for 'Microsoft Microsoft® Nano Transceiver v2.0'
[ 1687.627] (**) Microsoft Microsoft® Nano Transceiver v2.0: always reports core events
[ 1687.627] (**) Option "Device" "/dev/input/event3"
[ 1687.627] (**) Option "_source" "server/udev"
[ 1687.628] (II) input device 'Microsoft Microsoft® Nano Transceiver v2.0', /dev/input/event3 is tagged by udev as: Keyboard
[ 1687.628] (II) input device 'Microsoft Microsoft® Nano Transceiver v2.0', /dev/input/event3 is a keyboard
[ 1687.652] (II) libinput: Microsoft Microsoft® Nano Transceiver v2.0: needs a virtual subdevice
[ 1687.652] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.4/4-1.4:1.2/0003:045E:0745.0003/input/input5/event3"
[ 1687.652] (II) XINPUT: Adding extended input device "Microsoft Microsoft® Nano Transceiver v2.0" (type: MOUSE, id 13)
[ 1687.652] (**) Option "AccelerationScheme" "none"
[ 1687.652] (**) Microsoft Microsoft® Nano Transceiver v2.0: (accel) selected scheme none/0
[ 1687.652] (**) Microsoft Microsoft® Nano Transceiver v2.0: (accel) acceleration factor: 2.000
[ 1687.652] (**) Microsoft Microsoft® Nano Transceiver v2.0: (accel) acceleration threshold: 4
[ 1687.653] (II) input device 'Microsoft Microsoft® Nano Transceiver v2.0', /dev/input/event3 is tagged by udev as: Keyboard
[ 1687.653] (II) input device 'Microsoft Microsoft® Nano Transceiver v2.0', /dev/input/event3 is a keyboard
[ 1687.654] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 1687.654] (**) AT Translated Set 2 keyboard: Applying InputClass "libinput keyboard catchall"
[ 1687.654] (II) Using input driver 'libinput' for 'AT Translated Set 2 keyboard'
[ 1687.654] (**) AT Translated Set 2 keyboard: always reports core events
[ 1687.654] (**) Option "Device" "/dev/input/event0"
[ 1687.654] (**) Option "_source" "server/udev"
[ 1687.654] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is tagged by udev as: Keyboard
[ 1687.655] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is a keyboard
[ 1687.668] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 1687.668] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 14)
[ 1687.668] (**) Option "xkb_model" "pc105"
[ 1687.668] (**) Option "xkb_layout" "us"
[ 1687.669] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is tagged by udev as: Keyboard
[ 1687.669] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is a keyboard
[ 1687.669] (II) config/udev: Adding input device ETPS/2 Elantech Touchpad (/dev/input/event4)
[ 1687.669] (**) ETPS/2 Elantech Touchpad: Applying InputClass "libinput touchpad catchall"
[ 1687.670] (II) Using input driver 'libinput' for 'ETPS/2 Elantech Touchpad'
[ 1687.670] (**) ETPS/2 Elantech Touchpad: always reports core events
[ 1687.670] (**) Option "Device" "/dev/input/event4"
[ 1687.670] (**) Option "_source" "server/udev"
[ 1687.670] (II) input device 'ETPS/2 Elantech Touchpad', /dev/input/event4 is tagged by udev as: Touchpad
[ 1687.670] (II) input device 'ETPS/2 Elantech Touchpad', /dev/input/event4 is a touchpad
[ 1687.700] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input2/event4"
[ 1687.700] (II) XINPUT: Adding extended input device "ETPS/2 Elantech Touchpad" (type: TOUCHPAD, id 15)
[ 1687.700] (**) Option "AccelerationScheme" "none"
[ 1687.701] (**) ETPS/2 Elantech Touchpad: (accel) selected scheme none/0
[ 1687.701] (**) ETPS/2 Elantech Touchpad: (accel) acceleration factor: 2.000
[ 1687.701] (**) ETPS/2 Elantech Touchpad: (accel) acceleration threshold: 4
[ 1687.701] (II) input device 'ETPS/2 Elantech Touchpad', /dev/input/event4 is tagged by udev as: Touchpad
[ 1687.701] (II) input device 'ETPS/2 Elantech Touchpad', /dev/input/event4 is a touchpad
[ 1687.702] (II) config/udev: Adding input device ETPS/2 Elantech Touchpad (/dev/input/mouse1)
[ 1687.702] (II) No input driver specified, ignoring this device.
[ 1687.702] (II) This device may have been added with another device file.
[ 1687.702] (II) config/udev: Adding input device PC Speaker (/dev/input/event10)
[ 1687.702] (II) No input driver specified, ignoring this device.
[ 1687.702] (II) This device may have been added with another device file.
[ 1687.703] (II) config/udev: Adding input device Acer WMI hotkeys (/dev/input/event15)
[ 1687.703] (**) Acer WMI hotkeys: Applying InputClass "libinput keyboard catchall"
[ 1687.703] (II) Using input driver 'libinput' for 'Acer WMI hotkeys'
[ 1687.703] (**) Acer WMI hotkeys: always reports core events
[ 1687.703] (**) Option "Device" "/dev/input/event15"
[ 1687.703] (**) Option "_source" "server/udev"
[ 1687.704] (II) input device 'Acer WMI hotkeys', /dev/input/event15 is tagged by udev as: Keyboard
[ 1687.704] (II) input device 'Acer WMI hotkeys', /dev/input/event15 is a keyboard
[ 1687.744] (**) Option "config_info" "udev:/sys/devices/virtual/input/input16/event15"
[ 1687.744] (II) XINPUT: Adding extended input device "Acer WMI hotkeys" (type: KEYBOARD, id 16)
[ 1687.744] (**) Option "xkb_model" "pc105"
[ 1687.744] (**) Option "xkb_layout" "us"
[ 1687.745] (II) input device 'Acer WMI hotkeys', /dev/input/event15 is tagged by udev as: Keyboard
[ 1687.745] (II) input device 'Acer WMI hotkeys', /dev/input/event15 is a keyboard
[ 1687.757] (**) Microsoft Microsoft® Nano Transceiver v2.0: Applying InputClass "libinput pointer catchall"
[ 1687.757] (**) Microsoft Microsoft® Nano Transceiver v2.0: Applying InputClass "libinput keyboard catchall"
[ 1687.757] (II) Using input driver 'libinput' for 'Microsoft Microsoft® Nano Transceiver v2.0'
[ 1687.757] (**) Microsoft Microsoft® Nano Transceiver v2.0: always reports core events
[ 1687.757] (**) Option "Device" "/dev/input/event2"
[ 1687.757] (**) Option "_source" "_driver/libinput"
[ 1687.757] (II) libinput: Microsoft Microsoft® Nano Transceiver v2.0: is a virtual subdevice
[ 1687.757] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.4/4-1.4:1.1/0003:045E:0745.0002/input/input4/event2"
[ 1687.757] (II) XINPUT: Adding extended input device "Microsoft Microsoft® Nano Transceiver v2.0" (type: KEYBOARD, id 17)
[ 1687.757] (**) Option "xkb_model" "pc105"
[ 1687.757] (**) Option "xkb_layout" "us"
[ 1687.758] (**) Microsoft Microsoft® Nano Transceiver v2.0: Applying InputClass "libinput keyboard catchall"
[ 1687.758] (II) Using input driver 'libinput' for 'Microsoft Microsoft® Nano Transceiver v2.0'
[ 1687.758] (**) Microsoft Microsoft® Nano Transceiver v2.0: always reports core events
[ 1687.758] (**) Option "Device" "/dev/input/event3"
[ 1687.758] (**) Option "_source" "_driver/libinput"
[ 1687.758] (II) libinput: Microsoft Microsoft® Nano Transceiver v2.0: is a virtual subdevice
[ 1687.758] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.4/4-1.4:1.2/0003:045E:0745.0003/input/input5/event3"
[ 1687.758] (II) XINPUT: Adding extended input device "Microsoft Microsoft® Nano Transceiver v2.0" (type: KEYBOARD, id 18)
[ 1687.758] (**) Option "xkb_model" "pc105"
[ 1687.758] (**) Option "xkb_layout" "us"
[ 1689.705] (II) UnloadModule: "libinput"
[ 1689.705] (II) UnloadModule: "libinput"
[ 1689.705] (II) UnloadModule: "libinput"
[ 1689.705] (II) UnloadModule: "libinput"
[ 1689.705] (II) UnloadModule: "libinput"
[ 1689.705] (II) UnloadModule: "libinput"
[ 1689.706] (II) UnloadModule: "libinput"
[ 1689.706] (II) UnloadModule: "libinput"
[ 1689.706] (II) UnloadModule: "libinput"
[ 1689.706] (II) UnloadModule: "libinput"
[ 1689.706] (II) UnloadModule: "libinput"
[ 1689.706] (II) UnloadModule: "libinput"
[ 1689.706] (II) UnloadModule: "libinput"
[ 1689.777] (II) Server terminated successfully (0). Closing log file.ETA: And I have no idea where to find the display manager log. Since this is XFCE, I presume it's LightDM? Where does that put any logs?
#133 Re: Hardware & System Configuration » Ascii kernel update borks laptop » 2021-07-07 22:47:08
Then do:
apt install -fPlease post the output of this.
It will have information needed to find out what is going on.Best,
A.
It thinks the version '14' kernel is obsolete, which I guess it is, but says nothing about the current version '15' kernel. I purged the '16' version that cause the problems, of course. When I ran apt-get update, there was no return of that kernel either. Odd, I would have expected it to be listed again. I learned about the 'hold' option, but have not used it yet.
root@nautilus:~# apt install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
linux-image-4.9.0-14-amd64
Use 'apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
#134 Re: Devuan » Cinnamon desktop will be unmaintained after bullseye » 2021-07-05 22:39:48
Just use Fluxbox.....
That's a plain windowing manager, right? I've heard of people running with only a windowing manager wondered how difficult it might be to setup Devuan to do that. Is there a 'package' to install? Or do you have to manually tweak things?
#135 Hardware & System Configuration » Ascii kernel update borks laptop » 2021-07-05 22:38:37
- Micronaut
- Replies: 21
Ascii running on a Gateway NV57H63u (Yep, just about a decade old now) somehow could not reach the desktop after updating to the latest kernel. (linux-image-4.9.0-16-amd64{a}) It would boot and allow login, but after that it would hang indefinitely without showing the desktop. Using the 'advanced options' to boot to the previous kernel, I purged the 'update' and it now boots fine again to that previous kernel. (linux-image-4.9.0-15-amd64{a})
Weirdly, when I told aptitude to purge that '16' version of the kernel, it complained that there were unmet dependencies. That might explain the hang, but is a bit frightening. A kernel package was not constructed properly? Ouch...
Has there been any other notice of this problem? I hope my laptop is not so obscure that no one else has seen this. How can I tell when it's safe to update the kernel again? Will that '16' package be amended? Or will there just be a '17' to fix any problems? In the meantime, is there a way to get other updates while not allowing the kernel to update? Isn't there a 'hold' command for the apt packaging system?
#136 Re: Desktop and Multimedia » Hard freeze on Cinnamon desktop » 2021-05-07 22:44:44
I sent the links to dropbox copies of those logs in private email. Did you get it?
#137 Re: Desktop and Multimedia » Hard freeze on Cinnamon desktop » 2021-04-27 19:17:34
Gack... I'd hate to have to go back to the old version. It's only getting patches until next summer, isn't it?
#138 Re: Desktop and Multimedia » Hard freeze on Cinnamon desktop » 2021-04-27 02:08:00
It happened again. Ctrl-Alt-Backspace and Ctrl-Alt-F1/F2/etc had no effect. This time, the pointer was moving across the desktop when it froze, too. Not on a menu. So my guess that something in the menuing system was the cause seems to be wrong. It's got to be deep in the video driver stack.
One thing that was different this time, thought, is that I had just downloaded updates and a couple of them were related to X. Dunno what the fixes were supposed to be. Maybe someone with better knowledge of where to look up recent patches can check on that. Since I had not rebooted/restarted X, that is probably a potential source of problems.
So, I did restart it after having to use the hard power switch, and fiddled with it a bit. Had also just installed Chromium, which does not complain about the missing keyring with Cinnamon, since the keyring is present. 
It was nice to use another open source browser for a bit.
Since this happened yesterday, I'm sure some of the logs will be archived and new ones started when I boot it again. Which logs shall I post to pastebin for an analysis?
#139 Re: Desktop and Multimedia » Hard freeze on Cinnamon desktop » 2021-04-07 23:23:34
Yes, I used the remove option rather than create the directory. No noticeable difference yet, but it took hours of continuous use for the bug to hit the first time. It might be something like the Windows problem that occurs when you Alt-tab between windows many, many, many times. (Like when copying things from a web browser to a local editor.) Eventually, the system gets confused and starts scrambling the windows. This has been a thing with MS Windows all the way back to 95/98 days when it was still a shell on MS-DOS. It might take another long session to see for sure if this fixes the problem.
I also tried removing the intel driver on a different laptop. Granted, this one hasn't had the bug, but I thought it might have better performance using the modesetting driver if that one is updated more often. Instead, it didn't even boot to the desktop! It stopped at the command prompt and I had to re-install the intel driver to get the desktop back. Here's the thing -- it is also using the i915 driver??? But the kernel driver is apparently not the same thing as the video driver. It's a Gateway laptop from ~2011, five years older than the HP. And it's running Devuan Ascii with XFCE. The modesetting driver apparently doesn't recognize the video subsystem.
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller
Kernel driver in use: i915
Kernel modules: i915
Which logs shall I put on pastebin?
#140 Re: Desktop and Multimedia » Hard freeze on Cinnamon desktop » 2021-04-07 01:46:41
Yes, the driver listed is i915. Besides video, that Atom processor is acting as subsystem for most of the motherboard, PCI controller, audio, USB and various other functions seem to have been assigned to at least an Atom processor. I wonder how many there are and whether they are embedded in the CPU or the motherboard chip-set?
The logs aren't very large yet, since this is such a new system, but I really don't know what to look for. Grep for "Warning"? Or "Error"? Or something else?
#141 Re: Desktop and Multimedia » Hard freeze on Cinnamon desktop » 2021-04-05 22:50:50
There is no xorg.conf.d directory under X11, though at least the X11 directory exists! Have the workings of X changed in the latest release, or should I create that directory? I guess I could just go ahead and use the uninstall.
Yes, the video drivers seems to be the problem. When I saw something like this on a desktop with a nVidia-based video card using Devuan and XFCE a couple years ago, I gave up on Devuan and tried MX Linux. And it had the same problem... 
But when I installed the proprietary nVidia driver in MX, the problems went away. Now, this problem has something to do with Intel "HD Graphics" rather than an nVidia card, and the driver is apparently already the Intel driver? They published the source and Linux distros can just build it into their default config? So I'm at a loss how to 'fix' the problem this time. All I can do for now is try disabling the Intel part of X, I guess.
#142 Re: Hardware & System Configuration » Devuan and OpenVPN » 2021-04-05 19:19:12
OK, I can get the OpenVPN client to connect with "openvpn --config [filename]" where [filename] is the Windows config file with a little bit of editing to change the client key name. Gotta have different keys for different clients. It works, but I'm stuck with an open terminal window while it's running. How can I transfer the settings in the config file to a Network Manager profile that will just add a line in the Network Connections panel?
#143 Re: Desktop and Multimedia » Hard freeze on Cinnamon desktop » 2021-04-05 19:16:31
I'll have to try Ctrl-Alt-F1 if it happens again. I hadn't heard of that hot-key combination. I think it was Ctrl-Alt-Backspace that forces a desktop environment to quit? I didn't think to try that at the time, but will remember it next time along with Ctrl-Alt-F1....
#144 Re: Desktop and Multimedia » Hard freeze on Cinnamon desktop » 2021-04-05 19:13:19
lspci -k | grep -iA2 'vga\|display\|3d'
00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0e)
Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series Graphics & Display
Apparently the Atom architecture has been embedded in certain Pentium lines to serve as video controller...
aptitude search microcode
i A amd64-microcode - Processor microcode firmware for AMD CPUs
i A intel-microcode - Processor microcode firmware for Intel CPU
p microcode.ctl - Intel IA32/IA64 CPU Microcode Utility
Now why would both AMD and Intel microcode be installed?
Also, how would I go about removing the xserver-xorg-video-intel part of X?
And how would I put it BACK if that turns out to be worse?
#145 Desktop and Multimedia » Hard freeze on Cinnamon desktop » 2021-04-05 00:29:17
- Micronaut
- Replies: 20
Well, I had thought the problem was with XFCE, but now I'm seeing the exact same problem I had on other systems running Ascii and XFCE, but this time with a newly installed Beowulf with Cinnamon on an HP 15-f272wm. When clicking on a menu, something goes off the rails and freezes the desktop solid. It's not predictable, the system might work for hours with no apparent problems. But when it hits, it's permanent. There is no option but the hard power switch. When Gkrellm was visible on the other systems at the moment of freezing, I could see the process/thread count skyrocket. So there is something running out of control, probably in the menuing system, when this happens. In this case my running Gkrellm was covered so I can't say for certain. But now I know it's not just XFCE. It's apparently deeper in the system than the desktop.
This is more than just a bit frustrating. Windows 10 will soon (within 2 years) be the only thing available in the 'consumer' field, and it is not usable. If Linux is going to become buggy as hell, I'm either going to have to run obsolete and dangerously vulnerable versions of Windows, or I'm going to be unable to use computers.
#146 Re: Hardware & System Configuration » Devuan and OpenVPN » 2021-04-05 00:19:19
But sometimes the GUI helps you figure out what is going on when you don't understand what you are doing. The wiki only tells you how to run it manually, and suggests you use the GUI without explaining how to do that. Presumably, most of us want to run a VPN without having to have an open terminal on the taskbar all the time, so you would think they would be more verbose explaining about the Network Manager route.
Anyway, I finally realized that Network Manager creates a VPN connection like any other, by 'adding' with the "+" button. There isn't an obvious 'VPN' addition to the main window, only further down in the menus. The names in the GUI don't fully correspond to the names in the text config, so I had to guess about some things. But even after finishing an OpenVPN connection and clicking 'save' there still isn't a config file in the openvpn directory, so I still don't know where the data is and cannot yet fix any mistakes directly. So the GUI wasn't much help this time. Since I'm getting tired and annoyed today, I guess I'll have to work on it some more tomorrow.
#147 Hardware & System Configuration » Devuan and OpenVPN » 2021-04-04 21:16:45
- Micronaut
- Replies: 4
In a push to finally "get some things done" that I've been wanting to do for ages, I recently created a 'private VPN' in the AWS cloud using OpenVPN according to this tutorial. I did get it working, and it's now usable with my Windows desktop system. The directions explain how to install the Windows version of the OpenVPN client, but not the Linux version. Since I also recently converted a laptop from Windows to Linux (per my post in the Installation forum), I'd like to get that also able to use this personal VPN. Installing OpenVPN, Network-Manager-OpenVPN, and Network-Manager-OpenVPN-Gnome as the Debian Wiki suggests, I can't find anything to configure. There is a blank directly in /etc now, and no hint how to proceed. Can someone tell me how you configure the OpenVPN client in a Devuan Beowulf install running Cinnamon?
#148 Re: Installation » Devuan and Secure Boot » 2021-04-04 21:00:15
The system is an HP 15-f272wm, just about 5 years old. I got it second-hand, didn't actually buy it myself. It's got a 4-core Pentium N3540 CPU and an Atom Z36xxx GPU. I didn't even know it had a GPU until I installed Devuan with Cinnamon and the System Info panel told me. It was originally 4 GB of RAM, but I upgraded it to 8 GB trying to improve the performance of Wind'ohs.
Poking around in the BIOS again, I find there is a setting specifically for secure boot, which I had disabled. But it still wouldn't boot until I enabled legacy support, so I guess I chose MBR when I installed. The menus can be confusing, and I just wanted to get it running something else. Win 10 is a nightmare, spending more time 'updating' itself than I spend actually using the system. And most of the time I had spent using the system was struggling with Win 10 settings and quirks. I also enabled virtualization, which is disabled by default for some reason and I kept seeing error messages about kvm being disabled by BIOS at every boot.
Since everything 'just works' now I am reluctant to re-install just to get the UEFI/GPT. Are there any huge advantages to it? If I need to re-install at some future point, I'll remember to deliberately try GPT.
All I am wondering now is how to get OpenVPN working, so I will post a new thread in the system config forum about that.
#149 Installation » Devuan and Secure Boot » 2021-04-03 23:16:58
- Micronaut
- Replies: 4
After literally years of trying to accommodate a Windows 10 install on a second hand laptop, I finally took the plunge and purged the beast, replacing it with Devuan Beowulf. In order to do that, I had to enable 'legacy' booting, as it would not recognize anything but its originally imprinted Win 10 otherwise. So now I've got a system new enough to have UEFI, but still booting from a disk using ancient MBR.
Now I am wondering, as I tweak my new and actually usable laptop, do Debian/Devuan have 'keys' to be allowed to use this 'secure boot' feature? Or does it have to always be disabled to install Linux on a system that has it? Is it possible to use UEFI/GFT without secure boot? Would I have to dig further into the BIOS and figure out how to remove the existing keys to allow that?
#150 Re: Installation » I just installed Devuan 3.1.0 Beowulf and it's cool » 2021-03-15 02:08:48
Merely disabling wicd with this handy utility -- glad I chose sysv for my init system! -- does not work. I get error messages about the GUI not working until the daemon is restarted. So I just used 'aptitude remove wicd'. Bluetooth is OK with being disabled this way.
Googling around, I learned that putting "acpi_enforce_resources=lax" on my GRUB_CMDLINE_LINUX_DEFAULT= line allows more sensors to be seen. The sensor actually named cpu fan is still not showing any data, but six others are now visible to Gkrellm and three of them show actual live data. Now if I could just figure out which is which...
Board footer
