Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

Purist form of Kodi on Intel NUC7CJYH - No LibreELEC

Graphical Environments, Managers, Multimedia & Desktop questions.
Message
Author
User avatar
Head_on_a_Stick
Posts: 14114
Joined: 2014-06-01 17:46
Location: London, England
Has thanked: 81 times
Been thanked: 132 times

Re: Purist form of Kodi on Intel NUC7CJYH - No LibreELEC

#16 Post by Head_on_a_Stick »

jmgibson1981 wrote:This type of crap is why people hate linux. Elitist BS nitpicking every little thing
Do you even understand what the xserver-xorg-legacy package does and what a risk it represents?

Also, one of the advantages that a technical support forum has over random blogs is peer review — if somebody posts nonsense then the community will correct them.

I understand that you feel aggrieved by my post but please see if from my perspective: I'm annoyed that I had to correct you :mrgreen:
deadbang

User avatar
GarryRicketson
Posts: 5644
Joined: 2015-01-20 22:16
Location: Durango, Mexico

Re: Purist form of Kodi on Intel NUC7CJYH - No LibreELEC

#17 Post by GarryRicketson »

jmgibson1981 wrote:
This type of crap is why people hate linux
Speak for your self, but there are plenty of people that do like Linux, that is why they or we use it. The ones that "hate" it, hate it because it is not like their beloved MS windows, I suppose. With Linux, it is opensource, and this allows us to be able to see what the code is, and if and when something is bad, or could cause problems, we can speak out, and let others know as well.
H_O_A_S >Also, one of the advantages that a technical support forum has over random blogs is peer review — if somebody posts nonsense then the community will correct them.
As compared to :
jmgibson1981>>I have a feeling I wouldn't have gotten half this garbage if I left out the Ubuntu part of my post. Unreal.
Ubuntu is NOT Debian, and not mentioning that a script or tutorial is intended for Ubuntu, or that the packages to be installed are for Ubuntu, from Ubuntu ppas, is just plain bad advice. Fortunately HeadOnAStick, did say something, so other Debian users don't mess up their system , unwittingly. These are things that I like about Linux, my self. I don't know about others.

User avatar
stevepusser
Posts: 12930
Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 71 times

Re: Purist form of Kodi on Intel NUC7CJYH - No LibreELEC

#18 Post by stevepusser »

jmgibson1981 wrote:God forbid I try to help someone. Minimal yes. But most people want support for what they do, I know I do. You want to run unsupported methods, by all means. I have no vested interest. But you people are ridiculous. I have a feeling I wouldn't have gotten half this garbage if I left out the Ubuntu part of my post. Unreal. This type of crap is why people hate linux. Elitist BS nitpicking every little thing. I won't be back. Throw a party, I don't care. I've spent a couple years perfecting my deployment in every way with countless adjustments and experiments to configs to get things perfect. If that is worthless, I'm sorry I wasted your time. I won't make that mistake again, at least not here. If a mod is reading this, just close my damn account. Not worth the grief.
You disagreed with my statement that new hardware very often required new KMF (kernel mesa firmware) based on your personal experience with your own older hardware. I asked for inxi output to see what the graphics stack situation was doing with the stock KMF. And you complain about arrogance. Jeesh.

By the way, there are repositories with the current Kodi release that has been backported on Stretch: https://repology.org/metapackage/kodi/versions
MX Linux packager and developer

User avatar
peek
Posts: 18
Joined: 2018-10-31 10:15

Re: Purist form of Kodi on Intel NUC7CJYH - No LibreELEC

#19 Post by peek »

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 update
&

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!):

Code: Select all

startx $(which kodi)
Yes !!

Code: Select all

startx $(which kodi)
and also

Code: Select all

startx $(which kodi-standalone)
starts Kodi as a non-priviledged (not root) user.

I've been starting Kodi via

Code: Select all

xinit $(which kodi)
or

Code: Select all

xinit $(which kodi-standalone)
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

Code: Select all

su
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:

Code: Select all

DISPLAY=:0 glxinfo
And please stop running commands as root unless you absolutely have to: https://en.wikipedia.org/wiki/Principle ... _privilege
Even with Kodi started via

Code: Select all

startx $(which kodi)
and running on display 2, executing either

Code: Select all

DISPLAY=:2 glxinfo
or

Code: Select all

DISPLAY=:2 glxgears
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 :cry: Be it not the quickest resolution.

Make no mistake, I appreciate all the comments and assistance.

User avatar
peek
Posts: 18
Joined: 2018-10-31 10:15

