Thanks for joining this lab session Head_on_a_Stick. As advised:
Head_on_a_Stick wrote:peek wrote:Picking .... linux-image-4.18.0-0.bpo.1-amd64
You should install the kernel metapackage (the one without any version numbers) to make sure it is kept updated, running an outdated kernel is unwise.
I've installed the "linux-image-amd64" package which is currently still keeping the unit on 4.18.0-0.bpo.1-amd64
Head_on_a_Stick wrote:peek wrote:Code: Select all
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-2.fw for module r8169
The backported firmware-realtek package will remove those messages.
Unfortunately I cannot find any "firmware-realtek" package in the stretch-backports repository ... There is a "firmware-linux-free" package though, which I installed.
Head_on_a_Stick wrote:peek wrote:Code: Select all
[ 7.398073] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
[ 7.399067] i915 0000:00:02.0: firmware: failed to load i915/glk_dmc_ver1_04.bin (-2)
[ 7.399074] i915 0000:00:02.0: Direct firmware load for i915/glk_dmc_ver1_04.bin failed with error -2
[ 7.399077] i915 0000:00:02.0: Failed to load DMC firmware i915/glk_dmc_ver1_04.bin. Disabling runtime power management.
[ 7.399079] i915 0000:00:02.0: DMC firmware homepage: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915
The backported firmware-misc-nonfree package will remove those messages.
First edited /etc/apt/sources.list to include "non-free" which now reads
Code: Select all
deb http://ftp.debian.org/debian/ stretch main non-free
.
Then the usual
&
Code: Select all
apt-get install firmware-misc-nonfree
.
I also noticed package "intel-microcode", yet could not install it due to it's depency on "iucode-tool". Yet "iucode-tool" is either missing, obsolete or available from another source I'm not currently aware of...
The current status being:
Code: Select all
[ 7.463396] i915 0000:00:02.0: firmware: failed to load i915/glk_dmc_ver1_04.bin (-2)
[ 7.463398] i915 0000:00:02.0: Direct firmware load for i915/glk_dmc_ver1_04.bin failed with error -2
[ 7.463401] i915 0000:00:02.0: Failed to load DMC firmware i915/glk_dmc_ver1_04.bin. Disabling runtime power management.
...
[ 8.631479] r8169 0000:02:00.0: firmware: failed to load rtl_nic/rtl8168h-2.fw (-2)
[ 8.631524] r8169 0000:02:00.0: Direct firmware load for rtl_nic/rtl8168h-2.fw failed with error -2
[ 8.631528] r8169 0000:02:00.0 eno1: unable to load firmware patch rtl_nic/rtl8168h-2.fw (-2)
...
[ 6.942249] bluetooth hci0: firmware: failed to load intel/ibt-17-16-1.sfi (-2)
[ 6.942320] bluetooth hci0: Direct firmware load for intel/ibt-17-16-1.sfi failed with error -2
[ 6.942323] Bluetooth: hci0: Failed to load Intel firmware file (-2)
...
[ 7.061732] iwlwifi 0000:00:0c.0: firmware: failed to load iwlwifi-9000-pu-b0-jf-b0-38.ucode (-2)
[ 7.061774] iwlwifi 0000:00:0c.0: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-38.ucode failed with error -2
[ 7.061786] iwlwifi 0000:00:0c.0: firmware: failed to load iwlwifi-9000-pu-b0-jf-b0-37.ucode (-2)
[ 7.061819] iwlwifi 0000:00:0c.0: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-37.ucode failed with error -2
[ 7.061830] iwlwifi 0000:00:0c.0: firmware: failed to load iwlwifi-9000-pu-b0-jf-b0-36.ucode (-2)
[ 7.061863] iwlwifi 0000:00:0c.0: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-36.ucode failed with error -2
[ 7.061872] iwlwifi 0000:00:0c.0: firmware: failed to load iwlwifi-9000-pu-b0-jf-b0-35.ucode (-2)
[ 7.061905] iwlwifi 0000:00:0c.0: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-35.ucode failed with error -2
[ 7.061916] iwlwifi 0000:00:0c.0: firmware: failed to load iwlwifi-9000-pu-b0-jf-b0-34.ucode (-2)
[ 7.061948] iwlwifi 0000:00:0c.0: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-34.ucode failed with error -2
[ 7.061958] iwlwifi 0000:00:0c.0: firmware: failed to load iwlwifi-9000-pu-b0-jf-b0-33.ucode (-2)
[ 7.061990] iwlwifi 0000:00:0c.0: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-33.ucode failed with error -2
[ 7.062001] iwlwifi 0000:00:0c.0: firmware: failed to load iwlwifi-9000-pu-b0-jf-b0-32.ucode (-2)
[ 7.062033] iwlwifi 0000:00:0c.0: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-32.ucode failed with error -2
[ 7.062043] iwlwifi 0000:00:0c.0: firmware: failed to load iwlwifi-9000-pu-b0-jf-b0-31.ucode (-2)
[ 7.062075] iwlwifi 0000:00:0c.0: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-31.ucode failed with error -2
[ 7.062085] iwlwifi 0000:00:0c.0: firmware: failed to load iwlwifi-9000-pu-b0-jf-b0-30.ucode (-2)
[ 7.062118] iwlwifi 0000:00:0c.0: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-30.ucode failed with error -2
[ 7.062120] iwlwifi 0000:00:0c.0: minimum version required: iwlwifi-9000-pu-b0-jf-b0-30
[ 7.062149] iwlwifi 0000:00:0c.0: maximum version supported: iwlwifi-9000-pu-b0-jf-b0-38
...
[ 7.463396] i915 0000:00:02.0: firmware: failed to load i915/glk_dmc_ver1_04.bin (-2)
[ 7.463398] i915 0000:00:02.0: Direct firmware load for i915/glk_dmc_ver1_04.bin failed with error -2
[ 7.463401] i915 0000:00:02.0: Failed to load DMC firmware i915/glk_dmc_ver1_04.bin. Disabling runtime power management.
...
[ 8.631479] r8169 0000:02:00.0: firmware: failed to load rtl_nic/rtl8168h-2.fw (-2)
[ 8.631524] r8169 0000:02:00.0: Direct firmware load for rtl_nic/rtl8168h-2.fw failed with error -2
[ 8.631528] r8169 0000:02:00.0 eno1: unable to load firmware patch rtl_nic/rtl8168h-2.fw (-2)
Head_on_a_Stick wrote:peek wrote:Trying to start Kodi as a normal user:
Code: Select all
Fatal server error:
(EE) parse_vt_settings: Cannot open /dev/tty0 (Permission denied)
Does this get Kodi working (as your normal user!):
Yes !!
and also
starts Kodi as a non-priviledged (not root) user.
I've been starting Kodi via
or
until it started to fail executing as non-priviledged user.
Head_on_a_Stick wrote:peek wrote:Starting Kodi under root
*Never* do this.
Also, how are you "starting Kodi as root", exactly?
Did you log in as your normal user and use `sudo`? If so then the root-owned ~/.Xauthority will have to be deleted (I think).
No. I log in as a non-priviledged user. Then, if everything fails and creates headaches, I
only to see what would transpire as an elevated user. (be it root)
"sudo" is not not even installed.
Head_on_a_Stick wrote:peek wrote:With Kodi still running or exited:
Code: Select all
#glxinfo
Error: unable to open display
Code: Select all
#glxgears
Error: couldn't open display (null)
If you are running those commands from a console (TTY) then you need to state the display, for example:
And please stop running commands as root unless you absolutely have to:
https://en.wikipedia.org/wiki/Principle ... _privilege
Even with Kodi started via
and running on display 2, executing either
or
still causes "Error: unable to open display: 2".
I can understand that GLXGears would need to run in a window and as such a window manager would be required (of which none is installed), yet I didn't expect the same from GLXInfo though.
I've only used debian/Linux in console/terminal/ssh mode, being the reason I'm quite clueless with anything that involves X.
And it is specifically due to the principle of least priviledge that I just cannot trust LibreELEC, although it works perfectly out-of-the-box.
LibreELEC runs all processes as root, with the root password unchangeable and only changeable at compilation. Being the reason I included "No LibreELEC" in the heading.
Head_on_a_Stick wrote:Oh, and I agree with Segfault — you should probably use Arch instead with hardware this new; Debian 10 will be out next summer and should work much better with your hardware (once the non-free firmware has been installed).
I hear ya, but I don't want to use anything other than debian
Be it not the quickest resolution.
Make no mistake, I appreciate all the comments and assistance.