(2018-01-06, 21:40)mirtouf Wrote: [ -> ]https://paste.ubuntu.com/26334303/
Code:
sudo apt-get -f install
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
Code:
export LIBVA_DRIVER_NAME=i965
DISPLAY=:0 vainfo
libva info: VA-API version 0.40.0
libva info: va_getDriverName() returns -1
libva info: User requested driver 'i965'
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_39
libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit
Something is definitely wrong with your setup. You don't use encrypted LVM /home by chance do you? See my reply above to export the driver name to match i965
The above error normaly really only happens if you are not member of video group. I hope you rebooted after you added your user to this group?
I confirm the kodi user is part of the video group, I did not change my setup since I was using a N3150-ITX mainboard, I changed the hardware today without altering the software configuration. The /home is not encrypted.
No ideas left. Try LibreELEC from an USB stick and see what works here.
Argh! Yes obviously:
Quote:[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.4.0-104-generic root=/dev/mapper/kodi--vg-root ro quiet splash video=HDMI-A-3:1920x1080@60D drm_kms_helper.edid_firmware=HDMI-A-3:edid/edid.bin vt.handoff=7
Upgrade your kernel! Install 4.14.12 from ubuntu mainline. Download the all headers and the two 64 bit generic deb files and install them
Will do but kernel 4.13 failed also.
the kernel does not enumerate the GPU correctly. Modesetting does not seem to be active. Next step is: Try libreELEC - something is really fishy here.
I found the problem, xserver-xorg-video-intel is to be installed and the edid trick cannot be used meaning my AV receiver shall be started before I start kodi.
(2018-01-06, 23:39)mirtouf Wrote: [ -> ]I found the problem, xserver-xorg-video-intel is to be installed and the edid trick cannot be used meaning my AV receiver shall be started before I start kodi.
Works for me with 4.14 on J4205. I will add to also post /var/log/Xorg.0.log to the reporting of bugs sections. I checked your kodi.log and here it looked like the intel driver was already in use. Good it works now.
Yeah, checking /var/log/Xorg.0.log helps.
Hey,
i would like to use ALSA with HD audio passthrough instead of PulseAudio, but unfortunately, it doesn't appear on the audio device list. Could you please tell me, how i can fix this problem? As far as i can remember it used to work on my machine. I used this guide to install and setup my htpc.
Ubuntu server 16.04.3
HW: H97M-D3H
CPU: i3-4160
HDMI connection between the PC and the Onkyo TX-NR809
The howto on the first page does not install pulseaudio. I can not help you without providing all the log files from Post 1.
Okay, it could be that i rather used pulse audio to passthrough dts/dd audio streams.
i tried to collect the required logs:
dni@ubi-htpc:~$ dpkg -l |grep mesa | pastebinit
http://paste.ubuntu.com/26340191/
dni@ubi-htpc:~$ DISPLAY=:0 vainfo | pastebinit
libva info: VA-API version 0.40.0
libva info: va_getDriverName() returns -1
libva error: va_getDriverName() failed with unknown libva error,driver_name=(null)
vaInitialize failed with error code -1 (unknown libva error),exit
You are trying to send an empty document, exiting.
dni@ubi-htpc:~$ cat ~/.kodi/temp/kodi.log | pastebinit
http://paste.ubuntu.com/26340192/
dni@ubi-htpc:~$ dmesg | pastebinit
http://paste.ubuntu.com/26340193/
dni@ubi-htpc:~$ id | pastebinit
http://paste.ubuntu.com/26340194/
dni@ubi-htpc:~$ amixer | pastebinit
amixer: Mixer attach default error: No such file or directory
You are trying to send an empty document, exiting.
dni@ubi-htpc:~$ cat /var/log/Xorg.0.log | pastebinit
http://paste.ubuntu.com/26340202/
Your user is not member of video nor audio (see useradd on the first page)
Quote:uid=1000(dni) gid=1000(dni) groups=1000(dni),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),110(lxd),115(lpadmin),116(sambashare)
Hi, all. Older poster here.
Former XBMC->Kodi install (2:17.6+git20171114.2125-final-0trusty) on a Ubuntu (14.04.5 LTS) Zotac box was getting a bit long in the tooth, so decided to go for some new silent hardware (Gigabit GB-BXBT box) and follow this guide. Everything worked pretty much perfectly, give or take the odd mistake I made.
However, this new setup doesn't appear to be as stable. When I was first configuring the display options (setting overscan values) to resize the display port sometimes the screen would blank then bring the Kodi logo up, as though Kodi itself had restarted - but forgetting the overscan values so the picture was off-display. I've also noted that although the screen fits the TV fine when media isn't playing, when something's playing those overscan values aren't honoured - the date/time and subtitle menu is offscreen again.
But that's a moot point - the issue I have is Kodi seemingly restarting itself when not playing (returning to a blank screen), and crashing when it does - actually freezing the box itself part-way through the episode I'm watching: the image appears frozen onscreen and the box no longer responds to pings. Unfortunately this means I don't have a proper debug log (nothing is written).
I've uploaded information about my setup to pastebin:
http://paste.ubuntu.com/26379132/
error: XDG_RUNTIME_DIR not set in the environment.
libva info: VA-API version 0.40.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_39
libva info: va_openDriver() returns 0
http://paste.ubuntu.com/26379133/
http://paste.ubuntu.com/26379134/
http://paste.ubuntu.com/26379135/
http://paste.ubuntu.com/26379136/
http://paste.ubuntu.com/26379137/
http://paste.ubuntu.com/26379138/
Hope those will shed some light. I'm not convinced it's the kodi build, it seems I'm using the same on my Zotac and that's pretty stable, but hopefully those logs can be of help. If not - any other commands I can run, or information I can provide?