Re: Purist form of Kodi on Intel NUC7CJYH - No LibreELEC

#20 Post by peek »

stevepusser wrote:You can also get your wi-fi working, if that's important, by installing firmware-iwlwifi from backports.

Code: Select all

apt-get -t stretch-backports install firmware-iwlwifi
Eveything is important. From a learning perspective. 8)

Though DMESG still chokes a bit :

Code: Select all

[    6.979390] iwlwifi 0000:00:0c.0: enabling device (0000 -> 0002)
[    7.009364] iwlwifi 0000:00:0c.0: firmware: failed to load iwlwifi-9000-pu-b0-jf-b0-38.ucode (-2)
[    7.009404] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware
[    7.009448] iwlwifi 0000:00:0c.0: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-38.ucode failed with error -2
[    7.009463] iwlwifi 0000:00:0c.0: firmware: failed to load iwlwifi-9000-pu-b0-jf-b0-37.ucode (-2)
[    7.009496] iwlwifi 0000:00:0c.0: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-37.ucode failed with error -2
[    7.009507] iwlwifi 0000:00:0c.0: firmware: failed to load iwlwifi-9000-pu-b0-jf-b0-36.ucode (-2)
[    7.009557] iwlwifi 0000:00:0c.0: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-36.ucode failed with error -2
[    7.009567] iwlwifi 0000:00:0c.0: firmware: failed to load iwlwifi-9000-pu-b0-jf-b0-35.ucode (-2)
[    7.009599] iwlwifi 0000:00:0c.0: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-35.ucode failed with error -2
[    7.009610] iwlwifi 0000:00:0c.0: firmware: failed to load iwlwifi-9000-pu-b0-jf-b0-34.ucode (-2)
[    7.009642] iwlwifi 0000:00:0c.0: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-34.ucode failed with error -2
[    7.009652] iwlwifi 0000:00:0c.0: firmware: failed to load iwlwifi-9000-pu-b0-jf-b0-33.ucode (-2)
[    7.009684] iwlwifi 0000:00:0c.0: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-33.ucode failed with error -2
[    7.009694] iwlwifi 0000:00:0c.0: firmware: failed to load iwlwifi-9000-pu-b0-jf-b0-32.ucode (-2)
[    7.009726] iwlwifi 0000:00:0c.0: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-32.ucode failed with error -2
[    7.009737] iwlwifi 0000:00:0c.0: firmware: failed to load iwlwifi-9000-pu-b0-jf-b0-31.ucode (-2)
[    7.009769] iwlwifi 0000:00:0c.0: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-31.ucode failed with error -2
[    7.009779] iwlwifi 0000:00:0c.0: firmware: failed to load iwlwifi-9000-pu-b0-jf-b0-30.ucode (-2)
[    7.009811] iwlwifi 0000:00:0c.0: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-30.ucode failed with error -2
[    7.009814] iwlwifi 0000:00:0c.0: minimum version required: iwlwifi-9000-pu-b0-jf-b0-30
[    7.009843] iwlwifi 0000:00:0c.0: maximum version supported: iwlwifi-9000-pu-b0-jf-b0-38
...
[    7.050023] bluetooth hci0: firmware: failed to load intel/ibt-17-16-1.sfi (-2)
[    7.050078] bluetooth hci0: Direct firmware load for intel/ibt-17-16-1.sfi failed with error -2
[    7.050081] Bluetooth: hci0: Failed to load Intel firmware file (-2)
[    7.441842] [drm] GuC: No firmware known for this platform!
[    7.441844] [drm] HuC: No firmware known for this platform!
...
[    7.493791] i915 0000:00:02.0: firmware: failed to load i915/glk_dmc_ver1_04.bin (-2)
[    7.493793] i915 0000:00:02.0: Direct firmware load for i915/glk_dmc_ver1_04.bin failed with error -2
[    7.493797] i915 0000:00:02.0: Failed to load DMC firmware i915/glk_dmc_ver1_04.bin. Disabling runtime power management.
...
[    8.502684] r8169 0000:02:00.0: firmware: failed to load rtl_nic/rtl8168h-2.fw (-2)
[    8.502728] r8169 0000:02:00.0: Direct firmware load for rtl_nic/rtl8168h-2.fw failed with error -2
[    8.502732] r8169 0000:02:00.0 eno1: unable to load firmware patch rtl_nic/rtl8168h-2.fw (-2)

Thanks.

User avatar
peek
Posts: 18
Joined: 2018-10-31 10:15

Re: Purist form of Kodi on Intel NUC7CJYH - No LibreELEC

#21 Post by peek »

Thanks for the advise jmgibson1981. It is appreciated.

However, I wish to become more involved in the Debain project. Yet there is quite a bit I need to catchup with. Being the reason I'm a bit of a die hard on this topic. :roll: However, if Debian cannot provide the same performance and quality as with LibreELEC, well ... I will surely turn to Ubuntu. Hopefully to bring what I've learned with Ubuntu back to Debian later again.

Yet, security will remain a mayor concern, and services running as root will cause me some sleepless nights ... worrying. And I looooooveeeee sleep. :wink:

Sooo, please see this as a "lab session" which allows everyone to re-evalute and/or become more acquintented with what is involved/related/best practise these days on how to implement Kodi (minimalistic) on Debian.

In all regards, I'd re-install from scratch at the drop of a hat if someone requires. Quite honestly, a re-install will be performed once all the kinks have been resolved as to ensure a proper writeup does exist for the next wanderer.

Soooo, I hope you'd re-assess your opinion as the knowledge you already hold would surely be beneficial in re-assesing this endeavour.

----

Building on each other's shoulders. Isn't that what Linux is about ?

User avatar
peek
Posts: 18
Joined: 2018-10-31 10:15

Re: Purist form of Kodi on Intel NUC7CJYH - No LibreELEC

#22 Post by peek »

jmgibson1981 wrote: The reason why the OP has problems is because they tried `xinit` instead of `startx`, IMO.
The system included kodi.service file under /lib/systemd/system/ as referenced by jmgibson1981's also starts kodi with xinit :
ExecStart=/usr/bin/xinit /usr/bin/dbus-launch --exit-with-session /usr/bin/kodi-standalone -- :0 -nolisten tcp vt7

User avatar
peek
Posts: 18
Joined: 2018-10-31 10:15

Re: Purist form of Kodi on Intel NUC7CJYH - No LibreELEC

#23 Post by peek »

jmgibson1981 wrote:
Static IP on the Kodi machine(s) would be best. This allows one to use an app on your phone / tablet as the remote. I find it more convenient than using a physical remote with Lirc - https://wiki.debian.org/NetworkConfigur ... e_manually.
Finally, I can add something of value: Try Yatse @ https://play.google.com/store/apps/deta ... widgetfree

You'll never look back. It's brilliant & with shutdown & WOL you might even shelve the "refresh script" with the IR remote 8)

User avatar
peek
Posts: 18
Joined: 2018-10-31 10:15

Re: Purist form of Kodi on Intel NUC7CJYH - No LibreELEC

#24 Post by peek »

Status update - Complete redo:

Debian 9.5.0 minimal text based installation

Code: Select all

vi /etc/apt/sources.list
Added "non-free"
deb http://ftp.au.debian.org/debian/ stretch main non-free

Adding Backports Repository:

Code: Select all

echo "deb http://ftp.debian.org/debian stretch-backports main" > /etc/apt/sources.list.d/backports.list

Code: Select all

apt-get update
From backports repository:

Code: Select all

apt-get -t stretch-backports install 

		linux-image-amd64 			<- latest kernel

		libegl-mesa0
		libegl1-mesa
		libgl1-mesa-dri 			
		libgl1-mesa-glx
		libglapi-mesa

		libglu1-mesa
		libglx-mesa0 

		mesa-utils 
		mesa-va-drivers
		mesa-vdpau-drivers
From contrib repository:

apt-get install

??


From stable stretch repository:

Code: Select all

apt-get install 

		firmware-linux-free
		pulseaudio
		xinit
		dbus-x11

		kodi
		kodi-eventclients-kodi-send
		kodi-pvr-hts				
		kodi-pvr-iptvsimple
		kodi-visualization-spectrum

		mariadb-server
From non-free repository:

Code: Select all

apt-get install

		firmware-misc-nonfree
		firmware-realtek			<- r8169 realtek firmware
		firmware-iwlwifi			<- Intel WiFi		
MariaDB setup:

Code: Select all

vi /etc/mysql/mariadb.conf.d/50-kodi.optimize.conf

Code: Select all

	[mysqld]

	optimizer_search_depth = 1
	skip-name-resolve
	innodb_adaptive_hash_index = off
Kodi Service:

Code: Select all

cp /lib/systemd/system/kodi.service /etc/systemd/system/

Code: Select all

vi /etc/systemd/system/kodi.service 
or paste into new file:

Code: Select all

	[Unit]
	Description=Kodi Media Center

	# if you don't need the MySQL DB backend, this should be sufficient
	#After=systemd-user-sessions.service network.target sound.target

	# if you need the MySQL DB backend, use this block instead of the previous
	After=systemd-user-sessions.service network.target sound.target mysql.service
	Wants=mysql.service

	[Service]
	User=kodi
	Group=kodi
	Type=simple
	#PAMName=login # you might want to try this one, did not work on all systems
	ExecStart=/usr/bin/xinit /usr/bin/dbus-launch --exit-with-session /usr/bin/kodi-standalone -- :0 -nolisten tcp vt7
	Restart=on-abort
	RestartSec=5

	[Install]
	WantedBy=multi-user.target

Code: Select all

useradd kodi

Code: Select all

passwd kodi 

Code: Select all

usermod -a -G video kodi

Code: Select all

usermod -a -G audio kodi

Code: Select all

groups kodi
kodi : kodi audio video

Code: Select all

systemctl enable kodi
Created symlink /etc/systemd/system/multi-user.target.wants/kodi.service → /etc/systemd/system/kodi.service.
----

Reboot ...

Dedi has a new tantrum, just before the fscheck:

[ 0.048000] mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 4: a600000000020408
[ 0.048000] mce: [Hardware Error]: TSC 0 ADDR fef4c9e0
[ 0.048000] mce: [Hardware Error]: PROCESSOR 0:706a1 TIME 1541419467 SOCKET 0 APIC 0 microcode 28

Code: Select all

dmesg

Code: Select all

[    7.045832] iwlwifi 0000:00:0c.0: firmware: failed to load iwlwifi-9000-pu-b0-jf-b0-38.ucode (-2)
[    7.045882] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware
[    7.045917] iwlwifi 0000:00:0c.0: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-38.ucode failed with error -2
[    7.045933] iwlwifi 0000:00:0c.0: firmware: failed to load iwlwifi-9000-pu-b0-jf-b0-37.ucode (-2)
[    7.045966] iwlwifi 0000:00:0c.0: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-37.ucode failed with error -2
[    7.045977] iwlwifi 0000:00:0c.0: firmware: failed to load iwlwifi-9000-pu-b0-jf-b0-36.ucode (-2)
[    7.046010] iwlwifi 0000:00:0c.0: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-36.ucode failed with error -2
[    7.046020] iwlwifi 0000:00:0c.0: firmware: failed to load iwlwifi-9000-pu-b0-jf-b0-35.ucode (-2)
[    7.046053] iwlwifi 0000:00:0c.0: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-35.ucode failed with error -2
[    7.046064] iwlwifi 0000:00:0c.0: firmware: failed to load iwlwifi-9000-pu-b0-jf-b0-34.ucode (-2)
[    7.046097] iwlwifi 0000:00:0c.0: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-34.ucode failed with error -2
[    7.046107] iwlwifi 0000:00:0c.0: firmware: failed to load iwlwifi-9000-pu-b0-jf-b0-33.ucode (-2)
[    7.046140] iwlwifi 0000:00:0c.0: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-33.ucode failed with error -2
[    7.046161] iwlwifi 0000:00:0c.0: firmware: failed to load iwlwifi-9000-pu-b0-jf-b0-32.ucode (-2)
[    7.046194] iwlwifi 0000:00:0c.0: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-32.ucode failed with error -2
[    7.046206] iwlwifi 0000:00:0c.0: firmware: failed to load iwlwifi-9000-pu-b0-jf-b0-31.ucode (-2)
[    7.046238] iwlwifi 0000:00:0c.0: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-31.ucode failed with error -2
[    7.046248] iwlwifi 0000:00:0c.0: firmware: failed to load iwlwifi-9000-pu-b0-jf-b0-30.ucode (-2)
[    7.046281] iwlwifi 0000:00:0c.0: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-30.ucode failed with error -2
[    7.046283] iwlwifi 0000:00:0c.0: minimum version required: iwlwifi-9000-pu-b0-jf-b0-30
[    7.046313] iwlwifi 0000:00:0c.0: maximum version supported: iwlwifi-9000-pu-b0-jf-b0-38
...
[    7.255859] bluetooth hci0: firmware: failed to load intel/ibt-17-16-1.sfi (-2)
[    7.255904] bluetooth hci0: Direct firmware load for intel/ibt-17-16-1.sfi failed with error -2
[    7.255908] Bluetooth: hci0: Failed to load Intel firmware file (-2)
...
[    7.587732] i915 0000:00:02.0: firmware: failed to load i915/glk_dmc_ver1_04.bin (-2)
[    7.587740] i915 0000:00:02.0: Direct firmware load for i915/glk_dmc_ver1_04.bin failed with error -2
[    7.587744] i915 0000:00:02.0: Failed to load DMC firmware i915/glk_dmc_ver1_04.bin. Disabling runtime power management.
...
Does not launch into Kodi. (Gotta be permissions. I know someone said something. I'm just too tired at present to go look it up)

As user kodi executing:

Code: Select all

/usr/bin/xinit /usr/bin/dbus-launch --exit-with-session /usr/bin/kodi-standalone -- :0 -nolisten tcp vt7
results in:
Fatal server error:
(EE) Cannot establish any listening sockets ...
As user root executing: (Cringing as I type this knowing Head_on_a_Stick is gonna get excited about this one)

Code: Select all

/usr/bin/xinit /usr/bin/dbus-launch --exit-with-session /usr/bin/kodi-standalone -- :0 -nolisten tcp vt7
results in Kodi starting up.

Kodi looks good, though still uses software rendering - ff-h264 (SW) when playing content.

As root:

Code: Select all

update-pciids

Code: Select all

update-usbids
Non-priviledged user:

Code: Select all

inxi -Fxz

Code: Select all

System:    Host: Dedi Kernel: 4.18.0-0.bpo.1-amd64 x86_64 (64 bit gcc: 6.3.0) Console: tty 0
           Distro: Debian GNU/Linux 9 (stretch)
Machine:   Device: un-determined System: Intel product: NUC7CJYH v: J67971-402
           Mobo: Intel model: NUC7JYB v: J67967-401
           UEFI: Intel v: JYGLKCPX.86A.0045.2018.1001.1100 date: 10/01/2018
CPU:       Dual core Intel Celeron J4005 (-MCP-) cache: 4096 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 7987
           clock speeds: max: 2700 MHz 1: 1014 MHz 2: 975 MHz
Graphics:  Card: Intel Device 3185 bus-ID: 00:02.0
           Display Server: N/A drivers: modesetting (unloaded: fbdev,vesa)
           tty size: 168x44 Advanced Data: N/A out of X
Audio:     Card Intel Device 3198 driver: snd_hda_intel bus-ID: 00:0e.0 Sound: ALSA v: k4.18.0-0.bpo.1-amd64
Network:   Card-1: Intel Device 31dc bus-ID: 00:0c.0
           IF: N/A state: N/A speed: N/A duplex: N/A mac: N/A
           Card-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: e000 bus-ID: 02:00.0
           IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 15.4GB (39.6% used)
           ID-1: USB /dev/sda model: Ultra_Fit size: 15.4GB
Partition: ID-1: / size: 11G used: 2.3G (24%) fs: ext4 dev: /dev/sda2
           ID-2: swap-1 size: 3.85GB used: 0.00GB (0%) fs: swap dev: /dev/sda3
Sensors:   System Temperatures: cpu: 44.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 100 Uptime: 30 min Memory: 674.9/3532.4MB Init: systemd runlevel: 5 Gcc sys: N/A
           Client: Shell (bash 4.4.121) inxi: 2.3.5
? Why would I be seeing
Display Server: N/A drivers: modesetting (unloaded: fbdev,vesa)
?

I'll be combing through it again tomorrow. Thanks.

User avatar
Head_on_a_Stick
Posts: 14114
Joined: 2014-06-01 17:46
Location: London, England
Has thanked: 81 times
Been thanked: 132 times

Re: Purist form of Kodi on Intel NUC7CJYH - No LibreELEC

#25 Post by Head_on_a_Stick »

peek wrote: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...
It's in the contrib section of the repositories:

https://packages.debian.org/stretch-bac ... ucode-tool
Yes !!

Code: Select all

startx $(which kodi)
and also

Code: Select all

startx $(which kodi-standalone)
starts Kodi as a non-priviledged (not root) user.

I've been starting Kodi via

Code: Select all

xinit $(which kodi)
or

Code: Select all

xinit $(which kodi-standalone)
until it started to fail executing as non-priviledged user.
I think some things have changed in respect of the desktop since the X hole was noticed so you might need to use `startx` rather than `xinit` from now on.

Oh, and that silly kodi-standalone script is a relic from the XBMC days and just checks if pulseaudio is running and sets some variables, it is absolutely not needed — just run the /usr/bin/kodi binary directly.
deadbang

User avatar
stevepusser
Posts: 12930
Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 71 times

Re: Purist form of Kodi on Intel NUC7CJYH - No LibreELEC

#26 Post by stevepusser »

Backports does have updated versions of all those firmware packages; you need to install those to get rid of those missing firmware messages:

https://packages.debian.org/stretch-bac ... re-iwlwifi
https://packages.debian.org/stretch-bac ... re-realtek
https://packages.debian.org/stretch-bac ... sc-nonfree

Firmware packages are backwards-compatible with older kernels, by the way.

Check their status and available versions with

Code: Select all

apt policy <package name>
MX Linux packager and developer

User avatar
Head_on_a_Stick
Posts: 14114
Joined: 2014-06-01 17:46
Location: London, England
Has thanked: 81 times
Been thanked: 132 times

Re: Purist form of Kodi on Intel NUC7CJYH - No LibreELEC

#27 Post by Head_on_a_Stick »

peek wrote:

Code: Select all

systemctl enable kodi
Created symlink /etc/systemd/system/multi-user.target.wants/kodi.service → /etc/systemd/system/kodi.service.
Why did you do that? :?

You can get Kodi autostarting for your kodi user by setting up automatic login for that user, guide here:

http://forums.debian.net/viewtopic.php?f=16&t=123694

^ just add `$(which kodi)` to the end of the `exec startx` command in ~/.profile :wink:

And remember to disable kodi.service beforehand or the two methods may conflict.
As user root executing: (Cringing as I type this knowing Head_on_a_Stick is gonna get excited about this one)

Code: Select all

/usr/bin/xinit /usr/bin/dbus-launch --exit-with-session /usr/bin/kodi-standalone -- :0 -nolisten tcp vt7
Right, this is my final warning: you do that one more time and so help me ${DEITY} I will turn this thread around and drive it home, OK? :mrgreen:

But seriously, systemd launches dbus these days and the X server hasn't listened to tcp for a long while so I think that line is obsolete.
deadbang

User avatar
peek
Posts: 18
Joined: 2018-10-31 10:15

Re: Purist form of Kodi on Intel NUC7CJYH - No LibreELEC

#28 Post by peek »

The URL states Package: iucode-tool (2.3.1-1~bpo9+1) [contrib], yet I get

iucode-tool (2.1.1-1) and
intel-microcode (3.20180425.1~deb9u1)

I jabbed an apt-get update and apt-get upgrade, just to prevent any possibly grilling, followed by

an uninstall and reinstall via apt-get install intel-microcode

and also an uninstall and reinstall via apt-get -t stretch-backports install intel-microcode

*** iucode-tool being pulled due to intel-microcode's dependency *** (Just saying.)

but iucode-tool stays 2.1.1-1 ...

...why am I not 2.3.1-1~bpo9+1 worthy ? :cry:
Head_on_a_Stick wrote:
Oh, and that silly kodi-standalone script is a relic from the XBMC days and just checks if pulseaudio is running and sets some variables, it is absolutely not needed — just run the /usr/bin/kodi binary directly.
Ooooookay, I'll be kicking the kodi-standalone habit from this point forward, never to mention it again.

User avatar
peek
Posts: 18
Joined: 2018-10-31 10:15

Re: Purist form of Kodi on Intel NUC7CJYH - No LibreELEC

#29 Post by peek »

stevepusser wrote:Backports does have updated versions of all those firmware packages; you need to install those to get rid of those missing firmware messages:

https://packages.debian.org/stretch-bac ... re-iwlwifi
https://packages.debian.org/stretch-bac ... re-realtek
https://packages.debian.org/stretch-bac ... sc-nonfree

Firmware packages are backwards-compatible with older kernels, by the way.

Check their status and available versions with

Code: Select all

apt policy <package name>

Code: Select all

apt policy firmware-iwlwifi
firmware-iwlwifi:
Installed: 20161130-3
Candidate: 20161130-3
Version table:
*** 20161130-3 500
500 http://ftp.debian.org/debian stretch/non-free amd64 Packages
100 /var/lib/dpkg/status

Code: Select all

apt policy firmware-realtek
firmware-realtek:
Installed: 20161130-3
Candidate: 20161130-3
Version table:
*** 20161130-3 500
500 http://ftp.debian.org/debian stretch/non-free amd64 Packages
100 /var/lib/dpkg/status

Code: Select all

apt policy firmware-misc-nonfree
firmware-misc-nonfree:
Installed: 20161130-3
Candidate: 20161130-3
Version table:
*** 20161130-3 500
500 http://ftp.debian.org/debian stretch/non-free amd64 Packages
100 /var/lib/dpkg/status

Code: Select all

apt-get remove firmware-iwlwifi firmware-realtek firmware-misc-nonfree

Code: Select all

apt-get -t stretch-backports install firmware-iwlwifi firmware-realtek firmware-misc-nonfree


yet all packages still dates 20161130-3. Thus uninstalled & re-installed them each individually, as in apt-get -t stretch-backports install firmware-iwlwifi etc Yet ...

Code: Select all

apt policy firmware-iwlwifi
firmware-iwlwifi:
Installed: 20161130-3
Candidate: 20161130-3
Version table:
*** 20161130-3 500
500 http://ftp.debian.org/debian stretch/non-free amd64 Packages
100 /var/lib/dpkg/status

Code: Select all

apt policy firmware-realtek
firmware-realtek:
Installed: 20161130-3
Candidate: 20161130-3
Version table:
*** 20161130-3 500
500 http://ftp.debian.org/debian stretch/non-free amd64 Packages
100 /var/lib/dpkg/status

Code: Select all

apt policy firmware-misc-nonfree
firmware-misc-nonfree:
Installed: 20161130-3
Candidate: 20161130-3
Version table:
*** 20161130-3 500
500 http://ftp.debian.org/debian stretch/non-free amd64 Packages
100 /var/lib/dpkg/status
On the side, Backports Repo is still :

Code: Select all

cat /etc/apt/sources.list.d/backports.list
deb http://ftp.debian.org/debian stretch-backports main
Am I just going stupid really quickly ?

:?

User avatar
stevepusser
Posts: 12930
Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 71 times

Re: Purist form of Kodi on Intel NUC7CJYH - No LibreELEC

#30 Post by stevepusser »

peek wrote:
stevepusser wrote:Backports does have updated versions of all those firmware packages; you need to install those to get rid of those missing firmware messages:

.....
On the side, Backports Repo is still :

Code: Select all

cat /etc/apt/sources.list.d/backports.list
deb http://ftp.debian.org/debian stretch-backports main
Am I just going stupid really quickly ?

:?
You just have to add non-free to the end of that line to get the non-free section backports where that firmware lives.

Code: Select all

deb http://ftp.debian.org/debian stretch-backports main non-free
MX Linux packager and developer

User avatar
peek
Posts: 18
Joined: 2018-10-31 10:15

Re: Purist form of Kodi on Intel NUC7CJYH - No LibreELEC

#31 Post by peek »

Head_on_a_Stick wrote:
peek wrote:

Code: Select all

systemctl enable kodi
Created symlink /etc/systemd/system/multi-user.target.wants/kodi.service → /etc/systemd/system/kodi.service.
Why did you do that? :?
There's so many references on other writeups to do it ...
It just felt good, as I do it often to other services ...
It was already there, ready to be used ...
My friends made me do it !!
I felt lonely and depressed ...
I wanted to impress you.

Ooookay, I'm sorry. Won't do it again. I accept all punishment. :arrow:
Head_on_a_Stick wrote: You can get Kodi autostarting for your kodi user by setting up automatic login for that user, guide here:

http://forums.debian.net/viewtopic.php?f=16&t=123694

^ just add `$(which kodi)` to the end of the `exec startx` command in ~/.profile :wink:

And remember to disable kodi.service beforehand or the two methods may conflict.

Code: Select all

systemctl disable kodi
rm /etc/systemd/system/kodi.service
Any objection in also removing /lib/systemd/system/kodi.service ? Just prevents temptation and also creates an oppertunity for someone to Google their way into this thread. :idea:

Code: Select all

rm /lib/systemd/system/kodi.service
auto login: ** Unfamiliar territory. Not sure on what I'm about to do :| Just going with the flow **

Code: Select all

su
mkdir -p /etc/systemd/system/getty@tty1.service.d
vi /etc/systemd/system/getty@tty1.service.d/override.conf
[Service]
ExecStart=
ExecStart=-/sbin/agetty --autologin kodi --noclear %I $TERM

Code: Select all

exit
Side note:
** Yip, two lines starting ExecStart=
** Removing the first line, be it "empty", will cause the autologin process to fail. "Hanging" TTY1 whilst displaying the current hardware issues as seen in dmesg. Could possibly have been only a black screen, which woudl then have caused uncertainty as to what is happening should the system not have had any hardware issues.
** Whilst dmesg will utter : [ 5.519839] systemd[1]: getty@tty1.service: Service has more than one ExecStart= setting, which is only allowed for Type=oneshot services. Refusing.
** Non-priviledged "kodi" user's password had NOT been disabled. ie NO "passwd -d kodi" issued.

auto startx:

Check to ensure you're the "kodi" user. i.e "

Code: Select all

whoami
"

Code: Select all

vi ~/.profile
Add [ "$(tty)" = "/dev/tty1" ] && exec startx $(which kodi) at the end of file

** Set correct default.target to ensure the system boots to the console (TTY) rather than to a display manager:

Code: Select all

systemctl set-default multi-user.target
Created symlink /etc/systemd/system/default.target → /lib/systemd/system/multi-user.target.
To reverse this change, reset the default.target with:

# systemctl set-default graphical.target


** Nope, I dunno what I'm currently doing ... but it feels right ... :mrgreen:

Code: Select all

/sbin/reboot
Whoooooooo hooooooo ! Head_on_a_Stick ... Hhhmm, pondering naming my next kid after you. :D
Head_on_a_Stick wrote:
As user root executing: (Cringing as I type this knowing Head_on_a_Stick is gonna get excited about this one)

Code: Select all

/usr/bin/xinit /usr/bin/dbus-launch --exit-with-session /usr/bin/kodi-standalone -- :0 -nolisten tcp vt7
Right, this is my final warning: you do that one more time and so help me ${DEITY} I will turn this thread around and drive it home, OK? :mrgreen:
...but, daaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaad :| It made it work...
Head_on_a_Stick wrote:
But seriously, systemd launches dbus these days and the X server hasn't listened to tcp for a long while so I think that line is obsolete.
Ooookay, another "old timer" being shelved. DebKodi Revision 0.3 already in the making. Watch out LibreELEC, your inferior security is numbered ! Only to fix the hardware decoding ...

Yet seriously, where does all this wisdom come from and what do we mere users need to do to acquire these Super Dad powers (in this centuary) ?

User avatar
Head_on_a_Stick
Posts: 14114
Joined: 2014-06-01 17:46
Location: London, England
Has thanked: 81 times
Been thanked: 132 times

Re: Purist form of Kodi on Intel NUC7CJYH - No LibreELEC

#32 Post by Head_on_a_Stick »

stevepusser wrote:You just have to add non-free to the end of that line to get the non-free section backports where that firmware lives.

Code: Select all

deb http://ftp.debian.org/debian stretch-backports main non-free
...and the OP will also need the contrib section for the iucode-tool package:

Code: Select all

deb http://deb.debian.org/debian stretch-backports main contrib non-free
EDIT: package name corrected, thanks Steve!
Last edited by Head_on_a_Stick on 2018-11-06 17:31, edited 1 time in total.
deadbang

User avatar
peek
Posts: 18
Joined: 2018-10-31 10:15

Re: Purist form of Kodi on Intel NUC7CJYH - No LibreELEC

#33 Post by peek »

Thanks Head_on_a_Stick & stevepusser

Note to self: (and all others who missed this)

/etc/apt/sources.list => deb http://ftp.debian.org/debian/ stretch main non-free contrib

/etc/apt/sources.list.d/backports.list => deb http://ftp.debian.org/debian stretch-backports non-free

User avatar
Head_on_a_Stick
Posts: 14114
Joined: 2014-06-01 17:46
Location: London, England
Has thanked: 81 times
Been thanked: 132 times

Re: Purist form of Kodi on Intel NUC7CJYH - No LibreELEC

#34 Post by Head_on_a_Stick »

peek wrote:/etc/apt/sources.list.d/backports.list => deb http://ftp.debian.org/debian stretch-backports non-free
Nope.

This:

Code: Select all

deb http://deb.debian.org/debian stretch-backports main contrib non-free
deadbang

User avatar
stevepusser
Posts: 12930
Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 71 times

Re: Purist form of Kodi on Intel NUC7CJYH - No LibreELEC

#35 Post by stevepusser »

Head_on_a_Stick wrote:
stevepusser wrote:You just have to add non-free to the end of that line to get the non-free section backports where that firmware lives.

Code: Select all

deb http://ftp.debian.org/debian stretch-backports main non-free
...and the OP will also need the contrib section for the iucode-tools package:

Code: Select all

deb http://deb.debian.org/debian stretch-backports main contrib non-free
Ohh hoh hoh, monsieur! I acknowledge your correction and correct yours! Eet eez iucode-tool!
MX Linux packager and developer

Post Reply